Veritas Access Appliance 8.2 Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance- About Veritas Data Deduplication
- Benefits of using Veritas Data Deduplication with Access Appliance
- Supported features with different versions of Veritas Data Deduplication
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using the Access CLISH
- Managing Veritas Data Deduplication using GUI- Viewing information about Veritas Data Deduplication
- Starting or stopping the Veritas Data Deduplication service
- Increasing storage for Veritas Data Deduplication
- Unconfiguring Veritas Data Deduplication
- Adding secondary IP for Veritas Data Deduplication
- Deleting secondary IP for Veritas Data Deduplication
- Changing the primary IP for Veritas Data Deduplication
- Upgrade the deduplication version for Veritas Data Deduplication
- Setting affinity node for Veritas Data Deduplication
 
- Accessing Access Appliance storage shell for management tasks
- Support for multiple domains across networks for Veritas Data Deduplication
- Veritas Data Deduplication storage layout
- Configuring a Veritas Data Deduplication storage unit on NetBackup
- Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
- Enabling Veritas Data Deduplication encryption
- Support for bandwidth throttling during duplication
- Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
- About MSDP encryption using NetBackup KMS service
- Support for NetBackup Auto Image Replication
- Setting up Auto Image Replication (AIR) between two Access Appliances which have secure communication enabled
 
- NetBackup Dedupe Direct for Oracle
- Configuring MSDP-C with Access Appliance
- Migrating the NetBackup images from existing storage to Veritas Access storage
- Configuring Access Appliance with the NetBackup client- Configuring Access Appliance for NetBackup client
- Installing the NetBackup client add-on packages
- Prerequisites for configuring the NetBackup client
- Configuring the NetBackup client
- Adding an optional media server
- Adding multiple primary servers
- Adding file systems to the backup configuration
- Removing file systems from backup configuration
- Changing the virtual IP address used by the NetBackup client
- Upgrade the NetBackup client
- Unconfiguring the NetBackup client
- Enabling Veritas Data Deduplication catalog backup with NetBackup client
- Disabling Veritas Data Deduplication catalog backup from NetBackup client
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Restoring filesystems backed up with NetBackup client
 
- Configuring isolated recovery environment (IRE)- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a storage server
- Managing an isolated recovery environment on a storage server
- Configuring data transmission between a production environment and an IRE storage server
 
- Troubleshooting
- Index
Restoring filesystems backed up with NetBackup client
This section describes how you can restore filesystems (which are backed up using the NetBackup client) that get corrupted in the Access Appliance environment.
You can backup a filesystem with the NetBackup client using the backup fs add command. The backup of the filesystem is created on the NetBackup media server. If the filesystem goes corrupt and is destroyed, you can restore the filesystem.
To restore a corrupted filesystem
- Create a new filesystem. You can use the same name as that of the existing filesystem if a filesystem with that name is no longer present, else use a different name.
- Add the filesystem back to the NetBackup client's backup filesystem configuration using the backup fs add fs_name command.
- Restore the data backed up from the filesystem to the respective path on the new filesystem.
To restore the MSDP catalog filesystem
- Restore the MSDP catalog filesystem.If the NetBackup client is enabled with deduplication catalog backup and the catalog filesystem goes corrupt, you will need to format the catalog filesystem. - Disable the catalog backup. - backup> dedupe-catalog disable 
- Format the catalog filesystem or re-create it with the same name. 
- Add the catalog filesystem as a backup filesystem. - backup> fs add fs_name 
- From the deduplication catalog backup, restore the content that was backed up to - /vx/<catalog_fs>/dedupe/databasesby selecting Restore to a different location on the NetBackup primary.
- Enable the deduplication catalog to continue backing up the deduplication catalog. - backup> dedupe-catalog enable - Note: - In case the MSDP catalog filesystem is destroyed, ensure that a new filesystem is created with same name as the old MSDP catalog filesystem. You can then follow the steps to add, restore and enable the catalog filesystem.