Skip to main content
Solved

CommServe DR backup (Dump + Storage Policy) to Deduped Storage Library

  • 5 March 2024
  • 3 replies
  • 48 views

Hi Vaulters,

 

Hope everyone is doing good.

 

In our backup infra, we have a dedicated backup NAS storage array, in which deduplication will be enabled (Commvault Deduplication will not be used). Since it is a NAS, we intended to use it as our export location for our CommServe DR backup and also as our main Disk Library/Mount Path for the CommServeDR storage policy.

 

We read somewhere in the documentation that deduplication for CommServeDR is not recommended and should not be enabled in CommVault. Does that also imply storage Deduplication ? If so, does this impact for the DUMP export or Storage Policy copy or both ?

 

We’d love to get more details regarding this. As our NAS is only configured with one single shared FileSystem with Dedup enabled.

 

Kinf regards.

3 replies

S
Rank
Userlevel 2
Badge +9

Hi @Commvault Engineer ,

 

Yes, recomendation is always not to have Commserve DR backup deduplicated. That is why we see Commserve DR storage policy will not have deduplication enabled. 

 

If there is a problem and we have to restore CSDB, if we can recover it in Original format then we should be good.

 

Few recomendations,

Recommended

  • You must store the Disaster Recovery (DR) backup in a dedicated network location that is accessible from both the production host and the new server host that is used for recovery.

  • Do not use a local disk or local clustered disk because it is not safe and recommended.

  • Use a UNC path to access the network location. Make sure that this dedicated location is not used for any other CommServe task.

  • Do not use administrative shares as an export location. For example, \\MyServer\E$\.

  • For a network location that is on a Windows mount path, the software enables ransomware protection by default. For a network location that is on a Linux mount path, you must enable ransomware protection manually.

  • Do not use the Commvault installation directory as a backup location for DR backups to local disk. By default, the Commvault software enables ransomware protection for DR backup folders on Windo

ref: DR Backup Settings (Export Settings) (commvault.com)

 

Regards,

Suleman 

C
Userlevel 3
Badge +12

Hi @Commvault Engineer ,

 

Yes, recomendation is always not to have Commserve DR backup deduplicated. That is why we see Commserve DR storage policy will not have deduplication enabled. 

 

If there is a problem and we have to restore CSDB, if we can recover it in Original format then we should be good.

 

Few recomendations,

Recommended

  • You must store the Disaster Recovery (DR) backup in a dedicated network location that is accessible from both the production host and the new server host that is used for recovery.

  • Do not use a local disk or local clustered disk because it is not safe and recommended.

  • Use a UNC path to access the network location. Make sure that this dedicated location is not used for any other CommServe task.

  • Do not use administrative shares as an export location. For example, \\MyServer\E$\.

  • For a network location that is on a Windows mount path, the software enables ransomware protection by default. For a network location that is on a Linux mount path, you must enable ransomware protection manually.

  • Do not use the Commvault installation directory as a backup location for DR backups to local disk. By default, the Commvault software enables ransomware protection for DR backup folders on Windo

ref: DR Backup Settings (Export Settings) (commvault.com)

 

Regards,

Suleman 

Hi Suleman,

 

Thanks a lot for all the provided details. This is really helpful.

 

Our concern is that our main NAS storage is already used with Dedup enabled on it. Basically, the only UNC that can be used for our CommServe Export is the NAS storage and has Dedup, also regarding the storage policy (CommServeDR) it will be set on the same NAS storage with Dedup as it is dedicated for our backup data.

 

Is there any impact on using the storage ? Knowing that the Dedup is set on Hardware side and not Commvault’s side.

 

Regards.

S
Rank
Userlevel 2
Badge +9

Hi @Commvault Engineer ,

 

As deduplication is at the storage level, we write and read the data it is in the native format. Deduplication happens at the backedned. Therefore there should be no issues.

 

Regards,

Suleman

Reply


Terms & ConditionsCookie settings