Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- About configuring the Veritas Access network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Configuring DNS settings
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring Veritas Access to use jumbo frames
- Configuring VLAN interfaces
- Configuring NIC devices
- Swapping network interfaces
- Excluding PCI IDs from the cluster
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- IP load balancing
- Configuring Veritas Access in IPv4 and IPv6 mixed mode
- Configuring authentication services
- Section III. Managing Veritas Access 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
- About Flexible Storage Sharing
- Limitations of Flexible Storage Sharing
- Workflow for configuring and managing storage using the Veritas Access 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
- Increasing the storage capacity of a LUN
- Formatting or reinitializing a disk
- Removing a disk
- 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
- About using the NFS server with Veritas Access
- Using the kernel-based NFS server
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Veritas Access 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 Veritas Access as a CIFS server
- About configuring Veritas Access for CIFS
- About configuring CIFS for standalone mode
- Configuring CIFS server status for standalone mode
- Changing security settings
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- Setting NTLM
- About setting trusted domains
- Specifying trusted domains that are allowed access to the CIFS server
- Allowing trusted domains access to CIFS when setting an IDMAP backend to rid
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ldap
- Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ad
- About configuring Windows Active Directory as an IDMAP backend for CIFS
- Configuring the Active Directory schema with CIFS-schema extensions
- Configuring the LDAP client for authentication using the CLI
- Configuring the CIFS server with the LDAP backend
- Setting Active Directory 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
- About managing local users and groups
- Enabling CIFS data migration
- Configuring an FTP server
- About FTP
- Creating the FTP home directory
- Using the FTP server commands
- About FTP server options
- Customizing the FTP server options
- Administering the FTP sessions
- Uploading the FTP logs
- Administering the FTP local user accounts
- About the settings for the FTP local user accounts
- Configuring settings for the FTP local user accounts
- 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
- 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 creating a tuned file system for a specific workload
- About FastResync
- About fsck operation
- 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 VII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- 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
- 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
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section VIII. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Use cases for compressing files
- Best practices for using compression
- Compression tasks
- Compressing files
- Showing the scheduled compression job
- Scheduling compression jobs
- Listing compressed files
- Uncompressing files
- Modifying the scheduled compression
- Removing the specified schedule
- Stopping the schedule for a file system
- Removing the pattern-related rule for a file system
- Removing the modified age related rule for a file system
- Configuring episodic replication
- About Veritas Access episodic replication
- How Veritas Access episodic replication works
- Starting Veritas Access 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
- Episodic replication job failover and failback
- Configuring continuous replication
- About Veritas Access continuous replication
- How Veritas Access continuous replication works
- Starting Veritas Access continuous replication
- Setting up communication between the source and the target clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Veritas Access 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 Veritas Access instant rollbacks
- Listing cache objects
- Destroying a cache object of a Veritas Access instant rollback
- Compressing files
- Section IX. Reference
- Index
Setting up communication between the source and the target clusters
You need to set up communication between your source and your target clusters.
Make sure that you already created an online file system on the Veritas Access source cluster and an online file system on the Veritas Access target cluster.
Veritas Access Replication authentication strategy is based on RSA-key authentication, and both the source and the target clusters have to export their replication public keys. The source cluster imports the target cluster's public key and the target cluster imports the source cluster's public key.
After you have determined which two Veritas Access clusters to use, you need to authenticate them.
The replication continuous config commands must be executed in a specific order.
You need to run the replication continuous config bind command (to bind the virtual IP) before you can run the replication continuous service start command.
You need to run the replication continuous config export_keys and replication continuous config import_keys to export and import the keys of both the source and the target clusters.
Copy the keys displayed in the output of the replication continuous config export_keys command from the source cluster. Run the replication continuous config import_keys command on the target cluster using the output that you copied.
Copy the keys displayed in the output of the replication continuous config export_keys command from the target cluster. Run the replication continuous config import_keys command on the source cluster using the output that you copied.
You can only run the replication continuous config auth command after both the source and destination have imported each other's keys.
You need to run the replication continuous config auth command to create a link from every cluster to any remaining cluster that is used for replication irrespective of their role as a source or a target cluster.
The command checks the two-way communication between the source and the target cluster, and authenticates the clusters allowing the Veritas Access continuous replication service to begin.
This section provides a walk-through for the creation and export/import of these encrypted keys for both the source and the target cluster.
Note:
Without the correct authentication of the source and the destination encryption keys, Veritas Access continuous replication does not function correctly.
To export the source cluster's key to the target cluster
- To export the source cluster's key to the target cluster, enter the following:
Replication> continuous 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 continuous config export_keys command into the Replication> continuous config import_keys command at the target cluster.
By default, the output is displayed on your computer screen.
The SCP and FTP protocols are supported.
- To import the source cluster's key to the target cluster, enter the following:
Replication> continuous 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> continuous config export_keys command, you can cut and paste the output and enter it into the replication continuous config import_keys command.
- To verify that the key has been imported correctly, enter the following:
Replication> continuous config show
To export the target cluster's key to the source cluster
- To export the target cluster's key to the source cluster, enter the following:
Replication> continuous config export_keys [URL]
URL
The location you want to copy the public keys to.
The SCP and FTP protocols are supported.
If you do not want to enter a URL, you can cut and paste the output from the Replication> continuous config export_keys command to the Replication> continuous config import_keys command. By default, the output is displayed to your computer screen.
- To import the target cluster's key to the source cluster, enter the following:
Replication> continuous 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 continuous config export_keys command, you can cut and paste the output and enter it into the replication continuous config import_keys command.
- To verify that the key has been imported correctly, enter the following:
Replication> continuous config show
To authenticate source cluster and target clusters for replication
- This command should be executed on the source cluster as well as on the target cluster. To authenticate the public keys on the source cluster and the target clusters, enter the following:
Replication> continuous config auth conIP link_name
conIP
Enter the target cluster console IP address.
link_name
Both the source cluster and the target 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 target clusters. You can use the link name instead of the virtual IP addresses of the source and the target clusters when using the other replication commands. For example: Pune_Shanghai.
- To confirm the authentication, enter the following:
Replication> continuous config show
Note:
These steps must be executed on the destination side cluster to authenticate the public keys on the source and the target cluster.
Once you have configured the clusters and links, you need to set up the file system you want to replicate.