Checking the cloud services database integrity

There might be situations where the cloud services database that is associated with a container gets corrupted secondary to a power outage or system crash, and in such cases, you must check the integrity of the database before you proceed with any operation.

To check the integrity of database that is associated with a container, issue a command according to the following syntax:

mmcloudgateway files checkDB --container-pair-set-name ContainerPairSetName

For example, issue the following command to check the integrity of the database that is associated with the container, container1:

mmcloudgateway files checkDB --container-pair-set-name container1

The system displays output similar to this:


CheckDB returned OK.
mmcloudgateway: Command completed.

If the database is corrupted, the system displays an output similar to this:


MCSTG000130E: Command Failed with following reason: Request failed with error : 
Database is potentially not in a good state and needs to be rebuilt.
mmcloudgateway: Command failed. Examine previous error messages to determine cause.

Note: cloud services configurations contain sensitive security-related information regarding encryption credentials, so you must store your configuration back-up in a secure location. This configuration information is critical in helping you restore your system data, if necessary.