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
Setting up communication between the source and the destination clusters
You need to set up communication between your source and your destination clusters.
Make sure that you already created an online file system on the Access Appliance source cluster and an online file system on the Access Appliance destination cluster.
Access Appliance episodic replication authentication strategy is based on RSA-key authentication, and both the source and the destination clusters have to export their episodic replication public keys. The source cluster imports the destination cluster's public key and the destination cluster imports the source cluster's public key.
After you have determined which two Access Appliance clusters to use, you need to authenticate them.
The replication episodic config commands must be run in a specific order.
Use the replication episodic config del_keys after the replication episodic config deauth command, or it fails.
You can only run the replication episodic config unbind command (to unbind the virtual IP) after you have run the replication episodic service stop command.
You need to run the replication episodic config bind command (to bind the virtual IP) before you can run the replication episodic service start command.
You need to run the replication episodic config export_keys and Replication> episodic config import_keys to export and import the keys of both the source and the destination clusters.
You can only run the replication episodic config auth command after both the source and destination have imported each other's keys.
You need to run the replication episodic config auth command to create a link from every cluster to any remaining cluster that is used for episodic replication irrespective of their role as a source or a destination cluster.
After the source and the destination clusters have successfully imported each other's public keys, you need to run the Replication> episodic config auth command on the source cluster to complete the authentication between the two clusters. This command checks the two-way communication between the source and the destination cluster, and authenticates the clusters allowing the Access Appliance episodic replication service to begin.
Note:
The replication episodic config auth command must be run from the source cluster.
This section provides a walk-through for the creation and export/import of these encrypted keys for both the source and the destination cluster.
Note:
Without the correct authentication of the source and the destination encryption keys, Access Appliance episodic replication does not function correctly.
To export the source cluster's key to the destination cluster
- To export the source cluster's key to the destination cluster, enter the following:
Replication> episodic config export_keys [URL]
URL
The location you want to copy the public keys to.
If you do not want to enter a URL, you can copy the output from the Replication> episodic config export_keys command into the replication episodic config import_keys command at the destination cluster.
By default, the output is displayed to your computer screen.
The SCP protocol is supported.
- To import the source cluster's key to the destination cluster, enter the following:
Replication> episodic config import_keys [URL/keyfile]
URL
The location you want to copy the public keys from.
keyfile
The file name of the key that is generated by the export.
If you did not enter a URL during the replication episodic config export_keys command, you can cut and paste the output and enter it into the replication episodic config import_keys command.
- To verify that the key has been imported correctly, enter the following:
Replication> episodic config show
To export the destination cluster's key to the source cluster
- To export the destination cluster's key to the source cluster, enter the following:
Replication> episodic config export_keys [URL]
URL
The location you want to copy the public keys to.
The SCP protocol is supported.
If you do not want to enter a URL, you can cut and paste the output from the Replication> episodic config export_keys command to the Replication> episodic config import_keys command. By default, the output is displayed to your computer screen.
- To import the destination cluster's key to the source cluster, enter the following:
Replication> episodic config import_keys [URL/keyfile]
URL
Enter the URL of the location you want to copy the public keys from.
keyfile
Enter the file name of the key that is generated by the export.
If you did not enter a URL during the replication episodic config export_keys command, you can cut and paste the output and enter it into the replication episodic config import_keys command.
- To verify that the key has been imported correctly, enter the following:
Replication> episodic config show
To authenticate source cluster and destination clusters for episodic replication
- This command should be run on the source cluster as well as on the destination cluster. To authenticate the public keys on the source cluster and the destination clusters, enter the following:
Replication> episodic config auth conIP link_name
conIP
Enter the destination cluster console IP address.
link_name
Both the source cluster and the destination cluster need to be assigned a unique identifier (name). This identifier is used to identify the link that is established between the source and the destination clusters. You can use the link name instead of the virtual IP addresses of the source and the destination clusters when using the other episodic replication commands. For example: Pune_Shanghai.
- To confirm the authentication, enter the following:
Replication> episodic config show
Note:
These steps must be run on the destination side cluster to authenticate the public keys on the source and the destination cluster.
Once you have configured the clusters and links, you need to set up the file systems you want to replicate.