NetBackup Admin Guide Vault

VERITAS NetBackup Vault 6.0

System Administrators Guidefor UNIX, Windows, and Linux

N15283C September 2005

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

ii

NetBackup Vault System Administrators Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv Finding NetBackup Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv Accessing the VERITAS Technical Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . .xv Contacting VERITAS Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Chapter 1. Introduction to Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Vault Uses NetBackup Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 How to Access NetBackup Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Vault Original or Duplicate Images? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 The Vault Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Choose Backup Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Duplicate Backup Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Back Up the NetBackup Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Eject Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Generate Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 How Vault Uses Volume Groups and Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 NetBackup and Vault Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Vault Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Chapter 2. Installing Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

iii

Supported Robots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Upgrading to NetBackup Vault 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 The Upgrade Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Upgrade Conversion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Successful Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Failed Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Configuration Elements that are Converted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Your Responsibilities After a Successful Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installation Prerequisites for a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installing NetBackup Vault on a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Upgrading NetBackup Vault on a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Uninstalling NetBackup Vault from a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . 19 Microsoft Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Licensing Prerequisites for a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Licensing NetBackup Vault on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Upgrading NetBackup Vault on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . 23 Uninstalling NetBackup Vault from a Windows System . . . . . . . . . . . . . . . . . . . . . 23 Upgrading from bpvault 3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Chapter 3. Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Vaulting Paradigm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Preferred Vaulting Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Vault Original Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Use Disk Staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Ensure All Data is Vaulted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Overlap the Time Window in the Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Consequences of Not Overlapping the Time Window: Missing Data . . . . . . . . 28 Resolve Multiple Names for a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Specify Robotic Volume Group When Configuring a Vault . . . . . . . . . . . . . . . . . . . 29

iv


Multiple Volume Groups (Multiple Robots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Do Not Vault More Than You Need To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Send Only the Intended Backups Off-site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Avoid Vaulting Partial Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Vaulting Original Backups in a 24x7 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Preparing for Efficient Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Vault NetBackup Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Use Precise Naming Conventions for Volume Pools and Groups . . . . . . . . . . . . . . 32 Match Volume Pools to Data Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Designate a Primary Copy and Keep It On Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Suspend Vaulted Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Revault Unexpired Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Media Ejection Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Avoid Resource Contention During Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 When Two Processes Try to Use the Same Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Alternative A: Dedicated Robot for Vault Processing . . . . . . . . . . . . . . . . . . . . . 35 Alternative B: Each Robot as a Vault Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Alternative C: One Robot as Both a Backup and Vault Robot . . . . . . . . . . . . . . . 38 When the Read Drive Is Not in the Vault Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Sharing Resources with Backup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Profiles for Both Originals and Duplicates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 If Your Vault Vendor Does Not Pick Up Media Every Day . . . . . . . . . . . . . . . . . 40 Specify Different Volume Pools for Source and Destination . . . . . . . . . . . . . . . . . . . 40 Use a Separate Volume Pool for Each Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Avoid Sending Duplicates Over The Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Create Originals Concurrently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Use Alternate Read Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Use Advanced Duplication Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Use Storage Units That Specify a Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Contents v

Increase Duplication Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Configuring for Multiple-Drives: Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Multiple-Drive Scenario: Does Not Send Data Over Network . . . . . . . . . . . . . . . . . 45 Maximize Drive Utilization During Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Use Scratch Volume Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Ensure Report Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Organizing Reports by Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Organizing Reports by Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Organizing Reports by Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Consequences of Sharing an Off-site Volume Group Across Multiple Robots . . . 48 Generate the Lost Media Report Regularly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Chapter 4. Configuring NetBackup for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Off-site Volume Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Creating a Volume Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Catalog Backup Schedules for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Creating a Vault Catalog Backup Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Vault Catalog Backup Schedule Configuration Options . . . . . . . . . . . . . . . . . . . 55 Master Server Properties for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Setting the Maximum Number of Vault Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Chapter 5. Configuring Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Information Required to Configure Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Master Server, Media Servers, and Storage Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Robot Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Methods of Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configuring Vault Management Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Vault Management Properties General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Alternate Media Server Names Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Alternative Media Server Names Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Alternate Media Server Names Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 65

vi NetBackup Vault System Administrators Guide

Adding Alternate Media Server Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Retention Mappings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Retention Mappings Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring Robots for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Vault Robot Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Creating a Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Requirements for Creating a Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 How to Create a Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Vault Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Vault Attributes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Retention Mappings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Creating a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 The Number of Profiles Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 How to Create a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Choose Backups Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Choose Backups Tab Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Duplication Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 The Primary Backup Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Basic Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Advanced Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Duplication Tab Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Multiple Copies Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Duplication Rule Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Treatment of Images Without Corresponding Duplication Rule . . . . . . . . . . . . 97 Catalog Backup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Vault Catalog Backup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Catalog Backup Policy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Contents vii

Critical Policies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Catalog Backup Tab Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Eject Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Media Ejection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 ACS MAP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Eject Mode (Immediate or Deferred) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Media Ejection Timeout Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Eject Tab Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Reports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Report Mode (Immediate or Deferred) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Reports that Depend on Eject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Reports Tab Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Changing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Chapter 6. Vaulting and Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Running a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Scheduling a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Creating a Vault Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Vault Policy Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Running a Session Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Running a Session from the Administration Console . . . . . . . . . . . . . . . . . . . . 119 Running a Session from a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Running Multiple Sessions Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Previewing a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Stopping a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Resuming a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Monitoring a Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Detailed Vault Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Extended Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 The List of Images to be Vaulted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

viii


Duplication Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Ejection Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Vault Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Ejecting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Previewing Media To Be Ejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Ejecting Media by Using the NetBackup Administration Console . . . . . . . . . . . . 128 Ejecting Media by Using the Vault Operator Menu . . . . . . . . . . . . . . . . . . . . . . . . . 129 Ejecting Media by Using the vlteject Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Ejecting Media by Using a Vault Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Consolidating Ejects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Injecting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Injecting Media by Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . 134 Injecting Media by Using the Vault Operator Menu . . . . . . . . . . . . . . . . . . . . . . . . 135 Injecting Media by Using the vltinject Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Using Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Vaulting Media in Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Vaulting Container Media by Using the Vault Operator Menu . . . . . . . . . . . . 138 Vaulting Container Media by Using the vltcontainers Command . . . . . . . . . . 138 Managing Containers and Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Using the Vault Operator Menu to Manage Container Media . . . . . . . . . . . . . 140 Using the vltcontainers Command to Manage Container Media . . . . . . . . . . . 141 Reporting on Containers and Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Assigning Multiple Retentions with One Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Vaulting Additional Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Duplicating a Volume Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Duplicating a Volume by Using Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Revaulting Unexpired Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Tracking Volumes Not Ejected by Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Vaulting VSM Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Vaulting Media Not Created by NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Contents ix

Notifying a Tape Operator When Eject Begins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Using Notify Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Notify Script for a Specific Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Notify Script for a Specific Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Notify Script for a Specific Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Order of Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Clearing the Media Description Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Deassigning Vaulted NetBackup Catalog Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Restoring Data from Vaulted Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Replacing Damaged Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Chapter 7. Creating Originals or Copies Concurrently . . . . . . . . . . . . . . . . . . . . . 163 Understanding Concurrent Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Continue or Fail for Concurrent Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Continue Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Fail All Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Creating Original Images Concurrently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Creating Duplicate Images Concurrently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 When Duplication is Possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Concurrent Copies Through the Catalog Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Concurrent Copies During Basic Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Concurrent Copies During Advanced Duplication . . . . . . . . . . . . . . . . . . . . . . . . . 175 Chapter 8. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Generating Reports by Using the Vault Operator Menu . . . . . . . . . . . . . . . . . . . . . 182 Generating Reports by Using the vlteject Command . . . . . . . . . . . . . . . . . . . . . . . 182 Generating Reports by Using a Vault Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Consolidating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Vault Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

x NetBackup Vault System Administrators Guide

Reports for Media Going Off-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Picking List for Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Distribution List for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Detailed Distribution List for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Summary Distribution List for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Reports for Media Coming On-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Picking List for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Distribution List for Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Inventory Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Vault Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Off-site Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 All Media Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Graphical Representation of Inventory Reports Scope . . . . . . . . . . . . . . . . . . . . 200 Container Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Recovery Report for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Lost Media Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Non-vaulted Images Exception Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Iron Mountain FTP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Chapter 9. Administering Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Setting Up E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Administering Access to Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Vault Operator User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Printing Vault and Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Copying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Moving a Vault to a Different Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Changing Volume Pools and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Vault Session Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Session Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Setting the Duration of Vault Session Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Contents

xi

General Operational Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Vaulting Storage Migrator Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Disk Only Source of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 The Scope of the Source Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Chapter 10. Using the Menu User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Using the Vault Administration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Using the Vault Operator Menu Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Changes in vmadm for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Additions to Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Changes to the Special Actions Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Change Vault Name for Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Change Date Volumes are Sent to Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Change Date Volumes Return from Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Change Vault Slot for Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Change Vault Session ID for Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Changes to Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Changes in bpdbjobs for Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Chapter 11. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Printing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Errors Returned by the Vault Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 No Media Are Ejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Media is Missing in Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Bad or Missing Duplicate Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Tape Drive or Robot Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 No Duplicate Progress Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Ejecting Tapes While in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Tapes Not Removed from the MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Unexpired Tapes Were Injected into the Robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Debug Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

xii NetBackup Vault System Administrators Guide

Setting the Duration and Level of Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Logs To Accompany Problem Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Appendix A. Recovering from Disasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Definition of Disaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Definition of Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Definition of Disaster Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Recovery Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Developing a Disaster Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Testing a Disaster Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Disaster Recovery in the NetBackup Vault Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Preparing for Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Recovering NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Recovering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Recovering to a Specific Point in Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Appendix B. Vaults File and Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 245 UNIX Files and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Windows Files and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

Contents

xiii

xiv


Preface

This NetBackup Vault System Administrators Guide explains procedures performed by the system administrator and provides the administrative information needed to run NetBackup Vault on both UNIX, Windows, and Linux systems. A separate Operators Guide provides instructions for operators.

Getting HelpYou can find answers to questions and get help from the NetBackup documentation and from the VERITAS technical support web site.

Finding NetBackup DocumentationA list of the entire NetBackup documentation set appears as an appendix in the NetBackup Release Notes. All NetBackup documents are included in PDF format on the NetBackup Documentation CD. For definitions of NetBackup terms, consult the online glossary.

To access the NetBackup online glossary 1. In the NetBackup Administration Console, click Help > Help Topics. 2. Click the Contents tab. 3. Click Glossary of NetBackup Terms. Use the scroll function to navigate through the glossary.

Accessing the VERITAS Technical Support Web SiteThe address for the VERITAS Technical Support Web site is http://support.veritas.com. The VERITAS Support Web site lets you do any of the following:xv

Getting Help Obtain updated information about NetBackup Vault, including system requirements,

supported platforms, and supported peripherals Contact the VERITAS Technical Support staff and post questions to them Get the latest patches, upgrades, and utilities View the NetBackup Vault Frequently Asked Questions (FAQ) page Search the knowledge base for answers to technical support questions Receive automatic notice of product updates Find out about NetBackup Vault training Read current white papers related to NetBackup Vault

From http://support.veritas.com, you can complete various tasks to obtain specific types of support for NetBackup Vault: 1. Subscribe to the VERITAS Email notification service to be informed of software alerts, newly published documentation, Beta programs, and other services. a. From the main http://support.veritas.com page, select a product family and a product. b. Under Support Resources, click Email Notifications. Your customer profile ensures you receive the latest VERITAS technical information pertaining to your specific interests. 2. Locate the telephone support directory at http://support.veritas.com by clicking the Phone Support icon. A page appears that contains VERITAS support numbers from around the world. Note Telephone support for NetBackup Vault is only available with a valid support contract. To contact VERITAS for technical support, dial the appropriate phone number listed on the Technical Support Guide included in the product box and have your product license information ready for quick navigation to the proper support group. 3. Contact technical support using e-mail.

xvi


Accessibility Features

a. From the main http://support.veritas.com page, click the E-mail Support icon. A wizard guides you to do the following: Select a language of your preference Select a product and a platform Provide additional contact and product information, and your message Associate your message with an existing technical support case

b. After providing the required information, click Send Message.

Contacting VERITAS LicensingFor license information, you can contact us as follows: Call 1-800-634-4747 and select option 3 Fax questions to 1-650-527-0952 In the Americas, send e-mail to [email protected].

In the Asia and Pacific areas, send email to [email protected]. In all other areas, send email to [email protected].

Accessibility FeaturesNetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity. Accessibility features include: Support for assistive technologies such as screen readers and voice input (Windows

servers only) Support for keyboard (mouseless) navigation using accelerator keys and mnemonic

keys For more information, see the NetBackup Installation Guide.

Preface

xvii

Comment on the Documentation

Comment on the DocumentationLet us know what you like and dislike about the documentation. Were you able to find the information you needed quickly? Was the information clearly presented? You can report errors and omissions or tell us what you would find useful in future versions of our manuals and online help. Please include the following information with your comment:

The title and product version of the manual on which you are commenting The topic (if relevant) on which you are commenting Your comment Your name

Email your comment to [email protected]. Please only use this address to comment on product documentation. See Getting Help in this preface for information on how to contact Technical Support about our software. We appreciate your feedback.

xviii


Introduction to Vault

1

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, off-site storage facility. NetBackup Vault also generates reports to track the location and content of the media. Vault functionality does not have to be used only for disaster recovery; you can use Vault to manage data and media that you store off-site for regulatory archival purposes. For more information, see the following: Vault Uses NetBackup Functions on page 1 How to Access NetBackup Vault on page 2 Vault Original or Duplicate Images? on page 3 The Vault Process on page 3 How Vault Uses Volume Groups and Pools on page 5 NetBackup and Vault Configuration on page 5 Vault Management Procedures on page 6

Vault Uses NetBackup FunctionsNetBackup Vault uses existing NetBackup functions for all operations, such as duplication of images, media control, reporting, and ejecting and injecting of tapes. Information from Vault is integrated with other NetBackup components and appears in the NetBackup Activity Monitor. NetBackup Vault interacts with the following NetBackup services and catalogs: Media Manager manages robots and media. The NetBackup catalog and the Media Manager database record which images have

been vaulted. The Media Manager database information determines when expired media can be

returned to the robot for reuse. The Activity Monitor displays the status of the Vault job. 1

How to Access NetBackup Vault

The following diagram shows the NetBackup, Media Manager, and Vault relationships:Services Interaction Diagram

Vault * Chooses images to vault * Requests duplication; 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 VaultNetBackup Vault is installed on a NetBackup master server. 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, Vault Management will be a node of the Administration Console. You can use the Administration Console to configure and manage Vault. Alternatively, you can manage Vault by using the following methods:

Menu-based user interfaces. Command line utilities.

2


Vault Original or Duplicate Images?

Vault Original or Duplicate Images?One of your most important choices is whether to send original or duplicate images off site. If you send original images off site, you do not have to duplicate images and therefore do not have to configure duplication. Vault distinguishes between original images and duplicate images as follows: Original images are created by NetBackup during a backup job, including all copies

created concurrently by a backup policy. NetBackup can create up to four copies of an image concurrently during the backup process; all are considered originals. 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. Duplicate images are copies created by Vault. A Vault job reads the primary backup

image and writes one or more duplicate images concurrently; the Vault job is separate from the NetBackup policy job.

The Vault ProcessVaulting is the process of sending backup images off site to a protected storage location. For more information about the specific steps in a Vault process, see the following, 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). The other steps are optional so you can separate the Vault tasks into separate jobs if desired, using different jobs to accomplish different tasks. For example, you can use one job to select and duplicate images daily, and another job to eject media and generate reports weekly. Injecting returned media back into the robot is a manual operation. The Vault reports include the media that should be recalled from the off-site location and injected into the robot. 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.

Chapter 1, Introduction to Vault

3

The Vault Process

Choose Backup ImagesThe first step of the Vault process is choosing the backup images that are candidates to be transferred off site. This step, known as image selection, must be configured for every Vault job. Vault uses the criteria in a Vault profile (a set of rules for selecting images, duplicating images, and ejecting media) to determine which backup images are candidates to send off site. If you create multiple original images concurrently during a backup job, Vault can send original images off site (depending on the profile rules). If you duplicate images, Vault uses the primary backup image as the source image for the duplication operation (exception: to improve performance, Vault will duplicate from a nonprimary copy on disk if one exists).

Duplicate Backup ImagesThe second step of the Vault process is duplicating the backup images that are candidates to be transferred off site. This step, known as image duplication, writes copies of backup images on media that you can eject and transfer off site. Image duplication is optional. If you send your only backup image off site or create multiple original backup images and send one or more of those off site, you do not have to duplicate images in Vault and therefore do not have to configure the duplication step. However, that original image must be written to media in the off-site volume pool so it will be ejected and transferred off site.

Back Up the NetBackup CatalogThe third step of the Vault process is backing up the NetBackup catalog. The NetBackup catalog consists of databases of information about the NetBackup configuration and any backups that have been performed. The information about backups includes records of the files and the media on which the files are stored, including information about media sent off-site. The catalogs also have information about the media and storage devices that are under the control of Media Manager. Backing up the catalog is optional. However, vaulting a catalog backup with your data can help you recover from a disaster more efficiently. Vault creates its own catalog backup with up-to-date information; Vault does not duplicate the NetBackup catalog.

Eject MediaThe fourth step of the Vault process is ejecting the media that you then transfer to secure storage, often at a separate facility. Media that are ejected are tracked by Vault reporting facilities and will be recalled from off-site storage for reuse after the images expire. Media4 NetBackup Vault System Administrators Guide

How Vault Uses Volume Groups and Pools

can be ejected automatically by a scheduled Vault job or manually after the job has completed. Media can be ejected for each job individually or can be consolidated into a single eject operation for multiple Vault jobs.

Generate ReportsThe fifth step of the Vault process is generating reports. Reports track the media managed by Vault. 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. Reports can be generated as part of the Vault job or manually after the job is finished. Reports can be generated for each job individually or can be consolidated with a consolidated eject operation. Generating reports is optional.

How Vault Uses Volume Groups and PoolsVolume groups identify where volumes reside. They are used as a tracking mechanism by Vault to determine where a volume is located. Volumes in a robotic volume group reside in a robot. During a Vault job, Vault searches the robotic volume group for media that matches a profiles criteria; if media are found, Vault ejects that media and then moves it logically to an off-site volume group. (A logical move means to change the volume attributes to show the new location.) When a volume in off-site storage expires and is injected back into the robot, Vault moves it back into the robotic volume group. 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.

NetBackup and Vault ConfigurationBefore you can begin to use Vault, you must first set up and configure NetBackup so that volume pools and policies are available to support Vault operations. To do so, see Configuring NetBackup for Vault on page 51. After configuring NetBackup for use with Vault, you must configure Vault robots and profiles. Configuring Vault on page 59 provides instructions for configuring Vault.


5

Vault Management Procedures

You should also review the information in Best Practices on page 25; it can help you determine how to setup and configure Vault most effectively for your environment, resources, requirements, service level agreements, and so on.

Vault Management ProceduresThe following table summarizes operational procedures for Vault. The NetBackup Vault Operators Guide provides more detailed information on day-to-day procedures.Vault Management Procedures Operational Procedure Configuration: review backup procedures and determine duplication capacity needed. Staff Responsibilities Determine the need for basic levels of duplication service on a per policy basis.

Determine appropriate servers to run duplications Ensure sufficient hardware, software, and and determine appropriate time windows for network capacity is available for duplication of running duplication. backup images. Configure Vault profiles. Review duplication windows for performance and throughput. Duplication: set up Vault policies to run vault sessions on a schedule. Determine media requirements and setup initial volume pool for duplication. Monitor volume pool usage. Monitoring: use the NetBackup Activity Monitor to determine progress. Set up links between log files and monitoring system for e-mail and/or paging notification. Ensure duplication jobs complete successfully. Ensure errors are reported to appropriate personnel. Monitor jobs to ensure they start when scheduled. Ensure sufficient media are available for duplicates to run.

Vault reports: generate reports regularly to ensure Review production duplication cycle for that images are duplicated correctly. thoroughness. Compare report output with ejected and returned Ensure media going off-site and returning media. on-site matches reports. Check duplication volume pools and catalog backup pools for available media. Ensure sufficient media available for duplication.

6


Vault Management Procedures Vault Management Procedures (continued) Operational Procedure Use Media Manager to expire/freeze tapes manually when 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. Duplication capacity review: determine capacity planning cycle, including reaction time, costing factors, and new requirements. Assist production support to help determine system, robotic, and network utilization rates (for example, disk capacity). Assist in defining requirements for the system infrastructure to use Vault effectively with other computing environment resources. Recovery review: test recovery procedures Know procedures for restoring duplicated regularly to ensure recovery of essential data from images. off-site storage. Know how to restore database catalog, backup software, and so on in case of disaster on Netbackup server(s). Staff Responsibilities Recall media that was not recalled during normal Vault operations.

Ensure Vault catalog backup occurs.


7

Vault Management Procedures

8


Installing VaultThis chapter outlines the steps required to install NetBackup Vault on both UNIX and Windows systems. The following topics are covered:

2

Supported Systems on page 9 Supported Robots on page 9 Upgrading to NetBackup Vault 6.0 on page 10 UNIX Systems on page 14 Microsoft Windows Systems on page 22 Upgrading from bpvault 3.4 on page 24

Supported SystemsVault runs on the same operating systems and versions and in the same clustering environments as NetBackup except as noted in the NetBackup Release Notes. NetBackup restrictions and limitations related to systems, clusters, and peripherals also apply to Vault. Exception: Vault does not support standalone drives. For information about supported systems and supported upgrade paths, see the NetBackup Release Notes.

Supported RobotsVault supports all Media Manager-supported robot types except optical disk library (ODL) robots. Vault also supports robots that do not have media access ports and barcode readers. For best performance and to avoid user errors when entering media IDs, VERITAS recommends that you use robots that have media access ports and barcode readers. For information about how to use Vault with robots that do not have media access ports, see Media Ejection Overview on page 104.

9

Upgrading to NetBackup Vault 6.0

Upgrading to NetBackup Vault 6.0Changes in NetBackup and Vault beginning with the 6.0 release require corresponding changes to the Vault configuration during the upgrade process. For more information about the new features and capabilities mentioned in this upgrade information, see the NetBackup Release Notes or the appropriate sections in this administrators guide.

The Upgrade Conversion ProcessThe Vault configuration is converted to the 6.0 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). The upgrade conversion process first creates a saved version of the existing Vault configuration file:

/usr/openv/netbackup/db/vault/vault.xml.save.YYYYMMDD-HHMMSS (UNIX) install_path\db\vault\vault.xml.save.YYYYMMDD-HHMMSS (Windows)

It then converts/upgrades the Vault configuration file:

/usr/openv/netbackup/db/vault/vault.xml (UNIX) install_path\db\vault\vault.xml (Windows)

Upgrade Conversion LogThe 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):

/usr/openv/netbackup/db/vault/nbvault-upgrade.log.YYYYMMDD-HHMMSS (UNIX) install_path\db\vault\nbvault-upgrade.log.YYYYMMDD-HHMMSS (Windows)

The information written to the upgrade log file does not depend on any of the NetBackup or Vault log level settings.

Successful ConversionIf the upgrade conversion succeeded, the existing vault configuration file is converted to the 6.0 format and nbvault starts in service/daemon mode. You can confirm this by reading the upgrade log file, in which you can see the result of the upgrade.10 NetBackup Vault System Administrators Guide


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.

Failed ConversionIf the upgrade conversion fails, nbvault does not start in service/daemon mode, and the existing Vault configuration file remains unchanged. Because the NetBackup Vault Manager must be running, Vault will not work. If the conversion fails, do the following: 1. Read the upgrade log file to determine the details of the failure. If the upgrade log file does not exist, nbvault failed even before attempting to upgrade the vault configuration file. In that case, read the event log (on Windows) or system log (on UNIX or Linux) for more details. 2. Based on the information in the log file, take corrective action. 3. Start the nbvault service/daemon manually. nbvault will again attempt to upgrade the Vault configuration file. For every upgrade attempt, nbvault creates a new upgrade log file. If the upgrade fails again, nbvault will not start in service/daemon mode. Repeat the preceding steps to resolve the reason for failure. Upgrade information also is written to the nbvault log (see Debug Logs on page 230) but it depends on the existence of the log directory and the log level settings of Vault. Note On Windows systems, the nbvault service will only start automatically if you have a combined license key for both NetBackup and Vault. If you have a separate Vault license key, you must add the Vault license key and then start the nbvault service manually; nbvault will then attempt to upgrade the Vault configuration. (Does not apply to UNIX or Linux systems.)

Configuration Elements that are ConvertedMost of the upgrade conversion changes are required for the new catalog backup method. Vault uses the new hot, online catalog backup method for catalog backups. This new method requires a catalog backup policy (NBU-Catalog) that has a Vault Catalog Backup schedule. Following are the changes made to the Vault configuration file:

Chapter 2, Installing Vault

11

Upgrading to NetBackup Vault 6.0 Retention mappings. All retention mapping information (from files such as

retention_mappings and retention_mappings.vault_name) are added to the Vault configuration file. The existing retention mapping files are obsolete; they will be renamed to retention_mappings.save.YYYYMMDD-HHMMSS and retention_mappings.vault_name.save.YYYYMMDD-HHMMSS respectively. You can remove them later. Report distribution. Report distribution values in each profile are propogated to each

individual report in that profile. The new report distribution values at the Vault Management Properties level are set to blank. In previous releases, report distribution was configured at the profile level only. Eject notification e-mail addresses. The new eject notification values are set as follows: Blank at the Vault Management Properties level. At the robot level (Vault Robot dialog), they will be set to use the values from

Vault Management Properties level. At the profile level, they will be set to use the values from Robot or Vault

Management Properties level. In NetBackup Vault 5.1, the vlt_starteject_notify script was used to notify a tape operator when the eject began. Catalog backup. 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. Vault no

longer supports the legacy catalog backup methods, regular (one volume only) and two-phase. 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. All existing user-specified catalog paths will be removed. You can no longer

specify catalog paths or extra paths to include in the catalog backup. Paths to all files required for a catalog backup are part of the new catalog backup implementation, and they are backed up automatically. 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. Note that the Vault catalog backup does not include data from critical policies that are in the catalog backup policy. A new catalog backup policy (of type NBU-Catalog) with a unique name (such as

VltCat-Backup-0) will be created with default values. Every profile that has a catalog backup step configured will be converted to use this policy to back up the catalog. 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, where MyVault is the vault name). The profiles12 NetBackup Vault System Administrators Guide


will be converted to use volumes from these new pools to back up the catalog. Note: The upgrade process does not move any media to these volume pools; you must add media to them before running Vault sessions after the upgrade. After the upgrade, profiles will not use the catalog volume pools that they used before the upgrade. However, 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, 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 profiles catalog backup. The volume pool will be the new catalog volume pool created for that vaults

catalog backup. The existing retention period (which is specified in number of days) will be

converted to a matching retention level. Therefore, for every unique combination of storage unit, newly created volume pool, and converted retention level, a new Vault Catalog Backup schedule will be created with a unique name (such as VltCat-MyVault-0-SCHED-0, where VltCat-MyVault-0 is the newly created catalog backup volume pool). The new schedules will be created in the newly created catalog backup policy (VltCat-Backup-0). After the upgrade succeeds, all the existing values (such as media server, volume

pool, and so on) from the catalog backup step of profiles 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. Eject. For every profile that has catalog backup configured, 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 profiles eject step. (As noted earlier, you must add media to these new volume pools.) Also, 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. After all pre-6.0 catalog backup volumes are recalled, 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. Miscellaneous. Other, miscellaneous changes will be made in the vault configuration

file to upgrade it to the 6.0 format. Read the upgrade log file to understand them.


13

UNIX Systems

Your Responsibilities After a Successful UpgradeYou must read each and every statement written to the upgrade log file before you start using the upgraded Vault configuration. Especially consider the following: Note which configuration items are not supported or are ignored in 6.0, 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. Note the new volume pools (of type Catalog Backup), catalog backup policies, and

Vault Catalog Backup schedules that are created and how they are used by the upgraded Vault profiles. Note the retention levels of the new catalog backup schedules. The upgrade

conversion script assigns a retention level that is closest to the retention period of the original catalog backup step; therefore, the new retention level may not exactly match the original retention period. If it does not match, you can redefine a retention level in NetBackup so it will exactly match the original retention period, and then change the new catalog backup schedule so it uses the redefined retention level. You also must add volumes to the newly created volume pools (of type Catalog Backup) so that they will be used by the converted profiles to perform catalog backups.

UNIX SystemsNetBackup Vault can be installed and uninstalled on a UNIX system.

Installation Prerequisites for a UNIX System A NetBackup master server must be installed on the UNIX system. Vault cannot be

installed on a NetBackup media server or on a NetBackup client. You must have a valid NetBackup Vault license key.

Installing NetBackup Vault on a UNIX SystemUse this procedure to do an initial installation on a UNIX system. NetBackup must be installed before you can install Vault, and you must install the same version of Vault as NetBackup. For instructions about installing NetBackup, see the NetBackup Installation Guide for UNIX. If you are upgrading Vault, see Upgrading NetBackup Vault on a UNIX System on page 16.

14


UNIX Systems

If you are installing Vault in a cluster environment, you must install Vault on all systems in the cluster on which NetBackup master servers are installed. For information about where the various Vault components are installed, see Vaults File and Directory Structure on page 245. To install NetBackup Vault on a UNIX server

Note If you are installing Vault in a cluster environment, you must freeze the active node before you begin the installation process so that migrations do not occur during installation. For information about freezing a service group, see the NetBackup High Availability System Administrators Guide. 1. Log in as the root user on the system on which the NetBackup master server is installed. 2. 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. Insert the CD that contains the Vault software into the CD-ROM drive. 4. Change the working directory to the CD-ROM directory.cd /cd_rom_directory

Where cd_rom_directory is the path to the directory where you can access the CD-ROM. On some platforms, you may need to mount this directory. For instructions on how to mount the directory, see the NetBackup Installation Guide for UNIX. 5. Enter the following command: ./install The Installation Options menu appears. 6. Select the NetBackup Add-On Product Software option. A menu of NetBackup product options is displayed. 7. Select the NetBackup Vault option. 8. Enter q to quit the menu. 9. When asked if the list is correct, answer y.


15

UNIX Systems

The installation process begins. When completed, the Installation Options menu appears. 10. Enter q to quit the Installation Options menu. 11. In a cluster environment, complete step 1 through step 10for each node on which you installed a NetBackup master server. Note If you are installing Vault in a cluster environment, unfreeze the active node after the installation completes. For information about unfreezing a service group, see the NetBackup High Availability System Administrators Guide. 12. Start the NetBackup Administration Console by entering the following command:/usr/openv/netbackup/bin/jnbSA&

To complete a new installation, 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). Please read the following chapters so you will develop an understanding of how Vault works and how best to configure Vault for your operations. You should configure the e-mail address for notification of session status and enter alternate media server names, if appropriate. See Configuring Vault Management Properties on page 62. In a cluster environment, you can configure Vault by using the NetBackup Administration Console connected through the NetBackup virtual server name, regardless of which cluster server is currently active.

Upgrading NetBackup Vault on a UNIX SystemUse this procedure if you already have Vault installed and are upgrading to a newer version of Vault. 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, you must freeze the active node before you begin the upgrade process so that migrations do not occur during the upgrade. For information about freezing a service group, see the NetBackup High Availability System Administrators Guide.

16


UNIX Systems

1. Log in as root to the system on which Vault is installed. 2. Execute the following command to uninstall NetBackup Vault:pkgrm VRTSnbvlt

A message asking if you want to remove the package is displayed:Do you want to remove this package?

3. Enter y to remove Vault. 4. If you are prompted with a message about super-user permissions and you are asked if you want to continue, enter y. 5. 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,n,?,q]

6. Enter y. The package removal process will remove Vault program components but not database and log files, so you will not lose your configuration during the upgrade. 7. Upgrade NetBackup by following the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for UNIX. 8. Insert the CD that contains the Vault software into the CD-ROM drive. 9. Change the working directory to the CD-ROM directory.cd /cd_rom_directory

Where cd_rom_directory is the path to the directory where you can access the CD-ROM. On some platforms, you may need to mount this directory. For instructions on how to mount the directory, see the NetBackup Installation Guide for UNIX. 10. Enter the following command: ./install The Installation Options menu appears. 11. Select the NetBackup Add-On Product Software option. A menu of NetBackup product options is displayed. 12. Select the NetBackup Vault option.Chapter 2, Installing Vault 17

UNIX Systems

13. Enter q to quit the menu. 14. When asked if the list is correct, answer y. The installation process begins. When completed, the Installation Options menu appears. 15. Enter q to quit the Installation Options menu. 16. In a cluster environment, complete step 1 through step 15 for each node on which Vault is installed. Note If you are upgrading Vault in a cluster environment, unfreeze the active node after upgrading Vault. For information about unfreezing a service group, see the NetBackup High Availability System Administrators Guide. 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, you must freeze the active node before you begin the upgrade process so that migrations do not occur during the upgrade. For information about freezing a service group, see the NetBackup High Availability System Administrators Guide. 1. Log in as root to the system on which Vault is installed. 2. Optionally, delete the following files and directories. Although not required, deleting these items can help ensure that all Vault files installed on the system are the same revision.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

3. Upgrade NetBackup by following the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for UNIX. 4. Insert the CD that contains the Vault software into the CD-ROM drive. 5. Change the working directory to the CD-ROM directory.cd /cd_rom_directory

18


UNIX Systems

Where cd_rom_directory is the path to the directory where you can access the CD-ROM. On some platforms, you may need to mount this directory. For instructions on how to mount the directory, see the NetBackup Installation Guide for UNIX. 6. Enter the following command: ./install The Installation Options menu appears. 7. Select the NetBackup Add-On Product Software option. A menu of NetBackup product options is displayed. 8. Select the NetBackup Vault option. 9. Enter q to quit the menu. 10. When asked if the list is correct, answer y. The installation process begins. When completed, the Installation Options menu appears. 11. Enter q to quit the Installation Options menu. 12. In a cluster environment, complete step 1 through step 11 for each node on which you are installing a NetBackup master server. Note If you are upgrading Vault in a cluster environment, unfreeze the active node after upgrading Vault. For information about unfreezing a service group, see the NetBackup High Availability System Administrators Guide. 13. Start the NetBackup Administration Console by entering the following command:/usr/openv/netbackup/bin/jnbSA&

In a cluster environment, you should run the NetBackup Administration Console on the primary node in the cluster when you perform Vault configuration.

Uninstalling NetBackup Vault from a UNIX SystemThe following instructions describe how to remove Vault permanently from a UNIX system without uninstalling NetBackup.


19

UNIX Systems

Before you uninstall NetBackup Vault, you should delete all Vault-specific items from NetBackup, such as volume pools, Vault policies, and so on. Although all Vault program components are removed when Vault is uninstalled, configuration items related to NetBackup are not. All Vault components and configuration information are removed during this procedure. 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. 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, including the Vault database and log files. Note If you are removing Vault in a cluster environment, you must freeze the active node before you begin removing Vault so that migrations do not occur during the removal process. For information about freezing a service group, see the NetBackup High Availability System Administrators Guide. 1. Log in as root to the system on which Vault is installed. 2. Execute the following command to uninstall NetBackup Vault:pkgrm VRTSnbvlt

A message asking if you want to remove the package is displayed:Do you want to remove this package?

3. Enter y to remove Vault. 4. If you are prompted with a message about super-user permissions and you are asked if you want to continue, enter y. 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,n,?,q]

5. To remove Vault completely and not upgrade to a newer version, enter n. Messages that ask about removing Vault files will appear.20 NetBackup Vault System Administrators Guide

UNIX Systems

6. Enter y to each prompt to remove the Vault files. 7. In a cluster environment, complete step 1 through step 6 for each node on which Vault is installed. Note In a cluster environment, unfreeze the active node after removing Vault from all systems. For information about unfreezing a service group, see the NetBackup High Availability System Administrators Guide.

To remove NetBackup Vault from a UNIX system other than Solaris Caution This process removes Vault completely, including the Vault database and log files. Note If you are removing Vault in a cluster environment, you must freeze the active node before you begin removing Vault so that migrations do not occur during the removal process. For information about freezing a service group, see the NetBackup High Availability System Administrators Guide. 1. Log in as root to the system on which Vault is installed. 2. Remove the following files and directories:rm rm rm rm rm rm rm rm /usr/openv/lib/libvault /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. Remove the Vault database directory:rm -rf /usr/openv/netbackup/db/vault

4. Remove the two Vault log directories if they exist:rm -rf /usr/openv/netbackup/logs/nbvault rm -rf /usr/openv/netbackup/logs/vault

5. In a cluster environment environment, complete step 1 through step 4 for each node on which Vault is installed.


21

Microsoft Windows Systems

Note In a cluster environment, unfreeze the active node after removing Vault from all systems. For information about unfreezing a service group, see the NetBackup High Availability System Administrators Guide.

Microsoft Windows SystemsNetBackup Vault is installed on a Windows system when NetBackup is installed; no separate installation procedure is required. However, to use Vault, 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, including Vault. If you have already installed NetBackup and entered the license key, Vault is already licensed. You may have a separate license key specifically for the Vault option. If so, you will

have to enter the Vault license key before you can use Vault (see Licensing NetBackup Vault on a Windows System on page 22). If you are installing and running the Vault in a cluster environment, you must license Vault on all systems in the cluster on which NetBackup master servers are installed. For information about where the various Vault components are installed, see Vaults File and Directory Structure on page 245.

Licensing Prerequisites for a Windows System A NetBackup master server must be installed and running on the Windows computer.

Vault cannot be installed on a NetBackup media server or on a NetBackup client. You must have a valid NetBackup Vault license key.

Licensing NetBackup Vault on a Windows SystemAlthough NetBackup Vault is installed during NetBackup installation, you cannot use Vault until you enter the appropriate license key. Note If the license key for NetBackup Vault was included in the license key for the base NetBackup product, you do not have to perform this procedure.

22


Microsoft Windows Systems To add the Vault license key

1. From the NetBackup Administration console, choose Help > License Keys. The NetBackup License Keys dialog box appears. 2. Click New to display the Add a new License Key dialog box. 3. Enter the NetBackup Vault license key. 4. Click Add. The license key is displayed in the NetBackup License Keys dialog box. 5. Click Close to close the NetBackup License Keys dialog box. To complete a new installation, 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). Please read the following chapters so you will develop an understanding of how Vault works and how best to configure Vault for your operations. Be sure to configure the e-mail address for notification of sessions status and enter alternate media server names, if appropriate. See Configuring Vault Management Properties on page 62.

Upgrading NetBackup Vault on a Windows SystemOn Windows systems, NetBackup Vault is upgraded at the same time NetBackup is upgraded. Therefore, to upgrade NetBackup Vault, follow the upgrade installation procedures for NetBackup in the NetBackup Installation Guide for Windows.

Uninstalling NetBackup Vault from a Windows SystemThe NetBackup Vault software is not uninstalled; rather, you deactive Vault by deleting the license key from the list of current NetBackup licenses. When the license key is deleted, NetBackup Vault is no longer available for use. You can delete the Vault license key only if Vault was licensed with its own license key, separate from the base NetBackup product license key. Before you delete the Vault license key, you should remove all Vault-specific configuration items by using the NetBackup Administration Console to delete them. Deleting the Vault configuration ensures that NetBackup does not include anything that was configured for Vault, such as volume pools.


23

Upgrading from bpvault 3.4 To delete the Vault license key

If you are running BMR in a cluster environment, you must delete the BMR license key on every system in the cluster on which the BMR master server is installed. 1. From the NetBackup Administration Console, choose Help > License Keys. The NetBackup License Keys dialog box is displayed. 2. From the list of keys displayed, select the Vault license key. Caution If NetBackup Vault was included as part of the base product key, performing the following step will delete your base key and you will be unable to use NetBackup. If you do not want to delete the NetBackup license key, do not continue. 3. Click Delete. The Vault license key is deleted from the Current Licenses dialog box, and Vault Management is no longer displayed in the NetBackup Administration Console tree.

Upgrading from bpvault 3.4To upgrade from bpvault 3.4 to NetBackup Vault, first upgrade to a NetBackup Vault 4.5 release and then follow the upgrade path documented in the NetBackup Release Notes.

24


Best Practices

3

Vault can be configured to support how your computing or data center environment is set up and how it operates. A best practice recommendation that may provide benefit for one environment may not provide the same benefit for another. You should evaluate and implement any recommendations based on the benefit to your environment. For more information, see the following:

Vaulting Paradigm beginning on page 26 Preferred Vaulting Strategies on page 26 Ensure All Data is Vaulted on page 28 Do Not Vault More Than You Need To on page 30 Preparing for Efficient Recovery on page 32 Media Ejection Recommendations on page 35 Avoid Resource Contention During Duplication on page 35 Avoid Sending Duplicates Over The Network on page 41 Increase Duplication Throughput on page 44 Maximize Drive Utilization During Duplication on page 46 Use Scratch Volume Pools on page 47 Ensure Report Integrity on page 47 Generate the Lost Media Report Regularly on page 48

25

Vaulting Paradigm

Vaulting ParadigmHow you set up and name your vaults and profiles depends on your operations. For example, if you maintain a customer database and a payroll database, you may choose to organize your vaults by data usage and your profiles by time periods, as follows:

Vaults CustomerDB

Profiles Weekly Monthly

Payroll

Biweekly Monthly Yearly

Alternatively, if your operations are organized geographically, you can set up your vaults by location and your profiles by data type, as follows:

Vaults London

Profiles CustomerDB Payroll

Tokyo

CustomerDB Payroll

Preferred Vaulting StrategiesSeveral strategies can help you reduce resource and time contention when you back up your data and when you vault your backup media. Although these strategies may not be advantageous for all situations, they can be very beneficial in many environments. VERITAS recommends that you use one of the following: Vault the original NetBackup backup media. Because you can produce multiple

copies of images during a NetBackup policy job, fewer drives and less time may be required to create multiple original copies than duplicating media. Use disk staging. Send your backups to disk and then copy the data from disk to

removable media. This strategy reduces the time that the backup process uses.26 NetBackup Vault System Administrators Guide

Preferred Vaulting Strategies

Vault Original BackupsFor most situations, VERITAS 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 most situations, vaulting originals has the following advantages: Uses less drive time than duplicating backup images from the original tapes. For

example, a backup job that creates two originals of a backup image uses two drives two units of drive time. Conversely, 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. Over time, duplicating backup images consumes more drive-time than writing multiple originals during a backup job. Avoids configuring for duplication. In complex environments (such as with multiple

media servers, multiple robots, or multiple retention period requirements), it can be difficult to configure the duplication steps of Vault profiles. It is possible to send large amounts of data over the network without careful configuration, although in storage area network (SAN) environments network traffic may not be an issue. If you decide to

Date post:	12-Mar-2015
Category:	Documents
Upload:	anurag-sharma
View:	1,254 times
Download:	5 times

NetBackup Admin Guide Vault

Documents