Automatic hibernation policy of General-propose NAS will be enabled on November 1, 2022
2022/10/10
[Effective time]: from 00:00:00 (UTC+8), November 1, 2022
[Change]:
For all general-purpose NAS instances (including NFS and SMB protocols) with data capacity of 0 MB (including data in IA media and the recycle bin), and without I/O access for more than 60 days (including 60 days), the NAS mount point will be automatically switched to hibernated status. The mount point in hibernated status can be enabled through the OpenAPI or console.
[Impact of Change]:
For general purpose NAS (instances including NFS and SMB protocols) with data capacity of 0 MB (including data in IA media and the recycle bin), and without I/O access for more than 60 days (including 60 days), the NAS mount point will be automatically switched to hibernated status.
Before mounting a hibernated mount point, you need to enable it through the OpenAPI or console. With respect to NAS mounted to ECS, all I/O operations on NAS catalogue will be blocked once the mount point goes into hibernated status. If you run into this status, please re-enable the hibernated mount point through OpenAPI or console to recover the I/O operation.
[Suggestions]:
It is recommended to delete, through the NAS console, the mount points and instances of the general-propose NAS of 0 MB data capacity which do not expect to be used in a long period of time.
[Change]:
For all general-purpose NAS instances (including NFS and SMB protocols) with data capacity of 0 MB (including data in IA media and the recycle bin), and without I/O access for more than 60 days (including 60 days), the NAS mount point will be automatically switched to hibernated status. The mount point in hibernated status can be enabled through the OpenAPI or console.
[Impact of Change]:
For general purpose NAS (instances including NFS and SMB protocols) with data capacity of 0 MB (including data in IA media and the recycle bin), and without I/O access for more than 60 days (including 60 days), the NAS mount point will be automatically switched to hibernated status.
Before mounting a hibernated mount point, you need to enable it through the OpenAPI or console. With respect to NAS mounted to ECS, all I/O operations on NAS catalogue will be blocked once the mount point goes into hibernated status. If you run into this status, please re-enable the hibernated mount point through OpenAPI or console to recover the I/O operation.
[Suggestions]:
It is recommended to delete, through the NAS console, the mount points and instances of the general-propose NAS of 0 MB data capacity which do not expect to be used in a long period of time.
