Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Configuring ISCSI
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- 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 Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Using Access Appliance with OpenStack
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Addition of multiple file systems to a Replicated Volume Group
Access Appliance supports the addition of multiple file systems to a Replicated Volume Group (RVG). You can enable replication for many file systems in a single RVG.
To configure an RVG with multiple file systems
- Create an RVG. You can specify the name in the parameter.
replication> continuous enable fs_name pool_name link_name [delayed=yes|no] rvg_name
fs_name
Specifies the name of the file system. It should be present on the source cluster.
pool_name
Specifies the pool name. It should be present on the source as well as target cluster.
link_name
Specifies the link name. This link is created during authentication of the source and the target cluster,
[delayed=yes|delayed=no]
Specifies if the continuous replication should happen in delayed mode, This is an optional parameter and the default value is 'no'.
rvg_name
Specifies the name of the RVG.
create_target_fs
The value is yes if you want to create file system on secondary cluster. Else, the value is set to no.
srl_size
Specify the SRL size for the filesystem. .
For example: To create an RVG,
rvg_test
:replication> continuous enable fs1 pool1 src_link delayed=yes rvg_test
You can specify the RVG name in the command. If the RVG name is not specified, the RVG is created with the default name. The default name of the RVG is rvg_fs_name.
- Before adding another file system, ensure that the data is synced between the primary and secondary sites and the second filesystem is offline.
replication> continuous status fs_name
- Add another file system to the same RVG.
replication> continuous enable fs_name pool_name link_name [delayed=yes|no] rvg_name
Note:
If you have configured any CIFS shares on the file system, you must remove them before you add the file system to an existing RVG.
For example: To add a file system.
fs2
to the existing RVG, rvg_test:replication> continuous enable fs2 pool1 src_link delayed=yes rvg_test
After the execution of this command, rvg_test is created with two file systems in it, fs1 and fs2.
You can add more file systems in the RVG by repeating steps 2 to 3.
You can view the mapping between the RVG and the file systems using the following command:
replication> continuous show RVG FS List ------ --------------- rvg_test fs1,fs2
The replication continuous commands such as start, stop, pause, resume, failover, and failback accept the file system name as the parameter, but the changes are applicable for the entire RVG (including all the file systems which are part of the RVG).
For example, if you have multiple file systems in a RVG and if you failover using the replication continuous failover fs1 command, then the entire RVG will failover.
The replication continuous disable command does not delete the RVG until the file system is the last file system in the RVG.
For each file system that is added to the RVG, if the file system is configured in async mode, the Storage Replicator Log (SRL) grows by 20% of the file system size, and if the file system is configured in sync mode, it grows by 5% of the file system size. If the SRL has been grown more than 12 times(either as a result of the fs grow command or addition of file systems to the RVG), then the SRL will not be grown further.
Note:
If a file system was created before you performed an upgrade to Access Appliance 7.4.3, contact Veritas Technical Support to add the file system to an existing RVG or to create a new RVG with the file system.