Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments
- Overview and preparation
- Overview of InfoScale solutions in cloud environments
- InfoScale agents for monitoring resources in cloud environments
- InfoScale feature for storage sharing in cloud environments
- About SmartIO in AWS environments
- Preparing for InfoScale installations in cloud environments
- Installing the AWS CLI package
- VPC security groups example
- Configurations for Amazon Web Services - Linux
- Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
- HA and DR configurations in AWS - Windows
- Failover within a subnet of an AWS AZ using virtual private IP - Windows
- Failover across AWS subnets using overlay IP - Windows
- Public access to InfoScale cluster nodes in AWS using Elastic IP - Windows
- DR from on-premises to AWS and across AWS regions or VPCs - Windows
- DR from on-premises to AWS - Windows
- Configurations for Microsoft Azure - Linux
- Configurations for Microsoft Azure - Windows
- Configurations for Google Cloud Platform- Linux
- Configurations for Google Cloud Platform - Windows
- Replication to and across cloud environments
- Migrating files to the cloud using Cloud Connectors
- About cloud connectors
- About InfoScale support for cloud connectors
- How InfoScale migrates data using cloud connectors
- Limitations for file-level tiering
- About operations with Amazon Glacier
- Migrating data from on-premise to cloud storage
- Reclaiming object storage space
- Removing a cloud volume
- Examining in-cloud storage usage
- Sample policy file
- Replication support with cloud tiering
- Troubleshooting issues in cloud deployments
Limitations for file-level tiering
InfoScale supports file-level tiering in cloud environments with the following limitations:
A file can be present either in the cloud or on-premises, but not at both locations simultaneously. The filesystem may have a few files on-premises and few in the cloud, but at any given time, a single file can exist only at one location.
During migration, access to files is blocked. If any related applications try to access the files under migration, they are blocked until the migration is complete.
Migration of files from the cloud to on-premises is not supported if a size-based policy is specified.
Write operations on files in the cloud are blocked. Only buffered read is allowed on files in the cloud.
If you want to remove a cloud volume from MVFS, you must first move all the files that exist on the cloud volume to some other volume or to another cloud.
Migration of compressed files is not allowed.
Migration of memory-mapped files is not allowed.
Migration of files that contain shared extents, like deduplicated files, is not allowed.
The
vxcloudusageutility scans all the system Inodes and their block maps, which may be time consuming. Therefore, Veritas recommends that you do not run this utility frequently. Additionally, when Inodes and block maps are scanned, system caches may get recycled, which may indirectly affect the overall performance of the system. Therefore, Veritas recommends that you do not run this utility during active production hours.When the Veritas Volume Replicator (VVR) option is configured, SmartIO caching cannot be used on the target site.
The limitations for the command-line support are as follows:
The following commands are not supported for files in the cloud:
FSCACHE
SETEXT
VXCOMPRESS
VXFILESNAP
TRUNCATE
The following file system commands are not supported with cloud volumes:
FSCDSADM
FSCDSTASK
FSCKPTADM
Thin reclamation is not supported for file systems on cloud devices.
If a checkpoint is present, you cannot add a cloud volume to the filesystem.
The fragmentation index is always zero for files in the cloud.
Direct write operations on cloud devices are not allowed. However, the policy is invalid if it specifies file creation on a cloud volume.