FreeDestNMVBlocks
Command:
FreeDestNMVBlocks DcsSnap{relationship#}
Description:
Perform this command on a snapshot relationship whose destination virtual volume is from an NMV, to free NMV storage units allocated to that NMV destination volume. This command should be used after disabling, and before re-enabling the snapshot relationship.
(e.g., If you previously performed a Complete Image on a snapshot relationship and now you want to re-enable it, perform this command before performing the enable to clear the used NMV data blocks.)
Arguments:
relationship# : A value that represents the snapshot relationship number.
For example: FreeDestNMVBlocks DcsSnap1
Return Values:
0: success
-1: failure. Call the GetLastErrors command for extended error code information.
Error Codes:
DCSPIT_ERROR_INVALID_PARAMETERS: There is a potential version mismatch between API and driver, or the snapshot relationship is currently enabled.
DCSPIT_ERROR_DEVICE_DOES_NOT_EXIST: The snapshot relationship does not exist.
DCSPIT_ERROR_NO_SUCH_DEVICE: Either the Snapshot-configured volume does not exist, or Snapshot has not yet been established on the disk partition.
DCSPIT_ERROR_INSUFFICIENT_RESOURCES: Memory allocation has failed.
ERROR_INVALID_PARAMETER: hDeviceHandle is an invalid handle.
DCSPIT_ERROR_INVALID_DEVICE_REQUEST: The destination virtual volume is not an NMV.
DCSPIT_ERROR_DEVICE_BUSY: The NMV is still reclaiming allocated chunks and the NMV destination volume should not be used until a subsequent call of this CLI command returns successfully. Continue to re-issue the command until a successful status is returned.
Comments:
A successful return from this command indicates that all snapshot relationship destination volumes are NMVs and that the associated NMV pools have enough free blocks for the NMVs to be used.
This command can only be performed successfully if the snapshot relationship is disabled.
This command has no effect on destination volume created from partitioned-based volumes.