Director Guide

EVault Software Director 7.
0 Operations Guide
Revision: This manual is updated for Version 7.01 Software Version: 7.01 (September 2012) 1997-2012 EVault Inc. EVault, A Seagate Company, makes no representations or warranties with respect to the contents hereof and specif ically dis claims any implied w arranties of merchantability or fitness for any particular purpose. Furthermore, EVault reserves the right to revise this publication and to make changes from time to time in the content hereof w ithout obligation of EVault to notif y any person of such revision of changes. All companies, names and data used in examples herein are fic titious unless otherw is e noted. No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval System or translated into any language including computer language, in any form or by any means electronic, mechanic , magnetic, optical, chemical or otherwis e without prior written permission of: EVault, A Seagate Company c/o Corporation Trust Center 1209 Orange Street Wilmington, New Castle Delaw are 19801 www.evault.com EVault, EVault Software, EVault SaaS, and EVault DeltaPro, are registered trademarks of EVault Inc. All other products or company names mentioned in this document are trademarks or registered trademarks of their respective owners. Acknow ledgements: Tw o encryption methods, DES and TripleDES, include cryptographic software written by Eric Young. The Windows versions of these algorithms also include software written by Tim Hudson. Bruce Schneier designed Blowfish encryption. Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright 2001-2006 Robert A. van Engelen, Genivia Inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT ( INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The EVault Software Agent, EVault Software CentralControl, and EVault Software Director applications have the encryption option of AES (Advanced Encryption Standard) . Advanced Encryption Standard algorithm (named Rijndael, pronounced Rain Doll) w as developed by cryptographers Dr. Joan Daemen and Dr. Vincent Rijmen. This algorithm was chosen by the National Institute of Standards and Technology (NIST) of the U.S. Department of Commerce to be the new Federal Information Processing Standard (FIPS). The EVault Software Agents and EVault Software Director applications also have the added security feature of an over the wire encryption method.
Table of Contents
Table of Contents
1 Welcome to Director 7.0 ......................................................................................................... 1 1.1 1.2 1.3 2 Whats New in Version 7.01? .................................................................................................................... 2 What's New in Version 7.0? ...................................................................................................................... 2 Additional Resources ................................................................................................................................... 2
Installing the Director ............................................................................................................. 3 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 Hardware Requirements ............................................................................................................................ 3 Software Requirements .............................................................................................................................. 3 32-bit and 64-bit Support ............................................................................................................................ 3 Default Storage Policies ............................................................................................................................. 4 Inbound and Outbound P ort Requirements ......................................................................................... 4 Permission Requirements .......................................................................................................................... 5 Changing the Local Security Policy ........................................................................................................ 6 Installing the Vault and Director Management Console .................................................................. 6 Installing the Director Management Console ...................................................................................... 7 Improving Director Performance .............................................................................................................. 7 Automatically Created Directory Paths .................................................................................................. 7 Automatically Created S ervices ............................................................................................................... 8 Silently Installing the Vault and Director Management Console ................................................... 8 Silently Upgrading, Patching, and Repairing a Vault ........................................................................ 9
Upgrading the Director ......................................................................................................... 10 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 Upgrading Vaults to Version 7.0 ............................................................................................................ 10 Vault Manager Workspace Files ............................................................................................................ 11 License Verification .................................................................................................................................... 11 Upgrading with the Vault Running ........................................................................................................ 12 Upgrading Vaults for Replication ........................................................................................................... 12 Upgrading Standalone Vaults for Replication ................................................................................... 12 Upgrading Dual Vaults for Replication ................................................................................................. 13 Upgrading Vaults in 1:1 Replication ..................................................................................................... 14 Upgrading Vaults in N:1 Replication .................................................................................................... 15 Manually Upgrading Microsoft SQL Server Express ...................................................................... 15
Director 7.0 Operations Guide 3.11 3.12 3.13 3.14 4 Recreating Delta Files ............................................................................................................................... 16 Repairing a Vault ......................................................................................................................................... 16 Installing a Patch ......................................................................................................................................... 17 Uninstalling the Director ........................................................................................................................... 17
Adding and Activating Licenses........................................................................................... 18 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 Viewing Licensing Information ................................................................................................................ 18 Adding a License Key ................................................................................................................................ 18 Activating a License Online ..................................................................................................................... 18 Requesting a License Activation Code ................................................................................................ 19 Entering a License Activation Code ..................................................................................................... 19 Activating a License Manually ................................................................................................................ 20 Removing a License Key ......................................................................................................................... 20 Using Customer License Quotas ........................................................................................................... 21 Working with Expired Licenses .............................................................................................................. 21 Viewing License Quotas ........................................................................................................................... 21 Reclaiming a License ................................................................................................................................ 22
Introduction to the Director .................................................................................................. 23 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 Director Components ................................................................................................................................. 24 Director Vault Types .................................................................................................................................. 24 Vault Backup Agent .................................................................................................................................... 25 EVault Reports Extractor .......................................................................................................................... 26 Agent Registration and Re-Registration ............................................................................................. 26 Agent Licensing ........................................................................................................................................... 26 Vault Access ................................................................................................................................................. 28 Vault Passwords .......................................................................................................................................... 28 Preventive Maintenance ........................................................................................................................... 29
The Backup Life Cycle.......................................................................................................... 31 6.1 6.2 6.3 6.4 Backup ............................................................................................................................................................ 31 Migration ........................................................................................................................................................ 31 Optimization .................................................................................................................................................. 32 Data Retrieval .............................................................................................................................................. 32
ii
Table of Contents 6.5 6.6 7 Archiving ......................................................................................................................................................... 33 Diagnostics .................................................................................................................................................... 33
Getting Started with the Director .......................................................................................... 34 7.1 7.2 Starting the Director Management Console ...................................................................................... 34 Vault Data Hierarchy .................................................................................................................................. 35
Working with Workspace s and Vault Connections............................................................... 37 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 Creating a New Workspace ..................................................................................................................... 37 Opening a Workspace ............................................................................................................................... 37 Setting Workspace Options ..................................................................................................................... 37 Encrypting a Workspac e .......................................................................................................................... 38 Renaming a Workspace ........................................................................................................................... 39 Deleting a Workspace ............................................................................................................................... 39 Creating a New Vault Connection ......................................................................................................... 40 Restricting Vault Access ........................................................................................................................... 42
Working with Customers ...................................................................................................... 43 9.1 9.2 9.3 9.4 Adding a Customer ..................................................................................................................................... 43 Deleting a Customer .................................................................................................................................. 43 Setting Customer License Quotas ........................................................................................................ 43 Filtering the Customer List in a Vault ................................................................................................... 44
10
Working with Locations........................................................................................................ 45 10.1 10.2 10.3 10.4 10.5 Adding a Location ....................................................................................................................................... 45 Creating a New Loc ation Code .............................................................................................................. 45 Editing a Loc ation Code ........................................................................................................................... 46 Deleting a Location Code ......................................................................................................................... 46 Deleting a Location ..................................................................................................................................... 46
11
Working with Safesets.......................................................................................................... 47 11.1 11.2 11.3 11.4 11.5 Viewing Safesets ......................................................................................................................................... 47 Viewing and Editing Safeset Properties .............................................................................................. 48 Changing the Retention Settings of Multiple Safesets ................................................................... 50 Importing Safesets ...................................................................................................................................... 50 Deleting Safesets ........................................................................................................................................ 51
iii
Director 7.0 Operations Guide 12 Working with Accounts ........................................................................................................ 52 12.1 12.2 12.3 13 Creating a New Account ........................................................................................................................... 52 Changing Account Properties ................................................................................................................. 52 Deleting an Account ................................................................................................................................... 53
Working with Users .............................................................................................................. 54 13.1 13.2 13.3 13.4 13.5 13.6 Adding a New User .................................................................................................................................... 54 Changing Us er Properties ........................................................................................................................ 54 Changing Network Storage Credentials .............................................................................................. 55 Disabling a User .......................................................................................................................................... 56 Enabling a User ........................................................................................................................................... 56 Deleting a User ............................................................................................................................................ 57
14
Working with Registered Computers and Ta sks .................................................................. 58 14.1 14.2 14.3 14.4 14.5 14.6 Viewing Registered Computer Properties .......................................................................................... 58 Deleting a Registered Computer ........................................................................................................... 58 Enabled, Disabled and Suspect Tasks ................................................................................................ 59 Disabling a Task .......................................................................................................................................... 60 Enabling a Disabled or Suspect Task .................................................................................................. 61 Deleting a Task ............................................................................................................................................ 62
15
Managing Storage Groups and Locations ............................................................................ 63 15.1 15.2 15.3 15.4 15.5 15.6 15.7 15.8 15.9 15.10 15.11 15.12 Managing the Primary Storage Group ................................................................................................. 63 Changing the Maximum Pool File Size for the Primary Storage Group .................................. 64 Adding a Storage Location to the Primary Storage Group ........................................................... 64 Universal Naming Convention (UNC) Support ................................................................................. 65 Removing Storage Locations from the Primary Storage Group ................................................. 66 Viewing Primary Storage Group Location Policies and Settings ................................................ 66 Adding and Editing Location Policies for the Primary Storage Group ...................................... 67 Assigning a Location Policy to a Storage Location ......................................................................... 68 Deleting a Location Policy ........................................................................................................................ 68 Setting Vault Warning and Critical Threshold Limits ...................................................................... 69 Managing Secondary Storage Groups and Loc ations ................................................................... 69 Adding a Secondary Storage Group .................................................................................................... 70
iv
Table of Contents 15.13 15.14 15.15 15.16 15.17 15.18 15.19 16 Removing a Secondary Storage Group .............................................................................................. 70 Changing the Maximum Pool File Size for a Secondary Storage Group ................................ 71 Adding a Storage Location to a Secondary Storage Group ......................................................... 71 Removing a Storage Location from a Secondary Storage Group ............................................. 72 Managing Archive Locations ................................................................................................................... 73 Adding an Archive Location ..................................................................................................................... 73 Removing an Archive Location .............................................................................................................. 73
Managing Safesets and Pools .............................................................................................. 74 16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 16.9 Enforcing Safeset Retention Policies ................................................................................................... 74 Optimizing Pool Files ................................................................................................................................. 76 Setting the Minimum Pool Usage Parameter .................................................................................... 78 Verifying the Integrity of Backup Files ................................................................................................. 79 Copying and Cloning Data ....................................................................................................................... 80 Moving Data .................................................................................................................................................. 84 Migrating Safesets to Secondary Storage .......................................................................................... 84 Exporting Safesets ..................................................................................................................................... 86 Exporting Safesets using the vvexport Command .......................................................................... 88
17
Managing Safesets and Pools in Secondary Storage ........................................................... 89 17.1 17.2 17.3 17.4 17.5 17.6 17.7 17.8 Assigning Secondary Storage Groups to Tasks .............................................................................. 89 Applying Safeset Retention Settings to the Secondary Storage Pool ...................................... 90 Secondary Storage Deletion and Retention ...................................................................................... 91 Automatic Retention Management in the Secondary Pool ........................................................... 91 Secondary Storage Maintenance .......................................................................................................... 92 Closing a Secondary Storage Pool ....................................................................................................... 92 Detaching a Secondary Storage Pool ................................................................................................. 92 Attaching a Secondary Storage Pool ................................................................................................... 93
18
Archi ving Data...................................................................................................................... 94 18.1 18.2 18.3 18.4 Assigning an Arc hive Storage Location to a Task ........................................................................... 94 Archiving Safesets to Disk ....................................................................................................................... 94 Recalling Safesets ...................................................................................................................................... 95 Archiving Tasks ........................................................................................................................................... 95
Director 7.0 Operations Guide 19 Acti vating Automated Maintenance...................................................................................... 97 19.1 19.2 19.3 19.4 19.5 19.6 19.7 20 Verifying Automated Maintenance is Running .................................................................................. 97 Stopping Automated Maintenance ........................................................................................................ 98 Verifying Maintenance Performance .................................................................................................... 98 Viewing Maintenance Logs ...................................................................................................................... 98 Changes Affecting Current Versions of the Vault ............................................................................ 99 Scheduling Vault Maintenance ............................................................................................................. 100 Enabling Automated Secondary Storage Maintenance ............................................................... 100
Managing the Vault............................................................................................................. 102 20.1 20.2 20.3 20.4 20.5 20.6 20.7 20.8 20.9 20.10 20.11 20.12 20.13 20.14 20.15 20.16 20.17 20.18 20.19 20.20 20.21 Viewing the Job Monitor ......................................................................................................................... 102 Pinning the Job Monitor to your Desktop .......................................................................................... 102 Stopping a Job ........................................................................................................................................... 102 Setting the Number of Concurrent Jobs ............................................................................................ 103 Viewing a Log File from the Job Monitor .......................................................................................... 103 Setting Email Notifications ..................................................................................................................... 103 Changing a Registered Computer's Agent Type ........................................................................... 104 Requesting an Alert Notification .......................................................................................................... 104 Changing the Purge Log Setting ......................................................................................................... 104 Modifying Advanced Vault Settings .................................................................................................... 105 Modifying Agent Connection Settings ................................................................................................ 106 Changing the Time that a Scheduled Service Runs ..................................................................... 106 Creating a Custom Scheduled Entry .................................................................................................. 106 Disabling a Scheduled Entry ................................................................................................................. 107 Enabling a Scheduled Entry .................................................................................................................. 107 Removing a Scheduled Entry ............................................................................................................... 107 Starting a Vault Service .......................................................................................................................... 107 Stopping a Vault Service ........................................................................................................................ 108 Purging Activity Records and Logs ..................................................................................................... 108 Backing up a Vault with dbB ackup ..................................................................................................... 109 Backing up a Vault with VBA ................................................................................................................ 109
vi
Table of Contents 21 Creating and Running Reports ........................................................................................... 110 21.1 21.2 21.3 21.4 21.5 21.6 21.7 21.8 21.9 21.10 21.11 21.12 21.13 22 Running a Storage, Storage Location or Last Backup Status Report ..................................... 110 Creating a Storage Report ..................................................................................................................... 111 Creating a Storage Location Report ................................................................................................... 113 Creating a Vault Storage Report ......................................................................................................... 115 Creating a Last Backup Status Report .............................................................................................. 116 Creating a Late Server Status Report ................................................................................................ 117 Creating a Missed Backups Report .................................................................................................... 118 Creating a Storage Pool Summary Report ...................................................................................... 120 Selecting the Destination for a Report ............................................................................................... 122 Selecting the Scope for a Report ........................................................................................................ 123 Creating Schedules for Running Reports ......................................................................................... 124 Viewing Reports ........................................................................................................................................ 125 Viewing a Storage Pool Summary Report for a Task ................................................................... 126
Working with Log Files....................................................................................................... 127 22.1 22.2 22.3 22.4 22.5 22.6 22.7 22.8 22.9 Understanding Log Message Codes .................................................................................................. 127 Selecting the Log Files to Display ....................................................................................................... 129 Viewing Log Files ...................................................................................................................................... 129 Viewing Spawn Logs ............................................................................................................................... 130 Viewing License Logs .............................................................................................................................. 130 Viewing Replication Logs ....................................................................................................................... 130 Viewing Server Logs ................................................................................................................................ 131 Purging Log Files ...................................................................................................................................... 132 Scheduling a Log File Purge ................................................................................................................. 132
23
One-to-One (1:1) Replication .............................................................................................. 133 23.1 23.2 23.3 23.4 23.5 23.6 23.7 Installing an Active Vault for 1:1 Replication ................................................................................... 135 Installing a Passive Vault for 1:1 Replication .................................................................................. 135 Setting up Connections Between Active and Passive Vaults in 1:1 Replication ................ 136 Creating a Schedule for 1:1 Replication ........................................................................................... 137 Running an Unscheduled Replication in a 1:1 Configuration .................................................... 137 Allowing or Pausing 1:1 Safeset Replication for a Customer, Location or Computer ....... 138 Allowing or Pausing 1:1 Safeset Replication for a Task .............................................................. 138 vii
Director 7.0 Operations Guide 23.8 23.9 23.10 23.11 23.12 23.13 24 Disabling and Enabling 1:1 Replication Services on a Vault ..................................................... 139 Disabling Over-the-Wire Encry ption for 1: 1 Replication .............................................................. 139 Implementing Bandwidth Throttling for 1:1 Replication ............................................................... 140 Viewing 1:1 Replication Activity and Progress ............................................................................... 140 Running Replication Reports in a 1:1 Confi guration ..................................................................... 141 Failover from an Active to a Passive Vault in 1:1 Replication ................................................... 143
Many-to-One (N:1) Replication ........................................................................................... 144 24.1 24.2 24.3 24.4 24.5 24.6 24.7 24.8 24.9 24.10 24.11 24.12 24.13 24.14 24.15 24.16 24.17 24.18 24.19 24.20 Installing a Base Vault for N:1 Replication ....................................................................................... 146 Configuring Satellite Vaults for N:1 Replication on the Bas e Vault ......................................... 146 Installing and Registering a Satellite Vault for N:1 Replication ................................................. 147 Replacing a Failed S atellite Vault in N:1 Replic ation ................................................................... 148 Creating a Schedule for N: 1 Replication ........................................................................................... 149 Running an Unscheduled Replication in an N: 1 Configuration ................................................. 150 Disabling and Enabling N:1 Replication Services on a Vault .................................................... 150 Disabling Over-the-Wire Encry ption for N:1 Replication ............................................................. 151 Many-to-One (N:1) Replication and Dual Network Connections .............................................. 151 Implementing Bandwidth Throttling for N:1 Replication .............................................................. 152 Setting the Replication P olicy for a Satellite Vault in N:1 Replication .................................... 152 Setting the Retention Policy for a Satellite Vault in N:1 Replication ....................................... 153 Setting the Operating Mode for a Satellite Vault in N:1 Replication ........................................ 153 Setting the Operating Mode for a Customer, Location or Computer in N:1 Replic ation .. 154 Setting the Operating Mode for a Task in N:1 Replication ......................................................... 155 Setting the Heart beat Interval for a Satellite Vault in N:1 Replication .................................... 156 Assigning Settings Control to a Sat ellite Vault in N:1 Replication ........................................... 156 Viewing N:1 Replication Activity and Progress ............................................................................... 157 Stopping N:1 Replication Processes and Services ....................................................................... 158 Running Replication Reports in an N:1 Configuration ................................................................. 158
25
Many-to-One-to-One (N:1:1) Replication............................................................................. 160 25.1 25.2 25.3 Installing an Active Base Vault for N:1:1 Replic ation ................................................................... 163 Installing a Passive Base Vault for N:1:1 Replication .................................................................. 164 Setting up Connections Between Active and Passive Base Vaults in N:1:1 Replication ...... ......................................................................................................................................................................... 165
viii
Table of Contents 25.4 25.5 25.6 25.7 25.8 25.9 25.10 25.11 25.12 25.13 25.14 25.15 25.16 Configuring Satellite Vaults for N:1:1 Replication on the Active Base Vault ........................ 165 Installing and Registering a Satellite Vault for N:1:1 Replication ............................................. 166 Replacing a Failed S atellite Vault in N:1:1 Replication ................................................................ 167 Creating N:1:1 Replication Schedules ............................................................................................... 168 Running an Unscheduled Replication in an N: 1:1 Configuration ............................................. 169 Disabling and Enabling Replication Services on a Vault in N:1:1 Replication ..................... 169 Disabling Over-the-Wire Encry ption in N: 1:1 Replication ........................................................... 170 Many-to-One-to-One (N:1:1) Replication and Dual Network Connections ........................... 171 Implementing Bandwidth Throttling for N:1:1 Replication ........................................................... 171 Setting the Replication P olicy for a Satellite Vault in N:1:1 Replication ................................. 172 Setting the Retention Policy for a Satellite Vault in N:1:1 Replication .................................... 173 Setting the Operating Mode for a Satellite Vault in N:1: 1 Replication .................................... 173 Setting the Operating Mode for a Customer, Location or Computer in N:1:1 Replication .... ......................................................................................................................................................................... 174 25.17 25.18 25.19 25.20 25.21 25.22 25.23 26 Setting the Operating Mode for a Task in N:1:1 Replication ..................................................... 175 Setting the Heart beat Interval for a Satellite Vault in N:1:1 Replication ................................ 176 Assigning Settings Control to a Sat ellite Vault in N:1:1 Replication ........................................ 176 Viewing N:1:1 Replication Activity and Progress ........................................................................... 177 Stopping N:1:1 Replication Proc esses and Services ................................................................... 179 Running Replication Reports in an N:1:1 Configuration .............................................................. 180 Failover from an Active to a Passive Base Vault in N: 1:1 Replication ................................... 182
Working with QuickShip Vaults .......................................................................................... 183 26.1 26.2 26.3 26.4 26.5 26.6 26.7 26.8 26.9 Installing a QuickShip Vault ................................................................................................................... 183 Creating a QuickShip Profile ................................................................................................................. 184 Initializing a QuickShip Vault ................................................................................................................. 185 Exporting Data to a QuickShip Vault .................................................................................................. 185 Importing Data from a QuickShip Vault ............................................................................................. 187 Completing a Large Initial Seed ........................................................................................................... 187 Completing a Large Reseed ................................................................................................................. 188 Completing a Large Restore ................................................................................................................. 188 Using a QuickShip Vault to Export Data for Seeding ................................................................... 189
ix
Director 7.0 Operations Guide 26.10 26.11 27 Using a QuickShip Vault for Dis aster Recovery ............................................................................. 190 QSM Import Storage Location Selection .......................................................................................... 190
Command Reference .......................................................................................................... 192 27.1 27.2 27.3 27.4 27.5 27.6 27.7 27.8 27.9 27.10 27.11 27.12 27.13 27.14 27.15 27.16 27.17 agentinforeports ......................................................................................................................................... 193 dbbackup ..................................................................................................................................................... 194 migrates econdary ..................................................................................................................................... 195 qsm ................................................................................................................................................................ 198 replvault ........................................................................................................................................................ 199 secondaryop ............................................................................................................................................... 202 vaultop .......................................................................................................................................................... 207 vvanalyz ....................................................................................................................................................... 209 vvarchive ...................................................................................................................................................... 215 vvcopy ........................................................................................................................................................... 216 vvex port ........................................................................................................................................................ 218 vvimport ........................................................................................................................................................ 220 vvmigrat ........................................................................................................................................................ 221 vvmove ......................................................................................................................................................... 222 vvpoolop ....................................................................................................................................................... 224 vvpurge ......................................................................................................................................................... 227 vvrecall .......................................................................................................................................................... 229
Welcome to Director 7.0
Welcome to Director 7.0
The EVault Software Director provides backup storage and data recovery services to remote computer systems with EVault Software Agents. It is an online "data vault", which can reside locally (on a LAN) or across a WAN (Internet). The Director application controls the vault, securely manages and catalogs backup files, and monitors backup processes. This diagram shows the relationship bet ween different EVault Software products :
Quickship
Offline Backup Offline Restore Export
EVault Reporting System

Reports via Web Browser
Import Online Restore Online Backup
Agent
Director Vault
Synch Web
Agent
VBA
Primary Pool Data
Web or Windows CentralControl

Management of Agents and Jobs
Director Console (GUI)

Agent
Network Attached Storage

Secondary Pool data
The arrows illustrate the communication paths of a typical standalone EVault Soft ware Director installation. The Director vault, Agents, and CentralControl are the primary components of the data protection application. You use these components to back up and restore system and file data from your net work computers to a local or remote vault. Thes e applications protect your dat a without the need for tape devic es or other non-disk backup media. This document is intended for vault administrators who are responsible for installing, configuring, and maintaining the EVault Soft ware Director. This document assumes an intermediate knowledge of operating and administering the EVault Software Director.
Page 1
Director 7.0 Operations Guide
1.1
Wh ats New i n V ersion 7 .0 1 ?

To ensure that customers have unique location codes that can also be used in billing, location codes can now range from 5-20 characters in length. Previously, location codes could only be 5 characters long. For more information, see Creating a New Location Code.
1.2
Wh at's New i n V ersion 7 .0 ?

The Director now supports many-to-one-t o-one (N:1:1) replication, where Satellite vaults collect backup data from Agents, data is replicated automatically to an Active Base vault, and is then replicated from the Active Base vault to a Passive Base vault. For more information, see Many-toOne-to-One (N:1:1) Replication. The Vault API has been changed to support vaults with more than one replication role (i.e., Active Base vault, Passive Base vault). To maximize the use of available bandwidth and more clearly show the progress of replication activities, the Director now supports multiple conc urrent sessions for replicat ing configuration, metadat a and backup data. If a large amount of safeset data is being replicat ed for one task, Configuration, Metadata and Task replication sessions for ot her tasks can start and finish while the large task is still running. Configuration replication sessions have priority to run over ot her sessions, and Metadata replication sessions have priority over Task replication. You can view the progress of each replication session in the Job Monitor, and view separate logs for each replication activity. For more information, see Viewing 1:1 Replication Activity and Progress, Viewing N:1 Replication Activity and Progress, Viewing N:1: 1 Replication Activity and Progress, and Viewing Replication Logs. You can now only enable a suspect task if task pool data problems have been resolved. When you try to enable a suspect task, the Director checks the physical and logical integrity of task data and only enables the task if there are no issues. In previous versions, the Director did not check for data integrity issues when you enabled a suspect task. For more information, see Enabling a Disabled or Sus pect Task and vvpoolop. The Director now allows random read access to safesets, which will enable users to recover specific files and folders. Agents that use this functionality will be releas ed in 2012. Replication is now supported for vaults that are version 6.21d and later. The Director no longer supports replication for vaults version 6.04 or earlier.
1.3
Addition al Reso u rces
Release not es for this product are available from your servic e provider. Release notes cont ain the most current information about the product, including an overview of new features, any known defect (bug) fixes incorporated since the last release, and a description of any known issues.
Page 2
Installing the Director
This section provides information for installing, upgrading, and repairing EVault Software Director on a Microsoft Windows Server. The Director installation kit contains: Director vault Director Management Cons ole You can install the Director Management Console on the same or a different computer than the Director vault. You can have multiple Director Management Console instances running on different computers. When you install the Director vault, a separate instance of the vault database is installed. When you attempt to access help files on a computer with a Microsoft Windows Vista, Windows 7, or Windows Server 2008 operating system, a "Failed to launch help" message appears. To open help files, download and install the WinHlp32.exe file from the Microsoft website.
2.1
Hardw are Req ui rements
An EVault Software Director installation requires a minimum of 1,700 MB of disk space. A minimum of 1,400 MB must be available on the system volume and 300 MB is required for the Director. A minimum of 4 GB of RAM is required for the vault. However, for optimal vault performance it is recommended that you install a minimum of 16 GB of RAM. For assistance determining your hardware requirements, contact Support.
2.2
Software R eq uirem ent s
To install EVault Software Director you must install and configure these applications: Microsoft Windows Server Microsoft Internet Explorer (on the Director Management Console computer) TCP/IP stack .NET Framework and Microsoft Data Access Components (MDA C) Refer to the EVault Soft ware Director release not es for a list of supported software versions.
2.3
32-bit an d 64 -bit S uppo rt
EVault Software Director 7.0 automatically installs native 64-bit code on support ed 64-bit machines. If you currently have a 32-bit Director running on a 64-bit machine, it is upgraded to the 64-bit version.
Page 3
2.4
Def ault Storag e Policies
When you install EVault Software Director, the default storage policies for disk space are enabled. The minimum free space required for the system disk is 20 GB. If the system disk has less than 20 GB of free space, the system policy automatically disables maintena nce. If you increase the free space, or change the system policy, you must manually enable maintenance.
2.5
Inbo und and Outbou nd Port Requi rements
The following table lists the ports that the EVault Soft ware Director uses:
Port Number 809 TCP Admin service (communication with Director Management Console). External and inbound requirement. 2546, 807 2547/12547 TCP TCP Listener ports for backups and restores. Command and data ports for many-to-one (N:1) replication for all Satellites to this Base vault. (*) 2547/12547 TCP Command and data ports for one-to-one (1:1) replication. (*) (*) for Replication only Note: In N:1:1 replication, the same command and data ports are used for replication from Satellite vaults to the Active Base vault, and from the Active Base vault to the Passive Base vault. You cannot specify different ports for N:1 and 1:1 replication. Y N Y N N N N N Protocol Description Configurable? Optional?
Note: The vault allows outbound connections (usually TCP port 1433) for Web Reporting System programs.
Page 4
Agent CentralControl 808
Vault Director GUI
2546 Agent 808
809
- Represents a dynamically assigned port.
Communication bet ween CentralControl and the Agents is encrypted. Communication bet ween Agents and the vault is encrypted when Over The Wire (OTW) encryption is enabled.
2.6
Pe rmi ssio n R equi rem ents
The following table describes the permissions required by vault applications:

Software Director Function Installation Minimum Permissions Windows Administrator permissions Vault services require the "Log on as a service" right to run. Director Using the Director Management Console For Operator permissions, users must be members of a local Administrators group or a domain VaultAdmins group. For Salesperson permissions, users must be members of a local or domain Sales group and not be members of a local Administrators group or domain VaultAdmins group. For more information, see Restricting Vault Access. Upgrades Windows Administrator permissions
The EVault Software Director installation can fail if the "Log on as a service" right to the VaultService account cannot be assigned. This failure occurs on computers that are part of a domain and if there is a domain group policy that restricts assigning "Log on as a service" rights. To correct this issue, you can: Remove the domain group policy that assigns the "Log on as a service" right before installing EVault Software Director. During install ation, use an account that already has the "Log on as a service" right assigned.
Page 5
2.7
Ch angi ng th e Loc al S ec urit y Poli cy
For the Management Console to work correctly on a Microsoft Windows XP (SP 3) operating system, you need to change the local security policy to Classic. By default, the local security policy setting is Guest Only. To change the local security policy: 1. 2. 3. 4. 5. 6. 7. Click Start and then Control Panel . Double-click Administrative Tools. Double-click Local Security Policy. Expand Local Policies in the left pane. Click Security Options. Scroll to Network access: Sharing and security model for local accounts in the right pane. Right -click Network access: Sharing and security model for local accounts and select Properties. 8. 9. Select Classi c - local users authenticate as them selves in the Network acce ss list. Click OK.
2.8
Inst allin g the Vault and Directo r M an ag em ent Consol e
Before you start the EVault Software Director installation, it is recommended that you disable the automatic restart for Windows automatic updates. Automatic restarts can interrupt critical proc esses. After you verify that Jobs are not being proc essed, you can manually restart to apply Windows updates. To install the vault and Director Management Console: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 2. 3. 4. Select Vault and Management Console [together on thi s machine] and click Next. Complete the EVault Software Director Setup wizard. Click Finish.
Page 6
2.9
Inst allin g the Di recto r Management Co nsole
A license is not required when you install the Management Console without the vault. To install the Director Management Console: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 2. 3. 4. Select Management Console only [the Vault is on a different machine] and click Next. Complete the EVault Software Director Setup wizard. Click Finish.
2.1 0
Imp rovi ng Di re ctor Perform anc e
To improve the performanc e of the Director, you can optimize Windows performance for background services. To optimize the Windows for background services: 1. 2. 3. 4. 5. 6. 7. Click Start, Settings, and then Control Panel . Double-click System . Click the Advanced tab. Click Performance Options. Select Background service s in the Application response area. Click OK. Click OK again.
2.1 1
Autom atic ally Created Di recto ry Path s
When you install EVault Software Director, the following directories are created: Admin contains GUI programs and Help. Bill contains Location data and files. Conf cont ains Director configuration files. Database contains vault database files. Docs contains various documents in PDF files. Logs contains log files created by various server programs.
Page 7
Director 7.0 Operations Guide Prog cont ains all the Director's executable programs. Utils contains vaultop.exe. For more information, see vaultop.
2.1 2
Autom atic ally Created Servi ces
When you install EVault Software Director, these services are automatically initialized and started: Admin Service authorizes requests from Console to vault. Listener waits for customer connection requests and then spawns a Director process. Queue Manager monitors and manages Director specific job queues. Note: Stopping the Queue Manager servic e stops any jobs that have started. When you start the Queue Manager again, the jobs start again. As a result, you may see two operations running and two logs generated, one of which will have errors, and one that should be successful. Replication Service cont rols and runs vault replication for 1:1, N:1 and N:1:1 replication configurations. Note: This service starts automatically for vaults that are licensed for replication. Scheduler monitors and spawns regular scheduled Director functions.
2.1 3
Silentl y I nst alling t he V ault and Di rector Manag em ent Con sole
You can silently install a single standalone vault. A silent installation does not display any indication of its progress. The silent installation creates a new account named VaultService wit h administrative privileges. Vault services run under this account. The installation fails when you attempt to run services with a custom account. The Installer returns zero for a successful installation and a return code when the installation fails. If the installation fails, the reason for the failure is added to the log file. Online activation is the only supported method of validating licenses during a silent installation. If the vault cannot access the activation server, the installation fails. There is no license validation for Satellite vaults in interactive or silent mode. The silent installer ignores the BASEVAULT and OTRK entries on the Satellite registration window. To silently install the vault and Director Management Console: 1. Navigate to the location of the InfoStageDirector_Fres h.iss response file. This file is available from your service provider. 2. Open the InfoStageDirector_Fresh.iss file and enter your license key in the US E_YOUR_ LICENS E_KEY field.
Page 8
Installing the Director 3. Enter the locations for the vault installation fol der, the vault database engine folder, and the vault database data folder in the C:\Program Files\ field. 4. 5. Save your changes and close the InfoStageDirector_Fresh.iss file. Open a command prompt and run this command: InfoStageDirector.exe /s /f1.\InfoStageDirector_Fresh.iss KeepBackup NoRegSAT These are the command parameters: InfoStageDirector.exe the filename for the Director installer InfoStageDirector_Fresh.iss the filename for the silent installer the .\ after /f1 indicates that the response file is located in the same folder as the installer KeepBackup (Optional) keeps the backup files and folders after the installation NoRegSAT (Optional) removes the option to register the Satellite vault with the Base vault
2.1 4
Silentl y Upg rading , P atc hing , and Rep ai ring a Vault
You can silently upgrade, patch or repair a vault. A silent upgrade, patch or repair does not show any indication of its progress. To silently upgrade, patch, or repair a vault: 1. Open a command prompt and run the following command: InfoStageDirector.exe /s /f1.\SA-Repair-Patch-Upgrade.iss KeepBackup NoRegSAT These are the command parameters: InfoStageDirector.exe the filename for the Director installer SA-Repair-Patch-Upgrade.iss the filename for the silent installer the .\ after /f1 indicates that the response file is located in the same folder as the installer. KeepBackup (Optional) keeps the backup files and folders after the installation NoRegSAT (Optional) removes the option to register the Satellite vault with the Base vault 2. For Satellite vaults, register the satellite on the Base vault.
Page 9
Upgrading the Director
This section provides information and procedures for upgrading EVault Soft ware Director. EVault Software Director 7.0 is compatible with Agents version 5.0 and later. Replication is supported for vaults version 6.21d and later. It is recommended that you upgrade EVault applications in this order: Vault Cent ralCont rol Agent Plug-ins
3.1
Upgradin g V aults to Versio n 7. 0
On supported 64-bit operating systems, you can upgrade Director version 6.22 (32 -bit) or 6.31 (64-bit ) to Director version 7.0 (64-bit). Before upgrading a vault, review the Director 7.0 release notes and verify that the vault computer meets the minimum requirements for memory, disk space, hardware, and software. It is also recommended that you back up the vault with the Vault Backup Agent (VBA). You cannot upgrade a version 5.53 vault to a version 7.0 vault. However, you can upgrade a version 5.53 vault to a version 6.04 vault, and a version 6.04 vault to a version 6.2 vault. An upgrade cannot continue if files are open, or services are running that need to be replaced. You will see a message to stop any running processes or applications. When you upgrade the vault, a backup copy of the Schedule.cfg file is created. The backup file is named Schedule.cfg_BAK1. You can open this file and manually add your custom items. If an upgrade fails, new directories are added to the Director installation folder. The new directories are prefaced with ~Admin, ~conf, ~database, ~prog, and ~registry. You can use these directories to reverse an unsuccessful upgrade. You can delete these directories if you do not need to reverse an unsuccessful upgrade. If you have deduplication turned off (the default setting), the pool system is not upgraded. However, new backups have the new format. If deduplication is turned on, you can convert the entire pool system to the new system. The time required for the conversion depends on the amount of dat a and your hardware configuration. All pool files are verified for physical corruption during the upgrade. After an upgrade, existing Agents and jobs continue to function and your older vault licenses remain valid. You can restore new and previous backups.
Page 10
Upgrading the Director To upgrade a vault to version 7.0: 1. Review the Director 7.0 release notes and verify that the vault computer meets the minimum requirements for memory, disk space, hardware, and software. 2. Back up the entire vault with the Vault Backup Agent (VBA). Include system state and program files with the backup. If you are not using VBA, run dbBackup before upgrading your installation. 3. 4. Stop the Listener service. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 5. 6. Select Upgrade and click Next. Complete the EVault Software Director Setup wizard. If you are upgrading a Satellite vault, on the Evault Software Director Setup Type page, select the Do not perform reregistration on Base Vault option. 7. 8. Click Finish. Check that the vault services are running.
3.2
Vault Man age r Works pac e Fil es
The MyWorkspace. vmw file is stored in the My Documents folder. If you are upgrading an earlier version of EVault Software Director, the MyWorkspace file is copied to this location. You do not need Administrator permission to run the Director Management Console (VMA dmin.exe) and write to the MyWorkspace file.
3.3
Licen se Ve rifi catio n
When you run the installation program to patch, repair, or upgrade the Director, the program contacts the license activation server to verify that your vault license is current and valid. If the license activation server validates the vault license, the patch, repair, or upgrade continues. If the license activation server indicates that the licens e is invalid, the patch, repair, or upgrade is rolled back. If the license activation server is unavailable, you must validate the license manually. For more information, see Activating a License Manually. If the manual activation is unsuccessful, contact your service provider.
Page 11
3.4
Upgradin g with th e V ault Ru nni ng
During an upgrade, the installation attempts to stop all vault services. If there are backups or restores in progress, the VVServer service cannot be stopped and the following message appears: Could not stop the process In the Job Monitor, the status of backup and restore jobs is Running. If there are Jobs running, you can retry the upgrade when the backups or restores finish. Do not start new backups or restores while you are waiting for current jobs to finish. In addition, to prevent the vault from accepting new jobs, verify that the EVault Soft ware Listener is stopped. Before you start an upgrade, you should also verify that the Director Management Cons ole is not running.
3.5
Upgradin g V aults for R eplic ation
When you upgrade vaults in one-to-one, many-to-one, and many-to-one-to-one replication scenarios, you must upgrade vaults that receive replicated data before upgrading the sourc e vaults. Data cannot be replicated bet ween vaults if the target vault is an earlier version than the source vault. For example, in a many-to-one scenario, you must upgrade the Bas e vault before upgrading the Satellite vaults. In a manyto-one-to-one scenario, you must upgrade the Passive Base vault, then the Active Base vault, and then the Satellite vaults. After you upgrade the Passive vault in a one-to-one replication scenario, the Active vault will continue to work at the earlier version until it is upgraded. However, failover will not function correctly until the Active vault is upgraded to the same version as the Passive vault. Similarly, in a many -to-one-to-one replication scenario, an Active Base vault will work at the earlier version but failover will not function correctly until it is upgraded.
3.6
Upgradin g St and alon e V ault s fo r R eplic ation
You can upgrade a standalone vault to version 7.0 and set up replication with the vault i n a one-to-one (1:1), many-to-one (N:1) or many-t o-one-to-one (N:1: 1) scenario. To upgrade a standalone vault to a 1:1 configuration: 1. 2. 3. Upgrade the existing standalone vault to version 7.0. This vault will act as the Active vault. Install a second vault to act as the Passive vault. On the Active vault and Passive vault, add the same Replication One to One license.
To upgrade a standalone vault to an N:1 configuration: 1. 2. Upgrade the existing standalone vault to version 7.0. This vault will act as t he Base vault. On the Base vault, add a Replication Many to One license.
Page 12
Upgrading the Director 3. 4. On the Base vault, add a satellite license for each Satellite vault. Install Satellite vaults. Each Satellite vault must be a new installation with no existing data.
To upgrade a standalone vault to an N:1:1 configuration: 1. 2. 3. Upgrade the existing standalone vault to version 7.0. This vault will act as the Active Base vault. Install a second vault to act as the Passive Base vault. On the Active Base vault and on the Passive Base vault, add the same Replication One to One license and Replication Many to One license. 4. On the Active Base vault and on the Passive Base vault, add a satellite license for each Satellite vault. 5. Install Satellite vaults.
3.7
Upgradin g D ual Vaults fo r Repli catio n
You can upgrade a dual vault configuration to a one-to-one (1: 1), many-t o-one (N:1) or many-to-one-toone (N:1:1) replication scenario. Because dat a is not synchronized between vaults in a dual vault configuration, you can only upgrad e one of the vaults for replication. The other vault or vaults must be newly installed, and populated with data from the upgraded vault. To upgrade dual vaults to a 1:1 configuration: 1. 2. 3. 4. Upgrade one of the existing vaults to version 7.0. This vault will act as the Active vault. Uninstall the other existing vault, and delete all Agent jobs that were directed to this vault. Install a second vault to act as the Passive vault. On the Active vault and Passive vault, add the same Replication One to One license.
To upgrade dual vaults to an N: 1 configuration: 1. 2. 3. 4. 5. Upgrade one of the existing vaults to version 7.0. This vault will act as the Base vault. Uninstall the other existing vault, and delete all Agent jobs that were directed to this vault. On the Base vault, add a Replication Many to One license. On the Base vault, add a satellite license for each Satellite vault. Install Satellite vaults. Each Satellite vault must be a new installation with no existing data.
To upgrade dual vaults to an N: 1:1 configuration: 1. 2. Upgrade one of the existing vaults to version 7.0. This vault will act as the Active Base vault. Uninstall the other existing vault, and delete all Agent jobs that were directed to this vault.
Page 13
Director 7.0 Operations Guide 3. 4. Install a second vault to act as the Passive Base vault. On the Active Base vault and on the Passive Base vault, add the same Replication One to One license and Replication Many to One licens e. 5. On the Active Base vault and on the Passive Base vault, add a satellite license for each Satellite vault. 6. Install Satellite vaults.
3.8
Upgradin g V aults i n 1: 1 R eplic ation
You can upgrade both vaults in a one-t o-one (1:1) configuration, or set up many -to-one (N:1) or many-toone-to-one (N:1: 1) replication with the vaults. To upgrade vaults in a 1:1 configuration: 1. 2. Upgrade the Passive vault to version 7. 0. This vault will continue to act as the Passive vault. Upgrade the Active vault to version 7.0. This vault will continue to act as the Active vault.
Note: The Active vault will work at the earlier version until it is upgraded. However, failover will not function correctly until the Active vault is upgraded to the same version as the Passive vault. To upgrade vaults from 1:1 replication to an N:1 configuration: 1. 2. 3. 4. 5. 6. Upgrade one of the existing vaults to version 7.0. This vault will act as the Base vault. Uninstall the other existing vault. On the Base vault, remove the existing Replication One to One license. On the Base vault, add a Replication Many to One license. On the Base vault, add a satellite license for each Satellite vault. Install Satellite vaults. Each Satellite vault must be a new installation with no existing data.
To upgrade vaults from 1:1 replication to an N:1:1 configuration: 1. 2. 3. Upgrade the Passive vault. This vault will act as the Passive Bas e vault. Upgrade the Active vault. This vault will act as the Active Base vault. On the Active Base vault and Passive Bas e vault, add the same Replication Many to One replication license. Note: The vaults should already be licensed for 1:1 replication 4. 5. On the Active Base vault and Passive Bas e vault, add a satellite license for each Satellite vault. Install Satellite vaults.
Page 14
3.9
Upgradin g V aults i n N:1 Repli catio n
You can upgrade both vaults in a many-to-one (N: 1) configuration, or set up many-to-one-t o-one (N:1:1) replication with the vaults. To upgrade vaults in an N:1 configuration: 1. 2. Upgrade the Bas e vault to version 7.0. Upgrade each Satellite vault to version 7.0.
To upgrade vaults from N:1 replication to an N:1:1 configuration: 1. 2. 3. Upgrade the Bas e vault to version 7.0. This vault will act as the Active Base vault. Install another vault to act as the Passive Bas e vault. On the Active Base vault and the Passive Base vault, add the same Replication One to One license and Replication Many to One license. 4. Upgrade each Satellite vault to version 7.0.
3.1 0
Manu ally Up gradin g Mic roso ft S QL S erv er E xp ress
Director 7.0 uses Microsoft SQL Server 2008 R2 Express (X86) for the vault database. When you upgrade the Director, existing instances of Micros oft SQL Server Express are automatically upgraded to Microsoft SQL Server 2008 R2 Express (X86). If the Microsoft SQL Server Express upgrade fails during the Director upgrade, you must manually upgrade SQL Server Express. You can also install a full version of Microsoft SQL Server 2008 R2 for the EVAULT_DB dat abase. When you install Director 7. 0, it detects the Microsoft SQL Server Express 2008 R2 Express (X86) database, connects to it with Windows authentication, and resets the SA password. An SA account is required to connect the vault to the database. To manually upgrade Microsoft SQL Server Express: 1. Install Microsoft SQL Server Express 2008 and select these options: Name the dat abase EVAULT_DB. Choose mixed mode authentication. 2. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 3. 4. 5. Select Vault and Management Console [together on thi s machine] and click Next. Complete the EVault Software Director Setup wizard. Click Finish.
Page 15
3.1 1
Rec reati ng D elt a Fil es
Version 6 and lat er vaults recognize version 6 Agents that use delta recreation, if a DTA file is missing or corrupted. However, older backups from version 5 Agents do not have this functionality. Delta files can be recreated only if a backup was done by a version 6 Agent to a version 6 or later vault. If you upgrade a version 5 vault to a version 6 or later vault, a version 6 Agent may attempt delta recreation on these older files. This attempt at delta recreation results in error messages in the log file, but the restore succeeds. To correct the error messages, you can us e the /forcereseed command to force a reseed. The /forcereseed command is not available in the CentralControl console. During a backup, the Agent determines if the vault supports delta recreation. When backing up to disk, the Agent assumes that the vault does not support delta recreation, and the delt a mapping information is not included with the backup data. If you first back up (seed) to disk, and then import the data into the vault the delta recreation information is not included. All subsequent backups (deltas) of that Job inclu de the delta recreation as part of the backup.
3.1 2
Rep ai ring a V ault
Before you repair a vault, verify that you do not have any tasks scheduled to run during the upgrade. In addition, you should close the Director Management Console before you start the repair. To repair a vault: 1. 2. 3. Back up the entire vault with the Vault Backup Agent (VBA). Stop the Listener service. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVa ult Software products, or visit the Support website. 4. 5. 6. 7. Select Repair and click Next. Complete the EVault Software Director Setup wizard. Click Finish. Check that the vault services are running.
Page 16
3.1 3
Inst allin g a Patch
Before you install a patch, verify that you do not have any backups, restores, pool optimizations, or migrations running. In addition, you should close the Director Management Console before you install the patch. To install a patch: 1. 2. 3. Back up the entire vault with the Vault Backup Agent (VBA). Stop the Listener service. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 4. 5. 6. Select Patch and click Next. Complete the EVault Software Director Setup wizard. Click Finish. Note: After installing a patch, you can run the vvpoolop ssiverone subcommand to verify online safesets. For more information, see vvpoolop. 7. Check that the vault services are running.
3.1 4
Uninst allin g th e Di rector
Uninstalling EVault Software Director removes the Director programs, services, and most of the configuration data from the vault. However, you must remove the backup data manually. When you uninstall EVault Soft ware Director, you can choose to keep the existing databas e files. The database files are named Vault.ldf, and Vault.mdf, and are usually saved in the <...> \Director\database directory. To uninstall the vault and the Director Management Console: 1. 2. 3. 4. 5. 6. 7. Click Start and then Control Panel . Double-click Add or Remove Programs. Click EVault Software Director. Click Remove . Complete the EVault Software Director Setup Maintenance wizard. Click Finish. Restart the computer.
Page 17
4
4.1
Adding and Activating Licens es

Viewin g Lic ensi ng Info rm ation
Each vault has a vault license. Additional licenses are required for Agents, Plug-ins, replication and other features. You can use a quota to limit a customers access to features and functionality. See Setting Customer Licens e Quot as. If you have not activated a license, a warning message appears in the Activation Status field. See Activating a License Online or Activating a License Manually. To view license information: 1. 2. 3. From the Vault Maintenance menu, choose Vault Settings. Click the License Summary tab. Click OK.
4.2
Addin g a Li ce nse K ey
To add a license key: 1. 2. 3. 4. 5. 6. From the Vault Maintenance menu, choose Vault Settings. Click the License Summary tab. Click Manage Licenses. Enter or paste the license key in the top pane. Click Add License Key(s). Click OK.
4.3
Activ ating a Lic en se Onlin e
To activate a license online, the computer must be connected to the Internet. To activate a license online: 1. 2. 3. 4. 5. 6.
Page 18
From the Vault Maintenance menu, choose Vault Settings. Click the License Summary tab. Click Manage Licenses. Select a license key in the License Key list. Click Online Activation. If your activation is unsuccessful, contact your service provider. Click OK.
Adding and Activating Licenses
4.4
Req ue sting a Lic en se Activ ation Cod e
After requesting a licens e activation code from your service provider, you can enter the code. For more information, see Entering a License Activation Code. To request a license activation code: 1. 2. From the Vault Maintenance menu, choose Vault Settings. On the License Summary tab, click Manage License s. The Licenses dialog box appears. 3. Click Manual Activation. A message asks whether you have an activation code. 4. Click No. The Manual License Activation dialog box shows activation request text. 5. Click Save To Text File. In the Save As dialog box, choose a location for the text file and click Save . 6. 7. Click OK. Send your activation request to your servic e provider to get an activation code.
4.5
Ente ring a Lic en se Activ ation Cod e
This procedure describes how to enter a license activation code. You must request the license activation code from your service provider. For more information, see Requesting a License Activation Code. To enter a license activation code: 1. 2. From the Vault Maintenance menu, choose Vault Settings. On the License Summary tab, click Manage License s. The Licenses dialog box appears. 3. 4. 5. 6. 7. Click Manual Activation. Click Yes. Click Open From File to paste the activation code from a text file. Click Activate Now . Click OK.
Page 19
4.6
Activ ating a Lic en se Manu ally
To activate a license manually: 1. 2. From the Vault Maintenance menu, choose Vault Settings. On the License Summary tab, click Manage License s. The Licenses dialog box appears. 3. 4. 5. 6. 7. 8. 9. Select a license key in the License Key list. Click Manual Activation. Click No. Click Save to Text File to save the activation request as a text file. Click OK. Open your Internet browser and navigate to the license activation site (license.evault.com). Click Browse and browse to the location of your activation request text file.
10. Click Activate License . 11. Click Download Activation Key. 12. Activate the license manually and select Ye s when the Do you have an activation code for thi s specific computer prompt appears. See Entering a License Activation Code.
4.7
Re movin g a Li cens e K ey
Before you remove a license key, verify that it is not in use. See Viewing Licensing Information. To remove a license key permanently: 1. 2. From the Vault Maintenance menu, choose Vault Settings. On the License Summary tab, click Manage License s. The Licenses dialog box appears. 3. 4. 5. 6. Select a license key in the License Key list. Click Remove License Key(s). Click Yes. Click OK.
Page 20
Adding and Activating Licenses
4.8
Using Cu stome r Li cense Quotas
You can use quotas to limit the amount of storage and number of Agent and plug-in licenses that a customer can use. If you are using N:1 or N:1: 1 replication, you must set customer quotas. If you are using Satellite vaults, customer quotas need the correct Agent type. If the customer quota doe s not allow sufficient Desktop Agents, the license claim fails even if there is a customer quot a available for Server Agents. To adjust customer quotas on satellites, you must make the adjustments on the Base vault (BAV). To set quotas for a specific organization, see Setting Customer License Quotas. To set quotas: 1. 2. 3. 4. From the Vault Maintenance menu, choose Vault Settings. Click the License Summary tab. Select a license type in the License Type list. Click Use per-customer quotas. If you are using N:1 or N:1:1 replication, this option is enabled by default and cannot be changed. 5. 6. Click Yes. Click OK.
4.9
Workin g with E xpired Li cens es
When your License Activation expires, you can complete backups, but you cannot perform restores, imports, or exports. If you exceed the pool size, you can complete backups, imports, and exports, but you cannot perform restores. If the Agent count exceeds the activation limit, tasks created by new Agents cannot be run. Existing backups, restores, imports, and exports are allowed. Agents registered on computers without tasks, are not considered in the total number of Agents calculation.
4.1 0
Viewin g Lic ens e Quot as
To view the license quot a for a registered computer: 1. 2. 3. 4. 5. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location.
Page 21
Director 7.0 Operations Guide 6. 7. 8. 9. Expand the Regi stered Computers list. Right -click a registered comput er and select Properties. Click the License Quota s tab. Click OK.
4.1 1
Recl ai ming a Lic en se
A reclaimed license is assigned back to the vault license pool and can be claimed by another computer. To reclaim a license: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location. Expand the Regi stered Computers list. Right -click a registered comput er and select Properties. Click the License Quota s tab. Select a quota and click Reclaim.
10. Click OK.
Page 22
Introduction to the Director
Introduction to the Director
The EVault Software Director controls and manages the pooling and storage of data at a secure vault location. Agent computers use a LAN, a WAN, or the Internet to send backup data to the vault. The primary purpose of the Director is to protect corporate computer data. You can create scheduled or ad-hoc backups and restores with the Windows or Web Cent ralCont rol graphical user interface. You can also export backup data on removable media. With Delta technology, only the Agent data that has changed from the previous backup is sent to the vault. Deltizing is an Agent technology that tracks the changes within a backup file, and transmits only those changes to the vault. On the vault, a corresponding mechanism reconstructs the deltized files. The Director creates a database that indexes changes across versions of dat a, allowing you to reconstruct the data upon request. Director security features protect your data from unauthorized access. A three-part authorization sequence must be passed before a user can access Director services. Over-the-wire (OTW) encryption is used for all communications to and from the vault. To enhance security, you can choose to encry pt the backup data on your local computers with a secret password. When you use a secret password, the entire cryptographic process and key management is unknown to the Director, and independent of the Director process. To provide additional security, you can implement IP address or host name verific ation. To ensure the int egrity of your backup dat a, the Director performs a multi-level verification (block, stream, and file) of each backup to detect processing or transmission errors. In addition, the Director periodically schedules analysis and verification tasks to monitor and maintain the validity of backup data. To manage the large volumes of backup data submitted by multiple Agents, the Director us es a specialized storage pooling system (primary and secondary). A pool is a collection of safesets, stored in such a way that there is only one physical copy of the common segments of data. In combination with standard dat a compression techniques, a large number of safesets in a pool typically occupies less space on the vault than the original data did on the source computer. By managing pool indices, the Director maintains backup dat a in its deltized and compressed format. Pool file optimization reduces the overall storage volume on the vault, reduc es processor overhead and data movement, and improves backup and verification times. Computers that meet the minimum hardware requirements for a vault installation are capable of managing significant amounts of backup data.
Page 23
5.1
Directo r Co mpon ent s
The Director includes the following two components: Vault You use the Director vault to collect, store, collate, and verify backup dat a. You can also use the Director vault to restore backup data. A single vault typically stores data in thousands of tasks, from hundreds of systems. You can use a single Director vault installation to store dat a from one or multiple organizations. The hardware on which you install the Director vault determines the amount of backup dat a you can store. The Director vault can store a maximum of 2 TB of data per task, and a maximum of 1 TB of dat a per safes et. Director Management Cons ole The Director Management Console is the graphical user interfac e (GUI) used for managing the vault, scheduling automated tasks, and monitoring activities. You can use the Director Management Console to control a single vault or multiple vaults. You can install the Director Management Console on the same comput er as the vault, or on a local or remote Microsoft Windows computer that meets the minimum hardware requirements. You cannot use an earlier version Director Management Console to manage a later version vault. The console must be the same version or a later version.
5.2
Directo r V ault Typ es
When you install the Director, you can select these vault types: Single vault A standalone vault, or, with the appropriat e licensing, a Base vault to which Satellite vaults can replicate. With licensing, a standalone vault can become an Active, Passive, Active Base, or Passive Base vault. Vault replication allows you to replicate backup data from an Active vault to a Passive vault. If the main vault fails, the backup dat a is available on the secondary vault. This is one -to-one (1:1) replication. If your organization has multiple offices and Agents, you can use the Internet to send backup data from Satellite vaults to a central Base vault. This many -t o-one (N:1) replication is available with Director version 6 and later. You can also replicate data from Satellite vaults to an Active Bas e vault and then to a Passive Base vault. This many-to-one-to-one (N:1:1) replication is available with Director version 7.0.
Page 24
Introduction to the Director Director version 5.53 and earlier allowed only a standalone vault. When you inst alled a second vault, it had its own Agents. Each vault installation operated independently and information was not shared with other vault installations. To create an additional copy of your backup, you used the Vault Backup Agent (VBA) to back up the entire vault. QuickShip vault A specialized, portable vault that physically transports data between a vault data center and an office location. Satellite vault A local cache that can replic ate backup data to a Base vault. To improve efficiency, you can config ure Agents to send backup data to Satellite vaults installed at each of your local offices. You configure the Satellite vaults to send the backup data to a centralized Base vault. With this methodology, backup data is available locally for local restores and replicated on the Base vault. Local users can independently back up and restore dat a from the local Satellite vault. If the local vault fails, the user can use the Int ernet to back up and restore data from the Base vault. The retention period on the Bas e vault is usually longer than the retention period on Satellite vaults and you can restore backup data from this location if necessary.
5.3
Vault Backup A gent
You use the Vault Backup Agent (VBA) to do a full or partial backup of vault data to another vault, or a local disk. To use VBA, you must purchas e a license. VBA allows you to access these vault data components: configuration files log files registry settings vault databases web extract files agent task files task metadata (log files, catalog files, activity files) task pool data (primary storage pool)
Page 25
5.4
EVault Re port s Ext ractor
EVault Reports Extractor is a separate, optional application that runs on a vault. You can use it to gather information from the vault database, and send it to a web-reporting program for analysis.
5.5
Age nt R egist ration and R e- Regi stration
Registration is the process that occurs when you first configure an Agent. When you enter parameters such as your user ID, password, and vault address, the computer and its Agent is automatically registered to the vault. The vault can then recognize the Agent and allow backups and restores. When a registered Agent connects to a vault, the Agent is displayed as a registered computer in the left pane of the Director Management Console. If you need to re-register a computer, such as after a bare -metal restore or Agent reloc ation, you can change the authentication information. When you re-register the Agent, the vault sends new configuration files to the Agent.
5.6
Age nt Lic ensi ng
You use the vault to manage licensing for Agents and plug-ins. To run a backup, there must be enough licenses on the vault. Contact your service provider to purchase additional licenses. On vault versions 5.53 and later, a quota system is used to control Agent licensing. When an Agent connects to a vault, the vault automatically supplies the license. Licenses are required for most Agents, plug-ins, and other A gent products that use a vault. When an Agent connects to a vault, the quota system determines what tasks you can perform. For example, you might be allowed to: Create Jobs Perform backups or restores If you have insufficient licensing on the vault, the following error messages might appear when you connect an Agent to a vault: Vault storage limit exceeded. Vault limit for Agent type exceeded, or type not found. Vault limit for Plug-In type exceeded, or type not found. Customer Quota for Plug-In type exceeded (Agent 5.6 and above only).
Page 26
Introduction to the Director The following table shows the tasks you can perform on the vault when an error or warning message appears:
Version If Vault base license is invalid Agent (pre-5.6) Registration Allow Job Creation Backup Restore Disallow Allow Allow Allow Disallow Client Key Client Key N/A N/A If Vault storage If Vault limit for If Vault limit for plug-in type is exceeded If customer quota for plug-in type is exceeded
limit is exceeded Agent type is exceeded
Allow Disallow
Allow Disallow
N/A N/A
Client Key Client Key
N/A N/A
Agent (5.6 and above) Registration Allow Job Creation Backup Restore Disallow Allow Allow Allow Warn Allow Warn Allow Warn
Disallow* Disallow
Allow Disallow
Disallow* Disallow*
Disallow* Disallow*
Disallow* Disallow*
System I (pre-5.6) Registration Allow Job Creation Backup Restore Disallow Allow Allow Client Key Disallow N/A N/A N/A N/A
Allow Disallow
Allow Disallow
N/A N/A
N/A N/A
N/A N/A
* If the Agent already has a claim on the necessary licenses (it has previously done a backup of that type), the backup or restore operation is allowed. Client Key refers to an older licens e key that has been installed on the Agent. The vault does not use this key.
Page 27
5.7
Vault Acc es s
The following four access levels control vault access: Organization/Customer Location Account User To allow customers to back up to the vault, you must configure their Organization/ Customer, Location, Account, and User.
5.8
Vault Pass word s
On the Director, passwords are required in these locations: Vault connection password You use this password to allow the Director application to access the vault. This is a Windows authentication. Director users can have Operator or SalesPerson permissions. Users with Operat or permissions are members of a local Administrat ors group or a domain VaultAdmins group, and can access all menus in the Director Management Console. Users with SalesPerson permissions are members of a local or domain Sales group, but do not belong to a local Administrators group or the domain VaultAdmins group. Users with SalesPerson permissions have limited access to the Director Managem ent Console. Account/User Name/Password Used by an A gent task to execute backups and restores. Created by the vault administrator and given to the user. If the user los es or forgets their password, the vault administrator can issue a new one. This connection uses application authentication. The account, user name, and password are us ed on CentralControl to run backup or restore tasks. Multiple users with different passwords can access the same vault account. Workspace password Protects all other passwords and access to user information on the vault configured in that workspace. The password is set on a workspace in the Director Management Cons ole. Users that have access through another workspac e may also have access to the same passwords on the same vaults. If the password is lost, the user must create the Workspac e again.
Page 28
Introduction to the Director Encryption password The Agent may use an encryption password on backup data (safesets) on the vault. This password is known only to the user who encry pts the data. The passwords are not stored. This password also protects data going across the net work. If the encryption password is lost, the backup data is inaccessible. If you do not use an encryption password, you may optionally use over the wire encryption (with or without using a data enc ryption password) to secure data going across the network. You can turn over the wire encryption on or off. Over the wire encryption does not require any user supplied passwords or encryption methods. QuickShip (QSM) profile password A QSM vault has vault connection information. This needs to be reflected in the QSM profile on the main vault that will be exporting data to the QSM vault. This profile needs the IP address, or Host name, and the User name and password to access the QSM vault.
5.9
Prev enti ve Mai nte nanc e
To help ensure the safety of your data and optimal performance of the EVault Software Director, it is recommended that you complete the following tasks: Back up your vault Use the Vault Backup Agent to back up Director pool files and metadata. Alternatively, you can use vault replication to back up your vault data. Check Free Space The comput er on which you installed the vault must have enough storage for the backup. A full volume can cause the backup to fail. It is recommended that you add additional storage capacity when you us e more than 75% of your total vault storage space. With EVault Software Director version 6.2 and lat er, you can set policies to limit the amount of disk space to use, and creat e an email notification that notifies you when a volume reaches a defined maximum. Check the Job Monitor By default, the Director application runs 25 jobs at one time. You can raise or lower the maximum number of jobs the Director can run. If you lower the job number, you should check the job monitor daily for thes e issues: Stalled or unresponsive jobs. When this occurs, you do not receive a notification. A backed up job queue. This can occur when too many jobs stall or are running simultaneously. Ideally, the vault should be able to process its job allotment and the job queue should not remain full. If the job monitor remains full throughout the day, or it cannot catch up from evening to evening, you should check the storage performance, memory and CP U usage on the computer on which you installed the vault.
Page 29
Director 7.0 Operations Guide To raise or lower the number of jobs: 1. 2. 3. 4. 5. Open the EVault Software Director. Click Vault Settings. Click the Advanced tab. Enter or select a new number in the Maximum number of jobs field. Click OK.
Check Vault Notifi cations It is recommended that you activate notifications when you install and configure the vault. When you activate notifications, you receive an email notification when a job fails. Early notification allows you to quickly identify and correct job failures and pool system issues. Schedule Vault Jobs Verify that scheduled vault maintenance jobs including migration, optimization, purging and database backup are configured and running correctly.
Page 30
The Backup Life Cycle
The Backup Life Cycle
Backup data is stored on the vault in safesets, and can move through the follo wing phas es: Backup Migration Optimization Data Retrieval Archiving Diagnostics The phases are not always sequential, and safesets do not always pass through every phase.
6.1
Bac ku p
Agents send backup dat a to the Director. A Listener service on the Director listens for new Agent connections. When an Agent connects to the Director, the Listener starts a server proc ess. The server process authenticates the Agent credentials, and receives, sync hronizes and commits the backup. The vault then disconnects from the Agent, and dat a is available for restoring. Each backup is saved in primary storage as a safeset. A safeset is an instance of backup data with defined retention policies and other properties. The first backup from an Agent is a complete copy of the data, or full seed. In subsequent backups, the vault indexes changed data blocks against previous safesets to create full backups that require less disk space on the vault. Backup and Listener log files are created during the backup phas e. The log files are stored in the Task Logs folder.
6.2
Migration
The migration phase enforces the retention policy for each safeset and determines when safesets should be moved from primary storage. A migration runs by default on the entire vault once a day. However, you can run a migration at any time. It is recommended that you do not disable the default migration schedule. In addition, you should run optimization once a week. Running regular migrations and optimiz ations removes unnecessary safesets and cons erves storage space. A migrate log file is created during migration. The log file is stored in the Global Logs folder when the migration runs on multiple systems or in the Task Logs folder when the migration runs on a single task.
Page 31
6.3
Optimi zatio n
The optimization process ensures that the vault uses the smallest amount of storage possible. It removes pool system data that is no longer referenc ed by any safesets, defragments the pool, and uses the Minimal Pool Usage setting to combine valid data int o new pool files. Backups that have not been successfully updated are not migrated. Archive backups are expired when the number of archived days is reached. The optimization phase starts when the migration phase identifies ex pired data. This process ensures that the vault retains only valid safesets and that the vault only uses the spac e required by valid safesets. By default, deduplication runs every week. The deduplication process deletes all data blocks that are the same (except for one), and updates references to point to the same common block. Use vault storage reports to review what data blocks deduplication removed. Deduplication cannot run when a backup Job changes the encryption or compression type, or encryption password. If the parameters are not changed, deduplication can run on the next backup of the same Job. The optimizer log file is created during the optimization phase. The log file is stored in the Global Logs folder when the optimization runs on multiple systems or in the Task Logs folder when the optimization runs on a single task. Pool system is the term used to describe the total set of data and metadata stored on the vault for a specific task. All backup data is stored in a proprietary compressed format. Fi le compression allows you to protect multiple versions of data with a minimal inc reas e in pool system size. Deduplication, or common block pooling, inside the primary pool helps reduce the vault storage requirements. You use a retention policy to define ho w long to keep a specific data version or safeset before removing or arc hiving it. The retention policy you define on the A gent is assigned to the safes et when the backup starts. Every time the vault receives a new safeset, the Director checks to see if this new safeset affects the retention schedule of other safesets for that Job. When its retention date is reached, data is removed or arc hived.
6.4
Dat a R et rie val
You use a restore process to retrieve data. The system uses the pool index to rebuild a virtual co py of the data. The pool index contains pointers to pool files that contain the data. Data is retrieved in the sequence in which it existed when it was backed up. The restore process uses the TCP/ IP network to transmit backup data to the Agent. The ex port process uses a removable medium. You can run a restore on an online safes et at any time after a backup completes.
Page 32
The Backup Life Cycle A proprietary Safeset Image (SS I) format is used to transmit backup files. When the Agent rec eives the formatted data, it converts it to the original format. A restore log file is creat ed during the data retrieval phase, and is stored in the Task Logs folder.
6.5
Arc hivi ng
When migration enforces safeset retention policies, it removes or archives safesets. You can archive a safeset to disk, or to removable media. A propriet ary Safeset Image (SSI) format is used to transmit arc hived safesets. When you arc hive a safeset, optimization removes online components and the status changes from online to offline. The synchronization database retains a reference to the archived safeset. Archive storage is intended for long -term data storage wit h a minimum lifespan of one year. To restore an archived safeset, the safeset must be recalled and written back into online storage. An archive log file is created during the arc hival phase. The log file is stored in the Task Logs folder.
6.6
Diag nostic s
To ensure that safesets are valid and that client data can be retrieved, you can use Director diagnostic tools to verify the integrity of backup data and troubleshoot issues. You can also use the diagnostic tools to check physical objects within a Pool System as well as the logical integrity of the Pool System data.
Page 33
7
7.1
Getting Started with the Director

Starting t he Directo r M an ag em ent Con sole
To start the Director Management Console, do one of the following: On the desktop, double-click the Director Management Console shortcut. In the directory where the Director Management Console is installed, double-click the VMAdmin.exe file. The Director Management Console appears. As shown below, the Cons ole has two panes. The left pane displays vault connections. The right pane displays detailed information about items you select in the left pane.
Page 34
Getting Started with the Director
7.2
Vault Dat a Hie rarchy
Data is represented in a hierarc hy in the left pane of the Director Management Console. The following table lists and describes levels in the hierarchy, and shows icons that represent each level in the Director Management Console.
Level in Hierarchy Icon Workspace
Description A container (physically, a .vmw file) with vault connections. You can create different workspaces to group different vaults. You can password protect a workspace.
Vault connection
Connection to a standalone vault. Vault connections include the network address and authentication information required to connect to the vault. Connection to an Active vault in one-to-one (1:1) replication.
Connection to a Passive vault in one-to-one (1:1) replication.
Connection to a Base vault in many-to-one (N:1) replication.
Connection to a Satellite vault in many-to-one (N:1) or many-to-one-to-one (N:1:1) replication. Connection to an Active Base vault in many-to-one-to-one (N:1:1) replication.
Connection to a Passive Base vault in many-to-one-to-one (N:1:1) replication. Customer Organization that owns the protected systems and data. There may be only one, or many different customers on a vault. Location Account/User Registered Computer Physical location (e.g., office building) of the customer. Needed to authenticate systems when they connect to the vault. System protected by the vault.
Page 35
Level in Hierarchy Icon Registered cluster of VMware ESX and ESXi hosts Task Safeset
Description Cluster of VMware ESX and ESXi hosts protected by the vault.
The backup job defined to protect selected data. Data that has been backed up. The data can be encrypted so that no one but the owner can restore the data, and no one can read the data when it is being transmitted to or from, or stored on the vault.
When an item in the hierarc hy is disabled, a red Disabled icon appears for the item in the Director Management Console. For example, the following icon appears for a disabled task: When some, but not all, items lower in the hierarc hy are disabled for an item, a yellow Warning icon appears for the item. For example, in the following screen, the task named B ackup is disabled and yellow Warning icons appear for the tasks computer, location and customer.
Page 36
Working w ith Workspaces and Vault Connections
Working with Workspaces and Vault Connections
You can create workspaces to organize vault connections into logical groups. For example, you can create workspac es for individual company departments. However, you can only have one workspace open at a time. For more information, see Creating a New Workspace, Opening a Workspace and Creating a New Vault Connection. When you open the Director application for the first time, the default workspace is named MyWorkspace. It is recommended that you change this name.
8.1
Cre ating a New Works pace
You can create as many workspaces as required to represent logical groups in your vault environment. To create a new workspace: 1. 2. 3. 4. 5. From the File menu, choos e New Workspace . Select the workspace in the left pane of the Director Management Console. From the File menu, choos e Save Workspace As. Enter a name for the workspace in the File Name field. Click Save.
8.2
Op enin g a Wo rkspace
To open a workspac e: 1. 2. 3. From the File menu, choos e Open Workspace . Browse to the location of the workspace (. vmw) file. Click Open.
8.3
Settin g Wo rksp ac e Options
By setting workspace options, you can specify the logs that appear in the workspac e and frequency of refres hing workspace data. To set workspac e options: 1. 2. Select a workspace in the left pane of the Director Management Console. From the View menu, choose Options.
Page 37
Director 7.0 Operations Guide 3. 4. Edit the fields in the Options dialog box. For field descriptions, see Options Dialog Box Fields. Click OK.
8.3.1
Options Dialog Box Fields
The following fields appear in the Options dialog box:

Field Automatically reload last workspace on startup Auto-refresh tree for selected vault every Update executing jobs information every Show Spawn Logs and License Logs Show Replication Logs Show Server Logs Default text viewer Displays Replication Logs below a vault connection in the left pane. Displays Server Logs below a vault connection in the left pane. The default text viewer to use to open log files and other reports. Description Opens the current workspace when you close and then reopen the Director application. The frequency in minutes that the vault refreshes and information in the left pane updates. You can enter values from 60 to 32767. The default is 60. The frequency in seconds that job information updates. You can enter values from 60 to 32767. The default is 30. Displays Spawn Logs and License Logs below a vault connection in the left pane.
8.4
Encrypting a Works pace
Workspaces contain system names, usernames and passwords that allow vault access. You can encrypt a workspace to prevent unauthorized access. You must enter a password each time you open an encrypted workspace. Note: Encrypting a workspace does not affect backup data in any way. Note: If you forget a workspace password, you will need to re -create the workspace. You do not need the encryption password to delete the workspace. To encrypt a workspace: 1. Right -click a workspace in the left pane of the Director Management Console, and choose Encrypt Workspace from the menu. 2. Enter your existing password in the Old Password field.
Page 38
Working w ith Workspaces and Vault Connections 3. 4. Select an encryption type in the Encryption Type list. Enter a new password in the New Password field. If you forget this password, you must recreate the workspace. 5. 6. Enter the new password in the Confirm Password field. Click OK.
8.5
Re naming a Works pac e
To rename a workspace: 1. 2. 3. 4. Select a workspace in the left pane of the Director Management Console. From the File menu, choos e Save Workspace As. Enter a name for the workspace in the File Name field. Click Save.
8.6
Del eting a Wo rksp ac e
To permanently delete a workspace, you must remove the workspace file from the Director. Workspace files are saved with the . vmw (Vault Manager Workspace) extension. To delet e a workspace: 1. In Windows Explorer, browse to the location of the workspace (. vmw) file. By default workspace files are saved in the following locations: For Microsoft Windows 2008 and earlier operating systems: Documents and Settings\< somepoweruser>\My Documents\EVault InfoStage For Microsoft Windows Vista and Microsoft Windows 7 operating systems: Users\< somepoweruser>\My Documents\EVault Infostage 2. 3. Right -click the workspace file and select Delete . Click Yes.
Page 39
8.7
Cre ating a New V ault Con nection
You can create multiple vault connections in the same workspace. You can also test vault connections to see if they are working and accessible, and to obt ain Version information. To create a new vault connection: 1. 2. From the File menu, choos e New Vault Connection . Complete fields in the Vault Connection Properties dialog box. For field descriptions, see Vault Connection Properties Dialog Box Fields. 3. Click Get Status to test the vault connection. For field descriptions, see Vault Status Screen Fields. If the DNS or IP information is incorrect, the following message appears: Failed to connect to <...> If the authorization information is incorrect, the following message appears: Failed to authorize user () or user () possesses insufficient privilege. 4. Click OK.
8.7.1
Vault Connection Properties Dialog Box Fields
The following fields appear in the Vault Connection Properties dialog box:
Field Description Network address Use Windows Authentication Use Default Credentials Description A descriptive name for the vault connection. The IP address or Domain Name System (DNS) name for the vault computer. If selected, the username and password of the currently-logged-on Windows user are used to log in to the vault. If selected, default credentials are used to log in to the vault. With default credentials, one domain account and saved password can be used for multiple vaults in the domain. To change the default credentials, click Edit in the dialog box or, from the File menu, choose Set Default Credentials .
Page 40
Working w ith Workspaces and Vault Connections
Field Use Custom Credentials
Description If selected, custom domain name, username, and password are used to log in to the vault. To save the custom credentials, select Save password.
Note: When Save password is selected, the password is not stored in the workspace file. If
you copy the workspace to another computer, you must re-enter the default credentials. You can have more than one workspace with saved credentials on the same system.
Caution: If you save the password, be sure to encrypt the workspace so that an unauthorized
person cannot use the workspace to gain vault access. See Encrypting a Workspace.
8.7.2
Vault Status Screen Fields
The following fields appear on the V ault Status screen:

Label Type Version Operating system System name The host name of the computer on which the vault is installed. Service process number IP address Build date Unique Identifier The Internet Protocol (IP) address for the vault connection. The date and time the Director was published. A system-generated number. A system generated number for the task. Description The type of vault installed. The version and build number of the Director. The name and version of the operating system on which the vault is running.
Page 41
Label Access level
Description These options are available: OPERATOR SALESPERSON Users with Operator permissions are members of a local Administrators group or a domain VaultAdmins group, and can access all menus in the Director Management Console. Users with SalesPerson permissions are members of a local or domain Sales group, but do not belong to a local Administrators group or a domain VaultAdmins group. Users with SalesPerson permissions have limited access to the Director Management Console. For more information, see Restricting Vault Access .
8.8
Re stricti ng V ault Acc es s
Access to a vault is restricted using Operator and SalesPers on permissions. Users wit h Operator access have full vault access. Users with SalesPerson access have limited, primarily read -only, access to the vault. When a user logs in to a vault, the system assigns permissions using the following rules: If a user logs in with valid credentials and is a member of a domain VaultAdmins group or local Administrators group, the user is assigned Operator access to the vault. If a user logs in with valid credentials and is a member of a Sales domain group or Sales local group, but is not a member of a domain VaultAdmins group or local Administrators group, the user is assigned SalesPerson access to the vault. If a user does not meet either of the criteria above, the us er is not granted access to the vault.
Page 42
Working w ith Customers
Working with Customers
To allow an Agent to access vault data you must add a customer. After you add a customer, you can add locations, accounts, and users. For more information, see Adding a Customer and Setting Customer Lic ense Quotas.
9.1
Addin g a Cu stom er
To add a new customer or organization: 1. 2. 3. 4. 5. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Right -click Manage Customers/Orgs, Safesets, Ta sks and select Add New Customer. Complete the New Organization/Customer wizard. Click Finish.
9.2
Del eting a C usto mer
Note: You cannot restore a customer that has been delet ed. To temporarily disable tasks and us ers for a customer rat her than deleting the customer permanently, see Disabling a Task. To delet e a customer: 1. 2. 3. 4. 5. 6. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand Manage Customers/Orgs, Safesets, Ta sks. Right -click a customer and select Delete . Enter YES and click OK. Click OK again.
9.3
Settin g C ustom er Licens e Quot as
You can use customer license quotas to limit the amount of storage or number of Agents and plug-ins that a specific customer can us e. If you are using N:1 or N:1:1 replication, you must set customer quotas. To set license quotas for a customer: 1. 2. Select a workspace in the left pane of the Director Management Console. Expand a vault connection.
Page 43
Director 7.0 Operations Guide 3. 4. 5. 6. 7. Expand Manage Customers/Orgs, Safesets, Ta sks. Right -click a customer and select Properties. Click the Quota s tab. Select a feat ure (Storage, or a type of Agent or plug-in) and click Set Quota . Select Unlimited or enter a quota number in the Set quota area. You can assign a quota number that exceeds the available licens es. If the licens e quot a is reached, the following message appears: The total quota for this feature exceeds the amount licensed for the vault. A gents may fail even though customer level quot a is not exceeded, if total usage exceeds the licensed amount. 8. 9. Click OK. Click OK again.
9.4
Filte ring t he Cu stomer Li st in a V ault
Using a filter, you can specify which vault customers to show in the left pa ne of the Director Management Cons ole. You can filter the customer list by customer name, or by customer short name. If you specify a customer name and a customer short name, only the customers that match both criteria are displayed. After you apply a filter, the filter parameters appear in angle brackets < > after the vault name. To filter the customer list in a vault: 1. 2. 3. 4. Select a workspace in the left pane of the Director Management Console. Right -click a vault connection and select Change filter. Click Use filter. Do one or both of the following: To filter the list by customer name, ent er some or all of a customer name in the Customer name field. To filter the list by customer short name, enter some or all of the customer short name in the Customer short name field. 5. Click OK.
Page 44
Working w ith Locations
10 Working with Locations

After adding a customer, you can add locations specific to the customer. For more information, see Adding a Location and Creating a New Location Code.
10. 1
Addin g a Lo catio n
To add a new location: 1. 2. 3. 4. 5. 6. 7. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand Manage Customers/Orgs, Safesets, Ta sks. Expand the customer. Right -click Locations and select Add New Location . Complete the New Location wizard. Click Finish.
10. 2
Cre ating a New Loc atio n Cod e
When you create a location, you associate the location with a unique alphanumeric code. The code can range from 5-20 characters in length. You can use location codes to calculate storage and usage totals. Note: When using location codes longer than five characters, all vaults must be version 7.01 or lat er. Location codes can only be five characters long in Director 7.00 and earlier versions. Note: To ensure compatibility with EVault Reports, the EVault Reports Extractor truncates location codes to five characters. To create a new location code: 1. 2. 3. 4. 5. From the Reporting menu, choos e Location Code s Admini stration . Click the Active tab. Click New . Complete the Location Code wizard. Click Finish.
Page 45
10. 3
Editing a Lo catio n Cod e
To edit a location code: 1. 2. 3. 4. 5. 6. From the Reporting menu, choos e Location Code s Admini stration. Click the Active tab. Select a location code in the Associated Location Code s pane. Click Edit. Edit the location code. Click Close .
10. 4
Del eting a Loc ation Cod e
To delet e an unassociated location code: 1. 2. 3. 4. 5. From the Reporting menu, choos e Location Code s Admini stration . Click the Delete tab. Select a location code in the Una ssociated Location Code s pane. Click Delete. Click OK.
10. 5
Del eting a Loc ation
Deleting a location deletes all computers that are assigned to the location and removes all accounts and users. Caution: You cannot restore a location that has been delet ed. To temporarily disable all tasks and users for a location rather than permanently deleting the loc ation, see Disabling a Task. To delet e a location: 1. 2. 3. 4. 5. 6. 7. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Right -click a location and select Delete . Enter YES and click OK. Click OK again.
Page 46
Working w ith Safesets
11 Working with Safesets

This section provides information and procedures for working with safesets. A safeset is sent to a vault each time a backup is successfully performed. The safeset contains the data protected in that backup session. The safeset also carries the associated backup type, data options, and retention settings. This information is used to help manage the safeset until it (optionally) exp ires. Over time, a pool of safesets develops bas ed on values specified in the retention settings. This safeset pool mak es up the backup history for a specific task. The safeset pool, when stored on a vault, is dynamic. For instance, each time a new backup is performed or a safeset expires, the pool changes. Typically this happens automatically after each backup is performed. For more information, see Viewing Safesets, Changing the Retention Settings of Multiple Safesets and Importing Safesets.
11. 1
Viewin g S af eset s
To view the safesets associated wit h a location: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the le ft pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location. Expand the Regi stered Computers list. Select and expand a comput er list. Expand Backup Ta sks. Expand a backup task.
10. Click Backups. The safesets for the location appear in the right pane. For column descriptions, see Safeset Column Descriptions.
Page 47
11.1.1
Safeset Column Descriptions
The following table provides safeset column descriptions:

Column Backup # Description System-generated backup number, starting with 0000001. Successive backups are numbered sequentially. When a backup expires, the Optimize program deletes it and recovers the disk space. Backup time Retention # Date and time the backup started on the Agent. Retention group to which the safesets belongs. Safesets can have different retention values than other safesets in the same Job. Status Status of the safeset. Each safeset can have one of the following statuses: Online the safeset is online and can be restored. Offline the safeset is archived. Recalled the archived safeset can be restored. Secondary the safeset has been moved out of primary storage to a secondary sto rage area.
Original size Compressed size Storage size
Size of all the backup data in a safeset as it appeared on the client server. Size of the safeset's original data after it went through the Delta compression. Can be thought of as the size of data if you did a full restore of every safeset that is online (for that task). Amount of space this backup is using on the vault. This includes the data (the safesets) and other supporting files, such as indexes. This is a value global to the task.
Encrypted
Specifies whether an encryption password was specified on the backup.
11. 2
Viewin g and Editing S afeset Prop erti es
You can view properties for a safeset, including identification numbers and storage location information. You can also change some safeset properties, including retention settings and backup date and time. To view and edit safeset properties: 1. 2. Navigate to the safesets pane. See Viewing Safesets. Double-click a safeset in the right pane.
Page 48
Working w ith Safesets The Safeset Properties dialog box appears. For field descriptions, see Safes et Properties Dialog Box Field Descriptions. 3. View and edit safeset properties, and then click OK.
11.2.1
Safeset Properties Dialog Box Field Descriptions
The following tabs and fields appear in the Safeset Properties dialog box:
Tab General Field Available for restore Backup number Previous backup number Serial number Retention Retention group Sequential safeset number. Sequential safeset number for the previous safeset. The number 0 (zero) indicates that the safeset is a seed. System-generated number for the safeset, used for synchronizing. Number from 0 to 15 that identifies the Retention Group to which the safeset belongs. A task can belong to different groups to attain different retention values. You can change this value. Online safesets Number of safesets available for immediate recovery and restore. You can change this value. Online days Archive da ys Location Physical location Number of days safesets are kept online. You can change this value. Number of days safesets are archived. You can change this value. System-generated Globally Unique Identifier (GUID) that identifies the location of the safeset in the vault. Location code Available options are Online (primary or secondary storage) and Offline (archive storage). Time (adjusted for GMT offset, to match local time) that the backup started. You can modify this field when there is a discrepancy. Original size Compressed size Size of the safeset before deltizing and compression. Size of the safeset after deltizing and compression. Description If selected, if the safeset is online, or recalled, and can be restored.
Statistics
Backup time
Page 49
11. 3
Ch angi ng th e Ret ention Setti ngs o f M ultiple Saf es ets
To change the retention settings of multiple safesets: 1. 2. 3. Navigate to the safesets pane. See Viewing Safesets. Press CTRL and select multiple safes ets in the right pane. Right -click a selected safeset and select Properties. The Safeset Properties dialog box appears. For field descriptions, see Safes et Properties Dialog Box Field Descriptions. 4. 5. Edit retention settings for the safesets. Click OK.
11. 4
Impo rting Safe set s
You can import exported safesets to a vault using the Import wizard. The media used to import the data is typically a CD, DVD, or a removable disk. A full copy of the dataset is stored in compressed SSI format on the media. Do not run backups before your import completes. To create SS I files for importing, you can manually backup data on an Agent system and choose removable media that is directly attached to the system as the safeset destination. Backups done in this way will always be a seed (never delta). To import these safesets, you must directly attach the media to the vault. To import a safeset: 1. 2. 3. 4. 5. Connect the media containing the safeset to the va ult. From the Storage Management menu, choose Import. Complete the Import wizard. Click Finish. Delet e the safeset files on the media.
Page 50
Working w ith Safesets
11. 5
Del eting Safe sets
Deleting a safeset makes it unavailable for restores in the future. Before deleting a saf eset, confirm with the safes et owner that you can delete it and verify that you cannot recover the data. Permission to delete the safes et may not be required if the safeset affects the integrity of the vault. Caution: You cannot recover a safeset after you delete it. However, if you are using the Vault Backup Agent (VBA) to back up vaults, you might be able to recover an older version of the data. When you delete the last safeset, the previous safeset becomes the most current safeset. Because the next safeset is a full, deltized backup, a reseed is not required. However, if you delete the t wo most recent safesets, a reseed is required for the next backup. Note: In N:1 replication, if you manually delete a safeset from the Base vault, the safes et will be dele ted from the Satellite vault when data is synchronized. Similarly, in N:1:1 replication, if you manually delete a safeset from the Active Base vault, the safeset will be deleted from the Satellite vault when dat a is synchronized. To delet e a safeset: 1. 2. Navigate to the safesets pane. See Viewing Safesets. Right -click a safeset in the right pane and select Delete . A confirmation message appears. 3. Click Yes. A message indicates that the Delet e comman d has been submitted to the server. 4. Click OK.
To delet e multiple safesets: 1. 2. 3. Navigate to the safesets pane. See Viewing Safesets. Press CTRL and select multiple safes ets in the right pane. Right -click a selected safeset and select Delete . A confirmation message appears. 4. Click Yes. A message indicates that the Delet e command has been submitted to the server. 5. Click OK.
Page 51
12 Working with Accounts

After you create new customers and locations, you creat e customer accounts to allow the Agent to perform backups and restores. You create an account to register the computer on which the Agent is installed with the vault. If you do not create an account for the Agent, you cannot complete a backup or restore. If you add an account or a user that already exists, a message states that the account or us er could not be added. In addition, one of the following errors might appear in the AdminService log: Violation of UNIQUE KEY constraint 'account name' Cannot insert duplicate key in object dbo.VaultAccount. If these messages appear, select a different account or user name. For more information, see Creating a New Account and Changing Account Properties.
12. 1
Cre ating a New Acco unt
To create a new account: 1. 2. 3. 4. 5. 6. 7. 8. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand Manage Customers/Orgs, Safesets, Ta sks. Expand the customer. Expand Locations. Right -click a location and select Add New Account. Complete the New Account wizard. Click Finish.
12. 2
Ch angi ng A ccou nt Prop erties
To change the properties of an account: 1. 2. 3. 4. 5. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation.
Page 52
Working w ith Accounts 6. 7. Right -click an account and select Properties. Edit the fields in the Account Properties dialog box. If you change the storage locations for the account, the changes apply to new users. Select Apply the se settings to all the Users in the Account to apply the changes to existing and future users. 8. Click OK.
12. 3
Del eting an Acco unt
Note: You can only delete an account if no users under the account are associated with a computer. Note: You cannot restore a deleted account. To temporarily disable users in an account rather than deleting the account permanently, see Disabling a Us er. To delet e an account: 1. 2. 3. 4. 5. 6. 7. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Right -click an account and select Delete. Click Yes.
Page 53
13 Working with Users

After you create a customer, a location, and an account, you can add new us ers. After adding the user, the new user can configure and perform backups and restores. For more information, see Adding a New User, Changing User Properties, Changing Network Storage Credentials, and Enabling a User.
13. 1
Addin g a Ne w Us er
To add a new user: 1. 2. 3. 4. 5. 6. 7. 8. 9. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand Manage Customers/Orgs, Safesets, Ta sks. Expand the customer. Expand Locations. Expand a loc ation. Right -click an account and select Add New User. Complete the New User wizard. Click Finish.
13. 2
Ch angi ng Us e r Prop erties
To change the properties of a user: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Select an account. Right -click a user in the left pane and select Properties. Edit the fields in the User dialog. Click OK.
Page 54
Working w ith Users
13. 3
Ch angi ng Netwo rk Sto rag e Cred enti als
To change network storage credentials: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose Network Storage Credentials. Complete the Change User Credentials wizard. For field descriptions, see Change User Credentials Wizard Fields. 4. Click Finish.
13.3.1
Change User Credentials Wizard Fields
These fields appear in the Change User Credentials wizard:

Field Replace Credentials associated with a Specific Location Replace Credentials associated with a Specific Username Changes all the username and password for a specific user at multiple locations. The new credentials should allow the same access to the secondary pools. Replace Default Credentials Select ALL Select one or more Locations where you want to change the credentials Use Default Credentials Create New User Credentials Username Password Test connection under these credentials to Test Credentials Tests the UNC path credentials. Applies the default username and password to the locations you specify. Creates a new username and password for the locations you specify. A name that identifies the account user. The password for the account user. The UNC path to test. Replaces the default username and password for a UNC path. Applies the new settings to all locations. Applies the new settings to specific locations that you select. Description Changes the username and password at multiple locations.
Page 55
13. 4
Disabling a Us e r
To temporarily prevent a user from logging in and performing a backup or restore, you can disable the user. You can also disable all users in an account. The following icon appears for a disabled user in the Director Management Console: You can re-enable a disabled user. For more information, see Enabling a Us er. To disable a user: 1. 2. 3. 4. 5. 6. 7. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Select an account. Right -click a user in the left pane and select Di sable .
To disable all users in an account: 1. 2. 3. 4. 5. 6. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Right -click an account and select Disable Users.
13. 5
Enabli ng a Us er
You can re-enable a user that has been dis abled, or enable all users in an account. You can also enable all users and tasks for a customer or location. For more in formation, see Enabling a Disabled or Sus pect Task. To enable a user: 1. 2. 3. 4. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations.
Page 56
Working w ith Users 5. 6. 7. Expand a loc ation. Select an account. Right -click a user in the left pane and select Enable .
To enable all users in an account: 1. 2. 3. 4. 5. 6. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Right -click an account and select Enable Users.
13. 6
Del eting a Us e r
Note: You can only delete a user that is not associated with a computer. Note: You cannot restore a user that has been deleted. To temporarily disable a user rather than deleting it permanently, see Disabling a User. To delet e a user: 1. 2. 3. 4. 5. 6. 7. 8. Expand a vault connection in the left pan e of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Select an account. Right -click a user in the left pane and select Delete. Click Yes.
Page 57
14 Working with Registered Computers and Tas ks

Using CentralControl, you can register Agent comput ers with the Director vault so that the vault recognizes the Agent and computer for future backups and restores. You can also create tasks that define the options and parameters for backups. Using the Director Management Console, you can view registered computer properties, and delet e computers and tasks that are registered with the vault. For more information, see Viewing Registered Computer Properties, Deleting a Registered Comput er and Deleting a Task.
14. 1
Viewin g R egist e red Com puter Properti es
You can view information about computers registered to a vault, including their IP addresses, Agent versions, and unique identifiers. To view properties of a registered computer: 1. 2. 3. 4. 5. 6. 7. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location. Expand the Regi stered Computers list. Right -click a computer and choose Properties from the menu.
14. 2
Del eting a R egi stered Co mput er
Deleting a computer removes all information about that computer and its tasks from the Director, and invalidates the vault profile on the Agent. Before the computer could connect to the vault again, it would have to register as a new computer. To delet e a registered computer: 1. 2. 3. 4. 5. 6. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location. Expand the Regi stered Computers list.
Page 58
Working w ith Registered Computers and Tasks 7. 8. 9. Right -click a computer and select Delete . In the confirmation message box, click Yes. In the Confirm dialog box, enter YES and click OK.
14. 3
Enabl ed, Dis abl ed and S usp ect T as ks
Tasks in the Director can be enabled, disabled or suspect. Enabled tasks are available for backup, restore, and all other vault processes. The following icon appears in the left pane of the Director Management Console for each enabled task: Disabled tasks are not available for backup or restore, and are skipped by maintenance processes such as optimization, migration and reporting. However, you can run tasks such as "migrate delete" and replication operations for disabled tasks. The following icon appears in the left pane of the Director Management Console for each disabled task: You can manually disable a task to exclude it from maintenance operations. This can be useful if there are problems with the task files or data. For more information, see Disabling a Task. The Director can also disable tasks through the following operations: A vvcopy clone operation finishes successfully and disables the task on the source. A QSM export operation disables a task until a successful QSM import occurs. Suspect tasks are not available for backup, restore, optimization, migration or reporting. The following restrictions also apply to suspect tasks: 1:1 and N:1 Replication Safesets from a suspect task are not replicated. In addition, the last safeset on the sourc e side is not marked as replicated. VVCopy and QSM Export The suspect status on the sourc e is applied at the target location. QSM Import The behavior is identical to 1:1 replication, described above. Safesets are not imported the task is suspect on the vault or Agent. The following icon appears in the left pane of the Director Management Console for eac h suspect task: You cannot manually change a task to suspect. The Director marks a task as suspect if it detects possible data integrity issues. You can only change a task from suspect to enabled or disabled after you identify and correct any dat a errors in the task pool. For more information, see Enabling a Disabled or Suspect Task and Disabling a Task.
Page 59
14. 4
Disabling a Task
You can temporarily disable one task, or disable all tasks and users for a customer or location. Disabling a task can be useful if there are problems with the task, such as corrupt ed fi les or data. A disabled task is not available for backup or restore, and is skipped by vault processes such as optimization, migration, reports and storage extractor. For more information, see Enabled, Disabled and Suspect Tasks. You can re-enable a disabled task. For more information, see Enabling a Disabled or Suspect Task. To disable a task: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Right -click a task and select Disable .
To disable all tasks and users for a customer: 1. 2. 3. 4. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand the Manage Customers list. Right -click a customer and select Di sable All Users and Ta sks.
To disable all users and tasks for a location: 1. 2. 3. 4. 5. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Right -click a location and select Di sable all Users and Tasks.
Page 60
Working w ith Registered Computers and Tasks
14. 5
Enabli ng a Dis abl ed o r Su spect Task
You can re-enable one disabled or suspect task, or all tasks and users for a customer or location. You can only enable a suspect task if task pool data problems have been resolved. When you try to enable a suspect task, the Director checks the physical and logical integrity of the task data and only enables the task if there are no problems with the data. For more information, see Enabled, Disabled and Suspect Tasks. To enable a disabled or suspect task: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Right -click a disabled or suspect task and select Enable .
10. (If applicable) If you are trying to enable a suspect task, a warning message states that the task pool could be corrupted. Click OK. The Director checks the integrity of the task pool data. If there are no data issues, the Director enables the task. To enable all tasks and users for a customer: 1. 2. 3. 4. Select a workspace in the left pane of the Director Management Console. Expand a vault connection. Expand the Manage Customers list. Right -click a customer and select Enable all Users and Ta sks. If a task you are trying to enable is suspect, the Director checks the integrity of the suspect task data. If there are no data issues, the Director enables the task. To enable all users and tasks for a location: 1. 2. 3. 4. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list.
Page 61
Director 7.0 Operations Guide 5. Right -click a location and select Enable all Users and Tasks. If a task you are trying to enable is suspect, the Director checks the integrity of the suspect task data. If there are no data issues, the Director enables the task.
14. 6
Del eting a Task
When you delete a backup task, the entire Pool System for the backup is deleted and the task definition on the Agent stops working. If you accidentally delete a task, you might be able to recover it from a Vault Backup Agent (VBA) backup. To temporarily make a task unavailable for backup or restore, you can disable the task. For more information, see Disabling a Task. To delet e a task: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Right -click a task and select Delete .
10. Click Yes. 11. Click OK.
Page 62
Managing Storage Groups and Locations
15 Managi ng Storage Groups and Locations

After backup dat a is sent from the Agent to the vault, it is available in one of these locations: Primary Storage Group. Backup data is first stored in the primary storage group and pooled with other safesets from the same task. You can access this information for restore or recovery at any time. For more information, see Managing the Primary Storage Group. Secondary Storage Groups. After being saved in the primary storage group, backup dat a can be moved to secondary storage. This is slower, cheaper, storage that can be temporarily removed and transported. For more information, see Managing Secondary Storage Groups and Locations . Archive. Archive storage contains backup data on an offline, external device. For more information, see Managing Archive Locations. To improve the performanc e of backups and the efficiency of the storage areas, consider the following suggestions: Use storage groups and load balancing to prevent storage areas from runni ng out of space. Add storage space before it causes your backup to fail. Use secondary storage groups, archiving, and a retention policy to prevent your storage areas from becoming too large. Verify your main storage area is large enough to reseed your lar gest backup. Use deduplication to remove duplicate blocks of job data to make pool space available. Specify preferred storage locations in the primary storage group for index, data and log files. For more information, see Adding and Editing Location Policies for the Primary Storage Group.
15. 1
Managi ng th e Pri m ary Sto rag e G roup
The primary storage group is online storage for data to which you need immediate access. This includes pool file data, index and catalog information. The primary storage group area is the most active storage area on the vault. Data is added to the primary storage group by backups and removed through optimization. The constant addition and removal of data can result in fragmented data pool files and inefficient use of disk storage. To improve the use of disk storage space and reduce fragmentation, pool optimization is scheduled aut omatically. The amount of data submitted by the Agent det ermines the size of the Online Storage Groups area. As the size of the data submitted by the Agent increases, the size of the Online Storage Groups area increases. There is only one primary storage group. However, you can create multiple locations in the primary storage group. Each location can have a separate location policy. To ens ure the location policy is applied correctly, each location should be on a separate disk.
Page 63
15. 2
Ch angi ng th e M axim um Pool Fil e Siz e fo r th e Pri m ary Sto rag e G roup
You can change the maximum pool file size for the primary storage group. When the pool file size value is met, the Director creates a new pool file to accept safeset data. The pool file size setting must be less than your primary location volume size. If your volumes are smaller than your pool file size, backups can fail when the maximum volume size is exceeded. To change the maximum pool file size for the primary storage group: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 3. 4. On the Primary Storage Groups tab, select the storage group. Click Group Settings. The Edit Location Settings dialog box appears. 5. In the Pool file size field, enter the maximum pool file size. When the pool file size value is met, the Director creates a new pool file to accept safeset dat a. You can enter values from 10 to 2000. The default is 512 MB. The pool file size setting must be less than the primary location volume size. If volumes are smaller than the pool file size, backups can fail when the maximum volume size is exceeded. 6. 7. Click OK. Click OK again.
15. 3
Addin g a Storag e Loc ation to th e Pri mary Storag e Group
When you add a storage loc ation to the primary storage group, the Director automaticall y balances the distribution of new backups across all locations. This ens ures that you do not run out of disk space for backups. You can add multiple locations (loc al volumes or attached storage volumes) to a storage group. When the locations are on different volumes, the Director evenly distributes data evenly across all disks in the storage group, and adds pool files to locations with more space. The Director does not dynamically balance its storage to newly added locations. For example, if you are using a single location, and you add a new location wit hout any data, the Director does not automatically move data from one location to the other. The Director writes newly created pool files to the new location
Page 64
Managing Storage Groups and Locations until data on the old and new locations is balanced. New pool files are created by new incoming dat a from Agents or by a pool optimization. If you add two locations to the same volume, the Director does not balance the data between the two locations. Two or more volumes are required for storage balancing. The new location is used when it has more free space than the other locations. The other locations are used when they have the same free space as the new location. To add a storage location to a primary storage group: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Primary Storage Groups tab. Select a storage group. Click Add Location. Enter, select, or browse to a path in the Path field. You can enter a Universal Naming Convention (UNC) path for the new loc ation. The path must meet these requirements: The path must be absolute, not relative. The path cannot contain an invalid name. The path cannot contain invalid characters. UNC pat hs must be available at all times. 7. Select a storage policy for the primary storage location from the Storage Policy list. The Director application includes the Data and System policies. The System policy is applied to the default system drive, and Data policy is applied to any other drives that are in the Director's data paths 8. 9. Click OK. Click OK again.
15. 4
Unive rsal Namin g Co nv ention (U NC) S uppo rt
Universal Naming Convention paths allow you to use remote Network Attached Storage (NAS) devices. You can use UNC paths wit h Microsoft Windows 2003 and 2008 operating systems. The format for the path must be \\server\share, and not Z:\. By default, Microsoft Windows caches net work connections. To ensure consistent behavior, use the same credentials each t ime when you connect to the same UNC location.
Page 65
Director 7.0 Operations Guide When a connection to the UNC location is already established, the user credentials cannot be verified because a cached connection is used. The UNC path supports a maximum of 128 characters. This includes spaces and slashes (\). You cannot browse to a UNC path.
15. 5
Re movin g Sto rag e Loc ation s f rom t he Prim ary Storage Gro up
You can remove a storage location from the primary storage group if it does not have associated data. You cannot remove a location that has data associated with it. You cannot delet e the last location assigned to the last storage group. You must relocate or delet e all tasks associated with the location. To remove a storage location from the primary storage group: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Primary Storage Groups tab. Click Remove Location. Click Yes. Click OK.
15. 6
Viewin g Prim ary Sto rag e Gro up Loc ation Polici es and Setti ngs
To view primary storage group location policies and settings: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 3. 4. 5. Click the Primary Storage Groups tab. Select the storage group. Do one of the following: To view location policies, click Locations Policies. To view the group settings, click Group Settings. 6. Click OK.
Page 66
15. 7
Addin g and Editing Locatio n Policies fo r th e Pri m ary Sto rag e G roup
For the primary storage group, you can create loc ation policies that specify: the amount of free disk space to leave on a storage devic e the maximum percentage of disk space to use on a storage device whet her a storage device is a preferred loc ation for index, data or log files. To improve performance, you can specify that faster storage devices are preferred for index files, while slower performance devices are preferred for data files. After creating a location policy, you can assign it to one or more locations in the primary storage group. For more information, see Assigning a Location Policy to a Storage Location. To add or edit a location policy: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 3. On the Primary Storage Groups tab, click Locations Policies. The Policies dialog box appears. 4. Do one of the following: To add a location policy, click Add. To edit a location policy, select a location policy in the list, and click Edit. The Storage Policy dialog box appears. 5. Complete the following fields: Policy Name A name for the policy. You cannot edit this name after you create the policy. Stop using thi s volume if free disk space on thi s volume falls below x GB The amount in GB of free disk space to leave on the volume. Typically, the free space is left for the operating system to use. You can enter values from 0 to 4,194,303. Use no more than x % of di sk space on thi s volume The maximum percentage of disk space to use on the volume. Use for creation of pool index files If selected, the storage loc ation is a preferred location for saving index files. Index files have the following extensions: .optimized -filenames, .optimized-files, .optimized-segments, .optimized-streams, .file-names, .files, .segments, .stream-names, .streams, .names, .dat,.mir
Page 67
Director 7.0 Operations Guide Use for creation of pool data files If selected, the storage location is a preferred location for saving pool data files. Pool data files have the following extensions: .pf, .pf -map Use for creation of log files If selected, the storage location is a preferred location for saving log files. Log files have the .log extension. 6. Click OK.
15. 8
Assig ning a Loc ation Polic y to a Storag e Loc ation
After creating a location policy, you can add the policy to one or more locations in the primary storage group. For information about creating location policies, see Adding and Editing Location Policies for the Primary Storage Group. To assign a location policy to a storage location: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 3. 4. On the Primary Storage Groups tab, select a storage location. Click Location Settings. The Location dialog box appears. 5. 6. In the Storage Policy box, select a storage policy. Click OK.
15. 9
Del eting a Loc ation Polic y
Note: You cannot delete a location policy if it is assigned to a storage location with associated tasks. To delet e a location policy: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. On the Primary Storage Groups tab, click Locations Policies. Select a location policy. Click Delete. Click Yes.
Page 68
15. 10 Settin g Vault W arni ng and Criti cal T hres hold Limits
You can receive these email notifications when vault disks reach specific thresholds: Warning: All primary storage locations are running out of disk storage. Disk usage is above warning level. Error: All primary storage locations are running out of disk storage. Disk usage is above critical level. Backups may start failing until more disk storage is available. Maintenance has been disabled. Aft er making more disk storage available, please enable Maintenance. Normal: Disk usage is OK. To set vault warning and critical threshold limits: 1. Enable email notifications on the vault. You must provide an SMTP address and a recipient address. 2. 3. 4. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Monitor Configuration . Enter a value in the Warning Threshold field. You can enter values from 15 to 98. The default is 80. 5. Enter a value in the Cri tical Threshold for Backups field. This value must be greater than the value in the Warning Threshold field. You can enter values from 15 to 98. The default is 98. 6. Click OK.
15. 11 Managi ng S eco nd ary Sto rag e G roup s and Loc ation s
You can use secondary storage groups to store data that you do not access frequently. Typically, secondary storage is cheaper disk storage that you use for the long -term storage of data. A secondary storage pool can be online, detached and stored (offline), or attached to another system . After a backup, a safeset is in the primary pool and its status is online. When you migrate a safeset to secondary storage, its status changes to Secondary. A secondary pool is self-contained. It includes both pool data and pool indexes in one directory. The first safeset in the secondary pool is a seed, and the rest of the safes ets (for that task) are deltas. When you create a new secondary pool, the existing secondary pool becomes inactive. However, the safesets within the original secondary pool have a Sec ondary status and remain online. If you detach a secondary pool, the safeset status changes to Det ached Sec ondary and the safeset is offline. The contents of a detached pool are not included in the licensed storage quot a calculation.
Page 69
Director 7.0 Operations Guide You can use the Sec ondary Restore Server application to read or export a safes et directly from a secondary pool, without the participation of the primary vault. Data stored in secondary storage is not part of the replication schema.
15. 12 Addin g a Seco nd ary Sto rage G rou p

To add a secondary storage group: 1. 2. 3. 4. 5. 6. 7. 8. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Secondary Storage Groups tab. Click New Group. Enter a name for the group. Click OK. Add a location to the group. See Adding a Storage Location to a Secondary Storage Group. Click OK.
15. 13 Re movin g a Seco nd ary Sto rage G rou p

To remove a secondary storage group: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Secondary Storage Groups tab. Select a group. Click Delete Group. Click Yes.
Page 70
15. 14 Ch angi ng th e M axim um Pool Fil e Siz e fo r a Seco ndary Sto rag e G roup
You can change the maximum pool file size for a secondary storage group. After you change the group settings of a secondary storage group, all affected tasks start with a new secondary pool when the next secondary migration runs. This could significantly increase the amount of space that is required for secondary storage. To change the maximum pool file size for a secondary storage group: 1. 2. 3. 4. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. On the Secondary Storage Groups tab, select a storage group. Click Group Settings. The Edit Location Settings dialog box appears. 5. In the Pool file size field, enter the maximum pool file size. When the pool file size value is met, the Director creates a new pool file to accept safeset dat a. You can enter values from 10 to 2000 MB. The default is 512 MB. The pool file size setting must be less than the primary location volume size. If volumes are smaller than the pool file size, backups can fail when the maximum volume size is exceeded. 6. 7. Click OK. Click OK again.
15. 15 Addin g a Storag e Loc ation to a S econd ary Sto rag e Group
You can add multiple locations to a secondary storage group. When you first migrate safesets to secondary storage, the Director saves the safesets in the storage location with the most available space. The Director then saves safesets in this location until the location is closed. To add a storage location to a secondary storage group: 1. 2. 3. 4. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Secondary Storage Groups tab. Select a storage group.
Page 71
Director 7.0 Operations Guide 5. 6. Click Add Location. Enter, select, or browse to a path in the Path field. You can enter a Universal Naming Convention (UNC) path for the new loc ation. The path must meet these requirements: The path must be absolute, not relative. The path cannot contain an invalid name. The path cannot contain invalid characters. UNC pat hs must be available at all times. 7. Select a storage policy for the primary storage location from the Storage Policy list. The Director application includes the Data and System policies. The System policy is applied to the default system drive, and Data policy is applied to any other drives that are in the Director's data paths 8. 9. Click OK. Click OK again.
15. 16 Re movin g a Storag e Loc ation f rom a S eco nd ary Storage Gro up
You cannot delet e a storage location that has data associated with it. You cannot delete the last location assigned to the last storage group. You must relocate or delet e all tasks associated with a location before you can remove it. To remove a storage location from a secondary storage group: 1. 2. 3. 4. 5. 6. 7. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. Click the Secondary Storage Groups tab. Click a secondary storage location. Click Remove Location. Click Yes. Click OK.
Page 72
15. 17 Managi ng Archiv e Loc ation s

Archive locations store archived safesets offline. Archive storage locations can include fixed disks, USB drives, and removable media. Creating an archive storage area is not mandatory, but you cannot archive safesets without one. An archive location should provide enough space to store a compressed safeset. Use the A rchive command to archive a task and all associated task data to an archive location. Archived dat a is not part of the replication schema.
15. 18 Addin g an A rchi ve Locatio n

To add an archive location: 1. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 2. 3. Click the Archive tab. Click Add. The Add Location dialog box appears. 4. Do one of the following: To add an archive location on tape, click Tape, and then choose the location from the Tape Drive list. To add an archive location on other media, click File System, and then enter or select the location on the file system. 5. Click OK.
15. 19 Re movin g an A rc hive Locatio n

To remove an archive location: 1. 2. 3. 4. 5. From the Storage Management menu, choose S torage Groups and Locations. Click the Archive tab. Select an archive in the Location list. Click Remove . In the confirmation message box, click Yes.
Page 73
16 Managi ng Safesets and Pools

This section provides information and procedures for performing the following tasks: Enforcing Safeset Retention Policies Optimizing Pool Files Verifying the Integrity of Backup Files Copying and Cloning Data Moving Data Migrating Safesets to Secondary Storage You can also use automated storage management to perform storage utility functions. For more information, see Activating Aut omated Maintenance.
16. 1
Enforcing Safe set Ret entio n Poli cies
The system enforces the retention policy for each safeset and determines which backups are ready for transfer or deletion. By default, this migration occurs as a scheduled job on the entire vault once a day. It is recommended that you keep the default setting. However, you can run the process at any time. In addition, you should run optimization once a week. Running regular migrations and optimizations removes unnecessary safesets and conserves storage space. Migration runs as part of optimization, even when the migration is not scheduled. Backups that have not been successfully updated are not migrated. During the migration, a message is added to the log when a synch entry wit h a backup time that is earlier than the previous entry's backup time is encountered. This entry and all subsequent entries are processed as if they were backed up in sequential order. A migration works with these safeset types: Online Safesets An online safes et is a safeset in the primary or secondary pool. Note: When you migrate online safesets, the Director only enforces retention policies for safesets in the primary storage pool. To enforce retention policies in the secondary storage pool, use the secondaryop expire command. Offline Safesets An offline safes et is a safeset that is stored in the arc hive. The Agent retention settings determine how many days a safes et is available online. When the number of days for retaining the safeset in the secondary pool is met or exceeded, the safeset is moved to the archive for a specific number of days. When the number of days for retaining the safeset in the archive is met or exceeded, the Offline Migrate process removes the safeset from the vault.
Page 74
Managing Safesets and Pools Recalled Safesets A recalled safeset is a safeset that is retrieved from an archive for a restore or export. When a safeset is recalled, it is stored in the Main Storage area as a pool file, and a retention period is applied. When the number of days for retaining the recalled safeset is met or exceeded, the Online Migrate process removes the safeset from the vault. You can run a migration on the entire vault, or on an individual task. If you run a migration on the entire vault, and a single task fails, the migration does not stop. When the migration finishes, it reports one of these statuses: Completed Completed with errors Failed If a task fails during the migration, a Completed with Errors status message appears in the log and the email notification. When a migration finishes, it reports as Completed or Failed. When a migration task completes with errors, the Subject field in the email notification is Failure. When a migration runs on an entire vault and some of the tasks complete, a Completed message appears in the log. To enforce safeset retention policies: 1. 2. 3. 4. Select an object in the left pane of the Director Management Console. From the Storage Management menu, choose Migrate Tasks. Complete the Migrate wizard. For field descriptions, see Migrate Wizard Fields. Click Finish.
16.1.1
Migrate Wizard Fields
The following fields appear in the Migrate wizard:

Field Online Offline Vault Task Description Migrates expired safeset images marked for deletion stored in the online area. Migrates safeset images stored in the offline area. Selects all tasks on a vault. Selects individual tasks.
Page 75
Field
Description
Selected Organization/Customer Specifies a specific customer. This option is available when you select Task. Selected location Specifies a specific customer location. This option is available when you select Task. Selected Computer Selected Task Submit job immediately Schedule job Specifies a specific computer. This option is available when you select Task. Specifies a specific task. This option is available when you select Task. Submits the job immediately. Creates a schedule to complete the job weekly or monthly.
16. 2
Optimi zing Pool Fil es
When the vault receives data from its customers' Agent computers, it "pools" the data with ot her safesets from the same backup Task. This data pool can become fragmented as it is updated and migrated and as data is written and deleted. Pool files are left with data that is no longer referenc ed but still occupies space in the pool system. Over time, this fragmented data grows, wasting storage spac e. You can use the Pool Optimization Wizard to manage the file pools created by the vault and reduce data fragmentation. This reconstructs the Agent's data using better space conservation. Vault Optimization removes unreferenced data and defragments the pool system. In addition, optimization ensures that the vault retains only the required safesets. A migration is included as part of an optimization, even if you do not schedule a migration. Backups that have not been successfully updated are not migrated. Archive backups are expired when the number of archived days has passed. Pool optimization maintains a minimum storage footprint, and allows fast restores. Optimization maintains the size of the pool by removing non-essential expired or duplicat e data. E very optimization tunes the database to allow optimal restore performance. Deduplication (common block pooling) inside the primary pool helps to reduce the storage requirements for the vault. Common block pooling works independently of the Agent version. The process results in different disk space savings for different backup jobs. In the case of a re -seed, it can significantly reduce the size of the pool system. If the Agent changes the encryption type, or compression type, or encryption password of a safeset , then all pool blocks are different on the vault. A re-seed like this will not see any common block pooling (deduplication). The next backup of the same Job with the same parameters, though, will benefit from deduplication.
Page 76
Managing Safesets and Pools The vault calculates a Vault Hash Value (VHV ) for each data block, and updates the indexes to the data. Any duplicated blocks are marked for removal on the next Optimization. The vault can detect and deduplicate situations such as the same file in different directories, renamed files, and renamed parent directories. If deduplication starts before any commands such as Backup, Restore, Import or Export, then deduplication detects the lock request, stores its current state, releases the pool system, and retries the command later. If you want the deduplication to run without interruption, you can run the vvpoolop command from the command line (CLI) with a "nointerrupt" option. Only one vvpoolop command can run against a pool system at any given time. For more information, see vvpoolop. Optimize does not check to see if all the files exist, and does not verify index es. To verify the physical status of the pool system, run the command line utility CheckCRC. If you want to check the data integrity, run the command line utilities SSIVerOne or SSIVerAll. For more information, see the Command Referenc e. To optimize pool files: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose Optimize . Complete the Pool Optimization wizard. For field descriptions, see Pool Optimization Wizard Fields. 4. Click Finish.
16.2.1
Pool Optimization Wizard Fields
The following fields appear in the Pool Optimization wizard:

Field Remove duplicate and expired data from the pool Remove expired data only Description Detects duplicate pool system data, adjusts references, and then uses optimization to remove unused data. This process is longer than optimization. Removes unused data from the pool system, and allocates the recovered space. Note: After running an optimization with deduplication, run a Storage Pool Summary report to view the amount of space that was reclaimed. By computer Selects tasks on a specific computer.
Page 77
Field Entire Vault
Description Selects all accounts and computers for the online storage location. Generally, this option takes longer to complete than selecting the tasks on a single computer.
Select Organization/Customer
Specifies a specific customer. This option is available when you select By computer.
Selected location
Specifies a specific customer location. This option is available when you select By computer.
Selected Computer
Specifies a specific customer computer. This option is available when you select By computer.
Select Task
Specifies a specific task on a customer computer. This option is available when you select By computer.
Submit job immediately Schedule job
Submits the job immediately. Creates a schedule to complete the job weekly or monthly.
16. 3
Settin g the Mini mu m Pool Us age Param et er
The optimizer uses the Minimum Pool Us age parameter to determine whether to defragment pool files. The Director defragments a pool file when storage usage in the file is lower than the specified value. For example, if the minimum pool usage value is 75, the system defragments a pool file and recovers unused storage space in the file when its space usage falls below 75%. To set the Minimum Pool Usage parameter: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose S torage Groups and Locations. The Storage Locations dialog box appears. 3. 4. On the Primary Storage Groups tab, select the storage group. Click Group Settings. The Edit Location Settings dialog box appears. 5. In the Minimum pool usage field, enter the minimum percentage of storage us ed in a pool file. You can ent er values from 5 to 95. The default is 75. 6. Click OK.
Page 78
Managing Safesets and Pools
16. 4
Ve rifyi ng th e I ntegrit y of B ac kup Files
To verify the int egrity and consistency of a vault pool, and troubleshoot errors, you can create a backup verification job. To verify the int egrity of backup files: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Storage Management menu, choose Diagnose . Complete the Pool System Diagnostic wizard. For field descriptions, see Pool System Diagnostic Wizard Fields. 4. Click Finish.
16.4.1
Pool System Diagnostic Wizard Fields
The following fields appear in the Pool System Diagnostic wizard:

Field Check CRC integrity of the Pool System Description Validates the physical integrity of files in the pool system. The CRC integrity check does not read the data, but just checks that the safeset (as a file) is intact and uncorrupted. Verifying safesets reads the System Independent Data Format (SIDF) and verifies the integrity of a safeset as if it were getting ready to do a restore. A user's private information is not read. Only a user with the encryption key can read encrypted data. Verify all safeset generations Verify the last committed safeset generation Verify a specific safeset generation Entire Vault By Task Select Selects all accounts and computers for the online storage location. Selects a specific task on a specific computer. Specifies a specific customer. This option is available when you select Verify all Verifies the logical integrity of a specific safeset. Verifies the logical integrity of the last committed safeset. Verifies the logical integrity of all safesets.
Page 79
Field Organization/Customer
Description safeset generations, Verify the last committed safeset generation, Verify a specific safeset generation, or By Task.
Selected location
Specifies a specific customer location. This option is available when you select Verify all safeset generations, Verify the last committed safeset generation, Verify a specific safeset generation, or By Task.
Selected Computer
This option is available when you select Verify all safeset generations, Verify the last committed safeset generation, Verify a specific safeset generation, or By Task.
Select Task
This option is available when you select Verify all safeset generations, Verify the last committed safeset generation, Verify a specific safeset generation, or By Task.
Submit job immediately Schedule job
Submits the job immediately. Creates a schedule to complete the job weekly or monthly.
16. 5
Copyi ng and Clonin g D ata
You can use one of these methods to copy objects and data from one location to another or to another vault: Copy Copying creat es duplicate items with different globally unique identifiers (GUIDs). Copying dat a re-enables the original source objects and tasks. Clone Cloning creat es identical items with identical globally unique identifiers (GUIDs). Cloning data enables the destination cloned objects and tasks. You must re-register cloned dat a on the Agent. You can copy and clone vaults, customers, locations, computers and tasks. If you use the clone option to copy a customer from a source to a destination vault, the following error message can appear: Task failed: Violation of UNIQUE KEY constraint 'CU_Customer'. Cannot insert duplicate key in object '<customer>'. The statement has been terminated. To correct this error, specify the external IP address (or the visible hostname) of the vault in the Network Address field of the Vault Connection Properties dialog box. If you do not specify an IP address or host name, the clone task might attempt to add the cloned customer to the source computer.
Page 80
Managing Safesets and Pools The restore of a safeset after a clone can fail with an unk nown exception error. This error occurs when multiple vault profiles on the Agent attempt to connect to the first profile, which may not be the profile of the destination vault. To correct this error, run a backup to the destination vault, or synchronize with the destination vault, and then retry the restore. When you copy objects, the log file displays Total data transferred and Data transfer speed. A copy fails when the communication link between the source and destination vaults is lost. A communication failure can also cause a copy on the same vault to fail. When a copy fails, error m essages appear in the error log. For example: Error occurred while copying the pool files. ECONNRESET, connection reset by peer RPC-E-CANTSEND, failure in sending call task cancelled You must restart failed copy requests. On a net work share, Informational (I) or Warning (W) messages can appear in the log files when your copy is finished. For example: VVLT-I-0001 This network connection has files open or requests pending. VVLT-W-0002 Failed to disconnect from '\\192.168.2.58\e$' network share. You can ignore informational or warning messages. If you use the DNS host name and not the vault IP address to copy data from one vault to another, the inability of the DNS server to resolve the host name might cause the copy to fail. To complete a copy successfully, the two vaults must visible to each other on the net work. When you copy dat a from one vault to another, the values from the database configuration file overwrite the values in the database part of the copy configuration file. If the database computer is not visible on the network through the DNS server, replace the host name with an IP address in the database configuration file. Follow these recommendations to avoid a copy failure: Specify IP addresses when copying data between two vaults that are not visible to one another through the DNS server. Verify that the DA TABASESERVERNAME configuration value specifies an IP address, and not a host name. Errors can occur if you are using 1:1, N:1 or N:1: 1 vault replication, because cloned or copied objects already exist. To correct the errors, stop replication, copy or clone to the destination vault, and then restart replication.
Page 81
Director 7.0 Operations Guide Note: You cannot copy a task if it has safesets in both secondary storage and archive storage. Using secondary and archive storage for the same task is not supported, but is not prevented by the Director. To copy or clone objects: 1. In the left pane of the Director Management Cons ole, do one of the following: Select the object that you want to clone or copy. From the Storage Management menu, choose Copy. Drag the object that you want to clone or copy to its destination. 3. 4. Complete the Vault Copy wizard. For field descriptions, see Vault Copy Wizard Fields. Click Finish.
Review the vvcopy log to determine if the copy or clone was successful. If the copy or clone is successful, vvcopy performs fast index verification on the last safeset copied to ens ure the data int egrity of the pool .
16.5.1
Vault Copy Wizard Fields
The following fields appear in the Vault Copy wizard:

Field Select Source Items to Description The objects to copy to the target destination. All objects below the selected object are copied by default. Select Target Host Name Port User Name Password Confirm password The location to copy the selected objects. The host name of the target computer. The port used by the target computer. The user name used to access the target computer. The password used to access the target computer. The password used to access the target computer.
Page 82
Managing Safesets and Pools
Field Domain
Description The domain of the target computer. The copy can fail when the Windows 2008 operating system is installed without a Domain Name Service. For Windows 2008 operating systems, you must enter the computer name in the Domain field. When the copy is complete, the domain name is added to the Vault Copy domain field.
I have both physical and logical Updates the file paths and file names of the copied pool files. data already in their respective locations and I only want to adjust the target files to the proper location(s) Copy Copies existing data and tasks to another location or another vault. You cannot copy a task to a Passive vault. To complete backups and synchronizations, you must reregister the Agent at the new location. In addition, you must open the CentralControl Global.vvc file and specify the IP address for the new vault for this customer, and update the Authentication to reflect the new vault. Clone Creates identical items with identical globally unique identifiers (GUIDs) on another vault. This option is unavailable if you are copying objects within the same vault. It is recommended that you delete the source object when the clone completes. You must open the CentralControl Global.vvc file and specify the IP address for the new vault for this customer, and update the Authentication to reflect the new vault. Copy Physical Data Copies Pool data files. The logical data must exist before you can copy the physical data. If you have Secondary Pools on your vault, the secondary pools are cloned or copied to the new vault. If the secondary pool is connected to both vaults, you can change the link from the old vault to the new vault. Do not copy physical data from secondary pools . Copy Logical Data Copies the logical (metadata) files to the physical data files. For the Pools to work properly, you must copy both files and copy the logical data first.
Page 83
Field
Description
Do not copy physical data from Physical data from the secondary pool is not copied, but a link to the data is secondary pools, just link Source Storage Locations Destination Storage Locations created. The storage locations on the source computer. The storage locations on the target computer. Click the ellipsis (...) button to add destination storage locations. If there are name conflicts, rename the item Identifies naming conflicts. To correct a naming conflict, select an object and press F2 to enter a new name for the object.
16. 6
Moving D ata
You can move files bet ween storage locations in the primary storage group. Unless you specify a destination for the files, the system moves files to the storage location with the most available space. To move pool data from a drive that is old, small or slow to other locations in the storage group, you can retire the drive. Before retiring a drive, do the following: Set the location as read only, using the Storage Locations dialog box. This prevents new information from being written to the retired drive. Stop or pause the maintenance service on the vault. If the maintenance service runs during the drive retirement process, maintenance processes could fail or cause problems. To move dat a: 1. 2. 3. 4. Select an object in the left pane of the Director Management Console. From the Storage Management menu, choose Move to Another Location. Complete the Move Data wizard. Click Finish.
16. 7
Migratin g S af es ets to S econ dary Storag e
You use secondary storage to store backups that you access infrequently. Backups stored in secondary storage are still available for restores. You cannot move backups from secondary storage back to the primary storage group. You cannot move the most recent safesets. If you move a safeset from within a group of safesets, you cannot move the earlier safesets later. Relocated backups are reseeded in th e secondary pool.
Page 84
Managing Safesets and Pools You can migrate safesets from a primary pool to an active secondary pool. You cannot migrate safesets from a secondary pool to a primary pool or from one secondary pool to another. You can restore all safeset with an online status. Note: Do not move safesets for the same task to both secondary storage and archive storage. Using secondary and archive storage on the same task is not supported, but is not prevent ed by the Director. To migrate a safeset to secondary storage: 1. 2. 3. Select an object in the left pane of the Director Management Console. From the Storage Management menu, choose Migrate to Secondary Storage Pool . Complete the Migrate to Secondary Storage Pool wizard. For field descriptions, see Migrat e to Secondary Pool Wizard Fields. 4. Click Finish. Review the MigrateSec ondary log to determine if the move was successful. The status of migrated backups changes to Secondary in the Director Management Console.
16.7.1
Migrate to Secondary Pool Wizard Fields
The following fields appear in the Migrate to Secondary Pool wizard:

Field Use Rules to Determine Which Safeset To Migrate Explicitly Select Online Safesets To Migrate To Secondary Storage Use the Archive Retention settings Migrate all the safesets that are older than x days Keep up to x of the most recent safesets online. Migrate the rest. Detach the migrated safesets Identifies migrated safesets as offline to the Agent. Migrates safesets when the archive retention settings for online copies or days are reached. Migrates safesets that are older than a specified number of days. The default is 180 days. The number of safesets to keep in the primary pool. When the number is exceeded, the older safesets are moved to secondary storage. The default is 100. Migrates safesets that you select to secondary storage. Description Migrates safesets that meet specific retention settings.
Page 85
Field I want to preview which safesets are going to be migrated
Description Applies the retention rules to the safesets in the primary pool so you can see which safesets would be migrated.
Also preview the storage size Applies the retention rules to the safesets in the primary pool so you can see how required on the secondary storage pool Verify the first and then every Verifies safesets that are migrated to a secondary pool. Verification ensures that the x data in the safeset is valid and can be used for a restore. The default value 1 indicates that every safeset is verified. It is recommended that you keep the default value. Submit job immediately Schedule job Submits the job immediately. Creates a schedule to complete the job weekly or monthly. much storage would be required for the migrated safesets.
16. 8
Exporti ng S af es ets
You use the Export wizard to export safesets in Safeset Image (SSI) format. Agents can use SSI data for restores. You can export safesets to removable media or a secondary pool. You can export data to a local disk or a Universal Naming Convention (UNC) device. When you export safesets, the original pool system data is unchanged and is available for backups and restores. Each safeset that you ex port requires a corresponding catalog (CA T) file on the Agent. The CA T file provides a visual representation of the directories and files. You can export the CA T file with the safeset file. You add the CA T file to the correct Agent directory to complete the restore. When you export safesets from a primary storage pool, task information displays in the log files as: tn='somename', vid=#, cid=#, tid=#, tsid=# If you exported safesets from a secondary storage pool, only the task name appears in the log file. To export safesets: 1. Open a command prompt and run the vvexport command with the /simulate option to determine the size of the backup. 2. 3. If you are using removable media for your backup, connect it to the vault. From the Storage Management menu, choose Export.
Page 86
Managing Safesets and Pools 4. 5. Complete the Export wizard. For field descriptions, see Export Wizard Fields. Click Finish.
16.8.1
Export Wizard Fields
The following fields appear in the Export wizard:

Field Description
Export Safesets from this Vault Exports safesets from the vault. Export Safesets by specifying the physical path of a Secondary Pool Exports safesets from the secondary storage pool. When you export safesets from a secondary pool, you can use the secondary pool as an input for the Secondary Restore Server (SRS ) utility. The p rimary storage pool is unchanged, and its safesets are not marked as secondary. In addition, a secondary pool is not created, and the secondarystorage table on the vault is unchanged. Select Organization/Customer Specifies a specific customer. This option is available when you select Export Safesets from this vault. Selected Location Specifies a specific customer location. This option is available when you select Export Safesets from this vault. Selected Computer Specifies s specific computer. This option is available when you select Export Safesets from this vault. Select Task Specifies a specific task. This option is available when you select Export Safesets from this vault. Path The path where the secondary storage pool is located. . You can browse to a secondary storage pool on a local disk. If the secondary storage pool is remote, you must enter a UNC path. A maximum of 128 characters are allowed for a UNC path. If the default credentials do not allow you to access the remote path, you must supply custom ones for the specific location or username. Use Default User Credentials Create Custom User Credentials Applies the default username and password to the location you specify. Creates a new username and password for the location you specify.
Page 87
Field User Name Password Test Credentials Selected Safeset Export Safesets (to SSI file) Export Safesets (to Secondary Pool) Save to Safeset (SSI) file size Export Catalogs (to disk or UNC) Save catalogs to a separate location Save catalogs for version 3.1 Agents, and earlier Save catalogs for version 3.2 Agents, and later
Description A name that identifies the account user. The password for the account user. Tests the UNC path credentials. Specifies the safesets to export. Exports safesets as SSI files to the specified location. Exports safesets to the secondary storage pool.
The location to export the safesets. The size in MB of the e xported safeset. Exports catalog (CAT) files to disk or a UNC device.
Saves catalog (CAT) files to a location you specify.
Saves catalog (CAT) files for a version 3.1 Agent and earlier.
Saves catalog (CAT) files for a version 3.2 Agent and later.
16. 9
Exporti ng S af es ets usin g th e vv export Com mand
You can use the vvexport command to export safesets to a local hard disk. You can use your CD or DVD writing software to save the safesets to CD or DVD media. For more information, see the Command Referenc e. When you run the vvex port command, you must specify the size of the backup file. You can have multiple SSI files on a CD or DV D disk, or have a single SSI file that spans multiple CD or DVD disks.
Page 88
Managing Safesets and Pools in Secondary Storage
17 Managi ng Safesets and Pools in Secondar y Storage

If you change the Secondary Storage Group settings, the affected tasks start with a new secondary pool the next time that secondary migration occurs. This result s in a full seed of the data in the new secondary storage location, and could result in a significant increase in the amount of disk space required for secondary storage. If you close secondary pools for writing, or set a secondary storage location as read only, the affected tasks start with a new secondary pool the next time that secondary migration occurs. This result s in a full seed of the data in the new secondary storage location, and could result in a significant increase in the amount of disk space required for secondary storage. You can select aggressive settings for migration rules that require migration to secondary storage. This could res ult in a significant increas e in the amount of disk space required for secondary storage. Selecting non-sequential safesets for secondary migration is not recommended. If you later want to migrate these intermediate safesets to secondary storage, they will require a full reseed. You can use intermediate safesets for restores. They will remain in Primary Storage until t hey expire or they are deleted. After a Migrate to Secondary, on a large seed safeset with many files, the Secondary Pool size may have a size increase. If you have a large safeset with few files (such as a database) you will not notice much differenc e. However, if you have many files (such as a MAPI backup) you may notice an increase in size.
17. 1
Assig ning Se cond ary Sto rage Gro ups to T as ks
To assign a Secondary Storage group to a task: 1. From the Storage Management menu, choose Secondary Storage Pools, and then click Assign. The Global Scope Configuration wizard appears. 2. 3. Click Next. Complete the Global Scope Configuration wizard fields. For field descriptions, see Global Scope Configuration Wizard Fields. 4. 5. Click Finish. Right -click an object in the Director Management Console to which you applied secondary pool settings, and select Properties to see if the changes were applied.
Page 89
17.1.1
Global Scope Configuration Wizard Fields
The following fields appear in the Global Scope Configuration wizard:

Field Change Locations Override the Secondary Storage assignment for existing tasks which already have a Secondary Storage assignment Description Add locations and groups. Overwrites the existing secondary storage settings for existing tasks. Changing the settings causes a re-seed when the next backup runs. Selecting this option can use more disk space.
Assign this Secondary Storage Group only to Assigns the secondary storage settings to existing tasks that do not existing tasks, which currently do not use the currently use secondary storage. Secondary Storage Assign this Secondary Storage Group to all Assigns the secondary storage settings to all new and existing tasks
new and existing tasks which currently do not that do not currently use secondary storage. This option is available have a Secondary Storage assignment when you select a vault and all customers, computers, and tasks.
17. 2
Applyi ng S af es et R et ention Setti ngs to t he Seco ndary Sto rag e Pool
You can apply primary pool safeset retention settings to the secondary storage pool. To apply safeset ret ention settings to the secondary storage pool: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Expand a backup task.
10. Double-click Backups. 11. Right -click a backup in secondary storage in the right pane and select Properties.
Page 90
Managing Safesets and Pools in Secondary Storage 12. Click Also apply setting to secondary location on the General tab. This change applies only to safesets that are not detached. 13. Click OK.
17. 3
Seco ndary Sto rag e D el etion and Ret entio n
You can use the Director Management Console or execute a secondaryop command to delete a safes et from attached secondary storage. When you delete a secondary storage safeset, two entries appear in the Job Monitor and log files. One entry is the primary storage deletion, the second entry is the command that deleted the safeset from secondary storage: secondaryop delete taskid=<t> safeset=<s> When you use the Director Management Console to delete a safeset and the secondary storage is detached (offline), only the safeset information on the vault is deleted. The safes et data on the secondary storage is unaffected. When you use the Director Management Console to delete a safeset and the secondary storage is attached, but not connected, you must connect the secondary storage before you can delete the safes et.
17. 4
Autom atic Ret entio n M an ag em ent i n the Second ary Pool
In Director Version 6.2 and later versions, automatic retention management is disabled in the secondary pool by default. To delet e safesets in primary storage according to ret ention settings, specify Online in the Migrate wizard. Safesets in secondary storage are unaffected. For more information, see Migrate Wizard Fields. To apply the retention policy for a task across both the primary and secondary storage pools, run the following secondary op expire command: secondaryop expire taskid=<t> Note: Running the secondaryop expire command can result in the deletion of all safesets in secondary storage. For example, if a task has one backup in primary storage and nine in secondary storage, and the retention settings are Online safesets=1, Online days=0 and A rchive days=0, running the secondary op expire command deletes all safesets from secondary storage. You can also run the secondaryop expire command for particular storage locations: secondaryop expire storage_location=<path> If a path is specified, SecondaryOp scans all secondary pools in that path.
Page 91
17. 5
Seco ndary Sto rag e M ai nten ance
You use the secondaryop command to perform maintenance functions on secondary storage pools. For more information, see secondaryop. When the secondary storage pool is attached to its originating vault, you must specify the task ID on the command line. To obtain a task ID, right-click a task in the left pane of the Director Management Console and select Properties. The task ID appears in the Ta sk Name field. When the secondary storage pool is maintained by a foreign vault you must specify the physical storage location on the command line. You can use scheduled entries to automat e secondary storage pool maintenance. To enable the scheduled ent ries, specify these commands: #secondaryop expire taskid=* #secondaryop optimize taskid=*
17. 6
Closin g a Seco nd ary Sto rage Pool
You cannot migrate safesets to a closed secondary pool because it is read-only. To close a secondary storage pool: 1. From the Storage Management menu, choose Secondary Storage Pools, and then click Close . 2. 3. Complete the Close Secondary Pool for Writing wizard fields. Click Finish.
17. 7
Det achi ng a S econd ary Storag e Pool
Safes ets in a detached secondary storage pool are offline and you cannot use them for restores or exports. Detaching a secondary storage pool allows you to remove storage media. When you use a detached secondary storage pool on a different vault it becomes a Foreign Secondary Pool. A pool system on a detached device is not included in your storage license calculation. However, when you reattach the pool, it is included in your storage license calculation. To detach a secondary storage pool: 1. From the Storage Management menu, choose Secondary Storage Pools, and then click Detach. 2. 3. Complete the Detach Secondary Pool wizard. Click Finish.
Page 92
Managing Safesets and Pools in Secondary Storage
17. 8
Attac hing a S eco nd ary Sto rag e Pool
To access a detached secondary storage pool, you must attach it to its originating vault. When you attach a secondary storage pool, you can use the safesets for restores and exports. You can specify a Universal Naming Convention (UNC) path for the secondary pool location. UNC path names can be a maximum of 128 characters including spaces and slashes (\). You cannot browse to a UNC pat h; you must enter it manually. To access the secondary pool files of a UNC path, you can use default credentials or provide a valid user name, password and domain name. If you specify an invalid path or pool, the following message appears: Configuration file cannot be opened To attach a secondary storage pool: 1. From the Storage Management menu, choose Secondary Storage Pools, and then click Attach. 2. 3. Complete the Attach Secondary Pool wizard. Click Finish.
Page 93
18 Archiving Data
A retention policy on the Agent determines whether an online safeset is delet ed or archived. Safes ets retained for 6 months or longer occupy a large amount of vault disk space. An archive provides a cost effective method to store safesets that you access infrequently but are required to keep to meet the requirements of your corporate retention policy. Use the vault to store a small number of online safesets that you access frequently. If you set the archive location to a local disk, the archive job runs as a migration and a migration log is generated. A safeset is not archived if the backup time occurs in the future. To correct this issue, update the timestamp of the safeset on the vault or wait until the backup time for the saf eset passes. To prepare the archive, complete these tasks: Create a retention schedule and enable archiving on the Agent. A retention policy applies only to safesets that are created after you enable archiving. To apply the retention policy to existing safesets, you must edit their Archive Retention setting. Add an archive storage location. See Adding an Archive Location. Assign the archive storage location to tasks you want to archive. See Assigning an Arc hive Storage Location to a Task.
18. 1
Assig ning an A rchi ve Storag e Loc ation to a Task
To assign an archive storage location to a task: 1. 2. 3. 4. Right -click a task in the left pane of the Director management c onsole and select Properties. Click the Task Propertie s tab. Select an archive storage location in the Archive area list. Click OK.
18. 2
Arc hivi ng S af es ets to Dis k
When you select a file system as the archive storage loc ation, the vvarchive command is used to archive data. The vvarchive process runs automatically when the number of retention days for a safes et is met or exceeded. Safeset data is transmitted to the archive storage location in SSI format. When a task is archived to disk, the computer name and task name are created as directories in order to determine which SSI file belongs to which task. An archived safeset has a different icon and its status is Offline.
Page 94
Archiving Data All references to pool system data for the archived safest are removed from the pool i ndex file. An optimization removes all data not referenced by other online safesets, and decreases the pool system size. The only reference remaining is in the safeset list. When a safeset moves to an archive, the physical location path changes to the arc hive storage location.
18. 3
Rec alli ng S af es ets
A recall is the retrieval of a safeset from an archive for a restore or export. When you recall a safeset, a copy of the archived safeset is added as a pool file in the main storage area of the task. The original archived safeset is not removed or deleted. The status of the safeset changes from Offline to Recalled. A retention period is applied to recalled safesets. When the number of days for retaining the recalled safeset is met or exceeded, the Online Migrate pr ocess removes the safeset from the vault. The Recall log records all changes made to a recalled safeset.
18. 4
Arc hivi ng Tasks
Note: Do not move safesets for the same task to both archive storage and secondary storage. Using archive and secondary storage on the same task is not supported, but is not prevent ed by the Director. To archive a task: 1. 2. 3. 4. Select an object in the left pane of the Director Management Console. From the Storage Management menu, choose Archive Tasks. Complete the Archi ve wizard. For field descriptions, see Archive Wizard Fields. Click Finish.
18.4.1
Archive Wizard Fields
The following fields appear in the Archive wizard:

Field Selected Organization/Customer Selected location Selected Computer Selected Task Description Specifies a specific customer. Specifies a specific customer location. Specifies a specific computer. Specifies a specific task.
Page 95
Field Submit job immediately Schedule job
Description Submits the job immediately. Creates a schedule to complete the job weekly or monthly.
Page 96
Activating Automated Maintenance
19 Activating Automated Maintenance

You can activate automated maintenance on a vault. Automat ed maintenance enforces safeset retention settings, optimizes and deduplic ates data, and checks pools for physical corruption. Automating maintenance can improve the efficiency of jobs such as backups and restores. Automated maintenance jobs run automatically during periods of low activity. Automated maintenance breaks large jobs into smaller jobs. This increases efficiency and prevents the locking of files and resources for extended periods. When you enable automated maintenance, the vault Administrator cannot modify the maintenance settings. Each day, the system cancels maintenanc e jobs older than 14 days that have not yet started or finished. Canc elled jobs are noted in the maintenance log and in e-mails to the system administrator, if an e-mail address is provided for the vault. For more information, see Setting Email Notifications. If maintenance jobs do not run for 14 days, the vault might be under -powered or under-sized. If you disable maintenance on a vault, any pending jobs are removed from the maint enance queue. To activate automat ed maintenance on a vault: 1. 2. 3. 4. 5. Select a vault in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Vault Settings. Click the Maintenance tab. Select Enable maintenance host on <Vault name> . Click OK.
19. 1
Ve rifyi ng A utom ated M aint en an ce is Ru nni ng
To verify automated maintenance is running: 1. 2. 3. 4. 5. 6. 7. Select a vault in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Services. Verify the state for the Queue Manager is Running. Click Close . Click Job Monitor and select Show Internal Jobs. Verify the status for the Maintenance Host is Running. Click Close .
Page 97
19. 2
Stopping Auto mat ed Mai ntenance
Stopping the maintenance host stops jobs that are in progress and removes pending jobs from the maintenance queue. When maintenanc e services restart, jobs that were already in progress restart automatically. To stop automated maintenance: 1. 2. 3. Click Job Monitor: Select Maintenance Host and click Stop. Click Yes.
19. 3
Ve rifyi ng M aint en ance Perfor m anc e
To verify maintenance performance: 1. 2. 3. Click Job Monitor: Select Maintenance Host. Click Progress. The Progress Information dialog box shows the number of jobs with the following status es: Running: The maintenance jobs that are currently running and using computer resources. A fixed number of Jobs can run at a time, even though the other queues may add up to more than the limit. A running job can have multiple waiting and pending objects Waiting: Submitted jobs that are idle and waiting for an event, such as another spawned task to finish. Pending: Queued jobs that are waiting for resources. If the number of waiting and pending jobs is continually increasing, contact Support for assistance. 4. 5. Click Close . Click Close again.
19. 4
Viewin g M aint en anc e Log s
Maintenance logs that are generated during a failed backup remain in the global log location because of storage policy restrictions. If your storage policy limit for disk storage is exceeded, logs cannot be written to storage. Normally, backup logs are moved to the task log location. Logs created from a Maintenance command are prefaced with Mc. If the scope is all tasks, the log entry is prefaced with McG, where G means Global scope.
Page 98
Activating Automated Maintenance To view maintenance logs: 1. 2. 3. Select a connection in the left pane of the Director Management Console. Double-click Logs in the right pane. Double-click a maintenance log file in the right pane.
19. 5
Ch ang es Af fecti ng Cu rrent Versio ns of t he Vault
The following table describes how improvements made to earlier versions of the vault affect later versions of the vault.
Component Workflow Description Backup does not submit vvmigrat online task <X>. It is expected that online global migrations are scheduled daily. Scheduler Uses the maintenance queue if you use the vvmigrat or vvpoolop commands. Maintenance commands are triggered by the Scheduler. Queue Manager The Queue Manager is the container in which the maintenance service operates. To submit a job to the maintenance service, specify the queue type MAINTEN ANCE. Jobs on the same task are processed in the same order they arrive. Only one job can execute at a time. Maintenance jobs are executed during periods of low activity (disk and CPU I/O). Maintenance jobs can have dual modes of operation; maintenance mode and user mode. You can run the same commands in the Queue Manager and the command line. The Maintenance command runs as a VVQmanager process.
Maintenance Commands
Locked tasks delay the execution of maintenance commands. When a locked task is identified, it is added to the list of tasks that are not available for maintenance. The list of unavailable tasks expires in 5 minutes and the maintenance command is run again.
Maintenance Retention Management
When you run a global vvmigrat command, it is separated into task levels and the same command is used for each task. A task level migrate online is separated into safeset range levels that are run individually.
Page 99
Component Maintenance Jobs
Description To avoid multiple, duplicate, global jobs, the Queue Manager verifies if newly submitted jobs are the same as the jobs currently running. If the jobs are identical, the Queue Manager cancels the running jobs and starts the new jobs.
Maintenance CheckCRC Maintenance Optimization
Global CheckCRCs are split into task levels. Task level CheckCRCs are split into file levels. The same command is submitted for each task. Global optimizes are split into task levels. Task level optimizes are split into file -group levels. Then, Optimize or Delete the file-level groups.
19. 6
Sch eduli ng V ault Mai ntenanc e
The file pool can bec ome fragmented when it is updated and migrated. To avoid fragmentation, use the Director Management Cons ole to schedule a weekly Pool Optimization command to optimize your vault. You should schedule Pool Optimization command to run during periods of low activity such as a week end. Before running the Pool Optimization command, you can run a deduplication command. The deduplication command identifies duplicate blocks for deletion during the optimization. If you upgrade a vault to version 6 or lat er, the default setting is no deduplication when running the Pool Optimization command. For new vault installations, deduplication runs every Saturday by default. To check the integrity of your vault, it is recommended that you schedule a weekly Pool System diagnosis.
19. 7
Enabli ng A utom ated Second ary Sto rage Mai nte nance
You can use thes e scheduled entries to automate secondary storage pool maintenance: Delet e expired secondary safesets Optimize secondary pools The scheduled entries are disabled by default. To enable automated scheduled storage maint enance: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Select Delete expired secondary safesets in the De scription list.
Page 100
Activating Automated Maintenance 4. 5. 6. 7. Click Enable . Select Optimize secondary pool s in the Description list. Click Enable . Click OK.
Page 101
20 Managi ng the Vault

This section provides information and procedures for managing the vault, including modifying settings, scheduling entries, and starting vault services. For more information, see Modifying Advanced Vault Settings, Creating a Custom Scheduled Entry and Starting a Vault Service.
20. 1
Viewin g th e Job Monito r
You use the Job Monitor to view and monit or the vault activities, including: Backup jobs Restore jobs Internal jobs Completed jobs Jobs waiting to run (in a queue) To view the Job Monitor, click Job Monitor: During periods of high activity, the Job Monitor might be slow to respond to commands. In addition, a large number of jobs that are running concurrently can affect the res ponsiveness of Job Monitor commands. Completed and replication jobs are displayed in the Job Monit or for one hour. You cannot edit this setting.
20. 2
Pin ning t he Job Monito r to you r D es ktop
To permanently display the Job Monitor on your desktop: 1. 2. Click Job Monitor. Click the Pin icon:
20. 3
Stopping a Job
To stop a job: 1. 2. 3. Click Job Monitor. Select a job and click Stop. Click Yes.
Page 102
Managing the Vault
20. 4
Settin g the Numb er of Co nc urrent Jobs
To set the number of concurrent jobs that can run on the vault: 1. 2. 3. 4. From the Vault Maintenance menu, choose Vault Settings. Click the Advanced tab. Select the number of concurrent Jobs in the Maximum number of jobs field. The default is 25. Click OK.
20. 5
Viewin g a Log File fro m th e Job Mo nitor
To view a log file from the Job Monitor: 1. 2. Click Job Monitor. Select a job and click View Log.
20. 6
Settin g Email Noti ficatio ns
To receive an email notification when a failure occurs or a job completes: 1. 2. 3. From the Vault Maintenance menu, choose Vault Settings. Click the Email Notifications tab. Select your notification options in the Notification area: On successful job completion you receive an email when a job completes successfully. On job failure you receive an email when a job fails. On device notification you receive an email when a Univers al Naming Convention (UNC) connection is inaccessible. On replication failure you receive an email when a replication session fails. 4. Enter an SMTP address in the SMTP server network address field if you want to receive a generated report instead of a log file. 5. Enter the email address for the recipients of the email notifications in the Specify address(e s) of recipients below field. To enter multiple addresses, use a comma as a separator. 6. Click OK.
Page 103
20. 7
Ch angi ng a R egist ered Com puter's Ag ent Typ e
Typically, you change the Agent type when the vault cannot identify the Agent type during computer registration process. To change a registered computer's Agent type: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand the Locations list. Expand a Location. Expand the Regi stered Computers list. Right -click a registered comput er and select Properties. Click Change Agent Type . Select an Agent type in the New Agent Type list.
10. Click OK.
20. 8
Req ue sting an Al ert Notifi catio n
You can have an alert sent to a comput er when a Job fails on the vault. To request an alert notification: 1. 2. 3. 4. 5. From the Vault Maintenanc e menu, choose Vault Settings. Click the Alerts tab. Select Send notification when a job fails. Enter a computer address in the Send alerts field. Click OK.
20. 9
Ch angi ng th e Pu rg e Log S etting
To change the number of days log files are kept before they are purged: 1. 2. 3. From the Vault Maintenance menu, choose Vault Settings. Click the Logs tab. In the Purge logs after field, specify the number of days for keeping logs.
Page 104
Managing the Vault 4. 5. In the Minimal number of log files field, specify the minimum number of logs to keep. Click OK.
20. 10 Modifyi ng Adv anc ed Vault S ettings

To modify advanced vault settings: 1. 2. 3. 4. From the Vault Maintenance menu, choose Vault Settings. Click the Advanced tab. Edit the advanced setting fields. For field descriptions, see Advanced Vault Setting Fields. Click OK.
20.10.1
Advanced Vault Setting Fields
The following fields appear on the A dvanced tab of the Vault Settings dialog box:
Field Server ports Description The server ports configured for the vault. The default port is 2546. Separate ports with a comma. Multiple ports are attempted in order from left to right. If you change ports, you must restart the Listener service or the computer. Socket timeout The time in seconds that the socket remains open as the Listener waits to complete an Agent request. The default is 30 seconds. Lowering this value can cause communication errors. Raising this value can consume system resources and cause delays. Ma ximum Socket Connections Open Pool Files Limit The number of pool files that run concurrently. The default is 10. The maximum number of allowed socket connections. The default is 250.
Ma ximum number of jobs The number of jobs that can run concurrently. The default is 25 New password Resets the current Database Administrator password. The new password must adhere to the Windows password policy. If you change the DBA password, you must restart the vault services. Confirm password Confirms the new Database Administrator password.
Page 105
20. 11 Modifyi ng Age nt Co nn ection Setti ngs

If the vault is licensed for replication, you can use the Agent Connection tab in the Vault Settings dialog box to modify the Agent connection settings for backups and restores. To modify the Agent connection settings: 1. 2. 3. 4. From the Vault Maintenance menu, choose Vault Settings. Click the Agent Connection tab. Edit the connection settings for the Agent. Click OK.
20. 12 Ch angi ng th e Tim e th at a Sch ed uled Servi ce Ru ns

To change the time that a scheduled service runs: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Select a scheduled service in the De scription list. Click Edit. Complete the Change Schedule Entry wizard. Click Finish.
20. 13 Cre ating a C usto m Sc hed uled Ent ry

The command or batch file must reside in the <...>\Director\prog directory. You cannot edit a custom scheduled ent ry after you creat e it. To edit a custom scheduled entry, you must delete it and t hen recreate it. To view log entries for custom scheduled entries, view the spawn logs. To create a custom scheduled entry: 1. 2. 3. 4. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Click Custom . Complete the Custom Command Scheduling wizard. For a list of supported commands, see the Command Reference. 5. Click Finish.
Page 106
Managing the Vault
20. 14 Disabling a S ch edul ed Ent ry

To disable a scheduled entry: 1. 2. 3. 4. 5. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Select a scheduled service in the De scription list. Click Disable . Click OK.
20. 15 Enabli ng a Sc hed uled E ntry

To enable a scheduled entry: 1. 2. 3. 4. 5. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Select a scheduled service in the De scription list. Click Enable . Click OK.
20. 16 Re movin g a Sch edul ed E ntry

To remove a scheduled entry: 1. 2. 3. 4. 5. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Schedule Entrie s. Select a scheduled service in the De scription list. Click Remove . Click OK.
20. 17 Starting a V ault Servi ce

To start a vault service: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Services. Select a service in the Service Name list. To select multiple services, press CTRL and select the servic es.
Page 107
Director 7.0 Operations Guide 4. 5. Click Start. Click OK.
20. 18 Stopping a V ault Servi ce

To stop a vault service: 1. 2. 3. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Services. Select a service in the Service Name list. To select multiple services, press CTRL and select the servic es. 4. 5. Click Stop. Click OK.
20. 19 Pu rgin g Acti vity Record s and Log s

You can purge, or delete, activity records and logs. Unlike log files, activity records are not deleted automatically. Activity records list the time of completion, file size, and success messages for backup, restore, and migrate tasks . Activity report information is used to generate reports. To purge activity records and logs: 1. 2. Select a vault connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Purge Acti vity/Logs. The Purge wizard appears. 3. 4. On the Welcome page, click Next. On the Select Purge Type page, do one of the following: To delet e log files, select Purge log files, and then click Next. To delet e activity records, select Purge activity records. In the Purge activities older than x days field, enter number of days of activity records that you want to keep. Click Next. 5. On the Command Execution time page, do one of the following: To delet e files immediately, select Submit job immediately, and then click Next. To delet e files later, select Schedule job, click Next, and then specify a weekly or monthly schedule for deleting the files. 6. Click Finish.
Page 108
Managing the Vault
20. 20 Bac kin g up a V ault wit h dbB ac kup

The dbBackup.exe database backup utility is included with EVault Software Direct or. By default, dbBackup runs automatically at midnight every day. The scheduled dbB ackup automatically extracts the databas e data from the <database> directory, to the data.bin file. When dbB ackup is running, the vault database is read only. If you are using Vault Backup Agent (VBA) to back up your vault, you do not need to use dbBackup. If a folder is not specified during the backup, the C:\DBBACK UP folder is creat ed. When a folder is not specified during a restore, this default folder is used. The default user name and password are used. The default username and password are stored in a Vault DB.cfg. To view information about a backup, open the DBBackup-XXXXXXXX- XXXX.LOG in the logs directory. You can also use the Job Monit or to view backup information. To view the syntax and options available for the dbBackup command, see dbbackup or open a command prompt and enter the following command: dbbackup /?
20. 21 Bac kin g up a V ault wit h VB A

The Vault Backup Agent (VBA) is a vault plug-in that you use to back up vault data to another vault, or a local disk. VBA is a separately licensed product, with its own installation and user guides. You use CentralControl to configure and manage VBA. When a VBA backup runs, it has a high er priority than maintenance reader or writer tasks such as vvpoolop. To allow a VBA backup to complete quickly, VBA interrupts lower priority tasks. You should stop all vault servic es when you restore the entire vault. However, the database must be running.
Page 109
21 Creating and Running Reports

You can configure and run the following Director reports: Storage . The Storage report shows the number of safesets and amount of data in a vault for a single task, or for each task in a vault, organization/customer, location, or computer. See Creating a Storage Report. Storage Location. The Storage Location report lists all primary, secondary and archive storage locations for one task, or for each task in a vault, organization/customer, location, or computer. See Creating a Storage Location Report. Vault Storage . The Vault Storage report shows the number of customers, number of servers and the total amount of storage in a vault. The amount of storage includes both primary and secondary storage. See Creating a Vault Storage Report. Last Backup Status. The Last Backup Status report shows information about the last backup for one task, or for each task in a vault, organization/customer, location, or computer. See Creating a Last Backup Status Report. Late Server Status. The Late Server Status report lists tasks that were not backed up in a specified amount of time before the current time, and shows the last bac kup date and time for each task. See Creating a Late Server Status Report. Missed Backups. The Missed Backups report lists backup tasks that were scheduled or expected to run, but for which a safeset does not exist. See Creating a Missed Backups Report. Storage Pool Summary. The Storage Pool Summary report shows the amount of disk space allocated to one task, or to each task in a vault. See Creating a Storage Pool Summary Report. You can also run a Storage, Storage Location, or Last Back up Status report quickly from the left pane of the Director Management Console. For more information, see Running a Storage, Storage Location or Last Backup Status Report. When you configure a report, you can run the report immediately, or schedule it to run on specific days in a week or mont h at a specific time. For more information, see Creating Schedules for Running Reports.
21. 1
Run nin g a Storag e, St o rage Lo catio n or L ast Bac ku p St atus Report
You can run a Storage, Storage Location, or Last Backup Status report from the left pane of the Director Management Console. When you run a report from the left pane of the Director Management Console, it is saved as a log file. Storage and Storage Location reports are created in organized column format, and Last Backup Status reports are created in CSV format. If you want to create a schedule for running a report, e-mail a report to a recipient, or create a Storage report in CSV format, you must configure the report using the Report wizard. For more information, see
Page 110
Creating and Running Reports Creating a Storage Report, Creating a Storage Location Report, and Creating a Last Backup Status Report. To run a Storage, Storage Location or Last Backup Status report: 1. In the left pane of the Director Management Cons ole, right -click the vault, organization/customer, location, computer, or task for the report. 2. From the shortcut menu, choose the type of report to run: Storage Report, Storage Location Report, or Last Backup Status.
21. 2
Cre ating a Sto rage Report
The Storage report shows the number of safes ets and amount of dat a in a vault for a single task, or for each task in a vault, organization/customer, location, or computer. A report sample appears at the end of the procedure that follows. For each task, and in totals for each organization/computer, location, customer and vault, the report provides information in the following fields:
Field Media Description Location of the task's safesets. Possible values are:

Gen
PR primary storage SE secondary storage OF offline (i.e., detached) storage N/A not applicable. There are no safesets for the task.
Number of safesets for the task. The number of safesets is shown separately for each storage location (i.e., primary, secondary and offline).
Original
Total amount of original data protected by the task's safesets. This value is the sum of the safesets' Original size values. The Original size values are provided by the Agent. The amount of data is shown separately for each storage location (i.e., primary, secondary and offline).
Page 111
Field Compres'd
Description Total amount of compressed data in the safesets. This value is the sum of the safesets' Compressed size values. The Compressed size values are provided by the Agent. The amount of data is shown separately for each storage location (i.e., primary, secondary and offline).
Poolsize
Size of the task's pool. The amount of data is shown separately for each storage location (i.e., primary, secondary and offline).
You can use the following procedure to configure and run or schedule a Storage report. You can also run a Storage report quickly from the left pane of the Director Management Console. For more information, see Running a Storage, Storage Location or Last Backup Status Report . To create a Storage Report: 1. In the left pane of the Director Management Cons ole, select the vault connection for running a Storage History report. From the Reporting menu, choose S torage . The Report wizard appears. 2. 3. On the Welcome screen, click Next. On the Report Media screen, specify the report destination. For more information, see Selecting the Destination for a Report. 4. Select one of the following Output Style Format options: To format the report in columns, select Organized column format. To create the report in comma-separated values (CSV) format, select CSV format (comma separated). 5. 6. Click Next. On the Select Scope screen and any subsequent selection screens, choose data to include in the report. For more information, see Selecting the Scope for a Report. 7. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 8. On the Report Wizard completion page, review the report information, and then click Finish.
Page 112
Creating and Running Reports Storage Report Sample Note: Column widths in Storage reports are wider than shown here.
+---------------------------------------------------------------------------- + | EVAULT STORAGE HISTORY REPORT 3-JAN-2012 09:27:20.46 -0500 | | | | Server: VAULT Customer: <all> | | Location: <all> | | Start Date: <none> Computer: <all> | | End Date: <none> Task: <all> | +---------------------------------------------------------------------------- + Customer Location Computer Task Media Gen Original Compres'd ~Poolsize -------- -------- ------------- --------------- ----- --- ---------- ---------- ---------CUSTOMER1 LOCATION1 COMPUTER1 TASK1 PR 1 1.9MB 0bytes 1.1MB TASK2 PR 1 1.9MB 0bytes 878.9KB TASK3 PR 7 5.8GB 736.9MB 1.1GB TASK4 PR 15 12.4GB 1.5GB 1.5GB TASK5 PR 3 3.1GB 315.7MB 1.1GB ------------------------------- ----- --- ---------- ---------- ---------Computer Total PR 27 21.2GB 2.6GB 3.8GB ------------------------------------------ ----- --- ---------- ---------- ---------Location Total PR 27 21.2GB 2.6GB 3.8GB ----------------------------------------------------- ----- --- ---------- ---------- ---------Customer Total PR 27 21.2GB 2.6GB 3.8GB ----------------------------------------------------- ----- --- ---------- ---------- ---------Vault Total PR 27 21.2GB 2.6GB 3.8GB
21. 3
Cre ating a Sto rage Lo catio n R epo rt
A Storage Location report lists all primary, secondary and arc hive storage locations for one task, or for each task in a vault, organization/customer, location, or computer. A report sample appears at the end of the procedure that follows. You can use the following procedure to configure and run or schedule a Storage Location report. You can also run a Storage Location report quickly from the left pane of the Director Management Console. For more information, see Running a Storage, Storage Location or Last Backup Status Report. To create a Storage Loc ation report: 1. In the left pane of the Director Management Cons ole, select the vault connection for running a Storage Location report. 2. From the Reporting menu, choos e Storage Locations. The Report wizard appears.
Page 113
Director 7.0 Operations Guide 3. 4. On the Welcome screen, click Next. On the Report Media screen, specify the report destination, and then click Next. For more information, see Selecting the Destination for a Report. 5. On the Select Scope screen and any subsequent selection screens, choos e data to include in the report. For more information, see Selecting the Scope for a Report. 6. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 7. On the Report Wizard completion page, review the report information, and then click Finish.
Storage Location Report Sample

+---------------------------------------------------------------------------- + | EVAULT STORAGE LOCATION REPORT 3-JAN-2012 09:30:27.77 -0500 | | | | For Server: VAULT | +---------------------------------------------------------------------------- + Customer Location Computer Task Storage Locations -------- -------- ------------- --------------- ----------------CUSTOMER1 LOCATION1 COMPUTER1 TASK1 Primary: C:\Vault\W2008\pool1\ Secondary: C:\SECONDARY\ {SEC} Archive: C:\ARCHIVE\ TASK2 Primary: C:\Vault\W2008\pool2\ Secondary: C:\SECONDARY\ {SEC} Archive: C:\ARCHIVE\ TASK3 Primary: C:\Vault\W2008\pool3\ Secondary: C:\SECONDARY\ {SEC} Archive: C:\ARCHIVE\ TASK4 Primary: C:\Vault\W2008\pool4\ Secondary: C:\SECONDARY\ {SEC} Archive: C:\ARCHIVE\ TASK5 Primary: C:\Vault\W2008\pool5\ Secondary: C:\SECONDARY\ {SEC} Archive: C:\ARCHIVE\
Page 114
Creating and Running Reports
21. 4
Cre ating a V ault Sto rag e R epo rt
The Vault Storage report shows the number of customers, number of servers and the total amount of storage in a vault. A report sample appears at the e nd of the procedure that follows. The amount of storage includes bot h primary and secondary storage. Secondary storage is included in the total amount of storage regardless of whether it is attached or not. To create a Vault Storage report: 1. In the left pane of the Director Management Cons ole, select the vault connection for running a Vault Storage Report. 2. From the Reporting menu, choos e Vault Storage . The Report wizard appears. 3. 4. On the Welcome screen, click Next. On the Report Media screen, in the Send generated report by email to field, enter one or more email addresses where you want to send the report. Email addresses must be separated by commas. Note: The Vault Storage report cannot be saved as a log file. Before you can run the Vault Storage report, an SMTP server network address must be entered in Vault Settings. For more information, see Setting Email Notifications. 5. 6. Click Next. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 7. On the Report Wizard completion page, review the report information, and then click Finish.
Vault Storage Report Sample

+---------------------------------------------------------------------------- + | VAULT STORAGE REPORT 3-JAN-2012 09:32:12.30 -0500 | | | | Vault Name: Vault1 Vault Domain: | | Vault ID: 2136085941 | +---------------------------------------------------------------------------- + Total Customers Total Servers Total Storage --------------- ------------- ------------1 1 3.81 GB
Page 115
21. 5
Cre ating a L ast B ac kup Stat us Report
The Last Backup Status report shows information about the last backup for one task, or for eac h task in a vault, organization/customer, location, or computer. The report is available only in comma -separat ed values (CSV ) format. A report sample appears at the end of the procedure that follows. For each task, the report includes information in the following fields:
Field LastSynch# Date Original Description Highest safeset number for the task. Date of the last safeset for the task Amount of original data protected by the safeset. The Original size value is provided by the Agent. Compres'd Amount of compressed data in the safeset. The Compressed size value is provided by the Agent. Delta Difference in amount of data protected by the last safeset and the previous safeset.
You can use the following procedure to configure and run or schedule a Last Backup Status report. You can also run a Last Backup Status report quickly from the left pane of the Director Management Console. For more information, see Running a Storage, Storage Location or Last Backup Status Report. To create a Last Backup Status report: 1. In the left pane of the Director Management Cons ole, select the va ult connection for running a Last Backup Status report. 2. From the Reporting menu, choos e Last Backup Status. The Report wizard appears. 3. 4. On the Welcome screen, click Next. On the Report Media screen, specify the report destination, and then click Next. For more information, see Selecting the Destination for a Report. 5. On the Select Scope screen and any subsequent selection screens, choose data to include in the report. For more information, see Selecting the Scope for a Report.
Page 116
Creating and Running Reports 6. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 7. On the Report Wizard completion page, review the report information, and then click Finish.
Last Backup Status Report Sample

"Customer","Location","Computer","Task","LastSynch#","Date","Original","Compres'd","Delta" "CUSTOMER1","LOCATION1","COMPUTER1","TASK1","2054","18-OCT-2011 21:20","1,997,776","0","0" "CUSTOMER1","LOCATION1","COMPUTER1","TASK2","2068","03-NOV-2011 21:20","1,997,776","0","0" "CUSTOMER1","LOCATION1","COMPUTER1","TASK3","11","27-DEC-2011 14:25","1,217,595,364","110,195,704","110,690,444" "CUSTOMER1","LOCATION1","COMPUTER1","TASK4","15","27-DEC-2011 14:47","1,660,357,140","110,563,064","110,690,444" "CUSTOMER1","LOCATION1","COMPUTER1","TASK5","11","27-DEC-2011 12:46","1,217,595,364","110,236,504","110,690,444"
21. 6
Cre ating a L ate S erv er Stat us Repo rt
A Late Server Status report lists tasks that do not have safes ets from the specified amount of time before the current time, and shows the last backup date and time for each task. A report sample appears at the end of the procedure that follows. To create a Late Server Status report: 1. In the left pane of the Director Management Cons ole, select the vault connection for ru nning a Late Server Status report. 2. From the Reporting menu, choos e Late Server Status. The Report wizard appears. 3. 4. On the Welcome screen, click Next. On the Report Media screen, specify the report destination, and then click Next. For more information, see Selecting the Destination for a Report. 5. On the Report Settings screen, in the Report all tasks that have not backed up in the past x hours field, enter the number of hours before the current time for including tasks. Tasks appear in the report if they have not been backed up in the specified amount of time before the current time. By default, the report lists tasks that have not been backed up in the past 48 hours.
Page 117
Director 7.0 Operations Guide 6. On the Select Scope screen and any subsequent selection screens, choose data to include in the report. For more information, see Selecting the Scope for a Report. 7. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 8. On the Report Wizard completion page, review the report information, and then click Finish.
Late Server Status Report Sample

Late Server Status Report Report Scope: Entire Vault; Report Time Frame: 1-JAN-2012 09:34:04.05 -0500 To 3-JAN-2012 09:34:04.05 -0500 The following tasks have not been backed up in the past 48 hours "Customer","CustomerEmail","Location","LocationEmail","Computer","Task","LastBackupDate" "CUSTOMER1","customer1@address.com","LOCATION1","customer1@address.com","COMPUTER1","TASK1","18 OCT-2011 21:20:09.70 -0500" "CUSTOMER1","customer1@address.com","LOCATION1","customer1@address.com","COMPUTER1","TASK2"," 3 NOV-2011 21:20:26.91 -0500" "CUSTOMER1","customer1@address.com","LOCATION1","customer1@address.com","COMPUTER1","TASK3","27 DEC-2011 14:25:20.69 -0500" "CUSTOMER1","customer1@address.com","LOCATION1","customer1@address.com","COMPUTER1","TASK4","27 DEC-2011 14:47:48.33 -0500" "CUSTOMER1","customer1@address.com","LOCATION1","customer1@address.com","COMPUTER1","TASK5","27 DEC-2011 12:46:57.63 -0500"
21. 7
Cre ating a Mi ss ed B ac kup s R epo rt
The Missed Backups report lists backup tasks that were scheduled or expected to run, but for which a safeset does not exist. A task appears in the report even if the scheduled or expected backup ran successfully but the committed safeset was later deleted. The report lists tasks with missed backups, and shows the expected backup time and detected backup time (time of the last existing safeset) of each task. A report sample appears at the end of the procedure that follows. A backup task appears in the Missed Backups report if one of these is true: The task is scheduled in CentralControl, but there is no safeset from the last scheduled backup. A task appears only once in the report even if there are no safesets for multiple scheduled backups. The task is not scheduled in CentralControl, a safeset exists for the task from before the report timeframe, and no safes et exists for the task from during the timeframe. The report timeframe is based on the amount of time entered when you create the Missed Backups report, and is measured back from the current local time on the vault when the report runs. For example,
Page 118
Creating and Running Reports if you specify 48 hours for the report and the report runs on November 21, 2011 at 10:00, the report includes unscheduled backup tasks with safesets dated before November 19, 2011 at 10:00, and no safesets dated bet ween November 19, 2011 at 10:00 and November 21, 2011 at 10:00. Note: The timeframe does not have any effect on tasks scheduled in CentralControl. For a missed backup that is scheduled in CentralControl, the expected backup time in the report is the last date when the report was scheduled to run, and the time of the last existing safeset (or 00:00 GMT if there are no safesets). For example, if a backup task named Job1 was scheduled to run on November 20, 2011, but the last safeset is from November 16, 2011 at 13:01, the expected backup time is November 20, 2011 at 13:01, as shown in the following example: Computer TaskName ExpectedBackupTime DetectedB ackupTime DetectedFailure ---------------------------------------------------------------------------------COMP UTER1 JOB1 20-NOV-2011 13: 01 16-NOV-2011 13: 01 00-000-0000 00:00 For a missed backup that is not scheduled in CentralControl, the expected backup time in the report is the start of the timeframe. For example, if the report runs on November 21, 2011 at 10:00 with a timeframe of 48 hours before the current vault time, and the last safeset for a task named Job2 that is not scheduled in Cent ralCont rol is dated before the timeframe, the expected backup time is November 19, 2011 at 10:00, as shown in the following ex ample: Computer TaskName ExpectedBackupTime DetectedB ackupTime DetectedFailure
---------------------------------------------------------------------------------
COMP UTER2 JOB2
19-NOV -2011 10:00
16-NOV -2011 13:01
00-000-0000 00:00
Note: Backup tasks which occur in the future according to the vault time do not appear in the Missed Backups report. To create a Missed Backups report: 1. In the left pane of the Director Management Cons ole, select the vault connection for running a Missed Backups report. 2. 3. From the Reporting menu, choos e Mi ssed Backups. In the left pane of the Mi ssed Backups Report Configuration screen, select the customers, locations, computers, and tasks for the report. 4. In the right pane of the screen, ent er an amount of time in the Show Reports for Mi ssed or Failed Backups Before the Previous x Hours field. Note: The amount of time only affects whether tasks that are not scheduled in CentralControl appear in the report. The time does not affect whether tasks scheduled in CentralControl appear in the Missing Backups report. 5. In the Send Report To pane, specify recipients for the report.
Page 119
Director 7.0 Operations Guide 6. (Optional) To format report dat a as a CSV file, select Format Report Data in CSV (Comma Separated Values). 7. Do one of the following: To run the report immediat ely, click Submit Now . To schedule the report to run weekly or monthly on a specific day at a specific time, click Schedule . On the Change Schedule Entry Wizard screen, click Next. On the Select the Execution Cycle screen and subsequent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. Missed Backups Report Sample
+---------------------------------------------------------------------------- + | 22-NOV-2011 11:06:47.33 -0500 | | | | Server: SERVER1 Customer: CUSTOMER1 | | Location: <all> | | Start Date: <none> Computer: <all> | | End Date: <none> Task: <all> | +---------------------------------------------------------------------------- + *************************** Customer name: CUSTOMER1 *************************** Computer TaskName ExpectedBackupTime DetectedBackupTime DetectedFailure ------------------------------------------------------------------------------------------------COMPUTER1 TASK1 22-NOV-2011 09:25 16-NOV-2011 09:25 00-000-0000 00:00 COMPUTER1TASK2 15-NOV-2011 11:51 14-NOV-2011 11:51 00-000-0000 00:00 COMPUTER1TASK3 22-NOV-2011 09:30 21-NOV-2011 09:30 00-000-0000 00:00 COMPUTER1TASK4 22-NOV-2011 09:30 21-NOV-2011 09:30 00-000-0000 00:00 COMPUTER1TASK5 22-NOV-2011 09:30 21-NOV-2011 09:30 00-000-0000 00:00
21. 8
Cre ating a Sto rage Pool S um mary Report
The Storage Pool Summary report provides information about the amount of disk space allocated to one task, or to each task in a vault. For eac h task, the report shows the total physical size of the pool, the total amount of actual data in the pool, and an estimated amount of storage space that could be reclaimed through optimization. A report sample appears at the end of the procedure that follows. To create a Storage Pool Summary report: 1. In the left pane of the Director Management Cons ole, select the vault connection for running a Storage Pool Summary report. 2. From the Reporting menu, choos e Storage Pool Summary.
Page 120
Creating and Running Reports The Report wizard appears. 3. 4. On the Welcome screen, click Next. On the Scope screen, do one of the following: To include data for a specific task, click By Computer. To include task data for the entire vault selected in the Director Management Console, select Entire Vault. 5. (Optional) To include secondary storage information in the report, select the Include secondary storage in this report option. 6. 7. Click Next. (If applicable) If you are running the report for a specific computer, the Select Organization/Customer screen appears. Select the organization or customer for the report, and then click Next. On the Select Location screen, select the location for the report, and then click Next. On the Select Computer screen, select the computer for the report, and then click Next. On the Select Task screen, select the task for the report, and then click Next. 8. On the Command Execution Time screen, do one of the following: To run the report, click Submit job immediately, and then click Next. To create a schedule for running the report, click Schedule job, and then click Next. On the Select the Execution cycle screen and subs equent screens, create a schedule for running the report. For more information, see Creating Schedules for Running Reports. 9. On the Report Wizard completion page, review the report information, and then click Finish.
Storage Pool Summary Report Sample

Vault: VAULT1 EVault Software Director Pool Report task details: summaryall task * task started at 3-JAN-2012 09:37:30.35 -0500 Analyzing task: 'CUSTOMER1/LOCATION1/COMPUTER1/TASK1' UPGV5_CD529D22-C209-47FE-8762-5A1143C224CE Online Pool total physical size of the pool: 1,149,660 (1.1 MB) total actual data in the pool: 855,841 (835.8 KB) total space to reclaim, if optimized: 293,819 (286.9 KB) Analyzing task: 'CUSTOMER1/LOCATION1/COMPUTER1/TASK2' UPGV5_F35AF390-C9C7-4274-9AD3-CA96037CEF8C Online Pool 900,036 (878.9 KB) total actual data in the pool: 848,916 (829.0 KB) POOL-I-0000 total space to reclaim, if optimized: 51,120 (49.9 KB)
Page 121

Analyzing task: 'CUSTOMER1/LOCATION1/COMPUTER1/TASK3' UPGV5_10EC0212-116C-4400-A8A2-6A618EA18F74 Online Pool total physical size of the pool: 1,217,602,629 (1.1 GB) total actual data in the pool: 1,217,601,413 (1.1 GB) total space to reclaim, if optimized: 1,216 (1.2 KB) Analyzing task: 'CUSTOMER1/LOCATION1/COMPUTER1/TASK4' UPGV5_C7CB069D-FD04-4241-8A34-03AEFB433EAD Online Pool total physical size of the pool: 1,658,906,301 (1.5 GB) total actual data in the pool: 1,658,906,301 (1.5 GB) total space to reclaim, if optimized: 0 (0 bytes) Jan03 09:37:34.118 [3732] POOL-I-0001 Analyzing task: 'CUSTOMER1/LOCATION1/COMPUTER1/TASK5' UPGV5_C522A150-0209-40B9-8D3D-A1B33331ACB3 Online Pool total physical size of the pool: 1,217,262,658 (1. 1 GB) total actual data in the pool: 1,217,260,154 (1.1 GB) total space to reclaim, if optimized: 2,504 (2.4 KB) Task 'CUSTOMER1/LOCATION1/COMPUTER1/QSMImport' is disabled. Will not process it. Totals: total physical size of analyzed pools: 4,095,821,284 (3.8 GB) total actual data in analyzed pools: 4,095,472,625 (3.8 GB) total space to reclaim, if optimized: 348,659 (340.5 KB) POOL-I-0000 total # of errors: 0 ============================================================================================== Total # of tasks processed 5 # of successful tasks 5 # of disabled tasks 1 # of tasks with error(s) 0 # of errors in failed tasks 0 task completed at 3-JAN-2012 09:37:34.18 -0500 ==============================================================================================
21. 9
Sel ecting t he Destin ation for a R epo rt
When creating a report, you can specify whether to save a report as a log file or e -mail the report to a recipient. You can select the report destination for a Storage, Storage Location, Vault Storage, Last Backup Status, or Lat e Server Status report. To select the destination for a report: 1. When creating a report using the Report wizard, navigate to the Report Media screen. For more information, see Creating a Storage Report, Creating a Storage Location Report, Creating
Page 122
Creating and Running Reports a Vault Storage Report, Creating a Last Backup Status Report or Creating a Lat e Server Status Report. 2. On the Report Media screen of the Report wizard, select one of the following Out put Location options: To save the report as a log file, select Save report in a vault log file . Note: This option is not available for the Vault Storage report. To send the report by e-mail to one or more recipients, select Send generated report by Email to. In the field below this option, enter one or more email addresses to send the report to. Multiple email addresses must be separated by commas. Note: Before you can send reports by e-mail, an SMTP server must be specified in Vault Settings. For more information, see Setting Email Notifications. Note: When creating a Storage report, you can also specify whet her data appears in columns or in CSV format on the Report Media screen. For more information, see Creating a Storage Report. 3. Continue creating the report.
21. 10 Sel ecting t he Scop e fo r a R epo rt

When creating a report, you can specify whether to run the report for an entire vault, or restrict the report to a specific organization/customer, location, computer or task. You can select the report scope for a Storage, Storage Location, Last Backup Status, or Late Server Status report. You can also select the report scope for a Missed Backups or Storage Pool Summary report, using different procedures than described here. For more information, see Creating a Missed Backups Report and Creating a Storage Pool Summary Report. To select the scope for a report: 1. When creating a report using the Report wizard, navigate to the Select Scope screen. For more information, see Creating a Storage Report, Creating a Storage Location Report, Creating a Vault Storage Report, Creating a Last Backup Status Report or Creating a Late Server Status Report. 2. Do one of the following: To include data for the entire vault selected in the Director Management Console, click Vault, and then click Next. To restrict the report to a specific organization or customer, click Organization/Customer, and then click Next. On the Select Organization/Customer screen, select the organization or customer for the report, and then click Next.
Page 123
Director 7.0 Operations Guide To restrict the report to a specific location, click Location, and then click Next. On the Select Organization/Customer screen, select the organization or customer for the report, and then click Next. On the Select Location screen, select the location for the report, and then click Next. To restrict the report to a specific computer, click Computer, and then click Next. On the Select Organization/Customer screen, select the organization or customer for the report, and then click Next. On the Select Location screen, select the location for the report, and then click Next. On the Select Computer screen, select the comput er for the report, and then click Next. To restrict the report to a specific task, click Task, and then click Next. On the Select Organization/Customer screen, select the organization or customer for the report, and then click Next. On the Select Location screen, select the location for the report, and then click Next. On the Select Computer screen, select the computer for the report, and then click Next. On the Select Task screen, select the task for the report, and then click Next. 3. Continue creating the report.
21. 11 Cre ating S ch edul es for Ru nni ng R epo rts

After creating a report, you can run the report immediately, or create a schedule for running the report. For example, you can create a schedule for running a report monthly or weekly on a specific day and time. To create a schedule for running a report: 1. When creating a report using the report wizard, navigate to the Select the Execution Cycle screen. For more information, see Creating a Storage Report, Creating a Storage Location Report, Creating a Vault Storage Report, Creating a Last Backup Status Report, Creating a Late Server Status Report, Creating a Missed Backups Report or Creating a Storage Pool Summary Report. 2. Do one of the following: To run the report on one or more days each week, click Weekly, and then click Next. On the Weekly Cycle screen, click each day to run the report each week. In the Time field, ent er the time when you want to run the report each day. Click Next. To run the report on one or more days each month, click Monthly, and then click Next. On the Monthly Cycle screen, click each day to run the report each month. In the Time field, enter the time when you want the run the report each dat e. Click Next. 3. On the completion screen, review the report information, and then click Finish.
Page 124
Creating and Running Reports
21. 12 Viewin g R epo rts

After running a report, you can find the report in the Director Management Console a nd view the report. For information about running reports, see Creating and Running Reports. Note: The following procedure is used to open and view most reports in the Director Management Cons ole. To view a Storage Pool Summary report for a single task, see Viewing a Storage Pool Summary Report for a Task. To view a report: 1. 2. In the left pane of the Director Management Cons ole, select the report 's vault. In the right pane of the Director Management Console, double-click Logs. A list of report and log files appears in the right pane of the Console. Report files have the following names:
Report Storage Storage Locations Vault Storage Last Backup Status Late Server Status Report Missed Backups Storage Pool Summary File Name in Director Management Console StorageUsageReport StorageLocationReport VaultStorageReport LastBackupStatusReport LateServerStatusReport MissedBackupsReport Pool Summary
3.
(As applicable) If the report you want to view does not appear in the right pane of the Director Management Console, click Refresh to updat e the report and log file list.
4.
In the Log name column, double-click the report you want to view. The report file appears in a word processor or text editor window.
Page 125
21. 13 Viewin g a Storag e Pool Su mm ary R epo rt fo r a T as k

After you run a Storage Pool Summary report for one task, the report is available in the task's Logs folder in the Director Management Console. To view a Storage Pool Summary report for a task: 1. In the left pane of the Director Management Cons ole, expand the vault, customer, location, computer and backup tasks, and task for the report. 2. 3. Click the Logs folder for the task. In the right pane of the Director Management Console, double-click the Pool Summary report log.
Page 126
Working w ith Log Files
22 Working with Log Files

These are the two types of log files: System record information about scheduled or ad hoc vault functions and jobs. Task record information about backup, migrate, restore, and synchronize tasks. Log files larger than 256 KB are abbreviat ed. However, you can still view the ent ire log file. If you use policies and quotas, the following error message might appear: VVLT-W-0002 Log file will be kept in the global logs folder. Error(2): Vault is out of storage If this occurs, you can view the log file in the Job Monitor initially. To loc ate it later, go to the global logs folder.
22. 1
Unde rst an ding Lo g M ess ag e Co des
Log messages include the following components: Date and time Four-letter code that describes the task. For a list of task codes, see Log Message Task Codes. Single letter code that describes the severity of the issue. For a list of severity codes, see Log Message Severity Codes. Four-digit number for Support personnel In the following sample log message, REPL is the task code and I is the severity code: Jan15 15:05:56.109 [1696] REPL-I-0001 Collecting children for item: CBTd907bf01-a5a1-41cf-a52a-de8288611deaServer Agent Note: Some messages, such as messages with the REPL task code, might display unprintable characters as empty boxes. These box es represent special characters that are necessary for the item name.
22.1.1
Log Message Task Codes
The following task codes appear in log messages:

Code VVLT DISK Description A general message Disk I/O
Page 127
Code DEVC POOL COPY VVCP MIGR SSET MERG PMGR DAEM EVLT BRTP SRVC MOVE AL YZ UTIL UPDT REPL
Description Device Pool system Copying vvcopy Migrate Safeset Merge Pool Manager Daemon Log header Backup Restore Transfer Protocol Service Mo ve Analyze Acti vation utility Verify license key Vault Replication
Page 128
Working w ith Log Files
22.1.2
Log Message Severity Codes
The following severity codes appear in log messages:

Code I W E F S Description Informational Warning Error Failure Success
22. 2
Sel ecting t he Lo g Fil es to Di splay
To select what log files display for a connection: 1. 2. 3. Select a connection in the left pane of the Director Management Console. From the View menu, choose Options. Select these options in the Logs area: Show Spawn Logs and License Logs Show Replication Logs Show Server Logs 4. Click OK.
22. 3
Viewin g Log Fil es
To view log files: 1. 2. 3. Select a connection or task in the left pane of the Director Management Console. Double-click Logs in the right pane. Double-click a log file in the right pane.
Page 129
22. 4
Viewin g Sp awn Lo gs
Spawn logs provide detailed information about system tasks and custom commands. To view spawn logs: 1. 2. Select a connection in the left pane of the Director Management Console. Double-click Spawn Logs in the right pane. If spawn logs are not available, see Selecting the Log Files to Display. 3. Double-click a spawn log in the right pane.
22. 5
Viewin g Lic ens e Log s
License logs provide vault licensing information. To view license logs: 1. 2. Select a connection in the left pane of the Director Management Console. Double-click License Logs in the right pane. If license logs are not available, see Selecting the Log Files to Display. 3. Double-click a license log in the right pane.
22. 6
Viewin g R eplic ation Lo gs
When replication is used, a log is generated for each replication service and session. You can open logs from the Director Management Console and for services and sessions shown in the Jo b Monit or dialog box. Configuration and metadata replication logs are available in a vaults Replication Logs folder. Each replication log name includes the vaults replication role in the activity (Active, Passive, Base or Satellite) and the type of information being replicated (Config or Meta). Task data replication logs are available in a tasks Logs folder. Each task replication log name is the vaults replication role in the activity (Active, Passive, Base or Satellite). To view a configuration or metadata replication log: 1. 2. Select a vault connection in the left pane of the Director Management Console. Double-click Replication Logs in the right pane. If replication logs are not available, see Selecting the Log Files to Display. 3. Double-click a replication log in the right pane.
To view a task replication log: 1. 2. Expand a vault connection in the left pane of the Director Management Console. Expand the Manage Customers list.
Page 130
Working w ith Log Files 3. 4. 5. 6. 7. 8. 9. Expand a Customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Select a task.
10. Double-click Logs in the right pane of the Director Management Console. 11. Double-click a replication log in the right pane. To view replication logs from the Job Monitor: 1. 2. 3. 4. 5. 6. Select a vault connection in the left pane of the Director Management Console. Click Job Monitor: Select a replication activity. Click View Log. Click File and then Exit. Click Close .
22. 7
Viewin g S erve r Logs
Server logs show ServerHost logs created by VVServer, a vault service that controls backups and restores. To view server logs: 1. 2. Select a connection in the left pane of the Director Management Console. Double-click Server Logs in the right pane. If server logs are not available, see Selecting the Log Files to Display. 3. Double-click a server log in the right pane.
Page 131
22. 8
Pu rgin g Log Fil es
It is recommended that you purge your weekly log files to save space on the vault. To purge log files: 1. 2. 3. 4. 5. 6. 7. Select a connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Purge Acti vity/Logs. Click Purge log files. Click Next. Click Submit job immediately. Click Next. Click Finish.
22. 9
Sch eduli ng a Log Fil e Pu rge
To schedule a log file purge: 1. 2. 3. 4. 5. Select a connection in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Vault Settings. Click the Logs tab. Enter or select the number of days to wait before purging the logs in the Purge logs after field. Enter or select the minimum number of log files to purge in the Minimal number of log files field. 6. Click OK.
Page 132
One-to-One (1:1) Replication
23 One-to-One (1:1) Replication

This section provides information and procedures for setting up and managing one -to-one (1:1) replication. To set up and manage many-t o-one (N:1) replication or many-t o-one-to-one (N:1: 1) replication, see Many-t o-One (N:1) Replication or Many-to-One-to-One (N: 1:1) Replication. In 1:1 replication, safeset data is automatically and continually replicated from a main, Active vault, to a Passive vault. As shown in the following diagram, the Active vault accepts backups from Agents and is used for restoring data. Backup data is copied, or replicated, from the Active vault to the Passive vault.
Page 133
Director 7.0 Operations Guide 1:1 replication ensures that vault data is protected, and can still be backed up and restored, in the event of a disaster. If the main, Active vault fails or becomes unavailable for some reason, you can fail over to the Passive vault. As shown in the following diagram, Agents can bypass the formerly Active vault, send backups directly to the formerly Passive vault, and restore data from the formerly Passive vault.
In 1:1 replication, safesets are copied if they are online and unex pired. Data stored in archives and secondary storage pools are not replicated. Safesets on the Active vault can be copied to the Passive vault when a backup completes successfully, or you can schedule them to replicate on specific days at a specific time. The physical data structure on the disk is not duplicated; only the backup contents and their logical associations are copied to the replicat ed vault. The logical organization of customer, location, comput er, task, and safeset dat a is unchanged. If you disable a task on the main vault, the task is disabled on the Passive vault. If a task is identified as suspect on the Active vault, this status is not replicated on the Passive vault.
Page 134
23. 1
Inst allin g an Acti ve Vault fo r 1:1 R eplic ation
When installing an Active vault for 1:1 replication, you must add a vault license and a Replication One to One license. You can then install a Passive vault, and add the same vault and Replication One to One license that is installed on the Active vault. When the Acti ve vault first communicates with the Passive vault, the Passive vault is automatically configured as passive. A vault that already contains data cannot be designat ed as a Passive vault. To install an Active vault for 1:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 2. 3. 4. 5. 6. 7. 8. 9. Select Vault and Management Console [together on thi s machine] and click Next. Click Next. Click Next. Accept the license agreement and click Next. Select Single vault configuration . Complete the EVault Software Director Setup wizard. Click Finish. Add a vault connection for the Active vault. See Creating a New Vault Connection.
10. (If applicable) If the license you added during the installation did not include a Replication One to One license, add a Replication One to One license. See Adding a License Key. 11. Click Active Replication and select Configure . 12. Click the Connectivity tab and enter the credentials for the Passive vault. Click OK.
23. 2
Inst allin g a Passi ve Vault fo r 1:1 R eplic ation
When you install a Passive vault for 1:1 replication, you must add the same vault and Replication One to One licenses that are added on the Active vault. When the Active vault first communicates with the Passive vault, the vault is automatically configured as passive. Note: You cannot designate a vault as passive if it already contains data. A Passive vault can require more storage space than an Active vault. When you replicate data aft er a safeset is deleted from an Active vault, the safeset is marked for deletion on the Passive vault but is not deleted until maintenance processes run. To accommodate extra safesets that are marked for deletion, ensure that Passive vaults have more storage space than Active vaults.
Page 135
Director 7.0 Operations Guide To install a Passive vault for 1:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 2. 3. 4. 5. 6. 7. Select Vault and Management Console [together on thi s machine] and click Next. Click Next. Click Next. Accept the license agreement and click Next. Select Single vault configuration . Complete the EVault Software Director Setup wizard. During the installation, you must add the same vault license that is installed on the Active vault. 8. 9. Click Finish. (If applicable) If the license you added during the installation did not include a Replication One to One license, add the same Replication One to One license that you added on the Active vault. See Adding a License Key.
23. 3
Settin g up Con nectio ns B etw een Acti ve an d Passiv e V ault s in 1:1 Repli catio n
You must set up the connection bet ween an Active and Passive vault in 1:1 replication. When the Active vault first communicates wit h the Passive vault, the vault is automatically configured as passive. Note: The Passive vault must be empty, or you will not be able to configure it as passive. To set up a connection between an Active and Passive vault in 1:1 replication: 1. 2. In the Director Management Console, click the Active vault connection. Click Active Replication and select Configure . The Active Vault Replication Configuration activeVaultname dialog box appears. 3. On the Connectivity tab, enter Passive vault information, including the IP address, command port, data port, user name and password. 4. Click OK.
Page 136
23. 4
Cre ating a Sc he dul e fo r 1:1 R eplic ation
In 1:1 replication, you can schedule data replication from the Active vault to the Passive vault. You can also specify whether to replicate data as soon as changes occur, or only according to the defined schedule. To create a schedule for 1:1 replication: 1. 2. 3. 4. Select an Active vault in the left pane of the Director Management Console. Click Active Replication and select Configure . Click the Schedule tab. Do one of the following: To replicate data whenever changes occur as well as according to the schedule, select Replicate as soon a s possible after changes are made and on defined schedule . To only replicate dat a when specified by the schedule, select Replicate on a defined schedule only. 5. 6. 7. Select the days you want the replication to occur. Select a time for the replication in the Time field. Click OK.
23. 5
Run nin g an Uns ch edul ed Replicatio n in a 1: 1 Confi gu ratio n
To run an unscheduled replication from the command line, see replvault. To run an unscheduled replication in a 1:1 configuration: 1. In the left pane of the Director Management Cons ole, select the Active vault with data that you want to replicate to a Passive vault. 2. 3. Click Active Replication and select Replicate Now . Click OK.
Page 137
23. 6
Allowing o r Pausin g 1:1 Safeset R eplic ation fo r a Custo me r, Lo catio n or Com put er
In 1:1 replication, you can allow or pause safeset replication for specific customers, locations and computers. To allow or pause 1: 1 safes et replication for a customer, location or comput er: 1. Expand an Active vault connection in the left pane of the Director Management Console unt il you see the customer, location, or computers for which you want to allow or pause safeset replication. 2. Right -click the customer, location, or computer for allowing or pausing safes et replication, select Operating Mode , and select one of the following: Allow Safeset Replication for all tasks Pause Safeset Replication for all tasks 3. In the confirmation dialog box, click OK.
23. 7
Allowing o r Pausin g 1:1 Safeset R eplic ation fo r a Tas k
In 1:1 replication, you can allow or pause safeset replication for a single task. To allow or pause 1: 1 safes et replication for a task: 1. Expand an Active vault connection in the left pane of the Director Management Console until you see the task for which you want to allow or pause safeset replication. 2. Right -click the task for allowing or pausing safeset replication, select Operating Mode , and select one of the following: Allow Safeset Replication Pause Safeset Replication 3. If a confirmation dialog box appears, click OK.
Page 138
23. 8
Disabling an d En abling 1:1 Replicatio n S erv ic es on a V ault
Replication services are automatically enabled on Active and Passive vaults when you add a Replication One to One license. However, you can disable and re-enable replication services. To disable or enable 1:1 replication services on a vault: 1. 2. 3. Select an Active or Passive vault in the left pane of the Director Management Console. From the Vault Maintenanc e menu, choose Vault Settings. Click the Replication tab, and do one of the following: To disable replication services, clear the Enable 1:1 replication service s on vaul tName check box. To enable replication services, clear the Enable 1:1 replication service s on vaultNam e check box. 4. Click OK.
23. 9
Disabling Ov e r-th e- Wi re E nc ryptio n fo r 1:1 Repli catio n
Communication bet ween the Active and Passive vaults is encrypted when over-the-wire encry ption is enabled. Over-the-wire encryption is enabled by default. To disable over-the-wire encryption for 1:1 replication: 1. 2. 3. 4. 5. In the left pane of the Director Management Cons ole, select an Active vault Click Active Replication and select Configure . Click the Network Options tab. Clear Enable over-the-wire encryption. Click OK.
Page 139
23. 10 Impl em enti ng B andwidt h Th rottling for 1:1 Repli catio n

You can implement bandwidth throttling to restrict the amount of bandwidth used to send data from the Active to the Passive vault. To implement bandwidth throttling for 1:1 replication: 1. 2. 3. 4. 5. 6. 7. Select an Active vault in the left pane of the Director Management Console. Click Active Replication and select Configure . Click the Network Options tab. Select Limit bandwidth usage . Enter a bandwidt h limit in the up to field and select MBits/ s or KBits/ s. Select the days that you want to restrict bandwidth us e. Click OK.
23. 11 Viewin g 1:1 R eplic ation Activity and Prog r ess

You can view a vaults 1:1 replication activities in the Job Monitor. When a replication session is in progress, you can view detailed replication progress and status information in the Progress Information dialog box. Each replication session name in the Job Monitor begins with the vaults replication role in the activity: Active or Passive. Each session name also includes the specific process, such as the type of data being replicated: Configuration (i.e., replication configuration changes), Met adata (e.g., location, computer, account, user and task changes), or Task (i.e., safesets). Some replication session names include the name of the customer, comput er or task involved. For example, when task data is replicated from an Active vault to a Passive va ult, a Passive Replication Task Cust1/Location1/Computer1/Backup session appears in the Job Monitor for the Passive vault. When a replication task is in progress, the Job Monitor message can also show the process that is currently running. For example, when met adat a changes are replicated from an Active vault to a Passive vault, an Active Replication Metadata Vault (Sending Data) message appears in the Job Monitor for the Active vault. Because multiple replication activities can run at the same time, if a large amount of safeset data is being replicated for one task, Configuration, Metadata and Task replication sessions for other tasks can start and finish while the large task is still running. Configuration replication sessions have priority to run over other sessions, and Metadata replication sessions have priority over Task replication.
Page 140
One-to-One (1:1) Replication To view 1:1 replication activity and progress: 1. In the left pane of the Director Management Cons ole, select a vault for viewing replication activity. 2. 3. Click Job Monitor: To show replication activity, do one of the following: If the selected vault is an Active vault, select the Show Active Replication option. If the selected vault is a Passive vault, select the Show Passive Replication option. The Job Monitor shows the vaults replication activities . 4. (Optional) To view detailed progress information for a replication activity that is running, click the activity and then click Progress. The Progress dialog box shows detailed progress and status information for the replication activity. 5. (Optional) To view replication activity for a different vault, choose the vault from the Select Vault list.
23. 12 Run nin g R eplic ation Report s in a 1:1 Con figu ration
To compare data on an Active and Passive vault in 1:1 replication, you can run the following reports:
Report Description
Replication Comparison
Compares objects, including customers, locations, computers and tasks, on the Active vault and the Passive vault, and indicates whether there are differenc es. You can specify which objects to compare on each vault, and whet her to compare indexes and safes ets as well as metadat a.
Page 141

Report Description
Replication Lag
Shows safesets that have not been replicated from the Active vault to the Passive vault in a specified number of days. To specify which safesets to include in the report, you can select vaults, customers, locations, computers, or specific tasks. When you run the Replication Lag report, you must enter the number of days after a safeset is created that it should be replicated to the P assive vault. For example, if you want a safeset to be replicated to the Passive vault two days after a backup, enter 2 as the parameter value. When you run the report, the system compares the date and time of the last safeset created for a task to the date and time of the last replicat ed safeset for the task. If the time difference is greater than the parameter value, the report lists all online safesets that have not been replicated. An asterisk (*) appears beside any safeset where replication has lagged more than the number of days specified by the parameter value. If the time difference bet ween the last safeset and the last replicated safeset is less than the parameter value, the report does not list any safesets. The report also indicates the percentage of metadata (e.g., catalog files, activity files, index files) that has been replicated for vaults, customers, locations, computers, tasks and safesets in the report.
Reports are saved to the Replication log directory. You can also run a Replication report from the command line. See replvault. To run a replication report in a 1:1 configuration: 1. 2. Select an Active vault in the left pane o f the Director Management Console. Click Active Replication, and select Status Report. Complete the fields in the Report wizard. On the Objects To Include in the Report page, select the report you want to run. On the Report Scope Selection page, select the data and objects to compare. 3. On the last page of the Report wizard, click Finish.
Page 142
23. 13 Failov e r f rom an Activ e to a Passi ve Vault in 1:1 Repli catio n

If an Active vault fails or bec omes unavailable for some reas on, you can fail over to the Pa ssive vault so that it becomes the new Active vault. Agents then send data directly to the new Active vault instead of to the unavailable vault. Safes ets that are not replicated from the Active vault to the Passive vault before failover are mark ed for deletion on the formerly Active vault, and remain only until they are deleted by maintenance processes. If you fail over to a Passive vault before data is synchronized with the Active vault, unreplicated data might be lost. When the previously Active vault becomes available again, you must replicate data from the current Active vault to the current Passive vault to synchroniz e the data. You can then leave the vault assignments as they are, or use the Failover menu to change the current Passive vault into the Ac tive vault again. To fail over from an Active to a Passive vault in 1:1 replication: 1. 2. 3. Select a Passive vault in the left pane of the Director Management Console. Click Passive Replication and select Failover. Do one of the following: If a dialog box states that there are no pending or running sessions on the vault, type YES, and click OK. Note: You must type the word YES in all capital letters. If a dialog box states that replication events are pending or running, read the warning carefully. If you still want to fail over from the Active to the Passive Base vault, type I AGREE, and click Force . Note: You must type the words I AGREE in all capital letters. 4. In the confirmation message box, click OK.
Page 143
24 Many-to-One (N:1) Replicatio n

This section provides information and procedures for setting up and managing many -to-one replication. To set up and manage one-to-one replication or many -to-one-to-one replication, see One-t o-One (1:1) Replication or Many-to-One-to-One (N:1:1) Replication. N:1 replication allows you to centralize your backups in one secure location. As shown in the following diagram, local, Satellite vaults collect backup data sent from Agents. During periods of low net work activity, data from the Satellite vaults is copied, or replicated, to the Base vault. If communication with the Base vault fails, you can perform backups and restores locally. You cannot perform administration tasks on Satellite vaults because only SalesPerson permissions are allowed. Instead, you can manage Satellite vaults on the Base vault. For more information about permissions, see Restricting Vault Access.
Page 144
Many-to-One (N:1) Replication N:1 replication ensures that vault data is protected, and can still be backed up and restored, in the event of a disaster. As shown in the following diagram, if a Satellite vault fails or becomes unavailable for some reason, Agents can send backups directly to the Base vault and restore data from the Base vault.
For N:1 replication, you must use customer licens e quot as to limit the amount of storage or number of Agents and plug-ins that a specific customer can use. When you create customers, locations, accounts and users on the Base vault, they are replicated on the Satellite vaults. You cannot use a Satellite vault in a QuickShip environment, and import and export functions are not supported.
Page 145
24. 1
Inst allin g a B as e V ault for N: 1 R eplic ation
On a Base vault for N:1 replication, you must add a vault license, a Replication Many to One license, and a vault license for each Sat ellite vault that communicates wit h the Base vault. To install a Base vault for N:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. The EVault Software Director Setup wizard starts. 2. 3. 4. 5. 6. 7. 8. 9. Select Vault and Management Console [together on thi s machine] and click Next. On the Welcome page, click Next. On the releas e notes page, click Next. On the software license agreement page, click Accept, and then click Next. On the Director setup type page, click Single vault configuration , and then click Next. On the vault license page, enter your Director license, and then click Next. Complete the remaining EVault Soft ware Director Set up wizard pages. Click Finish.
10. Add a vault connection for the B ase vault. See Creating a New Vault Connection. 11. (If applicable) If the license you added during the installation did not include a Replication M any to One license and Satellite vault licenses, add the required licenses. See Adding a License Key.
24. 2
Confi gu ring Sat ellite Vaults for N:1 R eplic ation on the B as e V ault
After installing Satellite vault licenses on a Bas e vault and creating customers, you can configure Sat ellite vaults on the Base vault. You must create a customer that will use a Sat ellite vault before you can configure the vault. When you configure a satellite, the Base vault provides an authorization key. When installing a Satellite vault, you must enter an authorization key from the Base vault instead of entering a license key. To configure a Satellite vault for N:1 replication on the Base vault: 1. 2. 3. In the Director Management Console, click the Base vault connection. Click Base Replication and select Configure Satellites. Click New .
Page 146
Many-to-One (N:1) Replication 4. In the Select the customer that will use this Satellite vault field, select a customer. Only one customer can be associated wit h a Satellite vault. 5. In the Select quota for thi s Satellite vault field, select a Satellite vault storage quota. A vailable storage quot as are determined by the Satellite vault licenses added on the Base vault. 6. Record the authorization key. You use this key when installing a Sat ellite vault. For more information, see Installing and Registering a Satellite Vault for N: 1 Replication. 7. 8. Click OK. Click Close .
24. 3
Inst allin g and R egi stering a S at ellite V ault fo r N: 1 Repli catio n
After installing a Base vault and configuring a Satellite vault for N:1 replication, you can install the Sat ellite vault. When you install a Satellite vault, you must enter the authorization key that was generated when you configured the Satellite vault on the Base vault. If you are installing the Sat ellite vault on a mac hine with the Microsoft Windows Ultimate operating system, a maximum of 20 simultaneous sessions from ot her computers are allowed. To install and register a Satellite vault for N:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain the self-extracting installation file, contact your licensed servic e provider of EVault Software products, or visit the Support website. 2. Select Vault and Management Console [together on thi s machine] and click Next. The EVault Software Director Setup wizard starts. 3. 4. 5. 6. 7. On the Welcome page, click Next. On the releas e notes page, click Next. On the license agreement page, click Accept, and then click Next. On the Director Set up Type page, click Satellite vault, and then click Next. Complete Setup wizard pages.
Page 147
Director 7.0 Operations Guide The Setup Type page appears.
8. 9.
Enter the Base vault address in the Ba se vault address field. Enter the port number that the Satellite vault uses to communicate with the Bas e vault in the TCP Port field. You can find this port in the Command channel port field on the Replication tab of the Vault Settings dialog box for the Base vault.
10. Enter the Base vault authorization key in the Authorization key field. The authorization key is provided when you configure a Satellite vault on the Base vault. For more information, see Configuring Satellite Vaults for N:1 Replication on the Bas e Vault . 11. On the confirmation page, click Next. 12. Click Finish.
24. 4
Repl aci ng a F ailed Sat ellite Vault in N:1 Repli catio n
To replace a failed Satellite vault in N:1 replication: 1. 2. 3. 4. 5. 6. 7. Select the Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select the failed Satellite vault and click Edit. Click the Advanced tab and select Bypa ss Satellite . Click OK. Select the failed Satellite vault and click Edit. Click Reset Key and record the new authorization key. Click OK.
Page 148
Many-to-One (N:1) Replication 8. 9. Click Close . Uninstall the Sat ellite vault. See Uninstalling the Director.
10. Install the new Satellite vault. Use the new aut horization key and previous IP address. See Installing and Registering a Satellite Vault for N:1 Replication. Allow replication to finish. 11. Select the Base vault in the left pane of the Director Management Console. 12. Click Base Replication and select Configure Satellites. 13. Select the Satellite vault and click Edit. 14. Click the Advanced tab and select Normal Operation. Click OK. 15. Click OK again. 16. Click Close .
24. 5
Cre ating a Sc he dul e fo r N: 1 R epli catio n
In N: 1 replication, you can schedule data replication from eac h Satellite vault to the Base vault. You can also specify whether to replicate data as soon as changes occur, in addition to the scheduled times. To create a schedule for N:1 replication: 1. 2. 3. 4. 5. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Schedule tab. Do one of the following: To replicate data whenever changes occur as well as according to the schedule, select Replicate as soon a s possible after changes are made and on defined sched ule . To only replicate dat a when specified by the schedule, select Replicate on a defined schedule only. 6. 7. 8. Select the days on which you want replication to occur. In the Time field, specify the time at which you want the replication to occur each day. Click OK.
Page 149
24. 6
Run nin g an Uns ch edul ed Replicatio n in an N:1 Confi gu ratio n
You can run an unscheduled replication between a Satellite vault and the Base vault in N:1 replication. When you run an unscheduled replication, data is not replicat ed immediately. Ins tead, replication begins when the Satellite vault next contacts the Base vault. For more information, see Setting the Heartbeat Interval for the Satellite Vault in N:1 Replication. To run an unscheduled replication in an N:1 configuration: 1. 2. 3. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault with data that you want to replicate to the Bas e vault and click Replicate Now . 4. 5. Click OK. Click Close .
24. 7
Disabling an d En abling N:1 R eplic ation Servic es o n a V ault
You can disable and enable N:1 replication services. Replication services are automatically enabled on a Base vault when you add a Replication Many to One license. N:1 replication services are automatically enabled on Base vaults when you add a Replication Many to One license, and on Satellite vaults when the Satellite vaults are installed. To disable or enable N:1 replication services on a vault: 1. 2. 3. Select a Base vault in the left pane of the Director Management Console. From the Vault Maintenance menu, choose Vault Settings. Click the Replication tab and do one of the following: To disable replication services, clear the Enable N:1 replication service s on VaultNam e check box. To enable replication services, select the Enable N:1 replication service s on VaultName check box. 4. Click OK.
Page 150
Many-to-One (N:1) Replication
24. 8
Disabling Ov e r-th e- Wi re E nc ryptio n fo r N: 1 Repli catio n
Communication bet ween the Base and Satellite vaults is encrypted when over-the-wire encryption is enabled. Over-the-wire encryption is enabled by default, but you can disable it. To disable over-the-wire encryption for N:1 replication: 1. 2. 3. 4. 5. 6. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Network Options tab. Clear Enable over-the-wire encryption. Click OK.
24. 9
Many-to -One ( N:1 ) R eplic ation an d Du al Netwo rk Conn ectio ns
When you use a single network connection for backup and replication, the Satellite and Base vaults each have one IP address. When you register Agents with the Satellite vault, the Satellite vault provides the name of the Bas e vault. Backups are sent to the Base vault if the Satellite vault fails and the Agent is configured on the Base vault. You can install the Satellite and Base vaults on two separate networks. Use one net work connection for backups, and one network connection for replication. This configuration requires you to install two network cards for the Satellite and Base vaults so that each vault has two IP addresses. With this configuration, backups and replication run faster, and there is no risk of conflicting processes. Use the Vault Settings menu and the Agent Configuration tab to specify the addresses that the Agents should us e for backups and restores. If you are using a single network connection, specify the IP addresses of the satellite and Base vault. If you are using dual network connections, specify the IP address of the second Base vault connection and replace the Base vault replication address with the correct Base vault backup network address.
Page 151
24. 10 Impl em enti ng B andwidt h Th rottling for N: 1 Repli catio n

You can implement bandwidth throttling on a Satellite vault to restrict the amount of bandwidth used to send dat a from the satellite to the Base vault. To implement bandwidth throttling for N:1 replication: 1. 2. 3. 4. 5. 6. 7. 8. 9. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Network Options tab. Select Limit bandwidth usage . Enter a bandwidt h limit in the up to field, and select MBits/ s or KBits/ s. Select the days on which you want to restrict bandwidth use. Click OK. Click Close .
24. 11 Settin g the R eplic ation Polic y fo r a Sat ellite Vault in N: 1 R eplic ation
To set the replication policy for a Satellite vault in N:1 replication: 1. 2. 3. 4. 5. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Safeset Management tab. Select All safe sets to replicate all safesets. or Select Only safesets that will be kept on Satellite vault x or more days to replicat e safesets that are stored on the Satellite vault for a specific number of days. 6. 7. Click OK. Click Close .
Page 152
24. 12 Settin g the R ete ntion Policy for a S at ellite V ault in N:1 Re plic ation
To set the retention policy for a Satellite vault in N:1 replication: 1. 2. 3. 4. 5. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Safeset Management tab. Select All safe sets (use the agent's retention policy) to use the Agent retention policy for safesets. or Select Keep at most to keep a specific number of safesets for a specific period. This setting does not override the Agent retention policy. 6. 7. Click OK. Click Close .
24. 13 Settin g the Op e rati ng Mo de for a S at ellite V ault i n N:1 Re plic ation
In N: 1 replication, you can set the operating mode for each Satellite vault. This operating mode specifies whet her or not backups are accepted on the Satellite vault, and replicated to the Base vault. If the operating mode for a Sat ellite vault is Normal operation, you can set the operating mode for specific customers, locations, computers and tasks on the vault. For more information, see Setting the Operating Mode for a Customer, Location or Computer in N:1 Replication and S etting the Operating Mode for a Task in N:1 Replication. To set the operating mode for a Satellite vault in N:1 replication: 1. 2. 3. 4. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Advanced tab.
Page 153
Director 7.0 Operations Guide 5. Select a satellite operating mode: Normal operation Backups are accepted on the Satellite vault, and replicated to the Base vault. Don't Replicate Backups are accepted on the Satellite vault, but data is not replicat ed to the Base vault. If there are metadata changes on the Base vault, they are applied to the Satellite vault. Bypa ss Satellite Backups are sent directly from the Agent to the Base vault. Restore Only Backups are not allowed and replication is disabled on the Satellite vault. Customer Only Only customer data is replicat ed from the Satellite vault to the Base vault. This option is only available for EVault for DPM satellites. For more information, see Assigning Settings Control to a Sat ellite Vault in N:1 Replication. 6. Click OK.
24. 14 Settin g the Op e rati ng Mo de for a Custo mer, Location o r Comp uter in N:1 R eplic ation
In N: 1 replication, you can change replication settings for specific customers, locations and computers. The operating mode specifies whether backups are accepted on the Satellite vault and replicated to the Base vault. To set the operating mode for a customer, location or comput er in N: 1 replication: 1. Expand a Base vault connection in the left pane of the Director Management C onsole until you see the customer, location, or computer for changing the operating mode. 2. Right -click the customer, location, or computer for setting the operating mode, select Operating Mode , and select one of the following: Use Satellite Operating Mode for all tasks Uses the satellite operating mode you selected on the A dvanced tab of the Satellite Configuration on Base Vault - BaseVaultName dialog box. Pause Safeset Replication for all tasks Temporarily pauses safeset replication for all tasks. Bypa ss Satellite for all tasks Sends Agent backups directly to the Base vault. Note: The P ause Safeset Replication for all tasks and Bypass Satellite for all tasks options are only available if the Satellite vaults operating mode is Normal operati on. The operating mode for a task is automatically set to Use Satellite Operating Mode if the Satellite vaults operating mode is anything but Normal Operation. For more information, see Setting the Operating M ode for a Satellite Vault in N: 1 Replication. 3. In the confirmation message box, click OK.
Page 154
24. 15 Settin g the Op e rati ng Mo de for a Tas k in N:1 Repli catio n

In N: 1 replication, you can change the operating mode for a single task. The operating mode specifies whet her or not backups are accepted on the Satellite vault and replicated to the Base vault. To set the operating mode for a task in N:1 replication: 1. 2. 3. 4. 5. 6. 7. 8. 9. Expand a Base vault connection in the left pane of the Director Management Console. Expand the Manage Customers list. Expand a Customer list. Expand Locations. Expand a loc ation. Expand Registered Computers. Expand a computer. Expand Backup Ta sks. Right -click the task for changing setting the operating mode, click Operating Mode , and select one of the following: Use Satellite Operating Mode Uses the satellite operating mode you selected on the Advanced tab of the Satellite Configuration on Bas e Vault - BaseVaultName dialog box. Pause Safeset Replication Temporarily pauses safeset replication for the task. Bypa ss Satellite Sends Agent backups directly to the Base vault. Note: The P ause Safeset Replication and Bypass Satellite options are only available if the Satellite vaults operating mode is Normal operation. The opera ting mode for a task is automatically set to Use Satellite Operating Mode if the Satellite vaults operating mode is anything but Normal Operation. For more information, see Setting the Operating Mode for a Satellite Vault in N:1 Replication 10. If a confirmation message appears, click OK.
Page 155
24. 16 Settin g the H eartb eat Int erv al fo r a Sat ellite Vault in N: 1 R eplic ation
You can set the heartbeat interval between a Satellite vault and the Base vault in N: 1 replication. The heartbeat interval specifies how frequently the Satellite vault contacts the Base vault. During a heartbeat contact, the last heartbeat time is updated on the Base vault, and configuration changes and requests (e.g., replication report requests) from the Base vault are submitted to the Satellite vault. If the Base vault does not receive a heartbeat from a Satellite vault for 30 days, the Satellite vault replication profile on the Base vault expires. To set the heartbeat interval for a Satellite vault in N:1 replication: 1. 2. 3. 4. 5. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Advanced tab. Enter the number of minutes after whic h the Satellite vault should contact the Base vault in the minutes field. 6. 7. Click OK. Click Close .
24. 17 Assig ning Setti ngs Cont rol to a S atellit e V ault in N:1 Re plic ation
In N: 1 replication, settings on the Base vault usually control Satellite vaults. However, because EVault for DPM (EDPM) Satellite vaults can control their own replication settings, you should assign settings control to these Satellite vaults. To assign settings control to a Satellite vault in N:1 replication: 1. 2. 3. 4. 5. 6. 7. Select a Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Advanced tab. Select Allow this Satellite to control its own settings. Click OK. Click Close .
Page 156
24. 18 Viewin g N: 1 R eplic ation Acti vity and Progres s

You can view a vaults N:1 replication activities in the Job Monitor. When a replication session is in progress, you can view detailed progress and status information for the task in the Progress Information dialog box. Each replication process name in the Job Monitor begins with the vaults replication role in the activity: Base or Satellite. Each session name also includes the specific process, such as the type of data being replicated: Configuration (i.e., replication configuration changes), Met adata (e.g., location, computer, account, user and task changes), or Task (i.e., safesets). Some replication process names also specify the customer, computer or task involved. For example, when dat abase and configuration information is replicated from a Satellite vault to a Base vault, a Satellite Replication Metadata Cust1/Location1/ Computer1 message appears in the Job Monitor for the Satellite vault. When a replication task is in progress, the Job Monitor can also show the process that is currently running. For example, when task data is being replicated from a Satellite vault to a Base vault, a Base Replication Task Cust1/Location1/Computer1/ Task (Rec eiving Data) message appears in the Job Monitor for the Passive Bas e vault. Because multiple replication activities can run at the same time, if a large amount of safeset data is being replicated for one task, Configuration, Metadata and Task replication sessions for other tasks can start and finish while the large task is still running. Configuration replication sessions have priority to run over other sessions, and Metadata replication sessions have priority over Task replication. To view N:1 replication activity and progress: 1. In the left pane of the Director Management Cons ole, select a vault for viewing replication activity. 2. 3. Click Job Monitor: To show replication activity, do one of the following: If the selected vault is a Base vault, select the Show Base Replication option. If the selected vault is a Satellite vault, select the Show Satellite Replication option. The Job Monitor shows the vaults replication activities . 4. (Optional) To view detailed progress information for a replication activity that is running, select the activity and then click Progress. The Progress dialog box shows detailed progress and status information for the replication activity. 5. (Optional) To view replication activity for a different vault, choose the vault from the Select Vault list.
Page 157
24. 19 Stopping N: 1 R eplic ation Process es and Servi ces

Using the Job Monitor, you can stop N:1 replication processes and services that are running on a Base vault. Each replication process and service listed in the Job Monitor begins with the vaults replication role in the activity: Base or Satellite. For example, when a Base vault receives data from a Satellite vault, the Job Monitor proc ess name begins with Base. When you stop a replication servic e and later want to re -enable it, you must re-enable replication using the Base vault settings. See Disabling and Enabling N:1 Replication Services on a Vault. To stop an N:1 replication process or service: 1. In the left pane of the Director Management Cons ole, select a Base vault for stopping a replication process or service. 2. 3. 4. 5. 6. Click Job Monitor: Select the Show Base Replication option. In the list of replication activities, select the Base process or service that you want to stop. Click Stop. In the confirmation dialog box, click Yes.
24. 20 Run nin g R eplic ation Report s in an N:1 Confi gu ratio n

To compare data on Sat ellite and Base vaults in N:1 replication, you can run the following reports:
Report Description
Compares objects, including customers, locations, computers and tasks, on Satellite vaults and the Base vault, and indicates whether there are differenc es. You can specify which objects to compare on each vault, and whet her to compare indexes and safes ets as well as metadat a.
Replication Status
Shows information about each Sat ellite vault that is registered on the Base vault.
Page 158

Report Description
Replication Lag
Shows safesets that have not been replicated from a Satellite vault to the Base vault in a specified number of days. To specify whic h safes ets to include in the report, you can select vaults, customers, locations, computers, or specific tasks. When you run the Replication Lag report, you must enter the number of days after a safeset is created that it should be replicated to the B ase vault. For example, if you want a safeset to be replicated to the Base vault two days aft er a backup, enter 2 as the parameter value. When you run the report, the system compares the date and time of the last safeset created for a task to the date and time of the last replicat ed safeset for the task. If the time difference is greater than the parameter value, the report lists all online safesets that have not been replicated. An asterisk (*) appears beside any safeset where replication has lagged more than the number of days specified by the parameter value. If the time difference bet ween the last safeset and the last replicated safeset is less than the parameter value, the report does not list any safesets. The report also indicates the percentage of metadata (e.g., catalog files, activity files, index files) that has been replicated to the Base vault for vaults, customers, locations, computers, tasks and safesets in the report.
Reports are saved in the Replication log directory. You can also run a Replication report from the command line. For more information, see replvault. To run a Replication report in an N:1 configuration: 1. Do one of the following: To run a Replication Comparison or Replication Lag report for one Satellite vault and a Base vault, select the Satellite vault in the left pane of the Director Management Cons ole. Click Satellite Replication, and select Status Report. To run a Replication Comparison, Status, or Replication Lag report for one or more Satellite vaults and a Base vault, select the Base vault in the left pane of the Director Management Console. Click Base Replication and select Status Report. 2. Complete the fields in the Report wizard. On the Objects To Include in the Report page, select the report that you want to run. On the Report Scope Selection page, select the data and objects to include. 3. On the last page of the wizard, click Finish.
Page 159
25 Many-to-One-to-One (N:1:1) Replication

This section provides information and procedures for setting up and managing many -to-one-to-one (N:1:1) replication. To set up and manage one -to-one or many-to-one replication, see One-to-One (1:1) Replication or Many-to-One (N:1) Replication. In N: 1:1 replication, Satellite vaults collect backup dat a sent from Agents. As shown in the following diagram, dat a from the Satellite vaults is replicated automatically to an Active Base vault. The data is then replicated from the Active Base vault to a Passive Base vault.
Page 160
Many-to-One-to-One (N:1:1) Replication N:1:1 replication ensures that vault data is prot ected, and can still be backed up and restored in the event of a disaster. As shown in the following diagram, if a Satellite vault fails or becomes unavailable for some reason, Agents can send backups directly to the Active Base vault, and data can be restored from the Active Base vault.
Page 161
Director 7.0 Operations Guide As shown in the following diagram, if the Active Base vault fails, you can fail over from the Active Base vault to the formerly Passive Base vault. Data from the Satellite vaults is then replic ated directly from the Satellite vaults to the new Active Base vault.
When the previously Active Base vault bec omes available again, you must run replication from the current Active Base vault to synchronize the data. After synchronization, you can leave the vault assignments as they are, or change the current Passive Base vault into the Active Base vault again. If you change a Passive Base vault into an Active Base vault without synchronizing and replic ating the data, all unreplicated data is permanently deleted. In N: 1:1 replication, you must use customer license quotas to limit the amount of storage, number of Agents, and number of plug-ins that a specific customer can use.
Page 162
Many-to-One-to-One (N:1:1) Replication
25. 1
Inst allin g an Acti ve Base V ault fo r N: 1:1 Repli catio n
To set up N:1:1 replication, you must first install an Active Base vault. On the Active Base vault, you must add a vault license, a Replication Many to One license, a Replication One to One license, and a vault license for each Sat ellite vault. Satellite vault licenses are all managed on the Active Bas e vault. Note: Becaus e each vault can have only one vault license, one of the replication licenses must be added using an add-on replication license key that is not bundled with a vault license. To install an Active Base vault for N:1:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain this installation file, contact your licensed service provider or visit the Support website. The EVault Software Director Setup wizard starts. 2. 3. 4. 5. 6. 7. 8. 9. Select Vault and Management Console [together on thi s machine] and click Next. On the Welcome page, click Next. On the releas e notes page, click Next. On the software license agreement page, click Accept, and then click Next. On the Director setup type page, select Single vault configuration , and then click Next. On the vault license page, enter your Director license, and then click Next. Complete the remaining Setup wizard pages. Click Finish.
10. In the Director Management Console, add a vault connection for the Active Bas e vault. See Creating a New Vault Connection. 11. (If applicable) If the license you added during the installation did not include a Replication Many to One license, a Replication One to One license, or Satellite vault licenses, add the required licenses. See Adding a License Key.
Page 163
25. 2
Inst allin g a Passi ve B ase V ault for N: 1:1 Repli catio n
After installing an Active Base vault, you can install a Passive Base vault for N: 1:1 replication. On the Passive Base vault, you must add the same vault, Replication Many to One, Replication One to One, and Satellite vault licenses that you added on the Active Base vault. When the Active Base vault first communicates with the Passive Base vault, the vault is automatically configured as passive. Note: You cannot designate a vault as passive if it already contains data. A Passive Base vault can require more storage space than an Active Base vault. When you replicate data after a safeset is deleted from an Active Base vault, the safeset is marked for deletion on the Passive Base vault but is not deleted until maint enance processes run. To accommodate extra safesets that are marked for deletion, ens ure that Passive Base vaults have more storage sp ace than Active Base vaults. To install a Passive Base vault for N:1:1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain this installation file, contact your licensed service provider or visit the Support website. 2. 3. 4. 5. 6. 7. Select Vault and Management Console [together on thi s machine] and click Next. On the Welcome page, click Next. On the releas e notes page, click Next. On the software license agreement page, click Accept, and then click Next. On the Director setup type page, select Single vault configuration , and then click Next. On the vault license page, enter the same Director licens e that is installed on the Active Base vault, and then click Next. 8. 9. Complete the remaining Setup wizard pages. Click Finish.
10. In the Director Management Console, add a vault connection for the Passive Base vault. See Creating a New Vault Connection. 11. (If applicable) If the license you added during the installation did not include a Replication One to One license, Replication Many to One license, or satellite licenses, add the same required licenses (i.e., the same license keys) that you added on the Active Base vault. See Adding a License Key.
Page 164
25. 3
Settin g up Con nectio ns B etw een Acti ve an d Passiv e B as e V ault s in N:1: 1 R eplic ation
You must set up the connection bet ween an Active Base vault and Passive Base vault in N: 1:1 replication. When the Active Base vault first communicat es with the Passive Base vault, the vault is automatically configured as passive. Note: The Passive Base vault must be empty, or you will not be able to configure it as passive. To set up a connection between Active and Passive Base vaults in N:1:1 replication: 1. 2. In the Director Management Console, click the Active Base vault connection. Click Active Replication and select Configure . The Active Vault Replication Configuration activeBaseV aultname dialog box appears. 3. On the Connectivity tab, enter Passive Base vault information, including the IP address, command port, data port, user name and password. 4. Click OK.
25. 4
Confi gu ring Sat ellite Vaults for N:1: 1 R eplic ation on the Activ e B as e V ault
After installing Satellite vault licenses on an Active Base vault, you can configure Satellite vaults on the Active Base vault. You must create a customer that will use a Satellite vault before configuring the vault. For more information, see Adding a Customer. When you configure a Satellite vault, the Active Base vault provides an authorization key. When installing a Satellite vault, you must enter an authorization key from the Base vault instead of a license key. Satellite vault licenses are added on the Active Base vault. Note: The Satellite vault configuration from the Active Base vault will not be replicat ed to the Passive Base vault until the Satellite vault is installed and registered. To configure a Satellite vault for N:1:1 replication on the Active Base vault: 1. 2. 3. 4. In the Director Management Console, click the Active Base vault connection. Click Base Replication and select Configure Satellites. Click New . In the Select the customer that will use this Satellite vault field, select a customer. Only one customer can be associated wit h a Satellite vault. 5. In the Select quota for thi s Satellite vault field, select a storage quota. A vailable storage quotas are determined by the Satellite vault license sizes available on the Base vault.
Page 165
Director 7.0 Operations Guide 6. Record the authorization key. You use this key to activat e a Satellite vault. For more information, see Installing and Registering a Satellite Vault for N: 1:1 Replication. 7. 8. Click OK. Click Close .
25. 5
Inst allin g and R egi stering a S at ellite V ault fo r N:1: 1 R eplic ation
After installing an Active Base vault and configuring a Sat ellite vault for N:1:1 replication, you can install the Satellite vault. When you install a Satellite vault, you must enter the aut horiz ation key that was generated when you configured the Satellite vault on the Active Base vault. To install and register a Satellite vault for N:1: 1 replication: 1. Double-click the InfoStageDirector. exe file. To obtain this installation file, contact your licensed service provider or visit the Support website. 2. Select Vault and Management Console [together on thi s machine] and click Next. The EVault Software Director Setup wizard starts. 3. 4. 5. 6. 7. On the Welcome page, click Next. On the releas e notes page, click Next. On the license agreement page, click Accept, and then click Next. On the Director Set up Type page, select Satellite vault, and then click Next. Complete the Setup wizard pages. The Setup Type page appears.
Page 166
Many-to-One-to-One (N:1:1) Replication 8. 9. Enter the Active Base vault address in the Ba se vault address field. Enter the port number that the Satellite vault uses to communicate with the Active B ase vault in the TCP Port field. You can find this port in the Command channel port field on the Replication tab of the Vault Settings dialog box for the Bas e vault. 10. Enter the Base vault authorization key in the Authorization key field. An authorization key is provided when you configure a Satellite vault on the Active Base vault. For more information, see Configuring Sat ellite Vaults for N:1:1 Replication on the Active Base Vault. 11. On the confirmation page, click Next. 12. Click Finish.
25. 6
Repl aci ng a F ailed Sat ellite Vault in N:1: 1 Repli catio n
To replace a failed Satellite vault in N:1:1 replication: 1. 2. 3. 4. 5. 6. 7. 8. 9. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select the failed Satellite vault and click Edit. Click the Advanced tab and select Bypa ss Satellite . Click OK. Select the failed Satellite vault and click Edit. Click Reset Key and record the new authorization key. Click OK. Click Close . Uninstall the Sat ellite vault.
10. Install the new Satellite vault. Use the new aut horization key and previous IP address. Allow replication to finish. 11. Select the Active Base vault in the left pane of the Director Management Console. 12. Click Base Replication and select Configure Satellites. 13. Select the Satellite vault and click Edit. 14. Click the Advanced tab and select Normal Operation. Click OK. 15. Click OK again. 16. Click Close .
Page 167
25. 7
Cre ating N:1: 1 R eplic ation Sch ed ules
In N: 1:1 replication, you can schedule data replication from each Satellite vault to the Active Base vault, and from the Active Base vault to the Passive Bas e vault. You can also specify whether to replicat e data as soon as changes occur, in addition to the scheduled times. To create a schedule for replicating data from a Satellite vault to the Active Base vault: 1. 2. 3. 4. 5. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select the Satellite vault and click Edit. Click the Schedule tab. Do one of the following: To replicate data from the Satellite vault to the Active Base vault whenever changes occur as well as according to the schedule, select Replicate as soon as possible after changes are made and on defined schedule . To only replicate dat a from the Satellite vault to the Active Base vault when specified by the schedule, select Replicate on a defined schedule only . 6. 7. 8. Select the days on which you want replication to occur. In the Time field, specify the time at which you want the replication to occur each day. Click OK.
To create a schedule for replicating data from an Active Base vault to a Passive Base vault : 1. 2. 3. 4. Select the Active Base vault in the left pane of the Director Management Console. Click Active Replication and select Configure . Click the Schedule tab. Do one of the following: To replicate data from the Active Base vault to the Passive Base vault whenever changes occur as well as according to the schedule, select Replicate as soon a s possible after changes are made and on defined schedule . To only replicate dat a from the Active Base vault to the Passive Base vault when specified by the schedule, select Replicate on a defined schedule only . 5. 6. 7. Select the days on which you want replication to occur. In the Time field, specify the time at which you want the replication to occur each day. Click OK.
Page 168
25. 8
Run nin g an Uns ch edul ed Replicatio n in an N:1 :1 Confi gu ratio n
In N: 1:1 replication, you can run an unscheduled data replication from a Satellite vault to an Active Bas e vault, or from an Active Bas e vault to a Passive Base vault. When you run an unscheduled replication from a Satellite vault to an Active Bas e vault, data is not replicated immediately. Instead, replication begins when the Satellite vault next contacts the Active Base vault. For more information, see Setting the Heart beat Interval for a Satellite Vault in N:1:1 Replication. To run an unscheduled replication from a S atellite vault to an Active Base vault: 1. 2. 3. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault with data that you want to replicate to the Active Bas e vault, and click Replicate Now . 4. Click OK.
To run an unscheduled replication from an Active Base vault to a Passive Base vault: 1. 2. 3. Select the Active Base vault in the left pane of the Director Management Console. Click Active Replication and select Replicate Now . Click OK.
25. 9
Disabling an d En abling R eplic ation S ervic es o n a Vault i n N:1:1 R eplic ation
You can disable and enable N:1 replication services on Active Base vaults and Passive Base vaults. N:1 replication services are automatically enabled on Base vaults when you add a Replication Many to One license, and on Satellite vaults when the Satellite vaults are installed. You can also disable and enable 1:1 replication servic es on Active Base vaults and Passive Base vaults. 1:1 replication services are automatically enabled on Active and Passive Base vaults when you add a Replication One to One license. To disable or enable N:1 replication services on a vault: 1. In the left pane of the Director Management Cons ole, select an Active Base vault or Passive Base vault. 2. 3. From the Vault Maintenance menu, choose Vault Settings. Click the Replication tab.
Page 169
Director 7.0 Operations Guide 4. Do one of the following: To disable N:1 replication services on the vault, clear the Enable N:1 replication service s on vaultName check box. To enable N:1 replication services on the vault, select the Enable N:1 replication service s on vaultName check box. To disable or enable 1:1 replication services on a vault: 1. In the left pane of the Director Management Cons ole, select an Active Base vault or Passive Base vault. 2. 3. 4. From the Vault Maintenance menu, choose Vault Settings. Click the Replication tab. Do one of the following: To disable 1:1 replication services on the vault, clear the Enable 1:1 replication service s on vaultName check box. To enable 1: 1 replication services on the vault, select the Enable 1:1 replication service s on vaultName check box. 5. Click OK.
25. 10 Disabling Ov e r-th e- Wi re E nc ryptio n in N:1: 1 Repli catio n

Communication bet ween an Active Bas e vault and a S atellite vault, or bet ween an Active Base vault and a Passive Base vault, is encrypted when over -the-wire encryption is enabled. Over-the-wire encry ption is enabled by default. However, you can disable encryption between an Active Base vault and a Sat ellite vault, or bet ween an Active Bas e vault and a Passive Base vault. To disable over-the-wire encryption between an Active Base vault and a Satellite va ult: 1. 2. 3. 4. 5. 6. In the left pane of the Director Management Cons ole, select the Active Base vault. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Network Options tab. Clear the Enable over-the-wire encryption check box. Click OK.
Page 170
Many-to-One-to-One (N:1:1) Replication To disable over-the-wire encryption between an Active Base vault and a Passive Base vault: 1. 2. 3. 4. 5. In the left pane of the Director Management Cons ole, select the Active Base vault. Click Active Replication and select Configure . Click the Network Options tab. Clear Enable over-the-wire encryption. Click OK.
25. 11 Many-to -One -to- On e ( N: 1:1 ) R eplic ation an d Du al Netwo rk Co nn ection s

When you use a single network connection for backup and replication, the Sat ellite and Active Base vaults each have one IP address. When you register Agents with the Satellite vault, the Satellite vault provides the name of the Active Base vault. Backups are sent to the Active Bas e vault if the Satellite vault fails and the Agent is configured on the Active Base vault. You can install the Satellite and Active Base vaults on two separate networks. Use one net work connection for backups, and one net work connection for replication. This configuration requires you to install two network cards for the Satellite and Active Base vaults so that each vault has two IP addresses. With this configuration, backups and replication run faster, and there is no risk of conflicting processes. Use the Vault Settings menu and the Agent Configuration tab to specify the addresses that the Agents should us e for backups and restores. If you are using a single network connection, specify the IP addresses of the satellite and Active Base vault. If you are using dual network connections, specify the IP address of the second Active Base vault connection and replace the Active Base vault replication address with the correct Active B ase vault backup network address.
25. 12 Impl em enti ng B andwidt h Th rottling for N: 1:1 Repli catio n

You can implement bandwidth throttling on a Satellite vault to restrict the amount of bandwidth used to send dat a from a Satellite vault to the Active Base vault, or from the Active Base vault to the Passive Base vault. To implement bandwidth throttling from a Satellite vault to the Active Base vault: 1. 2. 3. 4. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Network Options tab.
Page 171
Director 7.0 Operations Guide 5. 6. 7. 8. Select Limit bandwidth usage . Enter a bandwidt h limit in the up to field, and select MBits/ s or KBits/ s. Select the days on which you want to restrict bandwidth use. Click OK.
To implement bandwidth throttling from the Active Base vault to the Passive Base vault: 1. 2. 3. 4. 5. 6. 7. Select an Active Base vault in the left pane of the Director Management Console. Click Active Replication and select Configure . Click the Network Options tab. Select Limit bandwidth usage . Enter a bandwidt h limit in the up to field, and select MBits/ s or KBits/ s. Select the days on which you want to restrict bandwidth use. Click OK.
25. 13 Settin g the R eplic ation Polic y fo r a Sat ellite Vault in N: 1:1 Repli catio n
To set the replication policy for a Satellite vault in N:1:1 replication: 1. 2. 3. 4. 5. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Safeset Management tab. Select All safe sets to replicate all safesets. or Select Only safesets that will be kept on Satellite vault x or more days to replicat e safesets that are stored on the Satellite vault for a specific number of days. 6. Click OK.
Page 172
25. 14 Settin g the R ete ntion Policy for a S at ellite V ault in N:1: 1 R eplic ation
To set the retention policy for a Satellite vault in N:1:1 replication: 1. 2. 3. 4. 5. Select an Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Safeset Management tab. Select All safe sets (use the agent's retention policy) to use the Agent retention policy for safesets. or Select Keep at most to keep a specific number of safesets for a specific period. This setting does not override the Agent retention policy. 6. Click OK.
25. 15 Settin g the Op e rati ng Mo de for a S at ellite V ault i n N:1: 1 R eplic ation
In N: 1:1 replication, you can set the operating mode for each Sat ellite vault. This operating mode specifies whether or not backups are accepted on the Satellite vault, and replicated to the Active Base vault. If the operating mode for a Sat ellite vault is Normal o peration, you can set the Base operating mode for specific customers, locations, computers and tasks on the vault. For more information, see Setting the Operating Mode for a Customer, Location or Computer in N:1:1 Replication and Setting the Operating Mode for a Task in N:1:1 Replication. To set the operating mode for a Satellite vault in N:1:1 replication: 1. 2. 3. 4. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit. Click the Advanced tab.
Page 173
Director 7.0 Operations Guide 5. Select a satellite operating mode: Normal operation Backups are accepted on the Satellite vault, and replicated to the Active Base vault. Don't Replicate Backups are accepted on the Satellite vault, but data is not replicat ed to the Active Base vault. If there are metadata changes on the Active Base vault, they are applied to the Satellite vault. Bypa ss Satellite Backups are sent directly from the Agent to the Active Bas e vault. Restore Only Backups are not allowed and replication is disabled on the Satellite vault. Customer Only Only customer data is replicat ed from the Satellite vault to the Active Base vault. This option is only available for EVault for DPM satellites. For more information, see Assigning Settings Control to a Satellite Vault in N:1: 1 Replication. 6. Click OK.
25. 16 Settin g the Op e rati ng Mo de for a Custo mer, Location o r Comp uter in N:1 :1 Repli catio n
In N: 1:1 replication, you can set the Base and Active operating modes for specific customers, locations and computers. The Base operating mode specifies whether or not backups are accepted on Satellite vaults and replicated to the Active Base vault. The Active operating mode specifies whether safes ets are replicated between the Active and Passive Base vaults. To set the operating mode for a customer, location or comput er in N: 1:1 replication: 1. In the left pane of the Director Management Cons ole, expand the Active Bas e vault connection until you see the customer, location, or computer for setting the operating mode. 2. Right -click the customer, location, or computer, and do one of the following: To specify whether or not backups are accept ed on the Satellite vault and replicated to the Active Base vault, select Base Operating Mode , and then select one of the following: Use Satellite Operating Mode for all tasks Uses the satellite operating mode selected on the A dvanced tab of the Satellite Configuration on Base Vault BaseVaultName dialog box. Pause Safeset Replication for all tasks Temporarily pauses safeset replication for all tasks. Bypa ss Satellite for all tasks Sends Agent backups directly to the Base vault. Note: The P ause Safeset Replication for all tasks and Bypass Satellite for all tasks options are only available if the Satellite vaults operating mode is Normal operation.
Page 174
Many-to-One-to-One (N:1:1) Replication The Base operating mode for a task is automatically set to Use Satellite Operating Mode if the Sat ellite vaults operating mode is anything but Normal Operation . For more information, see Setting the Operating Mode for a Satellite Va ult in N:1:1 Replication. To specify whether or not safesets are replicated bet ween the Active and Passive B ase vaults, select Active Operating Mode , and then select one of the following: Allow Safeset Replication for all tasks Pause Safeset Replication for all tasks 3. In the confirmation message box, click OK.
25. 17 Settin g the Op e rati ng Mo de for a Tas k in N:1: 1 Repli catio n

In N: 1:1 replication, you can set the Base and Active operating modes for a specific task. The Base operating mode specifies whether or not backups for the task are accept ed on Satellite vaults and replicated to the Active Base vault. The Active operating mode specifies whether safes ets for the task are replicated from the Active to the Passive Base vault. To set the operating mode for a task in N:1:1 replication: 1. In the left pane of the Director Management Cons ole, expand the Active Bas e vault connection until you see the task for setting the operating mode. 2. Right -click the task for setting the operating mode, and do one of the followin g: To specify whether or not backups for the task are accepted on the S atellite vault and replicated to the Active Base vault, click Base Operating Mode , and then select one of the following: Use Satellite Operating Mode Uses the satellite operating mode selected on the Advanced tab of the Satellite Configuration on Bas e Vault - BaseVaultName dialog box. Pause Safeset Replication Temporarily pauses safeset replication for the task. Bypa ss Satellite Sends Agent backups directly to the Base vault. Note: The P ause Safeset Replication for all tasks and Bypass Satellite for all tasks options are only available if the Satellite vaults operating mode is Normal operation. The Base operating mode for a task is automatically set to Use Satellite Operating Mode if the Sat ellite vaults operating mode is anything but Normal Operation. For more information, see Setting the Operating Mode for a Satellite Vault in N:1:1 Replication. To specify whether or not safesets for the task are replicated from the Active Base vault to the Passive Base vault, click Active Operating Mode , and select one of the following:
Page 175
Director 7.0 Operations Guide Allow Safeset Replication Pause Safeset Replication 3. In the confirmation message box, click OK.
25. 18 Settin g the H eartb eat Int erv al fo r a Sat ellite Vault in N: 1:1 Repli catio n
You can set the heartbeat interval between a Satellite vault and the Active Base vault. The heartbeat interval specifies how frequently the Satellite vault contacts the Active Base vault. During a heartbeat contact, the last heartbeat time is updated on the Active Base vault, and configuration changes and requests (e.g., replication report requests) from the Active Bas e vault are submitted to the Satellite vault. If the Active Base vault does not receive a heartbeat contact from a Satellite vault for 30 days, the Satellite vault replication profile on the Active Base vault expires. To set the heartbeat interval for a Satellite vault in N:1:1 replication: 1. 2. 3. 4. 5. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select the Satellite vault and click Edit. Click the Advanced tab. Enter the number of minutes after whic h the Satellite vault should contact the Active Base vault in the minutes field. 6. 7. Click OK. Click Close .
25. 19 Assig ning Setti ngs Cont rol to a S atellit e V ault in N:1: 1 R eplic ation
In N: 1:1 replication, settings on the Active Bas e vault usually control Sat ellite vaults. However, bec ause EVault for DPM Satellite vaults can control their own replication settings, you should assign settings control to these Satellite vaults. To assign settings control to a Satellite vault in N:1:1 replication: 1. 2. 3. Select the Active Base vault in the left pane of the Director Management Console. Click Base Replication and select Configure Satellites. Select a Satellite vault and click Edit.
Page 176
Many-to-One-to-One (N:1:1) Replication 4. 5. 6. 7. Click the Advanced tab. Select Allow this Satellite to control its own settings. Click OK. Click Close .
25. 20 Viewin g N: 1:1 Replicatio n A ctivity an d Prog ress

You can view a vaults N:1:1 replication activities in the Job Monitor. When a replication task is in progress, you can also view its progress in the Progress Information dialog box. In the Job Monitor, replication activities for Active and Passive Base vaults appear separately for N:1 replication (between Sat ellite vaults and Base vaults) and 1:1 replication (between Active and P assive Base vaults). You can choose to vie w both N:1 and 1:1 replication activities, or only one at a time. Each replication process name in the Job Monitor begins with the vaults replication role in the activity: Active, Passive, Base, or Satellite. For example, when the Active Base vault receives data from a Sat ellite vault, the process name begins with B ase. When the Active Base vault sends dat a to the Passive Base vault, the process name begins with Active. The following table shows the process name prefix for each vault type and replication role. Vault selected in Job Replication Role Monitor Active Base vault N:1 replication: Receiving data from Satellite vault 1:1 replication: Sending data to Passive Base vault Passive Base vault N:1 replication: Receiving data from Satellite vault 1:1 replication: Receiving data from Active Base vault Satellite vault N:1 replication: Sending data to Active Base vault Process Name Prefix Base Active Base Passive Satellite
Each replication process in the Job Monitor also includes specific process information, such as the type of data being replicated: Configuration (i.e., replication configuration changes), Met adata (e.g., location, computer, account, user and task changes), or Task (i.e., safesets). For example, when configuration information is replicated from an Active Base vault to the Passive Base vault, a Passive Replication Configuration Replication from vault message appears in the Job Monitor for the Passive Ba se vault. Some replication process names also specify the customer, computer or task involved. For example, when metadata is replicated from a Satellite vault to the Active Base vault, a Satellite Replication Metadat a Cust1/Location1/Computer1 proces s appears in the Job Monitor for the Satellite vault. When
Page 177
Director 7.0 Operations Guide task data is replicated from an Active Base vault to the Passive Bas e vault, an Active Replication Task Cust1/Location1/Computer1/ Task process appears in the Job Monitor for the Active Base v ault. When a replication task is in progress, the Job Monitor can also show the process that is currently running. For example, when task data is being replicated from an Active Bas e vault to a Passive Base vault, an Active Replication Task Cust1/Location1/Computer1/ Task (Committing P artial Pool) message appears in the Job Monitor for the Passive Base vault. Because multiple replication activities can run at the same time, if a large amount of safeset data is being replicated for one task, Configuration, Metadata and Task replication sessions for other tasks can start and finish while the large task is still running. Configuration replication sessions have priority to run over other sessions, and Metadata replication sessions have priority over Task re plication. To view N:1: 1 replication activity and progress for an Active Base vault: 1. 2. 3. In the left pane of the Director Management Cons ole, select an Active Base vault. Click Job Monitor: Do one or both of the following: To view replication activity between the Active Base vault and Passive Base vault, select the Show Active Replication option. To view replication activity between the Satellit e vault and the Active Base vault, select the Show Base Replication option. 4. (Optional) To view detailed progress information for a replication activity that is running, select the activity and then click Progress. The Progress dialog box shows detailed progress and status information for the replication activity. 5. (Optional) To vi ew replication activity for a different vault, choose the vault from the Select Vault list. To view N:1: 1 replication activity and progress for a Passive Base vault: 1. 2. 3. In the left pane of the Director Management Cons ole, select a Passive Base vault. Click Job Monitor: Do one or both of the following: To view replication activity between the Active Base vault and Passive Base vault, select the Show Passi ve Replication option. To view replication activity between the Satellit e vault and the Passive Base vault, select the Show Base Replication option.
Page 178
Many-to-One-to-One (N:1:1) Replication 4. (Optional) To view detailed progress information for a replication activity that is running, select the activity and then click Progress. The Progress dialog box shows detailed progress and status information for the replication activity. 5. (Optional) To view replication activity for a different vault, choose the vault from the Select Vault list. To view N:1: 1 replication activity and progress for a Satellite vault: 1. 2. 3. 4. In the left pane of the Director Management Cons ole, select a Satellite vault. Click Job Monitor: Select the Show Satellite Replication option. (Optional) To view detailed progress information for a replication activity that is running, select the activity and then click Progress. The Progress dialog box shows detailed progress and status information for the replication activity. 5. (Optional) To view replication activity for a different vault, choose the vault from the Select Vault list.
25. 21 Stopping N: 1:1 Repli catio n Proc es ses and S ervic es

Using the Job Monitor, you can stop replication processes and services that are running on an Active Base vault or Passive Base vault. You can stop N:1 replication processes and services separately from 1:1 replication processes and services. Each replication process and service listed in the Job Monitor begins with the vaults replication role in the activity: Active, Passive, Base, or Satellite. For ex ample, when an Active Base vault receives metadata from a Satellite vault, the Job Monitor process name begins with B ase. When a Passive Base vault receives data from an Active Base vault, the Job Monitor process name begins with Passive. To re-enable a replication service, use the Vault Settings dialog box. For more information, see Disabling and Enabling N:1:1 Replication Services on a Vault. To stop an N:1: 1 replication process or service for an Active Base vault: 1. 2. In the left pane of the Director Management Cons ole, select an Active Base vault. Click Job Monitor:
Page 179
Director 7.0 Operations Guide 3. Do one of the following: To stop an N:1 replication process or service for the vault, select the Show Base Replication option. In the list of replication activities, select the Base proc ess or service that you want to stop. To stop the vaults service for 1:1 replication, select the Show Active Replication option. In the list of replication activities, select the Active process or service that you want to stop. 4. 5. Click Stop. In the confirmation message box, click Yes.
To stop an N:1: 1 replication process or service for a Passive Base vault: 1. 2. 3. In the left pane of the Director Management Cons ole, select a Passive Base vault. Click Job Monitor: If the selected vault is a Passive Base vault, do one of the following: To stop the vaults service for N:1 replication, select the Show Base Replication option. In the list of replication activities, select the Base process or service that you want to stop. To stop the vaults service for 1:1 replication, select the Show Passive Replication option. In the list of replication activities, select the Passive process or service that you want to stop. 4. 5. Click Stop. In the confirmation message box, click Yes.
25. 22 Run nin g R eplic ation Report s in an N:1: 1 Confi gu ratio n

To compare safesets on vaults in N:1:1 repication, you can run the following reports:
Report Description
Compares objects, including customers, locations, computers, and tasks, on two vaults and indicat es whether there are differences. The report can compare objects on Satellite vaults and the Active Base vault, or objects on the Active and Passive B ase vaults. You can specify which objects to compare on each vault, and whether to compare indexes and safesets as well as metadata.
Status
Shows information about each Sat ellite vault that is registered on the Active Base vault or Passive Base vault.
Page 180

Report Description
Replication Lag
Shows safesets that have not been replicated from a Satellite vault to the Active Base vault, or from the Active Base vault to the Passive Base vault in a specified number of days. To specify whic h safes ets to inc lude in the report, you can select vaults, customers, locations, computers, or specific tasks. When you run the Replication Lag report, you must enter the number of days after a safeset is created that it should be replicated. For example, if you want a safes et to be replicated two days after a backup, enter 2 as the parameter value. When you run the report, the system compares the date and time of the last safeset created for a task to the date and time of the last replicat ed safeset for the task. If the time difference is greater than the parameter value, the report lists all online safesets that have not been replicated. An asterisk (*) appears beside any safeset where replication has lagged more than the number of days specified by the parameter value. If the time difference bet ween the last safeset and the last replicated safeset is less than the parameter value, the report does not list any safesets. The report also indicates the percentage of metadata (e.g., catalog files, activity files, index files) that has been replicated for vaults, customers, locations, computers, tasks and safesets in the report.
Reports are saved in the Replication log directory. You can also run a Replication report from the command line. For more information, see replvault. To run a replication report in an N:1:1 configuration: 1. Do one of the following: To run a Replication Comparison or Replication Lag report for one Satellite vault and an Active Base vault, select the Satellite vault in the left pane of the Director Management Cons ole. Click Satellite Replication, and select Status Report. To run a Replication Comparison, Status, or Replication Lag report for one or more Satellit e vaults and an Active Base vault, select the Active Base vault in the left pane of the Director Management Console. Click Base Replication, and select Status Report. To run a Replication Comparison and Replication Lag report for an Active Base vault and Passive Base vault, select the Active Base vault in the left pane of the Director Management Cons ole. Click Acti ve Replication, and select Status Report.
Page 181
Director 7.0 Operations Guide 2. Complete the fields in the Report wizard. On the Objects To Include in the Report page, select the report that you want to run. On the Report Scope Selection page, select the data and objects to include. 3. On the last page of the Report wizard, click Finish.
25. 23 Failov e r f rom an Activ e to a Passi ve Base Vault in N:1: 1 R eplic ation
If an Active Base vault fails or becomes unavailable for s ome reason, you can fail over to the Passive Base vault so that it becomes the new Active Base vault. Satellite vaults then replicate dat a directly to the new Active Base vault instead of the unavailable vault. Any online safesets that were not already replicated to the new Active Base vault are replicated to the new Active Base vault. Safes ets that are not replicated from the Active Base vault to the Passive Base vault before failover are marked for deletion on the formerly Active Base vault, and remain only until they are deleted by maintenance processes. If you fail over to a Passive Base vault before data is synchronized with the Active Base vault, unreplicated data might be lost. When the previously Active Base vault bec omes available again, you must replicate data from the current Active Base vault to the current Passive Base vault to synchronize the data. You can then leave the vault assignments as they are, or use the Failover menu to change the current Passive Base vault into the Active Base vault again. To fail over from an Active to a Passive Base vault in N:1:1 replication: 1. 2. 3. Select a Passive Base vault in left pane of the Director Management Console. Click Passive Replication and select Failover. Do one of the following: If a dialog box states that there are no pending or running sessions on the vault, type YES, and click OK. Note: You must type the word YES in all capital letters. If a dialog box states that replication events are pending or running, read the warning carefully. If you still want to fail over from the Active to the Passive Base vault, type I AGREE, and click Force . Note: You must type the words I AGREE in all capital letters. 4. In the confirmation message box, click OK.
Page 182
Working w ith QuickShip Vaults
26 Working with QuickShip Vaults

This section provides information and procedures for installing and managing a QuickShip vault. You use a QuickShip vault to complete these tasks: Seeding/re-seeding client backups To seed or re-seed client backups, you install the QuickShip vault on a portable computer, export the client data to the QuickShip vault, and then ship the portable computer to the client site to seed the backups. When the seeding is complete, the portable computer is returned to t he main vault location and the data is imported from the QuickShip vault, into the main vault. Disaster rec overy You install the QuickShip vault on a portable computer, export the client data to the QuickShip vault and then ship the portable computer to th e client site for a data restore. A QuickShip vault contains either a full or a partial copy of the client configuration and backup data from the main vault. You cannot use a QuickShip vault as a main vault. You cannot install a main vault and a QuickShip vault on the same computer. You can use a QuickShip vault to bypass slow Wide Area Network (WAN) or Local Area Network (LAN) connections by placing a vault close to Agents. When you install a QuickShip vault, use the license key for your main vault or a li cense key that you previously activated. You do not need to activate your QuickShip vault license.
26. 1
Inst allin g a Qui ckShip Vault
You must install the QuickShip vault on a different computer than the main vault. The main vault and the QuickShip vault must be the same version. To install a QuickShip vault: 1. 2. 3. 4. 5. Browse to the location of the Director installation file. Double-click the installation file. Select QuickShip vault on the EVault Software Director Setup Type page. Complete the EVault Director Software Setup wizard. Click Finish.
Page 183
26. 2
Cre ating a Quic kS hip Pro file
You creat e a QuickShip profile for every QuickShip vault. If you remove a QuickShip vault, you must recreate the profile. To create a QuickShip profile on a main vault: 1. 2. Click QuickShip and select Profile Setup in the Director Management Console . Complete the QuickShip Profile wizard. For field descriptions, see QuickShip Profile Wizard Fields. The new QuickShip vault profile is saved in the conf directory on the main vault. The QuickShip profile remains static unless connectivity or authentication information for the QuickShip changes or you reinstall the vault.
26.2.1
QuickShip Profile Wizard Fields
The following fields appear in the QuickShip Profile wizard:

Field Modify existing profile Create new profile Host Name Port User Name The host name or IP address of the QuickShip vault. The port used by the QuickShip vault. The user name used to access the QuickShip vault. The user must have Administrator privileges on the QuickShip vault. Password The password used to access the QuickShip vault. Creates a new QuickShip vault. Description Modifies existing QuickShip vault settings.
Confirm password The password used to access the QuickShip vault. Domain The domain name of the target QuickShip vault. If you are not using a domain name, enter a period (.). Storage Group The primary storage group on the QuickShip vault associated with this profile.
Page 184
Field Storage Group
Description The secondary storage group on the QuickShip vault associated with this profile. If your QuickShip vault does not have secondary locations, a default Secondary Storage Group named Secondary01 is created automatically
26. 3
Initi alizin g a Qui ckShip Vault
Initializing a QuickShip vault removes all data currently on the QuickShip vault, including secondary pool systems created by the main vault and other vaults. To initialize a QuickShip vault on a main vault: 1. 2. 3. 4. 5. 6. 7. Create a QuickShip profile. See Creating a QuickShip Profile. Click QuickShip and select Initialize in the Director Management Console . Select a QuickShip profile to initialize. Click OK. Verify the profile information is correct. Enter YES and click OK. Click OK again.
26. 4
Exporti ng D at a to a Quic kShi p Vault
When you export dat a to a QuickShip vault, all tasks with exported data are disabled on the main vault. Tasks are automatically enabled when you successfully import data on the main vault. To export data from a main vault to a QuickShip vault: 1. 2. Click QuickShip and select Export in the Director Management Console . Complete the QuickShip Export wizard. For field descriptions, see QuickShip Export Wizard Fields.
Page 185
26.4.1
QuickShip Export Wizard Fields
The following fields appear in the QuickShip Export wizard:

Field Reseeding and customer/account information only Restoring, reseeding and customer/account information QSM Export - Source Description Reseeds customer account information.
Restores and reseeds customer account information.
Select the data to export. Note: When exporting Agent for VMware data to a QuickShip vault, select the green icon for the cluster of VMware ESX and ESXi hosts, or subsequent backups to the QSM vault will fail because of licensing issues.
QuickShip Profiles Copy the Secondary Storage Safesets to the QSM Create Secondary Storage (reference only, no physical copy)
The QuickShip vault where the safesets are exported. Copies the primary and secondary pools from the main vault to the QuickShip vault. If you select one safeset, all safesets are copied. Copies secondary pool pointers to the QSM vault. It does not copy the location and credentials to the QSM vault. This option assumes that the physical
on the QSM as Detached secondary storage unit is moved with the QSM vault. You manua lly attach the Secondary. I will manually re-attach secondary safesets to the task's secondary pool pointers. the secondary safesets on demand. After running this option, the status of all secondary safesets is Secondary Detached. To do a Restore from the Secondary > Attach screen, you specify where the secondary location is (UNC or Local), along with the credentials (or the defaults). This information is then used to create a new storage location in the corresponding task's secondary storage group. At the end of running the Attach (which can be done for the entire vault at once, with Recursive Search and Attach), you will have the secondary safesets attached, and ready for Exports and Restores. Note: Default credentials can be specified (used) for access to the safesets. Otherwise, the locations and credentials for every unique secondary location in the exported safesets must be manually entered (including the credentials) into each individual secondary storage group used by every exported task. Otherwise, you may see an error message in the log file such as: "Requesting to connect the UNC device <name> but no suitable credentials were given or found in the storage location."
Page 186
26. 5
Impo rting Dat a f ro m a Qui ckShip Vault
When you import data, you should disconnect the Agent from the main vault. In addition, do not register new computers or tasks, and do not perform backups. To import data from a QuickShip vault to a main vault: 1. 2. Click QuickShip and select Import in the Director Management Console . Complete the QuickShip Import wizard.
26. 6
Compl eting a L arge Initi al S eed
To complete a large initial seed: 1. 2. 3. 4. 5. 6. 7. Add a new organization on the main vault. See Adding a Customer. Install the Agent. Register the Agent and a new Job on the main vault. Do not schedule backups. Connect the QuickShip vault to the same Local Area Network (LA N) as the main vault. Create a profile for the QuickShip vault on the main vault. See Creating a QuickShip Profile. Initialize the QuickShip vault. See Initializing a QuickShip Vault. Export the main vault data to the QuickShip vault. Select Reseeding and customer/account information only. See Exporting Dat a to a QuickShip Vault. 8. Ship the QuickShip vault to the location where the new computer is installed, and connect it to the same LA N with a valid network address. Record the network address. 9. Open CentralControl and, for the Agent involved, change the network address of the vault to the network address of the QuickShip vault. 10. Disconnect the QuickShip vault from the LA N and ship it to the main vault location. Change the network address of the QuickShip vault to the network address that it used before it was shipped. 11. Import the QuickShip vault data on the main vault. See Importing Data from a QuickShip Vault. 12. Open CentralControl and, for the Agent involved, change the network address of the QuickShip vault to the network address of the vault. You can now schedule regular backups. 13. Initialize the QuickShip vault. See Initializing a QuickShip Vault.
Page 187
26. 7
Compl eting a L arge Reseed
To complete a large res eed: 1. 2. 3. 4. Connect the QuickShip vault to the same Local Area Network (LA N) as the main vault. Create a profile for the QuickShip vault on the main vault. See Creating a QuickShip Profile. Initialize the QuickShip vault. See Initializing a QuickShip Vault. Export the main vault data to the QuickShip vault. Select Restoring, reseeding and customer/account information . See Exporting Data to a QuickShip Vault. 5. Ship the QuickShip vault to the location where you want to complete the reseed, and connect it to the LAN with a valid net work address. Record the network address. 6. For each of the Agents that you want to res eed, use Cent ralCont rol and change the net work address of the vault to the network address of the QuickShip vault. 7. Disconnect the QuickShip vault from the LA N and ship it to the main vault location. Change the network address of the QuickShip vault to the network address that it used before it was shipped. 8. 9. Import the QuickShip vault data on the main vault. See Importing Data from a QuickShip Vault. For each of the Agents that you reseeded, use CentralControl to change the net work address of the QuickShip vault to the network address of the vault. You can now schedule regular backups. 10. Initialize the QuickShip vault. See Initializing a QuickShip Vault.
26. 8
Compl eting a L arge Restore
To complete a large restore: 1. 2. 3. 4. Connect the QuickShip vault to the same Local Area Network (LA N) as the main vault. Create a profile for the QuickShip vault on the main vault. See Creating a QuickShip Profile. Initialize the QuickShip vault. See Initializing a QuickShip Vault. Export the main vault data to the QuickShip vault. Select Restoring, reseeding and customer/account information . See Exporting Data to a QuickShip Vault. 5. Ship the QuickShip vault to the location where you want to complete the restore, and connect it to the LAN with a valid net work address. Record the network address. 6. For each Agent you want to restore or res eed, use CentralControl to change the net work address of the vault to the network address of the QuickShip vault. 7. Restore the data from the QuickShip vault.
Page 188
Working w ith QuickShip Vaults 8. Optionally, to reseed Jobs, complete a regular backup and specify the QuickShip vault as the destination. 9. Disconnect the QuickShip vault from the LA N and change the network address of the QuickShip vault to the network address that it used before it was shipped. 10. If you completed a reseed, import the QuickShip vault data on the main vault. See Importing Data from a QuickShip Vault. 11. For each of the Agents that you restored or reseeded, use CentralControl to change the network address of the QuickShip vault to the network address of the vault. You can now schedule regular backups. 12. Initialize the QuickShip vault. See Initializing a QuickShip Vault.
26. 9
Using a Quic kS hip V ault to E xpo rt D ata for Seedi ng
You can run more than one export to a single QuickShip vault. You do not need to initialize the QuickShip vault when you run multiple exports. When you export safesets from wit hin a series, they are all seeds. To use a QuickShip vault to export dat a for seeding: 1. Export the customer data to the QuickShip vault. Select Reseeding and customer/account information only. See Exporting Dat a to a QuickShip Vault. 2. Ship the QuickShip vault to the location where you want to complete the reseed, and connect it to the LAN with a valid net work address. 3. For each Agent you want to seed, open CentralControl and change the network address of the vault to the network address of the QuickShip vault. You can now start ad-hoc backups. 4. 5. 6. Disconnect the QuickShip vault from the LA N and ship it to the main vault location. Connect the QuickShip vault to the same Local Area Network (LA N) as the main vault. Import the QuickShip vault data on the main vault. See Importing Data from a QuickShip Vault. Backup data, synchronization files and database records are copied from the QuickShip vault to the main vault. Backup and Restore logs are not copied. 7. Use CentralControl to change the network address of the QuickShip vault to the net work address of the vault. Agents can then resume backups to the main vault. 8. Initialize the QuickShip vault. See Initializing a QuickShip Vault.
Page 189
26. 10 Using a Quic kS hip V ault for Dis ast er R ecov ery
To use a QuickShip vault for disaster recovery: 1. 2. Initialize the QuickShip vault. See Initializing a QuickShip Vault. On the main vault, export the customer dat a to the QuickShip vault. Select Re storing, reseeding and customer/account information . See Exporting Data to a QuickShip Vault. 3. Ship the QuickShip vault to the location where you want to complete the disaster recovery, and connect it to the LAN with a valid network address. 4. For each Agent you want to restore, open CentralControl, change the network address from the main vault to the net work address of the QuickShip vault, and complete the restore/rec overy. 5. For each Agent you restored, connect to the Agent, open CentralControl and change the network address from the QuickShip vault to the network address of the main vault. 6. Initialize the QuickShip vault. See Initializing a QuickShip Vault.
26. 11 QS M I mport Storag e Loc ation Sel ection

The following table describes how imported and exported QuickShip vault data is stored:
Scenario The imported data was previously exported from the main vault The imported data was Description Data is added to the primary storage location on the main vault when the customer or organization can be authenticated. If the customer or organization cannot be authenticated, data is added to the default storage location. Data is added to the default storage locations on the main vault that are associated with
not previously exported the customer or organization if the data was exported from the main vault. from the main vault Data is added to the default storage location if the customer or organization backed -up to the QuickShip vault but have not previously exported to the main vault. Data is added to the storage location for the account if the customer or organization data was exported from the main vault, and a new customer or organization has backed up the computer to the QuickShip vault. When the data is imported to the main vault, the new customer or organization is updated with the correct storage locations. The imported task was exported from the main vault The storage locations are obtained from the existing task on the main vault.
Page 190
Scenario The imported task was not exported from the main vault A new computer is registered on the QuickShip vault
Description The storage locations are obtained from its associated user. If there is no associated user, the first available primary storage location is used.
The users that either registered or backed up to that computer are examined against the users on the original vault. If one is found, its storage locations on the original vault are used for the new computer during the import. If none are found, the default locations on the original vault are used. This requires that you create a computer with the same customer location with the same account/user. If the user name does not match a user name on the original vault, but the cu stomer location and account name are the same, then the storage locations for that account on the original vault are used. This will not update the storage locations for the new user itself when imported. You cannot create a new customer location on the QuickShip vault with the same account/user information as another customer location. Registering a new computer under a new customer location will cause the default locations to be used on the original vault.
Page 191
27 Command Reference
This command referenc e provides information about the following Director commands: agentinforeports dbbackup migrates econdary qsm replvault secondaryop vaultop vvanalyz vvarchive vvcopy vvex port vvimport vvmigrat vvmove vvpoolop vvpurge vvrecall Note: Only the listed commands are supported. The command documentation uses the following conventions: Variables appear in italics . Optional parameters appear in square brackets [ ]. Sets of choices appear in curly brackets { }. Choices are separated by vertical lines |. If you must enter a password for a command, the password appears as clear text. Commands that you run appear in the log files.
Page 192
Command Reference You can use the Custom Command option to run a group of Director commands in a batch file. Add the batch file to the prog folder in the EVault Software Director installation folder. Specify the FORCEDOS option. If you want the Scheduler to run a program, you must copy the program to the prog folder in the EVault Software Director installation folder.
27. 1
age ntin forepo rts
The agentinforeports command writes information about the Agents registered on the vault into comma separated value (CSV) files in the Director\bill directory. Unless the command is used with the /check subcommand described below, the agentinforeports command creates LicenseUsageReport_ yyyymmdd.cs v and DatatypeReport_yyyymmdd.cs v files, where yyyymmdd is the year, month and day when the report was generated. The LicenseUsageReport CSV file includes version, type, and license information for each Agent that is registered to the vault. The DatatypeReport CSV file includes the version and type of each Agent that is registered to the vault, and provides pool footprint information for each task. Syntax agentinforeports [ subcommand] Subcommands
Subcommand /id /check filename /defaultquotas /simdefaultquotas
Description Writes customer IDs instead of customer names in the CSV files. Verifies that the file has not been modified since it was generated. A filename must be specified. Sets all customer quotas to equal current usage for licensing of Agent features. Simulates setting all customer quotas to equal current usage for licensing of Agent features.
Page 193
27. 2
dbbackup
The dbbackup command is used to back up and restore the vault database, and reduce the size of the transaction log file. The command produces a DBBA CKUP.LOG file in the VV_LOGS directory. Syntax dbbackup subcommand Subcommands
Subcommand
Description
backup directory Creates a backup of a vault database . directory is the physical path to the location where the database backup will be saved. restore directory Restores a previously backed up vault database . directory is the physical path to the location of the database backup to restore. Shrink Shrinks a transaction log file.
Page 194
Command Reference
27. 3
migrate se cond ary
Moves safesets from primary (online) to the appropriate secondary storage group and location. Syntax migratesecondary taskid= taskid [safeset=<1,2,3,...>] [last_online] [path=< destination>] [user=<userName>] [password=<password>] [useDefaultCredentials] [preview=1|2] [verify_every=< value>] [verify_last] or migratesecondary taskid=< taskid> use_retention [last_online] or migratesecondary param= parameterFilename Parameters
Parameter taskid safeset last_online use_retention path preview
Description The task id or '*' for all tasks. A comma-separated list of safesets. Indicates that the last online safeset is migrated. Applies the retention rules for migration. Copies individual safesets to a secondary location without modifying the primary storage. Enter 1 to preview safesets, or enter 2 to preview the safesets and the storage that would be migrated to secondary.
verify_every
Verifies every first (1), second (2), or third (3) migrated safeset. Enter zero (0) for no verification.
verify_last param
Verifies the last safeset. replaces all parameters with a text file.
Page 195
Director 7.0 Operations Guide Remarks The parameter file has the following format: ============================================================ CONFIGVERSION=3 CONTENT_VERSION=1 # Global flags: ALLTASKS=TRUE # set to TRUE or FALSE MARK_AS_OFFLINE=FALSE # set to TRUE or FALSE MIGRATE_LAST_ONLINE=FALSE # set to TRUE or FALSE PREVIEW=2 # 1 for safesets, 2 for safesets and storage sizes. VERIFY_EVERY=<value> # verify every so many safeset (0 for no verification) VERIFY_LAST=FALSE # verify the last safeset always # You MUST specify one and ONLY one of the following methods for migration: # METHOD 1: Using Business Rules. # specify ONLY one of the following 3 rules to use for implicit migration MAX_DAYS_ONLINE=90 # Specify max days online rule) # Or MAX_SAFESETS_ONLINE=2 # Specify max online safesets rule) # Or USE_RETENTION=TRUE # Use Archive retentions (TRUE or FALSE) # Scope selection: # The specified objects are processed based on the business rule. CUSTOMER=1,4,5 # Process these customers LOCATION=1,4,5 # Process these customer locations COMPUTER=10,11 # Process these computers TASK_1=25 # Process this task TASK_2=28 # Process this task
Page 196
Command Reference # ... More tasks can go here ... # METHOD 2: Explicit Specification of Safesets. TASK_1=23:2,4,7,8 # Explicit migration. Process task 23, safesets 2,4,7,8# ... More tasks with safesets can go here ... Examples This example migrat es safesets 3, 4, 5 and 6 from task 23: migratesecondary taskid=23 safeset=3,4,5,6 The following example copies the online safes ets 3, 4, 5 and 6 from task 23 to a specified path. This creates a new (detached) secondary pool system. migratesecondary taskid=23 safeset=3,4,5,6 path=<directory_path> This example migrat es expired safesets from task 23 and applies the retention rules: migratesecondary taskid=23 use_retention This example migrat es all expired safesets for all tasks and applies the retention rules: migratesecondary taskid=* use_retention This example migrat es expired safesets for all tasks, applies the retention rules, and includes the last safest in the migration: migratesecondary taskid=* use_retention last_online
Page 197
27. 4
qsm
Initializes, imports, and exports a QuickShip vault. Syntax qsm subcommand Subcommands
Subcommand
Description Initializes the QuickShip vault described in the profile. Imports data from QuickShip vault described in the profile. Exports data to a QuickShip vault described in the profile. Export-specific data is in the export config file, it contains list of objects to copy and additional mapping info. The optional -cleanup argument deletes the export config file on exit.
init -qsmconf=qsmProfileName import -qsmconf=qsmProfileName export -qsmconf=qsmProfileName config=<export config file name > [-cleanup]
Page 198
Command Reference
27. 5
repl vault
Cont rols and runs vault replication for 1:1 and N:1 configurations. Syntax replvault subcommand [parameters] Subcommands
Subcommand cfgfile fileName DIFF scope [ob ject-id] [-lastsafeset] [-diffmethod={IDX|CRC|DATA}]
Description Takes all parameters from configuration file. Compares replication objects and creates a difference report. Where: scope : VAULT, CUSTOMER, LOC ATION, COMPUTER, TASK, ACCOUNT, or USER ob ject-id: Is the object's database ID, not required for VAULT. -lastsafeset: Compares hash values for last safesets only. -diffmethod: Controls how the safeset data gets compared. Available options are: IDX: Compares pool indexes only (fast but least reliable) CRC: Uses file CRCs to compare data (fast and reliable but will not detect data block level pool file corruption) DATA: Reads and compares the entire backup data (very slow but will detect data block level corruption)
DISABLE ENABLE GENSATREPORT scope [object-id] [-lastsafeset] [-diffmethod=IDX|CRC|DATA]
Disables processing of replication events. Enables processing of replication events. Compares replication objects and creates a difference report for Satellite vaults.
Page 199
Subcommand REGSAT basevault=hostname port=port otrk=authorization_code [altvault=address:port] [-force]
Description Registers the Satellite vault on a Base vault. Where: Basevault -The IP or hostname of the Base vault. Port - The port where the Base vault is listening. otrk: The authorization code for the Satellite vault. Altvault - Base vault address:port for the Agent connection (if different from <basevault> and <port> -force - Forces registration even if data exists on this Satellite vault which could be overwritten
REPSAT [emailto=email_address]
Generates a status report for all of the satellites registered on the Base vault. Email_address is the email address where the report is sent. Resets 1:1 replication configuration, if it exists. Changes the current vault replication role to active. force forces the replication role on the vault to active.
RESET SETACTIVE [-force]
SETSATREPORT satelliteID Compares replication objects and creates a difference report. [requestID=[params file]] OR * params file - The file that contains the parameters for the SETSATREPORT satelliteID scope [object-id] [diff report. lastsafeset] [-diffmethod={IDX|CRC|DATA}] scope - CUSTOMER, LOC ATION, COMPUTER, TASK [emailto=email_address] object-id - The object's database ID, not required for VAULT. -lastsafeset - Compares hash values for last safesets only. -diffmethod - Controls how the safeset data gets compared IDX - Compares pool indexes only (fast but least reliable) CRC - Use file CRCs to compare data. DATA - Read and compare the entire backup data. emailto - The email address to which to send the report. STATSAT Uploads the statistics from the Satellite vault to the Base vault.
Page 200
Command Reference
Subcommand SYNCH scope [object-id] [replmode=ACTIVE|BAV]
Description Submits a replication event for the specified object. scope - VAULT, CUSTOMER, LOC ATION, COMPUTER, TASK, ACCOUNT, or USER object-id - The object's database ID, not required for VAULT replmode ACTIVE or BAV. The default is both.
SYNCHSAT satelliteID
Submits a replication event for the specified Satellite vault, where satelliteID is the ID of the Satellite vault to synchronize. Removes "replicated" bit from safesets so the next satellite replication replicates this safeset. Where: taskID - a DB identifier for a particular task or "*" for all tasks. safesets - a comma-separated list of safesets to process or "*" for all safesets.
CLEARREPLBIT taskID safesets
LATE scope [object-id] [-days=X] [-handlePaused] [emailto=]
Produces a report for tasks that have fallen a specific numbers of days behind in replication. Where: scope - VAULT, CUSTOMER, LOC ATION, COMPUTER, TASK object-id - The object's database ID, not required for VAULT. X - The number of days. The default is 5 days. -handlePaused - Will process the tasks which are paused from replication
Note s If you run the Replication Lag Report (for 1:1 Replication) from the command line, you must specify REPLVAULT with the LA TE command. If you run the Replication Lag Report (for N:1 Replication) from the command you must use REPLVA ULT SETSA TREPORT LA TE. Example The following command produces a late report for the entire vault, for t asks over 10 days, includes paused tasks, and sends the report by email to the administrator: replvault late vault -days=10 -handlepaused emailto=administrator@EVault.com
Page 201
27. 6
seco ndaryo p
The secondaryop command performs the following operations in secondary st orage pools: checks physical and logical dat a integrity deletes safesets deduplicates dat a optimizes pools attaches, closes and detaches pools You can specify the secondary storage pool for an operation using a scope parameter in the command. Syntax secondaryop subcommand scopeParameter Subcommands
Subcommand checkcrc close [offline] [new_group= storageGroupName ]
Description Validates the physical integrity of files in secondary storage. Closes a secondary storage pool so that it is read-only and cannot be changed or updated. To mark safesets as offline after closing the pool, include the offline parameter. To specify a secondary storage group to use for a task after closing the previous one, include the new_group=storageGroupName parameter. You can only include the new_group=storageGroupName parameter if the command also includes the taskid=id scope parameter.
dedup delete safeset={id|last|*}
Deduplicates data in a secondary storage pool. Deletes one or more safesets from a secondary storage pool: the safeset with the specified id , the last committed safeset, or all safesets.
Page 202
Command Reference
Subcommand expire
Description Deletes expired safesets in a secondary storage pool. This command is similar to the vvmigrat online command for primary storage pools, but applies the retention policy across both the primary and secondary storage pools. This can result in the deletion of all safesets in secondary storage. For example, if a task has one backup in primary storage and nine in secondary storage, and the retention settings are Online safesets=1, Online days=0 and Archive days=0, running the secondary op expire command deletes all safesets from secondary storage.
mount storage_location=path [reattach_deleted]
Attaches a secondary storage pool. A secondary storage pool can only be attached for its associated task, and is then read-only. Use the storage_location= path parameter to specify the location of the secondary storage pool to attach. You can not include other scope parameters with this subcommand. To re-attach a deleted safeset to the primary pool, include the reattach_deleted parameter.
mountall storage_location=path
Attaches all secondary storage pools under a specified directory. Use the storage_location= path scope parameter to specify the directory with secondary storage pool locations to attach. You can not include other scope parameters with this subcommand.
optimize optimize dedup ssiverone safeset={id|last} [/local]
Optimizes a secondary storage pool. Optimizes and deduplicates data in a secondary storage pool. Checks a safeset in a secondary storage pool for logical corruption: either the safeset with the specified id, or the last committed safeset. This verification process is more reliable but slower than the verifyidxone process. To get information from the database for all tasks and skip detached pools, include the /local parameter. You can only include the /local parameter if the command also includes the storage_location=path scope parameter. Note: The system assigns an identification number ( id) to each safeset. To determine the id for a safeset, you can view its properties in the Director Management Console.
Page 203
Subcommand ssiverall [/local]
Description Checks all safesets in a secondary storage pool for logical corruption. This verification process is more reliable but slower than the verifyidxall process. To get information from the database for all tasks and skip detached pools, include the /local parameter. You can only include the /local parameter if the comm and also includes the storage_location=path scope parameter.
syncfix
Checks for and fixes discrepancies between main and pool synchronization information in a secondary storage pool.
unmount
Detaches a secondary storage pool. Use the storage_location= path parameter to specify the location of the secondary storage pool to detach. You can not include other scope parameters with this subcommand.
unmountall storage_location=path
Detaches all secondary storage pools under the specified directory. Use the storage_location=path scope parameter to specify the directory with secondary storage pools to detach. You can not include other scope parameters with this subcommand.
verifyidxone safeset={id|last} Checks a safeset in a secondary storage pool for logical corruption: either the safeset with the specified id, or the last committed safeset. This verification process is less reliable but faster than the ssiverone process. Unlike ssiverone, this process d oes not read the pool files. To get information from the database for all tasks and skip detached pools, include the /local parameter. You can only include the /local parameter if the command also includes the storage_location=path scope parameter. Note: The system assigns an identification number ( id) to each safeset. To determine the id for a safeset, you can view its properties in the Director Management Console. verifyidxall [/local] Checks all online safesets in a secondary storage pool for logical corruption. This verification process is less reliable but faster than the ssiverall process. Unlike ssiverall, this process does not need pool files. To get information from the database for all tasks and skip detached pools, include the /local parameter. You can only include the /local parameter if the command also includes the storage_location=path scope parameter.
Page 204
Command Reference Scope Parameters
Scope Parameter taskid=id
Description Performs the operation for the secondary storage pool for the task with the specified id. To perform the operation in pools for all tasks, enter * as the id. This parameter can only be used for secondary storage pools with tasks still on the local vault. Note: The system assigns an identification number ( id) to each task. To determine the id for a task, you can run a report for the task or view its properties in the Director Management Console. Note: The taskid parameter is not used with the mount, mountall, unmount or unmountall subcommands.
storage_location=path [user=[domain \]username password=password | /useDefaultCredentials]
Performs the operation for the secondary storage pool in the specified path. The path can be a local or a UNC path. If the location is a network share, user=[domain \]username password=password specify the domain, username and password for connecting to the network share. Alternatively, to connect to the network share using default credentials, include the /useDefaultCredentials parameter.
storage_group=storageGroupName
For use with the checkcrc, close, ssiverone, ssiverall, verifyid xone and verifyidxall subcommands only. Performs the operation for the secondary storage group with the specified storageGroupName.
Examples The following command performs a CRC in the "secondary" storage group: secondaryop checkcrc storage_group=secondary The following command closes secondary storage for task 2 and marks safesets in the pool as offline: secondaryop close taskid=2 offline The following command deduplicates data in the \\computer1\c$\secondary storage pool location: secondaryop dedup storage_location=\\computer1\c$\secondary The following command deletes the last safeset from the e: \secondary storage pool location:
Page 205
Director 7.0 Operations Guide secondaryop delete safeset=last storage_location=e:\secondary The following command deletes expired safesets for task 3 from secondary storage: secondaryop expire taskid=3 The following command attaches the secondary storage pool in c: \secondary3: secondaryop mount storage_location=c:\secondary3 The following command attaches all secondary storage pools under the e: \secondarystorage directory: secondaryop mountall storage_location=e:\secondarystorage The following command optimizes dat a in secondary storage for task 4: secondaryop optimize taskid=4 The following command optimizes and deduplicates data in the secondary storage pool in f: \secondary: secondaryop optimize dedup storage_location=f:\secondary The following command verifies the last safes et in the "secondary 2" storage group: secondaryop ssiverone safeset=last storage_group=secondary2 The following command verifies all safesets in the \\computer1\c$\secondary storage pool location: secondaryop ssiverall storage_location=\\computer1\c$\secondary The following command synchronizes main and pool synchronization information for task 1 in secondary storage: secondaryop syncfix taskid=1 The following command det aches the secondary storage pool in the f: \secondary storage directory: secondaryop unmount storage_location=f:\secondary The following command det aches all secondary storage pools under the d: \secondarystorage directory: secondaryop unmountall storage_location=d:\secondarystorage The following command verifies safeset 6 for task 5 in secondary storage: secondaryop verifyidxone safeset=6 taskid=5 The following command verifies safesets in the f:\secondary storage pool location: secondaryop verifyidxall storage_location=f:\secondary
Page 206
Command Reference
27. 7
vaulto p
Allows you to remotely start or stop vault services, or to shut down the vault services and spawned vault processes. Note: The vaultop command executable is available in the Utils directory where the Director is installed. Syntax vaultop subcommand [service1...servicen ] Subcommands
Subcommand start_services stop_services timeout
Description Starts one or more selected vault services. Stops one or more selected vault service(s). timeout is the number of seconds for each vault service to stop gracefully. The default value for timeout is 30 seconds.
restart_services shutdown_vault
Stops then starts one or more selected vault service(s). Stops all vault services and all spawned vault processes. timeout is the time for each vault service and process to stop gracefully. After the vault services and processes are stopped, all Active vault processes are terminated. The default value for timeout is 30 seconds.
Services service1...servicen specify one or more vault services to start or stop. The following table lists possible values. Note: You cannot specify services wit h the shutdown_vault subcommand.
Service * (asterisk) AdminService Description All vault services. This is the default value. Interface service for the Director Management Console. This service translates between commands made in the Console and the command line. It provides feedback to the Console on jobs that are running. This service produces AD MINSERVICE logs in the VV_LOGS directory.
Page 207
Service VVQmanager
Description Service that manages the launch sequence of non-backup, restore, and synch processes on the vault. It enforces the Maximum Number of Jobs setting. It produces QMAN AGER logs in the VV_LOGS directory.
VVSvrDae
Scheduler service that enforces the EVault Software Director schedule settings. It produces VVSVRDAE logs in the VV_LOGS directory.
VVListen
Service that listens to Agent-initiated traffic and spawns a server process. It validates the traffic based on the signature of the packets it receives. It also listens on the ports specified in Vault Settings. If you add, change, or delete a port, you must restart the VVListen service to allow the service to listen to the new port. It produces a SPAWN log for each server process it starts.
ReplService
Service that handles replication on the vault.
Examples This example starts the ReplServic e and VVListen servic es: vaultop start_services ReplService VVListen This example stops all vault services with a 120-s econd timeout: vaultop stop_services 120 * This example restarts the ReplService and VVListen services: vaultop restart_services ReplService VVListen This example shuts down the vault in 120 seconds: vaultop shutdown_vault 120
Page 208
Command Reference
27. 8
vvanal yz
The vvanalyz command produces reports on tasks, pools and vaults. You must run the vvanalyz command locally on the vault you want to report on. Syntax vvanalyz subcommand [parameters] Subcommands
Subcommand /latestatus [/timeframe=hours] [scopeParameter] [destination ]
Description Runs a Late Server Status report. The report lists tasks that were not backed up in a specified number of hours before the current time. For more information, see Creating a Late Server Status Report. To specify the number of hours before the current time for finding tasks that were not backed up, include the /timeframe= hours parameter, where hours is the number of hours before the current time. If you do not include the /timeframe= hours parameter, the report lists tasks that were not backed up in the past 48 hours. For scopeParameter and destination descriptions, see the ScopeParameters and Destinations tables .
/originalsizeupdate
Updates the Original size value in the database for one or more safesets. The Original size value is the amount of original data protected by a safeset, and is provided by the Agent. Note: This subcommand is only used for safesets created with Director 6.31 or earlier. The Original size is automatically updated in the database for safesets created with Director 7.0 or later.
Page 209
Subcommand /missedbackups [missedBackupParameters] [scopeParameter][destination ]
Description Runs a Missed Backups report. The report lists backup tasks that were scheduled or expected to run, but for which a safeset does not exist. A task appears in the report even if the scheduled or expected backup ran successfully but the committed safeset was later deleted. For more information, see Creating a Missed Backups Report. For a list of missedBackupParameters , see the vvanalyz /missedbackups parameters table. For scopeParameter and destination descriptions, see the ScopeParameters and Destinations tables . Note: If the vault's schedule.cfg file has been modified manually, the Missed Backups report does not report tasks correctly.
/storage [/bare] [scopeParameter][destination ] Runs a Storage report. The report shows the number of safesets and amount of data in a vault for a single task, or for all tasks in a vault, organization/customer, location, or computer. For more information, see Creating a Storage Report. To produce a report in CSV format, include the /bare parameter. If you do not include the /bare parameter, report data appears in columns. For scopeParameter and destination descriptions, see the ScopeParameters and Destinations tables . /storageLocation [scopeParameter][destination ] Runs a Storage Location report. The report lists all primary, secondary and archive storage locations for one task, or for each task in a vault, organization/customer, location, or computer. For more information, see Creating a Storage Location Report. For scopeParameter and destination descriptions, see the ScopeParameters and Destinations tables .
Page 210
Command Reference
Subcommand /storageextract /poolsize [storageExtractParameters][destination ]
Description Reports pool type (online or offline) and pool data file sizes for a vault in CSV and log files. The resulting CSV files are saved in the Director\bill directory, and are named yyyymmdd _ONLINE.csv and yyyymmdd _OFFLINE.csv, where yyyymmdd is the year, month and day when the report was generated. The CSV files include the customer name, location code, computer name, and total original gigabytes (GB) for the computer. You can import the contents of the output file into a spreadsheet or other application to produce reports. The log file is saved in a StorageExtract< uniqueIdentifier>.log file in the Director\logs directory. When report information appears in the log file, it contains more detail than the CSV files, and includes pool size information for each task, with totals at the computer, location, customer, and vault levels. Numbers in the CSV files are in gigabytes, and numbers in the log file are in bytes, kilobytes, megabytes and gigabytes. Discrepancies between the CSV and log files can occur because of conversion and rounding. For a list of storageExtractParameters, see the vvanalyz /storageExtract /poolsize Parameters table . For destination descriptions, see the Destinations table.
/syncscan [scopeParameter] [destination ]
Runs a Last Backup Status report. The report shows information about the last backup for one task, or for each task in a vault, organization/customer, location, or computer. For more information, see Creating a Last Backup Status Report. For scopeParameter and destination descriptions, see the ScopeParameters and Destinations tables .
/vaultstorage [destination ]
Runs a Vault Storage report. The report shows the amount of vault utilization. For more information, see Creating a Vault Storage Report. For destination descriptions, see the Destinations table.
Page 211
Director 7.0 Operations Guide Scope Parameters Note: If you do not specify a scopeParameter, the vvanalyz subcommand runs for the entire vault.
ScopeParameter /Customer=id Description Runs the report for the customer with the specified id. Note: The system assigns an identification number ( id) to each customer. To determine the id for a customer, you can run a report for the customer from the Director Management Console and view the customer id in the command line in the resulting report log file. /Location=id Runs the report for the location with the specified id. Note: The system assigns an identification number ( id) to each location. To determine the id for a location, you can run a report for the location from the Director Management Console. The location id appears in the command line in the resulting report log file. /Computer=id Runs the report for the computer with the specified id. Note: The system assigns an identification number ( id) to each computer. To determine the id for a computer, you can run a report for the computer from the Director Management Console. The computer id appears in the command line in the resulting report log file. /Task=id Runs the report for the task with the specified id . To run the report for all tasks, enter * as the id. Note: The system assigns an identification number ( id) to each task. To determine the id for a task, you can view its properties or run a report for the task in the Director Management Console.
Destinations Note: If you do not specify a destination for a report, the report is saved as a log file.
Destination /logfile /email=user@address Description Saves the report as a log file. Emails the report to the specified user@address and saves the report as a log file. Note: Before you can email a report, an SMTP server network address must be entered in Vault Settings. For more information, see Setting Email Notifications .
Page 212
Command Reference
Destination /output=filename
Description Saves the report as a text file with the specified filename , where filename is the path and filename for the output file.
vvanalyz /missedbackups Parameters In addition to the parameters listed in the ScopeParameters and Destinations tables, the vvanalyz /missedbackups subcommand can include the following paramet ers:
vvanalyz /missedbackups Parameter /bare Creates the Missed Backups report in CSV format. If you do not include the /bare parameter, report data appears in columns. /timeframe=hours Specifies the number of hours for the Missed Backups report timeframe. A backup task that is not scheduled in CentralControl appears in the Missed Backups report if a safeset exists for the task from before the report timeframe, and no safeset exists for the task during the timeframe. Note: The timeframe does not affect whether tasks scheduled in CentralControl appear in the Missed Backups report. The report timeframe is measured back from the current local time on the vault when the report runs. For example, if you specify 24 hours for the report timeframe and the report runs on November 21, 2011 at 10:00, the report includes unscheduled backup tasks with safesets dated before November 20, 2011 at 10:00 and no safesets from between November 20, 2011 at 10:00 and November 21, 2011 at 10:00. /sendtoadmin /detailed /sendtocustomer [/header=headerFile ] [/footer=footerFile ] Sends the Missed Backups report to the administrator. Specifies that the Missed Backups report should show errors for failed backups. Sends the Missed Backups report to the customer email address. To specify a header file for the report, include the /header= headerFile parameter, where headerFile is the path and filename for the header file.To specify a footer file for the report, include the /footer=footerFile parameter, where footerFile is the path and filename for the footer file. Note: Before you can email the report, an email address must be specified for the customer and an SMTP server network address must be entered in Vault Settings. For more information, see Setting Email Notifications . Description
Page 213
Director 7.0 Operations Guide vvanalyz /storageextract /poolsize Parameters The vvanalyz /storageextract /poolsize subcommand can include the following parameters:
vvanalyz /storageextract Description /poolsize Parameter /billing Creates CSV files in the \Director\bill directory, but does not include report data in the Director\logs directory. /analyzedisabledtask /url /nodata /header /native Includes disabled tasks in the report. Includes Customer URLs in the CSV files. Includes computers with no tasks in the pool information Includes field names at the top of the CSV files. Includes native storage amounts in the CSV files. The native storage amount is the amount of original client data that is protected by a safeset. /vaultname Includes the vault name in the CSV files.
Examples The following command runs a Late Server Status report that lists all tasks that were not backed up in the 24 hours before the current time: vvanalyz /latestatus /timeframe=24 The following command runs a Missed Backups report with a 72 -hour timeframe in CSV format, and emails the report to user@address.com: vvanalyz /missedbackups /timeframe=72 /bare /sendtoadmin /email=user@email.com The following command runs a Missed Backups report with a 48 -hour timeframe, and sends the report, with the specified header, to the customer e-mail address: vvanalyz /missedbackups /sendtocustomer /header=c:\headerfile.txt The following command runs a Storage report for Loc ation 1, and emails the report in CSV format to user@address.com: vvanalyz /storage /location=1 /email=user@address.com /bare
Page 214
Command Reference The following command runs a Storage report for Customer 3, and saves the report in CSV format in a log file: vvanalyz /storage /customer=3 /bare The following command runs a Storage Location report for Computer 1: vvanalyz /storageLocation /computer=1 The following command runs a Last Backup Status report for Task 1, and saves the report in a log file: vvanalyz /syncscan /task=1 The following command runs a Last Backup Status report for Location 3, and emails the report to user@address.com: vvanalyz /syncscan /location=3 /email=user@address.com The following command runs a Vault Storage report, and emails the report to user@address.com: vvanalyz /vaultstorage /email=user@address.com The following command reports pool type and pool dat a file sizes for a vault in CSV and log files, and includes Customer URLs, field names, and native storage amounts in the CSV files: vvanalyz /storageextract /poolsize /url /header /native The following command reports pool type and pool dat a file sizes for a vault in CSV files, but does not include pool information in the log file: vvanalyz /storageextract /poolsize /billing
27. 9
vvarc hiv e
Archives safesets from the primary pool. Syntax vvarchive [ taskid | -disk ] If you do not specify a taskid, all safesets are archived. If you do not specify a taskid, but include -disk, only the tasks that are set to archive to disk are archived. Example The following command arc hives all safesets from the primary pool: vvarchive
Page 215
27. 10 vvcopy
Copies or clones objects, including customers, locations, computers and tasks, or entire vaults. Syntax vvcopy /command_file=< commandFile> /vault_profile_from=< sourceVaultProfile> /vault_profile_to=<destinationVaultProfile> [/PHYSICAL] [/LOGICAL] [/linkSecondaryPools] [/MOVE] Parameters
Parameter command_file=<commandFile >
Description Path and filename of the vvcop y command file, which specifies the object to copy and provides names for copied objects. For more information, see Command File Structure. When you run the vvcopy command through the Director Management Console, the commandFile is created automatically and saved in the path \Director\conf folder. If the vvcopy command runs successfully, the file is deleted automatically. For more information, see Copying and
Cloning Data.
vault_profile_from=<sourceVaultProfile > Path and filename of a file containing source vault information. For more information, see Vault Profile File Structure. When you run the vvcopy command through the Director Management Console, the sourceVault Profile file is created automatically and saved in the path \Director\conf folder. If the vvcopy command runs successfully, the file is deleted automatically. For more information, see
Copying and Cloning Data.

vault_profile_to=<destinationVaultProfile > Path and filename of a file containing destination vault information. For more information, see Vault Profile File Structure. When you run the vvcopy command through the Director Management Console, the sourceVault Profile file is created automatically and saved in the path \Director\conf folder. If the vvcopy command runs successfully, the file is deleted automatically. For more information, see
Copying and Cloning Data.
Page 216
Command Reference
Parameter PHYSIC AL LOGICAL linkSecondaryPools
Description Copies pool data files. Copies meta data files. Creates a link to physical data from the secondary pool, but does not copy physical data from the secondary pool.
MOVE
Clones the object. Creates identical items with identical globally unique identifiers (GUIDs) on another vault.
Command File Structure The command file specifies which object to copy, and provides names for copied objects. To specify which object to copy, the command file includes one of the commands in the following table.
Object Vault Command
COPY_VAULT=VaultID COPY_CUSTOMER=CustomerID COPY_Location=LocationID COPY_ACCOUNT=AccountID COPY_COMPUTER=ComputerID COPY_USER=UserID COPY_TASK=TaskID
Customer
Location
Account
Computer
User
Task
The command file also includes names for objects that are lower in the hierarchy than the object being copied. For example, when you copy a customer, the command file includes the following information for objects lower in the hierarchy that are being copied: LOCATION_NEW_NAME= locationID,locationName ACCOUNT_NEW_NAME=accountID,accountName
Page 217
Director 7.0 Operations Guide CUSTOMER_NEW_NAME=c ustomerID,customerName BILLING_CODE_NEW_NAME= billingCode1ID,billingCode1Name BILLING_CODE_NEW_NAME= billingCode2ID,billingCode2Name COPY_CUSTOMER=CustomerID Vault Profile File Structure The vvcopy command requires two vault profile files: one for the source vault (where data is copied from) and one for the destination vault (where data is copied to). Each vault profile file has the following structure: CONFIGVERSION=3 SERVER=<serverHostname> Username=<username> DOMAIN=<domain> PASSWORD=<encryptedPassword> DATABASESERVERNAME=<Hostname\EVault_DB> DATALIB=SqlDbLib.DLL DATABASETYPE=sqloledb DATABASEUSERID=sa DATABASEPASSWORD=<encryptedDatabasePassword > VAULTID=<vaultID> CONTAINERID=0 CONTAINERTYPE=256 Note: < Hostname\EVault_DB>, < encryptedDatabasePass word> and < vaultID> values are available in the VaultDB.cfg file in the path\ Director\conf directory .
27. 11 vve xpo rt

Gets safesets from a local vault to a disk media. That media can then be transported to a user system, to be restored with the VVImport program.
Page 218
Command Reference Syntax vvexport taskid safeset(s) {devicename | /nobackupdata} [/maxfilesize=sizeInMegabytes][/catalog={4|5} [/catalogpath= location]] vvexport path safeset(s) {devicename | /nobackupdata} [/maxfilesize=sizeInMegabytes] [/catalog={4|5} [/catalogpath= location]] [/useDefaultForSrcUser |[/srcUser=<domain/username> /srcPassword=<encryptedPassword>]] [/useDefaultForDstUser | [/destUser=<domain/username> /destPassword=<encryptedPassword>]] [/catUser=<domain/username> /catPassword=<encryptedPassword>][/simulate] Parameters
Parameter taskid safeset(s) devicename nobackupdata maxfilesize
Description Unique internal task number. Found in the logs for that task's backup. Number in online list of safeset(s). Local disk path, or UNC path to remote disk for safesets (i.e., \\<Server>\<Share>\<path>) Exports catalogs and not safesets. Specifies the maximum safeset size, in megabytes, for use in outputting to a CD. If the safeset is larger in total than this size, you must split it across multiple CDs.
catalog catalogpath simulate
4 for version 3.1 Agents or earlier, OR 5 for version 3.2 Agents and later. Path on disk to which catalogs are exported. Allows you to view what would be generated, and the size required for the output storage. The simulate option writes the output to the VVExport log file.
Examples vvexport 1 4 c: /maxfilesize=1024 /catalog=5 /catalogpath=c:\Documents and Settings
Page 219
27. 12 vvimpo rt
Imports a safeset from disk into the pool system. Use for seeding or re-seeding. The safeset is stored in compressed SSI format, and named after the safeset being stored. You can use a UNC path to specify non-local disk. Syntax vvimport taskid synchnum sourcepath [/useDefaultCredentials | [/user=<username> /password=<password>]] Parameters
Parameter taskid synchnum sourcepath
Description Unique internal task number. Refer to the task for this safeset. Safeset number. Refers to local or remote (via UNC path) disk.
Page 220
Command Reference
27. 13 vvmig rat

Migrates safesets in accordance with retention policies. Syntax vvmigrat [noretentions] {online|offline|genoptidxv5|initsync} {tasked|last} [noninterruptible] or vvmigrat delete {taskID} {safeset#} [{safeset#}...] or vvmigrat param=<parameters_file> Note: vvmigrat param=<parameters_file> is only used for deleting objects. Remarks The parameter file has the following format: ============================================= CONFIG_VERSION=3 CONTENT_VERSION=1 # Command can be one of: DELETE COMMAND=DELETE # Scope selection: CUSTOMER=1,2,3 # Process these customers LOCATION=4,3 # Process these customer locations COMPUTER=49,60 # Process these computers ACCOUNT=5,6 # Process these accounts USER=11,12 # Process these users BILLINGCODE=250,139,3 # Process these billing codes # Tasks can be specified without safesets as follows: TASK=25,26,27,28 # Process these tasks # OR you can specify the tasks with/without safesets as follows:
Page 221
Director 7.0 Operations Guide TASK_1=25 # Process this task TASK_2=28 # Process this task TASK_3=23:2,4,7,8 # Explicitly process safesets 2,4,7,8 only in task 23 # ... More tasks with/without safesets go here ...
27. 14 vvmov e
The vvmove command moves files between storage locations in the primary storage group. Unless you specify a destination for the files, the system moves files to the storage location wit h the most available space. The vvmove command is useful, for example, for moving data from a storage location that you want to retire, or for moving index files to a faster location. Syntax vvmove subcommand [filter1... filtern] [/stoppedonbacktonormal] [/skipcrc] Subcommands
Subcommand /removeraidpath=physicalPath
Description Mo ves files from the specified storage location to other locations in the primary storage group. physicalPath is the path of the location from which you want to move files.
/consolidatetopath=physicalPath Mo ves files to the specified storage location from other locations in the primary storage group. physicalPath is the path of the location to which you want to move files. /applystoragepolicy [/filetype=filetype ] Mo ves files to preferred storage locations, as specified by the location storage policies. filetype can have the following values: idx Mo ves index files to their preferred locations. log Moves log files to their preferred locations. pool Moves pool data files to their preferred locations. You can include one or more /filetype parameters with the /applystoragepolicy subcommand. If you do not include a /filetype parameter, files with all types are moved to the preferred locations. /? Shows help information for the vvmove command.
Page 222
Command Reference Parameters
Parameter filter1... filtern
Description Specifies which files to move. You can include one or more of the following filters: /customer=id Moves files for the customer with the specified id. /customerlocation=id Mo ves files for the customer location with the specified id. /computer=id Moves files for the computer with the specified id. /task=id Moves files for the task with the specified id. Note: You cannot include /customer, /customerlocation, /computer and /task filters in the same vvmove command. For example, you cannot include both a /customer and a /computer filter in a vvmove command. /safeset=id Mo ves files in the safeset with the specified id. Note: You can include only one /safeset filter in a vvmove command. /srcraidpath=path For use with the /removeraidpath and /consolidatetopath subcommands only. Mo ves data with a minimum of one file in the specified path. If you do not include a filter, the system moves all files. Note: The system assigns an identification number ( id) to each customer, customer location, computer, task and safeset. To determine the id for a customer, customer location, computer, task or safeset, you can run a report for the item. You can also determine the id of a task by viewing its properties in the Director Management Console.
/skipcrc /stoppedonbacktonormal
Skips the cyclic redundancy check (CRC) when moving files. Stops moving files when the original storage location has enough free space.
Examples The following command moves files from the s:\local\index and s:\local\log directories: vvmove /removeraidpath="s:\local\index" /removeraidpath="s:\local\log" The following command moves index and log files to their preferred storage locations: vvmove /applystoragepolicy /filetype=idx /filetype=log The following command moves index, pool, and log files for customer 3 and customer 5 to the preferred storage locations: vvmove /applystoragepolicy/customer=3 /customer=5
Page 223
27. 15 vvpoolop
The vvpoolop command performs the following operations in primary storage pools: checks physical and logical dat a integrity deduplicates dat a optimizes pools re-enables suspect tasks You can specify the storage pool for an operation using a selection parameter in the command. You can also run Storage Pool Summary reports for both primary and secondary storage pools using the vvpoolop command. Syntax vvpoolop subcommand selection [parameters] Note: A selection must appear after the subcommand and before any parameters . Subcommands and Parameters
Subcommand and Parameters checkcrc [light]
Description
Checks the pool system for physical corruption. To only check for the presence of files, include the light parameter.
checksafesetpf checkallsafesetpf dedup
Checks single safeset pool files. Checks all pool files for safesets. Eliminates references to repeating data so the optimize subcommand can purge the data. For use with Version 5 pools only.
listfixed
Lists fixed files (i.e., files with no streams).
Page 224
Command Reference
Subcommand and Parameters optimize [dedup] [nointerrupt] [timeout minutes]
Description
Optimizes the pool system. To deduplicate data when optimizing the pool system, include the dedup parameter. To prevent incoming backups from cancelling existing optimization tasks, include the nointerrupt parameter. To unlock the tasks and exit after the specified number of minutes have elapsed, include the timeout minutes parameter, where minutes is the number of minutes. Note: The timeout minutes parameter is ignored for maintenance jobs .
ssiverone [id|last]
Checks a safeset for logical corruption: either the safeset with the specified id, or the last committed safeset. This verification process is more reliable but slower than the verifyidxone process. Note: The system assigns an identification number ( id) to each safeset. To determine the id for a safeset, you can view its properties in the Director Management Console.
ssiverall
Checks all online safesets for logical corruption. This verification process is more reliable but slower than the verifyidxall process.
summary [detailed]
Runs a Storage Pool Summary report for a primary storage pool system. The report provides information about the amount of disk space allocated to one task, or to each task in a vault. For more information, see Creating a Storage Pool Summary Report. To include information separately for each pool file in the report, include the detailed parameter.
summaryall [detailed]
Runs a Storage pool Summary report for both primary and secondary pool systems. The report provides information about the amount of disk space allocated to one task, or to each task in a vault. For more information, see Creating a Storage Pool Summary Report. To include information separately for each pool file in the report, include the detailed parameter.
unsuspect
Checks the logical and physical integrity of data for a suspect task, and enables the task if no data issues are found. If data integrity issues are found, the system does not enable the task.
upgrade_names
Upgrades the .file-names file to speed up the pool read operations.
Page 225
Subcommand and Parameters downgrade_names verifyidxone [id|last]
Description
Reverses the .file-names file upgrade made by the upgrade_names subcommand. Checks a safeset for logical corruption: either the safeset with the specified id, or the last committed safeset. This verification process is less reliable but faster than the ssiverone process. Unlike ssiverone, this process does not read the pool files. Note: The system assigns an identification number ( id) to each safeset. To determine the id for a safeset, you can view its properties in the Director Management Console.
verifyidxall
Checks all online safesets for logical corruption. This verification process is less reliable but faster than the ssiverall process. Unlike ssiverall, this process does not need pool files.
Selections
Subcommand task {id|*}
Description Performs the operation for the task with the specified id. To perform the operation for all tasks, enter * as the id. Note: The system assigns an identification number ( id) to each task. To determine the id for a task, you can run a report for the task or view its properties in the Director Management Console.
location physicalLocation
Performs the operation for pool systems that have at least one file in the specified physicalLocation . The physicalLocation can be a local or a UNC path.
Examples The following command performs a CRC in primary storage for task 2: vvpoolop checkcrc task 2 The following command optimizes and deduplicates data for all tasks: vvpoolop optimize task * dedup The following command deduplicates data in primary storage for task 3: vvpoolop dedup task 3
Page 226
Command Reference The following command runs a Storage Pool Summary report for all primary pool systems with files in c:\Vault184170841: vvpoolop summary location c:\Vault184170841 The following command runs a Storage Pool Summary report for both primary and secondary pool systems for all tasks: vvpoolop summaryall task * detailed
The following command checks for logical corruption in the last committed safeset for task 3:
vvpoolop ssiverone task 3 The following command checks for logical corruption in all safesets for pool systems with files in \\computer1: vvpoolop ssiverall location \\computer1 The following command checks for logical and physical corruption in suspect task pool systems, and enables suspect tasks that do not have data int egrity is sues: vvpoolop unsuspect task * The following command checks safeset 00000002 for task 4 for logical corruption without reading pool files: vvpoolop verifyidxone task 4 00000002
27. 16 vvpu rg e
The vvpurge command deletes log files or activity records that are older than a specified amount of time. When deleting log files, you can also specify a minimum number of each log file type (e.g., Backup log, Restore log) to keep. Log files are typically deleted automatically, as specified by Vault Settings. Activity record s are not deleted automatically and are saved in the vault database. Activity records list completion times, file sizes and success messages for backup, restore and migrate tasks. Syntax for Deleting Log Files vvpurge [numberOfFilesToKeep numberOfDays] Syntax for Deleting Activity Records vvpurge /activities /delete /age=n umber{h|d|y}
Page 227
Director 7.0 Operations Guide Parameters
Parameter [numberOfFilesToKeep numb erOfDays]
Description For deleting log files only. numberOfFilesToKeep specifies the minimum number of each type of log file to keep. numb erOfDays specifies the number of days old that a log file must be to be deleted. Each day represents a 24-hour period. For example, if numberOfDays=1, a log must be at least 24 hours old for the log to be deleted. If you do not include these parameters, the system deletes log files as specified by values on the Logs tab of the Vault Settings dialog box. For more information, see Scheduling a Log File Purge.
/age=number{h|d|y}
For deleting activity records only. Specifies the numb er of hours, days or years old that an activity record must be to be deleted. Include one of the following time units: h hours d days y years
Examples The following command deletes log files that are more than 48 hours old, while keeping at least three logs of each type: vvpurge 3 2 The following command deletes log files as specified by values on the Logs tab of the Vault Settings dialog box: vvpurge The following command deletes activity records that are more than one year old: vvpurge /activities /delete /age=1y The following command deletes activity records that are more than two days old: vvpurge /activities /delete /age=2d The following command deletes activity records that are more than four hours old: vvpurge /activities /delete /age=4h
Page 228
Command Reference
27. 17 vvrec all

Recalls an archived safeset. Syntax vvrecall [taskID] [catalog] [storagedays]
Page 229

Director Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Director Guide

Caricato da

Copyright:

Formati disponibili

EVault Software Director 7.

Welcome to Director 7.0

Welcome to Director 7.0

EVault Reporting System

Import Online Restore Online Backup

Primary Pool Data

Web or Windows CentralControl

Director Console (GUI)

Network Attached Storage

Director 7.0 Operations Guide

Wh ats New i n V ersion 7 .0 1 ?

Wh at's New i n V ersion 7 .0 ?

Addition al Reso u rces

Installing the Director

Installing the Director

Hardw are Req ui rements

Software R eq uirem ent s

32-bit an d 64 -bit S uppo rt

Director 7.0 Operations Guide

Def ault Storag e Policies

Inbo und and Outbou nd Port Requi rements

Installing the Director

Agent CentralControl 808

Vault Director GUI

2546 Agent 808

- Represents a dynamically assigned port.

Pe rmi ssio n R equi rem ents

The following table describes the permissions required by vault applications:

Director 7.0 Operations Guide

Ch angi ng th e Loc al S ec urit y Poli cy

Inst allin g the Vault and Directo r M an ag em ent Consol e

Installing the Director

Inst allin g the Di recto r Management Co nsole

Imp rovi ng Di re ctor Perform anc e

Autom atic ally Created Di recto ry Path s

Autom atic ally Created Servi ces

Silentl y Upg rading , P atc hing , and Rep ai ring a Vault

Director 7.0 Operations Guide

Upgrading the Director

Upgradin g V aults to Versio n 7. 0

Vault Man age r Works pac e Fil es

Licen se Ve rifi catio n

Director 7.0 Operations Guide

Upgradin g with th e V ault Ru nni ng

Upgradin g V aults for R eplic ation

Upgradin g St and alon e V ault s fo r R eplic ation

Upgradin g D ual Vaults fo r Repli catio n

Upgradin g V aults i n 1: 1 R eplic ation

Upgrading the Director

Upgradin g V aults i n N:1 Repli catio n

Manu ally Up gradin g Mic roso ft S QL S erv er E xp ress

Director 7.0 Operations Guide

Rec reati ng D elt a Fil es

Rep ai ring a V ault

Upgrading the Director

Inst allin g a Patch

Uninst allin g th e Di rector

Director 7.0 Operations Guide

Adding and Activating Licens es

Activ ating a Lic en se Onlin e

Adding and Activating Licenses

Req ue sting a Lic en se Activ ation Cod e

Ente ring a Lic en se Activ ation Cod e

Director 7.0 Operations Guide