cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Deduplication Storage Advice

StuartWhitehous
Level 3

Hi,

We are using Backup Exec 20.1 and testing the Deduplication option. All test's we've done so far are looking good, but I need some advice on backing up the Deduplication Storage.

Running a Deduplication Storage backup job is no problem, just select "Shadow Copy Components\User Data\Backup Exec Deduplication Storage" from the BE server (https://www.veritas.com/support/en_US/doc/72686287-131623464-0/v70445236-131623464).

Currently the Deduplication Storage volume is 32TB and 19TB is in use, a full Shadow Copy backup to tape will take over a day to complete but if we could run an Incremental or Differential backup during the weekday this should reduce our backup window, can this be done?  If so, would there be any complications if a restore is needed?

 

Thanks

Stuart

2 ACCEPTED SOLUTIONS

Accepted Solutions

DevG
Level 4
Employee Accredited Certified

Hello Stuart,

As you rightly pointed out, Deduplication storage folder needs to be backed up through 'Shadow Copy Components' resource. "Shadow Copy Components" and "System State" can´t be backed up using either Incremental or Differential, and Backup Exec will automatically use the Full method if either of these are included in the selection list, regardless the backup method chosen in the job settings (100020854)

View solution in original post

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

You might find it makes more sense to duplicate the  backup sets to another device instead of actually backing up the Deduplication Storage itself.

Pros

- restores of a duplicated backup set on tape can be sent directly back to the source server (no need to restore the deduplication folder before you can restore your data), although the GRT sets will still stage for individual files etc.

- you can schedule and manage when the duplicate jobs run to best fit into any critical time windows as they don't have to run in a single time window

- if one tape is somehow damaged/corrupted/lost it will have less of an effect on the backup sets on other tapes (this assumes your deduplication folder backup does not fit on one tape)

- you can choose to have different frequencies for running the duplicate jobs of less critical servers/resources 

- you won't need to run a single very long job on regular occasions

- a Shadow Copy Backup of Deduplication Storage is for DR ONLY as you cannot merge such a restore with an active deduplication folder (it would just take the whole folder back to the date of the backup and all newer sets would be lost.) whereas you can duplicate back into Deduplication or Restore a tape based set without affecting the newer backup sets.

Cons:

- if you do lose the Deduplication storage or the BE server then repopulating the deduplication folder would require a number of duplicate jobs back from tape (or you can just start running new backup jobs and use the tapes for any older restores)

- if you restore the BEDB and Catalogs after a DR of the BE server and have just recreated an empty deduplication storage folder instead of restoring it, then you will have data in the BEDB and catalogs that relate to sets that do not exist in your deduplication storage (which you might need formal assistance from tech support to clean up)

View solution in original post

4 REPLIES 4

DevG
Level 4
Employee Accredited Certified

Hello Stuart,

As you rightly pointed out, Deduplication storage folder needs to be backed up through 'Shadow Copy Components' resource. "Shadow Copy Components" and "System State" can´t be backed up using either Incremental or Differential, and Backup Exec will automatically use the Full method if either of these are included in the selection list, regardless the backup method chosen in the job settings (100020854)

Hi,

Thanks for the quick responce,  do you have any advice to reduce the backup window for Deduplication Storage backups?

Thanks

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

You might find it makes more sense to duplicate the  backup sets to another device instead of actually backing up the Deduplication Storage itself.

Pros

- restores of a duplicated backup set on tape can be sent directly back to the source server (no need to restore the deduplication folder before you can restore your data), although the GRT sets will still stage for individual files etc.

- you can schedule and manage when the duplicate jobs run to best fit into any critical time windows as they don't have to run in a single time window

- if one tape is somehow damaged/corrupted/lost it will have less of an effect on the backup sets on other tapes (this assumes your deduplication folder backup does not fit on one tape)

- you can choose to have different frequencies for running the duplicate jobs of less critical servers/resources 

- you won't need to run a single very long job on regular occasions

- a Shadow Copy Backup of Deduplication Storage is for DR ONLY as you cannot merge such a restore with an active deduplication folder (it would just take the whole folder back to the date of the backup and all newer sets would be lost.) whereas you can duplicate back into Deduplication or Restore a tape based set without affecting the newer backup sets.

Cons:

- if you do lose the Deduplication storage or the BE server then repopulating the deduplication folder would require a number of duplicate jobs back from tape (or you can just start running new backup jobs and use the tapes for any older restores)

- if you restore the BEDB and Catalogs after a DR of the BE server and have just recreated an empty deduplication storage folder instead of restoring it, then you will have data in the BEDB and catalogs that relate to sets that do not exist in your deduplication storage (which you might need formal assistance from tech support to clean up)

Hi,

Thanks for your help, need to re-think but I may have a cunning idea ;)