Job throttling


Published on

How we can use Bandwidth throttling from StorageEdge for SharePoint.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Hi Everyone, welcome to StorageEdge video tutorial. StorageEdge is all about storage optimization for SharePoint.
  • Wediscussedexternalizing Blobs to multiple tiers in our previous tutorials here on our youtube channel. Today, in this demo we are going to focus on how exactly we can use Bandwidth throttling from StorageEdge for SharePoint.
  • SharePoint uses SQL server heavily to store all its application data and documents. As the number of documents increase it becomes unmanageable inside SQL server. We discussed Blob externalization to solve this problem in another tutorial.Normally, in a medium to large size companies, the Sharepoint content database size is very large. The database size varies from company to company but it is usually in 100s of Gigabytes to terra bytes of Blobs. The larger the database size the longer it will take to externalize the content to your SAN/NAS storage. During this long running activity, which may prolong for days to weeks or months. you cannot afford to exhaust your CPU and Bandwidth resources and let your SharePoint applications slow down.You never want your SharePoint applications to be in a “Not Responding” state.What if you can schedule the migration job for the night hours ? What if you can control your bandwidth usage based on your peak time or low activity hours ?
  • Yes, with StorageEdge job throttling you can schedule to run your migration job at various speeds during different times. You can do the time based bandwidth throttling where you can specify multiple time slots to schedule various migrations jobs. So you can schedule the long running jobs for a time slot over night hours. Or you can schedule other long running activities over the weekend when there are less or no users on your SharePoint site. This will enable you to utilize your resources more efficiently.You can also control the Bandwidth consumption or speed at which the long running jobs should run in each time slot. For example you can completely pause these activities in peak hours, run it at medium speed (100-200 Blobs/sec) during night hours and run it at full speed at weekendsTime based and Size based Bandwidth throttling together give you full control over Bandwidth and resource usage.
  • You can use job throttling for a number of long running activities. When you are archiving your old blobs from your NAS /SAN storage tier to another cheaper tier e.g. Cloud Tier, it may take hours to days depending upon your data size. This is an excellent candidate for Bandwidth Throttling.Job throttling can also be used for Reverting the content back to your database. You can also use job throttling for Clean Garbage job to periodically clean deleted blobs out of your externalized content. We have discussed job throttling for content migration from SQL to your external storage. Job throttling can also be used for EBS to RBS migration job.
  • Job throttling

    1. 1.
    2. 2. Bandwidth Throttling prevents SharePoint slow down in BLOB externalization<br /><br />
    3. 3. BLOB Externalization is a long running activity<br />Database offloading may take weeks.<br />Tera Bytes of BLOBs require days to weeks to migrate<br />High CPU and Bandwidth usage<br />Slows down SharePoint applications<br />Challenges with BLOB Externalization?<br /><br />
    4. 4. <ul><li>Time based throttling
    5. 5. Use multiple time slots for scheduling
    6. 6. Pause during peak hours</li></ul>Size based throttling<br />Specify number of blobs transfer per second<br />Solution: Job throttling with StorageEdge<br />
    7. 7. Archiving Content on other storage tiers e.g cloud.<br />Revert Content Job<br />Garbage Cleaning<br />Migration<br />EBS to RBS migration<br />Other Content Migration Jobs<br />