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

symantec. When you contact Technical Support. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion.Technical Support Symantec Technical Support maintains support centers globally.com/techsupp/ Before contacting Technical Support. you should be at the computer on which the problem occurred. please have the following information available: ■ ■ ■ ■ Product release level Hardware information Available memory.symantec. and NIC information Operating system . Symantec’s 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. the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. 7 days a week Advanced features. you can visit our Web site at the following URL: www. Technical Support’s 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. make sure you have satisfied the system requirements that are listed in your product documentation.com/techsupp/ Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL: www. including Account Management Services ■ ■ ■ ■ For information about Symantec’s Maintenance Programs. disk space. Also. For example. in case it is necessary to replicate the problem.

language availability.com/techsupp/ Customer service Customer service information is available at the following URL: www. 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.com/techsupp/ Customer Service is available to assist with the following types of issues: ■ ■ ■ ■ ■ ■ ■ ■ ■ Questions regarding product licensing or serialization Product registration updates. access our technical support Web page at the following URL: www.symantec. such as address or name changes General product information (features. 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 .symantec.■ ■ ■ ■ Version and patch level Network topology Router.

and global insight. .com Select your country or language from the site index.com semea@symantec.symantec. design. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks. security education. Educational Services provide a full array of technical training. Consulting Services Educational Services To access more information about Enterprise services. and countermeasures to prevent attacks before they occur.Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement. and awareness communication programs. please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan Europe. comprehensive threat analysis. ensuring rapid response to real threats. expertise. please visit our Web site at the following URL: www. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. which enable you to manage your business risks proactively. Middle-East. security certification. and management capabilities. and Africa North America and Latin America customercare_apac@symantec. implementation. monitoring. Managed Security Services These services remove the burden of managing and monitoring security devices and events.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.

and installations and upgrades.0 documentation set.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. . and general NetBackup issues.0 that pertains to the NetBackup 7.

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

if you encounter a fatal install error. If you find a Return value of three in the install log. and install NetBackup again. If you encounter this issue. open a cmd window. the cause may be that the entry. you should check the installation logs to determine the cause of the error. ■ If you upgrade from NetBackup 6.dll ■ .0 Administrator's Guide.0 for Microsoft SharePoint Server Administrator's Guide NetBackup 7. you should verify that the PBX and NetBackup services have started after the reboot. 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.5. determine if the install_assist entry already exists in the /etc/inittab file. If the services did not restart. run the following command.0 on an AIX system and then perform a reboot.0 for Microsoft Exchange Server Administrator's Guide NetBackup 7. During a Windows installation. you can comment the entry or remove it from the file and attempt to reboot again. If it does.x to NetBackup 7. This entry exists if you encountered a minor issue while you installed AIX on an IBM machine. Volume I The following table indicates the disk storage units that support Granular Recovery. regsvr32 oleaut32.About additional operational notes About NetBackup general notes 9 ■ ■ ■ NetBackup 7. install_assist entry already exists in the /etc/inittab file. make sure that the PBX and NetBackup services start. After the reboot completes.

0 to 6. 04-07-2008. setRegistryValues. the files in the staging directory on the C drive are restored. Move the media that is currently in the CatalogBackup volume pool into the new volume pool.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. ■ If you upgrade from a previous version of NetBackup and currently have a volume pool named CatalogBackup. after a fresh install to NetBackup is performed. the Sybase staging directory defaults to the shared drive on the cluster.5 to NetBackup 7. users should do the following in the previous version of NetBackup: ■ ■ Create a new volume pool..14:32:36 : Action start 14:32:36: setRegistryValues. the Sybase recovery expected the files to be in the shared drive on the cluster. The issue occurs because the catalog backup was done in the Sybase staging directory that was configured on the C drive. To avoid this issue. When the catalog recovery is attempted. Thus. making the staging directory location on a different drive. Before the upgrade. That was the default staging directory in NetBackup 6.10 About additional operational notes About NetBackup general notes The following is a sample message from the install logs.B2D5B6C9_4698_42F7_AC9D_955789A69556. VXDBMS_NB_STAGING = C:\Program Files\VERITAS\NetBackupDB\staging After the restore is done. ■ The installation portion of the upgrade process creates a new default volume pool titled CatalogBackup. 04-07-2008. . Return value 3. This final step means you will not encounter this issue in the future. perform a catalog backup that you can use going forward.B2D5B6C9_4698_42F7_AC9D_955789A69556.0 and the upgrade process does not change it.14:32:36 : Action ended 14:32:36: setRegistryValues. you may not be able to recover the database in a clustered environment.B2D5B6C9_4698_42F7_AC9D_955789A69556. Delete the CatalogBackup volume pool.0. Then.. a volume pool name conflict can occur. edit the vxdbms. ■ If you attempt to restore a database catalog after you upgrade from NetBackup 6. however. you should edit the file AGAIN and put back the shared drive.

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

Can’t move assigned media. 1/1/1970 for all items. however. In addition. The exit notify scripts would only run after all streaming attempts completed. ■ ■ ■ ■ ■ The exit-notify scripts did not work properly. You can access the Browse dialog from the Policy Backup Selection tab. select the New Pool radio button. In the new pool field. This field should display the correct date. and the Change Storage Unit dialog. an argument was added to the parent_end_notify command that indicates the number of streams that were started. In the Change Volume dialog. the New Storage Unit dialog. it currently displays the date.2. Status 91 This error message appears after you perform the following steps: ■ In Media node. A change was made that adds a new argument to the backup_exit_notify command that indicates if a retry is performed. must open a range of ■ ■ . right-click on the Assigned Media that has NetBackup as the Volume Pool.5. Click OK. Before NetBackup 6. the scripts would run after every stream. 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. An incorrect data time value is shown in the Date column of the Browse dialog. Select Change.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. The error message with the erroneous character can appear. select any volume pool other than NetBackup.

5. . the incomplete jobs may be resumed.0 can be installed in a Service Guard cluster. Like a suspended job. Opening a range of ports to use synthetics means that the firewall is less effective. it continues to be a supported option with NetBackup 7. If you have a previous version of NetBackup installed in the cluster.0 environments.5 license keys for the remaining support life of 6. See. ■ Checkpoint restart is not supported for restores from Backup Exec media.About additional operational notes About NetBackup general notes 13 ports so a port can be randomly selected during the synthetic job.0. Synthetics may not function properly between two media servers if a firewall separates the media servers. Thus. However. it cannot be upgraded to version 7. The following items pertain to the NetBackup high availability feature. "Only a new installation of NetBackup 7. but restarts at the beginning of the job. since no checkpoints for the restore are available. However. Symantec recommands that you move only one volume or volume group at a time.5 media servers that use NetBackup 6. must open a range of ports so a port can be randomly selected during the synthetic job. the following limitation that is documented in the “NetBackup in an HP MC/Service Guard cluster” chapter is not valid. Opening a range of ports to use synthetics means that the firewall is less effective. The restore job may be suspended and resumed. Failed restore jobs are in an "incomplete" state rather than a "done" state. Users who want to perform a Synthetic backup across two media servers with a firewall between them. a resumed restore job restarts at the beginning of the job.0 master servers on NetBackup 6. the NetBackup High Availability Administrator's Guide for additional information: ■ ■ ■ ■ For NetBackup in a Veritas Cluster Server on UNIX or Linux. 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. 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." Additional End-of-life notes ■ The NAS SnapVault Option is not offered for sale with new NetBackup 7.

expires 24 hours after the logon finishes. To continue to use SnapVault on 7. the error message(s) returned to the user may not indicate an authorization failure. use the VxSS client interface (CLI) or the Veritas Security Services (VxSS Java user interface to increase the default expiration time. Per-policy access control is not implemented in the NetBackup.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. The NetBackup 6. That enables you to purchase licenses to support additional capacity.0 license keys. When you add someone who is not an administrator to the NBU_Admin group. ■ ■ For NetBackup 7.0. you must use a NetBackup 6. The use of NetBackup database agents with NBAC was not implemented in this NetBackup release.5 NetWare client for NetBackup7. 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. catalog backup can fail if you attempt the backup with USE_VXSS set to REQUIRED. When authorization failures occur in an NBAC-enabled configuration.0. support has been dropped for Novell NetWare client. 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). To avoid this issue.0 server and client support has been dropped. That implies that Novel Netware packages are available with this release. That disables further operations.5 SKU for the NAS SnapVault Option is available for one year after NetBackup 7. /user/openv/netbackup/logs/user_ops (UNIX) install path\NetBackup\logs\user_ops (Windows) ■ ■ ■ ■ ■ .5 media server and your NetBackup 6. Because NBAC is not supported with database agents.0 is released. set the permissions of the following directory to word readable and writable. Customers who want to continue to use NetWare must install a 6.0 DVD contains the NetBackup_AdminGuide_NetWare_Client guide. In addition. the NetBackup documentation set that is on the NetBackup 7. That is not true because 7.5 license keys that enable SnapVault. to have back-level support.

The Vault_Operator is also able to access policies since it has permissions to run reports. That occurs because the Read permission is checked for Policy object in nbproxy which the Vault Operator or Security Administrator does not have. Before you run a Windows .4 page 263 shows that the Vault_Operator cannot browse policies. The NetBackup dblibFacade_getAllPolicyNames in nbproxy gives a Permission Denied failure. The Vault_Operator can browse or list the policies but they cannot modify them. The NetBackup 7. ■ . then they can list the policies. ■ Several Windows NetBackup\bin\goodies scripts have not been modified to verify if NBAC credentials are needed.4 page 263 shows that the NBU_Security_Admin cannot browse policies.0 Security and Encryption Guide in Table 4. The Windows UI uses db_getCLASSnames from dblib that also directly goes to bpdbm. access to the policy is required and read access is provided. therefore. The NetBackup-Java user interface calls a trace through nbsl > nbproxy > bpdbm. That causes the user interface to not list the policies. The NetBackup 7. The Security Admin is able to list policies. 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. policies can be listed ■ ■ ■ ■ The Security Administrator does not have access to NDMP properties. The Vault Operator is unable to expire media. To generate reports. 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. Read on report.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. The Vault Operator should NOT have permissions to expire the media. The Vault operator user is able to show policies.0 Security and Encryption Guide in Table 4. verify that you have a valid credential by performing a bpnbat -login. As such. The Security Administrator has all permissions for the host properties.cmd script. the commands that run inside the scripts may fail if a user does not have a credential or has an expired credential. The NBU_Security_Admin can browse or list the policies but they cannot modify them. 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.

0 release. The catalog backup jobs that are started with the -host option to run on the media servers cannot be killed from the Activity Monitor. However. For the bpdbm protocol to go through. ■ The following list shows the tape reports that work for the NBU_Operator: . 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. Backing up the NetBackup catalog can fail if it is manually initiated and backups are in progress. NBConsole initiates the Q_CONFIGSET protocol with bpdbm. Therefore the SecAdmin cannot modify RESTORE_RETRIES for the master server. The workaround for that is to initiate cold backups when NetBackup activity is minimal. you must have either New. or schedule the cold catalog backup to occur automatically. and Delete on HostProp or ConfigureSecurity on SecurityObj. 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.Tape Summary . canceling the job from the Activity Monitor does not terminate the catalog backup. . this protocol goes through and bprd then talks to BPDBM to complete the operation. you must have New.Tape Lists The following list shows the disk reports that work for the NBU_Operator: . If a vault job starts the catalog backup on a media server. When the SecAdmin tries to modify RESTORE_RETRIES on the master server. Because SecAdmin has ConfigureSecurity on the Security object. and Delete permission on HostProperties object. Read. ■ 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. then you should use a hot catalog backup.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. The Security Admin has only Browse and Read permissions. If catalog backups are required when NetBackup activity is high. Read.16 About additional operational notes About NetBackup catalog notes ■ The NetBackup Operator has access for Media List Report. For the bprd protocol to go through.

You may encounter an issue if you use the NetBackup-Java Administration Console to stop the NetBackup services after you install NetBackup 7. close the BAR user interface in question to avoid excessively large log files that can lead to a disk full condition. the Backup Archive Restore (BAR) interface can hang.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.About additional operational notes About NetBackup Hyper-V 17 http://entsupport. If that occurs. In that case. If you select VM hostname as the Client Name Selection type in a Hyper-V policy for a Linux virtual machine. 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 . policy validation may fail. the user interface appears.com/docs/338123 About NetBackup Hyper-V The following describes any additional known issues that were found in the NetBackup 7. 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). That enables you to still use the NetBackup-Java Administration Console to administer NetBackup.0. specify a different Client Name Selection type in the policy (VM display name or VM GUID). Symantec recommends that you use the command-line interface to stop the NetBackup services to avoid any problems that may occur. However.0 on a Windows 2008 R2 server core platform and open the NetBackup Administration Console.symantec. If you silently install NetBackup 7.

sh script to back up your data on the NOM or the VBR server. ■ Custom chargeback reports that you have created in VBR are not migrated to OpsCenter after an upgrade. Chapter 1 of the Symantec OpsCenter Administrator's Guide incorrectly states the OpsCenter server is supported on Windows and Solaris platforms. Table 3-2. Then copy the data to the OpsCenter server. The OpsCenter server is supported on Windows and UNIX platforms. To upgrade on a different UNIX system.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. These jobs are called Sparse Jobs. the OpsCenter server is not supported on AIX platforms. For this release of NetBackup. which also included Sparse Jobs.0 release: ■ The Symantec OpsCenter Administrator's Guide incorrectly states the OpsCenter server is supported on AIX platforms. named "Processes used by OpsCenter on UNIX" in the Symantec OpsCenter Administrator's Guide lists an incorrect process for the Symantec OpsCenter database server . In OpsCenter. Because of this change. 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. ■ ■ . You can upgrade from NetBackup Operations Manager (NOM) or Veritas Backup Reporter (VBR) to OpsCenter server software on a different UNIX system. That is unlike the Job Count report in VBR.sh script is located in the Server directory of the OpsCenter DVD. use the Backup. the Job Count report does not include the jobs that were collected during the image data collection. The Backup. you may notice a mismatch between the job count on the OpsCenter report and the corresponding VBR report. The location on a 64-bit system is INSTALL_PATH\OpsCenter\server\db\WIN64.

Solaris x86 10. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service. 64-bit For example. the Report Template descriptions were incorrectly added in the Symantec OpsCenter Administrator’s Guide.0.0. Manual upgrades are supported only within a particular OS family. ■ To restart the OpsCenter server process on UNIX: ■ Enter the following command to stop the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/stopserver. 64-bit . To use the purge settings that you configured for NOM or VBR in OpsCenter. For example.0. Ensure that NOM is running on the following platforms: . To restart the OpsCenter server service on Windows: ■ Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. 10. you can upgrade from NOM running on Solaris SPARC 9 (64-bit) to OpsCenter server running on Solaris SPARC 10 (64-bit). ■ ■ ■ When you upgrade from NOM or VBR to OpsCenter server. ■ ■ The following Veritas Backup Reporter (VBR) and NetBackup Operations Manager (NOM) reports do not exist in OpsCenter. 64-bit .0. 5. . For example. the purge settings in OpsCenter take default values and not the values that you configured in NOM or VBR. Since the data migration from NOM or VBR to the OpsCenter database has started and is not complete. you can upgrade from VBR running on Solaris 8 to OpsCenter server running on Solaris 10.0. However. Use the following procedure to restart OpsCenter server service after the data migration is complete on Windows and UNIX platforms. you must restart the OpsCenter server service after the data migration is complete. the OpsCenter server service and the data migration process start simultaneously.Solaris SPARC 9.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. Manual upgrade from NOM to OpsCenter server is supported from specific NOM platforms.0 to Solaris 10.Linux RHEL 4. Enter the following command to start the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/startserver. you can upgrade from Solaris 8 to Solaris 10 but you cannot upgrade from RHEL 4.

20 About additional operational notes About NetBackup OpsCenter notes ■ ■ ■ ■ Job Duration – Historical (VBR) Protected files vs. ■ ■ In the About Report Templates section. Restore Job Summary by Volume Restored: This report shows the restore job count by volumes. In the Working with Report Templates section. In the About Report Templates section. as they were in VBR: ■ ■ ■ Tape Count Tape Count Trends by Volume Pool Tape Count Trends by Retention Level However. in the Report Templates tree description. the following description of the Client reports is 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. The correct description is as follows: This tree lists all Report Templates that are available in OpsCenter. 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 Job Summary by Status report is a historical report and area chart is not available for this report. ‘Manage report options’ is incorrectly added as a Report Template component. The Job Summary by Status report description incorrectly states the following: The area chart shows the percent of jobs that failed each day. ■ ■ ■ . OpsCenter appears twice. backed up Files (VBR) Job Summary by Client for media server Type (NOM) Symantec OpsCenter Administrator’s Guide describes the following as separate reports. or summary dashboard. Client reports provide details about clients such as backup status. in OpsCenter these three reports are merged into one report called Tape Count. restore job details. And in OpsCenter.

x) Vault 7. 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. Click the Service Groups tab in the Cluster Explorer configuration tree. Enterprise Enterprise (6.5. After you delete the OpsCenter resource group. 6.x. you must uninstall the OpsCenter server software from each node manually.5.0 6. ■ ■ ■ ■ ■ 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.3) Yes Yes .3.6) (5. 6. Right-click the OpsCenter resource group and select Delete. 7. See the installation chapter in the Symantec OpsCenter Administrator’s Guide for instructions on how to uninstall the OpsCenter server software from a cluster. Right-click the selected cluster monitor panel and click Explorer View from the menu to access Cluster Explorer.5. 6. use the following steps to uninstall the OpsCenter server software: ■ Delete the OpsCenter resource group from a cluster node.4.0MP7.5 Vault 8.4.x.5.0) 12. 5. the Vault Media Usage report is a bar chart report.x.2A. 11. 7. 6.x.2. 5. Click Yes to forcefully take the resource group offline.x. See "To delete OpsCenter resource group from the cluster node" below.5) Yes Yes Yes Yes No No No No Yes Yes Yes Yes Backup Exec IBM Tivoli storage manager EMC Legato Networker (6. Click Yes to delete the OpsCenter resource group. (10. ■ To delete OpsCenter resource group from the cluster node: ■ ■ Log on to the cluster Web user interface. 6. You may receive an error message when you uninstall the OpsCenter server software from an OpsCenter cluster.5.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. Right-click the OpsCenter resource group and select Offline > All Systems.5.

5.5. 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 .x. 11.5. 7.5. 7.3. (10.0 6. Enterprise Enterprise (6. 6.4.x.5.0MP7.x.5.5 Vault 8.6) (5. 6.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 Administrator’s Guide provides incorrect information about operating system (OS) requirements for OpsCenter.x. 5. 6.5.2.2A.0) 12. 6.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.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.4.x) Vault 7. 6.x.

you can configure the remote AT after upgrading to OpsCenter. 5. OpsCenter components are not supported if Windows or Linux OS is installed on IA-64 architecture. OpsCenter components are not supported on AIX.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. Use the following procedure to use remote AT with OpsCenter. The following corrections have been incorporated in this table: ■ Windows 2008 R2 does not support 32-bit platforms. If you use a remote AT configuration in NOM and upgrade to OpsCenter.31 Linux Red Hat 4.23. ■ ■ ■ ■ Configuring remote authentication service in OpsCenter OpsCenter supports using Symantec Product Authentication Service (AT) remotely. . you install the authentication server component on a remote computer in the network.0.About additional operational notes About NetBackup OpsCenter notes 23 Operating system Solaris 10 SPARC HP Itanium 11. Solaris 9 is changed to Solaris 9 SPARC. When you use the Symantec Product Authentication Service remotely. Hence OpsCenter components are not supported on Windows 2008 R2 32-bit platform. OpsCenter components are not supported on HP-Itanium 11.

Name The default value is broker.24 About additional operational notes About NetBackup OpsCenter notes To configure remote AT in OpsCenter 1 Enter the appropriate command: For Windows INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.sh 2 The authentication server parameters appear one by one.bat For UNIX /opt/SYMCOpsCenterServer/bin/changeVxATProperties. The default value is localhost if the authentication service is installed on the OpsCenter server. The default value is 2821. The current values of the parameters are specified in brackets. Authentication service user name The name of the broker user that was used for initial authentication. 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. Authentication service Domain The domain name of the broker. 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. . Authentication service port number The port number of the server on which the authentication service server component is running.

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.About additional operational notes About NetBackup OpsCenter notes 25 3 To use a remote AT configuration.conf file and then restart the OpsCenter server service. 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 value of the parameter does not change. 4 You must restart the OpsCenter services for these changes to be effective. Authentication service Password Enter the password of the broker user that was used for initial authentication. Name Authentication service user name Enter the name of the broker user that was used for initial authentication. . you need to configure the scl. Authentication service Domain Enter the domain name of the broker. 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. The NBSL process may consume a lot of memory on the NetBackup master server. If you do not enter a new value for a parameter. To resolve high NBSL memory consumption The OpsCenter server software collects data from the NetBackup master servers by using NetBackup Service Layer (NBSL). Answer y to restart the OpsCenter services. ■ To resolve any (or both) of these issues. enter the new values next to the respective parameter.

jobProxyTimeout parameter may be increased to 72000000000 (2 hours). 4 5 6 Save the scl. To resolve this issue.jobProxyTimeout parameter must be increased.jobProxyTimeout parameter is 36000000000 (1 hour). To resolve the timeout exception and high NBSL memory consumption on UNIX 1 Navigate to the following directory on the OpsCenter server: /opt/SYMCOpsCenterServer/config Note that it is the default location.agent. Add (or update) the following parameter in scl. Select Control Panel > Administrative Tools > Services and stop the Symantec OpsCenter Server Service. .conf file.agent. the value of the nbu. 2 Open the scl. Select Control Panel > Administrative Tools > Services and start the Symantec OpsCenter Server Service.scl. the value of the nbu. the data collection in OpsCenter may become slower than before.agent.scl.26 About additional operational notes About NetBackup OpsCenter notes To resolve the timeout exception and high NBSL memory consumption on Windows 1 Navigate to the following directory on the OpsCenter server: INSTALL_PATH\OpsCenter\server\config 2 3 Open the scl.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.conf file. Note that after you increase the value of this parameter.scl.agent.conf file: nbu.conf file. For example.scl. The default value of the nbu.

Enter the following command to stop the OpsCenter server process: /opt/SYMCOpsCenterServer/bin/stopserver 6 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.agent.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. You must perform a snapshot client backup after you make any configuration changes to the database. For example. the value of nbu.agent. ■ Lotus Notes Agent ■ Backup of password-protected databases is not supported.conf file: nbu. 4 5 Save the scl.agent. To resolve this issue. the data collection in OpsCenter may become slower than before.About additional operational notes About NetBackup database agent notes 27 3 Add (or update) the following parameter in scl. You can avoid the suspension by not using password protection.scl. Attempting to back up a password-protected database causes the job to suspend indefinitely.0 does not support the ability to back up or restore multiple nodes concurrently.scl. you should back up or restore each node individually.jobProxyTimeout parameter is 36000000000 (one hour).jobProxyTimeout parameter must be increased. the value of nbu. DB2 Agent with the Snapshot Client ■ NetBackup 7. Note that after you increase the value of this parameter. If the install_path of the NetBackup master server and the NetBackup client ■ .jobProxyTimeout parameter may be increased to 72000000000 (two hours).conf file. To back up or restore a multi-node environment. The default value of nbu. The suspension occurs within the Lotus Notes server. point-in-time restores may fail with a status 12.scl.scl. Master initiated Lotus Notes.

When an Exchange backup is launched from the NetBackup Client GUI and uses the Snapshot Client off-host backup capability. Microsoft Exchange server agent ■ For a restore of the Microsoft Key Management Service or Microsoft Site Replication Service. If restoring an Exchange database using a NetBackup client-only installation on a cluster. The lack of progress logging does not affect the backup operation. In that case. Alternate client (off-host) backup of Exchange 2010 fails with a status 130 with NetBackup 7. If detailed progress is desired.28 About additional operational notes About NetBackup database agent notes is different. ■ ■ ■ ERR .ubsStart_eseutil():CreateProcess() failed for "C:\Program Files\Verita You can use either of the following two solutions to address this issue: . it may not be possible to change the destination client value to match the virtual server name. use the NetBackup Administrator’s GUI to launch a Manual Backup operation on an Exchange policy. ■ The use of exclude lists for Lotus backups on NetBackup Windows clients has been disabled. For Exchange 2010. 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. one must set the destination client value to be the virtual server name. An alternate client (off-host) backup of Exchange 2010 may fail with a status 130 error. When you restore data in an Exchange cluster environment. This problem arises because the Exchange eseutil command is required on the alternate client if the EMC is not installed. you should remove the contents of the kmsdata or srsdata directory before initiating the restore may result in a corrupt database.0. eseutil requires that the VC9 runtime DLLs be installed. That occurs if the Exchange management console (EMC) is not installed on the off-host client. the progress log window does not display the usual progress messages evident when a scheduled backup is executed. the following error occurs. From the bpfis log on the alternate client. See the Testing Configurations Settings section in the NetBackup for Exchange System Administrator’s Guide for instructions regarding a manual backup operation. even after a restore status 0. use a NetBackup Client GUI on a NetBackup server to change the destination client value to the virtual server name. and these DLLs are not automatically installed with NetBackup.

A fix will be available in an EEB that you can receive from Symantec Technical Support as soon as it is available. That would be the preferred solution for this problem. SharePoint Agent Redirected restores of the SharePoint configuration database. The result if this issue causes all VxBSA database agents to fail when encryption is enabled.sxfmli=DA11ED-20B0-AD5816dslyn=n tpwwmcootcmdwlasdtisap?aiydB267-2643-899874CB&ipaige ■ ■ In the NetBackup for Exchange Administrator's Guide.ebf). An issue exists that causes bpfilter to stop as soon as it is initiated on Windows after the Windows compiler is upgraded. . document library Stores. The Windows file system agent does not use bpfilter so it is not affected in this scenario.) VxBSA Agent Encryption can fail on VxBSA database agents on Windows platforms.ebf) fails. You do not need to perform steps 6-13. are stored in the RUNDIRECTORY. (Note. and Single-Sign-On database are not supported.irsf.env configuration file and the backup history file(dbm. then backup of the history file( dbm. ht:w. MaxDB backups do not work if the RUNDIRECTORY parameter of the MaxDB database has spaces in the path. the instructions for "Configuring the NetBackup service account (Exchange 2010)" contain unnecessary steps. The bsi.About additional operational notes About NetBackup database agent notes 29 ■ Install the Exchange management console on the alternate client. Also. along with the Data volumes and log volumes.o/onod/eal. attempting to restore a SharePoint configuration database to a different name than what is currently configured in the farm causes the restore to fail. Install the VC9 runtime DLLs. That prevents the use of eseutil for performing the Exchange consistency checks. SAP Agent ■ ■ MaxDB backups fail if the pipe has Japanese or Chinese name. that names are case sensitive. Exchange 2010 uses the Role-based access control (RBAC) User Editor. These databases can only be restored to their original location. If the RUNDIRECTORY has spaces. You can download these DLLs from the following Microsoft x64 VC9 download page.

use the older VxVM disk naming scheme (called hdisk#naming format on AIX and old format or OS-native naming format on Linux). FlashBackup supports the backup of extended attributes for the VxFS file system.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. For Linux and AIX client data that was configured in VxVM volumes on supported EMC or Hitachi disk arrays. -o vers=3. The backup fails and the following message appears in the client's bpfis log: <32> onlfi_freeze_fim_fs: FTL . To work around this issue. extended attributes cannot be restored by means of SFR. 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. This mapping has been verified for the I/O system components that are listed in the NetBackup Snapshot Client compatibility list. Use the vxdiskadm utility to change the disk naming scheme. 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. The VxVM. Extended attributes can be restored from FlashBackup images only by raw partition restore. cause the bpbkar process to terminate abnormally and the backup fails. On these platforms FlashBackup policy backups.FlashBackup support for the VxFS file system is limited.0 release: ■ For Instant Recovery backups on Solaris clients that use the NAS_Snapshot method with no SnapVault storage unit configured. Use of enclosure-based naming causes the backup to fail. re-mount the primary volumes and specify the NFS mount option. backups may appear to succeed. However. ■ . Solstice Disk Suite is not supported. and VVR snapshot methods do not support VxVM volume sets when used with the Instant Recovery feature. Snapshot Client snapshot methods and off-host backup methods perform mapping of the underlying file system and volume structure. Instead. The Snapshot Client file system mapping does not work correctly on 64-bit AIX platforms. FlashSnap. however. and Standard snapshot backups that employ the NetBackup media server off-host method.pfi_get_fmr_att: FastResync not enabled for volume: fs_vset ■ ■ ■ ■ FlashBackup support for Solaris 9 and 10 is limited.

may result in an unreliable backup. attempt to use the NetBackup Java (UNIX) Backup.x Snapshot Client compatibility list is available from the following: http://entsupport. the backup fails if the virtual machine contains an IDE disk. As a workaround. ■ ■ ■ If a virtual machine backup uses VCB and the policy is configured with the Mapped full VM backup option. About VMware notes The following items describe the additional issues that were found in NetBackup 7. and Restore interface to restore the virtual machine to a different location. and Restore interface instead of the Java interface. 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.About additional operational notes About VMware notes 31 The use of other components in the I/O system.0: ■ The NetBackup Java (UNIX) Backup. the NetBackup Java interface may hang when you attempt to restore the virtual machine to a location other than its original location. When restoring a virtual machine that was backed up directly from its ESX server (not through a vCenter server). you can use the Windows Backup. To use the Mapped full VM backup option with VCB. see the "Configuration parameters for VMware" section of the NetBackup for VMware Administrator's Guide.com/docs/337052 ■ The NetBackup media server off-host backup method does not support clients that use client deduplication. The NetBackup 7. you must reconfigure the virtual machine so that it does not contain IDE disks. and Restore interface becomes unresponsive when you restore a virtual machine to an alternate location. . such as other volume managers or storage replicators.0. Archive. for NetBackup 7. The problem occurs in the following case: ■ NetBackup credentials are entered for a standalone ESX server (not for a vCenter server). For descriptions of other backup options.symantec. you must select Disable client-side deduplication on the policy Attributes tab. If the client is enabled for deduplication. Such configurations are not supported. Archive. Archive.

32 About additional operational notes About VMware notes .