Veritas Access Appliance 8.2 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- Configuring the network
- About configuring the Access Appliance network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Considerations for configuration a LACP bond
- Configuring DNS settings
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring IP addresses and FQDNs in a non-DNS environment
- Configuring VLAN interfaces
- Configuring NIC devices
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- Configuring Access Appliance in IPv4 and IPv6 mixed mode
- Support for multiple data subnets
- Adding console FQDN to the network and accessing the GUI using the console FQDN
- Configuring authentication services
- About configuring LDAP settings
- Configuring LDAP server settings
- Administering the Access Appliance cluster's LDAP client
- About Active Directory (AD)
- Configuring AD server settings
- Configuring entries for Access Appliance DNS for authenticating to Active Directory (AD)
- Configuring AD/LDAP using the GUI
- Configuring NSS lookup order
- Sign-in options for the Access Appliance UI
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- About storage provisioning and management
- About configuring disks
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- Enabling, disabling, and displaying the status of file system quotas
- Setting and displaying file system quotas
- Setting user quotas for users of specified groups
- About quotas for CIFS home directories
- Workflow for configuring and managing storage using the Access Appliance CLI
- Displaying information for all disk devices associated with the nodes in a cluster
- Displaying WWN information
- Importing new LUNs forcefully for new or existing pools
- Initiating host discovery of LUNs
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- About using the NFS server with Access Appliance
- Using the kernel-based NFS server
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Access Appliance for ID mapping for NFS version 4
- Configuring the NFS client for ID mapping for NFS version 4
- About authenticating NFS clients
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring Access Appliance for CIFS
- About configuring CIFS for Active Directory (AD) domain mode
- Adding an SPN entry on the Windows client
- About setting trusted domains
- About storing account information
- Storing user and group accounts
- Reconfiguring the CIFS service
- About mapping user names for CIFS/NFS sharing
- About the mapuser commands
- Adding, removing, or displaying the mapping between CIFS and NFS users
- Automatically mapping UNIX users from LDAP to Windows users
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Setting the CIFS aio_fork option
- Enabling CIFS data migration
- Using Access Appliance as an Object Store server
- About the Object Store server
- Use cases for configuring the Object Store server
- Configuring the Object Store server
- About buckets and objects
- File systems used for objectstore buckets
- Enabling WORM on buckets
- Object Access SSL certificate
- Object Access endpoints
- S3 with NFS use case
- S3 with NSP use case
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations when configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About troubleshooting
- Monitoring command activity
- Monitoring alerts
- About alert management
- Monitoring events
- Viewing reports
- Viewing cluster storage usage
- Viewing file system usage
- About event notifications
- About severity levels and filters
- About SNMP notifications
- Configuring a syslog server
- Displaying events on the console
- Appliance log files
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- About creating and maintaining file systems
- About encryption at rest
- Considerations for creating a file system
- Best practices for creating file systems
- Choosing a file system layout type
- Determining the initial extent size for a file system
- About striping file systems
- About FastResync
- About fsck operation
- Enabling WORM on a file system
- Setting retention in files
- Setting WORM over NFS
- Manually setting WORM-retention on a file over CIFS
- About managing application I/O workloads using maximum IOPS settings
- Creating a file system
- Bringing the file system online or offline
- Listing all file systems and associated information
- Modifying a file system
- Managing a file system
- Destroying a file system
- Upgrading disk layout versions
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- About the NFS shares
- Displaying file systems and snapshots that can be exported
- Exporting an NFS share
- Displaying exported directories
- About managing NFS shares using netgroups
- Unexporting a directory or deleting NFS options
- Exporting an NFS share for Kerberos authentication
- Mounting an NFS share with Kerberos security from the NFS client
- Exporting an NFS snapshot
- Creating and maintaining CIFS shares
- About managing CIFS shares
- About the CIFS shares
- Exporting a directory as a CIFS share
- Configuring a CIFS share as secondary storage for an Enterprise Vault store
- Exporting the same file system/directory as a different CIFS share
- About the CIFS export options
- Setting share properties
- Displaying CIFS share properties
- Hiding system files when adding a CIFS normal share
- Allowing specified users and groups access to the CIFS share
- Denying specified users and groups access to the CIFS share
- Exporting a CIFS snapshot
- Deleting a CIFS share
- Modifying a CIFS share
- Making a CIFS share shadow copy aware
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- About Access Appliance episodic replication
- How Access Appliance Replication works
- Starting Access Appliance episodic replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from an episodic replication unit
- Scheduling the episodic replication
- Defining what to replicate
- About the maximum number of parallel episodic replication jobs
- Managing an episodic replication job
- Replicating compressed data
- Displaying episodic replication job information and status
- Synchronizing an episodic replication job
- Behavior of the file systems on the episodic replication destination target
- Accessing file systems configured as episodic replication destinations
- Configuring an episodic replication job using the GUI
- Episodic replication job failover and failback
- Configuring continuous replication
- About Access Appliance continuous replication
- How Access Appliance continuous replication works
- Starting Access Appliance continuous replication
- Setting up communication between the source and the destination clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Preserving the file system on the destination cluster
- Cloud tiering with continuous replication
- Configuring Enterprise Vault with continuous replication
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Addition of multiple file systems to a Replicated Volume Group
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Access Appliance instant rollbacks
- Restoring a file system from an instant rollback
- Refreshing an instant rollback from a file system
- Bringing an instant rollback online
- Taking an instant rollback offline
- Destroying an instant rollback
- Creating a shared cache object for Access Appliance instant rollbacks
- Listing cache objects
- Destroying a cache object of a Access Appliance instant rollback
- Configuring episodic replication
- Section X. Reference
- Index
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.
Considerations while configuring Access Appliance for continuous replication:
The number of RVGs configured under continuous replication on Access appliance should be restricted to 4.
The number of file systems under one RVG should be limited to 12.
Veritas recommends that you to add one file system at a time to an RVG. Once the file system is added and the status of continuous replication becomes consistent (up-to-date), add another file system to the RVGs.
Ensure that continuous replication IPs configured on Access Appliance are properly resolved by the configured DNS server or by
/etc/hostsfile.Addition of multiple file systems to an existing Replicated Volume Group is supported only through CLISH.
If you try to add a file system to an existing RVG when the replication continuous enable operation is in progress, then the file system remains offline till the operation is complete. As a result, the application is not able to serve read-write requests. The time period for which the file system remains offline depends on the size of the file system and the amount of data present on it. Ensure that you consider this downtime before you run the replication continuous enable command.
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 create_target_fs srl_size evpsn ev_partition_path
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 destination cluster.
link_name
Specifies the link name. This link is created during authentication of the source and the destination 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 file system.
evpsn
It can be set to [evpsn=yes|evpsn=no]. Enables or disables Enterprise Vault partition secure notifications.
ev_partition_path
This parameter should be provided only if evpsn=yes. This is the partition path created inside the CIFS share (starting with a '/'). For example: If
ev_archivalis the directory created inside the exported CIFS share, ev_partition_path should be provided as/ev_archival.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 file system 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 or NFS 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.
fs2to 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 an RVG and if you failover using the replication continuous failover fs1 command, then the entire RVG will fail over.
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 is not grown further.
You can also set the maximum SRL size for an RVG.
replication> continuous config set_max_srl_size rvg_name size
For example, the following command sets the SRL size to maximum of 200GB for rvg_test.
replication> continuous config set_max_srl_size rvg_test 200G
You can also use the replication continuous enable command for setting the RVG size.
replication> continuous enable fs1 pool1 source delayed=yes rvg_test create_target_fs=yes 100G
Here, 100G is the SRL size for rvg_test, which is an optional parameter.
This option is useful when setting the SRL size for the first file system when an RVG does not exist.
You can also view the current SRL and maximum SRL size. Appropriate messages are shown after the completion of each command to inform the user about successful completion or reason for failure.
You can verify whether the file systems are added correctly and the appropriate SRL size is set.
replication> continuous show
RVG FS List SRL Size ============= ========= ======== rvg_test fs1,fs2,fs3 204m
You can also verify whether the maximum SRL size is set correctly.
replication> continuous config show
Link name Remote Console IP Remote Replication Time of Key Import
VIP
========= ================= =================== ===========================
clus_repl 10.221.35.102 10.221.35.104 Tue Oct 12 23:22:19 PDT 2021
Time of Authorization RVG Max SRL Size
============================ ============== =================
Tue Oct 12 23:23:32 PDT 2021 rvg_test -
rvg_test2 19g
rvg_test3 10g
rvg_test4 11g