Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Configuring the cloud as a tier for scale-out file systems
You can configure the following clouds as a storage tier with a scale-out file system:
Amazon S3
Amazon Glacier
AWS GovCloud(US)
Azure
Alibaba
Google cloud
IBM Cloud Object Storage
Veritas Access S3
If you want to add any other S3-compatible storage, then it can be qualified with Veritas Access and used.
The data is always written to the on-premises storage tier and then data can be moved to the cloud tier by setting up policies. The policies can be configured based on access time, modification time, and pattern of the files. File metadata including any attributes set on the file resides on-premises even though the file is moved to the cloud. The cloud as a tier feature is best used for moving infrequently accessed data to the cloud.
See About scale-out file systems.
Warning:
When any cloud service is used as a cloud tier for a file system, Veritas Access exclusively owns all the buckets and the objects created by Veritas Access. Any attempt to tamper with these buckets or objects outside of Veritas Access corrupts the files represented by those modified objects.
See Moving files between tiers in a scale-out file system.
See the storage_cloud(1) man page for detailed examples.
See the storage_tier(1) man page for detailed examples.
Warning:
Veritas Access cannot add a cloud tier if the clock on the Veritas Access system is more than 15 minutes out-of-sync with the actual time. To ensure that the Veritas Access clock time is accurate, configure an NTP server or use the System> clock set command.
To configure the cloud as a tier for scale-out file systems
- Display the available cloud services.
Storage> cloud listservice service_name
If the cloud service is not listed, you may need to add the cloud subscription to the cluster.
- Add the cloud as a tier to a scale-out file system.
Storage> tier add cloud fs_name tier_name service_name region S3 | Glacier
Amazon AWS has standard regions defined. Based on the region you choose in Veritas Access, AWS storage is served through that region. To get better performance, always select the closest geographic region.
- Verify that the cloud tier is configured on the specified scale-out file system.
Storage> tier list fs_name
To remove the cloud tier
- Remove the cloud tier.
Storage> tier remove fs_name tier_name
If there are any files present in the cloud tier, the remove cloud tier operation fails. Move the files back to the primary tier before removing the cloud tier.