We are implementing a new StoreOnce system as primary copy and test performance (and other topics) between FC-catalyst stores and FC-Virtual Tape Libraries
A Catalyst Store on StoreOnce can be configured either as high-bandwidth or low-bandwidth
- high-bandwidth: Backup server (media agent in case of CommVault) will send backupstreams unmodified to StoreOnce and then StoreOnce will do dedupe etc. before finally storing the data on its disks.
- low-bandwidth: already the backup server (media agent) will do de-dupe and only sends new things to the StoreOnce.
VTL is similar to high bandwidth (all goes from MA over FC-SAN to StoreOnce and only there the data reduction takes place).
As we have plenty of ressources on FC-SAN and the StoreOnce is made for doing all the datareduction we’d like to get StoreOnce connected/configured in high-bandwidth for Catalyst, especially as important servers are doing LAN-free backups (have their own media agent locally installed to directly backup over FC) - having them to do the extra DeDupe-work (CPU, RAM,...) is not what we want, the StoreOnce shall do it.
When we force the Catalyst to high-bandwidth we get this error in CommVault
Error occurred in Disk Media, Path [CS_Test1\STYMSI_07.18.2024_13.35\CV_MAGNETIC\V_3663970] [-3203 OSCLT_ERR_INVALID_BANDWIDTH_MODE]. For more help, please call your vendor's support hotline.
when we enable both ways (primary low, secondary high OR vice versa) then CommVault always selects low bandwith (can be seen in backup speed vs. interface usage. there is much less data physically transfered than backup size. thus the media agent is doing dedupe (which we do not want).
any experience / help available? unfortunately neither documentation of CommVault nor HPE is helping us...