Forum Discussion

phoenigs's avatar
phoenigs
Level 3
9 years ago

Deduplication - Restore

Hi

We have troubles restoring a deduplication store.

Following configuration: File backup with backup agent from a File server to Backup Exec Server (running on Windows Server 2012 R2)

to a deduplication store, works fine.

This deduplication store is written to a tape every day, it works fine.

If I try to restore the deduplication store back to file system from tape, there is only an empty folder called "BackupExecDeduplicationStorageFolder". I tried several backups to restore, without success.

Any ideas?

Best Regards,

Peter

 

2014
Backup and Recovery
Backup Exec
Windows Server (2003-2008)
  • Colin_Weaver's avatar
    Colin_Weaver
    9 years ago

    The more usual/recommended practice for backing up deduplication data to tape is to duplicate the backup sets and not backup the deduplication store itself. So your backup job definitions will have full/incremental/differential stages to deduplication and then duplication stages to tape.

    Main Advantage: For most data types you can restore directly from tape back to the original servers without restoring into Deduplication First (GRT sets may need  to stage on disk although the job configuration for the restore is still direct back to the original server as Backup Exec can do the staging for you) In the event of a complete disaster it is usually more important to restore data to critical production servers than it is to recover the backup exec server itself making this ability desirable.

    Main Disadvantages: the data is rehydrated onto tape  (but can be compressed) so will use more tape storage than the storage in deduplication requires. Also if a DR process against the backup server is needed you will either be starting with an empty deduplication folder (with your backup history still on tape) and just let new backups populate the deduplication storage OR you will need to deduplicate back from tape into deduplication (one set/server at a time) in an attempt to 'seed' the deduplication storage with historical backup sets.

    --------

    If you intend to backup the deduplication store itself, this must be done via Shadow Copy Components and not via the file system of the volume that owns the Deduplication Storage - if you backup via the file system I believe you may end up with an empty folder in the backup set. (which might be what you describe)

    Main Advantage: Less space used on tape.

    Main Disadvantages: to get back any data you have to recover the whole of the deduplication store first and then restore the data back to the original servers. Also to get back any data you have to take the whole of the deduplication store back in time to the timing of the backup - which means any newer backup set data will be lost - as such this process is really only for complete DR of the Backup Exec Server

    ----------

    Of course you could do both backup methods but that would use even more tapes.

1 Reply

Sort By
  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    9 years ago

    The more usual/recommended practice for backing up deduplication data to tape is to duplicate the backup sets and not backup the deduplication store itself. So your backup job definitions will have full/incremental/differential stages to deduplication and then duplication stages to tape.

    Main Advantage: For most data types you can restore directly from tape back to the original servers without restoring into Deduplication First (GRT sets may need  to stage on disk although the job configuration for the restore is still direct back to the original server as Backup Exec can do the staging for you) In the event of a complete disaster it is usually more important to restore data to critical production servers than it is to recover the backup exec server itself making this ability desirable.

    Main Disadvantages: the data is rehydrated onto tape  (but can be compressed) so will use more tape storage than the storage in deduplication requires. Also if a DR process against the backup server is needed you will either be starting with an empty deduplication folder (with your backup history still on tape) and just let new backups populate the deduplication storage OR you will need to deduplicate back from tape into deduplication (one set/server at a time) in an attempt to 'seed' the deduplication storage with historical backup sets.

    --------

    If you intend to backup the deduplication store itself, this must be done via Shadow Copy Components and not via the file system of the volume that owns the Deduplication Storage - if you backup via the file system I believe you may end up with an empty folder in the backup set. (which might be what you describe)

    Main Advantage: Less space used on tape.

    Main Disadvantages: to get back any data you have to recover the whole of the deduplication store first and then restore the data back to the original servers. Also to get back any data you have to take the whole of the deduplication store back in time to the timing of the backup - which means any newer backup set data will be lost - as such this process is really only for complete DR of the Backup Exec Server

    ----------

    Of course you could do both backup methods but that would use even more tapes.