Symantec NetBackup 7.

0 Additional Operational Notes

UNIX, Windows, and Linux

NetBackup 7.0

Symantec NetBackup 7.0 Additional Operational Notes

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.0

Legal Notice
Copyright 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Veritas, and NetBackup 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 maintenance 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 Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week Advanced features, including Account Management Services

For information about Symantecs Maintenance Programs, you can visit our Web site at the following URL: www.symantec.com/techsupp/

Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ 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: www.symantec.com/techsupp/

Customer service
Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with 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 maintenance contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

Maintenance agreement resources

If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com

Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. Managed Security Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.

Consulting Services

Educational Services

To access more information about Enterprise services, please visit our Web site at the following URL: www.symantec.com Select your country or language from the site index.

About additional operational notes

This document includes the following topics:

About NetBackup general notes About NetBackup Access Control About NetBackup catalog notes About NetBackup deduplication About NetBackup Hyper-V About NetBackup user interface notes About NetBackup OpsCenter notes About NetBackup database agent notes About NetBackup Snapshot Client About VMware notes

About NetBackup general notes

The following topics contain additional information about NetBackup 7.0 that pertains to the NetBackup 7.0 documentation set, and installations and upgrades, and general NetBackup issues.

About additional operational notes About NetBackup general notes

About NetBackup documentation notes

The following items describe the additional known issues that were found in the NetBackup 7.0 documents:

For NetBackup 7.0, support has been dropped for Novell NetWare Client. Customers who want to continue to use NetWare must install a 6.5 NetWare client for NetBackup7.0, to have back-level support. The Key Management Service (KMS) was enhanced in NetBackup 7.0 to support 20 key groups, which translates to 20 volume pools. However, the NetBackup Security and Encryption Guide incorrectly states that only two key groups and two volume pools are supported. Chapter 1 of the Symantec OpsCenter Administrator's Guide incorrectly states the OpsCenter server is supported on Windows and Solaris platforms. The OpsCenter server is supported on Windows and UNIX platforms. Table 2-3 in the NetBackup Release Notes incorrectly states the NetBackup-Java administration console and the Backup, Archive, and Restore interface are supported on the Windows 7 operating system. Only the Backup, Archive, and Restore interface is supported because NetBackup 7.0 supports only clients on Windows 7.0. Some links in NetBackup Installation guides do not work. In the section, About replacing NetBackup server types not supported in NetBackup 7.0 and its subsections, the links to other documents do not work correctly. To avoid this problem, copy the link from the installation guide and make sure to exclude the .htm extension. Then, paste the link into your browser. The Installation Checklist Beta PDF document was erroneously included with NetBackup 7.0 DVD image. Please disregard and delete this PDF document from your DVD media. The information in this document has been updated and incorporated into the NetBackup Getting Started Guide. That guide is included in all of the media kits. It is also available from the FTP download site and the NetBackup documentation Web site.

The following documents incorrectly indicate that PureDisk storage units support Granular Recovery Technology (GRT):

NetBackup 6.5.3 patch readme NetBackup 6.5.3 for Microsoft Exchange Server Administrator's Guide NetBackup 6.5.4 for Microsoft SharePoint Server Administrator's Guide NetBackup 6.5.4 Documentation Updates

About additional operational notes About NetBackup general notes

NetBackup 7.0 for Microsoft SharePoint Server Administrator's Guide NetBackup 7.0 for Microsoft Exchange Server Administrator's Guide NetBackup 7.0 Administrator's Guide, Volume I

The following table indicates the disk storage units that support Granular Recovery. Table 1-1 Disk storage unit
BasicDisk AdvancedDisk NearStore OpenStorage PureDisk SharedDisk SnapVault

Disk storage units that support Granular Recovery Granular Recovery supported
Yes Yes No No No No No

About NetBackup installation and upgrade notes

The following items describe additional NetBackup installation and upgrade known issues.

If you upgrade from NetBackup 6.5.x to NetBackup 7.0 on an AIX system and then perform a reboot, you should verify that the PBX and NetBackup services have started after the reboot. If the services did not restart, the cause may be that the entry, install_assist entry already exists in the /etc/inittab file. This entry exists if you encountered a minor issue while you installed AIX on an IBM machine. If you encounter this issue, determine if the install_assist entry already exists in the /etc/inittab file. If it does, you can comment the entry or remove it from the file and attempt to reboot again. After the reboot completes, make sure that the PBX and NetBackup services start. During a Windows installation, if you encounter a fatal install error, you should check the installation logs to determine the cause of the error. If you find a Return value of three in the install log, open a cmd window, run the following command, and install NetBackup again.
regsvr32 oleaut32.dll

10

About additional operational notes About NetBackup general notes

The following is a sample message from the install logs.

setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556. 04-07-2008,14:32:36 : Action start 14:32:36: setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556. 04-07-2008,14:32:36 : Action ended 14:32:36: setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556. Return value 3.

If you attempt to restore a database catalog after you upgrade from NetBackup 6.0 to 6.5 to NetBackup 7.0, you may not be able to recover the database in a clustered environment. The issue occurs because the catalog backup was done in the Sybase staging directory that was configured on the C drive. That was the default staging directory in NetBackup 6.0 and the upgrade process does not change it. Thus, after a fresh install to NetBackup is performed, the Sybase staging directory defaults to the shared drive on the cluster, making the staging directory location on a different drive. When the catalog recovery is attempted, the files in the staging directory on the C drive are restored, however, the Sybase recovery expected the files to be in the shared drive on the cluster. To avoid this issue, edit the vxdbms.conf file in shared drive:\Program Files\VERITAS\NetBackupDB\data and change the following entry from:
VXDBMS_NB_STAGING = shared drive:\Program Files\VERITAS\NetBackupDB\staging

To...
VXDBMS_NB_STAGING = C:\Program Files\VERITAS\NetBackupDB\staging

After the restore is done, you should edit the file AGAIN and put back the shared drive. Then, perform a catalog backup that you can use going forward. This final step means you will not encounter this issue in the future.

If you upgrade from a previous version of NetBackup and currently have a volume pool named CatalogBackup, a volume pool name conflict can occur. Before the upgrade, users should do the following in the previous version of NetBackup:

Create a new volume pool. Move the media that is currently in the CatalogBackup volume pool into the new volume pool. Delete the CatalogBackup volume pool.

The installation portion of the upgrade process creates a new default volume pool titled CatalogBackup.

About additional operational notes About NetBackup general notes

11

About general NetBackup 7.0 notes

The following items describe the additional issues that were found in NetBackup 7.0:

While restoring the Exchange database images that were imported from Backup Exec, you may encounter some misleading logs, such as, Restoring Exchange ESE object Error: 17349102. That is not an error message. However, because of an existing issue in the log message code this log message is printed instead of the Exchange object name that is restored. Starting with NetBackup 7.0, VSP is no longer supported. That leaves Microsofts Volume Shadow Copy Services (VSS) as the only choice for an open file backup for Windows clients. In addition, there is a binary incompatibility in the 32-bit Windows XP version of VSS. For this reason, NetBackup does not support VSS on the 32-bit Windows XP operating system. Therefore, there are no supported, open file backup solutions for this platform. Symantec recommends that you leave 32-bit Windows XP clients at the latest level of NetBackup 6.5 and do not upgrade them to NetBackup 7.0. That enables you to use VSP to continue to support open file backup, which is still supported on the latest NetBackup 6.5 version. This situation exists only on the 32-bit version of Windows XP. It does not apply to the 64-bit version of Windows XP. It also does not apply to any version Windows Vista/7/2008 Server/Windows 2008 R2 Server Platforms. Except for 32-bit Windows XP, NetBackup 7.0 continues to support VSS. DFSR data cannot be protected while DFSR (DFS Replication Service) is running. If that is attempted, backups may exit with Status 0 reporting success, but fail to protect all DFSR data. If a fix is not applied, all backups of DFSR data must be done using the flat file method, outlined in the following document: http://entsupport.symantec.com/docs/340248 Instant recovery point in Time rollback fails if the disk array command takes too long to respond NetBackup uses a disk array command line interface to perform an Instant recovery point in Time rollback. If the array command takes too long to respond (300 seconds on UNIX and 120 seconds on Windows), the rollback fails with NetBackup status 5. A message similar to the following appears in the bpfis log:
09:53:01.004 [25857] <2> onlfi_vfms_logf: INF - snapshot services: emcsymfi:Thu Dec 10 2009 09:53:01.003692 <Thread id - 1> Process has timmedout (600 sec)

This problem can occur with any of the following disk array snapshot methods:

EMC_CLARiiON_Snapview_Clone

12

About additional operational notes About NetBackup general notes

EMC_CLARiiON_SnapView_Snapshot EMC_TimeFinder_Clone EMC_TimeFinder_Mirror EMC_TimeFinder_Snap Hitachi_ShadowImage Hitachi_CopyOnWrite HP_EVA_Snapclone IBM_DiskStorage_FlashCopy

An unreadable character (a square box "") is displayed instead of a period between two sentences that comprise the following error message.
Cant move assigned media. Status 91

This error message appears after you perform the following steps:

In Media node, right-click on the Assigned Media that has NetBackup as the Volume Pool. Select Change. In the Change Volume dialog, select the New Pool radio button. In the new pool field, select any volume pool other than NetBackup. Click OK. The error message with the erroneous character can appear.

The exit-notify scripts did not work properly. The exit notify scripts would only run after all streaming attempts completed. Before NetBackup 6.5.2, the scripts would run after every stream. A change was made that adds a new argument to the backup_exit_notify command that indicates if a retry is performed. In addition, an argument was added to the parent_end_notify command that indicates the number of streams that were started. An incorrect data time value is shown in the Date column of the Browse dialog. This field should display the correct date, however, it currently displays the date, 1/1/1970 for all items. You can access the Browse dialog from the Policy Backup Selection tab, the New Storage Unit dialog, and the Change Storage Unit dialog. Synthetics may not function properly between two media servers if a firewaql separates the media servers. Users who want to perform a Synthetic backup across two media servers with a firewall between them, must open a range of

About additional operational notes About NetBackup general notes

13

ports so a port can be randomly selected during the synthetic job. Opening a range of ports to use synthetics means that the firewall is less effective.

Checkpoint restart is not supported for restores from Backup Exec media. The restore job may be suspended and resumed. However, a resumed restore job restarts at the beginning of the job, since no checkpoints for the restore are available. Failed restore jobs are in an "incomplete" state rather than a "done" state. Like a suspended job, the incomplete jobs may be resumed, but restarts at the beginning of the job. Synthetics may not function properly between two media servers if a firewall separates the media servers. Users who want to perform a Synthetic backup across two media servers with a firewall between them, must open a range of ports so a port can be randomly selected during the synthetic job. Opening a range of ports to use synthetics means that the firewall is less effective. Symantec recommands that you move only one volume or volume group at a time. Administering media servers of a server that is the target of a change server operation in the console requires the server specified in the console logon dialog be in the server list of all the relevant media servers. The following items pertain to the NetBackup high availability feature. See, the NetBackup High Availability Administrator's Guide for additional information:

For NetBackup in a Veritas Cluster Server on UNIX or Linux, to start the VCS NetBackup cluster agent on all nodes of the NetBackup Group, use the following command:
haagent -start NetBackup -sys <node>

Instead of this command:

haagent -start NetBackup -force -sys <node>

Upgrades for HPSG are supported. Thus, the following limitation that is documented in the NetBackup in an HP MC/Service Guard cluster chapter is not valid. "Only a new installation of NetBackup 7.0 can be installed in a Service Guard cluster. If you have a previous version of NetBackup installed in the cluster, it cannot be upgraded to version 7.0."

Additional End-of-life notes

The NAS SnapVault Option is not offered for sale with new NetBackup 7.0 environments. However, it continues to be a supported option with NetBackup 7.0 master servers on NetBackup 6.5 media servers that use NetBackup 6.5 license keys for the remaining support life of 6.5.

14

About additional operational notes About NetBackup Access Control

If you are a current NAS SnapVault Option user and intend to upgrade to NetBackup 7.0, you can continue to use the NAS SnapVault Option and the following applies:

SnapVault can no longer be purchased and you cannot enable it with the NetBackup 7.0 license keys. To continue to use SnapVault on 7.0, you must use a NetBackup 6.5 media server and your NetBackup 6.5 license keys that enable SnapVault. The NetBackup 6.5 SKU for the NAS SnapVault Option is available for one year after NetBackup 7.0 is released. That enables you to purchase licenses to support additional capacity.

For NetBackup 7.0, support has been dropped for Novell NetWare client. Customers who want to continue to use NetWare must install a 6.5 NetWare client for NetBackup7.0, to have back-level support. In addition, the NetBackup documentation set that is on the NetBackup 7.0 DVD contains the NetBackup_AdminGuide_NetWare_Client guide. That implies that Novel Netware packages are available with this release. That is not true because 7.0 server and client support has been dropped.

About NetBackup Access Control

The following items describe the additional notes that relate to the NetBackup Access Control (NBAC) feature:

The NBAC security credential that is generated upon logon from the NetBackup-Java Administration Console or NetBackup Console (MFC), expires 24 hours after the logon finishes. That disables further operations. To avoid this issue, use the VxSS client interface (CLI) or the Veritas Security Services (VxSS Java user interface to increase the default expiration time. Because NBAC is not supported with database agents, catalog backup can fail if you attempt the backup with USE_VXSS set to REQUIRED. When authorization failures occur in an NBAC-enabled configuration, the error message(s) returned to the user may not indicate an authorization failure. Per-policy access control is not implemented in the NetBackup. The use of NetBackup database agents with NBAC was not implemented in this NetBackup release. When you add someone who is not an administrator to the NBU_Admin group, set the permissions of the following directory to word readable and writable. /user/openv/netbackup/logs/user_ops (UNIX)
install path\NetBackup\logs\user_ops (Windows)

About additional operational notes About NetBackup Access Control

15

Set the permissions of this directory to [0777] for UNIX systems and FULL CONTROL for the user group on a Windows system.

Several Windows NetBackup\bin\goodies scripts have not been modified to verify if NBAC credentials are needed. As such, the commands that run inside the scripts may fail if a user does not have a credential or has an expired credential. Before you run a Windows .cmd script, verify that you have a valid credential by performing a bpnbat -login. The Security Admin is able to list policies. The NetBackup 7.0 Security and Encryption Guide in Table 4.4 page 263 shows that the NBU_Security_Admin cannot browse policies. The NBU_Security_Admin can browse or list the policies but they cannot modify them. The Vault operator user is able to show policies. The NetBackup 7.0 Security and Encryption Guide in Table 4.4 page 263 shows that the Vault_Operator cannot browse policies. The Vault_Operator can browse or list the policies but they cannot modify them. The Vault_Operator is also able to access policies since it has permissions to run reports. To generate reports, access to the policy is required and read access is provided. The Vault Operator or Security Administrator can list the policies if they use the bppllist command and the Windows user interface (UI) but not from the Java UI. The NetBackup-Java user interface calls a trace through nbsl > nbproxy > bpdbm. The NetBackup dblibFacade_getAllPolicyNames in nbproxy gives a Permission Denied failure. That causes the user interface to not list the policies. That occurs because the Read permission is checked for Policy object in nbproxy which the Vault Operator or Security Administrator does not have. The bppllist goes directly to bpdbm using the protocol Q_CLASS_NAMES that is allowed if the user has any of the following permissions: Read on policy, Read on report, or Configure permission Because the Vault Operator has read permission on the report object and the Security Admin is able to configure permissions on the security object, then they can list the policies. The Windows UI uses db_getCLASSnames from dblib that also directly goes to bpdbm; therefore, policies can be listed

The Security Administrator does not have access to NDMP properties. The Security Administrator has all permissions for the host properties. The Vault Operator is unable to expire media. The Vault Operator should NOT have permissions to expire the media.

16

About additional operational notes About NetBackup catalog notes

The NetBackup Operator has access for Media List Report.

The following list shows the tape reports that work for the NBU_Operator: - Tape Summary - Tape Lists The following list shows the disk reports that work for the NBU_Operator: - Disk Storage Unit Status

The Security Admin user is able to modify the settings in the media and the client host properties but not in master. When the SecAdmin tries to modify RESTORE_RETRIES on the master server, NBConsole initiates the Q_CONFIGSET protocol with bpdbm. For the bpdbm protocol to go through, you must have New, Read, and Delete permission on HostProperties object. The Security Admin has only Browse and Read permissions. Therefore the SecAdmin cannot modify RESTORE_RETRIES for the master server. However, when the SecAdmin tries to modify RESTORE_RETRIES on the media server and the client, NBConsole initiates the C_UPDATE_HOST_CONFIG protocol with bprd. For the bprd protocol to go through, you must have either New, Read, and Delete on HostProp or ConfigureSecurity on SecurityObj. Because SecAdmin has ConfigureSecurity on the Security object, this protocol goes through and bprd then talks to BPDBM to complete the operation.

About NetBackup catalog notes

The following is a list of additional notes that pertain the NetBackup catalog:

Manually initiating an offline backup of the NetBackup catalog can fail if backups are in progress. Backing up the NetBackup catalog can fail if it is manually initiated and backups are in progress. The workaround for that is to initiate cold backups when NetBackup activity is minimal, or schedule the cold catalog backup to occur automatically. If catalog backups are required when NetBackup activity is high, then you should use a hot catalog backup. The catalog backup jobs that are started with the -host option to run on the media servers cannot be killed from the Activity Monitor. If a vault job starts the catalog backup on a media server, canceling the job from the Activity Monitor does not terminate the catalog backup.

About NetBackup deduplication

See the following Technote on the Symantec Support Web site for the additional NetBackup deduplication notes that were found in the NetBackup 7.0 release.

About additional operational notes About NetBackup Hyper-V

17

http://entsupport.symantec.com/docs/338123

About NetBackup Hyper-V

The following describes any additional known issues that were found in the NetBackup 7.0 documents: Policy validation fails for a Linux virtual machine if the NetBackup policy is configured with VM hostname as the Client Name Selection type. If you select VM hostname as the Client Name Selection type in a Hyper-V policy for a Linux virtual machine, policy validation may fail. In that case, specify a different Client Name Selection type in the policy (VM display name or VM GUID).

About NetBackup user interface notes

The following is a list of additional known issues that relate to the NetBackup user interfaces:

When you attempt to restore from a backup set that contains a very high volume of files (more than 1 million), the Backup Archive Restore (BAR) interface can hang. If that occurs, close the BAR user interface in question to avoid excessively large log files that can lead to a disk full condition. You may encounter an issue if you use the NetBackup-Java Administration Console to stop the NetBackup services after you install NetBackup 7.0. Symantec recommends that you use the command-line interface to stop the NetBackup services to avoid any problems that may occur. That enables you to still use the NetBackup-Java Administration Console to administer NetBackup. If you silently install NetBackup 7.0 on a Windows 2008 R2 server core platform and open the NetBackup Administration Console, the user interface appears. However, an issue exists that causes some of the functionality to not work correctly. Symantec recommends that you use one of the following user options to perform an operation that you would have performed on the NetBackup Administration Console:

The NetBackup Remote Administration console The NetBackup-Java Administration console The command line interface

18

About additional operational notes About NetBackup OpsCenter notes

About NetBackup OpsCenter notes

The following items are additional NetBackup OpsCenter notes that were found in the NetBackup 7.0 release:

The Symantec OpsCenter Administrator's Guide incorrectly states the OpsCenter server is supported on AIX platforms. For this release of NetBackup, the OpsCenter server is not supported on AIX platforms. Chapter 1 of the Symantec OpsCenter Administrator's Guide incorrectly states the OpsCenter server is supported on Windows and Solaris platforms. The OpsCenter server is supported on Windows and UNIX platforms. Table 3-2, named "Processes used by OpsCenter on UNIX" in the Symantec OpsCenter Administrator's Guide lists an incorrect process for the Symantec OpsCenter database server . The following process depicts Symantec OpsCenter database server on UNIX platforms:
/opt/SYMCOpsCenterDatabase/bin/OpsCenterDBd

The "Saving the OpsCenter database and database logs on separate hard disks" section of the Symantec OpsCenter Administrator's Guide does not mention the path for 64-bit systems in the following procedure: "To move the database log files to a different hard disk on Windows" Step 2 of this procedure states the following: Navigate to the following location:INSTALL_PATH\OpsCenter\server\db\WIN32
INSTALL_PATH\OpsCenter\server\db\WIN32 is the location on a 32-bit system.

The location on a 64-bit system is INSTALL_PATH\OpsCenter\server\db\WIN64.

Custom chargeback reports that you have created in VBR are not migrated to OpsCenter after an upgrade. In OpsCenter, the Job Count report does not include the jobs that were collected during the image data collection. These jobs are called Sparse Jobs. That is unlike the Job Count report in VBR, which also included Sparse Jobs. Because of this change, you may notice a mismatch between the job count on the OpsCenter report and the corresponding VBR report. You can upgrade from NetBackup Operations Manager (NOM) or Veritas Backup Reporter (VBR) to OpsCenter server software on a different UNIX system. To upgrade on a different UNIX system, use the Backup.sh script to back up your data on the NOM or the VBR server. Then copy the data to the OpsCenter server. The Backup.sh script is located in the Server directory of the OpsCenter DVD.

About additional operational notes About NetBackup OpsCenter notes

19

Note the following points before you upgrade from NOM or VBR to OpsCenter server software on a different UNIX system:

Manual upgrade from VBR to OpsCenter server is supported on Solaris platforms. For example, you can upgrade from VBR running on Solaris 8 to OpsCenter server running on Solaris 10. Manual upgrade from NOM to OpsCenter server is supported from specific NOM platforms. Ensure that NOM is running on the following platforms: - Linux RHEL 4.0, 5.0, 64-bit - Solaris SPARC 9.0, 10.0, 64-bit - Solaris x86 10.0, 64-bit For example, you can upgrade from NOM running on Solaris SPARC 9 (64-bit) to OpsCenter server running on Solaris SPARC 10 (64-bit). Manual upgrades are supported only within a particular OS family. For example, you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from RHEL 4.0 to Solaris 10.

When you upgrade from NOM or VBR to OpsCenter server, the OpsCenter server service and the data migration process start simultaneously. Since the data migration from NOM or VBR to the OpsCenter database has started and is not complete, the purge settings in OpsCenter take default values and not the values that you configured in NOM or VBR. To use the purge settings that you configured for NOM or VBR in OpsCenter, you must restart the OpsCenter server service after the data migration is complete. Use the following procedure to restart OpsCenter server service after the data migration is complete on Windows and UNIX platforms. To restart the OpsCenter server service on Windows:

Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service.

To restart the OpsCenter server process on UNIX:

Enter the following command to stop the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/stopserver. Enter the following command to start the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/startserver.

The following Veritas Backup Reporter (VBR) and NetBackup Operations Manager (NOM) reports do not exist in OpsCenter. However, the Report Template descriptions were incorrectly added in the Symantec OpsCenter Administrators Guide.

20

About additional operational notes About NetBackup OpsCenter notes

Job Duration Historical (VBR) Protected files vs. backed up Files (VBR) Job Summary by Client for media server Type (NOM)

Symantec OpsCenter Administrators Guide describes the following as separate reports, as they were in VBR:

Tape Count Tape Count Trends by Volume Pool Tape Count Trends by Retention Level

However, in OpsCenter these three reports are merged into one report called Tape Count. Select any of the following filters from the Report On parameter to view the respective information:

The Backup Media Retention Level The Tape Type The Volume Pool Name

Descriptions for the Restore Job Summary by Job Count and Restore Job Summary by Volume Restored reports are not in the document. The Report Template descriptions are as follows:

Restore Job Summary by Job Count: This report is a graphical summary of the number of restore jobs that run for the selected time frame. Restore Job Summary by Volume Restored: This report shows the restore job count by volumes.

In the About Report Templates section, in the Report Templates tree description, OpsCenter appears twice. The correct description is as follows: This tree lists all Report Templates that are available in OpsCenter. In the About Report Templates section, Manage report options is incorrectly added as a Report Template component. In the Working with Report Templates section, the following description of the Client reports is in the document. Client reports provide details about clients such as backup status, restore job details, or summary dashboard. The Job Summary by Status report description incorrectly states the following: The area chart shows the percent of jobs that failed each day. And in OpsCenter, the Job Summary by Status report is a historical report and area chart is not available for this report.

About additional operational notes About NetBackup OpsCenter notes

21

The Vault Media Usage report description incorrectly states that the report consists of a line chart. In OpsCenter, the Vault Media Usage report is a bar chart report. You may receive an error message when you uninstall the OpsCenter server software from an OpsCenter cluster. You may receive the following error message when you uninstall the OpsCenter server software from an OpsCenter cluster:
Fatal error during installation

If you encounter this issue, use the following steps to uninstall the OpsCenter server software:

Delete the OpsCenter resource group from a cluster node. See "To delete OpsCenter resource group from the cluster node" below. After you delete the OpsCenter resource group, you must uninstall the OpsCenter server software from each node manually. See the installation chapter in the Symantec OpsCenter Administrators Guide for instructions on how to uninstall the OpsCenter server software from a cluster.

To delete OpsCenter resource group from the cluster node:

Log on to the cluster Web user interface. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer. Click the Service Groups tab in the Cluster Explorer configuration tree. Right-click the OpsCenter resource group and select Offline > All Systems. Click Yes to forcefully take the resource group offline. Right-click the OpsCenter resource group and select Delete. Click Yes to delete the OpsCenter resource group.

The following table lists the specific data types that OpsCenter collects from backup and archiving products: Symantec NetBackup PureDisk

NetBackup Data Types

Job Policy and Schedules

(6.0MP7, 6.5, 6.5.2A, 6.5.4, (10.x, 11.x, Enterprise Enterprise (6.2.x, 6.5.x, 6.5.5, 7.0) 12.x) Vault 7.5 Vault 8.0 6.6) (5.3, 5.4, 5.5)
Yes Yes Yes Yes No No No No Yes Yes Yes Yes

Backup Exec

IBM Tivoli storage manager

EMC Legato Networker (6.x, 7.3)

Yes Yes

22

About additional operational notes About NetBackup OpsCenter notes

NetBackup Data Types

Tape drive Image Error Logs Schedule Jobs Media Skipped Files Target Archive Vault Vault Store

(6.0MP7, 6.5, 6.5.2A, 6.5.4, (10.x, 11.x, Enterprise Enterprise (6.2.x, 6.5.x, 6.5.5, 7.0) 12.x) Vault 7.5 Vault 8.0 6.6) (5.3, 5.4, 5.5)
Yes Yes Yes Yes Yes No Yes No No No No No No No No No No No No No Yes No Yes No

Backup Exec

Symantec NetBackup PureDisk

IBM Tivoli storage manager

EMC Legato Networker (6.x, 7.3)

Yes No No No

Yes Yes

Yes Yes

No No

No No

No No

Yes Yes

Yes No

No No No No

No No No No

Yes Yes Yes Yes

No No Yes Yes

No No No No

No No No No

No No No No

Changes to operating system requirements for OpsCenter

Table 2-3 in the Symantec OpsCenter Administrators Guide provides incorrect information about operating system (OS) requirements for OpsCenter. The following table lists the correct OS requirements for OpsCenter: Operating system
Windows 2003 SP2 Windows 2003 R2 Windows 2008 Windows 2008 R2 Solaris 9 SPARC Solaris 10 x64

32-bit Server
Yes Yes Yes Yes No No

64-bit Server
Yes Yes Yes Yes Yes No

32-bit Agent
Yes Yes Yes Yes No No

64-bit Agent
Yes * Yes * Yes * Yes * Yes No

32-bit View 64-bit View Builder Builder

Yes Yes Yes Yes No No Yes * Yes * Yes * Yes * No No

About additional operational notes About NetBackup OpsCenter notes

23

Operating system
Solaris 10 SPARC HP Itanium 11.31 Linux Red Hat 4.0, 5.0 Linux SUSE ES 10 SP2 and 11

32-bit Server
No No No No

64-bit Server
Yes Yes Yes Yes

32-bit Agent
No No No No

64-bit Agent
Yes No No No

32-bit View 64-bit View Builder Builder

No No No No No No No No

Note: An asterisks "*" signifies the 32-bit binaries that work on 64-bit architecture. The following corrections have been incorporated in this table:

Windows 2008 R2 does not support 32-bit platforms. Hence OpsCenter components are not supported on Windows 2008 R2 32-bit platform. OpsCenter components are not supported on AIX. OpsCenter components are not supported on HP-Itanium 11.23. OpsCenter components are not supported if Windows or Linux OS is installed on IA-64 architecture. Solaris 9 is changed to Solaris 9 SPARC.

Configuring remote authentication service in OpsCenter

OpsCenter supports using Symantec Product Authentication Service (AT) remotely. When you use the Symantec Product Authentication Service remotely, you install the authentication server component on a remote computer in the network. If you use a remote AT configuration in NOM and upgrade to OpsCenter, you can configure the remote AT after upgrading to OpsCenter. Use the following procedure to use remote AT with OpsCenter.

24

About additional operational notes About NetBackup OpsCenter notes

To configure remote AT in OpsCenter

Enter the appropriate command: For Windows INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat For UNIX /opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

The authentication server parameters appear one by one. The current values of the parameters are specified in brackets. The following authentication service parameters are displayed:
Authentication service hostname The fully qualified host name (FQHN) of the server on which the authentication service server component is running. The default value is localhost if the authentication service is installed on the OpsCenter server. Authentication service port number The port number of the server on which the authentication service server component is running. The default value is 2821. Authentication service Domain The domain name of the broker. Name The default value is broker. Authentication service user name The name of the broker user that was used for initial authentication. The default value is admin. Authentication service Password The password of the broker user that was used for initial authentication. The default value is Vxadmin.

About additional operational notes About NetBackup OpsCenter notes

25

To use a remote AT configuration, enter the new values next to the respective parameter. If you do not enter a new value for a parameter, the value of the parameter does not change.
Authentication service hostname Authentication service port number Enter the FQHN of the remote server on which the authentication service server component is running. Enter the port number of the remote server on which the authentication service server component is running.

Authentication service Domain Enter the domain name of the broker. Name Authentication service user name Enter the name of the broker user that was used for initial authentication.

Authentication service Password Enter the password of the broker user that was used for initial authentication.

You must restart the OpsCenter services for these changes to be effective. Answer y to restart the OpsCenter services.

To resolve high NBSL memory consumption

The OpsCenter server software collects data from the NetBackup master servers by using NetBackup Service Layer (NBSL). If a large number of jobs exist on the master server (more than 25000 jobs approximately) and NBSL takes a long time (more than one hour) in collecting data for NetBackup jobs, then you may see the following issues:

Data collection for the Job data type fails and the following exception message is displayed in the OpsCenter console: client timeout reached This exception message can be viewed from the Last Exception Message column in the Settings > Configuration > NetBackup page of the OpsCenter console. The NBSL process may consume a lot of memory on the NetBackup master server.

To resolve any (or both) of these issues, you need to configure the scl.conf file and then restart the OpsCenter server service.

26

About additional operational notes About NetBackup OpsCenter notes

To resolve the timeout exception and high NBSL memory consumption on Windows

Navigate to the following directory on the OpsCenter server:

INSTALL_PATH\OpsCenter\server\config

2 3

Open the scl.conf file. Add (or update) the following parameter in scl.conf file: nbu.scl.agent.jobProxyTimeout=<time in 100 nanoseconds> This parameter indicates the time for which the OpsCenter server waits for NBSL to collect job data from the NetBackup master server. The default value of the nbu.scl.agent.jobProxyTimeout parameter is 36000000000 (1 hour). To resolve this issue, the value of the nbu.scl.agent.jobProxyTimeout parameter must be increased. For example, the value of the nbu.scl.agent.jobProxyTimeout parameter may be increased to 72000000000 (2 hours). Note that after you increase the value of this parameter, the data collection in OpsCenter may become slower than before.

4 5 6

Save the scl.conf file. Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service.

To resolve the timeout exception and high NBSL memory consumption on UNIX

Navigate to the following directory on the OpsCenter server:

/opt/SYMCOpsCenterServer/config

Note that it is the default location.

Open the scl.conf file.

About additional operational notes About NetBackup database agent notes

27

Add (or update) the following parameter in scl.conf file:

nbu.scl.agent.jobProxyTimeout=<time in 100 nanoseconds>

This parameter indicates the time for which the OpsCenter server waits for NBSL to collect job data from the NetBackup master server. The default value of nbu.scl.agent.jobProxyTimeout parameter is 36000000000 (one hour). To resolve this issue, the value of nbu.scl.agent.jobProxyTimeout parameter must be increased. For example, the value of nbu.scl.agent.jobProxyTimeout parameter may be increased to 72000000000 (two hours). Note that after you increase the value of this parameter, the data collection in OpsCenter may become slower than before.

4 5

Save the scl.conf file. Enter the following command to stop the OpsCenter server process:
/opt/SYMCOpsCenterServer/bin/stopserver

Enter the following command to start the OpsCenter server process:

/opt/SYMCOpsCenterServer/bin/startserver

About NetBackup database agent notes

The following topics contain the additional notes that pertain to the following database agents.

DB2 Agent with the Snapshot Client

NetBackup 7.0 does not support the ability to back up or restore multiple nodes concurrently. To back up or restore a multi-node environment, you should back up or restore each node individually. You must perform a snapshot client backup after you make any configuration changes to the database.

Lotus Notes Agent

Backup of password-protected databases is not supported. Attempting to back up a password-protected database causes the job to suspend indefinitely. The suspension occurs within the Lotus Notes server. You can avoid the suspension by not using password protection. Master initiated Lotus Notes, point-in-time restores may fail with a status 12. If the install_path of the NetBackup master server and the NetBackup client

28

About additional operational notes About NetBackup database agent notes

is different, the automatic restore of Lotus transaction log extents during the recovery of the Lotus database are not able to locate the path to the progress log and fails.

The use of exclude lists for Lotus backups on NetBackup Windows clients has been disabled.

Microsoft Exchange server agent

For a restore of the Microsoft Key Management Service or Microsoft Site Replication Service, you should remove the contents of the kmsdata or srsdata directory before initiating the restore may result in a corrupt database, even after a restore status 0. When an Exchange backup is launched from the NetBackup Client GUI and uses the Snapshot Client off-host backup capability, the progress log window does not display the usual progress messages evident when a scheduled backup is executed. The lack of progress logging does not affect the backup operation. If detailed progress is desired, use the NetBackup Administrators GUI to launch a Manual Backup operation on an Exchange policy. See the Testing Configurations Settings section in the NetBackup for Exchange System Administrators Guide for instructions regarding a manual backup operation. When you restore data in an Exchange cluster environment, one must set the destination client value to be the virtual server name. If restoring an Exchange database using a NetBackup client-only installation on a cluster, it may not be possible to change the destination client value to match the virtual server name. In that case, use a NetBackup Client GUI on a NetBackup server to change the destination client value to the virtual server name. Alternate client (off-host) backup of Exchange 2010 fails with a status 130 with NetBackup 7.0. An alternate client (off-host) backup of Exchange 2010 may fail with a status 130 error. That occurs if the Exchange management console (EMC) is not installed on the off-host client. This problem arises because the Exchange eseutil command is required on the alternate client if the EMC is not installed. For Exchange 2010, eseutil requires that the VC9 runtime DLLs be installed, and these DLLs are not automatically installed with NetBackup. From the bpfis log on the alternate client, the following error occurs.

ERR - ubsStart_eseutil():CreateProcess() failed for "C:\Program Files\Verita

You can use either of the following two solutions to address this issue:

About additional operational notes About NetBackup database agent notes

29

Install the Exchange management console on the alternate client. That prevents the use of eseutil for performing the Exchange consistency checks. That would be the preferred solution for this problem. Install the VC9 runtime DLLs. You can download these DLLs from the following Microsoft x64 VC9 download page.
ht:w.irsf.o/onod/eal.sxfmli=DA11ED-20B0-AD5816dslyn=n tpwwmcootcmdwlasdtisap?aiydB267-2643-899874CB&ipaige

In the NetBackup for Exchange Administrator's Guide, the instructions for "Configuring the NetBackup service account (Exchange 2010)" contain unnecessary steps. You do not need to perform steps 6-13. Exchange 2010 uses the Role-based access control (RBAC) User Editor.

SAP Agent

MaxDB backups fail if the pipe has Japanese or Chinese name. MaxDB backups do not work if the RUNDIRECTORY parameter of the MaxDB database has spaces in the path. The bsi.env configuration file and the backup history file(dbm.ebf), along with the Data volumes and log volumes, are stored in the RUNDIRECTORY. If the RUNDIRECTORY has spaces, then backup of the history file( dbm.ebf) fails.

SharePoint Agent
Redirected restores of the SharePoint configuration database, document library Stores, and Single-Sign-On database are not supported. These databases can only be restored to their original location. Also, attempting to restore a SharePoint configuration database to a different name than what is currently configured in the farm causes the restore to fail. (Note, that names are case sensitive.)

VxBSA Agent
Encryption can fail on VxBSA database agents on Windows platforms. An issue exists that causes bpfilter to stop as soon as it is initiated on Windows after the Windows compiler is upgraded. The result if this issue causes all VxBSA database agents to fail when encryption is enabled. The Windows file system agent does not use bpfilter so it is not affected in this scenario. A fix will be available in an EEB that you can receive from Symantec Technical Support as soon as it is available.

30

About additional operational notes About NetBackup Snapshot Client

About NetBackup Snapshot Client

The following items are additional NetBackup Snapshot Client issues that were found in the NetBackup 7.0 release:

For Instant Recovery backups on Solaris clients that use the NAS_Snapshot method with no SnapVault storage unit configured, backups may appear to succeed. However, those backups are immediately expired and unavailable for recovery operations when any primary volume in the backup selection list is mounted by NFS Version 4. To work around this issue, re-mount the primary volumes and specify the NFS mount option, -o vers=3. The Snapshot Client file system mapping does not work correctly on 64-bit AIX platforms. On these platforms FlashBackup policy backups, and Standard snapshot backups that employ the NetBackup media server off-host method, cause the bpbkar process to terminate abnormally and the backup fails. For Linux and AIX client data that was configured in VxVM volumes on supported EMC or Hitachi disk arrays, when the TimeFinder snapshot method is used on EMC or the ShadowImage method on Hitachi the VxVM names for the disks that underlay the volumes must not use the enclosure-based naming scheme. Use of enclosure-based naming causes the backup to fail. Instead, use the older VxVM disk naming scheme (called hdisk#naming format on AIX and old format or OS-native naming format on Linux). Use the vxdiskadm utility to change the disk naming scheme. The VxVM, FlashSnap, and VVR snapshot methods do not support VxVM volume sets when used with the Instant Recovery feature. The backup fails and the following message appears in the client's bpfis log:
<32> onlfi_freeze_fim_fs: FTL - pfi_get_fmr_att: FastResync not enabled for volume: fs_vset

FlashBackup support for Solaris 9 and 10 is limited.FlashBackup support for the VxFS file system is limited. FlashBackup supports the backup of extended attributes for the VxFS file system; however, extended attributes cannot be restored by means of SFR. Extended attributes can be restored from FlashBackup images only by raw partition restore. Solstice Disk Suite is not supported. Snapshot Client snapshot methods and off-host backup methods perform mapping of the underlying file system and volume structure. This mapping has been verified for the I/O system components that are listed in the NetBackup Snapshot Client compatibility list.

About additional operational notes About VMware notes

31

The use of other components in the I/O system, such as other volume managers or storage replicators, may result in an unreliable backup. Such configurations are not supported. The NetBackup 7.x Snapshot Client compatibility list is available from the following:
http://entsupport.symantec.com/docs/337052

The NetBackup media server off-host backup method does not support clients that use client deduplication. If the client is enabled for deduplication, you must select Disable client-side deduplication on the policy Attributes tab.

About VMware notes

The following items describe the additional issues that were found in NetBackup 7.0:

The NetBackup Java (UNIX) Backup, Archive, and Restore interface becomes unresponsive when you restore a virtual machine to an alternate location. When restoring a virtual machine that was backed up directly from its ESX server (not through a vCenter server), the NetBackup Java interface may hang when you attempt to restore the virtual machine to a location other than its original location. As a workaround, you can use the Windows Backup, Archive, and Restore interface instead of the Java interface. The problem occurs in the following case:

NetBackup credentials are entered for a standalone ESX server (not for a vCenter server). A virtual machine on the standalone ESX server is backed up by a policy that is configured with the "Full VM backup" type or the "Mapped full VM backup" type. attempt to use the NetBackup Java (UNIX) Backup, Archive, and Restore interface to restore the virtual machine to a different location.

If a virtual machine backup uses VCB and the policy is configured with the Mapped full VM backup option, the backup fails if the virtual machine contains an IDE disk. To use the Mapped full VM backup option with VCB, you must reconfigure the virtual machine so that it does not contain IDE disks. For descriptions of other backup options, see the "Configuration parameters for VMware" section of the NetBackup for VMware Administrator's Guide, for NetBackup 7.0.

32

About additional operational notes About VMware notes