Adding and Managing Destinations › How to Add a Destination › Add a Data Store › Various States of Data Store

Various States of Data Store

The data store displays different status depending on the task performed by the data store. When you select a data store from the resources tab, the data store status is displayed on the right pane

• Stopped: The data store is inactive. You cannot submit any job in this state.
• Starting: The data store is starting. When the data store is getting started, the progress is displayed on the Console.
• Running: The data store is active. You can submit jobs in this state.
• Stopping: The data store is stopping. When the data store is stopping, the progress is displayed on the Console.
• Modifying: The data store is getting updated with the new data. When the data store is getting modified, the progress is displayed on the Console.
• Deleting: The data store is getting deleted. When the data store is getting deleted, the progress is displayed on the Console.
• Out of Service: The data store is not functioning properly. You cannot submit any jobs in this state. Stop the data store and verify the reason for this behavior. The following cases can result in the Out of Service status of a data store:
  • The data store backup destination cannot be accessed.
  • The configurations in registry or file are corrupted.
  • The GDD index or data role has internal errors.
  • The GDD index or data role process is manually stopped.
• Restore Only: In the Restore Only state, any jobs that require to write data to the data store does not run. Jobs such as backup, replication (in) job, jumpstart (in), data migration job. All others jobs run, which require to read data from the data store. The data store status changes to Restore Only in the following conditions:
  • When the hash role process is manually stopped.
  • When the hash path volume capacity or the assigned hash memory reaches its maximum limit.

Important! When the status of the data store is Restore only (Degraded State) or Out of service (Bad State), the data store does not function properly. You must stop the data store and verify the root cause for the status. For example, the problem may be the data deduplication volume has reached its maximum. After you resolve the root cause, start the data store and resubmit the backup job.