HyperV ZDB on 3PAR with HW provider in DP 9.08: Stability???

Hello,

Great $ Subject is working with a 14 node cluster  and writing with an awesome speed to a CoFC on a SO 5100,

but

No single execution of a huge job works flawless

There are no 2 run's with an identical behavior

To master it, we're gonna split it (256 VM's and 70 TB of data) up into different Jobs and present the 3PAR vcopy's to different backup servers. But even at our initial splitting we still encountered "non-predictable & non-repeatible errors"

Bottom line Q: how to stabilise this kind of backups?

cause when all is virtualized and centralised with one huge consolidation, our backup should be able to cope with it ALL WAYS.....

or do we start pointing to Microsoft?

Luc Minnaert

Parents
  • Hello Luc, can you show us what are the specific errors errors you get or see from Data Protector side so we can have an opinion and can suggest?

  • Hello,

    excerpts out of the errors are:

    Volume shadow copy service failed to create Shadow copy set

    Writer 'Microsoft Hyper-V VSS Writer' failed to prepare the files for some components in the backup.

    From: OB2BAR_VSSBAR@... :        It was not possible to create Volume Shadow Copies

    Solution could be to have consequtive runs since the issue is "random" , so we have all data  (we do not have to care of uplicates since our StoreOnce is taken care of that) but...the data volume is huge and there are about 2000 backup jobs a day to take care of and since we have already  "There are no available connections on the StoreOnce device. Retrying..."  this too is not an option.

    Yesterday the Virtual environment backup was splitted in 3 part's (based on CSV on 3-PAR) with each their dedicated backup server.

    Any tip to stabelize the VSS part..... more than welcome

    Luc

     

Reply
  • Hello,

    excerpts out of the errors are:

    Volume shadow copy service failed to create Shadow copy set

    Writer 'Microsoft Hyper-V VSS Writer' failed to prepare the files for some components in the backup.

    From: OB2BAR_VSSBAR@... :        It was not possible to create Volume Shadow Copies

    Solution could be to have consequtive runs since the issue is "random" , so we have all data  (we do not have to care of uplicates since our StoreOnce is taken care of that) but...the data volume is huge and there are about 2000 backup jobs a day to take care of and since we have already  "There are no available connections on the StoreOnce device. Retrying..."  this too is not an option.

    Yesterday the Virtual environment backup was splitted in 3 part's (based on CSV on 3-PAR) with each their dedicated backup server.

    Any tip to stabelize the VSS part..... more than welcome

    Luc

     

Children
No Data