Please enter search query.
Search <book_title>...
Veritas InfoScale™ 7.4.1 Solutions in Cloud Environments
Last Published:
2019-02-07
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: Linux,Windows
- 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
- 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
Sample policy file
The following sample policy file defines the following policies:
Files which are not accessed for more than 30 days are moved to the cloud tier.
MP3 files are stored on the cloud tier.
(Applicable to block-level migration only, but not in case of file-level migration.)
All other files are created on the local tier.
<?xml version="1.0"?>
<!DOCTYPE PLACEMENT_POLICY SYSTEM "/opt/VRTSvxfs/etc/placement_policy.dtd">
<PLACEMENT_POLICY Version="5.0" Name="2tier_write_policy">
<RULE Flags="data" Name="Regular-Files-Rule">
<COMMENT>
Files which have not been accessed within the past 5 seconds
and which are on tier2 will be moved to LOCAL tier i.e. tier1
</COMMENT>
<SELECT Flags="Data">
<PATTERN> * </PATTERN>
</SELECT>
<CREATE>
<ON>
<DESTINATION>
<CLASS> tier1 </CLASS>
</DESTINATION>
</ON>
</CREATE>
<RELOCATE>
<FROM>
<SOURCE>
<CLASS> tier1 </CLASS>
</SOURCE>
</FROM>
<TO>
<DESTINATION>
<CLASS> tier2 </CLASS>
</DESTINATION>
</TO>
<WHEN>
<ACCAGE Units="days">
<MIN Flags="gt"> 30 </MIN>
</ACCAGE>
</WHEN>
</RELOCATE>
</RULE>
</PLACEMENT_POLICY>