Veritas NetBackup Vault™ Administrator’s Guide

UNIX, Windows, and Linux

Release 6.5

12308354

Veritas NetBackup Vault Administrator’s Guide
Copyright © 2001–2007 Symantec Corporation. All rights reserved. NetBackup Vault 6.5 PN: Symantec, the Symantec logo, NetBackup Vault are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Printed in the United States of America.

Third-party legal notices
Third-party software may be recommended, distributed, embedded, or bundled with this Veritas product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying release notes.

Licensing and registration
Veritas NetBackup Vault is a licensed product. See the NetBackup Vault Administrator’s Guide for license installation instructions.

Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service.

Contents

Chapter 1

Introduction to Vault
Vault uses NetBackup functions ........................................................................13 How to access NetBackup Vault ........................................................................14 Vault original or duplicate images? ..................................................................15 The Vault process ................................................................................................15 Choose backup images ................................................................................16 Duplicate backup images ............................................................................16 Back up the NetBackup catalog ..................................................................16 Eject media ....................................................................................................17 Generate reports ..........................................................................................17 How Vault uses volume groups and pools .......................................................17 NetBackup and Vault configuration .................................................................18 Vault management procedures ..........................................................................18

Chapter 2

Installing Vault
Supported systems ..............................................................................................21 Supported robots .................................................................................................21 Upgrading to NetBackup Vault 6.5 ...................................................................22 The upgrade conversion process ...............................................................22 Configuration elements that are converted from pre-6.0 vault configuration 24 Your responsibilities after a successful upgrade ....................................26 UNIX and Linux systems ....................................................................................27 Installation prerequisites for UNIX and Linux systems ........................27 Installing NetBackup Vault on UNIX and Linux systems ......................27 Upgrading NetBackup Vault on UNIX and Linux systems ....................29 Uninstalling NetBackup Vault from UNIX and Linux systems ............31 Microsoft Windows systems ..............................................................................34 Licensing prerequisites for a Windows system .......................................34 Licensing NetBackup Vault on a Windows system .................................34 Upgrading NetBackup Vault on a Windows system ...............................35 Uninstalling NetBackup Vault from a Windows system .......................35 Upgrading from bpvault 3.4 ...............................................................................36

Chapter 3

Best practices

................ 53 Create originals concurrently ........................................................................................ 40 Resolve multiple names for a single server ................................................................................................................ 41 Specify robotic volume group when configuring a Vault ........................................ 59 Ensure report integrity ................................... 53 Use alternate read server ..................................................................... 55 Use Storage units that specify a media server ....................................................................................................................................................................................... 39 Ensure all data is vaulted ......................................... 38 Vault original backups ....................................... 44 Use precise naming conventions for volume pools and groups ....... 37 Preferred vaulting strategies ............................ 54 Use advanced duplication configuration ...................................................................... 45 Suspend vaulted media ................ 47 Avoid resource contention during duplication ...................... 42 Send only the intended backups off-site ..................................................... 40 Overlap the time window in the profile .................................................................. 41 Do not Vault more than you need to ............. 42 Vaulting original backups in a 24x7 environment ................................................................................................................ 59 Organizing reports by robot .................................................................................................................... 46 Revault unexpired media .................................................................................. 44 Vault NetBackup catalogs .......................................................................................................... 56 Increase duplication throughput ............... 45 Match volume pools to data usage .... 47 When two processes try to use the same drive ............... 60 Consequences of sharing an off-site volume group across multiple robots 60 ..................................... 53 Avoid sending duplicates over the network ..........................................................6 Vaulting paradigm ............................... 42 Avoid vaulting partial images ............................................... 43 Preparing for efficient recovery ........... 47 Media ejection recommendations ..... 56 Multiple-drive scenario: Does not send data over network ......................................................................... 52 Specify different volume pools for source and destination ................................................................................................................... 51 Load balancing ............ 58 Use scratch volume pools ...................................................................................................................... 56 Configuring for multiple-drives: Basics .......................................................... 45 Designate a primary copy and keep it on site ................................................................................................................. 39 Use disk staging ....... 60 Organizing reports by profile ................................................................ 53 Use a separate volume pool for each Vault ................................................................................................................................................... 57 Maximize drive utilization during duplication ........... 59 Organizing reports by Vault ................... 51 Sharing resources with backup jobs .................................................................................. 47 When the read drive is not in the Vault robot ..........................................................................

.....114 Eject tab ..................................76 Retention mappings tab ................................60 Chapter 4 Configuring NetBackup for Vault Off-site volume pools ...................................................................................................................................................................84 Vault dialog box ..........................................................................................................................................................................................................................................................................................................................................................83 Requirements for creating a Vault .................................98 Catalog backup tab ...........................................................133 Running multiple sessions simultaneously ...124 Chapter 6 Vaulting and managing media Running a Vault session .........................................................69 Chapter 5 Configuring Vault Information required to configure Vault .65 Master server properties for Vault ................................................................................................................................................ media servers........................................................73 Configuring Vault management properties ......................................................................................................69 Setting the maximum number of Vault jobs ................74 Alternate media server names tab ........................82 Vault robot dialog box .130 Scheduling a Vault session .................................................88 Profile dialog box .................................................................................................................7 Generate the lost media report regularly .....83 How to create a Vault .....80 Configuring robots for Vault ..71 Master server......................134 ...................................118 Reports tab .......................................................................................89 How to create a profile ................................................................................................................................................................................................................................................................................79 Reports tab ...........................................................................................................................................................................92 Duplication tab .............72 Robot information .........................................................................................................130 Running a session manually ..............................................64 Catalog backup schedules for Vault ...............90 Configuring a profile ............... and storage units ...................................65 Creating a Vault catalog backup schedule ..................63 Creating a volume pool ...............82 Creating a Vault ...............................................................................................................................................................89 The number of profiles required ............................................................................................84 Creating a profile ..............74 Vault Management Properties General tab ...............................................................................................................73 Methods of configuration .......................................................................................................................................................................90 Choose backups tab ...................................................

............... 138 Extended error codes ....................................... 168 Notify script for a specific profile ................................... 167 Notify script for a specific Vault ....................................................................... 146 Injecting media .......................................................................................................... 148 Injecting media by using the Vault operator menu .........................................162 Vaulting VSM media ....................................................................................... 140 Vault resiliency ............................................................................................................................ 150 Vaulting media in containers ..........................................................................................................................................................8 Previewing a Vault session .......................................... 156 Vaulting additional volumes .............................................................................................................................................................136 Detailed Vault job status ................................... 143 Ejecting media by using the vlteject command ................................... 145 Consolidating ejects ............................................ 144 Ejecting media by using a Vault policy ............................................................................................... 166 Using notify scripts ......................... 159 Duplicating a volume by using Vault ......................................................................... 165 Notifying a tape operator when eject begins ............................................................................. 169 Restoring data from vaulted media ............................................................................................................................................................. 135 Resuming a Vault session ............... 166 Notify script for a specific robot ............................................................................. 138 The list of images to be vaulted .................................... 149 Injecting media by using the vltinject command ...................................................................................................................................................... 155 Assigning multiple retentions with one profile ..... 158 Duplicating a volume manually .......................139 Ejection exclusions ..............146 Injecting media by using the NetBackup Administration Console ............................................................................. 138 Duplication exclusions ............................................................. 171 ............................................... 141 Ejecting media by using the NetBackup Administration Console ............................ 140 Previewing media to be ejected ......... 142 Ejecting media by using the Vault operator menu ................................................ 136 Monitoring a Vault session ..... 153 Reporting on containers and media ................................................................................................................................ 149 Using containers ................. 151 Managing containers and media ........................ 168 Deassigning vaulted NetBackup catalog media ...........................................135 Stopping a Vault session ............. 168 Clearing the media description field .................................................................................................................................................................................................................................................................... 170 Replacing damaged media .................................................................................................168 Order of execution ................................ 160 Revaulting unexpired media ................................................................................ 163 Vaulting media not created by NetBackup ............................... 140 Ejecting media ...... 160 Tracking volumes not ejected by Vault .............................................

.....................................................................................................................211 Recovery Report for Vault ............................222 Session logs .............218 Printing Vault and profile information ...............................................................220 Moving a Vault to a different robot .................................179 Fail all copies .....................180 Creating duplicate images concurrently ........................208 Container inventory report ...................217 Administering access to Vault ............221 Changing volume pools and groups ...............................................................................................................................221 Vault session log files ...............................................................179 Creating original images concurrently ..............220 Copying a profile ............................................................................................................................................218 Vault Operator user group ..............................................................................................................201 Reports for media going off-site ...............................................................................................................................................196 Generating reports by using the vlteject command ....................................................................................................................214 Iron mountain FTP file .......200 Vault report types .....................................198 Viewing reports ............................224 ............212 Lost Media report .............183 Concurrent copies during basic duplication ...................189 Chapter 8 Reporting Generating reports ..................................213 Non-vaulted Images Exception report ............178 Continue copies ......224 Vaulting Storage migrator files .............................................................................................................................................................................................................................................................197 Consolidating reports ....................................177 Continue or fail for concurrent copies ................182 Concurrent copies through the catalog node ........................................................................9 Chapter 7 Creating originals or copies concurrently Understanding concurrent copies ..................................................222 Setting the duration of Vault session files .....................................................195 Generating reports by using the Vault operator menu ................................................................................................................................................................................................................223 General operational issues .......................................................................................215 Chapter 9 Administering Vault Setting up E-mail ................................................................................................................................................181 When duplication is possible .............................................................................................................................................................185 Concurrent copies during advanced duplication ............196 Generating reports by using a Vault policy ..................................................................................................................................................................201 Reports for media coming on-site .........................................................205 Inventory reports ....................

.................................................................... 231 Chapter 11 Troubleshooting Printing problems ............................................................................................................. 237 Ejecting tapes while in use ............................................................................................................................................. 227 Additions to volume configuration ............ 236 Need to Stop Bpvault .................................................................. 241 Definition of disaster ........................................................................................................................................................................................................................................................................ 246 Recovering NetBackup ...................................... 242 Definition of disaster recovery ............................. 238 Unexpired tapes were injected into the robot ......................................... 238 Debug logs ..................................................................... 235 Tape drive or robot offline .................................................................................................................... 234 Bad or missing duplicate tape ............................... 238 Setting the duration and level of logs ................... 239 Logs to accompany problem reports ....10 Disk only source of backups ............................................. 234 Media is missing in robot ...................................228 Changes to the special actions menu ............................................................................................................................................................................................................................................. 224 Chapter 10 Using the menu user interfaces Using the Vault administration interface ........................................ 243 Developing a disaster recovery plan ........................................................ 228 Changes to display options ......245 Preparing for recovery ................................................................237 Tapes not removed from the MAP ..................................................................236 No duplicate progress message .............................................................................................................................. 234 No media are ejected .... 230 Changes in bpdbjobs for Vault ..............................................................................................248 Recovering to a specific point in time ...... 224 The scope of the source volume group ............................................. 243 Recovery priorities .............................................................................................................................................................................. 225 Using the Vault operator menu interface ....................................................... 245 Disaster recovery in the NetBackup Vault context ..... 242 Definition of disaster recovery plan ............ 240 Appendix A Recovering from disasters Introduction ............................................................ 233 Errors returned by the Vault session .................... 250 ................................................... 244 Testing a disaster recovery plan ................................................................................................................. 226 Changes in vmadm for Vault ............................................................................................ 248 Recovering data .........................................................

.....................................................................253 Windows files and directories ..............257 Index 263 .........................................................11 Appendix B Vault’s file and directory structure UNIX files and directories ...............

12 .

Information from Vault is integrated with other NetBackup components and appears in the NetBackup Activity Monitor. see the following: ■ ■ ■ ■ ■ ■ ■ “Vault uses NetBackup functions” on page 13 “How to access NetBackup Vault” on page 14 “Vault original or duplicate images?” on page 15 “The Vault process” on page 15 “How Vault uses volume groups and pools” on page 17 “NetBackup and Vault configuration” on page 18 “Vault management procedures” on page 18 Vault uses NetBackup functions NetBackup Vault uses existing NetBackup functions for all operations. reporting. such as duplication of images.Chapter 1 Introduction to Vault Vault is an extension to NetBackup that automates selection and duplication of backup images and ejection of media for transfer to and from a separate. you can use Vault to manage data and media that you store off-site for regulatory archival purposes. NetBackup Vault interacts with the following NetBackup services and catalogs: ■ ■ Media Manager manages robots and media. off-site storage facility. Vault functionality does not have to be used only for disaster recovery. media control. The NetBackup catalog and the Media Manager database record which images have been vaulted. NetBackup Vault also generates reports to track the location and content of the media. . For more information. and ejecting and injecting of tapes.

. and Vault relationships: Figure 1-1 Services interaction diagram Vault * Chooses images to vault * Requests duplication. Alternatively. If you added the appropriate license key during the installation of Vault or by using the Help > License Keys option of the NetBackup Administration Console. The Activity Monitor displays the status of the Vault job. Media Manager. you can manage Vault by using the following methods: ■ Menu-based user interfaces. monitors duplication * Assigns media to vault slot or container * Requests media eject * Maintains OS level file security * Requests return of expired media from the vault * Requests catalog backup Vault Reports * Pick list of media ejected from robot * Pick list of expired media in the vault * Inventory reports * Recovery report NetBackup Backup/Restore Services * Duplicates images * Tracks images on media * Duplicates catalog Media Manager * Manages robotic devices and volumes * Tracks volume location * Ejects and injects media Activity Monitor * Monitors all services How to access NetBackup Vault NetBackup Vault is installed on a NetBackup master server. You can use the Administration Console to configure and manage Vault. ■ The following diagram shows the NetBackup. Vault Management will be a node of the Administration Console.14 Introduction to Vault How to access NetBackup Vault ■ The Media Manager database information determines when expired media can be returned to the robot for reuse.

all are considered originals. For more information about the specific steps in a Vault process. Duplicate images are copies created by Vault.Introduction to Vault Vault original or duplicate images? 15 ■ Command line utilities. see the following. you can use one job to select and duplicate images daily. NetBackup can create up to four copies of an image concurrently during the backup process. which briefly describes a basic Vault process: ■ ■ ■ ■ ■ Choose backup images Duplicate backup images Back up the NetBackup catalog Eject media Generate reports A Vault job must select images (Choose Backups). including all copies created concurrently by a backup policy. If you create multiple original backups in a NetBackup policy job. you should assign the first original (the primary copy) to the volume pool for media that remains on site and send a copy off site. If you send original images off site. Injecting returned media back into the robot is a manual operation. Vault distinguishes between original images and duplicate images as follows: ■ Original images are created by NetBackup during a backup job. The other steps are optional so you can separate the Vault tasks into separate jobs if desired. using different jobs to accomplish different tasks. ■ The Vault process Vaulting is the process of sending backup images off site to a protected storage location. . A Vault job reads the primary backup image and writes one or more duplicate images concurrently. you do not have to duplicate images and therefore do not have to configure duplication. the Vault job is separate from the NetBackup policy job. and another job to eject media and generate reports weekly. The Vault reports include the media that should be recalled from the off-site location and injected into the robot. For example. Vault original or duplicate images? One of your most important choices is whether to send original or duplicate images off site.

This step. you do not have to duplicate images in Vault and therefore do not have to configure the duplication step. duplicating images. The catalogs also have information about the media and storage devices that are under the control of Media Manager. Vault uses the primary backup image as the source image for the duplication operation (exception: to improve performance. writes copies of backup images on media that you can eject and transfer off site.16 Introduction to Vault The Vault process The term vault also refers both to a logical entity associated with a particular robot and to the off-site storage location of a set of tapes. The NetBackup catalog consists of databases of information about the NetBackup configuration and any backups that have been performed. Vault uses the criteria in a Vault profile (a set of rules for selecting images. However. Image duplication is optional. If you duplicate images. that original image must be written to media in the off-site volume pool so it will be ejected and transferred off site. However. Duplicate backup images The second step of the Vault process is duplicating the backup images that are candidates to be transferred off site. . The information about backups includes records of the files and the media on which the files are stored. known as image duplication. Vault can send original images off site (depending on the profile rules). Back up the NetBackup catalog The third step of the Vault process is backing up the NetBackup catalog. known as image selection. vaulting a catalog backup with your data can help you recover from a disaster more efficiently. must be configured for every Vault job. This step. and ejecting media) to determine which backup images are candidates to send off site. Vault does not duplicate the NetBackup catalog. If you send your only backup image off site or create multiple original backup images and send one or more of those off site. Vault will duplicate from a nonprimary copy on disk if one exists). If you create multiple original images concurrently during a backup job. Vault creates its own catalog backup with up-to-date information. Backing up the catalog is optional. including information about media sent off-site. Choose backup images The first step of the Vault process is choosing the backup images that are candidates to be transferred off site.

During a Vault job. Vault ejects that media and then moves it logically to an off-site volume group. How Vault uses volume groups and pools Volume groups identify where volumes reside. Volumes in a robotic volume group reside in a robot. . Volume pools identify logical sets of volumes by usage. Reports can be generated as part of the Vault job or manually after the job is finished. During a Vault job. Vault searches a robot for images that match the selection criteria. Vault searches the robotic volume group for media that matches a profile’s criteria. Vault ejects that media. You and your off-site storage vendor can use the reports to determine which media should be moved between your site and the off-site storage location and the timing of the moves.Introduction to Vault How Vault uses volume groups and pools 17 Eject media The fourth step of the Vault process is ejecting the media that you then transfer to secure storage. if media are found. (A logical move means to change the volume attributes to show the new location. Generate reports The fifth step of the Vault process is generating reports. often at a separate facility. Reports can be generated for each job individually or can be consolidated with a consolidated eject operation. Reports track the media managed by Vault. Vault moves it back into the robotic volume group. They are used as a tracking mechanism by Vault to determine where a volume is located. Media can be ejected for each job individually or can be consolidated into a single eject operation for multiple Vault jobs. Volume pools for images to be transferred off site are known as off-site volume pools. When you create the images that you want to send off site. Generating reports is optional.) When a volume in off-site storage expires and is injected back into the robot. They are used by Vault to determine if a volume should be ejected. Media that are ejected are tracked by Vault reporting facilities and will be recalled from off-site storage for reuse after the images expire. write them to media in an off-site volume pool. Media can be ejected automatically by a scheduled Vault job or manually after the job has completed. if the media the images reside on are in an off-site volume pool.

and so on. Configure Vault profiles. The NetBackup Vault Operator’s Guide provides more detailed information on day-to-day procedures. . Ensure sufficient hardware. and network capacity is available for duplication of backup images. you must configure Vault robots and profiles. you must first set up and configure NetBackup so that volume pools and policies are available to support Vault operations. Operational Procedure Configuration: review backup procedures and determine duplication capacity needed. Choosing Backups: Vault incorporates two new criteria when choosing a backup for vaulting. Read the information in the best practices section. resources. It can help you determine how to setup and configure Vault most effectively for your environment. . Table 1-1 Vault management procedures Staff Responsibilities Determine the need for basic levels of duplication service on a per policy basis. Ensure sufficient media are available for duplicates to run. See “Configuring Vault” on page 71. requirements. service level agreements. Review duplication windows for performance and throughput. After configuring NetBackup for use with Vault. Duplication: set up Vault policies to run vault sessions on a schedule. See “Best practices” on page 37. Vault management procedures The following table summarizes operational procedures for Vault. Monitor volume pool usage. software. Monitor jobs to ensure they start when scheduled.18 Introduction to Vault NetBackup and Vault configuration NetBackup and Vault configuration Before you can begin to use Vault. See “Configuring NetBackup for Vault” on page 63. Determine appropriate servers to run duplications and determine appropriate time windows for running duplication. Determine media requirements and setup initial volume pool for duplication.

and network utilization rates (for example. Ensure errors are reported to appropriate personnel. Set up links between log files and monitoring system for e-mail and/or paging notification. Duplication capacity review: determine capacity planning cycle. Ensure sufficient media available for duplication. Know procedures for restoring duplicated images. Vault operations. backup software. Vault reports: generate reports regularly to ensure that images are duplicated correctly. Use Media Manager to expire/freeze tapes manually when Recall media that was not recalled during normal needed for retrieval from the vault. Backup the catalog: set up a schedule for Vault backup of image catalog. Ensure media available to store catalog. Operational Procedure Monitoring: use the NetBackup Activity Monitor to determine progress. Know how to restore database catalog. . costing factors. Compare report output with ejected and returned media. and so on in case of disaster on Netbackup server(s). Assist in defining requirements for the system infrastructure to use Vault effectively with other computing environment resources. Ensure media going off-site and returning on-site matches reports. including reaction time. Ensure Vault catalog backup occurs. and new requirements. disk capacity). Assist production support to help determine system. Recovery review: test recovery procedures regularly to ensure recovery of essential data from off-site storage.Introduction to Vault Vault management procedures 19 Table 1-1 Vault management procedures (continued) Staff Responsibilities Ensure duplication jobs complete successfully. robotic. Review production duplication cycle for thoroughness. Check duplication volume pools and catalog backup pools for available media.

20 Introduction to Vault Vault management procedures .

and peripherals also apply to Vault. The following topics are covered: ■ ■ ■ ■ ■ ■ “Supported systems” on page 21 “Supported robots” on page 21 “Upgrading to NetBackup Vault 6. Exception: Vault does not support standalone drives.4” on page 36 Supported systems Vault runs on the same operating systems and versions and in the same clustering environments as NetBackup except as noted in the NetBackup Release Notes.5” on page 22 “UNIX and Linux systems” on page 27 “Microsoft Windows systems” on page 34 “Upgrading from bpvault 3. NetBackup restrictions and limitations related to systems. clusters. For information about supported systems and supported upgrade paths. Symantec recommends that you use robots that have media access ports and barcode readers.Chapter 2 Installing Vault This chapter outlines the steps required to install NetBackup Vault on both UNIX and Windows systems. Supported robots Vault supports all Media Manager-supported robot types except optical disk library (ODL) robots. see the NetBackup Release Notes. . For best performance and to avoid user errors when entering media IDs. Vault also supports robots that do not have media access ports and barcode readers.

The upgrade conversion process The Vault configuration is converted to the 6.xml. see “Media ejection overview” on page 119.log.0 vault configuration. see the NetBackup Release Notes or the appropriate sections in this administrator’s guide. The upgrade conversion process first creates a saved version of the existing Vault configuration file: ■ UNIX /usr/openv/netbackup/db/vault/vault. Upgrading to NetBackup Vault 6.xml.22 Installing Vault Upgrading to NetBackup Vault 6.5 Changes in NetBackup and Vault beginning with the 6.5 format when the new NetBackup Vault Manager (nbvault) is first invoked at the end of an upgrade installation of NetBackup (on Windows) or Vault (UNIX and Linux).5 release require corresponding changes to the Vault configuration during the upgrade process. YYYMMDD-HHMMSS ■ Windows install_path\db\vault\vault.5 For information about how to use Vault with robots that do not have media access ports.save. YYYYMMDD-HHMMSS It then converts/upgrades the Vault configuration file: ■ UNIX /usr/openv/netbackup/db/vault/vault.log.save.xml ■ Windows install_path\db\vault\vault. YYYYMMDD-HHMMSS . For more information about the new features and capabilities mentioned in this upgrade information. Most of the changes are required only if upgrading from pre-6. YYYYMMDD-HHMMSS ■ Windows install_path\db\vault\nbvault-upgrade.xml Upgrade conversion log The Vault upgrade conversion process writes messages of all of its activity in a log file with the following name (YYYYMMDD-HHMMSS is the timestamp of the upgrade): ■ UNIX /usr/openv/netbackup/db/vault/nbvault-upgrade.

5 format and nbvault starts in service/daemon mode.) . In that case. If you have a separate Vault license key. nbvault does not start in service/daemon mode. and the existing Vault configuration file remains unchanged. take corrective action. 2 3 Upgrade information also is written to the nbvault log (see “Debug logs” on page 238) but it depends on the existence of the log directory and the log level settings of Vault. Vault will not work. Successful conversion If the upgrade conversion succeeded. If the conversion fails. you must add the Vault license key and then start the nbvault service manually. Repeat the preceding steps to resolve the reason for failure. (This note does not apply to UNIX or Linux systems. nbvault then attempts to upgrade the Vault configuration. in which you can see the result of the upgrade.Installing Vault Upgrading to NetBackup Vault 6. nbvault attempts to upgrade the Vault configuration file. read the event log (on Windows) or system log (on UNIX or Linux) for more details. Note: On Windows systems.5 23 The information written to the upgrade log file does not depend on any of the NetBackup or Vault log level settings. the existing vault configuration file is converted to the 6. You can confirm this by reading the upgrade log file. You must read the upgrade log after the installation is completed so that you understand the changes made in your Vault configuration and what you have to do after a successful upgrade. If the upgrade log file does not exist. nbvault will not start in service/daemon mode. Based on the information in the log file. For every upgrade attempt. the nbvault service only starts automatically if you have a combined license key for both NetBackup and Vault. Failed conversion If the upgrade conversion fails. nbvault creates a new upgrade log file. do the following: 1 Read the upgrade log file to determine the details of the failure. Because the NetBackup Vault Manager must be running. If the upgrade fails again. Start the nbvault service/daemon manually. nbvault failed even before attempting to upgrade the vault configuration file.

Following are the changes made to the Vault configuration file: ■ Retention mappings. All retention mapping information (from files such as retention_mappings and retention_mappings. Report distribution. Vault uses the hot. they will be set to use the values from Robot or Vault Management Properties level. At the robot level (Vault Robot dialog box).5. You can no longer specify catalog paths or extra paths to include in the catalog ■ . The new eject notification values are set as follows: ■ ■ ■ ■ Blank at the Vault Management Properties level.vault_name. Note: A NetBackup 6. In previous releases.save. Report distribution values in each profile are propagated to each individual report in that profile.5 Configuration elements that are converted from pre-6. At the profile level. The upgrade log file will contain a list all of the existing two-phase catalog policies and warn that they will be ignored after the upgrade. online catalog backup method for catalog backups. Eject notification e-mail addresses. This method requires a catalog backup policy (NBU-Catalog) that has a Vault Catalog Backup schedule. regular (one volume only) and two-phase.0 Vault configuration requires only some formatting changes to upgrade it to NetBackup 6.0 vault configuration Most of the upgrade conversion changes are required for the new catalog backup method.24 Installing Vault Upgrading to NetBackup Vault 6. The following are the changes to the Vault configuration for the new catalog backup method: ■ All of the existing two-phase catalog backup policies will be removed. The existing retention mapping files are obsolete and are renamed to: retention_mappings.save. Vault no longer supports the legacy catalog backup methods.YYYYMMDD-HHMMSS and retention_mappings.YYYYMMDD-HHMMSS respectively. The new report distribution values at the Vault Management Properties level are set to blank. You can remove them later. All existing user-specified catalog paths will be removed. they will be set to use the values from Vault Management Properties level. ■ ■ Catalog backup. report distribution was configured at the profile level only.vault_name) are added to the Vault configuration file.

newly created volume pool. where VltCat-MyVault-0 is the newly created catalog backup volume pool). ■ ■ After the upgrade succeeds.Installing Vault Upgrading to NetBackup Vault 6.5 25 backup. For every vault that has at least one profile with the catalog backup step enabled. a new volume pool (marked for catalog backup) will be created with a unique name (such as VltCat-MyVault-0. After the upgrade. However. you must add media to them before running Vault sessions after the upgrade. for every unique combination of storage unit. Note that the Vault catalog backup does not include data from critical policies that are in the catalog backup policy. profiles will not use the catalog volume pools that they used before the upgrade. The new schedules will be created in the newly created catalog backup policy (VltCat-Backup-0). and they are backed up automatically. a new Vault Catalog Backup schedule will be created that has the following attributes (or an existing schedule will be used if one matches the following attributes): ■ ■ ■ The storage unit will be the first storage unit that the upgrade process finds on the media server used by the existing profile’s catalog backup. The upgrade log file will contain a list all of the existing user-specified catalog paths used in profiles and warn that they will be ignored after the upgrade. volume pool. Every profile that has a catalog backup step configured will be converted to use this policy to back up the catalog. a new Vault Catalog Backup schedule will be created with a unique name (such as VltCat-MyVault-0-SCHED-0. Paths to all files required for a catalog backup are part of the new catalog backup implementation. all the existing values (such as media server. Note: The upgrade process does not move any media to these volume pools. the existing volume pools will be added to the list of off-site volume pools in the eject step (if they are not already added) so that volumes in these pools that are already off-site will be recalled when they expire. For every profile that has a catalog backup step configured. ■ The existing retention period (which is specified in number of days) will be converted to a matching retention level. where MyVault is the vault name). The volume pool will be the new catalog volume pool created for that vault’s catalog backup. ■ A new catalog backup policy (of type NBU-Catalog) with a unique name (such as VltCat-Backup-0) will be created with default values. and converted retention level. and so on) from the catalog backup step of profiles . The profiles will be converted to use volumes from these new pools to back up the catalog. Therefore.

Read the upgrade log file to understand them. Note the retention levels of the new catalog backup schedules. (As noted earlier. and Vault Catalog Backup schedules that are created and how the upgraded Vault profiles use them.5. Note the new volume pools (of type Catalog Backup). Especially consider the following: ■ Note which configuration items are not supported or are ignored in 6. such as the previous catalog (or extra) paths in the Vault catalog backups and the two-phase catalog policies that are removed from the catalog backup steps of the modified profiles. you can redefine a retention level in NetBackup so it matches the original retention period. ■ ■ You also must add volumes to the newly created volume pools (of type Catalog Backup) so the converted profiles can use them to perform catalog backups.5 that perform catalog backup will be removed from the Vault configuration file and will be replaced by the new catalog backup policy and the new Vault Catalog Backup schedules.26 Installing Vault Upgrading to NetBackup Vault 6. and then change the new catalog backup schedule so it uses the redefined retention level. you can remove these volume pools from the list of off-site volume pools if you use these volume pools only for catalog backup in Vault. ■ Your responsibilities after a successful upgrade You must read each and every statement written to the upgrade log file before you start using the upgraded Vault configuration. Other. existing volume pools specified in the catalog backup step will be added to the list of off-site volume pools in the eject step (if they are not already added) so that volumes in these pools that are already off-site will be recalled when they expire.5 format. you must add media to these new volume pools. the new retention level may not exactly match the original retention period. miscellaneous changes will be made in the vault configuration file to upgrade it to the 6. catalog backup policies. For every profile that has catalog backup configured. After all pre-6. . The upgrade conversion script assigns a retention level that is closest to the retention period of the original catalog backup step. therefore. If it does not match.5 catalog backup volumes are recalled. ■ Eject. Miscellaneous.) Also. the new catalog backup volume pool (used in the Vault Catalog Backup schedule) will be added to the list of off-site volume pools in the profile’s eject step.

and you must install the same version of Vault as NetBackup. For instructions about installing NetBackup. To install NetBackup Vault on a UNIX server Note: If you are installing Vault in a cluster environment. see the NetBackup High Availability Administrator’s Guide.Installing Vault UNIX and Linux systems 27 UNIX and Linux systems You can install and uninstall NetBackup Vault on UNIX and Linux systems. 1 2 Log in as the root user on the system on which the NetBackup master server is installed. see “Upgrading NetBackup Vault on UNIX and Linux systems” on page 29. you must freeze the active node before you begin the installation process so that migrations do not occur during installation. You cannot install Vault on a NetBackup media server or on a NetBackup client. Installation prerequisites for UNIX and Linux systems ■ ■ You must install a NetBackup master server on the UNIX or Linux system. For information about where the various Vault components are installed. Verify that a valid license key for Vault has been registered by executing the following command to list and add keys: /usr/openv/netbackup/bin/admincmd/get_license_key 3 4 Insert the CD that contains the Vault software into the CD-ROM drive. If you are installing Vault in a cluster environment. see “Vault’s file and directory structure” on page 253. NetBackup must be installed before you can install Vault. You must have a valid NetBackup Vault license key. ■ Installing NetBackup Vault on UNIX and Linux systems Use this procedure to do an initial installation on a UNIX or Linux system. If you are upgrading Vault. cd /cd_rom_directory . see the NetBackup Installation Guide for UNIX and Linux. you must install Vault on all systems in the cluster on which NetBackup master servers are installed. For information about freezing a service group. Change the working directory to the CD-ROM directory.

regardless of which cluster server is currently active. See “Configuring Vault management properties” on page 74. if appropriate. You should configure the e-mail address for notification of session status and enter alternate media server names. complete step 1 through step 10 for each node on which you installed a NetBackup master server. you can configure Vault by using the NetBackup Administration Console connected through the NetBackup virtual server name. In a cluster environment. 6 7 8 9 10 Enter q to quit the Installation Options menu. Please read the following chapters so you will develop an understanding of how Vault works and how best to configure Vault for your operations. . Enter q to quit the menu. 5 Enter the following command: . the Installation Options menu appears. answer y. Select the NetBackup Vault option. Note: If you are installing Vault in a cluster environment. you may need to mount this directory. When asked if the list is correct. see the NetBackup Installation Guide for UNIX and Linux. see the NetBackup High Availability Administrator’s Guide. A menu of NetBackup product options is displayed. you must configure appropriate NetBackup attributes for use by Vault and identify which NetBackup policies you want to use with Vault (or create new ones to use with Vault). When completed. 12 Start the NetBackup Administration Console by entering the following command: /usr/openv/netbackup/bin/jnbSA& To complete a new installation. Select the NetBackup Add-On Product Software option. For information about unfreezing a service group.28 Installing Vault UNIX and Linux systems Where cd_rom_directory is the path to the directory where you can access the CD-ROM. The installation process begins. On some platforms. For instructions on how to mount the directory. unfreeze the active node after the installation completes. 11 In a cluster environment./install The Installation Options menu appears.

5 systems and beyond) Or pkgrm VRTSnbvlt (on systems that are older than NetBackup 6. you may need to mount this directory.n. For information about freezing a service group. Execute the following command to uninstall NetBackup Vault: pkgrm SYMCnbvlt (on NetBackup 6. see the NetBackup High Availability Administrator’s Guide.?. cd /cd_rom_directory 7 8 9 Where cd_rom_directory is the path to the directory where you can access the CD-ROM. you must freeze the active node before you begin the upgrade process so that migrations do not occur during the upgrade. so you will not lose your configuration during the upgrade. Upgrade NetBackup by following the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for UNIX and Linux.q] 6 Enter y.Installing Vault UNIX and Linux systems 29 Upgrading NetBackup Vault on UNIX and Linux systems Use this procedure if you already have Vault installed and are upgrading to a newer version of Vault. For . Change the working directory to the CD-ROM directory. 1 2 Log in as root to the system on which Vault is installed. If you are prompted with a message about super-user permissions and you are asked if you want to continue. Insert the CD that contains the Vault software into the CD-ROM drive. Use one of the following procedures: ■ ■ To upgrade NetBackup Vault on a Solaris system To upgrade NetBackup Vault on a UNIX system other than Solaris To upgrade NetBackup Vault on a Solaris system Note: If you are upgrading Vault in a cluster environment. enter y. On some platforms.5) A message asking if you want to remove the package is displayed: Do you want to remove this package? 3 4 5 Enter y to remove Vault. The package removal process will remove Vault program components but not database and log files. Messages that show the progress of the removal process are displayed until the following message appears: Are you doing this pkgrm as a step in an upgrade process? [y.

delete the following files and directories. 1 2 Log in as root to the system on which Vault is installed. For information about unfreezing a service group./install The Installation Options menu appears. A menu of NetBackup product options is displayed. 16 In a cluster environment. complete step 1 through step 15 for each node on which Vault is installed. 15 Enter q to quit the Installation Options menu. 17 Start the NetBackup Administration Console by entering the following command: /usr/openv/netbackup/bin/jnbSA& To upgrade NetBackup Vault on a UNIX system other than Solaris Note: If you are upgrading Vault in a cluster environment. 10 Enter the following command: . The installation process begins. deleting these items can help ensure that all Vault files installed on the system are the same revision. Although not required. 11 Select the NetBackup Add-On Product Software option.30 Installing Vault UNIX and Linux systems instructions on how to mount the directory. see the NetBackup Installation Guide for UNIX and Linux. the Installation Options menu appears. you must freeze the active node before you begin the upgrade process so that migrations do not occur during the upgrade. unfreeze the active node after upgrading Vault. 14 When asked if the list is correct. answer y. Note: If you are upgrading Vault in a cluster environment. Optionally. 13 Enter q to quit the menu. 12 Select the NetBackup Vault option. rm rm rm rm /usr/openv/netbackup/bin/bpbrmvlt /usr/openv/netbackup/bin/vlt* /usr/openv/netbackup/bin/goodies/vlt* -rf /usr/openv/netbackup/help/vltadm . see the NetBackup High Availability Administrator’s Guide. For information about freezing a service group. When completed. see the NetBackup High Availability Administrator’s Guide.

answer y.Installing Vault UNIX and Linux systems 31 3 4 5 Upgrade NetBackup by following the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for UNIX and Linux. On some platforms. For information about unfreezing a service group. Change the working directory to the CD-ROM directory. 7 8 9 10 When asked if the list is correct. 12 In a cluster environment. Uninstalling NetBackup Vault from UNIX and Linux systems The following instructions describe how to remove Vault permanently from a UNIX system without uninstalling NetBackup. you should run the NetBackup Administration Console on the primary node in the cluster when you perform Vault configuration./install The Installation Options menu appears. Enter q to quit the menu. For instructions on how to mount the directory. Insert the CD that contains the Vault software into the CD-ROM drive. see the NetBackup High Availability Administrator’s Guide. 13 Start the NetBackup Administration Console by entering the following command: /usr/openv/netbackup/bin/jnbSA& In a cluster environment. Note: If you are upgrading Vault in a cluster environment. Select the NetBackup Add-On Product Software option. When completed. unfreeze the active node after upgrading Vault. . 11 Enter q to quit the Installation Options menu. cd /cd_rom_directory Where cd_rom_directory is the path to the directory where you can access the CD-ROM. 6 Enter the following command: . the Installation Options menu appears. complete step 1 through step 11 for each node on which you are installing a NetBackup master server. you may need to mount this directory. see the NetBackup Installation Guide for UNIX and Linux. Select the NetBackup Vault option. The installation process begins. A menu of NetBackup product options is displayed.

configuration items related to NetBackup are not.q] 5 To remove Vault completely and not upgrade to a newer version. . Messages that show the progress of the removal process are displayed until the following message appears: Are you doing this pkgrm as a step in an upgrade process? [y. Vault policies. Note: If you are removing Vault in a cluster environment. enter y. Messages that ask about removing Vault files will appear. such as volume pools.5 systems and beyond) Or pkgrm VRTSnbvlt (on systems that are older than NetBackup 6. If you are prompted with a message about super-user permissions and you are asked if you want to continue. you must freeze the active node before you begin removing Vault so that migrations do not occur during the removal process.n. Although all Vault program components are removed when Vault is uninstalled. Execute the following command to uninstall NetBackup Vault: pkgrm SYMCnbvlt (on NetBackup 6. The procedure you should follow depends on whether the UNIX system runs the Solaris operating system or some other version of the UNIX operating system.5) A message asking if you want to remove the package is displayed: Do you want to remove this package? 3 4 Enter y to remove Vault. including the Vault database and log files. All Vault components and configuration information are removed during this procedure.?. For information about freezing a service group. Use one of the following procedures: ■ ■ To remove NetBackup Vault from a Solaris System To remove NetBackup Vault from a UNIX system To remove NetBackup Vault from a Solaris system Caution: This process removes Vault completely. see the NetBackup High Availability Administrator’s Guide. enter n.32 Installing Vault UNIX and Linux systems Before you uninstall NetBackup Vault. 1 2 Log in as root to the system on which Vault is installed. you should delete all Vault-specific items from NetBackup. and so on.

including the Vault database and log files. 1 2 Log in as root to the system on which Vault is installed.Installing Vault UNIX and Linux systems 33 6 7 Enter y to each prompt to remove the Vault files. see the NetBackup High Availability Administrator’s Guide. unfreeze the active node after removing Vault from all systems. For information about unfreezing a service group. . complete step 1 through step 6 for each node on which Vault is installed. you must freeze the active node before you begin removing Vault so that migrations do not occur during the removal process. In a cluster environment. For information about unfreezing a service group. unfreeze the active node after removing Vault from all systems. complete step 1 through step 4 for each node on which Vault is installed. To remove NetBackup Vault from a UNIX system other than Solaris Caution: This process removes Vault completely. Note: In a cluster environment. see the NetBackup High Availability Administrator’s Guide. see the NetBackup High Availability Administrator’s Guide. Note: If you are removing Vault in a cluster environment. For information about freezing a service group. Note: In a cluster environment. Remove the following files and directories: rm rm rm rm rm rm rm rm /usr/openv/lib/libvaultservice.s? /usr/openv/netbackup/bin/bpbrmvlt /usr/openv/netbackup/bin/nbvault /usr/openv/netbackup/bin/vlt* /usr/openv/netbackup/bin/goodies/vlt* -rf /usr/openv/netbackup/help/vltadm -rf /usr/openv/netbackup/vault /usr/openv/share/version_vault 3 4 5 Remove the Vault database directory: rm -rf /usr/openv/netbackup/db/vault Remove the Vault log directory if it exist: rm -rf /usr/openv/netbackup/logs/vault In a cluster environment.

including Vault. ■ If you are installing and running a Vault in a cluster environment. Click New to display the Add a new License Key dialog box. For information about where the various Vault components are installed. Enter the NetBackup Vault license key. Licensing prerequisites for a Windows system ■ A NetBackup master server must be installed and running on the Windows computer. Note: If the license key for NetBackup Vault was included in the license key for the base NetBackup product. you must enter the Vault license key before you can use Vault (see “Licensing NetBackup Vault on a Windows system” on page 34). choose Help > License Keys. The NetBackup License Keys dialog box appears. You may have a separate license key specifically for the Vault option. Vault is already licensed. You must have a valid NetBackup Vault license key. you cannot use Vault until you enter the appropriate license key. Vault cannot be installed on a NetBackup media server or on a NetBackup client. . to use Vault. Click Add.34 Installing Vault Microsoft Windows systems Microsoft Windows systems NetBackup Vault is installed on a Windows system when NetBackup is installed. you must license Vault on all systems in the cluster on which NetBackup master servers are installed. To add the Vault license key 1 2 3 4 From the NetBackup Administration console. However. see “Vault’s file and directory structure” on page 253. ■ Licensing NetBackup Vault on a Windows system Although NetBackup Vault is installed during NetBackup installation. you do not have to perform this procedure. you must enter a license key: ■ Your license key may be a single key for the base NetBackup product and all NetBackup add-ons that you are installing. If you have already installed NetBackup and entered the license key. no separate installation procedure is required. If so.

Deleting the Vault configuration ensures that NetBackup does not include anything that was configured for Vault. choose Help > License Keys. Before you delete the Vault license key. NetBackup Vault is no longer available for use. you should remove all Vault-specific configuration items by using the NetBackup Administration Console to delete them. 1 2 From the NetBackup Administration Console. To delete the Vault license key If you are running BMR in a cluster environment. separate from the base NetBackup product license key. you deactivate Vault by deleting the license key from the list of current NetBackup licenses. 5 Click Close to close the NetBackup License Keys dialog box. if appropriate. you must delete the BMR license key on every system in the cluster on which the BMR master server is installed. When the license key is deleted. NetBackup Vault is upgraded at the same time NetBackup is upgraded. . rather. Upgrading NetBackup Vault on a Windows system On Windows systems. Please read the following chapters so you develop an understanding of how Vault works and how best to configure Vault for your operations.Installing Vault Microsoft Windows systems 35 The license key is displayed in the NetBackup License Keys dialog box. To complete a new installation. Uninstalling NetBackup Vault from a Windows system The NetBackup Vault software is not uninstalled. See “Configuring Vault management properties” on page 74. From the list of keys displayed. Be sure to configure an e-mail address for notification of sessions status and enter alternate media server names. select the Vault license key. you must configure appropriate NetBackup attributes for use by Vault and identify which NetBackup policies you want to use with Vault (or create new ones to use with Vault). The NetBackup License Keys dialog box is displayed. such as volume pools. to upgrade NetBackup Vault. Therefore. You can delete the Vault license key only if Vault was licensed with its own license key. follow the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for Windows.

4 To upgrade from bpvault 3. performing the following step will delete your base key and you will be unable to use NetBackup.36 Installing Vault Upgrading from bpvault 3. Upgrading from bpvault 3. If you do not want to delete the NetBackup license key. first upgrade to a NetBackup Vault 4. 3 Click Delete. The Vault license key is deleted from the Current Licenses dialog box. do not continue.4 to NetBackup Vault. .5 release and then follow the upgrade path documented in the NetBackup Release Notes.4 Caution: If NetBackup Vault was included as part of the base product key. and Vault Management is no longer displayed in the NetBackup Administration Console tree.

see the following: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ “Vaulting paradigm” beginning on page 37 “Preferred vaulting strategies” on page 38 “Ensure all data is vaulted” on page 40 “Do not Vault more than you need to” on page 42 “Preparing for efficient recovery” on page 44 “Media ejection recommendations” on page 47 “Avoid resource contention during duplication” on page 47 “Avoid sending duplicates over the network” on page 53 “Increase duplication throughput” on page 56 “Maximize drive utilization during duplication” on page 58 “Use scratch volume pools” on page 59 “Ensure report integrity” on page 59 “Generate the lost media report regularly” on page 60 Vaulting paradigm How you set up and name your vaults and profiles depends on your operations. A best practice recommendation that may provide benefit for one environment may not provide the same benefit for another.Chapter 3 Best practices Vault can be configured to support how your computing or data center environment is set up and how it operates. For example. you . You should evaluate and implement any recommendations based on the benefit to your environment. if you maintain a customer database and a payroll database. For more information.

38 Best practices Preferred vaulting strategies may choose to organize your vaults by data usage and your profiles by time periods. you can set up your vaults by location and your profiles by data type. Because you can produce multiple copies of images during a NetBackup policy job. they can be very beneficial in many environments. fewer drives and less time may be required to create multiple original copies than duplicating media. ■ . Send your backups to disk and then copy the data from disk to removable media. Although these strategies may not be advantageous for all situations. This strategy reduces the time that the backup process uses. Use disk staging. if your operations are organized geographically. as follows: Table 3-2 Vaults CustomerDB Example of vaults and profiles organized by data type and time Profiles Weekly Monthly Payroll Biweekly Monthly Yearly Alternatively. as follows: Table 3-3 Vaults London Example of vaults and profiles organized by location and data type Profiles CustomerDB Payroll Tokyo CustomerDB Payroll Preferred vaulting strategies Several strategies can help you reduce resource and time contention when you back up your data and when you vault your backup media. Symantec recommends that you use one of the following: ■ Vault the original NetBackup backup media.

In most situations. a backup job that creates one original image uses one drive and a vault job that creates one duplicate of that original uses two drives — three units of drive time. For example. Sending the original copy to tape then duplicating to a second tape. not about using a disk staging storage unit. or multiple retention period requirements). vaulting originals has the following advantages: ■ Uses less drive time than duplicating backup images from the original tapes. Writing to disk is faster than writing to tape. ■ If you decide to create and vault original backups. Minimizes tape drive usage. requires one drive to make the first copy and two drives (a read drive and a write drive) to make the second copy. Using disk staging for your backup jobs can help avoid resource contention between backup operations and Vault duplication operations. it can be difficult to configure the duplication steps of Vault profiles. The following are some of the advantages of disk staging over tape-to-tape duplication: ■ Shortens backup time. a backup job that creates two originals of a backup image uses two drives — two units of drive time. so less time is needed for backing up. although in storage area network (SAN) environments network traffic may not be an issue. It is possible to send large amounts of data over the network without careful configuration. Avoids configuring for duplication. Conversely. Disk staging is the process of first writing the backup images to a disk storage unit during a NetBackup policy job and then writing the images to removable media during a Vault job. ■ . multiple robots.Best practices Preferred vaulting strategies 39 Vault original backups For most situations. Over time. see the following information before you configure Vault: ■ ■ “Vaulting original backups in a 24x7 environment” on page 43 “Avoid vaulting partial images” on page 42 Use disk staging Note: This topic is about using a disk storage unit as a destination for backup images. Symantec recommends that you use a NetBackup policy to produce multiple original backup images and then use a Vault profile to eject and transfer one or more of the original images off site. In complex environments (such as with multiple media servers. duplicating backup images consumes more drive-time than writing multiple originals during a backup job.

If a robot fails and requires three days to repair. Perhaps more importantly. A longer time window forces Vault to search a larger list of images for vault candidates. Also. you should configure the time window to be at least five days. such as seven days. the next time the profile runs it will select backup images that did not get vaulted during the three-day downtime. you should be sure that you configure it to vault all of the information that you want transferred off-site. Vault will not process images that have already been vaulted by a previous session. Because disk access is fast and disk space is less expensive than tape drives. Overlap the time window in the profile To ensure that all data is vaulted. you can configure the Vault profile to free up the disk space automatically for the next round of back ups. backups that were not processed if a previous session failed will be processed when the profile runs again if the time window is long enough. Configuring the window to be longer. if you have a profile that duplicates images daily and your longest expected downtime is three days. it is often advantageous to send your backups to disk. Therefore. You can schedule your Vault sessions to duplicate the original disk backup images to two (or more) media: one on-site volume and one off-site volume. overlap the time window in the profile. Ensure all data is vaulted When you are setting up NetBackup Vault.40 Best practices Ensure all data is vaulted ■ Reduces expense. suppose the time window for your daily profile extends from 1 day ago . provides even more resiliency. Vault does not duplicate or eject a backup image that already has a copy in the Off-site Volume Group. A Vault profile uses a time range as one of the criteria for choosing the backup images to be vaulted. some backup images may be missed if the time window does not allow Vault to select images from a wider time range. although that will consume more processing time. therefore. For example. Consequences of not overlapping the time window: Missing data When a vault session gets delayed. configure the time window to be the sum of the following: ■ ■ The longest expected downtime for a server or robot Twice the length of the frequency at which the profile runs For example. the extra processing time may not be a problem in your environment because Vault is a batch process that does not demand immediate system response.

When the next Vault session begins on Wednesday. At a minimum. if you want a volume to be ejected. For every media server. see “Alternate media server names tab” on page 76. Therefore. there should be. you should add an entry on the Alternate Media Server Names tab of the Vault Management Properties dialog box. it will only select backup images that were created during the previous 24 hours.Best practices Ensure all data is vaulted 41 to 0 days ago. and a volume group cannot span robots (typically. the robot is fixed. Resolve multiple names for a single server Note: Alternate media servers apply to NetBackup Enterprise Server only. which is useful if you have backup images on multiple robots and want to duplicate those images on media in a robot from which the media will be ejected. Also add any other names by which a media server has ever been known. an entry that contains both the abbreviated name and the fully qualified name. Multiple volume groups (Multiple robots) A profile will only eject media from the robotic volume group of the vault to which the profile belongs. Specify robotic volume group when configuring a Vault Volumes are ejected only if they are in a robotic volume group and in one of the off-site volume pools specified on the profile Eject tab. so Monday night’s backups are still not vaulted. a volume group identifies a specific robot). the session would have picked up both Monday night’s and Tuesday night’s backups. Consequently. If the profile’s time window had spanned more than 1 day. for each media server. On Tuesday. the robot has mechanical problems and the Vault profile fails. a profile can select images to duplicate that are in a different robot’s volume group and in multiple volume groups. For example. ensure that it is in a robotic volume group and in one of the off-site volume pools specified on the profile Eject tab. If you have multiple NIC cards in your server. However. On Wednesday. make sure that the server name or IP address associated with each NIC card is listed in the Alternate Media Server Names tab when you configure a profile. some images may not be recognized as a match for the criteria entered in the Choose Backups tab of the Profile dialog box and may therefore not get vaulted. Taking this action will avoid a number of problems. if you do not list alternate names for media servers. . Monday night’s backups are not vaulted. For more information.

. it must be configured with care as described in “Alternative A: dedicated robot for Vault processing” on page 48. If you use the same volume pool for both. volume ABC123 will be ejected even though it contains images from policy 2. you will vault the backup images that should remain on-site. Use different volume pools for backup images you want to keep on site and for backup images you want to send to the vault. you should be careful that you do not select and transfer off-site more data than you need to. In some circumstances. a deadlock situation may result if your Vault profile is duplicating images because it may attempt to read a backup image from the same tape to which it tries to write the image. Vault will eject a volume if it contains images not intended for off-site storage. use one of the following methods: ■ Stop backup activity long enough to run Vault. For example. if you use the same volume pool for both. Do not Vault more than you need to When you are setting up NetBackup Vault. Avoid vaulting partial images Original backup tapes often begin and end with partial images. if volume ABC123 has three images from policy1 and three images from policy2. that media may contain partial images. To avoid vaulting partial images.42 Best practices Do not Vault more than you need to If you use this configuration. Also. Send only the intended backups off-site When configuring your backup policies. do not assign backup images not intended to be moved off-site to volumes in an off-site volume pool. as shown in the following figure: If you eject and vault original backup media. and policy1 is specified on the profile Eject tab.

Therefore. Because Vault cannot suspend media on which backups are currently being written. such as media to which NetBackup is writing backup images. and that media will be ready to be ejected.Best practices Do not Vault more than you need to 43 ■ If backup jobs are running. it is possible that the original backup media vaulted will not be full. This option does not suspend media that is in use. The rest of the image will be vaulted the next time the profile runs if that tape is not busy and the choose backups time window is large enough to select the image again. You should carefully consider whether to use the Suspend Media for the Next Session option. an error will occur and partial images may be vaulted. seven days a week. If you use this option. the following shows what occurs during NetBackup and Vault operations: Only use the Suspend Media for the Next Session option if you eject original backup media and want to avoid vaulting partial images. . use the Suspend Media for the Next Session option on the profile Eject tab to suspend all media on which backups were written within the last day and then vault only those backups that are older than one day. Vaulting original backups in a 24x7 environment If you use Vault in an environment in which backups can occur 24 hours a day. When Suspend Media for the Next Session is used. prolonging the length of time required to suspend the media. some partial images on vaulted media may be acceptable. No more backup images will be written to that media. Note: Vault only suspends media in off-site volume pools specified on the profile Eject tab. It uses extra CPU cycles because it queries all of the databases again and applies all of the Choose Backups filters again. a profile may try to eject media to which backups are being written.

A current catalog backup is a critical component of an effective disaster recovery plan. (This assumes that your backups will be complete by the time the Vault session runs. Volume I). specify an appropriate retention level so that older catalog backups expire and are recalled from off-site storage and only the three most recent catalog backups remain in off-site storage. it does not duplicate an existing NetBackup catalog backup. you do not need to retain vaulted catalog backups for the same length of time that you retain other vaulted backup media. (See the discussion of NetBackup catalog backups in the NetBackup Administrator’s Guide. A NetBackup catalog backup is not a substitute for a Vault catalog backup because it does not include the latest information about duplicated media and media location. Use only one vault to do Vault catalog backup. If you have a robot attached to the master server. use it for the Vault catalog backup because in most circumstances that master server creates the NetBackup catalog that remains on site. Requirements and Guidelines ■ Perform the catalog backup step in Vault. it is a time-consuming process.44 Best practices Preparing for efficient recovery To avoid such problems when vaulting originals. Although you only need one catalog backup in your off-site vault. To retain only the three most recent catalog backups. In most circumstances. The Recovery Report for Vault lists only the three most recent catalog backups in the off-site vault regardless of how many actually reside in the vault. Use a dedicated volume pool for Vault catalog backups. for extra protection. Although you can rebuild the catalog by importing all of your backup media manually. Vault creates a new catalog backup with up-to-date information. choose backups that were created a day or more ago and suspend the media to prevent writing to the media.) Preparing for efficient recovery Preparing in advance can help you restore your data more quickly and easily. The following can help you prepare for recovery. Vault NetBackup catalogs Use Vault to vault the NetBackup catalogs. ■ ■ ■ ■ ■ . maintaining the three most recent catalog backups in your off-site vault is a good practice. Retain the three most recent catalog backups.

For Vault catalog backups. If your Vault profile duplicates media and you send the first original off site. Designate a primary copy and keep it on site The first (or only) original backup image is the primary backup copy. For off-site volume groups.” ■ ■ Match volume pools to data usage Volumes are assigned to volume pools. a user initiated restore operation will wait indefinitely for a mount of the off-site media. you will probably want to restore all of your customer database at the same time if you recover from a disaster.Best practices Preparing for efficient recovery 45 Use precise naming conventions for volume pools and groups How you name pools and groups can help you (and others) organize and more easily identify media if you have to recover data after a disaster: ■ For volume pools. 1_month_vault. For example. use names that indicate the physical location of the data. If you create multiple original backups during a NetBackup policy job. To assist with recovery. Vaulted_CustomerDB. Ensure that primary copies on removable media remain on site in your robot. it will be ejected and will not be available for restore or duplication operations. do not assign the primary copy to an off-site volume pool unless you intend to send it off site. such as “offsite_volume_group. All of your customer database backup data should be assigned to an off-site volume pool specifically for that data. Vaulted_CustomerDB) can correspond to all profiles within a logical vault or to a single profile. and only backup images of the customer database should be assigned to that off-site volume pool. . For example. NetBackup always uses the primary copy for restore operations. If the primary copy is off site. and 7_year_vault are descriptive volume pool names. the type of data). create and use off-site volume pools that match your data usage (that is. If you assign the primary copy to an off-site volume pool. depending on how your Vault environment is configured. if you maintain a customer database. Vaulted_Payroll. use an easily identified name for the catalog volume pool (such as Vault_Catalog_Backups). and Vault uses the primary copy for duplication operations (unless the primary copy is on removable media and another copy exists on disk). try to identify the purpose or data in the pools. configure Vault to designate one of the duplicate images that remain on site as the primary copy. This volume pool (for example.

Vault profile Eject tab options let you suspend the media that is ejected so you do not have to suspend it if it is recalled. Because Suspend this Session’s Media operates on media in the eject list. This option will suspend duplicate media created by Vault. You also can choose to suspend media before it is ejected so that partial images are not written to that media. no more images will be written to the media. Note: Vault only suspends media in off-site volume pools specified on the Eject tab.46 Best practices Preparing for efficient recovery Suspend vaulted media Unexpired media that is recalled and injected back into the robot should be suspended so NetBackup will not write images to it. Suspending media before it is ejected also helps to prevent errors from ejecting media that is in use. however. Purpose To suspend media in the eject list for the current session. such as media to which NetBackup is writing backup images. Suspend Media for the Next Session To prevent partial images from being written onto media that contains images to be vaulted. Use this option only if you vault original images and want to avoid vaulting partial images on backup media. If you select Immediately. If you select At Time of Eject. images may be written to the media until the media are ejected. it does not use more CPU cycles selecting media to suspend. see “Avoid vaulting partial images” on page 42. The following table describes the two suspend options available on the Eject tab: Table 3-4 Option Suspend this Session’s Media Suspend options available with the Eject tab. It uses extra CPU cycles because it queries all of the databases again and applies all of the Choose Backups filters again. this option will not suspend media that is in use. For information about how partial images can be written to media. the Suspend this Session’s Media option is a better choice for suspending duplicate media because it does not use CPU cycles to select media to suspend. You should carefully consider whether to use this option. Also. . select At Time of Eject if you want the media sent off-site to be full.

To avoid resource contention. Do not inventory a robot while Vault is ejecting media. you can reduce the chances of error conditions from busy robots and reduce potential problems by the following: ■ Eject media during a dedicated time period when no other inject or eject operations occur. Media ejection recommendations Although Vault queues jobs. If you do not eject the media and transfer it to your off-site vault location. Do not inject or eject other media while Vault is ejecting media. ■ ■ Avoid resource contention during duplication Note: If you vault original backups. when the operations occur) Media used Robots and drives Bandwidth Various configurations can help you avoid resource contention. if you recalled a volume to use for a restore operation).Best practices Media ejection recommendations 47 Revault unexpired media You should always revault media that was recalled from off-site storage and injected into the robot (for example. follow the advice provided in one of the following alternatives: . it will not be available if media at your site are damaged. Following are the resources that you should consider when configuring duplication in Vault: ■ ■ ■ ■ Time (that is. Also. you do not have to use practices that avoid or reduce resource contention in Vault. a general principle that can help avoid resource contention is to wait until backups are completed before using Vault to duplicate or eject media. which can occur when two processes try to use the same drive at the same time. When two processes try to use the same drive Careful configuration of your environment can help avoid resource contention during Vault duplication.

do not select Advanced Configuration or Alternate Read Server. they use available resources wisely and are unlikely to cause resource allocation problems. Write the first backup image (the primary backup) to a storage unit that is not in the Vault robot. Alternative A: dedicated robot for Vault processing Note: Alternate read servers apply to NetBackup Enterprise Server only. This configuration works best in a storage area network (SAN) environment where all media servers have direct access to the vault robot because then the duplication step will not send data over the network. Use Vault to duplicate images. as follows: ■ Use a NetBackup policy to create multiple original backup images concurrently. On the Duplication tab. specify All Media Servers in the Media Servers list. On the Choose Backups tab of the Profile dialog box. the media server that performed the backup will also perform the duplication. There are two ways to achieve this configuration. dedicate one robot strictly for vault processing. then create an entry for each media server in your environment. If the Destination Storage Unit media server is not the same as the media server that performed the backup. All media servers will send duplication data to the Destination Storage Unit media server. specify the destination storage unit’s media server as the Alternate Read Server but do not select Advanced Configuration.48 Best practices Avoid resource contention during duplication These alternative configurations work well for multi-robot environments. If the alternate read server also has access to all of the backup robots. no data will be sent over the network. Backup images will be duplicated from all other robots to the Vault robot. On the Duplication tab of the Vault Profile dialog box. Use one of the following alternatives to configure Vault to perform duplication: ■ ■ On the Duplication tab of the Profile dialog box. The media in this robot will contain only the duplicate backup copies that are to be ejected and sent to the off-site vault. select Alternate Read Server. select Advanced Configuration. the data will be sent over the network. Write one of the other originals to the Vault robot and assign it to the off-site volume pool. In a multi-robot environment. For each backup image. This configuration requires that all robots used be connected to the same NetBackup media server. To avoid sending ■ ■ . Configure a Vault profile to eject all media in that vault’s off-site volume pool.

In a multi-robot environment. Using Any Available for other storage units may cause images not intended for off-site storage to be written to the Vault robot. Specify half of the available drives in the robot as read drives so that an equal ■ . Use Vault to duplicate images. Each robot will duplicate and/or eject only backup images that were originally written to it. This will limit the profile so that it will duplicate only backup images that have their primary copy on media in this robot. You can do so in several ways. specify the robot to which the profile belongs in the Source Volume Group field. Disadvantage In a complex environment. configure one vault and one profile that ejects the backups that were assigned to the off-site volume pool in that robot.Best practices Avoid resource contention during duplication 49 duplication data over the network. On the Choose Backups tab of the Profile dialog box. that server must have access to all the robots that hold the source images so they will be duplicated. Ensure that the total number of write drives specified in the Write Drives column for each entry does not exceed the number of drives in the Vault robot. Alternative B: each robot as a Vault robot Note: Alternate read servers apply to NetBackup Enterprise Server only. Only backups on media in the off-site volume pools specified on the Eject tab and that meet the rest of the criteria specified in the profile will be ejected. do not use Any Available storage unit in your backup policies unless only your Vault storage units are set to On Demand Only. Advantage This configuration is most convenient for the operator. for each media server entry specify the destination storage unit’s media server as the alternate read server. If you use this alternative. configure each backup robot to be a Vault robot. this alternative can be difficult to configure if you want to avoid sending duplication data over the network. simplifying the tape rotation process. assigning the copy to be vaulted to an off-site volume pool in any of the robots. You can achieve the same behavior provided by Any Available storage unit by configuring your backup policies to use a storage unit group that includes all storage units except for the vault robot’s (although if you use storage unit groups you cannot make multiple copies simultaneously). For each robot. who can eject and inject tapes from only one robot. as follows: ■ Use a NetBackup policy to create multiple original backups.

■ ■ . Alternative C: one robot as both a backup and Vault robot In a multi-robot environment. configure all of the robots as backup robots and configure one of the backup robots as a Vault robot also. specify the volume group in robot two as the Source Volume Group. specify the volume group in robot three as the Source Volume Group. Four duplication jobs run simultaneously. Images in robot one are read by four drives and written to four drives in robot three. specify two read drives.) Configure one vault for the Vault robot. In each profile. configure the three profiles as follows: ■ In the profile for robot one (a backup robot only). if you have three robots that each have four drives. In the profile for robot two (a backup robot only). and specify a destination storage unit in robot three (robot three is the Vault robot). and in that vault configure one profile for each of the backup robots. specify the backup robot in the Source Volume Group field of the Choose Backups tab and specify a destination storage unit that is in the Vault robot. specify the volume group in robot one as the Source Volume Group. Two duplication jobs run simultaneously. Four duplication jobs run simultaneously. For example. Images in robot two are read by four drives and written to four drives in robot three. This configuration avoids resource contention when one profile attempts to duplicate images in multiple robots. In the profile for robot three (a backup and Vault robot). (One of the robots functions as both a backup robot and a Vault robot.50 Best practices Avoid resource contention during duplication number of read and write drives are available. specify the media server of the destination storage unit as the Alternate Read Server. Advantages These methods work well with backup policies that use Any Available storage unit. Note: The destination storage unit must have at least two drives if that robot will be used for both read and write functions. and specify a destination storage unit in robot three. specify four read drives. specify four read drives. Configure one such vault and profile for each robot. and specify a destination storage unit in robot three. Images in robot three are read by two drives and written to two drives. Using Vault to duplicate images also works well with storage unit groups if you make one copy only. To avoid sending duplication data over the network.

see “Previewing a Vault session” on page 135. If not enough drives are available. Symantec recommends that you preview the images you want to duplicate before you run the Vault job. including tape drives. When the read drive is not in the Vault robot The read drive does not have to be in the vault’s robot. Vault duplication job priority is assigned for each profile in the Duplication tab. Sharing resources with backup jobs Vault duplication jobs compete with other process in NetBackup (such as regularly scheduled backups) for resources. it requires a read drive and a write drive in the vault robot. Using Any Available storage unit in your backup policies sends backup images to media in any storage unit available. Vault catalog backup jobs run at the priority assigned in the catalog backup policy unless you assign a different priority in the Vault catalog backup schedule Multiple Copies dialog box. .Best practices Avoid resource contention during duplication 51 All images are duplicated to robot three and ejected from robot three. For configurations that include multiple media servers and multiple robots. which will show you where the images are located and what kind of resources will be required to duplicate them. To preview the images to be duplicated. we recommend that you seek advice from Veritas Enterprise Consulting Services. Advantages This method works well with backup policies that use Any Available storage unit. assign a higher priority to the Vault jobs than is assigned to other NetBackup processes. Priority for NetBackup jobs are assigned in the master server Global Properties. Subsequently. Note: The destination robot must have at least two drives if that robot will be used for both read and write functions. using the Any Available storage unit for backup jobs can send some original backup images to the Vault robot. a deadlock condition can occur. In addition. If you want your Vault duplication jobs to obtain resources before other processes. and this configuration selects backup images on all the robots and duplicates them to the Vault robot. when Vault tries to duplicate those images.

■ ■ When you run that Vault profile. so you can spread the load between backup jobs and Vault duplication jobs. The vault process is simpler and easier if you do not duplicate images. Configure a second Vault profile to do the catalog backup and eject steps. spreading the workload evenly throughout the week. several strategies can help you balance the load on your computing environment. it will eject both the copy of the original media from policy A and the duplicate media from policy B. if the vault vendor picks up the media every Friday.52 Best practices Avoid resource contention during duplication Load balancing If it is feasible. If you cannot Vault originals. This profile should use the same image selection criteria as the profile that ■ . Duplication occurs every day rather than one day only. Vault copies backup images from NetBackup policy B only and does not duplicate images from policy A because an original already exists in the off-site volume pool. Your Vault profile is configured to copy backup images and assign the duplicate images to an off-site volume pool. If you have configured the profile for eject. you can do the following: ■ Configure a Vault profile to do duplication only. NetBackup policy B creates one copy and assigns it to an on-site volume pool. you can create multiple copies of some of the backups and only one copy of the other backups and then configure a Vault profile to duplicate from the single original backups and eject both the original images and the duplicate images. The media remains in the robot until it is due to be collected by the vault vendor. Symantec strongly recommends that you create multiple original backup images concurrently in your backup policies to create both the on-site copy and the copy that will be sent to the vault rather than using Vault duplication. If your Vault vendor does not pick up media every day You can use Vault to duplicate backup images daily and eject volumes weekly. For example. For example: ■ NetBackup policy A creates multiple original copies and assigns one of the copies to an off-site volume pool. and configure a vault policy to run this profile every day of the week. if your backup window is too small to create multiple simultaneous copies of all backups. Profiles for both originals and duplicates Vault can eject both original backups and duplicate images. For example.

Therefore.) Use a separate volume pool for each Vault Jobs within the same vault are queued and then run when resources are available. This avoids the need for your Vault session to do duplication. Specify different volume pools for source and destination You should never configure a profile for duplication so that the source volume and the destination volume are in the same volume pool. those jobs could all pick the same target media. and the off-site copy to go to another robot. In this scenario. . except for the Catalog Backup step. circumventing the queuing mechanism and causing undesirable results (such as a deadlock condition when multiple jobs try to use the same drive at the same time). (This is a NetBackup limitation. Configure a Vault policy to run this profile before the vault vendor arrives on Friday. However. If you create multiple backup images concurrently. This will result in deadlock when NetBackup chooses the same tape as the source and the destination of the duplication operation. Vault takes no significant resource time. Vault need only eject the backup tapes. all destination storage units must be on the same media server.) Suppose you want the on-site copy of your backups to go to one robot. Avoid sending duplicates over the network Sending duplicate images over the network is not a problem if there is sufficient bandwidth. but even a fiber optic storage area network (SAN) has only enough bandwidth for two or three duplication jobs at a time.Best practices Avoid sending duplicates over the network 53 duplicates images. Create originals concurrently One way to avoid sending data over the network with your Vault job is to create multiple original backup images concurrently during your scheduled backup jobs. This method for duplicating and ejecting media provides the added benefit of consolidated reports that are not organized by session. you should configure Vault so that every vault has its own off-site volume pool. (Catalog Backup is necessary to capture the changed volume database information for each vaulted tape. if multiple profiles from different vaults run simultaneously and use the same off-site volume pool for duplication. Following are some strategies you can use to avoid sending data over the network.

Connected to the robot that contains the destination storage units. For example. An alternate read server is a server used to read a backup image originally written by a different media server. Use alternate read server Note: Alternate read servers apply to NetBackup Enterprise Server only. your media server will need a storage unit on both robots (one storage unit for your on-site copy and one for the off-site copy). Note: If the destination storage unit is not connected to the alternate read server. and D will be read by the alternate read server. You can avoid sending data over the network during duplication by specifying an alternate read server if the alternate read server is: ■ ■ Connected to the robot that has the original backups (the source volumes). in the diagram below. non-disk images written by media servers A. . you will send data over the network. C. B.54 Best practices Avoid sending duplicates over the network Therefore.

However. Take Care When Specifying All Media Servers If you specify All Media Servers on the Choose Backups tab of a profile and also use Advanced Configuration on the Duplication tab. you can use advanced duplication to process each media server independently and concurrently. If each media server has access to at least one unique drive in the destination robot. multiple profiles within a single vault must run consecutively. create an entry for each media server on the Duplication tab advanced configuration view.Best practices Avoid sending duplicates over the network 55 Use advanced duplication configuration Note: More than one media server applies to NetBackup Enterprise Server only. no alternate read server is used and each media server reads and duplicates its own backup images. (Note: all media from a single profile are ejected from the same robot. so this may not allow you sufficient bandwidth.) You can do the same thing by configuring a separate profile for each media server rather than using advanced duplication configuration. In the following diagram. .

56 Best practices Increase duplication throughput If you list more media servers on the Choose Backups tab than on the Duplication tab. Therefore. you can specify Any Available for the media server for the storage unit). Vault assigns the images written by media servers not listed in the advanced view to the first media server that finishes its duplication job. consequence is that backup images from the media servers not configured for duplication may be duplicated by a different media server each time the profile is run. a lot of data would be sent over the network. there are an equal number of read and write drives. data will be sent over the network. a separate duplication job (bpduplicate) will be started. though less problematic. Increase duplication throughput Adding drives will enable Vault to run multiple duplicate sessions concurrently. and one media server. The storage units are attached to the host on which the media server resides. A duplication process runs for each read/write drive pair. For each write drive. . NetBackup may choose a different media server for the duplication job than the source media server. When a job uses such a storage unit. one master server. NetBackup determines the media server to be used with the storage unit when a job runs. If the first available media server is across the network. If so. to avoid sending duplicates over the network. The following provides information about multiple drive environments: Configuring for multiple-drives: Basics In a basic multiple-drive configuration. use storage units that specify a media server (that is. Another possible. do not use storage units that are configured to use Any Available media server). media duplication data will be transferred over a network. Use Storage units that specify a media server NetBackup lets you create a storage unit without specifying a media server for that storage unit (that is. If you specify a destination storage unit that uses Any Available media server for Vault duplication. If the master server and media server reside on different hosts.

and multiple media servers.Best practices Increase duplication throughput 57 Note: Only NetBackup Enterprise Server allows a master server and media server to reside on different hosts. no data will be sent over the network. If you designate an alternate read server (media server A) for reading the images to duplicate and if the destination storage unit also resides on the alternate read server (media server A). A separate duplication process runs for each read/write drive pair during a duplication operation. . the configuration will have an equal number of read and write drives. one master server. Multiple-drive scenario: Does not send data over network In a multiple-drive configuration that does not send data over the network.

58 Best practices Maximize drive utilization during duplication Note: Alternate read servers apply to NetBackup Enterprise Server only. Symantec recommends that you do your duplication with as few Vault jobs as possible. Therefore.0 and later. if you can configure one Vault profile to duplicate all of your data. backing up the catalog. you can configure one Vault profile to create off-site copies with multiple. generating reports. with no pause. and so on). which keeps your drives spinning from the time of the first image to the last. different retentions. It is much more efficient to use as few Vault profiles as possible for duplication. In Vault 5. a single Vault profile can do all of your duplication. see “Assigning multiple retentions with one profile” on page 156. you will reduce idle time and get the maximum utilization of your drives. The more profiles you use. Maximize drive utilization during duplication To maximize drive utilization. . Drives will be idle between the duplication steps of consecutive Vault jobs while Vault is doing all of its other processing (selecting images. the less efficient the duplication process becomes. By doing this. For more information about multiple retention mappings.

This organizes reports by robot and maximizes the reuse of tapes. the Picking List for Vault. and the All Media Inventory reports may include volumes from other profiles or vaults that have expired and moved back into the scratch pool even though the reports may be for a specific Vault profile or session. . you can use either the off-site volume group or the off-site volume pool(s) to organize media for each robot. or profile. For information about configuring scratch pools. Create your volume pools and allocate volumes to them. Media Manager moves volumes between the scratch pool and the other volume pools as needed and returns the expired volumes to the scratch pool. Your decision affects how you use your volume groups and volume pools. Ensure report integrity You should determine whether you want your Vault reports to group media by robot. by vault. This method may be the best option if you decide to add a scratch pool to an existing NetBackup configuration. as follows: ■ Create a scratch pool and add all your volumes to it. Media Manager will then move volumes from the scratch pool to the other volume pools as needed and return the expired volumes to the scratch pool. Vault searches the off-site volume group for the media to include in the reports. each robot has its own off-site volume group). all the vaults within each robot should use the same off-site volume group (that is. or by profile. the Offsite Inventory. If you use a scratch pool. Therefore. see the NetBackup Administrator’s Guide. vault. then create all the other volume pools but do not allocate any volumes to them. including Vault pools.Best practices Use scratch volume pools 59 Use scratch volume pools A scratch pool is an optional volume pool that you can use to ensure that volumes are allocated to the volume pools that need them. It also uses the off-site volume pools for the same purpose. Media from one robot will not appear on the reports for another robot. Organizing reports by robot To ensure that reports are organized by robot. You can set up a scratch pool in two ways. Media Manager moves volumes from a scratch pool to other pools that do not have volumes available. ■ The scratch pool feature can affect reports for media coming on site. and then create a scratch pool and allocate volumes to it. Expired volumes are returned to the scratch pool automatically.

use a separate off-site volume pool for each profile. you can inject the incorrect media and possibly the incorrect number of media into your robots. Consequences of sharing an off-site volume group across multiple robots If profiles from multiple robots share both an off-site volume group and one or more off-site volume pools. it will never again be listed for recall. Doing so ensures that each report contains media from one vault. each vault has its own off-site volume group) and a common off-site volume pool for all profiles within each vault (that is. Every time the Picking List for Vault report is generated for any profile within any vault for the robot. Organizing reports by Vault To ensure that the Vault reports include media for each vault. specify a separate off-site volume group for each vault within a robot (that is. your vault vendor will return a group of tapes (for a single Picking List for Vault report) that were ejected from multiple robots. The operator will need to identify which tapes should be injected into each of the robots. ■ . Organizing reports by profile If you want the reports to include only media for a single profile. Media can get stranded at the off-site vault for various reasons: ■ Frozen backup tapes never expire. If a tape from that report is missed and is not returned to the robot. tapes from all profiles and logical vaults for that robot could be recalled for reuse (depending on how profiles share off-site volume pools). A backup tape appears on the Picking List for Vault and Distribution List for Robot only once. all profiles in the vault use the same off-site volume pool). If mistakes are made identifying and injecting tapes.60 Best practices Generate the lost media report regularly Reports will not seem consistent for an individual logical vault. Generate the lost media report regularly You should generate the Lost Media Report regularly so you can recall media that has not been returned from the off-site vault vendor but should have been returned. but this strategy will maximize the frequency with which tapes are returned for reuse. A backup tape that does not expire will not appear on the Picking List for Vault and will not be recalled from the vault.

Weekly or monthly may be often enough. if you begin using a new media type. . How often you generate the Lost Media Report depends on your operations.Best practices Generate the lost media report regularly 61 ■ You change off-site volume group or pool names. you will have to use a new volume pool name. If you change names. media may be stranded off-site because the Picking List for Vault is based on off-site volume pools and off-site volume groups. For more information. see “Changing volume pools and groups” on page 221. and media associated with the old names will not be listed. for example. Symantec recommends that you do not change or rename group or pool names.

62 Best practices Generate the lost media report regularly

Chapter

4

Configuring NetBackup for Vault
Before you configure Vault, you must do the following in NetBackup:
■ ■

Create Off-site Volume Pools Create a Vault Catalog Backup Schedule

You should review the best practices information. It can help you determine how to set up and configure Vault. See “Best practices” on page 37. You should be familiar with basic NetBackup concepts, such as volume pools and groups, policies, and storage units. For more information about them, including how to configure them in NetBackup, see the NetBackup Administrator’s Guide, Volume I.

Off-site volume pools
Volume pools identify logical sets of volumes by usage. They are used by Vault to determine if a volume should be ejected. Volume pools for images to be transferred off site are known as off-site volume pools. When you create the images that you want to send off site, write them to media in an off-site volume pool. During a Vault job, Vault searches a robot for images that match the selection criteria; if the media the images reside on are in an off-site volume pool, Vault ejects that media. You need at least two dedicated volume pools:

Off-site Volume Pool. Vault ejects media from off-site volume pools, so data that you want to transfer off site should be assigned to media in an off-site volume pool. You can assign either original backup images created as part of a NetBackup policy job or duplicate images created by a Vault job to the

64 Configuring NetBackup for Vault Off-site volume pools

off-site volume pool. How many off-site volume pools you use depend on your operations.

Vault Catalog Backup Volume Pool. If you are writing the Vault catalog to removable media, you should use a volume pool dedicated for Vault catalog backups. When you configure the volume pool in Media Manager, ensure that the Catalog Backup attribute is set. You should use only one Vault catalog backup volume pool. Vault does not require a dedicated volume pool for its catalog backups; however, if you do not use one, regular NetBackup media or catalog media may be ejected.

Do not use the NetBackup volume pool for Vault media. Because the NetBackup volume pool is the default volume pool, if you use it for Vault you will probably send more data off-site than you want to. Best Practices
■ ■ ■

“Use precise naming conventions for volume pools and groups” on page 45 “Match volume pools to data usage” on page 45 “Use scratch volume pools” on page 59

Creating a volume pool
Volume pools are configured in the Media and Device Management > Media node of the NetBackup Administration Console. Ensure that the volume pools you create have sufficient volumes allocated to them (or to a scratch pool if one exists). After a volume is assigned to an off-site volume pool, it remains in that pool and will be used for rotation within that same pool (unless a scratch pool exists, in which case it will be returned to the scratch pool). See the The following are basic instructions for creating a volume pool. For more information about volume pools and allocating volumes to them, see the NetBackup Administrator’s Guide, Volume I and the NetBackup Administration help. To create a volume pool 1 2 3 In the NetBackup Administration Console, click Media and Device Management > Media. Click Actions > New > Volume Pool. The Add a New Volume Pool dialog box appears. In the Pool name text box, enter a name for the new volume pool. The name must be 20 characters or less and cannot contain any spaces or special characters.

Configuring NetBackup for Vault Catalog backup schedules for Vault

65

4 5

In the Description text box, enter a brief description for the pool. NetBackup Enterprise Server only: To allow only a specific host to use the volumes in this pool, do the following: a b Select Permit only the specified host to access volumes in the pool. In the Host name text box, enter the name of the host that is allowed to request and use the volumes in this volume pool.

Note: Symantec recommends that you do not specify a specific host. Allowing any host (the default) is recommended and is required if you have NetBackup media servers (or SAN media servers) controlled by a master server. Never specify the name of a client. 6 Select the Catalog backup pool check box if you will use this volume pool to back up the NetBackup catalog. This check box creates a dedicated catalog backup pool to be used for catalog policies. A dedicated catalog volume pool reduces the number of tapes needed during catalog restores since catalog backup media are not mixed with other backup media.

Catalog backup schedules for Vault
NetBackup uses a special backup policy of type NBU-Catalog to perform catalog backups. To perform a Vault catalog backup, Vault uses a special schedule of type Vault Catalog Backup in an NBU-Catalog policy. Before you can configure the catalog backup step in Vault, you must create a Vault Catalog Backup schedule in an NBU-Catalog policy. Related Topics

“Catalog backup tab” on page 114

Best Practices

“Vault NetBackup catalogs” on page 44

Creating a Vault catalog backup schedule
You can create a schedule in an existing catalog backup policy or create a new catalog backup policy and schedule. You can create more than one Vault Catalog Backup schedule per policy, and your NetBackup environment may have more than one NBU-Catalog policy. You must specify the storage unit and, if the storage unit uses removable media, a volume pool for the Vault catalog backup:

If creating one copy of the catalog, you must:

66 Configuring NetBackup for Vault Catalog backup schedules for Vault

■ ■

Override the policy’s storage unit and select a storage unit. Override the policy’s volume pool and select the dedicated Vault catalog volume pool (for removable media only).

If making multiple copies, select the storage unit and the dedicated Vault catalog volume pool (removable media only).

You do not have to specify a volume pool for disk storage units. Prerequisite

Create an NBU-Catalog type of backup policy. For instructions, see the NetBackup Administrator’s Guide. To create a Vault catalog backup schedule in an existing policy In the NetBackup Administration Console, expand NetBackup Management > Policies. Double click on the policy name. Select the Schedules tab. Click New. The Change Schedule dialog box appears.

1 2 3 4

5

See Vault catalog backup schedule configuration options for the options you can configure.

Use a name that identifies it as a Vault catalog backup schedule.Configuring NetBackup for Vault Catalog backup schedules for Vault 67 Vault catalog backup schedule configuration options The following table shows the configuration options for the NBU Catalog policy Schedules Attributes tab: Table 4-5 Property Name Schedules Attributes tab configuration options Description Enter the name of the schedule. If you are using Media Manager storage units. Retention Multiple catalog backup configuration options The Configure Multiple Copies dialog box appears only if you select the Multiple Copies checkbox on an NBU Catalog policy Schedule Attributes tab and then click Configure. See “Multiple catalog backup configuration options” on page 67. Select the length of time before the catalog backup expires and the volumes are recalled from the off-site vault. Type of backup Multiple copies Override policy storage unit Select this option and then select the storage unit to use from the drop-down list Override policy volume pool If the storage unit is on removable media. After the Retention has passed. catalog backup media appear on the Picking List for Vault or Distribution List for Robot. click Configure. use a dedicated off-site volume pool for Vault catalogs. and then select the appropriate attributes for each copy in the Configure Multiple Copies dialog box. select this option and then select the volume pool for off-site catalog backups (does not apply to disk storage units). . To create multiple copies of the catalog. Select Vault Catalog Backup. Vault recalls that media so it is available to reuse as catalog backup media. select Multiple copies.

The action to perform if a copy fails: Continue or Fail All Copies. the value is two: one original backup and one copy. NetBackup will automatically retry the job if time permits and.) By default. (Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. NetBackup will again try to run the backup (regardless of the frequency of the schedule). The job for each copy will run using this priority. the next time the backup window for the policy opens. NetBackup will do this until the backup succeeds. For Media Manager storage units. Table 4-6 Property Copies Configure Multiple Copies dialog box options Description Select or enter the number of copies to create concurrently. The following table describes configuration options for the Configure Multiple Copies dialog box for catalog backup. You can create up to 4 or the number of copies specified in the Maximum Backup Copies field for the NetBackup master server (if less than 4). the entire backup job will fail and no copies will be made.68 Configuring NetBackup for Vault Catalog backup schedules for Vault Use this dialog box to create multiple copies of a Vault catalog backup. The number of copies to create concurrently.999 (highest) priority. . from 0 (lowest) to 99. all storage units must be connected to the same media server. If you choose Fail All Copies. although one or more backup windows may pass before the backup is successful. If This Copy Fails Priority of Duplication Job Specify the priority of the duplication jobs for the catalog copies.

select the volume pool for off-site catalog backups (does not apply to disk storage units). Volume I. Storage Unit Select the storage unit that contains the resources to which the catalog backup will be written. For information about how Vault queues jobs. expand NetBackup Management. Vault recalls that media so it is available to reuse as catalog backup media. see the Maximum Vault Jobs property in the NetBackup Administrator’s Guide. see “Running multiple sessions simultaneously” on page 134. Select Master Server. Master server properties for Vault Several NetBackup master server properties control some aspects of Vault. For more information. catalog backup media appear on the Picking List for Vault or Distribution List for Robot.Configuring NetBackup for Vault Master server properties for Vault 69 Table 4-6 Property Retention Configure Multiple Copies dialog box options (continued) Description Select the length of time before the catalog backup expires and the volumes are recalled from the off-site vault. For information about how to set these properties. use a dedicated off-site volume pool for Vault catalogs. After the Retention has passed. . see the following: ■ ■ ■ “Setting the maximum number of Vault jobs” on page 69 “Setting the duration of Vault session files” on page 223 “Setting the duration and level of logs” on page 239 Setting the maximum number of Vault jobs Vault uses the Maximum Vault Jobs property as a threshold for queueing jobs. Expand Host Properties. To set the maximum number of Vault jobs 1 2 3 In the NetBackup Administration Console. The Maximum Vault Jobs property is configured on the NetBackup master server. If you are using Media Manager storage units. Volume Pool If the storage unit is on removable media.

The greater the maximum number of vault jobs. Specify the maximum number of vault jobs that can be active on the master server. Select Global Attributes Properties. . select the master server and then Actions > Properties. the more system resources are used.70 Configuring NetBackup for Vault Master server properties for Vault 4 5 6 In the right pane.

It can help you determine how to set up and configure Vault. see the following: ■ ■ ■ ■ ■ ■ “Information required to configure Vault” on page 71 “Configuring Vault management properties” on page 74 “Configuring robots for Vault” on page 82 “Creating a Vault” on page 83 “Creating a profile” on page 88 “Configuring a profile” on page 90 Information required to configure Vault Information about the general configuration for NetBackup is required so you can set up and use NetBackup Vault. Before configuring Vault. To configure Vault. Collect and record the appropriate information about the following so that it is available when you begin to configure Vault. After you configure Vault profiles. you must configure volume pools and a catalog backup schedule for use with Vault. See “Scheduling a Vault session” on page 130. and profiles. vaults. you should review the best practices information. you configure robots. See “Configuring NetBackup for Vault” on page 63. . Before configuring NetBackup and Vault. See “Best practices” on page 37. you configure policies to schedule when the Vault jobs will run.Chapter 5 Configuring Vault When you configure Vault.

TLD. For every media server. For NetBackup. You can use the bpstulist -U command to generate a list of existing storage units. and robotic devices. configure alternate media server names. The number of media servers associated with the master server. The robotic devices associated with each media server. Storage Unit Name Number of Drives . This server should also be bound to a storage unit within the NetBackup configuration. which is the recommended configuration for NetBackup. Table 5-7 Property Master Server Host Name Server and storage unit information Description The name of the host server on which the NetBackup master server and Vault are installed. Operating System Level of Master Server Number of Media Servers Media Server Name Operating System Level of Media Servers Types of Robotic Devices The release of the operating system on the host machines on which the NetBackup media server or servers are installed. The NetBackup storage units that are associated with each media server. TL8) or specify the actual hardware manufacturer and model names for each device. all drives (of a given media type) that are attached to a server are defined as one storage unit. media servers. You may choose to keep some drives available for restores or backups while duplication is running. Use the appropriate NetBackup terminology to identify the devices (for example. The name of each media server that controls the drives you want to use for the vault process. which are used in various configuration options in Vault. Tape to tape duplication requires drives in pairs: one to read and one to write. ACS. media servers. The number of drives in each storage unit. Consider how many drives in each storage unit you want to use for vault sessions. see “Alternate media server names tab” on page 76. for more information.72 Configuring Vault Information required to configure Vault Master server. The release of the operating system on the system on which the NetBackup master server is installed. and storage units Collect the following information about master servers.

if you have to connect to your network ■ . In some circumstances. On StorageTek systems. On StorageTek systems. Alternatively.) You have to connect to the UNIX system on which the NetBackup master server is installed from a remote system that does not have the NetBackup Administration Console. StorageTek only. you may have to use the Vault Administration menu interface to configure Vault.Configuring Vault Methods of configuration 73 Robot information Collect the following information for each robot. it may help you plan your configuration so that you use resources efficiently. Although the following information is not required to configure a robot for Vault. The corresponding LSM number for this robot. The capacity of the media access port (also known as cartridge access port). you can obtain this information by using the ACSLS command query cap all from the ACSLS console. (The NetBackup Administration Console that runs on UNIX systems is a Java-based application. as follows: ■ The NetBackup master server is installed on a UNIX host that does not support the NetBackup Administration Console and your computing environment does not have a system from which you can run the NetBackup Administration Console. For example. These instructions describe using the NetBackup Administration Console to configure Vault. The corresponding ACS number for this robot. You can obtain this information by using the Media Manager tpconfig command or by using the ACSLS console commands such as query acs all or query lsm all. Table 5-8 Property ACSLS Server ACS Number Robot properties Description The name of the ACSLS server. you can use the Vault Administration menu user interface on UNIX systems (invoked by the vltadm command from a terminal window). You can obtain this information by using the Media Manager tpconfig or by using the ACSLS console commands such as query acs all or query lsm all. The identifiers for the media access port. StorageTek only. LSM Number MAP Capacity MAP Numbers Methods of configuration You can use the NetBackup Administration Console to configure Vault. StorageTek only. you can obtain this information by using the ACSLS command query cap all from the ACSLS console.

The NetBackup Vault Manager must be running at all times so Vault will function correctly. if one instance of an administration interface or Vault command tries to change configuration information while another instance is changing information. The e-mail address for eject notification for all profiles. The reporting period for media going offsite reports. Versions of Vault earlier than 6.74 Configuring Vault Configuring Vault management properties by using a dial-up connection over a telephone line. vault. and retention level mappings for all vaults. Configure Vault Management Properties in the following tabs in the dialog box: ■ ■ ■ ■ “Vault Management Properties General tab” on page 74 “Alternate media server names tab” on page 76 “Retention mappings tab” on page 79 “Reports tab” on page 80 Vault Management Properties General tab Use the Vault Management Properties General tab to configure the following: ■ ■ ■ ■ The E-mail address for session status notification. For information about using the Vault Administration interface. Configuring Vault management properties Vault Management Properties specify e-mail addresses for event notification. you may have to use a terminal window and use the Vault Administration interface. Vault prompts the user to reload the information by using the Refresh option.0 do not use the NetBackup Vault Manager to arbitrate access to the Vault configuration. Related Topics ■ “Setting up E-mail” on page 217 . and profile configuration information. report properties for all vaults. Because NetBackup Vault Manager arbitrates access. alternate media server names. see “Using the Vault administration interface” on page 225 The NetBackup Vault Manager (nbvault) manages Vault activity and arbitrates access to the Vault robot. you can run more than one instance of the NetBackup Administration Console. Therefore. The sort order for ejected media. do not use earlier versions of the NetBackup Administration Console to modify Vault configuration information.

Select the General tab. and the status of the operation.Configuring Vault Configuring Vault management properties 75 To configure general Vault management properties 1 From within Vault Management. 2 3 Enter information or select options as appropriate. The Vault Management Properties dialog box appears. If you enter e-mail addresses in the E-mail address for notification of session status field. Table 5-9 Property General Vault options Description An e-mail notification is sent at the end of each vault session. in the form of a summary. e-mail is sent to those addresses rather than to the root user.log file. To enter more than one address. Table 5-9 describes the options. select Vault Management Properties from the Actions menu. You cannot disable notification of session status. it provides a summary of the vault session. the e-mail is sent to the root or administrator user account on the system on which the NetBackup master server is installed. The subject line of the e-mail message is formatted as follow: Vault Status status_code [robot_number/vault/profile] (MasterServer) By default. E-mail address for notification of session status . separate the addresses with commas.

Specifying a value does not affect whether media are ejected and vaulted. . This use of the Alternate Media Server Names dialog box allows you to use one name to specify more than one server. which is useful if you want to duplicate images from multiple servers. you only have to specify the server name group rather than the individual servers. that image will not be listed on the media going off-site reports. You can configure different addresses in each place. you should add the fully qualified name. if a volume is ejected that has an image on it older than the period you specify. For every media server. any other names by which a media server has ever been known. By default. Vault sends the notification to the first e-mail addresses found in that order. all server names or IP addresses associated with each NIC. This can reduce the amount of time to generate reports because Vault will search fewer image database records to determine which images are on the ejected media. Adding alternate names for media servers simplifies configuration and helps ensure that all images eligible to be vaulted are chosen. separate the addresses with commas. and if you have multiple network interface cards (NICs) in the server. E-mail address for eject notification Eject media. Vault searches the entire image database. Then. By default. You also can create a server name group that includes different servers. To enter more than one address. however. the short name. sort by You can select whether to eject media alphabetically or by expiration date. Eject notification is configured for each profile on the Eject tab. Vault ejects media alphabetically. Vault expands any occurrence of one of the names in a server name group to include all of the names in the group. and globally for Vault on the Vault Management Properties dialog box General tab. for each robot on the Vault Robot dialog box. in the Media Servers field in the Profile Choose Backups tab. You can enter the number of days before the day a profile runs to search for images to include in media going off-site reports.76 Configuring Vault Configuring Vault management properties Table 5-9 Property General Vault options (continued) Description An eject notification is sent to the e-mail addresses entered in the E-mail address for eject notification field when the eject begins (includes a list of the media to be ejected) and when the eject is completed. every name used by storage units that refer to it. Lookback days for media going offsite reports Alternate media server names tab Use the Vault Management Properties Alternate Media Server Names tab to add alternate names of NetBackup media servers.

because the media server name for the duplication rule is expanded to include all media server names in the group. you risk a deadlock situation. If you specify only one of the names of that media server. a server can have a fully qualified name. if you do not add alternate media server names. but by the first duplication rule only. you do not have to specify alternate media server names. depending on the media server(s) in use. specify something other than the default. images backed up by it may be identified by an alternate name.Configuring Vault Configuring Vault management properties 77 If you use the default. a short name. all media servers. For example. Choose backups configuration is simplified if you specify media servers (that is. and more than one network interface card. successive rules do not get processed. If you do not. If not. Alternative media server names background A media server may have more than one name. If multiple duplication rules use different media server names that are part of a server name group. you must specify all the names associated with each media server on the Choose Backups tab. Your configuration can send data over the network. you only have to specify one of those names in the Media Servers field of the Profile dialog box Choose Backups tab. If a media server has more than one storage unit. Vault processes only the first duplication rule. use the Media Servers criterion on the Choose Backups tab to ensure that only backups from certain media servers will be selected. The specified media servers must have access to the destination storage unit. All images are processed. Also. all images written by all storage units that use those media server names are processed by the first duplication rule that uses any name from the group. for all of your vaults. each of which has its own name. If a media server has more than one name. ■ ■ ■ . Alternate media server names considerations Be aware of the following associated with alternate media server names: ■ You must have enough drives in the specified destination storage unit to keep up with the demand for duplication. To prevent this situation. all media servers). images identified by the other names will not be vaulted. If you add alternate media server names. each storage unit can use a different name for that media server. you risk a deadlock situation and your Vault job will fail.

highlight it and click Delete. Each server name group should occupy one line in the Media Server Names window. enter all the alternate names for the media server.78 Configuring Vault Configuring Vault management properties Note: Symantec recommends that you specify only one destination storage unit per server. 2 3 In the field below the Media Server Names window. you may create a problem because Vault does not have a mechanism to choose to which destination storage unit to send the duplicate images. The Vault Management Properties dialog box appears. If you specify more than one. select Vault Management Properties from the Actions menu. separated by commas. ■ To remove a media server name group you previously added. highlight it and click Change. To change a name group you previously added. and then click Add. Select the Alternate Media Server Names tab. Adding alternate media server names Use the following procedure to add alternate media server names. ■ . To add alternate media server names 1 From within Vault Management.

Configuring Vault Configuring Vault management properties 79 4 When finished. The following is an example of the Vault Management Properties Retention Mappings tab. To configure retention mappings for a specific vault. Related Topics ■ ■ “Retention mappings overview” on page 80 “Assigning multiple retentions with one profile” on page 156 . Click OK. Select a retention level from the drop-down list. see “Retention mappings tab” on page 87. click OK. Retention mappings tab Global retention mappings. To configure global retention mappings 1 2 3 4 Left-click in the field you want to change in the Vault Retention Level column. Use the Vault Management Properties dialog box Retention Mappings tab to configure alternative retentions for all vaults. Repeat for each level you want to change.

80 Configuring Vault Configuring Vault management properties

Retention mappings overview
Retention mapping lets you assign a retention level to a duplicate image that is based on the retention level of the original image. For example, if the retention of an original image is two weeks, you can configure the mapping so that the duplicate image that is transferred off-site has a retention level of seven years. You configure retention mappings in two places:

The Vault Management Properties dialog box Retention Mappings tab (global) The Vault dialog box Retention Mappings tab (vault specific)

By default, each retention level maps to itself (that is, retention level 0 maps to 0, 1 maps to 1, and so on). To use the retention mappings, you must specify Use Mappings for the retention level during duplication; you can specify normal retention calculation for some duplication rules and alternative retention mappings for other duplication rules. Vault uses the retention mappings in specific-to-global order; if vault-specific retention mappings do not exist, Vault uses the global retention mappings. The retention level for a duplicate image is based on the retention level of the primary backup image. The retention period begins on the date the primary backup image was created, not on the date the duplicate image was created. If the backup policy that created the primary backup image no longer exists, duplication of that image will fail and the job will continue but report status 306 (vault duplication partially succeeded). Retention mapping applies to duplication only; it does not apply if you vault original NetBackup images.

Reports tab
Use the Vault Management Properties global Reports tab to configure the following:
■ ■ ■

Each report that you want generated when a profile runs. Customize report titles. The destinations for each report (e-mail, printer, and location to save).

The values configured on this tab are propagated to the Reports tab of each profile. You can override the values you configure on this tab for any report on any profile.

Configuring Vault Configuring Vault management properties

81

The following is an example of the Vault Management Properties Reports tab.

To change report properties 1 2 Double-click on a report. The Change Report Properties dialog box appears. Select options and enter information as necessary.

If you change a title, the new title will be displayed on the Reports tab and in the Report Type list box when you view Vault reports in the Administration Console. If you consolidate your reports and also change titles, use the same title for all profiles whose reports will be consolidated. The title is printed on the reports and appears in the e-mail subject line if you e-mail the reports. Related Topics

“Vault report types” on page 201

Best Practices

“Ensure report integrity” on page 59

82 Configuring Vault Configuring robots for Vault

Configuring robots for Vault
Use the Vault Robot dialog box to configure the robots from which Vault will eject media.

Vault robot dialog box
Use this dialog box to specify robots that you want to use for your vault. Vault robots contain the media that has images to be stored off-site; that media will be ejected so it can be transferred to the vault. The images can be original images created during a backup job or duplicate images created by a Vault duplication job. You can select any robots that are recognized by NetBackup and that have storage units associated with them. NetBackup assigns a number to each robot that it recognizes, and eligible robots are recognized by Vault. To configure a robot in Vault 1 2 In the NetBackup Administration Console, highlight Vault Management. Open the Actions menu and select New > New Vault Robot. The New Vault Robot dialog box appears.

3

Enter information or select values as appropriate.

Configuring Vault Creating a Vault

83

Table 5-10 describes the fields.

Table 5-10 Property
Robot Number

Robot configuration information Description
The robot number assigned by Media Manager. Media Manager assigns a number to each robot that it recognizes, and eligible robots are recognized by Vault. Based on the robot number that you select, the other fields may be filled in automatically The name the robot. The name is configured in Media Manager, and Vault uses that information to populate the Robot Name field. The robot type as configured in Media Manager. Vault uses that information to populate the Robot Type field. The name of the host that controls the robot. Enter the name of the media server that controls the robot.

Robot Name

Robot Type

Robot Control Host

Select to use the global eject notification e-mail address or enter e-mail Use e-mail address from Vault Management Properties addressees, separated by commas, semicolons, or spaces, that will receive notification when eject begins and ends. for eject notification Eject notification is configured for each profile on the Eject tab, for each robot on the Vault Robot dialog box, and globally for Vault on the Vault Management Properties dialog box General tab; Vault sends the notification to the first e-mail addresses found in that order. You can configure different addresses in each place.

Creating a Vault
After you configure robots, you can create and configure vaults. Use the Vault dialog box to create and configure vaults. Topics
■ ■ ■

“Requirements for creating a Vault” on page 83 “How to create a Vault” on page 84 “Vault dialog box” on page 84

Related Topics

“How Vault uses volume groups and pools” on page 17

Requirements for creating a Vault
The following are the requirements for creating a vault:

At least one robot must be configured already in Vault.

84 Configuring Vault Creating a Vault

A robot may contain multiple vaults, but a vault cannot span robots. Therefore, if you configured three TLD robots for Vault (not connected with pass-through devices), you must define at least three logical vaults, one for each TLD robot. Volumes in a vault must have the same density. If a robot has volumes of different density and you want to use all of those volumes for Vault, that robot must have a separate vault for each volume density.

How to create a Vault
Use the following procedure to create a vault. To create a vault 1 2 3 4 5 6 In the NetBackup Administration Console, expand Vault Management. Highlight a robot in the Vault Management tree. From the Actions menu, choose New > New Vault. The Vault dialog box appears. On the Vault Attributes tab, enter or select values for each field. On the Retention Mappings tab, enter or select values for each field. Click OK.

Vault dialog box
A vault is a logical entity that refers to a collection of removable media drives (usually tape drives) within a robot. You can use vaults to organize the data that is going off-site; for example, you can use one vault for payroll data and another vault for customer data. Configure a vault in the following tabs of the Vault dialog box:
■ ■

“Vault attributes tab” on page 84 “Retention mappings tab” on page 87

Vault attributes tab
Use the Vault Attributes tab in the Vault dialog box to configure the attributes of a vault. If you are configuring a vault in an ACS robot, you also can configure the media access ports (MAPs) to use for eject operations.

Configuring Vault Creating a Vault 85 The following is an example of the Vault Attributes tab. in which you can add or remove MAPs from the Media Access Ports to Use list. Table 5-11 Property Change Vault dialog box configuration options Description For ACS robots only. the Media Access Ports dialog box appears. You may have a separate customer ID for each logical vault. Select if your media is stored in containers at your off-site storage location. Containers of Many Media Customer ID . Related Topics ■ “ACS MAP overview” on page 119 Best Practices ■ ■ ■ “Vaulting paradigm” on page 37 “Preferred vaulting strategies” on page 38 “Use precise naming conventions for volume pools and groups” on page 45 Vault dialog box configuration options The following are the options you can configure in the Vault dialog box:. Your customer identification if you selected Iron Mountain as your vault vendor. the button used to configure media access ports for eject operations. If you click Change.

assuming vault 3 has the maximum number of tapes to vault. Vault moves each piece of ejected media from the Robotic Volume Group into a standalone volume group (that is. To select or change MAPs to use. A Media Access Ports dialog box appears. The name should describe the data. First Off-site Slot ID Media Access Ports to Use For ACS robots only. you can use the default first off-site slot ID of 1. This usually is provided by your vault vendor. the vault vendor. The Robotic Volume Group is the group that indicates media resides in a robot. Vault starts with the off-site slot ID and counts upwards. if the vault vendor has assigned the range 1-2000 and you have defined 3 vaults for this vault vendor. If the off-site volume group does not exist. If you select slots. looking for slots that are no longer in use.86 Configuring Vault Creating a Vault Table 5-11 Property Vault dialog box configuration options (continued) Description The ID of the first slot in the off-site vault. and 1000-2000 to vault 3. it will be created during the vault session. the vault location. in which you can select the MAPs to use. Slots for Individual Media . Select if your media is stored in slots at your off-site storage location. Vault always fills in the gaps with newly vaulted media. then you can assign range 1-499 to vault 1. click Change. the media access ports (MAPs) to use for media ejection for the current vault. With every session. NetBackup creates a robotic volume group when media are added to a robot. 500-999 to vault 2. If the Off-site Volume Group does not exist. Slot IDs are assigned contiguously from the starting slot number. Ensure that the number of media in the vault does not exceed the range of slot IDs assigned by the vault vendor. The off-site volume group name may contain up to 25 characters. If your vendor does not use these identifiers. so a robot can have more than one robotic volume group name associated with it. Off-site slot IDs are often used by the vault vendor to track media. For example. you must divide the range of assigned slots between the various vaults. A robotic library can contain volumes from more than one volume group. it will be created during the vault session. Off-site slot IDs are unique only within a given vault. The Off-site Volume Group indicates that media are in off-site storage. Robotic Volume Group The name of the volume group associated with the robot for this vault. If multiple vaults are defined for the same vault vendor. Usually. a volume group that is not under the control of the robot). Off-site Volume Group The name of the off-site volume group. or a combination thereof so you can easily identify the volume group. you must complete the First Off-site Slot ID field.

Retention mappings tab Vault-specific retention mappings. If you select Iron Mountain. the Use retention mappings from Vault Management Properties is selected by default. For more information about configuring Vault for Iron Mountain electronic processing.) When you open the Vault dialog box Retention Mappings tab. Vault names are case sensitive. .Configuring Vault Creating a Vault 87 Table 5-11 Property Vault Name Vault dialog box configuration options (continued) Description The name of the vault. Note: Directory names are not case sensitive on Microsoft Windows systems. The vault name may contain up to 25 characters. For example. Vault Vendor The name of your off-site vault vendor (for example. see “Reports tab” on page 124. To configure retention mappings for all vaults. session directories are created in the same vault\sessions\vault_name directory for two or more vaults that have names that differ only in case. you also can configure Vault to put media lists into a file formatted in compliance with Iron Mountain’s electronic processing specification. You can then send this file to Iron Mountain for electronic processing of the media lists. The name should reflect its purpose. therefore. see the Vault Management Properties dialog box “Retention mappings tab” on page 79. Use the Retention Mappings tab in the Vault dialog box to configure alternative retentions for a specific vault. Iron Mountain). which populates this tab with the values from the Vault Management Properties dialog box Retention Mappings tab. you might call the vault Finance. if you are creating a vault primarily to duplicate and vault records from the finance department.

To configure vault-specific retention mappings 1 2 3 4 5 If Use retention mappings from Vault Management Properties is selected. Repeat for each level you want to change. . Select a retention level from the drop-down list. Related Topics ■ ■ “Retention mappings overview” on page 80 “Assigning multiple retentions with one profile” on page 156 Creating a profile After you configure vaults. you can create and configure profiles.88 Configuring Vault Creating a profile The following is an example of the Vault dialog box Retention Mappings tab. Click OK. Left-click in the field you want to change in the Vault Retention Level column. Use the Profile dialog box to configure profiles. clear the check box by clicking it.

and generate reports. it contains the rules for selecting.Configuring Vault Creating a profile 89 Profile dialog box A Vault profile is a template for a vault job. You must select at least one of the following steps when you create a new Vault profile: ■ ■ ■ Duplication Catalog Backup Eject The other steps are optional so you can separate the Vault tasks into separate jobs if desired. and ejecting media. use a Vault policy to schedule when it should run. one to duplicate and one to eject media and generate reports. eject media. you may require only one profile to choose backups. you may require only one profile. If you have only one vault and: ■ duplicate and eject media on a regular schedule (such as daily or weekly). and at least one profile must exist for every vault. A vault can contain multiple profiles. After you create a profile. You can select or deselect any of these steps at any time during the configuration process. If you have more than one Vault. Related Topics ■ “Scheduling a Vault session” on page 130 The number of profiles required The number of profiles required depends on your operations. although two profiles within the same vault cannot run simultaneously. Vault original images. For example. duplicate images daily and eject weekly. . All profiles select images (that is. Choose Backups). and another job to eject media and generate reports weekly. you can use one job to select and duplicate images daily. duplicating. you require two profiles. using different jobs to accomplish different tasks. ■ ■ Symantec recommends that you do your duplication with as few Vault jobs as possible. A profile is associated with a specific vault. See “Maximize drive utilization during duplication” on page 58. Two different profiles can run simultaneously if each profile is in a different vault and if each profile uses a different off-site volume pool. you will have more than one profile.

For efficient disaster recovery. Select the steps you want this profile to perform. 4 Configuring a profile After you create a profile. you can change the selections when you configure the profile. Because you must always configure the choose backups step. The New Profile dialog box includes the following five tabs: ■ The Choose Backups tab is where you specify the criteria for selecting backup images. choose New > New Profile. The Duplication tab is where you configure duplication of the selected backup images. the New Profile: profile name dialog box appears. Symantec recommends that you use descriptive names. From the Actions menu. However. The New Profile dialog box appears. 2 3 In the Name field. ■ ■ . Click OK.90 Configuring Vault Configuring a profile How to create a profile To create a profile 1 Highlight a vault in the NetBackup Administration Console. The Catalog Backup tab is where you choose which catalog backup policy and schedule to use for creating a Vault catalog backup. type a name for the profile. Profile names are case sensitive. it is not displayed on this dialog box. you should vault a new catalog backup each time you vault data. You must select at least one step. The New Profile: profile name dialog box appears.

and another profile to eject media and generate reports weekly. . highlight a profile in the NetBackup Administration Console window and select the Change icon in the toolbar. using different jobs to accomplish different tasks. you can use one profile to select and duplicate images daily. Select the tab for each step that you are configuring and complete the fields. The Reports tab is where you choose which reports to generate. For example.Configuring Vault Configuring a profile 91 ■ The Eject tab is where you choose in which off-site volume pools Vault should look for the media you want to eject. The other steps are optional so you can separate the tasks into separate jobs if desired. To configure a profile 1 2 3 If the Profile dialog box is not displayed. click OK. ■ A profile must select images (Choose Backups). When finished.

The criteria contained in the Location field represent physical locations of the images to backup. The default setting of these two criteria. if you are duplicating images. Or. The image selection process chooses all images in the NetBackup catalog that match the criteria that you select under Attribute and Location. even images that are in a different vault. Finally. The most basic criterion you can set is the time frame. For the most broad search coverage. however. you can refine your search using only criteria from the Attribute field. The criteria that you specify on the other tabs in the Profile dialog box determine whether Vault includes or excludes the images that are selected.92 Configuring Vault Configuring a profile Choose backups tab Use the Choose Backups tab to configure the search for images to be vaulted. The image selection process may select catalog backup images. This will include all criteria in your profile. you should leave the Attribute and Location check boxes empty and in their default state. Vault ejects the media on which those images reside if that media is assigned to a volume pool that is listed in the Off-site Volume Pools list on the Eject tab. Vault does not duplicate existing catalog images. which means all criteria in that particular field will be included in the search for an image to vault. or search physical locations by using the criteria in the Location field. is for the check boxes to be unselected. To refine the search for images to vault. Vault compares images in the NetBackup database with the criteria defined in the Choose Backups tab and generates a list of images that match the criteria. . The Choose Backups tab enables you to quickly configure how you select criteria for your profile. you can choose to restrict your search to cover very specific areas by utilizing various criteria in the Attribute and the Location fields. The criteria contained in the Attribute field are logical criteria to help you refine your search. you can select Attribute and Location to configure the advanced options.

Backup Policies . Policies are based on the storage unit used for backups. if the check box is not checked. A list of policies to use to select backup images. because storage units are related to a specific robot number. or by default if the Attribute check box is not checked. click Change then choose the backup policies you want to include in the profile.Configuring Vault Configuring a profile 93 The following is an example of the Choose Backups tab: Topics ■ “Choose backups tab configuration options” on page 93 Related Topics ■ “The list of images to be vaulted” on page 138 Best Practices ■ “Overlap the time window in the profile” on page 40 Choose backups tab configuration options The following are the options you can configure in the Choose Backups tab: Table 5-12 Property Attribute Choose Backups tab configuration options Description A filter enabling you to choose which logical attributes you want to use when searching for an image to vault. choose the policies by robotic device. Enabled if you select this criteria in the Attribute field. To change the backup policies. all criteria in this field are included in the search. By default.

or by default if the Location check box is not checked. relative to the time of the session. <server>:<path> (storage unit). for example. Time is expressed in terms of days and hours. or by default if the Attribute check box is not checked. Enabled if you select this criteria in the Location field. Note: An individual basic disk from this list would also display the storage unit name in parenthesis. To change the clients.94 Configuring Vault Configuring a profile Table 5-12 Property Backups Started Choose Backups tab configuration options (continued) Description The period of time from which the profile will select backups relative to the start time of the session. click Change then choose the basic disks that you want to include in this profile. the Include all basic disks is selected. The clients for which to select backup images. Change Button used to display a dialog box to change any of the criteria selected in the Attribute or Location fields. click Change then choose the clients you want to include in this profile. By default. in the form of <server>:<path>. An image will be selected for duplication or vaulting if its primary copy resides in any of the selected basic disk paths. An image will be selected for duplication or vaulting if its primary copy resides in any of the specified basic disks. count backwards from October 12. if you are duplicating images. the default time range is between 8 days and 1 day before the session runs. Clients . assume the following settings: between 8 day(s) 0 hour(s) ago and 1 day(s) 0 hour(s) ago If the session is started on October 12 at 1:00 pm. To change the basic disks. Selecting Basic disks refines your search to those paths that are selected. Basic disks A list of basic disk paths. If you are selecting original backup images to send off site. the default time range is between 7 and 0 days. The vaulted backups will be those started between October 4 at 1:00 pm (8 days before) and October 11 at 1:00 pm (1 day before). For example. Enabled if you select this criteria in the Attribute field.

. By default. Schedules A list of schedules to use to select backups. the Include all retention levels is selected. To change the default. “disk pool (storage unit)”. Enabled if you select this criteria in the Attribute field. By default. click Change then choose the media servers you want to include in this profile. or by default if the Attribute check box is not checked. Enabled if you select this criteria in the Attribute field.Configuring Vault Configuring a profile 95 Table 5-12 Property Disk pools Choose Backups tab configuration options (continued) Description A list of disk pools that you can choose search for an image to duplicate or vault. click Change then choose the level or levels that you want to include in this profile. because storage units are related to a specific robot number. or by default if the Attribute check box is not checked. click Change then choose the schedules you want to include in this profile. Enabled if you select this criteria in the Location field. Location A filter enabling you to choose which physical location you want to search for an image to vault. An image would be selected for duplication or vaulting if the retention level of the primary copy matches any of the values selected in the list. or by default if the Location check box is not checked. Media servers Retention levels A list of retention levels that you can use to further refine your search criteria. Enabled if you select this criteria in the Attribute field. Applies to NetBackup Enterprise Server only. for example. choose the schedules by robotic device. By default. An image will be selected for duplication or vaulting if its primary copy resides in any of the specified disk pools. Note: An individual disk pool from this list would also display the storage unit name in parenthesis. or by default if the Attribute check box is not checked. the Include all disk pools is selected. if the check box is not checked. To change the retention level. all criteria in this field are included in the search. The media servers from which to select backup images. To change the media servers. To change the disk pools. click Change then choose disk pools that you want to include in this profile. Schedules are based on the storage unit used for backups.

96 Configuring Vault Configuring a profile Table 5-12 Property Choose Backups tab configuration options (continued) Description This selection criterion contains a list of Volume Groups from which to select backup images. Enabled if you select this criteria in the Attribute field. Only those types for which you have configured policies will be available for selection. you can choose the backup type. or by default if the Attribute check box is not checked. if you select “Exclude All” for “source volume groups” it would automatically mean “Exclude All” for “volume pools” as well. If you want to vault all types of backups. or by default if the Location check box is not checked. Enabled if you select this criteria in the Location field. incremental. Usually. Source Volume Groups Backup Types The types of backups (full. Note: If you want to exclude all tape images from this profile. accept the default. and so on) the profile will capture. The images that are read are in the Source Volume Group in one robot. To change the default. To change the default. click Change then choose the backup types you want to include in this profile. then you should select the Exclude All check box. Selecting Source Volume Groups restricts the search for images to those in either all volume groups or the specific volume groups that you choose to include in your search. An image will be selected for duplication or vaulting if any fragment of its primary copy is found in a media that is from any of the selected volume groups. Depending on the different types of backups you have configured in NetBackup policy management. . This is an optional criterion. a Source Volume Group is specified if your master server has access to multiple robots and you want to duplicate images that reside on media in one robot to media in another robot. This would mean there would be no effect of the selection from “ Volume Pools” criterion as both of them apply to tape images. So. the images are written to media in the Robotic Volume Group in another robot. click Change then choose the volume groups you want to include in this profile.

So. then you should select “Exclude All” check box. This would mean there would be no effect of the selection from “Source Volume Groups” criterion as both of them apply to tape images. Selecting Volume pools restricts the search for images to those in either all volume pools or just the volume pools that you choose to include in your search. By default. if you select “Exclude All” for “volume pools” then it would automatically mean “Exclude All” for “Source Volume Groups” as well. click Change then choose the volume pool or pool s that you want to include in this profile. To change the volume pools. An image will be selected for duplication or vaulting if any fragment of its primary copy is found in a media that is from any of the selected volume pools. To change the default.Configuring Vault Configuring a profile 97 Table 5-12 Property Volume pools Choose Backups tab configuration options (continued) Description A list of volume pools that you can choose to include in your search for an image to duplicate or vault. click Change then choose the volume pools you want to include in this profile. the Include all Volume pools is selected. Enabled if you select this criteria in the Location field. . Note: If you want to exclude all tape images from this profile. or by default if the Location check box is not checked.

media server (advanced configuration only). a storage unit. and what to do if an image copy fails (multiple copies only). Topics ■ ■ ■ ■ ■ ■ “The primary backup copy” on page 99 “Basic duplication” on page 99 “Advanced duplication” on page 100 “Duplication tab configuration options” on page 102 “Multiple copies dialog box” on page 106 “Duplication Rule dialog box” on page 108 . retention period. Duplication is optional. if you create multiple original backup copies concurrently during a backup job and vault one of the originals.98 Configuring Vault Configuring a profile Duplication tab Use the Duplication tab of the Profile dialog box to configure the rules used to duplicate images and to configure other duplication attributes. off-site volume pool. The following shows the basic Duplication tab: Prerequisites ■ Create one or more dedicated off-site volume pools. A duplication rule specifies the number of copies to create. See “Off-site volume pools” on page 63. you do not need to duplicate images in Vault.

Vault will duplicate from a nonprimary copy on disk if one exists and the primary copy is on removable media. The first backup image created successfully by a NetBackup policy is the primary backup. You can create multiple copies of each backup image concurrently. but they are created using the same duplication rule. NetBackup also designates one of the backup images as the primary backup copy. it is the primary copy. All backups are duplicated according to the same rule. you cannot duplicate the image until the media is injected into the robot or a local copy (if available) is promoted to primary.Configuring Vault Configuring a profile 99 ■ “Treatment of images without corresponding duplication rule” on page 112 Best Practices ■ ■ ■ ■ “Avoid resource contention during duplication” on page 47 “Avoid sending duplicates over the network” on page 53 “Increase duplication throughput” on page 56 “Maximize drive utilization during duplication” on page 58 The primary backup copy NetBackup assigns an ordinal number to each copy of a backup image written by a backup policy. that number designates its sequence of creation. If the primary copy is off site.) If you send the primary copy off site and you duplicate images in Vault. if only one copy of a backup image is created. Vault duplicates from the primary copy. Best Practices ■ “Designate a primary copy and keep it on site” on page 45 Basic duplication In basic duplication. NetBackup automatically promotes the backup copy that has the lowest number to primary. Exception: for improved performance. Because both NetBackup and Vault use the primary copy. When the primary copy expires. (Exception: Vault will duplicate from a nonprimary copy on disk if one exists. whether it exists on disk or removable media. . in most circumstances if a primary copy is on removable media it should remain in a robot. NetBackup uses the primary copy to satisfy restore requests. you specify only one duplication rule. Usually. you can designate one of the copies that remains in the robot as the primary copy. and all selected images controlled by the specified master server are duplicated.

In this context. If a duplication rule does not specify an alternate read server. For example. you may want to send the duplicate copies of all backup images written by one media server to a storage unit of one density and all backup images written by another media server to a storage unit of another density. you may want to keep your customer database in off-site storage for a longer period of time (a different retention) than your warehouse inventory data. In this case. the media server does not have any effect other than to identify which rule to apply to each image. For that one media server you would specify an alternate read server. if media server A backs up your customer database and media server B backs up warehouse inventory data.100 Configuring Vault Configuring a profile Advanced duplication Note: Alternate read servers and multiple media servers apply to NetBackup Enterprise Server only. For example. Use advanced configuration only if you need to control exactly how to assign the backup images to be duplicated. each writing different types of data that require different retention periods. do the following: . you may want to balance the duplication job between multiple storage units. You have one media server that you need reserved for other operations. and you would let the rest of the media servers handle their own duplication. The following may help you understand why to use advanced configuration: ■ Your robot has different types of drives or media so that you have different storage units to use as destinations for the duplication process. Vault determines which media server wrote each backup image and then applies the duplication rule corresponding to that media server to that image. you use multiple media servers for duplication but dedicate one media server for backups. ■ ■ Note: You do not need to configure advanced options if your profile duplicates images backed up by a single media server. the media server that originally wrote the backup image will be used to read the original backup image during the duplication process. To avoid sending data over the network. Advanced duplication lets you specify more than one duplication rule. Your profile is duplicating backup images to different media servers. For example.

ensure that: ■ ■ The alternate read server is connected to all robots that have backup images written by the media server specified for this rule.Configuring Vault Configuring a profile 101 ■ For each duplication rule that does not specify an alternate read server. ensure that the media server controls both the source volumes and the destination storage units. For each duplication rule that specifies an alternate read server. The alternate read server is the same server as the media server of the destination storage unit. ■ The following shows the Duplication tab when Advanced Configuration has been selected: .

Configure For basic duplication only. If you selected Alternate Read Server on the Duplication tab. Table 5-13 Property Alternate Read Server Duplication tab configuration options Description Applies to NetBackup Enterprise Server only.102 Configuring Vault Configuring a profile Duplication tab configuration options Table 5-13 describes configuration options for the Duplication tab. If robots (or drives) are shared by more than one media server. click New to configure duplication rules). the button used to display the Duplication Rule dialog box so you can change a destination media server and duplication rules for that server. Delete Duplicate Smaller Images First . the button used to delete the selected destination media server and duplication rules for that server. select Alternate Read Server then select a media server from the drop-down menu (or for advanced duplication. the Duplication Rule dialog box will have fields for both Source Media Server and Alternate Read Server. For advanced configuration only. This choice does not affect the total time required to duplicate the images. Select to duplicate images in smallest to largest order. the button used to display the Multiple copies dialog box. Change For advanced configuration only. Using an alternate read server may transfer data over your network. affecting your site’s computing environment. you can select this option so that those images are duplicated before the larger images. The name of an alternate read server. To configure an alternate read server. By default this option is disabled. If you did not select Alternate Read Server. you can designate a different media server to read the original backups than the media server that wrote the backups. only a Source Backup Server field appears. The Source Media Server and Alternate Read Server may be the same. By default. Vault duplicates images from largest to smallest. If you know that your most important data is in smaller backup images. which improves tape drive utilization during duplication and duplicates more data sooner.

All duplication jobs for the profile run at the same priority. lets NetBackup choose the media owner. and Vault duplicates from the primary backup. which is the default. the imageDB cleanup process performs the expiration of eligible images as a separate operation. Specify a server group. Make This Copy Primary Whether the copy should be designated the primary backup. Only designate a duplicate as the primary if the primary backup is ejected and transferred off site. then the images will be expired immediately after a successful Vault duplication occurs. No media server is specified explicitly. ■ . restores. however. as follows: ■ ■ Any. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. In addition.Configuring Vault Configuring a profile 103 Table 5-13 Property Duplication tab configuration options (continued) Description The priority to assign to the Vault duplication jobs. All server groups that are configured in the NetBackup environment appear in the drop-down list. If the duplication of a disk image is not successful. and you have configured continue as the fail option. the disk image will not be expired. By default. None specifies that the media server that writes the image to the media owns the media. and synthetic backups is assigned in the master server Global Properties. You can use this option to set an earlier time for the images to become eligible to expire. from 0 to 99999. the first successful copy is the primary copy. assign a higher priority to the Vault jobs than to other NetBackup processes. A larger number is higher priority. If the copy that you indicate as primary fails. A server group. You can change this default value using the Image DB Cleanup Interval option on the "Cleanup" node of Master Server Host Properties on the NetBackup Administation Console or the bpconfig –cleanup_int command. if the number of hours (X) equals zero. Specify the media owner from the drop-down list box. The imageDB cleanup process is run every 12 hours by default. Duplication Job Priority Expire Original Disk Backup Images The delay (in hours) until duplicated backup images become eligible to expire after the Vault session runs (applies only if the backup images are on disk). If you want your Vault duplication jobs to obtain resources before other processes. Vault duplication jobs compete with other process in NetBackup (such as regularly scheduled backups) for resources. Refer to the NetBackup Commands document for more information about this command. NetBackup chooses a media server or a server group (if one is configured). but you want a media server to own the media. Priority for backups. the original backup image created during a NetBackup policy job is the primary copy. NetBackup restores from the primary backup. Media Owner The name of the owner of the media onto which you are duplicating images. including tape drives.

When you enter a number of read drives. You must have an equivalent number of read and write drives available. the same number will be entered into the Destination Write Drives field. click Configure to display the Multiple copies dialog box. or Primary Copy on the basic Duplication tab. If you select Multiple Copies. you cannot configure a Storage Unit. New Number of Read Drives The number of drives to use for reading backup images. but slows down restores and disaster recovery processes. If the option to preserve multiplexing is selected. Preserve Multiplexing . If you did not select Alternate Read Server.104 Configuring Vault Configuring a profile Table 5-13 Property Multiple Copies Duplication tab configuration options (continued) Description Whether to create multiple copies concurrently. For advanced configuration only. Retention Level. Multiplexing is the process of sending concurrent-multiple backup images from one or more clients to the same piece of media. This process speeds up duplication. If the source image is multiplexed and the Preserve Multiplexing option is selected. in which you can add a destination media server and duplication rules for that server. Multiplexing is configured in NetBackup Management > Storage Units. If you configure multiple copies. However. If you selected Alternate Read Server on the Duplication tab. only a Source Backup Server field appears. Volume Pool. You can select Multiple Copies if the master server properties allow it. Multiplexing does not apply to disk storage units or disk staging storage units as destinations. the multiplexed duplication process will occur for all multiplexed images that are selected for duplication during a given Vault session. if the source is a multiplexed tape and the destination is a disk storage unit or disk staging storage unit. selecting Preserve Multiplexing ensures that the tape is read on one pass rather than multiple passes. the Duplication Rule dialog box will have fields for both Source Media Server and Alternate Read Server. ensure that the destination storage unit configured for each copy has multiplexing enabled. the button used to display the Duplication Rule dialog box. Whether to preserve multiplexing.

Each copy has a separate expiration date. Storage Unit Volume Pool The name of the off-site volume pool to which Vault assigns the duplicate media. disk staging storage units. disk storage units. Write Drives . Images on media in the off-site volume pool will be ejected for transfer off-site. To ensure that two processes do not try to use the same volume at the same time. Because of potential NDMP performance limitations. or Network Data Management Protocol (NDMP) storage units. If the duplicated backup images are to be vaulted. If you specify Use Mappings for the retention level. see “Assigning multiple retentions with one profile” on page 156. If you specify a numeric retention level. the expiration date for the duplicate media is calculated by adding the specified retention period to the date the original backup was created. Storage units can be Media Manager storage units. The name of a storage unit that contains the resources to which the copies of the backup images will be written. The location of the backup images: disk or removable media or both.Configuring Vault Configuring a profile 105 Table 5-13 Property Retention Level Duplication tab configuration options (continued) Description The retention level for the copy. If a retention level is not specified. The number of write drives. NetBackup does not verify in advance that the media ID selected for the duplicate copy is different than the media that contains the original backup. the media in the destination storage unit must be in the Robotic Volume Group. When the retention period expires. specify a different volume pool. the expiration date will be the same as the original. If the Media Manager or NDMP storage unit has more than one drive. Vault will duplicate images from the primary backup images on removable media or from backup images on disk. Symantec suggests that you duplicate between drives that are directly attached to the same NDMP host. the source and destination storage units can be the same. the retention period is based on the retention period of backup image copy 1 For more information. the volume will be recalled from off-site storage. information about the expired backup will be deleted from the NetBackup and Media Manager catalog. Do not use the volume pool that was used for the original backup. and the backup image will be unavailable for a restore. NDMP storage units are supported only when one copy is created per duplication rule. All storage units must be connected to the same media server. Skip the Duplication Step Source Backups Reside On Select if you do not want to configure duplication. This value is the same as the number of read drives.

Table 5-14 Property Copies Multiple Copies dialog box configuration options Description The number of copies to create concurrently. . The following table describes configuration options for the Multiple Copies dialog box.) By default.106 Configuring Vault Configuring a profile Multiple copies dialog box The Multiple Copies dialog box appears only if you select the Multiple Copies checkbox on the basic Duplication tab and then click Configure. Use this dialog box to create multiple copies of a backup image concurrently. (Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. the value is two: one original backup and one copy. You can create up to 4 or the number of copies specified in the Maximum Backup Copies field for the NetBackup master server (if less than 4).

if you choose Fail All Copies. the option is configured to Fail All Copies in Vault. Vault will again try to duplicate the image if the following conditions are true: ■ ■ For Each Image. which is the default. If the copy that you indicate as primary fails. The Vault profile did not eject the primary backup. and you have configured continue as the fail option. all copies of that image will fail.Configuring Vault Configuring a profile 107 Table 5-14 Property Multiple Copies dialog box configuration options (continued) Description The action to perform if a copy fails: Continue or Fail All Copies. By default. NetBackup chooses a media server or a server group (if one is configured). but you want a media server to own the media. If you choose Continue for all copies. If This Copy Fails The image is selected. ■ Primary Whether the copy should be designated the primary backup. By default. A server group allows only those servers in the group to write to the media on which backup images for this policy are written. it is probable that at least one copy will succeed. NetBackup restores from the primary backup. A server group. the original backup image creating during a NetBackup policy job is the primary copy. independent of the success or failure of other image copy operations. Vault considers the duplication job successful if any of the copies succeed. lets NetBackup choose the media owner. . The next time the Vault profile runs. it is possible that a copy of the image may never get vaulted. see “Continue or fail for concurrent copies” on page 178. and Vault duplicates from the primary backup. None specifies that the media server that writes the image to the media owns the media. All server groups that are configured in the NetBackup environment appear in the drop-down list. Only designate a duplicate as the primary if the primary backup is ejected and transferred off site. the first successful copy is the primary copy. No media server is specified explicitly. Specify a server group. Media Owner The name of the owner of the media onto which you are duplicating images. Specify the media owner from the drop-down list box. In Vault. but it may not be the copy assigned to the off-site volume pool. For more information. However. as follows: ■ ■ Any.

For more information. Storage Unit The name of a storage unit that contains the resources to which the copies of the backup images will be written. see “Assigning multiple retentions with one profile” on page 156. If you specify a numeric retention level. If the Media Manager or NDMP storage unit has more than one drive. Because of potential NDMP performance limitations.108 Configuring Vault Configuring a profile Table 5-14 Property Retention Multiple Copies dialog box configuration options (continued) Description The retention level for the copy. Storage units can be Media Manager storage units. the volume will be recalled from off-site storage. The number of write drives. the expiration date will be the same as the original. specify a different volume pool. Symantec suggests that you duplicate between drives that are directly attached to the same NDMP host. When the retention period expires. and the backup image will be unavailable for a restore. Volume Pool The name of the off-site volume pool to which Vault assigns the duplicate media. If you specify Use Mappings for the retention level. Do not use the volume pool that was used for the original backup. disk storage units. If the duplicated backup images are to be vaulted. Images on media in the off-site volume pool will be ejected for transfer off-site. If you selected Alternate . All storage units must be connected to the same media server. the expiration date for the duplicate media is calculated by adding the specified retention period to the date the original backup was created. NetBackup does not verify in advance that the media ID selected for the duplicate copy is different than the media that contains the original backup. NDMP storage units are supported only when one copy is created per duplication rule. the retention period is based on the retention period of backup image copy 1. or Network Data Management Protocol (NDMP) storage units. Each copy has a separate expiration date. Write Drives Duplication Rule dialog box The Duplication Rule dialog box appears if you select New or Change on the Advanced Configuration options of the Duplication tab. To ensure that two processes do not try to use the same volume at the same time. information about the expired backup will be deleted from the NetBackup and Media Manager catalogs. This value is the same as the number of read drives. the media in the destination storage unit must be in the Robotic Volume Group. the source and destination storage units can be the same. disk staging storage units. If a retention level is not specified.

Backup Server Applies to NetBackup Enterprise Server only. If robots (or drives) are shared by more than one media server. an Alternate Read Server option appears on the dialog box. you can designate a different media server to read the original backups than the media server that wrote the backups. affecting your site’s computing environment. Use the Duplication Rule dialog box to create multiple copies of an image and to select different media servers and read servers for the copies.Configuring Vault Configuring a profile 109 Read Server on the Duplication tab. Using an alternate read server may transfer data over your network. Table 5-15 Property Alternate Read Server Duplication Rule dialog box configuration options Description Applies to NetBackup Enterprise Server only. The Media Server and Alternate Read Server may be the same. select a media server from the drop-down menu. To configure an alternate read server. The following table describes configuration options for the Duplication Rule dialog box. . Appear if Alternate Read Server was not selected on the Duplication tab. The name of the media server on which the backup images reside. The name of an alternate read server.

All server groups that are configured in the NetBackup environment appear in the drop-down list. The Vault profile did not eject the primary backup. it is possible that a copy of the image may never get vaulted. it is probable that at least one copy will succeed. However. You can create up to 4 or the number of copies specified in the Maximum Backup Copies field for the NetBackup master server (if less than 4). A server group. Media Owner The name of the owner of the media onto which you are duplicating images. lets NetBackup choose the media owner. For more information. In Vault.110 Configuring Vault Configuring a profile Table 5-15 Property Copies Duplication Rule dialog box configuration options (continued) Description The number of copies to create concurrently. independent of the success or failure of other image copy operations. the value is two: one original backup and one copy. The name of the media server on which the backup images reside. No media server is specified explicitly. A server group allows only those servers in the group to write to the media on which backup images for this policy are written.) By default. NetBackup chooses a media server or a server group (if one is configured). which is the default. the same number will be entered into the Destination Write Drives field. The action to perform if a copy fails: Continue or Fail All Copies. Vault considers the duplication job successful if any of the copies succeed. but it may not be the copy assigned to the off-site volume pool. see “Continue or fail for concurrent copies” on page 178. If you choose Continue for all copies. The next time the Vault profile runs. ■ Media Server Applies to NetBackup Enterprise Server only. If This Copy Fails The image is selected. Vault will again try to duplicate the image if the following conditions are true: ■ ■ For Each Image. . (Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. The Media Server and Alternate Read Server may be the same. Specify the media owner from the drop-down list box. None specifies that the media server that writes the image to the media owns the media. You must have an equivalent number of read and write drives available. Specify a server group. as follows: ■ ■ Any. if you choose Fail All Copies. but you want a media server to own the media. By default. all copies of that image will fail. the option is configured to Fail All Copies in Vault. Appears only if Alternate Read Server was selected on the Duplication tab. Number of Read Drives The number of drives to use for reading backup images. When you enter a number of read drives.

Vault will duplicate images from the primary backup images on removable media or from backup images on disk. the retention period is based on the retention period of backup image copy 1.Configuring Vault Configuring a profile 111 Table 5-15 Property Primary Duplication Rule dialog box configuration options (continued) Description Whether the copy should be designated the primary backup. the expiration date will be the same as the original. By default. When the retention period expires. Storage Unit . information about the expired backup will be deleted from the NetBackup and Media Manager catalog. and you have configured continue as the fail option. or Network Data Management Protocol (NDMP) storage units. Only designate a duplicate as the primary if the primary backup is ejected and transferred off site. If the copy that you indicate as primary fails. the media in the destination storage unit must be in the Robotic Volume Group. If you specify a numeric retention level. disk storage units. and Vault duplicates from the primary backup. see “Assigning multiple retentions with one profile” on page 156. If you specify Use Mappings for the retention level. All storage units must be connected to the same media server. If the duplicated backup images are to be vaulted. Symantec suggests that you duplicate between drives that are directly attached to the same NDMP host. the original backup image creating during a NetBackup policy job is the primary copy. the expiration date for the duplicate media is calculated by adding the specified retention period to the date the original backup was created. The name of a storage unit that contains the resources to which the copies of the backup images will be written. the first successful copy is the primary copy. Storage units can be Media Manager storage units. If the Media Manager or NDMP storage unit has more than one drive. Each copy has a separate expiration date. If a retention level is not specified. the source and destination storage units can be the same. For more information. Source Backups Reside On The location of the backup images: disk or removable media or both. NetBackup restores from the primary backup. disk staging storage units. and the backup image will be unavailable for a restore. Because of potential NDMP performance limitations. the volume will be recalled from off-site storage. NDMP storage units are supported only when one copy is created per duplication rule. Retention The retention level for the copy.

In some cases. To ensure that two processes do not try to use the same volume at the same time. Vault will duplicate those images but will try to minimize total duplication time by keeping as many drives as possible busy writing data until all images are duplicated. Write Drives Treatment of images without corresponding duplication rule Note: More than one media server applies to NetBackup Enterprise Server only. images written by media servers that have no corresponding duplication rule must also be duplicated. Vault will begin to assign images written by other media servers (media servers that have no rule of their own) to the duplication rule that had finished processing. Do not use the volume pool that was used for the original backup. This is handled as follows: ■ All images written by media servers that have a duplication rule are assigned to the appropriate duplication rule.112 Configuring Vault Configuring a profile Table 5-15 Property Volume Pool Duplication Rule dialog box configuration options (continued) Description The name of the off-site volume pool to which Vault assigns the duplicate media. This value is the same as the number of read drives. As soon as one duplication rule has finished processing the images assigned to it. specify a different volume pool. ■ . If this happens. NetBackup does not verify in advance that the media ID selected for the duplicate copy is different than the media that contains the original backup. Images on media in the off-site volume pool will be ejected for transfer off-site. The number of write drives. the profile may list more media servers in the Media Servers list on the Choose Backups tab than in the advanced configuration view on the Duplication tab.

Eventually all images written by all media servers listed on the Choose Backups tab will be duplicated and the duplication step will be complete. . All alternate read servers must be connected to all robots that have images written by any media server listed on the Choose Backups tab but not on the Duplication tab. ■ The previous configurations are best suited for a SAN environment where all media servers are visible to all robots. For each duplication rule.Configuring Vault Configuring a profile 113 ■ As other rules complete the duplication of their assigned images. they too will be assigned images written by other media servers that have no rule of their own. the alternate read server must be the same as the media server of the destination storage unit(s). If you have more media servers listed on the Choose Backups tab than on the Duplication tab. there is only one way to ensure that large amounts of duplication data do not get sent over the network: ■ ■ Every duplication rule must specify an alternate read server.

which can back up the catalogs even when other NetBackup or Vault activity is occurring. cold catalog backup that cannot occur when regular back up activity is occurring.) You must add the Vault catalog backup volume pool to the eject list on the Eject tab. (NetBackup provides two types of catalog backup. At least one NBU-Catalog policy that includes a Vault Catalog Backup schedule must exist so you can specify them on the Catalog Backup tab. Create a Vault Catalog Backup schedule in an NBU-Catalog policy. See “Off-site volume pools” on page 63. The following is the Catalog Backup tab: Prerequisites ■ Create a dedicated off-site volume pool. See “Catalog backup schedules for Vault” on page 65. Vault uses the online. hot catalog backup method. ■ Topics . the other type is an offline.114 Configuring Vault Configuring a profile Catalog backup tab Use the Profile dialog box Catalog Backup tab to specify the catalog backup policy and schedule that will perform the Vault catalog backup.

Therefore. . including the files backed up and the media on which they are stored. (NetBackup uses a special backup policy of type NBU-Catalog to perform catalog backups. it does not occur on the schedule defined in the NBU-Catalog policy. Vault will not duplicate existing catalog images. A Vault Catalog Backup schedule always performs a full backup of the entire NetBackup catalog. If you vault your regular NetBackup catalog backups. they will not appear on the Recovery Report but will appear on other reports. Vault creates a new catalog backup with up-to-date information. Symantec believes that it is better to vault the data without a catalog backup than to fail the job and vault nothing at all for that session. Data will be vaulted with no associated catalog backup. The Recovery Report for Vault shows the three most recent Vault catalog backups. To perform a Vault catalog backup. but it will eject the media on which those images are stored if both of the following are true: ■ ■ Those images are selected during the choose backups step. it does not duplicate an existing NetBackup catalog backup. You can create multiple copies concurrently of a Vault catalog backup. The media is assigned to the dedicated Vault catalog volume pool. If the catalog backup step fails but the remainder of the Vault job succeeds. Vault uses a special schedule of type Vault Catalog Backup in an NBU-Catalog policy.) A Vault catalog backup occurs when a profile that performs catalog backup runs. A NetBackup catalog backup is not a substitute for a Vault catalog backup because it does not include the latest information about duplicated media and media location. the session will end with a status 294 (vault catalog backup failed).Configuring Vault Configuring a profile 115 ■ ■ ■ ■ “Vault catalog backup overview” on page 115 “Catalog backup policy settings” on page 116 “Critical policies overview” on page 116 “Catalog backup tab configuration options” on page 117 Best Practices ■ “Vault NetBackup catalogs” on page 44 Vault catalog backup overview NetBackup catalogs are databases that contain information about the NetBackup configuration and backups. you should perform the catalog backup step in Vault.

The catalog backup job competes for resources with other backup jobs. you do not specify the catalog files to include in the Vault catalog backup. Specify the destination in the Vault Catalog Backup schedule. and you cannot add other files to the catalog backup. You also must specify the same volume pool on the Eject tab of the profile. Specify multiple copies on the Vault Catalog Backup schedule Attributes tab and then specify the number of copies on the Configure Multiple Copies dialog box. ■ ■ ■ ■ Critical policies overview A new NetBackup catalog policy option. You can create multiple copies of the catalog. The media that contains the backup images from those critical policies are listed in the new NetBackup disaster recovery report. You can specified the priority for the job. including disk and removable media storage units. critical policies. (Vault does not include critical policy data in its catalog backups. Beginning with NetBackup 6. see the NetBackup Administrator’s Guide. If you use removable media storage units. Destination. Volume I. A new NetBackup catalog policy option. lets you select policies that should be recovered before backups from other policies are recovered.116 Configuring Vault Configuring a profile For information about the location of the NetBackup catalog and the files included in a catalog backup. Critical policies. Specify critical policies on the policy Disaster Recovery tab. either on the policy Attributes tab (single catalog backup) or on the Configure Multiple Copies dialog box of the Vault Catalog Backup schedule. lets you select policies that should be recovered before backups from other policies are recovered.) The media from those critical policies also will be listed in the Vault Recovery Report so you can recall the media from those policies and recover that data before you recover data that is not as critical. Catalog backup policy settings Although you configure only two options on the Catalog Backup tab. You can send the catalog backup to any storage unit. . critical policies. Number of copies.0. and you can send them to any storage unit that is attached to the destination media server. settings in the catalog backup policy affect the Vault catalog: ■ Job priority. you must specify a volume pool for the catalog backup in the Vault Catalog Backup schedule. Volume pool.

Partial recovery means you can choose which parts of the catalog backup to restore and in what order. The drop-down list includes all Vault Catalog Backup schedules for the policy selected in Catalog Backup Policy field. Vault Catalog Backup Schedule The schedules available for the catalog backup policy. Select if you do not want to back up and vault the NetBackup and Media Manager catalogs. Partial recovery lets you restore part of the catalog. For information about specifying critical policies in an NBU-Catalog policy. you need a separate NBU-Catalog policy for Vault. During catalog recovery. Catalog backup tab configuration options The following are the configuration options for the Catalog Backup tab: Table 5-16 Property Catalog Backup Policy Catalog Backup tab configuration options Description The catalog backup policy to use. and finally restore the remainder of the catalog. see the NetBackup Administrator’s Guide. then restore data from critical policies. If you want to include certain critical policies in your Vault catalog backup but not your regular NetBackup catalog backup.Configuring Vault Configuring a profile 117 You can even recover the critical policies data before you recover the entire catalog. Volume I. partial recovery of the catalog is possible. Skip the Catalog Backup Step . The drop-down list includes all catalog backup policies that have a Vault Catalog Backup schedule.

The following is the Eject tab of the Profile dialog box. Suspend option. Topics ■ ■ ■ ■ “Media ejection overview” on page 119 “ACS MAP overview” on page 119 “Eject mode (Immediate or deferred)” on page 120 “Media ejection timeout impact” on page 121 . Vault suspends media when it is ejected. you must add the appropriate catalog volume pool to the off-site volume pools eject list. ■ ■ If you create catalog backup media in a profile in which you eject media. Vault only suspends the volumes in volume pools specified in the off-site volume pools list. If you eject media from Veritas Storage Migrator (VSM). By default.118 Configuring Vault Configuring a profile Eject tab Use the Profile dialog box Eject tab to specify the: ■ ■ Volume pools from which to eject media. When to eject the media (immediately when the profile runs or later). you must add the VSM volume pool to the VSM media eject list. E-mail addresses for eject notification.

Configuring Vault Configuring a profile 119 ■ “Eject tab configuration options” on page 122 Related Topics ■ “Ejecting media” on page 140 Best Practices ■ ■ ■ ■ “Specify robotic volume group when configuring a Vault” on page 41 “Avoid vaulting partial images” on page 42 “Suspend vaulted media” on page 46 “Media ejection recommendations” on page 47 Media ejection overview During media ejection operations. For ACS robots that have multiple MAPs. For libraries that have separate MAP doors such as libraries connected via pass-through mechanisms. you must remove the media from the library slots manually. ■ Do not inventory the robot until you remove the media from the MAP or library slots. do the following: ■ ■ Configure the profiles for deferred eject. Remove the media from the library slots. . If you use a library that does not have a MAP. you will have to revault the media. Although you can use automatic eject. each time you are prompted by NetBackup. empty all the MAPs. all doors are treated as one continuous MAP by NetBackup. and then retract the MAP. Vault will continue to fill the MAP until all media are ejected. open all the doors. See “Ejecting media” on page 140. and then close all the doors. If more media will be ejected. Eject the media manually. ACS MAP overview Applies to NetBackup Enterprise Server only. You also have to perform the eject operation in Vault so that the appropriate database entries are completed. Symantec recommends that you use deferred eject so you avoid resource contention with other NBU activity and you do not neglect to remove the media from the robot (the manual eject operation serves as a reminder to remove the media). In other words. Vault moves the media to be ejected into the default media access port (MAP) of the robotic library. If you do. You must extend the MAP. remove the media. To use deferred eject for a library that does not have a MAP. you can specify the MAPs to eject media to when you configure the robot in Vault.

each with multiple media access ports (MAPs). If you defer eject. as follows: ■ Use the NetBackup Administration Console to eject media for the session. if the media are ejected to only two MAPs in one LSM. Use the vlteject command to eject media for the session. you can specify any MAP or a subset of MAPs to be used for media ejection. other actions are required to eject the media for the session. If you use one profile to choose and duplicate images daily and another profile to eject the media. and the configuration of the LSMs. Use the Vault Operator Menu to eject media for the session. as follows: . If only a subset of MAPs are used during ejection. all MAPs will still be busy). all MAPs will be busy and unavailable (for example. ■ For all other robot types that have MAPs. ■ ■ ■ ■ Eject for multiple sessions for a specific profile. you should also defer reports. The algorithm assumes that the LSMs are connected in a line. If you select deferred eject. you should specify deferred eject for the profile that selects and duplicates images and immediate eject for the profile that ejects media. the MAPs configured for ejecting in the vault. media are ejected to the default MAP. see “Adjacent LSM Specification for ACS Robots” and “Media Access Port Default for ACS Robots” in the NetBackup Administrator’s Guide. if your LSMs are connected in a configuration other than a line. When you configure a vault that uses an ACS robot. If you specify any MAP: ■ ■ MAPs that have only one element will not be used. media will not be ejected to all MAPs. media will be ejected to the nearest MAP in each LSM. Eject mode (Immediate or deferred) You can eject media immediately when the profile runs or defer ejection until later. The following are the methods you can use to eject media after the session has ended: ■ Eject for one session only. MAPs that are off-line are not considered for eject operations. Any MAP does not mean all MAPs. Vault will choose from MAPs that are on-line when the eject begins.120 Configuring Vault Configuring a profile Automated cartridge system (ACS) robots can have multiple library storage modules (LSMs). NetBackup does not support ejecting to multiple MAPs for other robot types. Create a Vault policy and enter the appropriate vlteject command and options in the file list. The algorithm considers the volumes to be ejected. Vault will eject media to as few of the configured MAPs as possible based on a nearest MAP algorithm.

and configure a Vault policy to run this profile on the days you want to select and duplicate images. Use the Vault Operator Menu. This profile should use the same image selection criteria as the profile that duplicates images. Media ejection timeout impact The media ejection timeout period is the amount of time the eject process will wait for the removal of the ejected media from the media access port (MAP) before an error condition occurs. This method for duplicating and ejecting media provides the added benefit of consolidated reports that are not organized by session. If you defer eject operations. ensure that . you should also defer reports until you eject media. Create a Vault policy and enter the appropriate vlteject command and options in the file list. Configure a Vault policy to run this profile on the day you want the media ejected. When you eject the media. Use the vlteject command. Configure a second Vault profile to do the catalog backup and eject steps. ■ ■ Eject for all sessions for a specific vault or for all sessions for all vaults (consolidated eject) by doing one of the following: ■ ■ ■ ■ Use the NetBackup Administration Console. Table 5-17 Robot Automated Cartridge System (ACS) Media ejection timeout period for Vault Timeout period One week Note Applies to NetBackup Enterprise Server only Tape Library 8MM (TL8) Tape Library DLT (TLD) Tape Library Half-inch (TLH) One week One week None Applies to NetBackup Enterprise Server only Applies to NetBackup Enterprise Server only Tape Library Multimedia (TLM) One week Robots that do not have MAPs None For robots that do not have timeout periods or do not have MAPs. select deferred eject and then eject the media manually. The following table shows the ejection timeout periods for robots. The timeout period varies depending on the capability of each robot.Configuring Vault Configuring a profile 121 ■ Configure a Vault profile to duplicate only.

The reports that are marked with an asterisk (*) on the Reports tab are generated only when all media selected by the profile have been ejected. No more images will be written to the media even if ejection is deferred. or inventory operations. eject. If you also select deferred eject. Suspend the media during the current session. Suspend at time of eject is the default. Status messages displayed by the NetBackup Administration Console or on the command line provide information about the status of inject. The reports that are marked with an asterisk (*) on the Reports tab are generated only when all media selected by the profile have been ejected. To recover. If you click Add. Select to eject media in VSM volume pools and then add the VSM media volume pools to the eject list. VSM media are never suspended. Eject Media from additional (non-NetBackup) Volume Pools Immediate (Eject Mode) Immediately (Suspend this Session’s Media) . At Time of Eject (Suspend this Session’s Media) Deferred (Eject Mode) Defer media ejection until a later time. in which you can add or remove volume pools from the eject volume pool list. Suspend the media when it is ejected. Suspend options do not affect VSM media. Eject tab configuration options The following are the configuration options for the Eject tab: Table 5-18 Property Add Eject tab configuration options Description The button used to add a volume pool to the eject list. the Vault reports will not accurately show the status of the media. you should use the Vault Operator Menu (vltopmenu) or vlteject to eject the media that was not removed from the library and generate the reports. Eject media immediately as part of the current Vault job. Caution: If media are not removed and the timeout period expires. images can be written to the media until it is ejected. VSM media must have a return date set by VSM. the Volume Pools dialog box appears.122 Configuring Vault Configuring a profile the media are removed from the library in a timely manner so that other operations can occur. Select this option if you want the media sent off-site to be full.

and globally for Vault on the Vault Management Properties dialog box General tab. see “Using notify scripts” on page 166. For more information about preventing partial images from being vaulted. To send the notification e-mail to different address. then enter the number of days before the Vault job to suspend media. . Suspend at time of eject is the default. then select either Immediately or At Time of Eject. If you use a vlt_ejectlist_notify script to eject media not created by NetBackup or Vault. For information about notify scripts. You should carefully consider whether to use this option. however. you must add the appropriate catalog volume pool to the off-site volume pools eject list. This option will suspend duplicate media created by Vault. It uses extra CPU cycles because it queries all of the databases again and applies all of the Choose Backups filters again to select media to suspend. Use this option only if you vault original images and want to prevent NetBackup from writing partial images on backup media. Suspend this Session’s Media Select to suspend media in the eject list. enter the e-mail addresses in the field below the Use E-mail Address.. Only the media in the pools that contain images that meet the selection criteria are ejected. see “Avoid vaulting partial images” on page 42. such as media to which NetBackup is writing backup images. checkbox.. the Suspend this Session’s Media option is a better choice for suspending duplicate media because it does not use CPU cycles to select media to suspend. you must add the volume pool in which that media resides to the Off-site Volume Pools list of the profile that you run to eject that media. If you create catalog backup media in a profile in which you eject media. Also. Vault sends the notification to the first e-mail addresses found in that order. Select to suspend original backup media. Eject notification is sent when the eject process begins and ends. this option will not suspend media that is in use. You can configure different addresses in each place. for each robot on the Vault Robot dialog box. Use E-mail Address from Robot or Vault Management Properties for Eject Notification Off-site Volume Pools The names of the volume pools from which to eject media.Configuring Vault Configuring a profile 123 Table 5-18 Property Eject tab configuration options (continued) Description Select to send the eject notification e-mail to the e-mail addresses configured on the Vault Robot dialog box or Vault Management Properties dialog box. Eject notification is configured for each profile on the Eject tab. Skip the Eject Step Suspend Media for the Next Session (Suspend Media on Which Backups Were Written) Select if you do not want to eject media with this profile.

Generating reports is optional. The following is the Reports tab of the Profile dialog box.124 Configuring Vault Configuring a profile Reports tab Use the Reports tab to select which reports to generate for the profile. See “Changing report properties” on page 126. and when to generate them (immediately when the profile runs or deferred until later). Topics . Reports can be generated for one session or for multiple sessions (known as consolidating your reports and ejections). Note: You must specify a destination so that reports will be generated. You and your off-site storage vendor can use the reports to determine which media should be moved between your site and the off-site storage location and the timing of the moves. where to distribute them.

Reports that depend on eject The following reports can be generated from the Profile dialog box Reports tab. If eject has not been completed. you can specify whether reports should be generated immediately when the profile runs or deferred until later.Configuring Vault Configuring a profile 125 ■ ■ ■ ■ “Report mode (Immediate or deferred)” on page 125 “Reports that depend on eject” on page 125 “Reports tab configuration options” on page 126 “Changing report properties” on page 126 Related Topics ■ ■ ■ ■ “Generating reports” on page 195 “Consolidating reports” on page 198 “Vault report types” on page 201 “Setting up E-mail” on page 217 Best Practices ■ ■ “Ensure report integrity” on page 59 “Generate the lost media report regularly” on page 60 Report mode (Immediate or deferred) Similar to the eject mode. it is known as consolidating reports. If you defer reports from multiple sessions and then generate them together. if you duplicate images daily and eject media weekly. you can defer reports for the profile that duplicates images and use the profile that ejects media to generate reports. If you defer eject. Because some reports are generated only when media are ejected. The reports for media coming on-site are not dependent on the media being ejected before they are generated. those reports will not be regenerated if you run deferred reports again. If you defer reports. you may choose to defer reports until the media are ejected. the subset of reports that do not depend on completion of eject will be generated. you must perform or schedule another action to generate the reports. ■ Reports for media coming on-site: . For example. Reports marked with an asterisk (*) on the Reports tab are generated only when all media selected by the profile are ejected. all pending reports are generated and distributed. those reports will be generated again if deferred reports are run again. you should also defer reports. If the corresponding eject process has been completed when you generate reports.

Use Report Settings from Vault Management Properties Changing report properties Use the following procedure to change report properties (title. Iron Mountain FTP File Report Header If you want certain text to appear at the top of every report. Reports marked with an asterisk (*) are generated only when all media selected by the profile are ejected. Sending the file to Iron Mountain is not part of the vault process. Immediate Reports Generate the reports immediately as part of the current vault session.126 Configuring Vault Configuring a profile ■ ■ Picking List for Vault Distribution List for Robot ■ Inventory reports: ■ ■ ■ Vault Inventory Off-site Inventory All Media Inventory) ■ Recovery Report for Vault Reports tab configuration options The following are the Reports tab configuration options. To generate a file that you can send by FTP to Iron Mountain. If you selected Iron Mountain as your vault vendor (in the New Vault dialog box). printer to use. Table 5-19 Property Deferred Reports Reports tab configuration options Description Defer generating the reports until after the session has completed (for example. The header will appear on all reports. if you run Vault sessions daily and eject media weekly). select Iron Mountain FTP file and enter the name or browse to choose the Destination folder to which the file will be written. enter it in the Report Header box. and directory to save it to). Reports marked with an asterisk (*) are generated only when all media selected by the profile are ejected. Deferred is the default. . e-mail destination. Iron Mountain FTP file and Destination folder items are displayed. Select to use the report settings configured in the Vault Management Properties Reports tab.

If you change a title. Select options and enter information as necessary. the new title will be displayed on the Reports tab and in the Report Type list box when you view Vault reports in the Administration Console. use the same title for all profiles whose reports will be consolidated. The title is printed on the reports and appears in the e-mail subject line if you e-mail the reports. The Change Report Properties dialog box appears. .Configuring Vault Configuring a profile 127 To change report properties 1 2 Double-click on a report. If you consolidate your reports and also change titles.

128 Configuring Vault Configuring a profile .

Chapter 6 Vaulting and managing media The following provide information about vaulting and managing media: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ “Running a Vault session” on page 130 “Previewing a Vault session” on page 135 “Stopping a Vault session” on page 135 “Resuming a Vault session” on page 136 “Monitoring a Vault session” on page 136 “The list of images to be vaulted” on page 138 “Ejecting media” on page 140 “Injecting media” on page 146 “Using containers” on page 150 “Assigning multiple retentions with one profile” on page 156 “Vaulting additional volumes” on page 158 “Revaulting unexpired media” on page 160 “Tracking volumes not ejected by Vault” on page 162 “Vaulting VSM media” on page 163 “Vaulting media not created by NetBackup” on page 165 “Notifying a tape operator when eject begins” on page 166 “Using notify scripts” on page 166 “Clearing the media description field” on page 168 “Deassigning vaulted NetBackup catalog media” on page 169 .

at least one robot. you can use one policy to create the backups daily and another policy to eject media weekly. duplicates those images. and ejects the media on which those images are stored. If you create multiple original backup images concurrently. Before you can run a Vault session. or vaulting job. For example. ■ ■ Best Practices ■ “Media ejection recommendations” on page 47 . You can also run a vault session by using the Vault Administration menu interface (UNIX systems only).130 Vaulting and managing media Running a Vault session ■ ■ “Restoring data from vaulted media” on page 170 “Replacing damaged media” on page 171 Running a Vault session A Vault session. and another policy can run a profile that ejects media. and one profile must be configured. use a Vault policy. if you create backup media daily and transfer it off site weekly. you may prefer to eject media on the day the vault vendor arrives. That policy can perform both operations daily or at some other interval that meets your requirements. one vault. A Vault policy is a NetBackup policy that is configured to run Vault jobs. If your vault vendor arrives daily to pick up media or you remove the off-site media from your robot immediately. is the process of executing the steps specified in a Vault profile. If your vault vendor transfers your media weekly. The policy includes the schedule for when the Vault session should run (day or date and time window) and the command to run a Vault profile. Scheduling a Vault session To run a vault session automatically at a specific day and time. A Vault policy can run a profile that selects images. a Vault policy does not back up client systems. See “Using the Vault administration interface” on page 225. and a separate Vault policy can run a Vault job that ejects the media on which those images are stored. How you schedule your sessions depends on how you conduct operations: ■ A Vault policy can run a profile that ejects media that contains original images created during a backup job. One Vault policy can run a profile that duplicates images. you may need only one policy for that vault. you can assign one or more of the original images to an off-site volume pool.

Second. Third. use the following format: vltrun robot_number/vault_name/profile_name Use the vlteject command to eject media and/or generate reports for sessions that have been completed already and for which media have not been ejected. If you do not. you specify one of two Vault commands to execute. For example: vlteject -vault vault_name -eject -report ■ Caution: Include one Vault command only in a Vault policy. The vltrun command accomplishes all the steps necessary to vault media. rather than specifying files to backup on the Backup Selections tab. and profile for the job. Volume I. you do not specify clients for Vault policies. The vlteject command can process the pending ejects and/or reports for all sessions. If the profile is configured for immediate eject. If you use more than one command. as follows: ■ Use the vltrun command to run a Vault session. Note: If you create a vault policy by copying a regular NetBackup policy that has a client list configured. For more information about creating NetBackup policies. media are ejected and reports are generated. delete all the clients in the client list before you run the policy. the first command is invoked and the successive commands are interpreted as parameters to the first command. the rest will terminate with a status 275 (a session is already running for this vault). For more information about ejecting media. see the NetBackup Administrator’s Guide. For more information about the vlteject and vltrun commands. . or for a specific profile. If the vault profile name is unique. see “Ejecting media by using a Vault policy” on page 145.Vaulting and managing media Running a Vault session 131 Creating a Vault policy Setting up a Vault policy differs from setting up a regular policy in NetBackup: ■ ■ ■ First. Failure may occur and images may not be duplicated or vaulted. The first vault job will operate as a normal vault session. vault name. see the NetBackup Commands for UNIX or NetBackup Commands for Windows manual. you must specify Vault as the policy type. for a specific robot. You specify the robot. Vault will create one vault job for every client in the list even though the client is not used by the Vault job. for a specific vault. use the following format: vltrun profile_name If the vault profile name is not unique.

Record whether the policy selects original backup media. The Add New Policy dialog box appears. On the Attributes tab. Schedule Names Off-site Original. Complete the schedule. Table 6-20 Property Policy Names Policy configuration information Description The names of all policies used for off-site rotation. expand NetBackup Management > Policies. To get information about existing policies. you can use the bppllist command. click New to create a new schedule. The type of backup defaults to Automatic Vault. The names of the schedule or schedules associated with each policy. Vault policy configuration information Collect and record the following information for each new schedule/policy pair you create or existing pair you consider for off-site rotation. Click OK. Duplicate. or both. select Vault as the policy type. On the Schedules tab. or Both Storage Unit Retention Period . creates duplicate backup media. Click OK. enter the appropriate Vault command for the policy. Enter a unique name for the new policy in the Add a New Policy dialog box. The Add a New Policy dialog box appears.132 Vaulting and managing media Running a Vault session To create a Vault policy 1 2 3 4 5 6 7 8 9 In the NetBackup Administration window. The retention period for each schedule so that you will have an idea of when to expect the media to return from off-site. Click the New Policy button. The storage units for each policy. On the Backup Selections tab. The information you record will be used when you configure Vault and can help you determine if an existing policy can be used to create backup media that Vault can select for ejection.

When the session starts. 2 3 4 5 By default.Vaulting and managing media Running a Vault session 133 Running a session manually You can run a Vault session manually either by using the NetBackup Administration Console to initiate the session or by invoking the veteran command from a command line. the Details Pane of the Administration Console window does not show the Volume Pools (Ejected) and Report Destination columns. Use the Activity Monitor to view progress. In the left pane. click on the profile you want to run. the Console displays a message similar to the following: Manual vault session for profile has been started. expand the robot that contains the vault and profile you want to run. To invoke a Vault profile 1 Expand Vault Management in the left pane of the Administration Console window. or rearrange the columns displayed in the Details Pane by selecting View > Columns > Layout. The names of the robots configured for NetBackup appear. delete. . Start Session remains highlighted until the session begins. Select the policy you want to run. Select Actions > Manual Backup. Select Actions > Start Session. select the vault that you want to run. To invoke a Vault policy 1 2 3 Expand NetBackup Management > Policies in the left pane of the Administration Console window. Running a session from the administration Console To run a Vault session from the NetBackup Administration Console. first add the path in which the NetBackup executable files are installed to your PATH environment variable. In the left pane. Running a session from a command line To run a vault session from a command line. In the details (right) pan. you either invoke the policy manually or invoke the profile manually. The policy will be run at that time and also at its scheduled time and date. You can add.

Vault also uses locks on the duplication and eject steps of a job to enforce queueing for jobs that are contending for those resources.134 Vaulting and managing media Running a Vault session Then. some restrictions exist: ■ Vaults should not share on-site and off-site volume pools. Vault uses a global setting. Vault queues jobs as follows: ■ If Maximum Vault Jobs is reached. Profiles within the same vault can use the same off-site volume groups. A Vault job runs if resources are available and the maximum number of Vault jobs has not been reached. Vaults should not share off-site volume groups. the job is queued and shown as Active in the Activity Monitor. If a job needs to eject media and another job from any vault is ejecting media in the same robot. ■ ■ Queued jobs are scheduled or run when the resources required for them become available. Maximum Vault Jobs. and profile as in the following example: vltrun robot_number/vault_name/profile_name Alternatively. For information about the vltrun command. you can specify only the profile if it has a unique name. For jobs that run simultaneously. Vault queues jobs until the resources are available. ■ Related Topics ■ “Detailed Vault job status” on page 138 . If a job needs to duplicate images and another job from the same vault is duplicating images. any subsequent vault job is queued and its status is shown as Queued in the Activity Monitor. the job is queued and shown as Active in the Activity Monitor. as a threshold for queuing jobs from any vault. specifying the robot number. but profiles from one vault cannot use the same volume pools as profiles from another vault. but profiles from one vault cannot use the same off-site volume groups as profiles from another vault. Profiles within the same vault can use the same volume pools. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. vault. invoke vltrun from a command line. If resources are not available to run jobs. Running multiple sessions simultaneously Multiple Vault sessions can run at the same time. More detailed information about the status of these Active jobs appears in the Detailed Status tab of the Job Details dialog box.

select Cancel Job. ■ Stopping a Vault session You can use Activity Monitor to stop a Vault session. performs a search on the image catalog based on the criteria specified on the profile Choose Backups tab. which is located in: ■ UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx Windows: install_path\NetBackup\Vault\sessions\vault_name\sidxxx ■ Under certain circumstances. vault. . Vault does not act on the images selected. To stop a vault session 1 2 In the Activity Monitor. Use Cancel Job to end the failed session. After you run the preview option.list file may contain more backup images than will be vaulted: ■ If the profile is configured to duplicate only disk images. highlight the vault session you want to stop. writes the names of the images to a preview. The Activity Monitor must be configured to show the Vault fields. specifying the robot number. Note: If a vault session fails. To preview a session. If images in the list do not have a copy on media in one of the Off-site Volume Pools listed for the eject step.Vaulting and managing media Previewing a Vault session 135 Previewing a Vault session Before you run a Vault session.list file. you can preview the session to verify that the profile selects the appropriate images for off-site storage. the preview.list file. they will not be vaulted. you can specify only the profile if it has a unique name. From the Action menu. and then exits. you cannot run a new session until the old session has ended. and profile as in the following example: vltrun robot_number/vault_name/profile_name -preview Alternatively. examine the preview. use the vltrun command with the -preview option. selected images on removable media will not be vaulted. The vltrun -preview option starts a new vault job.

If they do not provide enough information to determine the cause of the problem. the Policy field displays the policy name. Vault will not duplicate any images it already duplicated. you can do one of the following: ■ If the session had reached the Eject step or had attempted to generate reports before encountering problems. Volume I.) ■ Monitoring a Vault session If you configure the NetBackup Administration Console Activity Monitor to display the Vault fields. The unique numeric value that identifies the vault session. the Policy field is empty. Parent JobID . For a Vault job initiated by the NetBackup scheduler. Session ID assignment starts at 1 the first time a vault session is run after vault has been installed.136 Vaulting and managing media Resuming a Vault session Resuming a Vault session If a vault job fails. If the Vault job is invoked by any means other than the NetBackup scheduler. (This behavior is similar to checkpoint and restart. Start a new session for your profile. If you are doing duplication. A Vault job that duplicates images starts one or more bpduplicate processes. you can use vltopmenu (or vlteject) to finish the eject and/or reporting for the session. The following are the fields that display Vault job attributes in the Activity Monitor: Table 6-21 Field Vault Profile Robot Session ID Fields in the Vault Job Activity Monitor Description The name of the vault under which this session is running.log). The name of the robot the vault is associated with. but it will eject those images if the profile is configured to eject. See “Debug logs” on page 238. see the “Monitoring NetBackup Activity” section in the NetBackup Administrator’s Guide. The name of the profile that holds the processing information for a vault session. Each of these child jobs refers to the job ID of the parent Vault job that started it. you should first consult the NetBackup Administration Console Activity Monitor or the notification of session status (the session’s summary. you can use the Activity Monitor to monitor the progress of Vault jobs. After you determine the cause. The value is incremented by one every time a new vault session runs. For information about configuring the Activity Monitor to display fields other than the default. examine the other log files.

The following values progress from the first value to the last as the vault job progresses: ■ ■ ■ ■ ■ Operation Choosing Images Duplicating Images Choosing Media Catalog Backup Eject and Report The following is an example of the Activity Monitor column layout dialog box showing the Vault fields at the top of the window: . the tapes will not be ejected when the profile runs.Vaulting and managing media Monitoring a Vault session 137 Table 6-21 Field Media to Eject Fields in the Vault Job Activity Monitor (continued) Description The number of tapes to be ejected for a vault session. If the profile is configured for deferred eject.

NetBackup has adopted the convention that the exit status 252 means that an extended error code is returned via stderr. Vault builds a list of images that are candidates for duplication or ejection. These values are called extended error codes because they extend beyond the standard 255 NetBackup error codes. If a vault job exits with an extended error code. the exit status returned to the shell is 252. see “Errors returned by the Vault session” on page 234. which resides in the session directory for the current Vault session. in this case. in this message: EXIT status = extended error code The Activity Monitor displays the extended error code rather than the value 252 returned to the shell. For more information about error codes in Vault. vault vault vault vault vault vault vault vault vault vault vault vault vault vault vault vault vault global lock acquired global lock released session ID lock acquired session ID lock released duplication lock acquired duplication lock released assign slot lock acquired assign slot lock released eject lock acquired eject lock released waiting for global lock waiting for session ID lock waiting for duplication lock waiting for assign slot lock waiting for eject lock lock acquisition failed lock release failed Extended error codes Vault jobs may exit with exit-status values greater than 255. The list of images to be vaulted During a Vault session. includes all images that match the criteria specified on the profile Choose Backups tab except for the following: . The following are the possible messages written to the Detailed Status tab. The preview. The Detailed Status tab of the Job Details dialog box shows information about such jobs.138 Vaulting and managing media The list of images to be vaulted Detailed Vault job status If a job needs to duplicate images and another job from the same vault is duplicating images. the job is queued and shown as Active in the Activity Monitor.list file.

. Each of the copies has its own . If the Source Volume Groups criteria in the Locations field on the Choose Backups tab has been set to a specific volume group and if no copy of that image exists in that volume group. Vault duplicates it.. that image will not be included in the preview. Because several filters (that is.list file is generated. Vault will not re-duplicate the image the next time the profile runs. that copy is not critically important to the user.list file. Because images that have a copy in an Off-site Volume Group are already vaulted. Duplication exclusions The following can eliminate an image from duplication: ■ ■ Catalog backup images are not duplicated. Vault does not select them as candidates for vaulting. the preview. If all copies are set to Continue. This forces Vault to retry the duplication the next ■ . and none of the copies will be successful. conversely. If the image exists in the Off-site Volume Pool. Fail All Copies. Vault uses the following criteria to determine if an image has already been duplicated: ■ ■ For One Copy Only. If Disk Only is specified on the Duplication tab. For Concurrent Copies. Vault evaluates the images in it to determine if they should be duplicated and/or ejected. Vault does not duplicate it. ■ After the preview. Vault interprets the user’s intent as follows: ■ ■ Continue. other profile configuration options) can exclude an image from duplication and ejection. If the setting for the copy is Fail All Copies. an image that has no disk copy will not be duplicated. that copy is critically important to the user. If the current copy is the only one that fails. if a copy of the image is not in the Off-site Volume Pool.list file.Vaulting and managing media The list of images to be vaulted 139 ■ If a copy of an image already is in the Off-site Volume Group. The duplication job will end with a partially successful (1) status if at least one of the other copies succeeds. the image will not be added to the preview. If the setting for the copy is Continue. Vault will not duplicate the image again. If Vault determines that an image has already been duplicated.If This Copy Fails setting. at least one of those copies must exist or Vault will duplicate the image.list file may be a superset of the images that will eventually get duplicated by the session. Vault uses the For Each Image If This Copy Fails setting (Continue or Fail All Copies) to decide whether or not to duplicate an image.

it will not be ejected. If the duplication operation results in more than the Maximum Backup Copies. To determine a sufficient length of time for the image selection period.list has no copy in an off-site volume pool (configured on the Eject tab). if the time window of the profile allows that image to be selected again). Ejecting media If you configure a profile to defer ejection. ■ One Vault profile can vault original backup images from some NetBackup backup policies and also duplicate and vault images from other backup policies. Not duplicate images that were successfully duplicated by a previous job. However.) Ejection exclusions Vault ejects media listed in the eject. you must perform or schedule another action to eject media. Vault resiliency The functionality that Vault uses to build the list of images to be duplicated and ejected allows Vault to do the following: ■ Duplicate and/or eject images that were not processed because of a problem during the previous run of the profile. If the profile skips the duplication step and an image in preview. By configuring the image selection period to be a sufficient length of time.140 Vaulting and managing media Ejecting media time the profile runs if that image is selected for duplication (that is.list file. see “Overlap the time window in the profile” on page 40. and Vault will not duplicate an image that was duplicated by a previous job. the Vault profile will duplicate an image if the duplication of that image failed during the previous run of that profile. This provides for maximum flexibility or resiliency by allowing you to configure a longer image selection period without reduplicating images. You can rerun a Vault session that was only partially successful. more than one copy of the image may be assigned to the destination volume pools. the duplication step will fail. You can use one of the following actions to eject media that was not ejected by a profile that selected or duplicated images: . (Maximum Backup Copies are configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. if an unscheduled (and unlikely) event creates copies of the image.

for a single vault. or session ID. you can use the following: To use the administration Console to preview media that will be ejected 1 2 Select the vault or profile for which you want to eject media. 3 4 . select a vault. profile. Related Topics ■ ■ ■ ■ “Media ejection overview” on page 119 “ACS MAP overview” on page 119 “Eject mode (Immediate or deferred)” on page 120 “Media ejection timeout impact” on page 121 Best Practices ■ ■ ■ ■ “Specify robotic volume group when configuring a Vault” on page 41 “Avoid vaulting partial images” on page 42 “Suspend vaulted media” on page 46 “Media ejection recommendations” on page 47 Previewing media to be ejected Before you eject media. or for a profile. Click Get Preview. Select Actions > Deferred Eject. you can preview the media that will be ejected.Vaulting and managing media Ejecting media 141 ■ Manually by using the Vault Management node in the NetBackup Administration Console Manually by using the Vault Operator Menu Manually by using the vlteject command Automatically by creating and scheduling a Vault policy and entering the appropriate vlteject command and options in the file list ■ ■ ■ Note: You must use one of the Vault methods to eject media. then select one or more of the profiles in the Eject Preview window. The Deferred Eject dialog box appears. The options selected in the dialog box depend on whether you are ejecting for all vaults. To preview that media. the correct database entries will not be made and the Vault reports will not be accurate. If necessary. if you use a NetBackup or Media Manager option to eject media.

To eject media by using the NetBackup administration Console 1 2 Select the vault or profile for which you want to eject media. The preview shows the session IDs for which the deferred eject will occur and the media IDs for each session selected. From the dialog box. for a single vault. . To preview the media that will be ejected. for a single vault. specifying the robot. or for a profile. for a single vault. then select one or more of the profiles in the Eject Preview window.142 Vaulting and managing media Ejecting media To use the vlteject command to preview media that will be ejected 1 From a command prompt. Select or change any of the options on the Deferred Eject dialog box. or for a profile. click Get Preview. enter vlteject command in the following format. or session for which you want to preview ejected media: vlteject -preview [-profile profile_name] [-robot robot_name] [-vault vault_name [-sessionid id]] Ejecting media by using the NetBackup Administration Console You can use the NetBackup Administration Console to eject media and generate reports for all vaults. The Deferred Eject dialog box appears. You also can select whether to generate the reports after the ejection. The options selected in the dialog box depend on whether you are ejecting for all vaults. 3 4 To monitor the progress of or cancel the eject operation. Click Eject. or for a profile for which media have not yet been ejected. use the NetBackup Administration Console Activity Monitor. Select Actions > Deferred Eject. you can initiate the eject operation or preview the media that will be ejected. the default selections on the Deferred Eject dialog box depend on whether you are ejecting for all vaults. When you select Deferred Eject. vault.

Vaulting and managing media Ejecting media

143

The following shows the Deferred Eject dialog box with all vaults selected and previewing the media that will be ejected for the highlighted session:

Ejecting media by using the Vault operator menu
You can use the Vault Operator Menu to eject media and generate reports for Vault sessions for which media have not yet been ejected (the reports must be configured in the profiles). The Vault Operator Menu calls the vlteject command to accomplish the media ejection. You also can use the Vault Operator Menu to preview the media to be ejected. For more information about the menu, see “Using the Vault operator menu interface” on page 226. To eject media by using the Vault operator menu 1 2 Start the Vault Operator Menu by invoking the vltopmenu command. If necessary, select a profile.

144 Vaulting and managing media Ejecting media

3

Select one of the following options:
■ ■ ■

Eject Media for This Session Consolidate All Ejects Consolidate All Reports and Ejects

Ejecting media by using the vlteject command
You can use the vlteject command to eject media and generate reports for Vault sessions for which media have not yet been ejected (the reports must be configured in the profiles). The vlteject command can process the pending ejects and/or reports for all robots (that is, all sessions for all vaults), for all sessions for a single vault, or for a specific Vault session. The following is the format of the vlteject command: vlteject -eject -report -preview [-profile profile_name] [-robot robot_name] [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] [-legacy] The vlteject command resides in the following directory: UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin The following is a vlteject command example that ejects media for all robots that have sessions for which media has not yet been ejected and generates the reports:
vlteject -eject -report

The following example ejects all media that has not yet been ejected for all sessions for the CustomerDB vault and generates reports:
vlteject -vault CustomerDB -eject -report

The following is a vlteject command example that previews the media to be ejected for the CustomerDB vault:
vlteject -vault CustomerDB -preview

For more information about the vlteject command, see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. To eject media by using the vlteject command 1 2 In a terminal or command window, change to the directory in which the vlteject command resides. Invoke the command, using the appropriate options and parameters.

Vaulting and managing media Ejecting media

145

Ejecting media by using a Vault policy
You can use a Vault policy to eject media and/or generate reports for Vault sessions that have been completed already and for which media have not been ejected. In the Vault policy, specify Vault as the policy type, do not specify clients, and specify the vlteject command on the Backup Selections tab. The following is the format of the vlteject command: vlteject -eject -report -preview [-profile profile_name] [-robot robot_name] [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] [-legacy] The vlteject command resides in the following directory: UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin The following is an vltejct command example that ejects media for all robots that have sessions for which media has not yet been ejected and generates the reports:
vlteject -eject -report

The following example ejects all media that has not yet been ejected for all sessions for the CustomerDB vault and generates reports:
vlteject -vault CustomerDB -eject -report

For more information about creating NetBackup policies, see the NetBackup Administrator’s Guide, Volume I. For more information about the vlteject command, see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. To create a Vault policy that ejects media 1 2 3 4 5 6 7 8 In the NetBackup Administration window, expand NetBackup Management > Policies. Click the New Policy button. The Add a New Policy dialog box appears. Enter a unique name for the new policy in the Add a New Policy dialog box. Click OK. The Add New Policy dialog box appears. On the Attributes tab, select Vault as the policy type. On the Schedules tab, click New to create a new schedule. The type of backup defaults to Automatic Vault. Complete the schedule. Bypass the Client tab (clients are not specified for Vault jobs).

146 Vaulting and managing media Injecting media

9

On the Backup Selections tab, enter the vlteject command and the appropriate options for the policy.

10 Click OK.

Consolidating ejects
You can eject media from more than one vault session, which is known as consolidating ejects. For example, you may use one vault policy to duplicate media daily but eject media only at the end of the week. If you consolidate ejects, you should also consolidate reports. Some restrictions may apply if you consolidate reports. By default, you cannot consolidate reports between vaults that use slots and vaults that use containers. Related Topics
■ ■ ■

“Consolidating reports” on page 198 “Eject tab” on page 118 “Reports tab” on page 124

To consolidate ejects and reports for a profile 1 Select Deferred Eject on the profile Eject tab. This action ensures that tapes will not be ejected automatically for each Vault session. Select Deferred Reports on the profile Reports tab. This action ensures that reports will not be generated automatically for each Vault session. Eject media and generate reports using one of the methods described in “Ejecting media” on page 140.

2

3

Injecting media
In a normal volume rotation, you have to inject media back into a robot after media expires and is returned from your off-site storage location so that it is available for reuse. You also may need to inject unexpired media for restore or disaster recovery operations. Injecting media updates the NetBackup and Media Manager catalogs so that the correct location of the media is recorded. If the robot does not have a bar code reader to identify the media being injected, you still must use an inject option so the location of the media is updated in the databases. How you accomplish the process of injecting the media depends on the robot library:

Vaulting and managing media Injecting media

147

If your library has a media access port (MAP), you insert the media to be injected into the MAP and then use one of the injecting options discussed in this section to move that media from the MAP to the library slots. If the library has a bar code reader, the appropriate database changes are made automatically. If the library does not have a MAP, you insert the media into the library slots or into a cartridge which is then placed into the robot. If the library has a bar code reader, the appropriate database changes are made automatically. If your library does not have a bar code reader, you must use the Move media option of the NetBackup Administration Console so the databases are updated.

You can inject media as follows:
■ ■ ■

Injecting media by using the NetBackup Administration Console Injecting media by using the Vault operator menu Injecting media by using the vltinject command

On UNIX systems, you also can inject media by using the vmadm command. For information about injecting media and the inject functions available by robot, see the NetBackup Administrator’s Guide. The vault fields in the Media Manager database are cleared when the media are unassigned while in a robotic volume group or moved into a robotic volume group and then unassigned (that is, injected back into the robot. The following are the Media Manager database fields dedicated to Vault information:

Field
vltcid vltname vltreturn vltsent vltsid vltslot

Description
The ID of the container (container vaulting only). The name of the vault. The date the volume or container should be returned from the off-site vault. The date the volume or container was sent off-site. The ID of the session that vaulted the volume or container. The ID of the slot in which the volume resides in the off-site vault (slot vaulting only).

Volume pool, volume group, and media description fields are used for all volumes, not just volumes used by Vault, so they are not cleared when media are injected back into a robot. You can, however, configure NetBackup so that the media description field is cleared. See “Clearing the media description field” on page 168.

click Advanced Options. Click Actions > Inventory Robot. Select the volume to be injected into the library. volume group. Click Actions > Move. To inject media for robots without bar code readers 1 2 3 4 5 Insert the media into the robotic library slots (or into the cartridge and then inject the cartridge into the robot). To clear any previous display in the Results section. select or enter the robot. Click Start to start the update. In the NetBackup Administration Console. click Media and Device Management > Media > Robots. In the Move Volumes dialog box. . To configure advanced options. In the NetBackup Administration Console. select Empty media access port prior to update in the Inventory operation section. Use the First Slot Number field to enter the slot into which you placed the volume. see the NetBackup Administrator’s Guide. and slot number. click Clear Results. If your robot has a media access port into which you placed the media. select Update volume configuration. Click OK to move the volume. To inject media by using the administration Console 1 2 3 4 5 6 7 8 9 Insert the media into the robotic library slots or media access port. Select the robotic library where you inserted the volume.148 Vaulting and managing media Injecting media Injecting media by using the NetBackup Administration Console Use the NetBackup Administration Console to inject media for libraries that have bar code readers and libraries that do not have bar code readers. 6 7 For information about how to use the Administration Console to inject media and the inject functions available by robot. Repeat as necessary until all media are injected. click Media and Device Management > Media. In the Inventory operation section. 10 Repeat as necessary until all media are injected.

select a profile. vault. the vault for the currently selected profile in vltopmenu). and profile name. If necessary. select a session. To inject media by using the Vault operator menu 1 2 3 4 5 6 Start the Vault Operator Menu by invoking the vltopmenu command. Select Inject Media into Robot. If they are not. To inject media by using the vltinject command 1 In a terminal or command window. as follows: . For more information about using the Vault Operator menu. see “Using the Vault operator menu interface” on page 226. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. The following is the format of the vltinject command: vltinject profile|robot/vault/profile The following example command injects volumes that were vaulted by the Payroll profile and that have been returned from the off-site vault: vltinject Payroll The following example injects volumes that were vaulted by the Weekly profile in the Finance vault and that have been returned from the off-site vault: vltinject 8/Finance/Weekly For more information about the vltinject command. If necessary. Load the media in the robot’s media access port. The Vault Operator Menu calls the vltinject application program interface (API) to inject the media.Vaulting and managing media Injecting media 149 Injecting media by using the Vault operator menu You can use the Vault Operator Menu to inject media. Repeat until all media are injected into the robot. change to the directory in which the vltinject command resides. It requires as an option the name of a profile (if unique) or a robot number. Injecting media by using the vltinject command The vltinject command injects volumes into a robot and updates the Media Manager volume database. Note: Ensure that all the media in the MAP are from the current vault (that is. inject will fail.

If you have a bar code reader that can write to a file. Repeat until all media are injected. (Keyboard interface readers are also known as keyboard wedge readers because they connect (or wedge) between the keyboard and the keyboard port on your computer. reports. To vault and manage containers and media. ■ ■ ■ The default return date of a container is the date of the volume in the container that will be returned the latest. and recalls your media regardless of how the media are transferred and stored off site. Scan the container and media IDs by using a keyboard interface bar code reader. You also can delete a container from the NetBackup and Media Manager databases. you select whether the media are stored in containers or slots at your off-site storage location.150 Vaulting and managing media Using containers UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin 2 3 4 Load the media to be injected into the robot’s media access port. you can add media to more than one container. Read an input file that contains the IDs or numeric equivalents of bar codes of all the media that will be added to one container. using the appropriate options and parameters. When you configure a vault. After the media are ejected from your robot. Add all the media ejected by a specific session to one container. you can scan media bar codes and use that output file as input for the vltcontainers command. Using this method. Invoke the command. Vault tracks. you must add the media logically to containers by using either the Vault Operator Menu or the vltcontainers command. If you use containers. see the following: . The options available for adding media to containers are as follows: ■ Enter the container and media IDs by typing them in with the keyboard. you can add media to more than one container. it is deleted from the NetBackup and Media Manager databases. Vault reports on the containers and media outside the context of a profile or session. If a container becomes empty after it is recalled and all media that reside in it are either injected back into the robot or assigned to another container. You can change the return date during the container and media ID entry process or at any time thereafter before a container is recalled. Using containers A container is a box in which you can place media and then transfer that box to your off-site storage location.) Using this method.

Select Container Management. you can use the vltcontainers command to enter the container and media IDs. For more information about the menu. you can use the Vault Operator Menu to enter the container and media IDs. Vaulting container media by using the vltcontainers command After the media are ejected from your robot. Move all media listed in a file. see “Using the Vault operator menu interface” on page 226.Vaulting and managing media Using containers 151 ■ ■ ■ Vaulting media in containers Managing containers and media Reporting on containers and media Vaulting media in containers You can use either the Vault Operator Menu or the vltcontainers command to add media IDs to containers. into one container if you want to add all media ejected by a session to a container. Eject the media that will be added to the containers. The following is the format of the vltcontainers command: vltcontainers -run [-rn robot_number] vltcontainers -run -usingbarcodes [-rn robot_number] vltcontainers -run -vltcid container_id -vault vault_name -sessionid session_id . ■ ■ 5 Follow the prompts to complete the process of logically moving media into containers. Move all media ejected by this session. To vault media in containers by using the Vault operator menu 1 2 3 4 Start the Vault Operator Menu by invoking the vltopmenu command. Select one of the following options: ■ Move media into one or more containers if you intend to use the keyboard to enter media and container IDs or use a bar code scanner to scan the bar codes on the volumes and containers. Vaulting container media by using the Vault operator menu After the media are ejected from your robot. into one container if you want to add all media listed in an input file to a container.

.152 Vaulting and managing media Using containers vltcontainers robot_number] vltcontainers vltcontainers vltcontainers vltcontainers -run -vltcid container_id -f file_name [-rn [-usingbarcodes] -view [-vltcid container_id] -change -vltcid container_id -rd return_date -delete -vltcid container_id -version The following examples show how to use the vltcontainers command to add media to a container: ■ To add the volumes ejected from robot number 0 to containers and enter the IDs by typing them in. use the following command: vltcontainers -change -vltcid ABC123 -rd 12/07/2004 ■ To delete container ABC123 from the NetBackup and Media Manager catalogs. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. use the following command: vltcontainers -run -vltcid ABC123 -vault MyVault_Cntrs -sessionid 4 ■ To add media listed in file C:\home\jack\medialist that are ejected from robot number 0 to container ABC123. use the following command: vltcontainers -run -usingbarcodes -rn 0 ■ To change the return date of container ABC123 to December 07. use the following command: vltcontainers -run -vltcid ABC123 -f C:\home\jack\medialist -usingbarcodes For more information about the vltcontainers command. 2004. To vault media in containers by using the vltcontainers command 1 Eject the media that will be added to the containers. use the following command: vltcontainers -run -rn 0 ■ To add the volumes ejected from robot number 0 to containers and use a bar code reader to scan the container and media IDs. use the following command: vltcontainers -delete -vltcid ABC123 ■ To add all media ejected by session 4 of vault MyVault_Cntrs to container ABC123. use the following command: vltcontainers -run -vltcid ABC123 -f C:\home\jack\medialist -rn 0 ■ To add media to container ABC123 that was ejected from a robot that is attached to the master server and read the bar codes for that media from file C:\home\jack\medialist.

if you do. You can view and change return dates of containers. . Note: Iron Mountain users: To change a container return date. Using the Vault operator menu to manage container media You can use the Vault Operator Menu to change a container return date and to delete the information about a container from the NetBackup databases. change the date using the Vault Operator Menu or the vltcontainers command then resend the Container Inventory Report or the Iron Mountain FTP file to Iron Mountain. Follow the prompts to enter a container name. Select Container Management > Delete a container. To delete a container by using the Vault operator menu 1 2 Start the Vault Operator Menu by invoking the vltopmenu command. Select Container Management > View a container’s return date. Do not use the Iron Mountain account management facilities to change a container return date. Managing containers and media After the media and containers are sent to your off-site storage location. see “Using the Vault operator menu interface” on page 226. Follow the prompts to move the media logically into containers. Follow the prompts to enter container names and change dates.Vaulting and managing media Using containers 153 2 3 Invoke the vltcontainers command. To change a container return date by using the Vault operator menu 1 2 3 Start the Vault Operator Menu by invoking the vltopmenu command. For more information about the menu. using the appropriate options and parameters. you can still perform tasks to manage the containers and media. the Vault reports will not match the report information maintained by Iron Mountain. If a container has been recalled and is empty of media. you can delete the information about a container from the NetBackup and Media Manager databases. To view a container return date by using the Vault operator menu 1 2 3 Start the Vault Operator Menu by invoking the vltopmenu command. Select Container Management > Change a container’s return date.

For more information about the vltcontainers command. Do not use the Iron Mountain account management facilities to change a container return date. 2004.154 Vaulting and managing media Using containers 3 Follow the prompts to enter a container name and delete the records of a container. For example. to view the return date of container ABC123. it is deleted from the NetBackup and Media Manager databases. To view a container return date by using the vltcontainers command ◆ Invoke the vltcontainers command using the -view option. For example. Note: If a container becomes empty after it is recalled and all media that reside in it are either injected back into the robot or assigned to another container. Note: Iron Mountain users: To change a container return date. using the -delete option and specifying the -vltcid parameter and argument. to change the return date of container ABC123 to December 07. to delete . Using the vltcontainers command to manage container media You can use the vltcontainers command to view and change a container return date and to delete the information about a container from the NetBackup and Media Manager databases. For example. use the following command: vltcontainers -change -vltcid ABC123 -rd 12/07/2004 To delete a container by using the vltcontainers command ◆ Invoke the vltcontainers command. the Vault reports will not match the report information maintained by Iron Mountain. use the following command: vltcontainers -view -vltcid ABC123 To change a container return date by using the vltcontainers command ◆ Invoke the vltcontainers command using the -change option and specifying the -vltcid parameter and argument and -rd parameter and argument. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. change the date using the Vault Operator Menu or the vltcontainers command then resend the Container Inventory Report or the Iron Mountain FTP file to Iron Mountain. if you do.

you can specify a container ID to generate a report of the media in a specific container. a container must be empty. Alternatively. . If you are using containers. You also can generate the Container Inventory Report by using the Vault Operator Menu (Run Individual Reports > Container Inventory). all of the other Vault reports will list the ID of the container in which the volume resides rather than a slot number. Reports will not show container information until after you add container and media IDs in Vault.Vaulting and managing media Using containers 155 container ABC123 from the NetBackup and Media Manager catalogs. the return date of each container. use the following command: vltcontainers -delete -vltcid ABC123 To be deleted. Reporting on containers and media The Container Inventory Report shows all the containers configured in your vaulting environment. see “Using the Vault operator menu interface” on page 226. and the media that are in each container. Media are removed logically from a container when they are injected back into the robot. For more information.

The details pane of the Administration Console will display the report details. Assigning multiple retentions with one profile Different types of data often are retained for different lengths of time. In the Container ID field. Click Run Report. you may want to vault your finance data for 7 years and your customer . For example. select Reports > Vault Reports > Container Inventory.156 Vaulting and managing media Assigning multiple retentions with one profile The following is an example of the Container Inventory Report window: To generate a container inventory report 1 2 3 In the NetBackup Administration Console. select All Containers or the ID of the container for which you want a report.

specifying Use Mappings instructs the profile to use the alternative retention mappings. Vault can process different types of data individually if your backups are organized based on the type of data being protected (for example. To do this. retention level 12 to be 7 years. assign retention level 1 (2 weeks) to the first (or only) copy configured in the schedule. Vault usually assigns the same retention to all of the duplicates created using one of the following duplication options: ■ ■ Specifying No Change keeps the same expiration date as the original copy. and the off-site copy of your CustomerDB data for 20 years. The retention mapping converts the original backup image’s retention to a new retention for the duplicated copy. During duplication. You can do this as follows: 1 Using Host Properties in the NetBackup Administration Console. Configure the retention mappings as follows: 0 1 2 3 4 0 12 2 3 4 2 3 4 5 . calculated from the backup time of the original image. Alternatively. suppose you want to retain the on-site copy of all your data for 2 weeks. In your Finance backup policy. assign retention level 11 (2 weeks) to the first (or only) copy configured in the schedule. In your Vault profile. When a Vault session creates a duplicate image.Vaulting and managing media Assigning multiple retentions with one profile 157 data for 20 years. Specifying a numeric retention level applies that retention. you can configure Vault to calculate a retention for the duplicate copy based on the type of data. the off-site copy of your backups will have different retentions based on the type of data. such as a Finance backup policy and a CustomerDB backup policy). configure retention levels 1 and 11 to be 2 weeks. on the Duplication tab configure Retention Level to be Use Mappings. The retention for a duplicate copy of a particular type of data is based on the retention level assigned by the backup policy for that type of data. For example. In your CustomerDB policy. if you have separate backup policies based on the data type. the off-site copy of your Finance data for 7 years. and retention level 13 to be 20 years.

After the Vault profile is run.158 Vaulting and managing media Vaulting additional volumes 5 6 7 8 9 10 11 12 5 6 7 8 9 10 13 12 With this mapping. and the Vault profile ejects the media for transfer off site. you create the necessary copies of backup media during a NetBackup policy job or a Vault profile duplication job. you can specify normal retention calculation for some duplication rules and alternative retention mappings for other duplication rules. Volume I. Related Topics ■ Vault Management Properties dialog box “Retention mappings tab” on page 79 Vault dialog box “Retention mappings tab” on page 87 ■ Vaulting additional volumes Usually. . you cannot run the profile again to create additional copies of media that was already sent off site. The duplicated images will be written to different media if the Allow Multiple Retentions Per Media property is not set (NetBackup Management > Host Properties > Master Server > Media). duplicated images from the Finance policy/schedule are assigned a retention level of 12 (7 years) and duplicated images from the CustomerDB policy/schedule are assigned a retention level of 13 (20 years). see the NetBackup Administrator’s Guide. You can configure retention mappings globally for all vaults by using the Vault Management Properties dialog box Retention Mappings tab or for each vault by using the Vault dialog box Retention Mappings tab. The values for the retention levels are configured in NetBackup Management > Host Properties > Master Server > Retention Periods. For information about configuring different values for the retention levels. When you configure a profile.

To duplicate a volume manually 1 Duplicate the volume manually by using the bpduplicate command. If you want to duplicate and eject one or several additional volumes one time only. Assign the vault vendor’s slot number for the volume by using the vltoffsitemedia command. then print the report and give it to the vault vendor. Duplicating a volume manually If you use the following instructions to duplicate a volume manually. Edit the file of the Picking List for Robot report to insert this volume into the list. the tape will appear on the Picking List for Vault report when it expires and be recalled from the off-site vault as part of your normal operations. the volume will never appear on the Picking List for Vault report. the easiest solution is to duplicate the volume manually. the primary copy of the volume must be in the robot. specify the same off-site volume pool used for the volume already vaulted. The slot number is assigned in the vltslot field. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. If you assign a value. you can use other methods to create and eject additional copies of backup media after the NetBackup policy and Vault profile have been run. To duplicate an additional volume. You can assign values to other vault fields if desired. this volume will appear on the Picking List for Vault report when the first vaulted copy expires (if you did not assign a value to the vltreturn field). Eject the volume. 2 Caution: Do not assign a value to the vltreturn field. 4 5 For information about the bpduplicate and vltoffsitemedia commands. Use the same off-site volume group as the first vaulted copy. . When duplicating the volume. If the primary copy is not in the robot but a duplicate copy is. You can duplicate the volume manually or you can configure Vault to duplicate the volume. For information about the bpchangeprimary command. you can use the bpchangeprimary command to change the duplicate to primary before you create an additional volume. If the volume is in the same off-site volume group and the same off-site volume pool used by the regularly scheduled Vault profile.Vaulting and managing media Vaulting additional volumes 159 However. 3 Move the volume into the off-site volume group by using the vmchange command.

Use a different off-site volume group than the first volume. To revault media by creating a new profile 1 2 Copy the original Vault profile that was used to eject the media. and different off-site volume pool than the first volume. Vault will recognize that copies of images eligible to be vaulted exist and will not duplicate the images even if the duplication step is configured. the volume will appear on the report after it expires. you should revault the media. Start a session using this new vault profile. you should create a new profile to revault them. The container ID field is cleared when media vaulted in containers is injected back into the robot. Create and configure a new profile to duplicate and eject the volume. The profile will eject the volumes to be revaulted. run the Lost Media Report. The additional volume will not appear in the Picking List for Vault. so you must add the media to containers. Assign the volume to a different off-site volume pool than the first volume. so you must use the Lost Media Report to recall the volume after it expires. If you have to revault many tapes. to perform a restore). logically add the volumes to containers. change the Choose Backups time window to shift it far enough back in time so that it will select the images on the volumes that you want to revault. 3 4 . Revaulting unexpired media When you inject unexpired media from off-site storage back into a robot (for example. Configure the eject step of the profile to search the off-site volume pool in which the additional volume was assigned. To recall the volume after it expires.160 Vaulting and managing media Revaulting unexpired media Duplicating a volume by using Vault If you use Vault to create and eject an additional copy of a volume that is already in the off-site vault. To duplicate a volume by using Vault 1 2 3 4 5 Create and configure a new vault. If you are vaulting containers. different off-site volume group. If only a few tapes are to be revaulted. In this new profile. revaulting them manually may be the easiest and fastest option. If you run the Lost Media Report as part of your normal operations. Run the profile. you must use a different vault.

Vault assumes that the media will be returned to the same slots in off-site storage from which they were recalled. highlight the media ID then select the Change Volume Group.. If you froze the media. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. so you must add the media to containers. If you froze your media during the data restore process.. Vault assumes that the media will be returned to the same slots in off-site storage from which they were recalled. using one of the following methods: ■ ■ Use the vmchange command. 5 6 Delete the new profile you created to do the revaulting. highlight the media ID then select the Eject Volumes from Robot. use the bpmedia command to unfreeze it. The container ID field is cleared when media vaulted in containers is injected back into the robot.. If you are vaulting media in slots. See “Using containers” on page 150. using one of the following methods: ■ ■ Use the vmchange command. In the NetBackup Administration Console. . operation on the Actions menu. In the NetBackup Administration Console. 2 Manually transfer the media to the off-site volume group. To revault media manually 1 Manually eject the media. Note: vlteject and vltopmenu will not work for this purpose. logically add the volumes to containers. If you are vaulting media in slots. Run the Recovery Report to ensure that media are available in off-site storage for future use.Vaulting and managing media Revaulting unexpired media 161 See “Using containers” on page 150.. you have to unfreeze the it so it will be recalled and returned to volume pool rotation when it expires. operation on the Actions menu.. 7 8 For information about the bpmedia command. 3 If you are vaulting containers.. Vaulted media that are suspended will be unsuspended automatically when they expire and are recalled. Return the media to your vault vendor so that all backups on that media will be available for future disaster recovery.

Return the media to your vault vendor so that all backups on that media will be available for future disaster recovery. use the vltoffsitemedia command to change the Vault specific attributes. In normal operation. Note: This process will work only if the volumes already are in a volume pool on the Eject tab of a profile. use the vmchange command to change the volume group of the volumes. First. . If you froze the media.162 Vaulting and managing media Tracking volumes not ejected by Vault 4 If you froze your media during the data restore process. Vaulted media that are suspended will be unsuspended automatically when they expire and are recalled. Vault must eject volumes so they are tracked and recalled from off-site storage after they expire. use the bpmedia command to unfreeze it. Using commands. 5 6 For information about the vmchange command. You cannot change the pool of an assigned volume. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. you can change the attributes for volumes that were not ejected by Vault so they will appear in the Vault reports and be recalled when they expire. For example. If you ejected volumes or removed them from your robot without using a Vault eject method. The following vltoffsitemedia example changes the vault attributes of volume A00001: vltoffsitemedia -change -m A00001 -vltname offsite_vault -vltsent 07/03/2004 -vltreturn 0 -vltslot 99 -vltsession 33 A catalog volume is processed the same except the return date is set to the date the volume should be recalled. Run the Recovery report to ensure that the media are available for future disaster recovery operations. it is still possible to use Vault to track them — if they are in a volume pool you are using for off-site media. the following vmchange command changes the volume group of volume A00001: vmchange -new_v offsite_volgrp -m A00001 Then. you have to unfreeze the it so it will be recalled and returned to volume pool rotation when it expires. which Vault uses to track their location. Tracking volumes not ejected by Vault Eject is the event that Vault uses to update the NetBackup database for the location of volumes and to recall volumes.

do not specify this option. and the media appears on the Picking List for Robot when they are ejected and on the Picking List for Vault that covers their return dates. the date syntax is mm/ dd/ yyyy [hh[:mm[: ss]]]. you may have to change the container return date if the volume you are adding expires later than any volume already in the container. Set the return date to 0. Vault assigns vendor slot or container IDs to the media.Vaulting and managing media Vaulting VSM media 163 If you are adding the volumes to slots at your off-site storage location. For the C locale. Set it to a nonzero number that is different from existing session IDs The ID of the slot in which the volume resides in the off-site vault. If you are placing the volumes in containers. use the vltcontainers command to add the volumes logically to containers after you specify the off-site volume group and the vault attributes See “Using containers” on page 150. If you are placing the volume in a container. The default return date of a container is the date of the volume in the container that will be returned the latest. The following are the vltoffsitemedia options you can use to set the necessary volume attributes: Table 6-22 Option -vltname vault_name -vltreturn date Options to vltoffsitemedia Description The name of the vault. -vltsent date -vltsession session_id -vltslot slot_id Vaulting VSM media Vault can eject and track Veritas Storage Migrator (VSM) media if it is in a VSM volume pool configured on the profile Eject tab and it has a return date from vault set by VSM. You can vault VSM media by using a profile specifically for VSM media or by using a profile that also ejects NetBackup media. The ID of the session that vaulted the volume or container. Vault uses the latest expiration date of the images on the volume as the return date. If you use a profile that you . Ensure that this is an empty slot at your off-site storage location. Exception: if the volume is a NetBackup catalog backup volume. set the date the volume should be recalled from offsite. The format of the date depends on your locale setting. Set the sent date to the date the volume was ejected. you can use the vltoffsitemedia command with the -list option to find empty slots into which you can add the volumes.

accept the defaults on the Choose Backups tab and skip the duplication and catalog backup steps. select (at a minimum) the following reports on the Reports tab: . Prerequisites to vaulting VSM media in Vault: ■ ■ Configure vaulting properties in VSM. Related Topics ■ “Eject tab” on page 118 To vault VSM media 1 Configure a Vault profile so it includes the dedicated VSM volume pool(s) from which you want to eject media: a b For a VSM-specific profile. you do not have to run a VSM-specific profile. and the VSM media will be ejected. vaulted. On the Eject tab. select Eject Media from VSM Volume Pools and then add the VSM volume pool(s) to the eject list. The VSM media must be in a volume pool dedicated to VSM. Vault suspend options do not affect VSM media. The VSM media must have a return date from Vault set by VSM. and recalled as part of your normal Vault operations.164 Vaulting and managing media Vaulting VSM media already use for ejecting media and generating reports. VSM media are never suspended. c For a VSM-specific profile.

The script will execute the vltoffsitemedia command(s) and assign the expiration date(s). . See “Using notify scripts” on page 166. Configure a Vault profile so that it includes the volume pool in which the media are assigned in the Off-site Volume Pools list on the Eject tab of the Profile dialog box. add the appropriate extension to the name). The following procedure documents how to copy and modify the vlt_ejectlist_notify script. The media will appear on the Picking List for Vault on the date it expires. Notify script templates are provided with Vault.The scripts include information about how to modify and test them. Vault uses a eject notify script to add valid media IDs to the eject list. the media will be ejected. and those media appear on the Picking List for Robot and Picking List for Vault reports. 3 4 Place the script in the NetBackup bin directory. Vault ejects notify script media even if no other media are selected for ejection by the Vault profile. To vault non NetBackup media managed by media Manager 1 2 Copy the vlt_ejectlist_notify script and name it appropriately (that is. Add a vltoffsitemedia command and use the vltreturn option to set a date to recall the media from the vault. Vaulting media not created by NetBackup Vault can eject and track media that was not created by NetBackup if the media are managed by Media Manager. You can schedule both the VSM vaulting session and the Vault session so they run at a regular interval. When the profile runs and if the script executes successfully. and Vault ejects that media if you add the volume pool in which that media resides to the Off-site Volume Pools list on the Eject tab of the Profile dialog box. Vault assigns vendor slot or container IDs to the media.Vaulting and managing media Vaulting media not created by NetBackup 165 ■ ■ Picking List for Robot Picking List for Vault 2 Run the profile so that VSM media are ejected and reports are generated. Edit the script as follows: a b Add the media IDs of the non NetBackup media that you want to eject.

A script must return a normal status (0) for the Vault job to continue processing. On Windows systems. In case of failure. The following scripts have been provided with Vault: vlt_start_notify Called by the Vault session after it starts. the names of the scripts include a . see the following: ■ ■ ■ “Configuring Vault management properties” on page 74 “Vault robot dialog box” on page 82 “Eject tab” on page 118 Related Topics ■ “Setting up E-mail” on page 217 Using notify scripts A Vault job can call notify scripts at specific points during the execution of the job. for each robot on the Vault Robot dialog box.166 Vaulting and managing media Notifying a tape operator when eject begins For information about the vltoffsitemedia command.cmd extension. you can use it to send notification when the Vault job begins. which is set by Vault. Vault sends the notification to the first e-mail addresses found in that order. The template notify scripts are in the following directory: UNIX: /usr/openv/netbackup/bin/goodies Windows: install_path\NetBackup\bin\goodies On Windows systems. a script must be copied to the NetBackup bin directory. You can use a script for a robot. Notifying a tape operator when eject begins Vault can send an e-mail notification when the eject process begins. Eject notification is configured for each profile on the Eject tab. On UNIX systems. For example. They include instructions that can help you edit them for your needs. a vault. the scripts communicate the return status in a file defined by the EXIT_STATUS environment variable. Vault includes template notify scripts that you can customize for your use. the return status is communicated to the Vault job through the exit call. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. To be called and executed. . To configure eject e-mail notification. the script must return a nonzero status code to cause the Vault job to stop. and globally for Vault on the Vault Management Properties dialog box. or a profile.

Vaulting and managing media Using notify scripts 167 vlt_ejectlist_notify Called by the Vault session before the list of media to be ejected (the eject.robot_number The script will be executed for all profiles created for the robot. Called at the end of eject processing. . You can use this script to send notification when the eject process ends. Notify script for a specific robot You can use a notify script to create a unique. For example.list) is built. You can use this script to send notification when the eject process begins or perhaps to suspend the media in the eject list. If the eject step is not configured for the profile. a vlt_start_notify script for a specific robot will appear as follows: vlt_start_notify. One use for this script is to start another vault job. Vault reads the addon_medialist file and ejects the media listed in that file during the current Vault session if the volume pool in which that media resides is in the Off-site Volume Pools list on the Eject tab of the Profile dialog box. See “Setting up E-mail” on page 217. If the eject step is not configured for the profile. the vlt_endeject_notify script is not called. append the robot number to the script name and copy the script to the NetBackup bin directory. You can use this script to add media managed by Media Manager but not created by NetBackup or Vault to the eject list. Called by the Vault session after the eject. Use the same methodology to create other notify scripts. ensure that your systems are set up properly for e-mail. customized script for each robot in your configuration. vlt_starteject_notify vlt_endeject_notify vlt_end_notify Before you use a notify script. Called by the Vault session immediately before it exits. the vlt_starteject_notify script is not called. The script writes media IDs to the addon_medialist file. To create a notify script for a specific robot. you can then run Vault jobs in succession and avoid resource contention.list file is built and before the automatic eject process begins.

robot_number. For example.robot_number. append the robot number and vault name to the script name and copy the script to the NetBackup bin directory. as follows: 1 2 3 4 script_name.robot_number.vault_name. use the nbemmcmd to set the . To create a notify script for a specific vault. they are expired and ready for reuse. To do so. customized script for each vault in your configuration. Use the same methodology to create other notify scripts. To create a notify script for a specific profile. You can configure NetBackup so that the media description field is cleared when media are returned to the robot. a vlt_start_notify script for a specific robot/vault/profile combination will appear as follows: vlt_start_notify. and profile name to the script name and copy the script to the NetBackup bin directory. append the robot number.vault_name.vault_name script_name.vault_name The script will be executed for all profiles created for a specific vault. customized script for each profile in your configuration. it may be helpful to clear the media description information when an expired volume is returned to the robot.robot_number. To avoid confusion. a vlt_start_notify script for a specific robot/vault combination will appear as follows: vlt_start_notify. Notify script for a specific profile You can use a notify script to create a unique. Use the same methodology to create other notify scripts.profile_name script_name. For example.profile_name This script will be executed for a specific profile defined for a specific vault.168 Vaulting and managing media Clearing the media description field Notify script for a specific Vault You can use a notify script to create a unique. vault name.robot_number script_name Clearing the media description field When media are returned from the off-site vault during a typical volume rotation. Order of execution The notify scripts are executed in specific to general order.

NetBackup catalog media are returned for use as catalog backup media after the retention period for the media has passed.Vaulting and managing media Deassigning vaulted NetBackup catalog media 169 VAULT_CLEAR_MEDIA_DESC parameter. The bplabel command is in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\NetBackup\bin\admincmd The vmquery command is in the following directory: UNIX: /usr/openv/netbackup/volmgr/bin Windows: install_path\NetBackup\Volmgr\bin To deassign a catalog volume 1 Obtain the pool number for the volume by using the vmquery command. If you want to reuse vaulted catalog backup media before it expires or if catalog backup media was not recalled properly from off-site storage.Not Robotic (0) . If you want to use the tape as a general NetBackup backup tape. Usually. For information about the nbemmcmd command. you must also relabel the tape by using bplabel.0. see the NetBackup Administrator’s Guide. For information about bplabel and vmquery. Deassigning vaulted NetBackup catalog media Applies only to Vault catalog backup media from releases earlier than NetBackup 6. you can use it again for a catalog backup. For information about setting media manager parameters. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. as shown in the following example for volume S04440: vmquery -m S04440 =============================================================== === media ID:S04440 media type:8MM cartridge tape (4) barcode:------------description:CH_V1|101|S278|00000000 volume pool:Offsite_Catalog (3) robot type:NONE . you must deassign that media manually by using the vmquery command. see the NetBackup Commands manual and “Using NetBackup Commands” in the NetBackup Administration Console help. After you deassign the media. The media description field will be cleared when other Vault information is cleared from the Media Manager volume database.

Inject the media into the robot. 2 Deassign the volume by using the vmquery command. 3 4 . Use the bpchangeprimary command to promote a copy to primary. For information about the bpmedia command. For information about the bpchangeprimary command. see “Injecting media” on page 146. The high-level procedure in this section describes how to restore data from vaulted media. and is the number in between the parentheses. Use the bpmedia command to suspend the media. the media ID would be S04440 and the pool number would be 3. Injecting the media moves it into the robot and also changes the off-site volume group attribute of the media to the robotic volume group so NetBackup knows that the media are in the robot. as in the example below: vmquery -deassignbyid S04440 3 1 Restoring data from vaulted media You may need to restore images from media that is stored in your off-site vault. In this case. see the NetBackup Commands for UNIX or NetBackup Commands for Windows guide. For procedures. If the media is not suspended or frozen. Change the images to be recovered to primary (NetBackup restores from the primary image). see the NetBackup Commands for UNIX or NetBackup Commands for Windows guide. suspend the media. To restore data from vaulted media 1 2 Recall the media.170 Vaulting and managing media Restoring data from vaulted media volume group:vault_grp created:Tue Sep 3 10:08:32 2000 assigned:Tue May 6 00:11:45 2001 last mounted:Tue May 6 11:34:25 2001 first mount:Tue Sep 3 18:20:48 2000 expiration date:--number of mounts:21 max mounts allowed:--status:0x1 =============================================================== === The pool number is listed on the volume pool line.

the errors are logged to the restore log and also show up on the Activity Monitor as the restore fails. see “Revaulting unexpired media” on page 160. To replace damaged media 1 Identify the damaged media. revault the media. see the NetBackup Backup. Most of the commands used to recover from damaged media are in the following directory: UNIX: /usr/openv/netbackup/bin/admincmd Windows: install_path\netbackup\bin\admincmd After you recover and restore the damaged media. All images on a specific tape can be identified by running the bpimmedia command. Archive. you can use copies of the media (if available) from your off-site storage location to replace the damaged media. When you receive an error message during a restore. see “Revaulting unexpired media” on page 160. Note: This image recovery process assumes that the NetBackup system and image catalog are current and up-to-date. 6 Replacing damaged media If media in your robot is damaged. You can set up a procedure using NetBackup scripts to send errors to an event management console to notify the storage administrator immediately of this type of media error. For example. The instructions use an example to illustrate how to invoke the various commands used in the recovery process. you should revault the media so that it again is available for recovery. For procedures. It scans the entire NetBackup image catalog. the following shows that volume S05423 contains one image from client fgolddust. Modify the command examples as appropriate for your purposes. restore the data. You also can use this process to recover images if the primary backup has expired. the volume has been overwritten and a copy in off-site storage is still available. Determine which backup images were on the damaged tape. and Restore Getting Started Guide. For procedures. The full image name is “fgolddust_0862806643”: 2 . Archive. It also shows that this image has been duplicated because it has (FRAG 2) entries. After restoring all the data.Vaulting and managing media Replacing damaged media 171 5 Using the Backup. For procedures. and Restore interface. so it may take a few minutes depending on the size of that catalog.

as follows: # bpimagelist -backupid fgolddust_0862806643 IMAGE fgolddust 0 0 2 fgolddust_0862806643 golddust_BR1 0 *NULL* root Full_Weekly 0 3 862806643 4591 865485043 0 0 2356562 19360 2 7 1 golddust_BR1_0862806643_FULL. in this case nirvana. the host could be different than the master server. so the host server names would be the same for both copies of the image. The (FRAG 2 -1) entry is the true image restore duplicate. You can confirm this information by using bpimagelist command. In this case. On copy 1 there were 4 fragments (usually due to multiplexing). the image fgolddust_0862806643 is using media S04440 for duplicating all of the original fragments. Also note that the host for the media is printed for each fragment. the (FRAG 2) entries show that an image has been duplicated: the (FRAG 2 1) entry is the duplicate copy. With media servers. while the duplicate was de-multiplexed during image duplication. the duplication should normally occur on the same server that made the original backup. and could fit on one tape. Under Vault.172 Vaulting and managing media Replacing damaged media # bpimmedia -mediaid S05423 IMAGE fgolddust 2 fgolddust_0862806643 golddust_BR1 0 Full_Weekly 0 3 19360 8654 85043 0 0 FRAG 1 -1 2293 0 2 6 2 S05423 nirvana 64512 0 862804830 3 0 *NULL* FRAG 1 1 232848 0 2 6 1 S02643 nirvana 64512 2 862804830 3 0 *NULL* FRAG 1 2 1225539 0 2 6 2 S02643 nirvana 64512 0 862804830 3 0 *NULL* FRAG 1 3 70182 0 2 6 3 S02643 nirvana 64512 0 862804830 3 0 *NULL* FRAG 1 4 825700 0 2 6 1 S05423 nirvana 64512 2 862808446 3 0 *NULL* FRAG 2 -1 2293 0 2 6 2 S04440 nirvana 32768 0 862927577 2 0 *NULL* FRAG 2 1 2335584 0 2 6 1 S04440 nirvana 32768 2 862927577 2 0 *NULL* 3 Determine which duplicate tapes were used and their host. In step 2.f *NULL* *NULL* 0 1 0 2 865830643 *NULL* 1 0 0 0 0 *NULL* HISTO -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 FRAG 1 -1 2293 0 2 6 2 S05423 nirvana 64512 0 862804830 3 0 *NULL* FRAG 1 1 232848 0 2 6 1 S02643 nirvana 64512 2 862804830 3 0 *NULL* FRAG 1 2 1225539 0 2 6 2 S02643 nirvana 64512 0 862804830 3 0 *NULL* . This is normal because the original image was multiplexed onto 4 tapes.

The new primary copy is used for restoring an image: # bpchangeprimary -copy 2 -id fgolddust_0862806643 -cl fgolddust To confirm the new primary copy. Use the command bpmedia -freeze to prevent NetBackup from expiring the images on the media and to ensure the media is assigned in Media Manager.Vaulting and managing media Replacing damaged media 173 FRAG 1 *NULL* FRAG 1 *NULL* FRAG 2 *NULL* FRAG 2 *NULL* 3 70182 0 2 6 3 S02643 nirvana 64512 0 862804830 3 0 4 825700 0 2 6 1 S05423 nirvana 64512 2 862808446 3 0 -1 2293 0 2 6 2 S04440 nirvana 32768 0 862927577 2 0 1 2335584 0 2 6 1 S04440 nirvana 32768 2 862927577 2 0 To confirm which is the primary copy (the copy to be used for restores). use the -L option with bpimagelist. You should also use the media host for this image. bpmedia -freeze -m S04440 -host nirvana 6 Recall media from the vault. use the following command: UNIX: # bpimagelist -L -backupid fgolddust_0862806643 | grep Primary Primary Copy: 2 Windows: bpimagelist -L -backupid fgolddust_0862806643 | find "Primary" Primary Copy: 2 5 Freeze the duplicated copy to ensure restore. located in the following directory: UNIX: /usr/openv/volmgr/bin Windows:install_path\volmgr\bin. Execute the bpimage -npc command and option to change the primary copy. To determine the media ID. which was printed by bpimmedia in step 2. This is required when the host is different than the machine on which you are running this command. the slot number (S278) is listed in the vault slot field: vmquery -m S04440 =============================================================== === . or container ID of the tape to recall. as follows: UNIX: # bpimagelist -L -backupid fgolddust_0862806643 | grep Primary Primary Copy: 1 Windows: bpimagelist -L -backupid fgolddust_0862806643 | find Primary Primary Copy: 1 4 Tell NetBackup to use the duplicated copy rather than the original. you can use the vmquery command. In the following example. slot number. Recall the appropriate volume from off-site storage.

Not Robotic (0) volume group: DB_offsite_volumes vault name: Customer_DB_Vault vault sent date: --vault return date: --vault slot: S278 vault session id: 1 created: Tue Sep 3 10:08:32 2000 assigned: Tue May 6 00:11:45 2001 last mounted: Tue May 6 11:34:25 2001 first mount: Tue Sep 3 18:20:48 2000 expiration date: --number of mounts: 21 max mounts allowed: --=============================================================== === 7 Inject recalled media back into the robot. Perform a normal restore operation. When the tape is returned from the off-site vendor. Perform a normal restore. option. unfreeze the duplicate media to allow the normal expiration process to be followed.. either remove it from the robot or leave it in the robot as the primary copy. Unfreeze media used for duplicates. you can create new duplicate images for transfer to your off-site vault vendor.174 Vaulting and managing media Replacing damaged media media ID: S04440 media type: 8MM cartridge tape (4) barcode: S04440 media description: Added by Media Manager volume pool: Vaulted_CustomerDB (2) robot type: NONE . Then. Select the Empty Media Access Port Prior to Update checkbox. 11 Modify the NetBackup catalog for a large number of images. choose Media and Devices Management. Optionally.. The restore log should show a mount request for the duplicate media. bpmedia -unfreeze -m S04440 -host nirvana 8 9 10 Create new duplicate images. You can also perform this function using the vltinject command. Symantec recommends that you suspend the media so that no images are written to it. If you want to send the tape off-site again. inject it into the appropriate robotic library. . Choose the Inventory Robot. See “Bad or missing duplicate tape” on page 235. from the NetBackup Administration Console. The restore should read from the new primary copy. First Insert the tape into the robot media access port. After the restore is successful.

.Vaulting and managing media Replacing damaged media 175 In a disaster recovery situation in which a large number of images need to have their primary copy modified. run the bpchangeprimary command. This command will change the primary copy of all the backup images in the off-site volume pool for which the media was returned from the off-site vault.

176 Vaulting and managing media Replacing damaged media .

(Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. see the following: ■ ■ ■ ■ “Understanding concurrent copies” on page 177 “Continue or fail for concurrent copies” on page 178 “Creating original images concurrently” on page 180 “Creating duplicate images concurrently” on page 181 Understanding concurrent copies You can create up to four copies of the same backup image concurrently. they are considered duplicate images.) By default. If the images are created during a NetBackup policy job. If the images are duplicated by using the NetBackup Administration Console Catalog node or during a Vault job. Also. You can write images concurrently to the following storage units: . NetBackup must be configured to allow a sufficient number of copies in the Maximum Backup Copies field for the NetBackup master server. For more information. the storage unit must be configured to allow a sufficient number of concurrent jobs to support the concurrent copies (Maximum Concurrent Jobs or Maximum Concurrent Drives Used for Backup setting).Chapter 7 Creating originals or copies concurrently You can create multiple copies of a backup image concurrently. Those copies are created concurrently by the Inline Tape Copy feature. the value is two. All storage units must be connected to the same media server. all are considered original images.

By default. Your choice also can determine whether copies will be ejected. select Advanced Configuration on the Profile dialog box Duplication tab. in Vault. the backup time required may be longer than for one copy. ■ ■ ■ If you create multiple original images concurrently during a NetBackup policy job. You cannot create images concurrently using the following: ■ ■ ■ ■ Storage unit groups Optical devices Quarter-inch cartridge (QIC) devices Third-party copies Continue or fail for concurrent copies When making multiple copies of images concurrently.178 Creating originals or copies concurrently Continue or fail for concurrent copies ■ Media Manager storage units. Network Data Management Protocol (NDMP) storage units only during Vault duplication and only one copy is allowed per duplication rule (NDMP is not supported during original backup). if you specify both Media Manager and disk storage units. the duration of disk write operations will match that of slower removable media write operations. It is possible for a duplication operation to succeed but no ejection to occur. Disk staging storage units. the source and destination storage units can be the same. In NetBackup. Disk storage units.) Because of potential NDMP performance limitations. you can choose how an operation will behave if one of the copies fails. Symantec suggests that you duplicate between disk and tape drives that are directly attached to the same NDMP host. your choice affects all copies of that image. If the NDMP storage unit has more than one drive. Although specifying an NDMP storage unit restricts the number of copies to one. depending on the success or failure of the copy operation. the option is configured to Continue in NetBackup and to Fail All Copies in Vault. you can use multiple duplication rules to specify other storage units for images created by other media servers. the source and destination storage units can be the same. you can use one duplication rule to read an image from one media server and write a copy to an NDMP storage unit and use another duplication rule to read an image from a different media server and write copies to other storage units. (To specify multiple duplication rules in a Vault profile. For example. If the Media Manager storage unit has more than one drive. your continue or fail choice affects only the current image copy. . Also.

NetBackup will automatically retry the backup if time permits and. NetBackup will again try to run the backup (regardless of the frequency of the schedule). In this case. the entire backup job will fail and no copies will be made. . a copy will be ejected for transfer off site. However. the concurrent copy job is considered successful if any of the copies succeed. the Vault profile will not duplicate it. Vault will again try to duplicate the image if the following conditions are true: ■ ■ The image is selected. if you choose Fail All Copies. If the copy fails during the original NetBackup backup job. the next time the backup window for the policy opens. all copies of that image will fail. ■ Fail all copies The behavior of the fail option and the default settings depend on whether the concurrent copies operation was configured in Vault or in NetBackup: ■ In Vault. if you choose Fail All Copies.Creating originals or copies concurrently Continue or fail for concurrent copies 179 Continue copies If you choose Continue for all copies. assign the copy to the off-site volume pool. The Vault profile did not eject the primary backup. The next time the Vault profile runs. NetBackup will do this until the backup succeeds. it is possible that a copy of the image may never get vaulted. it is probable that at least one copy will succeed. duplicate that image and assign it to the off-site volume pool so it will be ejected. ■ In NetBackup. do one of the following: ■ Configure a Vault profile to duplicate the image. although one or more backup windows may pass before the backup is successful. the Vault profile will subsequently duplicate it. That is. Monitor the Activity Monitor for a failed status for the copy that is assigned to the off-site volume pool. You can use the Administration Console Catalog node or the bpduplicate command to duplicate the copy. Either way. independent of the success or failure of other image copy operations. normal NetBackup behavior will ensure that a successful backup for this policy eventually occurs. but it may not be the copy assigned to the off-site volume pool for ejection. If that copy fails. If the copy succeeds during the original backup job. To ensure that media are ejected even if a concurrent copy operation fails during a NetBackup policy backup. and select Fail All Copies.

you can create multiple original backup images concurrently. select Multiple Copies. 7 . Double-click an existing schedule or click New to create a new schedule. then click Configure. expand Master Server > NetBackup Management > Policies. The Schedule dialog box appears. Vaulting original images has many benefits. including easier configuration of Vault. If copy 1 fails. fewer chances for resource contention. 3 4 Select the Schedules tab. Specify the priority of the duplication job for each copy. the first successful copy is the primary copy. from 0 to 99999. 5 6 In the Schedule Attributes tab. The maximum is four. To create multiple backup images concurrently through the policy node 1 2 In the NetBackup Administration Console. The Configure Multiple Copies dialog box appears. Copy 1 is the primary copy.180 Creating originals or copies concurrently Creating original images concurrently Creating original images concurrently In a NetBackup policy job. Double-click an existing policy or: ■ ■ Windows: select Actions > New > New Policy UNIX: click Add New Policy to create a new policy. Specify the number of copies to be created simultaneously. and possibly fewer drives required.

■ ■ 13 Click OK. 9 10 Select the retention level for each copy. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. No media server is specified explicitly. None specifies that the media server that writes to the media owns the media. the expiration date will be the same for the duplicate and original copies. so you must understand when you can use duplication in NetBackup. the expiration date of the copy is the backup date plus the retention period. If you select No Change. A server group. If you select a different retention period. . Specify the volume pool to which each copy will be assigned. 2003. For example. 11 Select whether to Continue the other copies if a copy operation fails or to Fail All Copies. either a media server or server group. 8 Specify the storage unit where each copy will be stored. 12 Specify who should own the media onto which NetBackup writes the images: ■ Any lets NetBackup choose the media owner. the new copy’s expiration date is November 21. Network Data Management Protocol (NDMP) storage units are not supported when creating multiple copies during a NetBackup policy job.Creating originals or copies concurrently Creating duplicate images concurrently 181 A larger number is higher priority. Duplication is not always possible. All media server groups configured in your NetBackup environment appear in the drop-down list. 2003. and its retention period is one week. if a backup was created on November 14. but you want a media server to own the media. All copies are duplicated at the same priority. Creating duplicate images concurrently You can create multiple duplicate backup images concurrently either by using the NetBackup Catalog node or by configuring the Duplication tab of a Vault profile. 14 Configure other schedule criteria as appropriate. it can be used for both the source and the destination. If a Media Manager storage unit has more than one drive.

If all backups in a multiplexed group are duplicated to a storage unit that has the same characteristics as the one where the original backup was created. This ensures that the fragment order and size is maintained in the duplicate. From one server to another. This is done with a single pass of the tape. it is necessary to duplicate all of the backups in the multiplexed group. A multiplexed group is a set of backups that were multiplexed together during a single multiplexing session.of the NetBackup catalogs. the grouping within each multiplexed group is maintained. While any other backup image is being written to a tape that contains the source primary backup.) ■ If you do multiplexed duplication. the multiplex settings of the destination storage unit and the original schedule are ignored. From multiplex to nonmultiplex format. the duplicated group will be identical. When duplicating multiplexed backups. Otherwise. By using the NetBackup scheduler to schedule duplications automatically (unless you use a Vault policy to schedule duplication). However. it is possible that restores from the duplicated backups will not work. While the backup is being created (unless you create multiple backup images concurrently during the backup job). if multiple multiplexed groups are duplicated. . be aware of the following: ■ When duplicating multiplexed SQL-BackTrack backups with multiplex mode enabled. This means that the duplicated groups will have a multiplexing factor that is no greater than that used during the original backup. The duplicate can contain all or any subset of the backups that were ■ included in the original multiplexed group. (A multiplexed group is a set of backups that were multiplexed together during a single session. When it is a multiplexed image of the following: – Auspex FastBackup – NDMP backup – Backups to or from disk type storage units – Nonmultiplexed backups ■ From multiplex format and retain the multiplex ■ format on the duplicate. When the primary backup image is not available. From one media density to another. with the following exceptions: ■ ■ ■ If end of media (EOM) is encountered on either the source or destination media.182 Creating originals or copies concurrently Creating duplicate images concurrently When duplication is possible The following describes when duplication is and is not possible in NetBackup: Table 7-23 Possible circumstances for duplicating a Vault profile Not possible to duplicate backups: ■ Possible to duplicate backups: ■ ■ ■ ■ ■ From one storage unit to another.

see the NetBackup Administrator’s Guide. then click Search Now. . To duplicate backup images concurrently through the catalog node 1 In the NetBackup Administration Console. 2 3 4 In the Action field. Right-click the image you want to duplicate and select Duplicate from the shortcut menu. Select the search criteria for the image you want to duplicate. For more information. expand Master Server > NetBackup Management > Catalog.Creating originals or copies concurrently Creating duplicate images concurrently 183 ■ If any of the fragments in the source backups are zero length (which can occur if many multiplexed backups start at the same time). select Duplicate. Volume I. during duplication these zero-length fragments are removed. Concurrent copies through the catalog node Use the following procedure to create concurrent copies of backup images manually through the NetBackup Administration Console Catalog node.

2001. 13 Specify who should own the media onto which NetBackup writes the images: ■ Any lets NetBackup choose the media owner. the expiration date for the copy is the backup date plus the retention period. the new copy’s expiration date is November 21. and you have configured continue as the fail option. the expiration date is the same for the duplicate and source copies. it can be used for both the source and destination. from 0 to 99999. A larger number is higher priority. select one of the retention level options. four copies are to be created and there are only two drives. 12 Specify whether the remaining copies should continue or fail if the specified copy fails. 11 To change the retention level for the copy. either a media server or server group. If a Media Manager or NDMP storage unit has more than one drive. for example. check the appropriate box. If you specify a numeric retention level. All copies are duplicated at the same priority. Otherwise. If you want one of the duplicated copies to become the primary copy. if a backup was created on November 14. Because of this potential deadlock. NetBackup restores from the primary backup. By default. the original backup image created during a NetBackup policy job is the primary copy. If enough drives are available.184 Creating originals or copies concurrently Creating duplicate images concurrently 5 6 The Setup Duplication Variables dialog box appears. For example. the system may require operator intervention if. Network Data Management Protocol (NDMP) storage units are supported only when one copy is created. Specify the storage unit where each copy will be stored. If the copy that you indicate as primary fails. If No Change is selected for the retention period. . specify a different volume pool to ensure a different volume is used. Specify the number of copies to be created. and Vault duplicates from the primary backup. NetBackup does not verify in advance that the media ID selected for the duplicate copy is not the same as the media ID of the volume that contains the original backup. the first successful copy is the primary copy. 2001 and its retention period is one week. Specify the priority of the duplication job for each copy. the copies will be created simultaneously. 7 8 9 10 Specify the volume pool to which each copy will be assigned.

duplication occurs serially using the fewest media mounts and least tape positioning time. select Preserve Multiplexing. No media server is specified explicitly. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. but you want a media server to own the media. ■ 14 If the selection includes multiplexed backups and the backups are to remain multiplexed in the duplicate. Only one backup is processed at a time. which displays the advanced duplication criteria. then select the duplication job just created to view the job results. NetBackup first duplicates all backups that cannot be multiplex duplicated before the multiplexed backups are duplicated. All media server groups configured in your NetBackup environment appear in the drop-down list. 15 Click OK to start duplicating. If Preserve Multiplexing is enabled.Creating originals or copies concurrently Creating duplicate images concurrently 185 ■ None specifies that the media server that writes to the media owns the media. (A multiplexed group is a set of backups that were multiplexed together during a single session. If you do not duplicate all the backups in a multiplexed group. Concurrent copies during basic duplication You can create multiple duplicate images concurrently in Vault by selecting either Multiple Copies on the basic Duplication tab or Advanced Configuration on the basic Duplication tab. A server group. . You can use the following instructions to create multiple copies concurrently from the basic Duplication tab.) By default. the duplicate will have a different layout of fragments. 16 Click the Results tab.

186 Creating originals or copies concurrently Creating duplicate images concurrently Instructions for configuring duplication in Vault also are included in “Duplication tab” on page 98. Enter the number of drives to be used for reading backup images for duplication. check Alternate Read Server and select the media server to use. 4 Select Multiple Copies. the same number will be entered into the destination Write Drives field. When you enter a number of read drives. . You must have an equivalent number of read and write drives available. you can specify a different media server to read the original backups than the media server that wrote the backups. then click Configure. To use a media server that is different from the server that wrote the images. 3 Note: Alternate read servers apply to NetBackup Enterprise Server only. If robots (or drives) are shared by more than one media server. The following is the basic Duplication tab: To create multiple copies concurrently by using the basic duplication tab 1 2 Indicate whether the images you want to duplicate reside on disk storage units only or on disk and/or media storage units.

which means one original backup and one copy. 6 7 Note: All storage units must be connected to the same media server. the source and destination storage units can be the same. the first successful copy is the primary copy. specify a different volume pool to ensure a different piece of media is used. By default. (Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. 8 Specify a volume pool for each copy. Because of this potential deadlock. Specify the storage unit to be used for the duplication. NetBackup does not verify in advance that the media ID selected for the duplicate copy is not the same as that of the piece of media that contains the original backup. the value is two.Creating originals or copies concurrently Creating duplicate images concurrently 187 The Multiple Copies dialog box appears. Network Data Management Protocol (NDMP) storage units are supported only when one copy is created. and Vault duplicates from the primary backup. and you have configured continue as the fail option.) By default. The number of copies you can choose cannot exceed the number of copies specified in the Maximum Backup Copies field for the NetBackup master server. 5 Select the number of copies to create. If the Media Manager or NDMP storage unit has more than one drive. the original backup image creating during a NetBackup policy job is the primary copy. select which copy is to be primary. If you want one of the copies to be the primary copy. If the copy that you indicate as primary fails. Specify the retention level for each copy. NetBackup restores from the primary backup. 9 .

the expiration date for the duplicate media is calculated by adding the specified retention period to the date the original backup was created. see “Assigning multiple retentions with one profile” on page 156. 10 Indicate what action is to be taken if a copy fails. and the backup image will be unavailable for a restore. 13 Specify the priority of the Vault duplication jobs. All media server groups configured in your NetBackup environment appear in the drop-down list. By default. If you specify a numeric retention level. The next time the Vault profile runs. including tape drives. it is possible that a copy of the image may never get vaulted. all copies of that image will fail. If you want your Vault duplication jobs to obtain resources before other processes. independent of the success or failure of other image copy operations. However. but you want a media server to own the media. If you specify Use Mappings for the retention level. the option is configured to Fail All Copies in Vault. Vault will again try to duplicate the image if the following conditions are true: ■ ■ The image is selected. ■ 12 Click OK to return to the basic Duplication tab. information about the expired backup will be deleted from the NetBackup and Media Manager catalog. the volume will be recalled from off-site storage. When the retention period expires. A server group. . it is probable that at least one copy will succeed. A larger number is higher priority. Vault considers the duplication job successful if any of the copies succeed. For more information. In Vault. None specifies that the media server that writes to the media owns the media. from 0 to 99999. the retention period is based on the retention period of backup image copy 1. Vault duplication jobs compete with other process in NetBackup (such as regularly scheduled backups) for resources. If you choose Continue for all copies. 11 Specify who should own the media onto which you are duplicating images: ■ ■ Any lets NetBackup choose the media owner. if you choose Fail All Copies. it is the same as the primary copy. but it may not be the copy assigned to the off-site volume pool. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written. The Vault profile did not eject the primary backup.188 Creating originals or copies concurrently Creating duplicate images concurrently Each image copy can have a separate expiration date. No media server is specified explicitly. All duplication jobs for the profile run at the same priority. If you do not specify a retention level.

.Creating originals or copies concurrently Creating duplicate images concurrently 189 assign a higher priority to the Vault jobs than to other NetBackup processes. Be sure you allow enough time for the duplication operation to be completed. 16 Check Expire Original Disk Backup Images. and then enter the number of hours after this Vault session completes to expire the disk images. If the option to preserve multiplexing is selected. 17 After you have completed the dialog box. select Preserve Multiplexing. ensure that the destination storage unit configured for each copy has multiplexing enabled. By default. the multiplexed duplication process will occur for all multiplexed images that are selected for duplication during a given Vault session. Concurrent copies during advanced duplication You can use the following instructions to create multiple copies concurrently from the advanced configuration criteria of the Vault profile Duplication tab. Use this option to free up space on the disk for subsequent backup images. which improves tape drive utilization during duplication and duplicates more data sooner. 14 To preserve multiplexing. 15 Select Duplicate Smaller Images First to duplicate images in smallest to largest order. Note: If the source image is multiplexed and the Preserve Multiplexing option is selected. If the duplication of a disk image fails. Multiplexing is configured in NetBackup Management > Storage Units. and synthetic backups is assigned in the master server Global Properties. you can select this option so that those images are duplicated before the larger images. restores. If you know that your most important data is in smaller backup images. Priority for backups. Multiplexing is the process of sending concurrent-multiple backup images from one or more clients to the same piece of media.. the disk image will not be expired. This process speeds up duplication but slows down restores and disaster recovery processes. click OK. . Instructions for configuring duplication in Vault also are included in “Duplication tab” on page 98. Vault duplicates images from largest to smallest. This choice does not affect the total time required to duplicate the images.

. The dialog box changes to display more advanced duplication options. If you select Alternate Read Server. To use a server that is different from the server that wrote the images. check Alternate Read Server. select Advanced Configuration. If robots (or drives) are shared by more than one media server. the SOURCE area displays an Alternate Read Server column heading. Note: Alternate read servers apply to NetBackup Enterprise Server only. click New.190 Creating originals or copies concurrently Creating duplicate images concurrently The following shows the Duplication tab when Advanced Configuration has been selected: To create multiple copies concurrently by using advanced configuration options 1 2 On the Duplication tab. 3 To add a destination media server and duplication rules for that server. you can designate a different media server to read the original backups than the media server that wrote the backups.

If you selected Alternate Read Server on the Duplication tab. and Vault duplicates from the primary backup. the Duplication Rule dialog box will have fields for both source Media Server and Alternate Read Server. select the source Media Server. 6 Select the number of copies to create. If you want one of the copies to be the primary copy. 4 5 Select the source Backup Server or. If you did not select Alternate Read Server. if you selected Alternate Read Server on the Duplication tab. If you selected Alternate Read Server on the Duplication tab. (Configured in NetBackup Management > Host Properties > Master Server > server_name > Global NetBackup Attributes. Note: Alternate read servers apply to NetBackup Enterprise Server only. the value is two: one original backup and one copy. By default. only a source Backup Server field appears. the original backup image creating during a 7 . The source media server and alternate read server may be the same. You can create up to 4 or the number of copies specified in the Maximum Backup Copies field for the NetBackup master server (if less than 4).) By default. NetBackup restores from the primary backup.Creating originals or copies concurrently Creating duplicate images concurrently 191 The Duplication Rule dialog box appears. select which copy is to be primary. select an Alternate Read Server.

192 Creating originals or copies concurrently Creating duplicate images concurrently

NetBackup policy job is the primary copy. If the copy that you indicate as primary fails, and you have configured continue as the fail option, the first successful copy is the primary copy. 8 Specify the storage unit to be used for the duplication. If the Media Manager or NDMP storage unit has more than one drive, the source and destination storage units can be the same. Network Data Management Protocol (NDMP) storage units are supported only when one copy is created.

Note: All storage units must be connected to the same media server. 9 Specify a volume pool for each copy. NetBackup does not verify in advance that the media ID selected for the duplicate copy is not the same as that of the piece of media that contains the original backup. Because of this potential deadlock, specify a different volume pool to ensure a different piece of media is used.

10 Specify the retention level for each copy. Each image copy can have a separate expiration date. If you do not specify a retention level, it is the same as the primary copy. If you specify a numeric retention level, the expiration date for the duplicate media is calculated by adding the specified retention period to the date the original backup was created. If you specify Use Mappings for the retention level, the retention period is based on the retention period of backup image copy 1. For more information, see “Assigning multiple retentions with one profile” on page 156. When the retention period expires, information about the expired backup will be deleted from the NetBackup and Media Manager catalog, the volume will be recalled from off-site storage, and the backup image will be unavailable for a restore. 11 Indicate what action is to be taken if a copy fails. In Vault, if you choose Fail All Copies, all copies of that image will fail, independent of the success or failure of other image copy operations. The next time the vault profile runs, Vault will again try to duplicate the image if the following conditions are true:
■ ■

The image is selected.

The Vault profile did not eject the primary backup. By default, the option is configured to Fail All Copies in Vault. If you choose Continue for all copies, Vault considers the duplication job successful if any of the copies succeed. However, it is possible that a copy of

Creating originals or copies concurrently Creating duplicate images concurrently

193

the image may never get vaulted; it is probable that at least one copy will succeed, but it may not be the copy assigned to the off-site volume pool. 12 Specify who should own the media onto which you are duplicating images:
■ ■

Any lets NetBackup choose the media owner. None specifies that the media server that writes to the media owns the media. No media server is specified explicitly, but you want a media server to own the media. A server group. All media server groups configured in your NetBackup environment appear in the drop-down list. Specifying a media server group allows only those media servers in the group to write to the media on which backup images for this policy are written.

13 Click OK to return to the Duplication tab. 14 Specify the priority of the Vault duplication jobs, from 0 to 99999. A larger number is higher priority. All duplication jobs for the profile run at the same priority. Vault duplication jobs compete with other process in NetBackup (such as regularly scheduled backups) for resources, including tape drives. If you want your Vault duplication jobs to obtain resources before other processes, assign a higher priority to the Vault jobs than to other NetBackup processes. Priority for backups, restores, and synthetic backups is assigned in the master server Global Properties. 15 Indicate whether you want to preserve multiplexing. Multiplexing is the process of sending concurrent-multiple backup images from one or more clients to the same piece of media. This process speeds up duplication but slows down restores and disaster recovery processes. If the option to preserve multiplexing is selected, the multiplexed duplication process will occur for all multiplexed images that are selected for duplication during a given Vault session. Note: If the source image is multiplexed and the Preserve Multiplexing option is selected, ensure that the destination storage unit configured for each copy has multiplexing enabled. Multiplexing is configured in NetBackup Management > Storage Units. 16 Select Duplicate Smaller Images First to duplicate images in smallest to largest order. By default, Vault duplicates images from largest to smallest, which improves tape drive utilization during duplication and duplicates more data sooner. If you know that your most important data is in smaller backup images, you can select this option so that those images are duplicated

194 Creating originals or copies concurrently Creating duplicate images concurrently

before the larger images. This choice does not affect the total time required to duplicate the images. 17 Check Expire Original Disk Backup Images... and then enter the number of hours after this Vault session completes to expire the disk images. Use this option to free up space on the disk for subsequent backup images. Be sure you allow enough time for the duplication operation to be completed. If the duplication of a disk image fails, the disk image will not be expired. 18 Click OK.

Chapter

8

Reporting
The reports for each profile are configured in the profile dialog box Reports tab. When you configure a Vault profile, you specify which reports should be generated, when they should be generated, and how and to whom they should be distributed. After reports are generated and distributed, you can view and print them until the Vault logs for that session are deleted. To view sample Vault reports and log files for this release, refer to the following file on the Symantec Support Web site. Examples of NetBackup 6.5 Vault reports and log files, http://support.veritas.com/docs/287612 For more information, see the following:
■ ■ ■ ■

“Generating reports” on page 195 “Consolidating reports” on page 198 “Viewing reports” on page 200 “Vault report types” on page 201

Related Topics
■ ■

“Reports tab” on page 124 “Vault session log files” on page 222

Generating reports
If the reports for a profile are configured as immediate, the reports are generated when the profile runs. If the reports for a profile are deferred, you can use one of the following methods to generate the reports after the profile runs:

By invoking the Deferred Eject option in the Administration Console and then selecting Generate Reports After Eject.

196 Reporting Generating reports

■ ■ ■

By using the Vault Operator Menu interface. By using the vlteject command. By using a Vault policy that invokes the vlteject command.

When you generate reports, the reports that are selected on the profile dialog box Reports tab are generated and distributed to the destinations specified. Reports can be generated for one session or for multiple sessions. Generating reports and ejecting media from more than one vault session is known as consolidating your reports and ejections. For example, you may duplicate images daily but eject media and generate reports only at the end of the week. Related Topics

“Ejecting media by using the NetBackup Administration Console” on page 142 “Reports tab” on page 124 “Reports that depend on eject” on page 125

■ ■

Generating reports by using the Vault operator menu
You can use the Vault Operator Menu to generate reports. To generate reports by using the Vault operator menu 1 2 3 Start the Vault Operator Menu by invoking the vltopmenu command. If necessary, select a profile. Select one of the following options:
■ ■ ■ ■

Run Reports for This Session Run Individual Reports Consolidate All Reports Consolidate All Reports and Ejects Consolidating reports and ejects also ejects media.

4

Continue as prompted by the Vault Operator Menu.

Generating reports by using the vlteject command
You can use the vlteject command with the -report option to generate reports from the command line. The following is the syntax for the command that generates all reports that have not yet been generated:
vlteject -report

You also can specify a robot, vault, profile, or session for which to generate reports.

These reports will be generated again if vlteject is run again. The following is the format of the vlteject command: vlteject -eject -report -preview [-profile profile_name] [-robot robot_name] [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] [-legacy] The vlteject command resides in the following directory: UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin For more information about the vlteject command. the subset of reports that do not depend on completion of eject will be generated. pending reports from the sessions selected are generated and distributed. To generate reports by using the vlteject command 1 2 In a terminal or command window. the subset of reports that do not depend on completion of eject will be generated and distributed. In the Vault policy. If eject has not been completed. You also can specify a robot. Generating reports by using a Vault policy You can use a Vault policy to generate reports for Vault sessions that have been completed already and for which reports have not been generated.Reporting Generating reports 197 If the corresponding eject process has been completed. Invoke the command. profile. or session for which to generate reports. using the appropriate options and parameters. The following is the format of the vlteject command: vlteject -eject -report -preview [-profile profile_name] [-robot robot_name] [-vault vault_name [-sessionid id]] [-auto y|n] [-eject_delay seconds] [-legacy] The vlteject command resides in the following directory: . If the corresponding eject process has been completed. do not specify clients. pending reports from the sessions selected are generated and distributed. If eject has not been completed. and specify the vlteject command with the -report option on the Backup Selections tab. change to the directory in which the vlteject command resides. The reports will not be generated again if vlteject is run again. see the NetBackup Commands for UNIX or NetBackup Commands for Windows manual. these reports will be generated again if vlteject -report is run again after eject has been completed. specify Vault as the policy type. The reports will not be generated again if vlteject is run again. vault.

The Add a New Policy dialog box appears. Consolidating reports Note: If you consolidate reports. You can consolidate the following: . see the NetBackup Commands for UNIX or NetBackup Commands for Windows manual. When you generate the reports. On the Attributes tab. you select the robot. On the Schedules tab. you should also consolidate ejects. Complete the schedule. To do so. select Vault as the policy type. 10 Click OK. enter the vlteject command with the -report option and any other appropriate options. vault. The type of backup defaults to Automatic Vault.198 Reporting Consolidating reports UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin For more information about the vlteject command. See “Ejecting media” on page 140. expand NetBackup Management > Policies. you may duplicate images daily but eject media and generate reports only at the end of the week. For example. Click OK. or profile sessions for which reports were deferred (that is. which is known as consolidating your reports and ejections. To create a Vault policy that generates reports 1 2 3 4 5 6 7 8 9 In the NetBackup Administration window. for reports that are pending). Enter a unique name for the new policy in the Add a New Policy dialog box. Click the New Policy button. On the Backup Selections tab. You can generate reports and eject media from more than one vault session. eject the media and generate the reports. specify deferred reports on the Reports tab and deferred eject on the Eject tab for each profile for which you want to consolidate reports. The Add New Policy dialog box appears. Then. click New to create a new schedule. Bypass the Client tab (clients are not specified for Vault jobs).

only the container information from the most recent session appears. All sessions for a vault. The customized report title is printed on the report and appears in the e-mail subject line if you e-mail the reports. If media applies to more than one session. Each time range will be calculated based on the start time of the individual sessions participating in the consolidated report. or profiles that are included in the report. the earliest date range among the consolidated sessions is the end date. a consolidated Picking List for Robot will include the appropriate media from all sessions whose profile has Picking List for Robot selected on the Reports tab. Time ranges specified in individual profiles will be used to generate the reports. All sessions for a robot. Summary In the Recovery Report. . vaults. All sessions for all vaults. the subset of reports that do not depend on completion of eject will be generated. use the same customized report title for all profiles whose reports will be consolidated. The sessions included in the report.Reporting Consolidating reports 199 ■ ■ ■ ■ All sessions for a profile. The robots. and the Recovery Report is generated from the current date and time to that end date. Report Body Shows media from all sessions included in the consolidation in which the report is selected on the profile Reports tab. similarly for containers. these reports will be generated again if deferred reports are run again. If you consolidate reports and also rename reports. A consolidated report includes information from all sessions in which that report is specified in the profile. The following defines the elements of a consolidated report: Table 8-24 Report element Report Header Consolidated reports elements Description Includes the following: ■ ■ ■ Identifies the report as a consolidated report. If eject has not been completed. only the information from the most recent session is included. For example. Shows the same information as in a nonconsolidated report.

the Reports window is displayed. Old Style Consolidated Reports Consolidated reports in previous releases of Vault simply concatenated the same reports from each session together. One advantage of that style is that you can consolidate reports from slot and container based vaults. which you cannot do with the new style of consolidated report. you also may have to specify a date range or time period. 3 . If you currently do immediate reports. you will have to change to deferred reports and either run the vlteject command manually or create a Vault policy to schedule the vlteject -report -legacy job. the picking list reports are only valid on the date they were generated. Select one of the Vault reports or report types. You can only view reports if the session directory for that vault still exists. for example. Only some of the reports will be valid. To view Vault reports 1 2 Select NetBackup Management > Reports > Vault Reports. you must specify a profile and a session ID. When you select a report or report type. Enter or select the appropriate values for the report you want to generate. you can use the vlteject command -report and -legacy options to consolidate the reports in that old style. you can add the -legacy option to the vlteject command you use to generate reports. Usually. Related Topics ■ ■ ■ ■ “Consolidating ejects” on page 146 “Reports that depend on eject” on page 125 “Eject tab” on page 118 “Reports tab” on page 124 Viewing reports You can use the NetBackup Administration Console to view and print reports for Vault sessions for which reports have already been generated. The Reports window includes a Report Settings area and a report contents window.200 Reporting Viewing reports Note: Reports cannot be consolidated between vaults that use slots and vaults that use containers. If you currently do deferred reports. If you prefer the old style of consolidated reports.

Media on these reports are from the eject. Vault report types The following reports and types of reports are available in Vault: ■ ■ ■ ■ ■ ■ ■ ■ Reports for media going off-site Reports for media coming on-site Inventory reports Container inventory report Recovery Report for Vault Lost Media report Non-vaulted Images Exception report Iron mountain FTP file Reports for media going off-site The reports for media going off-site show media that have been ejected from the robot and will be transported off-site. They vary in the amount of detail included in each report. for consolidated reports. displays zero. Picking List for Robot The Picking List for Robot report shows the volumes ejected from the robot that should be transported off-site. You can save the report for tracking purposes.list files of all unreported vault jobs (an unreported vault job is one that ejects media but does not generate reports). . This report is sorted by media ID and should be used by the operations staff as a checklist for media that has been ejected from the robots. click File > Print. Table 8-25 Column IMAGES Columns in the Picking List for Robot report Description The number of images on the volume. To print the report. or you can reprint it as long as the session directory still exists.Reporting Vault report types 201 4 5 Click Run Report. For Vault catalog backup media from releases earlier than NetBackup 6.list file for the session or.0. the combined eject.

The size in megabytes of images on the volume.0.0. For Vault catalog backup media from releases earlier than NetBackup 6. displays the date calculated as a return date during the volume assignment.202 Reporting Vault report types Table 8-25 Column CONTAINER ID Columns in the Picking List for Robot report Description The ID of the container in which the volume will reside in the vault. The vault vendor should use this report to verify that all the volumes listed were actually received. Table 8-26 Column IMAGES Columns in the Distribution List for Vault report Description The number of images on the volume. Media not managed by NetBackup.) The ID of the slot in which the volume will reside at the off-site vault. (Container vaulting only. The number of the robot from which the media was ejected.0 Add-on. This report is sorted by off-site slot number or container number and should accompany the media that is destined for the off-site vault. (Consolidated report only. Catalog backup media from NetBackup releases earlier than 6. (Container vaulting only. For Vault catalog backup media.) Yes or No. The ID of the container in which the volume resides in the vault. displays zero.0 and later releases.) Distribution List for Vault The Distribution List for Vault report shows the volumes that have been ejected from the robot and will be transported off-site. Catalog backup media from NetBackup 6. NetBackup media that contains backup images. displays the date calculated as a return date during the volume assignment. the field is empty. Date when the images on the volume expire. such as VSM media. Date when the images on the volume expire. For Vault catalog backup media. The type of media: ■ ■ ■ ■ EJECTED EXPIRATION MBYTES CATEGORY NBU. MEDIA ROBOT SLOT ID The ID of the media. Old NBU CTLG. CONTAINER ID EJECTED EXPIRATION .) Yes or No. New NBU CTLG. For Vault catalog backup media from releases earlier than NetBackup 6. (Slot vaulting only.

The date the container should be returned from the off-site vault. For Vault catalog backup media from releases earlier than NetBackup 6. The type of media: ■ ■ ■ ■ CATEGORY NBU. such as VSM media. If two or more fragments of the same image are on one volume. Catalog backup media from NetBackup releases earlier than 6. MEDIA RETURN DATE SLOT ID VAULT The ID of the media. The ID of the container in which the volume resides in the vault. fragments of a backup image may appear on more than one volume. EJECTED .0. Catalog backup media from NetBackup 6. they are reported on one line rather than on a separate line for each fragment (that is. New NBU CTLG.) The name of the vault to which the volume’s profile belongs. (Container vaulting only. Name of the client that was backed up.Reporting Vault report types 203 Table 8-26 Column MBYTES Columns in the Distribution List for Vault report (continued) Description The size in megabytes of images on the volume. The ID of the slot in which the volume resides in the off-site vault. Old NBU CTLG. the field is empty.0 Add-on. Table 8-27 Column BACKUP ID CLIENT CONTAINER ID Columns in the Detailed Distribution List for Vault report Description Identifier that NetBackup assigns when it performs the backup. NetBackup media that contains backup images. This report is similar to the Picking List for Robot and Distribution List for Vault reports except that it includes detailed information about the images on each volume.0 and later releases. Media not managed by NetBackup. This report is useful at a disaster recovery site. Symantec recommends that you send this report off-site. Because backup jobs can span volumes. (Slot vaulting only.) Detailed Distribution List for Vault The Detailed Distribution List for Vault report shows the volumes that have been ejected from the robot and will be transported off-site.) Yes or No. (Consolidated report only. each image is listed once for every media its fragments reside on).

except that the entry for each piece of media will list only a unique client. Catalog backup media from NetBackup releases earlier than 6. PARTIAL if some fragments reside on other volumes. The ID of the slot in which the volume resides in the off-site vault. (Consolidated report only. POLICY SCHEDULE SLOT ID VAULT WRITTEN Name of the policy that was used to back up the client.0 and later releases. The Summary Distribution List for Vault report summarizes the information and presents it in . For Vault catalog backup media. Catalog backup media from NetBackup 6. New NBU CTLG.0. (Slot vaulting only. For Vault catalog backup media from releases earlier than NetBackup 6.) The name of the vault to which the volume’s profile belongs. The size in megabytes of all images on the volume. EXTRA if the images does not belong to the session. displays zero. Name of the schedule that was used to back up the client. only one line of information will be printed out on this report. Old NBU CTLG. Partial images on the volume.0. MEDIA PARTIAL The ID of the media. such as VSM media. The number of images on the volume. That is.204 Reporting Vault report types Table 8-27 Column EXPIRATION Columns in the Detailed Distribution List for Vault report (continued) Description Date when the images on the volume expire. policy and schedule (usually seen with RDBMS backups or SAP backups) are written to the same volume on the same date. Media not managed by NetBackup. the field is empty. NetBackup media that contains backup images.) The date the image was written. if multiple backup jobs for a given client. displays the date calculated as a return date during the volume assignment. The size in kilobytes of the complete backup image. For Vault catalog backup volumes. schedule and date. The size of the complete image is listed even if the image is a fragment. Summary Distribution List for Vault This report is similar to the Detailed Distribution List for Vault report. the field is empty. The field displays: ■ ■ ■ COMPLETE if all fragments reside on that volume. which may generate a very long report. The Detailed Distribution List would show each of these backup jobs as a separate entry. For Vault catalog backup media from releases earlier than NetBackup 6. The type of media: ■ ■ ■ ■ IMAGES KBYTES MBYTES CATEGORY NBU.0 Add-on. policy.

such as VSM media. . New NBU CTLG.0. Catalog backup media from NetBackup 6. Name of the policy that was used to back up the client. For Vault catalog backup media.) Yes or No. For Vault catalog backup media from releases earlier than NetBackup 6. Catalog backup media from NetBackup releases earlier than 6. The size in megabytes of images on the volume. (Slot vaulting only.0. displays the date calculated as a return date during the volume assignment. This report is also very useful for disaster recovery situations. The ID of the container in which the volume resides in the vault. (Container vaulting only. To appear in these reports.) Reports for media coming on-site The reports for media coming on-site show the volumes that are being requested back from the off-site vault. Table 8-28 Column IMAGES Columns in the Summary Distribution List for Vault report Description The number of images on the volume. NetBackup media that contains backup images. Name of the client that was backed up. displays zero. we recommend that you send this report off-site. Name of the schedule that was used to back up the client. These reports can be generated before or after media has been ejected for the current Vault session. When the backup occurred. Old NBU CTLG. The type of media: ■ ■ ■ ■ BACKUP TIME CLIENT CONTAINER ID EJECTED EXPIRATION MBYTES CATEGORY NBU.Reporting Vault report types 205 a more compact form. Media not managed by NetBackup. (Consolidated report only.0 Add-on. media must: ■ Be in a Vault off-site volume group. The ID of the slot in which the volume resides in the off-site vault. the field is empty.) The name of the vault to which the volume’s profile belongs. Date when the images on the volume expire. MEDIA POLICY SCHEDULE SLOT ID VAULT The ID of the media. For Vault catalog backup media from releases earlier than NetBackup 6.0 and later releases.

This report should be sent off-site to the vault vendor. A slot at the off-site vault from which an expired volume is recalled will be available for use one day after the volume has been physically returned to the robot. Have a non-null return date which has passed when the report is generated (Catalog backup and VSM media only). Expired media appear on this report only once: either on the date the media expire or the next time the report is generated (if the report is not generated on the date a volume expires). does not appear for consolidated report. Also for VSM media the session ID should not be zero. they will appear on the Lost Media report. Table 8-29 Column CONTAINER ID Columns in the Picking List for Vault report Description The ID of the container in which the volume resides in the vault. If media appear on the report but are not recalled. For Vault catalog backup media from releases earlier than NetBackup 6. (Session report only. Be unassigned (NetBackup media only). DENSITY LAST MOUNT LAST SID .) The session ID of the Vault session that recalled the media.206 Reporting Vault report types ■ Be in an eject volume pool for a profile in the current vault or in a scratch pool. ■ ■ ■ ■ Picking List for Vault The Picking List for Vault report shows the volumes that are being requested back from the off-site vault. (Container vaulting only. Have a vault container value that is non-null (container vaulting only).0. If you use a scratch pool. displays a dash (-). it changes the Return Date field for the media and adds the media ID and date requested to this report. Volumes are listed on this report because Vault determined that they are in an off-site volume group and that all images have expired. this report may include volumes from other profiles or vaults that have expired and moved back into the scratch pool even if the report is for a specific Vault profile or session.) Density of the volume. The date the volume was last mounted. Be in any vault if the media is in a scratch pool. When Vault identifies these volumes.

For Vault catalog backup media from releases earlier than NetBackup 6. This report is identical to the Picking List for Vault. Retain this report to use as a checklist for the media returned from the off-site vault. displays a dash (-).Reporting Vault report types 207 Table 8-29 Column CATEGORY Columns in the Picking List for Vault report (continued) Description The type of media: ■ ■ ■ ■ NBU.0 and later releases. does not appear for consolidated report. Media not managed by NetBackup. (Session report only. Catalog backup media from NetBackup releases earlier than 6. New NBU CTLG.0 Add-on. such as VSM media.) The session ID of the Vault session that recalled the media. (Consolidated report only. (Container vaulting only. (Slot vaulting only. The date the volume was last mounted.) The name of the vault to which the volume’s profile belongs. (Container vaulting only. except that it includes the robot to which the media should be returned. MEDIA REQUESTED RETURN DATE The ID of the media. Old NBU CTLG. If you use a scratch pool.) The ID of the slot in which the volume resides in the off-site vault. DENSITY LAST MOUNT LAST SID . NetBackup media that contains backup images.) Density of the volume. Date when the volume is requested back from the off-site vault.0. Table 8-30 Column CONTAINER ID Columns in the Distribution List for Robot report Description The ID of the container in which the volume resides in the vault. this report may include volumes from other profiles or vaults that have expired and moved back into the scratch pool even if the report is for a specific Vault profile or session. The date the container should be returned from the off-site vault. Catalog backup media from NetBackup 6.) SLOT ID VAULT Distribution List for Robot The Distribution List for Robot report shows the volumes that are being requested back from the off-site vault.

The date the container should be returned from the off-site vault.) ROBOT SLOT ID Inventory reports The inventory reports show the location of the media. Media not managed by NetBackup. (Consolidated report only. In the current vault or in any vault if the media is in a scratch pool.) The ID of the slot in which the volume resides in the off-site vault. To appear in this report.208 Reporting Vault report types Table 8-30 Column CATEGORY Columns in the Distribution List for Robot report Description The type of media: ■ ■ ■ ■ NBU. in a scratch pool. NetBackup media that contains backup images.0 and later releases. (Slot vaulting only. (Container vaulting only. media must be: ■ ■ ■ In the off-site volume group. Vault inventory The Vault Inventory (or Inventory List for Vault) report shows media that are off-site at the vault vendor and media being sent off-site (outbound media in transit to the vault). In an eject volume pool for a profile in the current vault. such as VSM media. . Catalog backup media from NetBackup 6. Also. MEDIA REQUESTED RETURN DATE The ID of the media. Date when the volume is requested back from the off-site vault.0 Add-on. Catalog backup media from NetBackup releases earlier than 6.) The number of the robot in which the media resided. These reports are not generated until the media have been ejected. select the most recent session for that profile so the most recent data is reported. or in the catalog volume pool. New NBU CTLG. If you use the NetBackup Administration Console to display an inventory report. Old NBU CTLG. you must select a profile that ejects media.

Table 8-31 Column ASSIGNED Columns in the Vault Inventory report Description The date when the volume was assigned by NetBackup Media Manager.) The name of the vault to which the volume’s profile belongs. New NBU CTLG. Catalog backup media from NetBackup 6. Usually. the Inventory List for Vault report is sent to the vault vendor to perform verification.Reporting Vault report types 209 Symantec recommends that you send this report to your vault vendor so they can verify that they have the volumes that Vault indicates are at the vault vendor. Rather. Table 8-32 Column ASSIGNED Columns in the Off-site Inventory report Description The date when the volume was assigned by NetBackup Media Manager. .) Date when the images on the volume expire. this report may include volumes from other profiles or vaults that have expired and moved back into the scratch pool even if the report is for a specific Vault profile or session. Old NBU CTLG. (Container vaulting only. this report is not generated on a daily basis. Media not managed by NetBackup. The ID of the slot in which the volume resides in the off-site vault. (Slot vaulting only.0. inbound media in transit). displays a dash (-). NetBackup media that contains backup images. displays a dash (-). MEDIA SLOT ID VAULT The ID of the media. If you use a scratch pool.0. Catalog backup media from NetBackup releases earlier than 6.) Off-site inventory The Off-site Inventory (or Full Inventory List for Vault) report includes the information in the Vault Inventory report and also includes any volumes that have been requested back from the off-site vault vendor (that is.0 Add-on. The ID of the container in which the volume resides in the vault. The type of media: ■ ■ ■ ■ CONTAINER ID EXPIRATION CATEGORY NBU.0 and later releases. such as VSM media. (Consolidated report only. For Vault catalog backup media from releases earlier than NetBackup 6. For Vault catalog backup media from releases earlier than NetBackup 6.

(Slot vaulting only. media must be: ■ ■ ■ In the robotic volume group or off-site volume group. In the current vault or in any vault if the media is in a scratch pool. Catalog backup media from NetBackup releases earlier than 6. The ID of the slot in which the volume resides in the vault. Catalog backup media from NetBackup 6. The type of media: ■ ■ ■ ■ EXPIRATION CATEGORY NBU. (Container vaulting only. To appear in this report. this report may include volumes from other profiles or vaults that have expired and moved back into the scratch pool even if the report is for a specific Vault profile or session. NetBackup media that contains backup images. MEDIA REQUESTED SLOT ID VAULT The ID of the media. The date the volume was requested to be returned from the off-site vault.) Date when the images on the volume expire. Table 8-33 Column CONTAINER ID Columns in the All Media Inventory report Description The ID of the container in which the volume resides in the vault.0 Add-on. If you use a scratch pool.0 and later releases. (Container vaulting only.210 Reporting Vault report types Table 8-32 Column CONTAINER ID Columns in the Off-site Inventory report (continued) Description The ID of the container in which the volume resides in the vault. EXPIRATION . In an eject volume pool for a profile in the current vault or in a scratch pool. (Consolidated report only. Note: Volumes within the off-site volume pool must belong to either the off-site volume group or the robotic volume group or they will not appear on this report. New NBU CTLG. such as VSM media. Old NBU CTLG.) All media inventory The All Media Inventory (or Complete Inventory List for Vault) report shows all volumes in the off-site volume pool.) The name of the vault to which the volume’s profile belongs. Media not managed by NetBackup.) Date when the images on the volume expire.

the return date of each container. For a consolidated report. The ID of the media. . Alternatively. The ID of the session that duplicated and/or ejected this volume. The date the volume was requested to be returned from the off-site vault. shows the robot number if the volume is in the robot or the vault name if the volume is off-site. The ID of the slot in which the volume resides in the off-site vault. and the media that are in each container. shows Robot or Vault. (Slot vaulting only. you can specify a container ID to generate a report of the media in a specific container. For a session report.Reporting Vault report types 211 Table 8-33 Column LOCATION Columns in the All Media Inventory report (continued) Description Shows where the volume resides.) MEDIA REQUESTED SID SLOT ID Graphical representation of inventory reports scope The following illustration shows the different scopes of the reports: Container inventory report The Container Inventory report shows all the containers configured in your vaulting environment.

NetBackup catalog backups do not appear even if they have been ejected and transferred off site. you will not be able to generate a Recovery report to determine which volumes to request . The date the container should be returned from the off-site vault. If the master server is destroyed by a disaster. The report displays the date range to which the images on the media apply. Each time range will be calculated based on the start time of the individual sessions participating in the consolidated report. Recovery Report for Vault The Recovery Report for Vault shows all policies defined on a NetBackup master server and all media that are required to restore the backups between a given set of dates. Reports will not show container information until after you add container and media IDs in Vault. Sending the Recovery report to the vault vendor on a regular basis will help with disaster recovery efforts. ■ In a consolidated Recovery report. ID of the media ID that are in the container. Media are removed logically from a container when they are injected back into the robot. the earliest date range among the consolidated sessions is the end date. Time ranges specified in individual profiles will be used to generate the reports. Only Vault catalog backups appear on this report. Date when the container is requested back from the off-site vault. The last session ID of the profile that accessed this volume. This report also includes: ■ The three most recent Vault catalog backups in the vault’s off-site volume group. Table 8-34 Column CONTAINER ID LAST SID MEDIA ID REQUESTED RETURN DATE ROBOT Columns in the Container Inventory report Description The ID of the container in which the volume resides in the vault.212 Reporting Vault report types Generate this report only if you vault your media in containers. The information from the disaster recovery file generated by the catalog backup policy. The robot from which the volumes were ejected. and the Recovery report is generated from the current date and time to that end date.

Media that appear on the Lost Media report have: ■ ■ ■ ■ An assigned date of 0 or are frozen.) The date the catalog backup was written to the volume. Name of the client that was backed up.) The ID of the media. You do not have to configure your profiles for the Lost Media report. The ID of the slot or container in which the volume resides in the off-site vault. VAULT SLOT/CONTAINER Lost Media report The Lost Media report lists expired media that has not been returned from the off-site vault vendor. Name of the schedule that was used to back up the client. (Excluding catalog backup media. A non-null return date. it will never again be listed for recall. Media can get lost for various reasons. it is very important that the vault vendor have a copy of the Recovery report.) The off-site vault at which the media are stored. You change or rename your off-site volume groups and pools.Reporting Vault report types 213 from the vault vendor.) The ID of the media. A robot number value of null. Frozen backup media never expires. as follows: ■ A volume appears on the Picking List for Vault only once. Therefore. (Excluding catalog backup media. if you begin using a new media type. . (Vault catalog backup media only. If a volume from that report is missed and is not returned to the robot. it is not generated when you eject media. you will have to use a new volume pool name. for example. Table 8-35 Field POLICY SCHEDULE CLIENT MEDIA MEDIA ID WRITTEN Fields in the Recovery Report for Vault Description Name of the policy that was used to back up the client. Symantec recommends that you do not change or rename group or pool names. (Vault catalog backup media only. Media that does not expire will not appear on the Picking List for Vault and will not be recalled from the vault. A vault sent date value that is non-null. ■ ■ You must generate the Lost Media report.

Reports also are saved in the session directory. . This report lists the images (from the preview. When a Non-vaulted Images Exception report for a given session is generated. images that expired since the session ran will not be on the report even though they were not vaulted. to use the Non-vaulted Images report effectively. You can save the report by specifying a directory to save the report to on the Profile dialog box Reports tab. Table 8-37 Column ASSIGNED BACKUP ID Columns in the Non-vaulted Images report Description The date when the volume was assigned by NetBackup Media Manager. A good practice is to run the Lost Media report periodically.214 Reporting Vault report types Usually. such as weekly or monthly (depending on your operations). The ID of the media. Therefore. Non-vaulted Images Exception report The Non-vaulted Images Exception report shows images and media that were not vaulted when the Vault session was run. The volume group to which the volume is assigned. the current status of images (in the preview. you should generate it when a session runs and save it so you can refer to it later. media included in the Lost Media report should be returned from off-site and injected back into the appropriate vault in the robot. The date the volume was last mounted. Table 8-36 Column DENSITY LAST MOUNT MEDIA ID REQUESTED VAULT VOLUME GROUP Columns in the Lost Media report Description Density of the volume.list of the session) and the media they reside on is checked for those that were not vaulted. Date when the volume is requested back from the off-site vault.list file) and the media that match the Choose backups criteria. If you generate the report after a session runs. and were not vaulted at the time the report was generated. The vault to which the volume belongs. Identifier that NetBackup assigns when it performs the backup.

VOLUME GROUP VOLUME POOL Iron mountain FTP file If Iron Mountain is your vault vendor. (Slot vaulting only. The number of the Vault robot in which the volume resides. Name of the policy that was used to back up the client. You can use the file transfer protocol (FTP) to send the report file to Iron Mountain electronically. you should verify that the volumes ejected match the Distribution List for Vault. you can configure Vault to produce an Iron Mountain Electronic Format report. The pool to which the volume is assigned. You should contact Iron Mountain to determine where and when to send the report. You must select a report so that it will appear in the Iron Mountain report file.) Name of the schedule that was used to back up the client.) The group to which the volume is assigned.Reporting Vault report types 215 Table 8-37 Column CREATED EXPIRATION MEDIA POLICY ROBOT SCHEDULE SLOT ID Columns in the Non-vaulted Images report Description The date the volume was created (original backup or duplicated). Date when the images on the volume expire. and they use it to update their vaulting mechanism automatically. which is a file that can include the following reports: ■ ■ ■ ■ ■ Picking List for Vault (the “P” section) Distribution List for Vault (the “D” section) Vault Inventory report (if you are vaulting in slots) (the “I” section) Container Inventory report (if you are vaulting containers) (the “C” section) Recovery report (the “R” section) The reports included in the file depend on your selections on the Reports tab of the Profile dialog box. The report will be in a format that Iron Mountain’s automated vaulting mechanism can read and contain the information they require. does not appear for consolidated report. The ID of the slot in which the volume resides in the robot.) (Session report only. . The ID of the media. (Consolidated report only. Before you send the report to Iron Mountain.

216 Reporting Vault report types .

NetBackup passes the e-mail address. see the comments in the nbmail. NetBackup uses the nbmail. On UNIX systems. NetBackup uses the sendmail mail transfer agent to send e-mail. For e-mail notifications. If sendmail is not installed. . For instructions on configuring the script. ■ ■ ■ ■ ■ ■ ■ ■ “Setting up E-mail” on page 217 “Administering access to Vault” on page 218 “Printing Vault and profile information” on page 220 “Copying a profile” on page 220 “Moving a Vault to a different robot” on page 221 “Changing volume pools and groups” on page 221 “Vault session log files” on page 222 “General operational issues” on page 224 Setting up E-mail Depending on your computing environment. On Windows systems.Chapter 9 Administering Vault The following sections provide information about performing the tasks of managing your Vault configuration.cmd script (in install_path\VERITAS\NetBackup\bin) on the NetBackup master server to send e-mail. subject.cmd script. you must install it and configure your environment so it functions correctly. and message to the script. Default NetBackup behavior: nbmail. you may have to configure NetBackup or your computing environment so that notification e-mail from NetBackup functions properly. which then uses the mail program specified in the script to send e-mail.cmd does not send e-mail.

Enhanced Authorization and Authentication. For more information about configuring e-mail for NetBackup. Volume II. Access Management takes precedence. Each user group can perform only the actions explicitly granted and no others. Enhanced authentication allows each side of a NetBackup connection to verify the host and user on the other side of the connection. and assign users to those user groups. In NetBackup Access Management terminology. Vault Operator user group NetBackup Access Management is used to define user groups. Configuring user groups and assigning permissions is done using Access Management in the NetBackup Administration Console. Access Management lets you control access to NetBackup by defining user groups and granting explicit permissions to these groups. For a complete list of the permissions that a Vault operator has. ■ If both Access Management and Enhanced Authorization and Authentication are configured. NetBackup includes a Vault Operator user group that has permission to perform the operator actions necessary for the Vault process. NetBackup runs without enhanced authentication.cmd script so that the Vault reports are mailed correctly. When Vault is installed and licensed. Administering access to Vault NetBackup provides two mutually exclusive methods for controlling user access: ■ Access Management. NetBackup gives administrative privileges to UNIX root administrators or Windows system administrators on NetBackup servers. By default. see the NetBackup Administrator’s Guide. the Vault Operator user group has specific permissions. see the NetBackup Administrator’s Guide. include the -mime option on the blat command in the nbmail.218 Administering Vault Administering access to Vault Note: If you use the Blat e-mail client to deliver e-mail on Windows systems. For information about configuring and using these methods to control access to Vault. Access Management is the newest and will be the preferred method in future NetBackup releases. specify which actions each user group can perform. Volume I. refer to the “Permissions for NetBackup . Enhanced authorization determines if authenticated users (or groups of users) have NetBackup administrative privileges. By default.

such as when ejecting media changes volume group information for the volume ejected. NetBackup Administration Console messages will explain the restriction. Also. the Vault Operator group has permission to update databases — but only to the extent allowed by Vault. the Vault documentation cannot specify which actions are or are not allowed by Access Management. for a list of the Vault operator permissions. For information about installing Access Management components and using Access Management. A Security Administrator also can create new user groups to define new roles. Volume II. If you do not want your operators to view reports and change report destinations. see “Access Management” in the NetBackup Administrator's Guide. those permission sets and permissions apply regardless of whether the actions are invoked from the Vault Operator Menu or the NetBackup Administration Console. do not give them access to the Vault Operator Menu.Administering Vault Administering access to Vault 219 user groups” section in Chapter 4 of the NetBackup Security and Encryption Guide. For example. Caution: Giving operators access to the Vault Operator Menu also gives operators the capability to change report destinations. For example. . the Vault Operator cannot use the NetBackup Administration Console to change database information that is not related to the operate media actions. If an action cannot be performed because of access management restrictions. you may not want your operators to see the Recovery Report or to be able to change to whom reports are e-mailed. A NetBackup Security Administrator (a user group defined within NetBackup Access Management) can use Access Management to add users to the Vault Operator group and change the permission sets and permissions of the Vault Operator group. Because you can change which actions user groups can perform. refer to “Permissions for NetBackup user groups” section in Chapter 4 of the NetBackup Security and Encryption Guide. If you use Access Management to administer access by using the default Vault Operator group. The permissions are granted only in the scope of actions performed in Vault. As defined in the default permission sets.

To copy a profile 1 2 Highlight the profile you want to copy. From the File menu. . The Copy a Profile dialog box displays.220 Administering Vault Printing Vault and profile information Printing Vault and profile information You can print a list of the information (robots. vaults. Enter a new name for the profile. 3 4 5 From the drop down list under the Vault field. rename it. choose the vault in which to place the new profile. or profiles) that is currently displayed in the Administration Console Details Pane. Click OK. Note: The new profile must belong to the same robot as the original profile. Open the Actions menu and select Copy Profile. you can copy the existing profile. choose Print or click the Print icon on the toolbar. and then change the attributes. Copying a profile If you want to create a profile that is similar to another profile.

change its volume pool and group to the new ones . Robots are configured in NetBackup through Media Manager. you can change the robot to which the vault belongs. specifying another robot for the vault. Some profile configurations may be invalid under the new robot. the configuration will be invalid. If you change to a new off-site volume group and/or off-site volume pool(s). Then complete the dialog box. After each volume is recalled and injected back into the robot. you can ensure that media are recalled by configuring a profile that only generates the reports needed to recall media. and click OK. belongs to) a specific robot. To do so. the reports that recall expired media will not include the old groups and pools. The action described here does not change the configuration of a robot in Media Manager. Changing volume pools and groups Caution: If you have media in your off-site vault. right-click on the robot and select Change. if the previous robot was associated with a media server that the new robot is not associated with.Administering Vault Moving a Vault to a different robot 221 Moving a Vault to a different robot A vault is associated with (that is. configure the Choose Backups step so that no backup images are selected) Skips the Duplication and Catalog Backup steps Specifies the old volume pools in the volume pool list on the Eject step Generates only the Picking List for Vault and Distribution List for Robot reports ■ ■ ■ ■ Schedule the profile to run on a regular basis Media in the old off-site volume group and in the old volume pool(s) will be recalled from off-site storage as they expire. as follows: ■ ■ Configure a vault that uses the old off-site volume group Configure a profile in that vault that does the following: ■ Selects no images (that is. Note: All vaults that had been associated with the previous robot will now be associated with the new robot chosen in the dialog box. for example. However. If you begin using new volume pools and groups in your Vault profiles. Symantec recommends that you do not change or rename your off-site volume group(s) or off-site volume pool(s).

and the results of the session. If e-mail notification is enabled.log file contains a brief description of the vault session. The summary. The session identifier for a Vault session can be found by looking at the Activity Monitor entry for that session. The session logs can help you keep track of Vault processes. . either because they were duplicated in a prior session or because the duplication failed for some reason.log has information about the number of images selected by a particular session. it means that some images were not duplicated. Related Topics ■ “Debug logs” on page 238 Session logs The directory generated for each vault session collects information for the session in two log files. The log should contain information about which images were not duplicated. you do not have to change the volume pool). The detail. and volume pools. Vault maintains its session log files for a particular session in the directory for that session. you can delete the vault.log file contains a step-by-step record of each action performed for the session. Vault session log files Vault generates session logs and debug logs. The actual images selected by the session will show up only if a higher debug level (level 5) is used. After all media in those volume pools and groups are recalled. the information in this file is appended to the e-mail.222 Administering Vault Vault session log files (if a volume is returned to a scratch volume pool from which all media are allocated. If these numbers do not match. The detail. In addition. Some of the information in detail. volume group.log is also recorded in the NetBackup log files. The session ID starts at 1 the first time Vault runs and is incremented by 1 for each new session. it should record information (during the duplication step) about the total number of images and the number of images duplicated. The directory is located in the following path: UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx vault_name is the name of the vault used for the session and xxx is the unique session identifier that Vault assigns to each vault session.

list detail. In the right pane.list image. Select Master Server under Host Properties. Summary of images to be duplicated if Duplication step is configured. To set the length of time to keep working files 1 2 3 4 5 In the NetBackup Administration Console. set the length of time after which to delete the Vault working files. select Host Properties. generated by the -L option of the bpduplicate command.log summary. Select Clean-up. session directories are created in the same vault\sessions\vault_name directory for two or more vaults that have names that differ only in case. therefore. preview. the entire sidxxx directory is deleted.log. The following table describes the session logs. Summary of each action performed for a Vault session. If e-mail notification is enabled. data in this log file is appended. Brief description of the Vault session and its results. In the Delete vault logs field.nn Vault session log files Purpose Progress information for duplication operations. Lists all images and partial images for a session. Table 9-38 Name duplicate. We suggest that you keep . if Eject step is configured and Duplication step is not. When the set time has elapsed.log Setting the duration of Vault session files Vault’s session files are stored in the following directory: UNIX: /usr/openv/netbackup/vault/sessions Windows: install_path\NetBackup\vault\sessions You can configure the length of time NetBackup retains these files by using the NetBackup Administration Console. right-click the master server and choose Properties. You should plan to retain each sidxxx directory at least as long as the period of time over which you plan to span consolidated ejects.Administering Vault Vault session log files 223 Note: Directory names are not case sensitive on Microsoft Windows systems. or ejected.

a regular backup of the file system will save only the file pointer information. Vault will be unable to eject tapes or generate reports from that session. field on the Duplication tab applies only to the Duplication step. The scope of the source volume group The Source Volume Group on the Choose Backups tab spans all steps of a Vault profile (most notably Duplication and Eject). For more information about image selection. Vaulting Storage migrator files Files migrated by Storage Migrator are moved to secondary storage. Consequently. General operational issues General operational issues describe issues that you should be aware of when configuring and using Vault. see “The list of images to be vaulted” on page 138. However. If Vault duplicates those files. .. if you do not duplicate images. see “Vaulting VSM media” on page 163. an image that has no disk copy will not be duplicated even if a copy of that image exists on removable media and was selected during the Choose Backups step. and a pointer to each file remains in the file system. images may still be ejected if they are in the Source Volume Group and in an off-site volume pool specified on the profile Eject tab. Even if no images are selected for duplication. To vault VSM media. you should also vault a copy of the Storage Migrator media. the Source of Backups. Conversely. If the sidxxx directory has been deleted. Disk only source of backups If Disk Only is specified on the Duplication tab. you do not have to specify a source volume group (the Source Volume Group field is ignored). To ensure that the actual file is vaulted.224 Administering Vault General operational issues these directories at least a week longer than the consolidation span. only the file pointer information is vaulted..

Chapter 10 Using the menu user interfaces Vault also includes the following two menu user interfaces (MUIs) that you can use in a terminal window: ■ The Vault Administration interface. You can perform the same actions in the Vault Administration menu as in the NetBackup Administration Console. You must have root privileges to run the vltadm command. You can use the Vault Administration interface from any character-based terminal (or terminal emulation window) that has a termcap or terminfo definition. The Vault Operator Menu interface. It provides the same functionality as Vault Management in the NetBackup Administration Console. . which lets you configure Vault. Use the vltadm command to start the Vault Administration interface. which provides a way to eject media and print reports for one or more Vault sessions. and run the vltadm command only from the UNIX system on which the NetBackup master server resides. The Vault Administration interface lets you configure and run Vault from a text-based menu. ■ This chapter covers the following topics: ■ ■ ■ ■ Using the Vault administration interface Using the Vault operator menu interface Changes in vmadm for Vault Changes in bpdbjobs for Vault Using the Vault administration interface UNIX and Linux systems only.

.. select the help option on that menu. or p.. or profiles already configured in Vault. The vltopmenu command. Copy selected profile.. the following menu appears in the terminal window: Vault Administration -------------------Robot Name: <none> Vault Name: <none> Profile Name: <none> r) v) p) n) t) f) c) s) Browse all configured robots Browse all configured vaults for selected robot Browse all configured profiles for selected vault Robot management.. Start session for selected profile. vaults. Profiles for selected vault.... which starts the Vault Operator Menu. The criteria you can configure in the Vault Administration interface are described in “Configuring Vault” on page 71. Help includes a tutorial for learning and using the Vault Administration interface. or profile is displayed. or profile names at the top of the menu will change. v. type the letter of the action you want to perform. vault. When the correct robot. resides in the following directory: UNIX: /usr/openv/netbackup/bin Windows: install_path\NetBackup\bin . h) Help q) Quit ENTER CHOICE: To browse through specific robots. a) Vault properties. press r.. the robot. Vaults for selected robot.. vault. The vltadm command resides in the following directory: /usr/openv/netbackup/bin When you invoke the vltadm command..226 Using the menu user interfaces Using the Vault operator menu interface The vltadm command and interface is available on UNIX systems only. For help on the currently displayed menu.. Using the Vault operator menu interface The Vault Operator Menu interface lets an authorized user eject and inject tapes and print reports for one or more Vault sessions (an authorized user is one who can invoke the vltopmenu command).

.Print command: /usr/ucb/lpr Email: Directory: p) Select Profile Destinations. q) Quit Selection--> Upon startup. .Using the menu user interfaces Changes in vmadm for Vault 227 When you invoke the vltopmenu command. You can modify these fields by using the Special Actions menu in vmadm. several fields are added to the Volume Configuration display. The vltopmenu command writes messages about its operations to the log file for Vault commands: ■ ■ UNIX: /usr/openv/netbackup/logs/vault/log. see the NetBackup Vault Operator’s Guide. the menu displays the current profile. When Vault is installed.mmddyy Windows: install_path\NetBackup\logs\vault\mmddyy. and inventories robots controlled by the Media Manager volume daemon (vmd). the following menu appears in the terminal window: NetBackup Vault Operator Menu Current Profile: None Current Session: 0 Current Report Destinations . vmadm.. u) Profile Up d) Profile Down s) Select Session m) Modify the Report r) Run Reports for This Session v) Run Individual Reports.log For more information about the Vault Operator Menu interface.. and report destinations. manages volumes. session.. The vmadm utility has a character-based user interface and can be used from any terminal. cr) Consolidate All Reports i) Inject Media into Robot ce) Consolidate All Ejects e) Eject Media for This Session re) Consolidate All Reports and Ejects c) Container Management. manages volume pools. You must have root privileges to execute this utility. manages barcode rules. Changes in vmadm for Vault The command line media management utility...

This field is used by Vault to determine where the volume is located when it is at an off-site location. You will be prompted for the media IDs for which you want this vault name applied. or change the date a volume is sent to the off-site vault.228 Using the menu user interfaces Changes in vmadm for Vault Additions to volume configuration When you display the full Volume Configuration. Click the ESC key to cancel the action. This field is used by Vault to record when a volume was sent to the off-site vault location. Vault specific information is displayed. Enter a hyphen (-) to clear the field. clear. The prompt will repeat until you press the Enter key without entering a media ID. To modify the name of the vault 1 2 3 4 5 On the main menu. clear. Enter the new vault name (25 character maximum). Choose n for Change Vault Name for Volumes. or change the name of the vault in which the volume resides. You can modify this date for a single volume or for multiple volumes. The following is an example of the Vault specific information: volume group: TL8-0 vault name: V1 vault sent date: Wed Dec 02 09:34:01 2000 vault return date: Tue Feb 17 09:34:01 2001 vault slot: 546 vault session ID: 37 created: Mon Nov 29 08:29:03 2000 Changes to the special actions menu You can modify several Vault options by using the Special Actions > Change Vault Parameters for Volumes menu in vmadm: Vault Volume Parameters ----------------------n) Change Vault Name for Volumes d) Change Date Volumes are sent to Vault r) Change Date Volumes return from Vault s) Change Vault Slot for Volumes i) Change Vault Session ID for Volumes Change Vault name for volumes You can set. . choose s for Special Actions. Choose a for Change Vault Parameters for Volumes. Change date volumes are sent to Vault You can set.

or change the date a volume returns from the off-site vault. clear. Choose s for Change Vault Slot for Volumes. Change date volumes return from Vault You can set. choose s for Special Actions. Enter the new date the volume is requested to return from the off-site vault. To modify the slot ID for a volume 1 2 3 On the main menu. Enter a zero (0) to clear the field. Choose a for Change Vault Parameters for Volumes. Change Vault slot for volumes You can set.Using the menu user interfaces Changes in vmadm for Vault 229 To modify the Vault sent date of the vault 1 2 3 4 5 On the main menu. You can modify this date for a single volume or for multiple volumes. Press the ESC key to cancel the action. To modify the Vault return date of the vault 1 2 3 4 5 On the main menu. clear. choose s for Special Actions. Choose d for Change Date Volumes are Sent to Vault. Press the ESC key to cancel the action. choose s for Special Actions. You will be prompted for the return dates on which the volumes should be recalled from off-site storage. Choose a for Change Vault Parameters for Volumes. . The prompt will repeat until you press the Enter key without entering a return date. You can modify the slot for a single volume or for multiple volumes. Choose a for Change Vault Parameters for Volumes. Enter the new date the volume was sent off-site. Enter a zero (0) to clear the field. You will be prompted for the date on which the volumes were sent to off-site storage.The prompt will repeat until you press the Enter key without entering a date. This field is used by Vault to record when a volume is requested to return from the off-site vault location. This field is used by Vault to determine in what slot the volume is located in the off-site vault. Choose r for Change Date Volumes Return from Vault. or change the slot that the volume is contained in at the off-site location.

This field is used by Vault to determine in what vault session a volume was processed. Change Vault session ID for volumes You can set. Changes to display options By default. Press the ESC key to cancel the action. or change the session ID in which a volume was processed. You will be prompted for the slot IDs to assign to the volumes. The prompt will repeat until you press the Enter key without entering a slot ID. Enter the new session ID for the volume. To modify the session ID for a volume 1 2 3 4 5 On the main menu. clear. choose s for Special Actions. Press the ESC key to cancel the action. Choose f for Filter. Enter the container ID or a dash (-) to clear the container ID field and not filter on a container ID.230 Using the menu user interfaces Changes in vmadm for Vault 4 5 Enter the new vault slot ID for the volume. You can modify the session ID for a single volume or for multiple volumes. Choose 8 for VAULT CONTAINER ID. . Enter a zero (0) to clear the field. To display information about volumes in a container 1 2 3 4 On the main menu. Enter a zero (0) to clear the field. You will be prompted for the session IDs to assign to the volumes. Choose a for Change Vault Parameters for Volumes. You can set a filter option to limit the display to the volumes in a specific container. The prompt will repeat until you press the Enter key without entering a session ID. choose p for Print Information about Volumes. Choose i for Change Vault Session ID for Volumes. information about all configured volumes is displayed in vmadm.

Using the menu user interfaces Changes in bpdbjobs for Vault 231 Changes in bpdbjobs for Vault The NetBackup activity monitor utility. bpdbjobs. The name of the vault under which the session is running. a unique numeric value. displays Vault jobs by default. for the vault job. If the profile is configured for deferred eject. The session ID. the field contains one of the following values. . If you invoke the bpdbjobs command and use the -vault option. Table 10-39 Field Robot Vault Profile Session ID Vault fields in bpdbjobs output Description The name of the robot with which the vault is associated. For Vault jobs. The name of the profile that holds the configuration information for the vault session. These values progress from the first value to the last as the Vault job progresses: ■ ■ ■ ■ ■ ■ Tapes to Eject Operation Choosing Images Duplicating Images Choosing Media Catalog Backup Eject and Report Done If a Vault job completes successfully (with exit status = 0). The value is incremented by 1 every time a new vault job runs. the Operation field contains the operation occurring at the time the job failed. If a vault job fails. the State field and the Operation field both contain the value Done. The number of tapes to be ejected for a vault session. the tapes may not be ejected yet. the output includes the following Vault specific fields. Session ID assignment starts at 1 the first time a vault job is run after vault has been installed.

232 Using the menu user interfaces Changes in bpdbjobs for Vault .

If you experience such a problem. In some rare cases with Microsoft Windows. the print command will work correctly when tested from a command prompt but will not work when configured on the profile Reports tab. from a command prompt on the master server on which Vault is installed enter the following command (use the appropriate server and printer names): . The issue may be with how Windows calls the print command. see the following: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ “Printing problems” on page 233 “Errors returned by the Vault session” on page 234 “No media are ejected” on page 234 “Media is missing in robot” on page 234 “Bad or missing duplicate tape” on page 235 “Tape drive or robot offline” on page 236 “No duplicate progress message” on page 236 “Ejecting tapes while in use” on page 237 “Tapes not removed from the MAP” on page 238 “Unexpired tapes were injected into the robot” on page 238 “Debug logs” on page 238 Printing problems Problems with printing reports that appear to be Vault problems often are problems with the print command configured on the profile Reports tab. Therefore.Chapter 11 Troubleshooting For information about specific problems or areas that can cause problems. you should test print commands from a command line on the server on which Vault is installed to ensure that they work correctly.

To compare the tapes actually stored in the robot with the Media Manager database. If the tape is not found. ■ If the error generated by the Vault session is less than or equal to 255. Error codes less than or equal to 255 (except 252) map to standard NetBackup error codes and are documented in the NetBackup Troubleshooting Guide. you should delete it from the NetBackup system. it will return error code 252 and the actual error code will be written to stderr. No media are ejected If no media are ejected. it may be because of the following: ■ All images have already been vaulted. a tape may have been moved to the off-site volume group inadvertently even though it remains in the robot. ■ The format of the error text written to stderr is: EXIT status = error code For detailed information on status codes. it will return the actual error code. so no images were selected. This is because codes greater than 255 are called NetBackup Extended Error Codes and are not supported by all operating systems. ■ Media is missing in robot Duplication may fail if NetBackup does not know that a requested piece of media is in the robot. you will need to . If the tape is missing yet is assigned and has valid duplicate images. For example. Vault determines that a backup image has already been vaulted if a copy of the image already is on a volume in an off-site volume group. see the NetBackup Troubleshooting Guide for UNIX and Windows. If the tape is in the robot. The media to be vaulted are in a volume group other than the robotic volume group specified for the vault to which the profile belongs. use the NetBackup Administration Console to move the tape to the robotic volume group. Errors returned by the Vault session Every Vault session writes a detailed error status to stderr. use the NetBackup Administration Console Inventory Robot option. If the Vault session fails with an error code greater than 255.234 Troubleshooting Errors returned by the Vault session NET USE lpt1 \\servername\printername PERSISTENT:YES This problem can also occur in mixed environments of UNIX and Windows.

To reduplicate images 1 Determine which images were on the tape by running the bpimmedia command. . Expire the lost or damaged duplicate tapes by using the bpexpdate command. For more information. Bad or missing duplicate tape If a duplicate tape is lost or damaged. Before duplicating images. Create a profile that has the same criteria as the profile that created the missing duplicate tape except for the following: ■ 2 3 4 Specify policy names only for the policy names used to create the images on the missing tape. The bpimmedia command scans the entire NetBackup image catalog. see “Previewing a Vault session” on page 135. Determine when the images were created by using the bpimagelist command. Ensure that no other Vault sessions are running before running this new profile. Set the time window so the profile selects the images on the missing tape. which is documented in the NetBackup Administrator’s Guide. you can reduplicate the images that were on the tape if the primary backup images still reside in the robot. set the time window between 32 and 28 days ago. For example. you can verify that the correct images are selected by previewing the session. if the original backups were made 30 days ago. Save the output because you will need to verify that the correct images were reduplicated. ■ 5 Run the profile by selecting it in the Administration Console and then selecting Actions > Start Session. to expire the images before you delete the tape from Media Manager. so it may take a few minutes depending on the size of that catalog.Troubleshooting Bad or missing duplicate tape 235 use the command bpexpdate.

Sometimes this delay is caused by a media mount (which normally does not . 2 for the second. you should try to configure the drives in an UP state or reset the drive. examine the system logs (for example. this message is displayed only for informational purposes.log. If the number is relatively small. several gigabytes).n Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx\duplicate. and so on). You can also use the robotic test utilities (such as robtest) to further debug the problem.exe -L -backupid server2_0897273363 The output of this command will show you various statistics about this backup image. the Vault process has not received any new information from the bpduplicate process within the time frame specified (in this example. there may be a problem with the duplication process. Then execute the bpimagelist command and specify the image ID. you can determine the size of the current image. If the image that is currently being duplicated is very large (for example. including the number of kilobytes written during this backup. If drives persistently go offline. there may be a problem with the robotics control. TLD. and n is the number of the instance of the bpduplicate command (1 for the first instance. 30 minutes): bpduplicate_progress_logname: no activity in 30 minutes bpduplicate_progress_logname is the progress log that bpduplicate creates as it runs the duplication for Vault. /var/adm/messages on UNIX systems) for error messages. ACS. This message does not necessarily indicate an error has occurred. No duplicate progress message If you see a message similar to the following in the Vault detail. xxx is the unique session ID.log. To determine if a problem exists. but they will be converted to AVR control if a problem occurs with the robot. and so on). Also. This file resides in the following directory: UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx/duplicate. All drives should be listed as robotically controlled (that is. duplication may hang.log. as in the following example: UNIX: bpimagelist -L -backupid server2_0897273363 Windows: bpimagelist.236 Troubleshooting Tape drive or robot offline Tape drive or robot offline If you have a problem with ACSLS drives going offline. if the tape drives are listed as AVR control in the Administration Console Media and Device Management node. To diagnose the problem.n The vault_name is the name of the vault used for the session. First examine the last few lines of the details.log file to determine backup image ID.

This command sends a SIGUSR2 signal to the main duplication process. However. A similar error may be generated by non-Media Manager controlled robots if a piece of media is currently in use. You may receive additional error messages because the rest of the media for the scheduled job has already been ejected. the bpvault. then this message should be regarded as informational. do not kill the bpduplicate processes. an error message will be generated by Media Manager. by hardware problems. To end a bpvault process immediately. The failure of the bptm/bpduplicate will mean these images will be duplicated on the next attempt if the number of duplicate_days is not exceeded. it is possible that a piece of media could be in use during the eject process (for example. Ejecting tapes while in use If Vault is configured to eject original media. For more information about this command. or by the media being in use. . Need to Stop Bpvault To stop a bpvault duplication process. This signal is automatically propagated to the other bpvault duplication instances without waiting for any current duplication job instance to finish. rather than wait a number of minutes for the current bpduplicate processes to complete.all script will continue to complete processing of the other bpvault commands. refer to the NetBackup Commands manual. you must first run the -haltdups command and then manually kill the bptm jobs on each server. If the backup image is very large. The current duplication will complete and no more duplication instances will run. we recommend that you use the Vault Operator Menu (vltopmenu) to re-eject the media after the media is no longer in use. which is the primary vault job that is currently in the duplication process. If you receive one of these errors. you can use the vltrun -haltdups command from the command line interface. Examine the Activity Monitor to determine if there are any hardware problems and also check the system logs.Troubleshooting Need to Stop Bpvault 237 occur in robotic devices during duplication). The errors received by bpvault will be logged and these images will not be successfully duplicated. for a restore or a media verify procedure. However.) In this case.

as follows: a b c 2 In the NetBackup Administration Console. Unexpired tapes were injected into the robot If Vault tapes that have not expired have been injected back into a robot.. Select the media ID(s) you want to eject. Transfer the media to the off-site volume group by doing the following: a b c Select the media ID(s). If this occurs. Select Actions > Change Volume Group. select the robot into which the media was injected (Media and Device Management > Robots). you can use the vmchange command to eject the media and transfer it to the off-site volume group. Choose the appropriate off-site volume group from the New Volume Group Name drop down menu.238 Troubleshooting Tapes not removed from the MAP Tapes not removed from the MAP If media is not removed from the robot’s media access port (MAP) and a timeout condition occurs. the job is failed with status code 338 (vault eject timed out). You must first create the vault directories so that daily log files are generated. 3 4 Return the media to your vault vendor so that all backups on that media will be available for future disaster recovery. Select the Eject Volumes from Robot. Alternatively. you should use the Vault Operator Menu (vltopmenu) or the vlteject command to eject the media that was not removed from the library and generate the reports.. Debug logs Vault writes debug logs in the standard NetBackup debug logging path as follows: ■ Vault commands write messages in log files in a vault directory. you can revault them manually by doing the following: 1 Eject the media. Run the Recovery report to ensure that the media is available for future disaster recovery operations. the Vault reports will not accurately reflect the status of the media.. To recover. operation on the Actions menu. if the .

exe and bpdown. vault. expand NetBackup Management. On Windows systems. Vault logging level.) All unified logs are written to the following locations: UNIX: /usr/openv/logs Windows: install_path\NetBackup\logs The originator ID (OID) for NetBackup Vault is 166. (Unified logging creates log file names and messages in a standardized format. the log files will not be created. not just the Vault debug logs. In the right pane. on UNIX systems. use netbackup start and netbackup stop to start and stop NetBackup and Vault daemons. select the master server and then Actions > Properties.exe commands to start and stop the NetBackup services. The log files are in the following vault directories: UNIX: /usr/openv/netbackup/logs/vault/log. The NetBackup Vault Manager must be running at all times so Vault will function correctly. Expand Host Properties. . Select Clean-up. Select Master Server.mmddyy Windows: install_path\NetBackup\logs\vault\mmddyy.Troubleshooting Debug logs 239 directories do not exist. use the bpup. You can set the debug level to 5 for all Vault sessions or you can use the -verbose option on the vltrun command in the Vault policy that invokes the Vault job. Setting the duration and level of logs The amount of information logged and how long it is retained is controlled by two NetBackup configuration parameters. including the NetBackup Vault Manager. and profile configuration information.log ■ The NetBackup Vault Manager (nbvault) writes messages in Veritas unified log (VxUL) files. ■ The length of time NetBackup retains debug logs. This setting affect all debug log files generated by NetBackup. Refer to the "Using Logs and Reports" chapter of the NetBackup Troubleshooting Guide for more information on unified logging The NetBackup Vault Manager (nbvault) manages Vault activity and arbitrates access to the Vault robot. Symantec recommends that you use a debug level of 5 when you generate logs that you send to Symantec for troubleshooting purposes. ■ To set the duration and level for log files 1 2 3 4 5 In the NetBackup Administration Console.

conf entry VAULT_VERBOSE = level on UNIX systems. In most circumstances. This setting applies to all NetBackup logs. In the NetBackup Administration Console for Windows.240 Troubleshooting Debug logs 6 Enter the length of time to retain the NetBackup log files. If you use the vlteject command or the Vault Operator Menu (vltopmenu) to perform consolidated ejects and reports. the field name is Duration to Retain Logs. NetBackup tape manager nbvault (on the master server). . NetBackup backup scheduler bptm (on the media server).mstr For more information about the NetBackup debug logs. Vault Manager service/daemon vault (on the master server). In the NetBackup Administration Console for UNIX. and you should include the appropriate session log files with problem reports you send to Symantec. Select the Logging tab. Vault commands Session log files also are useful for troubleshooting problems. administrative commands process bpbrmvlt (on the master server). Select the Vault Logging Level.mstr Windows: install_path\NetBackup\vault\sessions\vlteject. the field name is Keep Logs For. NetBackup client daemon manager bpsched (on the master server). The logging level corresponds to the bp. including but not limited to. 7 8 Logs to accompany problem reports To troubleshoot problems. Vault job scheduler (similar to bpbrm) bpcd (on the master server). you will have to provide log files from the following NetBackup processes: ■ ■ ■ ■ ■ ■ ■ admin (on the master server). see the NetBackup Troubleshooting Guide for UNIX and Windows. the Vault logs. the following log file may also be useful: UNIX: /usr/openv/netbackup/vault/sessions/vlteject. Symantec Customer Service requires a set of log files produced by NetBackup and Vault.

backup protects against data loss from complete system failure. If . It also provides general information about preparing for a disaster recovery situation. especially a strategy that is expected to assist in disaster recovery. the data must be tracked to know at what point in time it was backed up. using NetBackup and Vault. which allows your organization to assess the information that cannot be recovered. Regardless of any other recovery provisions. For more information. see the “Disaster Recovery” section in the NetBackup Troubleshooting Guide.Appendix A Recovering from disasters This section provides information about recovering data. when you have to recall your media from your off-site storage location. see the following: ■ ■ ■ ■ ■ ■ “Introduction” on page 241 “Disaster recovery in the NetBackup Vault context” on page 245 “Preparing for recovery” on page 246 “Recovering NetBackup” on page 248 “Recovering data” on page 248 “Recovering to a specific point in time” on page 250 For information about recovering the NetBackup application. Introduction Data backup is essential to any data protection strategy. And off-site storage of backup images protects against damage to your on-site media or against a disaster that damages or destroys your facility or site. Your data backup schedules should be configured to allow your organization to achieve its recovery point objective (RPO). To perform recovery successfully. Regularly backing up data and then being able to restore that data within a specified time frame are important components of recovery. which is the point in time before which you cannot accept lost data.

Human disasters are caused by people. and so on. availability. network or telecommunication failures. Usually. power failures. Technological disasters include computer or Internet crimes. earthquakes. High availability technologies can make the recovery point very close or even identical to the point of failure or disaster. a disaster is an unplanned event that interrupts its ability to function. By planning and preparing for a disastrous event. computer viruses. You may have multiple RTOs. terrorist activities. and accessibility of your IT infrastructures. Definition of disaster For an organization.242 Introduction your organization can accept one day’s data loss. which is the expected recovery time or how long it will take to recover. Recovery time is a function of the type of disaster and of the methods used for recovery. depending on which services your organization must recover and when. Your organization also may have a recovery time objective (RTO). including accidents. the event affects the delivery of critical business functions and results in a loss of data. Understanding disaster recovery planning allows you to place Vault and tape-based backups stored off-site in the proper context within your disaster recovery objectives. and they also can provide very short recovery times. hardware or software failures. you can minimize the effect of the disaster. Although a disaster is an event that is beyond your control. floods. and so on. tornadoes. The following are generally recognized as the types of disasters possible: ■ Technological disasters result in shortcomings in performance. you can control the way in which your organization reacts to a disaster. explosions. the more expensive it becomes to build and maintain the systems required to achieve recovery. capacity. including hurricanes. Disaster recovery usually is focused on . your backup schedule should be at least daily so you can achieve an RPO of one day before any disaster. and so on. riots. ■ ■ The impact of a disaster often depends on the scale and timing of the event. Natural disasters are caused by nature. Definition of disaster recovery Disaster recovery is the process of responding to an interruption in the services your organization uses to operate. Your analysis of the costs and benefits of various recovery strategies should be part of your organization’s recovery planning. However. fires. the closer to the failure that you place your RTO and RPO.

For example. Although disaster recovery usually has been used to describe information technology and telecommunication services recovery. often at an alternative site and using one or more data-recovery methods. network. such as telephones. Therefore. function. office space. and so on. The longer your organization can operate without a function. A resilient organization will use business continuity planning to help ensure that it can survive a disaster and resume operations at an acceptable level. it may be acceptable to operate at a reduced level for a specific period of time. only those functions required for immediate operation need to be . You may choose to recover only the most critical business functions immediately and then recover other functions later. the easier and less expensive it becomes to recover that function. Definition of disaster recovery plan A disaster recovery plan is a plan to resume or recover a specific essential operation. help resume normal business operations. which is restoring the actual capability for employees to perform their jobs. an organization’s people also are subject to the effects of a disaster and planning should include the impact on them and the resources necessary to help them recover so they can perform their duties. other services an organization uses to conduct operations can and should be considered part of a plan. Although all functions of an organization should be valuable and necessary for the organization to operate. given the higher cost of rapid recovery. By planning how your company will respond in the event of a disaster.243 Introduction information. Disaster recovery is part of a larger topic called business recovery. and so on. and telecommunication services. Business recovery includes logistic related items. or process of an organization. which includes plans to manage the crisis to your organization. Business recovery itself is part of a larger topic called business continuity planning. you ensure that your company can: ■ ■ ■ ■ Protect critical data Minimize the impact of a disaster Use resources most effectively Maintain business continuity Recovery priorities Your organization must decide between recovery cost (the infrastructure and testing) and the level of functionality that must be recovered. living arrangements for employees.

fires. Delaying recovery of some functions can be a good business decision. Individual disaster-specific plans are easier to create than a general plan. Two approaches can be used to create disaster recovery plans: ■ A general plan that is used any time a disaster occurs.244 Introduction recovered quickly. based on the impact to your organization rather than the type of disaster). you can reduce your organization’s exposure to risks and ensure that your critical systems and networks are available during disruptions. because it may require that some decisions be made at the time of disaster (such as assessing the type of impact and determining the response). However. For example. network outages. The following are examples of objectives that may be in a disaster recovery plan: ■ ■ ■ ■ ■ ■ ■ Ensure service to customers by making critical resources available Minimize economic loss Secure company assets Minimize decision making during the recovery process Reduce reliance on key individuals Ensure a safe and orderly recovery within predetermined time period Maintain a sense of security and organizational stability The priority you assign your objectives depends on the needs of your organization. A general plan is easy to maintain and convenient. and so on. It is often clear which plan should be used. so fewer decisions are required at the beginning of recovery. Multiple smaller plans. each used for a specific disaster that your organization has determined is most likely to occur. Understanding the impact of disaster will help you identify the objectives for the recovery plan. A general plan should be flexible and is often impact driven rather than disaster driven (that is. floods. individual plans often are created for power outages. By setting clear. Developing a disaster recovery plan Developing a disaster recovery plan usually begins with an impact analysis that identifies the functions an organization requires to operate and determines how long each function can be unavailable until it affects the organization to an unacceptable extent. which can result in quicker recovery. A general plan usually is based on assumptions that define the scope of each impact in the plan. if ■ . the beginning of recovery may be delayed. prioritized objectives for your disaster recovery plan. however. which plan to use may not always be clear (for example.

. it should be simple. Or testing can be as complex as actually conducting operations at a recovery site to ensure that everything works correctly. The goal of disaster recovery testing is not to pass but to find out what does not work. understands how it works. Disaster recovery in the NetBackup Vault context In the NetBackup Vault context. If you use NetBackup and Vault to backup your applications and store removable media at a secure off-site location. and clients) and then restoring the data that is stored at the off-site storage facility. during which everyone involved in the recovery process discusses their roles in a moderated recovery scenario. which helps verify that everyone can be reached when needed. thoroughly. and frequently (frequently depends on any changes in your organization’s functions and environment). disaster recovery means restoring the NetBackup application (master server. A disaster recovery plan should be easy to follow and not require interpretation. Between those extremes. If the plan is implemented. media servers. therefore. Your tests should be designed to find problems because it is better to find them during a test than during an actual recovery situation. and simulations that invoke the recovery plan but use simulated data. and understands the reasoning behind the decisions in the plan. Testing can be as simple as calling all of the phone numbers in an emergency notification list. You should publicize your disaster recovery plan within your organization so that everyone knows about it.245 Disaster recovery in the NetBackup Vault context a fire causes a power outage). Do not include unnecessary detail. recovery may be slow to begin and difficult to achieve. Testing a disaster recovery plan Developing a disaster recovery plan is a waste of time and resources if it is not tested regularly. you also can perform application recovery so you do not have to reinstall your applications. and well tested. and if a disaster occurs for which a plan does not exist. Perhaps using a combination of testing scenarios to test specific parts of the plan also can be effective. specific. variations include walkthroughs. it will be in a time of high stress and pressure to perform.

and you may have to do more than what is listed: ■ ■ ■ Develop a disaster recovery plan. you may not have to do some of the items listed. You should back up all data that your organization’s impact analysis determines is critical and store copies at a secure. Your preparations for disaster and what you have to accomplish during a recovery depends on your recovery systems. the Windows system directories include the registry. it is important to select the correct files to back up. For Microsoft Windows systems. Symantec provides general disaster recovery information that is intended as a model only. Back up and vault data regularly. if your recovery site and systems are already operational and have NetBackup and Vault installed. off-site storage location. Restoring operating system files is not helpful if you are recovering data to a different system at your original or disaster recovery site. If you are using a NetBackup exclude list for a client. without which it is impossible to restore a system to its original configuration. In addition to backing up files on a regular basis. You . you must evaluate the information and then develop your own disaster recovery plans and procedures. Conversely. you have to prepare for that and accomplish it during recovery. do not specify any Windows system files in that list. Recovering data can be a difficult and time consuming process. back up and vault the applications that your organization’s impact analysis determines are critical. If you can recover to the same or identical hardware. Test the disaster recovery plan. For example. You also should back up system files so you can quickly restore a system to normal operation: ■ ■ Include all operating system files in your backups. The success of recovery often depends on how well you prepare for disaster.246 Preparing for recovery Preparing for recovery Note: Effective disaster recovery procedures are specific to an environment and provide detailed information about everything that should be accomplished to prepare for disaster and to recover after disaster occurs. You should do the following to prepare for recovery using NetBackup and Vault. if your recovery systems do not have NetBackup and Vault installed and configured. you do not have to protect the NetBackup installation media and the license keys and install NetBackup during the recovery process — you only have to recover the NetBackup catalogs and data.

restoring from a backup eliminates the need to reapply them. e-mail the Recovery Report to that site. You need the media so you can install NetBackup and Vault on the recovery system if it is not already installed. Your vault vendor may allow you to vault your Recovery Report. but then not restore them if you are recovering to a different system or site. Alternatively. Record and protect the names of the policies that are used to backup the data you want to recover. If you have a recovery site equipped with computers. but backing up critical applications ensures that you can restore them to their exact configurations. reducing recovery time. so you need to know which policies are used so you can identify the media you need to recover. Protect the NetBackup and Vault installation media. if you have applied software updates or patches. store the Recovery Report securely. You can use temporary license keys if necessary. you can obtain the off-site volume group names after you restore the NetBackup catalog (because the catalog includes the Vault configuration). Record and protect the license keys for NetBackup and Vault. Protect the installation media and record the license keys for any other Symantec products that must be installed on the recovery systems. Those names are used during the recovery process. ■ Every time you vault media. For example. ■ Back up executable and other files for applications you need to conduct critical operations. You need them for NetBackup and Vault on the recovery system if you have to install NetBackup. Document the commands and options that you need to recover data. You may want to save money by using fewer tape volumes. ■ ■ ■ ■ ■ ■ . You will need the Recovery Report to identify the media you need to recall from off-site storage. For example. So you should have a record of the commands and options that you need during the recovery process. you will need their license keys when you install those products.247 Preparing for recovery can back up those files. if you use the Veritas File System™ and Veritas Volume Manager™ on the recovery systems. For example. The Recovery Report is organized by policy. The same disaster that destroys your site can destroy your Recovery Report. the bpchangeprimary command is used to promote the vaulted images to primary images so that you can restore from them. Record and protect the names of the off-site volume groups for the data you want to recover.

Therefore. Symantec provides general disaster recovery information that is intended as a model only. Recovering data can be a difficult and time consuming process. and the configuration of NetBackup on the recovery systems. your original NetBackup configuration. these procedures are intended as general guidelines from which you can create . The steps you have to perform to recover can depend on the configuration of your original system and robotic devices. the configuration of your recovery system and robots. ■ Recovering NetBackup Information about recovering NetBackup master servers. in which case the device configuration will be restored if you recover the NetBackup catalogs). Your vault vendor may allow you to vault a copy of the DR plan. rather. You can then use an appropriate procedure in the NetBackup Troubleshooting Guide. you may have to configure robots and drives (unless you re-install NetBackup on the original system. You must first ensure that your computer and robotic hardware and any necessary network equipment is operational before you re-install NetBackup. The success of recovery often depends on how well you prepare for disaster and subsequent recovery. You should have copies stored so that they will be available when needed. and client systems after a disk failure is provided in the “Disaster Recovery” section of the NetBackup Troubleshooting Guide. media servers. Protect your DR plan. providing specific disaster recovery procedures for all situations is not possible. you must evaluate the information and then develop your own disaster recovery plans and procedures. The same disaster that destroys your site can destroy your DR plan and recovery report. After you re-install NetBackup. The procedures include re-installing NetBackup and may include re-installing the operating system if it is required. Recovering data Note: Effective disaster recovery procedures are specific to an environment and provide detailed information about everything that should be accomplished to prepare for disaster and to recover after disaster occurs.248 Recovering NetBackup ■ Protect the installation media for the operating system and other applications required to run the systems you are using for recovery.

By default. ■ ■ ■ ■ To recall media and restore backup images 1 Using the Recovery Report. The NetBackup master and media server software. so you should determine which policies were used to back up the data you want to recover. You know the name of the off-site volume group name to which the recovered images belong. If the recovery system has a different device configuration than the original system. Recover the catalog using one of the procedures in the “Recover the Catalog from an Online. You know the names of the original master and media servers. change the server names in the NetBackup catalogs by using the bpimage command. Although some detail is included about restoring the NetBackup catalogs to a recovery system. perform device discovery in NetBackup. The NetBackup catalogs and data media have not been recalled from off-site storage. If necessary. and devices are installed and robots and drives are configured on systems to which you are recovering data. Information in this section assumes the following: ■ ■ The primary backup images are unavailable. The Recovery Report is available. Vault software. The Recovery Report is organized by policy. NetBackup catalog backups include the NetBackup device configuration information. these procedures do not provide detail about every step of the recovery procedure. Recall the appropriate catalog backup and data media from off site storage. If the master and media server names on the recovery system are different than the original system. Hot Backup” section of the NetBackup Troubleshooting Guide. client software.249 Recovering data your own procedures for recovering NetBackup and the data that was transferred off-site. The bpimage command and options required are as follows: bpimage -newserver recovery_system -oldserver original_system 2 3 4 5 . identify the current catalog backup media and the media required to restore the data. the device configuration from the original system will overwrite the device configuration when the catalog is recovered.

and Restore interface or from the bprestore command. For procedures. Note: After you add the copy number to the file. see “Restoring from a specific backup copy” in the Backup. For procedures.250 Recovering to a specific point in time You can also use the bpimage command if the old system had separate media servers and the recovery system has a combined master and media server. suspend the media. Use the bpmedia command to suspend the media. Inject the media into the robot. see the NetBackup Backup. 7 If the media is not suspended or frozen. 8 9 10 Using the Backup. Archive. and Restore help. The ALT_RESTORE_COPY_NUMBER file must be in the following directory on the NetBackup master server: UNIX: /usr/openv/netbackup Windows: install_path\VERITAS\NetBackup For more information about alternate copy restore. Injecting the media moves it into the robot and also changes the off-site volume group attribute of the media to robotic volume group so NetBackup knows that the volumes are in the robot and ready for restore operations. restore the data. Archive. and Restore interface. Exception: the bprestore -copy x option and argument override the value in the ALT_RESTORE_COPY_NUMBER file. and Restore Getting Started Guide. all subsequent restore operations restore from that backup copy. The restore can be from the Backup. revault the media. If the NetBackup Administration Console is not running. you can set up a process that will ensure that you can recover both the NetBackup catalog and the data . 6 Specify the backup copy from which to restore by adding the copy number to the file ALT_RESTORE_COPY_NUMBER. Archive. Archive. Suspending the media prevents NetBackup from writing backup images to that media. start it. see “Injecting media” on page 146. see “Revaulting unexpired media” on page 160. Use the name of the combined master/media server for the argument to the -newserver option. Recovering to a specific point in time If your data center or computing environment requires recovery to a specific point in time (not just to the most recent valid backups). 11 After restoring all of the data. For procedures.

Vault a printed copy of the Recovery Report for that specific point in time. maintaining the media IDs in the volume database may not degrade performance much. Use the bpmedia command to freeze the data and catalog volumes that you want to retain. 4 5 . Do not recall the volumes from off-site storage when they expire. This reduces the size of the database and improves performance. 3 4 To recover the catalog and data 1 2 3 Retrieve the appropriate printed Recovery Report from off-site storage. That version of the catalog contains information about the archived volumes and the images on them. see the NetBackup Commands for UNIX or NetBackup Commands for Windows guide. remove the media IDs from the volume database. To change a large number of images to primary. For information about the bpchangeprimary command. Optionally. detailed instructions for accomplishing all the tasks necessary are not included. You will need the Recovery Report from the specific point in time so you can recall and restore the appropriate catalog and data volumes. Freezing the volumes prevents them from becoming unassigned and from appearing on the Picking List for Vault report. Change the images to be recovered to primary (NetBackup restores from the primary image). You should retain the corresponding catalog backups for the same length of time as the corresponding data backups. The following high-level information is intended as an overview of how to archive the catalog and data so you can recover to a specific point in time. Using the Recovery Report. recall the appropriate catalog backup and data volumes from off site storage. you can use bpchangeprimary -group option to specify all images in a specific off-site volume group. Recover the catalog that you recalled from off-site storage.251 Recovering to a specific point in time for that specific time. Use the bpexpdate command to reset the expiration date on the recalled volumes so they will not be expired. To archive the catalog and data 1 2 Use your normal procedures to vault the data and NetBackup catalogs for that data. Depending on the number of volumes. You can use the -policy option to change the expiration date for all media associated with a specific policy.

.252 Recovering to a specific point in time 6 Restore the data. For more information. see “Catalog Archiving” in the NetBackup Administrator’s Guide. The NetBackup Administrator’s Guide. That alternative procedure uses the catarc catalog archive policy to archive old data in the NetBackup catalog. You can then vault the archived catalog data or a copy of the archived catalog data. Volume I. Volume I includes an alternative procedure for archiving the catalog.

Command used to eject media from Vault sessions and run the reports selected in the profile. or File bin/bpbrmvlt bin/nbvault bin/vltadm bin/vltcontainers bin/vlteject . Also included are Vault files that reside in NetBackup directories.Appendix B Vault’s file and directory structure For information about the files and directories created by Vault. The files are either copied into the directories during the installation process or created as Vault sessions run. Table B-1 Files and directories for Vault in UNIX Purpose Process that kicks off vltrun from a scheduled or manual vault policy. The Vault daemon that manges Vault activity. Program. Directory. The paths are specified in relation to the netbackup directory. vltadm requires root (administrator) privileges. Curses-based utility to configure NetBackup Vault and monitor its operations. Command used to add media logically to containers. see the following: ■ ■ “UNIX files and directories” on page 253 “Windows files and directories” on page 257 UNIX files and directories Vault is installed in /usr/openv/netbackup on UNIX systems. The following table describes the files in each of the directories Vault creates and uses on UNIX systems.

In a cluster environment. and consolidate reports and ejects across sessions. Can be manually removed to reduce disk usage if necessary. Script called by the vault session after it starts. The database of information for media vaulted in containers. Process that executes all the NetBackup commands used during a Vault session. Script called by the vault session just before it exits. Program. Contains help files for the Vault Administration (vltadm) interface. the sessions directory must reside on the shared disk.last . print various reports individually or collectively. The main directory for Vault. db/vault/vault. Script called by the vault session just before vault tapes are ejected.254 UNIX files and directories Table B-1 Files and directories for Vault in UNIX (continued) Purpose Command used to inject media into a robot and update the Media Manager database. Subdirectory that contains working session subdirectories.xml help/vltadm /logs/vault vault vault/sessions The vault configuration file. Directory where the Vault commands log messages. It allows the user to eject or inject media. Directory. Script called by the vault session at the end of eject processing. Utility which allows the user to invoke a menu screen containing the various options that an operator of the NetBackup Vault feature can use. Command which allows the user to change the off-site parameters of a given piece of media. vault/sessions/cntrDB vault/sessions/sidxxx vault/sessions/vault_name/session Counter to show current duplication session . A subdirectory that contains working session directories and log files. Contains session directories. or File bin/vltinject bin/vltoffsitemedia bin/vltopmenu bin/vltrun bin/goodies/vlt_ejectlist_notify bin/goodies/vlt_end_notify bin/goodies/vlt_endeject_notify bin/goodies/vlt_start_notify bin/goodies/vlt_starteject_notify Script called by the vault session when the eject process starts.

or File vault/sessions/vault_name/sidxxx/ The All Media Inventory Report. vault/sessions/vault_name/sidxxx/ List of images successfully duplicated during the session.rpt time stamp. If you configure the profile Reports tab to write reports to a folder. Report filenames that include _ff are for debug purposes only.images vault/sessions/vault_name/sidxxx/ Contains output from bpduplicate. vault/sessions/vault_name/sidxxx/ The Distribution List for Vault report.log. vault/sessions/vault_name/sidxxx/ The Detailed Distribution List for Vault report. they are created when reports are generated from the Administration Console. If a report name includes a istlist_robot. Report filenames that include _ff are for debug purposes only. duped. If you configure the profile Reports tab to write reports to a folder. duplicate. the file name of the report will include the session ID. it is part of a consolidated report operation. the file name of the report will include the session ID. the file name of the report in that folder will include the session ID. Program. it is part of a consolidated report operation. If a report name etailed_distlist_vault. the file name of the report will include the session ID.255 UNIX files and directories Table B-1 Files and directories for Vault in UNIX (continued) Purpose Directory.rpt stamp. vault/sessions/vault_name/sidxxx/ The Distribution List for Robot Report. If a report name includes a distlist_vault.nn . If you configure the profile Reports tab to write reports to a folder. it is part of a consolidated report operation. they are created when reports are generated from the Administration Console. they are created when reports are generated from the Administration Console.rpt includes a time stamp. If a report name includes a time allmedia_inventory.rpt stamp. If you configure the profile Reports tab to write reports to a folder. they are created when reports are generated from the Administration Console.rpt time stamp. vault/sessions/vault_name/sidxxx/ The Container Inventory report.log session. it is part of a consolidated report operation. Report filenames that include _ff are for debug purposes only. they are created when reports are generated from the Administration Console. If you configure the profile Reports tab to write reports to a folder. vault/sessions/vault_name/sidxxx/ Shows the output of every command that was executed during the detail. Report filenames that include _ff are for debug purposes only. Report filenames that include _ff are for debug purposes only. If a report name includes a time container_inv. it is part of a consolidated report operation. the file name of the report will include the session ID.

If you configure the profile Reports tab to write reports to a folder.rpt stamp. If you configure the profile Reports tab to write reports to a folder. Report filenames that include _ff are for debug purposes only.rpt part of a consolidated report operation. If a report name includes a time picklist_vault. it is part of a consolidated report operation. vault/sessions/vault_name/sidxxx/ A list of all images that will be considered for duplication or ejection preview. it is lostmedia. eject. the file name of the report will include the session ID.256 UNIX files and directories Table B-1 Files and directories for Vault in UNIX (continued) Purpose Directory.rpt stamp. they are created when reports are generated from the Administration Console. . it is part of a consolidated report operation. Report filenames that include _ff are for debug purposes only. vault/sessions/vault_name/sidxxx/ The Non-vaulted Images Report. vault/sessions/vault_name/sidxxx/ The Picking List for Vault report. Report filenames that include _ff are for debug purposes only. vault/sessions/vault_name/sidxxx/ The Off-site Inventory Report. If a report name includes a time stamp. or File vault/sessions/vault_name/sidxxx/ List of media to be ejected for the session. it is part of a consolidated report operation. the file name of the report will include the session ID.rpt stamp. it is part of a consolidated report operation. If a report name includes a time non_vaulted. they are created when reports are generated from the Administration Console. If a report name includes a time offsite_inventory. they are created when reports are generated from the Administration Console. If a report name includes a time picklist_robot. Program. If you configure the profile Reports tab to write reports to a folder. the file name of the report will include the session ID. they are created when reports are generated from the Administration Console. Report filenames that include _ff are for debug purposes only. vault/sessions/vault_name/sidxxx/ The Picking List for Robot report. Report filenames that include _ff are for debug purposes only.rpt stamp. they are created when reports are generated from the Administration Console. the file name of the report will include the session ID. If you configure the profile Reports tab to write reports to a folder. If you configure the profile Reports tab to write reports to a folder.list by the current vault session.list vault/sessions/vault_name/sidxxx/ The Lost Media Report. the file name of the report will include the session ID.

Report filenames that include _ff are for debug purposes only. vault/sessions/vault_name/sidxxx/ The Summary Distribution List report. they are created when reports are generated from the Administration Console. If a report name includes a summary_distlist_vault. The NetBackup Vault Manager service. the file name of the report will include the session ID. Table B-2 Files and Directories for Vault in Windows Purpose Process that starts vltrun. vault/sessions/vault_name/sidxxx/ Concise view of detail. Program.rpt it is part of a consolidated report operation.log listing major events during the session. the file name of the report will include the session ID. Report filenames that include _ff are for debug purposes only. it is part of a consolidated report operation. summary. they are created when reports are generated from the Administration Console.rpt time stamp. If a report name includes a time stamp.log such as how many images were copied. If you configure the profile Reports tab to write reports to a folder. The paths are specified in relation to the NetBackup directory. vault/sessions/vault_name/sidxxx/ The Vault Inventory Report.257 Windows files and directories Table B-1 Files and directories for Vault in UNIX (continued) Purpose Directory. Also included are Vault files that reside in NetBackup directories. they are created when reports are generated from the Administration Console. or File bin\bpbrmvlt.rpt part of a consolidated report operation. The following table describes the files in each of the directories Vault creates and uses on Windows. If you configure the profile Reports tab to write reports to a folder. If you configure the profile Reports tab to write reports to a folder. If a report name includes a time stamp. The files are either copied into the directories during the installation process or created as Vault sessions run. This log is appended for e-mail notification. Command used to add media logically to containers. the file name of the report will include the session ID.exe from a scheduled or manual vault policy.exe bin\nbvault. or File vault/sessions/vault_name/sidxxx/ The Recovery Report. vault_inventory. Program.exe bin\vltcontainers. Windows files and directories Vault is installed in the directory specified by install_path\NetBackup on Windows systems. it is recovery.exe . Directory. Report filenames that include _ff are for debug purposes only.

logs messages. vault\sessions\cntrDB vault\sessions\sidxxx vault\sessions\vault_name\session Counter to show current duplication session .last . Subdirectory containing working session subdirectories. Directory where the Vault service.exe bin\vltopmenu. Script called by the vault session after it starts. nbvault. and consolidate reports and ejects across sessions. The database of information for media vaulted in containers.258 Windows files and directories Table B-2 Files and Directories for Vault in Windows (continued) Purpose Command used to eject media from Vault sessions and run the reports selected in the profile. Script called by the vault session at the end of eject processing. Script called by the vault session just before vault tapes are ejected. It allows the user to eject or inject media.exe bin\goodies\vlt_ejectlist_notify bin\goodies\vlt_end_notify bin\goodies\vlt_endeject_notify bin\goodies\vlt_start_notify bin\goodies\vlt_starteject_notify Script called by the vault session when the eject process starts. Utility which allows the user to invoke a menu screen containing the various options that an operator of the NetBackup Vault feature can use. Can be manually removed to reduce disk usage if necessary. print various reports individually or collectively. db\vault\vault. or File bin\vlteject. Command used to inject media into a robot and update the Media Manager database. Script called by the vault session just before it exits. Program. Directory. In a cluster environment. The main Vault directory.exe. Command which allows the user to change the off-site parameters of a given piece of media. A subdirectory containing working session directories and log files.exe bin\vltrun.exe bin\vltoffsitemedia. Contains session directories. the sessions directory must reside on the shared disk. Process that executes all the NetBackup commands used during a Vault session. Directory where the Vault commands log messages.xml logs\nbvault logs\vault vault vault\sessions The vault configuration file.exe bin\vltinject.

they are created when reports are generated from the Administration Console. If you configure the profile Reports tab to write reports to a folder.log. vault\sessions\vault_name\sidxxx\ The Container Inventory report.log session. Report filenames that include _ff are for debug purposes only.nn . vault\sessions\vault_name\sidxxx\ The Distribution List for Vault report. it is part of a consolidated report operation. they are created when reports are generated from the Administration Console. If a report name includes a time allmedia_inventory. If a report name detailed_distlist_vault. the file name of the report will include the session ID. it is part of a consolidated report operation. vault\sessions\vault_name\sidxxx\ The Distribution List for Robot report.rpt stamp.images vault\sessions\vault_name\sidxxx\ Contains output from bpduplicate. duped. it is part of a consolidated report operation.rpt stamp.rpt includes a time stamp. If you configure the profile Reports tab to write reports to a folder. If you configure the profile Reports tab to write reports to a folder. Program. Report filenames that include _ff are for debug purposes only. the file name of the report will include the session ID. duplicate. it is part of a consolidated report operation. the file name of the report in that folder will include the session ID. If a report name includes a time container_inv. Report filenames that include _ff are for debug purposes only. If a report name includes a distlist_vault. they are created when reports are generated from the Administration Console. Report filenames that include _ff are for debug purposes only. vault\sessions\vault_name\sidxxx\ The Detailed Distribution List for Vault report. vault\sessions\vault_name\sidxxx\ Shows the output of every command that was executed during the detail.rpt time stamp. If you configure the profile Reports tab to write reports to a folder.259 Windows files and directories Table B-2 Files and Directories for Vault in Windows (continued) Purpose Directory. Report filenames that include _ff are for debug purposes only.rpt time stamp. the file name of the report will include the session ID. they are created when reports are generated from the Administration Console. the file name of the report in that folder will include the session ID. If you configure the profile Reports tab to write reports to a folder. they are created when reports are generated from the Administration Console. it is part of a consolidated report operation. If a report name includes a distlist_robot. vault\sessions\vault_name\sidxxx\ List of images successfully duplicated during the session. or File vault\sessions\vault_name\sidxxx\ The All Media Inventory Report.

it is part of a consolidated report operation. eject. it is part of a consolidated report operation. the file name of the report will include the session ID. If you configure the profile Reports tab to write reports to a folder. Report filenames that include _ff are for debug purposes only. it is part of a consolidated report operation.list vault\sessions\vault_name\sidxxx\ The Lost Media Report. If a report name includes a time picklist_vault. the file name of the report will include the session ID. Program.list by the current vault session. . it is part of a consolidated report operation. Report filenames that include _ff are for debug purposes only. If you configure the profile Reports tab to write reports to a folder. they are created when reports are generated from the Administration Console. vault\sessions\vault_name\sidxxx\ The Off-site Inventory Report.rpt part of a consolidated report operation. vault\sessions\vault_name\sidxxx\ The Picking List for Vault report. If a report name includes a time offsite_inventory.rpt stamp. vault\sessions\vault_name\sidxxx\ The Picking List for Robot report. If you configure the profile Reports tab to write reports to a folder. they are created when reports are generated from the Administration Console. they are created when reports are generated from the Administration Console. If a report name includes a time stamp. If you configure the profile Reports tab to write reports to a folder.rpt stamp. vault\sessions\vault_name\sidxxx\ A list of all images that will be considered for duplication or ejection preview. or File vault\sessions\vault_name\sidxxx\ List of media to be ejected for the session.260 Windows files and directories Table B-2 Files and Directories for Vault in Windows (continued) Purpose Directory. vault\sessions\vault_name\sidxxx\ The Non-vaulted Images Report. it is lostmedia. they are created when reports are generated from the Administration Console. Report filenames that include _ff are for debug purposes only. the file name of the report will include the session ID. they are created when reports are generated from the Administration Console. Report filenames that include _ff are for debug purposes only. Report filenames that include _ff are for debug purposes only. If a report name includes a time picklist_robot. If you configure the profile Reports tab to write reports to a folder.rpt stamp.rpt stamp. If a report name includes a time non_vaulted. the file name of the report will include the session ID. the file name of the report will include the session ID.

Report filenames that include _ff are for debug purposes only. vault\sessions\vault_name\sidxxx\ The Summary Distribution List report. they are created when reports are generated from the Administration Console. If you configure the profile Reports tab to write reports to a folder. If a report name includes a time stamp. summary.log such as how many images were copied. the file name of the report will include the session ID.261 Windows files and directories Table B-2 Files and Directories for Vault in Windows (continued) Purpose Directory. Program. If you configure the profile Reports tab to write reports to a folder. This log is appended for e-mail notification. it is recovery. If a report name includes a summary_distlist_vault.db. Report filenames that include _ff are for debug purposes only. the file name of the report will include the session ID.log listing major events during the session. it is part of a consolidated report operation. vault_inventory. vault\sessions\vault_name\sidxxx\ Media Manager inventory for NetBackup database duplicate pool. If a report name includes a time stamp.rpt it is part of a consolidated report operation. or File vault\sessions\vault_name\sidxxx\ The Recovery Report. vault\sessions\vault_name\sidxxx\ Error log for duplication of specific image.rpt part of a consolidated report operation. volume. vault.list . vault\sessions\vault_name\sidxxx\ Concise view of detail. they are created when reports are generated from the Administration Console. Report filenames that include _ff are for debug purposes only.rpt time stamp. they are created when reports are generated from the Administration Console. the file name of the report will include the session ID. If you configure the profile Reports tab to write reports to a folder.err vault\sessions\vault_name\sidxxx\ The Vault Inventory Report.

262 Windows files and directories .

See media access port catalog backup Catalog Backup Schedule setting 117 reusing unexpired catalog backup media 169 Skip the Catalog Backup Step setting 117 Catalog Backup tab 114 changing off-site volume group name 221 changing off-site volume pool name 221 changing volume group name 221 changing volume pool name 221 choose backups Backup Policies setting 93 Backups Started setting 94 Clients setting 94 disk pools 95 Media Servers setting 95 Schedules setting 95 Source Volume Group setting 96 Type Of Backups setting 96 Volume pools 97 Choose Backups tab 92 clearing the media description field 168 clearing the vault fields 147 Clients setting 94 clusters 21 shared disk 254. 50. 110 copy . 109 Any Available storage unit setting 49. 51 assigning multiple retentions with one profile 156 At Time of Eject setting (Suspend This Session’s Media) 122 B Backup Policies setting 93 Backups Started setting 94 best practices 37 bpdbjobs changes for Vault 231 C CAP. 76 administering access to Vault 218 advanced duplication 100 to avoid sending data over the network 55 All Media Inventory report 210 alternate media server names adding 41.Index A access management 218 ACS number 73 ACSLS server 73 adding alternate media server names 41. 76 Alternate Media Server Names tab 76 alternate read server to avoid sending data over the network 54 Alternate Read Server setting 102. 258 Complete Inventory List for Vault. See All Media Inventory report concurrent copies continue or fail 178 during advanced duplication 189 during basic duplication 185 during original backup 180 during Vault duplication 181 overview 177 through the NetBackup Catalog node 183 to avoid sending duplicates over the network 53 configuration Catalog Backup tab 114 Choose Backups tab 92 Duplication tab 98 Eject tab 118 methods 73 profile 90 Reports tab 124 robots 82 volume pools 63 Container Inventory Report 211 Containers of Many Media setting 85 continue for concurrent copies 178 Copies setting 106.

See Off-site Inventory report G General tab 74 I images duplicate 15 original 15 primary backup 99 Immediate Eject setting 122 . 111 through the NetBackup Catalog node 183 when possible 182 Duplication tab 98 duplication throughput configuring for multiple drives 56 multiple-drive scenario 57 D debug logs 238 deferred reports 126 Deferred setting (Eject Mode) 122 Destination Storage Unit setting 105. 110 Destination Storage Unit setting 105. 111 Destination Volume Pool setting 105. 108. 108. 207 duplicate images 15 duplication advanced 100 Alternate Read Server setting 102. 110 Number Of Write Drives setting 105. 110 increase throughput 56 Multiple Copies dialog 106 Multiple Copies setting 104 multiplexed 182 Number Of Read Drives setting 104. 112 Preserve Multiplexing setting 104 Primary Copy setting 103. 111 Source Backup Server setting 109. 108. 107. 112 Detailed Distribution List for Vault 203 Directory structure 253 directory structure 253 disaster recovery definition 242 definition of disaster recovery plan 243 developing a disaster recovery plan 244 preparing for disaster 241 priorities 243 testing a disaster recovery plan 245 disk staging 39 Distribution List for Vault 202. 111 Destination Volume Pool setting 105. 112 Expire Original Disk Backup Images setting 103 Fail Copies setting 107. 108.list file 140 ejected tapes returned to robot 238 ejecting partial images use suspend to avoid 42 e-mail notifying a tape operator when eject begins 166 error codes 234 extended 138 EXIT status 234 Expire Original Disk Backup Images setting 103 extended error codes 138 F fail for concurrent copies 178 Fail Copies setting 107. 111 Retention Level setting 105 Retention setting 108. 110 E eject consolidating ejects 146 Eject Mode setting 122 Suspend Media On Which Backups Were Written setting 123 Eject Mode settings 122 Eject tab 118 eject. 108. 109 basic 99 Copies setting 106.264 primary backup 99 copying a profile 220 creating a profile 88 a vault 83 a vault policy 131 critical policies 116 Customer ID setting 85 Source Backups Reside On setting 105. 110 files and directories 253 First Off-Site Slot ID setting 86 Full Inventory List for Vault.

76 Media Servers setting 95 menu user interface bpdbjobs 231 changes in vmadm 227 overview 225 Vault Administration Interface 225 Vault Oerator Menu Interface 226 O Off-site Inventory report 209 off-site volume group 86 renaming 221 Off-Site Volume Group setting 86 off-site volume pool 63 renaming 221 Off-Site Volume Pools setting 123 Off-site Volume Pools windows (Eject tab) 123 organizing reports by profile 60 organizing reports by robot 59 organizing reports by vault 60 original images 15 . 110 Number Of Write Drives setting 105.265 immediate reports 126 Immediate setting (Eject Mode) 122 Immediately setting (Suspend This Session’s Media) 122 Inline Tape Copy during advanced duplication 189 during basic duplication 185 Inline Tape Copy. 112 L license key adding on Windows systems 34 load balancing by duplicating daily and ejecting weekly 52 profiles for both originals and duplicates 52 log files debug logs 238 set duration 239 vault session 222 LSM number 73 M MAP. See media access port master server host name of 72 media access port capacity 73 number 73 to use for eject 86 media description field clearing 168 media missing in robot 234 media server names 72 adding alternate 41. See concurrent copies installation on UNIX systems 27 on Windows systems 34 prerequisites for a UNIX system 27 prerequisites for a Windows systems 34 Inventory List for Vault. See Vault Inventory report Iron Mountain Electronic Format report 215 vltadm 225 vltopmenu 226 Monitoring a vault session 136 moving a vault to different robot 221 multiple copies overview 177 See Also concurrent copies Multiple Copies dialog 106 Multiple Copies setting 104 multiple retention mappings 156 multiple volume groups 41 multiplexed duplication 182 N network avoid sending duplicates over the network 53 New Profile dialog 90 New Vault dialog 84 New Vault Robot dialog 82 notify scripts for a specific profile 168 for a specific robot 167 for a specific vault 168 order of execution 168 using 166 vlt_ejectlist_notify 167 vlt_end_notify 167 vlt_endeject_notify 167 vlt_start_notify 166 vlt_starteject_notify 167 notifying a tape operator when eject begins 166 Number Of Read Drives setting 104. 108.

See All Media Inventory report consolidating reports 198 Container Inventory Report 211 deferred 126 Detailed Distribution List for Vault 203 Distribution List for Robot 207 Distribution List for Vault 202 Full Inventory List for Vault. See Vault Inventory report Iron Mountain Electronic Format 215 Lost Media Report 60. 213 Off-site Inventory 209 organizing by profile 60 organizing by robot 59 organizing by vault 60 Picking List for Robot 201 Picking List for Vault 206 printing 195 Recovery Report for Vault 212 Summary Distribution List for Vault 204 types of 201 Vault Inventory report 208 Reports tab 80.list file 135 primary backup copy 99 primary backup image 99 Primary Copy setting 103.266 P partial backups use suspend to avoid vaulting 42 Picking List for Robot 201 Picking List for Vault 206 policy 131 configuration information 132 names 132 NetBackup policy for Vault 130 schedule names 132 preferred vaulting strategies 38 Preserve Multiplexing setting 104 preview media to be ejected 141 preview vault session 135 preview. 124 resource contention avoid by robot usage 47 avoiding 47 load balancing 52 sharing resources with backup jobs 51 specifying different volume pools for source and destination 53 use disk staging to avoid 39 vault original backups to avoid 39 when the read drive is not in the vault robot 51 when two processes try to use the same drive 47 resuming a vault session 136 Retention Level setting 105. See Off-site Inventory report immediate 126 inventory 208 Inventory List for Vault. 111 Retention level setting 95 Retention Mappings tab 79 retention period based on copy one retention period 156 revault media 160 robot . 108. 111 printing troubleshooting problems 233 profile configuring 90 copying a 220 creating 88 notify script for a specific 168 organizing reports by 60 overlap time window 40 printing information 220 Profile dialog 89 profiles for both originals and duplicates 52 R recovering backup images 171 recovery keep primary copy on site 45 match volume pools to usage 45 of damaged media 171 preparing for efficient 44 revault unexpired media 47 use precise naming conventions 45 vault NetBackup catalogs 44 Recovery Report for Vault 212 renaming off-site volume group 221 renaming off-site volume pool 221 renaming volume group 221 renaming volume pool 221 reports All Media Inventory 210 Complete Inventory List for Vault. 107.

267 configuring for vault 82 control host 83 notify script for a specific 167 number 83 organizing reports by 59 properties 73. 51 name of 72 number of drives in 72 Summary Distribution List for Vault 204 supported clusters 21 supported robots 21 supported systems 21 suspend Suspend Media On Which Backups Were Written setting 42 Suspend Option setting 42 use suspend to avoid partial backups 42 Suspend Media for the Next Session setting 123 Suspend Media on Which Backups Were Written setting 123 Suspend Option setting 123 Suspend This Session’s Media setting 123 U unassigning catalog backup media 169 uninstall Vault from UNIX systems 31 UNIX files and directories 253 V Vault accessing 14 vault clearing the Vault fields 147 creating a 83 moving to a different robot 221 name 87 notify script for a specific 168 only the intended backups 42 organizing reports by 60 original backups 39 paradigm 15. 110 Source Backups Reside On setting 105. 111 source volume group 49. 50 Source Volume Group setting 96 status codes 234 storage unit Any Available setting 49. 50. 83 types of 72 Robot Name setting 83 Robot Number setting 83 Robot Type setting 83 robotic volume group 41 Robotic Volume Group setting 86 running multiple sessions simultaneously 134 T time window overlapping 40 troubleshooting bad or missing duplicate media 235 drive or robot offline 236 ejected tapes returned to robot 238 ejecting tapes while in use 237 error codes 234 logs 240 media missing in robot 234 no duplicate progress message 236 printing problems 233 Types Of Backups setting 96 S Schedules setting 95 scratch volume pools 59 server name group 76 session files setting the duration of 223 setting the duration of session files 223 Skip the Catalog Backup Step setting 117 Skip the Eject Step setting 123 Slot ID 86 Slots for Individual Media setting 86 Source Backup Server setting 109. 37 policy 130 printing vault information 220 vendor 87 Vault Administration Interface 225 Vault dialog 84 Vault Inventory report 208 Vault Management Properties dialog Alternate Media Server Names tab 76 General tab 74 Reports tab 80 Retention Mappings tab 79 Vault Name setting 87 Vault Operator Menu Interface 226 vault original backups 39 .

108.268 vault session previewing 135 resuming 136 running 130 running multiple sessions simultaneously 134 setting the duration of session files 223 stopping 135 Vault Vendor setting 87 vaulting containers 85 defined 15 original backups in a 24x7 environment 43 paradigm 15. 37 preferred strategies 38 VSM media 163 Veritas Storage Migrator (VSM) 163 vltoffsitemedia command adding an expiration date 165 assigning slot number 159 changing Vault attributes 162 vmadm changes for Vault 227 special actions menu 228 volume configuration 228 volume group configuration 86 renaming 221 robotic 86 source 96 volume pool configuration 63 destination 105. 112 for backup media that remains on site 64 for catalog media 64 match to data usage 45 naming conventions 45 off-site 63 overview 63 renaming 221 use scratch volume pools 59 Volume pools specifying different source and destination 53 VSM 163 setting the duration of 223 W Windows files and directories 257 Windows systems delicensing Vault 35 working files .

Sign up to vote on this title
UsefulNot useful