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 unplanned failover process

In some cases (for example, unexpected equipment failure), you may need to run an unplanned failover for replication. The unplanned failover process differs from the planned failover process.

If cluster A is the original source cluster that replicates data to cluster B which is the original destination cluster and if cluster A fails unexpectedly, you can perform an unplanned failover or a disaster recovery. This marks the cluster B as the new source cluster and you can access the data/applications replicated to it.

For unplanned failover, run the following command from the original destination cluster (cluster B):

Replication> continuous failover fs_name

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

Once an unplanned failover happens, the destination cluster (cluster B) becomes the new source cluster. It onlines the file system at the new source cluster (cluster B).

Note:

Though the commands used for planned and unplanned failover are the same, the intention and pre-requisites are different. For unplanned failover, the source cluster should be unreachable from the destination cluster.