NetBackup Upgrade Guide 7.5

Symantec NetBackup 7.
5
Upgrade Guide
Release 7.5
Document revision 11
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Documentation version: 7.5 Document revision 11
Legal Notice
Copyright 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, NetBackup, LiveUpdate, and Veritas
are trademarks or registered trademarks of Symantec Corporation or its affiliates in the
U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (Third Party Programs). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Supports primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right
amount of service for any size organization
Telephone and/or Web-based support that provides rapid response and

up-to-the-minute information
Upgrade assurance that delivers software upgrades
Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis
Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
Product release level
Hardware information
Available memory, disk space, and NIC information
Operating system
Version and patch level
Network topology
Router, gateway, and IP address information
Problem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
Customer service
Customer service information is available at the following URL:
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
Questions regarding product licensing or serialization
Product registration updates, such as address or name changes
General product information (features, language availability, local dealers)
Latest information about product updates and upgrades
Information about upgrade assurance and support contracts
Information about the Symantec Buying Programs
Advice about Symantec's technical support options
Nontechnical presales questions
Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan
[email protected]
Europe, Middle-East, and Africa
[email protected]
North America and Latin America
[email protected]
Contents
Technical Support ............................................................................................... 4

Chapter 1
Introduction
........................................................................... 9
About the NetBackup 7.5 Upgrade Guide ............................................ 9
Chapter 2
Planning for post-upgrade activities ............................... 11

About the migration phases ........................................................... 11
About operational restrictions during the image metadata
migration ............................................................................. 12
How to determine your plan for the image metadata migration ............. 13
About modifying the server.conf file to improve image metadata
migration and NetBackup performance ...................................... 16
About MSDP and PureDisk deduplication solutions upgrade ................ 16
Chapter 3
Image metadata migration methods ............................... 17

Migrating the image metadata using the Simple method ..................... 17
Migrating the image metadata using the Guided method ..................... 23
Chapter 4
Performance information reference ................................ 31

Modifying the server.conf file to improve image metadata migration
and NetBackup performance .................................................... 31
About the image metadata migration rate ......................................... 33
About monitoring the phase 2 migration process ............................... 34
Chapter 5
NetBackup 7.5 operational behavior changes .............. 37

About lock files ............................................................................ 37
About foreign media servers .......................................................... 37
Contents
Chapter
Introduction
This chapter includes the following topics:
About the NetBackup 7.5 Upgrade Guide

The NetBackup 7.5 Upgrade Guide is provided to help assist you plan and
accomplish your upgrade to NetBackup 7.5. This guide is updated periodically to
provide you with the most up-to-date information. You can obtain the latest
version of this guide on the NetBackup 7.5 Upgrade portal, at the following link:
http://www.symantec.com/docs/TECH74584
Starting with NetBackup 7.5, all backup image metadata is stored in the NetBackup
relational database (NBDB). Previous versions stored this data in either the NBDB
or the flat ASCII files (image header files), depending on the source of the image
information.
The following describes the advantages of this change:
Eliminates the consistency issues for any data that previously existed in
multiple databases.
Improves the product search performance, especially in large catalogs.
Improves the performance of restores, policy scheduling, and image cleanups.
After the upgrade from a previous version of NetBackup, post-upgrade migration

of pre-existing image metadata from the file system to the NBDB begins. Different
methods for the image metadata migration are available for you to choose from.
Your method of choice is dependent on the number of images that must be
migrated and the complexity of your NetBackup environment. Once the image
metadata migration has completed successfully, the upgrade to NetBackup 7.5 is
considered complete.
10
Introduction
The catalog migration only affects the backup headers. As a result, the compressed
.f files are not decompressed since it is not accessed.
Note: When you upgrade to NetBackup 7.5, you must also install the latest available
maintenance release before you begin the post-upgrade migration. Each migration
method includes specific instructions about how to access the latest maintenance
release from the NetBackup SORT website.
Please review and incorporate the information in this upgrade guide into your
upgrade plan as is appropriate for your NetBackup environment.
Note: In addition to the methods for image metadata migration in the NetBackup
7.5 installation guides, two additional methods are documented in this upgrade
guide. Although you can use any of the documented methods, Symantec
recommends that you use one of the methods in this upgrade guide.
Note: For NetBackup installations that include globally clustered master servers
using the Global Cluster Option (GCO), follow the upgrade planning guidelines in
this guide. Then, refer to the following document for the specific steps to upgrade
these servers to NetBackup 7.5:
http://www.symantec.com/business/support/index?page=content&id=HOWTO73064
Chapter
Planning for post-upgrade

activities
About the migration phases
About operational restrictions during the image metadata migration
How to determine your plan for the image metadata migration
About modifying the server.conf file to improve image metadata migration

and NetBackup performance
About MSDP and PureDisk deduplication solutions upgrade
About the migration phases

The image metadata migration begins after NetBackup 7.5 has started. The image
migration occurs in two phases as follows:
Phase 1 migration
This phase is initiated automatically after the upgrade steps

have been completed, when the first instance of the
nbstserv process runs.
The following images are migrated during this phase:
All SLP controlled images
All staged DSSU images
12
Planning for post-upgrade activities

About operational restrictions during the image metadata migration
Phase 2 migration
This phase is initiated automatically based on the image

clean-up jobs scheduled by nbpem, or you can initiate it
manually to speed up the migration process.
This phase migrates all of the images that were not migrated
in phase 1.
Note: The migration phases can run in any order and may also overlap. Refer to
the following topics for specific instructions about how to run the migration
phases:
See Migrating the image metadata using the Simple method on page 17. and
See Migrating the image metadata using the Guided method on page 23.
About operational restrictions during the image

metadata migration
During the image metadata migration, certain NetBackup and OpsCenter
operations may prevent a successful image metadata migration. Other NetBackup
operations are also affected and may report errors while the image metadata
migration is in progress.
The following describes the guidelines that you should follow before the upgrade
and during the image metadata migration. The following also describes expected
NetBackup operational behavior during the image metadata migration.

Disable OpsCenter data collection.

Guidelines to follow
before upgrades and
If you use OpsCenter, before you start the upgrade, disable
during image metadata
data collection for the master server. Do not activate data
migration
collection for the server until after phase 1 and phase 2 of the
image metadata migration have completed.
For information on how to disable OpsCenter data collection,
refer to the section "Modifying an OpsCenter Data Collector
configuration" in the NetBackup OpsCenter Administrator's
Guide.
Do not perform any catalog backup or catalog recovery

operations until after phase 1 and phase 2 of the image
metadata migration have completed.
Minimize the use of any NetBackup commands that query the
NetBackup catalog until after phase 2 of the image metadata
migration has completed. Such commands include but are not
restricted to bpimage and bpimagelist. During the
migration, these types of commands consume resources that
cause them to run inefficiently and also slow the migration
process.
NetBackup operational Capacity management and DSSU staging jobs cannot run while
behavior during image
phase 1 of the image metadata migration is in progress.
metadata migration
Some user-interface and reporting functions are likely to report
errors until phase 2 of the image metadata migration has
completed.
For example, in the NetBackup Administration Console, the
following error message appears if you attempt a catalog search
on your AdvancedDisk media:
INF - unexpected return value from db_IMAGEreceive:
unable to process request 228
The execution of the bpexpdate command with either the
-deassign or the -media option fails while phase 2 of the
image metadata migration is in progress.
How to determine your plan for the image metadata

migration
The following guidelines are intended to help you determine how to perform the
image metadata migration for your backup environment.
Calculate the estimated total time to complete an upgrade to NetBackup and both
migration phases as follows:
13

Determine the number of images on your system that need their image
metadata migrated by running the following command:
On UNIX systems:
/usr/openv/netbackup/bin/admincmd/bpimagelist -idonly -d
"01/01/1970 00:00:00" | wc -l
On Windows systems:
install_path\NetBackup\bin\admincmd\bpimagelist -idonly -d
"01/01/1970 00:00:00" | %SystemDrive%\Windows\System32\find.exe
/C " ID: "
Use Figure 2-1 to find the image count for your system, along the x axis. Then,
determine which line in the figure for your image count most accurately
represents the performance of your master server. Refer to Table 2-1 for a
description of each line.
Figure 2-1
Estimated image metadata migration times
24
22
20
18
Migration time (hours)
14
16
14
12
10
8
6
4
2
0
100,000
1,000,000
Image count
Insufficient resources
Simple method
10,000,000
Guided method

Table 2-1
Diagram line definitions for estimated image metadata migration

times
Line
Description
Insufficient
Resources line
(using the Simple
method)
This line assumes a migration rate of 30 images per second.

This performance level can be expected if your system disks are slow
and/or you cannot tune the NetBackup relational database (NBDB)
with enough cache memory.
Refer to the following topic for more information:
See Modifying the server.conf file to improve image metadata
migration and NetBackup performance on page 31.
Simple Method
line (adequate
system resources
using the Simple
method)

This performance level can be achieved if your system runs on low
latency disks and you can tune the NBDB with enough cache memory.
Guided Method
line (robust system
resources using
the Guided
method)

This performance level can be achieved only by using the Guided
method, high performance RAID disk, and ample cache memory for
the NBDB.
Plot your current total image count on the x axis and determine if your master
server qualifies for the Simple method, the Guided method, or if it has
insufficient system resources.
Referencing the appropriate line, determine the migration time on the y axis.
If you can schedule enough time to perform the upgrade and the migration
without the need to run backups, use the Simple method.
Otherwise, use the Guided method.
15
16

About modifying the server.conf file to improve image metadata migration and NetBackup performance
About modifying the server.conf file to improve image

metadata migration and NetBackup performance
Systems with more than 1 million images to be migrated can benefit greatly by
modifying the server.conf file before an upgrade. Certain changes can improve
the performance of the image metadata migration and NetBackup operations
after all images are migrated into the NetBackup relational database (NBDB).
For any systems that contain more than 1 million images, Symantec recommends
that you modify the server.conf file.
See Modifying the server.conf file to improve image metadata migration and
NetBackup performance on page 31.
About MSDP and PureDisk deduplication solutions

upgrade
NetBackup 7.5.0.6 contains an upgrade to the MSDP and PureDisk plug-in. The
upgrade corrects a potential case sensitivity issue with client names in backup
policies. If all of your NetBackup media servers are running Windows, and you
do not plan to add UNIX or Linux servers running MSDP, you may safely ignore
the rest of this section. Patch computers that match the listed criteria to NetBackup
7.5.0.6 or later.
Clients that perform client-side deduplication
Media servers that perform deduplication
UNIX or Linux media servers that use MSDP
VMware backup hosts
More information about this change is available. Please see

http://www.symantec.com/docs/TECH207194/.
Chapter
Image metadata migration

methods
Migrating the image metadata using the Simple method
Migrating the image metadata using the Guided method
Migrating the image metadata using the Simple

method
Use this method to perform the image metadata migration if the following is true
for your NetBackup environment:
You can suspend normal NetBackup operations while the image metadata
migration is in progress.
Note: Remember to update NetBackup OpsCenter to version 7.5 before you update
your NetBackup master servers to version 7.5. See the NetBackup OpsCenter
Administrator's Guide for complete information.
18
Image metadata migration methods

Table 3-1 describes the steps to upgrade NetBackup and complete the image
metadata migration. To help you keep track of your progress, the table includes
a Completed column for you to mark as you complete each task.
Table 3-1
Steps to upgrade NetBackup and complete the image metadata

migration using the Simple method
Step
Task
Perform any pre-upgrade tasks that you would normally do in regard to your
NetBackup environment. For example:
Stop all customized or third-party scripts.
Perform any cluster-specific tasks.
Perform the following pre-upgrade tasks as described in the NetBackup 7.5

installation guides:
Run a hot catalog backup.
Deactivate all NetBackup policies.
Deactivate all disk staging storage units.
Stop all NetBackup services.
Modify the server.conf file as recommended.
Note: If the image count is less than 1 million, it is not necessary to modify the
server.conf file.
5
Important! During the upgrade, make sure that you take the following action to
prevent job-related NetBackup services from starting immediately after you finish
the upgrade:
Upgrade NetBackup as described in the NetBackup 7.5 installation guides, as follows:
On UNIX systems:
When the following question appears, enter n and press Enter:
Do you want to start the NetBackup job-related daemons so
backups and restores can be initiated?
On Windows systems:
On the Symantec NetBackup Installation Type screen, select Custom.
On the NetBackup Services screen, remove the check mark next to the option
Start job-related NetBackup services following installation.
Completed

Table 3-1
Step

migration using the Simple method (continued)
Task
Completed
In the NetBackup Installation Guide for UNIX and Linux:

Perform steps 6 - 14 as described in the section "Upgrading server software
from versions 6.x or 7.x to 7.5".
In the NetBackup Installation Guide for Windows:
For local server upgrades, perform steps 4 - 14 as described in the section
"Installing or upgrading servers locally.
For remote server upgrades, perform steps 4 - 16 as described in the section
"Installing or upgrading servers remotely.
For clusters, perform steps 4 - 16 as described in the section "Installing or
upgrading servers in clustered environments.
Stop all NetBackup processes and services as follows:
On UNIX systems:
/usr/openv/netbackup/bin/bp.kill_all
On Windows systems:
install_path\NetBackup\bin\bpdown -f
Immediately after you stop all NetBackup processes and services, you must install
the latest NetBackup maintenance release. This release includes very important
fixes that were released after NetBackup 7.5.
To access the latest NetBackup 7.5 maintenance release:
Go to the NetBackup SORT website:

https://sort.symantec.com/netbackup
In the Installation and Upgrade Checklist section, select:

Product: Select the correct product (NetBackup Enterprise Server or
NetBackup Server)
Product version you are installing or upgrading to: Specify the latest
version of NetBackup
Platform: Select the platform of the server you want to upgrade.
Processor: Specify the processor of your server.
Product version you are upgrading from (Optional): Select the current
version of NetBackup on the server you want to upgrade.
Click Generate Checklist.
Under Upgrade Information, there is a version_number Download Links

hyperlink. Click that hyperlink for the latest maintenance release.
19
20

Table 3-1
Step
Task
Restart NetBackup as follows:

On UNIX systems:
/usr/openv/netbackup/bin/bp.start_all
On Windows systems:
install_path\NetBackup\bin\bpup -f
Note: After NetBackup is restarted, phase 1 of the image metadata migration

begins.
9
Start the NetBackup Administration Console and open the Activity Monitor.
10
To start phase 2 of the image metadata migration, run the following clean-up
command and wait for the image clean-up job to complete:
On UNIX systems:
/usr/openv/netbackup/bin/admincmd/bpimage -cleanup
-allclients
On Windows systems:
install_path\NetBackup\bin\admincmd\bpimage -cleanup
-allclients
Use the Activity Monitor to view the progress. If the clean-up job completes with
a status of zero, proceed to the next step.
Note: To view the progress details of phase 2 migration, refer to the following
topic: See About monitoring the phase 2 migration process on page 34.
Completed

Table 3-1
Step

Task
If the job status is not zero, do the following:
On UNIX systems:
/usr/openv/netbackup/bin/admincmd/nbemmcmd -listsettings
-brief -machinename masterservername
On Windows systems:
install_path\NetBackup\bin\admincmd\nbemmcmd -listsettings
If the result shows LIST_FS_IMAGE_HEADERS = "0", phase 2 has completed.

You can proceed to the next step.
If the result shows LIST_FS_IMAGE_HEADERS = "1" or if no result appears,
phase 2 has not completed.
You must re-run bpimage -cleanup -allclients and wait for it to complete.
Then, re-run nbemmcmd -listsettings -brief -machinename
masterservername.
If the result still shows LIST_FS_IMAGE_HEADERS = "1" or if no result appears,
contact Symantec Technical Support.
Check the following directory for corrupt images:
On UNIX systems:
/usr/openv/netbackup/db.corrupt
On Windows systems:
install_path\NetBackup\db.corrupt
Examine all files in the directory and if necessary, contact Symantec Technical
Support for assistance.
Completed
21
22

Table 3-1

Step
Task
11
Wait for both phase 1 and phase 2 migrations to complete.
Note: If the image metadata migration appears to be taking much longer than your
estimated total migration time, please contact Symantec Technical Support.
To determine if migration has completed, do the following:
On UNIX systems:
On Windows systems:
If the result shows SLP_DSSU_MIGRATION_STATE="1", phase 1 has completed.

If the result shows SLP_DSSU_MIGRATION_STATE="0", phase 1 has not completed.
12
This step applies only to cluster installations.

After all image metadata migration processes have completed on this master server,
for other master servers in the cluster, you can update the remaining nodes to
NetBackup 7.5 by using the the normal cluster upgrade process. For complete
details, see the NetBackup 7.5 Installation Guide.
13
If you have any media servers that you intend to upgrade to NetBackup 7.5, upgrade
them now.
If your UNIX or Linux media server uses MSDP, an upgrade to NetBackup 7.5.0.6
or later is recommended. Upgrades to 7.5.0.6 is also recommended for:
VMware backup hosts.
Clients that perform client-side deduplication to either a UNIX or Linux based

MSDP.
Clients that perform client-side deduplication to a PureDisk server.
More information is available on this topic.

See About MSDP and PureDisk deduplication solutions upgrade on page 16.
14
Reactivate the following in the order as shown:
All disk staging storage units.
All NetBackup policies.
Completed

Table 3-1

Step
Task
Completed
15
Upgrade your client computers as time and backup windows permit. A client upgrade
is the same as a client installation. See the installation guides for more information
about installing NetBackup clients.
Symantec NetBackup Installation Guide - Windows
Symantec NetBackup Installation Guide - UNIX and Linux
16
Monitor your backup environment to verify that normal NetBackup operation has
resumed.
Migrating the image metadata using the Guided

method
Use this method to perform the image metadata migration if the Simple method
requires too much time.
Note: Symantec is currently developing tools to help you perform the steps in this
method. For more details, contact your Business Critical Services (BCS)
representative.
Note: Remember to update NetBackup OpsCenter to version 7.5 before you update
your NetBackup master servers to version 7.5. You must also disable OpsCenter
data collection. See the NetBackup OpsCenter Administrator's Guide for complete
information.
Table 3-2 describes the steps to upgrade NetBackup and complete the image
metadata migration. To help you keep track of your progress, the table includes
a Completed column for you to mark as you complete each task.
23
24

Table 3-2

migration using the Guided method
Step
Task
Perform any pre-upgrade tasks that you would normally do in regard to your
NetBackup environment. For example:
Stop all customized or third-party scripts.
Perform any cluster-specific tasks.
Perform the following pre-upgrade tasks as described in the NetBackup 7.5

installation guides:
Run a hot catalog backup.
Disable OpsCenter data collection for this master server.
Disable all storage lifecycle policies (SLPs).
Deactivate all NetBackup policies.
Deactivate all disk staging storage units.
Stop all NetBackup services.
Modify the server.conf file as recommended.
Note: If the image count is less than 1 million, it is not necessary to modify the
server.conf file.
5
Important! During the upgrade, make sure that you take the following action to
prevent job-related NetBackup services from starting immediately after you finish
the upgrade:
Upgrade NetBackup as described in the NetBackup 7.5 installation guides, as follows:
On UNIX systems:
When the following question appears, enter n and press Enter:
Do you want to start the NetBackup job-related daemons so
backups and restores can be initiated?
On Windows systems:
On the Symantec NetBackup Installation Type screen, select Custom.
On the NetBackup Services screen, remove the check mark next to the option
Start job-related NetBackup services following installation.
Completed

Table 3-2
Step

migration using the Guided method (continued)
Task
Completed
In the NetBackup Installation Guide for UNIX and Linux:

Perform steps 6 - 14 as described in the section "Upgrading server software
from versions 6.x or 7.x to 7.5".
In the NetBackup Installation Guide for Windows:
For local server upgrades, perform steps 4 - 14 as described in the section
"Installing or upgrading servers locally.
For remote server upgrades, perform steps 4 - 16 as described in the section
"Installing or upgrading servers remotely.
For clusters, perform steps 4 - 16 as described in the section "Installing or
upgrading servers in clustered environments.
Stop all NetBackup processes and services as follows:
On UNIX systems:
/usr/openv/netbackup/bin/bp.kill_all
On Windows systems:
install_path\NetBackup\bin\bpdown -f
Immediately after you stop all NetBackup processes and services, you must install
the latest NetBackup maintenance release. This release includes very important
fixes that were released after NetBackup 7.5.
To access the latest NetBackup 7.5 maintenance release:
Go to the NetBackup SORT website:

https://sort.symantec.com/netbackup
In the Installation and Upgrade Checklist section, select:

Product: Select the correct product (NetBackup Enterprise Server or
NetBackup Server)
Product version you are installing or upgrading to: Specify the latest
version of NetBackup
Platform: Select the platform of the server you want to upgrade.
Processor: Specify the processor of your server.
Product version you are upgrading from (Optional): Select the current
version of NetBackup on the server you want to upgrade.
Click Generate Checklist.
Under Upgrade Information, there is a version_number Download Links

hyperlink. Click that hyperlink for the latest maintenance release.
25
26

Table 3-2
Step
Task
Restart NetBackup as follows:

On UNIX systems:
/usr/openv/netbackup/bin/bp.start_all
On Windows systems:
install_path\NetBackup\bin\bpup -f
Note: After NetBackup is restarted, phase 1 of the image metadata migration

begins.
9
The following command must be run on the master server for multiple clients,
simultaneously. To perform phase 2 migration, make sure that you run the command
for each client:
On UNIX systems:
/usr/openv/netbackup/bin/cat_import -client name
-delete_source -base /usr/openv/netbackup/db
On Windows systems:
install_path\NetBackup\bin\cat_import -client name
-delete_source -base install_path\NetBackup\db
10
Start the NetBackup Administration Console and open the Activity Monitor.
11
To complete phase 2 of the image metadata migration, run the following clean-up
command and wait for the image clean-up job to complete:
On UNIX systems:
/usr/openv/netbackup/bin/admincmd/bpimage -cleanup
-allclients
On Windows systems:
install_path\NetBackup\bin\admincmd\bpimage -cleanup
-allclients
Use the Activity Monitor to view the progress. If the clean-up job completes with
a status of zero, proceed to the next step.
Note: To view the progress details of phase 2 migration, refer to the following
topic: See About monitoring the phase 2 migration process on page 34.
Completed

Table 3-2
Step

Task
If the job status is not zero, do the following:
On UNIX systems:
On Windows systems:

You can proceed to the next step.
You must re-run bpimage -cleanup -allclients and wait for it to complete.
Then, re-run nbemmcmd -listsettings -brief -machinename
masterservername.
If the result still shows LIST_FS_IMAGE_HEADERS = "1" or if no result appears,
contact Symantec Technical Support.
Check the following directory for corrupt images:
On UNIX systems:
/usr/openv/netbackup/db.corrupt
On Windows systems:
install_path\NetBackup\db.corrupt
Examine all files in the directory and if necessary, contact Symantec Technical
Support for assistance.
Completed
27
28

Table 3-2

Step
Task
12
Wait for both phase 1 and phase 2 migrations to complete.
Note: If the image metadata migration appears to be taking much longer than your
estimated total migration time, please contact Symantec Technical Support.
To determine if migration has completed, do the following:
On UNIX systems:
On Windows systems:
If the result shows SLP_DSSU_MIGRATION_STATE="1", phase 1 has completed.

If the result shows SLP_DSSU_MIGRATION_STATE="0", phase 1 has not completed.
13
This step applies only to cluster installations.

After all image metadata migration processes have completed on this master server,
for other master servers in the cluster, you can update the remaining nodes to
NetBackup 7.5 by using the normal cluster upgrade process. For complete details,
see the NetBackup 7.5 Installation Guide.
14
If you have any media servers that you intend to upgrade to NetBackup 7.5, upgrade
them now.
If your UNIX or Linux media server uses MSDP, an upgrade to NetBackup 7.5.0.6
or later is recommended. Upgrades to 7.5.0.6 is also recommended for:
VMware backup hosts.
Clients that perform client-side deduplication to either a UNIX or Linux based

MSDP.
Clients that perform client-side deduplication to a PureDisk server.
More information is available on this topic.

See About MSDP and PureDisk deduplication solutions upgrade on page 16.
Completed

Table 3-2

Step
Task
15
Reactivate the following in the order as shown:
16
All disk staging storage units.
All NetBackup policies.
All SLPs.
OpsCenter data collection for this master server.
Upgrade your client computers as time and backup windows permit. A client upgrade
is the same as a client installation. See the installation guides for more information
about installing NetBackup clients.
Symantec NetBackup Installation Guide - Windows
Symantec NetBackup Installation Guide - UNIX and Linux
17
Monitor your backup environment to verify that normal NetBackup operation has
resumed.
Completed
29
30

Chapter
Performance information
reference
Modifying the server.conf file to improve image metadata migration and

NetBackup performance
About the image metadata migration rate
About monitoring the phase 2 migration process
Modifying the server.conf file to improve image

metadata migration and NetBackup performance
If the total image count to be migrated is more than 1 million, certain parameters
in the server.conf file should be changed before a NetBackup upgrade.
These changes help improve the following:
Performance of the image metadata migration.
Performance of NetBackup processes after all of the image metadata has been
migrated into the NetBackup relational database (NBDB).
If there are more than 1 million images in your database, it is recommended that
you make some modification to this file.
The following procedure describes how to modify the server.conf file to help
improve the image metadata migration performance.
To modify the server.conf file before a NetBackup upgrade
On the server that you want to upgrade, save a copy of the current
server.conf file in a remote and a secure location.
32
Performance information reference

Modifying the server.conf file to improve image metadata migration and NetBackup performance
The file resides in the following location:
On UNIX systems:
/usr/openv/var/global/server.conf
On Windows systems:
install_path\Program Files\Veritas\NetBackupDB\CONF\Server.conf
On the server that you want to upgrade, open the server.conf file in a text
editor.
Change the following parameters as appropriate for your backup environment:

-ch (maximum
cache size)
This parameter indicates the maximum cache size that dbsrv11

can use, which is the SQLAnywhere service that manages the
NBDB. The default size in NetBackup versions earlier than 7.5 is
512M. Beginning with NetBackup 7.5, the default value has been
increased to 1024M.
As a guideline, this parameter should be set to a minimum of 1G
of cache for every 1 million images to be migrated.
For example:
-ch 1G (for systems with up to 1M images)
Note: If the cache size is set too low, it can cause a slow rate of
migration and NetBackup operational response. If the cache size
is set too high, it can consume too much of the available system
memory (RAM). As with any tuning parameter, to achieve the
desired value and results may take multiple attempts of adjusting,
starting, migrating, and stopping.
Note: If the master server has ample available memory,

performance of some operations can be improved. In such
systems, you may want to increase -ch by a factor of two or three
above this guideline.
-m
Provides a way to automatically limit the growth of the

transaction log.
Create a new line and add this entry to the server.conf file.
Save the changes to the file and close it.


Because each NetBackup environment is unique, the precise rate at which the
image metadata migration runs and completes cannot be calculated.
Based on the empirical data that was observed in test scenarios, you can expect
a migration rate of approximately 75 images per second on a system with adequate
resources using the Simple method.
The following factors must be considered when you estimate the time needed to
complete the image metadata migration after the upgrade:
System performance
Size of the image catalog
Migration method
It is very important to note that the following information is based on the empirical
data that was observed in test scenarios. This information should be used only
for planning purposes.
The following provides an example of resource utilization on a master server
during the migration process.
Table 4-1
Example of master server resource utilization during the migration

process
Impact of Simple
method image
metadata migration
(see note)
Typical CPU % of
utilization
Typical memory
utilization
Typical disk
throughput rate
10-20%
Minimal, in addition 2 MB/sec write

to normal NetBackup 1 MB/sec read
operation.
Note: The Guided method for image metadata migration uses multiple cat_import
processes and each instance has the impact shown in Table 4-1.
The rates shown are based upon the best empirical data observed and are presented
only for planning purposes. Actual migration rates vary and are dependent on
the following factors:
A system with sufficient CPU and resource bandwidth for the NetBackup
environment.
33
34

Note: Under powered systems result in a significant degradation of the values

as shown by the insufficient resources line in the "Estimated image metadata
migration times" figure.
The throughput capability of the disk volumes that host the pre-existing image
metadata information and the NetBackup relational database (NBDB) location
where the image metadata is to be migrated.

While the clean-up job runs, you can monitor the progress of the phase 2 migration.
In the Activity Monitor, double-click on the clean-up job. When the Job Details
dialog box appears, click the Detailed Status tab.
The following describes an example of how phase 2 migration progress appears:
The start of phase 2 migration is logged as follows:

2/8/2012 4:05:50 PM - Info bpdbm(pid=5948) image catalog cleanup
2/8/2012 4:05:50 PM - Info bpdbm(pid=5948) Importing flat file
image headers into the database.
Phase 2 migration of each client is logged as follows:

2/8/2012 4:09:16 PM - Info bpdbm(pid=5948) [000:03:26] Initiating
import for client: section8
2/8/2012 4:09:18 PM - Info bpdbm(pid=5948) [000:03:28] Finished
importing images for client: section8 with 36 imported, 0 skipped,
0 corrupt.
2/8/2012 4:09:18 PM - Info bpdbm(pid=5948) [000:03:28] Overall
progress: 5525 images imported, 0 skipped, 0 corrupt. Import rate
= 26 images/sec
The end of phase 2 migration is logged as follows:

2/8/2012 4:09:44 PM - Info bpdbm(pid=5948) Finished importing all
images into the database. (Count = 6371)
The following describes the key parameters in the log:

Table 4-2
Key log parameters for phase 2 migration progress
Parameter
Description
[hhh:mm:ss]
The cumulative time that phase 2 has been

running.

Table 4-2
Key log parameters for phase 2 migration progress (continued)
Parameter
Description
n skipped
The number of images that were skipped for some

reason, and would need to be looked at.
n corrupt
The number of images that are determined to be

corrupt, and have been moved to the db.corrupt
directory.
Import rate = n images/sec
The cumulative import rate, which can be used

to validate the estimated migration time.
35
36

Chapter
NetBackup 7.5 operational

behavior changes
About lock files
About foreign media servers
About lock files

To provide access control for the NetBackup relational database (NBDB), NetBackup
7.5 creates a .lck lock file automatically for each backup image.
The .lck files reside in the following locations:
On UNIX systems:
/usr/openv/netbackup/db/images/client_directory/time_directory/image_name.lck
On Windows systems:
install_path\NetBackup\db\images\client_directory\time_directory\image_name.lck
When all images in a time_directory directory are expired, any remaining .lck
files are removed when the time_directory directory is deleted.
Warning: Do not delete, rename, move, or otherwise modify any .lck files.

Images may include the names of media servers that do not exist in the current
domain. These media servers are known as foreign media servers.
38
NetBackup 7.5 operational behavior changes

The following describes when a foreign media server may appear in a backup
image:
When a backup image is migrated from one domain to another.
When a media server is decommissioned.
Starting with NetBackup 7.5, foreign media servers also appear in the output for
the following command:
nbemmcmd -listhosts
The output displays the foreign media server as follows:

foreign_media server

NetBackup Upgrade Guide 7.5

Uploaded by

Copyright:

Available Formats

NetBackup Upgrade Guide 7.5

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetBackup Upgrade Guide 7.5

Uploaded by

Copyright:

Available Formats

Symantec NetBackup 7.

Telephone and/or Web-based support that provides rapid response and

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

Premium service offerings that include Account Management Services

Contacting Technical Support

Product release level

Available memory, disk space, and NIC information

Version and patch level

Router, gateway, and IP address information

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs, DVDs, or manuals

Support agreement resources

Europe, Middle-East, and Africa

North America and Latin America

Technical Support ............................................................................................... 4

About the NetBackup 7.5 Upgrade Guide ............................................ 9

Planning for post-upgrade activities ............................... 11

Image metadata migration methods ............................... 17

Performance information reference ................................ 31

NetBackup 7.5 operational behavior changes .............. 37

About the NetBackup 7.5 Upgrade Guide

About the NetBackup 7.5 Upgrade Guide

Improves the product search performance, especially in large catalogs.

Improves the performance of restores, policy scheduling, and image cleanups.

After the upgrade from a previous version of NetBackup, post-upgrade migration

Planning for post-upgrade

About the migration phases

About operational restrictions during the image metadata migration

How to determine your plan for the image metadata migration

About modifying the server.conf file to improve image metadata migration

About MSDP and PureDisk deduplication solutions upgrade

About the migration phases

This phase is initiated automatically after the upgrade steps

All SLP controlled images

All staged DSSU images

Planning for post-upgrade activities

This phase is initiated automatically based on the image

About operational restrictions during the image

Planning for post-upgrade activities

Disable OpsCenter data collection.

Do not perform any catalog backup or catalog recovery

How to determine your plan for the image metadata

Planning for post-upgrade activities

Estimated image metadata migration times

Planning for post-upgrade activities

Diagram line definitions for estimated image metadata migration

This line assumes a migration rate of 30 images per second.

This line assumes a migration rate of 75 images per second.