Director LVR Guide PDF

EVault Software LVR for Director 6.
21 Operations Guide
May 2010 This manual describes how to install, configure, and manage EVault Software Logical Vault Replication for Director version 6.21.
EVault LVR Guide for Director 6.2
Contents
1 INTRO DUCTIO N............................................................................................................7
1 .1 Ab ou t LVR (Log ica l Va u lt Rep lica tion )............................................................................ 8
1.1.1 1.1.2
1 .2 1 .3 1 .4
GUI Icons for LVR........................................................................................... 9 Some Explanations on LVR............................................................................. 10
Ba cku p Destin a tion Scen a rios ..................................................................................... 11 Version 6 Up g ra des .................................................................................................. 13 Glossa ry ................................................................................................................. 14 1 :1 Overview........................................................................................................... 15
ONE TO ONE REPLICATIO N (1:1) ..............................................................................15

2 .1
2.1.1 2.1.2 2.1.3

2 .2
Configuration Parameters .............................................................................. 16 Failover Scenario ........................................................................................... 17 Secondary Pools and Detached Secondary...................................................... 18 Overview of Steps to set up 1:1 Vault Replication ........................................... 20 Overview of GUI Workflows......................................................................... 20 Licensin g for 1:1 Replication ........................................................................... 21 Remove a 1:1 License key ....................................................................... 22 Replication Status .......................................................................................... 23 Upgrading the 1:1 Vaults ................................................................................ 23 Configuration - Active and Passive Menus ....................................................... 24 Passive Vault Settings ..................................................................................... 25 Passive Vault drive configuration .......................................................... 26 Network Options.......................................................................................... 27 Schedule Replication ...................................................................................... 28 Failover ......................................................................................................... 29 Agents list of Vaults ...................................................................................... 30 Options Replication Logs ............................................................................ 32
In sta lla tion a n d Setu p ................................................................................................ 19
2.2.1 2.2.2 2.2.3 2.2.3.1 2.2.4 2.2.5

2 .3
Con fig u ra tion .......................................................................................................... 24
2.3.1 2.3.2 2.3.2.1 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7

2 .4
1 :1 Fa ilover ............................................................................................................. 33
2.4.1 Vault Replication Failover menu choice on the Passive Vault ......................... 33 2.4.1.1 View Replication Configuration Passive Vault ........................................ 33 2.4.2 Proceed to Failover ....................................................................................... 34 2.4.3 Confirm data may be lost............................................................................... 35
2 .5 Rep lica te Now ......................................................................................................... 36
2.5.1 2.5.2
2 .6
Replicate Now menu ..................................................................................... 36 Vault Settings - Replication tab ....................................................................... 37
Mon itor a n d Rep ortin g .............................................................................................. 38
2.6.1 Job Monitor for Replication............................................................................ 38 2.6.1.1 Replication Session Progress................................................................... 39 2.6.2 Replication Status Report............................................................................... 40
2 .7 Q&A on 1 :1 Va u lt Rep lica tion..................................................................................... 44
2.7.1 3
3 .1
Best Practices for 1:1..................................................................................... 49
MANY TO ONE REPLICATIO N (N:1) ..........................................................................50

N:1 Overview .......................................................................................................... 50
Preface
Page 2 of 96
3.1.1 3.1.2
3 .2
N:1 Failover Scenario..................................................................................... 53 N:1 Replication Commands, Options and Wizards.......................................... 53
In sta lla tion Overview Ba se Va u lt a n d Sa tellite ............................................................. 54
3.2.1 Base Vault Installation .................................................................................... 55 3.2.1.1 Upgrading the N:1 Vaults........................................................................ 55 3.2.2 N:1 License Summary .................................................................................... 56 3.2.2.1 Remove an N:1 License key .................................................................... 57
3 .3 Va u lt Settin g s for Ba se Va u lt ....................................................................................... 58
3.3.1 3.3.2 3.3.2.1 3.3.2.2 3.3.3 3.3.4 3.3.4.1

3 .4
Replication tab ............................................................................................... 58 Satellite Installation ........................................................................................ 59 Satellite Installation on XP Pro ................................................................ 61 Replacing a Satellite Vault........................................................................ 62 Satellite Configuration Vault Settings for Satellites ........................................ 63 Agent Connection ......................................................................................... 65 Two Network Scenario .......................................................................... 66 Vault Replication Menus ................................................................................. 67 Satellite Configuration Add a new Satellite Vault .......................................... 68 Satellite Configuration Select a Customer to use the Satellite ....................... 69 Satellite Configuration Network Options ..................................................... 71 Satellite Configuration Schedule .................................................................. 72 Satellite Configuration Safeset Management.................................................. 73 Satellite Configuration Advanced ................................................................. 74 Task Operating Modes ........................................................................... 76 EVault for DPM Appliance ...................................................................... 80
Va u lt Rep lica tion Con fig u ra tion .................................................................................. 67
3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.7.1 3.4.7.2

3 .5
Mon itor a n d Rep ortin g .............................................................................................. 81
3.5.1 Job Monitor and Logs .................................................................................... 81 3.5.1.1 Replication Session Progress................................................................... 82 3.5.2 Replication Status Report............................................................................... 83
3 .6 Q&A on N:1 Va u lt Rep lica tion .................................................................................... 89
3.6.1 3.6.2 4
Best Practices for N:1 .................................................................................... 91 Troubleshooting............................................................................................ 92
INDEX .........................................................................................................................93
Preface
Page 3 of 96
Figures
Figure - 1. - Failover Scenario ............................................................................................... 17 Figure - 2. - Installation Director Setup Type for 1:1 Replication ......................................... 19 Figure - 3. - 1:1 Licensing ..................................................................................................... 21 Figure - 4. - Remove a 1:1 License Key ................................................................................. 22 Figure - 5. - Replication Status after installation ..................................................................... 23 Figure - 6. - Vault Configuration Active menu..................................................................... 24 Figure - 7. - Vault Replication Configuration Passive Vault Settings ...................................... 25 Figure - 8. - Network Options OTW and Throttling .......................................................... 27 Figure - 9. - Schedule Replication .......................................................................................... 28 Figure - 10. - Failover Configuration ..................................................................................... 29 Figure - 11. - Agent addresses for Vaults............................................................................... 30 Figure - 12. - Vault Inbound/Outbound Port Configuration - Including Active/Passive Vaults.... 31 Figure - 13. - Replication Log Options................................................................................... 32 Figure - 14. - Vault Replication Passive menu ....................................................................... 33 Figure - 15. - Proceed to Failover ......................................................................................... 34 Figure - 16. - Proceed to Failover, with pending events .......................................................... 35 Figure - 17. - Replicate Now ................................................................................................ 36 Figure - 18. - Replication tab Replication master switch ...................................................... 37 Figure - 19. - Job Monitor for Replication.............................................................................. 38 Figure - 20. - Job Monitor Replication Session Progress ...................................................... 39 Figure - 21. - Replication Status Report Analysis Scope....................................................... 40 Figure - 22. - Replication Status Report Replication Comparison ......................................... 41 Figure - 23. - Replication Status Report Replication Lag ...................................................... 42 Figure - 24. - Agents connected to Satellite Vaults, which are connected to a Base Vault......... 51 Figure - 25. - Agents connected to a Base Vault when the Satellite is lost. .............................. 52 Figure - 26. - Installation Director Setup Type for N:1 Replication ...................................... 54 Figure - 27. - Vault Settings License Summary..................................................................... 56 Figure - 28. - Remove an N:1 License Key............................................................................. 57 Figure - 29. - Vault Settings Replication tab ........................................................................ 58 Figure - 30. - Installation Director Setup Type for Satellite.................................................. 59 Figure - 31. - Installation Registration Confirmed for Satellite.............................................. 60 Figure - 32. - Satellite Vaults Configuration ........................................................................... 61 Figure - 33. - Replication Menus and Satellite icons ................................................................ 63 Figure - 34. - Vault Replication Configuration menus are grayed out....................................... 63 Figure - 35. - Vault Settings on a Satellite .............................................................................. 64 Figure - 36. - Vault Settings Agent Connection ................................................................... 65 Figure - 37. - Base Vault Replication menus........................................................................... 67 Figure - 38. - Configuration screen Add a new Satellite Vault .............................................. 68 Figure - 39. - Satellite configuration Select Customer for Vault............................................ 69 Figure - 40. - Satellite configuration Network options......................................................... 71 Figure - 41. - Satellite configuration - Schedule ...................................................................... 72 Figure - 42. - Satellite configuration Safeset management .................................................... 73 Figure - 43. - Satellite configuration - Advanced..................................................................... 74 Figure - 44. - Operating Mode tab, Task Properties............................................................... 77 Figure - 45. - Cannot overwrite Operating Mode.................................................................. 78 Figure - 46. - Right Click for Operating Mode on Tasks ......................................................... 79
Preface
Page 4 of 96
Figure - 47. - Right Click for Operating Mode on Customers, Locations, and Computers........ 79 Figure - 48. - Job Monitor Show Replication Activity........................................................... 81 Figure - 49. - Job Monitor Replication Session Progress ...................................................... 82 Figure - 50. - Cant run Replication Status Report on a Satellite ............................................. 83 Figure - 51. - Replication Status Report Analysis Scope....................................................... 84 Figure - 52. - Replication Status Report Replication Comparison ......................................... 85 Figure - 53. - Replication Status Report Replication Lag ...................................................... 87
Preface
Page 5 of 96
Revision: This manual is updated for Version 6.2 Software Version: 6.21 (May, 2010)
Copyright 1997-2010 i365, A Seagate Company. i365, A Seagate Company, makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, i365 reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of i365 to notify any person of such revision of changes. All companies, names and data used in examples herein are fictitious unless otherwise 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 otherwise without prior written permission of: i365, A Seagate Company c/o Corporation Trust Center 1209 Orange Street Wilmington, New Castle Delaware 19801
www.i365.com
EVault, EVault Software, EVault SaaS, and EVault DeltaPro, are registered trademarks of i365, A Seagate Company. All other products or company names mentioned in this document are trademarks or registered trademarks of their respective owners. Acknowledgements: Two 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 added encryption option of 128bit AES (Advanced Encryption Standard). Advanced Encryption Standard algorithm (named Rijndael, pronounced Rain Doll) was 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 Federal Information Processing Standard (FIPS). The EVault Software Agent and EVault Software Director applications also have the added security feature of an over the wire (OTW) encryption method.
Preface
Page 6 of 96
Introduction
The Director Vault is a system that provides Backup and Restore services to a number of remote computer systems (with Agents). It is an online data Vault, which may reside locally (LAN) or across a WAN (Internet). The Director itself is the application that powers the electronic Vault. It stores and catalogs the Backup files and it monitors the Backup process. The Director performs two main functions: First, the Director controls and maintains all of the information stored in the Vault. Second, the Director Management Console (the GUI) controls which computers and users have access to and from the Vault for storage and retrieval purposes.
The Director has an Operations Guide and an on-line help that are used by the operators/users responsible for installing, configuring and maintaining the Vault side of the system. It covers: Installation of the Director products - the Management Console and the Vault component. Operation of the Director GUI. Running of different Wizards. These correspond to the pull-down menu selections in the Director GUI. LVR (Logical Vault Replication) is a separate, licensed product. This LVR Operations Guide is supplemental to the Director Operations Guide, and assumes the user knows how to use the Director GUI. New Replication Features for 6.2x: - Replication logs now show the total time taken, and the speed (KB/sec) of the data transfer. - Late Replication Report shows (in the log file) any task not replicated after a chosen number of days. You can also choose to receive an email (if configured) with this information. - Replication Status (Progress) shows the size of the data completed (as a %), for the number of Customers, Locations, Computers, Tasks and Safesets. - You can choose whether or not to replicate a single task. - Pause Replication: You can temporarily pause Replication on a per task, or per customer basis. - A BAV can give Replication control to a Satellite. The Satellite can then turn replication on/off for tasks, computers, accounts and customers.
Introduction
Page 7 of 96
1.1
About LVR (Logical Vault Replication)
Previous versions of Director only allowed Agents to backup to one Vault at a time. Agents could backup to that Vault, and Restore from it. Of course you could have a second (separate) Vault, but it would have its own Agents. Neither Vault would know about the other. If you wanted to make sure that your Vault data itself was protected, you would have to backup the entire physical Vault. With Director 6, one-to-one Replication allows customer data on a main (Active) Vault to be copied to a secondary (Passive) Vault. If the Base Vault fails you are still protected with the secondary Vault. Alternatively, an organization might have many offices and Agents (computers) spread out across the country. They could all send their backups to a main, centralized Vault, across the Internet. With Director 6, and many to one Replication (N:1), you can have local Satellite Vaults (SVs) that local Agents can send their backups to, at LAN speeds. Then, later the Satellite Vaults would send the data to one main, centralized Base Vault. The data is still kept locally, for local restores. But it is also kept on the Base Vault, usually for a longer time, and can also be restored from there. Local users can independently backup and restore to and from the local Satellite Vault. If the local Vault fails, the users can still backup and restore to the Base Vault, over the communication link (Internet). Note: The Director installation kit contains all the types of Vault configurations Single Vault, QuickShip Vault and Satellite Vault. If you install a Vault as a Satellite Vault (see section 3.2) it cannot be reverted back to a single Vault without uninstalling and reinstalling. If you have a 1:1 Vault (Active /Passive), or as a Base Vault, you can convert it back to a single Vault, by removing the replication license. The Vaults data will still be intact, and Agents can still backup and restore to it. You could then add a replication license to make it either a 1:1 Vault, or an N:1 Base Vault. This version of the Vault works best in conjunction with Agent version 6, to support LVR. Replication works with older Agent versions, but failover is not automatic. With Director 6, 1:1 and N:1 Vaults operate totally independently from each other. You either have one or the other. They cannot be mixed. This manual has a chapter on 1:1 Replication, and another on N:1 Replication. You should only be referencing the one that applies to your installation.
Introduction
Page 8 of 96
1.1.1
GUI Icons for LVR
In the Director Console, you will see different Vault icons for Base and Satellite Vaults, and Active and Passive Vaults.
Note: In this diagram for MyWorkspace, the names shown are just descriptive, for this Operations Guide. Your Vault names should be meaningful to you.
Introduction
Page 9 of 96
1.1.2
Some Explanations on LVR
This section concerns what to watch out for, when working with LVR, either 1:1 or N:1 Vaults. Some of these points may be mentioned in the Release Notes as well. Safeset Backup Date: Changing the backup date of a safeset can cause Replication to fail. If you change the date of a safeset, and make it "earlier" than the next one, Replication (from the Base or Active vault) will fail. For example if you have safeset #1 for Monday and safeset #2 for Tuesday, and you switch Tuesdays date to before Monday, replication will fail. You must correct the dates to get Replication to start. Replication is Online Storage Only: In a 1:1 Replication scenario, you may see that the archive storage location on the Passive vault requires manual setup for each task, and is not propagated from the Passive vault configuration. Replication deals with Online storage only. Settings and data stored in Archives, and secondary pools are not part of the replication schema. Replication can Cleanup after a task fails Replication: If a Task fails to get replicated, there may be orphaned files left behind in the tasks storage location. These files will be automatically deleted. Replication will call (spawn) the VVPoolOp cleanup command to perform the function. Note that this is not part of the user interface, but can be run directly from the CLI. But, the user will see a log file produced from VVPoolOp. This will show the file list of orphaned files deleted. This cleanup will return any unused space back to the Vault.
Introduction
Page 10 of 96
1.2
Backup Destination Scenarios
The primary intention of Vault replication is to ensure that valuable backup data is protected. Also it ensures that a Vault is available for backups and restores, or minimally, for restores. One to one Replication copies backups only from the Active Vault to the Passive Vault, which is preferably in a different location. Many to one (N:1) Replication collects backup data at a Satellite Vault, and copies some or all of those backups to a larger Base Vault, preferably in a different location. In both of these cases if one of the Vaults (Satellite or Active) goes down, or if communication is lost, the other (the Base Vault or Passive Vault) can take over. When the broken one is fixed, the Vaults are synchronized, and normal backups can occur. When an Agent first connects to a Vault, information about that Vault and the other one(s), in either a 1:1 or N:1 configuration is passed back to the Agent. If the Agent therefore cannot access its preferred Vault, it will attempt to contact and use the other one. After the Vaults are fixed and synchronized, on the next backup session, the Agent can be switched back (by the Administrator) to its preferred Vault. A preferred Vault is the one that the Agent typically uses. In a 1:1 scenario, it is us ually the Active Vault. In an N:1 scenario, it is usually the Satellite Vault. In situations like these, backups appear normal, the Agent has automatically switched around the situation to continue backups. The log files will have entries about the failures and attempts and re-connections. There is a timeout that can be set in the Agent parameters to specify how long an Agent will attempt to reconnect if it cannot reach a Vault. So if both Vaults are unavailable (down, or not accepting backups) then the Agent will continue attempting to reconnect, until that time expires. This also will be logged. After that time, the scheduled backup will not occur. But if at least one of the connections is re-established before the next scheduled time, the backup will start. The previous backup will have been skipped over, though.
Introduction
Page 11 of 96
The following chart shows the possible conditions and outcomes for these scenarios: Vault1/Vault2 are different Vaults. They could be either Base Vault or Satellite (in N-1) or Active or Passive (in 1-1). Condition # 1 2 3 4 5 Vault1 Status Accept Accept Fail Fail Fail Vault2 Status Accept Reject Accept Reject Fail Agent Behavior Pick and Proceed Proceed Proceed Retry Retry
For a Satellite/Base Vault scenario with Vault1/Vault2: In a normal condition (1) the Satellite is running, and can communicate with the Base Vault. An Agent can backup to the Satellite and that can replicate to the Base Vault. If the Base Vault goes down, or loses communication with the Satellite (2), the Agent will continue backing up to the Satellite, as normal. The Satellite will keep trying to connect to the Base Vault, to continue replication. If the Satellite goes down, or cant communicate (3), the Administrator can switch the Replication mode, so that the Agent can switch over to the Base Vault for backups. The Agent will continue to check for the Satellite to come back. When it does, it will switch back to the Satellite. The Satellite and Base Vault will synchronize the backup data for the time when the Satellite was down. If the Satellite fails and the Base Vault does not accept Agent backups (4), or it otherwise fails (5), the Agent will keep retrying, and backups will not occur until the Satellite or Base Vault comes back (1, 2, or 3). Exception: Inside the EVault for DPM product (see section 3.4.7.2 of this Guide) is a DPM plug-in. This plug-in is specifically designed to always bypass the Satellite and go directly to the BAV. There is no Replication in this case. This functionality cannot be changed from the Satellite or the Base Vault.
Introduction
Page 12 of 96
1.3
Notes:
Version 6 Upgrades
1. The Director installation kit contains all the types of Vault configurations Single Vault, QuickShip Vault, and Satellite Vault. You first install a Vault that you intend to use as an N:1 Base Vault (or a 1:1 Active/Passive Vault) as a standalone Vault (the "Single Vault" choice). Then you can use the proper licensing to make it a Base Vault or an Active or Passive Vault. Note that Satellite Vaults get their licensing from the Base Vault. 2. During an upgrade, you may be prompted if there are any files open or processes running. The upgrade cannot continue if files are open, or services are running that need to be replaced. A message will instruct you to stop any running processes or applications. Then you can either try again, or terminate the installation. 3. For N:1 Replication, the Base Vault must be at a higher version before the Satellite Vaults can be upgraded to 6.21. A 6.21 BAV will still support 6.04 Satellites. But you cannot have a 6.04 BAV with 6.21 Satellites. 4. For 1:1 Replication, you must upgrade the Passive Vault first, from a 6.04 version. The Active vault will still work at the 6.04 version until it can be upgraded to 6.2. Note that Failover will not function correctly until you have upgraded the Active Vault to the same version as the Passive Vault. 5. If you install a Vault as a Satellite Vault, it cannot be reverted back to a single Vault without uninstalling and reinstalling. 6. If you have a Vault as a 1:1 replication (active/passive), or as a Base Vault, you can convert it back to a standalone Vault by removing the replication license. The Vaults data will still be intact, and Agents can still back up and restore to it. You can then add a replication license to make it either a 1:1 Vault, or an N:1 Vault. See section 8.2.4 in the Director Operations Guide for more information on Upgrades.
Introduction
Page 13 of 96
1.4
Glossary
Base Vault (for N:1 Replication). The Base Vault is the destination of multiple Satellite Vault replications. It accepts new computers, tasks (metadata) and safesets (data) to be replicated to it. It will replicate each customer location, accounts and users (metadata) to the Satellite. Failover - In 1:1 Replication, if one Vault cannot operate, another one can take over, so that backups and restores are not adversely affected. Heartbeat - The Base Vault listens for confirmation from the Satellite that it is still alive and connected. The heartbeat contains replication events and information about the health of a Satellite Vault. Many-to-one This is an N:1 Replication, from one or more Satellite Vaults, to a Base Vault. It works by allowing you to have Satellite vaults at each of your companys remote locations, and automatically replicating their backup data to a designated vault in your Disaster Recovery hot site. Metadata Metadata (data about data, and information about Customers, Locations, Accounts, Users, Computers and Tasks) describes how, when, and by whom a particular set of data was collected, and how the data was formatted. Replication - (in 1:1 or N:1) The process of copying safeset (backup) data, and metadata to another Vault, for safety and security. Replication can happen as needed, or on a schedule. SV (Satellite Vault). A Remote Vault, usually at the customer location. It keeps local backups, and replicates to the Base Vault. A Satellite Vault will support only one Customer name. Synchronize Two Vaults must have all the data that should be replicated, and all the current metadata, to be considered as synchronized. One to One This is 1:1 Replication, from an Active to a Passive Vault. Failovers from the primary to the alternate Vault ensure uninterrupted backups and data availability.
Introduction
Page 14 of 96
One to One Replication (1:1)
This section discusses 1:1 Installation and Setup, Configuration, Failover, Replication, and Monitoring. There are also Questions and Answers on 1:1, and some Best Practices.
2.1
1:1 Overview
One-to-One Vault Replication is intended as a means for Vault administrators to be able to automatically and continually duplicate whatever backups are on their main (Active) Vault, to another (Passive) Vault. If the Active Vault fails, the Passive one can take over, and become the Active one. This protects the valuable Vault data in case of a disaster. Replication deals with Online storage only. Settings and data stored in Archives and secondary pools are not part of the replication schema. Note that only online safesets that are not expired are replicated. Archive, Secondary and safesets with expired retentions are not replicated. The primary Vault is referred to as the Active Vault. That is, it accepts backups and facilitates restores. The secondary Vault is referred to as the Passive Vault, and is not normally seen by Agents for backups. Most recent Agents (6.x) do see both Vaults. The safesets on the Active Vault can either be copied to the Passive Vault as the backup completes successfully, and/or they can be scheduled to replicate at a certain time. If the Active Vault fails, the Vault administrator can choose to switch over to the Passive Vault, making it Active, that is, available for backups and restores. From the Agents point of view, nothing has changed. A Vault is still there, and it is accepting backups. The Director installation (fresh install or upgrade) contains all the programs necessary for the Vault Replication Service. The service is installed, along with Director, but replication is not enabled until an appropriate license is inserted. The Active and Passive Vaults must have at least comparable pool storage sizes. Backups on the Active Vault will use the same size on the Passive Vault. Note that, older pools do not support replication. Replication only operates on version 5 (and up) pools. You must upgrade your pools if you want them to be protected by replication. From the Director Console, view a tasks properties to see the pool version. Licensing 1:1: You first configure and license the Vault that will be the Active Vault. In this example there is a QuickRecovery250 Vault license, then other licenses such as MAPI, Agents, and ESR. Your system may be different. Following this is the 1:1 (UltraRecovery) License, which allows 1:1 Replication.
Once you have configured this Active Vault, you then use the same license keys on the Passive Vault. When the Passive Vault starts, the Active vault will now communicate with it.
One to One Replication
Page 15 of 96
2.1.1
Configuration Parameters Host Name/IP address, ports and credentials to use on either Vault. Using the same or different authentication for the two Vaults. Enabling and using Over The Wire (OTW) encryption. Bandwidth throttling. Setting a schedule for Replication.
Some of the parameters that the administrator can set include: -
The replication is logical, not physical. The physical data structure on the disk is not duplicated exactly, only the contents of the backups and their logical association are copied to the replicated Vault. So, the logical organization/structure of Customer, Location, Computer, Task and Safeset is not changed. Also, something like a Vault optimization on the Active Vault will not trigger a replication to the Passive Vault. Backup data (and its status) is kept on the target (Passive) Vault the same as it is on the main (Active) Vault. So, if a task is disabled on the Base Vault, that status is also propagated to the target Vault, but the safeset information and the data for the task will still be replicated. If a safeset is deleted, it is also deleted on the Passive Vault.
Page 16 of 96
2.1.2
Failover Scenario
Note: Care should be taken when using the Failover option. If the two Vaults are out of synch, data loss will result (because some data may have not been replicated yet). In this example, after an installation, Vault X was made Active, and Vault Z becomes Passive. Vault X is in control, and replicates to Vault Z. (Step 1). All Customers on Vault X are replicated to Vault Z.
1
Active
Vault X
Vault Z 2
Passive
Passive
Vault X 3
Vault Z
Active
Figure - 1. - Failover Scenario
Assume in this scenario that there is a failure on the Active Vault. A Vault administrator initiates a failover (Step 2), and makes Vault Z the Active one. If Vault X experiences a failure, there will be no replication from X to Z, so Vault Z will accept Agent backups, and supply restores as normal. Newer Agents (6.x) already have the addresses for both Vaults. Older Agents, however, are only aware of the Active Vault that they registered to. Later, if Vault X is returned on line, it will be Passive, and the Vault administrator can start replication to Vault X, to synchronize the Vaults. (Step 3). Also, after the replication, if the Vault administrator wants to return Vault X to being Active, and Vault Z Passive, the administrator can initiate a failover to switch them back. Note: If Vault X is rebuilt after a bare metal DR (Disaster Recovery), you may want it to be put/configured back as the Active Vault. As long as the rebuilt Vault has the same configuration (IP/Name, Replication keys, and is licensed) when it is brought online, Replication will start automatically.
Page 17 of 96
2.1.3
Secondary Pools and Detached Secondary
This section discusses the lifecycle of a long-term safeset, in a standalone Vault, and in an Active/Passive Replication. Standalone Vault: With Secondary Pools (and no Replication involved), the lifecycle of a long-term safeset is slightly different. After a backup, the safeset is in the Primary Pool, and its status in Director shows as Primary. If the user decides to migrate the safeset to the Secondary Pool (only one pool at a time can be Active - i.e.: writable), it is still online, but its status in the Director shows as Secondary. If the Active secondary pool is superseded by the creation (by the user) of a new secondary pool, the safeset is now in an inactive (read-only) secondary pool. It is still online, with a Secondary status. If the secondary pool is detached (by the user), the safeset becomes offline, and its status is shown as Detached Secondary.
As long as the safeset is online (as shown in the CentralControl), it can be restored. Note that safesets can only be moved (migrated) from the primary pool to the Active secondary pool. Migrations from secondary to primary, or secondary to secondary are not allowed. You can read or export a safeset directly from a secondary pool, without the participation of the associated primary Vault that created the secondary pool. Active/Passive Replication: With Active to Passive Replication of online safesets (in primary storage), the safeset (the data and its reference pointers) are copied to the Passive vault. After a failover, the safesets are immediately ready for backups, restores or exports. No Secondary storage data is copied during replication. And, if the data is offline, or is detached secondary on the Active vault, no reference pointers are copied during Replication. But, for online Secondary storage safesets on the Active Vault, only the pointers are copied during replication, and the secondary storage on the Passive vault will now show Detached. This is to be ready for when the actual secondary storage (for example, disk or USB device) is transported to the Passive vault, after a failover. You then Attach the secondary storage, and the pointers to the secondary storage data are logically re-constructed, so that you can now access the safesets on the secondary storage. So now, after the failover and the Attach, the safesets in secondary storage are ready for backups, restores or exports.
Page 18 of 96
2.2
Installation and Setup
The Director installation kit contains all the types of Vault configurations Single Vault, QuickShip Vault and Satellite Vault. See the Director Operations Guide for more information on installation. Note: If you are upgrading your Active/Passive Vaults, you must upgrade the Passive Vault first.
Figure - 2. - Installation Director Setup Type for 1:1 Replication
Both 1:1 Replication Va ults (Active and Passive) are each installed as a Single Vault Configuration type. Either during or after the installations, you apply a 1:1 license to make each of them a Replication Vault. That is, one 1:1 license will work on both the Active and Passive Vault. Once you have applied the licenses for replication, you will see an additional tab called Vault Replication in the Director GUIs. After you decide which Vault will be the Active Vault, you must configure it accordingly. You do not configure the Passive Vault. It will be turned Passive by the Active Vault, after they first communicate. Note: The Passive Vault must be an empty Vault. Replication will refuse to register a Passive Vault that contains existing data.
Page 19 of 96
2.2.1
Overview of Steps to set up 1:1 Vault Replication
You start by setting up two Vaults, with one going to be the Active one, and the other the Passive one. Install the Single Vault configuration Vault software on both Vaults. This is found in the Director: Setup Type screen during the Director installation. Use the appropriate licenses for Vaults and replication. On the intended Active Vault ONLY, do the following: 1. Configure the address, ports and credentials for the Passive Vault. 2. Configure authentication settings (if applicable). 3. Schedule Replication (Synchronization). 4. Configure failover settings (enter the Active Vault address and ports). 5. Click OK, which will propagate the information to the Passive Vault. These steps are described in more detail in the rest of this section. 2.2.2 Overview of GUI Workflows Initially both Vaults should show identical menus. After the first replication occurs between the Vaults and the individual roles are defined, the menus for the Active and Passive Vaults will show different options grayed out, depending on which role it is. For example, the Passive Vault would show the Failover menu option. This section describes the following high-level workflows in the Director GUI. Configuration Performed typically once when the user wants to start using the Replication option. The configuration process allows the user to configure both the Active and Passive Vaults in a single pass. Pre-populated defaults should work for the majority of users. Advanced configuration options are available for complex environments. Failover Performed when the preferred, Active Vault is not available for Agent backups. Failover changes the role of the Passive Vault to Active. Any data that is not replicated will be lost. Replicate now/Disable Replication The user will have the ability to manually override replication policy at any time with two options: o Replicate now allowing the user to start synchronization of both Vaults at any time. o Disable Replication This master switch option is available on both Active and Passive Vaults and allows the user to remove either of the systems from replication process. This option stops any currently running replication as well. Monitoring Vault Administrators can regularly monitor the status of the replication process with the help of the Directors Job Monitor. Reporting Vault Administrators can regularly generate reports (at various levels of detail) to determine if the two Vaults are out of synch.
These are discussed in more detail following this section.

One to One Replication Page 20 of 96
2.2.3
Licensing for 1:1 Replication
When you license your Vault for 1:1 replication, it will show as UltraRecovery. See the Director Operations Guide for more information on licensing. When you are adding and activating license keys for this configuration, you will see a license for a standalone Vault (for example QuickRecovery 1000), plus a license for the 1:1 Replication (UltraRecovery).
But, in the License Summary it shows as a License Type of Replication One to One.
Figure - 3. - 1:1 Licensing
After your license is activated, if you close and re-open Vault Settings, you will see a new Replication tab there.
Page 21 of 96
2.2.3.1 Remove a 1:1 License key If you attempt to remove an LVR license key, you will see a warning message:
Figure - 4. - Remove a 1:1 License Key
After you click Yes, you will be prompted with a message asking you if you want to activate to remove the license. Just as the license needed to be activated to start using it, it also needs to be activated (as in de-activated) to stop using it. The Vault needs to communicate with the License Activation Server. This can be either online or manual activation.
Page 22 of 96
2.2.4
Replication Status
After you have installed and licensed two Vaults, you will make one of them Active and one Passive. You can see the status of Replication in each Vault, under Vault Maintenance -> Vault Settings > Replication tab.
Figure - 5. - Replication Status after installation
The Replication Status of this Vault initially shows as Unconfigured 1:1. Later, after configuration, the Status will show as Active or Passive. See the section on Replication Master Switch for an example. 2.2.5 Upgrading the 1:1 Vaults
In preparation for a Director 6.04 to 6.20 upgrade, you must activate the licenses on both the Active and Passive Vaults. Even if the licenses were previously activated, it is important to be sure the licenses are current and valid. Upgrade Steps: 1. Stop the Replication, Listener and Admin services on both Active and Passive Vaults. 2. Upgrade the Passive Vault first to 6.20. 3. Upgrade the Active Vault to 6.20. 4. Start the services.
Page 23 of 96
2.3
Configuration
This section discusses the Active and Passive menus, Passive Vault settings, Network options, Scheduled Replication, Failovers, and Replication options. 2.3.1 Configuration - Active and Passive Menus In your Director, when you add a New Vault Connection for Replication, the icons for an Active and Passive Vault are different.
Figure - 6. - Vault Configuration Active menu
Configuration is typically performed when the user wants to start using the replication option. The configuration process allows the user to configure the Active Vault and its Passive Vault in a single pass. The default settings should work for the majority of users. If this Vault is the Active Vault, when you select it you will see a choice of: Configuration, Replication Status Report, and Replicate Now.
Page 24 of 96
2.3.2
Passive Vault Settings
From the intended Active Vault, you define how the intended Active Vault will connect to the intended Passive Vault. You should never configure the Passive Vault. It will be turned into a Passive Vault when an Active Vault talks to it the first time.
Figure - 7. - Vault Replication Configuration Passive Vault Settings
The Passive Vault address is typically the IP address. The command and data ports can be the same as the ones on the Active Vault, or they can be different. This is up to the Vault administration security policy. The username and password are the credentials to access the Passive Vault, during replication. These credentials must be valid Windows login accounts on the Passive Vault, much like the accounts you use to access the Vault using the Director console. This is the minimum required information to start the replication. Then it will store the replication configuration and start to replicate, using default settings for the rest of the parameters.
Page 25 of 96
2.3.2.1 Passive Vault drive configuration The Storage Groups on the Passive Vault must be at least the same size (or larger) than on the Active Vault. The actual Storage Locations (with drive letters), do not have to match, as each vault takes care of its own space.
If the Groups on the two Vaults are not the same (missing or unavailable), you will get errors in the logs during the replication. For example:
REPL-E-0003 Sent object tree does not have parent on destination vault, will start another session with parent object REPL-E-0003 Failed to process replication event: 'Unknown token type: token '', type 0'
Page 26 of 96
2.3.3
Network Options
In a more complex scenario, you can configure more details. These are shown in the following screen with defaults selected.
Figure - 8. - Network Options OTW and Throttling
You can turn Over The Wire (OTW) encryption for the data transfer channel On or Off. This uses a 128-bit strong AES encryption. This is particularly important if you are sending the data to the Passive Vault across the Internet. OTW does not require the user to input a password. Encryption and decryption are done automatically. For other communications Replication uses an industry standard SSL. All information on the command channel(s) is encrypted all the time using SSL. For Bandwidth Throttling, you can choose to use all available bandwidth to the Passive Vault, or limit (throttle) it to a certain value, or by time of day. Using all the bandwidth is the fastest way to replicate, but if other communication is Active at the same time, it will be impaired by the replication. You can make the replication only use a certain amount at certain times, thereby allowing other users to co-exist with replication during the day, for example.
Page 27 of 96
2.3.4
Schedule Replication
Figure - 9. - Schedule Replication
You must always have at least one scheduled weekly replication. You can optionally choose to also Replicate as soon as possible after changes are made on the Active vault. So, as soon as a backup is successfully completed, it will be replicated to the Passive Vault. If you choose Replicate on a defined schedule only, it means that you are deciding when all replication will take place. There will be no immediate replication after changes are made. The Replicate on a defined schedule ensures a full replication, at least once a week. You can optionally schedule replications more than once a week, depending on your frequency, and volume of backups and other business needs. A scheduled replication is necessary to ensure that all objects on both vaults are synchronized. You can choose to have the defined scheduled replication(s) take place at a certain time. You might use this if you wanted, for example, to do all your replication at night, when other users do not need the bandwidth.
Page 28 of 96
2.3.5
Failover
Figure - 10. - Failover Configuration
This dialog box collects the information on how (in case of failure) the Passive Vault can connect to the Active Vault. By default, the host name of the Active Vault is used as an address for the Passive Vault to connect to the Active Vault on Failover. And the same credentials can be used for both directions, if they are the same. A failover is performed when the preferred Active Vault is not available for Agent backups. Failover changes the role of the Passive Vault to Active. In case of a DR (Disaster Recovery), the Vault administrator would switch the Passive Vault to an Active one so that normal backups can continue. This is done from the console, from Vault Replication -> Failover, and you must confirm the change with YES.
Page 29 of 96
2.3.6
Agents list of Vaults
Figure - 11. - Agent addresses for Vaults
Under Vault Maintenance -> Vault Settings, Agent Connection provides the name for an Agent (version 6.x or greater) to use to connect to this Vault. The Vault sends this data back to the Agent the first time (after replication is set) that the Agent does a backup to this Vault. The Agent will request this information before each backup. This way it can be updated on the Vault, and the Agent can update its table. This list is the default addresses of Vaults (host name or IP) that the Agent will receive as possible backup/restore options.
Page 30 of 96
Agent 1 CentralControl 808
Active Vault
2546 Agent N 808

Cmd Port
809
Data Port
Director GUI
Cmd Port
Data Port
2546
809
Passive Vault
Figure - 12. - Vault Inbound/Outbound Port Configuration - Including Active/Passive Vaults
Note: TCP ports 2547 and 12547 are used for Cmd and Data for 1:1 (Active/Passive), and for N:1 Replication (for all Satellites to the Base Vault). A 6.x Agent will have the list of the two Vault connections (two different IP addresses). It will attempt to backup to one or the other, depending on which one is Active. The Passive Vault can only supply restores, it will not accept backups. If the Active/Passive roles are switched, the Agent will try both Vaults and succeed to the one that is accepting backups (that is, the currently Active one). In this diagram, the outbound ports, that do not show a port number, are assigned dynamically by the system. The inbound ones are pre-defined by the administrator (usually defaulted). The Command and Data ports are assigned in Vault Settings. Note that the direction of the Command and Data ports is from Active to Passive Vaults. If the Vaults switch their Active/Passive roles, then the ports direction will change also, to still be from the new Active to the new Passive. If you change the command and data channel ports on the Passive Vault, the Replication Service should be restarted to accept the changes. The service has to be restarted on both ends on port changes (on 1:1 and N:1 Vaults). In addition, the Satellite Vaults would have to be re-registered if the command port is changed.
Page 31 of 96
2.3.7
Options Replication Logs
Figure - 13. - Replication Log Options
By default, the Replication Logs option is initially not visible in the Director GUI. Under View -> Options -> Logs you can turn the Show Replication Logs function on or off. The Replication Logs will show up in the left pane, along with Spawn and License logs.
Page 32 of 96
2.4
1:1 Failover
If the Active Vault does not work (it has crashed, for example), and cannot be used, you can switch the Passive Vault over to being the Active one: 1. The Passive Vault is still running, but is only serving restores. It does not accept backups. Agent backups will fail, as they cannot find a Vault. 2. On the console, from Vault Replication -> Failover, confirm the change with YES. 3. The Listener service is running, so it will now accept backups. Note: At this stage there is only the one Vault running, but no Replication is taking place, as there is now no Passive Vault. After you repair the crashed Vault that used to be the Active one, you must synchronize the two Vaults once again by running replication from the now Active Vault to the now Passive Vault. You should also run Replication Status Reports to detect any out-of-sync issues. You can then either leave the current (new roles) as is, or, after Synchronization, you can switch them back to their original Active/Passive configuration. To switch them bac k, you must be on the console of the (previously crashed and now) Passive Vault. From Vault Replication -> Failover, confirm the change with YES. 2.4.1 Vault Replication Failover menu choice on the Passive Vault
Under Vault Replication, you will see a choice of: Failover, Replication Status Report and View Replication Config.
Figure - 14. - Vault Replication Passive menu
If this Vault is the Passive Vault, you will be able to do a Failover. It is highly recommended that you run Replication Status Reports (if both Vaults are available) before proceeding with the Failover. After completion of the initial configuration, and when no replication is running at the moment the user needs to simply confirm the process. 2.4.1.1 View Replication Configuration Passive Vault The configuration tabs are the same as before (on the Active Vault), except they are all grayed out, and cannot be changed here. See Section 2.3.2 to set these connectivity items.
Page 33 of 96
2.4.2
Proceed to Failover
Figure - 15. - Proceed to Failover
Here, you have decided to failover the Passive Vault to become the Active one. The system finds that there are no processes running which could interfere with the switch. The previous Passive Vault now becomes the Active one, and the previous Active one becomes the new Passive one. In this case, the Active and Passive systems are synchronized, which means the same data in the same structure. If they were not, the confirm message would be different. If the previous Passive Vault had any data deleted, for example, that change (which is now in the new Active Vault), would be replicated to the new Passive Vault. Typing YES and clicking Proceed to confirm this, ensures that you are aware of what is happening.
Page 34 of 96
2.4.3
Confirm data may be lost
Figure - 16. - Proceed to Failover, with pending events
In the previous screen, there were no outstanding events or processes that might interfere with the failover. Both Vaults were functioning, and you could select the time for a graceful failover. Note that the assumption here is that both Vaults are synchronized, which you can always determine by running Replication Status Reports. But, if the Active Vault fails suddenly, you do not have a chance to properly wait for replication to complete. So, if there are objects with pending or running states, you may lose data in the failover, if some backups have not been replicated yet. The reason for that is that backup data is not simultaneously replicated from the Agent to both Vaults, but rather it first goes to the Base Vault, and then gets replicated to the Passive Vault. This may take some time with a large backup. If the Active Vault crashes during this time then that data will not have been successfully replicated. Typing I AGREE here, and clicking Force, in this case ensures that you are fully aware of what may happen with your data. That is, some of the data that is not replicated will be lost. Replication Status Report is described in the next section (Monitoring and Reporting).
Page 35 of 96
2.5
Replicate Now
This is a simple menu option that will trigger a replication event that will compare the two Vaults as soon as possible. Note: Just submitting a replication event does not necessarily mean immediate execution. If there is another replication running, the event will not be processed before the running replication is complete. 2.5.1 Replicate Now menu
Figure - 17. - Replicate Now
You can click the Replicate Now menu options. These options are visible (not grayed out) only on the Active Vault. This function can also be run from the command line interface (CLI). For example:
REPLVAULT.EXE SYNCH VAULT (where VAULT is the name of a vault).

See the CLI section of the Director Operations Guide for more information on Replvault.
Page 36 of 96
2.5.2
Vault Settings - Replication tab
Note: This Replication tab will only appear after you have configured a Replication license.
Figure - 18. - Replication tab Replication master switch
Enable Replication services on <Vault> is the master switch that can turn the replication on or off, on the Vault (Passive or Active) that you are on. By un-checking the Enable replication services on <Vault> and clicking the OK button, you stop any replication processes to or from the Vault. Any replication activity will be cancelled immediately. The Replication Service can also be stopped from the Job Monitor, which will implicitly uncheck this box as well. You must re-enable it again, from here. The two communication ports, Command Channel and Data Channel, have default values, but the Vault administrator can change these, depending on the system needs and requirements. Note : If the Vault administrator changes those numbers, they need to also change them in the replication configuration from the ACTIVE Vault. The preferred protocol for the data channel is shown. This cannot be changed. Replication Status of the <Vault name> shows whether this Vault is the Active or Passive Vault in 1:1 replication.
Page 37 of 96
2.6
Monitor and Reporting
This section describes how to use the Job Monitor during Replication, to show the session progress. You can also get a Replication Status Report. 2.6.1 Job Monitor for Replication If you click the Show Replication activity box in the View Options area of Job Monitor, you can see the Replication jobs that have run, or are running.
Figure - 19. - Job Monitor for Replication
The types of activity that will be visible on the Active Vault include the replication service itself, replicating, completed and pending replication sessions. You can also see the Replication activity logs from here the service log and the individual session logs. Note : After a Replication, the log file will show Total data transferred and Data transfer speed. The Stop button will not stop the Replication Service from running but will turn off (disable) the master replication switch. To re-enable the service you must enable the Replication Master Switch (in Vault Settings -> Replication).
Page 38 of 96
2.6.1.1 Replication Session Progress When a Replication is running, you can monitor its progress from the Job Monitor, with the Replication Job selected (highlighted) and then selecting the Progress button. This will bring up the Replication Session Progress screen. Note: You can find similar information in the Replication Logs.
Figure - 20. - Job Monitor Replication Session Progress
The following Display only fields are shown. Click OK when finished. Session: A unique, internal GUID for this Replication. Session Start Time: When the Replication actually started (scheduled or manually). Total Objects to be Replicated: What should be Replicated. Objects Replicated: What was actually Replicated. If different from above, check the log file. Traffic: Number of bytes transferred during the Replication. Status: Status during the Replication can be Replicating, Sending, Receiving, Committing, Executing, or Completed. Message: A system supplied informational message, if needed.
Page 39 of 96
2.6.2
Replication Status Report
The Replication Status Report allows you to produce reports comparing the data on the Active Vault to the Passive Vault. This report is run from the Active Vault, and can be used, for example, to know if a failover could lose any data. 1. From the main Director screen, choose Vault Replication from the menus, and Replication Status Report from the drop down menu. In the Welcome screen, click Next. 2. Choose from Save report in a vault log file or Send generated report by email to one or more email addresses. You must have email configured in the Director to be able to get emailed reports. 3. The next screen is Analysis Scope. You can select one or the other of the two choices. The middle one Status is grayed out here, as it only applies to a Base Vault (see section 3 of this Guide).
Figure - 21. - Replication Status Report Analysis Scope
Page 40 of 96
4a. If you choose Replication Comparison you can choose how much detail you can see on the Vault. When you have selected your choices, you can run the job.
Figure - 22. - Replication Status Report Replication Comparison
The Replication Status Report, also known as a "diff report", can be quick and simple, with metadata only, or extensively compare all safeset data. You have four choices for the report. Compare metadata only (the fastest) checks that the data organization of Customers, Locations, Computers, Tasks and Backups is correct in both cases. This is a good, fast check to see that everything is there. Compare metadata plus safeset indexes does more than checking metadata, it also checks the data itself, at different levels. Comparing only the indexes of the physical data is fairly fast. It ensures that the pointers to the data are intact. If you want to compare the actual data, as well as the indexes and metadata, you can select the last replicated safeset only, or all safesets. All Safesets is the most extensive and timeconsuming option. If you check the last replicated safeset only, you know that you can get a complete restore of the most current backup.
Page 41 of 96
Note: Selecting last replicated safeset only or all safesets should only be made on the smallest possible number of jobs. Otherwise this could be a very lengthy operation, for large Vaults.
Click Submit Job immediately to start the Job that will produce the Report. Or, you may schedule it for later. The Report is stored in the Replication Log directory, under the Vault installation directory. Or, if you chose email, the report will be mailed to the recipients. 4b. If you choose Replication Lag (instead of Replication Comparison) in Analysis Scope, you can produce a report of all tasks that have fallen behind (not run) for 0 or more days. Zero days means all tasks that have not run yet today. One day means all tasks that have not run since yesterday, and so forth.
Figure - 23. - Replication Status Report Replication Lag
The Replication Lag command must be run from the ACTIVE Vault only. If you are on the Passive Vault the Replication Lag option is grayed out.
Page 42 of 96
Note: If you run the reports from the CLI (Command Line Interface) you must use REPLVAULT with the LATE command from the Active Vault. See section 8.4.2 in the Director Operations Guide for information on more options for the CLI. On an Active Vault, the Replication Lag Report does not show tasks as lagged if tasks (with backups) are missing from the Passive Vault. That is, if a task is replicated to the Passive, and later deleted on the Passive, this behaviour is as expected. This is a known limitation, as the Report does not check for tasks that have the Replication bit (which is on the Active Vault) set. If you run a diff report on the same tasks, the diff report will see them, as it checks to see if the actual tasks are there. Sample Report, showing Objects not accessible: In this report snippet, note that the legend shows [?] means not accessible. There are three tasks, each with four safesets that are not accessible. That is, they are locked by another process.
REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 Apr10 Apr10 Apr10 Apr10 Apr10 Legend: [ ] - item is replicated and identical on both vaults [*] - item is different on both vaults [?] - could not compare because item states are different on both vaults or items have partial children, or one of the items is not accessible [+] - item exists on the Active vault but does not exist on the Passive vault. [-] - item exists on the Passive vault but does not exist on the Active vault. [23756] [23756] [23756] [23756] [23756] REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 [ ]TSK: CDB4 [?]SS: 1 [?]SS: 2 [?]SS: 3 [?]SS: 4
20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015
~~~~~~~~~~~~~ Apr10 Apr10 Apr10 Apr10 Apr10 20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015 [23756] [23756] [23756] [23756] [23756] REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 [ ]TSK: 84F9 [?]SS: 1 [?]SS: 2 [?]SS: 3 [?]SS: 4
~~~~~~~~~~~~~ Apr10 Apr10 Apr10 Apr10 Apr10 20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015 20:05:04.015 [23756] [23756] [23756] [23756] [23756] REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 [ ]TSK: 13366 [?]SS: 1 [?]SS: 2 [?]SS: 3 [?]SS: 4
~~~~~~~~~~~~~ Apr10 Apr10 Apr10 Apr10 Apr10 Apr10 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 [23756] [23756] [23756] [23756] [23756] [23756] REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 Total objects examined:..............66 Identical objects found:.............54 Changed objects found:...............0 Objects with different state:........0 Objects with partial children:.......0 Objects not accessible:..............12
Page 43 of 96
2.7
Q&A on 1:1 Vault Replication
Q: What is the purpose of 1:1 Replication? A: 1:1 replication adds a high availability option to the EVault Software data protection solution and provides a number of benefits including: No single point of failure: Backups can failover to either of the Vault replicas. Accessible data redundancy: An additional recovery source means that both Vault replicas can be used for restores. Efficient use of bandwidth: Replication leverages DeltaPro technology to synchronize the Vaults. Integrated solution: Management of the solution is easy to use. Q: How does 1:1 replication work? A: In 1:1 replication there are two Vaults, which can be accessed by the EVault Software Agent. The Agent performs backups to the Active Vault and that Vault sends any new backups to the Passive Vault to keep them synchronized. The Agent can restore from either the Active or the Passive Vault (see Figure 1).
Vault1.EVault.com (ACTIVE)
Backup/Restore
Replication
Evault Agent
Vault2.EVault.com (PASSIVE) Restore
Figure 1. Normal operation
Q: What happens when the Active Vault stops working? A: If the Active Vault stops working, (for example, due to hardware failure) the Vault Administrator can failover the services to the other Vault. This changes the role of the Vault to Active and allows the Agent to perform both backups and restores to that Vault. (See Figure 2)
Page 44 of 96
Vault1.EVault.com
Evault Agent
Vault2.EVault.com (ACTIVE) Backup/Restore
Figure 2. Active Vault failure
Q: How do I re-establish service redundancy after a failure? A: In case of complete Vault loss, you need to rebuild the hardware, install the Director Vault, and re-establish replication from the Active Vault to the newly built Vault. Once the replication process synchronizes the Vaults your backup and recovery service is redundant again. (See Figure 3)
Restore
Vault1.EVault.com (PASSIVE)
Replication
Evault Agent
Vault2.EVault.com (ACTIVE) Backup/Restore
Figure 3. R e-establishing redundancy after failure
Q: Why would Vault providers want to use Vault Replication? A: Anybody that has to ensure continuous availability of backups and restores should be using Vault replication. Vault Replication ensures that Agents can always perform backups and restores in case of emergencies. The Passive Vault can continue to provide service even if the Active Vault is destroyed.
Page 45 of 96
Q: How does this feature differ from the earlier UltraRecovery 5.5? A: The main differences are: 1:1 replication is fully integrated (one console) and does not depend on third party products. 1:1 replication understands how the data is stored on Vaults and is sending only changes using DeltaPro technology. 1:1 replication is not affected by pool maintenance processes such as Optimization. 1:1 replication does not hinder an Agents ability to perform backups or restores. 1:1 has no failover capability 1:1 is not an automatic source for restores Q: What is the Agent allowed to do on the Active and Passive Vaults? A: Active Vault: The Agent can backup and restore from available backups. Passive Vault: The Agent can restore from available backups. Q: What is involved in setting up replication? A: Setup and initial configuration is easy. Replication capability is available out of the box and does not require a separate installation process. After installing both Directors and enabling the capability with the appropriate license, you need to select which Vault will be designated as Active and input the location of the Passive Vault. From that point on the management resembles any other stand-alone QuickRecovery Vault. Q: Has the Director GUI changed to show the new features? A: Yes, when licensed, there is a new selection in the top menus choices, to allow the administrator to change Vault settings, and replication configuration. Also the icons for an Active and Passive Vault are different, to show their function. Q: What overhead is incurred on my Active Vault, when sending backup data to the Passive Vault? A: There is a new service (ReplService.exe) running on the Active Vault. The service will use minimal additional memory, CPU cycles and disk I/O to keep both Vaults in-sync. The replication service runs in the background to assure that backups and restores are not hindered. Additionally, the administrator can adjust bandwidth throttling for communication limiting, so that the replication doesnt hog network bandwidth between the Vaults. Q: If a backup is a seed and takes some time to complete, does it go in parallel to the Passive Vault at the same time as the Active? A: No. For a seed or delta, the backup to the Active Vault has to complete successfully, before the Active Vault replicates it to the Passive Vault. Q: What happens if there is an interruption in the middle of replicating to the Passive Vault, and a backup is incomplete? Can it recover? A: The transport mechanism will attempt to reconnect and continue replicating to the Passive Vault if it is interrupted. But, if replication to the Passive Vault does not succeed, then the replication backup session will fail. Q: Do I still need the Vault Backup Agent running on the Vault?
Page 46 of 96
A: Yes. Replication only works on the customers backup data, and allows a switch from Passive to Active in case of a disaster so that you can continue running a Vault with minimal interruption. VBA allows you to re-build a Vault, or recover data that was accidentally deleted, or otherwise needs to be recovered. Q: Why do I need to schedule replication if it happens after each backup? A: After a backup the backup data is replicated to the Passive Vault. This only affects the data involved in that backup, and nothing else on the Passive Vault. Usually once a week, the administrator can schedule a full replication/synchronization on the Passive Vault. This does not replicate everything again, but it does ensure that the data and structure are consistent on both Vaults. Q: Is there a minimum time frame to schedule replication? A: Yes. You can schedule the replication down to a minimum of 15-minute intervals. The maximum is once a week. It is recommended to be run at least once daily. Q: If I make changes to the Vault replication configuration, do these changes take place immediately? A: You would need to stop and start the Replication Service to make changes, like port settings for example, available. Q: Does the replication produce any log files? A: There are log files for the Replication Service in the global directory. Replication sessions and reports will be generated in the global logs\replication folder. Q: Is the failover from the Passive Vault becoming Active (after a failure) automatic or are there manual steps involved? A: The Administrator must decide when to switch the Vaults over. If the Active Vault fails, the Passive Vault will still support restores, but it will not accept backups, until it is made Active. You can change the role of the Vaults by connecting to the Passive Vault. Q: Will there be data loss if the Vaults are not fully replicated when I failover replicated Vaults? A: Yes. If the Active Vault is not fully replicated, you will only keep what is available on the Passive Vault at the time of failover. If there is a replication connection at the time of failover, you will be prompted with information about the objects that are not synchronized. However, if you failover when there is no replication connection between the Vaults, that level of detail will not be available. Q: When I change the role of the Passive Vault to Active, does the Active Vault automatically become Passive? A: Yes if the Vault is replicating with the as soon as possible option. After a failure, if you loose the Active Vault, you would make the Passive Vault Active (Vault failover), so that it can receive backups. Later, you will rebuild the Vault that was destroyed, and bring it back online. Since there can only be one Active Vault at a time, the newly rebuilt Vault becomes Passive, and starts to synchronize data with the Active Vault. If you want to return them to their original status, you must ensure that they are fully synchronized (or you will lose backup data!), and that no backups are occurring at the time (the Listener is stopped). Then, make the original one Active, and the other will become Passive.
Page 47 of 96
Q: How do I re-synchronize the Vaults after failing over? A: After failing Vaulting services over to the redundant Vault, you need to recreate redundancy. You accomplish that by rebuilding a blank Vault, adding the appropriate licenses and establishing a replication connection. The Vault will replicate immediately if the Replicate Now menu command is executed. It will replicate after the first replication event if the Active Vault is replicating with the as soon as possible option, and on schedule in all other cases. Once the replication is complete, your Vaults are fully synchronized and redundant again. You can check on completeness of the synchronization with the Replication Status Report. Q: Do I need to change configuration of the Agent after Vault failover? A: This is typically not necessary. There are three scenarios: Using a replication aware Agent (6.x): No change is needed. The Agent is aware of Vault replicas and will perform backups to the Active Vault Using a legacy Agent with DNS: No change is needed. The Agents access the Active Vault via a DNS and the DNS entry is updated as part of the failover process. Using a legacy Agent without DNS: The IP or network address for the Active Vault must be changed for backups to succeed. Q: When I install the replication service, do I have to create a new account for it? A: No. The service is installed under the same user account as the rest of the Vault services. Q: Can I monitor the replication as it is running? A: Yes. The Job Monitor presents a view for all running replication sessions. The log files and execution are different on both Vaults. For Active, the Job Monitor shows: replicating, sending, committing, and completed. For Passive, it shows: receiving, and executing completed. Additionally, replication logs provide a detailed account of replication activity. Q: How does replication affect secondary and archived safesets? A: Replication is available for Safesets in primary storage. This means that Safesets in secondary storage (online or not), or archives will not be replicated. Q: If I havent activated the replication option, are the Replication menu choices (such as Configuration, Failover, Replication Status Report, and Replicate Now) not shown at all, or are they just grayed out? A: The Replication Menu is not shown until you license the Replication feature. Notice also, when replication is Active, the menu choices are different depending on whether you are on the Active or Passive Vault. Q: Can you have more than one Active Vault replicating to a Passive, or one Active Vault replicating to multiple Passive Vaults? A: No. This configuration can only support a one to one relationship. If you try to add another (i.e.: third) Vault, you will get an error message. Q: Can I replicate only some of the Safesets with 1:1 replication? A: No. 1:1 replication is meant to provide redundancy for the entire Vault. All Safesets for all computers will be always replicated.
Page 48 of 96
Q: Is there another way to do the seeding process from an Active Vault to a Passive Vault, if my bandwidth is limited? A: Yes. You would have to install a standalone vault, and do backups to it. Then, do a VVCopy clone twice, once to the active and once to the passive vault. Q: During a Replication, what data (which safesets) are replicated to the other vault? A: All online safesets that are not expired are replicated. Archive, Secondary and safesets with expired retentions are not replicated Q: After a failover, will the Agent restore from the other vault, or either one? A: Either one. After a failover, the Agent can restore data from the Passive vault (this was the first Active vault). If both vaults are running, the Agent will try to restore from what was its "preferred" vault, which was the old Active one. This is expected behavior. The restore can be from either vault, as the backup is the same on both. 2.7.1 Best Practices for 1:1
Agents that are before version 6 should have two Vault IP addresses, one for the Active Vault and one for the Passive Vault. These Agents do not know about failover, so if one Vault goes away they will simply try the other. Replication Status Report should be run before a failover, to tell you if a failover could potentially lose any data. On a Passive vault, the licensing information for OTM Licenses in the Customer Quota tab is not shown when Per Customer Quotas are enabled. This is the correct functionality. It only shows Quotas for which you have licenses (with the exception of Desktop Agent). You must ensure that the Active and Passive vaults have the same licenses installed and Active. If the licenses are not in place on the Passive vault, you will see licensing errors after a failover. Customer Quotas cannot be changed manually on a Passive vault. The Quota button is purposely grayed out. Changes are made on the Active Vault. When Replication occurs (either scheduled or ad hoc) the new Quotas are then replicated to the Passive Vault.
Page 49 of 96
Many to One Replication (N:1)
This section discusses N:1 Installation and Setup, Configuration, Vault Settings, Replication, and Monitoring. There are also Questions and Answers on N:1, and some Best Practices.
3.1
N:1 Overview
An organization may want to centralize its backups in one secure location. Previously, it was possible to have Agents across a large geographical area all perform their backups to one Vault, using communication facilities such as the Internet, or a private Intranet. But backups and restores at LAN speed would be faster and more efficient. Then, later (say, at night) those local backups can be sent to the Base Vault for permanent storage. This way, local Satellite (SAT) Vaults can collect backups (locally), and then duplicate them to the main (remote) Vault. All administration is done from the Base Vault, so no local administrator is needed on the Satellite Vaults. Administration of a Satellite Vault is limited to SalesPerson limitation. This limits the access to READ ONLY. You cannot create anything on the Satellite Vault. All administration is done from the Base Vault. Customers, locations, Accounts and Users are created on the Base Vault and replicated over to the SAT. The Agents then backup to the SAT. Also, to prevent later interaction with the Agents in the case of the SAT going down and the Agent losing the Base Vault's hostname/IP, both the Base Vault and SAT's hostname/IPs should be in the Vault registration. The SAT should be first in the hostname/IP list. If the local (Satellite) Vault fails, backups can switch over to the Base Vault. If communications to the Base Vault fails, backups (and restores) can still continue locally. Briefly, the main steps involved in using the N:1 Replication are: - Install the Base Vault. - License it for Replication. - On the Base Vault, create a Satellite Vault. Generate an authorization key. - Install the Satellite Vault. Register the authorization key back to the Base Vault. - Create a Backup Job (for an Agent) and point it to the Satellite Vault. - Start the Backups to the Satellite Vault. Details on installations and Vault and Replication configuration and setup are discussed in the rest of this Chapter. Note: A Satellite Vault is designed to be controlled by the Base Vault. That is, after it is installed, the Satellite Vault data is replicated to the Base Vault when directed by the Base Vault. The Director GUI on the Satellite is disabled by default, so you cannot create accounts and users. It may be used for troubleshooting, by support personnel. In those cases, they can create reports, view the Job Monitor, schedule commands, add Storage Locations, and other troubleshooting functions.
Many to One Replication
Page 50 of 96
Agent
LAN A - Local Backups and Restores

Online Restores
Agent A1
Online Backups
Agent
Online Restores Online Backups
Satellite Vault A
Satellite Vault in Location A contains local Backups.
Agent A2
Online Restores
Vault A Replicates to the Base Vault across the Internet.
Agent
Online Backups
Agent A3
Base Vault LAN C - Local Backups and Restores

Agent
Base Vault in Location B contains all the Backups from Satellite Vaults.
Agent C1
Vault C Replicates to the Base Vault across the Internet.
Agent
Satellite Vault C
Satellite Vault in Location C contains local Backups.
Agent C2
Online Restores
Agent
Online Backups
Agent C3
Figure - 24. - Agents connected to Satellite Vaults, which are connected to a Base Vault
Page 51 of 96
Agent
LAN A Backups and Restores when the Satellite vault is lost

Agent A1
Agent
Agents in LAN A can still do Backups and Restores from the Base Vault, across the Internet.
Agent A2
Online Restores
Agent
Online Backups
Agent A3
Base Vault
Base Vault in Location B still contains all the Backups from Satellite Vaults.
Other Satellite Vaults continue to access the Base Vault.
Figure - 25. - Agents connected to a Base Vault when the Satellite is lost.
Page 52 of 96
3.1.1
N:1 Failover Scenario
This scenario is an overview of a typical switch from Satellite, to Base Vault and back again to the Satellite. 1. The Satellite Vault is normally receiving backups. The first backup was a seed, and the following are deltas. 2. Failover to the Base Vault (for example, when the Satellite is lost). 3. Continue backups to the Base Vault (these are still deltas). 4. Failover back to the Satellite (replaced or fixed). You will be warned that it is replicating. Let this complete. 5. Now when you run a backup, it is going back to the Satellite. Note that this backup is a reseed. There is no data replication from the Base Vault back to the Satellite. It is only the metadata that gets replicated here. 3.1.2 N:1 Replication Commands, Options and Wizards This section provides an overview and summary of the commands, screens and programs that N:1 Replication may use. They are listed here, with a brief description of each one. These commands are run from the Base Vault Director console. Details, and how and when to use them are described later in this chapter.
Add a new Satellite Vault (or Edit or Delete an existing one). Shows the Customer
Satellite Vault name, Last Heartbeat, and Status. (Section 3.3) - Select existing Base Vault Customer, and get Authorization key for the Satellite installation. - Enable/Disable Over The Wire encryption, and choose Bandwidth Throttling. - Replication Schedule, as soon as possible, or on a daily schedule. - Satellite Replication and Retention Policies which safesets and how long to keep them. - Backup and Replication Options Normal, Dont Replicate, Bypass Satellite, or Restore only.
Vault Settings. (Section 3.4)

- Replication tab - Enable/Disable Replication, and Replication Connectivity port numbers. - Agent Connectivity addresses (Vaults) for Agents to use to backup and restore.
License Summary for Base Vault. (Section 3.4)

- License Type (displays current usage, and licensing values) and Activation Status (activated, trial licenses, expired).
Monitor and Reporting. (Section 3.5)

- Show Replication Activity in Job Monitor. View logs. - Replication Status Report: Scope Selection - Detailed (single Vault) or Status (of all Satellites on this Base Vault).
Page 53 of 96
3.2
Installation Overview Base Vault and Satellite
The Director installation kit contains all the types of Vault configurations Single Vault, QuickShip Vault and Satellite Vault. See the Director Operations Guide for information on installation. Note: If you are upgrading your Base Vault and Satellite Vaults, you must upgrade the Base Vault first.
Figure - 26. - Installation Director Setup Type for N:1 Replication
The Base Vault is installed as a Single Vault configuration type. After the installation you apply a license to make it a Base Vault. From the Base Vault you communicate with, and administer Satellite Vaults. These Satellite Vaults have been installed as Satellite Vault Director Setup Types. They do not require a special separate, license (like the Base Vault) but they do become activated with an internal license key from the Base Vault, and become registered to the Base Vault. See Satellite Configuration in the next section of this Guide. Once you have activated the license for replication, you will see an additional tab called Vault Replication in the Director GUI.
Page 54 of 96
3.2.1
Base Vault Installation
The Base Vault must be installed before any Satellite Vaults. The Base Vault will supply a different key a One Time Registration Key (OTRK) for authorization, which must be used in each Satellite installation. The Base Vault is first installed as a Single Vault Configuration. Section 3.3, following this section, takes you through the steps to license the Base Vault, and then configure a Satellite Vault. 3.2.1.1 Upgrading the N:1 Vaults The Base Vault (BAV) should be upgraded before upgrading any Satellite Vaults. See the detailed instructions below for upgrading the Base Vault and Satellite Vaults. Base Vault Upgrade Procedure: 1. Wait for all Replication sessions to complete, or disable replication to cancel any existing replication sessions and to avoid new replication sessions. 2. Upgrade the Base Vault. 3. Start services on the Base Vault if they are set to manual start. 4. Enable replication if it was disabled in step 1.
Satellite Vault Upgrade Procedure: Perform the following steps on each Satellite Vault: 1. Wait for the replication session to complete, otherwise the installer will cancel the Replication session as part of stopping replication service. 2. Upgrade the Satellite Vault.
Page 55 of 96
3.2.2
N:1 License Summary
Licensing for N:1 Replication is different than a regular Vault. A Base Vault requires a standalone license, and a "Replication Many to One license, while each Satellite Vault requires a Satellite Vault 1000, or 500 or 250 (for unlimited storage, 500 GB, or 250 GB of vault storage). The License Type in Vault Settings will show Replication Many to One.
Figure - 27. - Vault Settings License Summary
The Director Operations Guide has more information on installing and managing licenses, and Use per-customer quotas. If you are using N:1 Vault Replication, Customers Quotas are always required. In Vault Settings, License Summary, the Use per-customer quotas checkbox is always on, and grayed out so you cannot change it. Customer Quotas are optional in 1:1 Replication, and with a standalone vault. Note : The Satellite is controlled by Per Customer Quotas, which are configured on the Base Vault and replicated to the Satellite. The Base Vault is licensed for the number of agents and features purchased. The administrator can spread this total amount across the Satellites, but the total for all Satellites cannot be greater than the total on the Base Vault. To enforce this, the per customer quota selection (check box) is always checked on, and grayed out, so it cannot be changed.
Page 56 of 96
A Satellite Vault enforces customer quotas, which must be set correctly on the Base Vault for Replication to work. Note: The total quota for this feature cannot exceed the amount licensed for the vault. Agents may fail even though customer level quota is not exceeded, if total usage exceeds the licensed amount. Also, the Satellite vault enforces the amount of licensed storage space. If this space (not the unlimited license) is exceeded, the license logs and backup logs will have error and warning messages. 3.2.2.1 Remove an N:1 License key If you attempt to remove an LVR license key, you will see a warning message:
Figure - 28. - Remove an N:1 License Key
After you click Yes, you will be prompted with a message asking you if you want to activate to remove the license. Just as the license needed to be activated to start using it, it also needs to be activated (as in de-activated) to stop using it. The Vault needs to communicate with the License Activation Server. This can be either online or manual activation.
Page 57 of 96
3.3
Vault Settings for Base Vault
Vault settings here are the same as described in the Director Operations Guide, except that there are now two more: Replication and Agent Connection. 3.3.1 Replication tab
Figure - 29. - Vault Settings Replication tab
Enable Replication services on <Vault> is the master switch that can turn the replication on or off. By un-checking the Enable replication services on <Vault> you stop any replication processes to or from the Vault. Any replication activity will be cancelled immediately. The Replication Service can also be stopped from the Job Monitor, but it must be restarted from here. During the Satellite Vault installation, you supplied a TCP port number. The TCP port (default is 2547) is the Command Channel port that each Satellite uses to communicate with the Base Vault. It must match this port number on the Base Vault. The Base Vault listens on this port for commands (e.g.: heartbeats) from the Satellite. The Data Channel port (default 12547) is a port that the Base Vault negotiates with each Satellite, for data transfer. If you change it here, it will be propagated to the Satellites. Replication Status of the <Vault name> shows that this Vault is a Base Vault.
Page 58 of 96
3.3.2
Satellite Installation
The Satellite Vault acts as a cache, which replicates to a Base Vault. Satellite Vaults must be installed after the Base Vault is installed and running. You must have an Authorization key generated by the Base Vault, for the Satellite installation. Start the Director installation. See the Director Operations Guide for more information. When you get to the Director Setup Type screen, select the Satellite Vault button. The steps following this are the same as a regular Vault, until you get to the registration part (after the database installation). This is where you need the Authorization key that was generated earlier by the Base Vault.
Figure - 30. - Installation Director Setup Type for Satellite
The TCP port (default is 2547) is the command channel port that the Satellite uses to communicate with the Base Vault. The Satellite obtains this automatically from the Base Vault. See the Vault Settings screen, Replication tab in the Base Vault Director console. Note: The Do not perform re-registration on Base Vault button is used if you are Repairing a Satellite Vault. It allows you to not have to register the Satellite if it was already registered. On a new installation, this button is grayed out. Click Next. You will see a message: Registering Satellite to Base Vault. When this is done, you will see a Registration Confirmed screen.
Page 59 of 96
Figure - 31. - Installation Registration Confirmed for Satellite
The Satellite installation is finished. Note : The Satellite gets its licensing from the Base Vault. If there is no heartbeat from the Base Vault for 30 days, the Satellite will act like it has a trial license and expire at the end of the 30 days.
Page 60 of 96
When you return to the Base Vault, and check the Vault Replication Configuration, you will see the Satellite Vault there.
Figure - 32. - Satellite Vaults Configuration
In this screen the Replicate Now button is Active, to force a replication from the Satellite to the Base Vault. By default, the replication is scheduled to run once a week. If you click the Edit button, with a Satellite selected, and then the General tab in the Vault Replication Configuration, you will see that the Authorization key now shows Registered. 3.3.2.1 Satellite Installation on XP Pro If the Director is installed on Windows XP Professional as a Satellite vault, you may experience limitations on inbound connections. This is a Microsoft limitation on workstations, but not servers. For Windows XP Professional, the maximum number of other computers that are permitted to simultaneously connect over the network is ten. This limit includes all transports and resource sharing protocols combined. This limit is the number of simultaneous sessions from other computers the system is permitted to host. This limit does not apply to the use of administrative tools that attach from a remote computer.
Page 61 of 96
3.3.2.2 Replacing a Satellite Vault There may be times when you need to replace a Satellite Vault, for example if it has failed totally. These steps are an overview of the scenario. Details for each step (menus, options, and further explanations) can be found in the sections following this one. 1. In the Director on the Base Vault, under Vault Replication -> View Replication Config, select the Satellite that has failed. Click Edit. In the Vault Replication Configuration screen, choose the Advanced tab. Click on the Bypass Satellite option, and then the OK button. 2. Edit the failed Satellite Vault again, and select the General tab. Use the Reset key to create a new Authorization key. Copy this, or write it down. When you close the dialog, the changes will be saved to the Director. 3. Replace the Satellite Vault, and install it with this new Authorization key. You must use the same IP for the replacement Satellite Vault. 4. Wait until the replication completes. This will relocate all the metadata to the Satellite. 5. Edit the Satellite in the Satellite Vaults configuration screen, and, in the Advanced tab, change back to the Normal Operation option. 6. The Satellite will synchronize with the Base Vault, and the customer metadata will be transferred to the Satellite, so that it can start receiving backups. Any restores for previous backup data will come from the Base Vault, if they are not on the Satellite anymore. Notes: 1. If you switch the Vaults before the replication is completed and you do not allow backups on the Base Vault, then the backups will fail. 2. There is only one customer permitted per Satellite Vault. When a Satellite Vault is being switched from one customer to another, the software must be uninstalled and then reinstalled on the Satellite. If you attempt to re-register the Satellite either through the command line or through the installer, it will appear to succeed but all subsequent replication will fail on the Satellite. 3. QSM and Import/Export are not supported with a Satellite, and should not be used. It may cause unpredictable results and data loss. Replication is the only supported method of getting data from the Satellite Vaults to the Base Vault.
Page 62 of 96
3.3.3
Satellite Configuration Vault Settings for Satellites
After you have installed a Satellite Vault, you can add a New Vault Connection in the Base Vault Director console, and see and manage the Satellite.
Notice that the Vault Replication menus are different for a Base Vault and a Satellite Vault.
Also notice that the icons are different for a regular (standalone) Vault, a Base Vault, and a Satellite Vault.
Figure - 33. - Replication Menus and Satellite icons
If you select the Vault Replication -> Configuration menu, you will see the tabs for Network options, Schedule, Safeset Management, and Advanced. These are all grayed out on the Satellite Vault. They cannot be modified here. Changes are done on the Base Vault.
Figure - 34. - Vault Replication Configuration menus are grayed out
Page 63 of 96
If you choose the Vault Maintenance ->Vault Settings, the Replication tab is grayed out, except for the Enable Replication services on <name of Satellite>. This is the same as the Base Vault. You can enable/disable all replication from the Base Vault, or just for a particular Satellite.
Figure - 35. - Vault Settings on a Satellite
The message at the bottom of the screen tells you that this is a Satellite Vault. The Agent Connections tab for a Satellite is also grayed out.
Page 64 of 96
3.3.4
Agent Connection
This list is the default addresses of Vaults (host name or IP) that the Agent will receive as possible backup/restore options.
Figure - 36. - Vault Settings Agent Connection
This option should not be used for the Base Vault, only the Satellites.
Page 65 of 96
3.3.4.1 Two Network Scenario In a situation where there is only one network used for both backups and replication traffic, the SAT and Base Vault would each have only one IP address. Agents would register with the Satellite, which would pass back the Base Vault IP address, so that if the SAT goes away, the Agent knows about the Base Vault, which it would then use for backups. But, you may have a scenario where the SAT and Base Vault are connected on two separate networks, one for backups, and one for replication. The SAT and Base Vault each have two network cards, with two IP addresses. This allows backups and replication to run faster, without interfering with each other. When the Base Vault and SAT first communicate, the SAT gets the IP from the Base Vault, which is to be used by Agents in case the SAT goes away. The Agent, in its .ALT file, knows the addresses of the SAT and the Base Vault. But because the replication network was used, the IP that gets passed to the Agent is the one on the replication network, and not the backup network. Therefore, the Agent knows about the SAT, but its alternate IP is inaccessible on the other network. In Vault Settings -> Agent Configuration, you can specify what addresses the Agents should use for backups and restores. In a one network scenario, these would be the SAT and Base Vault addresses. But in the two network scenario, the Base Vault address is from the other network. You must remove that Base Vault replication address, and add the correct Base Vault backup network address.
Page 66 of 96
3.4
Vault Replication Configuration
Management and Administration of the Satellite Vaults is done from the Base Vault GUI (Management Console). Once the Base Vault is installed and licensed, you will see a Vault Replication menu choice, when you select a Base Vault. 3.4.1 Vault Replication Menus
Vault Replication is a new tab/field that is activated by licensing the Base Vault. It is not visible until licensed.
Figure - 37. - Base Vault Replication menus
All configurations are done from the Base Vault. The console/GUI on the Satellite only has read access to the Satellite. The Admin Service is running, but you cannot add or change accounts, users or tasks.
Page 67 of 96
3.4.2
Satellite Configuration Add a new Satellite Vault
The first time you try this, there will be no names in the list. You must have Customers created on the Base Vault already. You can only assign one Customer to each Satellite Vault.
Figure - 38. - Configuration screen Add a new Satellite Vault
If you try to add a New Vault without at least one Customer on the Base Vault, you will see a message: There are no customers available. After you have created a new Vault name here, and you install the Satellite Vault, and register it, that name will appear in this list, with an initial status of never replicated. The Customer metadata (not the customer data itself) is automatically copied to the Satellite Vault on the next heartbeat. The heartbeat replicates events and some basic Satellite Vault status information, such as available storage and any pending events. An Agent can now create a Job and start backing up to the Satellite. Customer Satellite Vault is the customer name and (short name). Last heartbeat is the time elapsed since the last heartbeat arrived at the Base Vault. That is, when the Satellite last contacted the Base Vault to communicate and synchronize. It may vary from one Satellite to another, as it configurable for each one, from 1 to 60 minutes - (the Heartbeat Interval) in the Advanced tab of Vault Replication Configuration.
Page 68 of 96
Note : If heartbeat intervals are configured longer apart, it will take longer to execute replicate now and ad-hoc reports. Until the heartbeat propagates the events, the Satellite Vault is not aware of the request. Operating Mode is one of: Normal Operation, Dont Replicate, Bypass Satellite, or Restore Only. These are the choices that are selectable in the Advanced tab of Vault Replication Configuration. 3.4.3 Satellite Configuration Select a Customer to use the Satellite
After you have selected New in the previous screen, you select a customer from the Base Vaults drop down list.
Figure - 39. - Satellite configuration Select Customer for Vault
There can be only one customer (already created on the Base Vault) per Satellite Vault. You can select a Quota (amount of disk space) for this satellite (customer). You would use per-customer quotas to allocate the Agents and Vault size to individual satellites (customers), so that one satellite cannot use all the resources of the Vault license. Each satellite has one customer and cannot exceed the quota assigned on the base vault. The This is an EVault for DPM satellite vault checkbox (not shown in this Figure) is discussed in section 3.4.7.2 (EVault for DPM Satellite Vault) in this Guide.
Page 69 of 96
The automatically generated Authorization key is only used once, on the Satellite. It is used to register that Satellite to this Base Vault and Customer. When you first configure a Satellite Vault, a unique, random Authorization Key is generated. This key is used in the Satellite installation, to enable trusted communication between the Satellite and Base Vault. The Reset key is used in case you are re-installing the Satellite Vault. It will create a new Authorization Key, which you will need when you run the re-installation. At this stage of the configuration, if you click OK, you could optionally skip the rest of the options [that is, accept the defaults there] and start. Or, you can see and set the options in the other tabs. If you change the options later, they will get picked up on the next heartbeat. Note : Do not click the Reset Key when the Satellite Vault is functioning normally (that is, when the Authorization Key field says REGISTERED). It will cause communication to the Base Vault to stop. You will have to re-install the Satellite with the Repair function, to validate the new Authorization Key. Also, whether you change other tabs in this screen or not, you must click the OK button to save the Authorization Key to the Base Vault.
Page 70 of 96
3.4.4
Satellite Configuration Network Options
Figure - 40. - Satellite configuration Network options
You can turn Over The Wire (OTW) encryption on or off. This is 128-bit AES, to provide a strong encryption for data across the communications channel (Internet, for example) to the Vault. SSL is used in the command channels to encrypt commands. You can choose to use all available bandwidth to the Passive Vault, or limit (throttle) it to a certain value (in megabits per second), or by time of day. Using all the bandwidth is the fastest way to replicate, but if other communication is Active at the same time, it will be impaired by the replication. You can make the replication only use a certain amount at certain times, thereby allowing other users to coexist with replication during the day for example. At night replication could use all the bandwidth, when backups are usually scheduled.
Page 71 of 96
3.4.5
Satellite Configuration Schedule
You must always have at least one scheduled weekly replication.
Figure - 41. - Satellite configuration - Schedule
You can optionally choose to also Replicate as soon as possible after changes are made on the Active vault. So, as soon as a backup is successfully completed, it will be replicated to the Passive Vault. If you choose Replicate on a defined schedule only, it means that you are deciding when all replication will take place. There will be no immediate replication after changes are made. The Replicate on a defined schedule ensures a full replication, at least once a week. You can optionally schedule replications more than once a week, depending on your frequency, and volume of backups and other business needs. A scheduled replication is necessary to ensure that all objects on both vaults are synchronized. You can choose to have the defined scheduled replication(s) take place at a certain time. You might use this if you wanted, for example, to do all your replication at night, when other users do not need the bandwidth. Note that if you do use a scheduled replication, you can also force a Replication at any time with the Replicate Now button in the Satellite Vaults Configuration screen.
Page 72 of 96
3.4.6
Satellite Configuration Safeset Management
Figure - 42. - Satellite configuration Safeset management
Satellite Replication Policy. This tells the Satellite what to replicate to the Base Vault. You can choose everything (all safesets), or only those that make it past a certain time frame (default of 1 day). Note : Retention policy is stored internally as hours, but displayed in days by the GUI. The backup time is compared against current system time on the Satellite vault. When the latest safeset is backed up, the Agent backup time will always be behind the current system time that Replication uses to check. So that safeset is not replicated, as it is not within the value for safesets to be kept on the Satellite vault. So, for example, if you want safeset retention properties to be 7 days kept online, you should make the value for safesets to be kept on the Satellite vault to be 6 days. This will ensure that the latest one (on the 7th day) will be included. Satellite Retention Policy. This tells the Satellite how long to keep them on the Satellite. They are on the Base Vault as well, so were optimizing space on the Satellite, while recognizing the need for speedy restores, when needed. The intention is to keep a little on the Satellite (for fast local restores) and everything (according to Agent retention) on the Base Vault.
Page 73 of 96
You may decide to keep <some number of safesets> for at least <some number of days>. This does not override the Agents retention policy. The Base Vault uses the Agents retention policy. That is, whatever the Agent says, it is done on the Base Vault, just like a regular Vault. The Satellite is simply a pass through, or cache. 3.4.7 Satellite Configuration Advanced
With a BAV selected, under Vault Replication, choose View Replication Config. In the Satellite Vaults Configuration screen, you will see a heading called Operating Mode. If you create a new configuration, or Edit an existing one, you will then see a Tab called Advanced. This is where you can set the Operating Mode for that Satellite, or set the Heartbeat Interval. Starting with version 6.21 of the Vault, there is a new functionality that allows the Administrator to affect Satellite Settings, to allow a Satellite to control its own settings. This cannot be turned on or off from the Satellite. It is grayed out (disabled) on the Satellite.
Figure - 43. - Satellite configuration - Advanced
Page 74 of 96
Backup options: Normal is the usual operating mode. Backups are accepted on the Satellite, and replicated, if needed, to the Base Vault. Dont Replicate turns off replication to the Base Vault, but backups can still happen on the Satellite. Note: With this option checked, no data is sent from the Satellite to the Base Vault. But if there are metadata changes on the Base Vault, they are sent to the Satellite. Bypass Satellite - If the Satellite fails, you can still backup to the remote Base Vault although it will not be at LAN speeds now. Restore only - Turning off all backups and replication effectively disables the Satellite Vault, but restores can still occur. Customer Only Replicate Customer Information Only. If you change any Organization/Customer information (meta data only, not backup data) on the Satellite, this button will replicate it back to the BAV in the next Replication session. Heartbeat Interval the Satellite is still alive as well as synchronizing to the Base Vault, and able to replicate. The default time interval is 5 minutes, but it can go from 1 to 60 minutes. Satellite Settings This allows an Administrator to let the Satellite control its own Replication Settings. Changes made here are propagated to the Satellite on the next Replication session. The Satellite can then turn Replication on/off for tasks, computers, accounts, and customers. Note that the BAV gives (allows) control to the Satellite. The Satellite Settings checkbox is grayed out when seen from the Satellite. But, on the BAV, the checkbox is still active so the BAV can always take back the control from the Satellite. Also, if both the BAV and Satellite change the same setting, the one that has control set will actually control that setting.
Page 75 of 96
3.4.7.1 Task Operating Modes If the BAV Allows this Satellite to control its own settings by setting the Satellite Settings checkbox on (see the previous section), the Satellite can change the operating mode of its tasks. Any changes then made are propagated back to the BAV during the next replication session Overview of Task operating mode functions: 1. The following modes are available to the Administrator: Default In N:1 , use the Satellite global replication settings. In 1:1 use default replication mode. Paused Replication replication is temporarily stopped. Bypass satellite Backups go to the BAV instead of the Satellite; no replication between satellite and BAV. (Bypass Satellite must be set on in the Agent.) 2. The Administrator can change a tasks operating mode from the GUI, by right-clicking in the Vaults tree node. An Operating Mode tab is also shown in a Tasks and Accounts property window. 3. In N:1 replication, if the global operating mode is not set to normal, then you cannot change the operating mode on a task/account level to Paused replication. And, if a tasks operating mode is not set to Bypass Satellite by the Agent, then you cannot change the tasks operating mode from the GUI. 4. An Administrator can view a tasks or accounts operating mode, in the tasks or accounts property window tab. 5. An Administrator can select an account level operating mode (different from default) that will be used each time a new task is created. 6. If the Allow Satellite Changes is set to off (the default behavior), the Administrator can change a tasks or accounts operating mode on the BAV. If Allow Satellite Changes is set to on, the Administrator can change a tasks or accounts operating mode on the Satellite and the changes will then be replicated to the BAV.
Page 76 of 96
You can see and change a tasks Operating Modes by selecting a task in the tree under a Vault, right click for Properties (or use F2), and select the Operating Mode tab.
Figure - 44. - Operating Mode tab, Task Properties
If Use Global operating mode is set, you will have a Pause Replication button. For the Bypass Satellite button to be active, the bypass satellite option must be set on in the Agent that owns this task. Note that once this Bypass Satellite is checked on for this task, it cannot be turned off from here.
Page 77 of 96
Depending on how you have set the Normal Operations button (in the Advanced tab), you may not be able to overwrite the operating mode.
Figure - 45. - Cannot overwrite Operating Mode
If Use Global operating mode is not set, you will not have a Pause Replication button.
Page 78 of 96
In the same way as using the properties of a task (above) you can also right-click on a task in the tree, and see and change the same three choices.
Figure - 46. - Right Click for Operating Mode on Tasks
Also, you can go up the Vaults tree node and choose particular Computers, Locations, or Customers and effect the changes on all the objects below them. (Note that you cannot choose Vault, Account or User.) With this ability, you can affect one or more, or all tasks under a Customer, Location or Computer.
Figure - 47. - Right Click for Operating Mode on Customers, Locations, and Computers
Page 79 of 96
3.4.7.2 EVault for DPM Appliance EVault for DPM (EVault for Microsoft System Center Data Protection Manager) is an appliance that uses Microsofts DPM, plus an integrated Satellite Vault to manage nonWindows Backups. In the General tab of Vault Replication Configuration is a check box called This is an EVault for DPM appliance. When you are creating a new satellite for the EVault for DPM appliance, you must make it an EVault for DPM appliance with this checkbox. This can only be done when you are creating a new satellite. It does not work if you try to edit an existing satellite vault. Once you have decided to make a Satellite an EVault for DPM appliance, you cannot change (undo) the setting. Now, in the Advanced tab (see the previous section) the checkbox to Allow this Satellite to control its own settings is checked on, and grayed out. The Operating Modes are also grayed out, with the Customer Only button set on. These now cannot be changed. In Satellite Vaults Configuration on the BAV, the EDPM Satellite now shows an Operating Mode of Replicate Customer Information Only. As an EVault for DPM satellite, the vault can control its own settings and replications. Any changes made on the BAV will not affect disabling, retentions and deletions on the Satellite. Backups and Restores will occur as normal on the satellite, controlled by its own configuration.
Note: Changes made on the BAV meta information will be propagated to the Satellite. Changes made on the Satellite will be replicated to the BAV. When changes occur on both sides, then the Satellite changes will be accepted on the BAV.
Note : An EVault for DPM appliance is special in that any DPM data cannot be removed from the Satellite when it is removed from the BAV. For example, this would happen when offsite protection is disabled. This is different from a regular satellite, where control is from the BAV. Control of the data always remains with the satellite.
Page 80 of 96
3.5
Monitor and Reporting
This section describes how to use the Job Monitor during Replication, to show the session progress. You can also get a Replication Status Report. 3.5.1 Job Monitor and Logs
When you install the Replication license, a new check field Show Replication Activity - will show in the Job Monitor.
Figure - 48. - Job Monitor Show Replication Activity
If you click the Show Replication activity box in View Options, you can see the Replication jobs that have run. You can also see the Replication logs from here. There are different types of activity that will be visible on the Active Vault, for example the replication service itself, replicating, completed, and pending replication sessions. You will be able to access the service log and the individual session logs from here . After a Replication, the log file will show Total data transferred and Data transfer speed. Note: You cannot change the Purge Log times on a Satellite vault. Under Vault Maintenance -> Vault Settings -> Logs, the default values are grayed out. They are set at installation time, and do not get changed or updated from the Base Vault.
Page 81 of 96
The Progress dialog will be available only for the running sessions. Replication progress is updated once every couple of seconds, and the job monitor is updated once every 30 seconds, by default (configurable). The Stop button will not actually stop the selected Replication Service from running but will turn off (disable) the master replication switch. To re-enable the service you must enable the Replication Master Switch (in Vault Settings -> Replication). The Stop button on a selected Replication Session will also stop the Replication Service (that is, it disables Replication). Again, you can restart this from the Replication Master switch. 3.5.1.1 Replication Session Progress When a Replication is running, you can monitor its progress from the Job Monitor, with the Replication Job selected (highlighted) and then selecting the Progress button. This will bring up the Replication Session Progress screen. Note : You can find similar information in the Replication Logs.
Figure - 49. - Job Monitor Replication Session Progress
The following Display only fields are shown. Click OK when finished. Session: A unique, internal GUID for this Replication. Session Start Time: When the Replication actually started (scheduled or manually). Total Objects to be Replicated: What should be Replicated. Objects Replicated: What was actually Replicated. If different from above, check the log file. Traffic: Number of bytes transferred during the Replication.
Page 82 of 96
Status: Status during the Replication can be Replicating, Sending, Receiving, Committing, Executing, or Completed. Message: A system supplied informational message, if needed. 3.5.2 Replication Status Report
The Replication Status Report runs on the Base Vault and allows you to produce reports showing the replication status between the Base vault and a Satellite Vault. If you attempt to run the Replication Status Report with a Satellite selected, you will see the commands grayed out. You must run it from the Base Vault.
Figure - 50. - Cant run Replication Status Report on a Satellite
Note: If you run the reports from the CLI (Command Line Interface) you must use REPLVAULT SETSATREPORT LATE from the base Vault. See section 8.4.2 in the Director Operations Guide for information on more options for the CLI.
Page 83 of 96
1. From the main Director screen, with a Base Vault selected, choose Vault Replication from the menus, and Replication Status Report from the drop down menu. In the Welcome screen, click Next. 2. Choose from Save report in a vault log file or Send generated report by email to one or more email addresses. You must have email configured in the Director to be able to get emailed reports. 3. The next screen is Analysis Scope. You can select one of the three choices.
Figure - 51. - Replication Status Report Analysis Scope
Page 84 of 96
4a. If you choose Replication Comparison you can choose how much detail you can see on the Vault. When you have selected your choices, you can run the job.
Figure - 52. - Replication Status Report Replication Comparison
The Replication Status Report, also known as a "diff report", can be quick and simple, with metadata only, or extensively compare all safeset data. You have four choices for the Report Scope selection. Compare metadata only (the fastest) checks that the data organization of Customers, Locations, Computers, Tasks and Backups is correct in both cases. This is a good, fast check to see that everything is there. Compare metadata plus safeset indexes does more than checking metadata, it also checks the data itself, at different levels. Comparing only the indexes of the physical data is fairly fast. It ensures that the pointers to the data are intact. If you want to compare the actual data, as well as the indexes and metadata, you can select the last replicated safeset only, or all safesets. All Safesets is the most extensive and time-consuming option. If you check the last replicated safeset only, you know that you can get a complete restore of the most current backup.
Page 85 of 96
Note: Selecting last replicated safeset only or all safesets should only be made on the smallest possible number of jobs. Otherwise this could be a very lengthy operation, for large Vaults.
Click Submit Job immediately to start the Job that will produce the Report. Or, you may schedule it for later. The Report is stored in the Replication Log directory, under the Vault installation directory. Or, if you chose email, the report will be mailed to the recipients. 4b. If you choose Status in Analysis Scope, you can get a quick status report of all the Satellite Vaults connected to this Base vault. The next screen in the Wizard runs the job immediately, or schedules it. Sample Status Report:
REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0001 VVLT-I-0033 Status report for all the Satellites on the Base Vault. Satellite Vault Customer: d6201 (d6201) Satellite ID: 1 (00000000-0000-0000-0000-000000000000) The Satellite Vault has not been registered yet. # # # # of of of of Satellites Satellites Satellites Satellites on the Base Vault:.................1 with overdue heartbeat:............0 with pending replication events:...0 that have not yet registered:......1
Satellite Status Report Completed. Total processing warnings: 0 Total processing errors : 0 Total processing failures: 0 Process Completed. elapsed time 00:00:01
Page 86 of 96
4c. If you choose Replication Lag in Analysis Scope, you can produce a report of all tasks that have fallen behind (not run) for 0 or more days. Zero days means all tasks that have not run yet today. One day means all tasks that have not run since yesterday, and so forth. If you have more than one Satellite Vault selected, you will get a separate report for each Satellite.
Figure - 53. - Replication Status Report Replication Lag
Page 87 of 96
Sample Report, showing Objects not accessible: In this report snippet, note that the legend shows [?] means not accessible. That is, the objects are locked by another process.
REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 vault. REPL-I-0001 Vault. Legend: [ ] - item is replicated and identical on both vaults [*] - item is different on both vaults [?] - could not compare because item states are different on both vaults or items have partial children, or one of the items is not accessible [+] - item exists on the Base Vault but does not exist on the Satellite [-] - item exists on the Satellite vault but does not exist on the Base
~~~~~~~~~~~~~ Apr10 Apr10 Apr10 Apr10 Apr10 Apr10 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 20:05:04.031 [23756] [23756] [23756] [23756] [23756] [23756] REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 Total objects examined:..............66 Identical objects found:.............54 Changed objects found:...............0 Objects with different state:........0 Objects with partial children:.......0 Objects not accessible:..............12
Note: In a Detailed Satellite Report, objects with partial children typically means that the task is paused. Sample Report, showing Replication Status (Progress): In this report snippet, it shows Replication Status (Progress). It includes the size of the data completed (as a %), for the # of Customers, Locations, Computers, Tasks and Safesets.
~~~~~~~~~~~~~ REPL-I-0001 EVault Software Director Replication Program REPL-I-0001 D:\Director\prog\REPLVAULT late vault -days=5 ~~~~~~~~~~~~~ REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 REPL-I-0001 10 Customer(s) on vault, 50.0% of metadata replicated 20 Location(s) on vault, 60.0% of metadata replicated 30 Computer(s) on vault, 55.0% of metadata replicated 40 Safeset(s) on vault, 39.5% of metadata replicated Total tasks processed: 124 Total tasks where replication is lagging: 20 Total failed tasks: 0 Replication Lag Report (5 days) generation completed.
~~~~~~~~~~~~~
Page 88 of 96
3.6
Q&A on N:1 Vault Replication
Q: What is the purpose of many to one replication? A: If you have remote sites that need backups, and you want the backups to be at LAN speed, you can use a Satellite Vault at that site. This allows fast backups and restores. Also the backups are securely stored on a Base Vault, at a central site. Q: How does it work? A: A Base Vault is installed and licensed at a central site. One-time Registration Keys are generated at the Base Vault and sent to the Satellite site. There they are used in the installation of the Satellite Vaults at the remote sites. Local Agents can backup and restore to the Satellite Vault. Configuration and administration is done from the Base Vault. The Satellite can then transfer its backups to the Base Vault. Q: What happens if the Satellite Vault fails, or cannot be accessed? A: Version 6 Agents will switch over automatically. For version 5 Agents, the Vault administrator must switch Local Agents over (re-direct the backups) to use the main Base Vault, over the network. Q: How many Agents can I have that backup to my Satellite Vault? A: This depends on how the Vault is sized and configured. This is similar to a standalone Vault. Q: How many Satellite Vaults can I have on one Base Vault? A: Again this depends on how many Agents there are, and how much data they backup. Q: Can I have more than one Customer on a Satellite? A: No. Each Satellite can have only one customer assigned to it. The Base Vault can have many Customers (Satellites). Q: Does each Satellite Vault require a license? A: The Base Vault will support up to a certain licensed number of Satellites, but the licensing is done on the Base Vault itself. When you install a Satellite you only need a unique, one-time Authorization key that the Base Vault generates when needed. This allows the Satellite to register with the Base Vault. Customer Quotas, which are defined on the Base Vault, are used by the Satellite. Q: Do I need a separate installation kit for the Base Vault and Satellite Vault? A: No, the Vault installation prompts you for the type of installation you want. You can use the same kit for all your Vault installations. Q: Can I use 1:1 replication to backup my Base Vault? A: No. 1:1 and N:1 do not work together. You either have one or the other, on a Vault. If you want to have your Base Vault itself backed up, you can use the VBA (Vault Backup Agent). Q: How long are my backups kept on the Satellite and the Base Vault? A: The administrator can decide how long the Satellite backups are kept. But the Agent retention is the deciding factor in how long safesets are eventually kept. Typically the Satellite would keep backups for a short time, while the Base Vault keeps them longer.
Page 89 of 96
Q: When does replication take place to the Base Vault? A: The Base Vault administrator can schedule when the replications take place. Q: How is the Satellite Vault administered? A: It is administered remotely via the Director Console (GUI) on the Base Vault. A Satellite Vault itself has a read only local Director Console. Q: Does an existing backup Agent have to be changed to use the Base Vault? A: The Agent does not know to what type of Vault it is backing up. Replication is strictly a Vault function. Q: Can I convert my existing standalone Vault to a Satellite without losing any backups, or having to re-seed? A: Typically a standalone Vault would become the Base Vault (by licensing). The Satellite Vault would typically be a new installation. You would have to re-install the Satellite Vault, if it was already a standalone Vault Q: Can I convert my existing standalone Vault to a Base Vault without losing any backups or having to reseed? A: Yes. With the proper license, you can make your regular Vault into a Base Vault. Any existing data on the Vault would not get replicated to a Satellite, but users could restore from the Base Vault. New backups would go to the Satellite, and also get replicated to the Base Vault. Q: If I have to replace a Satellite Vault, do the users notice the switch, or have to do anything? A: While you swap out a Satellite, users (with Agents 6.x) would use the Base Vault for un-interrupted backups and restores. You replace the Satellite, reset the authorization key, which replicates the customer metadata to the Satellite so that it can accept backups. Existing backups on the Base Vault do not get replicated back down to the Satellite, but users can still restore from previous backups on the Base Vault. Q: Can I move my Satellite Vault to another office? A: If it remains with the same Customer name, you can. But if you want to use it for a different Customer, you must uninstall the software and re-install it for the new Customer name. Then you can re-register it with the Base Vault. Q: Can a Satellite Vault replicate to two separate Base Vaults? A: No. A Satellite is only registered to one Base Vault. Q: Can I make my existing Satellite Vault into a regular standalone Vault? A: You would have to uninstall the Satellite Vault and run the installation again for a single Vault configuration. You will lose the existing data on the old Satellite Vault, but that data would still be on the Base Vault, if you did a final replication. Q: Can I backup to the Base Vault while the Satellite is supposed to be getting the backups? A: Not with the same customer. You are either backing up to the Satellite, or bypassing it to backup to the Base Vault. But, if you have a customer on the Base Vault that has not been assigned to a Satellite, then you can backup to that customer on the Base Vault like a regular Base Vault.
Many to One Replication Page 90 of 96
Q: If I expire a safeset on the Satellite, does it also get expired (deleted) on the Base Vault? A: . Safesets on the Base Vault do not get deleted when they expire on the Satellite. They only get deleted when they expire on the Base Vault. Also, a Satellite safeset will be deleted if it expired based on the normal Agent retentions. Q: Can a QSM Vault be used to circumvent the seeding process from a Satellite Vault to a Base Vault? A: No. QSM and Import/Export are not supported in this scenario, and should not be used. It may cause unpredictable results and data loss. Replication is the only supported method of getting data from the Satellite Vaults to the Base Vaults. 3.6.1 Best Practices for N:1
If you have to physically replace a Satellite with a new machine, it should have the same DNS address as before, or else all the Agents will not see it. When you first register an Agent to a Satellite Vault, it replicates immediately to the Base Vault. After that it replicates on each heartbeat, propagating events and Vault status information. You can set the heartbeat timing interval in Vault Replication Configuration -> Advanced Options. There is only one customer permitted per Satellite Vault. When a Satellite Vault is being switched from one customer to another, the software must be uninstalled and then reinstalled on the Satellite. If you attempt to re-register the Satellite either through the command line or through the installer, it will appear to succeed but all subsequent replication will fail on the Satellite. Upgrading N:1 Vaults: The correct sequence of upgrading is to upgrade the Base Vault (BAV) first and then the Satellite Vault(s). Some expired safesets may be removed (based on retention settings) from a Satellite Vault after a replication of all safesets to the Base Vault. Note: All safesets still exist on the Base Vault.
Page 91 of 96
3.6.2
Troubleshooting
N:1 Disaster Recovery Workaround: VBA (Vault Backup Agent) may not properly recover the Director Base Vault. The restore may complete with failures. These workaround steps (below) are run manually, to be able to recover the vault correctly. You must have a valid backup before a disaster occurs. 1. Install the latest VBA on the Base Vault. 2. Perform a complete VBA backup to another vault (e.g.: Vault B). 3. The VBA Backup will complete successfully. As a workaround, for when a disaster occurs (such as losing the Base Vault) follow these steps (replace the A and B vault names here with your vault names): 1. Install Vault A as standalone. Add appropriate N:1 license to change the standalone vault to a Base Vault. 2. Install VBA on Vault A. 3. Re-register to Vault B to retrieve the VBA job. 4. Restore the VBA job (but only select the metadata to be restored). 5. When restore finishes, reset the database password on Vault A. 6. Restart all the vault services (or reboot the server). 7. Restore the VBA job again but select data only. 8. After the VBA restore completes, the restored safesets will not be visible via the Director console. 9. Rename all files (for all jobs ) that have the extension ".vba-cashed" to their original file names. e.g.: (poolfiles.dat.vba-cashed.3552, renamed to poolfiles.dat).
(Note that they are called vba-cashed, not vba-cached.)
There are 6 files per job that need renaming: poolfiles.dat poolfiles.names poolsync.dat poolsync.names sync.dat sync.mir 10. Install a new Satellite vault, and register the Satellite vault to Base Vault. Replication should take place.
Page 92 of 96
Index
Compare metadata...................................... 41, 85 completed and pending replication sessions....................... 38, 81 Configuration default settings ................................... 24 definition ............................................ 20 Confirm delete data ......................................... 35 the change with YES........................... 33 credentials for Passive Vault................................. 25 Customer metadata...................................... 62, 68 Satellite Vault ..................................... 68 Data Channel default values ..................................... 37 port .............................................. 25, 58 Data transfer speed Replication ................................... 38, 81 default list of Vaults for failover .................................... 30, 65 Detached Secondary status................................................. 18 diff report Replication Status Report .............. 41, 85 Director GUI on Satellite is disabled.................. 50 installation kit.............................8, 19, 54 installed on Windows XP Professional.. 61 Management Console...........................7 Operations Guide .................................7 Setup Type.............................. 19, 20, 54 Single Vault configuration .................... 20 Vault, definition .....................................7 Disable all replication ...................................... 64 Vault Replication................................. 20 Do not perform re-registration on Base Vault ..................................... 59 Dont Replicate option................................................. 75 DPM plug-in bypass satellite................................... 12 DR switch Vaults ...................................... 29 EDPM Satellite Operating Mode.................................. 80 Enable Replication Services on Satellite ......................................... 64 on this Vault ................................. 37, 58 EVault for DPM
Active Vault fails ..................................... 15 Active/Passive roles switched............................................. 31 Admin Service on Satellite ......................................... 67 AES 128-bit ......................................... 27, 71 Agent .ALT file ............................................. 66 before version 6.................................. 49 Connection ......................................... 30 list of Vaults........................................ 30 Agent Configuration two network scenario .......................... 66 All Safesets compare data............................... 41, 85 Allow this Satellite to control its own settings .................... 80 Analysis Scope....................................... 84 for 1 to 1 ............................................ 40 Attach secondary storage .............................. 18 Authorization key for Satellite......................................... 55 on satellite.......................................... 70 Registered ......................................... 61 automatic failover.................................................8 Backup Destination Scenarios ................... 11, 13 has not been replicated yet.................. 35 Backup options Bypass Satellite.................................. 75 Dont Replicate ................................... 75 Normal ............................................... 75 Restore only ....................................... 75 Bandwidth Throttling option................................................. 27 bare metal Disaster Recovery .............................. 17 Base Vault Definition............................................ 14 Installation.......................................... 55 Bypass Satellite if failed ............................................... 62 option................................................. 75 Cleanup after replication ................................... 10 Command Channel default values ..................................... 37 port .............................................. 58, 59 command port ........................................ 25
Index
Page 93 of 96
EVault LVR Guide for Director 6.2 DPM Plug-in ....................................... 12 EVault for DPM appliance ....................... 80 expired safesets ............................................. 91 Failover could lose data ............................. 40, 83 definition ...................................... 14, 20 graceful .............................................. 35 N:1 .................................................... 29 option................................................. 17 to Base Vault...................................... 53 to Satellite.......................................... 53 Force a failover ............................................ 35 a Replication ...................................... 72 Heartbeat definition ............................................ 14 Interval............................................... 75 replicates events................................. 68 host name of the Active Vault............................... 29 hostname/IP list...................................... 50 I AGREE lost data............................................. 35 icons for Active and Passive Vaults .............. 24 for Base Vault and Satellite Vaults ....... 63 individual session log ........................ 38, 81 internal GUID ......................................... 39 Job Monitor Replication Service ............................. 58 Last heartbeat ........................................ 68 License for replication................................ 19, 54 Licensing 1:1.......................................... 15 limitations on inbound connections ...................... 61 Logical Vault Replication definition ..............................................8 Many-to-one definition ............................................ 14 master replication switch ......................... 38 Metadata definition ............................................ 14 plus safeset indexes ..................... 41, 85 metadata changes on Base Vault ..................................... 75 Monitoring of replication process .......................... 20 N:1 Failover Scenario................................ 53 Network options ............................................... 71 New Vault Connection Many to one ....................................... 24 N:1 .................................................... 63 no data replication back to Satellite.................................. 53 no heartbeat for 30 days ......................................... 60 Normal Operation option ......................... 62 not accessible in replication status ............................. 43 objects with partial children ............................. 88 Objects not accessible diff report............................................ 43 Objects Replicated.................................. 39 one network scenario.............................. 66 One Time Registration Key ORTK ................................................ 55 One to one definition ............................................ 14 open files or processes during upgrade ................................... 13 Operating Mode definition ............................................ 69 Replicate Customer Information Only ... 80 orphaned files after replication ................................... 10 OTW encryption for replication................................ 27, 71 Passive Vault settings .............................................. 25 Pause Replication button......................... 77 Per-Customer Quotas ............................. 56 preferred Vault........................................ 11 definition: ........................................... 11 Primary Vault Active ................................................. 15 status................................................. 18 protocol for the data channel ............................ 37 PTCP preferred protocol ............................... 37 Purge Log times on a Satellite vault .............................. 81 QSM and LVR not supported ....................... 62 Vault .................................................. 91 Quotas button is grayed out ............................ 49 on Passive vault ................................. 49 per customer quota selection ............... 56 Register Agent to a Satellite Vault ..................... 91 Satellite to Base Vault ......................... 59 Registration Confirmed............................ 59 Release Notes Caveats ............................................. 10 Remove an LVR license.................... 22, 57 Repair a Satellite Vault............................ 59
Index
Page 94 of 96
EVault LVR Guide for Director 6.2 Replace a Satellite............................ 62, 91 Replicate Now .................................. 61, 72 menu option ....................................... 36 workflow............................................. 20 Replication as soon as possible ...................... 28, 72 copies Quotas .................................... 49 definition ...................................... 14, 15 errors ................................................. 26 jobs that have run ......................... 38, 81 license .................................................8 Log directory ................................ 42, 86 Log files ............................................. 32 Master Switch............................... 23, 37 of online safesets................................ 18 on a defined schedule......................... 72 on a defined schedule only .................. 28 Online Storage Only:........................... 10 scheduled to run once a week. ............ 61 Service restarted ................................ 31 Status ................................................ 58 Status Report Base Vault ..................................... 83 tab ..................................................... 58 grayed out ...................................... 64 uses SSL ........................................... 27 Replication Comparison .......................... 85 for 1 to1 ............................................. 41 Replication Lag....................................... 87 for 1 to 1 ............................................ 42 option grayed out ................................ 42 Replication Status Progress ............................................ 88 Replication Status Report ........................ 40 grayed out .......................................... 83 out of sync issues ............................... 33 ReplVault CLI .................................................... 83 REPLVAULT CLI .................................................... 43 Reporting of replication process .......................... 20 Reset key ............................................... 62 satellite authorization .......................... 70 Restore only option................................................. 75 Safeset Backup Date: ...................................... 10 Retention policy.................................. 73 to be replicated to Passive ................... 15 Safeset management for Satellite configuration..................... 73 SalesPerson limitation ............................................ 50 SAT alternate IP address............................ 66 Satellite cant communicate.............................. 12 gets licensing from Base Vault............. 60 Installation.................................... 55, 59 never replicated.................................. 68 read only ............................................ 50 Replication Policy ............................... 73 re-registered....................................... 31 Retention Policy.................................. 73 trial license......................................... 60 Satellite Settings checkbox............................................ 75 control its own settings ........................ 74 Scheduled Replication N:1 .................................................... 28 Secondary Vault Passive .............................................. 15 Status ................................................ 18 security policy......................................... 25 Select Customer for Vault........................ 69 service log........................................ 38, 81 Session Replication ......................................... 39 Start Time .......................................... 39 Show Replication Logs .................................................. 32 Sessions ...................................... 38, 81 simultaneous sessions from other computers .......................... 61 Single Vault configuration .................. 19, 54 SSL to encrypt commands.......................... 71 Status Active or Passive ................................ 23 during the Replication ......................... 39 in Analysis Scope ............................... 86 of Replication ..................................... 23 stop button Replication ................................... 38, 82 Storage Locations passive vault ...................................... 26 Submit Job Report ................................................ 42 Submit Process Report ................................................ 86 SV Satellite Vault ..................................... 14 switch the Replication mode .................... 12 Synchronize backup data ....................................... 12 definition ............................................ 14 replication Vaults ................................ 20 task is paused partial children.................................... 88 TCP ports cmd and data ..................................... 31
Index
Page 95 of 96
EVault LVR Guide for Director 6.2 Satellite.............................................. 59 Total data transferred Replication ................................... 38, 81 Total Objects to be Replicated................. 39 Traffic during the replication .................... 39 troubleshooting N:1 Replication ................................... 50 turn replication on or off..................... 37, 58 two network scenario .............................. 66 Upgrading Active/Passive Vaults.......................... 19 Base Vault and Satellite Vaults ............ 54 N:1 Vaults .......................................... 91 Passive Vault first ............................... 13 Use Global operating mode ..................... 77 Use per-customer quotas checkbox............................................ 56 Vault optimization ........................................ 16 Vault configurations installations ........................................ 13 Vault connections different Agents .................................. 31 Vault registration Base Vault and SAT............................ 50 Vault Replication Configuration ...................................... 61 Customers Quotas .............................. 56 menu ........................................... 40, 84 tab ............................................... 19, 54 Vault Replication Service installation .......................................... 15 Vault Settings ports .................................................. 31 Vault tree node ....................................... 76 Vaults are out of synch.................................. 17 View Replication Config .......................... 33 YES to Active Vault .................................... 34
Index
Page 96 of 96

Director LVR Guide PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Director LVR Guide PDF

Загружено:

Авторское право:

Доступные форматы

EVault Software LVR for Director 6.

EVault LVR Guide for Director 6.2

GUI Icons for LVR........................................................................................... 9 Some Explanations on LVR............................................................................. 10

ONE TO ONE REPLICATIO N (1:1) ..............................................................................15

2.1.1 2.1.2 2.1.3

In sta lla tion a n d Setu p ................................................................................................ 19

2.2.1 2.2.2 2.2.3 2.2.3.1 2.2.4 2.2.5

Con fig u ra tion .......................................................................................................... 24

2.3.1 2.3.2 2.3.2.1 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7

Replicate Now menu ..................................................................................... 36 Vault Settings - Replication tab ....................................................................... 37

Mon itor a n d Rep ortin g .............................................................................................. 38

Best Practices for 1:1..................................................................................... 49

MANY TO ONE REPLICATIO N (N:1) ..........................................................................50

EVault LVR Guide for Director 6.2

N:1 Failover Scenario..................................................................................... 53 N:1 Replication Commands, Options and Wizards.......................................... 53

In sta lla tion Overview Ba se Va u lt a n d Sa tellite ............................................................. 54

3.3.1 3.3.2 3.3.2.1 3.3.2.2 3.3.3 3.3.4 3.3.4.1

Va u lt Rep lica tion Con fig u ra tion .................................................................................. 67

3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.7.1 3.4.7.2

Mon itor a n d Rep ortin g .............................................................................................. 81

Best Practices for N:1 .................................................................................... 91 Troubleshooting............................................................................................ 92

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

About LVR (Logical Vault Replication)

EVault LVR Guide for Director 6.2

GUI Icons for LVR

EVault LVR Guide for Director 6.2

Some Explanations on LVR

EVault LVR Guide for Director 6.2

Backup Destination Scenarios

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

EVault LVR Guide for Director 6.2

One to One Replication (1:1)

One to One Replication

EVault LVR Guide for Director 6.2

Some of the parameters that the administrator can set include: -

One to One Replication

EVault LVR Guide for Director 6.2

Figure - 1. - Failover Scenario

One to One Replication

EVault LVR Guide for Director 6.2

Secondary Pools and Detached Secondary

One to One Replication

EVault LVR Guide for Director 6.2

Installation and Setup

Figure - 2. - Installation Director Setup Type for 1:1 Replication

One to One Replication

EVault LVR Guide for Director 6.2

Overview of Steps to set up 1:1 Vault Replication

These are discussed in more detail following this section.

EVault LVR Guide for Director 6.2

Licensing for 1:1 Replication

Figure - 3. - 1:1 Licensing

One to One Replication

EVault LVR Guide for Director 6.2

Figure - 4. - Remove a 1:1 License Key

One to One Replication

EVault LVR Guide for Director 6.2