Open topic with navigation
An SM or SSM that is executing a hot copy does so in addition to its usual operations. That is, a hot copy operation does not block other SM or SSM operations. You should not notice any performance degradation during a hot copy operation.
The time it takes to perform a hot copy depends on how much information is being copied. It can take a while for a very large database. The default behavior is that
nuodbmgr waits for a hot copy operation to complete. To invoke
hotcopy so that it does not block
nuodbmgr, specify a value of
0 for the
timeout option when you invoke
hotcopy . Alternatively, you can set the
0. With a timeout of
0, you might want to monitor the SM or SSM process so that you know when the hot copy operation is complete and whether it was successful.
To monitor the progress of a hot copy operation, invoke the
show process status and specify the host and process ID of the SM or SSM 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.
Caution: The destinationArchiveDirectory, destinationJournalDirectory, and destinationSnapshotDirectory directories on every SM host must be empty. If they are not, hotcopy will generate an error and fail the operation.