Veritas Access Appliance 8.2 Solutions Guide for Enterprise Vault

Last Published:
Product(s): Appliances (8.2)
Platform: Veritas 3340,Veritas 3350,Veritas 3360
  1. Introduction
    1.  
      About this document
    2.  
      About Access Appliance as archival storage for Enterprise Vault
    3.  
      Access Appliance versions certified by Enterprise Vault
  2. System Requirements
    1.  
      Server roles
    2.  
      Hardware requirements
    3.  
      Software requirements
  3. Installing and configuring Enterprise Vault with Access Appliance
    1.  
      Enterprise Vault deployment
    2.  
      Access Appliance deployment
  4. Access Appliance features for Enterprise Vault archival storage
    1.  
      Write-Once-Read-Many support
    2.  
      Partition Secure Notification
  5. Access Appliance archival policy configuration for Enterprise Vault
    1.  
      Configuring CIFS for the Active Directory domain mode
    2.  
      Access Appliance GUI policies for archival storage
    3.  
      Configuring the replication job
    4.  
      Activating the archival policy using GUI
    5.  
      Configuration of CIFS shares for archival using Veritas Access CLISH
    6.  
      Storage provisioning using policies
    7.  
      Configuring Access Appliance storage with Enterprise Vault store partition
    8. Episodic replication job failover and failback
      1.  
        Process summary
      2.  
        Overview of the planned failover process
      3.  
        Overview of the planned failback process
      4.  
        Overview of the unplanned failover process
      5.  
        Overview of the unplanned failback process
    9. Continuous replication failover and failback
      1.  
        Process summary
      2.  
        Overview of the planned failover process
      3.  
        Overview of the planned failback process
      4.  
        Overview of the unplanned failover process
      5.  
        Overview of the unplanned failback process
    10.  
      Configuring replication failover and exporting CIFS share from target cluster
  6. Troubleshooting
    1.  
      Log locations for troubleshooting
    2.  
      Additional resources
  7.  
    Index

Overview of the planned failover process

Consider two Access Appliance clusters, cluster A and cluster B. Here, cluster A is the original source cluster that replicates data to cluster B which is the original destination cluster. If the source cluster A is taken down for routine maintenance or for moving applications to cluster B, you can use a planned failover operation so that the replication direction switches from cluster B (new source) to cluster A (new destination). You should perform the planned failover before cluster A is taken down.

For planned failover, run the following command on the source cluster (cluster A):

Replication> continuous failover fs_name

Where fs_name is the name of the file system which is configured under continuous replication.

Once a planned failover happens, the roles of primary and secondary are switched. It will online the file system at new primary site and offline the file system at new secondary site. Now, cluster B is the primary site and cluster A is the secondary site. The file systems come online at the new primary site (cluster B) and the file systems at new secondary site (cluster A) are offline.

Note:

Planned failover command should be run when both the source and the destination clusters are reachable from each other. It should be run from the source cluster and replication should be in progress.

While doing a planned replication continuous job failover from source to target, ensure that no NFS/CIFS shares are configured with the source file system.