NetBackup™ Veritas Access Appliance 8.3 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 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 continuous replication
- Section X. Reference
- Index
Displaying continuous replication information and status
The Replication continuous show and Replication continuous status commands display information on continuous replication which lets you 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 destination 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 destination 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 destination 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 restart. |
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 KB) (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 KB behind, yyy % full) | Updates to be transferred to secondary are logged into the SRL and are currently occupying xxx KB or yyy% of the SRL. |
SRL | SRL is used for logging. Check the Data status field for the status of the secondary data. |