We have a customer that has an Isilon for disk storage.
Backup speeds are ok, but DASH to DR or Copy to Tape speeds are terrible. “Last night’s” backups copy to DR at no more than 500GB/hr, if we’re lucky and copy to tape speeds do not exceed 200GB/hr.
Index and DDB are on NVME and tested fine.
Fallen Behind Copies are literally years behind.
Both Commvault and Isilon have checked it out and cannot do anything about it.
We did spec Hyperscale before implementation but we were overruled and now I sit with this issue. Very frustrating.
Has anyone experienced dog-slow Isilon restores, DASH copies or Tape copies?
How were you able to overcome this?
It’s gotten so bad that we are going to ask Commvault to either try help us fix it or reconsider certifying it as a DL destination.
Best answer by CSumner
There defiantly looks to be a read issue with the source library.
Each thread translates to 1 stream so per stream you are seeing sub optimal performance from the library.
Additional settings or a change configuration at this point will not give you the performance boost you need.
I would look at engaging your storage support to see why the read speeds are so slow.
You should also see very slow speeds if you attempt to copy a large file from the storage to the MA via the configured share. This with the two documents above should be more than enough evidence for your storage support to investigate.