Backup & Recovery

The Technical Services team for Backup and Recovery have produced a number of documents we call "Blueprints".

These Blueprints are designed to show backup and recovery challenges around specific technologies or functions and how NetBackup solves these challenges.

Each Blueprint consists of:

  • Pain Points: What challenges customers face
  • Whiteboard: Shows how NetBackup solves the customer challenges
  • Recommended Configuration: Shows recommended installation
  • Do’s: Gives detailed configurations suggested by Symantec
  • Don'ts: What configurations & pitfalls customers should avoid
  • Advantages: Summarises the NetBackup advantages

The NetBackup Enterprise Vault agent consists of the components that enable you to protect the Enterprise Vault configuration information and data that Enterprise Vault has archived. The agent supports Enterprise Vault 7.5, 8.0, 9.0, and 10 configurations. Thus, you should install all of the Enterprise Vault agent components on each of the systems that comprise an Enterprise Vault environment. The Enterprise Vault agent enables you to back up and restore the Enterprise Vault file system data and the Enterprise Vault SQL data. These types of data can reside on different systems or devices, such as NTFS or NAS devices.

The Enterprise Vault agent can also serve as a disaster recovery solution for data that is archived with Enterprise Vault. Recovery of the archived data is not dependent on the archive source, such as Exchange Server or a specific file system.

The NetBackup Enterprise Vault agent and its capabilities are provided as add-ons to the NetBackup Windows client software. This agent is tightly integrated with NetBackup and the Backup, Archive, and Restore interface. Thus, this manual provides an overview of the Enterprise Vault agent functionality as it pertains to NetBackup and the Backup, Archive, and Restore interface. Backup and Restore operations for the Enterprise Vault agent are identical to other NetBackup file operations with a couple of exceptions.

The NetBackup Enterprise Vault agent determines the configuration of an Enterprise Vault environment when an Enterprise Vault backup is run. This information is provided to the NetBackup master server to instantiate the appropriate NetBackup components on the clients for backup.

The Enterprise Vault agent enables you to back up and restore the following Enterprise Vault 7.5 components:

  • Enterprise Vault directory database
  • Enterprise Vault monitoring database
  • Enterprise Vault archives (such as open and closed partitions)
  • Enterprise Vault, vault store database
  • Enterprise Vault index location

Enterprise Vault agent supports Enterprise Vault 10.0. Enterprise Vault indexes the items that are archived. Indexing is done for faster and efficient searching of archived data.

Enterprise Vault 10.0 has a new 64-bit search engine. The 64-bit search engine has been created for the items that are indexed using Enterprise Vault 10.0 or later.

In the earlier release, indexes were created using the 32-bit search engine. In the 10.0 release, when a search is performed on an archive that has both the 32-bit and the 64-bit indexes, Enterprise Vault automatically searches across both the indexes.

For successful index locations and vault store partitions backups, there are some files that you need to exclude. These files must be added to the list of all NBU clients where the Enterprise Vault server is present.

You can download the full Blueprint from the link below.

Comments

Hello,

about "Closed Index Location" in this Blueprints and in this Whitepaper:

https://support.symantec.com/en_US/article.TECH147148.html

the statement is that the closed index locations could have their less frequency backup schedule.

My question is: if I have some open index locations and some closed index locations how can I exclude from daily backup the closed index locations if the only possible index directive is EV_INDEX_LOCATION=site name ?

With Netbackup agent for Enterprise Vault is possible or not to do this? or is possible only using 2 different "legacy" backup policy 1 for open index locations (backup physical path daily) and 1 for closed index locations (backup physical path weekly)

 

Regards

Does anyone have an answer to the question posed? I'm curious as well about backing up only the open Index locations. Is there a directive for EV 10.0 for EV_Index_Location so I can backup a single server's index locations?

this is awesome. any updates for EV 11 and NBU 7.7?