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
Displaying continuous replication information and status
The Replication continuous show and Replication continuous status commands display information on continuous replication which allows you to confirm any changes that are made to your replication file system and view the current file system status.
To display the list of file systems which are configured under continuous replication
- To display the list of file systems which are configured under continuous replication, enter the following command:
Replication> continuous show
To display the status of a replication file system
- To display the status of a replication file system, enter the following command:
Replication> continuous status fs_name
fs_name
Specify the file system name that you have configured for continuous replication.
Table: describes the important attributes displayed by the Replication> continuous status command.
Table:
Attribute | Description |
|---|---|
Replicated Data Set | Specifies the name of the replicated data set |
Replication role | Specifies the role of the cluster in continuous replication. It is either primary or secondary. |
Replication link | Specifies the link name which is created during the authentication of the source and the target cluster. |
Primary site Info | Provides the details of continuous replication related to the source cluster like host name and RVG state. |
Secondary site Info | Provides the details of continuous replication related to the target cluster like host name, configured mode, data status, replication status, current mode and timestamp information. |
Host name | For the primary site, it provides the continuous replication IP which binds on the source cluster using the Replication> continuous config bind command. For the secondary site, it provides the continuous replication IP which binds on the target cluster using the Replication> continuous config bind command. |
RVG state | Specifies the state of the primary RVG. See Table: RVG status for details on its various states. |
Configured mode | Specifies the continuous replication configured mode. It may be synchronous-override or asynchronous. |
Current mode | Specifies the mode of replication - asynchronous or synchronous, that is used to replicate data to the secondary. |
Data status | Shows the data status for the secondary. See Table: Data status for details on its various states. |
Replication status | Specifies the status of the replication to the secondary. See Table: Replication status for details on its various states. |
Logging to | Indicates whether updates for the secondary are tracked on the primary using the SRL or DCM. See Table: Logging to status for details on its various states. |
Timestamp information | Shows the time by which secondary is lagging behind the primary. |
Table: RVG status describes the values for the RVG state.
Table: RVG status
Value | Description |
|---|---|
acting_secondary | The primary RVG is currently the acting secondary as part of the fast failback process. Writes to the data volumes in this RVG are disabled independent of whether the RVG is started or stopped. |
disabled for I/O | Primary RVG is disabled for I/O. The RVG is stopped. |
enabled for I/O | Primary RVG is enabled for I/O. The RVG has been started. |
needs recovery | State of the RVG after an import or reboot. |
Passthru | The primary RVG is in passthru mode because the primary SRL is detached or missing. |
Table: Data status describes the values for the Data status.
Table: Data status
Value | Description |
|---|---|
consistent, behind | Secondary data is consistent but not up-to-date with the primary data. |
consistent, stale | The data on the secondary is consistent. Replication to the secondary has been stopped. The primary RLINK is detached. |
consistent, up-to-date | The secondary data is consistent and is current or up-to-date with the primary data. The primary role can be migrated to the secondary. |
inconsistent | The data on the secondary volumes is not consistent and the secondary cannot take over. |
N/A | Current state of the secondary data cannot be determined. This may occur because of a configuration error on the secondary. |
Table: Replication status describes the values for the Replication status.
Table: Replication status
Value | Description |
|---|---|
logging to DCM | DCM is active for the secondary. New updates on primary are tracked using DCM for the secondary. The following information may be displayed:
|
needs failback synchronization | The primary RVG is acting as secondary as part of the fast failback process. Start failback resynchronization on the new primary to continue replication. |
not replicating | Data is not being replicated to secondary because primary RLINK is in needs_recovery state.
|
paused by user | Replication to secondary is paused due to some administrative action. This results in the following states:
|
paused due to error | Replication to secondary is paused due to the following errors:
|
paused due to network disconnection | Replication to secondary is paused due to some network problem. |
replicating | Replication can take place if there are updates on the primary data volumes. |
resync in progress | Resynchronization to the secondary is in progress.
|
resync paused by user | Resynchronization to secondary is paused due to some administrative action. This results in the following states:
|
resync paused due to error | Resynchronization to Secondary is paused because of the following errors:
|
resync paused due to network disconnection | Resynchronization to secondary is paused due to some network problem. |
stopped | Replication to secondary is stopped due to the following:
|
N/A | The replication status cannot be determined. |
Table: Logging to status describes the values for the Logging to field.
Table: Logging to status
Value | Description |
|---|---|
DCM (contains xxx Kbytes) (log_type) | DCM is active (in use) for the replication to the secondary. The log_type can be autosync, failback logging, or SRL protection logging. The yyy% value can sometimes reach beyond 100%. If synchronization is restarted and the DCM map is full, new incoming writes cause the total yyy% to exceed 100%. |
SRL (xxx Kbytes behind, yyy % full) | Updates to be transferred to secondary are logged into the SRL and are currently occupying xxx Kbytes or yyy% of the SRL. |
SRL | SRL is used for logging. Check the Data status field for the status of the secondary data. |