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 failback process

After an unplanned failover, when the source cluster (cluster A) comes up, you can use the following unplanned failback process to return control to the original source cluster (cluster A):

  • Make sure that you are logged into the source cluster.

    Note:

    Before starting the failback process, verify that the episodic replication service is running on the primary node. If the service is not running on the primary node, stop the service using the replication episodic service stop command and start it again using the Replication> episodic service start command.

  • Use the replication episodic job failover force=yes/no job_name current_cluster_link command to configure the current source cluster as a valid target to the new source cluster. This command should be run from the original source cluster (cluster A).

  • Use the replication episodic job sync job_name command from the new source cluster to synchronize file system data with the newly added destination cluster.

  • Use the replication episodic job failback force=yes/no job_name current_cluster_link command to move control of the episodic replication job from the destination cluster back to the source cluster. This command should be run from the original source cluster (cluster A).

  • Use the replication episodic job sync job_name command to ensure that the episodic replication job is in a well-defined state and incremental episodic replication can be resumed.

Once the unplanned failback is completed, cluster A becomes the source cluster again and cluster B becomes the destination cluster again.

Note:

An administrator can use the Replication> episodic job destroy force command to clean up local job configuration. Configuration of the other clusters, which are part of the job, are not modified and any episodic replication units are disassociated from job. The Replication> episodic job destroy force and Replication> episodic repunit destroy force commands should be used in the event of an unrecoverable configuration or episodic replication direction mismatch.