Enterprise Vault How-To

Guide
Setting up Enterprise Vault
Migrations with NetBackup
This document provides an overview of how to configure Enterprise Vault and NetBackup for the
migration of archived Enterprise Vault content.

This document applies to the following version(s) of Enterprise Vault: 6 and later
If you have any feedback or questions about this document please email them to II-TEC@veritas.com
stating the document title.

2015 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of
Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the
information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information
in this document is subject to change without notice.

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Document Control
Contributors
Who

Contribution

Evan Barrett

Author

Revision History
Version

Date

Changes

1.0

July 2009

Initial Release

2.0

May 2013

Updates for NetBackup 7.1 and 7.5 and Enterprise Vault 10

3.0

August 2013

Minor changes and updated screenshots

4.0

November 2015

Minor updates

5.0

January 2016

Minor updates

Related Documents
Document Title

Version / Date

Backing Up Enterprise Vault

October 2015

http://www.veritas.com/docs/000010873

Registering the NetBackup Migrator

October 2015

http://www.veritas.com/docs/000074232

Page i

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Table of Contents
Overview ..................................................................................................................................................... 1
Considerations before Setting up Migration ................................................................................................ 1
What Types of Data Should Be Migrated? .............................................................................................. 1
If Not yet at Enterprise Vault 10............................................................................................................... 1
Requirements .............................................................................................................................................. 2
Enterprise Vault ....................................................................................................................................... 2
NetBackup ............................................................................................................................................... 2
Configuring the NetBackup Client on the Enterprise Vault Server .............................................................. 2
Installation ............................................................................................................................................... 2
Post Client Installation ............................................................................................................................. 3
Configuring the NetBackup Master Server .................................................................................................. 5
Adding a License Key .............................................................................................................................. 5
Configuring a NetBackup Policy for Enterprise Vault Migrations ............................................................. 5
Creating a Policy .................................................................................................................................. 5
Policy Attributes ................................................................................................................................... 6
Policy Schedule ................................................................................................................................... 7
Policy Clients ....................................................................................................................................... 9
Configuring Vault Store Partitions for Migration to NetBackup .................................................................... 9
Setting up Collections .............................................................................................................................. 9
Setting up Migration .............................................................................................................................. 10

APPENDIX A - Settings in the Vault Store Partition Advanced Tab that Relate to NetBackup Migrations

Page ii

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Overview
The purpose of this document is to provide best practices on configuring migrations of Enterprise Vault
archived data to Veritas NetBackup. Topics that will be covered include considerations before setting up
migration, software requirements, Enterprise Vault Vault Store partition configurations, NetBackup policy
configurations, and NetBackup client configuration considerations.
Starting with NetBackup 7.5.0.3, enhancements have been made to the migrator which include greater
migration speed. Previous versions of the migrator would only migrate one Enterprise Vault collections
file (.cab) at a time. The newer version of the migrator can migrate up to 25 (and in some cases higher)
.cab files per migration job. This will create less overhead on the NetBackup server as far as backup jobs
and catalog entries are concerned.
It should be noted that the Enterprise Vault NetBackup Migrator does not support migrations from a Vault
Store partition configured on a network share. This includes any partition path set up using a UNC path
name such as \\fileserver\share stored on any CIFS-compatible device.

Considerations before Setting up Migration

What Types of Data Should Be Migrated?
It is highly recommended that the NetBackup Enterprise Vault migrator not be used in conjunction with
email related archives (especially when migrating to tape) due to the potential sheer volume of archived
content. If the Enterprise Vault environment will be performing numerous recalls of archived emails (such
as using EV Browser Search/Enterprise Vault Search, Discovery Accelerator, eDiscovery Platform,
exporting archived emails to PST/NSF, or verifying Vault Store consistency using the Enterprise Vault
EVSVR utility), numerous restore jobs will be created on the NetBackup Master server. Index rebuilds
can also cause a mass recall of content from NetBackup.
If the backup tapes that contain migrated Enterprise Vault content are not available in the tape library, the
recall of the archived content will be further delayed. Lastly, if the NetBackup environment is busy with a
limited number of tape drives, restores can also be delayed as restore jobs generally have a lower priority
for tape and disk resources compared to that of scheduled backup jobs.

If Not Yet at Enterprise Vault 10

If the environment will be upgraded to Enterprise Vault 10 or later, it is recommended that migrations be
configured after the upgrade has been performed and if 32-bit indexes will be upgraded to 64-bit. If
content has been migrated before indexes have been upgraded, content will be recalled back from
NetBackup during the index rebuild process. This process can be very slow if there has been a large
amount of content migrated to NetBackup. It should be noted that it is not immediately necessary to
upgrade 32-bit indexes to 64-bit after an upgrade to Enterprise Vault 10.

Page 1

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Requirements
Enterprise Vault
Migrations are supported with Enterprise Vault 6.0 and later. It should be noted that the necessary
software components for migration are automatically installed with versions of Enterprise Vault 8.0 SP2
and earlier.
Starting with Enterprise Vault 8.0 SP3 and later, the migration software components are included with the
NetBackup Client software (NetBackup 7.1 or later). The necessary file, NBUMigrator.exe, can be found
in the <installation_directory>\NetBackup\bin. NBUMigrator.exe is a COM-based application and must be
registered on the Enterprise Vault server. This can be done by running NBUMigrator.exe /RegServer.

NetBackup
On the NetBackup Master and Media servers, the version of NetBackup must be NetBackup Enterprise.
NetBackup Standard is not supported with NetBackup Enterprise Vault migrator.
At minimum, a NetBackup 5.1 client must be installed on the Enterprise Vault server. The client version
installed on the Enterprise Vault server must not be greater than that of the version of NetBackup
(including patches) on the master and media servers. For example, if the NetBackup master and media
servers were running NetBackup 7.6.0.4, the client version must not be at a version lower than 7.6.0.4
and no higher than 7.6.04.

Configuring the NetBackup Client on the Enterprise Vault

Server
Installation
1. Install the base NetBackup Client software per the NetBackup installation instructions
2. During the installation, make sure to specify the correct name (or virtual name) of the NetBackup
Master server. Also add any NetBackup Media servers that may be used for migrations
3. For the NetBackup client name, the DNS alias (CNAME) for the Enterprise Vault server should be
used. For example, if the physical name of the Enterprise Vault server is server1, but the
CNAME record for the instance of Enterprise Vault is evserver1, specify evserver1 for the
NetBackup client name.

Page 2

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 1 - Configuring the NetBackup Client

4. After the client has been installed, apply any patches

Post Client Installation

Ensure that the system path on the Enterprise Vault server has been updated to include the
NetBackup\bin directory. To do this, bring up the System Properties on the EV server. Click on the
Advanced tab. Click on the Environment Variables button at the bottom of the screen. At the bottom of
the screen is a list of System variables. Look for Path. Highlight Path and then click on Edit. In the
Edit dialog, go to the end of the line for Variable value and add the following (assuming a NetBackup
client installation directory of C:\Program Files\VERITAS\NetBackup):
C:\Program Files\VERITAS\NetBackup\bin.

Page 3

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 2 - Adding the NetBackup installation directory to the system path

After updating the path variable, open a command line window and type in the following command:
bpbackup
If the output is similar to what is listed in Figure 3, the system path is set properly.

Figure 3 - Verifying the system path environmental variable

Using Registry Editor, ensure that the client name for NetBackup matches the DNS alias (CNAME) for the
Enterprise Vault server. Expand out to HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config.
Look for the Client_Name value as shown in Figure 4.

Page 4

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 4 - Verifying the NetBackup client name in the Windows Registry

If any changes were made, restart all NetBackup services on the Enterprise Vault Server.

Configuring the NetBackup Master Server

Adding a License Key
If the NetBackup administrator does not see the DataStore policy type available when creating a backup
policy, it will be necessary to add the following license key to the master server:
DEXW-PIHN-Z3IP-ZO63-PPP3-PPC6-PPRP-PPPP-PPC
After adding the key, restart the master server services/daemons. Note: it is a best practice to shutdown
services/daemons on any media servers associated with the master server before restarting
services/daemons on the master server and then restart services/daemons on media servers once the
master server is back up and running.

Configuring a NetBackup Policy for Enterprise Vault Migrations

Creating a Policy
Using the NetBackup Administration Console, right-click on Policies and click on New Policy. The policy
name can be any valid, unique name that conforms to NetBackup policy naming standards. Make sure
that the Use Backup Policy Configuration Wizard check box is NOT checked (if applicable) as show in
Figure 5

Page 5

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 5 - Adding a new NetBackup policy

Policy Attributes
1. In the policy attributes section, change the policy type to DataStore
2. Select an appropriate policy storage unit. A disk storage unit (NetBackup 5.1) or disk storage unit
that is not set for Enable Temporary Staging Area (NetBackup 6.0) should not be used. A disk
staging storage unit (NetBackup 5.1), disk storage unit with Enable Temporary Staging Area
enabled (NetBackup 6.0), a media manager storage unit (tape), NDMP storage unit, or a storage
unit group that does not contain a regular disk storage unit can be used. Storage units that are
part of a media server deduplication pool can also be used (NBU 7.0 and later).
3. If the storage unit is tape based, select a volume pool. It is recommended not to use the
NetBackup volume pool.
4. Set job priority levels as needed
5. Make sure that the policy is active
6. Set any other attributes as needed

Page 6

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 6 - Policy attributes

Policy Schedule
Depending on which version of NetBackup is being used, a schedule may be automatically configured.
With newer versions of NetBackup (7.1 and later), an application-based schedule named DefaultApplication-Backup will be created. With older versions of NetBackup, a schedule will need to be added.
Ensure that the schedule type is Application Backup. The name of this schedule must be changed to
EV_Default_Schedule. Change the retention to infinity (level 9) and set the Media multiplexing to 1 as
shown in Figure 7.

Page 7

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 7 - Setting schedule attributes

Ensure that the schedule is set for 24/7 by clicking on the Start Window tab in the Change Schedule
window as shown in Figure 8.

Page 8

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 8 - Setting the start window

Policy Clients
On the Clients tab, click on New. For the client name, use the DNS alias (CNAME) for the Enterprise
Vault server. Once the client name (or client names if multiple Enterprise Vault servers are to be
configured for migration) has been entered, click on OK at the bottom of the screen.

Configuring Vault Store Partitions for Migration to NetBackup

Setting up Collections
Before archived items can be migrated to NetBackup, collections must be first set up.
1. Using the EV Administration Console, bring up the properties on the vault store partition to be
configured for migration
2. Enable collections by going to the Collections tab. Click on Use collection files.
3. Enter appropriate values for collection times. By default, the schedule is from 10AM to 4PM daily.
4. Enter appropriate values for the Maximum collection file size and Age at which files will be
collected. It is recommended that the size be limited to 20 to 30 megabytes to ensure quicker
recalls of archived content if the need arises.
5. Click on Apply.

Page 9

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 9 - Configuring collections for a Vault Store partition

6. A prompt may appear asking if collections should be enabled. Click on Yes.

Setting up Migration
If collections have been enabled, migrations can be configured for the Vault Store partition. To set up
migration to NetBackup, perform the following steps:
1. Using the EV Administration Console, bring up the properties on the vault store partition to be
configured.
2. Click on the Migration tab.
3. Click on Migrate collection files or Migrate files depending on the version of Enterprise Vault.
A pop up window may appear explaining that enabling migrations may delay recalls of archived
items.
4. Select VERITAS NetBackup or Symantec NetBackup as the Migrator.
5. Enter the desired values for Migrate files older than and Remove collection files from primary
storage.
6. Click on Apply

Page 10

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 10 - Configuring migration of Vault Store partition

7. Click on Yes for Are you sure you want to use file migrator software?
8. Click on the Advanced tab.
9. For the NBU_Policy value, use the name of the NetBackup policy that was created in the
Configuring a NetBackup Policy for Enterprise Vault Migrations section (EV-Migration-Policy in
this example)
10. For the NBU_Server value, enter the name of the NetBackup master server (nbumaster in this
example).
11. See Appendix A for a definition of other settings in the Advanced tab
12. Click on the Test button to validate the configuration. If no errors are present in the Enterprise
Vault section of the Windows Event Viewer, then the configuration is set up property. Click on
OK.

Page 11

Enterprise Vault How-To Migrating Archived Enterprise Vault Content to Veritas NetBackup

Figure 11 - Advanced settings for migrations

Page 12

APPENDIX A Settings in the Vault Store Partition Advanced

Tab that Relate to NetBackup Migrations

NBU policy Name of the NetBackup policy that will be used for migrations
NBU server Name of the NetBackup master server
User wait timeout How long, in seconds, a user will be notified that an item is being retrieved from a
slow device (default is 40 or 60 seconds depending on the version of Enterprise Vault)
System wait timeout How long, in seconds, the Enterprise Vault system should wait for migrated file
retrieval requests before timing out (default is 600 seconds). The requested file will be removed from the
retrieval queue once the value has been reached.
Recalled file cache period How long, in days, a retrieved collection file (.cab) will stay on the
Enterprise Vault server before being re-cached (default is 7 days)
Migrate all files When set Yes, all eligible files (based on the Migrate files older than setting in the
Migration tab) will be collected and migrated. When set to No, a small number of Saveset files may
remain uncollected and therefore unmigrated. The default value is No.

About Veritas:
Veritas Technologies LLC
enables organizations to harness
the power of their information,
with solutions designed to serve
the worlds largest and most
complex heterogeneous
environments. Veritas works with
86 percent of Fortune 500
companies today, improving data
availability and revealing insights
to drive competitive advantage.
More information is available at
www.veritas.com.

For specific country offices and

contact numbers, please visit our
Web site: www.veritas.com

Veritas World Headquarters

500 East Middlefield Road
Mountain View, CA 94043 USA
+1 (650) 933 1000

2015 Veritas Technologies

LLC. All rights reserved. Veritas
and the Veritas Logo are
trademarks or registered
trademarks of Veritas
Technologies LLC or its affiliates
in the U.S. and other countries.
Other names may be trademarks
of their respective owners.
This document is provided for
informational purposes only and
is not intended as advertising. All
warranties relating to the
information in this document,
either express or implied, are
disclaimed to the maximum
extent allowed by law. The
information in this document is
subject to change without notice.