I had an old Data Domain 2500 that was out of support, but I still used it for some old archival secondary backups until I find them a better supported home. Then before I could get the purchase of the new storage I had a hardware failure. I was told by upper management that they are unwilling to invest money into a fix and that they were willing to accept the loss of the data.
This still leaves me with an Avamar yelling at me about data integrity issue because it can not see the old Data Domain.
When I go to the Server tab and attempt to delete the Data Domain it fails with an “Error searching for backups”. Now we do need to make sure that no datasets or replication point are pointing to (or using) the old Data Domain. Once you have verified this, you can then proceed with the following command to list all Data Domains.
admin@avamar:~/>: mccli dd show-prop
0,23000,CLI command completed successfully.
IPv4Hostname IPv6Hostname TotalCapacity ServerUtilization BytesProtected FileSystemAvailable FileSystemUsed UserName DefaultReplicationStorageSystem TargetForAvamarCheckpointBackups MaximumStreamsForAvamarCheckpointBackups MaximumStreams MaximumStreamsLimit InstantAccessLimit DDOSVersion SerialNumber ModelNumber EncryptionStrength AuthenticationMode MonitoringStatus Cloud Tier DDBoostLicensed DDBoostEnabled DDBoostUserEnabled DDBoostUserStatus DDBoostOptionStatus SNMPstatus FileSystemStatus Synchronizationofmaintenanceoperations
-------------------------- ------------ ------------- ----------------- -------------- ------------------- -------------- -------- ------------------------------- -------------------------------- ---------------------------------------- -------------- ------------------- ------------------ --------------- -------------- ----------- ------------------ ------------------ ---------------- ---------- --------------- -------------- ------------------ ----------------- -------------------- ---------- ------------------- --------------------------------------
dd2500.local N/A 0.0 GiB 0% 42.0 GB 0.0 GiB 0.0 GiB ddboost Yes No 0 50 0 1 5.7.5.6-580632 FLA0123456789 DD2500 none none Unknown disabled true false true User Valid Option not Available Enabled File System Unknown on
dd6800.local N/A 138669.4 GiB 68% 66.4 TB 44646.3 GiB 94023.1 GiB ddboost No Yes 2 50 400 32 6.1.2.20-606786 APC0123456789 DD6800 none none OK disabled N/A N/A N/A N/A N/A N/A N/A N/A
admin@avamar:~/>Now that we see the two current Data Domains we can copy its name and add it to the following command, “mccli dd delete –name=dd2500.local –force”. This will run for some time and once completed the Data Domain will have been removed.
admin@avamar:~/>: mccli dd delete --name=dd2500.local --force
0,30936,Deleted Data Domain system.
Attribute Value
------------------------- -------------------------------------------------------------------
replication-storage-check Data Domain system is the only default replication storage system.
ipv6Hostname
backup-search Error searching for backups.
force-delete Force delete option was in use for the Data Domain system deletion.
ipv4Hostname dd2500.local
admin@avamarIf we repeat the first command we will get the same results, except without the old Data Domain.
admin@avamar:~/>: mccli dd show-prop
0,23000,CLI command completed successfully.
IPv4Hostname IPv6Hostname TotalCapacity ServerUtilization BytesProtected FileSystemAvailable FileSystemUsed UserName DefaultReplicationStorageSystem TargetForAvamarCheckpointBackups MaximumStreamsForAvamarCheckpointBackups MaximumStreams MaximumStreamsLimit InstantAccessLimit DDOSVersion SerialNumber ModelNumber EncryptionStrength AuthenticationMode MonitoringStatus Cloud Tier DDBoostLicensed DDBoostEnabled DDBoostUserEnabled DDBoostUserStatus DDBoostOptionStatus SNMPstatus FileSystemStatus Synchronizationofmaintenanceoperations
-------------------------- ------------ ------------- ----------------- -------------- ------------------- -------------- -------- ------------------------------- -------------------------------- ---------------------------------------- -------------- ------------------- ------------------ --------------- -------------- ----------- ------------------ ------------------ ---------------- ---------- --------------- -------------- ------------------ ----------------- -------------------- ---------- ------------------- --------------------------------------
dd6800.local N/A 138669.4 GiB 68% 66.4 TB 44646.3 GiB 94023.1 GiB ddboost No Yes 2 50 400 32 6.1.2.20-606786 APC0123456789 DD6800 none none OK disabled N/A N/A N/A N/A N/A N/A N/A N/A
admin@avamar:~/>We shouldn’t get anymore data integrity alerts. You can clear the existing alerts by going to the Avamar console and clicking under the “Critical Events” on the red “ERRORS” button. The same location is found under the “Administration” tab and then “Event Management” tab.
We need to click on the Actions tab, then “Event Management” and finally “Clear Data Integrity Alert…”
Type in all-caps AVAMARDATAOK and click OK.
We can click the blue “Select All Events” and then the yellow “Acknowledge Events”
This will have cleared all Events. Your Avamar will do a cleanup at the next scheduled maintenance time. We are done! Let me know what you think below.
Cheers!