VERITAS NetBackup™ 6.

Release Notes - Additional Operational Notes
for UNIX, Windows, and Linux

September 2005

September 2005

Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. VERITAS Legal Notice Copyright © 1998 - 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and VERITAS NetBackup are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 650-527-8000 Fax 650-527-2908 Third-Party Copyrights For a list of third-party copyrights, see that Appendix in the NetBackup Release Notes for UNIX, Windows, and Linux.


NetBackup Release Notes - Additional Operational Notes for UNIX, Windows, and Linux

Chapter 1. Additional NetBackup 6.0 Operational Notes . . . . . . . . . . . . . . . . . . . . . . . 1 NetBackup General Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 NetBackup Documentation Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 NetBackup Installation and Upgrade Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 NetBackup Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Cluster Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 NetBackup Firewall and Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 NetBackup Windows Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Localization and Internationalization Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 NetBackup Port Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 NetBackup Access Control (NBAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 NetBackup Advanced Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 bpadm Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 FlashBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Network Appliance (NetApp) SnapVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Network Appliance (NetApp) NearStore Disk Storage Unit . . . . . . . . . . . . . . . . . . . . . 27 NetBackup Bare Metal Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 NetBackup Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 NetBackup Database Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 DB2 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 DB2 Agent With the Advanced Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Informix Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Lotus Notes Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


Microsoft Exchange Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 NetBackup for Exchange with Advanced Client . . . . . . . . . . . . . . . . . . . . . . . . . 32 Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 SQL Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Sybase Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 NetBackup Disk Backup Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Disk Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Inline Copy limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 NetBackup Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 General NetBackup Java Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 NetBackup-Java Backup Policy Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 NetBackup Remote Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 NetBackup Media Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Media and Device Selection (MDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 General Media Manager Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Enhanced Device Discovery and Auto Configuration . . . . . . . . . . . . . . . . . . . . . 47 Media Manager Cluster Support Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Storage Migrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 NetBackup Operations Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 NetBackup Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 NetBackup Operations Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Platforms Supported for the NOM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 NetBackup Managed Master Server Platforms Supported by NOM . . . . . . . . 53 Web Browsers Supported by NOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


Additional NetBackup 6.0 Operational Notes

Additional NetBackup 6.0 Operational Notes
This document contains other operational information pertinent to NetBackup 6.0. Some of this information describes known product limitations that are applicable to this release. For additional information about this release, you can refer to NetBackup Release Notes for UNIX, Windows, and Linux. For additional system environment information including memory requirements, refer to the NetBackup Release Impact Bulletin. You can locate this bulletin on the VERITAS support web site by searching for TechNote number 278132. Note References to UNIX also apply to Linux, unless otherwise stated.

NetBackup General Notes
1. Synthetics may not function properly between two media servers if the media servers are separated by a firewall. Users who want to perform a Synthetic backup across two media servers with a firewall between them, must open a range of ports so a port can be randomly selected during the synthetic job. Opening a range of ports to use synthetics means the firewall will be less effective. 2. VERITAS logview (vxlogview) hangs when you try to display logs from a large number of files. This situation occurs because of a file-descriptors quota limitation that exists on UNIX platforms. While attempting to view a large number of files, if you do not assign a large enough file-descriptors quota, then vxlogview hangs when it tries to acquire more descriptors. The following example demonstrates how you can determine the number of files that vxlogview is trying to display. If you are trying to display logs for product 1234 using the command, vxlogview -p 1234, you can use the same condition or query with vxlogmgr to list the files and file count. For example, use the command, vxlogmgr -s -p 1234, to list the files. To find the file-descriptors quota allocated to you, use the command, ulimit -n, to display the file-descriptor quota.


then you should increase the sem_mni and sem_msl semaphore values. Run the following commands to first determine how your current kernel parameters are set. 4. When configuring NetBackup 6. and then to change these values. Run the following two commands to change the sem_mni and sem_msl semaphore values respectively: sysconfig -r ipc sem_mni=1000 sysconfig -r ipc sem_msl=1000 Note The Sybase log is located at the following locations: /usr/openv/db/log/server. In addition. use the dxkerneltuner application to change the ipc settings.log (Windows) Note If the ipc subsystem does not support dynamic reconfiguration and you receive an error when running the sysconfig command. Run the following command to verify your system kernel parameters: sysconfig -q ipc A list of the kernel parameters will appear.0 for HP Tru64 systems.NetBackup General Notes To avoid this issue. If this is the case. If you have scripts that use the old command names and do not want to change the scripts.log (UNIX) installpath\VERITAS\NetBackupDB\log\server. you can create a symbolic link to use the old command names by performing one of the following procedures: To create a symbolic link on a UNIX platform: 2 Additional NetBackup 6.failed to allocate a SYSV semaphore This error indicates that you have an insufficient number of semaphores because you may be exceeding the number of clients and engine processes that can be run at any one time. The add_slave and add_slave_on_clients commands have been renamed to add_media_server and add_media_server_on_clients.0 Operational Notes . you can increase the file-descriptors quota using the command ulimit -n file count displayed by vxlogmgr + 10 3. the add_media_server command will be dropped in the next major release of NetBackup. you may need to adjust kernel parameters if you receive the following error: Insufficient system resources .

Additional NetBackup 6.6.4. For example. a resumed restore job will restart at the beginning of the job. but will restart at the beginning of the job.exe c. HP-UX and AIX systems in this release of NetBackup. a shared drive is configured in the NetBackup Administration Console by adding paths to that drive from multiple hosts. therefore. Checkpoint Restart is not supported for restores from Backup Exec media. however. returning error in underlying service module This message does not hinder NetBackup from functioning. Type: cd install_path/netbackup/bin b. since no checkpoints for the restore are available. Type: cd /usr/openv/netbackup/bin b.exe add_slave.exe 5.NetBackup General Notes a. Access control lists (ACLs) are supported on Solaris. you must have VxFS 3. 7. With this release of NetBackup there is no longer a way in the console to configure a drive as shared when it is only configured on a single host. Like a suspended job. Type: ln -s add_media_server add_slave To create a symbolic link on a Windows platform: a. however. Type: copy add_media_server_on_clients. When restarting NetBackup on system running Solaris 10 you may receive errors in /var/adm/messages.exe add_slave_on_client. 9. you can safely ignore it. 6.0. The restore job may be suspended and resumed.2 installed. Type: ln -s add_media_server_on_clients add_slave_on_client c. Failed restore jobs will be in the incomplete state rather than the done state. In NetBackup 6. you may encounter the following message: pam_dial_auth: terminal-device not specified by login. the incomplete jobs may be resumed. ACLs are not supported on Linux systems. 8.0 Operational Notes 3 . Type: copy add_media_server. For NetBackup to support Block-level Increment (BLI) on an AIX platform.

For example. (This parameter is called KeepAliveTime on Microsoft Windows and tcp_keepalive_interval on Solaris systems. Backup selections for VSS snapshot backups must use the same volume management software. a shared drive is configured in the NetBackup Administration Console by adding paths to that drive from multiple hosts. In NetBackup 6.0 volumes. the files to be backed up. There may be a delay in detecting of loss of connection from a NetBackup master server to a media server. however.0. Note The user should use the -h emm_server option to point the vm command at the proper host to get the correct records. For the VSS snapshot method.0 Operational Notes . You can find more information about the KeepAliveTime and other associated TCP/IP configuration parameters on Microsoft Windows in the following Microsoft Knowledge Base articles: Q140325 and Q120642 or using by man tcp on UNIX systems. 11. and are slightly larger. Enhancements have been made in NetBackup 6.x to NetBackup 6. When viewing the Files Written count for a job in the Activity Monitor.000 (two hours.0. In certain situations.) 14. this delay is actually a result of a certain TCP/IP configuration parameter that is set to 7. if a media server goes down while running a backup. these enhancements do not limit a user from viewing the old volume database records. configurable value that is greater than 15 minutes. in milliseconds) by default. it may be possible to run back-level vmquery commands on a back-level host and see the old volume database records that existed before the upgrade. there may be a delay on the master server before it detects that the media server is no longer available.000 milliseconds) or the next lowest. After upgrading from NetBackup 5. the value for Current Files Written does not include the extra directory entries (which are used during restore file browsing). Files Written count (Current. or all must not be in Storage Foundation 4.200.0 that limit the changes to the old volume database no longer in use. VERITAS recommends that you set this parameter to 15 minutes (900. While at first it may appear that there is a problem with the NetBackup master server. 13. You can check the man page on your system to identify what this parameter is called. The value displayed for Estimated Files Written does include those extra directory entries.NetBackup General Notes 10. there can be a delay on a NetBackup master server before it detects that the connection to a media server has been aborted. Previous) in Activity Monitor does not include extra directory entries used for restore file browsing. cannot be mixed: all must be in Storage Foundation 4. 12. 4 Additional NetBackup 6.0 volumes.

Also. http://support. Note Other command enhancements that were developed after the official release of the NetBackup documentation may also be included in this TechNote. 1. or provide corrections to the information in a particular document because of a change that may have occurred with the product. the following text is incorrect: 5 Additional NetBackup 6.switch. Because this is a new and important command for our NetBackup 6. 2.NetBackup General Notes NetBackup Documentation Limitations The following items either explain changes that occurred in the product that were not captured in the dcumentation before release. ensure that bpcd is running on any system that is being recovered.switch. There are a few references in the NetBackup System Administrator’s Guide for UNIX and Linux that tell the user to install VxSS from the VxSS installation CD. an update of this command has been documented in a TechNote that can be viewed from the VERITAS support web site. This note is not exactly 4. Updates and enhancements have been made to the nbemmcmd command/man page that supersedes what is documented with the release of the NetBackup 6.lis It should read as follows: The switch_list parameter must specify a file path in the following location: $ORACLE_HOME /sapbackup/. The following note in the bprecover command in the NetBackup Command documents states that bpdbm and bprd must be stopped before running the bprecover -wizard command.0 customers. The TechNote number is 278592. The following errors appear in the NetBackup for SAP System Administrator’s Guide for UNIX and Linux: ◆ On page 113.0 Operational Notes .veritas. This is misleading. the following text is incorrect: The switch_list parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/. Note Stop bpdbm and bprd before using this command.0 documentation set. 3. The note should state that these two processes should be stopped when recovering an offline backup only.lis ◆ On page 114. The documentation should tell the user to install VxSS from the ICS CD for NetBackup. Here is a link to this document.

log It should read as follows: The switch_log parameter must specify a file path in the following location: %SAPBACKUP%\sapbackup\.sem It should read as follows: The switch_sem parameter must specify a file path in the following location: 6 Additional NetBackup 6.0 Operational Notes .log ◆ On page 114. the following text is incorrect: The switch_sem parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.sem 5. the following text is incorrect: The switch_log parameter must specify a file path in the following location: %SAPDATA_HOME%\sapbackup\.switch.log It should read as follows: The switch_log parameter must specify a file path in the following location: $ORACLE_HOME/sapbackup/. the following text is incorrect: The switch_list parameter must specify a file path in the following location: %SAPDATA_HOME%\sapbackup\.switch.log ◆ On page 102.switch.switch.switch.sem It should read as follows: The switch_sem parameter must specify a file path in the following location: $ORACLE_HOME /sapbackup/.switch.switch. The following errors appear in the NetBackup for SAP System Administrator’s Guide for Windows: ◆ On page 101.switch. the following text is incorrect: The switch_sem parameter must specify a file path in the following location: %SAPDATA_HOME%\sapbackup\.lis It should read as follows: The switch_list parameter must specify a file path in the following location: %SAPBACKUP%\sapbackup\.lis ◆ On page 102.NetBackup General Notes The switch_log parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.

b.sem NetBackup Installation and Upgrade Limitations 1. Run the following command to add a host with the virtual name of the application cluster: nbemmcmd -addhost -machinename virtual_name -machinetype app_cluster where virtual_name is the virtual name of the application. Since nbpushdata -add_5x_inactivenode host will not overwrite an existing device configuration for a node in the EMM database. pkgrm fails. if you have storage units associated with an application in a cluster environment (also known as an application cluster type in NetBackup 6.0). the application cluster type must exist in the EMM database.0 Operational Notes 7 . you must run the following nbpushdata command before running.x media server.x. File requires removal from Solaris server systems prior to upgrades If the following file exists. After nbpushdata is complete. For each node of a clustered 5.x.0 -masterserver master_name Additional NetBackup 6.NetBackup General Notes %SAPBACKUP%\sapbackup\. run: nbpushdata -add_5x_inactivenode host Although it is not necessary to run this command for the node that was active when nbpushdata -add was run on the Global Device Database host. Before running nbpushdata. 2. 3. This is expected and it is not a problem. If you are leaving any clustered media servers at NetBackup 5. If the file exists. you must remove it before running pkgrm on Solaris server systems: /usr/openv/netbackup/bin/driver/snapctl10_x This file was created for patches to NetBackup 5. nbpushdata -modify_5x_hosts.switch. run the following command to associate the host with each node on which the application runs in the cluster: nbemmcmd -updatehost -add_server_to_app_cluster -machinename node_name -machinetype media -clustername virtual_name -netbackupversion 6. running it for all of the nodes does not require you to know which node was active. a. you will receive an error when the command is run for the node that was active.

refer to TechNote number 243461 on the VERITAS support web site.0 Operational Notes . but Tru64 clusters are different.0 server on an HP-UX machine. For a detailed explanation on how to change HP-UX kernel parameters. For Tru64 clusters only. Refer again to the “NetBackup Product Dependencies” chapter for the latest HP-UX patches. b. an error may occur while creating the NetBackup database during the installation process. Run nbpushdata -add on the active node. can be corrected by increasing the number of semaphores in the HP-UX kernel.failed to allocate a SYSV semaphore 6. and master_name is the name of the NetBackup master server. When installing on an HP-UX system.0. you should issue the following commands to determine if you need to update your HP-UX patches: # cd /usr/openv/netbackup/bin/admincmd # . SQL error (-832) -. you must uninstall GDM and NBAR from your server completely before you upgrade to NetBackup 6. This error. If you have a Tru64 cluster that is being upgraded to NetBackup 6. you should update your HP-UX patches. Normally. the procedure to run nbpushdata is different than for the other types of clusters.0. After you have successfully installed NetBackup 6. Disk CD image. shown below. Repeat the above step for each node on which the application can run. virtual_name is the virtual name of the cluster.0 version (with NBAR or GDM) installed on your server. 4. The files and directories in the ICS image do not have the “Other” bit set for read and execute permissions. 5. 7. 8. Failover to each of the inactive nodes and run nbpushdata -add -nocheck. If you have a pre-NetBackup 6. just as on the other cluster types. it is only necessary to run nbpushdata once in a cluster.Connection error: Insufficient system resources ./bpstsinfo -isremotecall -lsuinfo -serverprefix STSBasicDisk: bpstsinfo should run for a few seconds and issue this message: EXIT STATUS = 0 If the bpstsinfo command hangs. NFS shared root access install limitation An installation limitation exists with the ICS HP image.NetBackup General Notes where node_name is a node on which the application can run. the following procedure must be followed: a. 8 Additional NetBackup 6.

drvwddm. you need to correct the permits.exe .v.4 13.3077. refer to TechNote number 276504 on the VERITAS support web site for a detailed procedure on how to work around this problem. are missing file information.10.116KB (118.712 bytes) .576 bytes) . company name. If you are upgrading from a previous version of NetBackup and currently have a volume pool named CatalogBackup.dll C:\WINDOWS\system32\MSVCP71.01.v. Create a new volume pool. Delete the CatalogBackup volume pool. The following files.0 Operational Notes 9 .1. The following files remain after the uninstall of NetBackup 6. c.v.04/26/01 12:01 AM . Prior to the upgrade. such as.0. 12.340KB (348.NetBackup General Notes To enable this installation technique.7.160 bytes) .2.784 bytes) . 9.1.dll . restart the NetBackup services.56. If you have changed the application association of the cmd files from the default in the Windows NT Command Script on your machine. the VERITAS Private Branch Exchange SCM service will not start and you may receive the following error: Error 1920: Service VERITAS Private Branch Exchange (VRTSpbx) failed to start.488KB (499. a.48KB (49.01.04c Additional NetBackup 6. Restarting the services will ensure that the Help > About NetBackup menu displays the proper licensing information.152 bytes) . there will be a volume pool name conflict. users should do the following in the previous version of NetBackup.0.24KB (24.) C:\Program Files\Common Files\VERITAS Shared\VxFI\Bin\firtl. (The files listed below are shown in their default installation directories.v.7. 10. and/or file version. Verify that you have sufficient privileges to start system services To avoid this issue.04c drvwunin.dll .10.v.18a drvwenu.dll . product name. Move the media that is currently in the CatalogBackup volume pool into the new volume pool.04/26/01 12:01 AM .dll .12/28/01 03:56 AM . installed by NetBackup 6. When upgrading from a NetBackup Server evaluation license key to a permanent NetBackup Enterprise Server product license key on Windows 2000 or greater. The installation portion of the upgrade process will create a new default volume pool titled CatalogBackup.0 C:\WINDOWS\system32\MSVCR71. b.3052. 11.

Please see the appropriate installation guide.11/21/01 02:21 AM .53. make sure that the directory linked exists and is writable. create /usr/openv as a sym-link to the location in which you will be installing the software to in the non-global. In the global zone.21.v. On a server that: ◆ ◆ Does not have a master/media server on the global zone Has a sparse non-global zone using a read-only loopback device for the /usr directory The procedure is: a. make sure that /usr/openv exists as a link.5KB (54. On a server whose non-global zone is not using a read-only loopback device for the /usr directory. the client push-install or local install is done normally.784 bytes) . For eaxmple: # ls -al /usr/openv rwxrwxrwx 1 root root 10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv c./ Additional NetBackup 6. For eaxmple: # ln -s /nonglobdir/openv /usr/openv # ls /nonglobdir/openv /nonglobdir/openv: No such file or directory # ls -al /usr/openv rwxrwxrwx 1 root root 10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv b. In the non-global zone. In the non-global zone.exe .32-bit .1. The following are special instructions that provide clarification for installing NetBackup client software in non-global zones. This will need to be done even if the global zone does NOT have that directory.0 Operational Notes . For eaxmple: # ls -al /nonglobdir/openv total 32 drwxr-xr-x 10 9 root bin 512 Aug 18 15:23 .02a 14.NetBackup General Notes pnpninst.

NetBackup has supported mixed patch-level versions for many releases.0 media servers can reside in a mixed server (patch-level) environment.0 media server that can reside in a customer’s environment is a 5. On a server that: ◆ ◆ Has a master/media server installed on the global zone Has a sparse non-global zone using a read-only loopback device for the /usr directory The procedure is: a. the master or media server can be installed in a BASEDIR other than the default /opt. with this release of NetBackup a customer can have the following in their environment and have all managed by one master server: Additional NetBackup 6./ d. verify the directory linked to by /usr/openv. For eaxmple: # mkdir /opt/openv c. For example. the /usr/openv in a default installation is a link to /opt/openv. In the non-global zone.NetBackup General Notes drwxr-xr-x 18 root bin 512 Aug 18 15:30 . In the global zone. Client push-install or local install can now be done normally according to guides. In either case. Mixed patch-level support enables NetBackup servers to run a mixture of NetBackup major releases and patches in the same environment. and /usr/openv can be linked to /BASEDIR/openv. Client push-install or local install can now be done normally according to guides.0 Operational Notes 11 . create a writable directory where the /usr/openv points to.0 MP4 version level or greater. The minimum version level of a NetBackup 5. For eaxmple: # ls -al /usr/openv rwxrwxrwx 1 root other 10 Aug 18 11:39 /usr/openv -> /opt/openv/ b.. Alternatively. NetBackup Backward Compatibility Note The NetBackup Release Notes incorrectly state which 5.

veritas. NetBackup 5. refer to the NetBackup Installation Guides for detailed upgrade information.1 Maintenance Pack 1 (MP1) are both treated as NetBackup 5.0 configuration must be at a version level of 5. In NetBackup versions 5. Any other media server running either NetBackup 5. for NetBackup 5. MP2. and MP3.0 MP4 or greater.1 MPx. 5. The upgrade sections contain various mixed-version scenarios and how they must be upgraded to this version of NetBackup.0 MP4 or greater.) Client backwards compatibility extends only one major release behind the master server. or vmd/DA host. Any number of clients running NetBackup 5.0 MP4. http://support. A fix was introduced for this issue in NetBackup version 5. global device database host. A media server running NetBackup 6.x to 6.0. Again. Therefore. Only then can media servers be upgraded and finally client machines. (For more information about this fix.0. on the VERITAS support web site. the general rules for a mixed-server environment are as follows: ◆ ◆ ◆ In a mixed environment such as this.0 media servers.0.x servers performing these roles first. However.) ◆ ◆ ◆ 12 Additional NetBackup 6. please refer to TechNote 278153. Media server backwards compatibility extends only one major release behind the master server. Always upgrade NetBackup 5. Backlevel servers (those servers that are running NetBackup 5. or 5. if the media server and the client were the same machine. This includes database clients. No media server may have a numerically higher version than the master server. A master server can inter-operate with a media server that is running a level of NetBackup that is one major release lower.0.1 for compatibility purposes and have no co-existence issues.1. any media server that you want to coexist in a NetBackup 6. (The media servers must be running equal or lower levels of NetBackup. However.0 GA.0. refer to the NetBackup Installation Guide for your operating system.0. you would not be able to restore on the client. Applying a NetBackup maintenance pack (MP) does not alter the version of the release for NetBackup 5. MP1.x) cannot be used as a Volume Database Host.NetBackup General Notes ◆ ◆ ◆ ◆ ◆ A master server running NetBackup 6. The following is a link to this document. (The EMM server must also run NetBackup 6. For more information about upgrading NetBackup from For example. These capabilities are all on the EMM database host as part of the EMM server.x or 6.1 GA. this does not apply.) All remaining master servers must also run NetBackup 6. the master server must be running the highest version of NetBackup in use in that configuration.1 GA and NetBackup 5.0 Operational Notes .

During an upgrade of a NetBackup in a VERITAS Cluster Server or Sun Cluster you will see messages indicating that the database is created twice. a. 3. Additional NetBackup 6.0 Operational Notes 13 . perform the following steps to recover. If you have encountered this issue. the creation of the Sybase ASA database for NetBackup will fail. ◆ ◆ All components (master server. media server.NetBackup General Notes For customers who are currently at 5. 4. Freeze the NetBackup group. b. you can perform the following work-around on your machine.0 MP4 or greater or upgrade to NetBackup 6. 2. Backup images created under an older version of NetBackup will always be recoverable with a newer version of NetBackup.0 MP4. console. During cluster_config you must specify the same name used during the installation of NetBackup (install_bp) as the server name. The VERITAS Private Branch Exchange (PBX) software cannot be installed in a UNIX cluster using the push installation method provided with the infrastructure Core Services installer (installics). If the names differ. You must run the installics installer on every node in the cluster on which you are installing NetBackup. the name supplied to cluster_config must also be fully qualified and vise versa. and agent) on an individual system must be at the same version. If the name specified to install was fully qualified. Take all NetBackup daemons offline. client.0GA and do not want to upgrade to5. VERITAS recommends that you remove this file after you have upgrades to 5.0. Cluster Limitations 1. By creating this touchfile.conf file and cluster_config passes the -server option to create_nbdb. When installing NetBackup in a Sun Cluster all nodes must have NetBackup installed. you will likely see a performance degradation for backups and restores. Create the file /usr/openv/netbackup/NOSHM on a UNIX machine and install_path\NetBackup\NOSHM on a Windows machine. This is because install_bp populates the databases server. This is because the database is created in the default location (/usr/openv/db/) during install_bp and later moved / recreated on the shared disk.

and /usr/openv/netbackup/bp. If you have any add-ons to install. Next. restore of Flashbackup images will fail. VERITAS recommends that you not use Flashbackup for shared disks in a Microsoft Cluster. 5.conf and make sure all of the references to the virtual name are consistent. Run /usr/openv/netbackup/bin/nbnos g. /usr/openv/netbackup/bin/cluster/NBU_RSP. Bring the NetBackup group back online. d. Run /usr/openv/netbackup/bin/nbbms_start_stop start e. please following the procedures documented in the NetBackup High Availablility System Administrator’s Guide. call support for more information about the following error: EMM interface initialization failed. Run /usr/openv/volmgr/bin/tpext If this does not work. status = 77 i.NetBackup General Notes c. Modify /usr/var/global/server.0 Operational Notes . Due to Microsoft Cluster polling of shared disks. 14 Additional NetBackup 6. Therefore. unfreeze the NetBackup group and take it offline. Run /usr/openv/netbackup/bin/nbemm h.conf. Run /usr/openv/db/create_nbdb -index shareddir/db/data -tlog shareddir/db/data -mlog shareddir/db/data -data shareddir/db/data -server VERITAS_NB_hostname f. k. j.

11. Item 1.0 and AS3. Automatic client installation and update when the client is added to a policy is not supported at this release on the Windows NetBackup server. you must stop and start the NetBackup daemons (including daemons for any add-on products) in the native locale shell. NetBackup Windows Clients 1. Additional NetBackup 6. This problem will be resolved when NetBackup Java begins using a later version of JRE. a job will be created for each drive and the high level drive identifier will be backed up. which may not be the desired locale.0. 2. Localization and Internationalization Limitations 1. and Linux is not an accurate statement.Localization and Internationalization Limitations NetBackup Firewall and Port Usage 1.4(. if a drive is in the policy's file list.2_04) font configuration.23 systems because of the JRE1. feature Open File Backup VSS does not allow creating more than one snapshot per volume at a time. or bpclient are used in such a way that the ultimate daemon connection port is vnetd then ALLOW_NON_RESERVED_PORTS configuration option on the bpcd machine is ignored.0 Operational Notes 15 . Windows 2003 client. and on HP-UX IA64. This can cause a backup to finish with a status of 1 (some files were not backed up) when multistreaming is used to backup folders or files on the same volume and the backup is using VSS. If default_connect_options. The following correctly states how you should stop and start the NetBackup daemons. connect_options. either specifically or as part of ALL_LOCAL_DRIVES. Windows. 3. After installing NetBackup (or any add-on products such as BMR) on UNIX and Linux systems. Issue with bpmount command and include/exclude lists For multistreaming jobs. in the Localization and Internationalization Limitations section of the Release Notes for UNIX. and then excluded from the backup using the exclude list. NetBackup installation starts some of the daemons in the C locale. 2. NetBackup Java cannot display Chinese characters on Linux Red Hat AS4.

such as. these files displayed correctly when they were backed up from a Windows client.0 on top of a previous. on Windows the encoding for the Latin-1 character set is different than it is on Solaris. and vltadm. There is an inconsistency between the Windows and Java. The NetBackup – Java Administration Console does not support user-defined characters (UDC) and vendor-defined characters (VDC) because of the implementation of Java’s encoding converters.0 Operational Notes . if a Solaris client specifies a file name in the ja locale (EUC) and then attempts to display the file with the Backup. 5. such as. These character sets may have characters beyond the ASCII-defined character set.Localization and Internationalization Limitations 3. 6. bpadm. For instance. 16 Additional NetBackup 6. vmadm. A backup of file names with Portuguese characters resulted in the characters looking corrupt when displayed on a UNIX Master Server. varying encoding being used on different platforms caused this displaying issue. Archive and Restore GUI on HP server in the ja_JP. Administration Consoles with the Policy Keyword restrictions for Japanese characters. you must remove the localized contents installed on your system. there is a problem with spaces in the pathname that can cause a backup to fail. NetBackup menu user interfaces (MUI) can not input and modify multi-byte characters and are not localized to any language. ◆ For multi-byte file path characters.SJIS locale (SJIS). For Windows installations. This occurs because the same locale on different operating systems does not use the same encoding for the various locales with default character sets. however. The Solaris Latin-1 character set contains additional characters. the file name does not display correctly. both consoles should restrict the ja characters. 7. For this release of NetBackup. tpconfig menu. without install the localized contents in the Language package CD first. 8. This restriction may be removed in future releases of NetBackup. Windows and UNIX. When running on a non-English locale. These are operating system limitations and cannot be resolved through NetBackup. The MUI includes bp. If you plan to install an English version of NetBackup 6. ◆ 9. localized version NetBackup. The following examples demonstrate how encoding for various locales can effect how multi-byte file path characters or the file names of backups are displayed. File names and other text are not displayed correctly across different platforms. The NetBackup-Java Administration console does not restrict ja characters and the NetBackup Administration console for Windows does restrict ja characters. the install path must not contain multi-byte characters. characters that are specified on one locale may not display correctly in another locale. 4. Once again.

like script. or batch file locations This applies to all supported platforms. Media Server. The following NetBackup user-defined strings must not contain Multi-byte characters: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Host Name (Master Server. non-ASCII.0 Operational Notes 17 . Client) Policy Name Policy KEYWORD (Windows Only) Backup. or other database storage locations Path names specified in the policy “Backup Selections”.Localization and Internationalization Limitations 10. Path names of database files. At the time of this release. 11. the use of localized characters (for example. filegroups. Volume Database Host. multi-byte characters) is not supported in: ◆ ◆ ◆ Any database object names. tablespaces. including the use of previous versions of those NetBackup database agents with NetBackup 6. like instances. and so forth. databases. datafiles. portals. directories. transaction logs. Media Host. EMM server. the following database agents have restricted support of localized environments: ◆ ◆ ◆ ◆ ◆ ◆ ◆ NetBackup for DB2 NetBackup for Informix NetBackup for Oracle NetBackup for SAP NetBackup for SharePoint NetBackup for SQL Server with Advanced Client NetBackup for Sybase ASE When using any of these agents. template.0 servers. Archive and Restore KEYWORD (Windows Only) Storage Unit Name Storage Unit Disk pathname (Windows Only) Robot Name Device Name Schedule Name Media ID Additional NetBackup 6.

causing the cluster configuration to subsequently fail. If the clustered system's public network connection name contains any Chinese characters. you can use the Backup. or the View Status display on Windows) to view these files.0 Operational Notes . 18 Additional NetBackup 6. 13. Synthetics may not function properly between two media servers if the media servers are separated by a firewall. must open a range of ports so a port can be randomly selected during the synthetic job. Viewing log files with non-ASCII characters in some text editors may make the non-ASCII characters appear as gibberish. While there are some editors that will display the log file correctly. Users who want to perform a Synthetic backup across two media servers with a firewall between them.NetBackup Port Reduction ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Volume Group Name Volume Pool Name Media Description Vault Policy Names Vault Report Names Vault Name Vault Profile Name Off-site Volume Group 12. In the Frozen Image Client Configuration dialog box. the following strings are being displayed in English: Keep frozen image after backup Resynchronize mirror in background 14. then the wrong cluster information is entered into Registry. Archive and Restore GUI (Task Progress tab on UNIX. NetBackup Access Control (NBAC) The following subsections contain additional information about NBAC such as general notes on how to use this feature. An issue exists if you attempt to install an English version of NetBackup into a Chinese-clustered system. and known product issues. operational notes. NetBackup Port Reduction 1. Opening a range of ports to use synthetics means the firewall will be less effective.

Deassign -group NBU_Operator -object NBU_RES_Drive 4. devices. If you do not want root. 2.yourcompany. Enter the following: bpnbaz -addperms NBU_RES_Drive c. Under NBAC it may not be possible to manipulate Pending Requests (such as standalone tape mounts) on an upgraded system until the following actions are performed: a. administration of storage units. or Administrator (Windows) on the local install system as a security administrator for all VxSS security information. Do not modify settings in the Access Control properties pane in Host Properties.0. Log in as a security administrator b.Deassign -group NBU_Admin -object Additional NetBackup 6.Administrator limitations with the new connection protocols exist with Enhanced Authorization using a non-root (UNIX) or non-Administrator (Windows) user to administer On UNIX systems: vssaz removeazgrpmember --azgrpname "Security Administrators" --prplinfo ATP.root On Windows systems: vssaz removeazgrpmember --azgrpname "Security Administrators" --prplinfo ATP.NetBackup Access Control (NBAC) Caution An NBU_Security Admin member can delete all NBAC groups. or an Administrator. Assign. the following command will disable root’s access to VxSS security information. or Administrator. By default.unixpwd:your_host. VERITAS recommends NetBackup Access Control (NBAC) for authentication and authorization for non-root and non-Administrator NetBackup administration. and media will be affected.0 Operational Notes 19 . to be able to modify security information. These limitations also apply to root. Most notably. on hosts not in the NetBackup server list. In NetBackup 6. Enter the following: bpnbaz -addperms Assign. 1. causing all NBAC-enabled operations to stop and making re-initialization of NBAC security objects necessary. VxSS packages include root (UNIX).

On Windows machines. Perform the following steps: ◆ ◆ Open the file /usr/openv/netbackup/bp. On Windows machines. Stop and then start the NetBackup daemons. 5. you must edit the registry to modify a specific resource in the Registry Keys.NetBackup Access Control (NBAC) If you have erroneously modified settings in the Access Control pane and have been denied access to the NetBackup Administration Console. 20 Additional NetBackup 6.0 Operational Notes ..conf file to the following: USE_VXSS = PROHIBITED ◆ ◆ ◆ Save this file. VERITAS recommends that the user re-boots (the install target) after installing the Authentication (AT) server software.conf file you will see one of the following lines: USE_VXSS = AUTOMATIC or USE_VXSS = REQUIRED Change whichever line you have in the bp. VERITAS recommends that the user re-boots (the install target) after installing the Authorization (AZ) server software. Stop and then start the NetBackup services. For Windows-based systems.. In the bp. ◆ For UNIX-based systems. Select HKEY_Local_Machine\Software\VERITAS\NetBackup\ CurrentVersion\Config Double-click USE_VXSS Change the value to PROHIBITED and click OK. Exit the Registry. you can perform the appropriate procedure below to regain access to the NetBackup Administration Console. ◆ ◆ ◆ ◆ ◆ ◆ ◆ Select Start > Run.conf file on the master server. 6. you must modify a line in the bp. Enter regedt32 (for Windows 2000 and greater systems) or regedit (for Windows NT systems) in the Run window and select OK.conf for editing.

consequently they can change or disable NBAC. Several Windows NetBackup\bin\goodies scripts have not been modified to verify if NBAC credentials are needed. 8. will by default. 9. When authorization failures occur in an NBAC-enabled configuration. 15.NetBackup Access Control (NBAC) 7. The use of NetBackup Database Agents in conjunction with NBAC was not implemented in the NetBackup 6. On HP-UX. 11. 13. use the VxSS client interface (CLI) or the VERITAS Security Services Java GUI to increase the default expiration time.0 release. 12.0 release.cmd script. thus disabling further operations.0 Operational Notes 21 . expire twenty-four (24) hours after the login has been accomplished. anyone who belongs to the NetBackup Administration group has the ability to modify the Host Properties. Before you run a Windows . the error message(s) returned to the user may not clearly indicate an authorization failure. When adding someone who is not an administrator to the NBU_Admin group. Per-policy access control is not implemented in the NetBackup 6. 10. To avoid this issue. 14. you must set the permissions of the following directory to word readable/writable. Additional NetBackup 6. This is expected behavior that is caused by mixing C and C++ code on an HP-UX system. The NBU_Operator group alone does not possess the necessary permissions to inventory a robot. /user/openv/netbackup/logs/user_ops (UNIX) <install path>\NetBackup\logs\user_ops (Windows) Set the permissions of this directory to [0777] for UNIX systems and FULL CONTROL for the user group on a Windows system. Currently. This issue does not effect normal NetBackup operation. As such. the debug log may show a NON FATAL Unresolved external symbol. verify that you have a valid credential by performing a bpnbat -login. The NBAC security credential generated upon login using either the NetBackup-Java Administration Console or NetBackup Console (MFC) GUI’s. commands that run inside the scripts may fail if a user does not have a credential or has an expired credential.

never overwriting an existing subvolume. For Point in Time Rollback from a snapshot on the SnapVault secondary system.05. Snapshots of Windows 2003 clients using Advanced Client with the VSS snapshot method will fail with a job status of 156 if the Volume Shadow Copy Service is not started. use the older VxVM disk naming scheme (called hdisk# naming format on AIX and old format or OS native naming format on Linux). If the service is not running.time_stamp For example: subvol1_restore.2005. Use the vxdiskadm utility to change the disk naming scheme. however. Instead. the service may not always be running when an Advanced Client VSS snapshot backup is attempted. Use of enclosure based naming will cause the backup to fail. Extended attributes can be restored from FlashBackup images only by raw partition restore. the VxVM names for the disks underlying the volumes must not use the enclosure based naming scheme. 6. For Linux and AIX client data configured in VxVM volumes on supported EMC or Hitachi disk arrays. when using the TimeFinder snapshot method on EMC or the ShadowImage method on Hitachi.pfi_get_fmr_att: FastResync not enabled for volume: fs_vset 5. 4. restoring individual encrypted files from an Instant Recovery backup requires that the clients have all the latest Windows 2000 critical updates. 2. FlashBackup support for Solaris 9 is limited. the entire subvolume (qtree) is restored.NetBackup Advanced Client NetBackup Advanced Client 1. The VxVM.10h49m04s 22 Additional NetBackup 6. 3.0 Operational Notes . extended attributes cannot be restored via SFR. it must be manually started through the Windows Services Administrative Tool before the Advanced Client VSS snapshot backup can succeed. Note that the restore always goes to a new subvolume on the primary host.19. The backup fails and the following message appears in the client's bpfis log: <32> onlfi_freeze_fim_fs: FTL . Since the service starts only on an as-needed basis and NetBackup does not currently have a means of requesting it. and VVR snapshot methods do not support VxVM Volume Sets when used in conjunction with the Instant Recovery feature. FlashSnap. Windows Open File Backup using the VSS snapshot method is not affected by this problem. FlashBackup supports the backup of extended attributes for UFS file system (Solaris 9). The format of the new subvolume name is the following: mountpointname_restore. For Windows 2000 clients.

listed below.0) Advanced Client Configuration and Compatibility guide. and then mount the new subvolume on the client. 23 Additional NetBackup 6. new subvolume.veritas. Advanced Client snapshot methods and offhost backup methods perform mapping of the underlying file system and volume structure. Solstice Disk Suite is not supported. To access the NetBackup (6. In the search field in the upper. such as other volume managers or storage replicators. then on the filer rename the original subvolume and rename the new subvolume with the name of the original. bpfis should only return the first level of the circular mount point instead of a recursive path. b. The guide will appear when the web page refreshes and shows the results of the search. When bpfis is given a path that contains a circular mount point.0 Operational Notes . and then mount the new subvolume on the Circular mount points are not being processed correctly. it returns a recursive path from the circular mount points. The use of other components in the I/O system. then on the filer share the new subvolume. Or Unmount the original subvolume on the client. Such configurations are not supported. may result in an unreliable backup. a. retaining its current name. 7. Please note the following restrictions: ◆ VxFS_Checkpoint snapshot point in time rollback does not work with VxFS Cluster File System (CFS). you can do one of the following (see the documentation provided by your NAS vendor for command details): Unmount the original subvolume on the client. Go to http://support. This mapping has been verified for the I/O system components listed under "Matrix of Snapshot Methods and Requirements" in the Advanced Client Configuration and Compatibility guide. making sure the new subvolume is still shared. Unique restore features to Instant Recovery snapshots. perform the following steps. 9. 8. right corner of the web page. enter the following: Advanced client configuration c. There are three restore features unique to Instant Recovery snapshots. Click “>” search icon.NetBackup Advanced Client To use the restored.

VxVS 4. “fsck coredumped in recover_qlog() due to a long device name”. HP-UX.x.NetBackup Advanced Client ◆ Point-in-time rollback (image rollback) is for the following: ◆ ◆ VxFS_Checkpoint snapshots of Solaris clients (with VxFS 4. The space optimize snapshot method in VxVM 4. the client must have: UNIX clients: “OLD_VNETD_CALLBACK = YES” entry added in its bp.1. the user must install a VxVS patch that includes the Itool Incident 154093. Service Pack SP1 should be installed. 14. 13.0 or greater. Due to limitations in volume name size in VxVM for Windows 2000 3. crashes when the file system device name is comprised of more than 63 characters for VxVS 3.56.1 or greater must be installed.0 and later) VxVM snapshots of either Solaris. are unique. After installing VERITAS Volume Manager for Windows 2000. for backup volumes targeted by the VxVM and FlashSnap snapshot methods. and is labeled. Note: the master server and the destination client cannot be separated by a NAT (Network Address Translation). fsck.31. The following are Instant Recovery limitations in mixed environments: ◆ For a NetBackup 6. 11.x source and destination (tar) client are the same host. 12. the build level is reflected in the Windows Registry under the subkey HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Volume Manager 3. and VxVS 4. VERITAS Volume Manager for Windows 2000 version 3. and the Volume Manager build level should be 5. or Windows 2000 and 2003 clients These restore features are described in the NetBackup for Advanced Client System Administrator's Guide. Because of this issue. For VERITAS Volume Manager for Windows 2000 version 3.0.0 master server and when NetBackup 5. hot fix HF03 should be installed. which are derived from parent volume names.1\Version. VxVM volume names should be limited to 12 characters in order to guarantee that snapshot volume names. Advanced Client VxVM and FlashSnap snapshot methods on Windows 2000 platforms are supported by VERITAS Volume Manager for Windows 2000. To successfully employ these snapshot methods.conf file. Advanced Client FlashSnap backups fail if the file system device names that are used on the alternate client contain more than 63 characters. To avoid this issue. 24 Additional NetBackup 6.0 does not work with alternate client backups.1.1.0 Operational Notes . Windows clients: “OLD_VNETD_CALLBACK" string with value of “Yes” added to the HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\Config registry key. The system command. 10.

0 source client.x destination client. Instant Recovery is not supported. ◆ bpadm Interface 1. start the telnet command with a command line option that specifies the terminal type.NetBackup Advanced Client ◆ NetBackup 6.0 destination client. Changing the default terminal type in the Windows client from 'ansi' to 'vt100' seems to correct this display problem. When displaying menus or other output. Make sure it is exported to subprocesses (bourne shell). you can do the following: a. To avoid this issue.usually missing the first character. NetBackup 6. b.0 master server.x (different host than source) or NetBackup 6. Instant Recovery is not supported. b. you can change the terminal type implemented by the client and then connect to the remote system (where it will detect that terminal type) or change the terminal type after you have logged in.0 Operational Notes 25 .0 master server. the data does not appear correct . On Windows. Enter the following: telnet <host name> -t vt100 If you are already logged in. Enter the following: TERM=vt100 export TERM Additional NetBackup 6. you can change the terminal type through the environment by entering: a. and NetBackup 5. NetBackup 6. Setting the TERM environment variable to 'vt100'. NetBackup 5. and NetBackup 5. To change the terminal type implemented by the client. This issue seems to be caused by the interaction between the terminal type implemented by Windows telnet and the remote UNIX terminal output.x source client.

then it is necessary to have the NetBackup Client Service logged on as administrator. a restore of the directory on which the volume was mounted will not actually remount the volume (for example. 2. FlashBackup-Windows policies do not support the backup of file names that are in the 8-character plus 3-character format. It is possible to specify a partition in the backup policy that contains these files. and then the volume is unmounted. Examples of this problem would be: If a backup is done of a Mount Point Directory. the directory for the mount is first deleted. 3. but the restore of all Windows System data in the partition cannot be guaranteed. When restoring individual files from FlashBackup on Windows images. If a file is restored that exists on a Mount Point Directory. It is necessary to first delete any files that are to be restored. 26 Additional NetBackup 6. FlashBackup-Windows policies do not support the backup of Windows System database files (such as RSM Database and Terminal Services Database). change the log on for the NetBackup Client Services from Local System Account to Administrator. If. FlashBackup-Windows policies do not back up Windows system-protected files (the System State.3 character format is retained. This problem exists for all reparse points including RSM. and the backup will succeed. FlashBackup-Windows policies do not support the backup of Windows Operating System (OS) partitions (such as C:\). the restore will not replace the reparse point or data files under the reparse point unless the reparse point or files are first deleted. The 8. When restoring a reparse point for a FlashBackup Windows policy. Restoring FlashBackup on Windows encrypted files and hard links. but the name of the restored file may be different from the original name. It is possible to specify the partition in the backup policy.0 Operational Notes . 5. such as the Registry and Active Directory). 4. 6. restore of the reparse point is not actually done). but the restore of the data in these files cannot be guaranteed. and the backup will succeed. Under services on the control panel.NetBackup Advanced Client FlashBackup 1. if the files being restored are encrypted or are hard links. the file will not actually be restored if it still exists. then the restore of the reparse point will result in the directory being restored with the volume mounted.

The tpconfig command must also be run before a NearStore storage unit is created. Network Appliance (NetApp) NearStore Disk Storage Unit 1. as indicated under the "NearStore Authentication" sub-heading. Before creating a NearStore Storage Unit. Multistreamed NetBackup for Oracle Proxy Block Level Incremental (BLI) backups. DB2. This functionality will be incorporated into NetBackup in a later Maintenance Pack release. Optimized Snapshot/SnapVault restores are not supported for NetBackup 6. 4.0 GA release. Multistreamed backups using NetBackup for Sybase. This restriction will be removed in future NetBackup releases. The NearStore storage unit does not support backups based on the following policy configurations: ◆ ◆ ◆ Multistreamed backups using NetBackup for Microsoft SQL Server. It will queue subsequent job streams. each subvolume to be backed up must be specified in the NetBackup policy.) Note that each subvolume named in the policy must be individually mounted on the client. Windows Alternate Path Restores is not be supported. For further configuration details. This functionality will be incorporated into NetBackup in a later Maintenance Pack release. as indicated in the "NearStore Configuration" section of Appendix B in the NetBackup System Administrator’s Guide. 2. and SAP are not permitted to run as multiple concurrent jobs if these agents are run in multi-streaming mode. The NearStore storage unit does not support the checkpoint restart feature.0 Operational Notes 27 . It is not sufficient to mount only the volume containing the subvolumes. The following Data Base agents: Oracle. it is necessary to properly configure the NearStore. Optimized restores automatically select to restore from the primary/filer snapshot copy if it exists rather than the secondary/NearStore SnapVault copy. (A subvolume is a qtree in Network Appliance Data ONTAP. 3. Volume I. For SnapVault backups. see the NetBackup Advanced Client System Administrator's Guide. The code path for Windows is completely different and currently not implemented. The NetBackup job scheduler can only run one job stream at a time. 2. Additional NetBackup 6. Informix. Solaris alternate path restores are supported. 3.Network Appliance (NetApp) SnapVault Network Appliance (NetApp) SnapVault 1.

all stripes on a volume on the restored system will be the width of the first stripe on that volume on the protected system. 4.) 7. You cannot use the NetBackup Administration Console to manage Bare Metal Restore if you use the Change Server option to change to a NetBackup master server that is licensed for BMR. an HP-UX system must contain at least one volume group that is controlled by HP-UX Logical Volume Manager (LVM). change the following two options: ◆ ◆ "Microsoft network server: Digitally sign communications (always)" to "Disable" "Microsoft network server: Digitally sign communications (if client agrees)" to "Enable" After changing these settings. BMR does not support multiple stripe widths per volume when a Solaris system that uses Solaris Volume Manager is restored. 5. BMR point in time restore does not work when the policy that backs up the client has compression enabled and the BMR master server resides on a system that is different than the client (for example.0. You can create more than one SRT at OS levels at or below the OS level of the boot server. restores may fail because DOS cannot copy files from the shared resource table (SRT).) 3. 28 Additional NetBackup 6. reboot the system. For UNIX and Linux SRTs. To avoid this issue. do the following: In Administrative Tools > Local Security Policy > Local Policies > Security Options. For Solaris Volume Manager disk stripes. (BMR point in time restore is different than a regular NetBackup point in time restore. HP-UX systems can host only one shared resource tree at a time.NetBackup Bare Metal Restore NetBackup Bare Metal Restore 1. you must: ◆ Log into the NetBackup master server that is licensed for BMR each time you start the Administration Console (UNIX and Linux systems). If a Windows BMR boot server is also an active directory server. but the newly created SRT will invalidate any existing SRTs at other OS levels. Windows client and UNIX master server). the directory paths where the SRTs reside must contain ASCII characters only. To use the Administration Console to manage Bare Metal Restore. 6. BMR will delay its support of the BMR restore for Solaris NetBackup media servers that back up their own data until after the release of NetBackup 6. 2. To function as a boot server. (In the meantime. you can protect a Solaris NetBackup media server as a regular BMR client. AIX clients require at least 256 MB of RAM to support BMR restore operations.0 Operational Notes .

Block-level incremental. The System Administrators guide goes into details on how to configure the new Hot Catalog backup method. nor will it be restored during a Hot Catalog recovery. Manually initiating an offline backup of the NetBackup catalog can fail if backups are in progress. Encryption is not supported. NetBackup 6. The NetBackup FlashBackup option is not supported with BMR.0 Operational Notes 29 . Enhanced client/server authentication (vopie) is not supported with BMR. 15. VERITAS Storage Migrator is not supported with BMR. 2. the user can restore these databases manually. NetBackup Catalog 1. After you log into or start the Administration Console on a NetBackup master server that is licensed for BMR. After BMR restores the operating system. 10. BMR does not restore databases that require use of database agents.0 offers a new method to perform catalog backups of a Master server. then you should use a hot catalog backup. is not supported with BMR. Backing up the NetBackup catalog can fail if it is manually initiated and backups are in progress. 14. you can change to another server and then change back to the server on which you logged in or started and continue to manage BMR. The workaround for this is to initiate these cold backups when no other NetBackup activity is occurring.NetBackup Catalog ◆ Start the NetBackup Administration Console on the NetBackup master server that is licensed for BMR (Windows systems). 13. However it doesn't mention that the NetBackup Jobs database will not be included in the Hot Catalog backup. available with VERITAS Oracle Edition. 11. Restores from user initiated backups are not supported. After a Hot Catalog Recovery of the Master server the Jobs Additional NetBackup 6. 9. or to schedule the cold backup of the catalog to occur automatically. BMR cannot be used to restore a NetBackup master server. and true image restore information is not collected during a user initiated backup. BMR requires true image restore information. NetBackup database agents are not supported with BMR. 8. 12. If catalog backups are required while NetBackup activities are occurring.

all databases must have unique names. 3. The 6. Note If you are restoring a database to an instance that already has an existing database named identically to the one you are restoring. 64-bit databases. you must clear LIBPATH before executing bpdb2proxy or bpdbsbdb2 from the command line.NetBackup Database Agents database will be reset so all new jobs begin at JobID 1. search for TechNote number 278610 on the VERITAS support web site. the existing database will be overwritten. This is the correct behavior for NetBackup 6. The IBM DB2 restore command enables you to rename the database at the time of the restore to avoid overwriting the original database. If the catalog backup is started on a media server by a vault job.0 Operational Notes .0 NetBackup for DB2 database agent enables you to restore a DB2 database to a different/same instance on a different client or to a different/same instance on the database's original client. For 64-bit. 3. 2. DB2 Agent 1. canceling the vault job from the Activity Monitor will not terminate the catalog backup.0 due to the design of the Hot Catalog backup recovery. The NetBackup Client GUI does note recognize DB2 version 7. Within an instance. NetBackup Database Agents The following subsections contain known limitations that exist for the following database agents. 30 Additional NetBackup 6. For more detail on this issue. DB2 databases on AIX. For more information on performing alternate restores. DB2 version 7 does not support 32-bit application access of 64-bit databases. Catalog backup jobs started with -host option to run on the media servers cannot be killed from the Activity Monitor. see the NetBackup for DB2 System Administrator's Guide for UNIX or the NetBackup for DB2 System Administrator's Guide for Windows.

The use of exclude lists for Lotus backups on NetBackup Windows clients has been disabled. Informix Agent 1. Backup of password-protected databases is not supported. You must perform an advanced client backup after making any configuration changes to the database. Please contact Informix Support for onsmsync-related patches. Master initiated Lotus Notes. the user must back up or restore each node individually. You may encounter issues with the onsmsync utility with various versions of Informix.0 Operational Notes 31 .NetBackup Database Agents DB2 Agent With the Advanced Client 1. 2. Lotus Notes Agent 1. 3. To back up or restore a multi-node environment. Attempting to back up a password-protected database causes the job to suspend indefinitely. the automatic restore of Lotus transaction log extents during the recovery of the Lotus database will not be able to locate the path to the progress log and will fail. The ability to back up or restore multiple nodes concurrently is not supported in NetBackup 6. Additional NetBackup 6. The suspension occurs within the Lotus Notes server. If the <install_path> of the NetBackup master server and the NetBackup client is different. 3. Users have to be manually disconnected before performing an advanced client restore. and can be avoided by not using password protection.0. 2. Point-In-Time restores may fail with a status 12. There is no API available for exclusive database access in DB2 version 7.

3. When attempting multi-streamed backups using Exchange Advanced Client snapshot backups. use the NetBackup Administrator’s GUI to launch a Manual Backup operation on an Exchange policy. it may not be possible to change the destination client value to match the virtual server name. To obtain the correct behavior. use a NetBackup Client GUI on a NetBackup server to change the destination client value to the virtual server name.NetBackup Database Agents Microsoft Exchange Server Agent 1. For a restore of the Microsoft Key Management Service or Microsoft Site Replication Service. NetBackup for Exchange with Advanced Client 1. the use of multi-streaming requires a separate snapshot volume for use by each backup stream. When using the NetBackup Client Backup interface or the bpbackup command to initiate an Exchange offhost alternate client backup. the backup will fail and report a status of 200. a full backup will be performed. In that case. 2. one must set the destination client value to be the virtual server name. but the “Allow Multiple Data Streams” setting must be enabled. When an Exchange backup is launched from the NetBackup Client GUI and uses the Advanced Client offhost backup capability. use the NetBackup Administration Console to initiate a manual backup for that Exchange policy. This capability is planned for a future release. 4. Compression is not supported when using NetBackup for Exchange. If restoring an Exchange database using a NetBackup client-only installation on a cluster. When restoring data in an Exchange cluster environment. The backup operation is not impacted by this lack of progress logging. The compression attribute should not be enabled on Exchange policies. If detailed progress is desired. 32 Additional NetBackup 6. At this time.0 Operational Notes . 2. even after a restore status 0. 5. failure to remove the contents of the kmsdata or srsdata directory prior to initiating the restore may result in a corrupt database. Instead. When attempting an incremental backup of Exchange using a local snapshot (“Perform snapshot backups” is selected on the policy). Note: it is sufficient to use a single data stream. See the Testing Configurations Settings section in the NetBackup for Exchange System Administrator’s Guide for instructions regarding a manual backup operation. select the “Allow Multiple Data Streams” setting on the policy. the backup selections (storage groups or Information Storage) cannot share the same snapshot volume. the progress log window does not display the usual progress messages evident when a scheduled backup is executed.

1.1.6 client library on the libjava.6 with HP-UX from the ldflags file in $ORACLE_HOME/lib.1. (a runtime library that is part of JRE Java Runtime Library by performing the following procedure: a.8 and supplied with Oracle 8. The Oracle 8.1.00 systems. The default path for SAPDB installation is C:\Program Files.0 Operational Notes 33 .1. b. SAP Agent references to libjava. libjava.6. The NetBackup Client interface is unable to connect to Oracle 8. Users should install SAPDB under a directory that does not contain spaces in the directory name. Additional NetBackup d. should not appear on the list.00.6 installation directory that is defined by the $ORACLE_HOME variable.00. NetBackup explicitly loads Oracle database shared libraries during program execution. Run the $ORACLE_HOME/bin/genclntsh script to generate a new link has been removed from file: chatr linclntsh. To avoid this issue and use Oracle 8. If the default location is chosen for installation. The runtime library.1. you must remove the dependency of the Oracle 8. SAPDB backups fail if the SAPDB database is installed in C:\Program Files or the directory name contains spaces in it. libclntsh.1. is dependent upon the Java Runtime Library. then backups will not work. this involves a call to the shl_load() method to explicitly load the shared library.6 client libjava. The shl_load() method does not support the use of a library that contains thread local storage (TLS). Use the following command to confirm that the libjava.6). Search for. and remove. Go to the Oracle 8.NetBackup Database Agents Oracle Agent 1. The Java Runtime Library The chatr command lists all of the libraries that the specified one links to.6 databases that are on HP-UX contains TLS references that prevent the Oracle library from being c. This problem is specific to Oracle 8. For systems running HP-UX 11.

This can result in a failed backup or restore operation of that database. 34 Additional NetBackup 6. When restoring a SharePoint Document Library Store.) 5. the interfaces unexpectedly terminate. use a single client interface to browse SharePoint resources for backup. attempting to restore a SharePoint configuration database to a different name than what is currently configured in the farm causes the restore to fail. SharePoint Agent 1. VERITAS recommends that you try the backup or restore repeatedly until successful. the SharePoint Information Store service must be running. Redirected restores of the SharePoint configuration database. Document Library Stores.0 Operational Notes . 2. (Note. In a SharePoint Farm that contains multiple SQL Server hosts. 4. and Single-Sign-On database are not supported. Also. 3. If not. When the SharePoint Search Index service is running. Backup of files that contain Japanese or Chinese characters in their names will not work. When attempting to open multiple NetBackup Client Backup interfaces to browse SharePoint resources. it sometimes contends with NetBackup for access to the portal index database. the restore process sits idle for minutes and eventually terminates in error. attempting to restore a SharePoint Portal database to SQL Server host B may fail when the SharePoint Farm Configuration database resides on SQL Server host A.1 that is scheduled to be fixed in the first NetBackup 6. that names are case-sensitive.NetBackup Database Agents 2. These databases can only be restored to their original location. To avoid this issue. To avoid this issue. change the NetBackup Client Service account. on the SQL Server host B (where the portal database(s) resides.0 Maintenance Pack release. This account must have network access to the SQL server host A (where the configuration database resides). to a domain account other than LOCALSYSTEM. This is a regression from NetBackup 5.

NetBackup jobs may remain queued for long periods. Sybase Server Agent 1. “Resolving Problems Related to a Full Disk”.sybase. even though all NetBackup processes and services are running.0. VERITAS recommends that users use the Universal Naming Convention (UNC) name of the shared resource.0 Operational Notes 35 . If the NetBackup installation directory or the VxUL logging directory for NetBackup fills up. The UNC name is similar to the following: \\servername\sharename Note There are special batch files that run during a backup that allow the backup to be written to a mapped drive.NetBackup Disk Backup Capabilities SQL Server Agent 1. network mapped drive not permitted for storage unit Instead of using mapped drives. For example. there are some restrictions on the types of file systems where you can create the Sybase ASA database files. This includes NFS-mounted file systems and network shares on Windows.chm. Until then. such as with logging NetBackup Disk Backup Capabilities 1. Sybase offers more information about this limitation including what they support for SAN/NAS storage at the following URL: http://www. Windows. refer to. Attempts a backup with mapped drives used as disk storage unit names will fail with the following message: invalid drive type. in the NetBackup Troubleshooting Guide for UNIX. NetBackup cannot read an image that is on a mapped drive because of the way Windows handles mapped drives. These batch files map the drive in for the bpbkar process and then un-map the drive after the process is done. This problem originates within the Windows 64bit SDK and is expected to be resolved in a future service pack. and Linux. When using the NetBackup for SQL Server GUI on 64bit platforms. the online help cannot be opened. NetBackup may become unresponsive. Additional NetBackup 6. With the release of NetBackup 6. open the help file directly using the Windows Explorer: install_path\VERITAS\Help\nbmssql. For more information on how to avoid this issue. 2.

A message will appear if. a checkbox named ''Eject media from standalone drive(s)'' in the dialog box titled ''Stop/Restart Media Manager Device Daemon'' does not function. In NetBackup 5. even though NetBackup defaults to something much greater. This error indicates a disk full error condition. When using Inline Copy.0. In NetBackup 6. users should not specify the same Storage Unit Group for more than one concurrent copy. An error 84 coming from a pre-NetBackup 6. The result is that this limit causes backups to fail with the message.NetBackup Interfaces 3. is interpreted to mean the same as an error 155 in NetBackup 6.0 images cannot be imported. no importable images are found. and Windows reports that error as the disk is full. so users must use the nbemmcmd command to set that Enterprise Media Manager option. then the size of an image fragment is limited to 4GB.x the checkbox allowed temporary setting of the DO_NOT_EJECT_STANDALONE Media Manager configuration option. Because of logic changes made in NetBackup 6. NetBackup Interfaces General NetBackup Java Interface 1.0 media server.0 Operational Notes . Users can use the following example to set this option: nbemmcmd -changesetting -do_not_eject_standalone 1 -machinename lumiere 36 Additional NetBackup 6. 4. EC_diskfull (129). The real issue is that the fragment is too large. Inline Copy limitation 1. If a customer uses Windows FAT file systems for their disk storage units (DSUs) on media-servers. pre. In this release of NetBackup. Please refer to the NetBackup System Administrator’s Guide for more information on which images are not importable.0. VERITAS recommends that users configure DSUs on FAT file systems to have a maximum fragment size of 4000MB instead of using the NetBackup default.NetBackup 6. the checkbox has no effect on Media Manager processing. Disk Media Server 1.0.

.server. perform the following steps.NBJAVA_CONF=$NBJ_CONF -showversion -Dvrts. In the NetBackup-Java Administration Console. option. and you will see that the pathname you just entered was not saved. If you add a new pathname in the NetBackup Catalog Backup window and click the OK button.common. /usr/openv/netbackup/bin/jnbSA The log file for this execution instance is /usr/openv/java/logs/root. a. Right-click on the Catalog node in the NetBackup-Java Administration Console. Click the Files tab.0 AS configurations.path=${VRTS_LIBRARY_PATH} -Dvrts. Click New. the pathname may not be accepted. f.) e. b. adding new path names in the NetBackup Catalog Backup window may fail. To avoid this limitation and ensure that a new pathname is accepted.common. NetBackup-Java interface fails on certain Red Hat EL 3. c. 3. Go back to the NetBackup Catalog Backup window and verify that the correct paths are present. Additional NetBackup 6.0 AS Update 3 SMP kernel systems.log /usr/openv/netbackup/bin/jnbSA: line 163: 11296 Aborted $JAVA_PA TH -Dvrts. d.NetBackup Interfaces 2.utilities.11269.LOG_CMDLINES=$ {LOG_CMDLINES} -Djava.0 Operational Notes 37 .. The NetBackup-Java interface immediately fails on a single Xeon processor that is running on Red Hat Enterprise Linux 3.jnbSA. You can verify this by returning to the NetBackup Catalog Backup window after you have clicked the OK button. and select the Configure NetBackup Catalog Backup.library. Click OK. The following error occurs when trying to start the NetBackup-Java interface on this type of system. (You can enter additional paths by repeating steps c and d until all new paths have been entered. Enter a path and click on a different path that already exists.

the user can enter the correct settings in to the Adjust 38 Additional NetBackup 6. Use the information in the following list to avoid this issue in the future: ◆ ◆ ◆ Install another processor (the issue does not present itself on dual processor machines). AdminConsole >>$LOG_FILE 2>&1 Your DISPLAY environment variable is set as follows: 0:0 Another exception has been detected while handling the previous error.0 Operational Notes . (NX) page protection nexec=off ◆ ◆ Reinstall update 2 of this version of the operating system. Good bye.nbe. To correct this problem.NetBackup Interfaces DEBUG_PROPERTIES=$DEBUG_PROPERTIES -Xms$INITIAL_MEMORY -Xmx$MAX_MEMORY vrts. The following is the failed backup information about this error : ERROR REPORT FILE = (N/A) PC SIGNAL FUNCTION NAME OFFSET LIBRARY NAME = 0x0x554d0084 = 11 = (N/A) = 0x554D0084 = (N/A) Please check ERROR REPORT FILE for further information. A problem exists from the way Tru64 reports the timezone to the Java Timezone class causing the time in the Tasks Performed window to be one hour off from the actual time.conf and add the following lines to disable the no-execute function. 4. specify it in the login dialog of the NetBackup-Java Administration Console (running on another host). Reconfigure the kernel to be non-SMP. Edit the file /etc/grub. Run the NetBackup-Java Administration Console on another host. If you need to administer this type of configured host. if there is any.

Install and use the Windows Remote Administration Station to remotely administer your UNIX NetBackup servers.0 Operational Notes 39 .pmoffscreen=false This workaround will greatly degrade the performance of the GUI. Resizing the window causes the NetBackup-Java Administration Console to paint correctly. -Dsun.java2d. if you then try to perform other operations in Backup Policy Management which require entering text. Java moves the original non-modal dialog in front of the parent frame. 7. the characters you enter may be transposed in order when displayed in the text field. On Tru64 platforms. You can administer any NetBackup server by specifying the server in the login dialog. Additional NetBackup 6. 9. the menu and button mnemonics do not work properly. When the modal dialog is hidden. Paint problems in tables with large sets of data viewing with Exceed There is a Java problem that causes table painting problems when the NetBackup-Java Administration Console is viewed through Exceed for large data sets. You may also notice that response time is slow. The mouse control may lock up when deleting a large number of jobs. the non-modal dialog is moved back to its original position behind the parent frame. This bug may cause the interface to deteriorate to the extent where it is unusable. but behind the newest dialog (a modal dialog requires a response and blocks input to all other dialogs for the application until the response is received). Another workaround involves adding the following to the Java command in the jnbSA or jbpSA startup scripts. 8.NetBackup Interfaces Application Timezone dialog. Other options to consider are: ◆ Install the NetBackup-Java Windows Display Console and use it on the Windows desktop. A persistent file is saved in the user’s directory. If a non-modal dialog is visible and behind the parent frame and subsequently a modal dialog is made visible. the characters you enter into the text field may be displayed in the field out of order. for example. If you enter text into a dialog’s text field while either NetBackup Java is busy performing other operations. and is used on subsequent program operations to enable the NetBackup-Java Administration Console to use the correct default timezone. the job table in the Activity Monitor. 5. and save this as the default. or while your system is busy. For example. if you have started the Backup Policy Management Install Client Software operation and it is currently busy installing software. ◆ 6.

) 12.NetBackup Interfaces If the mouse seems to lock up when deleting a large number of jobs from Activity Monitor. Media The following items are known limitations with features associated with the Media and Device Management portion of the NetBackup Administration Console. be patient. 2. In the NetBackup Java Administration Console. it may take a while for the operation to complete. Remote client software install limitations: ◆ It does not support software install for non-UNIX clients and a small subset of UNIX clients are also not supported. Storage Unit GUI defaults to wrong number of drives When adding a storage unit for a robot that contains shared drives. It is enabled only when a master server node is selected. results in an Unknown hardware type: hardware type message. 11. the initial value for "Maximum concurrent write drives" may be greater than the number of drives in the robot or available to the media server. and only if the master server is the server the user logged into when starting NetBackup Java. An attempt to install on a UNIX client for which remote install is not supported. the NetBackup patch version is not displayed for hosts in the Media and Device Management > Devices > Hosts view and the Bare Metal Restore Management > Hosts > Bare Metal Restore Clients view. Remote display of the NetBackup Java Administration Console in multi-byte locale environments is not supported. (The patch version is displayed in the Administration Console title bar for the host being administered and in the hosts listed in NetBackup Management > Host Properties views (Master Servers. It is recommended that you move only one volume or volume group at a time. 10. 1. 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 login dialog be in the server list of all the relevant media servers. NetBackup-Java Backup Policy Management 1. and Clients). The mouse will work eventually in this situation. Media Servers. ◆ 40 Additional NetBackup 6.0 Operational Notes .

The PIRD mode is set on a robot and media server connection. and the 'Other' for OS Type column. If you use the NetBackup Remote Administration Console to configure any NetBackup host other than the master server. where NetBackup would pend mount requests to "DOWN" robots. the robot's hardware is not functional. NetBackup will try and pick another storage unit that has a robot that is not "DOWN". NetBackup will queue the job and a "Queued" state will be displayed in the Activity Monitor (refer to the section on job queuing for the reasons why a job can be in a "Queued" state). and it will be possible to manually assign these mount requests to drives. even when the job could have run on other robots.0. add the SERVER entry for the Remote Administration Console host to the host being configured. an error is incorrectly reported that indicates no snapshot methods will work for the policy and client. 1. If NetBackup cannot find a storage unit for the job. These pending requests will appear in the Device Monitor.0 Operational Notes 41 . the following issues can occur: ◆ ◆ ◆ Operating System or NetBackup version-specific nodes will not be seen in Host Properties dialog. and tells NetBackup to pend mount requests to the robot even if it is "DOWN" (refer to the tpconfig usage for details on how to set the PIRD state). and the robot needs to be operated in a manual mode (where NetBackup will not be loading media in the drives of the robot). If for some reason. NetBackup Media Manager Media and Device Selection (MDS) The following items describe the known limitations for the Media and Device Selection feature of EMM. the robot can be made to operate in the "pend if robot down" (PIRD) mode.NetBackup Media Manager NetBackup Remote Administration Console 1. The right pane of the NetBackup console will show blank for Operating System and version columns. When an Advanced Client policy is created or modified with Policies or a policy is created with the Snapshot Policy Wizard. and if the NetBackup host does not contain a SERVER entry for the Remote Administration Console host. This is different than pre NetBackup 6. To avoid this issue. and it will not be Additional NetBackup 6. Pending mount requests to "DOWN" robots for storage unit requests: NetBackup will not pend mount requests to "DOWN" robots (robots whose drives are in AVR mode) for storage unit related requests. NetBackup will not autoassign.

3. After media servers have been upgraded to NetBackup 6. This is different than pre-NetBackup 6. MDS will not select media with conflicts for write jobs (including backups. Any runtime integrity checks performed by querying the device serial number and comparing with the configured serial number in the database will fail for those few devices whose legacy serial number in the database differs from what the new serial number formatting algorithm generates. tpreq mount requests.0. 1.NetBackup Media Manager possible to manually assign a mount request targeted to one storage unit to drives of another storage unit. This change may cause certain devices (tape drives and robotic libraries) to be configured as unserialized or configured with a different serial number.0 and their Remote NDMP drives converted to Media Manager drives. tpreq mount requests for write.0 media servers when necessary. write side of duplicates. and so on). It is not possible to mount media that are not configured in EMM using NetBackup. NetBackup has improved its serial number formatting algorithm.0 Operational Notes . General Media Manager Limitations The following list identifies known limitations as they apply to NetBackup Media Manager in general.0 installations will still have the legacy serial numbers in the EMM database. verify. There are no known issues with having this unnecessary NDMP host in the list. it was possible to mount media that were not configured in the Media Manager volume database. write side of duplicates. and so on) are not storage unit related and will pend even if the robot is "DOWN" (irrespective of the PIRD state). Devices that are upgraded from pre-NetBackup 6. NetBackup will down all the paths on all the media servers for a drive if the TapeAlert information that the drive reports indicates that the drive needs to be downed. Note The above section applies only to storage unit specific mount requests (including backups. Refer to media conflicts section for details on media conflicts and how to remove them. 2. 4. the nbemmcmd -listhosts command will continue to show an NDMP host for each of the media servers on which Remote NDMP was configured. This can 42 Additional NetBackup 6. Prior to NetBackup 6. MDS will unload specific drives on media unload delay on NetBackup 6. imports. 5.0 where any mount request could be autoassigned and manually assigned to any compatible drive. Media specific mount requests (including restores. and so on). Such mount requests can be autoassigned by NetBackup and manually assigned to any compatible drive.

when using the drive_unmount_notify script.conf option (Windows only). The Breece Hill Q47 (TLD) is not supported with NetBackup multiple eject and inject. or libraries such as these may not work properly with NetBackup’s inject/eject features. Spectra Logic Gator). you must merge your original script with the newly installed script in the /usr/openv/volmgr/bin/goodies directory. you can do the following: a. 3. On UNIX. Update the serial number or reconfigure the device causing the new serial number to be stored in the EMM database. Additional NetBackup 6. Some libraries implement different functionality for their media access ports. In such cases. some libraries have front-panel inject/eject features that conflict with NetBackup's use of the media access port (for example. 4. The mount/unmount feature makes a system call to run its callout scripts. then the easiest solution is to rename the scripts or move them from the /usr/openv/volmgr/bin directory. Spectra Logic Bullfrog). ejecting tapes through the media access port of the ATL P3000 or Sun StorEdge L11000 robotic library can lead to the error unable to sense robotic device (applies only to NetBackup Enterprise Server). During testing. 2. Disable runtime serial number checks using the DISABLE_AUTO_PATH_CORRECTION vm. or when the run-time Plug-n-Play code (Windows only) performs serial number checks. the tape drive may be downed). The workaround is to wait until the robot has finished initializing again (checking for media) after the media access port door has been closed. the library initialization period for an empty port lasted for 2 minutes. This can happen when ltid performs automatic path correction. If you have changed this script in any way and would like to retrieve your changes. If you encounter this type of issue with this feature and you are not using the scripts. Other libraries require front-panel interaction when using the media access port (such as. Make sure you read each library’s operator manual thoroughly to gain an understanding of its media access port functionality. To fix this issue.NetBackup Media Manager lead to the device being unusable (for example. before responding (in the NetBackup Administration Console) that the tapes have been removed. place the script in /usr/openv/volmgr/bin directory. After you complete the merge. the shell script drive_unmount_notify has been altered and placed in /usr/openv/volmgr/bin/goodies/ directory along with the drive_mount_notify script.0 Operational Notes 43 .The system call returned the wrong value on a few platforms. For example. causing NetBackup to down drive(s). b. 10 seconds.

cannot connect to tldcd on host <hostname>. If you see this message. With robotic inventory. and knowledge of slot information is not required.NetBackup Media Manager 5. This situation occurs when the daemon/service start occurs too soon after the shutdown. The workaround is to use robotic inventory for managing volumes. and then restart it. or delete volumes that are optical Additional NetBackup 6. such that the full shutdown of all daemons/services does not complete before the daemons/services are started. at the robot inventory stage. only the volumes actually contained in the robot are configured. is not available. This in turn leads to a newly-started daemon/service being terminated by a delayed stop signal. Known Limitations Surrounding Optical Media Support Some optical disk media support is limited (applies only to NetBackup Enterprise Server). ◆ Known optical media support limitations for NetBackup Administration Console for Windows: ◆ Cannot add.0 Operational Notes 44 . or if the barcodes on added volumes could not be verified (for some robot types). Use the vmadm menu interface or the tpformat command to perform this function. ◆ Known optical media support limitations for NetBackup-Java Administration Console: ◆ ◆ No inject or eject capabilities for Single-media access ports. volumes are added to the Enterprise Media Manager volume database. format optical media option. VERITAS recommends that you stop the NetBackup Media Management device daemon (on UNIX) or Device Manager service (on supported Windows servers). Note For detailed information regarding the use of vmadm or tpformat. wait at least 20 to 30 seconds. When configuring robotic volumes with a media management New Volumes/Add Volumes interface. update. label. refer to the NetBackup Media Manager System Administrator’s Guide. restarting the Media Management device daemon (UNIX) or NetBackup Device Manager service (on supported Windows servers) can result in individual robotic daemons not being active. 6. The following two lists define the limitations as they relate to either the NetBackup-Java Administration Console or the NetBackup Administration Console for Windows. The feature. 7. even if an error is reported because one or more volumes were not currently in their specified slots. the inventory fails with a message similar to. Use the vmadm menu interface to perform this function. How do you know if this situation occurs? In the Volume Configuration wizard. In environments where network traffic or machine load is high.

a robot may be selected for robotic inventory when listed with the wrong robot control host. by clicking on the Advanced button in the wizard. possibly causing backups to fail.0 Operational Notes . and as a workaround. 45 Additional NetBackup 6. Inventory during installation results in duplicate media IDs when a robot contains media with the barcodes that are more than 6 characters and the last 6 characters are not unique. format optical media option. The VERITAS implementation using SCSI reserve/release has the following limitations: ◆ ◆ SCSI reserve/release is not applicable for NDMP configurations (no reserve command is available). is not available. This limitation only applies to TLD or TL8 robots that have no drives configured on the robot control host or are using a multimedia robot (for example. which includes Media ID Generation Rules. or Media Manager commands to perform these functions. leading to a robotic inventory that fails because it tried connecting to a robotic control daemon or process on the wrong host. Moves do not recognize optical partners. DLT7000 and DLT8000 in the same library). If media are configured with the wrong media type. To retain reservations of a tape device when doing a third-party copy backup. so if both partners are selected the move may fail. you must use barcode rules (see the NetBackup Media Manager System Administrator’s Guide). vmadm menu interface.conf file in the NetBackup Advanced Client System Administrator’s Guide for UNIX and Windows. 11. 8. Example 1: If your TLD robot has DLT2 drives on a host that is not the robot control host and the robot control host has no configured drives in that robot then you must specify DLT2 as the media type on the inventory robot update.NetBackup Media Manager ◆ No support for moving volume groups. This is a known operational issue. 9. 10. the media will be unmountable. Use the NetBackup Java Administration Console. Example 2: If you are using a multimedia robot. ◆ ◆ No inject capability for single-media access ports The feature. Use the vmadm menu interface or the tpformat command to perform this function. Robot inventory may add media with a media type that is not compatible with the drive type (applies only to NetBackup Enterprise Server). When using NetBackup media management on Windows. the user should choose to use the standard inventory. refer to the description of the mover. Third party copy configurations must be configured correctly.

Some fields that are affected include the Drive Name. Please use tpconfig -l or tpconfig -dl to see the entire field. Limitations exist with the physical inventory utility. vmoprcmd may also truncate the Drive Name. In addition. Note Disabling SCSI reserve/release may result in data loss. But if there is cleaning media in the tape library and the media type of the corresponding volume record that is found is not a cleaning media type. then the NetBackup SCSI reserve/release function must be disabled. The media is skipped and the next media in the list is mounted. Servers that do not have configured pass-through paths to each tape drive should be used with caution in a multi-initiator environment. Cleaning Media Handling: If the media type is specified as a cleaning media type (for example. ◆ ◆ ◆ ◆ API and optical disk library (ODL) robot types are not supported. There is no way to distinguish between volume records based on the application type. vmphyinv does not attempt to mount the media. When moving the media from robotic to standalone drives. 13.0 Operational Notes .NetBackup Media Manager ◆ ◆ Cluster environments or multi-path environments with fail-over capability may leave devices reserved when fail-over occurs. there is no option to move the media to a specific volume group. 14. If path sharing cannot be eliminated. 4mm_clean or dlt_clean) in the volume record corresponding to the cleaning media in the robot. 46 Additional NetBackup 6. Cluster environments or multi-path environments with dynamic path sharing (Tru64 for example) will cause backup and restore failures if the path changes during these operations. or if there is no volume record corresponding to the cleaning media in the Enterprise Media Manager volume database and vmphyinv is used with the slot range or list options. The lack of a pass-through path makes it impossible for NetBackup to issue the SCSI reserve command. 12. and the Drive Path. vmphyinv tries to mount the media continuously until the mount request times out. Using the tpconfig utility options The tpconfig -d utility option may truncate some data if it exceeds a certain threshold.

1b systems should keep current with the latest operating system patch and HBA firmware levels. VERITAS recommends that you perform a test of this function during an idle time on the server. 2.1b systems are scanned. If you want to test a long erase. L5500. if non-current operating system patches and HBA driver firmware are used. However. that are using ovpass to control robots. SL500. A long erase should be avoided on SGI IRIX servers. Enhanced Device Discovery and Auto Configuration This version of NetBackup enhances device discovery by upgrading the Device Configuration Wizard so it now configures robots and drives in StorageTek's Automated Cartridge System Library Software (ACSLS) and ADIC's Scalar Distributed Library Controller (SDLC) libraries. The following drives and libraries report drive serial numbers to ACSLS and allow Auto Configuration: ◆ Drives: T9x40x. Additional NetBackup 6. Device discovery attempts may cause system reboots when Tru64 5.1 and later releases report drive serial numbers by using the display command. Note For NetBackup ACS Robot Auto Configuration to work. you should perform your configurations when no backups are running or about to run. the robot will appear to be missing if the robot control daemon has the robot open at the time a remote system is running auto-discovery. L180. The remote system takes control away from the AIX system leaving the EMM database inconsistent. because system performance may become degraded during this operation. L700e.0 Operational Notes 47 . the ACSLS Server must be able to report the serial numbers of the robotic tape drives. ACSLS can only report serial numbers when the drives report their serial numbers to the library and the library reports the drive serial numbers to ACSLS. DLT 7000 and later drives. ACSLS 6. L20/40/80. ◆ Libraries: SCSI attached and SCSI over Fibre Channel attached STK libraries 97xx. 16. 3).0 environment. This can cause the NetBackup Device Configuration Wizard running on a different host to hang. and SDLT. L700. LTO (Gen 1. To avoid this issue. and SL8500. 17.NetBackup Media Manager 15. On AIX systems. Users of Tru64 5. Note The SGI IRIX media server is not supported in a pure NetBackup 6.

4410.0 Operational Notes . Storage Migrator The Storage Migrator Administration utility does not honor the console’s NBJAVA_CLIENT_PORT_WINDOW option settings.NDMP The following drives and libraries do not report serial numbers to ACSLS and must be configured manually: ◆ Drives: 9490 (TimberLine). NDMP 1. If you only back up the symbolic link. Note NetBackup ACS Robot Auto Configuration will not work with HSC/LibStation attached libraries since LibStation does not report drive serial numbers. If not. only the link file will be restored and not the actual object the link points to. Media Manager Cluster Support Limitations The following limitations have been identified to affect clustering support in Media Manager. the symbolic link must appear before the object itself in the file list. Breaking SCSI Reservations When fail over occurs in an environment where SCSI Reserve/Release is being used (explicitly in NetBackup. The drive will remain unusable by other nodes and other hosts until the SCSI reservation is cleared. 9360 (WolfCreek). if you back up both an object and a symbolic link to the object. you must back up the object of a symbolic link if you want to be able to restore that object. On UNIX systems and when the NetBackup catalog is in binary format. You must configure these devices manually. a SCSI reservation will be left on the drive. ◆ Libraries: 9310 (PowderHorn). 48 Additional NetBackup 6. It will use whatever free local port the operating system provides to connect to its daemon process on the host. or implicitly in lower-level drivers or hardware). Also. 1. SD3 (RedWood) and earlier drives. and serial-attached 9740. the backup may fail.

if a symbolic link points to an object that is one level or more higher. NOM is a 32-bit application that runs on 64-bit-capable Solaris Sparc as a 32-bit application. these alerts are not reflected in the Group Component Summary table displayed at the bottom. File-path includes the file name. NOMAdmin -Purge [Never | Daily | Weekly | Monthly] File-path DoDelete reload-file-path. the DoDelete option must be specified. 3. Additional NetBackup 6. 4. The following known limitations to this product apply for this release of NetBackup. It is recommended that you do not install NOM on a clustered master server. alerts are correctly shown in the summary displayed at the top. An alert policy can be defined for the alert conditions Lost Contact with Media Server or Mount Request. NOM can manage a NetBackup master server that is configured in a cluster environment. The PBX installer will leave dependent NetBackup services stopped. If the entire NOM domain is selected in the monitoring alerts summary view. 6. 1. 8. these limitations do not exist. You must restart these services after NOM is installed. NOM is included with the NetBackup 6. always use the values displayed for cluster name (ignore the values displayed for the server members of the cluster). 7. If the NetBackup catalog is in ASCII format. NOM is not supported on 64-bit Windows operating systems. There are no license keys to install or manage.NetBackup Operations Manager Finally. If you are installing NOM on a NetBackup master server. but no alerts are raised and no alert notifications are sent for either condition. ensure that NetBackup is idle (not doing any critical operations).0 Operational Notes 49 . 9. When viewing services and logs for clustered servers in NOM. Solaris x86 is not supported by NOM. When adding a clustered managed server in NOM. To use the purge command to clean up the NOM database.0 Enterprise Server product at no additional charge. NOM is not a clustered application. NetBackup Operations Manager NOM is a completely new product. 2. But. use the cluster name of the master server rather than the physical machine name for the server. You should back up the object rather than the symbolic link. 5. the backup may fail.

Logs for jobs of policy type Vault are not supported in this release of NOM. The Throughput Variance standard report shows incorrect data for job attempt instances. You are unable to view all of the log messages from NOM interface when a message record contains multiples lines. With the default VxUL debug logging level set to 1. 50 Additional NetBackup 6. 12. The table component that NOM uses in monitoring and reporting only supports fixed width tables without horizontal scrolling. NOM only shows the first line of NetBackup log messages that contain more than one line. some files may be truncated by the NOM server if it runs out of memory. some tables in NOM will be unreadable due to shortage of screen real-estate. If NOM stops logging messages. filtering for cleaning media or frozen media) is not operational in this release. examine the nblog. The following localization issue applies only to NOM software installed on Solaris servers. 15. NOM produces extensive debug messages. 17. email notification will not be sent. The remedy is to reduce the number of selected columns to view using the Table Settings icon or expand the column width using the mouse (this icon is not available with reports).0 Operational Notes . When Vault logs are viewed. 13. 10. 16. if extensive debug messages are not required. This happens because the details table does not include a row for the count of domain level alerts. 14. When viewing log files. alert policy names should be entered in English when an alert policy is created.conf file with an editor to set the log level. 19. This may occur when processing larger log files. the total alert count shown in the details table does not match the total number of alerts in Alert Summary Panel window. Set the debug level to 0. Otherwise. Media filtering (for example. NOM displays the retention level for media as an integer value instead of showing the currently associated retention period with the integer. no logs are returned or the NOM server returns an error exception. Custom filters created when using Netscape are not seen from Windows Internet Explorer. making sure that there are no trailing spaces. 11. 18.NetBackup Operations Manager Also in the monitoring alerts detail view. Therefore. If the system locale (where the NOM server is installed) is Japanese or Chinese.

21. User authentication fails (User authentication failed) when you try to log in with Unixpasswd user or NIS user when Root+AB is installed on windows. The wait will depend on system performance and can be in the order of minutes. 20. When the task "Enable All Logs" is used from the Managing -> Host Properties view.NetBackup Operations Manager The NOM UI initializes a user’s personal preferences and various settings such as filter definitions and column settings. as shown in the following figure. When NOM is used on a Windows server. Also.0 Operational Notes 51 . from disk on startup and keeps any changes made during the session in memory and saves them to disk at session logout. Please wait for the operation to complete. changes made in one session may get overwritten by another session. This window can be resized to show all conditions by grabbing and dragging the icon at the right bottom corner of the window. and does not contain a scroll bar. users in NIS and Unixpasswd domains can not be used. Therefore changes made in one session are private and will not be visible in another session. Additional NetBackup 6. 22. the browser will appear to hang for the duration it takes to perform the operation on the NetBackup server. The NOM alert policy conditions window in a Netscape browser does not show all available conditions and descriptions.

NetBackup Operations Manager The following tables update the supported platforms and browser tables that were published in the NetBackup 6. This is achieved by updating the addon_medialist file in the session directory. users can eject and vault media that are managed by Media Manager but not created by NetBackup or Vault. The command line interface for the parsable output from the Vault reports is not published. NetBackup Vault 1. it will not fail the job.0 Operational Notes .NetBackup Vault 23. The job will succeed if the regular media was ejected successfully. Using the vlt_ejectlist_notify script. In this case. Check the support web site for the current operating system compatability list for NetBackup for any additional support changes that may occur. use unique names that are less than 60 characters. NOM truncates Email and SNMP recipient names and master server group names to 60 characters. Platforms Supported for the NOM Server NetBackup Operations Manager server software can be installed on the following operating system platforms: Operating System Windows 2000 Windows Server 2003 Solaris Supported Versions 2000 SP4 2003 SP1 8 Notes No 64 bit support No 64 bit support SUN SPARC No 64 bit support Solaris 9 SUN SPARC No 64 bit support 52 Additional NetBackup 6. 2. Note however that even if Vault fails to eject one or more of such media for whatever reason.0 release notes.

SP.0 SLES9 Intel-32 bit Intel-32 bit Intel-32 bit Intel-32 bit Additional NetBackup 6. pServer 32 bit Redhat Enterprise Linux Redhat Enterprise Linux Redhat Enterprise Linux SuSE SLES 2.0 4.NetBackup Operations Manager Operating System Solaris Supported Versions 10 Notes SUN SPARC No 64 bit support NetBackup Managed Master Server Platforms Supported by NOM NetBackup Operations Manager software supports management and monitoring of NetBackup master servers on the following operating systems: Operating System Windows 2000 Windows Server 2003 Solaris Supported Versions 2000 SP4 2003 SP1 8 Notes No 64 bit support No 64 bit support SUN SPARC No 64 bit support Solaris 9 SUN SPARC No 64 bit support Solaris 10 SUN SPARC No 64 bit support HP-UX HP-UX AIX 11.2 IBM RS6000/.1 HP9000-PA-RISC HP9000-PA-RISC IBM RS6000/. pServer 32 bit AIX 5.1 3.0 11i 5.0 Operational Notes 53 . SP.

0 7. Supported on Solaris.NetBackup Operations Manager Web Browsers Supported by NOM The NetBackup Operations Manager user interface (the NOM console) is supported with the following web browsers: Web Browser Microsoft Internet Explorer NetScape NetScape Supported Versions 6. 54 Additional NetBackup 6.2 7.0 Notes Supported on Microsoft Windows.0 Operational Notes . Supported on Microsoft Windows.

Sign up to vote on this title
UsefulNot useful