Creating new Cloud deduplication storage

Problem

Creating new Cloud deduplication storage

Solution
 

Note: Gold or Silver edition license is required to configure a Cloud Deduplication Storage

1) The name of the cloud deduplication storage cannot be modified once the cloud deduplication storage is created. When importing the existing cloud deduplication storage mention the same name of the storage folder present in the bucket.

For more information on importing cloud deduplication storage, please refer the following article: https://www.veritas.com/support/en_US/article.100050611

2) If encryption is enabled on cloud deduplication storage, then the encryption key type should be AES – 256bit PBKDF2. Encryption keys used for the cloud deduplication storage should always be backed up.

For more information, please refer the following article:
https://www.veritas.com/support/en_US/article.100050759

3) Once the encryption is enabled, it cannot be disabled but the encryption key can be changed from the device properties page. If encryption key is not enabled while creating the Cloud deduplication storage device, then it can be enabled from the device properties page.

4) While creating the cloud deduplication storage please check the cache size. For more information, please refer the following article:
https://www.veritas.com/support/en_US/article.100050614

In case there are more than one cloud deduplication storage on the device and the cache folder size is full then steps to clear the cache folder are mentioned in the troubleshooting section.

5) Alibaba Cloud provider is not supported for creating cloud Deduplication Storage. Deep Archive and Glacier storage tiers are also not supported.

6) All Cloud deduplication Storage on a system use a common encryption key which needs to be provided when creating first cloud deduplication storage.

Troubleshooting errors encountered during creation of cloud deduplication Storage

Error 1) Cloud Deduplication Storage device operation failed.

Perform following steps to resolve above error:

1) After deleting a cloud deduplication storage, manual steps are required to clean up the folder data. If not done, the creation of subsequent cloud Deduplication storage will fail. For more information, please refer following article

https://www.veritas.com/support/en_US/article.100050612
(Skip step 2 and 3 from above article)
 

Error 2) Failed to create Cloud Deduplication Storage. The storage with the same name already exists in the selected bucket.

Perform following steps to resolve above error:

1) Check if there is an existing sub folder by the same name under the bucket selected for creating cloud deduplication storage. Please make sure a different name is used for creating a new cloud deduplication storage. In order to import existing cloud deduplication storage data, different steps are required. Please refer the following article for more details:

https://www.veritas.com/support/en_US/article.100050611

2) Please check the cache folder name “ds_<integer>” is present in that case you must delete that folder and retry creating the cloud deduplication storage.

Perform following steps to resolve this error:
 

Step 1: Disable the Disk storage lockdown setting from the 
               Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage lockdown setting.

Disabling Disk Storage Lockdown setting is a temporary step done for troubleshooting and must not be left permanent to avoid any data loss due a security threat.

Step 2: On the command prompt, enter the following command:

<Backup Exec install path>\pddecfg -a listcloudlsu

A list of cloud deduplication storage devices is displayed with Cache path “<BackupexecDeduplicationFolder>\data\ds_<integer>”. Note down the all the Cache path.
Following image shows how to find out CachePath.

Step 3: Go to <BackupexecDeduplicationFolder>\data and remove the ds_<integer> Cache Folder which are not present in the above list of Cache path.

Step 4: Enable the Disk storage lockdown setting from the 
               Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage lockdown setting.

Error 3) In case the bucket/sub bucket is deleted from the cloud storage and the Cloud deduplication storage is in discovering state

Perform following steps to resolve this error:

1. First delete Cloud Deduplication Storage from Backup Exec console, execute spoold –removepartion and clear the cache folder. If the bucket/sub-bucket was deleted then device goes into discovery state. More info refers following article for delete Cloud Deduplication Storage.

               https://www.veritas.com/support/en_US/article.100050612

2. In case if steps mentioned in above article are not followed and bucket/sub-bucket is directly deleted. After that you restarted Deduplication and Backup Exec services, in this case devices may go into discovering state so follow following steps to resolve this problem.

1) On the command prompt, enter the following command:

<Backup Exec install path>\pddecfg -a listcloudlsu

A list of cloud deduplication storage devices is displayed. Please note down StorageID & CachePath for deleted bucket/sub-bucket.
Following image shows how to find out StorageId and CachePath.

2) Stop Deduplication Services from Service Manager And restart BE services.

3) Disable the Disk storage lockdown setting from the 
Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage lockdown setting.

Disabling Disk Storage Lockdown setting is a temporary step done for troubleshooting and must not be left permanent to avoid any data loss due a security threat.

4) Delete the storage container or bucket configurations in spoold using the following command:
 

<Backup Exec install path>\spoold --removepartition <StorageID>
 

5) Remove the cache folder using the following command:
 

rmdir /S <CachePath>
  You can delete cache folder using window explorer also.
 

6) Start Duplication services and Restart Backup Exec Services.

7) From the Backup Exec user interface, right-click the cloud deduplication storage, and click Disable.

8) Right-click the cloud deduplication storage and click Delete. 

9) Enable the Disk storage lockdown setting from the 
Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage lockdown setting.

Error 4) In case the cache folder size is full and to clear the cache folder following steps need to be performed:

 Step 1: On the command prompt, enter the following command:

                <Backup Exec install path>\pddecfg -a listcloudlsu

               A list of cloud deduplication storage devices is displayed. Please note down CachePath.

                Following image shows how to find out CachePath.

 Step 2: Stop Backup Exec and Deduplication services.

 Step 3: Disable the Disk storage lockdown setting from the 
               Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage lockdown setting.

Disabling Disk Storage Lockdown setting is a temporary step done for troubleshooting and must not be left permanent to avoid any data loss due a security threat.

 Step 4: Remove the cache folder using the following command:

                rmdir /S <CachePath>

               You can delete cache folder using window explorer also.

Step 5: Enable the Disk storage lockdown setting from the 
             Configuration and Settings -> Backup Exec setting -> Network and Security -> Disk storage-lockdown setting.

Step 6: Start Backup Exec and Deduplication services