Monitoring Hot Copy Execution

A Storage Manager (SM) that is executing a hotcopy does so in addition to its usual operations. That is, a hotcopy operation does not block other SM operations. You should not notice any performance degradation during a hot copy operation.

The time it takes to perform a hotcopy depends on how much information is being copied. It can take a while for a very large database. The default behavior is that NuoDB Command waits for a hot copy operation to complete. To invoke hotcopy so that it does not block NuoDB Command, specify a value of 0 for the timeout option when you invoke hotcopy . Alternatively, you can set the timeout to 0. With a timeout of 0, you might want to monitor the SM process so that you know when the hot copy operation is complete and whether it was successful.

To monitor the progress of a hotcopy operation, invoke the show domain command and specify the host and process ID of the SM that is executing the hot copy. The output indicates whether the hot copy operation is in progress, was successfully completed, or terminated with an error.

The destinationArchiveDirectory, destinationJournalDirectory directories on every SM host must be empty. If they are not, hotcopy generates an error and the operation fails.