Veritas Access Appliance 8.2 Solutions Guide for Enterprise Vault
- Introduction
- System Requirements
- Installing and configuring Enterprise Vault with Access Appliance
- Access Appliance features for Enterprise Vault archival storage
- Access Appliance archival policy configuration for Enterprise Vault
- Episodic replication job failover and failback
- Continuous replication failover and failback
- Troubleshooting
Access Appliance GUI policies for archival storage
The Access Appliance GUI policies provide quick and easy configuration of archival storage for Enterprise Vault. The following policies are supported:
This policy provides Write Once Read Many (WORM) storage and mirrors data across two devices, thus protecting against devices failures.
The key features of this archival policy are:
Fault tolerance
WORM
Prerequisites for this archival policy:
Storage pool should be configured.
Cluster should be in enterprise or compliance mode.
This policy protects data against device failures by creating mirrored data across two devices.
The key features of this archival policy are:
Fault tolerance
Prerequisites for this archival policy:
Storage pool should be configured.
This policy protects the data against device, node, and site failures. It replicates data across two clusters. Veritas recommends that these clusters should be in different data centers. This policy mirrors data across two devices and protects against device failures.
The key features of this archival policy are:
Fault tolerance
Replication
Prerequisites for this archival policy:
Storage pool should be configured.
Replication link should be set up.
This policy provides Write Once Read Many (WORM) storage and protects data against device, node, and site failures. It replicates data across two clusters. Veritas recommends that these clusters should be in different data centers. This policy mirrors data across two devices and protects against device failure.
The key features of this archival policy are:
Fault tolerance
WORM
Replication
Prerequisites for this archival policy:
Storage pool should be configured.
Episodic replication link should be set.
Cluster should be in enterprise or compliance mode.
Note:
To ensure seamless disaster recovery for vault stores, it is important to collect simultaneously consistent point-in-time copies of the Enterprise Vault partitions, Enterprise Vault database, and associated Enterprise Vault indices on the disaster recovery site regularly. If simultaneously consistent point-in-time copies are not collected regularly for vault stores at the disaster recovery site, the recovery points and the recovery times for those vault stores may be adversely affected.
This policy protects the data against site failures by replicating data continuously across two clusters. Veritas recommends that these clusters should be in different data centers. This policy provides high performant storage with hardware-based RAID6 resiliency.
The key features of this archival policy are:
Fault tolerance
Replication
Replicated Volume Group
Prerequisites for this archival policy:
Storage pool should be configured.
Continuous replication link should be set.
Replicated Volume Group should be configured.
This policy provides Write Once Read Many (WORM) storage and protects data against site failures. It replicates data continuously across two clusters. Veritas recommends that these clusters should be in different data centers. This policy provides high performant storage with hardware-based RAID6 resiliency and provides WORM storage for data immutability.
The key features of this archival policy are:
Fault tolerance
WORM
Replication
Prerequisites for this archival policy:
Storage pool should be configured.
Continuous replication link should be set.
Replicated Volume Group should be configured.
Cluster should be in enterprise or compliance mode.
Note:
For Enterprise Vault PSN to show expected behavior with replication, it is recommended to configure replication from the Access Appliance GUI.
Veritas recommends that every vault store that is protected against disasters using replication should have backup mode set for it before replication is started for partitions in that vault store. The set of simultaneously consistent point-in-time copies should then be collected for that vault store. Once the sets of simultaneously consistent point-in-time copies have been collected, backup mode can be unset for that vault store resuming archival in the vault store.
Note:
In this Access Appliance release, the default block size of any file system created using a policy is 1024 KB.