Access Appliance Online Help
- Getting started
- About Access Appliance
- Enabling certificate-based authentication in Access Appliance
- Configuring storage for LTR
- About the dashboard
- Setting up the storage type for provisioning
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- About the NFS shares
- About an iSCSI target
- Creating an iSCSI target and provisioning LUNs
- About S3 buckets for NetBackup
- Using the Access Appliance product documentation
- Changing your password
- Managing storage
- Managing file sharing services
- Monitoring and troubleshooting
- Provisioning and managing file systems
- Creating a file system
- Setting the maximum IOPS
- Creating a snapshot
- Restoring a snapshot
- Configuring a replication job
- Stopping or starting a replication job for VVR
- Pausing and resuming a replication job for VVR
- Enabling or disabling a replication job for VFR
- Synchronizing a replication job for VFR
- Failing over or failing back a replication job for VVR
- Failing over or failing back a replication job for VFR
- Unconfiguring a replication job for VFR
- Unconfiguring a replication job for VVR
- Viewing the list of iSCSI targets
- Adding an initiator for an iSCSI target
- Removing an initiator for an iSCSI target
- Adding portal IPs for an iSCSI target
- Setting up authentication for an iSCSI target
- Viewing the list of initiators for an iSCSI target
- Viewing the portal IPs for an iSCSI target
- Removing portal IPs for an iSCSI target
- Removing authentication settings for an iSCSI target
- Removing an iSCSI target
- Removing the file system store for an iSCSI target
- Viewing the list of LUNs for an iSCSI target
- Creating a LUN for an iSCSI target
- Increasing the size of a LUN for an iSCSI target
- Reducing the size of a LUN for an iSCSI target
- Removing a LUN for an iSCSI target
- Cloning a LUN for an iSCSI target
- Creating a snapshot of a LUN for an iSCSI target
- Viewing the list of snapshots for an iSCSI target
- Removing a LUN snapshot
- Restoring a LUN snapshot
- Provisioning and managing shares
- About file sharing protocols
- About concurrent access
- About concurrent access with NFS and S3
- Sharing directories using CIFS and NFS protocols
- Adding a share
- NFS protocol options
- CIFS protocol options
- About buckets and objects
- About Active Directory (AD)
- Logging on as an active directory user
- Creating access and secret keys for an active directory user
- Exporting an NFS share as an S3 bucket
- Viewing information about a share
- Accessing share details
- Configuring a favorite share
- Deleting a share
- Managing permissions for CIFS shares
- Managing clients for the NFS shares
- Managing policies
- About policies for storage provisioning
- About policies for long-term data retention
- About policies for archiving data using Enterprise Vault
- About policies for file systems
- About pattern matching for data movement policies
- Viewing information about policies
- Activating storage policy templates
- Activating long-term data retention policies
- Activating archival policies
- Creating an S3 bucket
- About cloud-storage tiering
- Workflow for adding a cloud tier
- About tiering policies
- Adding a secondary tier
- Viewing information about the secondary tier
- Adding or editing a tier policy on a secondary tier
- Creating a policy schedule
- Managing settings
- Viewing Access Appliance settings
- About the cloud gateway
- Viewing information about cloud services
- Adding and removing a cloud service
- Viewing discovery information about your cluster
- About the Lightweight Directory Access Protocol
- Configuring LDAP
- Configuring Active Directory
- About user management
- Adding and removing user roles using GUI
- Performing user management using CLISH
- Configuring the NTP server
- Starting or stopping the CIFS or NFS servers
- Starting or stopping the S3 server
- Adding or removing storage pools for S3 users
- Configuring the /etc/hosts file for mapping of S3 users
- Registering a NetBackup master server or an EMM server
- Modifying a NetBackup media server list
- Viewing information about your NetBackup configuration with Access Appliance
- About cluster management
- Setting up the time and the time zone for the cluster
- About replication
- Viewing information about events
- Purging events
- About Access Appliance product licensing
- Setting object server default parameters
- Setting up the object server group-specific parameters
- Viewing information about S3
- Configuring the KMS server
- About the CIFS service management
- Setting up the home directory
- About the File Transfer Protocol
- About Veritas Data Deduplication
- About alert management
- STIG overview for Access Appliance
- FIPS compatibility list
- Index
About replication
Access Appliance replication lets you replicate a file system from one node in a source cluster to another node in a target cluster per a schedule.
There are two types of replication available:
Continuous replication - enables you to maintain a consistent copy of application data at one or more remote locations. Continuous replication replicates the application writes on the file system at the source location to one or more remote locations across any distance. It provides a consistent copy of application data at the remote locations. If a disaster occurs at the source location, you can use the copy of the application data at the remote location and restart the application at the remote location.
You can only configure continuous replication using policies.
Episodic replication - enables cost-effective periodic replication of data over IP networks, giving organizations a flexible storage solution for disaster recovery and off-host processing. Episodic replication tracks all updates to the file system and replicates these updates on regular intervals based on a schedule.
You configure file system replication using the File Systems tab and by using policies.
The major benefits of Access Appliance replication include:
Online access (read-only) to replicated data.
Immediate read or write access to target replicated data in the unlikely event that the source file system goes offline.
Load balancing across replication links.
Transport failover of the replication service from one node to another.
No limit on the number of episodic replication jobs that are configured, though the number of simultaneous/parallel jobs that can run at any time depends on the amount of memory available.