+ All Categories
Home > Documents > NB_7_0_Add_Op_Notes

NB_7_0_Add_Op_Notes

Date post: 29-Oct-2014
Category:
Upload: sandeepkumar93
View: 109 times
Download: 2 times
Share this document with a friend
Popular Tags:
32
Symantec NetBackup™ 7.0 Additional Operational Notes UNIX, Windows, and Linux NetBackup 7.0
Transcript
Page 1: NB_7_0_Add_Op_Notes

Symantec NetBackup™ 7.0Additional Operational Notes

UNIX, Windows, and Linux

NetBackup 7.0

Page 2: NB_7_0_Add_Op_Notes

Symantec NetBackup 7.0 Additional Operational NotesThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, Veritas, and NetBackup are trademarks or registeredtrademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Othernames may be trademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec 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 OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas 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 inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, 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.

Page 3: NB_7_0_Add_Op_Notes

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

Page 4: NB_7_0_Add_Op_Notes

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-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 Symantec’s Maintenance Programs, you can visit our Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:

www.symantec.com/techsupp/

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

Page 5: NB_7_0_Add_Op_Notes

■ 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 registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:

www.symantec.com/techsupp/

Customer serviceCustomer 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

Page 6: NB_7_0_Add_Op_Notes

Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

Page 7: NB_7_0_Add_Op_Notes

About additionaloperational 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 notesThe following topics contain additional information about NetBackup 7.0 thatpertains to the NetBackup 7.0 documentation set, and installations and upgrades,and general NetBackup issues.

Page 8: NB_7_0_Add_Op_Notes

About NetBackup documentation notesThe following items describe the additional known issues that were found in theNetBackup 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 NetWareclient for NetBackup7.0, to have back-level support.

■ The Key Management Service (KMS) was enhanced in NetBackup 7.0 to support20 key groups, which translates to 20 volume pools. However, the NetBackupSecurity andEncryptionGuide incorrectly states that only two key groups andtwo volume pools are supported.

■ Chapter 1 of the SymantecOpsCenterAdministrator's Guide incorrectly statesthe OpsCenter server is supported on Windows and Solaris platforms. TheOpsCenter server is supported on Windows and UNIX platforms.

■ Table 2-3 in theNetBackupReleaseNotes incorrectly states the NetBackup-Javaadministration console and the Backup, Archive, and Restore interface aresupported on the Windows 7 operating system. Only the Backup, Archive, andRestore interface is supported because NetBackup 7.0 supports only clientson Windows 7.0.

■ Some links in NetBackup Installation guides do not work.In the section, About replacing NetBackup server types not supported inNetBackup 7.0 and its subsections, the links to other documents do not workcorrectly. To avoid this problem, copy the link from the installation guide andmake sure to exclude the “.htm” extension. Then, paste the link into yourbrowser.

■ The Installation Checklist Beta PDF document was erroneously included withNetBackup 7.0 DVD image.Please disregard and delete this PDF document from your DVD media. Theinformation in this document has been updated and incorporated into theNetBackup Getting Started Guide. That guide is included in all of the mediakits. It is also available from the FTP download site and the NetBackupdocumentation Web site.

The following documents incorrectly indicate that PureDisk storage units supportGranular 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 notesAbout NetBackup general notes

8

Page 9: NB_7_0_Add_Op_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 GranularRecovery.

Table 1-1 Disk storage units that support Granular Recovery

Granular Recovery supportedDisk storage unit

YesBasicDisk

YesAdvancedDisk

NoNearStore

NoOpenStorage

NoPureDisk

NoSharedDisk

NoSnapVault

About NetBackup installation and upgrade notesThe following items describe additional NetBackup installation and upgrade knownissues.

■ If you upgrade from NetBackup 6.5.x to NetBackup 7.0 on an AIX system andthen perform a reboot, you should verify that the PBX and NetBackup serviceshave started after the reboot. If the services did not restart, the cause may bethat 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 onan IBM machine.If you encounter this issue, determine if the install_assist entry alreadyexists in the /etc/inittab file. If it does, you can comment the entry or removeit from the file and attempt to reboot again. After the reboot completes, makesure that the PBX and NetBackup services start.

■ During a Windows installation, if you encounter a fatal install error, you shouldcheck the installation logs to determine the cause of the error. If you find aReturn value of three in the install log, open a cmd window, run the followingcommand, and install NetBackup again.regsvr32 oleaut32.dll

9About additional operational notesAbout NetBackup general notes

Page 10: NB_7_0_Add_Op_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 NetBackup6.0 to 6.5 to NetBackup 7.0, you may not be able to recover the database in aclustered environment. The issue occurs because the catalog backup was donein the Sybase staging directory that was configured on the C drive. That wasthe default staging directory in NetBackup 6.0 and the upgrade process doesnot change it. Thus, after a fresh install to NetBackup is performed, the Sybasestaging directory defaults to the shared drive on the cluster, making the stagingdirectory location on a different drive.When the catalog recovery is attempted, the files in the staging directory onthe C drive are restored, however, the Sybase recovery expected the files to bein the shared drive on the cluster. To avoid this issue, edit the vxdbms.conf

file inshared drive:\Program Files\VERITAS\NetBackupDB\dataand changethe 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 theshared 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 avolume pool named CatalogBackup, a volume pool name conflict can occur.

Before the upgrade, users should do the following in the previous version ofNetBackup:

■ Create a new volume pool.

■ Move the media that is currently in the CatalogBackup volume pool intothe new volume pool.

■ Delete the CatalogBackup volume pool.

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

About additional operational notesAbout NetBackup general notes

10

Page 11: NB_7_0_Add_Op_Notes

About general NetBackup 7.0 notesThe following items describe the additional issues that were found in NetBackup7.0:

■ While restoring the Exchange database images that were imported from BackupExec, you may encounter some misleading logs, such as, Restoring Exchange

ESE object Error: 17349102. That is not an error message. However, becauseof an existing issue in the log message code this log message is printed insteadof the Exchange object name that is restored.

■ Starting with NetBackup 7.0, VSP is no longer supported. That leavesMicrosoft’s Volume Shadow Copy Services (VSS) as the only choice for an openfile backup for Windows clients. In addition, there is a binary incompatibilityin the 32-bit Windows XP version of VSS. For this reason, NetBackup does notsupport VSS on the 32-bit Windows XP operating system. Therefore, there areno supported, open file backup solutions for this platform. Symantecrecommends that you leave 32-bit Windows XP clients at the latest level ofNetBackup 6.5 and do not upgrade them to NetBackup 7.0. That enables youto use VSP to continue to support open file backup, which is still supportedon the latest NetBackup 6.5 version.This situation exists only on the 32-bit version of Windows XP. It does notapply to the 64-bit version of Windows XP. It also does not apply to any versionWindows Vista/7/2008 Server/Windows 2008 R2 Server Platforms. Except for32-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 failto protect all DFSR data. If a fix is not applied, all backups of DFSR data mustbe 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 takestoo long to respondNetBackup uses a disk array command line interface to perform an Instantrecovery 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 withNetBackup 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

11About additional operational notesAbout NetBackup general notes

Page 12: NB_7_0_Add_Op_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 periodbetween two sentences that comprise the following error message.Can’t 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 asthe 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 wouldonly run after all streaming attempts completed. Before NetBackup 6.5.2, thescripts would run after every stream.A change was made that adds a new argument to the backup_exit_notifycommand that indicates if a retry is performed. In addition, an argument wasadded to the parent_end_notify command that indicates the number of streamsthat 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 thedate, 1/1/1970 for all items.You can access the Browse dialog from the Policy Backup Selection tab, theNew Storage Unit dialog, and the Change Storage Unit dialog.

■ Synthetics may not function properly between two media servers if a firewaqlseparates the media servers. Users who want to perform a Synthetic backupacross two media servers with a firewall between them, must open a range of

About additional operational notesAbout NetBackup general notes

12

Page 13: NB_7_0_Add_Op_Notes

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

■ Checkpoint restart is not supported for restores from Backup Exec media. Therestore job may be suspended and resumed. However, a resumed restore jobrestarts at the beginning of the job, since no checkpoints for the restore areavailable. Failed restore jobs are in an "incomplete" state rather than a "done"state. Like a suspended job, the incomplete jobs may be resumed, but restartsat the beginning of the job.

■ Synthetics may not function properly between two media servers if a firewallseparates the media servers. Users who want to perform a Synthetic backupacross two media servers with a firewall between them, must open a range ofports so a port can be randomly selected during the synthetic job. Opening arange of ports to use synthetics means that the firewall is less effective.

■ Symantec recommands that you move only one volume or volume group at atime.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 logondialog 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 additionalinformation:

■ For NetBackup in a Veritas Cluster Server on UNIX or Linux, to start theVCS NetBackup cluster agent on all nodes of the NetBackup Group, use thefollowing 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 isdocumented in the “NetBackup in an HP MC/Service Guard cluster” chapteris not valid."Only a new installation of NetBackup 7.0 can be installed in a ServiceGuard cluster. If you have a previous version of NetBackup installed in thecluster, 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 NetBackup7.0 master servers on NetBackup 6.5 media servers that use NetBackup 6.5license keys for the remaining support life of 6.5.

13About additional operational notesAbout NetBackup general notes

Page 14: NB_7_0_Add_Op_Notes

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

■ SnapVault can no longer be purchased and you cannot enable it with theNetBackup 7.0 license keys.

■ To continue to use SnapVault on 7.0, you must use a NetBackup 6.5 mediaserver and your NetBackup 6.5 license keys that enable SnapVault. TheNetBackup 6.5 SKU for the NAS SnapVault Option is available for one yearafter NetBackup 7.0 is released. That enables you to purchase licenses tosupport 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 NetWareclient for NetBackup7.0, to have back-level support.In addition, the NetBackup documentation set that is on the NetBackup 7.0DVD contains the NetBackup_AdminGuide_NetWare_Client guide. That impliesthat Novel Netware packages are available with this release. That is not truebecause 7.0 server and client support has been dropped.

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

■ The NBAC security credential that is generated upon logon from theNetBackup-Java Administration Console or NetBackup Console (MFC), expires24 hours after the logon finishes. That disables further operations. To avoidthis 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 failif you attempt the backup with USE_VXSS set to REQUIRED.

■ When authorization failures occur in an NBAC-enabled configuration, theerror 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 inthis 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 notesAbout NetBackup Access Control

14

Page 15: NB_7_0_Add_Op_Notes

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

■ Several Windows NetBackup\bin\goodies scripts have not been modified toverify if NBAC credentials are needed. As such, the commands that run insidethe scripts may fail if a user does not have a credential or has an expiredcredential. Before you run a Windows .cmd script, verify that you have a validcredential 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 showsthat the NBU_Security_Admin cannot browse policies. TheNBU_Security_Admin can browse or list the policies but they cannot modifythem.

■ The Vault operator user is able to show policies.TheNetBackup 7.0 Security andEncryptionGuide in Table 4.4 page 263 showsthat the Vault_Operator cannot browse policies. The Vault_Operator canbrowse or list the policies but they cannot modify them. The Vault_Operatoris also able to access policies since it has permissions to run reports. Togenerate reports, access to the policy is required and read access is provided.

■ The Vault Operator or Security Administrator can list the policies if they usethe bppllist command and the Windows user interface (UI) but not from theJava UI.The NetBackup-Java user interface calls a trace through nbsl > nbproxy >bpdbm.

The NetBackup dblibFacade_getAllPolicyNames in nbproxy gives aPermission Denied failure. That causes the user interface to not list thepolicies. That occurs because the Readpermission is checked for Policy objectin nbproxywhich the Vault Operator or Security Administrator does not have.

The bppllist goes directly to bpdbm using the protocol Q_CLASS_NAMES thatis allowed if the user has any of the following permissions:Read on policy, Read on report, or Configure permissionBecause the Vault Operator has read permission on the report object and theSecurity Admin is able to configure permissions on the security object, thenthey can list the policies.The Windows UI uses db_getCLASSnames from dblib that also directly goesto 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.

15About additional operational notesAbout NetBackup Access Control

Page 16: NB_7_0_Add_Op_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 theclient 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 onHostProperties object. The Security Admin has only Browse and Readpermissions. Therefore the SecAdmin cannot modify RESTORE_RETRIES forthe master server.However, when the SecAdmin tries to modify RESTORE_RETRIES on themedia server and the client, NBConsole initiates the C_UPDATE_HOST_CONFIG

protocol with bprd. For the bprd protocol to go through, you must have eitherNew, Read, and Delete on HostProp or ConfigureSecurity on SecurityObj.Because SecAdmin has ConfigureSecurity on the Security object, this protocolgoes through and bprd then talks to BPDBM to complete the operation.

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

■ Manually initiating an offline backup of the NetBackup catalog can fail ifbackups are in progress. Backing up the NetBackup catalog can fail if it ismanually initiated and backups are in progress. The workaround for that is toinitiate cold backups when NetBackup activity is minimal, or schedule the coldcatalog backup to occur automatically. If catalog backups are required whenNetBackup 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 themedia servers cannot be killed from the Activity Monitor. If a vault job startsthe catalog backup on a media server, canceling the job from the ActivityMonitor does not terminate the catalog backup.

About NetBackup deduplicationSee the following Technote on the Symantec Support Web site for the additionalNetBackup deduplication notes that were found in the NetBackup 7.0 release.

About additional operational notesAbout NetBackup catalog notes

16

Page 17: NB_7_0_Add_Op_Notes

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

About NetBackup Hyper-VThe following describes any additional known issues that were found in theNetBackup 7.0 documents:

Policy validation fails for a Linux virtual machine if the NetBackup policy isconfigured with VM hostname as the Client Name Selection type.

If you select VMhostname as the Client Name Selection type in a Hyper-V policyfor a Linux virtual machine, policy validation may fail. In that case, specify adifferent Client Name Selection type in the policy (VMdisplayname or VMGUID).

About NetBackup user interface notesThe following is a list of additional known issues that relate to the NetBackupuser interfaces:

■ When you attempt to restore from a backup set that contains a very highvolume of files (more than 1 million), the Backup Archive Restore (BAR)interface can hang. If that occurs, close the BAR user interface in question toavoid excessively large log files that can lead to a disk full condition.

■ You may encounter an issue if you use the NetBackup-Java AdministrationConsole to stop the NetBackup services after you install NetBackup 7.0.Symantec recommends that you use the command-line interface to stop theNetBackup services to avoid any problems that may occur. That enables youto still use the NetBackup-Java Administration Console to administerNetBackup.

■ If you silently install NetBackup 7.0 on a Windows 2008 R2 server core platformand open the NetBackup Administration Console, the user interface appears.However, an issue exists that causes some of the functionality to not workcorrectly. Symantec recommends that you use one of the following user optionsto perform an operation that you would have performed on the NetBackupAdministration Console:

■ The NetBackup Remote Administration console

■ The NetBackup-Java Administration console

■ The command line interface

17About additional operational notesAbout NetBackup Hyper-V

Page 18: NB_7_0_Add_Op_Notes

About NetBackup OpsCenter notesThe following items are additional NetBackup OpsCenter notes that were foundin the NetBackup 7.0 release:

■ TheSymantecOpsCenterAdministrator'sGuide incorrectly states the OpsCenterserver is supported on AIX platforms. For this release of NetBackup, theOpsCenter server is not supported on AIX platforms.

■ Chapter 1 of the SymantecOpsCenterAdministrator's Guide incorrectly statesthe OpsCenter server is supported on Windows and Solaris platforms. TheOpsCenter server is supported on Windows and UNIX platforms.

■ Table 3-2, named "Processes used by OpsCenter on UNIX" in the SymantecOpsCenter Administrator's Guide lists an incorrect process for the SymantecOpsCenter database server . The following process depicts Symantec OpsCenterdatabase 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 mentionthe 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 followinglocation: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 isINSTALL_PATH\OpsCenter\server\db\WIN64.

■ Custom chargeback reports that you have created in VBR are not migrated toOpsCenter after an upgrade.

■ In OpsCenter, the Job Count report does not include the jobs that were collectedduring 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 onthe OpsCenter report and the corresponding VBR report.

■ You can upgrade from NetBackup Operations Manager (NOM) or Veritas BackupReporter (VBR) to OpsCenter server software on a different UNIX system. Toupgrade on a different UNIX system, use the Backup.sh script to back up yourdata on the NOM or the VBR server. Then copy the data to the OpsCenterserver. The Backup.sh script is located in the Server directory of the OpsCenterDVD.

About additional operational notesAbout NetBackup OpsCenter notes

18

Page 19: NB_7_0_Add_Op_Notes

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

■ Manual upgrade from VBR to OpsCenter server is supported on Solarisplatforms. For example, you can upgrade from VBR running on Solaris 8to OpsCenter server running on Solaris 10.

■ Manual upgrade from NOM to OpsCenter server is supported from specificNOM 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-bitFor 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. Forexample, you can upgrade from Solaris 8 to Solaris 10 but you cannotupgrade from RHEL 4.0 to Solaris 10.

■ When you upgrade from NOM or VBR to OpsCenter server, the OpsCenterserver service and the data migration process start simultaneously. Since thedata migration from NOM or VBR to the OpsCenter database has started andis not complete, the purge settings in OpsCenter take default values and notthe 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 iscomplete. Use the following procedure to restart OpsCenter server serviceafter 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 theSymantec OpsCenter Server Service.

■ Select Control Panel > Administrative Tools > Services and start theSymantec 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 OperationsManager (NOM) reports do not exist in OpsCenter. However, the ReportTemplate descriptions were incorrectly added in the Symantec OpsCenterAdministrator’s Guide.

19About additional operational notesAbout NetBackup OpsCenter notes

Page 20: NB_7_0_Add_Op_Notes

■ Job Duration – Historical (VBR)

■ Protected files vs. backed up Files (VBR)

■ Job Summary by Client for media server Type (NOM)

■ Symantec OpsCenter Administrator’s Guide describes the following as separatereports, 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 calledTape Count. Select any of the following filters from the Report On parameterto 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 JobSummary by Volume Restored reports are not in the document. The ReportTemplate descriptions are as follows:

■ Restore Job Summary by Job Count:This report is a graphical summary of the number of restore jobs that runfor 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 treedescription, 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 incorrectlyadded as a Report Template component.

■ In the Working with Report Templates section, the following description ofthe Client reports is in the document.Client reports provide details about clients such as backup status, restore jobdetails, 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 notavailable for this report.

About additional operational notesAbout NetBackup OpsCenter notes

20

Page 21: NB_7_0_Add_Op_Notes

■ The Vault Media Usage report description incorrectly states that the reportconsists of a line chart. In OpsCenter, the Vault Media Usage report is a barchart report.

■ You may receive an error message when you uninstall the OpsCenter serversoftware from an OpsCenter cluster.You may receive the following error message when you uninstall the OpsCenterserver software from an OpsCenter cluster:Fatal error during installation

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

■ Delete the OpsCenter resource group from a cluster node. See "To deleteOpsCenter resource group from the cluster node" below.

■ After you delete the OpsCenter resource group, you must uninstall theOpsCenter server software from each node manually. See the installationchapter in the Symantec OpsCenter Administrator’s Guide for instructionson 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 Viewfrom 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 > AllSystems.

■ 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 frombackup and archiving products:

EMCLegato

Networker

(6.x, 7.3)

IBM Tivolistoragemanager

(5.3, 5.4, 5.5)

SymantecNetBackupPureDisk

(6.2.x, 6.5.x,6.6)

EnterpriseVault 8.0

EnterpriseVault 7.5

BackupExec

(10.x, 11.x,12.x)

NetBackup

(6.0MP7, 6.5,6.5.2A, 6.5.4,6.5.5, 7.0)

DataTypes

YesYesYesNoNoYesYesJob

YesYesYesNoNoYesYesPolicy andSchedules

21About additional operational notesAbout NetBackup OpsCenter notes

Page 22: NB_7_0_Add_Op_Notes

EMCLegato

Networker

(6.x, 7.3)

IBM Tivolistoragemanager

(5.3, 5.4, 5.5)

SymantecNetBackupPureDisk

(6.2.x, 6.5.x,6.6)

EnterpriseVault 8.0

EnterpriseVault 7.5

BackupExec

(10.x, 11.x,12.x)

NetBackup

(6.0MP7, 6.5,6.5.2A, 6.5.4,6.5.5, 7.0)

DataTypes

YesYesNoNoNoYesYesTape drive

NoNoNoNoNoNoYesImage

NoYesNoNoNoYesYesError Logs

NoNoNoNoNoNoYesScheduleJobs

YesYesNoNoNoYesYesMedia

NoYesNoNoNoYesYesSkippedFiles

NoNoNoNoYesNoNoTarget

NoNoNoNoYesNoNoArchive

NoNoNoYesYesNoNoVault

NoNoNoYesYesNoNoVault Store

Changes to operating system requirements for OpsCenterTable 2-3 in the Symantec OpsCenter Administrator’s Guide provides incorrectinformation about operating system (OS) requirements for OpsCenter. Thefollowing table lists the correct OS requirements for OpsCenter:

64-bit ViewBuilder

32-bit ViewBuilder

64-bitAgent

32-bitAgent

64-bitServer

32-bitServer

Operating system

Yes *YesYes *YesYesYesWindows 2003 SP2

Yes *YesYes *YesYesYesWindows 2003 R2

Yes *YesYes *YesYesYesWindows 2008

Yes *YesYes *YesYesYesWindows 2008 R2

NoNoYesNoYesNoSolaris 9 SPARC

NoNoNoNoNoNoSolaris 10 x64

About additional operational notesAbout NetBackup OpsCenter notes

22

Page 23: NB_7_0_Add_Op_Notes

64-bit ViewBuilder

32-bit ViewBuilder

64-bitAgent

32-bitAgent

64-bitServer

32-bitServer

Operating system

NoNoYesNoYesNoSolaris 10 SPARC

NoNoNoNoYesNoHP Itanium 11.31

NoNoNoNoYesNoLinux Red Hat 4.0, 5.0

NoNoNoNoYesNoLinux SUSE ES 10 SP2 and 11

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 OpsCentercomponents 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 installedon IA-64 architecture.

■ Solaris 9 is changed to Solaris 9 SPARC.

Configuring remote authentication service in OpsCenterOpsCenter supports using Symantec Product Authentication Service (AT) remotely.When you use the Symantec Product Authentication Service remotely, you installthe authentication server component on a remote computer in the network.

If you use a remote AT configuration in NOM and upgrade to OpsCenter, you canconfigure the remote AT after upgrading to OpsCenter.

Use the following procedure to use remote AT with OpsCenter.

23About additional operational notesAbout NetBackup OpsCenter notes

Page 24: NB_7_0_Add_Op_Notes

To configure remote AT in OpsCenter

1 Enter the appropriate command:

For Windows

INSTALL_PATH\OpsCenter\server\bin\changeVxATProperties.bat

For UNIX

/opt/SYMCOpsCenterServer/bin/changeVxATProperties.sh

2 The authentication server parameters appear one by one. The current valuesof the parameters are specified in brackets.

The following authentication service parameters are displayed:

The fully qualified host name (FQHN) of the serveron which the authentication service servercomponent is running.

The default value is localhost if the authenticationservice is installed on the OpsCenter server.

Authentication service hostname

The port number of the server on which theauthentication service server component isrunning.

The default value is 2821.

Authentication service portnumber

The domain name of the broker.

The default value is broker.

Authentication service DomainName

The name of the broker user that was used forinitial authentication.

The default value is admin.

Authentication service username

The password of the broker user that was used forinitial authentication.

The default value is Vxadmin.

Authentication service Password

About additional operational notesAbout NetBackup OpsCenter notes

24

Page 25: NB_7_0_Add_Op_Notes

3 To use a remote AT configuration, enter the new values next to the respectiveparameter. If you do not enter a new value for a parameter, the value of theparameter does not change.

Enter the FQHN of the remote server on which theauthentication service server component is running.

Authentication servicehostname

Enter the port number of the remote server onwhich the authentication service server componentis running.

Authentication service portnumber

Enter the domain name of the broker.Authentication service DomainName

Enter the name of the broker user that was used forinitial authentication.

Authentication service username

Enter the password of the broker user that was usedfor initial authentication.

Authentication service Password

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

Answer y to restart the OpsCenter services.

To resolve high NBSL memory consumptionThe OpsCenter server software collects data from the NetBackup master serversby using NetBackup Service Layer (NBSL).

If a large number of jobs exist on the master server (more than 25000 jobsapproximately) and NBSL takes a long time (more than one hour) in collectingdata for NetBackup jobs, then you may see the following issues:

■ Data collection for the Job data type fails and the following exception messageis displayed in the OpsCenter console:client timeout reachedThis exception message can be viewed from the Last Exception Messagecolumn in the Settings > Configuration > NetBackup page of the OpsCenterconsole.

■ The NBSL process may consume a lot of memory on the NetBackup masterserver.

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

25About additional operational notesAbout NetBackup OpsCenter notes

Page 26: NB_7_0_Add_Op_Notes

To resolve the timeout exception and highNBSLmemory consumption onWindows

1 Navigate to the following directory on the OpsCenter server:

INSTALL_PATH\OpsCenter\server\config

2 Open the scl.conf file.

3 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 forNBSL to collect job data from the NetBackup master server. The default valueof the nbu.scl.agent.jobProxyTimeout parameter is 36000000000 (1 hour).

To resolve this issue, the value of thenbu.scl.agent.jobProxyTimeoutparametermust be increased. For example, the value of thenbu.scl.agent.jobProxyTimeout parameter may be increased to 72000000000(2 hours).

Note that after you increase the value of this parameter, the data collectionin OpsCenter may become slower than before.

4 Save the scl.conf file.

5 Select Control Panel > Administrative Tools > Services and stop theSymantec OpsCenter Server Service.

6 Select Control Panel > Administrative Tools > Services and start theSymantec OpsCenter Server Service.

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.

2 Open the scl.conf file.

About additional operational notesAbout NetBackup OpsCenter notes

26

Page 27: NB_7_0_Add_Op_Notes

3 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 forNBSL to collect job data from the NetBackup master server. The default valueof nbu.scl.agent.jobProxyTimeout parameter is 36000000000 (one hour).

To resolve this issue, the value of nbu.scl.agent.jobProxyTimeout parametermust be increased. For example, the value of nbu.scl.agent.jobProxyTimeoutparameter may be increased to 72000000000 (two hours).

Note that after you increase the value of this parameter, the data collectionin OpsCenter may become slower than before.

4 Save the scl.conf file.

5 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 notesThe following topics contain the additional notes that pertain to the followingdatabase 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 shouldback up or restore each node individually.

■ You must perform a snapshot client backup after you make any configurationchanges 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. Thesuspension occurs within the Lotus Notes server. You can avoid the suspensionby 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

27About additional operational notesAbout NetBackup database agent notes

Page 28: NB_7_0_Add_Op_Notes

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

■ The use of exclude lists for Lotus backups on NetBackup Windows clients hasbeen 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 srsdatadirectory before initiating the restore may result in a corrupt database, evenafter a restore status 0.

■ When an Exchange backup is launched from the NetBackup Client GUI anduses the Snapshot Client off-host backup capability, the progress log windowdoes not display the usual progress messages evident when a scheduled backupis executed. The lack of progress logging does not affect the backup operation.If detailed progress is desired, use the NetBackup Administrator’s GUI tolaunch a Manual Backup operation on an Exchange policy. See the TestingConfigurations Settings section in the NetBackup for Exchange SystemAdministrator’s Guide for instructions regarding a manual backup operation.

■ When you restore data in an Exchange cluster environment, one must set thedestination client value to be the virtual server name. If restoring an Exchangedatabase using a NetBackup client-only installation on a cluster, it may notbe possible to change the destination client value to match the virtual servername. In that case, use a NetBackup Client GUI on a NetBackup server to changethe destination client value to the virtual server name.

■ Alternate client (off-host) backup of Exchange 2010 fails with a status 130with NetBackup 7.0.An alternate client (off-host) backup of Exchange 2010 may fail with a status130 error. That occurs if the Exchange management console (EMC) is notinstalled on the off-host client. This problem arises because the Exchangeeseutil 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\Veritas\NetBackup\temp\eseutil.exe" /ml "\\?\GlobalRoot\Device\HarddiskDmVolumes\mbdg_89d6aa17\SnapV4B3C30C0013C\db\Mailbox\Mailbox Database 1006745976\E00tmp.log" - 0x36b1

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

About additional operational notesAbout NetBackup database agent notes

28

Page 29: NB_7_0_Add_Op_Notes

■ Install the Exchange management console on the alternate client. Thatprevents the use of eseutil for performing the Exchange consistencychecks. That would be the preferred solution for this problem.

■ Install the VC9 runtime DLLs. You can download these DLLs from thefollowing Microsoft x64 VC9 download page.http:www.microsoft.com/downloads/details.aspx?familyid=BD2A6171-E2D6-4230-B809-9A8D7548C1B6&displaying=en

■ In the NetBackup for Exchange Administrator's Guide, the instructions for"Configuring the NetBackup service account (Exchange 2010)" containunnecessary steps. You do not need to perform steps 6-13. Exchange 2010 usesthe 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 MaxDBdatabase has spaces in the path. The bsi.env configuration file and the backuphistory file(dbm.ebf), along with the Data volumes and log volumes, are storedin the RUNDIRECTORY. If the RUNDIRECTORY has spaces, then backup ofthe history file( dbm.ebf) fails.

SharePoint AgentRedirected restores of the SharePoint configuration database, document libraryStores, and Single-Sign-On database are not supported. These databases can onlybe restored to their original location. Also, attempting to restore a SharePointconfiguration database to a different name than what is currently configured inthe farm causes the restore to fail. (Note, that names are case sensitive.)

VxBSA AgentEncryption can fail on VxBSA database agents on Windows platforms.

An issue exists that causes bpfilter to stop as soon as it is initiated on Windowsafter the Windows compiler is upgraded. The result if this issue causes all VxBSAdatabase agents to fail when encryption is enabled. The Windows file system agentdoes 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 TechnicalSupport as soon as it is available.

29About additional operational notesAbout NetBackup database agent notes

Page 30: NB_7_0_Add_Op_Notes

About NetBackup Snapshot ClientThe following items are additional NetBackup Snapshot Client issues that werefound in the NetBackup 7.0 release:

■ For Instant Recovery backups on Solaris clients that use the NAS_Snapshotmethod with no SnapVault storage unit configured, backups may appear tosucceed. However, those backups are immediately expired and unavailable forrecovery operations when any primary volume in the backup selection list ismounted by NFS Version 4.To work around this issue, re-mount the primary volumes and specify the NFSmount option, -o vers=3.

■ The Snapshot Client file system mapping does not work correctly on 64-bitAIX platforms. On these platforms FlashBackup policy backups, and Standardsnapshot 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 onsupported EMC or Hitachi disk arrays, when the TimeFinder snapshot methodis used on EMC or the ShadowImage method on Hitachi the VxVM names forthe disks that underlay the volumes must not use the enclosure-based namingscheme. Use of enclosure-based naming causes the backup to fail.Instead, use the older VxVM disk naming scheme (called hdisk#naming formaton AIX and old format or OS-native naming format on Linux). Use thevxdiskadm utility to change the disk naming scheme.

■ The VxVM, FlashSnap, and VVR snapshot methods do not support VxVMvolume sets when used with the Instant Recovery feature. The backup failsand 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 forthe VxFS file system is limited. FlashBackup supports the backup of extendedattributes for the VxFS file system; however, extended attributes cannot berestored by means of SFR. Extended attributes can be restored fromFlashBackup images only by raw partition restore.

■ Solstice Disk Suite is not supported.Snapshot Client snapshot methods and off-host backup methods performmapping of the underlying file system and volume structure. This mappinghas been verified for the I/O system components that are listed in theNetBackup Snapshot Client compatibility list.

About additional operational notesAbout NetBackup Snapshot Client

30

Page 31: NB_7_0_Add_Op_Notes

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

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

About VMware notesThe following items describe the additional issues that were found in NetBackup7.0:

■ The NetBackup Java (UNIX) Backup, Archive, and Restore interface becomesunresponsive when you restore a virtual machine to an alternate location.When restoring a virtual machine that was backed up directly from its ESXserver (not through a vCenter server), the NetBackup Java interface may hangwhen you attempt to restore the virtual machine to a location other than itsoriginal 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 avCenter server).

■ A virtual machine on the standalone ESX server is backed up by a policythat is configured with the "Full VM backup" type or the "Mapped full VMbackup" type.

■ attempt to use the NetBackup Java (UNIX) Backup, Archive, and Restoreinterface to restore the virtual machine to a different location.

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

31About additional operational notesAbout VMware notes

Page 32: NB_7_0_Add_Op_Notes

About additional operational notesAbout VMware notes

32


Recommended