Cloud Storage Gateway:View and handle alerts

Procedure

1. View alerts for all gateways in a specific region

   1. Go to the Alerts page of the CSG console.

   2. You can search for alerts by time, gateway ID, share name, and alert status.

2. View alerts for a single gateway

   1. On the Gateways page of the CSG console, click the ID of the gateway. On the page that appears, click the Alerts tab.

   2. You can search for alerts by time, share name, and alert status.

Insufficient space for metadata cache

Cause

The space for metadata cache refers to the allocated metadata cache capacity in cache disks of Server Message Block (SMB) or Network File System (NFS) shares. This metadata primarily consists of directory structure information. A larger number of files in a share requires more metadata cache space. A cache disk includes space allocated for data cache and metadata cache. By default, 20% of the total cache disk space is allocated as the metadata cache. This alert is triggered if the remaining metadata cache space is less than 3 GB or 20% of the total metadata cache space.

Solutions

We recommend that you increase the cache disk space to prevent write failures caused by insufficient metadata cache space. For more information, see Increase cache disk capacity.

Throttled

Cause

This alert is triggered if the amount of data that is simultaneously written to the cache disk is greater than 80% of the total data cache size. In this case, data writes may fail.

Solutions

1. Troubleshoot problematic data uploads that cause failures in releasing cache space. The following factors cause problematic uploads:

• You attempt to upload data to a bucket that does not exist.

• The bucket policy denies access from the gateway.

• The share is mapped to an Archive bucket or a Cold Archive bucket.

• The size of files that are being simultaneously written to the cache disk exceeds the size of available data cache. As a result, the files cannot be closed and uploaded within the expected period of time.

2. Decrease the amount of data that can be simultaneously written to the cache disk.

3. Increase the cache capacity of the share. For more information, see Increase cache disk capacity.

Backlogged upload queue

Cause

This alert may be triggered by the following factors:

• You attempt to upload data to a bucket that does not exist.

• The bucket policy denies access from the gateway.

• The share is mapped to an Archive bucket or a Cold Archive bucket.

Solutions

Use the following steps to troubleshoot the alert:

1. Check whether the bucket exists. If the bucket does not exist, use an existing bucket.

2. Check whether access policies configured for the bucket deny access from the gateway.

3. Check whether the storage class of the bucket is Archive or Cold Archive. We recommend that you use a Standard bucket if your business application does not necessarily require a bucket in another storage class.

4. If the length of the current upload queue is less than 1,000, or the length of the upload queue decreases over a period of time after the alert is reported, the gateway is basically functioning normally.

   Note

   You can view information about an upload queue:

   • Starting from V1.9.2, upload queue metrics for file gateways are available in CloudMonitor. You can check upload queue metrics in the CloudMonitor console. For more information, see CloudMonitor integration

   • If your gateway version is lower than 1.9.2, you can check the length of the upload queue of a file gateway in the CSG console by using the following steps:

     • On the Gateways page of the CSG console, click the ID of the gateway.

     • On the Shares tab, find the share and click the plus (+) sign to expand share details. In the share details, view the value of the Upload Queue field.

If the alert remains or you have any other question, feel free to submit a ticket.