The command line tool (as_gddmgr.exe) lets you check data integrity at recovery point level and data store level for deduplication data stores.
You can use this tool to regenerate a hash database in case of a hash database failure. You can also use this tool to query and manage the backend purge and disk reclamation for deduplication data stores.
The output of the command is displayed on the Windows command console. The tool also generates a log file in the “Logs” folder. For example, as_gddmgr_2014-9-4_11-14-22-655.log is a log file that contains all details.
You can find as_gddmgr.exe in the "Bin" folder of the UDP installation path.
as_gddmgr.exe
-Scan ChecksumUDPSession <data store name> -Node [<All> |<UDP agent node name>] -RecoveryPoint [<All>|<recovery point number>] [-Password < data store password >] [-LogLevel <n>]
-Scan VerifyRefCount <data store name> [-LogLevel <n>]
-Scan VerifyData <data store name> [-Password <data store password>] [-LogLevel <n>]
-Scan VerifyAll <data store name > [-Password < data store password >] [-LogLevel <n>]
-Scan RebuildHash <data store name> [-NewHashPath <new hash path>] [-LogLevel <n>]
-Scan RebuildHashWithIndexPath <index path> -NewHashPath <new hash path> [-LogLevel <n>]
-Purge Start <data store name>
-Purge Stop <data store name
-Purge Status <data store name>
-Purge StartToReclaim <data store name>
Checks data integrity for the specified recovery point.
Specifies the agent node name.
Specifies the recovery point to check for integrity.
Specifies the data store password.
Specifies the log level number.
Scans index files and reference files to verify reference count recorded in the hash database. Before you specify this option, manually stop the deduplication data store.
Scans data files and then regenerates the hash keys by comparing this with the reference file. Before you specify this option, manually stop the deduplication data store.
Performs both the VerifyRefCount and VerifyData operations. Before you specify this option, manually stop the deduplication data store.
Specify data store name and then regenerate the hash database by scanning index and reference files. Before you specify this option, manually stop the deduplication data store.
Specify the deduplication index path and then regenerate the hash database by scanning index and reference files. The option is used only when the data store is not present on any recovery point servers.
Enables running the purge and disk reclamation in parallel with other regular Arcserve UDP jobs. Running purge in parallel may cause throughput degradation of regular Arcserve UDP jobs.
Disables running the purge and disk reclamation in parallel with other regular Arcserve UDP jobs.
Queries the status of purge or disk reclamation.
Enables running the purge and disk reclamation in parallel with other regular Arcserve UDP jobs. It skips the real purge phase, which finds out the obsolete data block, and then directly start disk reclamation phase, which free up the disk space. The side effect of this option is that it might degrade the efficiency of the disk reclamation because the real purge might find out more obsolete data blocks in the data files, but the disk reclaim does not wait for the real purge phase to complete. In addition, running purge in parallel might cause the throughput degradation of regular Arcserve UDP jobs.
Note: Be aware that the following options might run for a long time because the operation scans many files in the deduplication data store.
as_gddmgr.exe -Scan ChecksumUDPSession GDDDataStore1 -Node All -RecoveryPoint All -Password 123
as_gddmgr.exe -Scan ChecksumUDPSession GDDDataStore1 -Node myComputer -RecoveryPoint 1 -Password 123
as_gddmgr.exe -Scan VerifyRefCount GDDDataStore1
as_gddmgr.exe -Scan VerifyData GDDDataStore1 -Password 123
as_gddmgr.exe -Scan VerifyAll GDDDataStore1
as_gddmgr.exe -Scan RebuildHash GDDDataStore1
as_gddmgr.exe -Scan RebuildHash GDDDataStore1 -NewHashPath C:\NewHashPath
as_gddmgr.exe -Scan RebuildHashWithIndexPath D:\GDDDataStore\Index -NewHashPath D:\NewHashPath
as_gddmgr.exe -Purge Start GDDDataStore1
as_gddmgr.exe -Purge Stop GDDDataStore1
as_gddmgr.exe -Purge Status GDDDataStore1
as_gddmgr.exe -Purge StartToReclaim GDDDataStore1
|
Copyright © 2016
|
|