IBM Cloud Docs
Monitoring file share health states, lifecycle status, and events

Monitoring file share health states, lifecycle status, and events

By using the console, the CLI, or the API, you can check on the status and health states of the file shares.

File share statuses

When you view the list of your file shares in the console, you can see the status of each file share in the second column.

When you view file share details from the CLI by running either ibmcloud is shares or the ibmcloud is share command, the response contains the Status of the displayed file share.

When you make a GET /shares request, the API returns a lifecycle_state value as part of the information about the file share.

Table 1 shows the lifecycle statuses that the file share can have.

Table 1. File Storage lifecycle states
Status Explanation
stable The file share or mount target is stable and available for use.
pending The file share or mount target is being created.
failed The file share or mount target failed to be created. You can delete the failed share and try creating another one.
This status is also shown when the access to the origin share is revoked from the accessor share.
deleting The file share or mount target is being deleted.
suspended The file share violates IBM Cloud®’s Acceptable Use Policy. A suspended file share cannot be updated or deleted.
updating The file share capacity or IOPS is being updated.
waiting

file share replication status

When you view your file share in the console, you can see its Replication role and Replication status. This information is displayed in the file shares list and the file share details page in the File share replication relationship section.

When you view the details of a file share from the CLI by running the ibmcloud is share command, the response contains the Replication status of the specified file share.

When you make a GET /shares/{id} request, the API returns a replication_status value as part of the information about the file share.

Table 2 shows all the replication status that the file shares can have.

Table 2. File Storage replication status
Status Explanation
active This share is actively participating in replication, and the replica's data is up to date with the replication schedule.
failover_pending This share is performing a replication failover. Or the service is waiting for another operation to complete, such as file share expansion, before the failover can commence.
initializing This share is initializing replication.
none This share is not participating in replication.
split_pending This share is performing a replication split.

Replication sync health

Replication is an asynchronous operation, which is not instantaneous. The system queries the last sync status every 15 minutes. The result shows the data of the last replication that completed, such as start and end date, and the transferred data volume.

You can see information about the last replication operation when you view the details of either the source or the replica share. For more information, see View details of a file share in the UI.

You can see information about the last replication operation when you list the details of either the source or the replica share. For more information, see View details of a file share from the CLI.

You can programmatically retrieve the last sync details by calling the /shares method in the VPC API. Look for the latest_sync section in the API response to see when the replication started (started_at), when it ended (completed_at), and how much data was transferred (data_transferred). For more information, see View a single file share with the API.

When the amount of data to be transferred exceeds the amount of data that can be transferred during the replication window with the normal transfer rate, the replication process can't complete and the replication status becomes degraded. If this situation occurs, try adjusting the rate of change on the file share and the replication frequency.

Activity tracking events

You can use IBM Cloud® Activity Tracker Event Routing to configure how to route auditing events. Auditing events are critical data for security operations and a key element for meeting compliance requirements. Such events are triggered when you create, modify, or delete a file share. Activity tracker events are also triggered when you establish and use file share replication. For more information, see Activity tracking events for IBM Cloud VPC.

Logging for file share service

After you provision IBM Cloud Logs Routing to add log management capabilities to your IBM Cloud® architecture, you can enable platform logs to view and analyze logs of the File Storage for VPC service. When replication occurs, the file service generates a regional-file.00002I log message, which includes information about when the replication occurred, and how much data was transferred. For more information, see Logging for VPC.