Asigra Dsuser Guide

DS-Client User Guide
DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Asigra Inc. All Rights Reserved.
Generated on: 10/15/12 Page: 1

Confidential.
Assumptions
The following assumptions are made about the audience for this document: Familiarity: User is familiar with the Operating System platform. User is familiar with basic Internet browsing. Correct Input: User enters the correct data (e.g. user names, passwords, etc.) when asked or required. If invalid data is entered, an error message will appear, and you will be forced to correct the error before you may proceed. Canceling activities: The option to cancel the current activity (in some cases the option is No) will exit the activity.
Disclaimer
Information in this document is subject to change without notice and does not represent a commitment on the part of ASIGRA Inc. ASIGRA Inc. makes no representation or warranty, express, implied, or statutory, with respect to, and assumes no responsibility for the accuracy, completeness, sufficiency or usefulness of the information contained herein. This document may contain sample screen shots, used to demonstrate Asigra Cloud Backup procedures. All information appearing in this document is used for illustration purposes only, and it should be considered fictitious.
Copyright
The software described in this document is furnished under a license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement. Asigra, the Asigra logo, DS-Client, DS-System, and Cloud Backup are trademarks of Asigra Inc. All other brand and product names are, or may be trademarks of their respective owners.
About Asigra Cloud Backup

Asigra Cloud Backup is a unique alternative to traditional backup methods, replacing conventional tape based systems with a fully automated Online solution. It provides centralized and automated backups of PCs, file servers and application/database servers with secure offsite storage and immediate Online restoration. The system uses a DS-Client, installed onto the customer network, which hosts the Asigra Cloud Backup client application software that performs the backup and restore activity.
Document Prepared by: Asigra Inc. 1120 Finch Avenue West, Suite 400 Toronto, Ontario, CANADA M3J 3H7 info@asigra.com www.asigra.com


Confidential.
DS-Client User Guide Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1 - Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Document Revision History Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How It Works: Major Asigra Cloud Backup Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main DS-Client Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/Restore Data Transfer Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-User Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 23 23 24
Running DS-User and Connecting to a DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Initial DS-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2 - Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Change the DS-Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View the DS-Client Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-register the DS-Client with the DS-System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption Key Safeguarding at the DS-System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the Default Options (for Backup Sets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the E-Mail Notification Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the SNMP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the DS-Client Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit the Settings for DS-System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure DS-Client User and Group Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-Client Advanced Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 32 33 33 34 36 38 39 41 43 47
Export DS-Client configuration to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 To export DS-Client configuration to XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 To update a DS-Client using config-update.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Set a User/Group Maximum Online Storage Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Password Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Add or Edit a User for Password Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Add or Edit a Password Rotation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 View Quotas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Bandwidth Throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Modify the DS-Client Setup (Windows DS-Clients) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 DS-User Initialization (Win32 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 DS-User Initialization (Optional - JAVA Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Context (Win32 and Java GUI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto-Connection (Win32 and Java GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regional Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keep Alive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Look & Feel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63 63 65 65 66 67 68 68

Confidential.
Fonts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Show Memory (of the GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Grid DS-Client (Windows DS-Clients) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor Grid Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop a DS-Client Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Export the Grid DS-Client Addresses (to text file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View DS-Client Grid Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 71 72 73 74
3 - Schedules and Retention Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

About Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create or Modify a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add a Detail to a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Schedules and Schedule Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Schedule Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assign Backup Sets to a Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Backup Set Priority in a Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change Number of Simultaneous Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Retention Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create or Edit a Retention Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assign Retention Rule to a Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enforce Retention Rule (on demand) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 77 78 81 82 83 83 84 85 85 91 91
4 - Creating and Modifying Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Introduction & Common Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Backup Sets (New Backup Set Wizard). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Backup Sets (Backup Set Properties) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Set Options - Pre/Post. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Set Options - Exclude Old Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Set Options - Continuous Data Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 94 96 97 98 98
File System Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Step 2. Select the Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Step 5. Specify Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Step 6. Specify Advanced Options (Windows DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Step 7. Specify Backup Set Performance Options (Windows DS-Client) . . . . . . . . . . . . . . . . . . 106 Step 8. Specify Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Step 9. Specify the Retention Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Step 10. Specify the Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Step 11. Name the Backup Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the source for this backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112 112 112 113 113 113

Confidential.
Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Novell NetWare Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 MS SQL Server Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Backup Set Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Exchange Server Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the MS Exchange Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 8. Specify the Backup Set Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 116 116 117 118 119 120 120 121 121 121 122 123 124 124 125 125
Permissions Only Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Step 2. Select the Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Oracle Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify the protocol for dumping the database (Linux DS-Client) . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MySQL Database Backup (Windows DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MySQL Database Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 127 127 127 128 129 130 130 130 131 131 131 131 131 131 132 133 133 133 133 133 133 134
DB2 Database Backup (LINUX DS-Client). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Confidential.
Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the protocol for dumping the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 8. DB2 userexit log path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 9. Specify Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PostgreSQL Database Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-Mail Messages (DS-Recovery Tools) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the E-Mail Server Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Select Directories / E-Mails for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System i Server Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the share & path for the data dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS SharePoint Server (DS-Recovery Tools) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select Items for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VMware Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XenServer Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
135 136 136 136 136 137 138 138 139 139 139 139 139 139 140 141 141 141 142 143 144 145 145 147 147 147 147 148 151 151 152 153 153 153 153 154 154 154 154 154 155 155 156 156 156 156 156 156

Confidential.
Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Lotus Domino Server Database Backup (Windows DS-Client). . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sybase Database Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Database Dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSS-aware backup sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the VSS-aware backup set type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Select Items for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note about Retention Rules for VSS-aware backup sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note about Database Backup Policy for VSS-aware backup sets . . . . . . . . . . . . . . . . . . . . . . . Oracle-SBT Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VMware VADP Backup (LINUX DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup from the Cloud (Salesforce.com). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Select the Backup from the Cloud Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local DS-VDR backup set (VMware VADP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Local DS-VDR Backup Set Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
158 158 158 158 159 159 159 159 159 160 160 160 161 161 161 162 162 162 163 164 164 164 164 164 164 164 166 166 166 166 167 167 167 167 168 168 168 168 169 169 169 170 170 170 171 171

Confidential.
Physical to Virtual backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Choose the kind of backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Backup Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Backup Item Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Backup Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Notification Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172 172 172 173 173 174 174
5 - Backup Set Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Overview of Backup Set Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Statistical Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Self-Contained Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Local-Only Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Converting a Local-Only backup set to a Regular backup set . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Deleting Local-Only backup set data & Clean Local-Only Trash . . . . . . . . . . . . . . . . . . . . . . . . 181
6 - Working with Backup Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

View Backup Set Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Modify Share Access Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Exclude files that failed to backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Modify Database Information (MS SQL Servers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Modify Connection Information (MS Exchange Server and System i Server). . . . . . . . . . . . . . 188 Modify Connection Information (E-Mail backup sets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Modify Connection Options (Linux DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Re-name a Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Suspend and Activate a Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Synchronize a Backup Set's Backup Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Migrate a Backup Set from one computer to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Clone a Backup Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Change Backup Set Ownership. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Backup Set Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
7 - Deleting Backup Sets and Online Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Overview of Delete Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Selective Delete from Online Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Delete Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Delete Individual Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Assisted Delete from Online storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Remove Backup Set from Online Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8 - Demand Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Perform a Demand Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Confidential.
Initial Backup (Premium Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
9 - Restoring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Introduction & Common Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore a Specific File or Files of a Specific Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore only files that differ from those on the backup source volume . . . . . . . . . . . . . . . . . . . Restore an Older Generation of a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre/Post Restore Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore File System Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options (Windows DS-Client). . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Windows System State (Registry) and Services Database. . . . . . . . . . . . . . . . . . . . . . Restore NetWare Servers (Files and NDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Continuous Data Protection Backup Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore MS SQL Server Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Database(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore MS Exchange Server Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Database(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Permissions Only Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore MySQL Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Database(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options (Windows DS-Client). . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore DB2 Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Database(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215 217 219 221 222 223 225 225 225 227 228 229 230 232 233 234 234 234 235 235 236 237 237 237 238 238 238 239 239 239 239 239 241 241 241 241 241 241 242 242 242 242 242
Restore Oracle Server Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Confidential.
Restore PostgreSQL Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Database(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore E-Mail Backups (via DS-Recovery Tools) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore System i Server Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore MS SharePoint Backups (via DS-Recovery Tools) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Lotus Domino Server Database Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Sybase Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore VSS-aware Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the VSS Restore Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore VMware VADP Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the VMware VADP Restore Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
243 243 243 243 243 244 244 244 245 245 245 246 246 246 247 247 247 248 248 248 248 248 248 249 249 249 249 249 249 250 250 250 250 250 251 251 251 252 252 252 253 254 254 254 254 255 256

Confidential.
Restore a Backup from the Cloud (Salesforce.com) Backup Set. . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Select the Restore Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the Restore Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Specify the Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore to an Alternate Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Select the backup set items for restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Choose the destination computer (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Select the destination share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. Specify the path on the destination share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS SQL Server Backup Sets (Alternate Location Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Exchange Server Backup Sets (Alternate Location Restore). . . . . . . . . . . . . . . . . . . . . . . . Oracle Database Backup Sets (Alternate Location Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . VSS-aware Backup Sets (Alternate Location Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VMware VADP Backup Sets (Alternate Location Restore). . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257 257 257 257 257 257 261 261 262 263 264 266 268 270 271 273
Cloud database upload tool (Salesforce.com) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Restore from Disc / Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Restore from BLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Validation of Online Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Perform Validation on Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
10 - Premium Backup and Recovery Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Initial Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Initial Backup Path (Buffer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Initial Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor Initial Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disc/Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Request Disc/Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: View Orders for Disc/Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Restore from Disc/Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Lifecycle Management (BLM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure BLM (per backup set). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create BLM Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Backup Set for BLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Perform BLM Request on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore from BLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 280 281 282 283 283 285 286 289 290 291 291 292 293
Tape Conversion to BLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Conversion Wizard - Tape to BLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 DS-Client Monitoring by the DS-NOC Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure DS-Client to connect to DS-NOC via a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . Auto-detect Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual Proxy Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Proxy Server Configuration URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 300 301 301 302
Local Storage Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Set the Local Storage Path (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Confidential.
Apply the Local Storage Option (per Backup Set) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Restore from Local Storage Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Local Storage Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Multi-Tenant DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Activate the Multi-Tenant feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Create the Customers for this Multi-Tenant DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3. Assign existing backup sets to a customer (Edit backup sets) . . . . . . . . . . . . . . . . . . . . . . . 4. New backup sets for Multi-Tenant DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5. Reports from Multi-Tenant DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Snapshot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetApp License Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Configure the Storage that can be used for Snapshot Transfer . . . . . . . . . . . . . . . . . . . . . . . 2. Configure the Snapshot Retention Policies that can be used for Snapshot Transfer . . . . . . . 3. Configure the Snapshot Schedules that can be used for Snapshot Transfer . . . . . . . . . . . . . 4. Configure a Snapshot Transfer that will be managed by this DS-Client. . . . . . . . . . . . . . . . . What happens when Snapshot Transfer runs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Snapshot Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 307 308 309 310 311 312 312 313 314 315 316 321 321
11 - Logs and System Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Detailed Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Event Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Audit Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Current Activity Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 LAN Storage Discovery Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Share Discovery (Windows DS-Client). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Share Discovery (Linux DS-Client). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Scan Shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Scan Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4. File Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Summary Filtered View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Storage Discovery Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Large Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Share Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generate Reports (one-click reports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unprotected LAN Resource Discovery Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run the Unprotected LAN Resource Discovery (Windows DS-Client) . . . . . . . . . . . . . . . . . . . . Unprotected LAN Resource - Node Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-Mail the results of the last Unprotected LAN Resource scan . . . . . . . . . . . . . . . . . . . . . . . . . Unprotected LAN Resource - Share Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Backup Sets Summary (Unprotected LAN Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 330 332 334 336 337 338 340 340 341 343 344 345 346 347 348 352 353 354 355
Online File Summary Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356


Confidential.
DS-Client Load Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 DS-Client Storage Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 System Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update DS-Client Statistics immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run a Daily Admin immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run a Weekly Admin immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor current connections and processes on the DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . Send messages to users connected to the DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disconnect Network Connections to the DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutdown the DS-Client Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repair the DS-Client Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 362 362 362 363 363 364 364 364
Recover 'Orphaned' backup sets to the DS-Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Recover a Specific Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Recover the DS-Client Database (Disaster Recovery of DS-Client Computer) . . . . . . . . . . . . . 367
12 - Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Print Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Sets Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restorable Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Trends Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/Restore Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Groups Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistical Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Items Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 370 372 374 375 377 379 381 383
Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Backup Sets Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Global Reports (Java DS-User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting DS-Client(s) for a Global Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Export Backup Sets Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup Sets Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Restorable Volume Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup / Restore Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup Groups Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Backup Items Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Report - Statistical Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Create Customized Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Create Customized Report (with Third-Party application) . . . . . . . . . . . . . . . . . . . . . . . Step 3. View Customized Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 386 389 389 389 389 390 390 390 390 391 392 392 395 396
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
DS-Client Knowledge Base Contents . . . . . . . . . . . . . . . . . . . . . . . . . 403


Confidential.
Knowledge Base: SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Ports used in Asigra Cloud Backup applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Resolving port conflicts for the DS-Client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Running DS-Client using PostgreSQL database on Mac OS X with Apple Remote Desktop (ARD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Configuring DS-Client with Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Windows XP Service Pack 2 changes that affect the Asigra Cloud Backup Product. . . . . . 410 DS-Client Configuration File (Linux / Mac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 DS-Client Database (Maintenance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 DS-Client Database Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 DS-Client Database Migration (from MSDE to SQL Server 2005/2008 Express) . . . . . . . . . . . . 415 DS-Client Database Migration (from SQL Server Express version to SQL Server FULL version) 417 DS-Client Database Size (PostgreSQL 8.2.4 and below) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 DS-Client Database (Automatic Expansion) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 DS-Client Service Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 DS-Client under heavy processing loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Grid DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 DS-MLR Installation & Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Setting up DS-Client Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Setting up the Novell NetWare Client on the DS-Client computer . . . . . . . . . . . . . . . . . . . . . . . 442 Snapshot Transfer Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Troubleshooting: DS-Client Workaround for Mac OS X (10.6 Snow Leopard) Auto-Mount Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Knowledge Base: SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Digital Signature Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 DS-Client Encryption Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 DS-Client to DS-System Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Logon Impersonation and Integrated Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 User Rights and Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Encrypting your Network Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Logon using security context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Knowledge Base: ADMINISTRATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

DS-Client Advanced Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Access to DS-Client & Remote Management of DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Activity, Event and Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Confidential.
Administrative Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Weekly Admin and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Admin Processes with Grid DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Backup Set Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 When to Migrate a Backup Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 DS-Client Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 DS-Client performance considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 LAN Storage Discovery Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 LAN Storage Discovery considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 Load and Storage Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 Retention Rules vs. Maximum # of Online Generations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 Retention Rule Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Retention Rule combinations (multiple rule types) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Delete Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 Scheduled Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 Validation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Local Storage Cache Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Knowledge Base: BACKUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

Backup Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 Best Practices: Initial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Backing up Windows for Bare Metal Restore (BMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 Backup of Windows System State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 Backup of Windows Encrypted Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 Backup / Restore of UNIX File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539 Backup of NetWare Servers (DOS Partition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Backup / Restore of Novell NetWare files from a Windows DS-Client . . . . . . . . . . . . . . . . . . . . 542 Backup / Restore of Novell NetWare files from a Linux DS-Client . . . . . . . . . . . . . . . . . . . . . . . 544 Backup of Open Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 Backup using Microsoft VSS (Volume Shadow Copies) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 Backup / Restore of Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Backup / Restore of Microsoft Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 Troubleshooting: Microsoft Exchange Server Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Backup / Restore of Microsoft Exchange Server 2010 in DAG (Database Availability Group) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Backup / Restore of Microsoft SQL Server (ALL VERSIONS). . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Backup / Restore of Microsoft SQL Server with less privileged users . . . . . . . . . . . . . . . . . . . 565 Troubleshooting: Backup of Microsoft SQL Server 2000 Desktop Engine . . . . . . . . . . . . . . . . 567 Troubleshooting: Backup of Microsoft SQL Server 2005 (and up) and SQL Server 2005 Express

Confidential.
(and up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Backup / Restore using UNIX-SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Backup / Restore of NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Backup / Restore of Oracle Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Choosing the User for Oracle Backup / Restore Operations via SSH Dump . . . . . . . . . . . . . . 581 Troubleshooting: Oracle Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Backup / Restore of MySQL Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Backup / Restore of DB2 Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Backup / Restore of PostgreSQL Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590 Backup / Restore of Windows 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Backup / Restore of Windows 2008. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 Backup / Restore of E-Mails (using DS-MLR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 Backup Comparison: Microsoft Exchange Server vs. Message Level Restore . . . . . . . . . . . . 609 Backup / Restore of System i Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610 Backup / Restore of Virtual Machines using Windows DS-Client and VCB . . . . . . . . . . . . . . . 616 Backup / Restore of VMware (at Virtual Machine-level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 VMware Backup / Restore Process Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621 VMware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Backup / Restore of XenServer (at Virtual Machine-level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 Backup / Restore of MS SharePoint 2007 Servers (DS-Recovery Tools). . . . . . . . . . . . . . . . . . 627 Backup / Restore of Lotus Domino Server Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631 Backup / Restore of Sybase (Database-Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Backup / Restore of Oracle-SBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Backup / Restore of VMware VADP backup sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 Backup / Restore of Microsoft SQL Server (VSS-aware backup sets) . . . . . . . . . . . . . . . . . . . . 638 Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) . . . . . . . . . . . . . . . 640 Backup / Restore of Hyper-V (VSS-aware backup sets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 Backup / Restore of Microsoft SharePoint 2007 (VSS-aware backup sets). . . . . . . . . . . . . . . . 649 Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets). . . . . . . . . . . . . . . . 655 Backup / Restore of NAS (Linux DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666 Backup / Restore of NAS (Windows DS-Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669 Backup from the Cloud (Salesforce.com) Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 Local DS-VDR backup set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673 Physical-to-Virtual backup set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675 Block-Level Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676 Continuous Data Protection (Backup Set Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 Memory Requirements for DS-Client During Incremental Backup Using Delta Algorithm . . . 682 Stop Backup (DS-User Initiated) behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683

Confidential.
Troubleshooting: Tape Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684 Troubleshooting: Failure to backup of files from Windows 2008 / Windows 7 / Windows 8 . . 685
Knowledge Base: RESTORE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686

Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery) . . 687 Alternate Location Restore of Microsoft Exchange Server 2007 (mailbox recovery) . . . . . . . 689 Restoring Microsoft Exchange 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691 Bare Metal Restore of Windows (ALL VERSIONS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Bare Metal Restore of Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 Bare Metal Restore of SBS 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702 Bare Metal Restore of Windows 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705 Bare Metal Restore of SBS 2011 Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706 Important Notes for Bare Metal Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 Restoring Files from a specific time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708 Restoring MS SQL Server Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Restoring Locked Files on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Restoring NetWare Servers (5.1 and higher with NDS 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Troubleshooting: Full Server (file system and registry) restores . . . . . . . . . . . . . . . . . . . . . . . 715
Knowledge Base: RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

Disaster Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Recovering the DS-Client Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Recovering 'Orphaned' Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Restoring the MS SQL Database Server MASTER Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Oracle Database Point-In-Time Recovery (DBPITR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
DS-User F1 Help for GUI (Context-Sensitive) Contents . . . . . . . . . . 735

F1 (Context-Sensitive) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736


Confidential.
1 - Introduction
1 - Introduction
This section provides an overview of Asigra Cloud Backup, and a general introduction to the DS-User interface.


Confidential.
1 - Introduction
Document Revision History Table

This shows the major changes made to this document from version to version.
Version/Date Notes 1 - Introduction Running DS-User and Connecting to a DS-Client on page 26 2 - Setup and Configuration Configure the E-Mail Notification Setup on page 36 Export DS-Client configuration to XML on page 48 View Quotas on page 57 3 - Schedules and Retention Rules 4 - Creating and Modifying Backup Sets System i Server Backup on page 147 Backup from the Cloud (Salesforce.com) on page 167 Local DS-VDR backup set (VMware VADP) on page 169 Physical to Virtual backup set on page 172 5 - Backup Set Types 6 - Working with Backup Sets 7 - Deleting Backup Sets and Online Files 8 - Demand Backups 9 - Restoring Backups Restore VSS-aware Backups on page 251 Restore a Backup from the Cloud (Salesforce.com) Backup Set on page 257 Cloud database upload tool (Salesforce.com) on page 258 10 - Premium Backup and Recovery Services Snapshot Manager on page 312 11 - Logs and System Tools 12 - Reports Print Reports on page 369 Knowledge Base: SETUP Ports used in Asigra Cloud Backup applications on page 405 DS-Client Database Migration (from SQL Server Express version to SQL Server FULL version) on page 417 DS-MLR Installation & Setup on page 434 Snapshot Transfer Issues on page 443
v12.0 [Revision Date: October 15, 2012]


Confidential.
1 - Introduction
Knowledge Base: SECURITY Knowledge Base: ADMINISTRATION DS-Client Advanced Configurations on page 458 Knowledge Base: BACKUP Backup / Restore of UNIX File Systems on page 539 Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560 Troubleshooting: Backup of Microsoft SQL Server 2005 (and up) and SQL Server 2005 Express (and up) on page 568 Backup / Restore of Oracle Database Servers on page 573 Backup / Restore of PostgreSQL Database Servers on page 590 Backup / Restore of Windows 2000 on page 592 Backup / Restore of Windows 2008 on page 596 Backup / Restore of E-Mails (using DS-MLR) on page 599 Backup / Restore of MS SharePoint 2007 Servers (DS-Recovery Tools) on page 627 Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) on page 640 Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets) on page 655 Backup / Restore of NAS (Linux DS-Client) on page 666 Backup / Restore of NAS (Windows DS-Client) on page 669 Backup from the Cloud (Salesforce.com) Limitations on page 671 Local DS-VDR backup set on page 673 Physical-to-Virtual backup set on page 675 Troubleshooting: Failure to backup of files from Windows 2008 / Windows 7 / Windows 8 on page 685 Knowledge Base: RESTORE Knowledge Base: RECOVERY Restoring the MS SQL Database Server MASTER Database on page 722


Confidential.
1 - Introduction
Overview
What Is Asigra Cloud Backup?

Asigra Cloud Backup is a service that gives you state-of-the-art data protection at an affordable price. Data from your server(s) is backed up through the DS-Client, and sent through an IP WAN connection to an off-site data vault. Ease of use comes from the 'agentless' architecture: you only need to install the DS-Client on one LAN computer (thereby eliminating the need to install software on each target backup/restore computer). As long as that computer is networked with the target backup/restore computers, you will be able to browse data, back it up, and restore it as required. Asigra Cloud Backup offers users the advantage of automatic and unattended backups for data environments ranging from single-user standalone PCs through to enterprise-wide Local/Wide Area Networks. During backups, the DS-Client extracts, compresses, and encrypts the items you specify for backup. Only new or modified data is backed up, thereby accelerating the backup transmission time. The backup data is sent via the Cloud (Internet, Intranet) to the secure, off-site Data Center that hosts the DS-System Vault. Restores are performed on demand, via the same DS-Client installation, once the DS-Client's security measures have been cleared.


Confidential.
1 - Introduction
How It Works: Major Asigra Cloud Backup Components

This is an overview of the major components of Asigra Cloud Backup from the perspective of end-users who are protecting their data.
DS-User
Application dsuser.jar DSUser.exe (Win32 only) userhelp.jar (Java only) dsuser.chm (Win32 only) Description This is the user interface to the DS-Client service/daemon program referred to as DS-User. The JAVA version is dsuser.jar and the Win32 version is DSUser.exe. You must run DS-User, in order to configure DS-Client (e.g. create backup sets, perform backups or restores, view logs, etc.). Online help. Online help.


Confidential.
1 - Introduction
DS-Client
Application dsclient.exe DSConfig.exe dsstatus.exe Description (Windows) This is the service program. This program runs the portions of the installation that require you to specify the account number, DS-Client number, DS-System IP Address, the IP Address of the DS-Clients in a Grid, Encryption Keys or the DS-Client Service Account. The DS-Client Service Manager Program allows you to stop and start the DS-Client service (without having to open the Control Panel > Services folder).
In the DS-Client program files directory, there is a sub-folder called db, which includes the database patches that were applied during installation / upgrade of the DS-Client software. The DS-Client databases contain the backup set specifications, backup schedule settings, data usage statistics, logs, information about files and directories, generations that have dsclient databases been backed up, retention rules, data expiration rules, etc. They can be backed up during the daily or weekly admin processes to ensure quick recovery of the DS-Client computer, in case of disaster. MS SQL Server 2005 and up or MS SQL Server 2005/2008 Express: db folder contains the SQL scripts run by the DS-Client Setup application. Application unixdsclient dsclient.sh Description (Linux / Mac) This is the daemon program. This is the startup / shutdown script for the DS-Client daemon.
The DS-Client databases contain the backup set specifications, backup schedules settings, data usage statistics, logs, information about files and directories, generations that have been backed up, retention rules, data expiration rules, etc. They can be backed up during dsclient databases the daily or weekly admin processes to ensure quick recovery of the DS-Client computer, in case of disaster. DS-Client databases may reside on PostgreSQL database instances. dsclient DB scripts userhelp.jar In the DS-Client installation directory, there are *.sql files which represent the database patches that were applied during the installation / upgrade of the DS-Client software. Online help.
Main DS-Client Features

Refer to your Service Provider's list of features. These are subject to change without notice.
Backup/Restore Data Transfer Rate

The data transfer rate is dependent on the User's communications infrastructure. Communication may be over a public network, or through a direct LAN connection with the DS-System. Examples of connections include LAN (10 GbE, 1 GbE, 100 Base-T or 10 Base-T), ATM, FDDI, ISDN (PRI, T1, or BRI), Modem, DSL, Frame Relay, etc. Check with your Asigra Cloud Backup Service Provider to find out which connections are supported in your service area. Please note that the data transfer rate also depends on the file type and the compression ratio achieved on the file.


Confidential.
1 - Introduction
DS-User Screen
To access functions, you can select from the menu options found directly below the title bar, in the DS-User screen:
List of DS-Clients to which you can connect Backup Sets Tab Backup Schedules Tab
Retention Rules Tab
Menus
Connected DS-Client
The Monitor section shows current activities on the DS-Client
DS-Client Connection List: Shows a list of the available DS-Clients you can connect with on the LAN. You can connect to more than one DS-Client, however you may view only one at a time (by highlighting it from this list). Title Bar: Shows the name of the DS-Client computer that you are using. You can connect to more than one DS-Client from the Connection List at left (if available on the network). Menu Bar Items: Items here allow you to perform the various tasks necessary to backup and restore files, as well as manage and administer the DS-Client. The menu bar consists of the Sets, Backup, Restore, Initial Backup, Schedule, Retention, Logs, Grid, Tools, Reports, Setup, and Help menus. Backup Set Tab: Shows a Windows Explorer-like tree structure, containing all of the backup sets that have been defined on the DS-Client. You can browse the tree to select the backup set that you want to work with, then Right-click to open the available options menu. Backup Schedules Tab: Shows a tree view of all the schedules defined on the DS-Client. You can browse the tree to select the schedule that you want to work with, then Right-click to open the available options menu. You can reassign backup sets to different schedules using the "drag-and-drop" functionality.
Confidential.

1 - Introduction
Retention Rules Tab: Shows a tree view of all the Retention Rules defined on the DS-Client. You can browse the tree to select the Retention Rule that you want to work with, then Right-click to open the available options menu. You can reassign backup sets to different Retention Rules using the "drag-and-drop" functionality. Status Bar: This section may display basic instructions about the highlighted/ active option. Monitor: Shows the current activities running on the DS-Client (backup, restore, admin, etc.). Tool Bar Icons: Icons allow quick access to the most commonly used features.
Icon Function Create new backup sets with the New Backup Set Wizard.
Perform a Demand Backup.
Restore files with the Restore Now Wizard.
Opens the Schedule.
Opens the Activity Log.
Help


Confidential.
1 - Introduction
Running DS-User and Connecting to a DS-Client

1. Windows DS-Client: Start > All Programs > Asigra DS-Client | DS-User > DS-User. Linux DS-Client: Application > Asigra DS-Client | DS-User > DS-User. 2. If using a Java DS-User, a DS-Client List appears on the left-side of the GUI. From the DS-Client List, select a DS-Client by checking the box.
If the DS-Client you want does not appear, you may have to add it to the initialization list. See: DS-User Initialization > Connection on page 63. Right-click in the list to switch between a list of computer names and a list of IP addresses. Color codes for DS-Clients that appear in this list:
Color BLUE BLACK GREEN LIGHT BLUE BROWN AQUA RED RGB values (0, 0, 255) (0, 0, 0) (0, 153, 0) Meaning DS-Client running on the local machine where this DS-User is installed. (Supersedes other colors. Only one can appear, which helps you to quickly locate it if the list is long.) FullFeatured DS-Client (Windows / Linux / Mac) Un-initialized DS-Client (Linux / Mac) See Initial DS-Client Configuration on page 28. Consumer DS-Client (Windows) Service is not running.
(40, 120, 220) Mobile DS-Client (Windows) (150, 90, 60) (255, 0, 0) (20, 170, 170) Notebook DS-Client (Mac)
If using a Win32 DS-User, you select from the Server List in the Connect to DSClient Service screen .


Confidential.
1 - Introduction
3. The Connect to DS-Client Service screen appears.
F1 Help: See Connect to DS-Client Service screen on page 757. 4. Select the Protocol and enter your Credentials Encrypted: All the data between the GUI and the Service will be encrypted with a random encryption key at every connection. Standard: This option is only offered for backwards compatibility with old service/daemon versions that do not have this feature. 5. Click Connect. A popup appears if the (Linux / Mac) DS-Client is unregistered. (See Initial DS-Client Configuration on page 28.) On successful connection, the DS-User screen appears (See DS-User Screen on page 24.).


Confidential.
1 - Introduction
Initial DS-Client Configuration

[Linux / Mac DS-Clients only.] 1. On connection to a Linux / Mac DS-Client that has not registered with the DS-System, the Initial DS-Client Configuration screen will popup for you to enter this information. You can also access this screen for a registered DS-Client from the DS-Client Configuration Setup Tab screen (Setup Menu > Configuration). 2. To set or modify the DS-Client Configuration:
F1 Help: See Initial DS-Client Configuration / Modify DS-Client Configuration on page 786. 3. In the Customer Registration Info section, enter the following:
Customer Name Account # DS-Client # Enter a descriptive name for this DS-Client. This name appears in brackets after the computer name in the Java DS-User GUIs list of available DS-Client computers (when sorted by Name). Enter your Account number. This number is provided to you by your Service Provider. Enter your DS-Client number. This number is provided to you by your Service Provider.
Browse: An alternative to manually entering the above information is to use a .CRI file supplied by your Service Provider. Click Browse to search for this file on your network. 4. In the DS-System Info section, specify the DS-System connection information. You received the IP address of the DS-System from your Service Provider. The DS-Client


Confidential.
1 - Introduction
requires this address in order for it to connect to the DS-System. In the Address field: Enter the IP address of the DS-System your DS-Client will be using and click Add. Your Service Provider may have more than one IP address for the DS-System, if this is the case you can specify any or all of them. 5. In the Encryption Keys section, you must set the encryption key(s) that the DS-Client will use.
Encryption Keys An encryption key is case sensitive. Its length (in characters) depends on the type and level of encryption selected. DES requires 8 characters, AES-128 requires 16 characters, AES-192 requires 24 characters, and AES-256 requires 32 characters. For better security, do not use dictionary words or proper names, and try to randomly mix numbers in with the letters. Auto-complete feature: If you do not specify the full amount of characters in the Key field, the GUI will fill in the remainder by repeating the string of characters you have entered. (e.g. entering 123 with AES-128 will generate an encryption key of 1231231231231231, or entering a for DES will generate the encryption key aaaaaaaa). Keep the key(s) in a secure location. Your ability to select the same encryption type and reenter the same key is necessary if you ever need to reinstall your DS-Client to a new computer (e.g. if the computer is destroyed in a disaster). You must set a private key for this DS-Client. Backup data from your DS-Client installation will be encrypted with this key. Type: Select from the available types. Stronger encryption requires longer keys. Key: Enter the key. Confirm: Re-enter the key to verify the string is correct. You cannot change this key once it is set. You must set an account key if more than one DS-Client belongs to your customer account. Common backup data from all your DS-Client installations will be encrypted with this key. Once the account key is set, all DS-Clients from this customer must be configured with that same account key. Type: Select from the available types. Stronger encryption requires longer keys. Key: Enter the key. Confirm: Re-enter the key to verify the string is correct. You cannot change this key once it is set.
Private Key
Account Key
Allow encryption key forwarding to DS-System Check to have DS-Client forward the encryption key(s) to the DS-System the first time it connects with DS-System. NOTE: If you forward the keys, they will remain encrypted on the DS-System. However, your Service Provider will be able to create a valid .CRI file containing the encrypted keys. This file will be able to recreate a working version of this DS-Client. Make sure this conforms to your security policies before enabling this option.
6. Once you have made all the initial DS-Client configurations, click OK to register with the DS-System. If registration is successful, you will be able to use DS-Client immediately.


Confidential.
2 - Setup and Configuration
This section provides information about setup and configuration of the DS-Client and DS-User software.


Confidential.
Change the DS-Client Configuration

Administrators may need to edit some default configurations and settings for the DS-Client. Most default configuration settings are established during Installation. The following briefly describe the DS-Client Configuration screen tabs: Setup: View the DS-Client setup information. - Re-register the DS-Client with the DS-System. - Enable Encryption Key forwarding to DS-System, delete any keys that have already been sent, and resent encryption keys. Defaults: Set and change Defaults that will apply to new Backup Sets. Notification: Set and change the DS-Client Notification setup for E-Mail and Pager notifications. SNMP: Configure DS-Client to work with SNMP to send traps. (You need to have SNMP management software installed if you wish to receive and handle the trap information). Parameters: Set and change the administrative Parameters for the DSClient. These include: - setting the Daily Admin process start time. - setting the Weekly Admin process start time. - setting database backup options. - setting the time interval to keep saved DS-Client logs. - setting the time interval to keep saved Detailed logs. - specifying the reconnection defaults for backups. - specifying the Buffer directory path, where database dumps and Use Buffer (backup and restore) dumps will be temporarily stored. - specifying the default Local Storage directory path, where backup data will be stored locally to the DS-Client LAN (configurable per backup set). Connections: Edit the settings the DS-Client uses to connect to the DSSystem. Roles: Specify User / Group access on DS-Client. Advanced: Specify Advanced DS-Client options.


Confidential.
View the DS-Client Setup Information

Use the Setup Tab to view the information input during the installation of the DS-Client. Once set, these settings should not be changed. 1. Setup menu > Configuration. The DS-Client Configuration screen appears on the Setup tab.
F1 Help: See DS-Client Configuration Setup Tab screen on page 769. 2. Options available from this tab: Modify DS-Client Configuration (Linux / Mac DS-Client): Same as Initial DS-Client Configuration on page 28 Re-register the DS-Client with the DS-System on page 33 Encryption Key Safeguarding at the DS-System on page 33


Confidential.
Re-register the DS-Client with the DS-System

In order to provide an extra level of security, the DS-Client is automatically registered with the DSSystem during the first activity that requires connection. See the Registration Layer section of the DS-Client to DS-System Authentication Knowledge Base Article (See DS-Client to DS-System Authentication on page 450.). THE ONLY SITUATION where you must re-register the DS-Client is if: The DS-Client computer's hardware or operating system is replaced (or the DS-Client has been installed on a new machine). To re-register your DS-Client: 1. Your Service Provider must permit re-registration with the DS-System. Arrange a time with your Service Provider when you will perform the Registration process. Your Provider will open a registration window (approx. 5 minutes) for you to complete the re-registration. 2. Setup menu > Configuration. The DS-Client Configuration screen appears on the Setup Tab. 3. Click Register Now. 4. A confirmation screen appears. 5. Click Yes. 6. A message will appear informing you that registration was either successful, or that some error occurred and the reason why.
Encryption Key Safeguarding at the DS-System

Encryption Key Safeguarding is an additional security provision that can be enabled from the DSSystem. Forwarding the key(s) will send an encrypted copy of the key(s) for storage in the DSSystems database. Your Service Provider will not be able to read your Encryption Key(s), but will be able to create a Customer Registration Information (.CRI) file with them embedded for distribution. This means anyone who has the .CRI file can recreate a functioning DS-Client that will be able to perform backups and restores to the corresponding account on the DS-System. Therefore, you should determine your own policy on Encryption Key Safeguarding, and consult your Service Provider if you have any questions. If your Service Provider enforces mandatory safeguarding, the DS-Client will not be able to connect to DS-System until you enable the option. To enable Safeguarding of your DS-Clients encryption key(s): 1. Setup menu > Configuration. The DS-Client Configuration screen appears on the Setup Tab. 2. Click Enable encryption key forwarding to DS-System. 3. Click Apply. To forward or delete the encryption keys from the DS-System database: 1. Setup menu > Configuration. The DS-Client Configuration screen appears on the Setup Tab. 2. In the Encryption key safeguard section: Click Forward Now or Request Deletion. 3. The screen will update to indicate if the key(s) are Forwarded or Not Forwarded.


Confidential.
Configure the Default Options (for Backup Sets)

Use the Defaults Tab to configure the default settings that will appear in the New Backup Set Wizard. The Default Options affect all backup sets created after the defaults are set. The default selections will appear for all new backup sets (however you may change the settings individually). If you wish to change the settings of older backup sets, you must modify each older set's settings individually (see the Backup Options Section). 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Defaults to bring it to the front.
F1 Help: See DS-Client Configuration Defaults Tab screen on page 764. 3. In the Generations setup section, select the default number of generations for new backup sets. Optional: You can select a default Retention Rule for new backup sets (See About Retention Rules on page 85.) 4. In the Backup options section, select the default options for new backup sets. 5. In the Open files section, specify the options for how the backup set handles open files (in use by other applications) encountered during backup. Note: If the file(s) are locked by the other application, they will not be backed up (unless the backup is using VSS). An error will appear in the activity log if the files are not backed up. To backup locked files, you must enable the VSS option for the backup set (See: Backup of Open Files Knowledge Base article - Backup of Open Files on page 546).
6. In the Backup schedule section, select the default options for new backup sets.

Confidential.
7. In the Notification section, select the default notification options for new backup sets by clicking Add / Modify: In the Add / Edit Notification screen, you select the notification type, recipient, and event that triggers notification.
F1 Help: See Add Notification screen on page 742. Click OK to save the notification setting. Note: The E-Mail and Pager fields will be grayed out if the DS-Client has not been configured for E-Mail notification (For more information, see Configure the E-Mail Notification Setup on page 36). 8. In the Data Compression section, select the default compression type for new backup sets. 9. Click OK to save the changes.


Confidential.
Configure the E-Mail Notification Setup

Use the Notification Tab to configure the DS-Client to send notifications. For information on setting up the DS-Client computer for E-Mail notifications, see the Setting up DS-Client Notifications Knowledge Base article - Setting up DS-Client Notifications on page 438. For MAPI Only: This requires Microsoft Outlook on the DS-Client computer. DS-Client notifications (specified in backup set properties) are E-Mail reports or pager alerts that may be sent to the Administrator at the end of a backup session or, on a regular basis during Admin processes. If the DS-Client Messaging Profile section is empty, the E-Mail options will be hidden when creating new Backup Sets or reviewing Backup Set Properties. 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Notification to bring it to the front.
F1 Help: See DS-Client Configuration Notification Tab screen on page 765. 3. In the Outgoing E-Mail settings section, select: - None


Confidential.
- SMTP: In the SMTP Server Settings section that appears, click [...] to open the SMTP Settings screen:
4.
5. 6. 7. 8.
F1 Help: See SMTP settings on page 879. Enter the DNS name or IP address of the SMTP Server the DS-Client will use. Select the Port Enter any authentication information (if required) Note: The DS-Client will use its existing network connection when sending SMTP notifications. Click OK to save the settings. The Notification Settings screen returns. Enter the E-Mail address you want to appear in the E-Mail headers From field. Enter the Display Name (if any) you want to appear in the E-Mail headers From field. - MAPI: In the DS-Client messaging profile section that appears, select the MAPI profile to use. In the E-Mail notification subject section, enter the information. You can enter your own text in combination with optional placeholder variables. Refer to the F1 Help for details about these placeholders (See DS-Client Configuration Notification Tab screen on page 765.). In the Administrator Notification Setup section, enter the information. In the Daily / Weekly Admin setup section, select the settings you want. Click OK to save the changes. (MAPI only) After you change the profile, you must stop and restart the DS-Client Service (Start > All Programs > Asigra DS-Client > DS-Client Service Manager) for the new setting to take effect.


Confidential.
Configure the SNMP Settings

For more information on SNMP see the Windows Help. Use the SNMP Tab to configure DS-Client to work with SNMP to send traps. (You need to have SNMP management software installed if you wish to receive and handle the trap information). Note: Load the asigra.mib file (found in the DS-Client installation directory) with your SNMP software to receive the traps sent by DS-Client. See the SNMP Knowledge Base article SNMP Notification on page 440.
1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click SNMP.
3. 4. 5. 6. 7. 8. 9.
F1 Help: See DS-Client Configuration SNMP Tab screen on page 769. In the Community field, enter a name and Click Add to list. Under the Destination host list, click Add. The Add host name or IP address screen appears. F1 Help: See Add / Modify address screen on page 739. Enter a host name or IP address from your network and click OK. Continue to add as many destination host / IP addresses as are in the community. Check the Send traps as heartbeats every [], to send traps as heartbeats. Select the frequency of heartbeats from the dropdown list. Click OK to save these settings.
Confidential.

Configure the DS-Client Parameters

Use the Parameters Tab to view and change certain key processes and options for your DS-Client. The top two sections of this screen allow you set the retention period for various database logs, and the frequency of DS-Client Database backups. The Backup options section lets you configure how the DS-Client handles connection failures between the DS-Client and DS-System. The bottom section of this screen deals with the local temporary storage location (for Use Buffer data dumps and Registry/Database dumps) on the DS-Client computer and with the local storage location on the DS-Client LAN. 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Parameters.
F1 Help: See DS-Client Configuration Parameters Tab screen on page 767. 3. In the Admin Process section, you can specify when and how the daily and weekly administrative tasks are performed. 4. In the Database options section, you can specify the frequency of DS-Client database backups, how to handle the database dump file (if applicable), and how long to keep logs. 5. In the Backup options section, you may specify reconnection options. These are used if the DS-Client loses connection with the DS-System during a backup. Note: This applies to Scheduled and On-demand backups. By default, DS-Client is configured to skip running a pre-scan on scheduled backup sets (this makes the process faster). Disabling this option will force a pre-scan for all scheduled backup sets, which allows the Process Window to show an estimated completion time for each backup.


Confidential.
6. In the DS-Client Buffer field, specify the local disk location that DS-Client will use to save Use Buffer dumps and its own Database dumps (from Daily/Weekly Admin activities). The DS-Clients database server (e.g. MS SQL) must have rights to dump to this location. This is an important consideration if you are using a remote database. For more information, see the Knowledge Base Article: DS-Client Buffer on page 500. 7. In the Local Storage Path field, enter a path to enable the following features that send data to a local storage location (instead of, or in addition to backup to the DS-System). Self-Contained Backup Sets: If you enter a path, you will be able to select this type of backup set on the last screen of the New Backup Set Wizard. (See Self-Contained Backup Sets on page 178.) Local Only Backup Sets: Your Service Provider must enable the Local-Only Capacity tool and assign a maximum storage amount for this DS-Client. (See Local-Only Backup Sets on page 179.) Local Storage Backup Sets: Your Service Provider must enable the Local Storage tool for this DS-Client. (See Local Storage Tool on page 303.) IMPORTANT NOTE: Backup sets that use any local storage location require an extra table in the DS-Client database in order to manage the data stored on the DS-Client side. Make sure enough space is allocated for the DS-Client database when using any feature that requires a local storage path. 8. Click OK to save the changes to this tab.


Confidential.
Edit the Settings for DS-System Access

Use the Connections Tab to view and change the setup used by DS-Client to connect with the DSSystem. The initial settings are made during the DS-Client Installation. Your Service Provider will supply you with the address(es) you must use. To add a new Connection entry: 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Connections.
F1 Help: See DS-Client Configuration Connections Tab screen on page 764. Note: There can only be one Primary Connection. All other entries in the DS-System connection setup list are alternate methods to connect in case the Primary Connection fails. DSClient will return to the Primary Connection based on the RetryPrimary parameter in the DS-Client Advanced Configurations (Setup Menu > Configuration > Advanced Tab).


Confidential.
3. Click Add. The Add DS-System connection entry screen appears.
F1 Help: See Add / Modify DS-System connection entry screen on page 741. 4. Click Add. A screen appears for you to enter an address (IP or DNS). 5. Repeat step 4 for as many addresses as you have been provided. Pre/Post: You can configure each DS-System connection entry to perform pre and post commands. This can help in some network situations, like dealing with firewalls. 6. Optionally (for Backup from the Cloud Salesforce.com backup sets only), you can configure the DS-Client to use a proxy server to access the Internet when connecting to the Salesforce.com site. Use a proxy server to access Internet: Select to enable this option. Address: Enter the address (DNS name or IP address) of the proxy server that the DS-Client will use. Port: You must specify the port that will be used to connect to the proxy server. (By default, this is port 80.) 7. When finished, Click OK to save the connection entry in the Connections Tab. 8. Click OK to save the DS-Client Configuration.


Confidential.
Configure DS-Client User and Group Roles

Use the Roles Tab to view and change the DS-Client User / Group Roles. Each time a user attempts to log in to DS-Client, the account will be checked against Roles. When more than one role applies, the role with the greater rights will apply. Standalone PC users should connect to their DS-Client as local Administrators (or a user with administrator privileges). Users and Groups can be assigned one of the following Roles: DS-Client Administrator: Users and groups assigned this Role will have Administrator rights (See Administrator Rights on page 44.). For Windows DS-Clients, the local Windows Administrators group is assigned to this role by default (you cannot remove this group from the Administrator role).
For Linux/Mac DS-Clients, this role includes the local root user (you cannot remove this user from the Administrator role). DS-Client Backup Operator: Users and groups assigned this Role will have Backup Operator rights (See Backup Operator Rights on page 44.). For Windows DS-Clients, the local Windows Backup Operators group is assigned to this role by default. DS-Client Regular User: Users and groups assigned this Role will have Regular User rights (See Regular User Rights on page 43.).
Each type of user has the right to perform the following tasks:
Regular User Rights

Note: The right to perform a task is different from the permission to access a particular backup set. For users with the Regular User Role, even if you have the right to perform a task, you must also have permission to the backup set in question. By default, only the creator / owner and administrators have permissions to a backup set. For more information on individual backup set permissions, see Backup Set Permissions on page 199.
Regular users have the following rights on the DS-Client: Create File System backup sets Create special backup sets (MS SQL Server, MS Exchange, etc.) View the list of backup sets (to which they have permission) Modify backup sets (Items, Options, Advanced Options, Set Info, Schedule, Share, Retention, Connection, etc.) Backup a set on demand Restore backup sets Restore from a Disc/Tape Request BLM and Restore from a BLM Restorable Image Remove backup sets Selective Delete of backed up files from Online storage Enforce Retention on a backup set Suspend/Activate backup sets Synchronize backup sets Clone backup sets Migrate backup sets View and print reports (except for Backup Groups, Load Summary and Storage Summary)

Confidential.
View Quotas View the Activity Log View the Event Log (from Activity Log or Current Activity Monitor only) Convert Local-Only backup sets to regular backup sets View the DS-Client Info (Help Menu)
Backup Operator Rights

Backup Operators have all the functions and access of Regular Users plus the following: View the list of all backup sets Perform a Demand Backup on all backup sets Specify Notification options Synchronize all backup sets Create Initial Backup Sets Perform a BLM Request for all backup sets Create and modify Backup Schedules View the Backup Groups Report View the Load Summary View the Storage Summary Recover orphaned backup sets Use the System Status utility Send messages to connected users Disconnect users from the DS-Client Initiate Daily or Weekly Admin. Process runs on demand Disable/Enable Scheduled Activities Disable/Enable Demand Activities View the Audit Trail View the Event Log View the DS-Client Configuration Clean Local-Only Trash View DS-NOC Settings & set DS-NOC Proxy Server Settings
Administrator Rights
Administrators have all the functions and access of Backup Operators plus the following: Administrators have full access to all of the DS-User tools and features. Administrators can view all information on all activities recorded in the DS-Client logs. Full access (backup, restore, delete, migrate, permissions, etc.) to all backup sets Request a Disc/Tape Set and change user and group access rights to backup sets: Set Maximum Online Amount for Users and/or Groups View Users belonging to a Group and/or Groups to which a User belongs Change backup set owner Re-register the DS-Client with the DS-System (coordinated with your Asigra Cloud Backup Service Provider) Repair the DS-Client Database (disaster recovery) Shut Down the DS-Client computer Change DS-Client default configurations

Confidential.
Add / remove permissions for a backup set to other users and groups Perform Validation Migrate the backup share/path of your backup set to a different share/path LAN Discovery LAN Unprotected Resource Discovery DS-Client and Encryption Setup Notification Setup Connections (to DS-System) Roles Bandwidth Throttle System Activities Administration Export to XML Event Filter


Confidential.
To add a new Role Setting: 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Roles.
F1 Help: See DS-Client Configuration Roles Tab screen on page 768. 3. Click Add or highlight an entry and click Modify. The New / Edit User / Group Role screen appears. F1 Help: See New / Edit User / Group Role on page 792. 4. Specify User or Group 5. Edit the User or Group name. 6. Specify the computer or domain where the DS-Client will verify the User or Group credentials. 7. Select the DS-Client Role for the User or Group. 8. Click OK.


Confidential.
DS-Client Advanced Configurations

By default, DS-Client is optimized for maximum performance under most conditions. For customers who know their backup data very well, there are some further configurations available that can improve performance. Use the Advanced Tab to view and change Advanced Parameters for your DS-Client. Windows DS-Client: Parameters correspond entries in the DS-Client database or DS-Client computers Registry. UNIX DS-Client (Linux / MAC): Parameters correspond to entries in the dsclient.cfg file. For details about each parameter, see the Knowledge Base Article DS-Client Advanced Configurations on page 458. 1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Advanced.
F1 Help: See DS-Client Configuration Advanced Tab screen on page 763. 3. Parameter names can be selected from the Name drop down list. The current parameter value (or the default) will appear in the Value field, along with a brief description underneath. The parameters that appear depend on if this is a Windows or Unix DS-Client. 4. Click OK to save the changes to this tab. Depending on the parameter, you may have to restart the DS-Client service before the changes take effect.


Confidential.
Export DS-Client configuration to XML

See To export DS-Client configuration to XML on page 48. See To update a DS-Client using config-update.xml on page 49.
To export DS-Client configuration to XML

You can export the current DS-Clients configuration, Backup Schedules, Retention Rules, and Backup Sets to an XML file named config-update.xml. Windows DS-Clients: Use either Win32 DS-User or Java DS-User to export. Note: The "Export to XML" feature is not supported for Local DS-VDR, Lotus Domino Server, or Permissions-Only backup sets. Linux / Mac DS-Clients: Use Java DS-User to export. 1. Setup menu > Export to XML.
F1 Help: See Export DS-Client configuration to XML on page 780. 2. Select the options to export: DS-Client Configuration: exports all settings from the DS-Client Configuration screen tabs (Setup, Defaults, Notification, SNMP, Parameters, Connections, Roles). Backup Schedules: Exports all (or selective) Backup Schedules. Retention Rules: Exports all (or selective) Retention Rules. Backup Sets: Exports all (or selective) Backup Sets. Note: Recovered orphaned backup sets that have not been migrated (or had their backup information for connection, backup items, and schedule re-specified) cannot be exported. Meta Symbol (Windows DS-Client only): Check to use a Meta Symbol wherever necessary in the config-update.xml file. This will allow the XML file to be used for DS-Clients on different localized operating systems. Include Encryption Keys: Check to include the DS-Client and Account Keys in the XML file (they will be encrypted). 3. Click Save As to save the XML file.

Confidential.
To update a DS-Client using config-update.xml

DS-Client will read any XML file named config-update.xml and will verify that its structure is correct. If the file has not previously been applied, DS-Client applies its settings. Note: Depending on your requirements, you can use an exported XML file as is, edit the file, or create your own. The XML file must be named config-update.xml, and it must conform to the structure defined in the file asigra_conf.dtd.
1. For Windows DS-Clients, place the file config-update.xml in the program folder containing the DS-Client service. For Linux / Mac DS-Clients, place the file config-update.xml in the /etc sub-folder of the program folder containing the DS-Client service. DS-Client checks for an updated config-update.xml file every 10 seconds if the AllowAutoConfig parameter is set (Setup Menu > Configuration > Advanced Tab). If updated, DS-Client will read the XML file and apply its settings. After the XML file is applied, DS-Client renames the file to config-update-nnn.xml, where nnn is an incremental number. 2. This will overwrite configuration settings, backup schedules, retention rules, and backup sets (depending on the contents of the XML file). Note: The DS-Client Configuration elements <account-name>, <account-number>, <clientnumber>, and <encryption-keys> are only updated when DS-Client restarts.


Confidential.
Set a User/Group Maximum Online Storage Limit

The Users & Groups screen lists all users who have connected to the DS-Client. You can set a maximum Online limit either for specific users, or for an entire group (e.g. Regular Users). The lowest group limit applies to individual users (Effective Limit). Backups will fail, once the Online limit has been reached (an error message will appear in the Event Log). If more than one limit applies (e.g. User and Group limits overlap), the lower limit will apply. 1. Setup menu > Users & Groups. The Users & Groups screen appears.
F1 Help: See Users & Groups screen on page 893. 2. To set a maximum Online amount, highlight the user/group and click the Max Online button. The Maximum Online for ... screen appears. F1 Help: See Maximum Online for ... screen on page 790. 3. Uncheck the No Limit box. 4. Enter the maximum online amount (in MB) in the Online Storage Limit field. 5. Click OK. The Users & Groups screen reflects the change.


Confidential.
Password Rotation
[Windows DS-Client only] Password Rotation is a feature that allows you to randomize a specific users password at a frequency you select. Once a password is rotated, it becomes unknown to anyone (even to an Administrator). This feature can help to increase your network security. When Password Rotation is applied to a user account, the only way someone can use that account again (for login or as credentials on your network) is for an Administrator to manually reset the password from the Windows Computer Management console. This means you must use the Password Management screen to manage the backup sets. You cannot use the Backup Set Properties screen, since you will not know the password. Note: Password rotation involves the DS-Client service changing the Windows password of the specified network or computer user.
1. Setup menu > Password Rotation. The Password Management screen appears.
F1 Help: See Password Management screen on page 795. 2. To add or edit the list of managed users, see Add or Edit a User for Password Rotation on page 52. 3. To rotate a password immediately, highlight the user in the Managed Passwords list and click Rotate Now. The Last Updated time will refresh and the password will be changed. All password changes are logged in the DS-Client Audit Trail. (See Audit Trail on page 327.)


Confidential.
Add or Edit a User for Password Rotation

This section describes how to add or edit users for Password Rotation management. Depending on if you are adding or editing, the interface will appear as a wizard or a screen with tabs. These descriptions assume you are adding a user to the list (through the wizard). 1. Setup menu > Password Rotation. The Password Management screen appears. 2. To add a new user to the managed passwords list, click Add. To edit a user in the managed passwords list, highlight it and click Edit. 3. The Create / Modify User screen appears on the User Details tab.
F1 Help: See Password Management - User Details Tab on page 796. 4. Enter this users logon information.


Confidential.
5. Click Next (or Apply if editing). The Create / Modify User screen appears on the Password Rotation tab.
F1 Help: See Password Management - Password Rotation Tab on page 796. Enable Automatic Password Rotation: Check to activate the Rotation Settings section. If you do not select this option, this users password will only be rotated manually (from the Password Management screen). Rotation Rule: Click [...] beside the Rotation Rule field. The Available Password Rotation Rules screen appears.
F1 Help: See Available Password Rotation Rules on page 746. Highlight the Rotation Rule you want to use. (To create a new Rotation Rule, see Add or Edit a Password Rotation Rule on page 56.)
- Click Select. Your selection appears in the Rotation Rule field. Rotation Frequency: Specify the rotation interval (in hours or days).
Confidential.

6. Click Next (or Apply if editing). The Create / Modify User screen appears on the Backup Sets tab.
F1 Help: See Password Management - Backup Sets Tab on page 796. This screen allows you to associate this user to any of the backup sets currently defined on the DS-Client. The Associated Backup Sets list displays all backup sets currently using this users credentials for connection.


Confidential.
Click Select to add or modify the list. The Select Backup Sets screen appears.
F1 Help: See Select Backup Sets (Password Management) on page 821. Check beside all backup sets you want and click OK. Note: Once you apply your selection, it will overwrite the Connect As setting (Backup Set Properties) for all selected backup sets. 8. Click Finish (or Apply if editing).


Confidential.
Add or Edit a Password Rotation Rule

Rotation Rules contain the constraints the DS-Client will use when randomly selecting a new password. 1. From the Available Password Rotation Rules screen, click New or Edit. The New / Edit Password Rotation Rule screen appears.
F1 Help: See New / Edit Password Rotation Rule on page 791. 2. Enter a name for the rule. 3. Enter the Length Constraints for the password. 4. Click Add or Edit to define the complexity constraints for the password. You can add multiple complexity rules. The Add / Edit Complexity Rule screen appears.
F1 Help: See Add / Edit Complexity Rule on page 738. Select Minimum Length. Select the corresponding character set from which to choose. 5. Click OK. The Available Password Rotation Rules screen returns.


Confidential.
View Quotas
1. Setup menu > View Quotas. The View Quotas screen appears.
F1 Help: See View Quotas on page 894. 2. These settings are established on the DS-System by your Service Provider. (They can only be viewed.)


Confidential.
Bandwidth Throttle
This feature allows the DS-Client Administrator to manage the amount of bandwidth used by the DS-Client at any time during the week. Separate throttles can be defined both to the DS-System (backups) and from the DS-System (restores). By default, if nothing is configured, the DS-Client will use as much bandwidth as it can to perform operations as fast as possible. Note: Your Service Providers may impose their own bandwidth restrictions from their respective sides (carrier, DS-System).
1. Setup menu > View Bandwidth Throttle. The Bandwidth Throttle screen appears.
F1 Help: See Bandwidth Throttle on page 751. 2. There are two tabs, which have identical configurations except for the data direction where the throttling is applied: To DS-System (e.g. backups) From DS-System (e.g. restores) 3. By default, if nothing is configured, the DS-Client will use as much bandwidth as it can to perform operations as fast as possible (Unlimited). You can switch to a limited amount (in KB/Sec). In addition, you can use the Exceptions List to create detailed time periods on different weekdays when throttling will occur. 4. To add a Throttle Schedule Detail, click Add. To edit a Throttle Schedule Detail, highlight one from the Exceptions List and click Edit.


Confidential.
5. The New / Edit Bandwidth Throttle Schedule Detail screen appears.
F1 Help: See New / Edit Bandwidth Throttle Schedule Detail on page 791. 6. Configure the day(s) and time window at which to apply this detail. This detail will be an exception against the default (which is either Unlimited or Limited To). To create more specific exception periods, you may need to use multiple details. 7. Click OK to add / update the Throttle Schedule Detail. The Bandwidth Throttle screen appears with the changes to the Exception List. 8. Click OK / Apply to save the Bandwidth Throttle settings for this DS-Client.


Confidential.
Modify the DS-Client Setup (Windows DS-Clients)

The DS-Client Setup program (Filename: dsconfig.exe) is installed in the Asigra Cloud Backup Program Group folder. It allows you to change the following DS-Client Settings, which were set during installation: DS-Client Registration Information Customer Name Account #
- DS-Client # Grid DS-Client Information (if applicable) DS-System Address DS-Client service Logon Account Encryption Keys (Private Key, Account Key) Note: Once set, you may not change the Encryption Keys.
1. On the DS-Client computer: Start > All Programs > Asigra DS-Client > DS-Client Setup. 2. Most tabs in Setup are the same as those used in the DS-Client Installation program. 3. The Enter Registration Information screen appears. Edit if necessary and click Next. 4. The Configure Grid DS-Client Information screen appears. Select Configure Grid DSClient or Skip Configuring Grid DS-Client. 5. The Select DS-System Connection Type screen appears. Edit if necessary and click Next. 6. The Specify DS-System Address screen appears. Edit the DS-System IP Address(es) as required and click Next. 7. The DS-Client Service Logon Account screen appears. Edit if necessary and click Next. 8. The Encryption Keys Setup screen appears. Set key(s) if necessary and click Next. You may only set each Key once. You must set the Account Key if you upgrade your LAN to have more than one DS-Client. 9. Click Next to finish the setup. The changes take effect immediately once you restart the DS-Client. Note: For Linux DS-Clients, you can accomplish the above steps from the DS-Client Configuration Setup Tab screen (See View the DS-Client Setup Information on page 32.)


Confidential.
DS-User Initialization (Win32 Only)

Settings only apply to this DS-User installation.
Language
(Win32 only) This screen controls the GUI language settings. 1. Setup menu > Initialization. F1 Help: See DS-User Initialization - Language on page 776. 2. Select the GUI language. You must restart DS-User before the new settings take effect.
Connection
(Win32 only) This screen allows you to configure the specific IP address(es) or subnet(s) where this DS-User will look for additional DS-Clients (for remote management). By default (if this screen is left empty), Win32 DS-User automatically detects the local DS-Client and all other DS-Clients on the same subnet as this Win32 DS-User installation.
Note:
This modifies the file DSUSER.INI located in the same folder as the DS-User executable (DSUser.exe).
1. Setup menu > Initialization > Connection Tab.
F1 Help: See DS-User Initialization - Connection (Win32) on page 774.


Confidential.
2. DS-User can search for a specific DS-Client, or for all DS-Clients on a subnet. Click New or Modify in the corresponding section to add or edit entries. DS-Client level: Enter the specific IP Address or computer name. (It is easier to specify by IP address.) Note: Specifying a computer name requires a corresponding entry to exist in the local computer's %systemroot%\system32\drivers\etc\hosts file (typically found in C:\WINNT\system32\drivers\etc\). Each entry must be on a separate line, with the IP separated from the HOSTNAME by at least one space (e.g. 10.20.30.111 C_Name). Subnet: Enter the subnet, in the correct format (three sets of numbers separated by two periods). 3. The Connection Configuration screen appears.
F1 Help: See Connection Configuration on page 758. (If applicable) Select Single DS-Client or Grid DS-Client. -
Grid DS-Client expands the screen to allow you to specify the IP address or hostname of each node in the Grid. Enter the Host or Subnet. By default, the Port field is 4403, and should not be changed unless you have a specific requirement. Click OK. 4. At the bottom of the Connection tab, in the Logon using security context section, you have options for this GUI installations auto-connection behavior to DS-Client when it is launched. See Security Context (Win32 and Java GUI) on page 65. See Auto-Connection (Win32 and Java GUI) on page 65. 5. In the Connection Tab, click Apply.


Confidential.
DS-User Initialization (Optional - JAVA Only)

These optional settings can be configured from DS-User without logging in to a DS-Client. Settings only apply to this DS-User installation. Connection on page 63 Regional Settings on page 66 Keep Alive on page 67 Plugins on page 68 Look & Feel on page 68 Fonts on page 68 Show Memory (of the GUI) on page 69
Connection
(Optional - this screen can be left empty. If empty, the GUI will scan the local computer and the local computers subnet.) Use these settings to indicate a specific IP or DNS Address where the DS-User will look for a DSClient Service. This can speed up your login in larger network environments. You can also configure the GUI to scan entire subnets. 1. Setup menu > Initialization.
F1 Help: See DS-User Initialization - Connection (Java) on page 773.


Confidential.
To add an entry in this screen, click New. To edit an entry in this screen, highlight it and click Modify. 2. To add a specific DS-Client, click New in the Additional DS-Clients section. The Add / Modify DS-Client screen appears.
F1 Help: See Add a DS-Client on page 741. 3. Specify the DS-Client IP or DNS Address (host name). For Grid DS-Client, the screen expands to allow you to specify the IP address or hostname of each node in the Grid. 4. Click OK. The entry appears in the Additional DS-Clients section. 5. To add an entire subnet, click New in the Additional Subnets section. The Add / Modify Subnet screen appears.
F1 Help: See Add / Modify Subnet (Java DS-User) on page 742. Specify the subnet and click OK. The entry appears in the Additional Subnets section. 6. Continue with steps 2-5 as required. 7. At the bottom of the Connection tab, in the Logon using security context section, you have options for this GUI installations auto-connection behavior to DS-Client when it is launched. See Security Context (Win32 and Java GUI) on page 65. See Auto-Connection (Win32 and Java GUI) on page 65. 8. Click OK to save any changes.

Confidential.
Note:
DS-User will scan the LAN for all active DS-Clients, whether or not any entries are in the Additional DS-Clients list. DS-Clients specified in the Additional DS-Clients list which are not detected, will appear in Red. A DS-Client on the local computer appears in Blue.
Security Context (Win32 and Java GUI)

(For Windows DS-Client only) The Target Name is optional. This field can be left blank, particularly if you are only connecting to the local DS-Client. It is only used if this DS-User GUI tries to connect to a DSClient in an Active Directory Domain. The default Target Name is CloudBakSvc. You must have your network administrator create and register this Target Name (or any other name you choose to use) with Active Directory using a tool like Microsoft setspn.exe provided with Windows Support Tools. This is an advanced configuration option that requires the assistance of a network administrator. For more information, refer to the Knowledge Base Article Logon using security context on page 455.
Auto-Connection (Win32 and Java GUI)

(For Windows DS-Client only) In the DS-User Initialization - Connection tab, there are options for Logon using security context. The Auto-Connection selection configures how this installation of the DS-User GUI will behave when it launches. Last DS-Client: This DS-User GUI will search for the last DS-Client it successfully connected with. If that DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Local DS-Client: This DS-User GUI will search for the local DS-Client. If the local DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Last or Local DS-Client: This DS-User GUI will search for the last connected DS-Client first. If the last connected DS-Client is found, DS-User will attempt to connect using the already logged on user credentials from the current Windows login session (provided that the same username and password is provided). If however, the last connected DS-Client is not available DS-User will connect to the local DS-Client using the current security context. Local or Last DS-Client: (Default) This DS-User GUI will search for the local DS-Client first and connect using the current security context. If the local DSClient is not found, DS-User will attempt to connect to the last connected DSClient using the current security context (provided that the same user network credentials are used, and that the local user exists on the remote DS-Client, and appropriate user permissions are there in the remote DS-Client). Disabled: Users can select this option to turn off the auto-connect functionality. Users will see the Connect to DS-Client Service screen at GUI startup and must supply a valid username and credentials to connect to the selected DS-Client.


Confidential.
Regional Settings
(Java version only) This screen controls the GUI language settings and other regional formatting. 1. Setup menu > Initialization. 2. Click Regional.
F1 Help: See DS-User Initialization - Regional on page 776. 3. Click OK to save any changes.


Confidential.
Keep Alive
(Optional - this screen can be left empty) These settings limit the amount of idle time on DS-User, after which the connection with DS-Client will be terminated. 1. Setup menu > Initialization. 2. Click Keep Alive.
F1 Help: See DS-User Initialization - Keep Alive on page 776. 3. Specify the Keep Alive settings. 4. Click OK to save any changes.


Confidential.
Plugins
Some plugins are automatically applied, depending on the DS-Client's configuration. Others can be manually enabled / disabled, and configured. 1. Setup menu > Initialization. 2. Click Plugins. F1 Help: See DS-User Initialization - Plugins on page 776. 3. Highlight a plugin and configure any options. 4. Click OK to save any changes.
Look & Feel

(Optional - this screen can be left empty) To adjust the look and feel of the DS-User GUI: 1. Setup menu > Look & Feel. 2. Select one of the available themes. 3. For the Metal theme only, you can customize the look further: Setup menu > Initialization. Click Look & Feel. F1 Help: See DS-User Initialization - Look & Feel on page 776. Adjust the Metal Theme and Custom Colors. Click OK to save any changes.
Fonts
(Optional - this screen can be left empty) DS-Users default fonts may not be enough to display some Unicode characters. In these cases, you can add specific fonts that the DS-User will attempt to use (in order) to display such characters. 1. Setup menu > Initialization. 2. Click Fonts. F1 Help: See DS-User Initialization - Fonts on page 775. 3. Click Add. F1 Help: See Select Font on page 829. 4. Select a font to add to the DS-User Initialization list. 5. Click OK. 6. The entry appears in the Additional Fonts list. 7. Continue with steps 3-6 as required. The order that appears in the Additional Fonts list is the order that DS-User will use if it attempts to display characters that its default font cannot. 8. Click OK to save any changes. 9. Exit the DS-User program and restart in order to for the changes to take effect.


Confidential.
Show Memory (of the GUI)

Memory information applies to the current instance of the GUI (not the underlying service). 1. Setup menu > Click Show Memory. 2. In the top right corner of the GUI, a memory usage bar appears. If you hover the cursor over the bar, the information appears in a ToolTip.
Maximum Memory: The maximum amount of memory this GUI can consume from this computer. Total Memory: This amount has been consumed (allocated) from the computer to this GUI instance. Free Memory: Amount of the allocated memory that is still free for use. Used Memory: Amount of memory that is currently being used.


Confidential.
Grid DS-Client (Windows DS-Clients)

In high-performance environments you can maximize DS-Client processing and distribute the load across two or more computers in a configuration called Grid DS-Client. The DS-Client software is installed on multiple computer (nodes) and configured to use the same database. See the section Grid DS-Client Installation in the Windows DS-Client Installation Guide (Filename: installation_dsclient.pdf). The Grid DS-Client is composed of one Main Node and any number of Leaf Node(s). The Main DS-Client is the one that accepts DS-User connections for management. The Leaf Nodes perform activities, as instructed by the Main Node. Any DS-User that is going to connect to the Grid DS-Client must be able to see all of its nodes (IP addresses). This is because DS-User can only connect to the Main Node, and that one is chosen randomly among the running nodes. To do this, make sure DS-User is configured with the IP address of each node in the Grid DS-Client: See DS-User Initialization (Win32 Only) on page 61. See DS-User Initialization (Optional - JAVA Only) on page 63. Note: This will not be necessary if DS-User and all DS-Client nodes are in the same subnet. By default, a DS-User can see all running DS-Clients in the same subnet.
If you connect to a Grid DS-Client, a Grid Menu is activated. From this menu, you can access the following screens to manage the Grid: Grid Status: See Monitor Grid Status on page 71. Stop DS-Client Node: See Stop a DS-Client Node on page 72. Export Grid DS-Client Node Addresses: See Export the Grid DS-Client Addresses (to text file) on page 73. DS-Client Grid Log: See View DS-Client Grid Log on page 74. If you connect to a Grid DS-Client, the following screens will have an additional option to select by the Node ID: Activity Log viewer screen Load Summary screen (Reports menu > Load Summary) DS-Client System Status screen (Setup menu > System Activities > System) DS-Client Advanced Configurations screen (Setup menu > Configuration > Advanced Tab) For more information, see the following Knowledge Base Articles: Grid DS-Client on page 426 Admin Processes with Grid DS-Client on page 496


Confidential.
Monitor Grid Status

You can monitor the Grid DS-Client from DS-User. 1. Grid Menu > Grid Status. The Grid Status screen appears on the Graph Tab.
F1 Help: See Grid Status on page 784. The graph view gives a quick overview of the status of the Grid DS-Client. 2. Click List. The List Tab appears.
The list view shows details about each of the nodes of the Grid DS-Client, including which one is the Main Node. The list view also shows details about the Grid DS-Clients database node.


Confidential.
Stop a DS-Client Node

If you need to stop a node in the Grid DS-Client, you can do it from the Grid Status screen. You can also stop the DS-Client service from a local nodes terminal using the DS-Client Service Manager (Start > All Programs > Asigra DS-Client > DS-Client Service Manager). 1. In the Grid Status List Tab. Highlight the node you want to stop.
F1 Help: See Grid Status on page 784. 2. Click Stop Node. The Stop Node screen appears.
F1 Help: See Stop DS-Client Node on page 888. Wait for all running activities to complete: Stops the DS-Client on the selected node, after all the current activities have completed. No new activities will be allowed once you click OK. Stop when all activities complete or force stop after [...] minute(s): Stops the DS-Client on the selected node after all the current activities have completed, or forces a stop after the specified time has elapsed. No new activities will be allowed once you click OK. Stop Type: You must specify if you want to shut down or reboot the node, or to only stop the DS-Client service (keep the computer running).


Confidential.
Export the Grid DS-Client Addresses (to text file)

You can export the Grid DS-Clients IP Addresses (internal or external) to a text file. This facilitates distribution (e.g. to quickly configure each DS-User GUI installation with all the correct nodes of a Grid DS-Client). 1. In the Grid Status screen, click Export. The Export Grid DS-Client Address screen appears.
F1 Help: See Export Grid DS-Client Address on page 781. 2. Select Internal or External Address and click OK. A Save As screen appears, allowing you to select the destination format and location. 3. The exported file can then be imported to any other DS-User installation using the Load button. Win32 DS-User: See DS-User Initialization (Win32 Only) on page 61. Java DS-User: See DS-User Initialization (Optional - JAVA Only) on page 63.


Confidential.
View DS-Client Grid Log

This log displays all events specific to the Grid DS-Client configuration. 1. Grid Menu > Grid Log. The DS-Client Grid Log screen appears.
F1 Help: See DS-Client Grid Log on page 770. 2. You can narrow the display in the Select by section.


Confidential.
3 - Schedules and Retention Rules
This section provides information about creating and working with Schedules (for unattended backups, etc.) and Retention Rules (for data that has been backed up).


Confidential.
About Schedules
The Schedules allow you to perform automatic, unattended activities on specified backup sets. This is done by creating a schedule, then assigning backup sets to that schedule. A Schedule is composed of Details. Each Detail refers to a specific backup circumstance (e.g. "Occurs every 2 week(s) on Friday, at 6:00 PM"). When combined, the details indicate all times when unattended backups will be performed.
The Schedule tab allows Administrators and Backup Operators to monitor and adjust the scheduled backup load on the DS-Client. (For example: if the backup load from a particular schedule becomes too heavy.)


Confidential.
Create or Modify a Schedule

A Schedule is a set of details. Each detail refers to a specific backup circumstance (e.g. "Occurs every 2 week(s) on Friday, at 6:00 PM"). Each Schedule must have at least one detail. 1. DS-User screen > Schedules tab. 2. To create a new schedule, right-click and choose New Schedule. To modify an existing schedule, right-click on it and choose Edit Schedule. 3. The Schedule screen appears.
F1 Help: See Schedule screen on page 816. 4. Enter a name for the schedule. 5. If this schedule is specifically for a Portable Computer, check the box and set a CPU Usage limit (%). This will limit the DS-Client Services CPU usage to that amount in order to permit continued use of the Portable by its user. 6. Add details to the schedule (See Add a Detail to a Schedule on page 78.). 7. Continue with step 6 until you are finished, then click Save.


Confidential.
Add a Detail to a Schedule

Each Detail is a description of a specific date/time pattern when to perform a backup (or other task that can be scheduled). You may add as many details to the schedule, as are required. For example: You may wish to back up weekly, and back up on a specific day (such as the last Friday of every month). To do so, create one detail for the weekly backup, and a second detail for the monthly backup. 1. Adding a detail starts slightly differently for JAVA and Win32 versions: JAVA: Click New beside the Detail List. The Detail List will indicate the current detail is new (e.g. Weekly: <new>). Then, click on the Detail Type Tab you want (One Time, Daily, Weekly, Monthly). Win32: Select <New> from the Details List then, in the Occurs section click the Detail Type you want. 2. In the Detail Type section, specify when you would like this detail to run. 3. In the Daily frequency section, specify the frequency when this detail will run. 4. In the Detail Period section, specify the dates this detail will be active for this Schedule. 5. In the Tasks section, specify the task(s) to run for this detail. You may run multiple tasks in a single detail, but they will run in the following order: 1. Perform Backup: scheduled backup 2. Enforce Retention: enforce the Retention Rules (if any) for backup sets (See About Retention Rules on page 85.). 3. Perform Validation: scheduled validation of backup set data. See Validation of Online Storage on page 276 for more information. - When you check the box, the Verify Encryption Key screen appears, prompting you to enter the DS-Client Encryption Key(s).
F1 Help: See Verify Encryption Key on page 894.


Confidential.
- Click >> to edit the Scheduled Validation Options.
F1 Help: See Scheduled Validation Options on page 819.

Validate last generation only Select to validate only the latest generation of backup data for the selected backup set. Exclude files deleted from source Select to skip validation of files that have been deleted from the source computer. Resume from previously interrupted location Select to configure this Schedule to resume validation from the point of interruption if the last scheduled Validation did not finish. This is useful for large backup sets that might not be completed in the Schedules time window.
4. Perform BLM: Request DS-System to copy a backup set snapshot to BLM. Click >> to edit the BLM Options. See Backup Lifecycle Management (BLM) on page 289 for more information. - Click >> to select the BLM Options.
F1 Help: See Select BLM Options on page 822.

Archive Options Archive packages are specific to a particular backup set. The default (if these options are not selected) is for each BLM Request to be added to the current Archive Package on the BLM Archiver. Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. You must specify when the package will be closed: at session start - makes a new Archive Package. This means the previous package (if one exists) will be closed, and the new request will go to the new package. at session end - uses the current Archive Package. This means the new request will go to the current package, and after it finishes, the package will be closed. Once a package is closed, no new data will be added. Subsequent archiving requests will create a new archive package.
Close active package


Confidential.
Reference previous archive packages
Generations to include
Select to allow the Archive Package to contain references to older packages. This may save space by removing data redundancy. The default (if this option is not selected) is for each Archive Package to contain all of the required files. Latest generation - Creates a BLM Archive containing the latest generation of all items selected. All generations - Creates a BLM Archive containing all the (online) generations of all items selected.
5. Start LAN Scan of Shares: The schedule will start scanning the LAN Shares for statistical data. Since this may take a significant amount of time, this task is run last. 6. Clean Local-Only Trash: The schedule will start a Clean Local-Only Trash process on all Local-Only storage locations for this DS-Client. (For a description of this process, see Deleting Local-Only backup set data & Clean Local-Only Trash on page 181). 6. Click Save. The Detail is saved. Each new detail is automatically assigned a name, based on the frequency chosen and an automatic number (e.g. daily:1, weekly:2). 7. You may continue adding Details, as required by repeating steps 1-6 above. 8. When you are finished, click Close to exit.


Confidential.
Deleting Schedules and Schedule Details

To delete a Detail from a Schedule: 1. DS-User screen > Schedules tab. 2. In the Schedule Tree, highlight the Schedule you would like to edit. 3. Right-click 4. Click Edit Schedule. The Schedule screen appears, with the selected Schedule's Details. 5. Highlight the detail in the left hand list, and right-click. 6. Click Delete to delete the Detail from the list. 7. A confirmation screen appears. Click Yes to delete the Detail. Note: You cannot delete the last Detail of a Schedule. In this case, you must delete the Schedule.
To delete a Schedule: The schedule must be empty in order to be deleted. This means, no Backup Sets may be scheduled with it. 1. DS-User screen > Schedules tab. 2. In the Schedule Tree, highlight the Schedule you would like to delete. 3. Right-click. 4. Click Delete Schedule. A confirmation screen appears. 5. Click Yes to delete the Schedule.


Confidential.
Viewing Schedule Calendar

This is a visual representation of the backup schedules, and the backups that have occurred. You can see if schedules overlap (which might cause higher network traffic), or if errors occurred for backups that have run.
Highlight a cell to view what is scheduled at that time in the Cell details section. Highlight a schedule to view its description.
The color of the cell corresponds to the selection and Legend.
1. DS-User screen > Schedules tab > Right-click > Schedule calendar. The Schedule Calendar Screen appears. F1 Help: See Schedule Calendar on page 815. 2. By default, the screen shows all schedules for the current week. 3. The display can be changed from the top left portion of the screen: 4. The table changes to reflect the selections. 5. Click any cell. The Schedules / Processes at that time are shown. 6. Enable the Performed radio button. The Schedule refreshes automatically. 7. The numbers that remain in the Calendar reflect the actual number of backups at that time. 8. Click a time cell with an actual backup number to show the sets that were backed up. 9. The Description section displays the details of the highlighted Schedule.


Confidential.
Assign Backup Sets to a Schedule

Backup sets can be assigned to a schedule (but only one schedule at a time). This can be done as follows: when they are created in New Backup Set Wizard from the Sets Menu > Backup Sets > Properties (Schedule Tab) from the DS-User Windows Backup Schedules Tab - where DS-Client administrators can manage all the Schedules from that Tab When more than one backup set is assigned to a schedule, it may be necessary to manage the order that those backup sets run. Even though a backup schedule has a specific start time, the actual start time of a backup set may depend on its priority in the schedule.
Change Backup Set Priority in a Schedule

You can view a list of all the backup sets using a specific Schedule. 1. DS-User screen > Schedules tab. 2. Highlight the Schedule that you wish to view and right-click. 3. Select Set Priority. The Set Backup Set Priority for Schedule screen appears.
F1 Help: See Set Backup Set(s) Priority for Schedule ... screen on page 853. 4. The list displays the names of all backup sets that are specified using this particular schedule. 5. Highlight the Backup Set you want to prioritize. 6. In the Backup set priority field, click the arrows to change the priority of the highlighted backup set. The number in the # column changes with the number field. The set will sort automatically by priority (lower number = higher priority), so the highest priority items are first in the list. 7. Click Save to save the new settings.


Confidential.
Change Number of Simultaneous Backups

You can limit the number of backup sets that can be run simultaneously by this schedule. This is useful if some data must be backed up through a slower connection, and there is no benefit to running simultaneous backups. Similarly, if there are too many backup sets using the schedule, this may decrease the DS-Client's efficiency. If the number of sets scheduled to run simultaneously is higher than the DS-Client's Global Parameter for Maximum Concurrent Activities (Maximum sessions), the Calendar Section number will appear in bold. The default (if no parameter is set) is 8 for DS-Clients running on 32-bit Operating Systems, and 12 for DS-Clients running on 64-bit Operating Systems. You can alter this setting from the DS-Client Advanced Configurations Tab (See DS-Client Advanced Configurations on page 47.): For Windows DS-Clients, the parameter name is MaxSessions, found under the Performance category. For UNIX DS-Clients, the parameter name is MaxSession Number. 1. In the Schedule field, enter the maximum number of backup sets you would like to permit to run simultaneously. Note: For Grid DS-Clients, the limit will be the sum of all the MaxSessions parameters from all running nodes. 2. Click Save to save the new settings.


Confidential.
About Retention Rules

Retention allows you to implement granularity (specific pattern retention) in your backed up generations. For example: you might want to retain all generations of the previous day, then 1 generation each day for a week, 1 generation each week for a month, 1 generation each month for a year and 1 generation each year for the next 10 years. When you define retention rules, you implement a granularity according to your own retention policy. Retention Rules are optional. If you do not use the retention feature, your backup data will remain online according to the backup set generation setting (the oldest generation of a file will be overwritten if the maximum number of generations is reached). Retention Rules are applied per backup set, but are only enforced on demand or on schedule. When a Retention Rule is enforced, the online data that does not qualify for retention is deleted. If retention rules overlap, the default will be to keep the most data online possible. The following sections describe how to work with Retention Rules: Create or Edit a Retention Rule on page 85 Assign Retention Rule to a Backup Set on page 91 Enforce Retention Rule (on demand) on page 91 WARNING: Since this feature deals with the removal of backed up data, you must be very careful when you define Retention Rules. It is best to think of retention as a process that will delete everything except what is specified for retention. More information is available in the following Knowledge Base articles: See Retention Rules vs. Maximum # of Online Generations on page 512. See Retention Rule Examples on page 516. See Retention Rule combinations (multiple rule types) on page 518.
Create or Edit a Retention Rule

The Retention Rule Wizard assists you with selecting the options for a Retention Rule. Once a Retention Rule is defined (the collection of retention, delete, and other options), it can be assigned to a backup set (backup set properties > Retention Tab | Retention Rules Tab > ). For each Retention Rule, all selected retention options (generic or time-based) are combined using the AND logic. It is not necessary to set every option. This means when the Retention Rule is enforced, the maximum amount of data is kept online. Data that does not meet at least one of the specified retention options will be deleted. However, the Delete Options will always apply (if selected). Delete Options are specific for online files, when the DS-Client has detected that the actual corresponding backup source file has been deleted. The Archive Options (if selected) apply only to what is retained (i.e. after the files that should be removed have been deleted from online). For more information about BLM, see Backup Lifecycle Management (BLM) on page 289. 1. DS-User screen > Retention Rules tab. 2. To create a new Retention Rule, right-click and choose New Retention Rule. To modify an existing rule, right-click on it and choose Edit Retention Rule.


Confidential.
3. The Retention Rule Wizard appears on the Choose Retention Settings screen.
F1 Help: See Retention Rule Wizard - Choose Retention Settings on page 812. For details on these options, see the online help for the screen. This screen prompts you to select what type(s) of retention settings you want to define for this Retention Rule. The number of screens that appear in this Wizard depends on the selections made in this screen. You must make at least one selection. In order to explain the different screens, the following instructions assume you select every available retention option in this screen.
Note:
4. Click Next. The Retention Rule Wizard appears on the Delete Options screen.
F1 Help: See Retention Rule Wizard - Delete Options on page 813.


Confidential.
For details on these options, see the online help for the screen. 5. Click Next. The Retention Rule Wizard - Time Retention Rules screen appears.
F1 Help: See Retention Rule Wizard - Time Retention Options on page 814. To add a time-based rule, click Add. The New Time Retention Rule screen appears.
F1 Help: See New Time Retention Option on page 793. For details on these options, see the online help for the screen.


Confidential.
6. Click Next. The Retention Rule Wizard - Archive Old Data to BLM screen appears.
F1 Help: See Retention Rule Wizard - Archive Old Data to BLM Options on page 811. For details on these options, see the online help for the screen. To add an Archive rule, click Add. The New BLM Archive Rule screen appears.
F1 Help: See BLM Archive Rule on page 752. Select what files you want to push to BLM. Age: Online files older than the specified amount will be pushed to BLM. Filter options: All files (default), or files that conform to a specific filter pattern. You can select a different pattern from the drop-down list, or add a new one. For details on


Confidential.
these options, see the online help for the screen(s).
F1 Help: See File Filtering Rule on page 782. F1 Help: See File Filtering Option on page 781. Tip: Try to keep any rules as simple as possible.
7. Click Next. The Retention Rule Wizard - Local Storage Retention Options screen appears.
F1 Help: See Retention Rule Wizard - Local Storage Retention Options on page 813. For details on these options, see the online help for the screen.


Confidential.
8. Click Next. The Retention Rule Wizard - Choose The Name screen appears.
F1 Help: See Retention Rule Wizard - Choose a name on page 812. For details on these options, see the online help for the screen. 9. Choose a name. Review the description (each option selected is listed). Once you are satisfied, click Finish.


Confidential.
Assign Retention Rule to a Backup Set

Backup sets can be assigned to a Retention Rule (but only one at a time). This can be done as follows: when they are created in New Backup Set Wizard from the Sets Menu > Backup Sets > Properties (Retention Tab) from the DS-User Windows Retention Rules Tab - where DS-Client administrators can manage all the Retention Rules from that Tab Retention Rules only apply when they are enforced (either on demand, or on schedule). 1. DS-User screen > Retention Rules tab. 2. Browse for the backup set you want and highlight it. 3. Right-click and choose Assign to Retention. The Assign to Retention screen appears.
F1 Help: See Assign to Retention on page 744. 4. Select the Retention Rule to use for this backup set, then click OK.
Enforce Retention Rule (on demand)

You can enforce a backup sets Retention Rule on demand. This can be done as follows: 1. DS-User screen > Backup Sets tab. 2. Browse for the backup set you want and highlight it. 3. Right-click (or open the Retention Menu) and choose Enforce Retention. 4. A confirmation screen appears. Click Yes.


Confidential.
4 - Creating and Modifying Backup Sets
This section provides information about creating new backup sets and modifying backup sets.


Confidential.
Introduction & Common Functions

A backup set includes: A list of the backup items you specify for backup. A series of settings defining how to back up the set (i.e. schedule, options, etc.) Creating backup sets is done using the New Backup Set Wizard. See Creating Backup Sets (New Backup Set Wizard) on page 94. Once backup sets have been created, their properties can be modified through the Properties function. See Modifying Backup Sets (Backup Set Properties) on page 96. Most screens in the New Backup Set Wizard correspond to a tab on the Backup Set Properties screen (where the fields and options are the same), as shown in the following table. Some screen titles may be different, depending on the kind of backup set selected.
New Backup Set Wizard Choose the kind of backup set Select the computer Select the backup source (Linux) Select share & path for the database / data dump screen Specify the protocol for dumping the database (Linux DS-Client) Select Items for Backup Set Select backup item options Choose a Retention Rule for this backup set Specify backup set options Specify backup set Advanced Options (Windows DS-Client) Specify notification options Choose a schedule for this backup set Choose the name for this backup set Properties Tab N/A N/A N/A N/A Items Items Retention Options Advanced Options Notification Schedule Set Info
Some options are common to most backup sets: Backup Set Options - Pre/Post on page 97 Backup Set Options - Exclude Old Files on page 98 Backup Set Options - Continuous Data Protection on page 98


Confidential.
Creating Backup Sets (New Backup Set Wizard)

The New Backup Set Wizard helps you create a backup set by guiding you through the required selections. The following selections are common to all backup sets: Select the kind of backup (file system, database, mail server, etc.). Select the computer to backup. Select the items to backup (files, directories, databases, E-Mails, etc.). Select any special backup options for the backup items. Select a Retention Rule for the backup set. Select any special backup options for the backup set. Select any notification options for the backup set. Select a Schedule for the backup set. Select a name for the Backup Set. Select the type of Backup Set (Regular, Self-Contained, Local-Only, or Statistical). 1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears.
Windows DS-Client
Linux DS-Client
F1 Help: See Choose the kind of backup set screen on page 753. F1 Help: See Choose the kind of backup set screen (Linux DS-Client) on page 754. Note: This function is available only when you create a backup set. It cannot be modified. The screen looks different, depending on the type of DS-Client you are using (Windows, Linux, Mac), the tools that are enabled for the DS-Client, and if any pre-requisite software is installed on the DS-Client computer.


Confidential.
2. Choose the kind of backup:

Windows DS-Client File System Backups on page 99 MS SQL Server Database Backups on page 116 MS Exchange Server Backups on page 121 Permissions Only Backups on page 126 Oracle Database Backup on page 127 E-Mail Messages (DS-Recovery Tools) on page 141 System i Server Backup on page 147 MySQL Database Backup (Windows DS-Client) on page 131 MS SharePoint Server (DS-Recovery Tools) on page 153 Lotus Domino Server Database Backup (Windows DSClient) on page 158 VSS-aware backup sets on page 161 Backup from the Cloud (Salesforce.com) on page 167 Local DS-VDR backup set (VMware VADP) on page 169 Physical to Virtual backup set on page 172 LINUX / MAC DS-Client NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client) on page 112 Permissions Only Backups on page 126 System i Server Backup on page 147 MySQL Database Backup (LINUX DS-Client) on page 133 PostgreSQL Database Backup (LINUX DS-Client) on page 139 Oracle Database Backup on page 127 Oracle-SBT Backup (LINUX DS-Client) on page 164 DB2 Database Backup (LINUX DS-Client) on page 135 XenServer Backup (LINUX DS-Client) on page 156 Sybase Database Backup (LINUX DS-Client) on page 159 VMware Backup (LINUX DS-Client) on page 154 VMware VADP Backup (LINUX DS-Client) on page 166 Local DS-VDR backup set (VMware VADP) on page 169 Physical to Virtual backup set on page 172
3. Click Next. The next screen that appears depends on the kind of backup set you are creating.


Confidential.
Modifying Backup Sets (Backup Set Properties)

The Backup Set Properties screen helps you modify a Backup Set after it has been created. 1. Browse the Backup Set Tree for the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab.
F1 Help: See Set Properties - Items tab on page 859. F1 Help: See Set Properties - Items tab (Linux DS-Client) on page 860. 4. Use the various tabs in the Properties screen to modify the backup set. For details on the options, see the online help for the screen.
Properties Tab Items Retention Options Notification Schedule Set Info Share Connection Database Advanced Options Function Use to change the selected set's backup items and backup item options. Use to change the backup sets retention rules. Use to change the backup set options. Use to change the set's notification options. Use to change the set's schedule. Shows information about the backup set. Use to change the set name. Use to view and edit information about the selected backup share(s). Use to view and edit credentials used for connection to the backup source or dump for certain kinds of backup sets (Appears instead of Share Tab). Use to view and edit credentials used for database backup sets (Appears instead of Share Tab). Use to change the backup sets Advanced Options (Windows DS-Client only).


Confidential.
Backup Set Options - Pre/Post

This screen is accessed from the Backup Set Options. Use this screen to specify a command to run before (Pre) and/or after (Post) execution of the backup. This screen can also be brought up from the Restore Wizard, in order to execute Pre/Post options with a restore operation (ex: stop service, restore file, start service). 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Options. 5. Click Pre/Post. The Pre & Post Execution screen appears.
F1 Help: See Pre & Post Execution screen on page 797. F1 Help: See Pre & Post Execution screen (Linux DS-Client) on page 799. 6. For details on these options, see the online help for the screen. 7. Click OK to save the Pre/Post settings. Special Case: Windows Services Using the Pre/Post features, you can backup Windows Services. Services normally lock associated files while the Windows computer is running (i.e. these files will not normally be backed up). Examples of Services include DHCP and WINS. Note: It can be problematic to back up services on the DS-Client computer itself, since shutting down some core services may cause problems for the backup process.
The steps that apply to Windows Service Backups are identical to File System backups. However, you must know the specific file path of the service files to be backed up.


Confidential.
Backup Set Options - Exclude Old Files

Note: This option is not available if the Windows System State or Services Database is selected for backup.
Use this screen to exclude old files from backup. 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Options. 5. Click Exclude Old Files. The Exclude Old Files screen appears. F1 Help: See Exclude Old Files screen on page 780. 6. Select the exclusion for this backup set: No exclusion Exclude files older than [...] days / weeks / months / years Exclude files older than [date] Note: The age of a file is determined by its Last Modified date. 7. Click OK to save the Exclude Old Files settings.
Backup Set Options - Continuous Data Protection

Note: The DS-Client Administrator must permit creation of CDP backup sets from the DSClient Configuration - Defaults Tab (Setup Menu > Configuration > Defaults Tab). See Configure the Default Options (for Backup Sets) on page 34.
This section provides some background on the Continuous Data Protection option. It can be applied to File System backup sets (Windows / UNIX DS-Client), and E-Mail backup sets of MS Exchange E-Mails (Windows DS-Client with DS-MLR). For more information see the Knowledge Base article: Continuous Data Protection (Backup Set Option) on page 677. Knowing your data environment is important when using the continuous data protection option. Statistical Backups and LAN Storage Discovery help you to test your data environment. You should also take into consideration the number of generations that you want to maintain online (each change will normally count as a generation). See Statistical Backups on page 177. See LAN Storage Discovery Tool on page 329. The backup trigger for any continuous data protection set is the detection of a change to a file on the backup source. The File Change Detection method depends on the operating system and backup set type. Backup frequency depends on the interval for changes selected, which can be wide (up to many hours) or precise (down to the second-level). Note: Because this is a time-sensitive operation, make sure the DS-Client computer time and the backup source computer times are synchronized.


Confidential.
File System Backups

Step 1. Choose the kind of backup set
1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select File System. 3. Click Next >
Step 2. Select the Computer

1. The New Backup Set Wizard prompts you to select the computer to back up.
F1 Help: See Select the computer screen on page 850. 2. Browse through and highlight the computer that contains the files to be backed up. 3. Click Next >. Ask for Network Credentials: If Ask for Network Credentials is checked, Enter Network Credentials appears. F1 Help: See Specify Credentials (Windows DS-Client) on page 884. Enter the valid credentials to the computer. Note: DS-Client connections to NetWare servers - You should supply a 'context' in the From field of the Connect As box. Click OK. Use DS-Client Account: This option is only available for Windows DS-Clients. Allows you to use the DS-Client services account credentials to connect to the local (DS-Client) computer. You must be logged in through DS-User using an Administrator account (or equivalent). This option is only available when you select My Computer (i.e. the local DSClient computer).


Confidential.
Step 3. Specify the Backup Items

1. The New Backup Set Wizard switches to the Shares & Directories List for the selected computer.
F1 Help: See Select Items for Backup Set screen on page 831. 2. From this screen, you can do the following:
Add an entire directory To add an entire directory, browse through the Shares & Directories List until the directory you want appears and Click it.
Note:
You can select only one directory at a time. Subdirectories are automatically included, unless you clear the Include Subdirectories check box.
Add files that match a filter To add files that match a filter, in the Filter field, enter the file pattern that you would like to search for in the selected directory. (e.g. *.doc will search the directory for all files with the .doc file extension.)


Confidential.
Add specific files To add specific files, browse through the Shares & Directories List until the directory the files are stored in appears and Click it. A screen showing the list of files in that directory appears. Highlight the file(s) you wish to add to the backup set and click Add.
Exclude directories You can exclude a subdirectory if its parent directory is selected for backup. Exclude using Regular Expression Regular Expression provides more specific filtering than the Exclude function. For example, you can filter to exclude individual filenames or patterns. You should only use this option if you take the time to learn the Regular Expression syntax. Example: To exclude a specific filename from the backup, use \\filename\.ext$ (e.g. \\cache\.dsk$ will exclude the file cache.dsk). Source code and some documentation available from: http://www.boost.org (search the site for regex). Add special backup items Windows File Systems have additional special backup items that can be selected: - System State (including Registry) - Services Database For more information, see the following Knowledge Base articles: Backup of Windows System State on page 536 Backing up Windows for Bare Metal Restore (BMR) on page 534 Backup / Restore of Windows 2000 on page 592
3. The selected items appear in the Selected for Backup list. The icons indicate the type of item: directory with subdirectory directory without subdirectory file filter extension exclude 4. To add more items to the backup set, repeat steps 2-3. 5. Click Next >

Confidential.
Step 4. Specify the Backup Item Options

1. The New Backup Set Wizard switches to its backup item options menu.
F1 Help: See Set Properties - Items tab on page 859. 2. You should leave the default settings alone, unless there are specific backup set option requirements. For details on these options, see the online help for the screen. 3. Generation and options apply to each backup item (each line), and can be changed by highlighting the backup item and editing the settings. Permissions see Permissions Only Backups on page 126 4. Click Next >


Confidential.
Step 5. Specify Backup Set Options

Backup options affect the way the set is handled during the backup process. Some options are specific to the type of server that is being backed up. 1. The New Backup Set Wizard switches to the backup set options screen.
F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. You should leave the default settings alone, unless there are specific backup set option requirements. For details on these options, see the online help for the screen. For more detailed instructions on Pre/Post, see Backup Set Options - Pre/ Post on page 97 For more detailed instructions on Excluding old files, see Backup Set Options - Exclude Old Files on page 98 For more detailed instructions on Continuous Data Protection, see Backup Set Options - Continuous Data Protection on page 98 3. Click Next >


Confidential.
Step 6. Specify Advanced Options (Windows DS-Client)

Some additional advanced options are available for Windows File System backup sets. 1. The New Backup Set Wizard switches to the Specify Advanced Options screen.
F1 Help: See Set Properties - Advanced Options tab (Windows DS-Client) on page 854. 2. You should leave the default settings alone, unless there are specific backup set option requirements. For details on these options, see the online help for the screen. Windows options: Additional options specific to Windows file systems (2000 and up). Volume Shadow Copy: If the target backup computer supports this feature, this option appears. When selected, DS-Client will use Volume Shadow Copy Service (VSS) to copy the volume(s) selected for backup, then perform the backup of items from that VSS copy. If the VSS copy fails, DS-Client attempts to backup like a normal File System backup set. For more detailed instructions, see Backup using Microsoft VSS (Volume Shadow Copies) on page 550. Pure file data backup options: This option controls the automatic file filtering performed by the DS-Client during Windows file system backups. By default, the Windows DS-Client will exclude some files automatically out of the sharebased backup of files, even if such files would be readable (e.g. when using VSS). The excluded files my include: temporary files (e.g. pagefile.sys) files that are being backed up as part of System State backups (e.g. Operating System DLLs, executable) Registry hive files Other files that may interfere with a successful Agentless BMR
This option should usually remain unchecked, unless there are specific reasons why all such excluded data would need to be included in the share-based backup. Selecting this option will interfere with the ability to perform Agentless BMR without manual file filtering, however it may be used in conjunction with the VSS option in order to allow bootable-disk BMR (this requires 3rd-party BMR provisioning

Confidential.
integration). It is recommended that unless BMR provisioning is supported by your installed DS-Client, you should leave this option unchecked. Note: This option normally requires the Volume Shadow Copy option to be selected. Backup strategy for backed up files: By default, DS-Client skips files that have already been backed up. It uses each backed up files last modified time and size for comparison purposes, and if those on the source match those of the latest generation in the DS-Client database, the file will be skipped. Normally this is the required behavior for backup sets. However, in some specific situations, you may want to force the backup of those files by enabling this option. 3. Click Next >


Confidential.
Step 7. Specify Backup Set Performance Options (Windows DSClient)

Some additional backup set performance options are available for Windows File System backup sets, classic (non-VSS) Microsoft SQL Server database backup sets, classic Microsoft Exchange backup sets, Oracle Server backup sets, and VSS-aware backup sets. Note: This option only applies to backup items that are pure data files. It does not work on backup items with backup streams, encrypted files, sparse files, junction points, etc.
Note 2: This option does not apply for database backups if the backup set is using DS-Client Pipe as a dump option. 1. The New Backup Set Wizard switches to the Performance screen.
F1 Help: See Set Properties - Performance tab (Windows DS-Client) on page 875. 2. In normal operating environments, you should leave the default settings alone (i.e. use the DS-Clients settings). These performance options are provided for customers with high performance backup environments, where the DS-Client might be able to take advantage of the speed of the storage where the target backup data resides. Maximum pending asynchronous I/O for a file: This is the maximum I/O operations the DS-Client will allow to queue for each file from this backup set. This is for storage devices that support better parallel disk I/O, such as NAS devices, RAID 5/10, etc. Increasing this value may significantly increase the backup speed. The best setting for this value mainly depends on the storage device and network speed. WARNING:If your storage device does not support better parallel disk I/O (e.g. single read head on a physical disk, etc.), use the default value, otherwise the performance may be significantly degraded. Read buffer size for backup: This option adjusts the internal buffer amount that the DS-Client allocates for reading individual files for backup.

Confidential.
To achieve optimum backup performance, the DS-Client read buffer size may need to be different, depending on the combination of target storage device, target operating system, as well as any mid-ware involved (between the storage and the Operating System). 3. Click Next >.
Note:
Step 8. Specify Notification Options

If the DS-Client has been configured with a default notification option (Configure the Default Options (for Backup Sets) on page 34), the default notification will appear in this tab. You may add more notifications from this tab, if you wish. 1. The Specify Notification Options Tab appears.
F1 Help: See Set Properties - Notification tab on page 861. 2. You should leave the default settings alone, unless there are specific notification requirements. 3. Click Add (or modify), to specify a notification option for the backup set. The Add Notification screen appears.


Confidential.
F1 Help: See Add Notification screen on page 742. 4. In the Notification section, you may select one of the notification options. Note: The E-Mail and Pager fields will be grayed out if the DS-Client has not been configured for E-Mail notification (DS-Client Configuration - Notification Tab).
5. The Recipient section options change, depending on the type of notification selected: 6. In the Completion list, select from one of the notification conditions. The specified notification will be sent, if a backup meets the selected condition. Detailed notification: An expanded list of the backup will be included. Attach detailed log: A file-level detailed backup log file will be attached to the E-Mail. Compress: Indicates if the file attachment (file-level detailed backup log) will be compressed or uncompressed. 7. Click OK to save the notification setting. The Notification screen returns with the new option displayed in the Notification list. 8. Continue performing steps 3-7 for as many notification options and recipients as required. Click OK to save any modifications. 9. In the Send SNMP Traps when section, check each box to notify about the event: Successful Completed with warnings Completed with errors Incomplete 10. Click OK to save any modifications. 11. Click Next >.


Confidential.
Step 9. Specify the Retention Rule

[OPTIONAL] The Retention feature allows you to define specific scenarios (Retention Rules) when online data should be deleted. Retention rules are applied per backup set, but are only enforced on demand or on schedule. 1. The New Backup Set Wizard switches to the retention rules screen.
F1 Help: See Set Properties - Retention tab on page 875. 2. You should leave the default settings alone, unless there are specific backup set retention requirements. For details on these options, see the online help for the screen. For more information, see About Retention Rules on page 85. 3. Click Next >


Confidential.
Step 10. Specify the Schedule

1. The New Backup Set Wizard Schedule screen appears.
F1 Help: See Schedule Tab screen on page 818. 2. You should leave the default settings alone, unless there are specific schedule requirements for this backup set. For details on these options, see the online help for the screen. 3. Click Next >.
Step 11. Name the Backup Set

1. The New Backup Set Wizard Choose the name for this backup set screen appears.


Confidential.
2. 3.
4.
5.
F1 Help: See Choose the name for this backup set screen on page 755. F1 Help: See Choose the name for this backup set screen (Linux DS-Client) on page 756. The Wizard assigns a default name in the Set Name field. You may change this name. In the Set Type list, select what type of backup set you want: Regular: Creates a full featured backup set of any kind (File System, Database, etc.). Local-Only: See Local-Only Backup Sets on page 179 Self-Contained: See Self-Contained Backup Sets on page 178 Statistical: See Statistical Backups on page 177 Additional options appear if they are enabled for this DS-Client: BLM: See Backup Lifecycle Management (BLM) on page 289 Local Storage: See Local Storage Tool on page 303 Click Finish to create the backup set as specified.


Confidential.
NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client)

Linux DS-Client can backup the local file system, or servers visible on the LAN with NFS or UNIXSSH. More information is available in the following Knowledge Base articles: See Backup / Restore of UNIX File Systems on page 539. See Backup / Restore using UNIX-SSH on page 570. See Backup / Restore of NFS on page 572. See Backup / Restore of NAS (Linux DS-Client) on page 666.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select NAS, UNIX-SSH, NFS, Local File System. 3. Click Next >
Step 2. Select the source for this backup set

F1 Help: See Select the computer screen (Linux DS-Client) on page 850. 1. Select from the available options:
Back up the local DS-Client computers file system. If backing up the local DS-Client, make sure the backup items exclude (or do not contain) the postgres data folder. This will likely happen if you select / as the backup item (i.e. the entire / drive). If the DS-Client is currently using the local Postgres, backing up the postgres data folder may cause errors during the backup. Back up a NAS (Network Attached Storage) device. You must enter the IP of the NAS in the Path field (e.g. NAS\10.20.30.100). For more details, see the Knowledge Base article Backup / Restore of NAS (Linux DS-Client) on page 666. Back up using the NFS protocol. Back up using the UNIX-SSH protocol. SSH Notes: 1. The backup source machine must be a Unix system (Linux, Solaris, HPUX, or AIX). 2. The source machine must have an OpenSSH compatible server installed and started. 3. The source machine must have either Perl5 (core function, 5.6 or beyond) installed, or Python (2.4) installed. [Alternatively, you can use the DIRECT option to run a specific script/binary located on the source machine.] 4. The SSH approach cannot scan the LAN to get an initial machine list. You must enter the IP of the source machine in the Path field (e.g. UNIXSSH\10.20.30.100). The user or administrator can also put the initial machine list into the file hostlist_ssh located in the installation path (usually /opt/CloudBackup/DS-Client). 5. For more details, see the Knowledge Base article Backup / Restore using UNIX-SSH on page 570.
Local File System
NAS
NFS
UNIX-SSH
2. Browse through and select the server you want to backup. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer.

Confidential.
F1 Help: See Specify Credentials (Linux DS-Client) on page 886. Ask for credentials: Click to specify alternate credentials. For UNIX-SSH backup sets, this user's default shell must be either the Bourne shell or the BASH shell. If this user's default shell is anything else (like csh, tcsh), the operation may fail with: "SSH connection failed! The host may not be accessible!". sudo as an alternate user (UNIX-SSH backup sets): For security reasons, you may not want to use a super user for remote login to a source machine. Linux DS-Client is able to login to a source machine as a regular user, and then use 'sudo' to execute a shell as an alternate user with higher access permissions. The regular user must have privileges to connect to the SSH server on the source machine. Both regular and alternate users must be listed in the sudoers file on the source machine. The sudoers file can be edited with visudo. (Please consult your 'sudo' documentation for further information.)
The regular user must have privileges to run the "/usr/bin/perl" or /usr/bin/python command on the source machine as the alternate user. If you have perl/python installed in a different path, each sudoers user must be able to run perl/python from that installed path. Advanced connection options (UNIX-SSH backup sets): By default (if no selection is made), DS-Client runs PERL from the default path (normally /usr/bin). If PERL is not located in that directory, you must specify the exact path in this screen. This screen allows you to specify the type of script to use for backup of files on the source machine (PERL or PYTHON).
The DIRECT option allows you to run the specific program from the path entered in this screen. (Only for use if you have a specific requirement.) 4. Click Next >.

1. The New Backup Set Wizard switches to its Select items for backup screen. F1 Help: See Select Items for Backup (Linux DS-Client) on page 832. 2. Browse through the Shares & Directories List and click Add for as many items as are required. 3. Click Next >.

1. The New Backup Set Wizard switches to its backup item options screen. F1 Help: See Set Properties - Items tab (Linux DS-Client) on page 860. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.
Step 5. Specify the Backup Set Options

1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866.


Confidential.
2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.
Step 6. Specify the Notification Options

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups.


Confidential.
Novell NetWare Backups

There are some requirements that must be met in order to perform backups of NetWare Servers. In particular, the DS-Client computer must be running a Novell NetWare Client. For more information, refer to the following DS-Client Knowledge Base Articles: Backup / Restore of Novell NetWare files from a Windows DS-Client on page 542 Backup / Restore of Novell NetWare files from a Linux DS-Client on page 544 NetWare files can be backed up with Windows and Linux DS-Clients. The files are backed up using the corresponding File System backup set type. There is no separate NetWare backup type, however there are special items (like NDS) that can be selected for backup. For Windows DS-Clients, see: File System Backups on page 99 Once NetWare is configured on DS-Client properly, you will be able to see the NetWare Services network provider when you open New Backup Wizard:
For Linux DS-Clients, see: NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client) on page 112


Confidential.
MS SQL Server Database Backups

The steps to create a backup set are generally the same for all supported versions of MS SQL Server. More specific information is available in the following Knowledge Base article: Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Microsoft SQL Server. 3. Click Next >
Step 2. Select the Server

1. The Select a database server tab appears. 2. Browse through the list. The New Backup Set Wizard searches for all MS SQL servers with active databases on the network and prompts you to select which one you want to back up.
You can also type the server name in the Path box once you have clicked on the network: (ex:\\server_name) 3. Browse through and select the server you want to backup. 4. By default, your current user login to the DS-Client will be used to connect to the selected computer and database. There are two "ask for credentials" checkboxes available, in the event that you need to specify alternate credentials: 5. Click Next >.
Note:
Ask for network credentials (MS SQL Server)

1. If the Ask for Network Credentials box is checked, the Enter Network Credentials screen appears. See Ask for Network Credentials: on page 99 2. Enter the credentials and click OK.


Confidential.
Ask for database credentials

1. If the Ask for Database Credentials box is checked, the Enter Database Credentials screen appears. 2. Enter the database credentials and click OK.
Step 3. Specify the Database Dump options

In order to back up an active database, a "full dump", incremental dump, or differential dump of the database must be made. Use this screen to select the path (on the selected computer) where you wish to save the dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump.
F1 Help: See Select share & path for the database / data dump screen on page 849. 2. Select the dump location. Remote dump location: To specify a different computer for the database dump, you can type a valid UNC path into the Dump Path field. The MS SQL Server service account and the backup set user credentials must have rights to access this UNC path (read-write permissions). 2. Select the dump location. 3. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its Database List screen.
Multiple instances on the same server are displayed, however you can only add from one instance per backup set. 2. To Add a Database to the Backup Set: Browse through the Database List and highlight the database you wish to include. Highlight the entire instance to backup all databases. Click Add. The database is added to the Selected Items for Backup list. 3. Continue performing step 2 for as many items as are required. You can exclude individual databases if the entire (parent) instance has been selected for backup. 4. Click Next >.
Note:


Confidential.

1. The New Backup Set Wizard switches to its backup item options menu. The type of SQL Server is displayed at the top of the screen.
2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. For more details on these options, see the online help. 3. Click Next >.


Confidential.

Backup options affect the way the set is handled during the backup process. 1. The New Backup Set Wizard switches to the backup set options screen.
F1 Help: See Set Properties - Options tab (Windows database backup sets) on page 872. For more information on Database Backup Policy options, see the Knowledge Base article: Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560. 2. Click Next >.
Step 7. Specify the Backup Set Performance Options

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 7. Specify Backup Set Performance Options (Windows DS-Client) on page 106 in the section for File System Backups.


Confidential.
MS Exchange Server Backups

This backup set type uses the native Microsoft Exchange backup API and Windows Networking to perform backup and restore of target Microsoft Exchange Servers (2003 and 2007 only). For more information, refer to the following Knowledge Base article: Backup / Restore of Microsoft Exchange Server on page 553

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Microsoft Exchange Server. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network.
You can also type the server name in the Path box once you have clicked on the network (ex: \\server_name). You must supply the fully qualified domain name of the Exchange computer (i.e. Do not supply the server's IP address.) 2. Browse through and select the server you want to backup. For clustered Exchange servers, you must select the Exchange cluster name. If you choose an individual nodes name, you will get an error like 'Error returned from callback function call. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer and database: The "ask for credentials" checkbox allows you to specify alternate credentials. 4. Click Next >.
Note:
Ask for network credentials (MS Exchange Server)

See Ask for Network Credentials: on page 99 (File System section). 1. If the Ask for Network Credentials box is checked, the Enter Network Credentials screen appears. 2. Enter the credentials and click OK.

Confidential.

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the method to handle the database dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump.
F1 Help: See Select share & path for the database / data dump screen on page 849. 2. Select the dump option. 3. Click Next >.


Confidential.

1. Once you have successfully connected to the computer, the New Backup Set Wizard switches to its Database List screen.
2. To Add an MS Exchange Database to the Backup Set: Browse through the Database List and highlight an item to include. Click Add. 3. Continue performing step 2 for as many items as are required. You can exclude individual databases if the entire (parent) instance has been selected for backup. 4. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its options menu.

Backup options affect the way the set is handled during the backup process. Some options are specific to the type of server that is being backed up. 1. The New Backup Set Wizard switches to the backup set options screen. F1 Help: See Set Properties - Options tab on page 862. 2. You should leave the default settings alone, unless there are specific backup set option requirements. For details on these options, see the online help for the screen. 3. Click Next >


Confidential.
Step 7. Specify the MS Exchange Advanced Options

1. The New Backup Set Wizard switches to its Advanced Options menu.
F1 Help: See Set Properties - Advanced Options tab (Windows DS-Client) on page 854. 2. Backup Passive Node: This option only applies to Microsoft Exchange 2007 Servers in CCR (Continuous Cluster Replication) configuration where there is a main node that handles transactions and a passive node that handles only replication. If selected, this will backup the passive node. If not selected, this will backup the main node of the Exchange Server. NOTE: Do not change this setting once you have performed a backup of this set. 3. Click Next >.
Step 8. Specify the Backup Set Performance Options

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 7. Specify Backup Set Performance Options (Windows DS-Client) on page 106 in the section for File System Backups.


Confidential.
Permissions Only Backups

This special backup set type allows you to backup only the permissions of the selected item (directory or file for Windows DS-Clients; directory only for Linux / Mac DS-Clients). It shortens the backup time (since this will not backup the actual files). You may select more than one backup item. A separate dump file will be saved for each backup item you select. When a regular file system backup set is performed the files are saved with the current permissions and attributes. If only the permissions or attributes are changed and the content of the files remains the same, DS-Client will not backup those changes to DS-System. Modifications to attributes like Compress, Read-Only, Hidden, Archive, Index can only be detected (and backed up) using a Permissions Only Backup Set. Modifications to the Encrypt attribute are detected by Regular File System Backup Sets. In order to save the last permissions and attributes for your files you must create a Permissions Only Backup Set.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Permissions Only. 3. Click Next >
Step 2. Select the Computer

The steps for all subsequent screens are the same as for File System Backups. Follow from Step 2. Select the Computer on page 99 in the section for File System Backups.


Confidential.
Oracle Database Backup

There are some requirements that must be met in order to perform backups of Oracle Database Servers. You must refer to the DS-Client Knowledge Base Article: Oracle Database Servers (See Backup / Restore of Oracle Database Servers on page 573.). Specifically, look at the sections: DS-Client Requirements Oracle Server Requirements General Requirements

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Oracle Database Backup. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. Oracle on Windows: Expand the Microsoft Windows Network tree. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer. There are two "ask for credentials" checkboxes available, in the event that you need to specify alternate credentials:
Will prompt you to enter a valid user name and password for the selected computer. The Network Credentials must also be valid for the Network Protocol you select to dump the database file. The Network Credentials you specify must have "read" and write privileges for the dump path you select. (Mandatory) Will prompt you to enter a valid user name and password for the database server.
Ask for Network Credentials
Ask for Database Credentials
4. Click Next >.
Ask for network credentials (Oracle Server)

Ask for database credentials (Oracle Server)

1. The Ask for database credentials box is checked by default, and the Enter Database Credentials screen appears. 2. Enter the credentials and click OK.
Specify the protocol for dumping the database (Linux DS-Client)

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the method to handle the database dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump.

Confidential.
F1 Help: See Select the protocol for dumping database file (Linux DS-Client) on page 851. 2. Select the protocol: Local File System (for Oracle or DB2 servers on the DS-Client computer): dumps the database into the specified path on the local file system (on the DS-Client computer). NFS (for remote Oracle or DB2 servers): DS-Client will read the database dump files from the database server through the NFS transmission protocol. UNIX-SSH (for remote Oracle or DB2 servers): DS-Client will read the database dump files from the database server through the UNIX-SSH transmission protocol. DS-PIPE (for Oracle only): DS-PIPE is an alternative to the database dump for Oracle database server backups. This option does not consume any additional disk space. During backups, the DS-Client reads from the pipe on the source database. This method is useful if your database is too big to be dumped to a file on either the database server or the DS-Client buffer. 3. Click Next >.

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the method to handle the database dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump. 2. Select the Dump Device path. Make sure the Oracle Server username has read and "write" privileges to this dump path. 3. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its Database List screen.
2. To back up the full Oracle Database, select all items in the list or select the parent instance. Otherwise, browse through the Database List and click Add for as many items as are required. You can exclude individual databases if the entire (parent) instance has been selected for backup. 3. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its backup item options screen.

1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.



Confidential.
MySQL Database Backup (Windows DS-Client)

There are some requirements that must be met in order to perform backups of MySQL Databases: Windows DS-Client: The mysql utility must be listed in the PATH environment variable of the DS-Client computer. (If you must edit this variable, stop and restart the DS-Client service after making the change.) The user who performs MySQL Backup / Restore should have knowledge about the MySQL database. DS-Client backs up MySQL Server using the MySQL utilities mysqldump and mysql. The DS-Clients mysqldump and mysql utilities must be compatible with the MySQL version running on the source machine (MySQL server). For more information, refer to the following Knowledge Base article: Backup / Restore of MySQL Database Servers on page 585

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select MySQL. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. (You can also type the IP Address of the machine in the Path field.) 3. Click Next >. You must enter credentials to the database and click OK.

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the method of transmitting the dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump. 2. Select the dump location. 3. Click Next >.

1. The New Backup Set Wizard switches to its Database List screen. 2. Browse through the Database List and click Add for as many items as are required. You can exclude individual databases if the entire (parent) instance has been selected for backup. 3. Click Next >.

1. The New Backup Set Wizard switches to its backup item options screen. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.


Confidential.

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 5. Specify Backup Set Options on page 103 in the section for File System Backups.


Confidential.
MySQL Database Backup (LINUX DS-Client)

There are some requirements that must be met in order to perform backups of MySQL Databases: Linux DS-Client: The mysql utility must be listed in the PATH environment variable of user root on the DS-Client computer. Mac DS-Client: The path to the mysql utility must be added to the following file on the DS-Client computer:
/etc/rc.common
The user who performs MySQL Backup / Restore should have knowledge about the MySQL database. DS-Client backs up MySQL Server using the MySQL utilities mysqldump and mysql. The DS-Clients mysqldump and mysql utilities must be compatible with the MySQL version running on the source machine (MySQL server).
For more information, refer to the following Knowledge Base article: Backup / Restore of MySQL Database Servers on page 585

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select MySQL. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. (You can also type the IP Address of the machine in the Path field.) 3. By default, your current user login to the DS-Client will be used to connect to the selected computer. Click "Ask for database credentials" to specify alternate credentials. 4. Click Next >.

1. The New Backup Set Wizard switches to its Database List screen. 2. Browse through the Database List and click Add for as many items as are required. 3. Click Next >.



Confidential.



Confidential.
DB2 Database Backup (LINUX DS-Client)

There are some requirements that must be met in order to perform backups of DB2 Database Servers. You must refer to the DS-Client Knowledge Base Article: DB2 Database Servers (See Backup / Restore of DB2 Database Servers on page 587.). Specifically, look at the sections: DS-Client Requirements DB2 Server Requirements General Requirements

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select DB2 Database Backup. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. You must know the hostname or IP address of the target DB2 Server to backup. (It can be on a different subnet.) This hostname or IP address must be the same one used in the DB2 catalog command. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer. There are two "ask for credentials" checkboxes available, in the event that you need to specify alternate credentials:
Will prompt you to enter a valid user name and password for the selected computer. The Network Credentials must also be valid for the Network Protocol you select to dump the database file. The Network Credentials you specify must have "read" and write privileges for the dump path you select. (Mandatory) Will prompt you to enter a valid user name and password for the database server.
Ask for Network Credentials
Ask for Database Credentials
4. Click Next >.
Ask for network credentials (DB2 Server)

Ask for database credentials (DB2 Server)

1. The Ask for database credentials box is checked by default, and the Enter Database Credentials screen appears. 2. Enter the credentials and click OK: User Name: Enter a valid database User Name on the DB2 database server you want to back up. Password: Enter the corresponding password.

Confidential.
Node Name: Enter the local alias of the target DB2 server node. This is the name on the DS-Client computer that is used to identify that node. Port Number: Enter the TCP/IP port number of the DB2 Server Database Manager instance. DB2 Client Instance: Enter the local DB2 instance name installed on the DSClient computer.
Step 3. Specify the protocol for dumping the database

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the method to handle the database dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump. 2. Select the protocol: Local File System (for DB2 Server on the DS-Client computer). NFS (for remote DB2 Server) UNIX-SSH (for remote DB2 Server) 3. Click Next >.

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select where to place the database dump file. 1. New Backup Set Wizard prompts you to specify how to handle the database dump. 2. Select the Dump Device path. Make sure the DB2 Server username has read and "write" privileges to this dump path. 3. Click Next >.




Confidential.

1. The New Backup Set Wizard switches to the backup set options screen.
2. You should leave the default settings alone, unless there are specific backup set option requirements. For details on these options, see the online help for the screen.
Prune History / Delete entries from the history file or log files from the active log path. Logfile If unchecked, perform Offline DB2 backup. During an offline backup, applications cannot connect to the database. If checked, perform Online DB2 backup. An online backup allows Online Backup applications to connect to the database and read and write to tables during database backup. Log retain or userexit must be enabled for an online backup.
3. Click Next >


Confidential.
Step 8. DB2 userexit log path

1. This Wizard screen only appears if you selected Online Backup in the previous screen. Otherwise, follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups.
F1 Help: See New Backup Set Wizard - Input DB2 userexit log path on page 792. If User Exit is OFF on the DB2 database server, you can leave this field empty. If User Exit is ON on the DB2 database server, you must enter the path for the DB2 Archive Logs.
Archive Log backup path This is the path where the DB2 Archive Log files are written by the User Exit program. Click [...] to specify the path. This opens the Select Directory screen.
2. Click Next >
Step 9. Specify Notification Options



Confidential.
PostgreSQL Database Backup (LINUX DS-Client)

There are some requirements that must be met in order to perform backups of PostgreSQL Databases: The psql and pg_dump utilities must be listed in the PATH environment variable of the user root on the DS-Client computer. The DS-Client computers psql and pg_dump utilities must be compatible with the PostgreSQL version running on the source machine (PostgreSQL server). For more information, refer to the following Knowledge Base article: Backup / Restore of PostgreSQL Database Servers on page 590

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select PgSQL. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer. Click "Ask for database credentials" to specify alternate credentials or an alternate port number if PostgreSQL instance is not running on the default port (5432). 4. Click Next >.


1. The New Backup Set Wizard switches to its backup item options screen. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. For details on these options, see the online help for the screen (Press F1 in this screen). 3. Click Next >.



Confidential.



Confidential.
E-Mail Messages (DS-Recovery Tools)

NOTE: From v.7.0, the DS-MLR Service is bundled with the DS-Recovery Tools installation. Windows DS-Client only: For online backup and restore of E-Mail servers at the message-level. This option must be enabled by your Service Provider from the DS-System. You must install the DS-MLR Service on the target MS Exchange, MS Outlook, Lotus Notes / Domino Server or GroupWise computer. Refer to the DS-Recovery Tools Installation Guide for instructions. For more information, refer to the following Knowledge Base articles: See DS-MLR Installation & Setup on page 434. See Backup / Restore of E-Mails (using DS-MLR) on page 599.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select E-Mail Messages. 3. Click Next >.
Step 2. Select the E-Mail Server Type

1. You must select the E-Mail Server Type.
F1 Help: See Choose the E-Mail Server type on page 753. 2. Select the type of E-Mail Server you want: Microsoft Exchange Server Microsoft Outlook Lotus GroupWise 3. Click Next >.


Confidential.

1. Browse through and select the server you want to backup. If the name resolution to IP address is not functional, you can create the backup set by typing the IP address in the Path field.
2.
3. 4. 5.
To backup E-Mails of clustered MS Exchange Servers, you must select the virtual computer of the Exchange Cluster. To backup GroupWise E-Mails, you must select the server where the GroupWise Client (and DS-Recovery Tools) are installed. By default, your current user login to the DS-Client will be used to connect to the selected computer. The "ask for credentials" checkbox allows you to specify alternate credentials. Click Next >. If Ask for Network Credentials is checked, the Enter Network Credentials screen appears. Enter the credentials to the target computer. The amount of mailboxes that appear will depend on the credentials supplied.


Confidential.
Step 4. Select Directories / E-Mails for Backup

1. The New Backup Set Wizard switches to its Select directories / E-Mails for backup screen.
2. This dialog is the same as the Select Items for Backup Screen (File System Backups), except two name differences: The Shares and Directories List is called the Mailboxes List; The Files button is called the E-Mails. 3. Select the mailboxes to backup. 4. Click Next >.


Confidential.

2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. For more details on these options, see the online help. 3. To add a filter to a backup item, highlight the item and click Filter. The Select Filter screen appears.


Confidential.
4. Select from one of the available filters, or click Add to create one. If you click Add, the Add / Modify Filter Screen appears.
F1 Help: See Add / Modify Filter on page 740. 5. Create the filter by giving it a name in the Filter Name field. 6. Select the filter conditions (you can make complex filters with the AND, OR, and BRACKETS). When finished, click OK. Note: If you add a filter, the backup will search and backup only those E-Mails that match the filter description.
7. Click Next >.

1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab on page 862. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.

The steps for all subsequent screens are the same as for Windows File System Backups.


Confidential.
Follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups.


Confidential.
System i Server Backup

[Windows DS-Client] For this option to be enabled, the IBM iSeries Access for Windows must be installed on both the System i Server and the computer on which the DS-Client is running. For more information, see Backup / Restore of System i Server on page 610.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select System i Server. 3. Click Next >

1. The Select a System i Server to backup screen appears. 2. In the Path field: You must manually enter the IP address of the System i server. 3. By default, your current user login to the DS-Client will be used to connect to the selected computer. To specify alternate credentials: The "ask for credentials" checkbox allows you to specify alternate credentials. 4. Click Next >.
Step 3. Specify the share & path for the data dump
This screen appears for Windows DS-Client only. Linux DS-Client skips to Step 4. Specify the Backup Items on page 148. 1. New Backup Set Wizard prompts you to specify the location of the data dump. 2. Select a folder in the ROOT file system: The System i Server ROOT file system must be shared (with read-write permissions) for this operation to work. 3. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its Items List screen.
2. Create a list of items that you are going to backup. Your items list can consist of:
Applications
An application is a specific list of libraries you create for backup. To create or modify an application, click "Applications". F1 Help: See Modify Applications (System i Server) on page 791. In the Modify Applications screen, highlight the libraries that belong to the application and click Modify.
In the Select Applications screen, enter or choose a name in the Application name field and click OK.
Confidential.

F1 Help: See Select Applications (System i Server) on page 821. In the Modify Applications screen, the application name appears to the left of the selected libraries. Click OK to return to the Items List screen. The application created will appear in the Applications folder. Note: The "Selected Items for Backup" list cannot contain applications and libraries at the same time.
IBM System Libraries

The System i comes shipped from IBM pre-loaded with the operating system and additional licensed programs that support the System i OS. Most of these IBM System Libraries (or IBM Supplied Libraries) begin with the letter Q. You can choose individual IBM System Libraries for backup directly. The entire contents of the selected IBM System Library (or libraries) will be backed up. If you wish to backup all the IBM System Libraries from the System i server, highlight the object IBM System Libraries" and press "Add". Note: IBM System Libraries cannot be backed up as individual objects.
IBM User Libraries

Although some libraries with names that begin with the letter Q are provided by IBM, they typically contain user data that changes frequently. Therefore, these libraries are also considered user libraries. You can choose individual IBM User Libraries for backup directly. The entire contents of the selected IBM User Library (or libraries) will be backed up. If you wish to backup all the IBM User Libraries from the System i server, highlight the object IBM User Libraries" and press "Add". To backup the system directory files, you must end the QSNADS subsystem before saving the QUSRSYS library. To backup the system performance data you must end the performance monitor before saving the QPFRDATA library. Note: IBM User Libraries cannot be backed up as individual objects.
Libraries
You can choose individual libraries for backup directly. The entire contents of the selected library (or libraries) will be backed up. If you wish to backup all libraries of your system, highlight the line "Libraries" and press "Add". Note: The "Selected Items for Backup" list cannot contain applications and libraries at the same time.


Confidential.
System info
You can backup the entire system info at once, or select either: A) User Profiles - the user profiles of your System i Server, or B) Configuration - the configuration, which consists of: Line descriptions Controller descriptions Device descriptions Mode descriptions Class of service descriptions Network interface descriptions Network server descriptions NetBIOS descriptions Connection lists Configuration lists Hardware resource data Tokenring adaptor data
Backup of files, members and objects.

In order to backup single files, expand a library and Add the file(s). In order to backup a member, select the file, and press the "Objects" button. In the window that appears, select a member and press "Add". In order to backup other objects from a library, e.g. programs or data areas, select the library the objects are in, and press "Objects". In the window that appears, select your objects and press the "Add" button. You can add as many items to the "Selected Items for Backup" list as you need. If you wish to remove an item, use the "Remove" button. "Individual obj" checkbox: if you wish to be able to quickly restore individual objects, check this box before you press the "Add" button. (Note: this option will reduce the backup speed and increase the disk space required. The performance will also be affected if the libraries contain a large number of small objects.) The icon for "individual objects" contains an additional blue "+" sign.
3. Once you have finished selecting the backup items, click Next >.


Confidential.

2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.

1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. You should leave the default settings alone, unless there are specific requirements. DS-Client supports the Private Authorities parameter PVTAUT (*YES/*NO) and Target Release parameter TGTRLS (*CURRENT/*PRV):
(PVTAUT): Specifies whether to save private authorities with the objects that are saved. Saving private authorities will increase the amount of time it takes to save the objects, but it can simplify the recovery of an object or a group of objects. It will not simplify the recovery of an entire system. NOTES: IBM cautions against using this option for individual objects only because PVTAUT increases the amount of time needed to save an object. It is not recommended that you select this option for large scale backup and recovery of user data. You must have save system (*SAVSYS) or all object (*ALLOBJ) special authority to specify this value. This parameter can only be specified when the backup set is created. Check your IBM System i documentation for more information regarding the PVTAUT parameter.
Backup Private Authorities


Confidential.
(TGTRLS): Specifies the release of the operating system on which you intend to restore and use the object. *CURRENT: The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed. *PRV: The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed. Previous Target Release NOTES: For system Libraries, Q* Libraries and/or *IBM Libraries, only the current release can be the target release. Not all objects can be targeted to another release. To find out which objects are supported check your IBM System i documentation. If DS-Client cannot backup the object to a previous release, it will retry the command without the TGTRLS parameter; this operation will be show on the log with the message "System i returned previous release target error; trying to rerun the same command without TGTRLS(*PRV) flag." This parameter can only be specified when the backup set is created.
3. Click Next >.



Confidential.
MS SharePoint Server (DS-Recovery Tools)

For online backup and restore of Microsoft SharePoint 2007 servers only. This backup set permits item-level backup and restore. This option must be enabled by your Service Provider from the DS-System. You must install the DS-Recovery Tools service on the MS SharePoint computer. Refer to the DS-Recovery Tools Installation Guide for instructions.
For more information, refer to the following Knowledge Base article: Backup / Restore of MS SharePoint 2007 Servers (DS-Recovery Tools) on page 627

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Microsoft SharePoint Servers. 3. Click Next >.

1. Browse through and select the server you want to backup. If the name resolution to IP address is not functional, you can create the backup set by typing the IP address in the Path field. 2. By default, your current user login to the DS-Client will be used to connect to the selected computer. The "ask for credentials" checkbox allows you to specify alternate credentials. 3. Click Next >. 4. If Ask for Network Credentials is checked, the Enter Network Credentials screen appears. Enter the credentials to the target computer.
Step 3. Select Items for Backup

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 3. Specify the Backup Items on page 100 in the section for File System Backups. Some options may not appear for MS SharePoint backup sets.


Confidential.
VMware Backup (LINUX DS-Client)

There are some requirements that must be met in order to perform backups of Virtual-Machines from a VMware ESX Server. For more information, refer to the following Knowledge Base article: Backup / Restore of VMware (at Virtual Machine-level) on page 620

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select VMware. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. In the Path field: You must manually enter the IP address of the VMware Virtual Center machine or ESX Server in the following format:
VMware\IP_address
By connecting to the VMware Virtual Center, you will be able to see (and backup) all the Virtual Machines from all the VMware ESX servers connected to this Virtual Center. 3. You must know the version of ESX that is running on the target Virtual Machine. The protocol used to connect to it will depend on the version. For ESX versions 3.5 and 3.5i, the HTTPS protocol is used. By default, your current user login to the DS-Client will be used to connect to the selected computer. To specify alternate credentials:
Ask for VMware logon credentials: ESX Connect: Ask for credentials: ESX Connect: sudo as an alternate user: Credentials to logon to the Virtual Center or ESX Server (the target computer specified at the IP address in step 2). Do not use this option for ESX version 3.5 or 3.5i. Do not use this option for ESX version 3.5 or 3.5i.
Note:
The user that is backing up ESX 3.5 or 3.5i must be added as a user with "Administrator" permissions (member of Administrators, on the Permissions tab) both on the Virtual Center and on the ESX server. This must be done using the Virtual Infrastructure Client. 4. Click Next >.
Note:

1. The New Backup Set Wizard switches to its Select Items for Backup screen. 2. Browse through the Shares & Directories List and click Add for as many items as are required. 3. Click Next >.


Confidential.




Confidential.
XenServer Backup (LINUX DS-Client)

There are some requirements that must be met in order to perform backups of Virtual-Machines from a XenServer. For more information, refer to the following Knowledge Base article: Backup / Restore of XenServer (at Virtual Machine-level) on page 625

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select XenServer. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. In the Path field: You must manually enter the IP address of the XenServer in the following format:
XenServer\IP_address
3. By default, your current user login to the DS-Client will be used to connect to the selected computer. To specify alternate credentials:
Ask for XenServer API Prompts you to enter a valid user name and password for the selected logon credentials: XenServer.
4. Click Next >.

1. The New Backup Set Wizard switches to its Select Items for Backup screen. 2. Browse through the Shares & Directories List and click Add for as many items as are required. 3. Click Next >.





Confidential.
Follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups.


Confidential.
Lotus Domino Server Database Backup (Windows DSClient)

There are some requirements that must be met in order to perform online backups of Lotus Domino Server Databases: The user who performs Lotus Backup / Restore should have knowledge about Lotus Domino. For more information, refer to the following Knowledge Base article: Backup / Restore of Lotus Domino Server Databases on page 631

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Lotus Domino Server. 3. Click Next >

1. The New Backup Set Wizard scans for servers on the network. 2. Browse through and select the server you want to backup. (You can also type the exact name of the Domino Server in the Path field.) 3. Click Next >. You must enter credentials to the Domino Server and click OK. F1 Help: See Specify Credentials (Windows DS-Client) on page 884. The credentials are contained in the notes.ini file described in Backup / Restore of Lotus Domino Server Databases on page 631. Note: Each Domino Server has its own notes.ini file.

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 3. Specify the Backup Items on page 100 in the section for File System Backups.


Confidential.
Sybase Database Backup (LINUX DS-Client)

For more information, refer to the following Knowledge Base article: Backup / Restore of Sybase (Database-Level) on page 633

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Sybase. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. Highlight the Sybase tree. In the Path field: You must manually enter the IP address (or network HostName) of the Sybase server followed by the Adaptive Server port, in the following format:
Sybase\IP_Address:Port_Number
For example:
Sybase\12.34.56.111:5000
The port number must always be placed after the IP address, separated by a colon. The default port for Sybase Adaptive Server is 5000. 3. By default, your current user login to the DS-Client will be used to connect to the Sybase database, and for the connection to the selected computer. You must supply database credentials with the sa_role. To specify alternate credentials, refer to the F1 Help. F1 Help: See Specify Credentials (Linux DS-Client) on page 886. 4. Click Next >.
Note:

In order to back up an active database, a copy or "dump" of the database must be made. Use this screen to select the location for the dump file. The Sybase database server must have read and write permissions to this path. 1. New Backup Set Wizard prompts you for the database dump path. 2. Select the dump location. 3. Click Next >.



Confidential.

1. The New Backup Set Wizard switches to its backup item options screen. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. For details on these options, see the online help for the screen (Press F1 in this screen). 3. Click Next >.




Confidential.
VSS-aware backup sets

[Windows DS-Clients only] This type of backup set uses the target backup computers Microsoft VSS (Volume Shadow Copy Service) components to perform online backup. VSS-aware backup sets can be made for the following server types: Microsoft SQL Server Microsoft Exchange Server Microsoft Hyper-V (Virtual Machine) Microsoft Cluster Hyper-V (Virtual Machine) Microsoft SharePoint Server

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select VSS-aware Backup Set. 3. Click Next >.
Step 2. Select the VSS-aware backup set type

1. You must specify what type of VSS-aware backup set you are creating.
F1 Help: See Select the VSS-aware backup set type on page 852. 2. Click Next >.


Confidential.

1. You are prompted to select the computer where the backup target is located. If the name resolution to IP address is not functional, you can create the backup set by typing the IP address in the Path field. 2. By default, your current user login to the DS-Client will be used to connect to the selected computer. The "ask for credentials" checkbox allows you to specify alternate credentials. 3. Click Next >. 4. If Ask for Network Credentials is checked, the Enter Network Credentials screen appears. Enter the credentials to the target computer.
Step 4. Select Items for Backup

The steps for all subsequent screens are the same as for the corresponding non-VSS backup types: Microsoft SQL Server: Follow from Step 4. Specify the Backup Items on page 118 in the section for MS SQL Server Database Backups. Note: A VSS-aware backup set of a Microsoft SQL Servers master database does not support the Full+Differential database backup policy. For more information, see the Knowledge Base article: Backup / Restore of Microsoft SQL Server (VSS-aware backup sets) on page 638 Microsoft Exchange Server: Follow from Step 4. Specify the Backup Items on page 123 in the section for MS Exchange Server Backups. For more information, see the Knowledge Base article: Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) on page 640 Microsoft Hyper-V: Follow from Step 3. Specify the Backup Items on page 100 in the section for File System Backups. (Hyper-V is a Virtual Machine, which means its backup item selection is similar to regular File System backup sets.) For more information, see the Knowledge Base article: Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644 Microsoft Cluster Hyper-V: Follow from Step 3. Specify the Backup Items on page 100 in the section for File System Backups. (Cluster Hyper-V backup requires you to select the Cluster Virtual Node by IP address.) Refer to the Knowledge Base article: Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644 for specific instructions before proceeding. Microsoft SharePoint Server: Follow from Step 3. Select Items for Backup on page 153 in the section for MS SharePoint Server Backups. For more information, see the Knowledge Base articles: Backup / Restore of Microsoft SharePoint 2007 (VSS-aware backup sets) on page 649 and Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets) on page 655
Note about Retention Rules for VSS-aware backup sets

An additional retention category applies to VSS-aware backup sets only (Component data integration options). Component data integration options: For an explanation, see the F1 Help for the Retention Rule Settings screen. (See Retention Rule Wizard - Choose Retention Settings on page 812.)


Confidential.
Note about Database Backup Policy for VSS-aware backup sets

On the Backup Set Options Tab, if the target server supports the feature, you will see the database incremental and / or differential backup options. These are the same options as for regular Microsoft SQL Server backup sets. For VSS-aware backup sets, Database Backup Policy options appear for supported Microsoft SQL Servers, Microsoft Exchange Servers, and Microsoft SharePoint Servers (but not for Hyper-V). For more information on Database Backup Policy options, see the Knowledge Base article: Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560.


Confidential.
Oracle-SBT Backup (LINUX DS-Client)

IMPORTANT:This backup set type requires manual command input from the Oracle Server itself. Only Oracle Database Administrators should attempt to use this backup set type. This type of backup set configures the DS-Client to receive Oracle RMAN (Recovery MANAGER) data dumps via the Oracle SBT (System Backup to Tape) protocol. For more information, refer to the following Knowledge Base article: Backup / Restore of Oracle-SBT on page 634

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Oracle-SBT. 3. Click Next >

1. 2. 3. 4. The Select the source for this backup set screen appears. In the Oracle-SBT tree and select RMAN-SBT-Data. Click Next >. You must supply backup set access credentials. These credentials (username / password) are required by the Oracle RMAN client. They must be defined in the DS-Client/Oracle-SBT parameter file (see Backup / Restore of Oracle-SBT on page 634).

1. The New Backup Set Wizard switches to its Select Items for Backup screen. 2. In the Shares & Directories List, select the data_dumps item and click Add. 3. Click Next >.

1. The New Backup Set Wizard switches to its Specify backup item options screen. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. For details on these options, see the online help for the screen (Press F1 in this screen). 3. Click Next >.



Confidential.
Follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups. Do not assign this backup set to a Retention Rule or Backup Schedule. NOTE: This backup set type is controlled by Oracle RMAN (not from DS-User). On-Demand and Scheduled backups do not apply to it.


Confidential.
VMware VADP Backup (LINUX DS-Client)

[This backup set type is not supported on Mac DS-Clients.] This type of backup set uses the native VMware API (vStorage API for Data Protection) when DSClient performs backup and restore of the target Virtual Machines. For more information, refer to the following Knowledge Base article: Backup / Restore of VMware VADP backup sets on page 635

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select VMware VADP. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. Highlight the VMware VADP tree. In the Path field: You must manually enter the IP address of the VMware ESX server or VMware vCenter server in the following format:
VMware VADP\IP_Address
For example:
VMware VADP\12.34.56.111
3. By default, your current user login to the DS-Client will be used to connect to the VMware ESX server or VMware vCenter server. To specify VMware logon credentials, refer to the F1 Help. F1 Help: See Specify Credentials (Linux DS-Client) on page 886. 4. Click Next >.

Once connected to the target VMware ESX server or VMware vCenter server, the steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 3. Specify the Backup Items on page 113 in the section for NAS, UNIX-SSH, NFS, Local File System Backups.


Confidential.
Backup from the Cloud (Salesforce.com)

[64-bit Windows DS-Client only] There are some requirements that must be met in order to perform Backup from the Cloud (of Cloud Server Databases): You must install the Backup from the Cloud Plug-in on the DS-Client computer. This can be found on the installation DVD in the folder:
\Software\DS-Client\Windows_64_bit\plugin\install.exe
The Local Storage Path must be set (see Local Storage Tool on page 303.) The user who performs Backup from the Cloud should have knowledge about the target Cloud server (Salesforce.com database). You must have a valid Salesforce.com account (username, password, and security token). Your Salesforce.com license must be an Enterprise, Unlimited version. The DS-Client computer must be able to connect to the Salesforce.com site (e.g. have an Internet connection). Optionally, you can configure the DSClient to connect to Salesforce.com via a proxy server (from Setup menu > Configuration > Connections tab). For more information, see the Knowledge Base article Backup from the Cloud (Salesforce.com) Limitations on page 671.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Backup from the Cloud (Salesforce.com). 3. Click Next >

1. The New Backup Set Wizard prompts you to select the Cloud Server to backup. 2. The Enter Network Credentials screen appears. F1 Help: See Specify Credentials (Windows DS-Client) on page 884. 3. You must enter credentials to the (Salesforce.com) Cloud Server and click OK. Enter the Salesforce.com username and password. Select the target database for backup (Production or Sandbox). Type or copy the security token that was E-Mailed to you by Salesforce.com. You can request the security token from the Salesforce.com website (Setup > My personal information > reset my security token). Click OK.

1. If DS-Client can successfully login to Salesforce.com, the New Backup Set Wizard switches to its Database List screen. 2. The Database List will contain only one database. Highlight it and click Add to backup this entire Salesforce.com database and tables. Optionally, you can click Tables to selectively include or exclude specific database tables from the backup. 3. Click Next >.


Confidential.


1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab on page 862. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. Click Next >.
Step 6. Select the Backup from the Cloud Parameters

1. You can specify some parameters that will affect the behavior of the backups.
F1 Help: See Set Properties - Backup from the Cloud (Salesforce.com) Parameters on page 856. 2. Click Next >.



Confidential.
Local DS-VDR backup set (VMware VADP)

Note: A Local DS-VDR backup set does not backup data to DS-System.
This type of backup set uses the Local DS-VDR Tool (separate installation) to interface with a VMware vCenter / Host. When you backup this set, the Local DS-VDR Tool will export the Virtual Machines (from the selected backup items) to another datastore on the vCenter / Host. This allows you to schedule backup of the latest generation of a Virtual Machine to a standby Virtual Machine that is always available (on the local vCenter / Host). For more information, refer to the following Knowledge Base article: Local DS-VDR backup set on page 673 There are some requirements that must be met in order to create a Local DS-VDR backup set: You must install the Local DS-VDR Tool on a network computer that can connect to both this DS-Client and the target VMware vCenter. This can be found on the installation DVD in the folder:
\Software\Tools\Local_DS-VDR\Windows_64_bit\setup.exe
The DS-Client must be configured to point to a Local DS-VDR Tool from Local DS-VDR menu > Configure Local DS-VDR Tool.
F1 Help: See Local DS-VDR Tool Setup on page 790. Each DS-Client must have its own, dedicated Local DS-VDR Tool. You cannot use the same Local DS-VDR Tool with multiple DS-Clients. The DS-Client must have at least one Local DS-VDR license count available. This is allocated by your Service Provider from DS-System.

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select VMware VADP. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. Highlight the VMware VADP tree. In the Path field:

Confidential.
You must manually enter the IP address of the VMware ESX server or VMware vCenter server. 3. By default, the credentials checkbox is selected and you must supply the credentials that the DS-Client will use to connect to the VMware ESX ser or VMware vCenter server. 4. Click Next >. To specify VMware logon credentials, refer to the F1 Help. F1 Help: See Specify Credentials (Windows DS-Client) on page 884. F1 Help: See Specify Credentials (Linux DS-Client) on page 886.

1. The New Backup Set Wizard switches to its Select items for backup screen. F1 Help: See Select Items for Backup (Linux DS-Client) on page 832. 2. Browse through the Shares & Directories List and click Add for as many items as are required. Note: Each Virtual Machine that is added to the Local DS-VDR backup set counts for 1 license from the pool allocated to this DS-Client. You can verify this in Setup Menu > View Quotas: DS-Client Local DS-VDR License.
3. Click Next >.

1. The New Backup Set Wizard switches to its backup item options screen. F1 Help: See Set Properties - Items tab on page 859. F1 Help: See Set Properties - Items tab (Linux DS-Client) on page 860. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. Note: A Local DS-VDR backup set does not backup data to DS-System. The backup item generations (Max Gen) setting for a Local DS-VDR backup set determines how many versions of a Virtual Machine will be exported on the vCenter. Once this limit is reached, the oldest exported VM is overwritten at the next backup.
3. Click Next >.

1. The New Backup Set Wizard switches to its backup set options screen. F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. You should leave the default settings alone, unless there are specific generation or option requirements for each backup item. 3. In the Additional Backup Set Options section, select Use Local DS-VDR. Once selected, the normal backup (to DS-System) options are disabled. 4. Click Next >.


Confidential.
Step 6. Specify the Local DS-VDR Backup Set Options

1. The New Backup Set Wizard switches to its backup set options screen.
F1 Help: See Set Properties - Options tab (Local DS-VDR backup sets) on page 872. 2. You must configure the destination on the vCenter, where you want the selected backup items (Virtual Machines) to be exported.
Backup Virtual Machine Memory Backup Virtual Machines snapshots Export to host ON: Saves the VM state (running programs loaded in memory). OFF: Backs up the VM as if it were not running. ON: Backup will export the actual running VM and all its snapshots. OFF: Backup will export the actual running VM only (no snapshots).
This dropdown list contains the available ESX hosts where you can export the selected Virtual Machines. You must assign one as the target. Click [>>] to open the Specify Credentials screen. This is dropdown list of available Datastores on the destination host where you can export the Virtual Machine. You must assign one as the target.
Export to datastore
3. Click Next >.

The steps for all subsequent screens are the same as for Windows File System Backups. Follow from Step 8. Specify Notification Options on page 107 in the section for File System Backups. Note: A Local DS-VDR backup set does not backup data to DS-System.


Confidential.
Physical to Virtual backup set

[DS-Client requires connection to a Local DS-VDR Tool for the backup set type to be available. Each Physical machine that is protected will cost one Local DS-VDR license count.] There are some requirements that must be met in order to create Physical to Virtual backup sets: 1. Your DS-Client must be configured with the Local DS-VDR Tool feature and be pointing to a running instance of the tool (Local DS-VDR menu > Configure Local DSVDR Tool). 2. You must install the following VMware component (package) on the Local DS-VDR Tool computer:
VMware vCenter Converter Standalone
This component can be found on the vmware.com Web site. Run the installation and choose the Client-Server installation (advanced) Setup Type. (Optional) Since the Local DS-VDR Tool and VMware vCenter Converter component are on the same computer, the DS-VDR Tool should be able to access the component without additional credentials. If connection errors occur (when creating the P2V backup set), you can specify the (administrator level) credentials that will be used to access the VMware vCenter Converter from Local DS-VDR menu > Local DS-VDR Settings.
F1 Help: See Local DS-VDR Settings on page 790. 3. This feature currently supports conversion of Windows physical machines only. For more information, refer to the following Knowledge Base article: Physical-to-Virtual backup set on page 675

1. Sets menu > New Backup Set. The New Backup Set Wizard screen appears. 2. Select Physical to Virtual. 3. Click Next >

1. The Select the source for this backup set screen appears. 2. For Windows DS-Clients: Manually enter the IP address of the physical machine you want to virtualize in the Path field. For Linux DS-Clients: Highlight the Physical to Virtual tree. In the Path field: You must manually enter the IP address of the physical machine you want to virtualize:

Confidential.
Physical to Virtual\IP_Address
For example:
Physical to Virtual\12.34.56.111
3. By default, your current user login to the DS-Client will be used to connect to the specified server. To specify different logon credentials select Ask for credentials. You are prompted to specify credentials. F1 Help: See Specify Credentials (Windows DS-Client) on page 884. F1 Help: See Specify Credentials (Linux DS-Client) on page 886. Note: These credentials are not immediately verified by the DS-Client. They will be used by the Local DS-VDR Tool when a Physical to Virtual backup is performed on this set.
4. Click Next >.

1. The New Backup Set Wizard switches to its Select items for backup screen. F1 Help: See Select Items for Backup (Linux DS-Client) on page 832. 2. You must highlight the physical machine in the Shares & Directories List and click Add in order for it to appear in the Selected Items for Backup section. Note: Each Virtual Machine that is added to the Local DS-VDR backup set counts for 1 license from the pool allocated to this DS-Client. You can verify this in Setup Menu > View Quotas: DS-Client Local DS-VDR License.
3. Click Next >.

1. The New Backup Set Wizard switches to its backup item options screen. F1 Help: See Set Properties - Items tab on page 859. F1 Help: See Set Properties - Items tab (Linux DS-Client) on page 860. 2. You should leave the default settings alone, unless there are specific generation requirements. Note: A Physical to Virtual backup set does not backup data to DS-System. The backup item generations (Max Gen) setting for a Physical to Virtual backup set determines how many versions of a physical machine will be virtualized on the vCenter. Once this limit is reached, the oldest backed up VM is overwritten at the next backup.
3. Click Next >.


Confidential.

1. The New Backup Set Wizard switches to its backup set options screen.
F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. You should leave the default settings alone, unless there are specific requirements. 3. In the Additional Backup Set Options section, specify the vCenter that will host the virtualized machine that is backed up. Once selected, the normal backup (to DS-System) options are disabled. 4. Click Next >.

Note:
A Physical to Virtual backup set does not backup data to DS-System.


Confidential.
5 - Backup Set Types
This section describes how to create and use the different backup set types (Statistical Backup Sets and Self-Contained Backup Sets).


Confidential.
Overview of Backup Set Types

This section describes the different types of backup sets. (These are in addition to the Regular type.) Statistical Backups on page 177 Self-Contained Backup Sets on page 178 Local-Only Backup Sets on page 179


Confidential.
Statistical Backups
Statistical backup data can be generated to determine the data backup usage and trends before performing actual backups. You do not need a customer account with a Service Provider, and no backup data is transmitted. Statistical data is gathered and stored in the DS-Client database. Statistical backup sets can help you to estimate the initial backup size, as well as the data change trends of your backup data. This allows you to determine how long the initial backup of baseline data will take. You can estimate the amount of changes your backup data will experience between backups (the greater the amount, the longer the backups time). To do so, simply let the backup(s) run on schedule for at least five or more full sessions. This will distinguish the backup data change trend from the initial baseline backup. Note: You cannot convert a Statistical Backup to a Regular Backup.
1. Configure the backup set in the New Backup Set Wizard. On the last tab (Choose the name for this backup set), you can select the backup set type. 2. In the Set Type list, select Statistical.
3.
4. 5. 6.
F1 Help: See Choose the name for this backup set screen on page 755. F1 Help: See Choose the name for this backup set screen (Linux DS-Client) on page 756. The Calculate Transmit Amount checkbox appears. Check this box to emulate an actual backup transfer process. During statistical backups, specified backup files will be read from their source and processed for compression/encryption. Click Finish. Allow the backup set to run on schedule (or demand). To generate accurate trends, you should let it run in your data environment for at least 1-2 weeks. Use the DS-Client Load Summary, Storage Summary and Report features to view the statistics generated. See the section: 11 - Logs and System Tools on page 322.


Confidential.
Self-Contained Backup Sets

Self-Contained Backup Sets perform backup and restore using only local storage. Like Statistical Backup Sets, this backup type is provided to help you to experience the features of Asigra Cloud Backup. Self-Contained backup sets have the following features and limitations: Platforms: DS-Client running on Windows / Linux / Mac Data is stored locally at customer site (local disk or UNC path) The Local Storage Path must be set (from Setup Menu > DS-Client Configuration > Parameters Tab) Up to 5 self-contained backup sets Up to a total of 10 GB of protected data Only one generation of a file is protected (only latest generation) Data stored is compressed Note: You cannot convert a Self-Contained Backup Set to a Regular Backup Set. You can use the Clone feature to duplicate it as a new Regular backup set (see Clone a Backup Set on page 197).
1. Configure the backup set in the New Backup Set Wizard. On the last tab (Choose the name for this backup set), you can select the backup set type. 2. In the Set Type list, select Self-Contained.
3. Click Finish.


Confidential.
Local-Only Backup Sets

Local-Only Backup Sets must be enabled by your Service Provider from the DS-System. These are the same as Self-Contained backup sets, but without the restrictions on number of sets or capacity. Local-Only backup sets have the following features and limitations: Platforms: DS-Client running on Windows / Linux / Mac Data is stored locally at customer site (local disk or UNC path) The Local Storage Path must be set (from Setup Menu > DS-Client Configuration > Parameters Tab) Data stored is compressed (however no Master/Delta processing is applied). The total amount of Local-Only storage is allocated from the DS-System (in GB). You can verify this in Setup Menu > View Quotas: DS-Client Local-Only Storage Quota. IMPORTANT: There must be enough capacity available in the Local Storage Path to accommodate the total amount of Local-Only capacity licensed. To convert a Local-Only backup set to a regular backup set, see Converting a Local-Only backup set to a Regular backup set on page 180. Local-Only backup set data is protected from accidental / inadvertent deletion with a Safe Delete mechanism. See Deleting Local-Only backup set data & Clean Local-Only Trash on page 181. 1. Configure the backup set in the New Backup Set Wizard. On the last tab (Choose the name for this backup set), you can select the backup set type. 2. In the Set Type list, select Local-Only.
3. Click Finish.


Confidential.
Converting a Local-Only backup set to a Regular backup set

At any time, you may convert an existing Local-Only backup set into a regular backup set (that sends its backup data to DS-System online storage). Conversion will perform the following: All the backup data in the Local-Only path will be copied to the DS-System. The backup set type will be changed from Local-Only to Regular. The backup sets Options Tab setting for Use Local Storage will have Save selected, meaning the backup set will continue to save a copy of data locally in the corresponding Local Storage Path. The number of generations that remain in Local Storage will depend on the backup sets Retention settings. (See Local Storage Tool on page 303.)
Note:
Conversion from Local-Only to Regular backup set type is one-way (you cannot revert once the data has been completely copied to the DS-System on-line storage).
1. 2. 3. 4.
Browse the Backup Set Tree and highlight the Local-Only backup set you want. Right-click. Click Convert. A confirmation screen appears. Click Yes to proceed. A Process Window opens to show the progress of the backup set conversion. If the conversion is interrupted before it has finished, the backup set will not be able to backup new data until the conversion process is either completed or cancelled. Those options (Convert / Cancel Convert) will appear in the right-click menu for this set.


Confidential.
Deleting Local-Only backup set data & Clean Local-Only Trash

Local-Only backup set data is stored in a Local Storage Path, which can be either the default path defined for the DS-Client (Setup menu > Configurations > Parameters tab) or a specific path defined for a backup set (Set Properties > Options tab). Local-Only backup set files can be deleted in the following ways: On demand, through the Delete Wizard; By a Retention Rule (Enforce Retention), either scheduled or on demand; Note: Local-Only backup sets use the Online Storage retention settings (and not the Local Storage retention settings which only applies to Regular backup sets configured with the Save on local storage option.). This is because the Local-Only backup sets behave exactly like Regular backup sets with the exception of where the data is stored. By automatic generation recycling, when a backup file reaches its maximum number of generations (Set Properties > Items tab: Max gen). Whenever Local-Only backup set files are deleted by the DS-Client, that data is moved to a recycle sub-folder of the Local Storage Path. This is a Safe Delete feature that reduces the chance of accidental or inadvertent deletion of data. Because of this move to trash behavior, customers must periodically Clean their Local-Only Trash folder(s): 1. Tools Menu > Clean Local-Only Trash. 2. In the Clean Local-Only Trash screen, select the Trash location.
F1 Help: See Clean Local-Only Trash on page 757. You must select how long (in days) that the data has been deleted in order to qualify for this Clean Trash process. By default, this will clean the trash from all local storage paths on the DSClient. You can also choose to clean the trash from a specific local storage path by selecting one from the drop down list. 3. Click OK. Note: This process can also be scheduled. See Add a Detail to a Schedule on page 78 for more information.


Confidential.
6 - Working with Backup Sets
This section contains instructions for working with backup sets. You can also consult the PDF document DS-Client User Guide (filename: dsuser.pdf). The PDF sections are reproduced in this online help (without screenshots), and can be viewed by navigating the Contents Tab at left.


Confidential.
View Backup Set Information

Backup options affect the way the set is handled during the backup process. Some options are specific to the type of server that is being backed up. 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Set Info.
F1 Help: See Set Properties - Set Info tab on page 876.


Confidential.
Modify Share Access Properties

It may be necessary to change the User Name and password associated with a backup set (For example: if you are creating backup set for someone with limited LAN access rights). The user name and password to "connect as" will be used to connect to the backup items on the LAN in the backup set. 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Share.
F1 Help: See Set Properties - Share tab on page 877. F1 Help: See Set Properties - Share tab (Linux DS-Client) on page 877. 5. Click >> beside the Connect As field. The Modify Network Credentials screen appears. See Ask for Network Credentials: on page 99. (Windows DS-Clients) If this is a share on the local (DS-Client) computer, and you are logged in to DS-User as an administrator, you have the option to use the DS-Client Account (the username and password used by the DS-Client service itself). 6. Type a new User Name and/or a new password to be associated with the backup set. 7. In the From list, select the machine where the DS-Client will verify the user information.


Confidential.
8. Click OK to save your changes and close the Modify Network Credentials screen. The Share Tab returns with the modified Connect As information.
9. Click OK to save any modifications.


Confidential.
Exclude files that failed to backup

[Windows DS-Client, File System Backup Sets only] This feature is added for your convenience when editing a backup set. You can exclude some or all from this list, allowing you to define the exclusion quickly (especially with long lists). 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Edit. The Edit Items screen appears. 5. Click Failed Files.
F1 Help: See Failed Files During Backup on page 781. 6. The file list is a cumulative list of every file that ever failed to back up since this backup set was created. Use the CTRL and SHIFT keys to highlight some or all of the files from the list, or Select one of the failed files and check Custom Exclude. This will exclude all files in the same path with the same extension. 7. Click Exclude. The Edit Items screen returns with your exclusions in the list of backup items selected. 8. Click Close. The Items Tab returns. You must click Apply or OK to save your changes.


Confidential.
Modify Database Information (MS SQL Servers)

1. 2. 3. 4. Browse the Backup Set Tree and highlight the backup set you want. Right-click. Click Properties. The Backup Set Properties screen appears on the Items Tab. Click Database.
F1 Help: See Set Properties - Database tab on page 858. If "Access integrated with share" is checked, you can only edit the credentials from the "Dump location" section. Windows authentication will be performed when connecting to the database. Note: Access integrated with share will not work if your network is using Windows Integrated Security. (Even though you can check and uncheck the box, and enter any credentials, the Windows Integrated Security ignores any credentials from the Database Info section.) 5. Click OK to save any modifications.


Confidential.
Modify Connection Information (MS Exchange Server and System i Server)

1. 2. 3. 4. Browse the Backup Set Tree and highlight the backup set you want. Right-click. Click Properties. The Backup Set Properties screen appears on the Items Tab. Click Connection.
F1 Help: See Set Properties - Connection tab on page 856. 5. Click OK to save any modifications.


Confidential.
Modify Connection Information (E-Mail backup sets)

This applies to E-Mail message backup sets created using DS-MLR (DS-Recovery Tools). 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Connection.
F1 Help: See Set Properties - Connections tab (E-Mail backup sets) on page 858. Click [>>] to modify the credentials used by the backup set. 5. Click OK to save any modifications.


Confidential.
Modify Connection Options (Linux DS-Client)

1. 2. 3. 4. Browse the Backup Set Tree and highlight the backup set you want. Right-click. Click Properties. The Backup Set Properties screen appears on the Items Tab. Click Connection Options.
F1 Help: See Set Properties - Connection Options tab (Linux DS-Client) on page 857. The amount of options depends on the type of backup set and whether the data source is local or remote. For details on these options, see the online help for the screen. 5. Click OK to save any modifications.


Confidential.
Re-name a Backup Set

You can rename a backup set from its Properties screen. 1. Browse the Backup Set Tree and highlight the backup set you want to rename. 2. Right-click. 3. Click Properties. The Backup Set Properties screen appears on the Items Tab. 4. Click Set Info. 5. In the Set name field, change the backup set name as desired.
6. Click OK to save the change. 7. The set reappears in the Backup Sets tree with the new name.


Confidential.
Suspend and Activate a Backup Set

Scheduled backups can be suspended indefinitely with the Suspend function. They will only resume when you use the Activate function. 1. In the Backup Set Tree, highlight the backup set you want.
2. Right-click. 3. Click Suspend or Activate on the Backup Set desired. 4. The set's name changes color to reflect its new status: black = active gray = suspended


Confidential.
Synchronize a Backup Set's Backup Logs

It is possible that a backup set's backup logs could fall out of synchronization with the DSSystem's Online storage. This could happen to regular backup sets for a variety of reasons (though not frequently during normal DS-Client operations). The synchronization process is used to correct discrepancies between the DS-Client backup set logs and the DS-System's Online storage if they occur. "Normal" synchronization is also run automatically during the Weekly Admin. and Scheduled Backup processes, if "Files not in sync" errors are found for a backup set. If the synchronization was successful, the files will maintain an active status. This enhances the probability of long-term unattended operation of the DS-Client. 1. In the Backup Set Tree, highlight the backup set you want. 2. Right-click. 3. Click Synchronize. The Select Synchronization Options screen appears. F1 Help: See Select Synchronization Options screen on page 849. 4. Choose the synchronization option, and click Synchronize. The Synchronization Process screen appears, showing the progress. 5. Verify any errors that occurred for the Synchronization process. Errors that state "Directory not in Backup Set" indicate that the directory was added to the Backup Set. 6. You may wish to run another Synchronization ("Check Only" this time) to verify that the synchronization was successful. If no errors appear in the Activity Log, the Backup Set is properly synchronized.


Confidential.
Migrate a Backup Set from one computer to another

A situation may arise, where you need to change the network provider (Microsoft Windows Network, NetWare, etc.), or computer from which the DS-Client backs up an existing backup set. (This is useful if you rename your computer, change the operating system, or change the physical location of files). Asigra Cloud Backup allows you to change the provider/computer of a backup set with the Migration feature. This involves selecting the backup set to migrate, then specifying the new path from which the backup set will be backed up. 1. In the Backup Set Tree, highlight the backup set you want. 2. Right-click. 3. Click Migrate. Browse and select the new network / node path where you want to migrate this backup set.
4. Click Next > If Ask for network credentials is checked, the Enter Network Credentials screen appears. Enter the User name, password, and source server (if applicable) from which to connect with the selected network / node, then click OK.


Confidential.
5. The Migrate Backup Set Wizard switches to match the source / destination shares screen.
F1 Help: See Migrate Shares screen on page 790. 6. Match each Source item with a Destination cell. 7. Click Next >. 8. The Select directories / files for backup screen appears.
9. The Selected Items for Backup remain, with their share path changed to the destination share selected in the previous tab. Make sure that the new path is correct for each backup item. You may add more files, or leave this screen unchanged. 10. Click Next >

Confidential.
11. The Specify backup item options screen appears.
12. Select the backup item options, as you would a normal backup set. Depending on which network you have migrated to, you may see more or less backup options than previously available for this backup set. 13. Click Finish to complete the migration. 14 The Backup Sets screen returns. If you check the properties for the migrated backup set (Sets menu > Backup Sets > Properties), you will see the changes to the provider, network and / or node. 15. Synchronize the migrated backup set. (See Synchronize a Backup Set's Backup Logs on page 193.) 16. You may now perform backups and restores with this backup set.


Confidential.
Clone a Backup Set

This is a shortcut to copying an existing backup set with all its settings, except retention rule, schedule and name. 1. In the Backup Set Tree, highlight the backup set you want. 2. Right-click 3. Click Clone. The Clone Backup Set Wizard appears on the Choose Retention Rule screen. [Optional] Select a Retention Rule. For more information, see About Retention Rules on page 85. 4. Click Next >. The Choose a Schedule screen appears. [Optional] Select a schedule. 5. Click Next >. The Choose the name for the backup set screen appears.
6. Select a set name, a set type, and click Finish. 7. The new backup set appears in the Backup Sets Tree.


Confidential.
Change Backup Set Ownership

The user who creates a backup set is that Backup Set's Owner. Administrators can change the ownership of a backup set (e.g. due to personnel changes). 1. Browse the Backup Set Tree for the backup set you want. 2. Right-click. 3. Click Change Owner. The Change Backup Set(s) Owner screen appears.
F1 Help: See Change Backup Set(s) Owner screen on page 752. 4. Click >>. The Select Group / User screen appears.
F1 Help: See Select Group / User screen on page 829. 5. Highlight the User you want, and click Select. 6. The Change Backup Set(s) owner screen returns with selected username. 7. Click OK to proceed with the change.


Confidential.
Backup Set Permissions

By default, only the administrator and the backup set's owner have permissions to a backup set. This includes viewing, changing, backing up, restoring or deleting the backup set or items in it. Backup Operators may perform demand backups on a backup set, as well as change the schedule applied to it. These backup set permissions may be modified. 1. Browse the Backup Set Tree for the backup set you want. 2. Right-click. 3. Click Permissions. The Backup Set Permissions screen appears, showing users other than the owner or Administrator, with rights to this backup set.
F1 Help: See Permissions screen on page 797. 4. To add permissions to a user or group, click Add. The Add Permission for Users and Groups screen appears. Users and groups only appear once they have logged into the DS-Client.
F1 Help: See Add / Edit Permissions for a User or Group screen on page 741. 5. Highlight the user or group that is to receive permissions. 6. In the Permission type section, check all permissions you want to apply: Backup, Restore, Modify and Delete. 7. Click Add to add the permissions. The Backup Set Permissions screen returns with the new user or group and permissions listed. 8. Click Close to exit this screen.


Confidential.
7 - Deleting Backup Sets and Online Files
This section describes how to delete backup sets, and permanently remove backed up files or file generations that are stored Online on the DS-System.


Confidential.
Overview of Delete Options

Since there is a cost to storing data, you may decide to remove obsolete items (backup sets, directories, specific files and/or file versions) from Online storage. WARNING:Take care in any delete situation, since once data is deleted, it is gone.
Delete Option Selective Delete Assisted Delete Delete Backup Set
Description Allows you to choose items to delete from a single backup set. See: Selective Delete from Online Storage on page 202 Displays items to delete from all the DS-Clients backup sets. See: Assisted Delete from Online storage on page 206 Delete all of the backup sets files and remove the backup set from the DS-Client. See: Remove Backup Set from Online Storage on page 209
For more more detailed information about delete behavior in more advanced scenarios, see the Knowledge Base article Delete Considerations on page 522.


Confidential.
Selective Delete from Online Storage

Since there is a cost to storing data, you may decide to remove obsolete items (backup sets, directories, specific files and/or file versions) from Online storage. Performing a Selective Delete will remove the selected directories from Online Storage. The backup set, however, will continue to exist (and scheduled backups will continue to be performed).
Delete Directories
1. Browse the Backup Set Tree for the backup set you want. 2. Right-click. 3. Click Delete. The Delete Wizard screen appears on the Select how you want to delete screen.
F1 Help: See Select how you want to delete screen on page 829. 4. For details on these options, see the online help for the screen. Selections in this screen help to narrow the display of files and directories for delete in the last Wizard Tab. In the Data selection for Delete section, select the method that this Wizard will use to select data. Time based data selection is the default, but Windows has additional options if the data source is using a recognized HSM system (i.e. if a placeholder/stub is detected on the source). Select the period of backups that you want to delete.


Confidential.
5. Click Next >. The Delete Wizard switches to allow you to select delete options. For details on these options, see the online help for the screen.
F1 Help: See Select how you want to delete (Delete Options) screen on page 830. Archived data placeholders: These options relate to displaying generations that have already been pushed to BLM from online storage (i.e. the actual file has been removed from online to BLM). Select what you want to display in the next screen of the Delete Wizard (Include archived files, exclude archived files, or show only archived files). Move to BLM: select if you want to send a copy of all the files that are deleted to BLM.


Confidential.
6. The Select directories/files to delete screen appears. The contents of the Tree depend on the options specified in the previous screen.
F1 Help: See Select directories / files (Restore / BLM / Delete / Validation) on page 826. 7. Browse through the Directory Tree and check the box beside each directory you want to delete. The number and total size of the files selected for delete appear at the bottom of the screen. 8. Click Finish. The Delete Process Screen appears.
Delete Individual Files

1. Follow Steps 1-7 in the previous section Delete Directories on page 202. The Select directories/files to delete screen appears. 2. Highlight the directory containing the files you want to delete. 3. Click Show Files, the Files List appears, showing all of the files in the highlighted directory.


Confidential.
4. The Files List section appears. 5. Browse through the Files List and check the box beside each file you want to delete. 6. The number and total size of the files selected for delete appear at the bottom of the screen. 7. You can view your delete selections by clicking the Selection button. The Delete Selection screen appears, showing the full path \ file name of each delete item.
F1 Help: See Selection screen on page 852. 8. Click Finish. The Delete Process Screen appears.


Confidential.
Assisted Delete from Online storage

Assisted Delete allows you to delete obsolete online data from several backup sets in one process. The granularity of the delete depends on the DS-Client: Windows DS-Clients delete from ALL the File System & DS-MLR backup sets. The Assisted Delete Wizard automatically selects any directories that have been removed from the backup source. Linux / Mac DS-Clients delete from ALL the NAS, UNIX-SSH, NFS, Local File System backup sets. The Assisted Delete Wizard automatically selects any directories that have been removed from the backup source, or that contain file(s) that have been removed from the backup source. Note: On Linux/Mac DS-Client, directories containing deleted files can be selected, but only the obsolete files will be deleted.
Note:
Items (directories / files) from the source are detected during the backup session. This means, if no backups have run recently, any items deleted since the last backup will not be included in the Assisted Delete Wizards selection.
1. Sets Menu > Delete > Assisted Delete.


Confidential.
2. The Assisted Delete Wizard appears on the Select how you want to delete tab.
F1 Help: See Assisted Delete - Select how you want to delete on page 745. 3. For details on these options, see the online help for the screen. Selections in this screen help to narrow the display of directories for delete in the next Wizard Tab. In the Delete Period section, select the range of backups to delete and the number of generations (if any) you want to leave online. In the Filter Section, enter the cut-off date and time that you want to apply against items that qualify for the Delete Period: For Windows DS-Client: The Assisted Delete Wizard will only display directories that were deleted from the source backup computer before this date & time. The Filter is applied against the directories that match the Delete Period.
For Linux/Mac DS-Client: The Assisted Delete Wizard will only display directories (or directories containing files) that were deleted from the source backup computer before this date & time. The Filter is applied against the directories/files that match the Delete Period. [Windows DS-Client only]: For file system backup sets, you have an additional option for deleting files if a placeholder/stub is detected on the source. Move to BLM: select if you want to send a copy of all the files that are deleted to BLM.


Confidential.
4. Click Next >. The Select Backup sets/directories tab appears.
F1 Help: See Assisted Delete - Select Backup Set / Directory on page 745. 5. Directories that are grayed out do not match the Delete Period or Filter selections. You can deselect items in this screen, as required. Windows DS-Clients perform selection at the directory-level. The Assisted Delete Wizard automatically selects any directories that have been removed from the backup source. (It will not select individual files in a directory.) Linux / Mac DS-Clients perform selection at the file-level. The Assisted Delete Wizard automatically selects any directories that have been removed from the backup source, or that contain file(s) that have been removed from the backup source. 6. Click Finish to start the Delete Process.


Confidential.
Remove Backup Set from Online Storage

Since there is a cost to storing data Online, you may decide to remove obsolete items (backup sets, directories, specific files and/or file versions) from Online storage. This option will remove all Online backups of the set (and the set itself). Note: You can only remove Initial Backup sets that are marked incomplete. See Monitor Initial Backup Sets on page 282.
1. Browse through and highlight the backup set you want to delete.
2. Sets Menu > Delete > Remove Backup Set. The Remove Backup Set screen appears.
F1 Help: See Remove Backup Set on page 809. For details on these options, see the online help for the screen. 3. Press the 'OK' button to continue. A confirmation screen appears. Click 'Y' to remove the set. Press any other key to abort.


Confidential.
8 - Demand Backups
8 - Demand Backups
Asigra Cloud Backup is designed to perform unattended backups at scheduled intervals. However, you may want to back up certain files at other times (on demand). This section provides information on how to perform such demand backups.


Confidential.
8 - Demand Backups
Perform a Demand Backup

You can perform demand (immediate) backups at any time. The options available depend on the backup set type. 1. Browse the backup set tree and highlight the backup set you want. 2. Right-click. 3. Click Backup Now. The Backup Now Wizard screen appears on the Select items for demand backup screen.
F1 Help: See Select items for demand backup screen on page 833. 4. A check mark appears beside each item to indicate it is selected for the demand backup. Uncheck any item(s) you do not want to backup. 5. You may change a backup item's options (for this session only) by highlighting it, then checking or un-checking the option boxes that appear at the bottom of the tab.


Confidential.
8 - Demand Backups
6. Click Next >. The Select options for demand backup screen appears.
7. 8.
9. 10.
F1 Help: See Select options for demand backup screen on page 836. F1 Help: See Select options for demand backup screen (Linux DS-Client) on page 837. In the Backup set options section, you may select options for this demand backup session. In the Open files section you can specify how the DS-Client will deal with any open files encountered during the backup. Note: This does not guarantee an open file will be backed up. An error will appear in the activity log if the files are not backed up. To backup locked files, you must use the VSS option or backup set type (See: Backup of Open Files Knowledge Base article - Backup of Open Files on page 546). Click Finish to start the backup procedure. The Backup Process screen appears, showing the progress of the backup session.


Confidential.
8 - Demand Backups
Initial Backup (Premium Service)

For more information, see Initial Backup on page 279 from section Section 10 - Premium Backup and Recovery Services.


Confidential.
9 - Restoring Backups
This section describes how to restore your backed up data. Various options are available to help you select the specific items to restore.


Confidential.
Introduction & Common Functions

Restores are conducted per backup set: Select the backup set to restore Select the locations The Restore Wizard assists you with the selection and options. An overview of common functions is presented in this section. Separate sections appear with instruction for restoring each kind of backup set.
Step 1. Select the backup set Restore Wizard Screen
See Step 1. Select the Backup Set on page 225. Description See Step 2. Select the Restore Items on page 225. See Advanced Restore Options on page 217. See Restore a Specific File or Files of a Specific Pattern on page 219. See Restore only files that differ from those on the backup source volume on page 221. See Restore an Older Generation of a File on page 222. See Step 3. Specify the Restore Location on page 227. See Restore to an Alternate Location on page 261. See Step 4. Specify the Restore Performance Options (Windows DS-Client) on page 228. See Step 5. Specify the Restore Options on page 229. See Pre/Post Restore Activity on page 223.
Step 2. Select Items for Restore
Step 3. Select restore location Step 4. Select performance options Step 5. Specify restore options


Confidential.
Specific Backup Type restore descriptions can be found in the following sections:
Backup Type Restore File System Backups on page 225 Restore MS SQL Server Backups on page 234 Restore MS Exchange Server Backups on page 237 Restore Permissions Only Backups on page 239 Restore Oracle Server Backups on page 240 Restore MySQL Backups on page 241 Restore DB2 Backups on page 242 Restore PostgreSQL Backups on page 243 Restore E-Mail Backups (via DS-Recovery Tools) on page 244 Restore System i Server Backups on page 246 Restore MS SharePoint Backups (via DS-Recovery Tools) on page 248 Restore Lotus Domino Server Database Backups on page 249 Restore Sybase Database Backups on page 250 Restore VSS-aware Backups on page 251 Restore VMware VADP Backups on page 254 Restore a Backup from the Cloud (Salesforce.com) Backup Set on page 257


Confidential.
Advanced Restore Options

The Advanced Restore Options screen allows you to narrow your restore selection: Select from a single backup session Select from a period of backups Filter the selection to show only deleted files Specify a file overwrite policy for the restore files 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click. 3. Click Restore Now. 4. The Restore Now Wizard opens and the Select directories / files to restore screen appears.
F1 Help: See Select directories / files (Restore / BLM / Delete / Validation) on page 826.


Confidential.
5. Click Advanced. The Advanced Restore Options screen appears.
F1 Help: See Advanced Options screen on page 743. 6. Specify the Advanced Restore Options. Select from a single backup session Select from a period of backups Select the filter for deleted data. You can show all data (including deleted data) or you can hide / show only the deleted data from before a specific date and time (backup session). Note: During each backup session, the DS-Client scans the directories on the backup source. Over the course of time, some directories may have been deleted from the source. Using a filter avoids restoring directories that were intentionally deleted. Specify a file overwrite policy for the restore files 7. When you have finished your selections, click OK. The Select directories/files screen returns with the new restore selection availability. 8. In the Directories Tree, only those directories that match the specified restore options will appear. 9. When you are finished selecting making your selections, click Next >. Follow from Step 3. Specify the Restore Location on page 227 to complete the restore.


Confidential.
Restore a Specific File or Files of a Specific Pattern

A backup set may contain so many files, that you cannot easily find the specific file(s) you want to restore. In this case, you can use the Find Backed Up File function to search through the entire set for the desired file(s). 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click. 3. Click Restore Now. 4. The Restore Now Wizard opens and the Select directories / files to restore screen appears. 5. Click Show Files. The screen expands to show the Files List, and the Find File button activates.
6. Click Find File. The Find Backed Up File screen appears.
F1 Help: See Find Backed Up File screen on page 783.


Confidential.
7. In the Search For section, enter the name/pattern of the file you would like to find. (ex: document.doc will search the entire backup set for that specific file; *.exe will search for all files with the .exe file extension). 8. Click Find. All files (including each generation of a file) that meet the search parameters are displayed (including their original directory path). 9. Highlight the file that you want to select to restore. 10. Click Select. The Select Files to Restore screen reappears with the selected file added to your restore list. The Files List appears and shows the contents of the directory that contains the specified file. 11. Repeat as necessary. When you are finished selecting files to restore, click Next >. 12. Follow from Step 3. Specify the Restore Location on page 227 to complete the restore.


Confidential.
Restore only files that differ from those on the backup source volume
You may wish to restore only the files that are different (or do not exist) from those on the destination volume. In this case, you can use the Show/Add Modified function to search through the destination volume's directories, and select only those backed up files that are different from those scanned on the destination. 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click, then select Restore Now from the menu. 3. The Restore Now Wizard opens. 4. Browse through the Directories Tree and highlight the directory containing the files you want to restore. 5. Click Show Files. The Files List section appears with the files in the selected directory.
6. Click Show Modified to show any modified files in the selected directory. The DSClient will scan the backup source, and compare the files with the backup log. Files in the list that do not exist on the source, or are different (changed), will be highlighted. 7. The Show Modified button changes to Add Modified. Click to add all of the modified files to the restore selection. 8. Repeat as necessary. When you are finished selecting files to restore, click Next >. 9. Follow from Step 3. Specify the Restore Location on page 227 to complete the restore.


Confidential.
Restore an Older Generation of a File

In some cases, you may wish to restore an older version of a backed up file. This is useful if you discover that files after a certain date became corrupted. The number of Online generations is specified in the backup set item's Generation settings. Note: If you select an older file generation, the directories/files displayed will change to show the files backed up with the selected generation. The From and To fields in the Restore Period (see Advanced Restore Options on page 217) changes to the backup time of the selected backup generation.
1. 2. 3. 4. 5.
Browse the Backup Sets tree and highlight the one you want to restore. Right-click, then select Restore Now from the menu. The Restore Now Wizard opens. Browse through and highlight the directory with the file you want to restore. Click Show Files. The Files List Appears.
6. Browse through and highlight the file whose previous generation you want to restore.


Confidential.
7. Click File Info. The Backup Generations screen appears.
8. 9. 10. 11.
F1 Help: See Backup Generations for ... screen on page 747. Highlight the desired generation of the file from the list and click Select. The Restore Now Wizard returns to the Select Files and Directories screen, with your selection highlighted with a red checkbox. The directory list refreshes automatically to reflect the time of the selected generation. Click Next >. Follow from Step 3. Specify the Restore Location on page 227 to complete the restore.
Pre/Post Restore Activity

The DS-Client can perform an activity before and/or after the restore operation runs. This is the same feature used in backups. It runs on either the DS-Client computer or on the target restore computer. For example: stopping an NT service, restoring the files, restarting the NT service. Once you set the Pre/Post Execution Options for a backup set, they will be automatically reapplied on each subsequent restore of the set. Use the Skip Pre/Post checkbox to skip the Pre/ Post restore options (if any have been specified). 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click. 3. Click Restore Now. 4. Follow the steps for restoring until you reach the Select restore options screen. F1 Help: See Select restore options screen on page 842. F1 Help: See Select restore options screen (SQL / Microsoft Exchange / Oracle / System i) on page 845.


Confidential.
5. Uncheck the Skip Pre/Post box. The Pre/Post Button appears.
6. Click Pre/Post. The Pre & Post Execution screen appears for this backup set. F1 Help: See Pre & Post Execution screen on page 797. F1 Help: See Pre & Post Execution screen (Linux DS-Client) on page 799. 7. Follow the steps specified in the section: Backup Set Options - Pre/Post on page 97) 8. Click OK when you are finished. The Select restore options screen returns. 9. Click Finish to start the Restore. The specified Pre/Post options will be saved, and reapplied during each subsequent restore of this backup set.


Confidential.
Restore File System Backups

File System backup sets are the most common backup type. Since the restore steps and options of other backup types are similar, an explanation of all restore steps is provided for File System backups. Abridged explanations are provided for other backup types (relevant differences are noted). Restoring a backup set involves the following basic steps: Step 1. Select the Backup Set on page 225 Step 2. Select the Restore Items on page 225 Step 3. Specify the Restore Location on page 227 Step 5. Specify the Restore Options on page 229 Further information is available for special backup sets: Restore Windows System State (Registry) and Services Database on page 230 Restore NetWare Servers (Files and NDS) on page 232 Restore Continuous Data Protection Backup Set on page 233
Step 1. Select the Backup Set

1. 2. 3. 4. Browse the Backup Sets tree and highlight the one you want to restore. Right-click Click Restore Now. The Restore Now Wizard opens and the Select directories / files to restore screen appears. F1 Help: See Select directories / files (Restore / BLM / Delete / Validation) on page 826.
Step 2. Select the Restore Items

1. For directories, check the box beside each directory you want to restore.
2. In the Directory Tree, check the box beside each directory you wish to select for restore. You may choose multiple directories.


Confidential.
3. For individual files, browse through the directories list tree and highlight the directory that contains the files you want to restore.
4. Click Show Files. The screen expands to display the File List section.
5. In the Files List section options: Selectively choose files for restore. View and select by File Info (See Restore an Older Generation of a File on page 222.) Show modified, and select modified files: See the Restore Options section Restore only files that differ from those on the backup source volume on page 221


Confidential.
6. To review the selected restore items, click Selection. The Restore Selection screen shows the selected restore items.
F1 Help: See Selection screen on page 852. 7. When you have made all your restore selections, click Next >. Archived to BLM popup: If this backup set has been configured with a Retention Rule that includes the Archive old data to BLM option, you may encounter a popup indicating some files in your restore selection have been archived to BLM. If this occurs, it means some files have been moved to BLM and you can only restore those files by requesting a BLM image of that data.
Step 3. Specify the Restore Location

1. The Restore Now Wizard switches to its Select Restore Location screen.
F1 Help: See Select restore location screen on page 840. 3. Select the restore location:


Confidential.
Original location - By default, the restore will be to the original backup location. This will overwrite any existing files of the same name. Alternate location - see Restore to an Alternate Location on page 261. 4. Click Next >.
Step 4. Specify the Restore Performance Options (Windows DSClient)

This screen only appears for Windows DS-Clients (except Permissions Only backup sets). Linux DS-Clients skip to Step 5. Specify the Restore Options on page 229. 1. The Restore Now Wizard switches to its Select restore performance options screen.
F1 Help: See Select Restore Performance Options (Windows DS-Client) on page 847. 2. These options are intended for large backup sets in high performance environments. In general, you should use the defaults and skip to the next screen. For more information, see the F1 help for this screen. 3. Click Next >.


Confidential.
Step 5. Specify the Restore Options

1. The Select restore options screen appears.
F1 Help: See Select restore options screen on page 842. 2. Select all restore options you require. Restore Method Description
OPTION Save Fast All Files use indirect restore method. All Files use direct restore method.
Direct restore method: Files are restored on a "write-data-as-received" basis. Files are overwritten upon receipt of the first byte of data. Indirect restore method: Restores files to a temporary location first. If the file is restored successfully, then the original file is overwritten with the temporary file. This prevents partially restored files from overwriting an existing file. 3. Click Finish to restore as specified. 4. The Restore Process screen appears, showing the progress of each file as it is restored. Note: The amount of data received may be different from the transmitted amount (in the backup logs). This happens because the DS-Client sends some additional information during backup (file name, size, etc.), that is stored on the DS-System. This information is not sent on restore, and may cause a difference of about 50 bytes per file.


Confidential.
Restore Windows System State (Registry) and Services Database

Windows backup sets have additional special backup items that can be selected for backup: System State (Registry for Windows NT) Services Database One example of when you would want to recover the System State (Registry) would be if a user account was accidentally deleted from a Windows computer. Since they are generated with a unique Security ID, the only way to recover the user account is to restore a backed up Registry / System State containing the deleted user account. Note: The Registry/System State contains information that is critical to your computer and applications. Use caution when using this feature.
1. 2. 3. 4.
Browse the Backup Sets tree and highlight the one you want to restore. Right-click, then select Restore Now from the menu. The Restore Now Wizard opens. Check the box beside the System State and/or Services Database icon in the Directory Tree.
5. The Restore Now Wizard switches to its Select restore performance options screen.


Confidential.
6. Click Next >. The Select Restore Location screen appears.
7. The default settings will automatically restore the System State / Services Database to its original source location. Note: Disable the Use Buffer option for System State restores. This may cause restore problems. 8. Click Finish to start the restore. 9. Once the Restore is complete, you must re-boot the computer before the restored System State / Services Database takes effect. 10. If you are satisfied with the restored System State (Registry) after rebooting, you can manually delete all of your old Registry files. The old Windows Registry files will be located in the following directories: %SystemRoot%\HKEY_LOCAL_MACHINE\ %SystemRoot%\HKEY_USERS\ where %SystemRoot% points to C:\Windows by default on Windows 2003, XP and higher Operating Systems. Note: You will lose any registry changes that have occurred since the backup time of the System State / Services Database being restored.
For more information, refer to the following DS-Client Knowledge Base Articles: Backing up Windows for Bare Metal Restore (BMR) on page 534 Backup / Restore of Windows 2000 on page 592 Bare Metal Restore of Windows (ALL VERSIONS) on page 693


Confidential.
Restore NetWare Servers (Files and NDS)

Restoring NetWare Server files is essentially the same as other restores. The following describes some Server-specific options and notes. 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click, then select Restore Now from the menu. 3. The Restore Wizard opens on the Select Directories/Files screen.
4. Select the restore item(s) from the Directory Tree. 5. Click Next >. The Select Restore Location screen appears.
6. The Restore Now Wizard switches to its Select restore performance options screen.


Confidential.
7. Click Next >. The Select Restore Options screen appears.
8. Note the following options:

Trustees If you are restoring to an existing directory, the DS-Client will append the trustee assignments to those of the existing directory. If your intention is to CLEAR the existing permissions, you MUST DELETE the existing directory, then restore. In the Restore NDS Object(s) from field, you may specify the object (container or leaf) which you want to restore. The object name should be typeless and fully qualified (distinguished) from the Root. (The default is to restore the whole NDS).
If restoring NDS
9. Click Finish to start the restore. Once the files are restored, it may take a few minutes to load the NDS (if it was restored).
Restore Continuous Data Protection Backup Set

Restoring a CDP backup set files is essentially the same as Regular File System backup set restores. The only difference occurs if you need to select from a range of backups. Since files in a CDP backup set have been backed up individually, as changes were detected, you can only distinguish previous versions by the time they were backed up. 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click, then select Restore Now from the menu. 3. The Restore Wizard opens on the Select Directories/Files screen. To select data from a specific period, click Advanced. In the Advanced Restore Options screen, click Selective data (from a certain period). F1 Help: See Advanced Options screen on page 743. In the Restore Period section, click [>>] beside the From and To fields to open the Select backup time screen. Click OK. 4. Select the restore item(s) from the Directory Tree. 5. Continue from Step 2. Select the Restore Items on page 225 for File System Backup Sets.


Confidential.
Restore MS SQL Server Backups

Only users with sufficient permissions may restore SQL Servers. Steps which are the same, or very similar to File System restores are condensed.

1. Highlight the MS SQL Server backup set you want to restore. 2. Restore Menu > Restore Now. The Restore Now Wizard appears on the Select Backup Set screen. 3. Browse through the tree of backup sets and highlight the one that contains the backup items you want to restore. 4. Click Next >.
Step 2. Select the Database(s)

1. The Select Databases to restore screen appears. Browse through the tree and highlight the database(s) you want.
2. The total size of the file selection and the total number of files selected appear in the Selected for Restore section. 3. To view and/or select individual database tables, highlight a database and click Show Files. 4. Click Next >.


Confidential.

1. The Restore Now Wizard switches to its Specify Database Restore Location screen.
F1 Help: See Select database restore location screen (MS SQL / PostgreSQL / MySQL) on page 824. 2. Select the restore location: Original location - By default, the restore will be to the original backup location. This will overwrite any existing files of the same name. Alternate location - see MS SQL Server Backup Sets (Alternate Location Restore) on page 266. 3. Select the Restore Options. 4. Click Next >.
Step 4. Specify the Restore Performance Options

1. The Restore Now Wizard switches to its Select restore performance options screen. F1 Help: See Select Restore Performance Options (Windows DS-Client) on page 847. 2. These options are intended for large backup sets in high performance environments. In general, you should use the defaults and skip to the next screen. For more information, see the F1 help for this screen. 3. Click Next >.


Confidential.

1. The Restore Now Wizard switches to its Specify Database Restore Options screen. F1 Help: See Select restore options screen (SQL / Microsoft Exchange / Oracle / System i) on page 845. 2. Select restore options. 3. Click Finish to complete specifications and begin the restore. 4. The Restore Process screen appears, showing the progress of each file as it is restored. If restoring Microsoft SQL Server 2005 (or higher), you may want to run a MS SQL maintenance task to shrink the log files and reclaim unused space. Note: For more information on Restoring MS SQL Server backups, please review the Knowledge Base articles: Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560 and Restoring the MS SQL Database Server MASTER Database on page 722.


Confidential.
Restore MS Exchange Server Backups

Only users with the proper authority may restore MS Exchange backups. The following headings show the various steps. Steps that are similar to File System restores have been condensed.

1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click. Click Restore Now.

1. Browse through the tree and highlight the database(s) you want. 2. Click Add. The highlighted database will be tagged for restore.
3. The total size of the file selection, and the total number of files selected appear in the Selected for Restore section. 4. Repeat 1-2 for as many databases as required. 5. Click Next >. DS-Client will try to detect if a Recovery Storage Group (RSG) exists on selected Exchange server. An RSG is a specially defined location on an MS Exchange 2003 server where any recovered data is saved. Note: This process may take a while, depending on your network environment. If an RSG exists, the selected database will be restored to that location. A popup message will inform you of this. Note: The target Exchange servers RSG must use the exact name "Recovery Storage Group".


Confidential.
Step 3. Specify the Restore Location and Options

1. The Restore Now Wizard switches to its Select database restore location screen. If there is no Recovery Storage Group, the default is to restore the Exchange databases to their original backup source location(s).
F1 Help: See Select database restore location screen (Microsoft Exchange) on page 824. 2. Select the restore location: Original location - By default, the restore will be to the original backup location. This will overwrite any existing files of the same name. Alternate location - see MS Exchange Server Backup Sets (Alternate Location Restore) on page 268. 3. In the Restore Options section, check all options that you require. 4. Click Next >.


1. 2. 3. 4. The Restore Now Wizard switches to its Select restore options screen. Select restore options. Click Finish to complete specifications and begin the restore. The Restore Process screen appears, showing the progress of each file as it is restored.
Confidential.

Restore Permissions Only Backups

Only users with the proper authority may restore Permissions Only backups. The following headings show the various steps. Steps that are similar to File System restores have been condensed.


1. Browse through the tree and highlight the permission(s) you want. 2. For each path, permissions are backed up as a single file named dump.acl. 3. Click Next >.

1. The Restore Now Wizard switches to its Specify Restore Location screen. 2. Select the restore location. 3. Click Next >.

1. 2. 3. 4. The Restore Now Wizard switches to its Specify Restore Options screen. Select restore options Click Finish to begin the restore. The Restore Process screen appears, showing the progress of each file as it is restored.


Confidential.
Restore Oracle Server Backups

The steps are the same as for MS SQL Server Backups. However, there are requirements and limitations. You must refer to the DS-Client Knowledge Base Article: Backup / Restore of Oracle Database Servers on page 573. Specifically, look at the sections: Backup Requirements (Oracle Server) Oracle Database Backup Sets (Alternate Location Restore). Additional information can be found in the Article: Oracle Database Point-In-Time Recovery (DBPITR) on page 724


Confidential.
Restore MySQL Backups

Only users with the proper authority may restore MySQL backups. The following headings show the various steps. Steps that are similar to File System restores have been condensed.


1. Browse through the tree and highlight the database(s) you want. 2. The total size of the file selection, and the total number of files selected appear in the Selected for Restore section. 3. Repeat 1-2 for as many databases as required.

Step 4. Specify the Restore Performance Options (Windows DSClient)

This screen only appears on Windows DS-Clients. Linux DS-Clients skip to Step 5. Specify the Restore Options on page 241. 1. The Restore Now Wizard switches to its Select restore performance options screen. F1 Help: See Select Restore Performance Options (Windows DS-Client) on page 847. 2. These options are intended for large backup sets in high performance environments. In general, you should use the defaults and skip to the next screen. For more information, see the F1 help for this screen. 3. Click Next >.

1. 2. 3. 4. The Restore Now Wizard switches to its Specify Restore Options screen. Select restore options. Click Finish to begin the restore. The Restore Process screen appears, showing the progress of each file as it is restored.


Confidential.
Restore DB2 Backups

There are some requirements that must be met in order to perform restores of DB2 backups. You must refer to the DS-Client Knowledge Base Article: DB2 Database Servers (See Backup / Restore of DB2 Database Servers on page 587.). Only users with the proper authority may restore DB2 backups. The following headings show the various steps. Steps that are similar to File System restores have been condensed.






Confidential.
Restore PostgreSQL Backups

Only users with the proper authority may restore PostgreSQL backups. The following headings show the various steps. Steps that are similar to File System restores have been condensed.






Confidential.
Restore E-Mail Backups (via DS-Recovery Tools)

NOTE: From v.7.0, the DS-MLR Service is bundled with the DS-Recovery Tools installation. [Windows DS-Client] Steps that are similar to File System restores have been condensed. See DS-MLR Installation & Setup on page 434. See Backup / Restore of E-Mails (using DS-MLR) on page 599.


1. Browse through the tree and check the item(s) you want.
2. To filter for specific E-Mails, click Filter. F1 Help: See Select Filter on page 829. In the Select Filter screen, specify the filter conditions. You can make complex filters with the AND, OR, and BRACKETS. When finished, click OK. The Restore Wizard will only display those E-Mails that match the filter description. Select the item(s) you want. 3. Click Next >.


Confidential.

1. By default, data is restored to the original backup source location(s).
2. Select the restore location: Original location Alternate location - You must select the alternate server and the dump location, then map the Source Mailbox to the Destination Mailbox. 3. Click Next >.


1. Select the restore options you want. 2. Click Finish to begin the restore.


Confidential.
Restore System i Server Backups

Steps that are similar to File System restores have been condensed.


1. Browse through the tree and check the item(s) you want. To restore individual Backup Objects: a)Click Show Files > Highlight an item in the Files List b)Click File Info > Highlight the generation to restore c)Click Objects
F1 Help: See Backup Objects for ... (System i Server and Backup from the Cloud) on page 748. d)Use the "Select"/"Deselect" buttons to selectively restore only the objects you need. Unselecting objects has no influence on the restore speed if the objects were backed up without the "Individual obj." option. 2. Repeat 1 for as many items as required. 3. Click Next >.


Confidential.

2. Select the restore location: Original location Alternate location - You must select the alternate server and the dump location, then map the Source Library to the Destination Library. 3. Click Next >.




Confidential.
Restore MS SharePoint Backups (via DS-Recovery Tools)



1. Browse through the tree and check the item(s) you want. 2. Click Next >.

1. By default, data is restored to the original backup source location(s). 2. Select the restore location: Original location Alternate location - You must select the alternate server and the dump location, then map the Source SharePoint Server to the Destination SharePoint Server. 3. Click Next >.




Confidential.
Restore Lotus Domino Server Database Backups

Steps that are similar to File System restores have been condensed. For more information, refer to the following Knowledge Base article: Backup / Restore of Lotus Domino Server Databases on page 631



1. By default, data is restored to the original backup source location(s). 2. Select the original restore location: Alternate Location Restore is not available for this kind of backup set. 3. Click Next >.




Confidential.
Restore Sybase Database Backups




1. By default, data is restored to the original backup source location(s). 2. Select the restore location: Original location Alternate location - You must select the alternate Sybase server and the dump location, then map the Source database to the Destination database. 3. Click Next >.



Confidential.
Restore VSS-aware Backups

Steps that are similar to File System restores have been condensed. For more information, refer to the following Knowledge Base articles: Backup / Restore of Microsoft SQL Server (VSS-aware backup sets) on page 638 Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) on page 640 Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644 Backup / Restore of Microsoft SharePoint 2007 (VSS-aware backup sets) on page 649 Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets) on page 655

Step 2. Select the VSS Restore Method

1. There are two different VSS restore methods, which you can toggle.
F1 Help: See Select the VSS Restore Method on page 852. VSS Restore: Performs an online restore of the selected backup session to the original backup source (or alternate location) using the target computers Microsoft VSS tools. File Restore: Allows you to selectively restore individual files from a backup session. These are pure file restores, which can be useful with the corresponding Microsoft SQL Server, Exchange or SharePoint management tools. Granular Restore: This applies to SharePoint 2010 only. See Item-Level Restore of SharePoint 2010 in the Knowledge Base Article Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets) on page 655.
Confidential.


1. This screen displays different content, depending on the VSS-aware restore method selected.
VSS Restore: Performs an online restore of the selected backup session to the original backup source (or alternate location) using the target computers Microsoft VSS tools. File Restore: Allows you to selectively restore individual files from a backup session. These are pure file restores, which can be useful with the corresponding Microsoft SQL Server, Exchange or SharePoint management tools. 2. Browse through the tree and check the item(s) you want. 3. Click Next >.

1. By default, data is restored to the original backup source location(s). 2. Select the restore location: Original location Alternate location - For more information, see VSS-aware Backup Sets (Alternate Location Restore) on page 271. 3. Click Next >.

1. The Restore Now Wizard switches to its Select restore performance options screen. F1 Help: See Select Restore Performance Options (Windows DS-Client) on page 847. 2. These options are intended for large backup sets in high performance environments. In general, you should use the defaults and skip to the next screen.

Confidential.
For more information, see the F1 help for this screen. 3. Click Next >.



Confidential.
Restore VMware VADP Backups


Step 2. Select the VMware VADP Restore Level

1. Select what type of VMware restore you want to perform.
F1 Help: See Select restore level (VMware VADP) on page 840. 2. Select what type of VMware VADP restore you want to perform. VM-level Restore: Restore entire Virtual Machines. VM Disk-level Restore: Restore individual virtual disks from a backed up Virtual Machine. 3. Click Next >.

1. Browse through the tree and check the item(s) you want. VM-level Restore: You will only be able to select an entire Virtual Machine. If you cannot select an item, it means no full VM is available to restore for the backup period listed (use the Advanced button to change the period). VM Disk-level Restore: You can select individual virtual disks from the list available (use the Show Files button to list the *.vmdk disks in each folder). 2. Click Next >.


Confidential.

F1 Help: See Select restore location screen on page 840. 2. Select the restore location: Original location Alternate location - For more information, see VMware VADP Backup Sets (Alternate Location Restore) on page 273. 3. Click Next >.


Confidential.

1. Select the restore options you want.
F1 Help: See Select restore options screen on page 842. 2. VM-level Restore: Additional Restore Options are available when restoring an entire Virtual Machine. For each selected VM, you can specify the following options: Power on VM after restore: Starts the virtual machine if it is successfully restored. Unregister VM after restore: After successful restore, the virtual machine will be unregistered from the vCenter. Append timestamp to VM name: Appends the restore time to the end of the virtual machines name. For example: RestoreVM would be restored as RestoreVM_(yyyy-mm-dd-hh:mm:ss) when you view it from the vCenter. 3. Click Finish to begin the restore.


Confidential.
Restore a Backup from the Cloud (Salesforce.com) Backup Set

Steps that are similar to File System restores have been condensed. For more information, refer to the following Knowledge Base articles: Backup from the Cloud (Salesforce.com) Limitations on page 671


1. Browse through the tree and check the item(s) you want. For this type of backup set, there is only one backup item (Salesforce.fdb). 2. Click Next >.
Step 3. Select the Restore Tables

1. A list of all the tables in the Salesforce.fdb appear in this screen. F1 Help: See Backup Objects for ... (System i Server and Backup from the Cloud) on page 748. By default, all tables are selected. The data from each selected table will be appended to the existing table on the Cloud application server (Salesforce.com). 2. Click Next >.

1. By default, data is restored to the original backup source location (i.e. the original Salesforce.com account). F1 Help: See Select restore location screen on page 840. 2. Select the restore location: Original location Alternate location - You must enter credentials to the alternate Salesforce.com account. Pure file restore (via DS-Client Buffer) to a network location visible to DSClient. 3. Click Next >.

1. Select the restore options you want. Win32 F1 Help: See Select restore options screen on page 842. Java F1 Help: See Select restore options screen (SQL / Microsoft Exchange / Oracle / System i) on page 845. Restore Schemas: If you select this option, the backed up schema(s) will be used to wipe and then rebuild the corresponding tables in the Salesforce.com database. This is useful if any tables have had their structure changed since the backup session you are restoring. 2. Click Finish to begin the restore.

Confidential.
Cloud database upload tool (Salesforce.com)

This is a tool included in the DS-User GUI if you have Backup from the cloud (Salesforce.com) backup sets. It allows you to upload the table(s) from any of the dump files in the Local Storage. (This is an alternative to restoring from a DS-System backup.) To use this tool, there are the following requirements: The backup set must be configured with the Keep db dump for differential backup option selected. You will be selecting one of those database dump files to upload (i.e. restore) to Salesforce.com. 1. Restore menu > Cloud Database Upload. The Cloud database upload tool screen appears.
F1 Help: See Cloud database upload tool on page 757. 2. In the Select SalesForce DB File Location section: Click [>>] and select the Local Storage folder containing the specific SalesForce.com database dump file you want to use for the upload.


Confidential.
3. Once a dump file has been selected, the Cloud database upload tool screen displays all the tables from the selected dump.
To select tables, highlight the item in the left column and click the [+] button. The table(s) will move to the right column, meaning they are selected for upload. 4. In the Connect to SalesForce with section, you must supply your SalesForce.com user credentials.
F1 Help: See Specify Credentials (Windows DS-Client) on page 884. Click [>>] to open the Enter / Modify Network Credentials screen. Enter the Salesforce.com username and password. Select the target database for backup (Production or Sandbox). Type or copy the security token that was E-Mailed to you by Salesforce.com. You can request the security token from the Salesforce.com website (Setup > My personal information > reset my security token). Click OK. DS-Client will immediately connect to verify the credentials.


Confidential.
5. If the SalesForce.com credentials work, the Upload button activates on the Cloud database upload tool screen.
6. Click Upload. The upload process begins as DS-Client connects to your SalesForce.com account. Uploaded table data is appended to any existing tables.


Confidential.
Restore to an Alternate Location

Asigra Cloud Backup allows you to restore your backups to alternate (different) locations, as required. An alternate location can be another disk drive on your computer, another share on a different computer, or another server on a different network (with some restrictions). To restore to an alternate location, you must specify the new location and the path on the new location. Since each backup type has particular requirements and specifications, instructions on how to restore to an alternate location are listed below separately. Similar procedures are condensed. Follow these steps to restore to an alternate location: Step 1.Select the backup set items for restore. Step 2.Choose the destination computer. Step 3.Select the destination share. Step 4.Specify the path on the destination share.
Step 1. Select the backup set items for restore.

1. Follow the steps necessary to specify the restore items until the Restore Now Wizard switches to its Select Restore Location screen. 2. Check the Alternate Location radio button. This activates the entire restore to alternate location section.


Confidential.
Step 2. Choose the destination computer (optional)

If you wish to restore to an alternate location on the same computer, skip to Step 3. Select the destination share on page 263. To select a different computer as the alternate location: 1. Click >> beside the Location field. The Select Alternate Server screen appears, allowing you to browse the available servers on the network (if any).
2. Browse through and highlight the computer that you want. 3. Click Select. If you are using Domain Security, your current login credentials are used to access the destination computer. Otherwise: If the Ask for Network Credentials box is checked, you are prompted for credentials to the destination computer. The Enter Network Credentials screen appears. Enter the User Name and password and click OK. 4. The Restore Now Wizard reappears. The Location field contains the alternate computer information.


Confidential.
Step 3. Select the destination share

You must select a share on the alternate computer. 1. Double click in the Destination field. A drop down list box will appear with all of the available shares on the alternate node.
2. Select one of the shares from the Destination List. Depending on your DS-Client computer, the Share Path cell may show the path of the destination directory on the selected computer.


Confidential.
Step 4. Specify the path on the destination share

By default, files will be restored to the destination computer's share path (indicated in the Share Path cell). To change the destination directory, select a directory from the Restore To cell (or simply type in a restore directory). 1. Double click in the Restore To cell beside the specified destination.
2. The Select Directory screen appears. Browse through and highlight the directory where you wish to restore the backup.
3. Click Select. The Restore Now Wizard reappears with the directory information in the Path cell.


Confidential.
4. Truncate: If the selected restore item(s) contain a common restore path, you may shorten that portion of the restore path by increasing the truncate level in the number field. Truncated portions of the restore path will disappear. 5. Click in the number field beside the Truncate field. The number represents the number of subdirectories in the current restore path. 6. Click the upward arrow to increase the truncation, and to reduce the number of subdirectories from the rightmost directory. Note: When restoring to an alternate location, if the entire path is truncated, the alternate location directory will inherit the security of the truncated parent directory. 7. Click Next >. The Restore Now Wizard switches to its Select restore performance options screen. 8. Click Next > The Select restore options screen appears. 9. Click Finish to start the restore. The Restore Process screen appears, showing the progress of each file as it is restored.


Confidential.
MS SQL Server Backup Sets (Alternate Location Restore)

Restoring to an alternate location involves specifying the alternate server's location and specifying the path on the new location. 1. Follow the steps necessary to specify the restore items until you reach the Restore Now Wizard's Select Restore Location screen.
2. Check the Alternate Location radio button. This activates the >> buttons and alternate location section. To restore to a different directory on the same server, skip to step 6. To restore to a different server on the network, follow from step 3. 3. Click >> beside the Location field. The Alternate Database Server Wizard screen appears, allowing you to browse the available servers on the network. 4. Browse through and highlight the server where you want to restore the backed up database. 5. Click Select: If the Ask for Network Credentials box is checked, the Enter Network Credentials screen appears. See Ask for Network Credentials: on page 99 If the Ask for Database Credentials box is checked, the Enter Database Credentials screen appears. See Ask for database credentials on page 117 6. If all your credentials are valid, the Select Restore Location screen reappears with the Alternate Server in the Location field.


Confidential.
7. Click >> beside the Dump field. This brings up the Select Share & Path for the Database Dump screen.
8. Browse through and choose the computer and path for the database dump. Click Select. Note: You may select the DS-Client Buffer as an option for the database dump, if none of your shares has sufficient capacity. This will save the dump to the local storage on the DSClient computer. Similarly, you may choose the DS-Client Pipe option to bypass a dump file altogether. 9. When restoring to a different location, you must re-specify the Destination Database for each item. Do so by double clicking on the Destination cell adjacent to the source name. The spreadsheet table will contain the list of databases (and/or tables) specified for restore. Each line has four columns, which initially contain default restore information:
Source Destination Database This cell shows the title of the database (or database\table name in the case of tables). This cell shows the destination database where the backup set will be restored.
11. Follow the same steps if you are restoring individual database tables. 12. In the Restore Option Section you may choose from the following:
Restore only the dump file(s) Restore Path Restores the dump files, but does not load them as databases (this option is not available for DS-Client Pipe). When restoring to an alternate location, you can specify the path for the log and data files separately. Opens the Select Restore Path screen.
This option only applies to restores to the original location. Off (default) - The restored files will be placed on the target instance's Preserve original default path(s). database file location On - The restore files must be placed in their original path(s). If the original path(s) do not exist, the restore will fail.
13. Click Next >. The Restore Now Wizard switches to its Select restore performance options screen. 14. Click Next >. The Select Restore Options screen appears. 15. Click Finish when you are ready to start the restore. The Restore Process screen appears, showing the progress of each file as it is restored.

Confidential.
MS Exchange Server Backup Sets (Alternate Location Restore)

1. Follow the steps necessary to specify the restore items until the Restore Now Wizard switches to its Select Restore Location screen. 2. Select the Alternate Location radio button. This activates the >> button beside the Location field.
3. Click >> beside the Location field. The Alternate Exchange Server Wizard screen appears, allowing you to browse the available servers on the network.


Confidential.
4. Browse through and highlight the server where you want to restore the database. Click Select. If the Ask for Network Credentials checkbox is marked, the Enter Network Credentials screen appears. Enter the user name and password to connect to the server and Click OK. 5. The Restore Now Wizard returns. Click Next and continue from Step 4. Specify the Restore Performance Options on page 238.


Confidential.
Oracle Database Backup Sets (Alternate Location Restore)

Oracle requires certain conditions for successful restore. See Restore Oracle Server Backups on page 240. In addition, the following apply for Alternate Restore: 1. The backup must be a full Oracle database backup (with Control File). You must also have a backup of the password file (this will be in a File System backup set). 2. The target restore computer must have an Oracle database service Instance of the same name. 3. The target restore computer must have the same tablespace path as the original backup (this can be created when setting up the database). 4. Restore the (File System) backup of the password file to the alternate computer. This is a separate backup set of the password file from the original backup computer. 5. Restore the full Oracle database backup.


Confidential.
VSS-aware Backup Sets (Alternate Location Restore)

The VSS-aware backup set type is available for Windows DS-Clients. These backup sets use the target backup / restore computers Microsoft VSS (Volume Shadow Copy Service) writers to backup and restore. The following backup items: Microsoft SQL Server Microsoft Exchange Server Microsoft Hyper-V (Virtual Machine) Microsoft SharePoint Server VSS-aware backup sets may have requirements for alternate location restores. See Restore VSS-aware Backups on page 251. The following options apply for Alternate Restore: 1. Select the VSS-aware backup set to be restored. Follow the steps necessary to specify the restore items until the Restore Now Wizard switches to its Select Restore Location screen. 2. Select the Alternate Location radio button. This activates the >> button beside the Location field, which allows you to select a different target location.
F1 Help: See Select restore location screen on page 840. 3. A Rename Component button appears for alternate location restores. Click to open the Rename Component screen, which allows you to rename individual components


Confidential.
being restored to the alternate location.
F1 Help: See Rename Component screen on page 810. To change a component name, click in the target cell and rename as required. Click OK to save the component name mapping. 4. The Restore Now Wizard returns. Click Next and continue from Step 5. Specify the Restore Performance Options on page 252.


Confidential.
VMware VADP Backup Sets (Alternate Location Restore)

1. Follow the steps necessary to specify the restore items until the Restore Now Wizard switches to its Select Restore Location tab. 2. Select the Alternate Location radio button. This activates the >> button beside the Location field.
3. Click [>>] to open the Select Alternate Location screen.
Click on the VMware VADP icon.


Confidential.
In the Path field, manually enter the IP address of the VMware ESX server or VMware vCenter server in the following format:
VMware VADP\IP_Address
Click Select. A popup appears where you must supply the VMware logon credentials and click OK. 5. The Restore Now Wizard returns. Map the selected restore item(s) to the Destination server. VM-level alternate restores: If you are restoring a virtual machine and have connected to an alternate VMware vCenter Server you can select the Datacenter, folder path, virtual machine name, Host and Datastore to which you will restore the virtual machine.
If you are restoring a virtual machine and have connected to an alternate ESX host server you can select the virtual machine name and the Datastore to which you will restore the virtual machine. VM Disk-level alternate restores: If you are restoring a virtual disk and have connected to an alternate VMware vCenter Server you can only select the Datacenter, folder path, virtual machine and Datastore to which to attach the virtual disk.
If you are restoring a virtual disk and have connected to an alternate ESX host server you can only select the virtual machine and the Datastore to which to attach the virtual disk. 6. Click Next and continue from Step 5. Specify the Restore Options on page 256.


Confidential.
Restore from Disc / Tape

Once a Disc/Tape has been delivered, it can be restored at your convenience from Restore Menu > Disc/Tape > Restore from. You must select the path (computer and directory) where the Disc/Tape data can be read. Once the Restore from Disc/Tape Wizard appears, you can continue like a regular restore (select the items to be restored, the restore location, and the restore options). For information on obtaining a Disc/Tape, see Disc/Tape on page 283 of Section 10 - Premium Backup and Recovery Services.
Restore from BLM

Once you have a BLM Restorable Image it can be restored at your convenience from Restore Menu > BLM Restore. You must select the path (computer and directory) where the BLM Restorable Image is located. Once the BLM Restore Wizard appears, you can continue like a regular restore (select the items to be restored, the restore location, and the restore options). For information, see Backup Lifecycle Management (BLM) on page 289 of Section 10 - Premium Backup and Recovery Services.


Confidential.
Validation of Online Storage

This process can be scheduled or performed on demand. It allows a DS-Client Administrator to validate the online data down to the Digital Signature applied to each file at backup time. Scheduled Validation: See Add a Detail to a Schedule on page 78 in section 3 - Schedules and Retention Rules. On Demand Validation: See Perform Validation on Demand on page 276.
Perform Validation on Demand

1. Browse the Backup Sets tree and highlight the one you want to validate. 2. Right-click > Validation (or Restore Menu > Validation). 3. The Validation Wizard appears on the Set Validation Settings screen.
F1 Help: See Validation Wizard - Set Validation Settings on page 893. 4. Enter the DS-Client Encryption Key(s). 5. Select the type of Validation: All: All generations of all data in this backup set will be validated. Selective: Allows you to specify the file(s) to validate. 6. Click Next >.


Confidential.
7. The Validation Wizard switches to the Select directories/files for validation screen. This screen is the same as the one used in the Restore Wizard.
8. Select the items you want to validate (everything will be selected if you specified All in the previous screen). 9. Click Finish to start the Validation.


Confidential.
10 - Premium Backup and Recovery Services
This section provides information on the premium services that may be offered by your Asigra Cloud Backup Service Provider.


Confidential.
Initial Backup
The DS-Client service is designed to perform automated backups to an offsite location. This approach requires an adequate communication link between the DS-Client and the DS-System that allows backup of any changed data in the given time window. After the first (initial) backup, the DS-Client service backs up only the incremental changes. However, there may be a problem performing that first backup of a large baseline amount of data. If the communication link between the DS-Client and the DS-System cannot handle this baseline backup in a reasonable amount of time (e.g. a few days), then an Initial Backup can be performed. Use the LAN Storage Discovery Tool (See LAN Storage Discovery Tool on page 329.) to analyze your LAN. Use Statistical Backup Sets (See Statistical Backups on page 177.) to calculate the amount of data to transmit. Divide this number by your communications bandwidth to estimate how long this baseline backup will take. The Initial Backup feature allows you to backup to local buffer location(s) that are either directly connected to the DS-Client, or visible to it on the LAN. Then, you ship that media (e.g. disks) to your Service Provider. Your Service Provider will import the Initial Backup data from the media (either attached to the DS-System, or via a LAN connection). Once it is imported to the DSSystem, you can continue protecting your data with subsequent scheduled and on-demand backups. The following steps describe the Initial Backup Service: 1. Your DS-Client must be registered with the DS-System. 2. Configure the Initial Backup buffer path. See Configure Initial Backup Path (Buffer) on page 280. 3. Create the Initial Backup Set(s). See Create Initial Backup Set on page 281. 4. Perform a Backup of all Initial Backup Sets to the Initial Backup buffer. See Perform a Demand Backup on page 211. 5. Ship the Initial Backup buffer media to your Service Provider. 6. Monitor the status of Initial Backup Sets. Once your Service Provider has imported a backup set, it will disappear from the Initial Backup Status screens list of Initial Backup Sets. See Monitor Initial Backup Sets on page 282. More information can be found in the Knowledge Base article: Best Practices: Initial Backup on page 533.


Confidential.
Configure Initial Backup Path (Buffer)

You can configure as many Initial Backup Paths as you need. These are local disks or UNC path locations (Windows DS-Client) that can be shipped to your Service Provider. 1. Initial Backup Menu > Path. The Set Initial Backup Path screen appears.
F1 Help: See Set Initial Backup Path on page 854. 2. Click Add. The Select Initial Backup Path screen is slightly different, depending on if this DS-Client is running on Windows or Linux.
F1 Help: See Select Initial Backup Destination Path on page 831. Specify the Computer and Directory for the Initial Backup path. Use a descriptive name for paths (to make it easier for your Service Provider to identify the DS-Client associated with the data). If desired, select an Encryption Method for the meta-data (the descriptive files used by Asigra Cloud Backup to manage the Initial Backup). Click OK to save the path.


Confidential.
Create Initial Backup Set

You can create as many Initial Backup Sets as required. 1. From the New Backup Set Wizard: Sets Menu > New Backup Set... > Specify backup set options screen From the Backup Set Tree: Right-click the backup set > Properties > Options Tab Check the Initial Backup box.
F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 2. The Initial Backup Settings screen appears.
F1 Help: See Initial Backup Settings on page 786. 3. Highlight the Initial Backup path you want to use for this backup set. Click OK. Assign an Initial Backup Path to backup sets from only one DS-Client. (Do not assign the same path to backup sets from two or more DS-Clients.) 4. Finish the New Backup Set Wizard, or click Apply if you are editing from the backup sets Properties Tab. 5. Perform a Demand Backup of all Initial Backup Sets to the Initial Backup buffer. See Perform a Demand Backup on page 211.

Confidential.
Monitor Initial Backup Sets

You need to monitor Initial Backup Sets, until your Service Provider has imported the data to the DS-System. Scheduled and on demand backups of Initial Backup sets will fail until the data is imported to the DS-System. 1. Initial Backup Menu > Status. The Initial Backup Status screen appears.
F1 Help: See Initial Backup Status on page 786. 2. Before sending an Initial Backup buffer (the physical media) to your Service Provider, make sure all the backup sets have Completed for their Set Status. 3. Once an Initial Backup Set has been imported to the DS-System, it will disappear from the Initial Backup Status screen.


Confidential.
Disc/Tape
Disc/Tape is a tool that allows you to copy backed up files from the DS-System to any media supported by your Service Provider (e.g. CD/DVD, Tape, Hard Disk Drive, or USB). This allows you to have a copy of backed up data on hand (at your location). Data on the Disc/Tape media must be restored through the DS-Client. The steps are as follows: Step 1. Request Disc/Tape on page 283 Step 2: View Orders for Disc/Tape on page 285 Step 3. Restore from Disc/Tape on page 286
Step 1. Request Disc/Tape

1. Highlight the backup set you want from the Backup Sets Tree and right-click. 2. Click Request Disc/Tape. The Request Disc/Tape Wizard appears.
F1 Help: See Select restore media & options screen on page 842. 3. Select the Media and Option for the Disc / Tape request.


Confidential.
4. Click Next >. The Select directories/files screen appears.
If you chose the Snapshot option, the entire backup set will be selected and you will not be able to change any settings. If you chose the Selective option, you must choose the directories/files for restore. Do this in the same manner as for regular restores. 5. Once you are satisfied with the selection, click Finish. 6. The Disc/Tape Mailing Information screen appears.
F1 Help: See Disc / Tape Mailing Information screen on page 763. 7. Enter the pertinent mailing information and click OK to proceed. Note: This has the same effect as signing a Purchase Order Contract.
8. The DS-System will then mirror all of the selected files (from the Request Process) to a buffer directory at the DS-System (i.e. your Service Provider's site). Your service provider will then make the Disc/Tape order from this buffer. Note: This backup set will not be accessible (for backup) until your service provider makes the Disc/Tape.


Confidential.
Step 2: View Orders for Disc/Tape

You can view the progress of your order. Once the DS-System has resolved the requested files in its database, the order status will be changed to 'Purchased'. However, the backup set's files must not be altered (i.e. by subsequent backups or any other process with write access to the backup files). Therefore, the backup set is locked until your Service Provider can replicate the requested files to the media you selected (i.e. when the Status is 'Finished'). 1. Restore > Disc/Tape > Orders. The Orders for Disc / Tape screen appears.
F1 Help: See Orders for Disc / Tape screen on page 795. 2. The columns show details and the status of each order.


Confidential.
Step 3. Restore from Disc/Tape

Once a Disc / Tape has been delivered, you may restore from it at your convenience. 1. Restore menu > Disc/Tape > Restore from. The Select Disc/Tape restore path screen appears.
F1 Help: See Select Disc / Tape Restore Path screen on page 827. 2. Click >> to select the computer.
See Step 2. Select the Computer on page 99 3. The computer field is filled with your selection.


Confidential.
4. Click >> to select the directory.
Select the directory containing the disc / tape catalog.

Shares and Directories Tree Select Shows the available shares and directories. Click to select the highlighted directory.
5. Your selection appears in the Directory field. A field appears if you need to enter an encryption key. 6. Click OK. The Restore from Disc/Tape Wizard Select directories/files to restore tab appears.


Confidential.
7. Click Next >. The Select restore location tab appears.
8. Click Next >. The Select restore options tab appears. Specify any restore options.
9. Click Finish to start restoring.


Confidential.
Backup Lifecycle Management (BLM)

This tool is provided by your Service Provider from the DS-System. The Backup Lifecycle Management (BLM) Module is a solution that works with DS-Client, DSSystem, and a BLM Archiver to extend the options for your backed up data. In addition to archiving data to less costly media, this Module gives you additional options for copying, removing, and destroying data. Data stored in the BLM Archiver is billed on a different scale than the online (DS-System) data. BLM Requests can be performed as follows: 1. On schedule from DS-Client side: Configure BLM (per backup set) on page 290 Create BLM Schedule on page 291 Schedule Backup Set for BLM on page 291 2. On demand from DS-Client side: Perform BLM Request on Demand on page 292 Tape Conversion to BLM on page 294 3. On demand from DS-System (Service Provider) side: Contact your Service Provider. BLM and Retention: 1. If the BLM Module is enabled for this DS-Client, an additional feature becomes available for Retention: Time-Push. See About Retention Rules on page 85. Restoring from BLM: Data that is stored by the BLM Archiver is accumulated into Archive Packages. Data in these Archive Packages may not be in a format that is immediately readable by the DS-Client. This is why there is the additional step of creating a Restorable Image: a DS-Client readable image of archived data. Each Restorable Image represents data from a single backup set, though it can contain multiple generations of files. 1. To restore from a BLM Restorable Image, see: Restore from BLM on page 293


Confidential.
Configure BLM (per backup set)

Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. When you configure a backup set for BLM, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver. 1. In the Backup Sets Tree, right-click the backup set you want. 2. Choose Properties > Options Tab. Check the BLM (Infinite Generations) option.
F1 Help: See Set Properties - Options tab on page 862. F1 Help: See Set Properties - Options tab (Linux DS-Client) on page 866. 3. Click OK.


Confidential.
Create BLM Schedule

You can create a new BLM schedule (or edit an existing Schedule by adding a detail to copy files to BLM). Use the Perform BLM detail with the Enforce Retention detail to set the policies for handling backed up data. 1. In the Backup Schedules Tree, click the backup schedule you want. 2. Schedule Menu > Edit Schedule.
3. 4. 5.
6. 7.
F1 Help: See Schedule screen on page 816. In the Details section, choose <new> to create a new detail. Check Perform BLM. Click [>>] beside Perform BLM. The Select BLM Options screen appears. F1 Help: See Select BLM Options on page 822. Use these settings to configure what will be archived, and how the BLM will handle the data when this schedule is run. Click OK. Click Save.
Schedule Backup Set for BLM

Assign the BLM Schedule to the backup set(s) you want. The backup set(s) do not have to be configured with the BLM (Infinite Generations) option. 1. In the Backup Sets Tree, right click the backup set you want. 2. Select Properties. The Backup Set Properties screen appears. 3. Click Schedule. The Schedule Tab appears. 4. Select Schedule and click OK.


Confidential.
Perform BLM Request on Demand

BLM Requests can be performed as follows: On schedule from DS-Client side On demand from DS-Client side On demand from DS-System (Service Provider) side You may perform an on Demand BLM Request for any existing backup set with backed up data online. The backup set does not have to be configured with the BLM (Infinite Generations) option. 1. In the Backup Sets tree, highlight the backup set you want. 2. Backup Menu > BLM Request. The Request BLM Wizard appears. Select the backup items you want to copy to the BLM Archive. 3. Click Next. The Select BLM Options screen appears. F1 Help: See Select BLM Options (Request BLM Wizard) on page 822. Select the BLM options. 4. Click Finish. A Process Window opens to show the progress of the BLM Request. Note: An alternative is to contact your Service Provider and have them perform the BLM Request from the DS-System side on Demand.


Confidential.
Restore from BLM

Once data has been sent to the BLM Archive, you may request to have any generation in the archive written to media and shipped to you. [Ask your Service Provider to generate a restorable image, or use the DS-NOC if it is available.] Data on BLM Media may be restored, as long as the media can be viewed as a directory on the DS-Client network. Alternatively, you can copy the data from the BLM Media to a directory on the network. 1. Restore Menu > BLM Restore. The Select BLM Restore Path screen appears. F1 Help: See Select Restore Path screen on page 848. 2. Click [>>] and select the computer. 3. Click [>>] and select the directory. 4. Click OK. The Restore from BLM Wizard appears.
5. The next steps are the same as for a regular restore.


Confidential.
Tape Conversion to BLM

[Windows DS-Client] DS-Client can convert data from tape backups into BLM format Archive Packages (See Backup Lifecycle Management (BLM) on page 289.). These Archive Packages can then be sent to your Service Provider to import to the BLM Archiver (for offsite storage). The following are requirements to convert from tape to BLM: Tape Drive must be directly connected to the DS-Client computer. Tape Format must be MTF (Microsoft Tape Format). The following limitations exist for data you convert from tape: Special Operating System backups that were created using the tape backup utility (e.g. System State, MS Exchange) are not restorable.
Conversion Wizard - Tape to BLM

1. Load the tape(s) you want to convert. 2. Initial Backup Menu > Tape Conversion to BLM. The Tape Conversion Wizard appears.
F1 Help: See Tape Converter - Select the backup set on page 891.


Confidential.
3. When this screen opens, the Tape Converter automatically counts how many physical tapes are in the drives. At first, all tapes appear under Unidentified Tapes. This is because identifying a tape requires more intense use of the tape drive (it must be loaded and read).
Refresh: Updates the screen with the latest information that DS-Client has from the Tape Librarys memory. Identify Tape: Scans the highlighted tape for information about the backup data on the tape. Note: If the DS-Client service is restarted, all tapes will be reset to Unidentified Tapes. 4. If you need to identify a tape, highlight it and click Identify Tape. A new activity will start (a separate Process Monitor will appear). When this activity has finished, you must click Refresh to update the list. IMPORTANT NOTE ABOUT CHANGING TAPES The DS-Client Tape Converter depends on Windows to interface with the Tape Drives. Therefore, you must change tapes in a way that Windows will always be aware of your changes. To change a tape: Open the Tape Drive door, and take a tape out from its slot. Close the Tape Drive door. Let Windows perform its inventory, and the removed tape will be marked as off-line. Open the Tape Drive door again, and put the new tape in the empty slot. Close the Tape Drive door. Windows will identify the new tape. After Windows finishes its identification of the Tape, you must click Refresh in the Tape Conversion Wizard to update the DS-Clients list from the Tape Librarys memory.


Confidential.
5. Once a Tape has been identified, all the backup set(s) on that tape appear in the list. .
Note: You can only convert from a tape that has been identified. 6. Highlight the level that you want to convert: Computer Name: converts all backup sets listed for that computer. Backup Set: converts the highlighted backup set. 7. Click Next. The Tape Conversion Wizard prompts you to select the backup data to convert.
F1 Help: See Tape Converter - Select the directories on page 891.


Confidential.
Select the data to convert. By default, the entire backup set is selected. 8. Click Next. The Tape Conversion Wizard prompts you to specify the conversion options.
F1 Help: See Tape Converter - Options on page 891. Before Conversion: The current implementation does not require any input. If the tape is in MTF, DS-Client can convert the data without entering any password(s). After Conversion: You must specify the location where DS-Client will save the Archive Package. The BLM Session and Backup Set Name are labels that will help you find the Archive Package after it is imported to the BLM Archiver.


Confidential.
9. Click Next. The Tape Conversion Wizard displays a summary of the tape data you are about to convert.
F1 Help: See Tape Converter - Summary on page 891. 10. Click Finish. A Tape Conversion Process Window opens. When the conversion is finished, the data in the Target Path can be shipped to your Service Provider for import to the BLM Archiver. After the data has been imported to the BLM Archiver, you can request Restorable Images. (See Restore from BLM on page 293.)


Confidential.
DS-Client Monitoring by the DS-NOC Tool

This tool must be enabled (either by you or your Service Provider) from the DS-NOC server. If enabled, this DS-Client will send event information (backup logs) to the DS-NOC for monitoring purposes. 1. Setup Menu > DS-NOC Settings.
F1 Help: See DS-NOC Settings on page 772. 2. The information displayed in this screen is read-only. It is obtained from the DSSystem. The buttons allow you to perform the following tasks: Configure a Proxy Server: See Configure DS-Client to connect to DS-NOC via a Proxy Server on page 300. Check New Settings: Connects immediately to the DS-System to obtain the latest settings. DS-Client automatically updates these settings on every connection with DS-System. Connect to DS-NOC: Immediately connects this DS-Client to the DS-NOC server to send its monitoring information.


Confidential.
Configure DS-Client to connect to DS-NOC via a Proxy Server

Some network environments may not allow the DS-Client to connect directly to the DS-NOC Server. In these situations, DS-Client can be configured to use a Proxy Server for external HTTP / HTTPS protocol connections. Note: Your Proxy Server must be configured and working before using this option.
To configure the DS-NOC Proxy Server: 1. Setup Menu > DS-NOC Settings. 2. In the DS-NOC Settings screen, click Proxy Server.
F1 Help: See DS-NOC Proxy Server Settings on page 773. 3. There are 4 options available in this screen: No proxy: This is the default setting. DS-Client connects directly to DS-NOC. The protocol (HTTP or HTTPS) will be automatically selected based on the DS-NOC address provided by the DS-System. Auto-detect proxy settings for this network: - See Auto-detect Proxy Server on page 301. Manual proxy configuration: - See Manual Proxy Server Configuration on page 301. Automatic proxy configuration URL: -
- See Automatic Proxy Server Configuration URL on page 302. 4. If the Proxy Server requires authentication, you can supply the User Name and Password at the bottom of the screen. 5. Click OK to save the configuration.

Confidential.
Auto-detect Proxy Server

The auto-detection method depends on the type of DS-Client. Linux DS-Clients Linux DS-Client will try to find the URL 'http://wpad/wpad.dat'. If this URL exists, DS-Client will load the URL and analyze it. Then it will get a proxy server and port from the URL and then use that proxy server to connect to DS-NOC. Windows DS-Clients Windows DS-Client tries to find the proxy server using the following methods, in order. If one method fails, the next method is attempted. 1. Web Proxy Auto-Discovery Protocol (WPAD) URL: This is a method used by clients to locate a URL of a configuration file using DHCP and/or DNS discovery methods. Windows DS-Client checks the DHCP server first. The DHCP server must be configured to serve up the site-local option 252 (auto-proxy-config) with a string value of http://xxx.yyy.zzz.qqq/wpad.dat (without the quotes) where xxx.yyy.zzz.qqq is the address of a web server (either IP or DNS). If DHCP fails to provide the required information, Windows DS-Client will try to find the configuration URL by checking the DNS server. If the network name of the DS-Client computer is pc.department.branch.example.com, the browser will try the following URLs in turn until it finds a proxy configuration file within the domain as follows:
http://wpad.department.branch.example.com/wpad.dat http://wpad.branch.example.com/wpad.dat http://wpad.example.com/wpad.dat
If DS-Client finds the WPAD URL (using either DHCP or DNS), it will load and analyze it. Then it will use the proxy server specified to connect to DS-NOC. If DS-Client fails to find the WPAD URL, it attempts the next method: 2. Internet Explorers configuration: This is the equivalent of opening Internet Explorer (if logged in to Windows as the DS-Client service account) and checking the Tools menu > Internet Options > Connections tab > LAN Settings: Proxy Server. Windows DS-Client will try to find the DS-Client Service Accounts Internet Explorer configuration to get the proxy server settings. If DS-Client fails to find a proxy server, it attempts the next method: 3. WinHTTP settings: This method checks the DS-Client computers registry for a default proxy server setting. The WinHTTP default setting is saved in the Windows Registry. It is defined by using the "proxycfg.exe" command (Windows 2003 & Windows XP) or the "netsh winhttp" command (Windows 2008, Windows Vista, and Windows 7).
Manual Proxy Server Configuration

This option allows you to specify the proxy server address. A separate proxy server can be configured for the HTTP and HTTPS protocols, or the same one can be used for both protocols. The standard port used for HTTP connections is 80 and for HTTPS connections it is 443.


Confidential.
Automatic Proxy Server Configuration URL

This is useful if you have multiple DS-Clients and want to be able to change the Proxy Server address without reconfiguring each DS-Client. DS-Client will try to load the URL and analyze it to obtain the proxy server and port. If successful, DS-Client will use that proxy server to connect to DS-NOC. The URL should be to a PAC (proxy auto configure) file. The following is a sample of the file contents required for a proxy server located at IP address 10.20.30.44 using port 8888:
function FindProxyForURL(url,host){ return "PROXY 10.20.30.44:8888"; }
Note:
For all options (except No proxy), if DS-Client fails to find a correct proxy server, it will try to connect to DS-NOC directly. The protocol (HTTP/HTTPS) will be automatically selected based on the address provided by the DS-System.


Confidential.
Local Storage Tool

WARNING:Make sure the location(s) you select can accommodate the potential capacity. Note that FAT and FAT32 volumes are not supported as Local Storage locations. This tool must be enabled by your Service Provider from the DS-System. You must request this tool from your Service Provider, and it should be a part of your service agreement. Local Storage behaves differently for backup sets depending on if they are assigned to a Retention Rule: Without Retention: Local Storage keeps a copy of the latest generation of the backup set files (as well as online, offsite at the DS-System). With Retention: the same number of generations are backed up to Local Storage as are on DS-System. Make sure there is enough space in the local storage buffer, and perform the Enforce Retention process regularly. Note: In both cases, when a new backup session occurs and an existing generation of a file is replaced by a new one, the deletion of the old generation will take place after the new one was successfully saved on the local storage. This means there must be enough free space on the Local Storage to accommodate both generations.
The Set Properties Options Tab will contain the following additional checkboxes: Save on Local Storage: Enables local storage for the backup set. Transmission cache on Local Storage: Local Storage Cache on page 305
Set the Local Storage Path (Default)

1. Setup menu > Configuration. The DS-Client Configuration screen appears. 2. Click Parameters.
3. In the Local Storage Path field, enter a path where snapshots of the latest backup of each selected Backup Set will be stored. When a path is entered, the Save on Local Storage checkbox appears in the Options Tab of the Backup Set Properties screen.

Confidential.
4. Click OK to save the changes to this tab.
Apply the Local Storage Option (per Backup Set)

1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click and select Properties. The Backup Set Properties screen appears on the Items Tab. 3. Click the Options Tab.
For new backup sets, this feature is activated on the last tab of the New Backup Set Wizard (Choose the name for this backup set). 4. After Use Local Storage select Save. By default, this backup set will use the same Local Storage Path set in Set the Local Storage Path (Default) on page 303. Click [>>] to specify a different Local Storage Path for this specific backup set. Local storage will be used for this backup set starting from the next backup session. 5. Click OK to save any modifications.
Note:
Restore from Local Storage Path

Backup sets flagged with Save on Local Storage will be restored from the local storage path. If any files are missing, then the DS-Client will retrieve them from online storage on the DS-System. 1. Follow from Step 1. Select the Backup Set on page 225 in section 9 - Restoring Backups.


Confidential.
Local Storage Cache

Note: For more information see the Knowledge Base Article: Local Storage Cache Overview on page 528.
The Local Storage Cache feature extends the capability of the local storage to provide a cache if the connection from DS-Client to DS-System is interrupted during a backup session. This reduces the possibility of missed backup sessions in normal operating environments. 1. Browse the Backup Set Tree and highlight the backup set you want. 2. Right-click and select Properties. The Backup Set Properties screen appears on the Items Tab. 3. Click the Options Tab Note: For new backup sets, this feature is activated on the last tab of the New Backup Set Wizard (Choose the name for this backup set). 4. After Use Local Storage select Cache. By default, this backup set will use the same Local Storage Path set in Set the Local Storage Path (Default) on page 303. Click [>>] to specify a different Local Storage Path for this specific backup set. Any data that is cached by this feature will be saved in this Local Storage Path in a sub-folder called Cache. Data in the Local Storage Cache will be forwarded to the DS-System when the connection can be re-established. In the meantime, subsequent backups from this set will accumulate in the cache. 5. Click OK to save any modifications.


Confidential.
Multi-Tenant DS-Client
NOTE: This option adds a customer layer to the backup set data, which enables the DS-Client administrator to assign and sort backup sets by this customer tag.
This is a configuration of the DS-Client that allows the administrator to assign a customer to individual backup sets for sorting purposes. This allows reports to be generated and sorted by customer (in addition to all other current functionality). All other features of DS-Client remain the same whether or not the Multi-Tenant mode is enabled. To enable the Multi-Tenant DS-Client mode: 1. Activate the Multi-Tenant feature on page 307 2. Create the Customers for this Multi-Tenant DS-Client on page 308 3. Assign existing backup sets to a customer (Edit backup sets) on page 309 4. New backup sets for Multi-Tenant DS-Client on page 310 5. Reports from Multi-Tenant DS-Client on page 311


Confidential.
1. Activate the Multi-Tenant feature

The DS-Client is configured for Multi-Tenant mode through the DS-Client Configuration Advanced Tab. 1. Setup Menu > Configuration. The DS-Client Configuration screen appears. 2. Click Advanced.
3. 4. 5. 6.
F1 Help: See DS-Client Configuration Advanced Tab screen on page 763. From the Category dropdown list, select Miscellaneous. From the Parameter dropdown list, select Multi-Tenant. From the Value dropdown list, select Yes. Click Apply. The DS-Client immediately enters Multi-Tenant mode:
Multi-Tenant OFF
Multi-Tenant ON
The Backup Sets Tree adds the customer level as the root branch (by default it will have <Customer Unspecified>). A Multi-Tenant item appears in the Setup menu.


Confidential.
2. Create the Customers for this Multi-Tenant DS-Client

This mode is useful if you are backing up data from this DS-Client that can be grouped to different customers. (The term customer is flexible; at its simplest level, it is an assignment of data to a specific owner.) 1. Setup Menu > Multi-Tenant. The Customer Management screen appears.
F1 Help: See Customer Management on page 760. 2. To add a new customer, click Add. To edit a customer, highlight one and click Modify. The Customer Information screen appears.
F1 Help: See Customer Information on page 759. 3. To add a new customer, click Add.


Confidential.
3. Assign existing backup sets to a customer (Edit backup sets)

This is optional. You can leave existing backup sets with the <N/A> customer setting. 1. Any existing backup sets will initially be placed under the <Customer Unspecified> branch of the Backup Sets tree.
2. Right-click on the backup set you want to assign and select Properties. The Set Properties - Items tab appears. 3. Click Set Info. In the Set Information section, assign a customer to this backup set.
4. Continue with as many backup sets as you want to assign to customers.


Confidential.
5. When you are finished, the Backup Sets tree will be sorted by customer.
4. New backup sets for Multi-Tenant DS-Client

When Multi-Tenant mode is enabled, you will have one additional selection when you create new backup sets. A Customer dropdown list appears, where you can assign the backup set to one of the defined customers.
F1 Help: See Choose the name for this backup set screen on page 755. F1 Help: See Choose the name for this backup set screen (Linux DS-Client) on page 756. Once a backup set is created, you can adjust its customer assignment from the Set Properties - Set Info tab.
Confidential.

5. Reports from Multi-Tenant DS-Client

The main use of the Multi-Tenant DS-Client mode is to generate reports grouped by customer. When the DS-Client is in Multi-Tenant mode, all Report Print screens contain an additional dropdown list 1. All the report print screens will have an additional dropdown list, where you can select to view only the information for a specific customer.
You can view <All> customers, or only data from a specific customer.
2. All other steps and instructions are the same as for regular reports. For instructions, see: Print Reports on page 369


Confidential.
Snapshot Manager
NOTE: This feature integrates the DS-User GUI with Storage volumes to manage their native SnapVault feature. DS-Client does not process any data from the storage. [Linux DS-Client only] This tool must be enabled by your Service Provider from the DS-System. This feature allows you to use the DS-User GUI as a tool to transfer volumes\qtrees to another volume without having to use the scripting required by the native Storage management software.
NetApp License Requirements

In order to use this functionality, you must have the following NetApp licenses: For the source NetApp Storage, a SnapVault ONTAP Primary license is needed. For the destination NetApp Storage, a SnapVault ONTAP Secondary license is needed. If the source volume and the destination volumes are on the same filer, then the two licenses are required on the same filer: SnapVault ONTAP Primary and SnapVault ONTAP Secondary. To use Snapshot Manager: 1. Configure the Storage that can be used for Snapshot Transfer on page 313 2. Configure the Snapshot Retention Policies that can be used for Snapshot Transfer on page 314 3. Configure the Snapshot Schedules that can be used for Snapshot Transfer on page 315 4. Configure a Snapshot Transfer that will be managed by this DS-Client on page 316 What happens when Snapshot Transfer runs? on page 321 Managing Snapshot Transfers on page 321 For more information, see the Knowledge Base Article Snapshot Transfer Issues on page 443.


Confidential.
1. Configure the Storage that can be used for Snapshot Transfer

The DS-Client must be configured to connect to each Storage that will be used for Snapshot Transfer. This section assumes the Storage device(s) are running and can be accessed by the DSClient. 1. Snaphot Manager Menu > Register Storage. The Register Storage Management screen appears.
F1 Help: See Snapshot Transfer - Register Storage Management screen on page 880. 2. To add a new storage, click New. The New Storage screen appears. To edit an existing Registered Storage, highlight it and click Edit. The Modify Storage screen appears.
F1 Help: See Snapshot Transfer - New / Modify Storage screen on page 881. 3. Configure the Storage connection information. 4. Click OK to save the connection information for this Storage. DS-Client will immediately verify that it can communicate. If successful, the Storage is added to the list.


Confidential.
2. Configure the Snapshot Retention Policies that can be used for Snapshot Transfer
[Optional, but recommended] You should configure the list of Retention Policies this DS-Client can apply to the snapshots taken by the Snapshot Manager. Each Snapshot Transfer that is configured can be assigned to one Retention Policy. 1. Snapshot Manager Menu > Snapshot Retention. The Snapshot Retention Management screen appears.
F1 Help: See Snapshot Transfer - Snapshot Retention Management screen on page 880. 2. To add a new Retention Policy, click New.The New Snapshot Retention screen appears. To edit an existing Retention Policy, highlight it and click Edit. The Modify Snapshot Retention screen appears.
F1 Help: See Snapshot Transfer - New / Modify Snapshot Retention screen on page 881. 3. Configure the Retention Policy. 4. Click OK to save the Snapshot Retention Policy. A Retention Policy is applied at volume-level, meaning that all Snapshot Transfers for the same volume will have the same Retention Policy WARNING: Once retention is enforced, any deleted snapshots are gone forever.


Confidential.
3. Configure the Snapshot Schedules that can be used for Snapshot Transfer
[Optional, but recommended] You should configure the list of Schedules this DS-Client can use for Snapshot Transfer. Each Snapshot Transfer that is configured can be assigned to one Snapshot Schedule. 1. Snapshot Manager Menu > Snapshot Schedule. The Snapshot Schedule Management screen appears.
F1 Help: See Snapshot Transfer - Snapshot Schedule Management screen on page 881. 2. To add a new Snapshot Schedule, click New. The New Snapshot Schedule screen appears. To edit an existing Snapshot Schedule, highlight it and click Edit. The Modify Snapshot Schedule screen appears.
F1 Help: See Snapshot Transfer - New / Modify Snapshot Schedule screen on page 882. 3. Configure the Snapshot Schedule. 4. Click OK to save the Snapshot Schedule. A Schedule is applied at volume-level, meaning that all Snapshot Transfers for the same volume will have the same Schedule.


Confidential.
4. Configure a Snapshot Transfer that will be managed by this DSClient

NOTE: At the end of the configuration Wizard, the initial Snapshot Transfer is run from source to destination. The DS-Client must be configured to connect to each Storage that will be used for Snapshot Transfer. This section assumes the Storage device(s) are running and can be accessed by the DSClient. 1. Snapshot Manager Menu > Snapshot Transfer. The Snapshot Transfer Manager screen appears.
F1 Help: See Snapshot Transfer Manager on page 883.


Confidential.
2. To add a new Snapshot Transfer configuration, click Snapshot Transfer Setup. The Snapshot Transfer Setup Wizard appears on its Select Source Storage screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Storage screen on page 882. Select the source Storage, from which the volume data will be read. 3. Click Next. The Snapshot Transfer Setup Wizard appears on its Select Volume screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Volume screen on page 883. Select the volume on the source Storage that will be protected.


Confidential.
4. Click Next. The Snapshot Transfer Setup Wizard appears on its Select Destination Storage screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Storage screen on page 882. Select the destination Storage, where the data will be copied. 5. Click Next. The Snapshot Transfer Setup Wizard appears on its Select Volume screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Volume screen on page 883. Select the volume on the destination Storage where the data will be copied.


Confidential.
6. Click Next. The Snapshot Transfer Setup Wizard appears on its Select Snapshot Retention screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Snapshot Retention screen on page 882. Note: This screen only appears for the first Snapshot Transfer created on a destination volume. If you create a new Snapshot Transfer on a destination volume where a Retention Policy is already defined, this step is skipped. (Optional) Select a Snapshot Retention Policy for the destination volume. 7. Click Next. The Snapshot Transfer Setup Wizard appears on its Select Snapshot Schedule screen.
F1 Help: See Snapshot Transfer Setup Wizard - Select Snapshot Schedule screen on page 882. (Optional) Select a Snapshot Schedule for the destination volume.
Confidential.

8. Click Next. The Snapshot Transfer Setup Wizard appears on its Specify Snapshot Transfer Name screen.
F1 Help: See Snapshot Transfer Setup Wizard - Specify Snapshot Transfer Name screen on page 883. Note: This screen only appears for the first Snapshot Transfer created on a destination volume. If you create a new Snapshot Transfer on a destination volume where a Schedule is already defined, this step is skipped. Assign this Snapshot Transfer configuration a name and (optionally) a Bandwidth Throttle and description. 9. Click Finish. The initial transfer from source to destination is triggered immediately after the Snapshot Transfer is created.


Confidential.
What happens when Snapshot Transfer runs?

The initial transfer from source to destination is triggered immediately after the Snapshot Transfer is created. Each subsequent scheduled or on-demand Transfer will perform an incremental transfer (only the changes since the last update, as determined by the Storages management software. After each scheduled or on-demand Transfer (data transfer) has completed, a new snapshot will be created for the destination volume.
Managing Snapshot Transfers

1. The Snapshot Transfer configuration appears as a tree item in the Snapshot Transfer Manager.
You can right-click at different levels to access the item-options.


Confidential.
11 - Logs and System Tools
This section provides information on how to use the system logs and other system administration tools.


Confidential.
Activity Log
The Activity Log is a tool that is useful for tracking the activities on the DS-Client. You will only be able to view activities that you have permission to see. 1. Logs menu > Activity Log. The Activity Log Viewer screen appears.
2. 3. 4. 5.
6. 7.
F1 Help: See Activity Log viewer screen on page 737. Click Find. The activities that are displayed reflect the parameters in the Select By section. You can change the Select By parameters if you would like to search for activities from a specific time, a particular type of activity, a specific node/backup set or user, etc. Click Find to refresh the display with the activities that meet your Select By specifications. If an error occurred during the selected activity, a record of what happened is kept in the Event Log. Click Event Log to display specific event information on the highlighted activity. If detailed information exists for an activity, you can click Detailed Log. See Detailed Log on page 324. Click Close when you are finished.


Confidential.
Detailed Log
This feature is available if the selected activity contains Detailed Log information (refer to Step 5. Specify Backup Set Options on page 103). This means a log of all the files processed in the selected session was recorded. DS-Client dumps all detailed logs to a folder called asigra_archivlog. By default, this is located in the DS-Client installation directory, but can be configured from the DS-Client Configuration Advanced Parameter screen (Category:Miscellaneous ; Parameter: LogArchivePath). See DSClient Advanced Configurations on page 47. For Grid DS-Clients, the default (if LogArchivePath is not configured) is each node will write to the asigra_archivlog folder in its own (local) DS-Client installation directory for the activity sessions it performs. However, the DS-User can only access the Detailed Log on the Main Node. To ensure the Detailed Log for all sessions is accessible, configure LogArchivePath to a UNC path (which can be accessed by all nodes). 1. In the Activity Log, highlight the activity session you would like to view. 2. Click Detailed Log. The Detailed Log Viewer appears, which displays the processed files in list format.
F1 Help: See Detailed Log Viewer on page 762. 3. Select a filter (the default is *, meaning ALL) and click Find. 4. You can narrow the list by using the Path Filter. Note: When you search a Detailed Log, you are actually searching through the file stored in the asigra_archivlog folder. You (the end-user) must make decisions about the maintenance for this folder (e.g. delete / archiving). By default, the logs will constantly accumulate.


Confidential.
Event Log
The Event Log is a searchable log that records events that occur on the DS-Client. Events include errors, warnings, and information messages. 1. Logs menu > Event Log. The Event Log Viewer screen appears.
F1 Help: See Event Log Viewer screen on page 779. 2. You can change the Select By parameters to narrow your search. 3. Click Find to refresh the display based on the Select By settings.
Event Filter
Events come with a default severity. Over time, you may notice that some events should have either higher or lower severity than the default. The Event Filter allows you to alter the Event Log by over-ruling an events default severity with your custom setting. 1. Setup menu > Event Filter. The Event Filter screen appears.
F1 Help: See Event Filter on page 778. 2. To add a new filter, click New. To edit an existing filter, highlight it and click Edit.


Confidential.
3. The Add / Edit Event Filter screen appears.
F1 Help: See Add / Edit Event Filter on page 738. 4. Select the following:
Event # Category This must be the exact event number, as it appears in the Event Log Viewer. This must be the same category as the corresponding event number, as it appears in the Event Log Viewer. Select what Event Severity to apply. This over-rules the default for the corresponding event. Remember: this can affect the notifications that are sent. Information Warning Error Shows the corresponding description for this event. This field cannot be edited.
Type
Description
5. Click OK to save the Filter. The Event Filter screen returns with the updated information. 6. Click OK to save the settings and close the Event Filter screen. The next time the filtered event(s) appear in the Event Log Viewer, the Filter will apply the designated severity type (over-ruling the default setting). The filter only applies if both the Event # and Category match with a corresponding event.


Confidential.
Audit Trail
The audit trail is a log that records all of the changes made to the DS-Client database. You can see who has made changes to the database, when, and what the changes were. 1. Logs menu > Audit Trail. The Audit Trail screen appears.
2. 3. 4. 5.
F1 Help: See Audit Trail screen on page 746. Click Find. You can change the Select By parameters to narrow the display: Click Find to refresh the display based on the information you specified. Click Close when you are finished.


Confidential.
Current Activity Monitor

The bottom section of the DS-User Screen contains a real-time activity monitor for the DS-Client. More information about DS-Client connections may be found in the System Status Screen (see Monitor current connections and processes on the DS-Client on page 363). 1. Current activities on DS-Client appear at the bottom of the DS-User Screen.
2. For more information, double-click a process. 3. The Process Window opens in the space to the right of the backup sets tree. From here you may monitor details, or stop the activity. F1 Help: See Process Window screen on page 807. Note: Since most processes are multi-threaded, they may finish faster than the GUI can refresh the screen. The Working on section displays a file currently being processed and last directory scanned, but these are independent of one another and might not correspond.


Confidential.
LAN Storage Discovery Tool

Use this tool to scan the shares on your LAN. It generates a list of the files on the LAN. This is useful to identify shares that are contained within other shares, and duplicate files on the network(s). For more details, see the Knowledge Base article: LAN Storage Discovery Overview on page 503
The following four steps are used with this tool: Step 1. Share Discovery: You select the networks \ computers to scan, and supply the list of credentials to use for connection. The first step depends on the type of DS-Client you are using: Step 1. Share Discovery (Windows DS-Client) on page 330 Step 1. Share Discovery (Linux DS-Client) on page 332 Step 2. Scan Shares on page 334: You can modify the discovered list of shares to scan. You can set the Scan to run with a Schedule. Step 3. Scan Monitor on page 336: Shows a real-time monitor of the Scan Process (at the share level). Step 4. File Summary on page 337: A list of the files scanned on the LAN. You can view additional details about particular files (file duplication, etc.). Additional LAN Storage Discovery Reports can be generated using the information from the File Summary: LAN Storage Discovery Reports on page 340


Confidential.
Step 1. Share Discovery (Windows DS-Client)

This wizard helps you select which networks \ workgroups \ domains \ computers to scan. Once complete, a list of all the shares visible will be available for the Scan Shares process. 1. Tools menu > LAN Storage Discovery > Share Discovery. 2. The Share Discovery Wizard appears.
F1 Help: See Select items for network share discovery screen on page 834. 3. From the Network tree, specify each item you wish to scan and click Add. Clean Share List: removes any previously scanned shares with size of 0. 4. When you have added all the network items you wish to scan, click Next. The Wizard switches to the Network Credentials tab.
F1 Help: See Specify network credentials for LAN Share Discovery screen on page 888.

Confidential.
5. In the Additional credentials section, click Add. The Set Credentials screen appears.
F1 Help: See Set Credentials screen on page 853. 6. Enter the credentials, and click OK. 7. Continue steps 5-6 until you have input all the credentials you want to use for the Share Discovery. Once you are satisfied with the settings, click Finish. The LAN Share Discovery Process Window appears.
8. This process may take some time, especially on a large LAN. 9. When complete, a list of the discovered shares will appear in Tools Menu > LAN Storage Discovery > Scan Shares: Share List (See: Step 2. Scan Shares on page 334).


Confidential.
Step 1. Share Discovery (Linux DS-Client)

This wizard helps you select which file system protocols \ computers to scan. Once complete, a list of all the shares visible will be available for the Scan Shares process. 1. Tools menu > LAN Storage Discovery > Share Discovery. 2. The Share Discovery Wizard appears.
F1 Help: See Select items for network share discovery screen (Linux DS-Client) on page 835. 3. On the left side of this Wizard, browse to select a network \ item you wish to scan and click Add. If the Ask for credentials box is checked, that screen appears. Enter the credentials and click OK. (UNIX-SSH only) If the sudo as an alternate user box is checked, that screen appears. Enter the credentials and click OK. (UNIX-SSH only) If the Advanced connection options box is checked, that screen appears. Enter the connection options and click OK. 4. The item appears in the Selected Items for Discovery list on the right side of this Wizard Tab. 5. Continue adding items until the Discovery list contains all the locations you wish to scan (to discover shares).


Confidential.
6. Click Next. The Wizard switches to the Clean previous unscanned shares in list tab.
F1 Help: See Clean previous shares in list (Linux DS-Client) on page 757. This screen shows a summary of the previous (Scan Shares) scan. If you select Clean share list, any shares with a Scanned Size of 0 will be automatically removed from the current Scan Shares List. However, they will be added again, if the previous Wizard Tab (Selected Items for Discovery) still contains them. 7. Once you are satisfied with the settings, click Finish. The LAN Share Discovery Process Screen appears.
8. This process may take some time, especially on a large LAN. 9. When complete, a list of the discovered shares will appear in Tools Menu > LAN Storage Discovery > Scan Shares: Share List (See: Step 2. Scan Shares on page 334).


Confidential.
Step 2. Scan Shares

Once you have run the Share Discovery Process, a Share List is generated, with the best credentials to connect to each share. Shares discovered are automatically enabled/disabled, depending on if they are already included in other shares (or if a connection cannot be established). Each subsequent Share Discovery that is run will add newly discovered shares to this Discovered Share list. You can only remove specific shares from this list manually. The Clean Empty Shares option (from the Share Discovery Wizard) only applies to shares with a Scanned Size of 0 (from the last Scan Shares process). Use this screen to edit the Scan settings. 1. Tools menu > LAN Storage Discovery > Scan Shares. 2. The Scan Shares screen appears.
F1 Help: See Scan Shares screen on page 815. 3. Click Share List. 4. The Share List screen appears with the enabled/disabled shares on the LAN to scan.
F1 Help: See Share List screen on page 878. TIP: 1st time scan all. Subsequent scans you can disable / enable shares to your scan requirements. (e.g. if you wish to do a quick scan of only one share.)


Confidential.
5. You can automate the Scan with a Schedule (new or existing), or perform it on demand by clicking Scan. 6. To perform it on demand, click Scan. A monitor screen will start.
7. This will take some time, depending on your settings (# of threads), the number and size of the share(s). 8. You may monitor the Scan Process through the Step 3. Scan Monitor on page 336. 9. Once the scan is complete, you may view the Scan results in Step 4. File Summary on page 337.


Confidential.
Step 3. Scan Monitor

This monitors the Scanned shares. It is updated at specified intervals with the most recent information. 1. Tools menu > LAN Storage Discovery > Scan Monitor.
F1 Help: See Scan Monitor screen on page 815. 2. Check the Show disabled shares box to display all shares found on the network(s) scanned.


Confidential.
Step 4. File Summary

The File Summary is compiled from the information gathered during the Scan Monitor. 1. Tools menu > LAN Storage Discovery > File Summary.
F1 Help: See Online / LAN File Summary screen on page 793. 2. For more information, highlight a line and click Details. The Details screen appears.
F1 Help: See Details screen on page 762. 3. Options: This screen shows all of the files for the selected line from the File Summary (e.g. All Files, Changed Files, etc.).


Confidential.
The Duplication Level is important, since it indicates the level of redundancy of some LAN data. You should monitor Backup Sets to ensure this duplication is considered. The Details list is limited to a maximum of 50,000 files. If the scan returns more than this number (which is likely on a LAN), the results are sectioned. 4. Click Close to exit this screen.
File Summary Filtered View

Use the Filtered View section (the lower half of the screen) to narrow your search. 1. The options at the bottom of the screen can be applied to narrow your search.
F1 Help: See Online / LAN File Summary screen on page 793. 2. Highlight a line in the Global or Filtered views, and click to open the Details screen.
F1 Help: See Details screen on page 762.


Confidential.
3. Each line shows a different file. 4. Highlight a file and click Show Duplicates.
F1 Help: See Duplicates screen on page 777. 5. Click Close to exit.


Confidential.
LAN Storage Discovery Reports

Based on the File Summary scan results, you can generate the following reports that describe the data trends on the LAN: Large Files on page 340 Extensions on page 341 Access on page 343 Growth on page 344 Share Usage on page 345 Generate Reports (one-click reports) on page 346 (One-click reports can be generated to HTML, CSV and XLS files.)
Large Files
Tools Menu > LAN Storage Discovery > Large Files
F1 Help: See File Size Report screen on page 782.


Confidential.
Extensions
Tools Menu > LAN Storage Discovery > Extensions: This is a customized view of the File Summary information. It sorts the files by extensions specified. The report shows the results of the extension search (of files scanned by the LAN File Summary Tool).
F1 Help: See Extension Report screen on page 781. 1. To search for specific file extensions, click New Report. To search for the most frequent file extensions, click Top Report. The Select Extensions (Top Report) screen appears.
F1 Help: See Select Extensions (Top Report) screen on page 829. A.Fill in all the fields. B.Click OK to scan and return the results in the Extension Report screen.


Confidential.
To search for selective file extensions, click Customize Report. The Select Extensions screen appears.
F1 Help: See Select Extensions (Customize Report) screen on page 828. A.Click Add. A new extension line appears. B.Enter the extension (without a period "."). C.Continue for as many extensions you want. D.Click OK to scan and return the results in the Extension Report screen. 2. Fill in the required information and click OK. 3. The Extension Report screen returns with a graph and list of the results.


Confidential.
Access
Tools Menu > LAN Storage Discovery > Access: This is a customized view of the File Summary information. It sorts the files by the time the file(s) were last accessed.
F1 Help: See Access Report screen on page 736. 1. Click New Report to specify the report intervals. The Select Access Intervals screen appears.
F1 Help: See Select Access Intervals screen on page 821. Click Add. A new Access Time line appears. Select the time interval. Continue for all the Access Time intervals required. Click OK to scan and return the results in the Access Report screen. 2. The Access Report screen returns with a graph and list of the results.

Confidential.
Growth
Tools Menu > LAN Storage Discovery > Growth: This is a customized view of the File Summary information. It sorts the files by the growth (positive and negative) over time (days). This report shows the data patterns (if any) on the LAN (or a specific share).
F1 Help: See Growth Report screen on page 785. You may change the view to different charts (Bar, Line) from the View drop down list.


Confidential.
Share Usage
Tools Menu > LAN Storage Discovery > Share Usage: This is a customized view of the File Summary information, sorted by owner and share.
F1 Help: See Share Usage Report screen on page 879.


Confidential.
Generate Reports (one-click reports)

Tools Menu > LAN Storage Discovery > Generate Reports: The above customized reports of the LAN Storage Discovery process can be generated to text, XLS, and HTML files at your request. This will generate all reports to a file folder you specify on the network. This may take some time, depending on the size of the report data.
F1 Help: See Generate Reports screen on page 784.


Confidential.
Unprotected LAN Resource Discovery Tool

Use this tool to scan the shares on your LAN. It generates a list of the nodes \ shares on the LAN that are not currently part of any backup set on the DS-Client. This is useful to identify new shares that require backup protection.
Note:
A scan can only detect unprotected resources for the current DS-Client.
The following section explain how to use this tool: Run the Unprotected LAN Resource Discovery (Windows DS-Client) on page 348 Unprotected LAN Resource - Node Summary on page 352 E-Mail the results of the last Unprotected LAN Resource scan on page 353 Unprotected LAN Resource - Share Summary on page 354 New Backup Sets Summary (Unprotected LAN Resource) on page 355


Confidential.
Run the Unprotected LAN Resource Discovery (Windows DS-Client)

This wizard helps you select which networks \ workgroups \ domains \ computers to scan. Once complete, a list of all the shares that this DS-Client does not currently backup is generated. You can also choose to have the wizard automatically create backup sets for these computers. 1. Tools menu > Unprotected LAN Resource > Discovery. 2. The Share Discovery Wizard appears. Select the network items you want to scan.
F1 Help: See Select items for scanning on page 835. 3. From the Network tree, specify each item you wish to scan or exclude. Add: Adds the highlighted item from the Network Tree to the Selected Items for Discovery list. Exclude: Excludes the highlighted item from the Network Tree from the scan. The items parent must already be in the Selected Items for Discovery list. Subnet: Allows you to add or exclude a specific subnet. The subnet is the third part of the IP address. (For example 12.34.56.0 will search the entire 56 subnet from 12.34.56.1 to 12.34.56.254.)
F1 Help: See Add / Exclude Subnet on page 739.


Confidential.
Select: Allows you to add or exclude scan items that were discovered by the previous scan of the Unprotected LAN Resource Discovery Tool.
F1 Help: See Add / Exclude item from scanning result on page 739. 4. When you have added all the network items you wish to scan, click Next. The Wizard switches to the Input Credentials tab.
F1 Help: See Input the credentials on page 787. 5. You must input at least one set of credentials. To add a new credential, click Add. To modify an existing credential, highlight it from the list and click Modify. The Set Credentials screen appears. F1 Help: See Set Credentials screen on page 853. 6. Enter the credentials, and click OK. 7. Continue steps 5-6 until you have input all the credentials you want to use for the Share Discovery. Once you are satisfied with the settings, click Next.


Confidential.
8. The Select a Schedule Tab appears. (This setting is optional. The default is Not scheduled, meaning the scan is only run on demand.)
F1 Help: See Select a schedule for scanning on page 820. 9. Click Next. The Select Scanning Options Tab appears. These are additional options that can apply once any unprotected network resource(s) have been discovered.
F1 Help: See Set the scanning options on page 877.


Confidential.
10. Click Next. The Select Scanning Parameters Tab appears.
F1 Help: See Set the scanning parameters on page 878. 11. Click Finish. The scan settings are saved. If you selected Start Scan Now, a process monitor window appears. This process may take some time, especially on a large LAN. 12. When the scan is finished, the following options are available: View a list of the unprotected computers sorted by Node (See: Unprotected LAN Resource - Node Summary on page 352). View a list of the unprotected shares (See: Unprotected LAN Resource Share Summary on page 354). View a list of the new backup sets automatically created by the last scan process (See: New Backup Sets Summary (Unprotected LAN Resource) on page 355). E-Mail the results of the last scan process (See: E-Mail the results of the last Unprotected LAN Resource scan on page 353).


Confidential.
Unprotected LAN Resource - Node Summary

Once the Unprotected LAN Resource Discovery Scan has run, any scanned computers (nodes) \ shares that are not currently backed up by this DS-Client are listed. This screen displays that information, sorted by computer (server). 1. Tools Menu > Unprotected LAN Resource > Node Summary.
F1 Help: See Unprotected LAN Resource Node Summary on page 892. 2. The contents of this screen are the results from the last scan. From this screen, you can:
E-Mail Exclude Shares Backup Set See E-Mail the results of the last Unprotected LAN Resource scan on page 353. Exclude the highlighted computers (nodes) from the next scan. See Unprotected LAN Resource - Share Summary on page 354. See New Backup Sets Summary (Unprotected LAN Resource) on page 355.


Confidential.
E-Mail the results of the last Unprotected LAN Resource scan

Once a scan has finished, you can E-Mail those results at any time from the various Summary screens. 1. To E-Mail the results of the last scan, click E-Mail. The Send Unprotected LAN Resource E-Mail screen appears.
F1 Help: See Send Unprotected LAN Resource Discovery E-Mail on page 852. 2. Enter the recipient E-Mail address(es). Separate multiple addresses with a semi-colon or a comma. 3. Click OK to send.


Confidential.
Unprotected LAN Resource - Share Summary

Once the Unprotected LAN Resource Discovery Scan has run, any scanned computers (nodes) \ shares that are not currently backed up by this DS-Client are listed. This screen displays that information, sorted by computer (server). 1. Tools Menu > Unprotected LAN Resource > Share Summary.
F1 Help: See Unprotected LAN Resource Share Summary on page 892. 2. The contents of this screen are the results from the last scan. From this screen, you can:
E-Mail Exclude See E-Mail the results of the last Unprotected LAN Resource scan on page 353. Exclude the highlighted computers (nodes) from the next scan.


Confidential.
New Backup Sets Summary (Unprotected LAN Resource)

Once the Unprotected LAN Resource Discovery Scan has run, any scanned computers (nodes) \ shares that are not currently backed up by this DS-Client can have backup sets automatically created. This screen displays that information, sorted by computer (server). 1. Tools Menu > Unprotected LAN Resource > Node Summary. 2. Click Backup Set. The New Backup Sets Summary screen appears.
F1 Help: See New Backup Sets Summary on page 792. 3. This screen shows the new backup sets that were automatically created by the last Scan process.


Confidential.
Online File Summary Tool

Use this tool to scan the backup sets created by your DS-Client. It generates a list of the files on the DS-System online vault. This is useful for identifying duplicate files that are being backed up. You can reduce backup traffic and online storage with this information. The screens are the same as for the LAN file summary (See: Step 4. File Summary on page 337 in the LAN Storage Discovery Tool section). 1. Reports Menu > Online File Summary.
F1 Help: See Online / LAN File Summary screen on page 793. For each row, a file is only counted once (even if there are multiple generations of that file). 2. Click Find. The process scans all of the backup files (based on the Filter parameters) on the DS-System.


Confidential.
3. Highlight a line in the Summary and click Details. The Details screen appears.
F1 Help: See Details screen on page 762. Each line represents a unique file. If more than one copy exists, the duplication amount is indicated in that column. 4. Highlight a file from the list and click Show Duplicates. The location of each duplicate file is shown in this screen.
F1 Help: See Duplicates screen on page 777. 5. Click Close when you are finished.


Confidential.
DS-Client Load Summary

The load summary is a visual tool that helps administrators analyze the load on the DS-Client computer for a selected period. Note: You can only view an analysis of the backup sets to which you have sufficient rights.
How to read the chart:

The default chart type is Line. You can change it to a bar graph from the dropdown list. The chart displays the period of days in the Select By section. You may change this period as required. By default, the last seven (7) days are selected. The horizontal axis shows the time intervals selected in the Chart Options section. By default, intervals each represent one day. The default graph shows the Send & Receive load (in KB), and the CPU load (%) on the DS-Client for the corresponding time. You can view more load information by selectively adding load summary items from the Series screen (described below).
Reports menu > Load Summary. The DS-Client Load Summary screen appears.
F1 Help: See Load Summary screen on page 789. 1. To change the Load Summary content, click Series. The Load Summary Series screen appears.
F1 Help: See Load Summary Series screen on page 789.


Confidential.
2. Add/change as many items as you wish. (It is recommended to view only 2-3 items at a time, to keep the display manageable). 3. Click OK. The Load Summary graph reappears with the updated information.
If you modify any Select By options, you must click Refresh if you wish to update the graph. To view more details about a particular period, hover the cursor over a point or bar. The details for that point / bar are displayed in a tooltip.


Confidential.
DS-Client Storage Summary

During the Daily Admin. process, storage information is saved about the backup sets specified on the DS-Client. Note: If the Daily Admin. process is not run, the Storage Summary will use the results of the last Daily Admin. that was run.
This chart will automatically open and refresh on the "best fit" for the screen. You may modify the type of chart or its appearance, depending on your particular requirements. Reports menu > Storage Summary. The DS-Client Storage Summary screen appears.
F1 Help: See Storage Summary screen on page 889. 1. To change the display, click Series. The Storage Summary Series screen appears.
F1 Help: See Storage Summary Series screen on page 890. 2. Add as many items as you wish. 3. Click OK when you are done selecting items. 4. The Storage Summary screen returns and is updated automatically.


Confidential.
System Administration Tools

Administrators and Backup Operators have access to more detailed tools to administer the DSClient. The System Activities Administration tools provide a variety of options to perform real-time troubleshooting. You can communicate with users connected to the DS-Client, disconnect users from, view the process queues, specify administrative backups and shut down the DS-Client computer. Setup menu > System Activities. The System Activities Administration screen appears.
F1 Help: See System Activities Administration screen on page 890. DS-Client Activities: Enable / Disable Scheduled activities Enable / Disable Demand activities DS-Client Operations: Shutdown the DS-Client Computer on page 364 Repair the DS-Client Database on page 364 Administrative Processes: Update DS-Client Statistics immediately on page 362 Run a Daily Admin immediately on page 362 Run a Weekly Admin immediately on page 362 System Status Operations: Monitor current connections and processes on the DS-Client on page 363 Send messages to users connected to the DS-Client on page 363 Disconnect Network Connections to the DS-Client on page 364


Confidential.
Update DS-Client Statistics immediately

Statistical data is gathered during one part of the Daily/Weekly Admin process. This feature allows you to update the statistics (number of files per backup set, online amount per backup set, and statistical data for Storage Summary) without running a full Daily or Weekly Admin: 1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Press Update Now beside the Statistics updated on ... field. 3. The Update Statistics process window appears.
Run a Daily Admin immediately

The following steps describe how to run the Daily Admin on demand: 1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Press Run Now beside the Last Daily Admin run on ... field. 3. The Daily Admin process window appears.
Run a Weekly Admin immediately

The following steps describe how to run the Weekly Admin on demand: 1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Press Run Now beside the Last Weekly Admin run on ... field. The Weekly Admin Options screen appears.
For details on these options, see the online help for the screen. F1 Help: See Weekly Admin Options screen on page 895. 3. Click OK to proceed.
Note:
For more information, see the Knowledge Base Article Weekly Admin and Synchronization on page 494.


Confidential.
Monitor current connections and processes on the DS-Client

You can monitor the current connections and processes, as well as view details of message queues and database connections through the DS-Client System Status screen. 1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Click System for real-time information about the current connections and activities on the DS-Client. The DS-Client System Status screen appears.
F1 Help: See DS-Client System Status screen on page 770. 3. Click Refresh to update the screen as required. The information provided in the tables is current as of the moment you selected the System Status screen, or refreshed the screen.
Send messages to users connected to the DS-Client

1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Click System. The System Status screen appears. 3. In the Network Connections tab, highlight the recipient for your message. 4. Click Send Message. The Enter Message Screen appears.
F1 Help: See Enter Message screen on page 777.


Confidential.
5. Type the message in the Send Message Field. 6. Click Send to send the message.
Disconnect Network Connections to the DS-Client

1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Click System. The System Status screen appears. F1 Help: See DS-Client System Status screen on page 770. 3. Highlight the connection you wish to remove in the Network Connections section of the screen. 4. Click Disconnect to disconnect the highlighted user from the DS-Client. A confirmation screen appears. 5. Click Yes to disconnect the selected user.
Shutdown the DS-Client Computer

The following steps describe how to shut down the DS-Client computer: 1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Click Initiate beside the System Shutdown checkbox. The Initiate System Shutdown screen appears. F1 Help: See Shutdown DS-Client Computer screen on page 879. 3. Enter the time (in seconds) that you wish to allow before shutting down. 4. Check the Reboot box if you want the DS-Client computer to reboot after shutdown. 5. Enter a message (if any) that you wish to send to users connected to the system. 6. Click Shutdown to proceed.
Repair the DS-Client Database

The following options are available to repair the DS-Client database: Recover the DS-Client Database (Disaster Recovery of DS-Client Computer) on page 367 Recover 'Orphaned' backup sets to the DS-Client on page 365


Confidential.
Recover 'Orphaned' backup sets to the DS-Client

It is possible (though unlikely), for some backup sets to become 'orphaned' on the DS-System. This means the backup data exists on the DS-System, but the settings have somehow been lost from the DS-Client's database. (This is possible if the DS-Client database is deleted, overwritten with an older version, or damaged.) The Event Log will have "Backup Set not found in Backup Log" errors, if this has occurred. These will appear on Daily or Weekly Admin. activities.
Use the System Activities > Repair DS-Client Database > Orphaned backup sets to Repair to repair the missing database information. This does not restore backup data; it recreates any missing backup sets in the DS-Client database. Once the backup sets are recovered, you may perform restores immediately. However, in order to resume backups, you must re-specify all of the information (backup items, schedule, etc.) using one of the following two options: Option A. Migrate (See: Migrate a Backup Set from one computer to another on page 194) Option B. Re-specify the Backup Set's information individually. Step 1. Specify the Connection Information (Network Credentials) for a Recovered Backup Set Step 2. Re-Specify the Backup Set's Backup Items Step 3. Re-Specify the Backup Set's Backup Schedule Step 4. Activating the Recovered Backup Set
Recover a Specific Backup Set

1. Setup menu > System Activities. The System Activities Administration screen appears. 2. Click Repair. The Repair DS-Client screen appears. F1 Help: See Repair DS-Client screen on page 810. 3. Select the Orphaned backup sets radio button. Click OK.


Confidential.
4. The Backup Set Recovery screen appears. Select the Backup Set you would like to recover.
F1 Help: See Backup Set Recovery screen on page 749. 5. In the Recovery Info screen, select the appropriate User Name and/or Network Provider for the Backup Set.
F1 Help: See Recovery Info screen on page 807. 6. Click Save to save the Recovery Info profile as specified. 7. In the Backup Set Recovery Screen, click Recover. The Backup Set will be recovered and Synchronized. 8. Open the Backup Sets screen and the recovered set(s) appear in suspended status (grayed out). 9. Once you have recovered the backup sets, you may restore files (to alternate location) at any time. 10. To perform backups you must ensure that the Computer Name, Connect As, Backup Items, and Backup Schedule information are complete. 11. For Backup Sets missing the Computer Name information, you must Migrate the backup set from <Unknown> to the actual provider name. 12. In the Backup Sets screen, Activate the Backup Set.

Confidential.
Recover the DS-Client Database (Disaster Recovery of DS-Client Computer)

In case of a disaster or other event at your location that requires the replacement of the DS-Client computer, you will need to recover the DS-Client's Database to the new machine. This database is backed up, based on the specification in the DS-Client ConfigurationParameters Tab (See: Configure the DS-Client Parameters on page 39). The recovered database will show data up to the time it was last backed up. Run a Weekly Admin. process to ensure that no other data exists on the DS-System that is not in the DS-Client's database. If more data exists, an error will appear and you must synchronize the backup set before any further backup/restore activities may be performed (See: Synchronize a Backup Set's Backup Logs on page 193). 1. Assemble the replacement DS-Client computer (hardware). 2. Install the Windows Operating system (same version as previous DS-Client), recreate the user accounts (including the DS-Client account) and then reinstall the DS-Client software to the computer. 3. Start the DS-Client Service and run DS-User. Verify the DS-Clients database patch levels (Help Menu > About DS-User > DS-Client Info: Database Build) 4. Setup menu > System Activities. 5. Click Repair. The Repair DS-Client screen appears. F1 Help: See Repair DS-Client screen on page 810. 6. Choose the DS-Client Database button or the DS-Client & Delta databases button. 7. Click OK. A recovery message appears, instructing you to restart the DS-Client service. 8. Stop and Restart the DS-Client service. The recovered Database will become active upon restart. 9. Run a Weekly Admin. process to ensure that the recovered DS-Client database data is not missing any backup sets. If it is, perform a backup set recovery. (See: Recover 'Orphaned' backup sets to the DS-Client on page 365.) 10. Follow the steps to Take Ownership of the backup sets (See: Change Backup Set Ownership on page 198). 11. Verify the DS-Clients database patch levels again (Help Menu > About DS-User > DS-Client Info). If the Database Build number is less than the number seen in Step 3, the database you recovered was from an older version of DS-Client, and is missing some patches. Re-run the most recent DS-Client service pack upgrade to get back to the same database build.
Note:
For more information, see the Knowledge Base Article Recovering the DS-Client Database on page 718.


Confidential.
12 - Reports
12 - Reports
This section provides information on the various reports that DS-User can produce, as well as the steps involved in generating these reports.


Confidential.
12 - Reports
Print Reports
The DS-User can print and export the following reports: Backup Sets Report on page 370 Restorable Report on page 372 Backup Users Report on page 374 Backup/Restore Report on page 377 Backup Trends Report on page 375 Backup Groups Report on page 379 Statistical Summary on page 381 Backup Items Report on page 383 You can only view reports that include all DS-Client users if you are logged into DS-Client as a member of the Administrators group.


Confidential.
12 - Reports
Backup Sets Report

This report shows information about each of the DS-Client's backup sets. 1. Reports menu > Backup Sets. The Backup Sets screen appears. F1 Help: See Print Report on page 805. 2. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Backup Sets Report details

Report Header Account No. Account Name DS-Client No. Customer Name The customer account number. The name of the customer account. The number of the DS-Client covered in this report. [Multi-Tenant DS-Client mode only] If this appears, it indicates this report only displays information from backup sets belonging to this customer.
Backup Sets report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed. Description The Backup Set Column lists all of the Backup sets specified on the DS-Client. The Connect As column lists the User Name being used to connect to the share/application. The Files column lists the number of files in each backup set (including all file generations). This column displays the protected size of the backup set data. This is the original, uncompressed amount of all the backup generations stored. For Regular backup sets, this shows the amount protected in the DS-System Online storage. For Statistical backup sets, this shows the amount of data that would theoretically be protected (if they were Regular backup sets). For Self-Contained and Local-Only backup sets, this shows the amount of data protected in the corresponding Local Storage Path(s).
Regular Statistical Self contained Local-Only Local DS-VDR
Printing date Report Table Columns Backup Set Column Connect As Files
Protected Size


Confidential.
12 - Reports
Stored Size
[This column only appears if it is enabled from the DS-System.] For Regular backup sets, this is the actual amount stored in the DS-System Online storage (after processing, compression, etc.). DS-Client retrieves the current Stored Size amount from DS-System at the end of any successful backup, retention or delete process, as well as during any Weekly Admin or Daily Admin process. For Statistical, Self-Contained and Local-Only backup sets, this column does not apply. The Last Backup column indicates the most recent date a scheduled backup was performed for that share. The Status column indicates whether the corresponding backup set is active or suspended.
Last Backup Status


Confidential.
12 - Reports
Restorable Report
This report shows information about restorable files. 1. Reports menu > Restorable. The Restorable screen appears. F1 Help: See Print Report on page 805. 2. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Restorable Report details

Restorable Volume report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed. Description The Backup Set Column lists all of the Backup sets specified on the DS-Client. Restorable amounts are calculated using the latest generation of files in the backup set. This column displays the restorable amount, which includes Deleted Data (Deleted data is backed up files that no longer exist on the source computer). Files: The number of files available for restore, including any files deleted from the backup source that are still backed up online. Restorable Size: The corresponding size of these files. This is the original (protected) size of the files as they were on the backup source. This column displays the restorable amount (latest generation of files in the backup set), but it excludes Deleted Data. Files: The number of files available for restore, excluding files deleted from the backup source that are still backed up online. Restorable Size: The corresponding size of these files. This is the original (protected) size of the files as they were on the backup source.
Printing date Report Table Columns Backup Set Column
With deleted data (Native Size)
Without deleted data


Confidential.
12 - Reports
Last Backup
The Last Backup column indicates the most recent date a scheduled backup was performed for that share.


Confidential.
12 - Reports
Backup Users Report

This report shows every user that is currently associated with any backup sets on the DS-Client. 1. Reports menu > Backup Users. The Backup Users screen appears. F1 Help: See Print Report on page 805. 2. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Backup Users Report details

Backup Users report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed. Description The User Name column lists each user associated with at least one backup set. The Full Name column lists the corresponding full name of each user who created the backup set (if applicable). The Connect As column lists the credentials being used to access the backup set's share. The Backup Set column lists the share\set name of each backup set on the DS-Client. The Online Limit column lists the maximum limit that each user may store Online. The Online Amount column lists the amount that each user currently has Online.
Printing date Report Table Columns User Name Full Name Connect As Backup Set Online Limit Online Amount


Confidential.
12 - Reports
Backup Trends Report

This report shows usage statistics. 1. Reports menu > Backup Trends. The Backup Trends screen appears.
F1 Help: See Print Backup/Restore Summary & Backup Trends Report on page 800. 2. By default, you will see trends for all backup sets from the beginning of the month to the current day. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Backup Trends Report details

Backup Trends report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Weekly / Monthly Summary Shows if this report covers any or all of the Regular (actual), Statistical, Deleted, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Deleted backup sets are calculated using data from the Activity Log. Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Indicates the period covered by the report.
Regular Statistical Deleted Self contained Local-Only Local DS-VDR
Period


Confidential.
12 - Reports
User Name Backup Set(s) Printing date Report Table Columns Week / Month Date Files Total Size Backup Time Total
Shows the user or <All> Shows the backup set, or <All> Day the report was printed. Description Lists the week or month number for each row of data. Lists the date each row of data covers. Shows the total number of files backed up in each period. Shows the total size of all the files backed up in each period. Shows the total time taken for backups in the corresponding period (in minutes). Shows a grand total of each of the last three columns.


Confidential.
12 - Reports
Backup/Restore Report
This report summarizes each user's backup and restore operations during the specified Report period. 1. Reports menu > Backup/Restore. The Backup/Restore Report screen appears.
F1 Help: See Print Backup/Restore Summary & Backup Trends Report on page 800. 2. By default, you will see summaries of daily user backup and restore sessions from the beginning of the month to the current day. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Backup / Restore Report details

Backup / Restore report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Deleted, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Deleted backup sets are calculated using data from the Activity Log. Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Indicates the period covered by the report. Shows the user or <All>
Confidential.
Regular Statistical Deleted Self contained Local-Only Local DS-VDR
Period User Name

12 - Reports
Backup Set(s) Printing date Report Table Columns User Name
Shows the backup set, or <All> Day the report was printed. Description The User Name column lists the user who performed the backup or restore, and the date of the operation. Each day listed beneath a user name represents a day within the report period when either backup or restore activities occurred for that user. The Activities columns list the total time taken for backup/restore activities and the total number of sessions for the listed user. Time (min): Total duration of all the sessions for the corresponding line of the report. (Note: CDP backups are counted when they are stopped, which means if a CDP backup that has been running for 5 days is stopped, it will report 7200 minutes on that day.) #: Total number of sessions (both backup and restore). These columns list the number of files backed up that day, the volume of data backed up, and the number of connections made on that day to perform a backup. # of Files: Total number of files backed up. Amount (MB): Total amount of data backed up (Protected Size). #: Total number of backup sessions. These columns list the number of files restored that day, the volume of data restored, and the number of connections made on that day to perform a restore. # of Files: Total number of files restored. Amount (MB): Total amount of data restored (Protected Size). #: Total number of restore sessions. The last row for each user listed in the report contains that users totals for the report period. The last row of the entire report contains the grand totals for all users listed in this report.
Activities
Backup Activities
Restore Activities
User Total Grand Total


Confidential.
12 - Reports
Backup Groups Report

This report is a breakdown of the current Online usage, sorted by user group. 1. Reports menu > Backup Groups. The Backup Groups Report screen appears. F1 Help: See Print Backup Groups screen on page 801. 2. Leave the Group Name field empty for a summary for all backup groups. To specify a single group, click the >> button. The Select Group screen appears.
3. 4. 5. 6.
F1 Help: See Select Group / User screen on page 829. Highlight the group you want and click Select. Select Regular [Default], Self Contained, and / or Statistical backup set type(s). Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.


Confidential.
12 - Reports
Backup Groups Report details

Backup Groups report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Group Shows the backup group, or <All> Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed. Description The first column lists the user group. Shows all users belonging to the Group. May contain the appropriate real name associated with the user in the User Name column (if applicable). Lists the number of files that the user currently has stored Online. Lists the total amount which the files occupy Online. At the bottom of the data for each group, there is a summary total in the Files and the Online Amount columns.
Printing date Report Table Columns Group User Name Full Name Files Online Amount Totals


Confidential.
12 - Reports
Statistical Summary
This report shows usage statistics. It is particularly useful in conjunction with the Statistical Backup Set feature (see Statistical Backups on page 177). 1. Reports menu > Statistical Summary. The Statistical Summary screen appears.
F1 Help: See Print Statistical Summary on page 806. 2. Make your report selections. For details on these options, see the online help for the screen (Press F1 in this screen). 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Statistical Summary Report details

Statistical Summary report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed.
Confidential.
Printing date

12 - Reports
Period Statistics updated on User Name Backup Set(s) Report Table Columns Machine Name / Backup Set / User Date New Files
Indicates the period covered by the report. Date when the statistics used in this report were gathered. Shows the user, or <All> Shows the backup set, or <All> Description This column name shows if the report is sorted by computer, backup set, or user. Each line corresponds to a specific day. These columns display the total number of new files backed up on the corresponding day. #: Number of new files Amount (MB): Amount of data (MB) in the new files These columns display the all the files backed up on the corresponding day. This includes multiple generations of the same file (if applicable). At the bottom of each section (computer, backup set, or user), totals and averages for the period appear. #: Total number of files backed up Amount (MB): Amount of data in the backed up files Transmitted (MB): Total size of files transmitted (this only includes the successfully transmitted amount) Compression Ratio: Ratio achieved = Amount/Transmitted Total amount transmitted from DS-Client to DS-System. This number includes any amounts transmitted for incomplete or failed backups. These columns display a running total of all the files stored on DS-System for the corresponding computer / backup set / user. (Do not consider these columns in relation to the others.) #: Total number of backup files stored offsite Amount (MB): Total size of the backed up files This amount includes each generation of a file. For example three generations of a 10MB file would show 3 files and 30MB transmitted. Only generations that are still online are counted. This column refers to the amount of data before compression, encryption, common file elimination, master/delta processing. Total backup time (per day) for the corresponding computer / backup set / user.
Backed Up Files
Transmitted Amount (MB)
Files Stored Off Site
Backup time (min.)


Confidential.
12 - Reports
Backup Items Report

This report shows information about each of the DS-Client's backup sets. 1. Reports menu > Backup Items. The Backup Items screen appears. F1 Help: See Print Report on page 805. 2. Make your report selections. 3. Click OK (Java DS-User) or Print Preview (Win32 DS-User). A preview of the report appears. 4. Click the printer icon to print. To export the report to a file, you can click the Save (Java DS-User) or Export (Win32 DS-User) icon. Choose the export format (PDF, Word, Excel, etc.) and destination.
Backup Items Report details

Backup Items report selection DS-Client Report (Java DS-User displays the DS-Client computer name in parenthesis) Shows if this report covers any or all of the Regular (actual), Statistical, Self contained, Local-Only, or Local DS-VDR backup set types. Statistical backup sets allow you to estimate the potential storage those backup(s) would occupy. Self contained and Local-Only backup sets perform backup and restore using only the Local Storage (DS-User Setup Menu > Configuration > Parameters Tab > Local Storage Path) Local DS-VDR backup sets do not show any DS-System data storage or transmission amounts, since they do not apply. Day the report was printed. Description The Backup Set Column lists the source server, backup set name, and backup set owner. Shows what type of backup set (Regular, Statistical, Self Contained). The Backup Items column lists the individual backup items specified in the backup set. A double-plus sign (++) indicates this backup item includes sub-directories. A single-plus sign (+) indicates this backup item does not include sub-directories. A minus-sign (-) indicates that this is an Exclude backup item.
Printing date Report Table Columns Backup Set Set Type
Backup Items


Confidential.
12 - Reports
Export
An export function is included to allow you to save important backup set information in an electronic format.
Backup Sets Info

This exports the following:
ID Name Restorable Files (without deleted data) Restorable Amount (without deleted data) Restorable Files Restorable Amount Protected Generation Count Protected Amount Backup Set Stored Amount Library Stored Amount Unique Backup Set ID number Backup Set Name Number of files available for restore without deleted data. This is the size that the Restore Wizard would display when selecting to restore the entire backup set. Deleted data is backed up files that no longer exist on the source computer. Amount (in Bytes) of data available for restore. Number of files available for restore with deleted data. Amount (in Bytes) of files available for restore with deleted data. Total number of file generations stored on the DS-System. Amount (in Bytes) of the data storage on the DS-System (as it appears in the Backup Sets Properties > Set Info - Online Amount). DS-Size on DS-System Side. This number is always 0. Library amount after the distribution. Library size is split by the number of links. This means the Distributed Library Amount is calculated with this formula: LibSize / TotalLinksToThisLib x NrLinksInThisBkSet + sizeOfNrLinksInThisBkSet Distributed Library Amount Because the sizeOfNrLinksInThisBkSet is included in Distributed Library Amount, the value for Library Stored Amount is always 0. Therefore the backup set total stored size is: Backup Set Stored Amount + Distributed Library Amount Last Backup The Last Backup column indicates the most recent date a backup was performed for that share.
Files that were not backed up by the last backup session. If the backup Files not picked up by Last Backup was not interrupted by the user ("User Stop"), this is the number (amount) of files that did not change. Amount not picked up by Last Backup Amount (in Bytes) of the above.
Note:
Some additional columns might be visible (depending on the DS-Client configuration set by your Service Provider).
1. Reports Menu > Export > Backup Sets Info. The Backup Sets Info screen appears. F1 Help: See Backup Sets Information on page 750. 2. In the File Format list, select a format to export the Backup Sets Info as. 3. In the Save As section, click the icon to open a standard Save As dialog.


Confidential.
12 - Reports
Global Reports (Java DS-User)

NOTE: You do not need to be connected to a specific DS-Client to use this feature. This option is always available from the JAVA DS-User > Reports Menu > Global Reports. Global Reports are the same as the reports available from: Print Reports on page 369 The Global Reports feature allows you to print the selected report for multiple DS-Clients in the same print session. This saves a lot of time if your environment has many DS-Clients, since you would otherwise have to connect to each DS-Client individually, and then print the desired report(s). The Java DS-User must be able to connect to the selected DS-Clients, and you must supply valid credentials to each DS-Client. The following Global Reports can be generated: Global Report - Export Backup Sets Information on page 389 Global Report - Backup Sets Report on page 389 Global Report - Restorable Volume Report on page 389 Global Report - Backup Users Report on page 389 Global Report - Backup / Restore Report on page 390 Global Report - Backup Trends on page 390 Global Report - Backup Groups Report on page 390 Global Report - Backup Items Report on page 390 Global Report - Statistical Summary Report on page 391


Confidential.
12 - Reports
Selecting DS-Client(s) for a Global Report

Global Reports require a list of the DS-Clients and credentials in order for the Java DS-User to connect and generate the reports. Remember that this section (under the Global Reports sub-menu) applies only to the current Java DS-User installation from which you are working. 1. A DS-Client field appears at the top of each Global Report print screen.
F1 Help: See Print Global Report - Export Backup Sets Information on page 804. 2. Click [...]. The Select DS-Clients screen appears.
F1 Help: See Select DS-Client (Print Global Report) on page 828. From this screen, you create the list of DS-Clients whose reports you want to generate. You must specify at least one DS-Client (otherwise no report can be generated). 3. You can add DS-Clients to the list individually, or together as a group using the Autosearch feature. To add DS-Clients individually: Click Add / Modify. The New / Modify DS-Client Connection Entry screen appears. F1 Help: See Add / Modify DS-Client Connection Entry (Print Global Report) on page 739. When you enter the IP address of the target DS-Client computer, press TAB or highlight a different field. Java DS-User attempts to connect to the DSClient at that IP address. If successful, the drop-down list activates beside the From field (with the available servers where the credentials can be verified).

Confidential.
12 - Reports
You must supply valid credentials to this DS-Client. These must be administrator equivalent if you want to view Reports for all users and groups. To add using the Autosearch feature: Click Auto Search. Java DS-User scans the network, and the DS-Clients Auto Search screen appears with the visible DS-Clients in its list.
F1 Help: See DS-Clients Auto Search (Print Global Report) on page 772. To add multiple DS-Clients, hold down the CTRL key while clicking. When you have finished making your selections, click Add Selected. The DS-Client Connection Entry screen appears. You must enter a user name and password that is valid on all of the selected DS-Clients. If you do not have common credentials (with sufficient permissions), you must specify each DSClient individually. Click OK. The Select DS-Clients screen returns with the added connection entries. 4. You can save the connection entries you have listed, but they will only be retrievable from the current Java DS-User installation. (The computer / IP / credentials are saved to the local user.ini file in encrypted format.) To save or load credentials, click the corresponding button. Enter the key to lock or unlock the credentials and click OK. If loading, the Select DS-Clients screen returns with the saved connection entries.
F1 Help: See Enter Lock Key For Credentials (Print Global Report) on page 777.


Confidential.
12 - Reports
You can only save one set of DS-Client Connection Entries. If you click Save again, whatever is in the Select DS-Clients screen at that time will overwrite any saved credentials. 5. Once you have finished the list of DS-Clients, click OK. The Global Report Print screen returns with the selected DS-Clients in the corresponding field. Make any required report selections, then click OK to generate the reports.
Note:


Confidential.
12 - Reports
Global Report - Export Backup Sets Information

1. Reports menu > Global Reports > Export Backup Sets Info. The Global Report Backup Sets Information screenv12.0 [Revision Date: October 15, 2012] appears.
F1 Help: See Print Global Report - Export Backup Sets Information on page 804. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Export Options section, specify how you want to save the file. 4. Click OK. The report that is exported is essentially the same as the regular Backup Sets Info report. See Backup Sets Info on page 384.
Global Report - Backup Sets Report

1. Reports menu > Global Reports > Backup Sets. The Global Report - Backup Sets screen appears. F1 Help: See Print Global Report - Backup Sets Report on page 803. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Sets report. See Backup Sets Report details on page 370.
Global Report - Restorable Volume Report

1. Reports menu > Global Reports > Restorable. The Global Report - Restorable Volume screen appears. F1 Help: See Print Global Report - Restorable Volume Report on page 804. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Volume report. See Restorable Report details on page 372.
Global Report - Backup Users Report

1. Reports menu > Global Reports > Backup Users. The Global Report - Backup Users screen appears.

Confidential.
12 - Reports
F1 Help: See Print Global Report - Backup Users Report on page 803. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Users report. See Backup Users Report details on page 374.
Global Report - Backup / Restore Report

1. Reports menu > Global Reports > Backup / Restore. The Global Report - Backup / Restore screen appears. F1 Help: See Print Global Report - Backup / Restore Report on page 801. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup / Restore report. See Backup / Restore Report details on page 377.
Global Report - Backup Trends

1. Reports menu > Global Reports > Backup Trends. The Global Report - Backup Trends screen appears. F1 Help: See Print Global Report - Backup Trends Report on page 803. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Trends report. See Backup Trends Report details on page 375.
Global Report - Backup Groups Report

1. Reports menu > Global Reports > Export Backup Sets Info. The Global Report Backup Groups screen appears. F1 Help: See Print Global Report - Backup Groups Report on page 802. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Groups report. See Backup Groups Report details on page 380.
Global Report - Backup Items Report

1. Reports menu > Global Reports > Backup Items. The Global Report - Backup Items screen appears. F1 Help: See Print Global Report - Backup Items Report on page 802. 2. To select the DS-Client(s):

Confidential.
12 - Reports
See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Backup Items report. See Backup Items Report details on page 383.
Global Report - Statistical Summary Report

1. Reports menu > Global Reports > Statistical Summary. The Global Report - Statistical Summary screen appears. F1 Help: See Print Global Report - Statistical Summary Report on page 804. 2. To select the DS-Client(s): See Selecting DS-Client(s) for a Global Report on page 386. 3. In the Report Selection section, specify what you want to display. For details on the options, see the online help for the screen. 4. The report that appears is essentially the same as the regular Statistical Summary report. See Statistical Summary Report details on page 381.


Confidential.
12 - Reports
Custom Reports
The Custom Reports feature allows you to create your own reports, based on the data provided from the DS-Client database tables. This feature is meant for advanced users. This requires a third-party application (either JasperReports or Crystal Reports), which means you must have the development resources to create and compile the custom report templates. Step 1. Create Customized Data on page 392 Step 2. Create Customized Report (with Third-Party application) on page 395 Step 3. View Customized Report on page 396
Step 1. Create Customized Data

The first step is to select what data you want to use for the customized report. 1. Reports menu > Customized Data. The Customized Data Wizard screen appears.
F1 Help: See Customized Data Wizard - Select a Data Set on page 760. Choose an existing Data Set or select <new> to create a new one. Data Set selections are saved in the .ini file for the DS-User installation you are using (user.ini for Java DS-User or DSUSER.INI for Win32 DS-User). Choose a View. Data is grouped into different views. Each view can contain one or more tables from the DS-Client database. The same table can appear in different views.


Confidential.
12 - Reports
2. Click Next. The Customized Data Wizard - Select Display Columns screen appears.
F1 Help: See Customized Data Wizard - Select Display Columns on page 761. A list of all fields from all tables for the selected View appears in the left column. Click on a field to select it. At the bottom of the screen you will see an expanded description of what that field contains. Click Add to move the field to the selected column list on the right. (Multiple fields can be selected using the SHIFT or CTRL keys). You can order the selected fields with the Up and Down arrow buttons. This is the order in which the data fields will be written. Continue for as many fields as you require. 3. Click Next. The Customized Data Wizard - Select Order screen appears.
F1 Help: See Customized Data Wizard - Select Order on page 761. A list of all available sort fields appears in the left column. This is based on the fields you selected to display in the previous screen. Add as many sort fields as you require. You can order the selected fields with the Up and Down arrow buttons. This is the order in which the data set will be sorted. Continue for as many columns as you require.
Confidential.

12 - Reports
If you do not make a selection, data will be written as it is read from the database. (Note: This sort order is not used by JasperReport or Crystal Reports.) 4. Click Next. The Customized Data Wizard - Select Data Filters screen appears.
F1 Help: See Customized Data Wizard - Set Data Filters on page 761. The default (if you do not set any filters) is to search for all data. If you set a filter, only data that matches the filter will be exported. 5. Click Next. The Customized Data Wizard - Enter Data Set Name screen appears.
F1 Help: See Customized Data Wizard - Enter Data Set Name on page 760. You can save the Data Set settings for quicker access next time. These selections (with the exception of Data Filters) are saved in the .ini file for the current DS-User GUI installation you are running. Export data to file is selected by default. You must export the Data Set to a file in either XML or CSV format.


Confidential.
12 - Reports
6. Click Next. The Customized Data Wizard - Confirm Data Set Summary screen appears.
Note:
F1 Help: See Customized Data Wizard - Confirm Data Set Summary on page 760. Click Finish. If Export data to file was selected, a Save As dialog appears, allowing you to save the Data Set to a file in either XML or CSV format. Export as XML if you want to create a custom report template. The Data Set you export contains a snapshot of the data from the fields you queried from the DS-Client database at the moment you clicked Finish. This can be used to create a one-time custom report. However, it is the data structure (data fields) that is used to create a re-usable custom report template.
Step 2. Create Customized Report (with Third-Party application)

A third-party application is required to manipulate the Data Set into a custom report (and custom report template). There are two options, depending on the type of DS-User you are using: Win32 DS-User: You must purchase the Crystal Reports application from http://www.crystaldecisions.com. These examples use v.10 of the Crystal Reports software. Java DS-User: You need to download the free JasperReports application from http://www.jasperforge.org. These examples use v.3.7.0 of the JasperReports software. 1. With the exported Data Set (XML file), you must now use the third-party jasper tools to create your custom report using the fields from the Data Set. 2. Refer to the DS-Client Knowledge Base article describing Custom Reports on page 477 for instructions. 3. Once you have created the compiled .jasper or .rpt report file, copy it to the \report subdirectory of the folder where this DS-User GUI is running (if it does not exist, create it - this is case-sensitive, so make sure the folder is named report).


Confidential.
12 - Reports
Step 3. View Customized Report

1. Reports menu > Customized Reports. The Customized Report Wizard screen appears.
F1 Help: See Customized Report Wizard - Select Report Template on page 761. In the Template name field, select the custom report you wish to view. The list shows the compiled report template files in the \report subdirectory of the folder where this installation of DS-User is running. 2. Click Next. The Customized Report Wizard - Select Data Filters screen appears.
F1 Help: See Customized Report Wizard - Set Data Filters on page 762. The default (if you do not set any filters) is to display all data in the report. If you set a filter, the custom report will display only data that matches the filter.


Confidential.
12 - Reports
3. Click Next. The Customized Report Wizard - Confirm Report Summary screen appears.
F1 Help: See Customized Report Wizard - Confirm Report Summary on page 761. 4. Click Finish. The Custom Report appears.


Confidential.
Glossary of Terms
Glossary of Terms
Asigra Cloud Backup

An automatic, unattended backup/restore management service, including the DS-System, DS-System Software, DS-Operator Software, DS-Client, DS-Client Service Software, DS-User Software, and communication links.
Administrator
A user with full access privileges to the DS-Client.
Audit Trail
A log that records changes made to the DS-Client database.
Backup Groups (Report)

The backup groups report summarizes the usage by user group (Administrator, Backup Operator, Regular User, etc.).
Backup Operator
A user with rights to backup sets that would not otherwise be accessible. Backup Operators possess the full backup authority, but not the permissions of Administrators (e.g. no unlimited restore permissions).
Backup Set
A list of the items (directories, files, and applications) you wish to back up from your computer (or network). A Backup Set includes information about how these items will be backed up (Backup Options), and when they will be backed up (Schedule). Backup sets are created through the DS-User program.
Backup Sets (Report)

This report shows all of the DS-Client's backup sets. It shows details about the source path, owner, connection, number of files, Online amount, last scheduled backup and status.
Backup Trends (Report)

This report shows usage statistics (files backed up, size in KB, and Backup time in Minutes) grouped by week or by month. It can be made for an individual user, all users, or a particular node /share.
Backup Users (Report)

This report displays all of the users who currently have specified backup sets. This is useful when tracking the storage usage of users, and may assist to determine whether an individual requires a higher storage limit.
Backup/Restore (Report)
This summary provides a detailed breakdown of each Asigra Cloud Backup user's daily backup and restore activities. Then it breaks down usage by connection time, number of files, and data volume. A summary total is provided for the selected time period at the bottom of the user's section.

Confidential.
Glossary of Terms
Grand totals are provided for the entire period at the bottom of the report.
Backup Wizard
A DS-User utility to guide you through the creation of a backup set.
Current Activity Monitor

A DS-User utility that allows Administrators to monitor DS-Client connections and activities.
Daily Admin.
Performs a verification of backup sets, and (if configured) transfers a dump of the DS-Client database to the DSSystem.
Demand Backup
A DS-User utility that allows users to backup a set immediately (as opposed to waiting for it to run at a scheduled time).
Details (Schedule)
Each Detail is a description of a specific date/time pattern when to perform a backup. You may add as many details to a Schedule, as are required. Each Detail refers to a specific backup circumstance (e.g. "Occurs every 2 week(s) on Friday, at 6:00 PM"). For example: You may wish to back up weekly, and back up on a specific day (such as the last Friday of every month). To do so, simply create one detail for the weekly backup, and a second detail for the monthly backup.
Digital Signature
A standard feature applied to all backup files. Asigra Cloud Backup automatically creates, attaches and stores a unique digital signature for each backup file. During restore processes, the signature of the restored file is compared with the signature that was generated at backup time. If they match, this confirms a 'carbon-copy' restore of the file that was backed up.
Disaster Restore
A process to restore a large amount of backup data that is coordinated between the DS-Client LAN Administrator and the Service Provider. The restore is performed via direct (or LAN) connection to Disc/Tape media brought to the recovery site.
DS-Client
ASIGRA's proprietary software, designed to perform unattended and demand backups and selective restoration of a user's specified files. The DS-Client software runs as a service on Windows Platforms, and as a daemon on Linux Platforms. It serves as a gateway to the DS-System: User data tagged for backup (see Backup Set) flows through the DSClient, where it is compressed, encrypted and sent to the DS-System for storage.
DS-Client Buffer
DS-Client buffer is disk space on the DS-Client computer that is used as temporary storage during some types of backups (ex: MS Exchange Server, MS SQL Server dumps).
DS-Client Pipe
DS-Client Pipe is an alternative to the database dump for MS SQL and MS Exchange Server backups. This option does not consume any additional disk space. During backups, the DS-Client reads from the pipe on the source database. This method is useful if your database is too big to be dumped to a file on either the database server or the DS-Client buffer.

Confidential.
Glossary of Terms
DS-Client Service Manager

(Windows DS-Client) This program allows you to start and stop the DS-Client service. By default, it is located in the DS-Client installation directory.
DS-System
The DS-System stores the customer's Online data, and is located at a Asigra Cloud Backup Service Provider's secure, offsite, Vault location.
DS-User
DS-User is the end-user software that runs on your standalone PC or LAN workstation. This application is the interface that permits you to create a Backup Set to identify the files and directories you want the DS-Client to back up.
Event Log
A log that displays the error, warning, and information messages that occurred during DS-Client activities for the period selected.
Exclude
An option which is available in some screens. This allows you to exempt specific subdirectories, if the parent directory has been selected.
Filter
A pattern that can be specified to reduce a search of a large list (e.g.: *.exe will search for all files with an 'exe' extension).
Generation
Indicates the version of a file kept Online.
Incremental Files
A standard DS-Client feature, whereby only the changed files are backed up to the DS-System. This process eliminates the redundancy of backing up unchanged files.
Initial Backup
The Initial Backup feature allows you to backup to local buffer location(s) directly attached to the DS-Client (or on the LAN). Then, you can ship that media (e.g. disks) to the DS-System location. Your Service Provider will attach the media to the DS-System and import the Initial Backup data. Once it is imported to the DS-System, you can continue protecting your data with subsequent scheduled and on-demand backups.
Knowledge Base
The DS-Client Knowledge Base on page 403 contains additional information regarding DS-Client operations for more technical users.
Load Summary
The Load Summary is a tool that can help administrators analyze the load on the DS-Client computer for a selected period of time.
Migration
Asigra Cloud Backup allows you to change the provider/computer of a backup set with the Migration feature. This is useful if you rename your computer, change the operating system, or change the physical location of files.

Confidential.
Glossary of Terms
Registration
If hardware registration is required by your Service Provider, during the first activity between the DS-Client and DS-System, the DS-Client is registered with the DS-System. In this process, the DS-Client sends a unique key identifier (based on the operating system and hardware configuration of the DS-Client computer), which is used in the connection and verification process. This registration is an added security step, whereby the DS-System will only accept communication from the registered installation of the DS-Client. (i.e. You cannot copy the DS-Client software from one machine to another and immediately use it as if it were the same machine. If you change your DS-Client computers hardware or Operating System, this may also cause the registration verification to fail. Only your Service Provider can permit your DS-Client to re-register with the DS-System. Contact your Service Provider for more details.)
Regular User
The majority of Asigra Cloud Backup users in a LAN environment are Regular Users. Their main requirement is to be able to specify and backup data that they can access, and restore their backups, as required.
Reports
Reports are an important administrative and bookkeeping tool for administrators. These help to track usage and trends among Asigra Cloud Backup users. The DS-User software can create, print and export five different reports (Backup Sets, Backup Users, Backup/Restore Summary, Backup Trends, and Backup Groups). Each of these reports sorts the collected data in different ways.
Restore Wizard
The Restore Wizard is a graphical tool that will assist you to restore a backup set. It is divided into separate tabs that depend on the type of backup you are trying to restore. The information in these tabs change to reflect each successive choice you make in a previous tab. The Wizard is designed to guide you through the necessary selections to restore a backup set.
Schedule
A Schedule is a set of Details that indicate when unattended (automatic) tasks like backups are to be performed. Each Detail refers to a specific backup circumstance (e.g. "Occurs every 2 week(s) on Friday, at 6:00 PM").
Scheduled Backup
A backup that runs automatically, according to the Schedule used.
Statistical Backups
The only difference between Statistical Backups and Regular backups, is that backup data is not sent to the DSSystem for storage with a Statistical Backup. All other processes are performed, allowing you to analyze the data trends before committing to perform real backups.
Status
An item's status indicates whether activities are being performed with it. The corresponding status could be Active, Suspended, or Synchronize.
Storage Summary
The Storage Summary is a tool to help administrators analyze the trends for Online amount, number of files and backup time.


Confidential.
Glossary of Terms
Suspended
A Suspended status indicates that scheduled backups are not being performed on this item. Backup data will remain stored on the DS-System according to the backup sets' Generation settings.
Use Buffer
The Use Buffer option can be used for backups and restores. It is useful in cases where the LAN allows only a short screen for backup/restore. Since the data must be transferred and compressed/encrypted through the DSClient, it may take more time than the period available. If Use Buffer is selected, the backup/restore process will copy all of the specified backup files to the local storage on the DS-Client's hard disk first. This ensures that the backup/restore transfers files from/to the target servers at LAN speed (i.e. as fast as possible given your LAN infrastructure).
User Name
The name that you use on the machine or domain where the DS-Client will verify your credentials.
Weekly Admin.
Performs all Daily Admin. activities, and a low-level synchronization of backup sets. During this process, an indepth verification occurs between the DS-System's and the DS-Client log.


Confidential.
DS-Client Knowledge Base


Confidential.
Knowledge Base: SETUP
The Knowledge Base contains articles on specific areas of DS-Client operation.


Confidential.
Ports used in Asigra Cloud Backup applications

Creation Date: November 2, 2005 Revision Date: April 26, 2012 Product: DS-Client
Summary
The following table shows the map of ports used by DS-Client in Asigra Cloud Backup applications:
New 80 443 4401 4403 4405 4407 4408 4410 4411 Description DS-Client -> DS-NOC (http) DS-Client -> DS-NOC (https) DS-Client -> DS-System DS-Mobile Client -> DS-System DS-User -> DS-Client DS-Client -> DS-MLR DS-Client -> Local DS-VDR DS-Client -> DS-Recovery Tools DS-Client -> DS-Client (Grid DS-Client) API Connections -> DS-Client service / daemon
Note:
Port numbers 4400-4406 are IANA-assigned.
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. Asigra Inc. All Rights Reserved. Confidential.


Confidential.
Resolving port conflicts for the DS-Client software

Creation Date: October 18, 2005 Revision Date: October 18, 2005 Product: DS-Client installed on Windows Operating Systems
Summary
In order to operate, the DS-Client needs to open the port 4403 (or 3002 for versions older than v.6.0) for the TCP/UDP protocols on the machine where it is installed. If this fails, the DS-Client service will stop and will record the following error in the Windows Application Log: "Failed to open ports (ds-user,TCP)." The DS-Client might fail to start on some Windows Operating Systems because of a port conflict between the DS-Client and some Microsoft services like WMI. A workaround from Microsoft to resolve the port conflicts is described below: 1. Run "RegEdit". 2. Browse to
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters"
3. Double click the key named "ReservedPorts", and add "4403-4403" (or "3002-3002" for DS-Clients before v.6.0). 4. Make sure that the key value ends with one empty line by hitting the "Enter" key. 5. Click the "OK" button to save the Registry changes. 6. Restart Windows and the port conflict should not occur.


Confidential.
Running DS-Client using PostgreSQL database on Mac OS X with Apple Remote Desktop (ARD)
Creation Date: March 02, 2006 Revision Date: March 02, 2006 Product: DS-Client (Macintosh)
Summary
This article deals with some potential problems when running DS-Client using PostgreSQL database on Mac OS X with Apple Remote Desktop (ARD) installed.
Problem
ARD uses a built-in PosgreSQL that listens to port 5432. If the DS-Client's own PostgreSQL is also configured to listen to port 5432, the database fails to start because of this conflict. DS-Client may not work well with this built-in database due to version problems. Workaround The port conflict can be avoided by changing either port number to another value (other than 5432): 1. Edit the file postgresql.conf The file is under the folder defined by $PGDATA (usually /Library/ PostgreSQL8/). For ARD, this file is normally located in /var/db/RemoteManagement/RMDB/ rmdb.data/. 2. Uncomment the line "port = xxxx" and change it to something else. 3. Restart the service. When installing DS-Client, make sure to set the port number in the Database Login Screen to the correct value. If the software is already installed, you can check / change the Database Port field value in the configuration file. Changes will take effect after the service restarts.


Confidential.
Configuring DS-Client with Firewalls

Creation Date: March 8, 1999 Revision Date: March 21, 2008 Product: DS-Client
Summary
In order to operate, the DS-Client needs to establish a session with the DS-System on port 4401. If you have a firewall installed, you need to allow access to port 4401. In a standard firewall configuration there is an inside network interface (i.e. your LAN with the DS-Client) and an outside network interface (i.e. the Internet or WAN). The inside network is considered to be 'trusted', while the outside network is 'not trusted'. Connections with the DS-System are always initiated by the DS-Client. (A DS-System never initiates a connection to the DS-Client.) Therefore, you must allow port 4401 for the TCP protocol for the inside network interface. If you do not use DHCP for the DS-Client computer, you have additional flexibility: You can specify in the firewall that only the DS-Client computer's IP address can use port 4401. Depending on your firewall's configuration, you may even be able to set up a range of IP addresses.
Setup
Transparency 1. Most default firewall configurations provide transparency for users inside your firewall, but not for the users outside the wall. A DS-Client needs transparency for the connection with the DS-System. Therefore, you must either set transparency ON for the internal network interface (if it is not ON yet), or allow the connection on port 4401 to be transparent. This will depend on the type of firewall you are using. 2. There is no need for transparency on the outside network interface. Ports 1. The basic configuration required to setup your firewall for DS-Client activities (backup/ restore) is to allow port 4401 for the TCP protocol. Monitoring the DS-Client with the DS-User (GUI) from an outside connection: 1. You must allow port 4403 (TCP and UDP) in addition to port 4401. 2. If the DS-Client computer has more than one network interface (assuming the DS-Client computer is running Windows) and has default gateways on each interface, then you must modify the routing table manually to include the network from which the DS-User machine is connecting.
Grid DS-Client
The nodes in a Grid DS-Client communicate with one another on port 4410. All nodes must be in the same domain, therefore an external firewall is unlikely to be an issue. However, if a firewall is configured on any of the DS-Client nodes, make sure it does not prevent the DS-Client service from using port 4410. See Grid DS-Client on page 426.


Confidential.
Conclusion
To summarize - if you want full control of the DS-Client from the GUI, enable port 4401 (TCP) with transparency, as well as enabling port 4403 (TCP and UDP).
See Also
Ports used in Asigra Cloud Backup applications on page 405 Grid DS-Client on page 426


Confidential.
Windows XP Service Pack 2 changes that affect the Asigra Cloud Backup Product
Creation Date: September 16, 2004 Revision Date: August 29, 2011 Product: DS-Client
Summary
The following changes in Windows XP Service Pack 2 affect the Asigra Cloud Backup Product.
1. Firewall port conflict

In the README.TXT file shipped with the Release 5.9.5 there is a note about a port conflict between DS-Client and Internet Connection Firewall (ICF) on Windows XP:
In order to run DS-Client/DS-User on Windows XP, Internet Connection Firewall (ICF) should not be running. There is a port conflict with the firewall. We are working with Microsoft to resolve this conflict.
After applying Windows XP Service Pack 2, the Internet Connection Firewall service has been changed to Windows Firewall/Internet Connection Sharing (ICS) service and we did not encounter such conflicts anymore; therefore you can ignore the recommendation to disable the Internet Connection Firewall from README.TXT.
2. Firewall access rules

After applying the XP Service Pack 2, the Windows Firewall is automatically enabled with very restrictive access rules and DS-User may not discover DS-Client service. This is because the broadcast messages and incoming connections are blocked by the firewall. You will need to do one of the following configuration changes, depending on your environment: a. If you try to connect from a different computer, you need to add the TCP port 4403 in the Windows Firewalls Exceptions List. This works when trying to connect from the local computer as well. b. If you try to connect from the local computer, unless you add the firewall rule as described above, you need to specifically add either the loopback address (127.0.0.1) or the local IP address in the initialization file (Win32 DS-User) or menu (Java DSUser).


Confidential.
DS-Client Configuration File (Linux / Mac)

Creation Date: November 09, 2011 Revision Date: November 09, 2011 Product: DS-Client (Linux / Mac)
Summary
The DS-Client configuration file is <DS-Client HOME>/etc/dsclient.cfg. This file is created during installation. Though it can be edited manually, almost all parameters can be changed through the DS-User GUI. Some advanced users may encounter situations where they need edit the configuration parameters manually. WARNING: If your dsclient.cfg file is improperly configured, damaged, or missing, the DS-Client may not start.
DS-Client Configuration File Location and Format

The DS-Client configuration file (dsclient.cfg) is a text file that contains key + value pairs. The key is separated from the value by a colon (:). The key name can be followed by any number of spaces before the colon (:). Depending on the key, the value may or may not be case sensitive. It is safest to assume the value is case sensitive.
Using the asigraenc tool to encrypt password strings

Passwords must be stored in encrypted format in the configuration file. To encrypt a string manually, you may use the asigraenc tool provided in the DS-Client installation directory. This tool will generate an encrypted string for any input string. Note that the encrypted string may vary between different runs of asigraenc. There is no tool to decrypt such encrypted strings.


Confidential.
DS-Client Database (Maintenance)

Creation Date: July 24, 2007 Revision Date: May 20, 2008 Product: DS-Client
Summary
The DS-Client database is created by the DS-Client Installation. Ideally, you should not have to perform any further configurations after installation. This article covers some of the possible maintenance issues that might arise: Increasing Disk Space for DS-Client Database on page 412 DS-Client Database Version (compatibility checking) on page 413 Backing up the DS-Client Database on page 413
Increasing Disk Space for DS-Client Database

DS-Client is installed with notification levels to warn when the DS-Client Database free disk space is running low. You have the following options if the disk location of the DS-Client database is running out of space:
Windows DS-Client databases (MS SQL Server) Option 1: Free up disk space on the database drive. Move the DS-Client database to a bigger drive by using any method of backing up and restoring the DS-Client database. Make sure the MS SQL Server version on the target drive is compatible. The simplest way is to use the same version. MS SQL Server 2000 instances can be restored to MS SQL Server 2005 instances, but not the other way (i.e. 2005 to 2000). You must re-configure the DS-Client to point to the new database location. Modify the Database registry key on the DS-Client computer (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DS-Client\Parameters). Set the value to the UNC path to the new database instance (e.g. \\servername\instance_name\dsclient). Since this is an MS SQL Server specific task, no instructions are provided on how to perform these steps.
Option 2:
Create additional data files for the DS-Client databases on other disks (please refer to the MS SQL Server documentation). Option 3: NOTE: If the additional data files are located on another drive and those paths (NOT Recommended) do not exist when recovering the DS-Client database to another machine, then DS-Client will report errors and the database recovery will fail. Linux / Mac DS-Client databases (PostgreSQL Server) Option 1: Free up disk space on the database drive. Move the DS-Client database to a bigger drive by using any method of backing up and restoring the DS-Client database. Make sure the PostgreSQL Server version on the target drive is compatible. The simplest way is to use the same version. You must re-configure the DS-Client to point to the new database location. Modify the Database Host value in the DS-Clients configuration file (dsclient.cfg). Set the value to the IP address or UNC path of the server where the new database instance is located. Since this is an PostgreSQL Server specific task, no instructions are provided on how to perform these steps.
Option 2:


Confidential.
DS-Client Database Version (compatibility checking)

On running DS-Clients, you can check the database build number from DS-User > Help > About DS-User... > DS-Client Info. On startup, DS-Client checks if the database build number is compatible with the executable: Standalone DS-Client: For standalone DS-Clients (Windows / Linux / Mac), if the DS-Client database build number is not consistent with the DS-Client executable, the service is not allowed to start. If you recovered an old DSClient database that has a lower build number, you must run DS-Client setup to upgrade the DS-Client database (Windows) or re-run the latest installation (Linux / Mac). Grid DS-Client (Windows): For Grid DS-Clients, if a node has the same software version as the highest version in the Grid, the same database compatibility checking as for standalone DS-Clients applies. Otherwise, for any node that has a lower (software) version, the (database) compatibility checking will be skipped and an auto-upgrade will be issued immediately after the DS-Client service is started. If this auto-upgrade fails, the database compatibility checking will be done after the auto-upgrade.
Backing up the DS-Client Database

Since most of the DS-Client configuration settings (DS-User > Setup > Configuration) are stored in the DS-Client database, it is strongly recommended that it be regularly backed up. This is the default behavior for the DS-Client (set from DS-Client Configuration > Parameters Tab: Database options) during its Daily or Weekly Admin Processes. Note: If you ever recover an older DS-Client database, you must remember that any configuration changes that were made after the last database backup (if any) will not be saved. They must be manually re-applied.
See Also
DS-Client Database Installation Script on page 414 Recovering the DS-Client Database on page 718 Administrative Processes on page 491 Grid DS-Client (Windows DS-Clients) on page 70


Confidential.
DS-Client Database Installation Script

Creation Date: November 19, 2002 Revision Date: October 04, 2011 Product: DS-Client (with MS SQL Server database)
Integrity and Scalability Recommendations

It is recommended that the DS-Client database data files reside on a different physical device than the log files and if possible, on a different disk controller (unless using different, more sophisticated integrity strategies, like RAID subsystems, database replication, standby servers, etc). Microsofts recommendation is: "Do not place the transaction log file or files on the same physical disk with the other files and filegroups". This will maximize the performance due to parallel disk I/O. It will also improve the chances to recover the database to its state at the point of disk failure (in case that disk is damaged) The database installation script automatically detects the Default Data Directory and the Default Log Directory for the particular SQL Server (or instance) where it is installed. However, if the defaults are empty (this is likely), the installation script will create both the data and log files in the same location (i.e. the one where the "master" database resides). Before running the DS-Client installation to upgrade to a newer version, it is recommended to reset the Default Data Directory and the Default Log Directory to a different path on different physical drives as specified above. This can be done using SQL Enterprise Manager: select the SQL Server or Instance where the DS-Client database will be installed > Right-click > Properties > Database Settings tab.


Confidential.
DS-Client Database Migration (from MSDE to SQL Server 2005/2008 Express)

Creation Date: November 28, 2007 Revision Date: May 10, 2010 Product: DS-Client (Windows)
Introduction
The following options are available if you want to migrate a DS-Client database from MSDE to SQL Server 2005/2008 Express. MSDE is no longer supported as a database instance for DSClient installations. If you have an older version of DS-Client running with MSDE, you must migrate the database before you can upgrade the DS-Client. Note: SQL Server 2005/2008 Express has a 4GB database limit. Option 1 - Migrate by importing DB files to a new Instance on page 415 Option 2 - Migrate by upgrading the DB Instance on page 416
Option 1 - Migrate by importing DB files to a new Instance

1. Run a Daily Admin. This will backup the DS-Client databases to the DS-System. 2. Stop DS-Client Service. 3. Backup (dump) all three DS-Client databases (dsclient, dsdelta and dslanfiles). You can also use the dump files created by the Daily Admin in step 1 (if the DS-Client is configured to keep them in the DS-Client Buffer). 4. Obtain and install a SQL Server 2005/2008 Express instance (free download of the latest Service Pack). 5. Obtain Microsoft SQL 2005/2008 Management Studio Express (which can be downloaded from http://www.microsoft.com). Using the Studio Express tools, restore all three DS-Client databases (from the dump files in step 3) to the new SQL Server 2005/2008 Express instance. 6. Reconfigure the Registry Keys on the DS-Client computer, in order to use the new SQL 2005/2008 Express instance (where you have just restored the DS-Client databases). In Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DS-Client: Provide the path for the database:
Parameters\Database=\\MACHINE_NAME\INSTANCE_NAME\dsclient
Note: -
To view the instance names that are running, type osql L from the Command Prompt. This will list all the running database instances.
Change the Dependency for DS-Client service by modifying the value DependOnService from MSSQL$MSDE_INSTANCE to MSSQL$SQLEXPRESS. 7. Start DS-Client Service. 8. Test the connection with the DS-System by running a Daily Admin. Verify there are no errors in the Activity Log.


Confidential.
Option 2 - Migrate by upgrading the DB Instance

1. Run a Daily Admin. This will backup the DS-Client databases to the DS-System. 2. Stop DS-Client Service. 3. Obtain a SQL Server 2005/2008 Express installation from Microsoft (free download of the latest Service Pack). 4. Running the SQL Server 2005/2008 Express installation over the MSDE instance is NOT sufficient to perform a successful upgrade. You must follow the instructions for installation using the skuupgrade parameter that can be found at:
https://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade
5. After the upgrade is successful, start the SQL Server 2005/2008 Express instance. 6. Start the DS-Client service. 7. Test the connection with the DS-System by running a Daily Admin. Verify there are no errors in the Activity Log.


Confidential.
DS-Client Database Migration (from SQL Server Express version to SQL Server FULL version)
Creation Date: November 28, 2007 Revision Date: September 20, 2012 Product: DS-Client (Windows)
Introduction
Note: This article uses Microsoft SQL Server 2005 as an example, however, this procedure is also applicable for higher versions (i.e. SQL Server 2008, 2008 R2, 2012, and up).
The following options are available if you want to migrate a DS-Client database from SQL Server 2005 Express to Microsoft SQL Server 2005. You need to migrate if you reach the 4GB limit of the SQL Server 2005 Express database, or if you plan a significant increase to the number of files protected with this DS-Client. Option 1 - Migrate by importing DB files to a new Instance on page 417 Option 2 - Migrate by upgrading the DB Instance on page 418
Option 1 - Migrate by importing DB files to a new Instance

1. Run a Daily Admin. This will backup the DS-Client databases to the DS-System. 2. Stop DS-Client Service. 3. Backup (dump) all three DS-Client databases (dsclient, dsdelta and dslanfiles). You can also use the dump files created by the Daily Admin in step 1 (if the DS-Client is configured to keep them in the DS-Client Buffer). 4. Install a new MS SQL Server 2005 instance (separate purchase required). 5. Obtain MS SQL Server 2005 Management Studio Express (which can be downloaded from http://www.microsoft.com or which comes with the MS SQL Server 2005 you purchased). Using the Studio Express tools, restore all three DS-Client databases (from the dump files in step 3) to the new MS SQL Server 2005 instance. 6. Reconfigure the Registry Keys on the DS-Client computer, in order to use the new MS SQL Server 2005 instance (where you have just restored the DS-Client databases). In Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DS-Client: Provide the path for the database:
Parameters\Database=\\MACHINE_NAME\INSTANCE_NAME\dsclient
Change the Dependency for DS-Client service by modifying the value DependOnService from MSSQL$SQLEXPRESS to MSSQLServer. 7. Start DS-Client Service. 8. Test the connection with the DS-System by running a Daily Admin. Verify there are no errors in the Activity Log.


Confidential.
Option 2 - Migrate by upgrading the DB Instance

1. 2. 3. 4. Run a Daily Admin. This will backup the DS-Client databases to the DS-System. Stop DS-Client Service. Obtain a new MS SQL Server 2005 instance (separate purchase required). Running the MS SQL Server 2005 installation over the SQL Server 2005 Express instance is NOT sufficient to perform a successful upgrade. You must follow the instructions for installation using the skuupgrade parameter that can be found at:
https://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade
5. After the upgrade is successful, start the MS SQL Server 2005 instance. 6. Start DS-Client service. 7. Test the connection with the DS-System by running a Daily Admin. Verify there are no errors in the Activity Log.


Confidential.
DS-Client Database Size (PostgreSQL 8.2.4 and below)

Creation Date: June 27, 2008 Revision Date: June 27, 2008 Product: DS-Client (Linux)
Summary
Some customers have run into problems where the DS-Client database (PostgreSQL 8.2.4 and below) grows to a significant size (40-100GB or more). This article describes why this can happen, and some workarounds. On Linux machines, the PostgreSQL DS-Client database can grow to a considerable size, despite the fact that DS-Client automatically vacuums its database during Daily Admin or Weekly Admin.
Details
During normal PostgreSQL operation, an UPDATE or DELETE of a row does not immediately remove the old version of the row, because those are still potentially visible to other transactions. Depending on the frequency of these transactions, a significant amount of free space can accumulate causing the database size to grow. PostgreSQL has a VACUUM feature that reclaims this free space for reuse by new rows. VACUUM is run during a DS-Client Daily Admin or Weekly Admin. However, it only marks those free space blocks for future reuse. Unused space is not reclaimed and the database file size remains the same. This means if the VACUUM is not run often, the database may grow significantly (especially if there is a large amount of UPDATE or DELETE activities). Recommendations: Perform regular, scheduled Daily Admin and Weekly Admin on DS-Client database. If you find there is unusual growth in the database size, try the procedures in the Workaround to reduce its size. See Workaround to reduce DB size on page 420.


Confidential.
Workaround to reduce DB size

Manually reclaim the disk space by following this procedure: Backup the DS-Client database Drop DS-Client database Create a new DS-Client database Restore from the dump
Note:
It is very important that you use the same version of PostgreSQL, pg_dump (command) and pg_restore (command). For example, if the PostgreSQL version is 8.2.4, then the versions of pg_dump and pg_restore must be 8.2.4.
1. Stop DS-Client daemon:

/etc/init.d/dsclient stop
2. Backup DS-Client database:

pg_dump U username h hostname F c f <path to dsclient.dmp> dsclient
3. Make sure the command in step 2 is performed successfully. 4. Go to the PostgreSQL prompt: Drop the existing DS-Client database:
psql > DROP DATABASE dsclient;
Create a new dsclient database:

psql > CREATE DATABASE dsclient template=template0 encoding=unicode;
5. Exit the PostgreSQL prompt. 6. Restore the dump (created in step 2) to the newly created DS-Client database:
pg_restore U username h hostname F c d dsclient <path to dsclient.dmp>
7. Start DS-Client daemon again:

/etc/init.d/dsclient start
PostgreSQL 8.3 and higher

Starting from PostgreSQL 8.3, an Auto-Vacuum daemon monitors table activity and performs VACUUMs whenever necessary. This eliminates the need for administrators to worry about disk space recovery in all but the most unusual cases.


Confidential.
DS-Client Database (Automatic Expansion)

Creation Date: August 29, 2008 Revision Date: September 20, 2012 Product: DS-Client (Windows)
Note:
This feature only works for Windows standalone DS-Clients. It does not work with Windows Grid DS-Client.
Summary
The free Microsoft SQL Server Express databases contain the following built-in limitations:
Microsoft SQL Server 2005 Express (For DS-Client database) Microsoft SQL Server 2008 Express (For DS-Client database) Microsoft SQL Server 2008 R2 Express (For DS-Client database) Microsoft SQL Server 2012 Express (For DS-Client database) SQL Server 2005 Express has a 4GB limit for the databases. SQL Server 2005 Express will use a maximum of 1 CPU, and can use up to 1GB of RAM (even if the computer has more). SQL Server 2008 Express has a 4GB limit for the databases. SQL Server 2008 Express will use a maximum of 1 CPU, and can use up to 1GB of RAM (even if the computer has more). SQL Server 2008 R2 Express has a 10GB limit for the databases. SQL Server 2008 R2 Express will use a maximum of 1 CPU, and can use up to 1GB of RAM (even if the computer has more). SQL Server 2012 Express has a 10GB limit for the databases. SQL Server 2012 Express will use a maximum of 1 CPU, and can use up to 1GB of RAM (even if the computer has more).
If you reach the GB size limit of either database type, you have two options: upgrade to the full MS SQL Server (which requires you to purchase the license), or enable the DS-Client database Automatic Expansion feature
There is no workaround to the CPU and RAM limitations. If you find you need more processing capability, you must purchase the full licensed MS SQL Server.
Details
The DS-Client database Automatic Expansion feature is a workaround to the maximum database size limitation in the free Microsoft SQL Server Express databases. If activated, when an Administrative Process (Local, Daily, Weekly) detects the DS-Client database is nearing the maximum capacity, it will automatically create a new database and move some of the backup set tables to that new location. Expansion can continue forever, meaning this solution removes the 4GB (or 10GB) limitation of Express. In practice, the performance will be affected as the database is expanded, given the CPU and RAM limitations. To activate the DS-Client database Automatic Expansion feature: 1. DS-User > Setup Menu > Configuration > Parameters Tab. 2. In the DS-Client Configuration Parameters Tab screen, check the Automatically Expand DS-Client Database box. 3. Click OK or Apply. To configure the parameters for the DS-Client database Automatic Expansion feature:

Confidential.
1. DS-User > Setup Menu > Configuration > Advanced Tab. 2. In the DS-Client Configuration Advance Tab screen, select the Miscellaneous category. 3. From the Parameter drop down list, you can make the following configurations:
This parameter (in percent) sets the level at which the Daily Admin or Weekly Admin will automatically expand the DS-Client database to create a new, sequentially named expand<nnnn> database. The percentage is calculated against the maximum allowed size for an individual database (4GB or 10GB). range 0 to 100, default is 70 (percent) If the current amount of space used in an expand<nnnn> database is less than this parameter (in percent), Daily Admin and Weekly Admin can move backup set tables into that database. range 0 to 100, default is 40
DBHighWaterMark
DBLowWaterMark
4. Click OK or Apply to save the changes. NOTES: 1. HighWaterMark is the trigger that the Administrative Process uses to determine if backup set(s) need to be moved out of a database. 2. LowWaterMark is used to balance the distribution of backup sets among the expanded databases. During an Administrative Process (Local / Daily / Weekly), if backup set(s) need to be moved and all databases are past the LowWaterMark, a new expanded database will be created. 3. What gets moved: The largest backup set is moved first (unless it would fill the new database higher than the DBHighWaterMark). Then the next largest backup set is moved and so forth, until the database fill level falls under the DBHighWaterMark (e.g. less than 70% for default settings). Note: If a single backup sets tables are larger than the 4GB (or 10GB) limit, it cannot be moved. In this case you will have to migrate to the full, licensed MS SQL Server version. Only an entire backup set can be moved (it must all reside within the same expand<nnnn> database). All tables for a single backup set from both the dsclient and dsdelta databases are moved. 4. When compared with using a single DS-Client database on a full (purchased) MS SQL Server, the performance will be slower. 5. How a DS-Client with expanded-databases would appear from SQL DB Manager:
DSCXXXX00002_dsclient DSCXXXX00002_dsdelta DSCXXXX00002_dslanfiles DSCXXXX00002_expand0001 DSCXXXX00002_expand0002
Example:This DS-Client (DS-Client #DSCXXXX00002) has two expanded databases. Expanded databases contain both dsclient and dsdelta tables.
See Also
Administrative Processes on page 491


Confidential.


Confidential.
DS-Client Service Account

Creation Date: May 3, 1997 Revision Date: September 22, 2009 Product: DS-Client (Windows)
Summary
The DS-Client software runs as a service on a Windows computer and requires a user account in order to logon (to allow access to network resources). This account must be provided during the DS-Client installation process (make sure that this user account exists on the target Windows machine). Before starting the DS-Client installation program, you must log on to the DS-Client computer as the administrator or other user with equivalent permissions.
Service Account Rights

The Service Account requires some advanced user rights. Therefore, the DS-Client installation program grants the following rights to the DS-Client Service Account: "Act as part of the operating system". "Logon as a service". "Backup files and directories". "Restore files and directories".
How the DS-Client uses the Service Account

The DS-Client installation/configuration programs store the username and password for the DS-Client Service Account in the Registry (in encrypted form). The DS-Client service uses this user account for logon impersonation during backup/restore sessions that are not configured with a user account that has permissions to perform logon impersonation (e.g. connection to a non-Windows computer). This (logon impersonation) allows the DS-Client to perform simultaneous backup/restore operations from/to the same server with different user credentials.
Changing and Maintaining Service Account

In order to provide uninterrupted service, make sure that the Service Account is not disabled, that the "Password never expires" option is set, and that no expiry date is set for this account. If the DS-Client Service Account or password must be changed, reconfigure with Start > All Programs > Asigra DS-Client > DS-Client Setup. Do not reconfigure through Control Panel > Services > Startup, because the DS-Client service may not function properly. If the service account is changed, re-create the Mail Profile used for DS-Client notifications.


Confidential.
DS-Client under heavy processing loads

Creation Date: January 9, 2003 Revision Date: May 10, 2010 Product: DS-Client (Windows)
Summary
Error messages may occur on DS-Client in heavy processing load situations. If lots of activities (especially Backup activities) are running on a DS-Client at the same time, DSClient could report errors "Insufficient System Resources Exist to Complete the Requested Service" (Error code: 1450) even if the system has plenty of RAM and disk space available.
Details
For DS-Client, if the System Resources problems occur, you can try with less activities running at the same time or reduce the threads settings for DS-Client in the DS-Client Advanced Configurations (DS-User > Setup Menu > Configuration: Advanced Tab): "MaxThreads" parameter for Backup activities "MaxRestoreThreads" parameter for Restore activities.


Confidential.
Grid DS-Client
Creation Date: February 08, 2008 Revision Date: September 20, 2012 Product: DS-Client (Windows) This article provides an overview of the Grid DS-Client. 1. Introduction & Overview on page 426 2. Operating Systems Supported on page 427 3. Hardware and Software Setup on page 428 4. Connectivity on page 430 5. Grid DS-Client Setup on page 430 6. Specific GUIs for Grid DS-Client on page 431 7. Upgrading, Recovering DS-Client DB, and Version control on page 431 8. Configuring the Grid DS-Client Nodes (node level configuration) on page 432 9. Frequently Asked Questions (FAQ) on page 433
1. Introduction & Overview

Data storage protection is a fast growing market. More and more data needs to be backed up and the backup jobs / sets are getting bigger and bigger. Meanwhile, backup time windows are shrinking and RTO (recovery time objective) is vital. This means multiple DS-Clients for a single LAN are becoming commonplace. Automatic balancing between multiple DS-Clients for higher performance becomes a new challenge. High availability becomes more important. The Agentless Grid DS-Client is the Asigra Cloud Backup solution to achieve these requirements and to meet customer Service Level Agreements.


Confidential.
1. The Grid DS-Client is designed to deliver better performance scalability of the DS-Client and to increase the availability of the Backup Service. It is designed so that the DS-Client can survive failures of some of its nodes without interrupting the backup service. 2. Configuring the Grid DS-Client means that several DS-Clients will work together to provide backup and restore services as if they are a single DS-Client (from the DS-System perspective). Any of the nodes in the Grid DS-Client is able to provide the same service (backup, restore, delete, synchronization, admin, etc.) as long as the nodes are configured properly (see section 3. Hardware and Software Setup on page 428). 3. All nodes in a Grid DS-Client share the same DS-Client database. They also share the same Account Number, DS-Client number and private/account encryption keys. 4. Each node in the Grid DS-Client has a separate network connection to DS-System. 5. One of the nodes will be selected as the Main Node to perform common internal tasks and to synchronize and balance activities. It also interacts with DS-User GUI. Any other node is called a Leaf Node. Leaf nodes will perform tasks assigned by the Main node. 6. Activities are controlled by the Main Node and assigned to all nodes in a balanced way. The balance is measured by the load (determined by the activities assigned, compared to the MaxSession parameter configured for that node) and CPU usage. 7. If the Main Node goes down, the other (leaf) nodes will continue their current tasks. In the meantime, a new Main Node will be elected. 8. Even if only one node is alive and all other nodes are down because of failures or other reasons, the Grid DS-Client will still be available and will continue providing the same backup services.
2. Operating Systems Supported

Grid DS-Client can be installed on the following platforms. It is strongly recommended to run all nodes on the same platform, or at the very minimum the same architecture (32-bit only or 64-bit only).
Platform Windows XP x86 (32-bit) Windows XP x64 (64-bit) Windows 2003 x86 (32-bit) or x64 (64-bit) Version Professional SP3, or Media Center SP3 Professional SP2, or Media Center SP2 Standard SP2/R2 SP2, or Enterprise SP2/R2 SP2, or SBS SP2, or Data Center SP2 (64-bit only) Ultimate SP2, or Enterprise SP2, or Home Basic SP2, or Business SP2, or Home Premium SP2 Standard SP2, or Enterprise SP2 Standard SP2/R2 SP1, or Enterprise SP2/R2 SP1, or SBS SP2, or Data Center SP2/R2 SP1
Windows VISTA x86 (32-bit) or x64 (64-bit) Windows 2008 x86 (32-bit) Windows 2008 x64 (64-bit)


Confidential.
Windows SBS 2011 x64 (64-bit) Windows 7 x86 (32-bit) or x64 (64-bit) Windows 2012 x64 (64-bit) Windows 8 x86 (32-bit) or x64 (64-bit)
Standard Ultimate SP1, or Professional SP1, or Enterprise SP1 Essentials, or Standard, or Datacenter Pro, or Enterprise
3. Hardware and Software Setup

NOTE: For step-by-step instructions, refer to the Windows DS-Client Installation Guide (filename: installation_dsclient.pdf) section Grid DS-Client Installation. 1. In order for each node to be able to provide the same backup services, the nodes must have the same access to the source data. This means that the nodes must be configured the same way with regards to network credentials: If one node with a specific network credential can access the source data, all other nodes must also be able to access that source data with that same network credential. Moreover, if one node has software installed to access a specific data source type (e.g. Oracle Client to backup Oracle Server, iSeries Access for Windows to backup System i Servers, etc.) all other nodes must also be configured with the same capability. 2. Each of the nodes must be able to access the DS-Client database using a trusted connection. This means that a central database must be configured for the Grid DS-Client to access. ASIGRA recommends that the database be clustered in order to avoid single point of failures. 3. All nodes (including the DS-Client database machine) must be in the same domain to achieve the above two requirements. 4. Grid DS-Client is supported on VMware. Multiple nodes can be configured to run on VM on the same physical machine. Since all these nodes share the same CPU/RAM on the physical machine, if some nodes are idle or down, other nodes will get more CPU/RAM resources and will become more powerful. 5. Database configuration is the same as for stand-alone DS-Clients: The database configuration is kept in the Registry of each nodes machine. The database service account must have enough credentials to access the DS-Client buffer on each of the Grids nodes (in order to perform database dump during Daily/Weekly Admin). Proper delegation must also be configured so that bulk insert is possible from each nodes DS-Client buffer. 6. Each nodes service account must have enough credentials to remotely start/stop the DS-Client service on all other nodes. This is required for the Auto upgrade feature. In addition, perform the following: On Windows 2003 / XP / VISTA: Go to the Windows Control Panel > Administrative Tools > Local Security Settings > Local Policies > Security Options > Network Access: Sharing and security model for local accounts. Set its value to Classic - local users authenticate as themselves.

Confidential.
On Windows VISTA: Go to the Windows Control Panel > Network and Internet > Network and Sharing Center: the option File Sharing should be set to ON. On Windows XP / VISTA, configure the firewall setting: For XP, make sure File and printer sharing is open. For VISTA, make sure File and printer sharing and Remote Administration are in the exception list. On Windows VISTA / 2008 / 7: Verify that UAC (User Account Control) is turned off. On all Windows platforms: Check if the firewall allows remote control of the DS-Client service between the nodes with the following commands:
sc \\[other-node] start|stop ds-client taskkill /S \\[other-node] /IM dsclient.exe
7.
8.
9.
10.
11.
Replace [other-node] with the IP address or machine name of the target node. If these commands fail, you have a network or configuration problem that you must resolve before you can continue. All nodes (including the DS-Client database machine) must be synchronized to the same time server and configured to the same time zone to ensure time-consistency. Otherwise, confusing (or even failure) scenarios may occur regarding logs and backups. To configure a Grid DS-Client, you must first install the DS-Client software on all nodes (pointing to the same database and using the same encryption keys, etc.) WITHOUT starting the DS-Client service. After completing all installations, run DS-Client setup (DSConfig.exe) on any node to configure the nodes that will join together as the Grid DS-Client. See 8. Configuring the Grid DS-Client Nodes (node level configuration) on page 432. The machine name (NetBIOS name) and internal/external IP are needed in the Grid DS-Client configuration for each node. The internal IP is used for communication between nodes in a Grid DS-Client. The external IP is used by the DS-System to identify if connection is allowed for that DS-Client. DS-User can use either internal or external IP, depending where the DS-User is located (LAN/WAN). If a stand-alone DS-Client is upgraded to a Grid DS-Client, the original DS-Client must be the first node in the Grid DS-Client to be configured using DS-Client setup (DSConfig.exe). To downgrade a Grid DS-Client to a stand-alone DS-Client, you can run DS-Client setup on the node that will become stand-alone, and remove all nodes from the Grid DS-Client configuration. Alternatively, you can start DS-Client setup on any of the other nodes. You must leave the node that will become the stand-alone DS-Client in the Grid DS-Client configuration, and all other nodes must be removed from the list. If you need to re-configure (add new nodes or remove existing nodes) a Grid DS-Client (including upgrade from stand-alone and downgrade to stand-alone): You must first stop the DS-Client service on all nodes. After that, start DS-Client setup to configure the Grid DS-Client. After the Grid DS-Client configuration is done, modify the connection on DS-System side accordingly for this (Grid) DS-Client. Un-register this (Grid) DS-Client on DS-System side. Start the DS-Client service on the desired nodes, and register to DS-System.
Note:


Confidential.
Any nodes that were not started at the time you re-registered to DS-System will send their hardware registration information to DS-System later, on their next connection to DS-System. 12. If any nodes hardware information is changed, or new nodes are added into the Grid DS-Client (including upgrading from stand-alone), you must re-register to DS-System. For more details, see: Re-register the DS-Client with the DS-System on page 33 13. Port 4410 is used for the communication between nodes in a Grid DS-Client. This port must be opened on all nodes of the Grid DS-Client. 14. Since the Grid DS-Client configurations are stored in the DS-Client database, whenever you change the Grid configuration, you should backup the DS-Client database with Daily Admin or Weekly Admin as soon as possible. Otherwise, if the database becomes corrupted or suffers some type of failure, you will have to reconfigure after recovering the DS-Client database.
4. Connectivity
1. The DS-User will only be able to connect to the Main Node. Since the Main Node is variable, the DS-User must be initialized with all the IP addresses of all the nodes of the Grid DS-Client. 2. Each node will connect to DS-System in a separate network connection, using its own external IP. 3. Each node must be able to connect to all source data to be protected. 4. A High-speed network connection (at least 1 Gigabit per second is recommended) is necessary between Grid DS-Client and the data source to improve the overall backup service performance.
5. Grid DS-Client Setup

NOTE: For step-by-step instructions, refer to the Windows DS-Client Installation Guide (filename: installation_dsclient.pdf) section Grid DS-Client Installation. The DS-Client Setup (default path "C:\Program Files\CloudBackup\DS-Client\DSConfig.exe") has an optional screen to Enter Grid DS-Client information. The Grid DS-Client section is displayed when the user selects Configure Grid DS-Client or if DS-Client Setup is running on an existing


Confidential.
Grid DS-Client.
You must configure at least two nodes to make a Grid DS-Client. If you configure only one node (or none), this DS-Client will be a standalone DSClient. User input and modification of nodes is controlled by the Add, Update and Delete buttons.
6. Specific GUIs for Grid DS-Client

In general, the DS-User functionalities are the same as for the stand-alone DS-Client, with a few additional functionalities for managing the Grid DS-Client. For a description, see: Grid DS-Client (Windows DS-Clients) on page 70
7. Upgrading, Recovering DS-Client DB, and Version control

NOTE: For step-by-step instructions, refer to the Windows DS-Client Installation Guide (filename: installation_dsclient.pdf) section Grid DS-Client Installation. Manual upgrade To manually upgrade a Grid DS-Client to a new version: 1. Stop all DS-Client services on all nodes in the Grid DS-Client. 2. Run the Service Pack / Release / Hot Fix package on each node, using the same steps as for stand-alone DS-Client. 3. Start all the DS-Client services that are part of the Grid DS-Client. Auto upgrade Grid DS-Clients can auto-upgrade if their DS-System is configured to allow it. 1. The first node that downloads a higher version auto-upgrade package from DS-System will stop the DS-Client service on all other nodes. After the first node has finished upgrading, it will restart the DS-Client services on all other nodes. Once those

Confidential.
nodes restart, they will connect to DS-System and download the auto-upgrade package (this time auto-upgrade will only stop the DS-Client service on the local node). 2. Auto-upgrade will be triggered if: When starting DS-Client service, at least one other node is found to have a higher version (only the node performing upgrading will be stopped for upgrading and restarted automatically). When connecting to DS-System, a higher version DS-Client auto-upgrade package is available. Recover DS-Client Database 1. The Recover DS-Client database process can be performed on any node (DS-User > Setup Menu > System Activities: Repair). Since the DS-Client Database Recovery needs exclusive access to the database, all nodes are required to stop for recovery. After the node that performed recovery successfully downloads the database dump, it will notify all other nodes to stop. Once it detects all other nodes have stopped, it will notify the user to restart the DS-Client service on that node. Before that node has successfully recovered the DS-Client database (database load completed), other nodes will not be able to start. 2. If an old DS-Client database is recovered and is not compatible with the current DS-Client executable, you must run the latest DS-Client installation to upgrade the DS-Client database. Otherwise, the nodes will not be allowed to start. 3. For more information on this process, see the Knowledge Base article: Recovering the DS-Client Database on page 718. Version control If a nodes version is lower than the highest version in the Grid DS-Client, it will perform auto-upgrade right after starting the DS-Client service. If auto-upgrade is not allowed or fails to upgrade, a version compatibility check will be performed and nodes that are not compatible will not be allowed to start.
8. Configuring the Grid DS-Client Nodes (node level configuration)

The default configuration (created by installing and running DS-Client Setup) is sufficient to run a Grid DS-Client. Advanced users may wish to configure individual nodes for optimum performance. For different nodes in the same Grid, some DS-Client parameters can be different. These local parameters are flagged Local Setting. All local parameters must be configured from the DSClient configuration - Advanced Tab (see: DS-Client Advanced Configurations on page 47). Every Local Setting parameter has a corresponding Global Setting that is the default value for each node. To switch, a user must check the Use global setting. If unchecked, the Value field activates and the user can give each node a different value. A special parameter is DSCBuffer. This is same as DS-Client Buffer in the DS-Client Configuration - Parameters Tab. However, it can be set to a different value for each DS-Client node. This is because each DS-Client node can have its own buffer.


Confidential.
9. Frequently Asked Questions (FAQ)

Question How is the Main node elected? 1. Answer The first node that detects there is no existing Main node will become the Main node. This means the first node that is started will most probably become the Main node. Question How is a Leaf crash handled by the Grid DS-Client? Answer In case a Leaf node crashes (for example because of hardware failure), all activities on that node will be interrupted. However, if there are still some nodes active, the rest of the nodes will continue functioning and the rest of the activities running on other nodes continue to run. All activities that are run2. ning on the node that crashed will be considered to have failed. For interrupted backup sessions, the files that have already been completely sent to DS-System will be protected, while the others will be backed up in the next backup session. Retries for scheduled activities keep the same behavior as on a stand-alone DS-Client: it will retry in case the connection to DS-System is lost, but not if the activity is stopped on the DS-Client side. Question How is a Main node crash handled? Answer 3. In case of the Main node is down, the internal tasks (scheduling, etc.) will be temporarily stopped. However, all activities that are running on the Leaf nodes will continue. In the meantime, a new Main node will be elected from among the remaining nodes. This will occur in a short period (usually a few seconds, but sometimes it may take a few minutes). Question How many nodes can be configured in a Grid DS-Client? Answer 4. The minimum number of nodes in a Grid DS-Client is logically two (2). If there is only one node configured, it becomes stand-alone DS-Client. There is no actual maximum node limit. However, a larger number of nodes means the DS-Client database server must have the CPU and RAM capabilities to support the nodes. Question How do you add a new node to the Grid DS-Client? Answer To add a new node, you must install the DS-Client software pointing to the same database, using the 5. same registration info (Account number and DS-Client number, etc.), and same encryption key configuration. After that, you must stop all nodes in the Grid DS-Client and re-configure the Grid DS-Client via DSConfig.exe. Then you must start the nodes and re-register with the DS-System. Removing an existing node from a Grid DS-Client is similar, you just need to stop the Grid, re-configure, and re-register. Question How do you downgrade a Grid DS-Client to a stand-alone DS-Client? 6. Answer See #10 in section 3. Hardware and Software Setup on page 428.
See Also
Grid DS-Client (Windows DS-Clients) on page 70


Confidential.
DS-MLR Installation & Setup

Creation Date: August 13, 2004 Revision Date: August 28, 2012 Product: DS-Client (Windows) with DS-MLR Service (DS-Recovery Tools)
Summary
NOTE: The DS-MLR Service is bundled with the DS-Recovery Tools installation.
This article covers DS-MLR (Message Level Restore) installation and setup issues: DS-MLR Server Installation Support Matrix on page 434 : DS-MLR Service Account requirements on page 435
DS-MLR Server Installation Support Matrix

This Matrix shows the platforms where DS-MLR can be installed:
Microsoft Exchange Server Version Exchange 2010 Exchange Enterprise 2007 Exchange Enterprise 2003 Exchange Enterprise 2003 Cluster Platform for Exchange Server Windows Server 2008/2008 R2 (64-bit ONLY) Windows Server 2003/2008 (64-bit ONLY) Windows Server 2003 Windows Server 2003 in Single quorum device server clusters Windows Server 2000 in Single quorum device server clusters Windows 2000 Advanced Server Windows Server 2003 Platform for Outlook Windows 2000 Advanced Server Windows 2003 Server Windows 2003 Server Windows 2003 Server in Single quorum device server clusters Windows 2003 Server (32-bit/64-bit) Support status Active Support Active Support Active Support Active Support Passive Support Active Support Active Support Support status Active Support Active Support Active Support Active Support Active Support
Exchange Enterprise 2000 Microsoft Outlook Version Outlook 2000
Outlook 2003
Windows 2003 Server (32-bit) Server in Single quorum device server clusters Active Support Windows Vista Outlook 2007 Windows 2008 (32-bit/64-bit) Windows 2008 R2 (64-bit) Windows 7 (32-bit/64-bit) Windows 8 (32-bit/64-bit) Windows Vista Windows 2008 (32-bit/64-bit) Outlook 2010 Windows 2008 R2 (64-bit) Windows 7 (32-bit/64-bit) Windows 8 (32-bit/64-bit) Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support


Confidential.

Lotus Version Platform for Lotus Windows XP Professional Lotus Notes 7.0 & 8 & 8.5 Windows 2000 Advanced Server Windows Vista Windows 2000 Advanced Server Lotus Domino Server 7.0 & 8 & 8.5 Windows 2003 Server Windows 2008 Server GroupWise Version Platform for GroupWise Client Windows 2000 Advanced Server + Novell Client 4.9.1 SP3 GroupWise Client 6.5.4 & 7 Windows 2000 Professional + Novell Client 4.9.1 SP3 Windows 2003 Server + Novell Client 4.9.1 SP3 GroupWise Client 8 Windows XP + Novell Client 4.9.1 SP5 Windows 2003 Server / R2 + Novell Client 4.9.1 SP5 Support status Active Support Active Support Active Support Active Support Active Support Active Support Support status Active Support Passive Support Active Support Active Support Active Support
Matrix Legend: Active Support: DS-Client supports backup / restore on these target objects. Passive Support: Backup / restore tests have not been performed on these platforms, but there should not be any technical limitations. Not Supported: Backup / restore is not supported. No Vendor Support: Vendor does not support installation of target object on these platforms.
DS-MLR Service Account requirements

This section is reproduced from the DS-Recovery Tools installation guide. It describes the requirements for the DS-MLR Service Account (the Windows account used by the DS-MLR service). NOTE: If you encounter any backup or restore problems when using DS-MLR, it is most likely due to problems with the DS-MLR Service Account configuration. GroupWise: The DS-MLR Service Account must be a local administrator. Lotus Notes / Domino Server: The DS-MLR Service Account must be a local administrator. MS Outlook: The DS-MLR Service Account must be a local administrator. MS Exchange: The DS-MLR Service Account determines the rights to backup the MS Exchange Servers E-Mails. Even if the service is run by a user from the local Administrators group, that user may not have enough rights to backup all the MS Exchange Servers E-Mails. The following table shows the User Scenarios for backup / restore, depending on the permissions of the DS-MLR Service Account:
Service Account is a User Scenarios member of:


Confidential.
Domain Admins Domain User Local Administrator
DS-MLR service account must be a member of Domain Admins and local/Builtin Administrators groups. This scenario is simple, but some network security policies may not allow use of the Domain Admins group. DS-MLR service account must be a member of local Administrators group. DS-MLR service account must be a member of Domain Builtin Backup Operator or Administrators group. DS-MLR service account must be delegated as Exchange Full Administrator. This scenario is a little complicated, but does not require use of the Domain Admins group. This option is more flexible from a network security standpoint. However, when starting up, DS-MLR may fail to grant the "Receive As" right for some or all mailboxes to the service account. Therefore, you must manually add the "Receive As" privilege to the Windows User account for the backup set (Backup Set Properties > Connection Tab).
Microsoft Exchange Contacts and Distribution Lists: Contacts and Distribution Lists may need to be handled with different APIs in order to successfully backup Microsoft Exchange Servers.
Backup using MAPI API Because the Distribution Lists and Contacts are Outlook-based attributes, the DS-MLR can use MAPI to perform backups. MAPI has the following limitations based on the DS-MLR service account: In order to logon to another users mailbox through MAPI, the service account needs the receive as right, and the right to create a temporary profile. DS-MLR can grant the receive as right if the DS-MLR service account is either a Domain Admin or an Exchange Full Admin. Backup using Exchange CDO API (up to Microsoft Exchange 2007) If DS-MLR uses Exchange CDO to backup all items, some Outlook attributes (like the members list of the Distribution List) cannot be read. With CDO, DS-MLR has the following limitations: The restored Distribution Lists are empty. The restored Contacts cannot be seen in Outlook Address Book.
1. Both CDO and MAPI APIs are kept in DS-MLR. The default is to try using MAPI API. 2. If DS-MLR fails to grant receive as right to its DS-MLR service account, then DSMLR will use the CDO API. 3. If DS-MLR fails to use MAPI, then DS-MLR will use the CDO API. 4. When using the CDO API, DS-MLR will not backup the Distribution List. Important notes about MAPI and CDO for newer Microsoft Exchange Server releases: From Microsoft Exchange 2007, the MAPI (Messaging Application Programming Interface) client was removed from the installation. From Microsoft Exchange 2010, the CDO client is no longer supported. Only the MAPI client will work, even though it is not included with the default Exchange 2010 installation. The MAPI client is still required by DS-MLR and must be downloaded and installed separately from Microsoft (free download). For Exchange 2007 / 2010, you must download it separately from Microsoft and install it on the DSMLR machine / Exchange server.


Confidential.
See Also
E-Mail Messages (DS-Recovery Tools) on page 141 Backup / Restore of E-Mails (using DS-MLR) on page 599


Confidential.
Setting up DS-Client Notifications

Creation Date: April 28, 1997 Revision Date: March 21, 2008 Product: DS-Client (Windows)
Summary
DS-Client can be configured to send E-Mail / pager notifications in the event of a critical backup failure, allowing an Administrator to react instantly to such failures. In addition, DS-Client can regularly mail out a summary of backup activities (during Admin processes). DS-Client notifications can be: SMTP MAPI
Messaging Service Setup

Restrictions The delivery of notifications is provided by 3rd-party mail clients installed on the DS-Client computer and registered with the Windows Messaging Subsystem (MAPI). By design, MAPI and most mail clients cause their client applications to pop up dialog boxes to interact with a user. Because DS-Client is unattended service software, it would hang if it displays a dialog. Therefore, DS-Client will only use compatible mail clients known to never display a user interface. Such mail clients are listed in the order of preference in the Registry value [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DS-Client\Para meters] MailClientsSupported The entry for Microsoft Outlook is added to this list by DS-Client Setup. DS-Client will use the first MailClientsSupported entry installed on the computer, i.e. listed under [HKEY_LOCAL_MACHINE\Software\Clients\Mail] Note that DS-Client is not compatible with the Outlook Express mail client. Restrictions Specific to Windows The normal procedure for sending E-Mail in Windows is as follows. The client application places the message in the Outbox of a message store provider, the latter notifies the MAPI Spooler, the Spooler dispatches the message to the appropriate transport provider based on message recipients and, finally, the transport provider takes over message delivery. Since Microsoft overlooked security and identity issues in designing the MAPI Spooler, it cannot properly work with client applications that are services. For instance, the Spooler may not be able to access Mail Profiles due to incorrect security context, and may not receive new message notifications from a message store provider by way of window messages (every service runs in its own virtual desktop and window messages do not propagate between desktops). Because DS-Client runs as a service on Windows, it must not use the MAPI Spooler. This means DS-Client notifications will forever remain in the Outbox of the message store provider unless the latter is tightly coupled to a transport provider, so that the two can work out between themselves how to send the message without the intervention of the MAPI Spooler. At this time, only the Microsoft Exchange Server mail client is known to offer tightly coupled message store and transport. You can specify the message store and transport to be used by DS-Client by creating a Mail Profile (see next section) and selecting it in DS-User Configuration (See Configure the E-Mail Notification Setup on page 36.).

Confidential.
To use DS-Client with non-tightly coupled transports, such as Internet Mail, you can force DS-Client to use the MAPI Spooler by setting the Registry value [HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ DS-Client \ Parameters] MailUsingSpooler to a nonzero DWORD value. Keep in mind that such use is not supported by Windows architecture and errors are bound to ensue. Make sure no other MAPI client applications are executed on the DS-Client computer. How to Create a Mail Profile for DS-Client 1. Have a mail account created on the mail server for use by DS-Client. 2. Login to the DS-Client computer using the <<DS-Client service account>>. If the DS-Client computer is running Windows, it is the account found in the Services Control Panel for Asigra Cloud Backup service. Don't forget to select the correct domain when logging in. 3. While logged in with the DS-Client service account, install your mail client (if not already installed) and use it to create a new (or edit an existing) Mail Profile. a. Add to the Mail Profile a messaging service that includes a tightly coupled message store and transport, such as Microsoft Exchange Server, and configure this messaging service to use the mail account created in step 1; b. Specify a message store added in 3.a as the default message store; c. Move transports added in 3.a to the top of the transport order; d. Specify the default address book of your choice; e. Save the Mail Profile, start a mail application, configure it to use the Profile just created and proceed to send a test message. Once you have successfully tested your Mail Profile, you may configure DS-Client to use it. (See DS-User Guide: Notification Tab).
Notes
1. ASIGRA strongly recommends using SMTP notifications. 2. Certain mail clients (e.g. Eudora Mail) may replace the MAPI Stub Library (MAPI32.DLL) with a version that does not support the Extended MAPI interface. If this happens, reinstall Microsoft Outlook.


Confidential.
SNMP Notification
Creation Date: May 27, 2002 Revision Date: August 29, 2011 Product: DS-Client
Traps
Asigra Cloud Backup software can send traps as notifications as follows: SNMP Traps from DS-Client SNMP traps that are configured per backup set (Set Properties - Notification tab) can be sent for any of the following backup results: Successful Completed with warnings Completed with errors Incomplete For per backup set DS-Client SNMP traps, a trap will be sent once, immediately after each backup activity finishes. In addition, DS-Client can be configured to send a special trap as a "heartbeat" signal (at a user-defined frequency configured in Setup > Configuration > SNMP tab). This signal can be used to determine if the monitored Asigra Cloud Backup service is running normally. SNMP Traps from DS-NOC DS-NOC tool can be configured to send traps after it receives (monitors) the following events from DS-Clients (these events are defined on the DS-NOC server): Backup finished successfully Backup finished with intermediate errors Backup finished with critical errors Scheduled backup was not triggered for [xx] hour(s) DS-Client does not connect to DS-NOC for [xx] day(s) Further information (backup set name and DS-Client name) about this backup activity is in the first VarBind parameter coming with the trap. For example, in HP OpenView, you can use "$1" parameter in event message setting to retrieve the first VarBind data. In addition, DS-NOC can be configured to send a special trap as a "heartbeat" signal (at a user-defined frequency). This signal can be used to determine if the monitored Asigra Cloud Backup service is running normally.
ASIGRA MIB
The MIB (Management Information Base) file for Asigra Cloud Backup can be found in the DS-Client installation directory (filename: asigra.mib). This file describes how the objects are organized. ASIGRAs IANA Private Enterprise Number is 15538. Check http://www.iana.org/assignments/ enterprise-numbers.


Confidential.
Configuration
DS-User From main menu, choose "Setup > Configuration > SNMP" to configure DS-Client SNMP settings (destinations). Notification events are configured per backup set ("Sets > Backup Sets > Properties > Notification"). For more details, use the online help for these dialogs. DS-NOC The DS-NOC server is configurable via a Web Browser. Once logged in to a DS-NOC, you can configure Notifications for DS-Clients. In one of the configuration pages, you can select the option "Send SNMP trap". For more details, refer to the DS-NOC User Guide. Configuration Sample (With HP OpenView) This sample provides a general example of how a third-party application can use the traps sent by DS-Client or DS-NOC. Load asigra.mib into HP Openview. 1. Options > load/unload mibs: snmp >load from disk 2. After that, two new categories (enterprises) can be found in event configuration dialog. Configure DS-Client Events 1. Options > event configuration 2. Choose DS-Client from enterprises portion. There are several options in the event list for enterprise DS-Client, including: Clientbackup completed Clientbackup completed with errors Clientbackup failed Client Heartbeat 3. You can modify these events by double-clicking these specific events, setting event message actions, severity level and event log messages.


Confidential.
Setting up the Novell NetWare Client on the DS-Client computer

Creation Date: April 7, 1999 Revision Date: February 14, 2011 Product: DS-Client (Windows)
Summary
If you wish to backup and restore NetWare file systems (including NDS, Trustees, etc.) the DS-Client computer must have the Novell NetWare client loaded.
Windows
For DS-Clients running on Windows XP or Windows 2003, Novell's NetWare client v.4.9.1 SP2 or higher is required. For DS-Clients running on Windows VISTA or Windows 2008, Novell Client 2 for Windows Vista/ 2008 is required.
Conclusion
Once the appropriate Novell NetWare client is installed, the DS-Client will be ready to backup/ restore NetWare servers (with all features, including security).
See Also
Backup / Restore of Novell NetWare files from a Windows DS-Client on page 542 Backup / Restore of Novell NetWare files from a Linux DS-Client on page 544


Confidential.
Snapshot Transfer Issues

Creation Date: October 09, 2012 Revision Date: October 09, 2012 Product: DS-Client (Linux)
Summary
This article contains additional information about Snapshot Transfer.
How to access NetApp snapshot data

In order to access the snapshot data, you need to use either the NFS protocol or CIFS protocol. For example: If the volume (share) name is 'example' and the snapshot name is 'SV_20121001_080000' For NFS you would use the following:
mount nas_address:/vol/example/.snapshot/SV_20121001_080000 /mnt
For CIFS you would use the following:

UNC: \\nas_address\example\~snapshot\SV_20121001_080000
For further information, consult your NetApp documentation.
See Also
Snapshot Manager on page 312


Confidential.
Troubleshooting: DS-Client Workaround for Mac OS X (10.6 Snow Leopard) Auto-Mount Configuration
Creation Date: March 25, 2010 Revision Date: May 12, 2010 Product: DS-Client (Macintosh)
Summary
This article only applies to DS-Clients running on Mac OS X 10.6 (Snow Leopard). With the release of Mac OS X 10.6, Apple removed the public API for listing exported volumes. As a result, although the ability to mount volumes and access data remains, the Mac DS-Client is unable to obtain the available volumes for backup. This limitation affects backup set creation, editing backup sets, and restoring data to alternate locations. This means a default DS-Client installation running on Mac OS X 10.6 cannot use auto-mount backup sets (agentless backup for Mac OS X using Mac-specific API). These are backup sets created by browsing for active Mac volumes on your network (New Backup Set Wizard > Select the computer screen: Local File System\Auto Mount). The rest of this article deals with a temporary workaround.
Configuring the Mac DS-Client for auto-mount backup

In order to bypass the limitation caused by removal of the Apple public API from OS X 10.6, the Mac DS-Client can use two configuration files named mountpoints.cfg and mountpoints.permissions. Both are plain-text files, which for a default installation must be located in /Library/CloudBackup/DS-Client/automount/. The file mountpoints.cfg contains all the available mount points on the remote machines that will be made available by the DS-Client via the DSUser GUI. The file mountpoints.permissions contains the permission rules which will grant or deny users the right to authenticate (i.e. wrong credentials will fail) with the mount points listed in mountpoints.cfg. WARNING: The credential files you create must be kept secure, since they contain network credential information in clear text. Do not create these files unless their use conforms to you companys network / security policies.
File format and example: mountpoints.cfg

The file mountpoints.cfg contains computer name / volume name pairs, separated by a colon (:) where computer name may be a local domain name or an Ipv4 address). The # character denotes a comment and entries following it will be ignored. The following is a sample mountpoints.cfg file (/Library/CloudBackup/DS-Client/automount/ mountpoints.cfg):
# format = <Machine name or IP>:<shared volume name> MacMach.local : Dave's Public Folder MacMach.local : Macintosh HD AppleMach.local : Mac Hard Disk # IP works too 192.168.100.101 : Macintosh HD

Confidential.
192.168.100.101 : Mac HD2 #another comment
File format and example: mountpoints.permissions

The file mountpoints.permissions processes each line as one rule. A rule dictates which users are allowed to authenticate with the listed mountpoints. It is formatted as follows:
<mountpoints> % <user permissions>
The mountpoint list is composed of double-quoted items with comma as a separator. Each item must specify the machine name (or IP) followed by a colon (':') and then the exact mountpoint name or wildcard ('*') to denote all mountpoints (e.g. MacMach.local:Macintosh HD). You can exclude an item by using the minus (-) sign before the machine name or IP address. The user permissions list is composed of keywords (cAsE-sEnSiTiVe) and usernames with comma and whitespace as separators. Any usernames after the keyword ALLOW will be allowed to authenticate with the corresponding mountpoint list. For rules that are intended to apply to all users, the keyword EVERYONE can be used. To exclude certain users from the permissions list, place the usernames after the keyword EXCEPT (note: EXCEPT EVERYONE will deny all users right to authenticate with the corresponding mountpoint list). These usernames must also be defined on each corresponding machine where they attempt to authenticate. The following is a sample mountpoints.permissions file (/Library/CloudBackup/DS-Client/ automount/mountpoints.permissions):
# format = <Mountpoint list> % <Users permissions list> # allow dave to authenticate with Dave's Public Folder on # any machine Dave's Public Folder % ALLOW dave # allow dave and alice to authenticate with Mac HDD on # MacMach.local MacMach.local:Mac HDD % ALLOW dave, alice # allow everyone except dave to authenticate with Macintosh # HD on MacMach.local MacMach.local:Macintosh HD % ALLOW EVERYONE EXCEPT dave # allow alice to authenticate with all mountpoints on # AppleMach.local except Mac HDD AppleMach.local:*, -AppleMach.local:Mac HDD % ALLOW alice # IP works too 192.168.100.101:Mac HD2 % ALLOW EVERYONE #in-line comment
Changes to these configuration files do not require a DS-Client restart. They will take effect upon the next activity.


Confidential.
Knowledge Base: SECURITY


Confidential.
Digital Signature Verification

Creation Date: October 7, 1997 Revision Date: February 21, 2008 Product: DS-Client
Summary
In order to ensure integrity of the data that the DS-Client backs up and restores on a customer network, a digital signature is created and attached to every file that the DS-Client transfers to the DS-System. A digital signature represents 128-bit code that identifies data within the file. Even a one-bit change to a file will produce a different digital signature. Digital Signatures are used for several processes: Digital Signature during Restore on page 447 Digital Signature during Validation on page 447 Verify Digital Signature (option on Demand Backup) on page 447
Digital Signature during Restore

During a restore operation, the DS-Client recreates the digital signature and compares it to the one attached to the file. This verifies that the file content is exactly the same as that which was backed up. This is especially important when restoring databases, Registry, NDS and other types of data where even one-byte changes can make the data useless or even harmful.
Digital Signature during Validation

Validation uses the Digital Signature to verify the integrity of the online file. For more information see Knowledge Base Article Validation Overview on page 526.
Verify Digital Signature (option on Demand Backup)

[Windows DS-Clients only] During a Demand Backup, you have the option to select Verify signature for unchanged files. This feature is intended as a troubleshooting tool. If you use it, DS-Client will read the digital signature from the latest online generation of each unchanged file, and compare it with the digital signature that is generated from the current source file. If the signatures do not match (this should not occur often, or even at all), DS-Client will re-backup that file in that same backup session. This option is available for file system, E-Mail (DS-MLR) and System i Server backup sets. This option will apply only to latest generation of the files. This option cannot be used in conjunction with the Use Buffer option. If you use this feature, backup performance will slow by a significant amount, since the files that would otherwise be ignored must be processed.


Confidential.
DS-Client Encryption Keys

Creation Date: October 7, 1997 Revision Date: September 22, 2009 Product: DS-Client
Summary
In order to secure customer information that is transferred to the DS-System, the DS-Client encrypts every file it sends to the DS-System with encryption keys provided by the customer. The files are stored and remain encrypted on DS-System storage at all times. The decryption process occurs during the restore operation on the DS-Client itself. This ensures that any information transferred and stored outside the customer location is always encrypted. Currently, the DS-Client uses either the DES encryption algorithm (56-bit encryption key), or AES encryption algorithm (128-bit, 192-bit, or 256-bit). Configuration and Location of Encryption Keys on page 448 DS-Client Encryption Key Types and Usage on page 448 Encryption Key Verification on page 448 Retrieving the DS-Client Encryption Keys on page 449 AES Disclaimer on page 449
Configuration and Location of Encryption Keys

The DS-Client encryption keys are configured during DS-Client installation. Windows DS-Clients can also configure them using the DS-Client Setup program (normally found in Start > All Programs > Asigra DS-Client > DS-Client Setup). Encryption keys are stored in the DS-Client database in encrypted form, so even a person with full access to the DS-Client computer (like administrators) cannot find out the values of the encryption keys. For Grid DS-Clients, all DS-Clients in the same Grid must be configured with the same Private and Account Encryption Keys (both Types and Values).
DS-Client Encryption Key Types and Usage

The DS-Client can be configured with two encryption keys: a private key and an account key:
Private Key (Mandatory) This is a default encryption key that always used by the DS-Client except in the cases outlined below. If the customer account has more than one DS-Client installation, each DS-Client for this customer account must be configured with the same account key. A DS-Client that is configured with the wrong (or no) account key will not be granted connection to DS-System. The account key is used to encrypt customer files if the DS-Client discovers (during the backup process) that a backup file was already backed up to the DS-System by another DS-Client within same customer account. In this case, the file will be located in the account library area and encrypted with the account key.
Account Key (Optional)
Encryption Key Verification

In order to ensure that the DS-Client uses the same encryption keys as were initially configured (reinstalling DS-Client or hackers), the DS-System is able to verify the DS-Client key integrity on every connection. This is accomplished by comparing the encryption cookies (code generated with the encryption key, but not the key itself) that the DS-Client sends on every connection request, with the cookies that the DS-System received during DS-Client registration.

Confidential.
Intentional or unintentional changes to the encryption keys will make data stored on the DS-System unusable. This verification process ensures integrity of both private and account keys (account key verification ensures that all DS-Clients for the same customer account are configured with the same account key).
Retrieving the DS-Client Encryption Keys

The DS-Client has the capability to forward its encryption keys to the DS-System for safekeeping. This option must be enabled by your Service Provider. For more details, see Encryption Key Safeguarding at the DS-System on page 33.
AES Disclaimer
The DS-Client integrates Dr. Brian Gladmans implementation of the AES (Rijndael) algorithm designed by Joan Daemon and Vincent Rijmen. This implementation is referenced in the information on the AES development efforts on the Computer Security Resource Center website maintained by NIST (National Institute of Standards and Technology - USA). For more information please visit the following URLs:
http://csrc.nist.gov/CryptoToolkit/aes/rijndael http:/fp.gladman.plus.com/cryptography_technology
Here is the copyright notice for Dr. Brian Gladmans implementation:

------------------------------------------------------------------------Copyright (c) 2001 Dr Brian Gladman <brg@gladman.uk.net>, Worcester, UK TERMS Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. This software is provided 'as is' with no guarantees of correctness or fitness for purpose. -------------------------------------------------------------------------
See Also
Encryption Key Safeguarding at the DS-System on page 33 DS-Client to DS-System Authentication on page 450


Confidential.
DS-Client to DS-System Authentication

Creation Date: April 30, 1997 Revision Date: September 26, 2002 Product: DS-Client
Summary
In order to prevent unauthorized access to the DS-System, several protection layers are implemented on the DS-System computer to ensure that only authorized computers are able to gain access to DS-System storage. Those protection layers can be divided into following categories: Network access layer 1. Outside connections can only be initiated on a separate network interface with the TCP/IP protocol. 2. The only TCP and UDP ports enabled are those used by the DS-System and DS-Client services. 3. The incoming DS-Client connection's IP address (or range) is validated against the DS-Client profile (optional). 4. User ID and password validation is performed for dialup connections (T1/ISDN access). 5. CLID (caller ID) validation is performed for T1/ISDN access (optional). Configuration layer 1. The DS-Client must pass valid Customer Account and DS-Client numbers to the DS-System. Registration layer 1. The DS-Client performs an automated, one-time registration with the DS-System (if "requires registration" is selected). The registration is performed automatically on the first DS-Client connection to the DS-System. If re-registration is required, a registration request must be explicitly enabled by the DS-System operator at the request of the DS-Client user. 2. The Registration process passes information constructed from the DS-Client computer's hardware and system on every connection request. Once a DS-Client is registered, the DS-System can optionally validate DS-Client registration information for every subsequent connection attempt. Registration validation provides a high level of confidence that the DS-Client computer attempting to connect is the same computer that performed the registration. 3. The DS-Client registration validation will fail in the following circumstances: if you reinstall the Operating System of the DS-Client computer install the DS-Client on a different computer boot a different Operating System on the DS-Client computer (e.g. if you have a dual-boot machine.) change hardware components like the system hard drive or network card Encryption authentication layer 1. Encryption Key Cookies: The Registration process also saves encryption key cookies (meaningless data encrypted with DS-Client keys, that are passed on every connection request) that the DS-System validates on each connection attempt. This

Confidential.
prevents a DS-Client from connecting to the DS-System with changed or corrupted encryption keys. Additional conditions for connection request failure 1. Customer Account or DS-Client does not have 'active' status. 2. DS-System shutdown is in progress. 3. DS-System activities are disabled. 4. DS-Client Service period violation (service period expired). 5. Account Key required and not configured for customers with multiple DS-Clients.


Confidential.
Logon Impersonation and Integrated Security

Creation Date: October 7, 1997 Revision Date: January 23, 2008 Product: DS-Client (Windows)
Summary
When the DS-Client is installed and deployed on the Windows platform, it uses the Logon Impersonation feature. This feature allows the DS-Client to perform backup/restore activities under the security context of that particular user account. Several such activities can be performed simultaneously, each under a different (or the same) user account, connecting to a different (or the same) network resource. This feature is especially valuable (and sometimes even essential) when connecting to resources on a Microsoft Windows Network.
Connecting to resources on a Microsoft Windows Network

When supplying credentials to a resource on a Microsoft Windows Network, the 'from' value determines if the user account should be authenticated (if the 'from' value is not <None>) or if a simple connection to the network resource should be made with the supplied credentials.
Microsoft Developer Network's definition of Impersonation is: "... the ability of a thread to execute in a security context different from that of the process that owns the thread ... [thereby allowing] ... the server thread to act on behalf of that [process] Logon Impersonation. to access objects or validate access to its own objects." In Asigra Cloud Backup, "logon impersonation" is the DS-Client's ability to run under a different security context for each backup set, as specified in the "Connect As" field (Sets Menu > Backup Sets > Properties > Share Tab). When the 'from' value is something other than <None> (e.g. represents a server or a domain), the DS-Client will perform user account authentication and logon impersonConnecting with inte- ation before connecting to the network resource. This allows the network server to see grated security. the incoming connection as if it were established by that user account. This is essential to successfully connect to network resources such as MS SQL server and MS Exchange server that use integrated security to validate user access. Connecting without integrated security. When the 'from' value is <None>, the DS-Client performs logon impersonation of the user account under which the DS-Client service is running (this is necessary in order to allow simultaneous connections to the same network server). Then, the DS-Client connects to the network resource with the supplied credentials.
Connecting to resources on other networks

When connecting to resources that are not on a Microsoft Windows Network, the DS-Client performs the same steps as in 'Connecting without integrated security'. If connecting to NetWare servers, the 'from' value is used as a context in NDS authentication.


Confidential.
User Rights and Privileges

Creation Date: October 14, 1997 Revision Date: March 21, 2008 Product: DS-Client (Windows)
Summary
When the DS-Client is installed and deployed on the Windows platform, it uses the User Privileges feature. The DS-Client attempts to activate specific user privileges when performing backups or restores of a Windows computer. Those privileges are applied for each activity (thread) under the supplied user's credentials. To successfully activate those privileges, the user account must have user rights enabled for that privilege (in 'User Manager'). Depending on the server configuration, failure to activate those privileges may not permit the backup/restore to be performed successfully.
Privileges used by the DS-Client

Back up files and directories - SE_BACKUP_NAME Allows a user to back up the files, directories and registry of a computer. This right supersedes files, directory and registry permissions. Used in the backup process. Restore files and directories - SE_RESTORE_NAME Allows a user to restore the files, directories and registry of a computer. This right supersedes files, directory and registry permissions. Used in the restore process. Manage auditing and security log - SE_SECURITY_NAME Allows a user to manage the auditing of files, directories, and other objects. Used by the backup and restore processes to backup/restore security information (auditing portion of ACL).
See Also
Logon Impersonation and Integrated Security on page 452


Confidential.
Encrypting your Network Credentials

Creation Date: December 10, 2005 Revision Date: February 03, 2011 Product: DS-Client
Summary
If you want to distribute credentials without telling the recipient the actual password to a network resource, DS-Client can accept input from an encrypted file. All the recipient needs to know is the key (password) that unlocks the file. For example: If your Service Provider is managing the DS-Client, and you do not want them to know the credentials, you can create an encrypted file (default filename: backup.key). You can supply this file to your Service Provider and tell them the password to use the backup.key. The backup.key file can be used in the Enter / Modify Credentials screen. 1. Create an encrypted file. A software tool (filename: MakeKey.jar) is supplied for you to make the backup.key file. MakeKey.jar is located in the DS-User or DS-Client installation directory. The Java 2 Runtime Environment Version 1.4.2 or later must be installed on the local computer. Double click on the application icon and enter the information. 2. Give the file to your service provider and tell them where to use it. They need to know the key that unlocks the file. Multiple encrypted key files can be created. Using descriptive names can help recipients know the right key to use. If you want, you can use the same password (unlock key) for different backup key files, according to your requirements. 3. The encrypted file can be used when creating or editing backup sets.


Confidential.
Logon using security context

Creation Date: May 18, 2011 Revision Date: May 18, 2011 Product: DS-Client (Windows)
Summary
This section describes the Logon using security context features in greater detail. Target Name (Logon using Security Context) on page 455 Auto-Connect (Logon using Security Context) on page 456
Target Name (Logon using Security Context)

This feature allows DS-User to automatically connect to a DS-Client using the current security context of the user (i.e. the current Windows logged on user). It does this by using the Microsoft Security Support Provider Interface (SSPI). The SSPI APIs require a Target Name that points to a Service Principal Name (SPN), or to the security context of the destination server. This feature will use the Microsoft Negotiate security package, which selects between Kerberos and NTLM. Negotiate normally selects Kerberos, unless it cannot be used by one of the systems involved in the authentication. Kerberos requires Domain membership. Therefore, when a DS-Client is not under any Domain, the Target Name is optional and can be left blank, particularly if you are only connecting to the local DS-Client. It is only used if this DSUser GUI tries to connect to a DS-Client in the same Active Directory Domain or in a completely separate domain. These involve modifications to the Windows network settings, therefore make sure any changes conform to your network security policies. The default Target Name is CloudBakSvc. To enable this for use, you must use the Microsoft Networking Tool (setspn.exe) to give this name the authentication and trust required to log into the desired DS-Clients on your network(s). For example: If the DS-Client was installed on a computer that is a member of an Active Domain (AD), by a Domain Administrator, then CloudBakSvc is registered in the AD. If a DS-User GUI connects to that DS-Client and supplies the registered Target Name (CloudBakSvc), the DSClient will accept the connection, given the user has been logged into their local Windows environment. The Target name points to an SPN that must be registered and configured in Active Directory. 1. The default Target Name is CloudBakSvc. You must have your network administrator create and register this Target Name (or any other name you choose to use) with Active Directory using a tool like Microsoft setspn.exe provided with Windows Support Tools. In an Active Directory environment, you must have your network administrator register this Target Name in form <name/host> or <name/host-DNS-name> for the account used by the DS-Client service (if LocalSystem, the target name must be registered under the computer account). 2. Register this Target Name with Active Directory. Microsoft supplies a tool (setspn.exe) that can register with the command line:
C:\>setspn -A CloudBakSvr/hostname ComputerAccount-OR-ServiceAccount
ComputerAccount must be used if registering DS-Client on the local computer. ServiceAccount must be used if registering on a Domain.


Confidential.
3. Once registered, this DS-User will supply the Target Name for DS-Client to verify using Kerberos authentication. This will establish the trust required for an authenticated user from this DS-User GUI to connect to a remote DS-Client on another network. Each DS-Client requires its own separate SPN for the same Target Name.
Auto-Connect (Logon using Security Context)

The Auto-Connection selection configures how this installation of the DS-User GUI will behave when it launches. Last DS-Client: This DS-User GUI will search for the last DS-Client it successfully connected with. If that DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Local DS-Client: This DS-User GUI will search for the local DS-Client. If the local DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Last or Local DS-Client: This DS-User GUI will search for the last connected DS-Client first. If the last connected DS-Client is found, DS-User will attempt to connect using the already logged on user credentials from the current Windows login session (provided that the same username and password is provided). If however, the last connected DS-Client is not available DS-User will connect to the local DS-Client using the current security context. Local or Last DS-Client: (Default) This DS-User GUI will search for the local DS-Client first and connect using the current security context. If the local DSClient is not found, DS-User will attempt to connect to the last connected DSClient using the current security context (provided that the same user network credentials are used, and that the local user exists on the remote DS-Client, and appropriate user permissions are there in the remote DS-Client). Disabled: Users can select this option to turn off the auto-connect functionality. Users will see the Connect to DS-Client Service screen at GUI startup and must supply a valid username and credentials to connect to the selected DS-Client.


Confidential.
Knowledge Base: ADMINISTRATION


Confidential.
DS-Client Advanced Configurations

Creation Date: March 20, 2008 Revision Date: September 28, 2012 Product: DS-Client
Summary
WARNING:The default settings are sufficient to run any DS-Client. Do not attempt to change these settings, unless you have a specific requirement and have confirmed this with your Service Provider.
The Advanced Configuration option contains a list of parameters that can fine-tune how the DSClient behaves. To access the Advanced Configurations settings: 1. From DS-User Setup Menu > Configuration. 2. In the DS-Client Configuration screen, select the Advanced tab. 3. Parameter values can only be edited. The parameters screen is slightly different, depending on the type of DS-Client: Windows DS-Client parameters on page 458 Note: Windows DS-Clients have additional settings for Grid DS-Clients (Global parameters and Leaf-Node-Specific parameters). Some parameters can only be Global, while others can be both. These differences are noted in the table. Linux / Mac DS-Client parameters on page 468 WARNING:If you change any of these parameters, they will significantly change DS-Client behavior (performance). Changes to some parameters only take effect after the DS-Client restarts.
Windows DS-Client parameters

Category: ADMIN on page 458 Category: COMMUNICATION on page 459 Category: INSTALLATION on page 460 Category: MISCELLANEOUS on page 460 Category: NOTIFICATION on page 464 Category: PERFORMANCE on page 465 Grid DS-Client Only - Local Setting on page 467
Category: ADMIN Parameter Global / LeafNode-Specific Description / Values (Weeks) - Interval for Weekly Admin to not synchronize backup sets that have only internal inconsistencies. Range: 0-12 Default Value: 0
AdminNoSyncInterval Global only


Confidential.
AdminSkipSync
Global only
Skip synchronization of backup sets during Weekly Admin if no database inconsistencies are detected. No = OFF Yes = ON (default) Specifies the order in which backup sets will be synchronized during Weekly Admin. Possible values are: No specific order enforced Bigger sets first (ones that contain more backup items) (default) Smaller sets first This parameter configures maximum number of synchronization threads during weekly admin. Range: 1 to 8 Default Value: 1 This parameter configures the Dump path for DS-Client Database during admin activities. This path can be local or a UNC path. UNC is recommended for Grid DS-Clients. If not set, the default dump path will be the DS-Client Buffer.
AdminSyncOrder
Global only
AdminThreads
Global only
DSCDBDumpPath
Global only
Category: COMMUNICATION Parameter Global / LeafDescription / Values Node-Specific Low-level communication method between DS-Client and DS-System. 0 = Network packets are not encrypted. (Fastest) 1 = Same as method 0 with a different implementation. (For trouble-shooting purposes only.) 2 = (DEFAULT) Network packets are encrypted on top of existing data encryption. (Slowest) Low-level communication method between DS-Client and DS-MLR / DS-Recovery Tools. 0 = Network packets are not encrypted. (Fastest) 1 = Same as method 0 with a different implementation. (For trouble-shooting purposes only.) 2 = (DEFAULT) Network packets are encrypted. (Slowest) Default value of this parameter is 0. This parameter configures the Alternate port to connect to DS-System. If DS-Client fails to connect to DS-System on the default port (4401), it will try this port number (if configured). 0 means do not try to use an alternate port. IP Address to listen for Hessian API Connections. Use '0.0.0.0' to listen on all interfaces. Port on which to listen for Hessian API Connections Default is 4411 Log file to use for the Hessian API Server Valid Values: any valid file name Log level to record in the Hessian API Server logging file debug: info: warning: (default) error: fatal: SSL certificate/key file to use for the Hessian API Server (PEM format) Default Value: C:\Program Files\CloudBackup\DS-Client\api.pem
Confidential.
CommunicationMethodDSS
Global only
CommunicationMethodMLR
Global only
DSSystemAlternatePort
Global only
HessianAPIListenIP (RESTART REQUIRED) HessianAPIListenPort (RESTART REQUIRED) HessianAPILogFile (RESTART REQUIRED)
Global only Global only Global only
HessianApiLogLevel (RESTART REQUIRED)
Global only
HessianApiSSLFile (RESTART REQUIRED)
Global only

HessianApiSSLPassword (RESTART REQUIRED)
Global only
SSL certificate/key file passphrase Enter a valid password / passphrase for the SSL certificate/key file specified in the HessianApiSSLFile parameter. This parameter configures the interval after which the network connection with DS-System is checked regularly by the DS-Client having schedule(s) configured with the option of verify network connection. This is particularly useful for DS-Client installed on portable devices. The minimum timeout period for API messages. You can increase this parameter if you encounter a large amount of Timeout on receive message errors. range 10-14400, default is 10 (minutes) Defines how often to retry the primary DS-System connection after switching to a secondary connection (in hours). -1 never retries, 0 retries immediately. range -1 to 240, default is 24
LaptopCheckInterval
Global only
MinApiMsgTimeout
Global only
RetryPrimary
Global only
TcpSocketBuffer
The value of this parameter is in Bytes. This value is used if it is bigCan be either ger than the default TCPWindowSize. Default value of this parameter is 24*MSS=0x87C0 (34752) Bytes Global only (seconds) Timeout period for DS-Client to receive a response for a VSS (Volume Shadow Copy) operation. The VSS operation will fail after the timeout period. range 60 to 3600, default is 300
VSSKeepAliveTimeout
Category: INSTALLATION Parameter Global / LeafDescription / Values Node-Specific Determines what DS-User auto-upgrade packages this DS-Client will download from DS-System if they are available. Disabled: DS-User auto-upgrade packages will not be automatically downloaded from the DS-System. Cross-Platform DS-User Auto-Upgrade: DS-Client will download all DS-User auto-upgrade packages that exist on the DS-System to the DS-Client directory during Daily/Weekly Admin. Compatible-Platform DS-User Auto-Upgrade: DS-Client will only download the DS-User upgrade packages which are compatible with the OS of the DSClient. A list of file names that will be skipped by Windows DS-Client if encountered during backup. The list is an alphanumeric text string of file names. Each file name is separated by \; (a backslash followed by a semi-colon). The end of the string it signalled by a second \; as in the following example of the default list: system.da0\;user.da0\;pagefile.sys\;win386.swp\;backout.tts\;btrieve.trn\;net$obj.sys\;net$val.sys\;net$prop.sys\;\; Note: Each Windows computer can have additional files configured to be skipped in the local registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup. DS-Client will skip these files when encountered during backup of regular shares or drives (but not for System State or Services Database items).
DS-UserAutoUpgrade
Global only
SystemFiles
Global only
Category: MISCELLANEOUS Parameter Global / LeafDescription / Values Node-Specific

Confidential.

AllowAutoConfig
Global only
Allow DS-Client to apply Auto-configuration from the file configupdate.xml. No = OFF Yes = ON (default) Allow auto-upgrade of DS-Client from DS-System when their version does not match. No = OFF Yes = ON (default) If set to "YES", it allows the execution of local commands during Pre/ Post Activities. You must be an administrator and have this option enabled, in order to enable the Pre/Post Activities. If this parameter is changed, it takes effect next time the DS-User GUI connects to DS-Client Service. No = OFF (default) Yes = ON Configures scheduled backups to use the "verify signature for unchanged files" feature. By default scheduled backups do not verify the signatures of unchanged files on the backup source. If this parameter is set to "YES", then scheduled backups will verify the signatures of unchanged files on the backup source. Turning this option ON can have significant implications on the performance of the DS-Client. No = OFF (default) Yes = ON Detect MS SQL instances when browsing domains/workgroups No = OFF (default) Yes = ON [DS-Clients using SQL Server 2005/2008 Express] This parameter (in percent) sets the level at which the Daily Admin or Weekly Admin will automatically expand the DS-Client database to create a new, sequentially named expand<nnnn> database. The percentage is calculated against the maximum allowed size for an individual database (4GB). range 0 to 100, default is 70 (percent) For SQL Server 2005/2008 Express, the maximum size of an individual database is 4GB. [DS-Clients using SQL Server 2005/2008 Express] If the current amount of space used in an expand<nnnn> database is less than this parameter (in percent), Daily Admin and Weekly Admin can move backup set tables into that database. range 0 to 80, default is 40 This parameter value (in seconds) sets the default Database query timeout. Default: 500 0=Unlimited Timeout Range: 0 to 65535 This parameter only applies to time consuming Database queries known by the DS-Client. The value (in hours) sets the longest Database query timeout period. If a Database Query takes more time than this parameter value, it is aborted by the DS-Client. Default: 18 0=Unlimited Timeout Range: 0 to 19
AllowAutoUpgrade
Global only
AllowLocal
Global only
AllowScheduledBackGlobal only upCheckSignature
BrowseCheckSQLInstances
Global only
DBHighWaterMark
Global only
DBLowWaterMark
Global only
DBQueryDefaultTimeGlobal only out
DBQueryTimeout
Global only


Confidential.
DebugMessage
This parameter sets the detail level of error messages reported in the DS-Client Event Log. 0 = (Default) Standard level of error-message reporting. 1 = Some additional detailed log information is reported. You will Can be either notice that database errors are appended with the SQL statement. 2 (or any higher number) = Same behavior as 1, with additional debug information reported in a DS-Client debug log file (dsclient.exe.dbg.log located in the DS-Client installation directory). This option is meant for debug situations only. Global only The default period to keep data in the Local-Only trash. This applies to all defined Local-Only paths for this DS-Client. Valid values: 1-999, default is 7 (days) (count) - Maximum number of attempts to read the first buffer from a file during Microsoft Exchange server backups. Default: 30 Range: 1-3600 If yes, force all applicable backup sets to check signature for unchanged files. The checking will be performed once during the next backup of each backup set. This setting applies only once. This means, as soon as you select "Yes" and apply, it will immediately take effect and the value is changed to "No" again. No = OFF (default) Yes = ON This parameter value will configure the Local Drive Filter Flag for Backup. By changing this parameter value you can control the Drives available for backup in the New Backup Set Wizard (applicable only to File System & Permissions Only backup sets). The default value for this parameter is -1, allowing all the available local drives. This value is converted from decimal to binary to determine if a drive is allowed (1 means allowed, 0 means disabled). For example: to allow only C and E drives, use the value 20 ... F E D C B A [drive letter map] ... . 1 0 1 0 0 [binary] ... . . . . 2 0 [decimal value] The binary representation of 20 matches bit0 for 'A:' disabled, bit1 for 'B:' disabled, bit2 on - 'C:' allowed, etc. Note for Grid DS-Client, this parameter has no effect.
DefaultLocalTrashKeepDays ExchangeMaxESERetries
Global only
ForceBackupCheckSignature
Global only
LocalDriveAllowed
Global only
LocalVDRToolHardwareCookie
Global only
Reset the Local DS-VDR Tools hardware cookie. If Yes, the hardware cookie will be reset on the next connection, then this value will automatically become No. No = OFF (default) Yes = ON Path where the Detailed Log for activities on the DS-Client are stored. Detailed Logs are located in this folder, under a sub-folder called asigra_archivlog where each backup set has its own numbered subfolder. Note for Grid DS-Clients: You should enter a UNC path that is accessible from all nodes of the Grid. This will ensure that all detailed logs are located in a common and accessible location. This parameter sets the default Stop on errors value that appears when creating new backup sets (in the New Backup Set Wizards Options Tab). range 0 to 9999, default is 0 (no limit)
LogArchivePath
Global only
MaxErrors
Global only


Confidential.
MaxNonFullDumps
Global only
Default maximum number of times a full dump of a Microsoft SQL Server database can be skipped in favor of a differential or incremental dump. After this number is reached, the next backup will force a full dump of the database. range 2 to 1000, default is 120 Configures the DS-Client for Multi-Tenant mode. No = OFF (default) Yes = ON If this DS-Client has started in Read-Only (Stand By) mode (no backup / restore allowed), this is the interval at which it will check for an upgrade package from DS-System. Valid values 1-60, default is 5 (minutes) (Minutes) - This parameter configures the default timeout period of DSClient for Remote Command Execution during Pre/Post Activities. range 1 to 1440, default is 60 Integration DLL for automatic restore target provisioning Any valid path to the corresponding DLL file that the DS-Client can access. Default is none. (Hours) - This is the period in which missed schedules will be triggered by the DS-Client, even after the actual scheduled time. range 1 to 16, default is 6 Path to a third party security DLL to secure the communication. By default, this path is empty. When this parameter is set to "YES", then in the New Backup Set Wizard (for File System & Permissions Only Backup Sets) you can see the "Backup as POSIX" checkbox. "Backup as POSIX" can only be selected when you create a new backup set. It cannot be configured from backup set properties. No = OFF (default) Yes = ON Indicates if Microsoft SQL Server backup set database dumps are kept in the dump location after the backup has been performed. This only applies to the classic MS SQL Server backup set type (not the VSSaware version). No = OFF (default) - Dump is deleted after backup has finished. Yes = ON - Dump is kept in the dump location. It will be overwritten during the next backup of that set. Note the storage implications, since this will affect all MS SQL Server backup sets created on this DS-Client. For VSS-aware Microsoft SQL Server backup sets. Stops a differential backup if it failed to retrieve the LSN (Log Sequence Number) information of the previous full backup. Yes = ON (default) No = OFF If Yes, the VSS-aware backup will continue even if there were writer errors, as long as the snapshot was created successfully. This will only occur after all configured retries have been attempted (VSSSnapshotRetries). Yes = ON (default) No = OFF
Multi-Tenant
Global only
ReadOnlyUpgradeInterval RemoteExecutionTimeout
Global only
Global only
RestoreTargetProvision Global only (RESTART REQUIRED) ScheduleMiss SecurityDll Global only Can be either
ShowPOSIX
Global only
SQLKeepDumpFile
Global only
StopOnRetrieveLSNFailed
Global only
VSSContinueIfSnapshotCreatedWithWriterErrors
Global only


Confidential.
VSSSnapshotRetries
Global only
If a VSS-aware backup creates a snapshot with writer errors, the DS-Client will retry creating the snapshot without any errors. This is the number of times DS-Client will retry creating an error-free snapshot. Default: 3 Range: 0-999, (0 means backup will fail if snapshot encounters VSS writer errors The retry interval for VSS snapshot retries (VSSSnapshotRetries). Default: 5 (minutes) Range: 1-99 Timeout while waiting for a VSS snapshot to be created. A longer period can prevent backup failures if different backup sets need to perform VSS backups of a common volume at nearly the same time. (Only one VSS snapshot can be performed on a volume at a time. Since snapshots are fairly fast, a timeout of 5-15 minutes should ensure two different backups of the same volume can be successfully completed, even if they overlap.) Default: 60 (seconds) Range: 1-3600 (Seconds) - This parameter value sets the time the DS-Client will wait for file confirmation from the DS-System if a backup activity is stopped. Default: 60 Range: 0 to 3600
VSSSnapshotRetryInterval
Global only
VSSWaitSnapshotTimGlobal only eout
WaitConfirmation
Global only
Category: NOTIFICATION Parameter Global / LeafDescription / Values Node-Specific [Only works if DS-Client database is local. Ignored if using a remote DB.] (0.01%) - Emergency warning level for the available space on the disks where the DS-Client database resides. Default: 500 (5%) Range: 0-10000 [Only works if DS-Client database is local. Ignored if using a remote DB.] This parameter value (in MB) configures the Minimum amount of free space reserved in the DS-Client Database. Low space checking will not count this reserved space as free space. Default: 100 Range: 10 to 500 [Only works if DS-Client database is local. Ignored if using a remote DB.] (0.01%) - Stop service level for the available space on the disks where the DS-Client database resides. Default: 100 (1%) Range: 0-10000 [Only works if DS-Client database is local. Ignored if using a remote DB.] (0.01%) - Warning level for the available space on the disks where the DS-Client database resides. Default: 1000 (10%) Range: 0-10000 This parameter value (in hours) configures the intervals after which regular Low Local Storage Emergency Warning Notifications will be issued by DS-Client. Default: 1 Range: 1 to 6
DBEmergencyLevel
Global only
DBReserveSpace
Global only
DBStopServiceLevel
Global only
DBWarningLevel
Global only
EmergencyFrequency Global only


Confidential.
MemEmergencyFreq
Global only
This parameter value (in hours) configures the interval at which regular Low Memory Emergency Warning Notifications will be issued by DS-Client. Default: 1 Range: 1 to 6 This parameter configures the Free Memory Emergency Level. If the DSClient free memory falls to equal or below this level DS-Client will start issuing Low Memory Emergency Warning notifications. Default: 20 (20%) Range: 5 to 100 This parameter value (in hours) configures the interval at which regular Low Memory Warning Notifications will be issued by DS-Client. Default: 4 Range: 1 to 24 This parameter configures the Free Memory Warning Level. If the DS-Client free memory falls to equal or below this level, DS-Client will start issuing Low Memory Warning Notifications. Default: 30 (30%) Range: 10 to 100 This parameter value (in %) sets the Emergency Warning level for DS-Client Local Storage root. If the DS-Client Local Storage free space falls to equal or below this level DS-Client will start issuing Emergency Warning notifications. Default: 30 (0.3%) Range: 1 to 10,000 This parameter value (in %) sets the Warning level for DS-Client Local Storage root. If the DS-Client Local Storage free space falls equal or below this level DS-Client will start issuing Warning Notifications. Default: 300 (3%) Range: 1 to 10,000 This parameter value (in hours) configures the interval at which regular Low Local Storage Warning Notifications will be issued by DS-Client. Default: 4 Range: 1 to 24
MemEmergencyLevel Global only
MemWarningFreq
Global only
MemWarningLevel
Global only
OLEmergencyLevel
Global only
OLWarningLevel
Global only
WarningFrequency
Global only
Category: PERFORMANCE Parameter Global / LeafNode-Specific Global only Description / Values Defines the number of records in one block for System i Server (formerly AS/400) backup sets. The bigger the block size, the more efficient the delta algorithm, but more memory will be required during restore. The default is 100000 (about 50 MB). (MB) - If the file size is bigger than this value, DS-Client maintains additional meta-data during backup until a new generation is confirmed to have been saved on DS-System. This overhead is balanced by the benefit of reducing the chance of sending the next generation as a master in case the backup experiences unexpected failures. range 1 to 102400, default is 100 MB If this parameter is set to "YES" then the SQLite Database File is cached to improve the speed. By default this parameter is set to "NO". No = OFF (default) Yes = ON
AS400BlockSize
BigMasterSize
Global only
CacheSQLiteFile
Global only


Confidential.
DBBulkOptions
Global only
This parameter can be set as follows (selection is effective immediately): Bulk inserts disabled Bulk inserts from files allowed Bulk inserts from memory allowed Bulk inserts from files and memory allowed (RECOMMENDED) (default) This parameter configures the number of DS-Client database connections to be created when DS-Client service is started. Changes to this parameter only take effect after the DS-Client service is restarted. Default: 3 Range: 1 to 16 For ZLIB Compression only: Enter 0-9, 0 = no compression (faster) and 9 = maximum compression (slower). Default value is 6. This parameter configures number of delta threads per backup thread. If set to 0, Delta backup is singled threaded. If set to 1, a single thread does compression/encryption but it is separated from I/O thread. If set to a value more than 1, then the Delta process is multithreaded. range 0 to 16, default is 1 This parameter configures number of delta threads for file system backups. If you only backup big files, this can improve speed. For backup of small files, the default DS-Client backup threads are usually sufficient. range 0 to 16, default is 1 Encrypt the data saved in the Local Storage Buffer for Local Storage and Local-Only backup sets. If enabled, the DS-Clients Private Encryption Key will be used. No = OFF (Default) Yes = ON The internal buffer size (in KB) allocated for reading a file during the backup process. range 16 to 16384, default is 64 Used with the SendFullMaster parameter to determine when to send (backup) a full master to DS-System. range 1 to 25, default is 10 Maximum concurrent activities supported by DS-Client. Increase if hardware can support additional processing. range 1 to 99, default is 8 (32-bit Operating Systems) and 12 (64bit Operating Systems) (GB) - Maximum file size for delta algorithm to apply. The bigger it is, the more memory is needed for delta processing. range 1 to 102400, default is 102400 (32-bit Operating System) range 1 to 1048576, default is 1048576 (64-bit Operating System) The allowed maximum pending I/O requests for a single file (backup or restore). Increasing this value may improve backup / restore speed if the target storage has very good parallelism (ability to perform simultaneous I/O requests). This option is provided for high performance environments where you can test the disk I/O. WARNING: Increasing this value too much can cause performance to slow. range 1 to 16, default is 2 Maximum number of read threads on DS-System side for a restore process. Valid values 1-16, default is 1
Confidential.
DBConnections Can be either (RESTART REQUIRED)
DefaultCompression
Global only
DeltaThreads
Can be either
DeltaThreadsFS
Can be either
EncryptedLocalData
Global only
FileReadBufferSize
Global only
MasterGenerations
Global only
MaxCacheCopySessions
Can be either
MaxDeltaSize
Global only
MaxPendingIOPerFile Global only
MaxRestoreReadThreads
Global only

MaxRestoreThreads
Can be either
This parameter configures the maximum number of threads for a restore process. range 1 to 16, default is 4 Determines when the MaxSessions parameter applies. Scheduled Activities Only = (default) Users can perform OnDemand activities that exceed the maximum concurrent activities. (Scheduled activities cannot exceed this limit.) Scheduled and On-Demand Activities = Scheduled and On-Demand activities cannot exceed the maximum concurrent activities limit. This parameter configures the maximum concurrent activities supported by DS-Client. Increase the value of this parameter only if your hardware can support additional processing. For Grid DS-Client this parameter also refers to the Task Limit as seen in DS-User: Grid Menu > Grid Status > List Tab for each Leaf/Node. range 1 to 99, default is 8 (32-bit Operating Systems) and 12 (64bit Operating Systems) This parameter configures the maximum number of threads for each backup activity. Increase the value of this parameter only if your hardware can support additional processing. range 1 to 16, default is 4 Maximum number of threads for each DS-MLR backup activity. Increase if hardware can support additional processing. range 1 to 16, default is 4 The minimum number of online generations required in order to process files as deltas. Enter 2 or 3. Default value is 3. (KB) - Minimum file size for delta algorithm to apply. range 8 to 1048576, default is 32. (MB) - This parameter sets the internal buffer size for caching restore data. Increasing this value may improve the restore performance. range 1 to 1024, default is 2 Sends a full master (instead of sending a delta and asking DS-System to reconstruct). No = OFF (default) Yes = ON If the value of this parameter is "YES", then DS-Client will skip compression on files identified as already being compressed. Files types identified as compressed are: pk, zip, gif, png, Microsoft Cabinet Files, gzip, win, jpeg & jfif. No = OFF Yes = ON (default) Sort algorithm used to sort internal list. Merge Sort Quick Sort (%) - Limits the DS-Client's consumption of the computer's CPU during statistical backups to this percentage. range 0 to 100, default is 70
MaxSessionCheck
Global only
MaxSessions
Can be either
MaxThreads
Can be either
MaxThreadsMLR MinDeltaGen MinDeltaSize
Can be either Global only Global only
RestoreCacheBufferGlobal only Size
SendFullMaster
Global Only
SkipCompressionOnGlobal only CompressedFiles
SortMethod
Global only
StatisticalCpuUsage
Global only
Grid DS-Client Only - Local Setting This parameter only appears for Grid DS-Clients, when you select Local Setting. Parameter Description / Values


Confidential.
DSCBuffer
DS-Client buffer path. This can only be a local path on the selected Leaf-Node of the Grid DS-Client. The DS-Client service account must have full privileges for this location. The Global Value for the DS-Client buffer can be set from DS-User > Setup > Configuration > Parameters Tab.
Linux / Mac DS-Client parameters

Category: Admin on page 468 Category: API Connectivity on page 468 Category: Miscellaneous on page 469 Category: Notification on page 470 Category: Performance on page 470
Category: Admin Parameter Description / Values Specifies the order in which backup sets will be synchronized during Weekly Admin based on the estimated synchronization time: small backup sets first synchronize according to backup set ID big backup sets first (DEFAULT) The maximum number of synchronization activities that can run at the same time during scheduled Weekly Admin. The default value is 1. range 1-8 Skip synchronizations during scheduled Weekly Admin if no database inconsistencies are detected: No = OFF Yes = ON (default) This parameter configures the TCP/IP port(s) DS-Client uses to connect to DS-System. (Normally you should not change this setting unless instructed to by your Service Provider.) range 1-65535, default is 4401 Multiple ports can be configured by separating entries with a space, comma, semi-colon or pipe (|). Invalid configuration causes DS-Client to use 4401.
AutoSync Order
Max AutoSync Number
Skip WeeklyAdmin Sync
System Port
Category: API Connectivity Parameter API IP API Key File API Key Password API Log File Description / Values IP Address to listen for API Connections. Use '0.0.0.0' to listen on all interfaces. SSL certificate/key file to use for the API Server (PEM format) Default Value: /opt/CloudBackup/DS-Client/etc/api.pem SSL certificate/key file passphrase Enter a valid password / passphrase for the SSL certificate/key file specified in the API Key File parameter. Log file to use for the API Server Valid Values: any valid file name Log level to record in the API Server logging file debug: info: warning: (default) error: fatal:
Confidential.
API Log Level

API Port
Port on which to listen for API Connections Default is 4411
Category: Miscellaneous Parameter AllowAutoConfig Description / Values Allow DS-Client to apply Auto-Configuration from the file "config-update.xml". No = OFF Yes = ON (default) Allow auto-upgrade of DS-Client from DS-System when their version does not match. No = OFF Yes = ON (default) Number of days to retain old copies of the DS-Client configuration file. Valid values: 1-99, default is 30 (days)
Auto Upgrade
Config Keep Days
[Linux DS-Clients only] DB2 Client Library DirecSpecify the DB2 client library directory on the DS-Client machine. Please make sure tory the dynamic library <libdb2.so.1> resides in this directory. (RESTART REQUIRED) For example: /opt/ibm/db2/v9.7/lib64/ DefaultLocalTrashKeepDays The default period to keep data in the Local-Only trash. This applies to all defined Local-Only paths for this DS-Client. Valid values: 1-999, default is 7 (days) Determines what DS-User auto-upgrade packages this DS-Client will download from DS-System if they are available. Disabled: DS-User auto-upgrade packages will not be automatically downloaded from the DS-System. Cross-Platform DS-User Auto-Upgrade: DS-Client will download all DS-User autoupgrade packages that exist on the DS-System to the DS-Client directory during Daily/Weekly Admin. Compatible-Platform DS-User Auto-Upgrade: DS-Client will only download the DS-User upgrade packages which are compatible with the OS of the DS-Client.
DS-UserAutoUpgrade
Local DS-VDR Tool's Hard- Hardware cookie of the machine on which the local DS-VDR tool is running. ware Cookie Set by the DS-Client. Do not modify this value. Local DS-VDR Tool's IP Address Address of the machine on which the local DS-VDR tool is running. Valid values: Any valid IP address. The default value is an empty string (no address specified). Path where the Detailed Log for activities on the DS-Client are stored. Detailed Logs are located in this folder, where each backup set has its own numbered sub-folder. Linux default is /opt/CloudBackup/DS-Client/asigra_archivelog/ Mac default is /Library/CloudBackup/DS-Client/asigra_archivelog/ Valid values: Any valid path where the DS-Client can write data. Configures the DS-Client for Multi-Tenant mode. No = OFF (default) Yes = ON
LogArchivePath
Multi-Tenant
If this DS-Client has started in Read-Only (Stand By) mode (no backup / restore allowed), this is the interval at which it will check for an upgrade package from DSReadOnlyUpgradeInterval System. Valid values 1-32000, default is 5 (minutes) Skip Compress (RESTART REQUIRED) Skip compression on files identified as already being compressed. File types skipped are: lzop, zip, standard linux compression, gzip, bzip2, scocompress, bzip, jpeg, jfif, png, and gif. No = OFF Yes = ON (default)


Confidential.
VMware Path Escape (RESTART REQUIRED)
[Linux DS-Clients only] Determines how DS-Client handles VMware data paths, since HTTP is used. URL paths may require path escaping for special characters (e.g. use %26 instead of &). auto (default) - DS-Client tries to determine what path format is required. yes - Always use escape characters in paths no - Never use escape characters in paths [Linux DS-Clients only] For debug purposes. Writes trace logs of any SOAP requests to /tmp on the DS-Client. No = OFF (default) Yes = ON [Linux DS-Clients only] For VMware-VIX backup set type only. Path to the VMware Virtual Disk Library configuration file. This setting is only required if you want to define your own configuration file and specify different settings. You must refer to the VMware documentation for the specific parameters and file format. Default is blank (The default VMware Virtual Disk Library settings will be used). Valid Values: any valid file name
VMware SOAP Debug (RESTART REQUIRED)
VMware VixDiskLib configfile path (RESTART REQUIRED)
Category: Notification Parameter Database Emergency Level Database Stop Level Description / Values Emergency warning level for the available space on the disks where the DS-Client database resides. range 0-10000, default 500 (5%) Stop service level for the available space on the disks where the DS-Client database resides. range 0-10000, default 100 (1%) Warning level for the available space on the disks where the DS-Client database resides. range 0-10000, default 1000 (10%)
Database Warning Level
Local Storage Emergency Available space emergency warning level for Storage root. Level range 1-10000, default 30 (0.3%) Local Storage Warning Level Memory Emergency Level Memory Warning Level Available space warning level for Local Storage root. range 1-10000, default 300 (3%) (in %) Free memory emergency warning level. range 5-100, default 20 (in %) Free memory warning level. range 10-100, default 30
(Hours) - Emergency warning notification interval when space is low (DS-Client DB / PM Emergency Frequency Local Storage / Use Buffer / Memory). range 1-10, default 1 PM Warning Frequency Use Buffer Emergency Level Use Buffer Warning Level (Hours) - Warning notification interval when space is low (DS-Client DB / Local Storage / Use Buffer / Memory). range 4-10, default 4 Available space emergency warning level for Use Buffer root. range 1-10000, default 30 (0.3%) Available space warning level for Use Buffer root. range 1-10000, default 300 (3%)
Category: Performance

Confidential.
Parameter Compression Level
Description / Values For ZLIB Compression only: Enter 0-9, 0 = no compression (faster) and 9 = maximum compression (slower). Default value is 6. Encrypt the data saved in the Local Storage Buffer for Local Storage and LocalOnly backup sets. If enabled, the DS-Clients Private Encryption Key will be used. No = OFF (Default) Yes = ON (GB) - Maximum file size for delta algorithm to apply. The bigger it is, the more memory is needed for delta processing. range 1 to 102400, default is 102400 (32-bit Operating System) range 1 to 1048576, default is 1048576 (64-bit Operating System) Determines when the MaxSession Number parameter applies. Default is Scheduled Activities Only (If this is selected, users can perform OnDemand activities that exceed the maximum concurrent activities.) Valid Values: Scheduled Activities Only or Scheduled and On-Demand Activities Maximum concurrent activities supported by DS-Client. Increase if hardware can support additional processing. range 1 to 99, default is 8 (32-bit Operating System) and 12 (64-bit Operating System) Maximum number of threads for each backup activity. Increase if hardware can support additional processing range 1 to 99, default is 2 (KB) - Minimum file size for delta algorithm to apply. range 8 to 1048576, default is 32. The minimum number of online generations required in order to process files as deltas. Enter 2 or 3. The default value is 3. range 2-3 Defines how often to retry the primary DS-System connection after switching to a secondary connection (in hours). -1 never retries, 0 retries immediately. range -1 to 24, default is 24
EncryptedLocalData
Max DeltaSize
MaxSession Check
MaxSession Number
MaxThread Number (RESTART REQUIRED) Min DeltaSize MinDeltaGen (RESTART REQUIRED) RetryPrimary
Interval (in minutes) that must elapse before the Scan Shares activity will perform a database vacuum on the dslanfiles database. This only removes unnecessary data Scan Shares Vacuum Freto make the database more compact. It does not affect the information gathered quency from the scan. range 1 to 240, default is 30 [Linux DS-Clients only] Interval (in minutes) that must elapse without response before DS-Client considers the connection to a System i server to have timed out. System i Connection Tim range 1 to 600, default is 60 eout Note: The timeout is subject to change (upwards) during backup and restore, based on the size of the data being processed, however it will not be reset lower than this value.
See Also
DS-Client Advanced Configurations on page 47


Confidential.


Confidential.
Access to DS-Client & Remote Management of DSClient

Creation Date: October 14, 1997 Revision Date: December 03, 2007 Product: DS-Client
Summary
The DS-Client software runs on Windows, Linux, and MAC computers (refer to the corresponding installation guide for supported Operating System versions). All interactions with the DS-Client are performed via the DS-User software, which is a GUI interface for DS-Client administration. The DS-User software can run on any computer with the TCP/IP protocol installed. The DS-User software can administer a DS-Client running on a local or remote computer (thereby providing remote management over a TCP/IP connection, and even over the Internet). The DS-User (or user that uses it) is required to provide valid credentials to the DS-Client for authentication before it is able to perform any activity. The authentication method that the DS-Client uses for user access validation depends on the DS-Client platform. There are two different DS-User products that are included on the installation DVD: 1. Win32 DS-User: installed by default by the Windows DS-Client installation process. This only works with Windows DS-Clients. 2. Java DS-User: installed by default on Linux and Mac by DS-Client installation process. (It can also be installed on Windows computers using the separate DSUser-Java installation.)
Access to DS-Client using Win32 DS-User

Win32 DS-User can only connect to Windows DS-Clients. Only one connection per GUI instance is possible.
Access to DS-Client using Java DS-User

Java DS-User also allows users to connect to multiple DS-Clients from the same GUI instance, allowing them to switch easily between DS-Client management sessions with one click. The DSClients can be on any platform (Windows / Linux / Mac), as long as they are visible on the network from the DS-User computer.
DS-Client authentication of DS-User connections

A DS-Client performs logon validation (for DS-User sessions) with the local or domain user account database (if applicable). For Windows DS-Clients, by default, only administrators or backup operators are allowed access to the DS-Client. For Linux and Mac DS-Clients, by default, only "root" users are allowed access to the DS-Client. An administrator can configure the DS-Client with different user and group roles for access to DSClient. A DS-Client allows multiple, simultaneous DS-User connections, with the same or different authentication. See Configure DS-Client User and Group Roles on page 43.


Confidential.
Note
1. DS-Client uses the DS-User credentials as default credentials for network resources when creating new backup sets.


Confidential.
Activity, Event and Audit Logs

Creation Date: October 22, 1997 Revision Date: November 30, 2007 Product: DS-Client
Summary
The DS-Client software logs all information about the activities performed (scheduled and demanded) in the DS-Client database. This information is organized into four categories and can be used to troubleshoot, monitor and report DS-Client activities. The DS-Client keeps this information in its database for a period specified in the Keep DS-Client logs' parameter of the DS-Client configuration (DS-User > Setup Menu > Configuration: Parameters Tab).
Activity Log
The Activity Log contains a high-level summary of a particular DS-Client's activities (such as backup or restore). This information can be viewed using the Activity Log Viewer, which contains the following fields:
User Name Type Owner Description Errors Start End Duration Files Online Completion ID Shows the name of the user that performed the activity (empty if scheduled). Shows the type of activity (backup, restore, delete, ...). Shows the name of the Owner of the Backup Set Shows the node, and backup set name. Shows the number of errors that occurred during activity. Shows the date and time the activity started. Shows the time of day the activity ended. Length of time between the activity's start and end times. Shows the number of files that were affected by the activity. Shows the amount of data affected by the activity. Shows the completion status of the corresponding activity. An Activity would have an incomplete status, if it was stopped by an event that did not allow it to complete. Such events are: time limit, user stop, amount limit, too many errors, internal error, lost connection/didn't connect to the DS-System and failed to connect to network resource. Activity's unique identification number.
Event Log
The Event Log contains detailed information (events) which was recorded during a particular activity. It contains mostly error events that occurred during an activity. The Event Log also contains entries for all DS-User logon/logoff attempts and errors that occurred outside of any activity (like in schedule module). This information can be viewed with the Event Log Viewer or from the Activity Log Viewer and it contains the following fields:
Icon Time User Category Event # ID Text Description Shows the event type (Information, Warning or Error) Shows the date and time that the event occurred. Shows the User Name of the user (if any) associated with the event Shows the category of the event (database, socket, system, ...) Shows a numeric error ID code. Unique ID numbers used to distinguish one activity from another. May display additional information associated with the message (ex: the IP address of a connection). Shows a description of the event.
Confidential.

Detailed Log
The Detailed Log contains a log of all files that were affected by a specific backup or restore activity. Only those activities whose 'Detailed Log' flag is set, will have that information recorded. This is set as follows: Scheduled backups: Backup Set Properties > Options Tab On-Demand backups: Backup Wizard > Select options for demand backup screen Restores: Restore Wizard > Select Restore Options screen. Detailed Log information can be viewed from the Activity Log Viewer.
Audit Trail
The Audit Trail contains a log of all modifications (additions, deletions and updates) made to the DS-Client configuration information. This information includes DS-Client Setup, Backup Set, and Schedule information. The DS-Client administrator can use these logs for troubleshooting and auditing purposes. This information can be viewed with the Audit Trail and it contains the following fields:
Time User Operation Table Description Shows the time the modification occurred. Shows the name of the user who performed the modification. Shows the type of modification performed. Shows the table that was modified. Shows details of the modification that occurred.
Note
1. If a DS-Client fails to start due to a configuration, database or other error, it will record errors in the Operating System Event Log:
For Windows, they can be seen in the Event Viewer. For Linux, this is either /tmp/dsclient.err, or /tmp/dsclient.out, or /var/log/messages. For Mac, this is either /Library/Logs or /var/log.


Confidential.
Custom Reports
Creation Date: February 11, 2008 Revision Date: May 12, 2010 Product: Third-Party (For information only)
Summary
The Custom Reports feature allows you to create your own reports, based on the data provided from the DS-Client database tables. This feature is meant for advanced users. This requires a third-party application (either JasperReports or Crystal Reports), which means you must have the development resources to create and compile the custom report templates. The basic steps for this feature are as follows: Step 1. Create Customized Data on page 392 After this step is completed, you will have a Data Set file (XML) containing the structure and data you chose for export. You can actually use the Data Set file to generate a one-time report. If you want to regularly generate a custom report, you must use the structure of the data fields to create and compile a template file. Step 2. Create Customized Report (with Third-Party application) on page 395 This article gives general instructions on how to make the template. Refer to the corresponding third-party documentation for the most up-to-date information. Step 3. View Customized Report on page 396 Once you have created a custom report template, you place it in the \report subfolder of the GUI you are using. The GUI will then be able to generate the custom report. Creating the customized report template requires a third-party application. This depends on the type of GUI you plan to use to view the report: Java GUI (JasperReports) on page 477 Win32 GUI (Crystal Reports) on page 486
Java GUI (JasperReports)

You need to download and install the free JasperReports application from http:// www.jasperforge.org. These examples use v.3.7.0 of the JasperReports software. 1. With the exported Data Set (XML file), you must now use the third-party jasper tools to create your custom report using the fields from the Data Set. Create a sub-folder named report in the folder where the DS-User GUI (dsuser.jar) you want to use is located. Normally, this is in the DS-Client installation path. The default for Windows is C:\Program Files\CloudBackup\DS-Client. The default for Linux is /opt/CloudBackup/DS-Client/. The default for Mac is /Library/CloudBackup/DS-Client/. Copy the exported Data Set (XML file) to this directory (i.e. backupset.xml).


Confidential.
2. Open the Jasper Report Designer.
3. Start a new report (File > New). The New File Wizard appears.


Confidential.
4. Select the Blank Letter template and click the Open this Template button. The Name and Location screen appears.
Enter the Report name (e.g. backupset). Click Browse to select the location where the report will be created. When you have made your selections, click Next. A Finish summary page appears. Click Finish to create the report. 5. The new document (backupset.jrxml) appears in the designer.
Report Datasources button
Compile Report button Edit Query button


Confidential.
6. Click the Report Datasources button. The Connections / Datasources dialog appears. This dialog allows you to configure the data source for the template.
7. Click New to create a new data source. A wizard appears.
8. Select XML file data source in the wizard, and click the Next button.


Confidential.
9. In the following screen:
Input the data source name (i.e. backupset). Select the XML data file (the one that was exported in Step 1. Create Customized Data on page 392). Select the Use the report XPath expression when filling the report option. Click Save to close the dialog. 10. Select the Default checkbox for the backupset, then close the Connections / Datasources screen.


Confidential.
11. In the Jasper Report Designer, right-click on the report name (i.e. backupset), then select Edit Query.
12. The Report Query dialog appears.
13. Select the Report Query Tab. Set the query language to XPath. Input a query in the form /<root_element>/* in the text edit area. (In this example backupsets is the root element of the XML data file, thereby requiring the query /backupsets/*.)


Confidential.
14. On the right-side of the dialog, you will see the structure of the XML File.
Note: The root element name may change for different XML data files. 15. Under the backupsets (root element), expand the Item branch and you will see some sub-items in the tree. These are the available data fields that you can use in the custom report.
root element input query here
field table data fields
Right-mouse click on an item you want to add to the custom report, then click Add node as field. Continue adding items as required until you are finished. Click OK to close the dialog.


Confidential.
16. Now you can see those fields in the Report Inspector panel of the designer.
17. By default, all the fields are set to the java.lang.String type. For some fields this may not be a suitable format. It will be apparent when you generate a test report. If you need to modify the Field Class Type to the correct type, go to the field properties panel on the right side of the designer. You can set the correct field data type from the Expression Class list. 18. Start designing the custom report. 19. You can preview your design with the following commands: Preview menu > Select preview format, then click the Preview button. 20. When you are satisfied with the report design, click on the Compile Report button. The report will be compiled into a .jasper file that is generated in the report directory created in Step 1 (e.g. C:\Program Files\CloudBackup\DSClient\report\backupset.jasper).


Confidential.
21. Now you can generate the custom report from that DS-User installation. (To use another DS-User GUI from a different computer, you must copy the same .jasper file to the report directory in the corresponding DS-Users installation path.)
See Step 3. View Customized Report on page 396.


Confidential.
Win32 GUI (Crystal Reports)

You need to purchase and install the Crystal Reports application from http:// www.crystaldecisions.com. These examples use v.10 of the Crystal Reports software. 1. With the exported Data Set (XML file), you must now use the third-party Crystal Reports tools to create your custom report using the fields from the Data Set. 2. Open the Crystal Report and create a new Report.
Select Blank Report in the Welcome page. Click OK to continue.


Confidential.
3. Click Database menu > Database Export. The Database Expert dialog appears.
4. Expand the Create New Connection item. Select Database Files. 5. Expand Database Files. An Open File dialog will appear if this is the first time you create a database file data source.
Otherwise, Double click Find Database File below the Database Files item.


Confidential.
6. Select the XML data file (the one that was exported in Step 1. Create Customized Data on page 392). Click Open to close the dialog.
7. In the Database Expert dialog, one new sub-item appears in the tree under the Database Files item. Select Item in the Available Data Sources list and click the >


Confidential.
button. The new database file appears in the Selected Tables list.


Confidential.
8. Click OK to return to the main window.
9. In the Field Explorer, you can find the database fields in the XML file. 10. Now you can start designing the custom report. Note: All the fields are string in the table. You may need to create some Formula fields for fields that are not string.
11. After you finish designing, you will get a .rpt file. Copy this file to report sub-directory in the DS-User installation path. 12. Now you can generate the custom report from that DS-User installation. See Step 3. View Customized Report on page 396.
See Also
Custom Reports on page 392


Confidential.
Administrative Processes
Creation Date: April 29, 1997 Revision Date: October 04, 2011 Product: DS-Client
Summary
The DS-Client software has been designed for unattended operation, which is both self-tuning and self-maintaining. In order to accomplish these tasks, the DS-Client performs regular administrative processes. These processes clean, tune and backup the DS-Client database, create statistical data, and verify backup sets with the DS-System's actual online storage.
Types of Administrative Processes

Type Local Description Performs activities that do not require a connection to the DS-System. This type of administrative process is always performed and cannot be disabled. (A Local Admin runs every time that the DS-Client starts, once every 12 hours since the previous Admin, or every 24 hours.) Performs all Local activities (see above), a verification of backup sets (see Detailed Activities below) and transfers the DS-Client database dump to the DS-System. A Daily Admin process can be disabled or configured to run at a specific time (Setup Menu > Configuration > Parameters Tab). Performs all Daily activities and a low-level synchronization of backup sets (see below). A Weekly Admin process can be disabled or configured to run at a specific date and time (Setup Menu > Configuration > Parameters Tab).
Daily
Weekly
Configuration and Scheduling of Administrative Processes

Default Configuration The default administrative configuration (which can be changed from Setup Menu > Configuration > Parameters Tab) will have the following settings: The Daily Admin process is scheduled to run once every day between 8PM and 6AM. (See note below.) The Weekly Admin process is scheduled to run once a week between 8PM Friday and 6AM Monday. (See note below.) Note: In order to distribute the Administrative Process load from many DS-Clients, the exact (default) start time is randomly determined with an algorithm based on the DS-Client number, which results in a time that is some interval of 15 minutes (e.g. 9:30 or 01:45). Automated reboot An automated system reboot can be performed after the admin process. This option is turned off by default, but can be reconfigured (Setup Menu > Configuration > Parameters Tab). It is recommended that this option be turned on if the DS-Client computer performs unattended scheduled backups and does not normally shut down. This will refresh computer resources and memory leaks (if any have occurred). Execution of Administrative processes No other activities (backup, restore, etc.) are allowed while an Admin process executes. Therefore, any demand activity will be rejected. If an activity is executing at the time the admin process is scheduled, the admin process will wait for all activities to terminate. During this time (waiting for activities to terminate) new activities can still be executed. Therefore it is possible that the scheduled Admin process never gets the opportunity to run (i.e. in the unlikely event that you have scheduled backups that run 24hrs/7days a week).


Confidential.
Who should perform Administrative processes? It is recommended that you schedule the DS-Client to perform Daily and Weekly administrative processes wherever possible for all DS-Client configurations (i.e. Typical or Custom installation on LANs as well as on Standalone PCs). If it is not possible to schedule Admin processes, you should manually execute a Daily or Weekly Admin occasionally (Setup Menu > System Activities Administration dialog).
Administrative Process Activities Description

Activities Matrix The following table shows administrative activities in the order that they are performed, and the administrative processes that perform them. The DS-System column indicates whether a connection to the DS-System is required for that activity.
Activity 1. Prepare database dump 2. Clean database 3. Update statistical data 4. Expand database (if necessary) 5. Verify backup sets 6. Transfer database dump 7. Synchronization (Normal) 8. Send daily E-Mail notification X X Local X X X X Daily X X X X X X Weekly X X X X X X X X X X X DS-System
Detailed Activities Description 1. Prepare database dump. [MS SQL Server] This activity depends on the selection for Keep DS-Client database dump file (Setup Menu > Configuration > Parameters): a) [Do not delete] Save the previous dump, dump the DS-Client database and dsdelta database, run database consistency checks (DBCC). If a fatal error occurs, restore the previous dump, otherwise the previous dump will be deleted and only the current dump will remain in the DS-Client buffer. b) [Delete after successful backup] Save the previous dump (if it exists). Dump the DS-Client database and dsdelta database, run database consistency checks (DBCC). If no errors occur, remove the previous database dump (if it exists) from the DS-Client buffer before connecting to the DS-System. If step 6 (Transfer Database Dump) is successful, then remove the current DS-Client database dump from the DS-Client buffer. c) [Always delete] Dump the DS-Client database and dsdelta database, run database consistency checks (DBCC). After the Daily/Weekly Admin process is finished, delete the database dump. Note: For more details, see Database Dump method (MS SQL Server) on page 493. [PostgreSQL] This step is not performed. 2. Clean the databases. Delete old history logs (activities, events and statistics), drop unused tables and delete unused records. 3. Update statistical data Update statistical information for each backup set (number of files and online amount). Update statistical information used by the storage summary. 4. Expand database (if necessary).

Confidential.
[Only applies to the free Microsoft SQL Server Express versions (2005, 2008 and 2008 R2). This step is not performed for full (purchased) Microsoft SQL Servers.] If DS-Client database is above its DBHighWaterMark parameter (DS-User: Setup Menu > DS-Client Configuration > Advanced Tab), expand the database by creating a new, sequential expand<nnnn> database. Move backup set(s) from the database that is over its high water mark into the new expanded database. This is done sequentially, starting with the largest backup set, until the database falls below the high water mark. Note: For more details, see DS-Client Database (Automatic Expansion) on page 421. [PostgreSQL] This step is not performed. 5. Verify backup sets. Send a list of all backup sets to the DS-System. The DS-System will send back a list of backup sets that: a) Do not exist on the DS-System's disk or b) Exist on the DS-System's disk but were not included in the DS-Client's list Update the information needed to recover backup sets falling into category 'b'. 6. Transfer database dumps. [MS SQL Server] Transfer database dumps to DS-System if Activity 1 was performed successfully. [MS SQL Server] Delete database dumps if Activity 1 (b) or (c) was selected (from Setup Menu > Configuration > Parameters). [PostgreSQL] Instead of transferring a dump, the database is backed up via Pipe to DS-System. 7. Synchronization (Normal). Perform synchronization check for all backup sets that are not in category 'a' or 'b' of Activity 5. (Note this is the same as a 'Normal' synchronization. However, any synchronized files will retain an 'active' backup status.) 8. Send daily E-Mail notification. If the DS-Client is configured for E-Mail notifications with Daily Notification on, a summary of backup activities will be sent to the administrator, showing a summary of what occurred since the last admin process.
Database Dump method (MS SQL Server)

To speed up the Daily Admin process, Windows DS-Client uses differential backups if a full database dump exists on the DS-System. DS-Client will always perform a full database dump during Weekly Admin. If Weekly Admin is disabled, a full database dump is performed during Daily Admin every 6 days (the full backup rotates the day on which it occurs). A differential backup creates a copy of all the pages in a database modified since the last full database backup. The database dump of dsclient and dsdelta will be composed of the following: xxxxxxxxxxxx.dmp (full backup) xxxxxxxxxxxx_diff.dmp (differential backup) dsdelta.dmp (full backup) dsdelta_diff.dmp (differential backup)


Confidential.
Weekly Admin and Synchronization

Creation Date: September 14, 2007 Revision Date: October 02, 2007 Product: DS-Client
Summary
Weekly Admin can be configured to run automatically, once a week, based on the specification in the DS-Client Configuration - Parameters Tab (See: Configure the DS-Client Parameters on page 39). The Weekly Admin performs all the tasks of a Daily Admin, and also performs a synchronization of backup sets. The type of synchronization depends on how the Weekly Admin is run: Synchronization during Scheduled Weekly Admin on page 494. Synchronization during On-Demand Weekly Admin on page 494.
Synchronization types
The following backup set synchronizations can be performed by the Weekly Admin process: Normal: Compare and update where necessary, the DS-Client backup log (database) with the DS-System's Online storage information. Check only (On-Demand only): Perform only a check of the synchronization between the DS-Client's backup log and the DS-System's Online storage. This will only identify whether inconsistencies exist (i.e. no corrective action will be taken.). DS-System based (On-Demand only): Update the entire DS-Client backup log with the DS-System's Online storage information.
Synchronization during Scheduled Weekly Admin

Scheduled Weekly Admin performs a normal synchronization on any backup sets that have already been marked Out of Sync. In addition, Windows DS-Client will perform normal synchronization on a backup set if it detects any database inconsistencies that might cause it to be Out of Sync. Note: This does not apply to Linux DS-Clients. If you want the scheduled Weekly Admin to perform the synchronization on all the backup sets, you must configure the AdminSkipSync parameter in the DS-Client Advanced configuration options (See DS-Client Advanced Configurations on page 47.).
Synchronization during On-Demand Weekly Admin

On-Demand Weekly Admin is requested from Setup menu > System Activities > Weekly Admin: Run Now (See Run a Weekly Admin immediately on page 362.). This opens the Weekly Admin Options screen. The default is to synchronize all backup sets with a normal synchronization. You can also select how many simultaneous synchronizations to run. If Synchronize all sets is unchecked: Weekly Admin performs a normal synchronization on any backup sets that have already been marked Out of Sync.

Confidential.
In addition, Windows DS-Client will perform normal synchronization on a backup set if it detects any database inconsistencies that might cause it to be Out of Sync. Note: This does not apply to Linux DS-Clients.
Weekly Admin for DS-Client database backup / recovery If Weekly Admin was run specifically to provide you with a DS-Client database backup that you intend to recover immediately, and you notice that the Weekly Admin performed synchronization on any backup sets, you should run the Weekly Admin again to obtain the latest and most accurate backup of the DSClient databases. This will avoid your having to go through the synchronization process again after the database is recovered.
See Also
Run a Weekly Admin immediately on page 362 Administrative Processes on page 491 Recovering the DS-Client Database on page 718


Confidential.
Admin Processes with Grid DS-Client

Creation Date: March 26, 2008 Revision Date: March 26, 2008 Product: Grid DS-Client (Windows)
Summary
This article explains the specific differences that occur when a Grid DS-Client run Daily Admin or Weekly Admin activities. For a more general description, refer to the Knowledge Base article Administrative Processes on page 491.
Description
For standalone DS-Clients, Daily / Weekly Admin activities instruct the MS SQL Server where the DS-Client databases reside to save a copy of the DS-Client databases in the DS-Client Buffer. By default, the DS-Client buffer is located in the folder configured as the default Operating System temporary folder (usually C:\Windows\Temp). For Grid DS-Clients, Daily / Weekly Admin activities instruct the MS SQL Server where the DSClient databases reside to save a copy of the DS-Client databases in the DS-Client Buffer of the node that performs the Daily / Weekly Admin activity. The Daily / Weekly Admin activity is allocated to a node with a lower load by the Main Node of the Grid DS-Client. By default, the DS-Client Buffer folder for a node in a Windows Grid DS-Client is the folder configured as the default Operating System temporary folder (usually C:\Windows\Temp). The DSClient Buffer can be configured for each node in the Grid DS-Client using the DS-Client Advanced Configuration options (See DS-Client Advanced Configurations on page 458.).
See Also
Grid DS-Client (Windows DS-Clients) on page 70 Grid DS-Client on page 426 DS-Client Advanced Configurations on page 458 Administrative Processes on page 491 DS-Client Buffer on page 500


Confidential.
Backup Set Migration

Creation Date: April 30, 1997 Revision Date: July 30, 2004 Product: DS-Client
Summary
The migration process for backup sets has two purposes: 1. It allows users to map an existing backup set to a different computer (other than the one the backup set is currently on). 2. It allows users to update crucial information (i.e. computer name, operating system) about a backup set, if such a change occurred to the backup source computer.
Details
When creating backup sets, the DS-Client service automatically collects information about the backup source computer (i.e. operating system, file system). Based on this information, the DS-Client presents the available backup options for the selected computer. Each time a backup is performed, the DS-Client service automatically updates part of the collected information (i.e. operating system version, file system type). However, you must migrate the backup set if you wish to keep your backed up data in any of the following situations: The backup source computer's name has been changed. The backup source computer's Operating System has been changed. The backup directories or files have been moved to another computer.
Restrictions
1. You cannot migrate a backup set containing the Registry, NDS or Bindery to a different Operating System. If you wish to migrate a backup set containing the Registry, NDS or Bindery to a different Operating System, you must first delete all generations of these special backup items from the backup set (with the Delete Wizard). Then, you must remove these items from the backup set's Selected Items for Backup ('Directories Tree' dialog). 2. For each share selected for backup (or backed up), you should select the destination share on the computer to which you are migrating. The DS-Client service restricts the migration to a one-to-one match (i.e. you cannot select the same destination share for two different source shares). 3. When migrating items from one file system to another, you should verify the backup set's Permissions and Streams options are consistent with the new file system (i.e. these options must be unchecked if you migrate from NTFS to FAT32).


Confidential.
When to Migrate a Backup Set

Creation Date: October 31, 2007 Revision Date: October 31, 2007 Product: DS-Client
Summary
Asigra Cloud Backup DS-Client stores information about the source machine that is being backed up with a specific backup set: machine name, machine IP address, Operating System version, etc. Because of these specifications, you may need to migrate a backup set to respecify those settings if they are changed on the source. The following scenarios require migration: Scenario # 1: Source computers Operating System has been upgraded on page 498 Scenario # 2: Source computers Machine name or IP address has changed on page 498 Scenario # 3: Source data has been moved to a different machine on page 499 Scenario # 4: Orphaned backup set was recovered by the DS-Client from the DS-System on page 499 Scenario # 1: Source computers Operating System has been upgraded If the Operating System of the source machine (for the backup data) has changed, DS-Client will fail to perform the backup activity with the following message:
Server changed from Windows 2000 to Windows 2003. Please create a new backup set for this version.
In order to continue to backup with the same backup set, you must migrate the backup set, and re-select the same computer (with the upgraded Operating System). Otherwise, you can create a new backup set and start backing up the data again. IMPORTANT NOTES: Not all Operating System upgrades will allow a backup set migration. For example: Upgrading from Windows NT to Windows 2003 will not allow you to migrate the registry to system state and services database. In these cases, you must create a new backup set. If you perform a Bare Metal Restore from a migrated backup set, you must make sure that you only restore Operating System files from the same backup session (if applicable). Otherwise, you may restore a combination of incompatible files from different versions of the Operating System. Scenario # 2: Source computers Machine name or IP address has changed If the source computers machine name or IP address has changed, the DS-Client will fail to backup with the message:
The network name was not found.
Any backup sets created with the previous machine name or IP address must be migrated. Otherwise, you can create new backup sets and start again.


Confidential.
Scenario # 3: Source data has been moved to a different machine If the actual data has been moved from one server to another server, you can migrate the backup set, specify the new machine information and continue backing up with the same backup set. However, you must pay attention to the following items: If you move data from one server to another and you keep the same path format for that data, then DS-Client will backup incremental data. For example: if data resides on e$\data and you moved it to e$\data or c$\data on the new server, then DS-Client will process incremental backups for those files. If you move data from one server to another and you do not keep the same path format for that data, then DS-Client must perform an initial backup (which will take longer). For example: if data resides in e$\data and you move it to e$\newlocation\data or c$\destination\newlocation\data on the new server, then DS-Client will process new masters for the files found in the new location. Scenario # 4: Orphaned backup set was recovered by the DS-Client from the DS-System See Knowledge Base Article: Recovering 'Orphaned' Backup Sets on page 720.
See Also
Migrate a Backup Set from one computer to another on page 194 Backup Set Migration on page 497


Confidential.
DS-Client Buffer
Creation Date: October 14, 1997 Revision Date: January 11, 2010 Product: DS-Client
Summary
The DS-Client buffer is a temporary storage location on the DS-Client computer. This directory can be seen or changed from the DS-User > Setup > Configuration > Parameters tab. For more information, see: Configure the DS-Client Parameters on page 39. When the Use Buffer option is employed: 1. Backup files are transferred to the buffer location first, then 2. The backup/restore operation is performed (data is processed through the DS-Client). This minimizes the time that the LAN must support the additional backup/restore traffic. It is particularly useful if the DS-Client's connection to the DS-System is much slower than its connection with the LAN. The DS-Client buffer can also provide temporary storage as the database dump location for MS SQL and MS Exchange database backups (this avoids the need for extra disk capacity on network servers). Adequate disk capacity for your backup needs is required on the drive containing the DS-Client computer's buffer directory. You must also make sure that the buffer storage location supports the same structure as the source. For example, if your DS-Client buffer is on a Linux File System, the maximum number of sub-directories allowed within a single directory is 32767. If you try to backup a path that holds more than this number of sub-directories using the DS-Client buffer, it will fail since it exceeds the maximum number of sub-directories allowed. Essentially, you must to ensure the DS-Client buffer has enough space to hold all the data AND can support the same tree structure as the source.
Types of DS-Client activities that use the DS-Client Buffer

Backup: Speeds up backup operations by copying files to DS-Client buffer first (at LAN speed) and then transferring files to the DS-System (at DS-System connection speed). Minimizes time that the network resource is used for the backup operation. Restore: Speeds up restore operations by restoring files to the DS-Client buffer first (at DS-System connection speed) and then copying files to the network resource (at LAN speed). This minimizes the time that the network resource is used for the restore operation. The DS-Client always copies the MS Exchange Server database(s) to the DS-Client Buffer first, and then transfers the files to the DS-System. For extremely large MS Exchange Server databases (that would require too much disk space), you can specify that backups be performed with the DS-Client Pipe option. When performing backups/restores of MS SQL Server or Oracle Server databases with the 'Dump to DS-Client Buffer' option, database dump(s) are created on the DS-Client Buffer and then transferred to the DS-System. This provides disk space for database dumps on the DS-Client computer and saves the need for extra disk capacity on the database servers.
Use Buffer
MS Exchange Server
MS SQL Server, Oracle Server


Confidential.
Notes
1. The DS-Client deletes all files from the DS-Client buffer after each activity, regardless whether or not the operation was performed successfully. 2. Do not select the Use Buffer option with backup sets that have data on the DS-Client computer. Use Buffer copies backup files to the DS-Client buffer. From there, they are processed for backup by the DS-Client. If the DS-Client buffer directory is part of a backup set, problems may occur since the Backup may catch a loop that reads the same directories being copied for backup. 3. DS-Client Buffer and Performance: The DS-Client Buffer is also used by activities that access DSClient Database to create temporary files for bulk insert (for optimization of processing). If a backup set is not assigned enough credentials to Create/Delete/Read/Write files in the DS-Client Buffer directory, bulk insert operations will fail and a regular insert is used instead. To maximize the speed, we recommend providing enough credentials for all backup sets to access the DS-Client Buffer directory. 4. Backup sets configured to use the DS-Client buffer automatically benefit from the Block-Level Resume feature (See Block-Level Resume on page 676.).


Confidential.
DS-Client performance considerations

Creation Date: November 17, 1997 Revision Date: March 21, 2008 Product: DS-Client
Summary
The DS-Client software is designed to perform unattended, scheduled backups of single PCs or an entire LAN. To maximize the DS-Client's performance, there are some issues that you should consider.
Considerations
In order to maximize backup speed, consider the following points:
Use the latest supported Windows Operating System Running the DS-Client software on the latest supported Windows Operating System will boost backup speed, since the DS-Client software is able to take advantage of features like asynchronous I/O processing and multi-processor support.
Since the DS-Client software performs compression and encryption during the Provide adequate CPU and backup, it is CPU-intensive. Use the DS-Client 'Load Summary' feature to determemory mine CPU and memory utilization during backups. If it is very high, you should consider a more powerful CPU and/or more memory for the DS-Client computer. Use multi-processor systems The DS-Client software is designed to scale on SMP systems, when installed on Windows. Running the DS-Client on such a system provides large performance boosts when compared with a single CPU configuration. The DS-Client uses a database to store backup logs (catalogs). When using the DS-Client in a LAN configuration that can exceed a few hundred thousand backup files, the database update/retrieve speed will affect backup performance significantly. Use MS SQL Server as the DS-Client database to provide faster update/ retrieve performance.
Use MS SQL Server
When running the DS-Client on a powerful system (e.g. dual CPU), LAN connecProvide 100 Base or higher tions of 10 mbps (Ethernet) or 16 mbps (Token Ring) become a bottleneck. Provide LAN connections. a faster LAN connection to significantly improve the backup speed. Schedule appropriate number of backups Scheduling too many backups at the same time will increase overall backup time due to CPU, memory and LAN connection over utilization. 'Load Summary' feature of DS-Client can be used to determine CPU and memory utilization during backups.


Confidential.
LAN Storage Discovery Overview

Creation Date: August 18, 2006 Revision Date: May 10, 2010 Product: DS-Client
Summary
For step-by-step instructions, see the section: LAN Storage Discovery Tool on page 329
It is very useful to analyze the LAN storage before using any backup application. The most important information is the redundancy (duplication) factor, and the frequency of data changes. The main purpose of the LAN Storage Discovery Tool is to provide customers with a clear view of information about their LAN by scanning and analyzing the LAN files. LAN Storage Discovery is a tool integrated in DS-Client, designed to analyze the LAN storage. To analyze the LAN, you must first discover the shares on the LAN (or a particular part of the LAN) using a list of credentials you provide. Then, the share list is arranged, defining which shares to scan and how they will be scanned. Finally, the scan process is started for the files on the LAN. Tools to manage and monitor the discovery and scan processes are also provided. The scan process runs on DS-Client and can be scheduled. Several reports are generated to analyze the scanned storage: Duplication, growth trends, access reports, file type distribution, etc. Summary and detailed reports are provided, as well as an export feature that you can customize.
LAN Storage Discovery Tool

This section outlines the features of the LAN Storage Discovery Tool. Discovery on page 504 Scan process on page 504 Reports on page 504 Unix Support Limitations (Windows DS-Clients) on page 507 Unix Support Limitations (Linux DS-Clients) on page 507


Confidential.
Discovery
1. Configure the range (extent) of your LAN that will be analyzed. This range is a collection of items. Each item can be a network provider, a domain, or a computer. A list of credentials can be provided for the discovery / scanning process. For Unix DSClients, an additional level of authentication for credentials is available. 2. The discovery process will automatically analyze the overlapping of shares, if the shared path can be retrieved. The overlapped shares will be disabled for scanning by default to avoid false duplication counting. 3. LAN Storage Discovery (Windows DS-Client) supports the following network providers: Microsoft Windows Network NetWare Services Hummingbird NFS 4. LAN Storage Discovery (UNIX DS-Client) can discover shares on the network through: NFS SSH
Scan process
1. The scan process is applied to the list of shares found by the discovery process. 2. The discovery process automatically disables some shares: if the share is covered by other shares; if not enough credentials were provided to retrieve all necessary information from the share if the share is not supposed to be scanned (e.g. CD/DVD, etc.) Note: The status (disabled / enabled) can be manually changed from the GUI. 3. By default, the credentials used to discover the share are also set as the scan credentials for that share by the discovery process. However, the credentials used for scanning can be changed for particular shares from the GUI. 4. The scanning of a share to follow reparse point (Microsoft Windows only) is configurable from the GUI. 5. To speed up the scanning process and reporting, the scanning process can be configured from the GUI to skip files that are smaller than a specific size. 6. The number of scanning threads is also configurable from the GUI (to provide scalability). 7. The scan process can be scheduled, or started on demand. The best practice is to schedule it to run over a period (i.e. a few weeks) to get more accurate statistical information on data growth and changes. 8. A Scan Monitor is available to give a real-time overview of the scan process.
Reports
The reports can be divided into three categories: One-click generated reports on page 504 LAN File Summary on page 506 Other reports on page 506 One-click generated reports

Confidential.
The One-click generated reports are the most important ones. Windows DS-Clients have 12 reports and UNIX DS-Clients have 8 reports. The generated reports will be saved as files in HTML and Microsoft Excel format. Many of them can be customized. The reports included are:
Report Share usage Largest Files Largest Duplicates Ownership (Windows DS-Client only) File Type Distribution Partition Size (Windows DS-Client only) Description Reports the total files and size (all and duplicated) for each share. List top n (default is 100) largest files. Also report the percentage size compared to the entire LAN. List top n (default is 100) largest duplicate files. Also report the total duplicate file number and the percentage of this number as well as the total size of the top n files comparing to the entire LAN. Reports the total storage occupied by each owner for each share as well as the total. Select top n (default is 10) file types, sorted either by space or file number (default is by space). For each file type, select top m (default is 100) largest files from the entire LAN. For each partition, report the total, free, and used space.
For each share, and each interval (5 intervals are provided: <1 Day, >1 Day, >1 Week, >1 Month, >1 Year), report the top n (default is 100) largest files whose Access Report / Dormant Files last access time is within the specified interval. There is also a summary report of the total size and files for each interval of each share. Growth and Modified Files SQL Server Size (Windows DS-Client only) Exchange Server Size (Windows DS-Client only) Index of Generated Reports All Duplicate Files Reports how many files and size created/modified for each share, each day over the specified period (default is 14 days). For each computer, how much space (total, free, used) are for SQL Server. Report all .edb and .pst files. An index of all generated reports. A list of all duplicate files. By default this report will not be generated.


Confidential.
LAN File Summary This provides an overview, as well as detailed (up to file level) information of the scanned files on the LAN. Complicated filters are also available so that it is possible to analyze a particular group of files.
Report Description An overview of the total files and size for the following categories: All files Duplicate files Duplicate groups Changed and new files Unchanged files Not accessed files The changed / unchanged, new, not accessed are determined by the parameter last n days. The default is last 30 days. This is similar to the global view. However, it is for each share based on the specified condition. This condition is the combination of the following: Last n days: to determine changed/unchanged, new, not accessed. Filter: like *.c* on file name Duplication: Only the files with duplicates equal to or greater than the specified number will be counted. Share: Specify a group of shares to be considered. Show the detailed information of the files corresponding to the selected row from the global / filtered view. Show the pie charts for the selected row from the global / filtered view. The charts could be based on size or file numbers for all categories (Duplicated, Unchanged, etc.). Show all files that are duplicated with the selected file.
Global view
Filtered view
Show Details Charts Show Duplicates
Other reports These reports are already included in the One-click generated reports. However, they can be customized in a more powerful way from DS-User > Reports Menu > LAN Storage Discovery: report_name.
Report Large Files report Description List top n (default is 100) large files whose duplicate count is at least equal to the given value (default is all files) for the specified share or all shares. There are two kinds of reports. The Top Report shows the top n extensions ordered either by size or by file numbers for the specified range (a share or all shares). The Customize Report asks for a list of specific extensions and the range (specific shares). The total size and file numbers are also reported. Reports the files and size for the given intervals, set within the given range (specific shares). An interval could be a number of days, weeks, months, or years. User provides the period for analysis: intervals (in days), range (specific shares), and type (total or new). Report shows the files and size for each interval that falls within the specified period. Reports the files and size grouped by owner for the specified shares.
Extension report
Access report Growth report Share usage report


Confidential.
Unix Support Limitations (Windows DS-Clients)

Like backup/restore, LAN Discovery uses Hummingbird NFS to access Unix servers. The limitations are described below. 1. Soft links and device files will be silently skipped. 2. Hard links will be treated as regular files. If two hard links point to the same file, they will be considered as duplicates of each other. 3. Owner field will always be empty. 4. Hummingbird Client (hclnfs.sys) has some serious known problems: Kernel/regular memory leaks that eventually could crash the DS-Client machine. These problems are fixed in V8.0.0.17 and V9.0.0.5 File handle leaks (when reading symbolic links) that eventually could crash the DS-Client machine. V9.0.0.5 has this problem, and it is fixed in V9.0.0.6 Windows blue screen when accessing a long path. This problem was found in all known versions. To bypass this problem, LAN Discovery will simply skip all files/directories with paths longer than or equal to 260 characters. Extra dot in the hostname for stand alone machine. This problem was found only in version 9. To bypass this problem, add the stand alone host using IP address instead of machine name.
Unix Support Limitations (Linux DS-Clients)

1. Soft links and device files will be silently skipped. 2. Hard links will be treated as regular files. If two hard links point to the same file, they will be considered as duplicates of each other.
See Also
LAN Storage Discovery considerations on page 508


Confidential.
LAN Storage Discovery considerations

Creation Date: April 01, 2008 Revision Date: April 01, 2008 Product: DS-Client
Summary
The LAN Storage Discovery process can be disruptive. The reason is because the DS-Client must connect to each target share, read the files in the share, and prepare a signature for each file in order to report on common files, largest file sizes, file types, etc.
Considerations & Recommendations

The following considerations and recommendations will help you when using the LAN Storage Discovery Tool: 1. If you do not wish to have LAN Discovery Interfere with your network or users, you can run LAN Discovery outside of the business hours by scheduling the process and setting an "End Time" for the schedule. This way, the LAN Storage Discovery Process will start after users leave the office, and stop before users arrive at the office the next day. Shares that have been recently scanned will not be in priority sequence for scanning. Only shares that have not been scanned will receive priority for the scanning process when the schedule is triggered again. 2. It is recommended that you prepare a special Domain Administrator account that can access all the shares that need to be scanned. This will simplify the configuration of credentials required on the DS-Client and thereby reduce the potential for connection errors during LAN Discovery (DS-Client will try to use each of the credentials provided to connect to each share it tries to discover). If using a Domain Administrator account is not an option, then you can create the same local Administrator account (username and password) on each server that will be scanned. 3. After the share discovery process has finished, you will have as a result a share list that may include duplicate shares (shares that are included in other shares). Leave them as disabled, since you do not need to scan those files twice. 4. Ignoring small files can considerably reduce the network overhead and the total time required for the Scan Shares process. 5. Adjust the number of threads used to scan the shares. If the number is higher, the network will be busier, but the total time for the scan share process will be less than if the number of threads is smaller. 6. If you have both Windows and Linux computers on the network, you should use two different DS-Clients to scan the shares: a Windows DS-Client to scan your Windows shares and a Linux DS-Client to scan your Unix shares. During a Scan Shares process, the network and I/O of the scanned machines and the SQL Server where the DS-Client database resides will normally remain under a constant heavy load.


Confidential.
See Also
LAN Storage Discovery Overview on page 503


Confidential.
Load and Storage Summaries

Creation Date: April 30, 1997 Revision Date: June 21, 2010 Product: DS-Client
Summary
The DS-Client accumulates statistical information that can help to analyze load, utilization and storage trends it experiences. For new target backup servers, the DS-Client can perform statistical backups for a few days or weeks to generate statistical information. Statistical backup sets are similar to regular backup sets (the data source is scanned, new files are compressed and encrypted) except no data is sent to DS-System. Statistical backups can help you analyze data amounts, trends and incremental amounts before performing actual backups. In production environments, all the statistical information gathered is displayed (for Regular backup sets, Statistical backup sets, Self-Contained backup sets, and Local-Only backup sets). The Load Summary and Storage Summary screens are accessible from the Reports menu. The Storage Summary allows you to filter for statistical information from specific backup set types.
Load Summary statistics

The Load Summary can help administrators analyze the load on the DS-Client computer for a selected period of time. If you observe high values at a particular time period, you should consider rescheduling the activities to distribute the load more evenly. If you observe high values at all times, you should consider using a more powerful computer or delegate some backup sets to another DS-Client. The DS-Client service automatically collects data for these statistics at one-minute intervals. Every five minutes, the DS-Client service updates an internal table with the peak amounts for the following statistics:
Send amount Receive amount CPU load Memory load Memory committed Activities Peak of transmitted amount to DS-System (KB/sec) Peak of received amount from DS-System (KB/sec) CPU utilization (0-100%) Memory utilization (0-100%) Amount of allocated memory (in MB) Number of DS-Client activities
Storage Summary statistics

The Storage Summary can help administrators analyze the trends for Online amount, number of files and backup time. There are two types of figures (statistics): primary (such as Online, Files, Backup Files, etc.) and derived (all of the incremental amounts). A primary figure reflects a real number obtained from the statistics. A derived figure is linked to a primary figure (e.g. Incremental Files is linked to Files), and is obtained by subtracting the current primary figure point from the previous primary figure point. During administrative processes, the DS-Client service automatically calculates the following statistics:


Confidential.
Time statistics (in minutes)

Average Time Actual Time An average of the backup times for scheduled backups. The actual backup time duration of both Scheduled and Demand Backups for the selected period.
Files statistics
Total Files Incremental Files New Files Backup Files The total number of files stored Online (including all generations) This is a derived figure, showing the increment to the Total files. The total number of new backed up files (i.e.: files backed up for the first time). The total number of files backed up for the selected period.
Incremental Backup Files This is a derived figure, showing the increment to the Backup Files.
Amount statistics (MB)

Total Online Incremental Online New Online Transmitted Incremental Transmitted Online Backup The total amount stored Online. This is a derived figure, showing the increment to the Total Online. The total amount for the new backed up files. The total amount of data transmitted to DS-System (includes the effects of compression, DS-Delta and DS-Library technologies.) This is a derived figure, showing the increment to the Transmitted amount. The total amount of data backed up for the selected period.
Incremental Online Backup This is a derived figure showing the increment to Online Backup.


Confidential.
Retention Rules vs. Maximum # of Online Generations

Creation Date: October 09, 2007 Revision Date: April 07, 2010 Product: DS-Client
Summary
This information is only provided as a sample of different strategies. Each customer is ultimately responsible for the storage and deletion policies for their data. This article outlines the differences between setting up maximum generations on a backup set and using retention rules. It also describes how these two functions work together. The main point is that the customer must choose what mechanism will be in charge of deleting generations from online storage: Maximum Generations are passive - they allow generations to be overwritten whenever necessary (on the DS-System online storage). Retention Rules are active - they must be applied to a backup set, then enforced (either on schedule or on-demand) to physically delete generations from the DS-System online storage or move generations from DS-System online storage to BLM Archiver. The default setting from DS-Client installation is to use maximum generations, meaning the oldest version of a file will be overwritten if you have backed up the maximum allowed number of generations for a file. Generations are created on the online storage when the backup detects that a file has changed. Files that never change have only one generation on the DS-System online storage.
Maximum Generations
The maximum generations parameter is set up in the backup set properties, and it must be a number between 1-9999. This means that this backup set will save up to this maximum number of restorable generations on the DS-System online storage. It will not keep more than this number on the online storage (when it reaches the limit, the oldest generation is overwritten). Overwriting is done during the backup process and does not take into consideration any retention rules that might apply, since retention rules run separately from the backup. Best uses for maximum generations are: for CDP (continuous data protection) backup sets, where files are constantly changing and immediately being backed up, and the client would like to control the size of the online storage. when there are no retention rules applied, and online storage size is a concern. All cumulative backups (on-demand and scheduled) will keep up to the maximum generation number. In case a low number of maximum generations is set up for a backup intended to run on schedule, be aware that if you run an on-demand backup, what is kept online may not be what you expect. For example: You create a backup set with maximum generations set to 7, and schedule it to run daily (to keep the daily changes for a week). Assuming all backup files change daily, you would expect one generation for each day. If an on-demand backup is run on this set, it will disrupt the pattern, and you will have 2 generations from the same day (and restorable generations going back 6 days, instead of 7). [This assumes that the file was changed before the ondemand backup, and before the scheduled backup.]


Confidential.
Retention Rules
Retention rules apply to the online generations every time they are enforced on a backup set. This can happen in two ways: On-demand, separately from the backup process. Within a schedule, independently or right after a backup task for this backup set. When using retention rules, the enforce retention process works with what is saved in the online storage by the backup process. The following considerations should be made when applying Retention Rules to a backup set: 1. Retention Rule compatibility with Maximum number of generations You must make sure the Retention Rules work with the maximum number of generations for the backup set. If the maximum generations is set to a low number (e.g. 7), then the retention rules may not produce the intended result. (The oldest generations are likely to be overwritten by the backup process, before any of the generations qualify for deletion by the retention rules.) 2. Retention Rule compatibility with its own rules (Delete options, Time-based online Retention, and Moving old data to BLM Archiver) Retention Rules work best if the maximum generations parameter is set to the maximum (9999) or to a high number (e.g. 300). The retention rules help by deleting what you define to be unnecessary, and to retain online what you define to be critical. As a result, you will most likely never reach a high number of generations for the same file on the DS-System online storage. Note: Results depend on the Retention Rules and how often they are enforced. Delete options (Deletion of files removed from source / HSMed data): Once this retention rule is enforced on a backup set, it will check the options configured for the files that are removed from source, or for data that has been moved by a third-party HSM/ILM solution to a remote location. DS-Client can be instructed to keep [x] number of generations for each file in the backup set after a certain period of time, since the file has been removed from the source machine. Note: DS-Client detects that files have been removed from source when the backup activity is running. If a placeholder / stub is detected on the source machine, (Windows) DSClient can be instructed to delete all file generations backed up before the stub / placeholder was detected, or to delete all generations that are not stubs / placeholders and were backed up in an earlier backup session than the stub. By default, enforcing any Retention Rule will cause a deletion of all data that is defined as obsolete on from the DS-System online storage. However, a copy of this data can be sent to BLM Archiver before it is removed completely from the DS-System online storage. Time-based online retention (deletion of files from the DS-System online storage based on user-specified time-based rules): Keep most recent generations has a default value of 1. All generations of a file will be removed from the DS-System online storage, with the exception of the latest (most recent) generation. If this number is increased to a very high amount (e.g. 9999), all the other time-based rules specified in this Retention Rule configuration will not have any effect or the required effect (because they will be over-ruled by this particular rule). Keep all generations for [x] interval of time for [y] interval of time. Timebased rules should be as specific as possible. When a retention rule has more


Confidential.
details, it will work better and be much more precise than a general rule. For more details, see Retention Rule Examples on page 516. Archive old data to BLM Archiver: Specify the age of the files at which DS-Client will move that data to BLM Archiver. The algorithm will compare the last modification date with the backup session date, and will apply the oldest of the two for the archiving rules. For example: If all files older than one (1) month should be sent to BLM, DSClient will compare the last modification time and backup time of a file; it will take the oldest value to calculate the age of the file and will execute the corresponding action (archive / do not archive). Local Storage Retention: This only applies to the files saved in the DS-Client Local Storage Buffer(s). In order to have the DS-Client save multiple generations on the local storage, the backup set must be assigned to a retention rule that has the Local Storage Retention options enabled. Local Storage can only keep data on the local storage buffer if that same data (exact generation) exists on the DS-System online storage as well.
To Summarize
Customers have a choice between 2 methods of deleting online generations. Passive: Maximum generations: overwrites oldest generation whenever necessary (no user intervention required) If set to a low number, this will make the backup set's retention rule inefficient. It is best used with a CDP backup, because it is enforced every time a backup runs (once maximum generations have been reached).
Active Retention rules: to be used correctly, the following best practices apply: Maximum generations of the backup set should be set to the maximum, or another high number (several hundreds/thousands). Keep most recent generations should be set to a low number, such as 1, if timebased rules are also specified in the same Retention Rule.
Time-based rules should be as specific as possible (e.g. Keep one generation every week on or before Sunday at 11:59PM for 1 Month) instead of being generic (like Keep one generation every week for 1 Month). Manual Delete: (Sets Menu > Delete > Selective Delete) can be performed on-demand at any time to free up space on the DS-System online storage.
NOTE: Because of the many configurations that are possible, it must be emphasized that the customer is responsible for configuring the storage and retention policies. Treat retention as if you are performing a manual delete of data: once data is deleted from online, you can never get it back.
Your Service Provider might also offer the BLM Archiving to lower cost media. Every time you delete data, you have the option to send a copy of the generations that are about to be deleted to BLM.


Confidential.
When BLM selected for a backup set, you can effectively save a copy of every backup generations forever.
See Also
About Retention Rules on page 85 Retention Rule Examples on page 516


Confidential.
Retention Rule Examples

Creation Date: November 15, 2007 Revision Date: January 23, 2008 Product: DS-Client
Summary
This article describes some common retention policies that have been implemented in production environments. NOTE: Because of the many configurations that are possible, it must be emphasized that the customer is responsible for configuring the storage and retention policies. Treat retention as if you are performing a manual delete of data: once data is deleted from online, you can never get it back.
Example 1
The most common requirement for companies to retain data on the DS-System online storage is the following: 1 generation every day for a week 1 generation every week for a month 1 generation every month for a year 1 generation every year for 7 years In order to implement this (or a similar) Retention Rule: 1. The backup set must be configured with a high number of generations for the backup items (e.g. 300). Know your backup data: Retention is designed for backup items that change regularly (e.g. daily). A backup item that does not change will have only one generation. 2. Follow the steps from Create or Edit a Retention Rule on page 85. 3. In the Retention Rule Wizard, make the following configurations. 4. In the Generic retention options screens Keep most recent generations field: Choose the number of most recent generations that you always want to be able to restore. Retention will not apply to these generations. Some examples of common choices: 1, for the most recent generation (e.g. for disaster recovery); 7, for the most recent 7 generations (assuming one daily backup for items that change, this keeps the last weeks worth of backups); 5, for most recent 5 generations (assuming daily backups during business days from Monday-Friday for items that change, this keeps the last business weeks worth of backups). 5. In the Time retention options screen, add each time-based rule individually to the list. Rules appear in the form Keep one generation every [x - time] for [y - time]. Choose the interval of time (x) over which you want to keep one generation online. All other generations in that interval will be deleted when retention is enforced. For the same rule, you must also choose the interval of time (y) that the rule applies to the entire online storage. This means one generation is retained for every x-interval that fits into y (e.g. every 1 month for last 1 year means 12 generations will be retained).

Confidential.
6. Add the four time-based retention options so the Time Retention Option List looks as follows:
Keep one generation every 1 day(s) for last 1 week(s) Keep one generation every 1 week(s) for last 1 month(s) Keep one generation every 1 month(s) for last 1 year(s) Keep one generation every 1 year(s) for last 7 year(s)
However, you may wish to be more specific with the data that you want to retain. For example:
Keep one generation every week on or before Friday at 23:59:59 for last 6 month(s)
7. Finish creating the Retention Rule. 8. Apply the Retention Rule to the backup set(s) you want. 9. Schedule the Enforce Retention process (or run it on-demand). This will delete all online generations, except those specified to be kept in the Retention Rule.
Example 2
More complex rules and regulations can be implemented with Asigra Cloud Backup software. For example, a company may have the following data retention requirements:
Any files deleted from source should be retained online on the DS-System online storage for a period of three (3) months, and afterwards this data must be moved to archive. All files must be moved from DS-System online storage to BLM Archiver if files are older than 6 months.
In order to do this, you would create the following Retention Rule: 1. Open the New Retention Rule Wizard. Select Deletion of files removed from source / HSMed data Select Archive old data to BLM 2. Click Next. In the Delete Options screen: Configure If files are removed from source after 3 months, Keep Generations: 0 3. Click Next. In the Archive Options screen: Add the Archive Rule Archive files older than 6 month(s) Make sure the rule applies to All files 4. Click Next. In the Choose a name screen: Select the option Move obsolete data to BLM 5. Click Finish.
See Also
About Retention Rules on page 85 Retention Rules vs. Maximum # of Online Generations on page 512


Confidential.
Retention Rule combinations (multiple rule types)

Creation Date: August 23, 2010 Revision Date: August 23, 2010 Product: DS-Client
Summary
WARNING:Retention rules involve the removal of data from online storage. As such, they should be treated as 'delete data' operations. You will not be able to recover data that is deleted because of retention, therefore make sure the rules you create and apply are appropriate. This article describes some of the possible retention rule combinations. A retention rule can be created with one, or a combination of the following types of rules, whose effects can overlap: Deletion of files removed from source / HSMed data Time-based online retention Archive old data to BLM [Time Push] Local Storage retention Component data integration options for VSS-aware backup sets In general, if you create a retention rule with only one of the above types selected, the behavior will be as specified. If you combine two or more of the above types, then some overlapping of the rules may occur which will affect the behavior of the retention. REMEMBER: The Time-Push (Archive old data to BLM) option is applied last, after all other retention types have been applied. On the last tab of the Retention Rule Wizard, you have the "Move obsolete data to BLM" option. This option is a safer way to test retention, since it will 'push' all data deleted from DS-System online storage to the BLM Archiver. (The worst case is data is moved to the BLM.)
Details
The following types of rules can be defined from the Retention Rule Wizard: (1) Deletion of files removed from source / HSMed data The Delete Options (for files that have been removed from the backup source) will always apply. They are the first rules that are applied when a Retention Rule is enforced on a backup set. If the "Move obsolete data to BLM" option is not selected, data that is not retained online is deleted permanently. (2) Time-based online retention When a Retention Rule is enforced on a backup set, it will delete data from online, unless that data falls into one of the time-based retention categories. The time-based retention options in a Retention Rule can overlap, with the result being that the option that leaves the most generations for the longest time is applied. If the "Move obsolete data to BLM" option is not selected, data that is not retained online is deleted permanently. This approach prioritizes retention, and makes the BLM Archiving optional.


Confidential.
(3) Archive old data to BLM [Time Push] This option is applied last, to the files that remain online after the Delete Options and/or Time Retention Options have run (if defined). By design, this retention rule sends all data to BLM once that data qualifies as "old", based on the archive rules. This approach prioritizes archiving and is focused on a specific age for files to be archived. If "Archive old data to BLM" is used with other retention rule types, you must remember it is applied last, and only to the files that remain online (after the Delete Options and / or Time Retention Options have run). (4) Local Storage retention This is a special type of retention for use with the Local Storage feature. For the purposes of this article, this option is not described any further. (5) Component data integration options for VSS-aware backup sets This is a special type of retention for use with Windows VSS-aware backup sets. For the purposes of this article, this option is not described any further. In this article, the rule types (2 - time-based) and (3 - archive to BLM) are examined in greater detail.
FAQ: what rule(s) to use for a desired outcome

The following table shows which of the different types of retention rules can be used to accomplish a specific outcome. Some overlap may be necessary where more that one rule is required, or the solution might be accomplished by different rules entirely. These are only suggestions, since the different types of rules have been designed for maximum user configuration flexibility and it is ultimately up to the user to define and use a Retention Rule.
Retention Rule types (1) Deletion of files removed from source / HSMed data (2) Time-based online retention (3) Archive old data to BLM [Time Push] (4) Local Storage retention (5) Component data integration options for VSS-aware backup sets Desired outcome Rule(s) that can be used (1), (2), (3), (4) Use Keep generation option. (3) Use Archive special files options. Archive old generations, but keep the latest generation of all files online Bare Metal Restore (BMR) backup set: Archive old data from a BMR backup set, but maintain the latest generation of all data for a BMR. Filter for a specific pattern of generations to keep online Send to BLM only data that has satisfied the longest retention rule Archive data based on file type
(2) Define Time Retention Rules. (2) + (3) Define Time Retention Rules. Make an Archive Rule that is longer than the longest Time Retention Rule. (3) Define Archive Rules that use File Filtering rules.
Confidential.
Combining Retention Rule types

The following retention rule combination descriptions may be useful: Retention rule combination: Send to BLM only data that has satisfied the longest retention rule on page 520 Retention rule combination: How to archive everything that is not required for BMR but keep the latest 1 generation for BMR on DS-System on page 520 Retention rule combination: Send to BLM only data that has satisfied the longest retention rule To send data to BLM only if (after) it as satisfied the defined time-based retention rules: 1. Create a retention rule with "Time-based online retention" and "Archive old data to BLM" rules. 2. The time based rules can be anything. For example: Keep latest x generations. Keep 1 generation every day for 1 week. Keep 1 generation every week for one month. The last time-based rule must be with 1 unit longer than expected: e.g. the customer expects to keep 1 generation every month for 6 months, but the actual configuration is to "keep 1 generation every month for 7 months", etc. The time-based retention should use the Delete obsolete data retention option (i.e.it must NOT have the option Move obsolete data to BLM checked). 3. The archive rules should be configured so the longest retention rule also defines the age at which data is archived to BLM. For example, if the longest retention rule is "keep 1 generation every month for 6 months" the archive rule should state "Archive to BLM data older then 6 months" and the "compare backup time only" option must be checked. Retention rule combination: How to archive everything that is not required for BMR but keep the latest 1 generation for BMR on DS-System If your requirement is to archive any file generation older than 1 year but keep the latest online generation, then you could configure a time-based rule that says: Keep latest 1 generation Keep all generations for 365 days Alternatively, you combine this time-based rule with archiving rules that will move obsolete files completely to BLM such as user documents or pictures or movies based on the file extensions.


Confidential.
Enforce Retention Frequency

The frequency at which a Retention Rule is applied should be a major consideration. If you define an extremely granular Retention Rule (e.g. Time-based retention with rules for daily, weekly, monthly, and yearly retention that will be applied to a backup set with data from a long period of time online - like 10 years). This type of retention works best when applied ONCE. If you apply it again, the next day, even if changes have been made in the past 24 hours and backed up, the other retention rules (weekly, monthly, yearly) will probably not catch data fitting the policy. By applying the rule only once, you can make it as granular as you want, based on your knowledge of the data online. Regular retention (e.g. weekly enforcement) is more effective with Retention Rules that do not contain rule intervals longer than the frequency of enforcement. This means if you enforce retention weekly, it is best not to have rules for intervals longer than one week (7 days). Consideration must also be made as to the frequency of data changes.
See Also
About Retention Rules on page 85 Retention Rule Examples on page 516


Confidential.
Delete Considerations
Creation Date: June 20, 2011 Revision Date: June 20, 2011 Product: DS-Client
Summary
This article describes some advanced considerations regarding delete activities. The basic form of delete simply removes a generation from online storage. However, when the delete is combined with some of the other features of Asigra Cloud Backup, there are some more considerations that need to be taken into account.
Basic Delete Methods

Remove a backup set This deletes all online data of a backup set and also removes the backup set itself. Selective Delete This is the simplest delete method. You browse backup sets with the Delete Wizard and pick the specific file(s) to delete. Assisted Delete This is a faster method to remove obsolete data from multiple backup sets. It only selects backup data the DS-Client has detected that was removed from the backup source. Generation recycling (Passive Delete) All backup items must have a maximum number of online generations. For backup data that does not change often, you may only have 1 generation online even after several backups. However, data that changes often will have multiple generations. When the maximum number of generations for a particular file is reached, the oldest generation gets overwritten after the next backup. To prevent loss of those old generations, you can configure the backup set with the BLM (Infinite Generations) option, which will send a copy of each overwritten generation to BLM Archiver (if this is available from your Service Provider). Delete because of Retention Any data that is not retained when a Retention Rule is enforced will be deleted.


Confidential.
Additional Options that can affect deletes and/or delete behavior

Move to BLM (Archiving) If BLM Archiving is available, every delete situation will offer the Move to BLM option. For passive deletes (generation recycling), this is configured in the backup sets Properties > Options tab: BLM (Infinite Generations). If the backup set is configured with the BLM (Infinite Generations) option, the Move to BLM is always selected. If the DS-System cannot move the deleted data to BLM, the delete will fail. DS-System Delete Lock (from Service Provider) If your service provider has applied a Delete Lock to your customer account or to this specific DS-Client, the following will occur: You will see a warning message in the Activity Log when a delete activity is performed. If the DS-System can move the deleted data to BLM, it will do so. If the DS-System cannot move the deleted data to BLM, the delete will fail. If the delete was a passive delete (e.g. generation recycling), the maximum generation configuration will be overruled and those surplus generations will accumulate online. BLM Delete Lock (from Service Provider) Note: BLM is only accessible to end-users via a DS-NOC web site.
If your service provider has applied a Delete Lock to your customer account or to this specific DS-Client on the BLM Archiver, the following will occur: You can perform Destruction Requests, however you will not be able to Confirm Destruction of any Destruction Requests. You will see an error in the BLM Activity Log when a Data Destruction Confirmation activity is performed.


Confidential.
Scheduled Operations
Creation Date: February 10, 2006 Revision Date: October 03, 2012 Product: DS-Client
Summary
This article provides additional information about scheduled activities on DS-Client.
How scheduled operations start and run

DS-Client checks for scheduled operations that are to be triggered every minute (24 hours a day). If an operation is started but cannot be completed (because the connection to DS-System cannot be established or is lost), it will retry, by default, 3 times over five minutes to resume or initiate the connection. The number of attempts and the interval between retries (up to 60 minutes) can be configured (DS-User > Setup > Parameters). If the scheduled operation is missed for this reason, a new attempt to perform it will be made at the next scheduled time (e.g. a backup scheduled to take place everyday at 14:00 will retry next day at 14:00.). If an activity is running at the time of a scheduled operation, and that activity prevents other operations from running, the scheduled operation will start as soon as that activity ends. By default, DS-Client will attempt to start a scheduled operation every minute for 6 hours from the (actual) scheduled start time. This interval is configurable on Windows DS-Clients using the ScheduleMiss parameter from the DS-Client Advanced Configurations on page 458. Examples: If Daily Admin or any other activity which is locking the backup set is running, the schedule will start as soon as that activity ends. If the schedule is skipped for a reason other than losing connection to DSSystem (e.g. DS-Client service is stopped), the schedule will start as soon as the DS-Client reaches its normal state (e.g. DS-Client is running).
Scheduling from a DS-User in a different Time Zone

DS-User configures the DS-Client in real-time, whatever time zone the DS-User might be connecting from. The main point to remember is that you are configuring the DS-Client. When you connect to a DS-Client from a DS-User in a different time zone, the times returned by the DS-Client are all converted to match your time zone. For example: 1. Pacific Time DS-User connects at 07:50AM to Eastern Standard Time DS-Client (10:50AM). 2. Pacific Time DS-User sets Eastern Standard Time DS-Client schedule to 07:51AM. 3. On DS-Client, that 07:51AM PST is interpreted as the corresponding current local time (10:51AM EST). All log times returned by DS-Client are Eastern Standard Time (from its database). If the DS-User is not in the same time zone, the time is converted to the equivalent value for the time zone. This means if an EST DS-User displays 10:51 for an activity, on a remote Pacific Time DS-User, that same activity will show a time of 07:51.


Confidential.
See Also
Configure the DS-Client Parameters on page 39 DS-Client Advanced Configurations on page 458


Confidential.
Validation Overview
Creation Date: August 24, 2006 Revision Date: August 24, 2006 Product: DS-Client
Summary
The Validation process is designed to verify the restorability of online data. Without the customer / DS-Client encryption keys, DS-System is not able to create the digital signature to validate backed up data for some types of corruption. In order to avoid transmitting large amounts of data from DS-System to DS-Client for validation, DS-Client will send the encryption keys to DS-System based on your ACCEPTANCE / ACKNOWLEDGEMENT / AGREEMENT to this option. The decision to perform validation must be made from the DS-Client side. The customer knows better than anyone else what data is more important (i.e. data that needs to be validated more often). When a Validation process is triggered on DS-Client side, DS-Client sends a request to DS-System to perform the validation. For each file (generation), DS-System will first check the file header and delta linking/library linking, etc. If everything is fine, it will try to validate the data by performing a procedure like a virtual restore. The data will be decrypted and decompressed to generate the original signature. If it fails due to a decryption or decompression problem, the validation fails. Finally, it will compare the generated signature with the original one: if it does not match, the validation fails; otherwise the validation is successful. For any validation failure, the error will be reported on both DS-Client and DS-System. If the validation fails due to reading or network problems, it is unknown whether or not the file is valid. Validation will skip the file and report the corresponding errors on both DS-System and DS-Client event logs. For other failures where DS-System can confirm the file is corrupted, the file will be moved to the trash (\del directory). All dependant files will also be moved as well. Since the validation process will read all data to check the digital signature, the validation process is Disk I/O intensive on DS-System side. The whole process is almost the same as an actual restore, except that INSTEAD OF writing to a target location, the decrypted/decompressed data is not kept after generating the signature. A variety of options are provided to help validate online data in the most flexible and efficient way. These options include: validation of all data, selective validation, scheduled / on-demand validation, excluding data deleted from source, and resuming mechanism, etc.
Validation functionality description

1. The encryption keys must be input by the customer (from DS-User) and DS-Client verifies them. The dialog that asks for encryption key(s) will display a warning with a description of how the encryption key(s) are involved in the Validation process. The encryption keys are encrypted when being transmitted from DS-User to DS-Client, and from DS-Client to DS-System. Encryption keys are only used to perform the data Validation: DS-System will not keep the keys after the Validation has finished. 2. The Validation process can be triggered on demand, as well as scheduled. 3. The demand Validation has two options:

Confidential.
4. 5.
6.
7.
8. 9.
10.
11. 12. 13.
Validate all online data (all generations of all files). Selective pop up a selection tree similar to the restore tree to allow selection of directories/files as well as generations to validate. The execution sequence for a backup sets scheduled activities is: 1. Perform Backup, 2. Enforce Retention, 3. Perform Validation, 4. Perform BLM. When setting a schedule to perform Validation, the customer must input the encryption key(s) and DS-Client verifies them. The Validation activity can only be enabled in a schedule if the user provides the correct encryption key(s). The scheduled Validation has options to: Validate all online data (all generations of all files) or last generation only (snap shot) Include or exclude files already deleted from source. The scheduled Validation also has the option to resume from the point of interruption of the previous scheduled Validation process. If a scheduled Validation completely processes all selected files, the next scheduled Validation (for the same backup set) will process files from the beginning. To determine the interruption point, the files are processed in sequence based on the order of share ID, directory ID, file ID and generation. Note: On demand Validations do not have the resume mechanism. Validation is not available for statistical backup sets, since there is no data on DS-System to validate. If a file corruption is detected (including Digital Signature does not match errors), that file and all files that actually depend on it (occasionally, a delta may formally depend on a file, but does not actually depend on it) will be moved to the \del directory. The corresponding error will be reported on both DS-System and DS-Client sides. If a files restorability status cannot be determined temporarily (networking problems, etc.), DS-System will skip the validation for this file. The corresponding error will be reported on both DS-System and DS-Client sides. If a file originally did not have a signature that is needed for Validation, a warning will be reported. If any bad files are removed, DS-System will mark the backup set as out of sync at the end of the Validation process. Only users with the Administrator Role on DS-Client are allowed to start a Validation process.
See Also
Validation of Online Storage on page 276


Confidential.
Local Storage Cache Overview

Creation Date: March 06, 2009 Revision Date: December 15, 2010 Product: DS-Client
Summary
The Local Storage Cache feature enables DS-Clients to perform backup on a local attached disk or UNC path accessible by the DS-Client software and send the data to the DS-System at a later time when the DS-System service becomes available. Backup sets must be configured to use this option. The Local Storage Cache option is available for backup sets if the DS-Client has the "Local Storage" tool enabled (from the DS-System). This article describes the following: Saving Data to Local Storage Cache on page 528 Data in Local Storage Buffer vs. Data in Local Storage Cache Buffer on page 529 Local Storage Number of Generations vs. Local Storage Cache Number of Generations on page 530 Restoring data from Local Storage Buffer vs. Local Storage Cache Buffer on page 530 Detecting File Corruptions in the Local Storage Cache Buffer on page 530
Saving Data to Local Storage Cache

DS-Clients will send data to the Local Storage Cache when backup sets are configured with the "Local Storage Cache" option and: the connection between the DS-Client and DS-System is lost during a backup activity and the connection cannot be re-established after the number of retries configured for the activities expire. (The number of retries can be configured from DS-User > Setup Menu > Configuration > Parameters Tab.) DS-Client cannot establish a connection to the DS-System for a scheduled or on-demand backup activity. the backup activity is stopped from the DS-System-side and the DS-Client fails to reconnect to the DS-System based on the configured number of retries for backup activities. [Windows DS-Client only]: backup activity starts and data still exists in the Local Storage Cache buffer for this backup set. If a DS-Client tries to connect to a DS-System and cannot establish the connection, DS-Client will process the data and save it in the Local Storage Cache buffer. Once DS-Client is able to connect to the DS-System, a Local Cache Copy process will be triggered which will be responsible to send to DS-System each generation of the files that are needed, in the required format: i.e. master/ delta/regular. If the DS-Client was able to establish a connection to the DS-System for this backup set and the backup activity was interrupted, when a connection to the DS-System can be re-established, the DS-Client must run a synchronization activity and then proceed with the Local Cache Copy process. The Local Cache Copy process is considered as being a backup activity (by the DS-System) and it has the same priority and the same backup set locking rules apply.


Confidential.
Data in Local Storage Buffer vs. Data in Local Storage Cache Buffer
Feature
Local Storage Buffer
Local Storage Cache Buffer Connection to the DS-System is NOT available Full File Content ("Master" generation format) + Meta Data ("Delta" generation pointers) Yes
Data is stored in "Buffer" Connection to the DS-System is when: available Types of Generations: Compression: Full File Content ("Regular" generation format) Yes No (by default) Can be configured using the EncryptedLocalData Parameter. See DS-Client Advanced Configurations on page 458. No
Encryption:
Yes
Data "Buffered" during Initial Backup:
No
Data is sent to the Local Storage Buffer at the same time when the processing occurs to send data to the DS-System (connection from the DS-Client to the DS-System must be available). Data is sent to the Local Storage Cache Buffer ONLY when connection to the DS-System is NOT available. By default, data is saved in the Local Storage Buffer compressed, but not encrypted (configurable), and as "regular" generations of the files. Data is saved in the Local Storage Cache buffer compressed and encrypted as "master" generations of the files. Data is saved in the Local Storage Cache buffer as a master generation that includes additional information that determines which blocks of data from within that file are required for delta generations. When a connection between the DS-Client and the DS-System can be established, DS-Client will move the files required to reside in the Local Storage Buffer (based on backup set configuration) in the format they were stored in the Local Storage Cache Buffer (encrypted and compressed) and will send only "delta" generations to the DS-System (when applicable). As a result, DS-Client can still process Master/Delta (Incremental forever) when performing backup using the Local Storage Cache Option. Similarly, the Local Storage Buffer may include encrypted as well as unencrypted data, depending on when the files were processed during a particular backup activity. Files from the Local Storage Cache Buffer are only removed from the Local Storage Cache Buffer or moved to the Local Storage Buffer when they have been successfully transferred to the DSSystem. File are released from Local Storage Cache Buffer one-by-one as their successful transmission to the DS-System is confirmed between the DS-System and the DS-Client. An initial backup session does not process data for Local Storage Buffer or Local Storage Cache Buffer.

Confidential.
Local Storage Number of Generations vs. Local Storage Cache Number of Generations
The configured number of generations for a backup sets items does not take effect when data is sent to the Local Storage Cache Buffer. For example: a backup set configured to store up to three generations of data on the DS-System Online Storage may store more than three generations of data in the Local Storage Cache buffer if the DS-System does not become available while DSClient has backed up those generations and/or DS-Client did not have a sufficient backup window to finish the move of the data from the Local Storage Cache Buffer to the DS-System. All generations will be sent to DS-System whenever possible as "regular" generations or "Master/ Delta" generations and DS-System will process them as it would process any generations sent directly to it (e.g. it will mark generations as recycled when required, it will trigger reconstruction when required, etc.). By default, the Local Storage Buffer will store the latest generation of all the files processed for a backup set. However, if Local Storage Retention is enabled and assigned to a backup set with Local Storage Options enabled, the DS-Client will store all generations that meet the criteria specified in the Local Storage Retention rules in the Local Storage Buffer.
Restoring data from Local Storage Buffer vs. Local Storage Cache Buffer
DS-Client can restore data directly from the Local Storage Buffer and can connect to the DSSystem to retrieve only the data that does not exist in the Local Storage Buffer (this behavior is configurable from the Restore Wizard, before triggering the restore activity). Data from the Local Storage Cache Buffer cannot be restored until it has been transferred to the DS-System.
Detecting File Corruptions in the Local Storage Cache Buffer

DS-Client is able to perform basic checks to ensure the validity of the files from the Local Storage Cache Buffer at the time when the files are transferred to the DS-System. If as a result of these checks, DS-Client determines that the files are corrupted, it will remove the file information from the DS-Client database and it will try to determine if the files need to be backed up again during the subsequent backup session. IMPORTANT NOTES: 1. If a backup set is marked as "out-of-sync" and the DS-Client cannot connect to the DS-System to perform synchronization, then DS-Client cannot run backup to the Local Storage Cache Buffer. 2. DS-Client Administrators must ensure that sufficient Local Storage disk space is available to accommodate all data in the Local Storage Buffer or Local Storage Cache Buffer for all the configured backup sets. 3. If data exists in the Local Storage Cache Buffer for a selected backup set, that data must be transferred to the DS-System first, and only afterwards can the DS-Client perform subsequent backups for that backup set directly to the DS-System. 4. Suspending a backup set configured with the Local Storage Cache Buffer will not allow the Local Storage Cache Copy process to be triggered and to connect to the DS-System to move the data.
See Also
Local Storage Cache on page 305


Confidential.
Knowledge Base: BACKUP


Confidential.
Backup Limitations
Creation Date: March 17, 2006 Revision Date: October 31, 2007 Product: DS-Client
Summary
This article describes some DS-Client backup limitations related to the length of the source file names and to the length of the path where the source files reside.
Details
The following directory path and file name limits exist, depending on the type of database used by the DS-Client: Windows DS-Client Directory Path Limit: 435 characters (the entire path up to the beginning of the file name). File Name Limit: 255 characters (file system limitation). Linux DS-Client Directory and File Path Limit: 1023 characters (the entire path including the file name). File Name Limit: 255 characters (file system limitation). In most cases, the file system will prevent users from creating directory paths longer than these limits. However, if your environment has paths that exceed a DS-Client Database limit, the DSClient will log an error (Directory path is too long.).


Confidential.
Best Practices: Initial Backup

Creation Date: December 04, 2007 Revision Date: December 04, 2007 Product: DS-Client
Summary
This article describes the Initial Backup Best Practices.
DS-Client-side best practices for Initial Backup

When running initial backups the following aspects need to be taken into account: The path specified must accommodate the size of the incoming data. The file system on the initial backup buffer must be able to handle the size of the incoming files (e.g. FAT32 has a 4GB file size limitation). When running several initial backups at the same time, make sure the device where initial buffer is located can handle the I/O load. If too many initial backup processes are sending data to the same path at the same time, the sessions may stop and the related errors will be reported. All Initial Backup Sets written to the same Initial Backup Path must be "completed" before the physical media is sent to your Service Provider (check in DS-User > Initial Backup > Status). Always check the DS-Client Activity Log and the Event Viewer at the end of every initial backup session to ensure that no errors are reported. If the initial backup session is interrupted, it can be resumed but you must synchronize the backup set (Right-click the backup set > Synchronize: Normal). To resume, start another backup session. The other option is to reset the backup set as Incomplete, then re-run the Initial Backup from the beginning (DS-User > Initial Backup > Status).
See Also
Initial Backup on page 279


Confidential.
Backing up Windows for Bare Metal Restore (BMR)

Creation Date: April 23, 2007 Revision Date: September 19, 2011 Product: DS-Client (Windows)
Summary
A Bare Metal Restore is the restore of an entire machine (usually to replacement hardware and to a new Operating System installation). To be able to perform BMR, you must protect the target computer with a single backup set that contains: System State and Services Database Operating System Volume NOTE: Some applications can be installed and can store data across multiple volumes. You must include all of those volumes in this backup set if you want to be able to restore those applications. It is strongly recommended to configure the BMR backup set with the VSS option (select "backup through volume shadow copies" but leave the sub-options "do not involve writers" and "do not process components" unselected). If the VSS option is not selected, depending on the applications running on the target computer, you may need to stop them for the first backup session, in order to facilitate a smooth BMR. To protect those services after the first backup and when they are running (i.e. in 'hot' mode), you must create separate backups with the corresponding special backup sets (e.g. MS SQL Server Database Backups on page 116).
Details
The reason you must perform at least one backup of the target computer with the service applications stopped is to ensure that any locked files used by those applications are backed up at least once. Otherwise, those services will not start after you perform the BMR. In order to restore from the special backup sets (e.g. MS SQL Server), the DS-Client needs to connect to a running service. If the service cannot start, you must repair that service installation with the corresponding Installation Package. In general, the steps for BMR of a Windows computer running MS SQL Server are: 1. Assemble the replacement hardware for the target BMR computer. 2. Re-install the same Windows Operating System (you do not need to apply any Service Packs). 3. If the Hardware is different from the original computer, you must install the corresponding hardware drivers. 4. Restore from the target computers backup set (including Operating System Volume, System State and Services Database). The restore of System State, Services Database and Operating System files must be done in one step (at the same time). 5. Restart the MS SQL Server (if applicable). 6. Restore the latest version of MS SQL Server from the separate special backup set (if applicable).


Confidential.
System Reserved Partition (Windows 2008 & up)

Starting from Windows 2008 (including Windows 7 and higher versions), Microsofts Operating System installation includes a System Reserved Partition (usually 100MB). This partition contains the boot files for the operating system, but it does not have an assigned drive letter (by default). For these Operating Systems, the following considerations should be made when creating a BMR backup set: If you assign a drive letter to the System Reserved Partition, you will be able to select it as a separate drive for backup. However, if you select this drive for backup along with the System State, you will back up the System Reserved Partition twice (see the next bullet point, below). Even if it is not assigned a drive letter, the System Reserved Partition is automatically included as part of the System State backup item for Windows File System backup sets. As long as you include the System State as part of your BMR backup set, DS-Client will automatically restore the System Reserved Partition when the System State is restored.
See also
Bare Metal Restore of Windows (ALL VERSIONS) on page 693. Bare Metal Restore of Windows XP on page 701. Bare Metal Restore of SBS 2008 on page 702. Bare Metal Restore of Windows 2008 R2 on page 705. Important Notes for Bare Metal Restore on page 707.


Confidential.
Backup of Windows System State

Creation Date: February 12, 2010 Revision Date: February 12, 2010 Product: DS-Client (Windows)
Summary
To back up a Windows computers System State, you must be an administrator or have administrator-level permissions. (Windows VISTA and Windows 7 have additional special requirements: see Special Requirements: Windows VISTA & Windows 7 on page 536.)
Details
System State data contains most elements of a Windows computers configuration, and it must be backed up along with the boot and system volume(s) of any target computer you want to recover from serious failure or disaster. Therefore, it is recommended that you create a Bare Metal Restore backup set to cover all restore possibilities for any important server. This means you create a single backup set to back up all boot and system volumes, including the System State and Services Database which appear as separate objects that can be selected from the Shares & Directories List (Set Properties Items Tab or New Backup Set Wizard). See: Backing up Windows for Bare Metal Restore (BMR) on page 534
Special Requirements: Windows VISTA & Windows 7

The default Microsoft installation settings will not automatically allow you to browse and select the System State of any remote target machine (even if you are using Administrator-level credentials). You will get the error Access denied when you try to select the System State. This behavior is due to the User Access Control (UAC) that Microsoft introduced beginning with Windows VISTA. By default, UAC denies all users from access to the administrative shares (i.e. System State), except for the built-in administrator user. The built-in administrator user is disabled by default. The following workarounds are available. They must be performed on each target computer whose System State you want to back up: 1. Enable built-in administrator account and specify its credentials when defining the backup set. -OR2. Disable UAC. -OR3. Enable the access to the administrative shares. This is equivalent to disabling UAC but only for network access. You can do this by adding / editing the DWORD LocalAccountTokenFilterPolicy registry value under:
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\system\registry key
Set it to 1. A reboot may be required.


Confidential.
See also
Backing up Windows for Bare Metal Restore (BMR) on page 534. Bare Metal Restore of Windows (ALL VERSIONS) on page 693. Bare Metal Restore of Windows XP on page 701. Bare Metal Restore of SBS 2008 on page 702. Important Notes for Bare Metal Restore on page 707.


Confidential.
Backup of Windows Encrypted Files

Creation Date: March 26, 2008 Revision Date: March 26, 2008 Product: DS-Client (Windows)
Summary
When a DS-Client encounters Windows encrypted files on a Windows source machine, the DSClient uses a different Microsoft API to back them up. Windows encrypted refers to files encrypted using the Windows File System encryption. The DS-Client will receive the data in its encrypted format, and it will encrypt it again and compress it, then send it to the DS-System. The master/delta algorithm is still invoked, however the delta file size will be close (in terms of size) to the master files size. During restores, the DS-Client will retrieve the data from the DS-System, decrypt the data from the DS-Client encryption, and then save it to the destination machine (in Windows Encrypted form). The restored files are still encrypted as they were when they were backed up. Windows has to manage and decrypt them at that point (i.e. you cannot restore them on FAT, etc.).


Confidential.
Backup / Restore of UNIX File Systems

Creation Date: August 15, 2008 Revision Date: September 21, 2012 Product: DS-Client (Linux)
Summary
If you have UNIX servers on your network, install a Linux DS-Client to perform backup / restore. This article deals with issues for the backup set type NAS, UNIX-SSH, NFS, Local File System Backup from a Linux DS-Client.
Excluded Directories
When backing up any target UNIX machine (Local File System, via UNIX-SSH or NFS), the following directories are always excluded from backup (even if selected in a backup set):
/proc /sys /dev /devices /selinux
These directories constitute pseudo-file system(s), which do not contain physical files or do not contain persistent data. If excluded directories are skipped during a backup, a warning appears in the Event Log for that activity. Excluded Directories for SSH backups of SOLARIS machines In addition to the above general UNIX directory exclusions, the following directories are excluded from UNIX-SSH backup sets of SOLARIS machines:
/system/contract /system/object
and
<zone>/system/contract <zone>/system/object <zone>/proc
Note:
The zoneFS path can be shown with the zoneadm list function.
Backup of Hard Links

Hard Links are created in Unix-based file systems with the ln function. In general, if you want to perform backup and restore of hard links, you must create a backup set that includes all files that are linked through hard-links. If even one linked file (from a hard link group) is not included a backup set, then the backup will not be able to record all the hard-link information. Similarly, for a restore, if only some of the hardlinked files are selected for restore, then the restore will only link the hard-linked files that are restored. If it is desired to restore only one file, and preserve any existing hard-links, then use the 'Fast' restore option. Note: this will also change the data of the other linked files not restored.

Confidential.
By default, the Backup hard links option is selected for any new backup sets. This means the backup will record file and hard link information at backup time in order for the hard links to be restored. If the Backup hard links option is not selected for a backup set, this means any backed up hard link will be backed up and restored as a separate (individual) file. In this case, the backup set will not contain any hard link information. Even with the Backup hard links option selected, you must create a backup set that includes all the hard linked files. Otherwise a warning will appear in the Event Log for the backup activity and if you restore from that backup, your existing hard links will be broken. The same applies if you perform a partial restore of hard linked files.
Restoring Hard Links

Restoring hard links assumes the backup contains all hard linked files and file information. (For example: If the source computer has 5 files that are hard linked, your backup set must contain those same 5 files and the backup set must have the Backup hard links option selected.) The restore behavior for hard linked files depends on the Restore Method selected in the Restore Wizards Select restore options screen: Save / Use Buffer: This is the default restore method, which will restore the selected hard linked file(s) and recreate the hard links for those restored files. Fast: This method allows you to selectively restore the hard link data (inode information) from a single file while preserving the existing hard link information on the restore target. After restore, this effectively changes the data of the other linked files (that were not restored).
See Also
NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client) on page 112


Confidential.
Backup of NetWare Servers (DOS Partition)

Creation Date: March 10, 2000 Revision Date: December 21, 2005 Product: DS-Client (NetWare 6.x)
Summary
This article covers one of the methods you can use to backup the DOS Partition of a NetWare Server.
Mount the DOS Partition as a volume

1. Once NSS is loaded, issue the following command at the server console prompt:
dosfat.nss
2. The volume DOSFAT_C will be created and can be backed up by DS-Client.


Confidential.
Backup / Restore of Novell NetWare files from a Windows DS-Client

Creation Date: January 21, 2008 Revision Date: August 25, 2011 Product: DS-Client (Windows)
Summary
This article deals with Backup and Restore of NetWare files from a Windows DS-Client.
NOTE: You must install the corresponding Novell NetWare Client on the target backup/restore computer. There are several other Knowledge Base articles that deal with specific situations. These are listed below, under See Also.
Backup
Once Novell NetWare is properly configured, the NetWare files can be backed up (and restored) through: a File System backup set (See File System Backups on page 99.). Backup file path limitation The NetWare client API used by the Windows DS-Client has a 255 character limit. This means the path of any NetWare file being backed up cannot be longer than 255 characters. This includes the NetWareServername, the NetwareVolumename, the folders and the filename itself. Any files longer than this 255 character limit will fail to be backed up with either of the following errors:
"The filename, directory name, or volume label syntax is incorrect." - OR "The request is not supported."
The only backup solution is to shorten the path on the (NetWare) backup source.
Restore
Since NetWare files are backed up as File System backup sets, see the following restore sections for instructions: Restore File System Backups on page 225 Restore NetWare Servers (Files and NDS) on page 232


Confidential.
See Also
Novell NetWare Backups on page 115 Restore NetWare Servers (Files and NDS) on page 232 Setting up the Novell NetWare Client on the DS-Client computer on page 442 Backup of NetWare Servers (DOS Partition) on page 541 Backup / Restore of Novell NetWare files from a Linux DS-Client on page 544


Confidential.
Backup / Restore of Novell NetWare files from a Linux DS-Client

Creation Date: April 11, 2007 Revision Date: January 21, 2008 Product: DS-Client (Linux)
Summary
This article deals with setup of Novell NetWare for Backup and Restore of NetWare files from a Linux DS-Client. Once Novell NetWare is properly configured and its mount point is visible to Linux DS-Client, the NetWare files can be backed up (and restored) through: a Local File System backup set, if the file system is mounted on the DSClient computer; an SSH backup set, if the file system is mounted on a different network computer. Note: You cannot use the NFS protocol to browse to a mounted NetWare File System. Linux DS-Client can backup the following NetWare configurations: NetWare on Open Enterprise Server (with Novell Client for OES) NetWare on SuSE 9 (with Novell Client for SuSE 9) NetWare on SuSE 10 (with Novell Client for SuSE 10) NOTE: You must install the corresponding Novell NetWare Client on the target backup/restore computer.
Configuring NetWare Server

Once a NetWare volume is mounted and its share is visible to DS-Client, its files can be backed up and restored like any other pure data backup sets: On the NetWare Server, install Novell Client for the corresponding type of Operating System (Open Enterprise Server, SuSE 9, or SuSE 10). Novell Client automatically starts upon successful installation. Login to NDS using either gnwlogin or nwlogin utilities. By default, they are located in /opt/novell/ncl/bin; By default the Novell Netware of the server that logged in will be mounted on / var/opt/novell/nclmnt. If using the DS-Client on the NetWare Server, you can create Local File System backup sets to backup files under the mounted NetWare volume(s). If using DS-Client on another machine, you can create an SSH backup set to backup files under the mount point. You should be able to perform backup, disc/tape, blm, and restore. There are several other Knowledge Base articles that deal with specific situations. These are listed below, under See Also.


Confidential.
See Also
Novell NetWare Backups on page 115 Restore NetWare Servers (Files and NDS) on page 232 Setting up the Novell NetWare Client on the DS-Client computer on page 442 Backup / Restore of Novell NetWare files from a Windows DS-Client on page 542 Backup of NetWare Servers (DOS Partition) on page 541


Confidential.
Backup of Open Files

Summary
Since workstations and servers can have any number of open files during backups, those files might cause problems and/or backup errors. Open files can be backed up successfully, fail to be backed up, or be backed up with potential integrity problems. Depending on the type of open file and operating system of the server/workstation, steps can be taken to reduce or eliminate this Open Files Backup problem. Types of Open Files on page 547 Open File Backup Strategy Options on page 548 VSS (Volume Shadow Copy Service) on page 548 Conclusion on page 549


Confidential.
Types of Open Files

Type of Open file Backup Methods These files are just temporary storage and do not require backup/restore. System-only files (like backout.tts on NetWare servers or pagefile.sys on Windows servers) and temporary files created by various applications are useless and should be excluded from backups. The DS-Client has a list of the files that will be ignored during the backup process, thereby eliminating unnecessary errors (the DS-Client installation sets up a default list of System only files for Windows and NetWare computers). This list is found in the DSClient Configuration > Advanced Tab: Installation category > SystemFiles parameter. See DS-Client Advanced Configurations on page 458. The default list includes: system.da0, user.da0, pagefile.sys, win386.swp, backout.tts, btrieve.trn, net$obj.sys, net$val.sys, net$prop.sys, dsclient.mdb, dsdelta.mdb The DS-Client has separate backup set types for a significant number of common applications which use locked files (e.g. Databases). When backing up such resources, they are not backed up as files. Instead, the DS-Client will use the native backup API corresponding to the backup source (it will perform hot backup of such databases, without any locked files or consistency issues). The DS-Client automatically excludes known Special Files, like Registry and Bindery files during regular file system backups, in order to eliminate unnecessary errors. Any open file that does not belong to first two categories (Temporary or Special files) is considered a regular file. DS-Client will attempt to backup a regular file using the steps described below. Files can be opened by applications in different ways. In general, the DS-Client will be able to back up a file successfully as long at it has permission to read it. To improve the chance of reading a file, DS-Client has the following options: On read failure, the DS-Client can be instructed to retry up to 10 times with a userconfigurable delay between retries (Backup Set Properties > Options Tab). If a locked file can be opened for reading, the DS-Client will attempt to make a consistent backup by trying to prevent other applications from writing to the file, using 4 levels of locking (whole file lock, complete byte ranges lock, partial range lock and no lock usage). Locking options can be modified by the end-user (See below: Open File Backup Strategy Options on page 548). Pre/Post capabilities in the DS-Client allows a customized backup to be performed for special files/applications for which the DS-Client does not have a built-in backup set type. This allows the DS-Client to issue dump commands to 3rd party applications or to stop applications/service that keep files locked and once the backup is complete, to erase the dump files or restart/resume the application. (See Backup Set Options - Pre/Post on page 97.).
Temporary or System-Only Files e.g.: pagefile.sys backout.tts
Special File Types e.g.: MS Exchange Oracle DB2 MS SQL Server MS Outlook System State / Registry etc.
Files opened by other applications


Confidential.
Open File Backup Strategy Options

Each backup set is configured (Backup Set Properties > Options Tab) with a strategy to handle open files. Unless altered, the default setting will apply (Setup > Configuration > Defaults Tab). If the DS-Client encounters an open file during the backup process, it will deal with it as prescribed in the strategies below:
Strategy Try Deny Write Backup Strategy Description Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open for writing), place the backup file in 'Allow Write' mode. This mode prevents any other process from opening backup file for writing to, while the DS-Client has it open. DS-Client will not back up the file, if another process has already opened it for writing. (However, you may instruct the DS-Client to retry backing up the open file.) Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open for writing), then open in Allow Write mode and lock the file, thereby preventing any process from writing to the file for duration of backup. This ensures that the most recent version of the file is backed up. Allow another process to read/write to the backup file (no restrictions). Since other applications can write to the file while it is being backed up, this may affect file consistency.
Deny Write
Prevent Write
Allow Write
If the backup of an open file fails on the first attempt, the DS-Client can be instructed to retry up to ten times. Note: Even with the Open File Backup Strategy options, files that are completely locked will not be accessible (they will fail to be backed up with errors). However, these files can be accessed by using the VSS backup set option (See below: VSS (Volume Shadow Copy Service) on page 548). Once DS-Client can read the file, it can be backed up.
VSS (Volume Shadow Copy Service)

The DS-Client will fail to backup files that are completely locked (i.e. files opened with deny read/ write). Even if open files are backed up, those files may have potential integrity problems (as described above). If you must backup those locked files, then you can use the Backup through volume shadow copies File System backup set option. Windows operating systems (since Windows 2003) support VSS, which is a Windows feature that DS-Client can use to create an exact copy of the files, including all open files. VSS is configured from the Backup Set Properties > Advanced Options Tab (for Windows servers that have the service available). If configured, DS-Client will initiate a VSS snapshot for the specified computer (for any local volumes included in the backup) and perform the backup from the VSS snapshot. If the VSS snapshot fails, DS-Client tries to backup like a regular File System backup set (where the Open File strategy will apply). For more information about VSS, refer to the corresponding Windows Help.


Confidential.
Conclusion
To reduce problems caused by backup of open files: 1. Perform scheduled backups during off-peak hours. 2. Perform special file backups for appropriate backup types. 3. Exclude system and useless files to eliminate unnecessary errors.
See Also
Backup Set Options - Pre/Post on page 97 Backup using Microsoft VSS (Volume Shadow Copies) on page 550


Confidential.
Backup using Microsoft VSS (Volume Shadow Copies)

Creation Date: February 05, 2008 Revision Date: June 14, 2010 Product: DS-Client (Windows)
Summary
This article covers backup of Windows Servers (XP, 2003, and newer) using Microsoft VSS (Volume Shadow Copy Service). It explains how DS-Client works with VSS and when it is recommended to use VSS to perform backups.
Details
File System backup sets for Windows Servers (XP, 2003, and newer) may be configured to use VSS to perform the backup. This option must be specifically enabled for each backup set in the Set Properties Advanced Options Tab. During backup of sets configured to use VSS: 1. The DS-Client will connect to the source machine and will instruct the VSS service to take a snapshot of that machine. 2. After the snapshot is generated, DS-Client will continue its backup using the VSS snapshot. Note: In order to use the VSS backup method, sufficient storage must be available on the source machine in order to hold the snapshot. Note 2: Only one VSS snapshot of a volume can be taken at a time. This means that simultaneous snapshots of the same volume from different VSS-aware backup sets is not possible. If this is attempted, the error Another VSS backup already in progress. Failed to create new VSS Snapshots. will be reported. To work around these situations, you can either edit the backup schedules so that the backups run at different times, or adjust the VSSWaitSnapshotTimeout Advanced DS-Client Parameter (Setup menu > Configuration > Advanced Tab: Miscellaneous). 3. If any problems occur during the backup from the snapshot (or if the VSS snapshot fails), DS-Client will try to backup using the traditional Asigra Cloud Backup agentless backup (lock the files, open them, read the files, process the files for incremental forever, compression, encryption and send the files to the DS-System). 4. The "Do not involve writers" option is left unchecked by default (recommended). This means DS-Client will communicate with the applications that integrate with Microsoft VSS in order to produce the most consistent backup of data.
Backup of Windows VISTA and newer servers (File System backup sets)
For Windows VISTA and newer operating systems, VSS is always used to backup the System State and Services Database.
Common scenarios when to backup using VSS

Locked files. See How Asigra Cloud Backup handles locked files article in Backup of Open Files on page 546. Bare Metal Restore Other databases (not part of the special backup types available in the New Backup Wizard) if the database engine you are trying to backup integrates with VSS (has writers).


Confidential.
See Also
Backup of Open Files on page 546 Backing up Windows for Bare Metal Restore (BMR) on page 534.


Confidential.
Backup / Restore of Windows XP

Creation Date: April 10, 2006 Revision Date: April 10, 2006 Product: DS-Client (Windows)
Summary
This article covers various backup/restore Windows XP issues.
Backup of Windows XP from a remote DS-Client

In order to perform a full backup of a Windows XP computer, make sure the following requirements are met: The 'Simple File Sharing' option must be unchecked;
Windows Explorer > Tools > Folder Options > View > Use Simple File Sharing
Network Access: Sharing and security model for local accounts must be set to Classic - local users authenticate as themselves.
Start > Programs > Control Panel > Administrative Tools > Local Security Policy > Local Policies > Security Options > Network Access: Sharing and security model for local accounts > Classic - local users authenticate as themselves


Confidential.
Backup / Restore of Microsoft Exchange Server

Creation Date: June 19, 1997 Revision Date: January 10, 2012 Product: DS-Client (Windows) Summary on page 553 Microsoft Exchange Server Support Matrix on page 553 Backup on page 553 Restore on page 554 Requirements for Microsoft Exchange Server 2007 SP1 on page 555
Summary
This articles refers to the classic MS Exchange backup set type that uses the native Microsoft Exchange backup API and Windows Networking to perform backup and restore of target Microsoft Exchange Servers. Note: An alternate method of backing up a Microsoft Exchange Server is to use the VSS-aware backup set type. For more information, see Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) on page 640.
The DS-Client service allows you to backup live Microsoft Exchange Server databases (i.e. while the databases are running). For more information, or to compare the benefits of online/live versus offline backups, see Microsoft Knowledge Base article - Q237767. The machine on which the MS Exchange Server is running must have all the default administrative shares (C$, D$, ADMIN$).
Microsoft Exchange Server Support Matrix

Check the Matrix for supported Exchange Server Versions:
Exchange Version
Exchange Server 2007 Standard & Enterprise Edition
Platform for Exchange Server

Windows 2003 Server (x64 version) Windows 2008 Server (x64 version) Windows 2003 Server
Support status
Active Support Active Support Active Support Passive Support
Exchange Enterprise 2003 Windows 2000 Advanced Server
Matrix Legend: Active Support: DS-Client supports backup / restore of Exchange server. Passive Support: Backup / restore tests have not been performed on these platforms, but there should not be any technical limitations. Not Supported: Exchange server backup / restore is not supported. No Vendor Support: Vendor does not support installation of Exchange on these platforms.
Backup
The account that you are using either must be a member of the administrative group, or explicitly included in MS Exchange with administrator rights. If the DS-Client is not a member of the same domain as the MS Exchange server, you must enter the network credentials when creating the backup set (Select Server Wizard Tab). In the Enter

Confidential.
Network Credentials dialog, you must specify either a computer name or domain name for authentication. MS Exchange server will not accept <None>, as in this case DS-Client performs logon impersonation (and this is invalid, since the DS-Client is not a member of the same domain). You must also create an account on the DS-Client computer, which is exactly the same (name & password) as the MS Exchange server administrator account. This way, when the DS-Client computer performs the authentication, you can select DS-Client computer name in the "From" field. MS Exchange Backups are "packages" of files that are all interdependent. If one file is missing or corrupted, the entire backup session cannot be successfully restored. If for any reason, there is an error in the backup of the MS Exchange Server, DS-Client will delete all the files backed up during that session.
Restore
For restores of MS Exchange 2000: If, during restore, you receive the error "The server is not operational", make sure the DS-Client computer can resolve the fully qualified domain name of the Exchange computer through a proper DNS setting. In cases where you are performing disaster recovery drills, or an actual disaster recovery, several checks must be performed: 1. Assuming the machine that you backed up no longer exists (i.e. was destroyed), you must configure a new machine and install MS Exchange on it. If you had a backup set for the entire machine (including registry), you can restore immediately. Otherwise, follow the next step; 2. If you did not restore the registry, check the following: Make sure that the machine names are the same (the server that you are restoring to must have the same name as the server that you backed up). The same applies for the domain name and the administrator account. Make sure the location of the databases is the same (including the drive letters). Once you have all these checks performed, you can start the restore process. After the restore is complete, you should have no errors, and MS Exchange should be up and running. 3. For more information, see Microsoft Knowledge Base articles - Q175469, Q176239, and Q224977.


Confidential.
Requirements for Microsoft Exchange Server 2007 SP1

The following information is specific for backup and restore of Microsoft Exchange Server 2007 with Service Pack 1: 1. To adhere to the Microsoft Secure by Default initiative, the remote streaming functionality (server-wide) in Exchange 2007 SP1 is disabled by default. This functionality is required by the DS-Client in order to perform backup and restore of the Exchange server. To enable this functionality, edit the following registry value on the target Exchange server (using regedt32.exe):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Paramet ersSystem Name: Enable Remote Streaming Backup Type: DWORD Value: 0 = default behavior (remote backup disabled); 1 = remote backup enabled
2. When you apply SP1 to an existing MS Exchange 2007 server, the Microsoft version number changes from 8.0 to 8.1. Any existing Microsoft Exchange Server backup sets will not work. You can migrate an existing backup set (See Backup Set Migration on page 497.) or create a new one for the SP1 version.
See Also
Backup Set Migration on page 497 Troubleshooting: Microsoft Exchange Server Backup on page 556 Backup / Restore of Microsoft Exchange Server 2010 in DAG (Database Availability Group) configuration on page 558 Backup / Restore of Microsoft Exchange Server (VSS-aware backup sets) on page 640 Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery) on page 687 Alternate Location Restore of Microsoft Exchange Server 2007 (mailbox recovery) on page 689


Confidential.
Troubleshooting: Microsoft Exchange Server Backup

Creation Date: February 23, 2007 Revision Date: February 01, 2010 Product: DS-Client (Windows) Summary on page 556 MS Exchange backup set errors with Firewall on page 556 MS Exchange Server errors when backing up with firewall enabled on page 556 Error creating new MS Exchange server backup set on page 557 Information Store may crash during MS Exchange server backups on page 557
Summary
This Knowledge Base article contains a list of known errors, the reason(s), and suggested solutions.
MS Exchange backup set errors with Firewall

Problem: During MS Exchange server backup, you get the following error in DS-Client event log
Error returned from an ESE function call (%d). (-1003) (\\crsexc01\G$\Exchsrvr\First Storage Group\MDBDATA\zzArchiveMailboxStorePriv.stm )
Reason: One known reason for this problem is the firewall between DS-Client and Exchange server is enabled and blocks some ports. For example, after applying Windows XP SP2 to the DS-Client machine, the XP firewall will be enabled automatically and causes this error. These ports are not required directly by the DS-Client, but are required by the Exchange server functions that DS-Client invokes. Solutions: Disable the firewall; or If you must keep the firewall up and running, configure it to allow connections between the DS-Client machine and the Microsoft Exchange Server.
MS Exchange Server errors when backing up with firewall enabled

Problem: Microsoft Exchange Server experiences unexpected stops after a backup starts. Solution: Disable the firewall; These unexpected stops were not reproducible after disabling the firewall. --Problem: Backup or restore of Exchange set fails with one of the following errors:
"Error returned from an ESE function call (%d). (317)" "The remote procedure call failed."
Solution:

Confidential.
Disable the firewall.
Error creating new MS Exchange server backup set

Problem: When creating a new MS Exchange server backup, you get the following error when you select the server:
Error returned from a callback function call (0x%X).
Reason: You have tried to select the MS Exchange server by supplying its IP address. Solution: You must supply the fully qualified domain name of the Exchange computer. The DS-Client computer must be able to resolve the fully qualified domain name of the Exchange computer. This can be done through a proper DNS setting.
Information Store may crash during MS Exchange server backups

Problem: The MS Exchange server Information Store crashes during backup. Reason: When a backup session is started for an MS Exchange Server backup set, DS-Client invokes dedicated Exchange API functions that open a TCP/IP connection to the Exchange Server. The ports used may change from one session to another. If a firewall on DSClient computer, on Exchange Server or anywhere in between is blocking the required ports, the connection method will change to RPC. Eventually, this will also fail and may cause an Information Store crash. Solution: In order to prevent such events, the dsclient.exe must be added as an exception in your firewall configuration. All the steps taken by MS Exchange API / ESE Backup during a backup session are listed in the Operating System Event Viewer/application log on the Exchange Server computer. If you see the line Backup data transfer method is TCP/IP, this confirms TCP ports are available for use by dsclient.exe.
See Also
Backup / Restore of Microsoft Exchange Server on page 553 Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery) on page 687 Alternate Location Restore of Microsoft Exchange Server 2007 (mailbox recovery) on page 689


Confidential.
Backup / Restore of Microsoft Exchange Server 2010 in DAG (Database Availability Group) configuration
Summary
This article contains specific instructions related to Backup and Restore of Microsoft Exchange Server 2010 in DAG (Database Availability Group) configuration.
Backing up the Exchange Server part of DAG

1. To back up a Microsoft Exchange Server 2010 in DAG configuration, you must create a VSS-aware backup set and add the entire Exchange Server (Microsoft Information Store) as the backup item. (It can contain both the active mailbox databases and the replica mailbox databases under the Replica folder). 2. A DAG configuration may contain two or more mailbox database servers as part of the group. One backup set must be created to protect one exchange server by using its IP or computer name. If more servers that are part of the DAG need to be protected, then additional backup sets must be created for each Exchange server. 3. Follow the backup wizard to complete the backup set until you reach the following options on the Specify Backup Item Options / Set Properties - Items tab: Backup active database: If selected, DS-Client filters for the active Exchange databases from that backup item. Backup passive database: If selected, DS-Client filters for the passive Exchange databases from that backup item. Note: If you select both these options, the DS-Client will backup all databases in the backup item, regardless if they are active or passive. 4. If some database(s) do not require backup, you can exclude them after creating the backup set with the entire Exchange Server (Microsoft Information Store). Use the Edit option from backup set Properties and selectively exclude any mailbox(es) that are not required. If the entire Exchange Server (Microsoft Information Store) is the backup item, then the mailbox databases which are part of DAG will be backed up even if their status changes (switched from active to healthy status or from heathy to active status). If the backup set was created at mailbox database level (the backup set contains only a specific mailbox database part of DAG), the backup will not continue if the database status is ever changed (active to healthy or healthy to active).
Restoring the Exchange Server part of DAG

The active mailbox databases can be restored to their original location using the VSS Restore and File Restore options. Restores to an alternate location (another mailbox database from the same server) can only be performed with the VSS Restore option. To restore a mailbox database to a Recovery Database (RDB), you must select the File Restore option.
Confidential.

The healthy mailbox databases (replicas) may be restored to their original location using only File Restore option. The replica mailbox databases cannot be restored using the VSS Restore option because of a VSS Replica writer limitation.
See Also
Backup / Restore of Microsoft Exchange Server on page 553


Confidential.
Backup / Restore of Microsoft SQL Server (ALL VERSIONS)

Creation Date: April 30, 1997 Revision Date: July 24, 2012 Product: DS-Client (Windows)
Summary
The DS-Client software allows you to perform online backups of MS SQL Server databases. The DS-Client supports backup and restore of MS SQL Server versions 2000 and above. This article contains information in the following sections: Features Supported on page 560 Special requirement for support of MS SQL Server 2000 on page 560 Special requirement for support of Clustered MS SQL Server 2000 on page 560 Security and User Accounts on page 561 Backup Dump Devices on page 561 Using DBCC on page 561 Database Backup Policy on page 562 Advantages and Disadvantages of different DB backup policies on page 563 Restoring Databases on page 564
Features Supported
Features Skip Database Load Online Database Backup NT Integrated Security Database Server Browsing Alternate Server Restore Alternate Database Restore Backup Integrity Verification Truncate Transaction Log before Backup DB Consistency Check Dump to DS-Client Buffer/Pipe Multiple Instances on Same Computer Backup Transaction Log 2000 + + + + + + + + + + + + + + + + + + + + 2005 + + + + + + + 2008 + + + + + + + 2012 + + + + + + +
Special requirement for support of MS SQL Server 2000

You must have MS SQL Client Tools installed on the DS-Client computer in order to backup / restore MS SQL 2000 databases.
Special requirement for support of Clustered MS SQL Server 2000

In order to support clustered SQL 2000, the DS-Client computer must be running Windows 2000 Advanced Server.

Confidential.
Security and User Accounts

The DS-Client software requires either one or two user accounts in order to successfully backup an MS SQL Server. The number depends on the setup of the MS SQL Server:
Network user account This account is used when connecting to the computer where the MS SQL server is running. This account must have sufficient permissions (e.g. member of the Administrator Group).
This is a database user account. If the MS SQL server is configured for integrated Database user account security access, this account is not required and the network user account will be used for both network and database access.
Backup Dump Devices

Depending on the MS SQL Server's version and the backup set's configuration, the DS-Client will use different backup/restore methods:
Databases will be dumped directly to a disk file either on the MS SQL Server computer, or to an accessible UNC path (remote location). The file name will be in the form 'database.y', where 'y' is an internal number. After the database is dumped, the dump file will be backed up like a regular file and then removed. The backup set's configuration should provide the path for the dump location. You can enter a UNC path directly in the Dump Path field when you select the dump location. Databases will be dumped directly to a disk file on the DS-Client computer in the DS-Client buffer directory (this directory location is set up in the DS-Client Configuration dialog box - Parameters tab). You can use this option if you do not have enough space on the MS SQL Server computer. The database is dumped through a pipe. During backups, the MS SQL server writes to the pipe, and the DS-Client service reads from the pipe and sends data to the DS-System. The pipe is created on the MS SQL Server computer. Use this method if your database is too big to be dumped to a file with either of the above options. NOTE: You should only use this option if you have a consistently fast and reliable connection to the DS-System. In order to dump the transaction log, before backing up a database, the DS-Client will use the native dump transaction with NO_LOG statement.
Dump to disk file
Dump to DS-Client buffer
DS-Client Pipe
Truncate Transaction Log before Backup (up to MS SQL 2000)
The database must be configured with FULL or BULK_LOGGED recovery mode, otherwise this option will have no effect. If selected, the DS-Client will dump the Transaction Log and send it to the DS-SysBackup Transaction Log tem in addition to the database(s). (MS SQL 2005 and up) To view the transaction logs from the Restore Wizard, you must select the Advanced Option Latest generation of all data and click the Show Files button to display the files. Backed up log files have a *.log extension.
Using DBCC
DS-Client service can run a Database Consistency Check (DBCC) after the database is dumped. The DBCC will check the database and the database allocation ('checkdb' / 'checktable' and 'checkalloc' options). If using the DS-Client Pipe option, the DBCC is performed before the dump. In either case, the DS-Client service can be instructed not to perform the backup if DBCC errors are found.


Confidential.
Database Backup Policy

DS-Client supports additional backup options for Microsoft SQL Server 2005 / 2008 / 2012. These options can help reduce the backup time for very large databases (where the dump takes up significant time). You can configure the backup set to perform differential or incremental database backups (after the backup of a full dump). Differential backups contain all the changes to the database since the last full dump. Incremental backups contain only the changes to the database since the last backup. Database Backup Policy requirements: Windows DS-Client only. Target Microsoft SQL Server version must be 2005 / 2008 / 2012. (MS SQL Server 2000 always requires a full dump.) For Full dump + incremental backup, each target databases model must be full or bulk_logged recovery.
Full dump always [Default] This is the default behavior for all MS SQL Server backups. Each backup of the SQL Server performs a full dump of each database. Performs a full dump of the database on first backup, followed by differential backups until another full backup is needed (*). This policy can be used on MS SQL Server 2005 / 2008 / 2012 databases. The database can be selected with or without the backup transaction log option. Performs a full dump of the database on first backup, followed by incremental backups until another full dump is needed (*). This policy can be used on MS SQL Server 2005 / 2008 / 2012 databases. The database should be selected without the backup transaction log option. (Even if backup transaction log is selected, that option will be ignored if this backup policy is selected.) The databases Recovery Model must be: full or bulk_logged.
Full dump + differential backup
Full dump + incremental backup
(*) A full dump is needed (other than first time) when: a database has been backed up by another backup set (or manually from the SQL tools); a database has been restored (either from another database or an earlier generation); the database properties have been modified (recovery model switched to simple); local cache is used for the backup set (This can occur for Regular backup sets with the option Transmission cache on local storage, but only when a generation must actually pass through the local cache. If the connection to DS-System is down, then a full dump occurs and is written to the local cache. After that dump, DS-Client continues with the selected database backup policy.) the DS-Client requires a Master generation (configured in the MasterGenerations value of the DS-Client Advanced Parameters - Setup Menu > Configuration > Advanced Tab).
Note:
The DS-Client can only take advantage of the differential or incremental backup policy if the backup set (of the SQL database) is the only process that backs up that target. If another backup set is used to backup the database (or the internal SQL commands are used to perform manual backups / dumps), then the backup policy requires the next backup to be a full dump.
Database Backup Policy Full Backup Schedule Over-ride Rules: These rules are optional. They allow greater control over when a Full Backup can occur (e.g. not during business hours).

Confidential.
Warning: Full dumps can be delayed, but a full database dump needs to be performed at some regular frequency to protect the integrity of the database backup. By default, DS-Client allows a full backup to be skipped a maximum of 120 consecutive times. This number is configurable in the DS-Client Advanced Configuration options MaxNonFullDumps parameter (see: DSClient Advanced Configurations on page 458). In general, if using any skip full backup rules, you should force a full backup before this maximum interval occurs. Use the Full every... option(s) to specify that time.
Advantages and Disadvantages of different DB backup policies

Choosing the best database backup policy method depends primarily on the backup window and how often the backups need to be run. For example, a customer that needs to backup a 400GB database may not be able to backup every hour with the Full dump always policy, however the backup may be able to accommodate an incremental or differential dump every hour. The following table lists the advantages and drawbacks of each respective DB backup policy:
Backup Policy Full dump always Advantages No restrictions on the number of backup sets backing up a particular MS SQL Server. Less dump time of the data from the MS SQL Server, therefore less data transmitted from the source MS SQL Server to the DS-Client (over LAN) and possible storage savings on the DS-System because of the size of the incremental / differential generations. Even when a Full dump is required, DS-Client still processes incremental forever and only sends the delta changes to DS-System. Less dump time of the data from the MS SQL Server, therefore less data is transmitted from the source MS SQL Server to the DS-Client (over LAN) and possible storage savings on the DS-System because of the size of the incremental/differential generations. Even when a Full dump is required, DS-Client still processes incremental forever and only sends the delta changes to DS-System. Disadvantages Dump time required for each backup.
Full dump + differential backup
Only one backup set can backup the target MS SQL Server, since the backup set must maintain the record of differential backups. No manual backups from the SQL tools can be performed (otherwise a Full backup is required). Only available for Microsoft SQL Server 2005 / 2008 / 2012 databases.
Full dump + incremental backup
Backup using VSS (Separate VSS-aware backup set)
Avoids the dump time for the data.
Only one backup set can backup the target MS SQL Server, since the backup set must maintain the record of incremental backups. No manual backups from the SQL tools can be performed (otherwise a Full backup is required). Configuration requirements: Database Recovery Model must be full or bulk_logged, which means that more processing will occur on the MS SQL Server and more data and logs will be stored. Only available for Microsoft SQL Server 2005 / 2008 / 2012 databases. More data is transmitted between source MS SQL Server and DS-Client.


Confidential.
Restoring Databases
A database that was backed up using the dump to disk file option can only be restored using the same method. (i.e. you cannot restore such a backup using DS-Client Pipe.) The file name generated by the restore using the "dump to disk file" option will be in the form 'database.y', where 'y' is an internal number.
See also
MS SQL Server Database Backups on page 116 Restore MS SQL Server Backups on page 234 MS SQL Server Backup Sets (Alternate Location Restore) on page 266 Troubleshooting: Backup of Microsoft SQL Server 2000 Desktop Engine on page 567 Troubleshooting: Backup of Microsoft SQL Server 2005 (and up) and SQL Server 2005 Express (and up) on page 568 Restoring MS SQL Server Transaction Logs on page 709 Restoring the MS SQL Database Server MASTER Database on page 722


Confidential.
Backup / Restore of Microsoft SQL Server with less privileged users

Creation Date: March 15, 2011 Revision Date: March 15, 2011 Product: DS-Client (Windows)
Summary
This article shows the configuration requirements that must be performed if you want to backup / restore a Microsoft SQL Server with less privileged users (i.e. non-system administrators / nondatabase administrators). This applies to both backup set types currently supported (classic MS SQL Server backup set and the VSS-aware type).
I) Requirements to perform backup

In order to backup MS SQL Server databases using less privileged users (e.g. a regular user), that user must have: db_backupoperator role on the databases on the target server The following are some additional user requirements in order for the backup to be successful: 1. On Windows VISTA and later Operating Systems, there are UAC related requirements (in order to be able to access remote registry): Disable UAC (User Access Control) on the target MS SQL Server computer. - OR Use a domain account. When the computer is member of a domain, remote UAC does not apply when using a domain user account. - OR Disable UAC for remote connection to the target server if using a local account to connect to the target server. In order to do this you must set the registry key LocalAccountTokenFilterPolicy (DWORD) to 1. If the key does not exist, you must create it. This key is found in:
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System
2. Minimum privilege requirements for user performing the backup: The user must be a member of SQL Server target computers local Power Users. This is in order to be able to translate from a shared path to a local path and to create the SQL statement pointing to the local path (if applicable). - AND The user must have privileges to access remote registry (besides the UAC requirement). The easiest way is to make it a member of the Backup Operators group on the SQL Server target computer.


Confidential.
II) Requirements to perform restore

1. The user must be granted the dbcreator role for the database that must be restored. 2. The user must be added under the xp_cmdshell stored procedure properties, with EXECUTE permissions. 3. You must create an xp_cmdshell proxy Account for the user.


Confidential.
Troubleshooting: Backup of Microsoft SQL Server 2000 Desktop Engine

Creation Date: February 6, 2004 Revision Date: February 01, 2010 Product: DS-Client (Windows)
Summary
This article deals with backups of the Microsoft SQL Server 2000 Desktop Engine (MSDE).
Problem
Due to a Microsoft security fix in the MSDE, the databases backup through pipe does not work for instances build version >=818. Windows SharePoint Services 2003 is one example (there may be others) of an application that installs MSDE v.8.00.880 by default. When backing up databases from this instance using DSClient Pipe or DS-Client Buffer, DS-Client fails and records an error for each database backed up, like:
"Cannot open backup device \\.\pipe\model.1. Device error or device offline. See the SQL Server error log for more details. BACKUP DATABASE is terminating abnormally."
Workaround
There are three options when creating a SQL Server type set: 1. Backup through DS-Client Pipe. 2. Backup through DS-Client Buffer. 3. Backup through local buffer (it dumps the databases to a specified location on the same server as MSDE/SQL Server. Use the option 3. (above) in order to successfully backup MSDE instances build version >= 818.


Confidential.
Troubleshooting: Backup of Microsoft SQL Server 2005 (and up) and SQL Server 2005 Express (and up)
Creation Date: January 12, 2007 Revision Date: September 20, 2012 Product: DS-Client (Windows)
Summary
This article deals with backup of Microsoft SQL Server 2005 (and up), both the Full and Express versions.
Troubleshooting / FAQ / Error Messages

Problem If you try to backup a remote instance of Microsoft SQL Server or SQL Server Express, it may fail with the following error:
"SQL server does not exist or access denied. ConnectionOpen (Connect( )).SQL:exec xp_msver ProductVersion)"
Reason The remote SQL Server instance may not be configured for remote connections. By default, SQL Server Express is installed (configured) only for local connections. By default, MS SQL Server is installed (configured) for remote connections, but this might have been changed. Workaround Use the SQL "SQL Server Configuration Manager" tool: 1. Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager: Enable TCP/IP and Named Pipes for each of the instances you want to backup. 2. Start the SQL Browser service on the remote server. --Problem 64-bit Windows DS-Client fails to create a new MS SQL Server backup set (in New Backup Set Wizard) with the following popup error:
"Runtime Error! Program: c:\program files\CloudBackup\DS-Client\dsclient.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information."
Reason This is a Microsoft Bug with MS SQL Server 2005.


Confidential.
The 64-bit MS SQL Server 2005 release (prior to Service Pack 1) has a problem with native 64-bit applications that use SQL-DMO (SQL Distributed Management Objects).
Solution The MS SQL Server 2005 minimum requirement for DS-Client is Service Pack 1. Use 64-bit MS SQL Server 2005 Service Pack 1 for the DS-Client database. --Problem DS-Client backing up a mirrored MS SQL Server 2005 database receives the following error:
"BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database '<databasename>' because it is configured for database mirroring."
Reason This is a limitation with MS SQL Server 2005. Mirrored MS SQL Server 2005 databases do not support the Truncate Transaction Log backup option. Solution Truncate logs should not be used on backup sets connecting to a mirrored MS SQL Server 2005 database. (Do not select Truncate Transaction Log in the New Backup Set Wizard - Set Properties Items Tab screen.) You can turn this option off from Backup Set Properties > Items Tab: Truncate Transaction Log


Confidential.
Backup / Restore using UNIX-SSH

Creation Date: June 30, 2006 Revision Date: September 26, 2012 Product: DS-Client (Linux & Mac)
Summary
This article covers various backup/restore issues for backup sets using the UNIX-SSH protocol. This is the type of connection DS-Client opens to the target computer. To backup or restore, the DS-Client must run the corresponding script on the source / target computer in either PERL or PYTHON languages. SSH Requirements on page 570 SSH Limitations on page 570 SUDO Errors on page 571
SSH Requirements
1. The backup source machine must be a Unix system (Linux, Solaris, HP-UX, or AIX). 2. The source machine must have an OpenSSH compatible server installed and started. 3. The source machine must have either Perl5 (core function, 5.6 or beyond) installed, or Python (2.4) installed. [Alternatively, you can use the DIRECT option to run a specific script/binary located on the source machine.] 4. The SSH approach cannot scan the LAN to get an initial machine list. You must enter the IP of the source machine in the Path field (e.g. UNIX-SSH\10.20.30.100). The user or administrator can also put the initial machine list into the file hostlist_ssh located in the installation path (usually /opt/CloudBackup/DS-Client/etc). The following is a sample:
#================= sample hostlist_ssh begin ================= # format: (comments must begin with '#') # name_or_IP_address[:port] 10.20.30.101 10.20.30.102 10.20.40.33 10.20.40.34:2233 [shortdescription] (less than 20 chars) [Computer 1] [Computer 2] [Server A] [Server B] # SSH server running on port 2233
#================= sample hostlist_ssh end ===================
5. If PERL or PYTHON is not installed in the default path (usually /bin, /usr/bin, ...) on the source machine, you must enter the exact path in the Advanced connection options screen.
SSH Limitations
Due to a PERL limitation, UNIX-SSH backup sets can not backup files with a <tab> symbol at the end of the file name. If a file with this type of name is encountered, backup of that file will fail. The following error message will appear in the Event Log:
Open for read failed (cannot open file <file_with_path> for reading: No such file or directory)


Confidential.
SUDO Errors
If either of the following errors occur, the backup source computer may require an update to its sudoers file. Trying to login via SSH using "sudo as an alternate user option" results in the following error:
User Change failed ()
Attempting to run "ssh <ip> sudo -u <user name> perl/python" from a terminal window results in the following error message:
sudo: sorry, you must have a tty to run sudo
Solution: 1. Login as root on the backup source machine. 2. Use the visudo command to edit the /etc/sudoers file. 3. Disable the following line:
Defaults requiretty
To disable this line, either delete the whole line or comment it out (put a # at the beginning of the line). 4. Save and then exit the editor. 5. SSH should now work properly with the sudo as an alternate user feature.
Note:
See also


Confidential.
Backup / Restore of NFS

Creation Date: December 10. 2007 Revision Date: February 17, 2010 Product: DS-Client (Linux & Mac)
Summary
This article covers various backup/restore issues for NFS backup sets using the NAS, UNIX-SSH, NFS, Local File System backup type.
Configuring a source machine for backup through NFS using Linux DS-Client
Note: The following are general suggestions that do not take into consideration network security requirements. Consult your network administrator and NFS documentation for full details.
1. In order to backup a source machine that supports NFS (version 3 or higher), the NFS source machine must be configured to export the NFS share (assuming the source machine is an NFS server). 2. To verify if the source server is exporting the NFS share, run the following command on the DS-Client:
Shell> rpcinfo p NFS_server_address
3. If it is working, nfs should be listed in the output, and you should be able to connect to the NFS share via Linux / Mac DS-Client. Otherwise continue with step 4. 4. Strictly speaking, you only need to edit /etc/exports to get NFS to work with DS-Client. This file is on the source machine, and contains a list of entries. Each entry indicates a volume that is shared and how it is shared. Check the man pages (man exports) for a complete description of all the setup options for the file, although the description here will probably satisfy most people's needs. An entry in /etc/exports will typically look like this:
directory machine1(option11,option12)
For example:
/ 192.168.1.250(rw,no_root_squash)
The above line allows the DS-Client machine whose IP is 192.168.1.250 to have read and write access to the / folder. If the option no_root_squash is selected, then root on the DS-Client machine will have the same level of access to the files on the NFS share as root on the NFS server. 5. Save the file and restart the NFS daemon with the following command:
Shell> /etc/init.d/nfs restart
6. Now, the DS-Client machine should be able to connect to the NFS share.
See also


Confidential.
Backup / Restore of Oracle Database Servers

Creation Date: March 12, 2003 Revision Date: September 13, 2012 Product: DS-Client Oracle Backup Set Overview on page 573 Oracle Database Server Support Matrix on page 574 Backup / Restore of Oracle Database Servers using Windows DS-Client on page 575 Backup / Restore of Oracle Database Servers using Linux DS-Client on page 578
Oracle Backup Set Overview

This table summarizes the DS-Client capabilities to backup and restore online Oracle databases.
Functionality On a scheduled or an on-demand basis, the DS-Client will instruct the Oracles Recovery Manager (RMAN) to access the Oracle Server via IP (LAN, WAN, etc) and use the Oracle-supplied functions to perform a database backup (through Pipe or using dump files). The data is then compressed, encrypted and transmitted to the DSSystem. The first time this action is performed, the entire database is dumped and transmitted (creating a master). During subsequent backups, only the changes are transmitted (creating a delta). The DS-Client never accesses the Oracle database data files directly and therefore, there is never an issue with open and locked database files. The database does NOT have to be taken offline to perform the backup. SECURITY During the Oracle server backup (as with all backups), the database credentials (sysdba username and password) are entered and stored in the DS-Client database, using AES128 encryption. The backup data is encrypted with a security algorithm that is secure up to AES-256 (256-bit) with a private key known only by you (the customer). Your Service Provider will never have access to this information. The DS-System uses a one-way hash to validate encryption keys, however the hash cannot be used to recover the encryption keys. Items available for backup/restore - individual tablespaces - control file - archived logs - Whole database backup: Backup all items (individual tablespaces, control file, and archived logs) in one oracle database backup set. Create a file system backup set to backup only init<sid>.ora and pwd<sid>.ora. Options for backup: Logical Corruption Check Backup Only Current Archived Logs Truncate Transaction Logs Possible items to restore: - Original restore (restore to the original Oracle server) individual tablespaces control file + tablespaces + archived logs Whole database (including files init.ora & pwd.ora) - Alternate restore (restore to another Oracle server) All possible options in Original restore Restore only the dump files Options for restore: Restore only dump files Create temp tablespace


Confidential.
Oracle Database Server Support Matrix

Check the Matrix for supported Oracle Server Versions, and on which platform to install Linux DSClient or Windows DS-Client in order to backup and restore:
ORACLE Databse Server Enterprise Edition
Version Platform Running on ASM Standalone (Raw Devices) Oracle DB Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S Supp. Supp. Supp. Supp. Passive Supp. N/S Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S N/S Passive Supp. Supp. Supp. Supp. Supp. N/S Supp. Supp. Supp. Supp. Passive Supp. N/S Supp. Passive Passive Supp. Passive Supp. Supp. Supp. N/S Passive Supp. Supp. Passive Passive Passive N/S Passive Passive Passive Passive Passive Passive N/S Passive Passive Passive Passive Passive Passive Passive Passive N/S Passive Passive Passive N/S Passive Passive Supp. Supp. Supp. Supp. Supp. Supp. N/S Passive Passive Passive No VS Supp. Supp. Supp. N/S Supp. Supp. Supp. Supp. Passive Supp. N/S Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S Passive Supp. Supp. Passive Passive Passive Passive Passive Passive Passive Passive Passive Passive N/S Passive Passive Passive Passive Passive Passive Passive Passive N/S Passive Passive Passive N/S N/S N/S N/S Supp. Supp. Supp. Supp. N/S N/S N/S N/S Supp. Supp. Supp. Supp. Supp. Supp. N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. No VS Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. No VS Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S
DS-Client Linux
Red Hat Red Hat Red Hat SUSE ES / AS ES/ AS ES/ AS Linux Linux 4 Linux 5 Linux 6 Ent. 9 SUSE Linux Ent. 10 SUSE Linux Ent. 11
DS-Client Windows
Windows Windows Windows Windows Vista XP, 2003 2008 7 Ent., Ult. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp.
Windows XP, 2003, 2003 R2 (x86/x64) Windows Vista Business, Ent., Ult. (x86/x64) Windows 2008 (x86/x64) Windows 2008 R2 (x64) Windows 7 Pro, Ent., Ult. (x86/x64) 11gR2 Solaris 10 (SPARC 64 bit) HPUX Itanium 11.3 Red Hat ES/AS Linux 5, 6 (x86/x64) Oracle Enterprise Server 5.4 (x86/x64) Oracle Linux 6 (x86/x64) SUSE Linux 11, 11.2 (x86/x64) Windows 2008 (x86) Windows 7 Pro, Ent., Ult. (x86) 11gR2 EXPRESS Red Hat ES/AS Linux 5, 6 (x86/x64) (see Note 1) Oracle Enterprise Server 5.4 (x86/x64) Oracle Linux 6 (x86/x64) SUSE Linux 11, 11.2 (x86/x64) Windows XP, 2003 (x86/x64) Windows VISTA Ultimate (x86/x64) Windows Vista Enterprise (x86/x64) Windows 2008 x64 Red Hat ES/AS Linux 4 (x86/x64) Red Hat ES/AS Linux 5 (x86/x64) 11gR1 SUSE Linux 10 (x86/x64) RS6000 AIX 5L (64 Bit) up to 5.2 Oracle Enterprise Server 5.4 (x86/x64) AIX on Power System 5.3/6.1 SUSE Linux 11 (x86/x64) Itanium Integrity, HPUXi 11.23/11.3 Solaris 9 (SPARC 64 bit) Solaris 10 (SPARC 64 bit) Windows 2008 x64 Windows XP, 2003 Solaris 10 (SPARC 64 bit) Solaris 9 (SPARC 64 bit) 10gR2 Red Hat ES/AS Linux 4 (x86/x64) Red Hat ES/AS Linux 5 (x86/x64) SUSE Linux 9 (x86/x64) SUSE Linux 10 (x86/x64) RS6000 AIX 5L (64 Bit) up to 5.2 Itanium Integrity, HPUXi 11.23 10gR2 EXPRESS Red Hat ES/AS Linux 3 (x86/x64) (see Red Hat ES/AS Linux 4 (x86/x64) Note 1) SUSE Linux 9 (x86) Windows 2003 / XP Pro (x86)
Windows Vista Business, Ent., Ult. (x86) Supp.


Confidential.
ORACLE Databse Server Enterprise Edition

Version Platform Running on ASM Standalone (Raw Devices) Oracle DB Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. Supp. N/S Supp. Supp. Supp. Supp. Supp.
DS-Client Linux
Red Hat Red Hat Red Hat SUSE ES / AS ES/ AS ES/ AS Linux Linux 4 Linux 5 Linux 6 Ent. 9 N/S Supp. Supp. Supp. N/S Supp. Supp. Passive N/S Passive Passive Passive N/S Supp. Supp. Passive N/S Passive Passive Passive N/S Passive Passive Passive N/S Supp. Supp. Supp. N/S Supp. Supp. Passive No VS No VS No VS No VS SUSE Linux Ent. 10 SUSE Linux Ent. 11
DS-Client Windows
Windows Windows Windows Windows Vista XP, 2003 2008 7 Ent., Ult. Supp. Passive N/S N/S Supp. N/S N/S N/S N/S N/S N/S
Windows 2003 Windows XP 10gR1 Solaris 9 (SPARC 64 bit) Red Hat Enterprise Linux 3.4 SUSE Linux Enterprise Server 9 Windows XP, 2003 9iR2 Red Hat Enterprise Linux ES 3,4 SUSE Linux Enterprise Server 9 Red Hat Enterprise Linux AS 3
Supp. (Active Support): DS-Client supports backup / restore of Oracle server. Passive (Passive Support): Backup / restore tests have not been performed on these platforms, but there should not be any technical limitations. N/S (Not Supported): Oracle server backup / restore is not supported. No VS (No Vendor Support): Oracle client used by DS-Client to backup / restore Oracle server is not supported by vendor.
Note 1: You must install the full Oracle client (10gR2 or 11gR2) on the DS-Client that performs backup / restore of the target Oracle Express server. Do not install the Oracle Express client on the DS-Client.
Note 2: This matrix does not cover Oracle-SBT (System Backup to Tape), which is covered in separate documentation.
Backup / Restore of Oracle Database Servers using Windows DS-Client

For offline database backup / restore, the operations and requirements are the same as File System Backup and Restore. You can use the Pre/Post function to Stop/Start Oracle Server before/after backup and restore. (If your database is in NOARCHIVE mode, then you must perform offline backup of the database.) The following requirements must be met in order to perform online backup / restore of Oracle Database Servers.
General Requirements The user who performs Oracle Backup / Restore should have knowledge about the Oracle database file structure and instance management. The DB Administrator / Backup Operator must know the name of the Service when creating a new backup set. (You cannot browse the database(s) for names, therefore you must know the exact name in advance.) The credentials used for backup / restore of the Oracle database must have the sysdba privilege. You can not use an IP address to specify a computer for backup / restore. Only the computer name is allowed.


Confidential.
DS-Client Computer Requirements Windows XP / Windows 2003 / Windows VISTA / Windows 2008 / Windows 7. Oracle Client must be installed. It must be the same version as the Oracle Server you want to backup. If you want to backup different versions of Oracle servers, you must install each corresponding version of Oracle client on the DS-Client computer. (If you are using both 9i and 10g Oracle clients on the DS-Client computer, make sure 10g is not the first path in the PATH environment variable.) You must configure the Net service Name for this Oracle Client to connect to each Oracle Server you want to backup or restore. If the Oracle Instance is a shared server, set the Connection Type as "Dedicated Server". Recovery Manager (RMAN) utility must be installed. To backup / restore Oracle 9i and 10g, you must manually copy recover.bsq to %ORACLE_HOME%\RDBMS\ADMIN directory on DS-Client computer. Please see Oracle bug #2421470. You can find recover.bsq on the Oracle 9i Server in the %ORACLE_HOME%\RDBMS\ADMIN directory. Oracle Server Requirements [32-Bit Windows Platforms] orasbt.dll must be copied to the target Oracle Server's computer. Place it in the path \%SYSTEMROOT%\SYSTEM32 (System Root path). You can find this file in the DS-Client installation directory. [64-Bit Windows Platforms] orasbt_x64.dll must be copied to the target Oracle Server's computer. Rename it to orasbt.dll, then place it in the path \%SYSTEMROOT%\SYSTEM32 (System Root path). You can find this file in the DS-Client installation directory. Oracle Instance must be running in "ARCHIVELOG MODE" (this allows online backup of the database). Set the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter to slightly longer than the period (in days) between backups of the whole Oracle database (all tablespaces, control files, and archive logs). RMAN has a limitation of how many archived logs can be backed up at one time. Increase the "redo log file" size to reduce the number of archived logs. If you are using DS-Client Buffer or DS-Client Pipe as the dump path for backup, make sure both the "OracleServiceXXXX" and "Oracle TNSListener" services use the "administrator" account. Backup Requirements The Oracle database should be in Open state when you perform the online backup. In order to perform full or alternate restore of an Oracle database, the backup must be a full Oracle database backup (all tablespaces, archived log files, and control file). In addition, you must have a backup of the password file and the init file. The password file (e.g.c:\oracle\ora92\database\pwd<instance>.ora) and the init file (e.g. c:\oracle\admin\<instance>\pfile\init.ora) should be backed up in a File System backup set. You do not need to place online tablespaces in backup mode when performing backups. Restore Requirements There are the following requirements and limitations: To restore the Control File, you must start the database in nomount (started) state. To restore Tablespaces without the Control File, you must start the database in mount state. Otherwise, you must change the tablespaces offline. Tablespaces can be restored, however the logs will be applied to the present (unless DBPITR is performed). This means they will not be "as when backed up". The control file should only be restored when performing DBPITR (Database Point In Time Recovery). After restoring, the database will be opened with the "RESETLOGS" option. By doing this, you will not be able to restore any tablespaces backed up after that point in time (unless you restore the control file). When performing a DBPITR, all the files backed up in that particular session must be restored. For full restore to the original location, the requirements are the same as for Alternate Location Restore, except the target computer is the original computer. [Oracle 10g only] Before performing a DBPITR, if the backup and flash_recovery_area have different reset log times, you must rename the flash_recovery_area directory. After performing the restore, you should shutdown and manually restart the Oracle database (see Oracle Note: 286964.1).


Confidential.
Alternate Location Restore Requirements The Oracle Server (target restore server) must satisfy the requirements listed in the sections above. In addition, the following apply for Alternate Restore: 1.The backup must be a full Oracle database backup. You must also have a backup of the password file and the init file (this will be in a File System backup set). 2.The target restore computer must have an Oracle database service Instance of the same name. 3.The target restore computer must have the same tablespace path as the original backup (this can be created when setting up the database). This is because of Oracle limitations and specifications. All information about file structure is recorded in the Control File and the Oracle Database as a whole. 4.Restore the (File System) backup of the password file and the init file to the alternate computer. This is a separate backup set of the password file and the init file from the original backup computer. 5.Restore the full Oracle database backup. 6.If you choose a different dump path, only dump files are restored to that path. You must use RMAN to restore your Oracle database manually.


Confidential.
Backup / Restore of Oracle Database Servers using Linux DS-Client

For offline database backup / restore, the operations and requirements are the same as File System Backup and Restore (You can use the Pre/Post function to Stop/Start Oracle Server before/after backup and restore.). The following requirements must be met in order to perform online backup / restore of Oracle Database Servers.
General Requirements The user who performs Oracle Backup / Restore should have knowledge about the Oracle database file structure and instance management. The DB Administrator / Backup Operator must know the name of the Service when creating a new backup set. (You cannot browse the database(s) for names, therefore you must know the exact name in advance.) The credentials used for backup / restore of the Oracle database must have the sysdba privilege. DS-Client Computer Requirements DS-Client must be running on a supported Linux platform listed in the Oracle Database Server Support Matrix. Oracle Client must be installed on the machine running the DS-Client (this must be a full installation created from the Oracle Installer). It must be the same version as the Oracle Server to backup. You must configure the Net service Name for this Oracle Client to connect to each Oracle Server you want to backup or restore. If the Oracle Instance is a shared server, set the Connection Type as "Dedicated Server" using Net Manager (Oracle 9). Recovery Manager (RMAN) utility must be installed. To backup / restore Oracle 9, you must manually copy recover.bsq to $ORACLE_HOME/rdbms/admin directory on DS-Client computer. Please see Oracle bug #2421470. You can find recover.bsq on the Oracle 9 Server. The remote Oracle database server hostname must be configured in /etc/hosts file on the Linux DS-Client computer.


Confidential.
Oracle Server Requirements Oracle Instance should be running in "ARCHIVELOG MODE" (this allows online backup of the database). Set the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter to slightly longer than the period (in days) between backups of the whole Oracle database (all tablespaces, control files, and archive logs). RMAN has a limitation of how many archived logs can be backed up at one time. Increase the "redo log file" size to reduce the number of archived logs. Oracle Server should be a certified product. For example, Oracle 10.2 for Red Hat Enterprise Linux AS/ES 4, SuSE SLES 10, or Solaris 10 (64-bit). To use DS-PIPE for backup and restore, a library file must be copied to $ORACLE_HOME/lib on the Oracle server. This file must correspond to the Oracle servers platform. The files are found in the DS-Client installation directory in the sub-folder /Misc/Oracle_Classical_Library: libobk.so libobk-64.so [for Linux 32-bit Oracle database] Copy to $ORACLE_HOME/lib on 32-bit Linux Oracle Server. [for Linux 64-bit Oracle database] Copy to $ORACLE_HOME/lib on 64-bit Linux Oracle Server and make a soft link "ln -s libobk-64.so libobk.so". libobk.a [for AIX Oracle database] Copy to $ORACLE_HOME/lib on AIX Oracle server. libobk_ia64.sl [for HPUX Itanium oracle database] Copy to $ORACLE_HOME/lib on HPUX Itanium Oracle Server and make a soft link "ln -s libobk_ia64.sl libobk.so" libsbt64.so [for Solaris 64-bit Oracle database] Copy to $ORACLE_HOME/lib on Solaris 64-bit Oracle server and make a soft link "ln -s libsbt64.so libobk.so". libsbt32.so [for Solaris 32-bit Oracle database] Copy to $ORACLE_HOME/lib on Solaris 32-bit Oracle server and make a soft link "ln -s libsbt32.so libobk.so". Backup Requirements The Oracle database should be in Open state when you perform the online backup. In order to perform full or alternate restore of an Oracle database, the backup must be a full Oracle database backup (all tablespaces, archived log files, and control file). In addition, you must have a backup of the password file and the init file. The init file (e.g. admin/<instance>/pfile/init<instance>.ora) and password file (e.g. $ORACLE_HOME/dbs/ orapw<instance>) should be backed up in a File System backup set. A backup of the password file is necessary for any full or alternate restore of the Oracle database. You do not need to place online tablespaces in backup mode when performing backups. For Oracle backup using NFS protocol, you must supply the user account of root for the network credentials.


Confidential.
Restore Requirements There are the following requirements and limitations: To restore the Control File, you must start the database in nomount (started) state. To restore Tablespaces without the Control File, you must start the database in mount state. Otherwise, you must change the tablespaces offline. Tablespaces can be restored, however the logs will be applied to the present (unless DBPITR is performed). This means they will not be "as when backed up". The control file should only be restored when performing DBPITR (Database Point In Time Recovery). After restoring, the database will be opened with the "RESETLOGS" option. By doing this, you will not be able to restore any tablespaces backed up after that point in time (unless you restore the control file). When performing a DBPITR, all the files backed up in that particular session must be restored. For full restore to the original location, the requirements are the same as for Alternate Location Restore, except the target computer is the original computer. [Oracle 10g only] Before performing a DBPITR, if the backup and flash_recovery_area have different reset log times, you must rename the flash_recovery_area directory. After performing the restore, you must shutdown and manually restart the Oracle database (see Oracle Note: 286964.1). Alternate Location Restore Requirements The Oracle Server (target restore server) must satisfy the requirements listed in the sections above. In addition, the following apply for Alternate Restore: 1.The backup must be a full Oracle database backup. You must also have a backup of the password file and the init file (this will be in a File System backup set). 2.The target restore computer must have an Oracle database service Instance of the same name. This is to simplify the process of recovery. You must modify the initial file manually if you use a different Instance name. 3.The target restore computer must have the same tablespace path as the original backup (this can be created when setting up the database). This is because of Oracle limitations and specifications. All information about file structure is recorded in the Control File and the Oracle Database as a whole. 4.Restore the (File System) backup of the password file and the init file to the alternate computer. This is a separate backup set of the password file and the init file from the original backup computer. 5.Restore the full Oracle database backup. 6.If you choose a different dump path, only dump files are restored to that path. You must use RMAN to restore your Oracle database manually.
See Also
Troubleshooting: Oracle Database Servers on page 583 Oracle Database Point-In-Time Recovery (DBPITR) on page 724


Confidential.
Choosing the User for Oracle Backup / Restore Operations via SSH Dump
Creation Date: November 09, 2009 Revision Date: February 01, 2010 Product: Linux DS-Client
Summary
For backups, DS-Client instructs RMAN to perform a database dump then sends the files to the DS-System. The dump files are set to 640 permission and are owned by the Oracle user that RMAN used to create them (which is usually "oracle"). For restores, DS-Client places the dump files to be restored in the dump path with 777 permission and instructs RMAN to perform restore with those files.
Choosing a User for SSH

The combination of file ownerships and permissions (described above) restricts the range of eligible SSH users that can perform backup and restore operations in the absence of additional assistance (detailed in Choosing other Users for SSH on page 582). The possible users are: root "oracle" (see above) any user belonging to the same primary group as "oracle"


Confidential.
Choosing other Users for SSH

If you cannot use root, oracle or a member of oracles primary group, you must configure the dump path's extended attributes (POSIX ACL) to allow the designated user to perform backup and restore operations. Setting up Extended Attributes Both the designated and RMAN users need browse access along the dump path, read/write access in the dump folder, and default ACL to read and write in the dump folder. Here is a small example for Linux to setup the necessary extended attributes:
dump path RMAN user = /some_path/oraDump = "oracle"
designated user = "dscuser"
1. Make sure that the designated and RMAN users have browse access to the path. (-R makes the ACL settings apply recursively so ACL for oraDump is set as well):
setfacl -R -m user:dscuser:rx -m user:oracle:rx /some_path
2. Make sure that the designated and RMAN users have read/write permissions in the dump folder:
setfacl -m user:dscuser:rwx -m user:oracle:rwx /some_path/oraDump
3. Set default ACL for the dump folder so that files created in the folder will grant designated and RMAN users read/write permissions:
setfacl -m default:user:dscuser:rw -m default:user:oracle:rw /some_path/ oraDump
See Also
Backup / Restore of Oracle Database Servers on page 573


Confidential.
Troubleshooting: Oracle Database Servers

Creation Date: July 29, 2009 Revision Date: June 30, 2011 Product: DS-Client
Summary
This article covers the following troubleshooting issues for Oracle database backup sets: RMAN reports file corruptions during backup on page 583 Oracle restore fails on page 583 Oracle backup reports error ORA-12154 on page 584
RMAN reports file corruptions during backup

Problem DS-Client backup of Oracle server fails with the following RMAN error:
ORA-19566: Exceeded Limit Of 0 Corrupt Blocks From Backup
More information For more information, refer to the Oracle documentation: Metalink document #457422.1
Oracle restore fails

Problem DS-Client restore of Oracle server fails with the following error:
ORA-01152: File %s was not restored from a sufficiently old backup
More information For more information, refer to the Oracle documentation: Metalink document #243264.1 (Creating a Database From an Existing Database Fails with an ORA-01152 on Alter Database Open Resetlogs)


Confidential.
Oracle backup reports error ORA-12154

Problem DS-Client backup of Oracle server reports the following error:
ORA-12154: TNS: Could not resolve the connect identifier specified
More information This occurs if the Oracle Database Service Name has changed since this backup set was created. When you define an Oracle backup set, each backup item contains the Service Name as part of the path (e.g. an Oracle DB with the Service Name orcl might have backup items orcl\SYSTEM or orcl\*). If the Service Name is changed, DS-Client will fail to connect to the Oracle database with the ORA-12154 error. Resolution This is not likely to occur often (or at all), but in the event such a change is made, you must migrate the backup set in order to change the <oracle_service_name>\item_name from the old Oracle Service Name to the new one. To migrate the backup set: 1. Right-click the Oracle backup set and select Migrate.... The Migrate Backup Set wizard appears. 2. Select the computer to backup. In this situation, this will be the same machine as the original backup set. 3. When you click Next >, you are prompted to supply the Oracle Database credentials.
Adjust the backup sets database credentials to use the new service name. 4. Follow the rest of the Wizard screens to re-specify the backup set items and complete the migration. Once migration is complete, try backing up again to verify you do not get the ORA-12154 error. Another alternative is you can create an entirely new backup set and stop using the old one.
See Also
Backup / Restore of Oracle Database Servers on page 573


Confidential.
Backup / Restore of MySQL Database Servers

Creation Date: December 08, 2007 Revision Date: August 04, 2011 Product: DS-Client
Summary
This article covers various backup/restore issues for MySQL database backup sets. The following requirements must be met in order to perform backup / restore of MySQL Database Servers. General Requirements 1. The user who performs MySQL backup / restore should have knowledge about the MySQL database structure. DS-Client Computer Requirements 1. DS-Client backs up MySQL Server using the MySQL utilities mysqldump and mysql. The DS-Clients mysqldump and mysql utilities must be compatible with the MySQL version running on the source machine (MySQL server). 2. The following requirements depend on the type of DS-Client you are using: Windows DS-Client: The mysql utility must be listed in the PATH environment variable of the DS-Client computer. (If you must edit this variable, stop and restart the DS-Client service after making the change.) Linux DS-Client: The mysql utility must be listed in the PATH environment variable of user root on the DS-Client computer. Mac DS-Client: The path to the mysql utility must be added to the following file on the DS-Client computer:
/etc/rc.common
Connecting to MySQL using non-standard Ports

In order to backup a MySQL Server that is using non-standard ports, you must specify the port number when creating the MySQL backup set. For Windows DS-Clients: 1. You must specify the port numbers when creating the MySQL backup set. Sets Menu > New Backup Set. Select MySQL backup type and click Next. In the Select a MySQL Server to backup screen, you must specify the IP address of the server and the port number in the Path field, in the following format:
\\IP_address:Port_Number
For example, if you want to connect to a MySQL instance at IP address 10.20.30.111 using the port number 3310, you would type the following line into the Path field:
\\10.20.30.111:3310
Note:
If you do not specify a port number, Windows DS-Client will use 3306 as a default.
For Linux / Mac DS-Clients: 1. You can specify the port numbers when creating the MySQL backup set: Sets Menu > New Backup Set. Select MySQL backup type and click Next.

Confidential.
In the Select the source for this backup set screen, select Ask for database credentials. When the credentials screen appears, you will be able to enter the port number that the MySQL Server is configured to use. 2. You can also change the port number by editing the backup set properties (Backup Set Properties > Connection Options > Ask for database credentials: Port Number).
How to display the MySQL backup set type in the New Backup Set Wizard
If you do not see the MySQL backup set type option when you open the New Backup Set Wizard (Sets Menu > New Backup Set), your DS-Client may not be configured to support it. Make sure the following requirements are met: For Windows DS-Client: MySQL client software is installed. The folder that contains the MySQL utilities (such as: mysqldump.exe and mysql.exe) is in the PATH environment variable of the DS-Client computer. To verify if the path is included, launch a command window on DS-Client computer, and in the command prompt, run the command path. For Linux DS-Client: MySQL client software is installed. The folder that contains the MySQL utilities (such as: mysqldump and mysql) is in the search PATH of the DS-Client. To verify, edit the /etc/init.d/dsclient and in the line PATH, make sure the folder is listed. For Mac DS-Client: MySQL client software is installed. The folder that contains the MySQL utilities (such as: mysqldump and mysql) is in the search PATH of the DS-Client. The path to the mysql utility should be added to the following file on the MAC DS-Client computer: /etc/rc.common.
Backup / Restore of MySQL in a cluster

Backing up and restoring a MySQL Cluster database is the same as standalone MySQL database backup and restore.
Restoring Stored Routines to a MySQL database

MySQL added the capability to backup stored routines from its release version 5.0.13. In order to restore backed up stored routines, the user who performs the restore (MySQL database user) must have the following privileges for the MySQL database: Grant Create_Routines Alter_Routines
See also
MySQL Database Backup (Windows DS-Client) on page 131 MySQL Database Backup (LINUX DS-Client) on page 133


Confidential.
Backup / Restore of DB2 Database Servers

Creation Date: December 24, 2004 Revision Date: March 22, 2011 Product: DS-Client (LINUX)
DB2 Database Server Support Matrix

Check the Matrix for supported DB2 Server Versions, and on which platform to install Linux DSClient in order to backup and restore:
DB2 Server
Version Platform Solaris 10 (SPARC 64-bit) Red Hat ES/AS Linux 4 (x86/x64) Red Hat ES/AS Linux 5 (x86/x64) SUSE Linux 9 (x86/x64) 9.7 SUSE Linux 10 (x86/x64) SUSE Linux 11 (x86/x64) AIX on Power System 5.3 AIX on Power System 6.1 HP-UX-11.3-IA64 Solaris 10 (SPARC 64-bit) Red Hat ES/AS Linux 4 (x86/x64) Red Hat ES/AS Linux 5 (x86/x64) SUSE Linux 9 (x86/x64) 9.5 SUSE Linux 10 (x86/x64) SUSE Linux 11 (x86/x64) AIX on Power System 5.3 AIX on Power System 6.1 HP-UX-11.3-IA64
Linux DS-Client
Red Hat ES/AS Linux 4 No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support Passive Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Red Hat ES/AS Linux 5 Active Support No Vendor Support Active Support No Vendor Support Active Support Active Support Active Support Active Support Active Support Passive Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support SUSE Linux Enterprise 9 No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support No Vendor Support Passive Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support SUSE Linux Enterprise 10 Active Support No Vendor Support Active Support No Vendor Support Active Support Active Support Active Support Active Support Active Support Passive Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support SUSE Linux Enterprise 11 Active Support No Vendor Support Active Support No Vendor Support Active Support Active Support Active Support Active Support Active Support Passive Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Matrix Legend: Active Support: DS-Client supports backup / restore of DB2 server. Passive Support: Backup / restore tests have not been performed on these platforms, but there should not be any technical limitations. No Vendor Support: DB2 client used by DS-Client to backup / restore DB2 server is not supported by vendor.


Confidential.
Backup / Restore of DB2 Database Servers (Linux DS-Client)

The following requirements must be met in order to perform backup / restore of DB2 Database Servers. General Requirements The user who performs DB2 backup / restore should have knowledge about the DB2 database structure and instance management. The DB Administrator / Backup Operator must catalog the remote node and database name before creating a new backup set. You cannot browse the database(s) for names, therefore you must know the exact name in advance. The credentials used for backup / restore of the DB2 database must have the SYSADM, SYSCTRL, or SYSMAINT authority. DS-Client Computer Requirements DS-Client must be running on Red Hat ES/AS Linux 4/5, or SUSE Linux Enterprise 9/10. DB2 Client must be installed on the machine running the DS-Client. You must specify the DB2 Client library directory on the DS-Client. This is done in the DS-Client Configuration screens Advanced Tab (See DS-Client Advanced Configurations on page 47.): 1. DS-User > Setup Menu > Configuration. The DS-Client configuration screen appears. 2. Click on Advanced. From the Name drop-down list, select DB2 Client Library Directory. 3. In the Value Field, enter the path where the DB2 Client libraries are located on this DS-Client (e.g. /opt/ibm/db2/V9.7/lib64). 4. Click Apply. 5. Stop and start the DS-Client service / daemon. The DB2 node and database must be cataloged in order for the DB2 Client to connect to each DB2 Server you want to backup or restore.
DB2 Server Requirements DB2 Server should be a certified product.
Backup Requirements
The DB2 database must not be in use when you perform an offline backup. Otherwise an error will be reported. When you create a DB2 backup set, in the "Select the source for this backup set" screen, you must specify the DB2 server hostname or type its IP address in "Path" field. This must be the same as the one used in the catalog command. Linux DS-Client should have read and write privileges to access the transaction log directory on the DB2 database computer (for example ~db2inst1/db2inst1/NODE0000/SQL00005/SQLOGDIR/). Online backups are only available for databases configured with either logretain or userexit enabled. The backup set must specify that the backup is online or offline, as determined by the DB2 database configuration settings. (DO NOT CHANGE THIS PROPERTY. If you change this DB2 configuration, make a new backup set with the new option setting.) It is recommended that the online option setting not be changed for a demand backup. If it is changed, you must make a record of the change and the date


Confidential.
(manually on paper or other format), so that the information is available if a restore is performed.
Restore Requirements
The DB2 database must not be in use when you perform the restore. This requirement applies to all DB2 backup sets (whether configured for online or offline backup). The DB2 database must be configured for online or offline restore. This setting must match the Backup Set Properties > Options setting that was used for the backup.


Confidential.
Backup / Restore of PostgreSQL Database Servers

Creation Date: November 08, 2006 Revision Date: September 21, 2012 Product: DS-Client (LINUX)
Summary
This article covers various backup/restore issues for PostgreSQL database backup sets. The following requirements must be met in order to perform backup / restore of PostgreSQL Database Servers. General Requirements 1. The user who performs PostgreSQL backup / restore should have knowledge about the PostgreSQL database structure. 2. Configure each PostgreSQL database to be able to connect to other PostgreSQL instances: For PostgreSQL 7.x: Enable TCP/IP connection. In <pg_data_path>/ postgresql.conf, uncomment the line tcpip_socket=false and set the option to true:
tcpip_socket = true
For PostgreSQL 8.x / 9.x: In <pg_data_path>/postgresql.conf, add the line listen_addresses='*' as follows:
# CONNECTIONS AND AUTHENTICATION listen_addresses='*'
where <pg_data_path> is the path to the configuration files (usually "/var/lib/pgsql/ data" for the free installation from www.postgresql.org, or "/usr/local/pgsql/data" for the commercial package from www.commandprompt.com. DS-Client Computer Requirements The psql and pg_dump utilities must be listed in the PATH environment variable of the user 'root' on the DS-Client computer. The DS-Client computer's psql and pg_dump utilities must be compatible with the PostgreSQL version running on the source machine (PostgreSQL server). Configure the PostgreSQL database on the DS-Client computer to be able to connect to other PostgreSQL instances as described in the General Requirements above. PostgreSQL Server Requirements PostgreSQL Server should be a certified product. Configure each target PostgreSQL database to be able to connect to other PostgreSQL instances (to perform backup and restore) as described in the General Requirements above.


Confidential.
Connecting to PostgreSQL using non-standard Ports

In order to backup a PostgreSQL Server that is using non-standard ports, you must specify the port number when creating the PostgreSQL backup set. 1. You can specify the port numbers when creating the PostgreSQL backup set: Sets Menu > New Backup Set. Select PostgreSQL backup type and click Next. In the Select the source for this backup set screen, select Ask for database credentials. When the credentials screen appears, you will be able to enter the port number that the PostgreSQL Server is configured to use. 2. You can also change the port number by editing the backup set properties (Backup Set Properties > Connection Options > Ask for database credentials: Port Number).
Restore Requirements
The PostgreSQL database must not be in use when you perform the restore. This requirement applies to all restores (to original or to alternate location). The PostgreSQL Server where you are restoring must be compatible with the version of the PostgreSQL Server that was backed up. This is only an issue if the target restore server is different (Alternate Restore Location), or has been upgraded since the backup. In general, backups of databases residing on an older DB instance can be restored on a newer DB instance (but not the other way around).
Troubleshooting: Linux DS-Client with an Embedded database backing up PostgreSQL versions 9.2 (and up)
The v12 Linux DS-Client ships with an embedded PostgreSQL 9.1.1 database. If you want this DS-Client to backup a higher version of PostgreSQL (e.g. 9.2), you must install the compatible version on the DS-Client computer in order for it to use the compatible pg_dump tools. However, due to a startup timing issue (encountered if your Linux DS-Client is configured to automatically start after reboot), the DS-Client defaults to using the embedded (9.1.1) pg_dump tools. This issue will occur every time the machine is rebooted. Workaround 1: Each time after rebooting the machine, restart the DS-Client service. Workaround 2: Edit the /etc/init.d/dsclient file by adding /opt/PostgreSQL/9.2/bin or whatever the correct path is to the pg_dump tools (psql/pg_restore) to the PATH variable.
See also
PostgreSQL Database Backup (LINUX DS-Client) on page 139


Confidential.
Backup / Restore of Windows 2000

Creation Date: April 10, 2001 Revision Date: March 13, 2012 Product: DS-Client
Summary
This article covers various Windows 2000 issues. Note: As of v11.2, backup and restore of Windows 2000 is no longer supported. However, some information is relevant to higher versions that are still supported. In general, if no specific version is mentioned, these issues also apply to higher versions of Windows.
Encrypted Files
Encrypted files in Windows 2000 may experience Backup / Restore problems in versions prior to SP 3. To avoid these potential errors, upgrade your Windows 2000 computers to SP3. Windows 2000, SP1, and SP2 have the following known problems (from MSDN): Q307306: EFS Backup Functions May Not Work on Computers That Are Running Windows 2000. Q303873: File Creation on an NTFS Volume May Not Work Even If You Have the SeRestorePrivilege
System State
The System State can only be backed in its entirety. It contains the Registry, as well as other items that must be handled differently than normal files. The following are components of the System State (there may be less, depending on your version or if the component is not activated): Active Directory (You must have the same user account on both DS-Client computer and backup server.) Boot and System Protected Files Certificate Services Database Cluster Database COM+ Class Registration Database Registry SysVol In order to fully protect a Windows computer, make sure that the entire system drive is backed up in the same backup set as the System State.
Services Database
This contains databases that are not included in the System State, which still need to be treated in a similar manner to be successfully backed up. For a complete backup of a Windows computer, you should include the Services Database.


Confidential.
Special Options For Windows 2000 (and higher versions)

Backup data in Remote Storage Windows has the functionality (if enabled) to migrate infrequently accessed data from the local hard drive to directly attached tape libraries. The local disk usage is reduced by replacing the file with a link (shortcut). This is a Backup Set option that can be enabled or disabled. If enabled, all the data in Remove Storage represented by the link will be backed up. If disabled, only the link (shortcut file) will be backed up. Windows has an optional service 'Single Instance Store' to handle multiple copies of the same file on the computer. If enabled, local disk usage is reduced by placing one copy of the file in the Single Instance Store, with links (shortcuts) in all associated directories. If the Single Instance Store Service has been enabled on the Windows computer, you should configure the backup set with this option.
Backup Single Instance Store file data
Junction points are file links to other directories. If enabled in the backup set options, DS-Client will backup directories (all data) represented by the junction point. If disFollow junction points abled, DS-Client will backup only the link (shortcut). Notes: Junction points that are mounted FAT or FAT32 volumes are not supported. Overwrite Junction Point Overwrites any junction point(s) of the same name when restoring. Option to enable or disable.
Error Messages
Some error messages might appear in the DS-Client computer's log(s), which occur as a normal result of backing up Windows 2000. " DCOM had error "Class not registered" from the computer <<COMPUTER_NAME>> when attempting to activate the server: {XnnXnXnn-XXnn-nnXX-Xnnn-nnXnXnnnnnXn} " This happens if you create a new backup set for Windows 2000, and try to list all items in the System State. The error is reported because the DS-Client is trying to locate installed services for backup, and Windows 2000 reports this error to DS-Client.
Restore Limitations
Restoring Encrypted Files with Streams to Alternate Location: You will get error messages if you restore to the local computer by browsing the network. Use "My Computer" as the restore destination instead.
Restoring System State - Cluster Quorum

The Cluster Quorum is protected as part of the System State backup and restore. There are different scenarios for a restore process, and you may have to perform some manual actions after a successful restore. Please read this entire section carefully before starting the restore process. Microsoft Knowledge Base articles related to this subject are: 257905, 224999, 245762, and 258078. You may need to manually load the cluster quorum. In this case you will need a tool named dsclusrs.exe from Asigra. The tool can be found \winnt\cluster\Asigra directory after you successfully restore the cluster quorum. To manually load disk quorum, you must run "dsclusrs.exe f <quorum drive letter>". For example, if the quorum disk drive letter is e:, then run "dsclusrs.exe f e". Determine the type of cluster restore you are going to perform: You are performing restore on the same hardware (the disk signature of the quorum and resource disks are the same). 1.1 The cluster nodes are not domain controllers

Confidential.
In this scenario DS-Client will take care of the whole process. If you are restoring only one node or all of them, DS-Client will attempt to restore the cluster quorum if the "load cluster quorum" option is selected in the DS-User Restore Wizard. If you turn off this option, the data will be copied to \winnt\cluster\Asigra, and you have to manually load it by using the dsclusrs.exe tool. 1.2 The cluster nodes are domain controllers In this scenario you have to boot the target node(s) into "Directory Services Restore Mode". You are performing total disaster restore (including hardware changes). 2.1 The cluster nodes are not domain controllers If you are restoring both nodes, when installing the operating system, follow the same instructions as during the cluster installation (make sure that all nodes have seen the shared disks and have the same drive letters as before). Restore all nodes one by one, while keeping the others down. You can restore all nodes simultaneously, but make sure that they are not attached to the shared disks. At the end of a successful restore, shutdown all nodes and attach them to the shared disk(s). Power them up one by one. When you reboot the first node, the cluster service may fail to start due to the hardware changes (e.g. If you changed the quorum disk). This means you must manually load the quorum using the dsclusrs.exe tool. After you successfully load the quorum, the cluster service can be started. If you changed the resource disks, the resource disks will be offline in the cluster administrator view. In order to fix this problem you have to find out the new signature and edit the registry. Start "regedt32" and go to HKEY_LOCAL_MACHINE > Cluster > Resources and locate the resource disk. Under Parameters you will see the Signature. This is the signature the cluster service expects to see. To find out what is the current signature, go to HKEY_LOCAL_MACHINE > System > MountedDevices and locate the drive letter of the resource disk (e.g. If your resource disk is F, you should see something like "\DosDevices\F..." of type REG_BINARY). Please note that the signature here is stored in little endian format. If you have 78563412, the signature would be 12345678. You must enter this number for the Signature under the Cluster > Resources > GUID > Parameters. Once the correct signature is entered, you can restart the cluster service. If you have troubles with the service, please check the Microsoft Knowledge Base articles mentioned above. The correct quorum data would be located under \winnt\cluster\Asigra. This is the content of the quorum disk. 2.2 The cluster nodes are domain controllers Please read the DS-Client Knowledge Base article titled Bare Metal Restore of Windows (ALL VERSIONS) on page 693. It explains how to handle domain controller restores. We recommend you restore the primary domain controller first. This way, you will avoid problems with Active Directory (AD). If the target server does not have AD, make sure the "Load Cluster Quorum" option in the DS-User Restore Wizard is not selected, then start the restore. If the target server already has AD, you must boot in "Directory Services Restore Mode". After the reboot (in both cases), you must manually load the quorum data using the dsclusrs.exe tool from Asigra. You may also need to fix the cluster service as described in 2.1 above.


Confidential.
See also
Backup / Restore of Windows 2008 on page 596.


Confidential.
Backup / Restore of Windows 2008

Creation Date: May 24, 2010 Revision Date: March 13, 2012 Product: DS-Client (Windows)
Summary
This article contains the following sections with information specific to Windows 2008: Backup of a Windows 2008 (and up) Cluster on page 596 Restoring a Windows 2008 SP2 Cluster on page 596 DFS (Distributed File System) Namespaces on page 598
Backup of a Windows 2008 (and up) Cluster

Windows 2008 clusters (including higher versions, like 2008 R2), can only be backed up by specifying their Virtual Node IP address (and not by their Virtual Node name). This applies to all the applications that can be installed on these clusters (including Microsoft SQL Server, Microsoft Exchange Server, etc.).
Restoring a Windows 2008 SP2 Cluster

A cluster can work when a minimum of 2 resources are up and running and can communicate with each other. Therefore there are two restore cases: A. The cluster starts after the minimum 2 nodes are restored. See Case A. Cluster will be available after both nodes are restored. on page 596. B. The cluster can start after one node has access to cluster quorum. See Case B. Cluster will be available after Node1 is restored and witness disk signature corrected. on page 597. These restore examples use the following backup environment. Cluster configuration: Node and Disk Majority. Backup sets items: Node1 contains C$, Q$(cluster's share), System State, Services Database Node1 is the active node for the entire duration of the backup. Node2 contains C$, System State, Services Database Node2 is a passive node for the entire duration of the backup. Case A. Cluster will be available after both nodes are restored. Restore Steps: 1. Have available 2 machines with two network adapters each. Install the same operating system (Windows 2008) on each machine. Set up the IP addresses for both public and private cluster networks. 2. Keep the machine that has the IP of Node2, shut down. Restore the backup set of Node1. After the restore is finished, the Node1 machine must be rebooted to apply all changes.


Confidential.
The restore will not keep the network settings, therefore the IP addresses need to be reset. Bring quorum disk online (from Server manager > Disk Management). After this is finished, shut down the Node1 machine. 3. Keep Node1 shut down, and power on the Node2 machine. Restore the backup set belonging to Node2. After the restore is finished, the Node2 machine must be rebooted to apply all changes. The restore will not keep the network settings, therefore the IP addresses need to be reset. Bring quorum disk online (from Server manager > Disk Management). 4. Power on the Node1 machine. 5. Connect to the active node and open the Failover Cluster Management console. Run Validate a Configuration to make sure that the environment is correctly configured. Even if the validation does not return any error, the cluster might not work properly because some resources could be offline. If the Cluster Disk1 is offline, select Repair and after that, bring this resource online. If the Cluster Name is offline, select Repair Active Directory Object and after that, bring this resource online. Case B. Cluster will be available after Node1 is restored and witness disk signature corrected. Restore Steps: 1. Have available 1 machine with two network adapter. Install the same operating system (Windows 2008) on that machine. Set up the IP addresses for both public and private cluster networks. 2. Restore the backup set of Node1 (the one with the clusters share). After the restore is finished, do not reboot the Node1 machine. 3. In the Windows Operating System Event Log > Windows Logs > System, there will be an error message like:
"Cluster physical disk resource 'Cluster Disk 1' cannot be brought online because the associated disk could not be found. The expected signature of the disk was 'B46F3BE8'. If the disk was replaced or restored, in the Failover Cluster Management snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource."
4. You will not be able to use the suggested functions because the Failover Cluster Management will not be able to connect to the cluster (because there are not yet the minimum of 2 resources communicating to each other). At this stage, the restored Node 1 cannot see the quorum disk because it is a new disk, and it has a different signature than the original one. If you want to have the cluster running with only one node and the quorum disk, the quorum disks signature must be modified to the expected (original) signature. 5. To modify a disk signature you can use the Diskpart tool on the Node1 machine. To access the utility type "diskpart" at a Windows command prompt. Use the command list disk to show the available disks. Use the command select disk # to select the disk whose signature you want to change. (Where # is replaced with the corresponding disk number.) Use the command "uniqueid disk" to see the present disk signature.


Confidential.
If the original disk id was abcd1234, you would type the following command to change it:
"uniqueid disk id=abcd1234"
Note:
If later on the second node will be restored, this can be done. However you must first shut down Node1, then continue with steps 3, 4, and 5 from Case A. (See Case A. Cluster will be available after both nodes are restored. on page 596.)
4. Open the Failover Cluster Management console and connect to the cluster. If the Cluster Disk1 is offline, select Repair and after that, bring this resource online. If the Cluster Name is offline, select Repair Active Directory Object and after that, bring this resource online.
DFS (Distributed File System) Namespaces

Distributed File System (DFS) was introduced by Microsoft in Windows 2003 R2, which allows creation of DFS Namespaces. This enables you to group shared folders that are located on different servers into one or more logically structured namespaces. If you want to backup the data in a DFS Namespace, you must select the target backup computer by browsing for it through the network in the New Backup Set Wizard. (Do not select My Computer if you want to backup the local DS-Client computer.) Any namespaces visible from the selected computer will appear as a separate share in the New Backup Set Wizards Shares & Directories List. Select the DFS namespace as you would any other file system directory. No other special selections are required for backup or restore.
See also
Backup / Restore of Windows 2000 on page 592. Backing up Windows for Bare Metal Restore (BMR) on page 534. Important Notes for Bare Metal Restore on page 707.


Confidential.
Backup / Restore of E-Mails (using DS-MLR)

Creation Date: November 3, 2005 Revision Date: August 24, 2012 Product: DS-Client (Windows) with DS-MLR Service (DS-Recovery Tools)
Summary
NOTE: The DS-MLR Service is bundled with the DS-Recovery Tools installation. This article covers Backup and Restore issues for E-Mail message backup sets (using DS-MLR). DS-MLR Backup / Restore Support Matrix on page 600 Using DS-MLR with Microsoft Exchange Server E-Mails on page 602 Using DS-MLR with Microsoft Outlook E-Mails on page 603 Using DS-MLR with Lotus E-Mails on page 603 Using DS-MLR with GroupWise E-Mails on page 604 DS-MLR Computer Registry Keys on page 605 Selective Backup of E-Mails on page 606 Selective Restore of E-Mails on page 606 Troubleshooting / FAQ / Error Messages on page 607 DS-Message Level Restore (DS-MLR) is a solution to backup E-Mails from MS Exchange Server, MS Outlook, Lotus Notes / Domino Server and GroupWise at the individual message level. DS-MLR is part of the DS-Recovery Tools Module that must be enabled from the DS-System (by your Service Provider). DS-MLR is a Windows service. For a list of supported platforms, see DSMLR Installation & Setup on page 434. DS-MLR searches for E-Mails based on a user defined filter, then it transforms each E-Mail into a data stream and passes this stream to DSClient for processing (for backup to DS-System). During backup, DS-Client scans all items and only backs up the new or changed items. Changed items will be processed as delta and only the changes will be sent to DS-System. E-Mails are saved (along with any attachments) as individual objects on DSSystem. The DS-MLR service must be installed and running as follows:
MS Exchange MS Outlook Lotus Domino Lotus Notes GroupWise Install DS-MLR on the MS Exchange Server. (For Clustered MS Exchange Servers, DS-MLR must be installed and running on each node of the cluster.) Install DS-MLR on the computer with MS Outlook. Install DS-MLR on the Lotus Domino Server. Install DS-MLR on the computer with Lotus Notes. Install DS-MLR on the computer with GroupWise client.
The DS-MLR Service Account has some special requirements. See DS-MLR Installation & Setup on page 434.


Confidential.
DS-MLR Backup / Restore Support Matrix

This Matrix shows the objects DS-MLR can backup and restore:
MS Exchange Server Object Type Sub Type Appointment All day event Calendar Meeting request Recurring Appointment Recurring Event Recurring Meeting Contacts Deleted Items Drafts Incoming E-Mails with/without attachment. Inbox Journal Notes Outbox Sent Items Tasks Public folder Tasks Request Tasks FW E-Mails with/without attachment. Reply E-Mails - with/without attachment. Contacts (*1) Distribution List (*2) Backup / Restore of individual E-Mails Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
MS Outlook Object Type Sub Type Appointment All day event Calendar Meeting request Recurring Appointment Recurring Event Recurring Meeting Contacts Deleted Items Drafts Incoming E-Mails with/without attachment. Inbox Journal Notes Outbox Sent Items
Backup / Restore of individual E-Mails Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Confidential.
Contacts Distribution List
FW E-Mails with/without attachment. Reply E-Mails - with/without attachment.
Tasks Public folder Lotus Object Type
Tasks Request Tasks
Active Support Active Support Active Support
Sub Type Drafts Sent Inbox Folders Follow-Up Junk Mail
Backup / Restore of individual E-Mails Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Mail
Calendar To Do Contacts Personal Journal (*3) Trash Views Archive Tools Rules Stationery [Lotus Notes only] [Lotus Notes only]
Active Support Active Support Not Supported Not Supported Not Supported Not Supported Not Supported
GroupWise Object Type Cabinet Calendar Checklist Contacts Documents Incoming E-Mails with/without E-Mail attachment Mailbox (*4) Work in progress FW E-Mails Reply E-Mails Sub Type Backup / Restore of individual E-Mails Active Support Active Support Not Supported Not Supported Not Supported Active Support Active Support Active Support Not Supported
Active Support: DS-MLR can backup / restore this type of E-Mail object. Not Supported: DS-MLR does not support this type of E-Mail object. (*1) If the service account is not a member of the Domain Admins group and is not an Exchange Full Administrator, DS-MLR can backup Contacts, but the restored Contacts cannot be seen in the Outlook Address Book. (*2) If the service account is not a member of the Domain Admins group and is not an Exchange Full Administrator, DS-MLR cannot backup Distribution Lists. (*3) Personal Journal may require some configuration (See Using DS-MLR with Lotus EMails on page 603.). (*4) GroupWise supports E-Mails if the body size is no more than 32K (kilobytes).


Confidential.
Using DS-MLR with Microsoft Exchange Server E-Mails

DS-MLR supports backup and restore of individual E-Mails from the following Microsoft Exchange objects: Storage group Mailbox Store / Public Folder Store Users User Folders For each backup or restore request, DS-MLR checks if the user is a member of the Domain Admins group or is an Exchange Full Administrator (Exchange Organization Administrator for Exchange 2007), and if the service account has the "Receive As" privilege: If yes, DS-MLR will proceed using the service account and the user will be able to see all mail boxes. If no, DS-MLR will proceed using the users credentials (from the Backup Set Properties > Connection Tab). DS-MLR processes Exchange E-Mails based on their Exchange ID, which is usually unique for any Exchange object. In special scenarios (e.g. create calendar items based on a template) several items may have the same Exchange ID, and DS-MLR will only be able to backup the first item created with that ID (instead of backing up all items with the identical Exchange ID). In order to deal with this scenario, a dedicated switch can be added to the DS-MLR computers registry configuration:
ChangeDuplicateID
If this key is set to 0 any items with a duplicate Exchange ID are skipped and a warning is logged in the DS-Client event log. If this key is set to 1 any items with a duplicate Exchange ID are backed up (DS-MLR assigns a new Exchange ID for the items with identical ID). For more information, see: DS-MLR Computer Registry Keys on page 605. DS-MLR access depends on both its service account and the individual backup set credentials The DS-MLR service must be installed to run under an account that is a member of the Local Administrators group, or under the "Local System" account. When starting, it will attempt to grant itself Receive As privileges on the entire Exchange Server. If it is a Domain Admin account, this should succeed. The logic behind this is the following: A Domain Admin account has full privileges on that domain; any Domain Admin account should be able to grant itself the privileges necessary to back up all mailboxes under an Exchange Server. If a backup set uses Domain Admin credentials, it is expected that DS-MLR should be able to back up all mailboxes. The problem is that DS-MLR is able to back up those mailboxes only if it accesses the Exchange Server using a (service) account that has Receive As permissions. While it could make the necessary changes when running the backup, in a large organization that may take time to become effective; hence, DS-MLR attempts to grant itself Receive As permissions when starting the service and then, it will use its privileges whenever backing up a set configured with an account (backup set credentials) that is member of Domain Admins. Other sets will use whatever accounts they are configured with. Having said that, there are 3 distinct scenarios for exactly what credentials are used: 1. DS-MLR is installed under a non-domain user. In this case, DS-MLR will be able to back up one or more mailboxes, depending on the privileges of the user (which should be a domain user)

Confidential.
whose credentials are specified when creating the backup set. If the user is configured (on the Exchange Server) to have Receive As privileges on multiple or all mailboxes, DS-Client/DS-MLR will be able to back up those mailboxes. 2. DS-MLR is installed under a domain user, which is not Domain Admin. This is similar to the previous case: DS-Client/DS-MLR will be able to back up those mailboxes that the user (whose credentials are used for the set) has privileges to. 3. DS-MLR is installed under a Domain Admin user In this case, if the backup set is configured with a non Domain Admin user's credentials, DS-MLR will only allow access to those mailboxes that the user has rights to (as configured on the Exchange Server). If the set is configured with a Domain Admin users's credentials, DS-MLR will use its own service account privileges (which should have Receive As permissions on all mailboxes, that were configured at service start-up).
Using DS-MLR with Microsoft Outlook E-Mails

If you encounter any problems, read through the section Troubleshooting / FAQ / Error Messages on page 607. With DS-MLR you can backup the PST file while someone is using it (up to Windows 2003). However, this will only work if that logged on user is the same Windows user account as the one used by the DS-MLR service. If DS-MLR / Outlook are installed on Windows Vista (or newer Operating Systems) the backup is only successful if Outlook is closed. If you have configured MS Outlook to use a .PST file on a remote machine, remember that the DS-MLR service must always be installed on the MS Outlook computer. For MS Outlook configured for Exchange profiles, the E-Mails are sitting on the Exchange server. To access those E-Mails, the DS-MLR service account needs the "Receive As" privilege on that Exchange server. Otherwise, DSMLR will return an access denied error. (The DS-MLR service account must be recognized on the Exchange server.) Note: Using DS-MLR to back up an MS Outlook Exchange profile is not recommended. In such a situation, it is better to install DS-MLR on the Exchange Server itself. Then, you can use DS-MLR to backup any of the Exchange mailboxes. You can restore backed up E-Mails to their original location or to an alternate location.
Using DS-MLR with Lotus E-Mails

For backup of Lotus Notes / Domino Server, the DS-MLR Service Account must be a local administrator. You can restore backed up E-Mails to their original location or to an alternate location. For alternate location restores: you can only restore a directory to the <username>\Folders directory. This is a Lotus limitation. For backup of Personal Journal: the Journal must already be created, otherwise the option does not appear in the New Backup Set Wizard. For restores of Personal Journal: make sure the Journal database exists in destination machine, otherwise the restore will fail.
Confidential.

By default, the name of the Journal database is Notebook.nsf (in versions prior to Lotus 8.5 the name was journal.nsf). If the name is different from the default name (for example: Myjournal.nsf), then you must add the following line to the notes.ini, which is located under Lotus\Notes:
JOURNAL=Myjournal.nsf.
The following are known limitations of the Lotus API that directly affect the performance of the DS-MLR: E-Mails received in the Lotus Notes / Domino Server inbox that were created by other E-Mail applications (e.g. Microsoft Outlook, python script, etc.) are not stored in the native Lotus format. Since DS-MLR uses the Lotus API for backup / restore of the Lotus Notes / Domino Server, any backups of these types of E-Mails may lose significant amounts of content (like attachments) and / or formatting. (E-Mails created in Lotus are not affected.) Memory is not released by the dsmlr.exe application when backing up Lotus E-Mails. This is a direct result of the Lotus API, which does not release all the memory used and causes the dsmlr.exe memory usage to increase over time (especially in high data traffic environments). The only workaround is to monitor usage and periodically stop and restart the DS-MLR service.
Using DS-MLR with GroupWise E-Mails

For backup of GroupWise Servers, the DS-MLR Service Account must be a local administrator. DS-MLR currently supports E-Mails whose body size is no more than 32K. You can restore backed up E-Mails to their original location or to an alternate location. Make sure the GroupWise client is accessible. Test this by verifying you can send and receive E-Mails through it without problems. Otherwise, you will get a MAPI error when you try to create a GroupWise backup set. DS-MLR can work with GroupWise folders that contain up to 65535 E-Mails. The reason is because DS-MLR calls GroupWise Object API Folder>get_Messages() and this function returns an exception when the target folder contains more than 65535 E-Mails. This number may vary in different versions of GroupWise (65535 is the number for GroupWise 6.5). If the backup folder contains more than 65535 E-Mails, the folder will be backed up with no items in it (i.e. it will be empty).


Confidential.
DS-MLR Computer Registry Keys

The DS-MLR installation configures some registry parameters in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DS-Message Level Restore\Parameters
IMPORTANT: These keys are set in the registry of the computer where the DS-MLR is installed. Some keys are not installed by default and can only be manually added. Since DS-MLR does not have a GUI interface, the following table lists the possible keys, values and effect.
Registry key Name LastRunningDSMLR LotusDomino NotesIniPath NovellUser NovellPsw GWIPAddress GWPort GWTAppKey LogConfiguration SkipUnread Type String Binary String String String String String String String Dword Backup Set All Lotus Lotus GroupWise GroupWise GroupWise GroupWise GroupWise All GroupWise Installed Default Description by default Value Yes Yes Yes Yes Yes Yes Yes Yes No No 0 1677 The version of the last dsmlr.exe that ran on the local computer. The password for Lotus Domino. The path of notes.ini file. The Novell user name. The Novell user password. The GroupWise server address. The port number of GroupWise POA. The Trusted Application Key of GroupWise Domain. The path to the logconf_mlr.cfg file. If this value is not 0, all unread message will be skipped during backup. In the event of a failure to save the attachment of an E-Mail, DS-MLR will continue backup of this E-Mail and report a warning. Otherwise, DS-MLR will not be able to backup this E-Mail. This value is the number of seconds before release of the main session. 0 means do not try to release the main session. If this value is 0, DS-MLR will not try to use MAPI. If this value is 0, DS-MLR will try to use CDO first. When using MAPI to save an E-Mail with thousands of recipients, MAPI may hang. If you add this value, it will avoid this situation. If the length of from / to address exceeds this limit, DS-MLR will not try to use MAPI. -1 means no limit. This is the wait time (in seconds) when trying to create a MAPI profile. This is the wait time (in seconds) before killing a non-responding thread. Maximum number of logs DS-MLR keeps for each thread. If this value is 1, DS-MLR will create a new EMail ID for duplicated items.
GWSkipAttachment
Dword
GroupWise
No
LotusSessionExpire ExchangeMapiEnabled ExchangeMapiFirst
Dword Dword Dword
Lotus Exchange Exchange
No No No
0 1 1
ExchangeMapiAddressMaxLength
Dword
Exchange
No
-1
ExchangeCreateProfileTimeout ThreadTimeout MaxThreadLog ChangeDuplicateID
Dword Dword Dword Dword
Exchange All All Exchange
No No No No
20 0 100 0


Confidential.
Selective Backup of E-Mails

If you want to backup specific E-Mails from specific folders (instead backing up all of them), the following filters are available when configuring a backup set: 1. Exclude button (Select Directories/E-Mails for Backup screen): When you create or edit a backup set, you can exclude specific objects. For example: you can add a Storage Group/Mailbox, then exclude specific users from backup. This filters at the folder-level. 2. Regular Expression (Select Directories/E-Mails for Backup screen): When you create or edit a backup set, you can use the RegEx button to define a regular expression that can exclude objects at any level. You must know the Regular expression syntax. For example, if you have 1000 users in the mailbox store and you do not want to backup any Deleted Items folders, you can add the Regular Expression .*\\Deleted Items (without quotes). This saves you from manually excluding all 1000 folders using the Exclude button. 3. Filter (Specify backup item options screen): This screen allows you to filter E-Mails at the individual message-level (you can filter for or filter out). Multiple filters can be created and applied to the same backup set.
Selective Restore of E-Mails

You can restore backed up E-Mails to their original location or to an alternate location (as long as the alternate location computer has a DS-MLR service installed and running). You can manually select backed up E-Mails to restore, or you can use filters to perform selective restore.


Confidential.
Troubleshooting / FAQ / Error Messages

MS Exchange Question / Problem You get the error System 0x80550053 in the DS-Client Event Log. Explanation DS-MLR is backing up an Exchange Public Folder that is also a Replication Folder. Solution / Workaround Add the public folder into the Replication List on the Exchange Sever. Question / Problem The backup fails with the message: "DS-MLR could not open the specified MS-Outlook store." Explanation
1.
MS Outlook
This is due to a Microsoft bug that only occurs for the following:
2. German Windows 2003, and Outlook 2003 with a .PST file configured on a remote mapped drive, and Backup of Outlook E-Mail messages using DS-MLR. Solution / Workaround Instead of using a mapped drive (e.g. F:) for the .pst file, use a UNC path (a path in the form \server\share\directories\filename.pst). The DS-MLR service logon account must have full rights to the UNC path. Question / Problem Can I backup an Outlook PST file that is open? Explanation Only if DS-MLR / Outlook are installed on Windows 2003 and if the current logged on user is the same user as the DS-MLR service account. If DS-MLR / Outlook are installed on Windows Vista (or newer Operating Systems) the backup is only successful if Outlook is closed. Solution / Workaround N/A Question / Problem Can I backup an Outlook profile that is connecting to an Exchange mailbox? Explanation There are two kinds of MS Outlook profiles: Exchange and Internet. Solution / Workaround For Internet Profiles, the E-Mails are downloaded from the E-Mail server (Exchange, etc.) and stored in the local PST file. DS-MLR can read those E-Mails. For Exchange profiles, the E-Mails are sitting on the Exchange server. To access those E-Mails, the DSMLR service account needs the Receive As privilege on that Exchange server. Otherwise, DS-MLR will return an access denied error. Question / Problem I have more than one Personal Folder (PST file) in my Outlook Mailbox, but only one of them gets backed up. Explanation MS Outlook allows its Mail users to add multiple Personal Folders to their account (pointing to different PST files). However, if the name of the folder is the same, this duplication is not recognized by the DS-MLR. In these cases, only the first folder that is backed up will continue to be backed up. Solution / Workaround This is only an issue if the mailbox user has two or more PST files with the same name (e.g. both are called Personal Folder). MS Outlook recognizes these as different folders even though they have a duplicate name because they point to different PST files. The workaround is to rename the duplicate folder(s), so each has a unique name (for example Personal Folder 2, Personal Folder 3, Personal Folder n).
3.
4.
5.


Confidential.
6.
Question / Problem An MS Outlook backup fails with the message: "The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance." Explanation If you confirm the Exchange Server is running properly, and that there are no network problems, this may be a problem with your MS Outlook profile configuration. There are two kinds of MS Outlook profiles: Exchange and Internet. For Exchange profiles, MS Outlook must supply the correct username and password for the desired mailbox. This problem may occur if the DS-MLR computer is not in the same domain as the Exchange server and/or the DS-MLR service account is not a Domain Admin for the Exchange servers domain. Solution / Workaround Save the username and password of the mailbox in Outlook with the option Remember my password. NOTE: Using DS-MLR to back up an MS Outlook Exchange profile is not recommended. In such a situation, it is better to install DS-MLR on the Exchange Server itself. Then, you can use DS-MLR to backup any of the Exchange mailboxes.
See Also
E-Mail Messages (DS-Recovery Tools) on page 141 DS-MLR Installation & Setup on page 434


Confidential.
Backup Comparison: Microsoft Exchange Server vs. Message Level Restore

Creation Date: July 19, 2007 Revision Date: July 19, 2007 Product: DS-Client (Windows) with DS-MLR Service (DS-Recovery Tools)
Summary
NOTE: The DS-MLR Service is bundled with the DS-Recovery Tools installation. This article gives comparisons for when you might protect a Microsoft Exchange Server with an Exchange Server database backup set, with DS-MLR (message level restore), or with both.
Microsoft Exchange Server database backup set

Restoring a backup of an Exchange database will roll-back the whole Exchange Server to that last successful backup time (unless you manually apply the transaction logs). This solution is best for large scale recovery situations (e.g. disasters, server failure, etc.). If you only need to recover one or two E-Mails, the down-time may be a consideration against restoring the entire database.
DS-MLR backup set

The benefit of message-level restore is the very precise granularity of the restore item. Restoring an individual message or mailbox is much faster than rolling back an entire database to the last backup. Since DS-MLR treats each E-Mail object as a separate backup item, it can be somewhat slower when it has to backup many small E-Mails.
DS-MLR on: MS Exchange Server This configuration allows you to perform message-level backups from all mailboxes on the MS Exchange server. The main point is to provide message-level backups of the local .PST file. This is for an MS Outlook installation configured with an Internet profile (a profile that downloads all E-Mails to the local computers .PST file). Though it is possible to backup an MS Outlook Exchange profile (an Outlook profile configured to read E-Mails that reside on an MS Exchange server), in such a situation it would be better to install DS-MLR on the Exchange Server itself (see above).
MS Outlook
Both types of backup sets

The only consideration is cost (duplication). Otherwise, you can take advantage of the strengths of both.
See Also
Backup / Restore of Microsoft Exchange Server on page 553 Backup / Restore of E-Mails (using DS-MLR) on page 599


Confidential.
Backup / Restore of System i Server

Creation Date: February 16, 2006 Revision Date: December 21, 2011 Product: DS-Client
Summary
This article covers the following System i Server issues: Unix DS-Client issues on page 610 DS-Client performance considerations on page 610 Backing Up and Restoring Private Authorities on page 610 Configuring the System i Server on page 611 Services Required on the System i Server on page 611 System i Server Backup Checklist on page 612 System i Server Disaster Recovery on page 612 Known System i Server backup issues: on page 613 Known System i Server restore issues: on page 614
Unix DS-Client issues

Windows DS-Client is recommended for backups of System i Server because it uses IBM iSeries Access to communicate with the System i Server. Unix DS-Client uses FTP to communicate with the System i Server.
DS-Client performance considerations

If you create System i Server backup sets with the "Individual obj." option selected, the following performance considerations apply: 1. The backup performance will be affected. 2. If the saved library contains a large number of small objects, the backup performance will be further significantly affected. 3. If you only wish to restore certain objects from the backup set, this option will improve the restore performance. If you plan to restore the entire library, do not to use this option.
Backing Up and Restoring Private Authorities

The "Backup Private Authorities" backup set option applies to System i objects with the Private Authority (PVTAUT) parameter (This parameter was introduced in IBM i 6.1). When PVTAUT is set to *YES, you will be able to save the private authorities attached to your saved objects. These updated commands will store and restore Public Authorities, Owner and object authorities, Primary group and primary group authorities, and the names of authorizations lists linked to the saved object. NOTE: IBM cautions against using this option for .individual objects only because PVTAUT increases the amount of time needed to save an object. It is not recommended that you select this option for large scale backup and recovery of user data.


Confidential.
Configuring the System i Server

The following configurations must be made on the System i Server before backups / restores can be performed. 1. Create a special user on the System i Server for the purpose of backup. Do not use this user for any other purpose. This user must also have: the user class *SECADM on its user profile the special authorities *SECADM *ALLOBJ *JOBCTL the *SAVSYS special authority if a backup of the system info is required You can change the above parameters using the following command:
===> CHGUSRPRF USRPRF(user_name) USRCLS(*SECADM) SPCAUT(*SECADM *ALLOBJ *JOBCTL)
2. In order to exchange data between a System i Server and the DS-Client, the folder DSBUFFER and one or more subfolders must be created in the "root" IFS system. To create these folders from the command prompt, type the following command(s):
===> MD DIR('/DSBUFFER') ===> MD DIR('/DSBUFFER/folder_name')
3. Create two libraries on the System i Server: LIBIN and LIBOUT. These are the locations where DS-Client creates the save files (the System i Server equivalent of a database dump file). To create these libraries you can use the following commands:
===> CRTLIB LIB(LIBIN) ===> CRTLIB LIB(LIBOUT)
The LIBIN and LIBOUT libraries are used as a buffer to transfer save files from or to the System i Server. In addition, these libraries could be used by the System i Server administrator to locate a save file for a manual restore (in case the "Restore only dump file" option is checked, or on unsuccessful completion of a restore process). 4. [Windows DS-Clients only] Install iSeries Access for Windows on the DS-Client computer using the following installation program:
\\<System i Server>\QIBM\ProdData\Access\Windows\Install\Image\Setup.exe
Refer to your iSeries Access for Windows documentation for further instructions. 5. DSBUFFER share: In order to create and execute backup sets, the DSBUFFER folder must be shared (with read/write permissions). You can manage the DSBUFFER share in the iSeries Navigator or System i Server Operations Navigator. 6. Firewall: If there is a firewall between the DS-Client computer and the System i Server to backup, the ports 139, 449 as well as the ports between 4400 and 4407 must be opened.
Services Required on the System i Server

The System i Server must be running the TCP/IP jobs. They can be started with the STRTCP command. To start the TCP application server jobs individually, you can use the STRTCPSVR command with a corresponding parameter. For Windows DS-Clients, the Netserver is required. This can be started using the command STRTCPSVR SERVER(*NETSVR). For Unix DS-Clients, the FTP TCP/IP server is required. This can be started using the command STRTCPSVR SERVER(*FTP).


Confidential.
System i Server Backup Checklist

The following checklist can be used to quickly verify if an System i Server machine is properly configured for Asigra Cloud Backup Backup.
General checklist (Windows) DS-Client computer: verify iSeries Access is installed System i Server: Login as QSECOFR or a user with equivalent rights to perform the following checklists Backup user checklist Run the following command: ===> DSPUSRPRF USRPRF(USERNAME) Verify user class *SECADM Verify special authorities *SECADM *ALLOBJ *JOBCTL If you need to backup the System i Server system information, verify special authority *SAVSYS Buffer folder checklist Verify DSBUFFER is shared with read/write permissions using System i Server Operations Navigator or iSeries Navigator on the DS-Client PC Run the following command: ===> WRKLNK OBJ('/DSBUFFER') Verify at least one folder exists Libraries checklist Run the following command: ===> WRKLIB LIB(LIB*) Verify libraries LIBIN and LIBOUT exist Firewall checklist Verify ports 139, 449, 4400-4407 are open (Perform only if there is a firewall between the System i Server and the DS-Client computer.)
System i Server Disaster Recovery

The following section explains how to perform an System i Server disaster recovery given the following scenario: A backup of the System i Servers Operating System is made on tape. Your Windows DS-Client has backups of the System i Servers data and System Info. 1. Perform the following manual steps to get the System i Server running: Repair or obtain a replacement System i Server machine. Restore the LIC from your Full Tape Backup (The PTF level of the original system must be restored on the backup machine). Restore the i5/OS. 2. Configure the following networking services on the System i Server: Client Access TCP-IP The Host servers 3. Perform the configurations described in section Configuring the System i Server on page 611. When your are finished, the System i Server should be able to communicate with the DS-Client. 4. From DS-Client (DS-User > Restore Wizard), restore the System i Server System Info:

Confidential.
Restore the user profiles Restore the configuration 5. Once the System i Servers operating system and system info are restored, you may restore the user data using Asigra Cloud Backup. Once user data is restored, you must restore authority. (See Known System i Server restore issues: on page 614.)
Known System i Server backup issues:

Due to the iSeries servers own features, there are some issues to consider when performing backups: 1. Disk space: The necessary free disk space required for DS-Client to dump the files is as follows: Windows DS-Client: 2 X (largest files size X number of threads) - Linux DS-Client: largest files size X number of threads Reducing the number of threads means less disk space is required, however it will increase the time span due to more batch processing (instead of parallel processing). Time span: As a rule, file-level backups will take a lot of time because the internal operations needed to process a file are time and resource consuming. Therefore it is highly recommended to backup at library-level when there are more than 2000 objects. Library-level backups could be 70%-80% faster when compared with file-level backups. Backup as individual objects will be faster in only one situation: The library contains many objects but only a few of them ever change. The size of all changed objects will be much smaller than the library size (even though the initial backup will still be slower than a library-level backup). QUSRSYS library: To save the system directory files, you must end the QSNADS subsystem before saving the QUSRSYS library. QPFRDATA library: To save the system performance data, you must end the performance monitor before saving the QPFRDATA library. For System i V5R4, the PVTAUT parameter does not exist. If a backup set of this version has "Backup Private Authorities" checked, it will be ignored completely.
2.
3.
4.
5.
6.


Confidential.
Known System i Server restore issues:

1. User profiles: Due to the RSTUSRPRF commands own restrictions, the following situations may apply to user profiles being restored:
If a user profile exists on the system, but not on the media, the system profile remains. If a user profile exists on the media, but not on the system, a new user profile is created If the user profile exists on both the media and the system, the media user profile is restored. If the user profile exists on the media and is being restored individually, a new user profile is created without its password or group connection. If the user profile exists on both the media and the system, and is being restored individually, the media user profile is restored. However, the password and group connection on the system remains unchanged. If all user profiles are being restored, the passwords and group connections are also restored from the media. If user profiles exist on the system, there are no changes to the existing objects authorities.
To restore all user profiles with USRPRF(*ALL), all other operations on the system must be stopped. Since DS-Client cannot connect when the system is in restricted state, the DS-Client cannot restore with the *ALL option, therefore the DS-Client restores all user profiles from online individually (one by one). If you need to restore using USRPRF(*ALL) or RSTAUT, you must restore the dump file first, and then restore the user profiles manually from the SAVF that was delivered by the dump file restore process. The RSTUSRPRF(*ALL) command is normally used after the restore of the operating system, but before the user libraries are restored. The user profiles must be restored before any libraries or objects belonging to them can be restored. After the libraries and their objects are restored, the authority for the objects is restored to the user profiles using the RSTAUT command. Refer to your System i documentation for more information on restoring the system. By default, a restore of a user profile will make the following changes to the user profiles attributes: - Group Profile (GRPPRF) value is set to *NONE - Owner of new object (OWNER) value is set to *USRPRF - Group authority (GRPAUT) value is set to *NONE - Password is set to *NONE
This means the message "CPF1118: No password associated with user ABC" is generated if the user attempts to sign without initializing the password. 2. The contents of the queues are empty (e.g. there are no spool files or jobs waiting for execution). 3. IBM Supplied Libraries: As a security measure, when restoring IBM User Libraries and/or IBM System Libraries, the DS-Client only restores the dump file *SAVF. Then, the System i Operator may put the server into Restricted State and can complete the restore process using normal System i OS restore commands (via the main console). You cannot restore IBM Supplied Libraries as a whole. However, you can restore individual objects through a Restricted State restore (as described above).


Confidential.
4. While restoring *DTAQ object(s) through DS-Client into System i servers, the operator must be aware that *DTAQ objects cannot be restored over an existing one (of the same name). If this occurs, DS-Client will encounter System i error CPF3756 and possibly CPD2415 and CPF3770. In order to continue restoring the *DTAQ objects, the existing *DTAQ(s) need to be manually deleted. The alternative is to restore the data queue object(s) to another library. 5. While restoring *PVTAUT the object must have being backed up with Private Authorities. If this is not the case, DS-Client will encounter System i error CPF3780 (file for library &1 not found) and CPD37BB (Objects from save file &1 in LIBOUT not restored). CPF3780 - The data in the save file or on the tape, diskette or optical volume did not match the specified parameters. CPD37BB - You specified *YES for the private authorities (PVTAUT) parameter. Objects in save file &1 in library &2 were saved without their private authorities.
See Also
System i Server Backup on page 147


Confidential.
Backup / Restore of Virtual Machines using Windows DS-Client and VCB

Creation Date: January 04, 2008 Revision Date: January 30, 2012 Product: DS-Client (Windows)
Summary
Windows DS-Client can perform Virtual-Machine-level backup and restore of VMware servers. This only works for VMware ESX servers.
Prerequisites
DS-Client is using the VMware Consolidated Backup (VCB) to backup and restore virtual machines on VMware ESX servers with two custom-made applications (vcbBrowse.exe & VCBRun.exe). VCB can be downloaded from the VMware site. VCB needs the Microsoft .NET Framework 2.0 to be installed on the DS-Client machine. After installing VCB, create a directory on the local hard disk and copy the following files into that location: vcbBrowse.exe - This file is a program which helps you to select the virtual machines you would like to backup and will create the xml file needed by the VCBRun.exe program. VCBRun.exe - This file is an application that uses VCB to backup virtual machines. VimService.dll VimService.XmlSerializers.dll Note: These files can be found on the installation DVD or you can request them from your Service Provider.


Confidential.
Steps to backup a virtual machine

1. Run vcbBrowse.exe and connect to the VMware ESX server with Administrator credentials:
2. Select the VCB destination directory where the virtual machines files will be exported along with some parameters: Monolithic file (which is off by default). If set, the disk will be exported into a single (monolithic) file. Flat disk (which is off by default). If set, the disk is exported as a "flat" disk with no optimizations. Transport: This is the method DS-Client connects to the storage where the Virtual Machines reside. By default, the selection is Network, which covers most scenarios. (If the VMs reside on a Storage Area Network, you can select SAN, which may improve access speed.) 3. Select the virtual machines which you wish to backup. 4. Press the Generate XML button to create the xml file and specify the name of the file. The file should be created into the same directory where the vcbrun.exe program exists. 5. Create a File System backup set for the VCB destination directory using the full UNC name (not My Computer).


Confidential.
6. In the New Backup Set Wizards Set Properties Options Tab, click Pre/Post and configure the following Pre/Post commands to run:
You can specify the following parameters for vcbrun.exe: -pre: use pre processing (mount vms) -post: use post processing (unmount vms) Note: One of -pre or -post is a mandatory parameter. -xml <name>: specify the name of the xml file. Default is "vcbrun.xml" if no <name> is typed. -log: enable a log for troubleshooting (named vcblog.txt). By default it will be put in C:\WINDOWS\system32.


Confidential.
Steps to restore a virtual machine

1. To restore a virtual machine, you must first restore the backup set to an alternate location. 2. Copy the restored files and directories with WinSCP (or equivalent program) to the VMware ESX server storage. 3. Connect using a console to the VMware ESX server and run the command vcbRestore. 4. To restore the virtual machine to the original location you must specify some parameters, such as: the machine name which will perform restore, the credentials, the source directory for the restore (which is the directory where you copied the files that resulted from the DS-Client restore). The following is an example of the command to use:
vcbRestore -h localhost -u username -p password -s vcb-backup/ source_directory
Note:
Be sure the existing virtual machine is shutdown.
5. To restore to an alternate location you must edit the catalog file for every virtual machine you want to restore. More details are specified in the "Virtual Machine Backup Guide" document from the VMware site.
See Also
VMware Backup (LINUX DS-Client) on page 154 Backup / Restore of VMware (at Virtual Machine-level) on page 620


Confidential.
Backup / Restore of VMware (at Virtual Machine-level)

Creation Date: January 16, 2008 Revision Date: January 08, 2010 Product: DS-Client (Linux)
Summary
Linux DS-Client can perform Virtual-Machine-level backup and restore from VMware ESX servers. This only works for VMware ESX servers.
General Requirements
The user who performs VMware ESX server backup / restore should have knowledge about the VMware ESX server infrastructure.
DS-Client Computer Requirements

1. On the Linux DS-Client computer, modify the /etc/hosts file. Add a line containing the hostname and IP address of each VMware ESX Server you want to backup or restore. For example:
ESX5 10.10.10.105
See Also
VMware Backup (LINUX DS-Client) on page 154 Backup / Restore of Virtual Machines using Windows DS-Client and VCB on page 616 VMware Considerations on page 623


Confidential.
VMware Backup / Restore Process Description

Creation Date: November 11, 2008 Revision Date: January 08, 2010 Product: DS-Client
Summary
Asigra Cloud Backup can backup and restore VMware Servers at file-level (inside Virtual Machine itself, like a regular file server backup) or at Virtual Machine-level (as a snapshot of the Virtual Machine as it is at the time of the backup). Both backup and restore are agentless, meaning one DS-Client installation can perform the tasks, as long as it can access the target backup item(s).
File-level backup
Backup of Virtual Machines at file-level is done by DS-Clients using 3rd party APIs by accessing the Virtual Machines file system using a valid IP address / computer name and valid network access credentials with sufficient permissions to perform the backup. Using this type of backup, DS-Client does not distinguish the machine as being a Virtual Machine or a physical machine.
Virtual Machine-level backup

Backup of Virtual Machines at Virtual Machine-level is done by DS-Clients using the following methods:.
ESX Server Version v.3.5 / v.3.5i DS-Client Operating System Linux Windows Method HTTPS and VMware APIs VCB and Pre/Post scripts
Backup Process Description

List the folders and the Virtual Machines Perform snapshot for selected Virtual Machines Backup files for selected Virtual Machines Delete backup snapshots for the selected Virtual Machines
Restore Process Description

Check if Virtual Machine with the same name exists. If yes, overwrite the configuration information for the existing machine. Check if destination folder exists: if yes, generate a new folder and path for the Virtual Machine. Restore all backed up files Register the Virtual Machine and revert to the backup snapshot Delete backup snapshot


Confidential.
See Also
VMware Backup (LINUX DS-Client) on page 154 Backup / Restore of Virtual Machines using Windows DS-Client and VCB on page 616 VMware Considerations on page 623


Confidential.
VMware Considerations
Creation Date: March 27, 2008 Revision Date: November 14, 2008 Product: DS-Client (Linux)
Summary
This article describes various VMware backup and restore considerations. It should be read before performing backups of VMware servers. Alternate Location Restore on page 623 Backup of Virtual Machines uses snapshots on page 623 Virtual Machines with the same name on page 624 Backup of Virtual Machines running on VMware Clusters on page 624
Alternate Location Restore

The paths that are shown in the DS-User for virtual machines are the same as the ones available in the Virtual Infrastructure Client. When performing restores, the paths must match the legal path for a virtual machine to be created in the Virtual infrastructure Client. This means the path is always of the form:
<data-center-name>\<vm>\<path-to-vm>
To summarize: When connecting to ESX through the Virtual Center, the alternate restore path must be:
data center\vm\folder-name
When connecting directly to the ESX Host, the alternate location restore path must be:
datacenter\vm\vm-name
Trying to restore into a path that is not valid will result in SOAP errors during the restore. When restoring to alternate locations, always make sure that the path in the "Truncate" area is a valid path for Virtual Machines. In addition, you should not change the Virtual Machine name when performing alternate restores. Attempting to change the name will restore all the files to the VMware server, however the registration of the virtual machine will fail (see Virtual Machines with the same name on page 624).
Backup of Virtual Machines uses snapshots

Backup of VMware uses snapshots in order to unlock locked disks for backup. As a result, any disks that cannot be unlocked by a snapshot (e.g. independent disks or raw disks) cannot be backed up while the virtual machine is running. Backup and restore of Virtual Machines that are using independent or raw disks is not supported.


Confidential.
Virtual Machines with the same name

Restoring two Virtual Machines on the same server with the same name, does not work. When restoring a Virtual Machine, the VM name is contained in the backup set files for that VM. As such, when performing restores, the DS-Client will use the backed up virtual machine name to find configuration settings and perform virtual machine registrations. Do not try to change the virtual machine names when performing alternate location restores. Any such name changes will not take effect and may cause the restore to fail. What you can do is change the folder to which a virtual machine will be restored.
Backup of Virtual Machines running on VMware Clusters

There are two (2) types of VMware clusters: VMware HA (High Availability), and VMware DRS (Distributed Resource Scheduler). The DRS feature improves resource allocation across all VMware hosts, however it can automatically migrate Virtual Machines between hosts. Backup of a VM during those migrations will fail with libcurl errors.
See Also
VMware Backup (LINUX DS-Client) on page 154 Backup / Restore of Virtual Machines using Windows DS-Client and VCB on page 616


Confidential.
Backup / Restore of XenServer (at Virtual Machinelevel)

Creation Date: January 18, 2008 Revision Date: December 12, 2011 Product: DS-Client (Linux)
Summary
Linux DS-Client can perform Virtual-Machine-level backup and restore from XenServers.
Backup
The following backup issues must be considered: Linux DS-Client supports backup of: shut down Virtual Machines (XenServer 5.0 and up) running Virtual Machines (for XenServer 5.5 and up if using the snapshot feature) snapshots
- Custom Templates Linux DS-Client does not support backup of: Default XenServer Templates - XenServer's "Domain 0" Note: Custom Templates and snapshots on the XenServer are directly backed up. Even if the "Use Snapshots" option is selected, the DS-Client does not attempt to create snapshots of these backup items. The backup wizard can only list Virtual Machines / Custom Templates with unique names. If you have Virtual Machines or Custom Templates with the same name, you must use XenCenter to make all names unique, before a XenServer backup can be performed. Templates are actual Virtual Machines that are pre-configured on the XenServer to allow users to quickly create new Virtual Machines. Default XenServer Templates are supplied with the XenServer. Custom Templates are created by XenServer users.
Note:


Confidential.
Restore
The following restore issues must be considered: Virtual Machines cannot be overwritten during a restore; a new Virtual Machine with the same name will be created Duplicate Virtual Machines can be destroyed through the XenCenter application or through the command-line interface. A Virtual Machine will be created if restoring from a generation of a Virtual Machine that was backed up without the Use Snapshot option. A Custom Template will be created if restoring: from a generation of a Virtual Machine that was backed up with the Use Snapshot option, or a Custom Template, or a snapshot.
See Also
XenServer Backup (LINUX DS-Client) on page 156


Confidential.
Backup / Restore of MS SharePoint 2007 Servers (DSRecovery Tools)

Creation Date: January 18, 2008 Revision Date: September 12, 2012 Product: DS-Client (Windows) with DS-MLR Service (DS-Recovery Tools)
Summary
This article describes the Microsoft SharePoint 2007 items that can be backed up and restored. It also describes how to configure a DS-Recovery Tools installation to log events for a backup activity. SharePoint 2007 Server Support Matrix on page 628 Logging DS-Recovery Tools for SharePoint activities (troubleshooting) on page 630


Confidential.
SharePoint 2007 Server Support Matrix

SharePoint Item
Libraries Document Library Form Library Wiki Page Library Picture Library Data Connection Library Translation Management Library Report Library Slide Library Communications Announcements Contacts Discussion Board Tracking Links Calendar Tasks Project Tasks Issue Tracking Survey Custom Lists Custom List Custom List in Datasheet View Languages and Translators KPI List Import Spreadsheet Web Pages Basic Page Web Part Page Sites and Workspaces Publishing Page Users and Permissions People and groups Site collection administrators Advanced permissions Email and Workflow Incoming email setting Email message and attachment Workflow Active Support Active Support Not Supported Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Windows DS-Client
SharePoint Template
Collaboration Team Site Blank Site Document Workspace Wiki Site Blog Meetings Basic Meeting Workspace Blank Meeting Workspace
Windows DS-Client
Active Support Active Support Active Support Active Support Active Support Active Support Active Support


Confidential.

Decision Meeting Workspace Social Meeting Workspace Multipage Meeting Workspace Enterprise Document Center Records Center Personalization Site Site Directory Report Center Search Center with Tabs Search Center Publishing Publishing Site Publishing Site with Workflow News Site Active Support Not Supported Active Support Active Support Active Support Not Supported Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Site Admin Templates

Board of Directors Business Performance Reporting Case Management for Government Agencies Classroom Management Clinical Trial Initiation and Management Competitive Analysis Site Discussion Database Disputed Invoice Management Employee Activities Site Employee Self-Service Benefits Employee Training Scheduling and Materials Equity Research Integrated Marketing Campaign Tracking Manufacturing Process Management New Store Opening Product and Marketing Requirements Planning Request for Proposal Sports League Team Work Site Timecard Management
Windows DS-Client
Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Server Admin Templates

Absence Request and Vacation Schedule Management Budgeting and Tracking Multiple Projects Bug Database Call Center Change Request Management Compliance Process Support Site Contacts Management Document Library and Review Event Planning Expense Reimbursement and Approval Help Desk Inventory Tracking IT Team Workspace
Windows DS-Client
Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support Active Support


Confidential.

Job Requisition and Interview Management Knowledge Base Lending Library Physical Asset Tracking and Management Project Tracking Workspace Room and Equipment Reservations Sales Lead Pipeline Active Support Active Support Active Support Active Support Active Support Active Support Active Support
Matrix Legend:
Active Support: DS-Client supports backup / restore of this SharePoint item. Not Supported: DS-Client does not support backup / restore of this item.
Logging DS-Recovery Tools for SharePoint activities (troubleshooting)

There are two configuration files in the DS-Recovery Tools installation directory: dsrcvtools.cfg - the main configuration file, containing the path to the log configuration file and sharepoint.dll logconf.cfg - the configuration for logging. By default, debug logging is disabled. There are some examples inside the file logconf.cfg. Sample dsrcvtools.cfg file:
DS-Recovery Tools Ports BackupLibs share_point : 4408 Log Configuration: C:\Program Files\CloudBackup\DS-Recovery Tools\logconf.cfg : share_point : C:\Program Files\CloudBackup\DS-Recovery Tools\SharePoint.dll
Sample logconf.cfg file:

"C:\Program Files\CloudBackup\DS-Recovery Tools\evlog.txt" { filter { severity = debug; } }
Note:
This sample logconf.cfg will dump all the debug information from the DS-Recovery Tools service to the evlog.txt file.
If you configure the DS-Recovery Tools service to dump a debug log, this will create a very large text file. Note there will be a significant performance impact if you do this. This feature is available for troubleshooting purposes in order to assist your Service Providers Technical Support Team.
See Also
MS SharePoint Server (DS-Recovery Tools) on page 153


Confidential.
Backup / Restore of Lotus Domino Server Databases

Summary
This article covers various backup/restore issues for the Lotus Domino Server backup sets. DS-Client Requirements The following requirements must be met in order to perform online backup / restore of a Lotus Domino Server Database. 1. Lotus Notes (client) must be installed on the DS-Client computer. It must be configured with Connect to Domino Server with Administrator privileges. This allows DS-Client to backup all the mailboxes from the Lotus Domino Server. 2. For each Lotus Domino Server Database you want to backup, you will need the following files:
A text file containing settings for the separate, corresponding user.id file. This file can be found in the Lotus Notes (client) installation location on the DS-Client computer. You must make sure this files KeyFileName parameter references the exact current location of the corresponding user.id file (as seen from the DSClient computer). This file is required for the Database Credentials when creating a Lotus Domino Server backup set. A binary file from the Lotus Domino Administrator (generated from the Lotus Domino Administrator machine). This user.id file must belong to a Lotus Domino Administrator or user with Administrators rights.
notes.ini
user.id
Restore
Restore to Alternate Location is not supported for Lotus Domino Server Database backup sets.


Confidential.
Restoring Lotus Domino Server Database in a Clustered Environment

In order to restore clustered Lotus Domino Server Databases, the following steps are required: 1. You must have a backup of all the database(s) of the Lotus Domino Server that are in the clustered environment. 2. Restore each database to its original location. When doing the restore, you must manually shutdown all other servers (in the cluster), except for the target server. In the Restore Wizards Select Restore Options screen, you must select the Keep Replica ID' option. 3. Continue with step 2 for all the databases in the cluster. 4. After all the databases have been restored, restart all servers in the cluster (one at a time). 5. Take note of the following information: If old data was restored, then all the newer data which was created after that backup will be lost. If you only restore data to one server (in the cluster), after restarting that server, the replica will apply all new changes (those which happened after the backup time, on the restored server). For example: User Mike's draft E-Mail with subject "Happy new year" was backed up. After backup, he deleted this E-Mail. Then after restore, this E-Mail does not appear in Mike's draft folder. Since replication of the databases dbdirman.nsf, dpicfg.nsf and webadmin.nsf is not allowed, the replica ID of these three databases will change after any restore.
See Also
Lotus Domino Server Database Backup (Windows DS-Client) on page 158 Restore Lotus Domino Server Database Backups on page 249


Confidential.
Backup / Restore of Sybase (Database-Level)

Creation Date: September 17, 2009 Revision Date: September 17, 2009 Product: DS-Client (Linux)
Summary
This article covers various backup/restore issues for the Sybase backup sets.
Restore
You can restore any backed up Sybase database into any existing Sybase database. This will overwrite all data in the existing database.
Database size issues: When you create a new database specifically for restore purposes, you must allocate at least as much space as was allocated in the original (source) database. Database loading issues: You cannot load a dump that was made on a different platform or with a different version of Sybase server. If the database you are loading includes tables that contain the Primary Keys for tables in other databases, you must load the dump into a database with the same name as the source database. It is recommended that for the duration of the database load, you put the database into single_user mode to prevent other users from making changes to the database.
See Also
Sybase Database Backup (LINUX DS-Client) on page 159 Restore Sybase Database Backups on page 250


Confidential.
Backup / Restore of Oracle-SBT

Creation Date: March 02, 2010 Revision Date: March 02, 2010 Product: DS-Client (Linux)
Summary
This article covers various backup/restore issues for the Oracle-SBT backup sets. SBT refers to the Oracle System Backup to Tape functionality. The Oracle-SBT backup set is a special configuration of DS-Client that allows a native Oracle-SBT process to be re-directed through DSClient to DS-System (instead of to tape). The main advantage of this backup set type is to combine the native backup process speed (Oracle RMAN) with the DS-Clients incremental forever technology. IMPORTANT: This backup set type requires manual command input from the Oracle Server itself. All backup and restore commands must be initiated from the Oracle Server side (either through RMAN command-line or through Oracle Enterprise Manager. Only Oracle Database Administrators should attempt to use this backup set type. Additional documentation is available from the DS-Client installation DVD in the folder:
\Tools\Oracle_SBT_Library
Troubleshooting
Error The following error message may appear in the DS-Client Event Log when you restore from an Oracle-SBT backup set:
SBT restore cancelled: Remote side stopped the restore of this file before all data was transmitted.
Reason This error is normal, the RMAN restore successfully completed and the restored file is good. This error may happen when you perform a tablespace restore. Because the restore is performed by RMAN, RMAN will read the backed up backupset and determine which tablespace needs to be restored. If the backupset contains the same named tablespace, you will not see this error. If the backupset contains any different tablespaces, you will see this error (i.e. if you are performing a selective restore of less than all the tablespaces in the backupset). Example: You restore a tablespace from a whole database backupset, RMAN will read the backupset and restore only the tablespace you need. After the tablespace is restored, the SBT channel is released and RMAN stops. However, DS-Client still expects RMAN to continue sending the whole database in the backupset. This causes the above error in the DS-Client Event Log.
See Also
Oracle-SBT Backup (LINUX DS-Client) on page 164


Confidential.
Backup / Restore of VMware VADP backup sets

Creation Date: April 26, 2010 Revision Date: October 10, 2012 Product: DS-Client (Linux)
Summary
This article covers various backup and restore issues for the VMware VADP backup sets. DS-Client Requirements for VMware VADP backup / restore on page 635 Backup Limitations on page 635 Backup of VMware VADP backup sets using CBT (Changed Block Tracking) on page 635 Backup / Restore of VM in a cluster on page 636 Backup of Fault Tolerant Virtual Machines on page 636 Restore to Alternate Location (different VMware DataCenter connected to different vCenter server) on page 636 Best practice: Conflicting activities on Virtual Machines on page 636 TROUBLESHOOTING: Backup of a migrated VM using the CBT feature gets file fault error on page 637
DS-Client Requirements for VMware VADP backup / restore

When an ESX host is added with its DNS name to the vCenter server, the DS-Client machine must be able to do name resolution for that ESX host, in order to backup / restore the virtual machines.
Backup Limitations
You cannot backup virtual machines that have Fault Tolerance turned on. See Backup of Fault Tolerant Virtual Machines on page 636. You cannot backup Virtual Machines with physical or virtual Raw Disk Mapping (RDM) devices.
Backup of VMware VADP backup sets using CBT (Changed Block Tracking)
DS-Client can use CBT (Changed Block Tracking) for VMware VADP backup sets. If enabled, DSClient attempts to reconfigure the Virtual Machine to allow tracking of the blocks of data that have changed. This option can improve the speed of incremental backup activities, but may also slow down the VM since it consumes additional resources. When CBT is enabled, the first backup activity will scan the Virtual Machine. For thick disks, the scan will be of the entire VMs disks. For thin disks, the scan will only cover the space occupied by the disks. Subsequent backup activities will track the changes for the VM files and will only retrieve the blocks of data that have changes. These blocks will be processed for master/delta generations and sent and saved to DS-System and/or Local Storage. If CBT fails to be enabled (even if configured for use in the backup set), DS-Client will continue its incremental backup activities by reading the entire data of the VM disks, processing the data for master/delta generations and sending the backup data to DS-System. Note: As of the Revision Date of this article, the DS-Client cannot perform CBT if the backup set is configured with the Use Buffer option. By default, the New Backup Set Wizard selects the CBT option and disables the Use Buffer option.


Confidential.
Backup / Restore of VM in a cluster

Backup of Virtual Machines on clustered hosts (VMware cluster) should be done through the VMware vCenter. Make sure to input the IP Address of the vCenter when creating the backup set. Then you can browse and select the specific VM cluster to backup. If you backup an individual VM in a VMware cluster by specifying the host IP address when creating the backup set, subsequent backups may fail, depending on the configuration of the cluster. Normally, a VMware DRS (Distributed Resource Scheduler) clusters automation level is configured to be Fully automated for High Availability. This means the individual Virtual Machines that make up the cluster will be dynamically assigned to the best suited host at startup. This means the VM might be automatically moved to another host when the VMware cluster (or VM) is restarted. Since you can backup individual VMs in a VMware cluster (by specifying the host IP address when creating the backup set), if the VM moves to another host, it will not be found by the backup set and you will get errors. However, if the VM is selected through the vCenter, the location of the VM is always known (even if it moves to another host). If you must backup a specific VM in a VMware cluster (using a dedicated backup set to a specific host machines IP address), you must configure the cluster to not move that VM to different hosts. In the Virtual Center, edit the VMware DRS cluster settings: Enable individual virtual machine automation levels. For the specific VM you want to backup, you must change its Automation Level setting to Disabled. This will prevent the vCenter Server from migrating the virtual machine. Note: It is much simpler to create the backup set by specifying the vCenter Servers IP address as the source in the New Backup Set Wizard. This allows you to browse and select the specific virtual machine from the cluster and you will not need to change the automation settings for the cluster.
Backup of Fault Tolerant Virtual Machines

Linux DS-Client cannot backup virtual machines which have fault tolerance (FT) enabled since it depends on making a snapshot of the virtual machine to back it up and VMware does not support snapshot creation on FT virtual machines. VMware has documented the full procedure for backup / restore of FT virtual machines using templates in their knowledge base article # 1016619.
Restore to Alternate Location (different VMware DataCenter connected to different vCenter server)
DS-Client must have network access to the vCenter and all involved ESX host(s).
Best practice: Conflicting activities on Virtual Machines

Running conflicting activities on the same Virtual Machine should be avoided. Running multiple Clone with Local DS-VDR activities on the same Virtual Machine from the same or different Local DS-VDR Tools should be avoided. When running conflicting activities, files may be left in the ESX server which are not registered and not used and they can occupy large amounts of space.


Confidential.
TROUBLESHOOTING: Backup of a migrated VM using the CBT feature gets file fault error
Error A known issue for VMware VADP backup sets using the CBT feature occurs in a very specific scenario where an incorrectly configured VM is backed up. The following steps describe the situation when this error occurs: Migrate a VM using vCenter. Backup the migrated VM with a VMware VADP backup set using the CBT feature. When you backup, the following error appears:
"Error opening file disk2000.vmdk for reading QueryChangedDiskAreas: SOAP 1.1 fault: "":ServerFaultCode [no subcode] "Error caused by file /vmfs/ volumes/4ac65eb0-8b20da10-c550-0030483062fe/rhel61thin-test/rhel61thintest.vmdk" Detail: <FileFaultFault xmlns="urn:vim25" xsi:type="FileFault"><file>/vmfs/volumes/4ac65eb0-8b20da10-c5500030483062fe/rhel61thin-test/rhel61thin-test.vmdk</file></FileFaultFault> (rhel61thin-test) (VMware VADP\10.20.30.111\\DataCenter\Test\rhel61thintest\disk2000.vmdk)."
Reason This is because after migration, even though the VM has a property setting of CTKenabled=true, it has not been properly reconfigured by the vCenter. If this error occurs, it means the VM has a configuration problem and probably should not be used. If this error occurs you must fix the VM with the fix described below. Fix (after the file fault error is encountered) One possible fix is to make a modification that triggers vCenter to run a re-configuration cycle on the VM. This can be done by performing the following steps: 1. Power off the target VM. 2. Using vCenter, select the VM and choose Edit Settings. The Virtual Machine Properties screen appears. 3. Select the Virtual Disk. On the right side of the Virtual Disk Configuration panel, there is a Mode section with an Independent check box. Select the Independent checkbox and click OK. 4. Select the VM again and choose Edit Settings. The Virtual Machine Properties screen appears. In the Mode section, uncheck the Independent checkbox and click OK. 5. The vCenter should perform a re-configuration of this VM (this may take a few minutes). Once re-configuration is finished, power on the VM. You should now be able to backup the VM with the Use CBT feature. Suggested Best Practice (to prevent the file fault error) Whenever you migrate a VM using vCenter, always perform the steps in the Fix (above) that will trigger vCenter to run a re-configuration cycle on the VM.
See Also
VMware VADP Backup (LINUX DS-Client) on page 166


Confidential.
Backup / Restore of Microsoft SQL Server (VSS-aware backup sets)

Summary
This article covers various backup / restore issues for Microsoft SQL Server backups (using the VSS-aware backup set type). MASTER database does not support Differential backup (VSS-aware sets) on page 638 Database Backup Policy (VSS-aware sets) on page 638 Data integration issues on page 639 Alternate Restore Location Issues for Pure Files on page 639
MASTER database does not support Differential backup (VSS-aware sets)

VSS-aware backup sets only support backup of the master database from any Microsoft SQL Server instance with the Full Database backup policy. If you add the master database to a VSS-aware backup set with the Full+Differential policy selected, the backup will fail on every differential backup attempt.
Database Backup Policy (VSS-aware sets)

Database backup policy options can help reduce the backup time for very large databases (where the dump takes up significant time). You can configure the backup set to perform differential database backups. Differential backups contain all the changes to the database since the last full dump.
[Default] This is the default behavior for all MS SQL Server backups. Each backup of the SQL Server performs a full dump (VSS Snapshot) of each database. Performs a full dump (VSS Snapshot) of the database on first backup, followed by differential backups until another full backup is needed (*).
Full dump: Always Full dump: Plus Differential
(*) A full dump is needed (other than first time) when: a database has been backed up by another backup set (or manually from the SQL tools); a database has been restored (either from another database or an earlier generation); the database properties have been modified (recovery model switched to simple); a set number of consecutive differential backups have been performed, unless over-ruled with the Do not start full dump option. This uses the same number set in the DS-Client Advanced Configurations MasterGenerations parameter (note: this parameter is also used for another purpose).
Note:
The DS-Client can only take advantage of the differential backup policy if the backup set (of the SQL database) is the only process that backs up that target. If another backup set is used to backup the database (or the internal SQL commands are used to perform manual backups / dumps), then the backup policy requires the next backup to be a full dump.


Confidential.
Database Backup Policy Full Backup Schedule Over-ride Rules: These rules are optional. They allow greater control over when a Full Backup can occur (e.g. not during business hours). Warning: Full dumps can be delayed, but a full database dump needs to be performed at some regular frequency to protect the integrity of the database backup. By default, DS-Client allows a full backup to be skipped a maximum of 120 consecutive times. This number is configurable in the DS-Client Advanced Configuration options MaxNonFullDumps parameter (see: DSClient Advanced Configurations on page 458). For more information about Database Backup Policy options, see Advantages and Disadvantages of different DB backup policies on page 563 in the Knowledge Base article Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560.
Data integration issues

Each SQL database is presented as a component by the SQL VSS Writer. In the VSS-based SQL restore, a component must be restored with all its contents (the file snapshot) based on the rules specified in its Metadata. These issues are similar to those in VSS-aware backups of Hyper-V. See Data integration issues on page 647 in the Knowledge Base article Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644.
Alternate Restore Location Issues for Pure Files

VSS-aware backups have the ability to restore the pure files from a backup. These files may be usable by the corresponding Microsoft management tools. To restore MS SQL Server databases in alternate location, you must first restore the database files as pure files using the Restore Wizard: 1. Select the VSS-aware backup set and start the restore wizard. Press the File Restore button. 2. The Database Tree changes to display the individual file components (not the database instances). 3. Browse and select the directories and files to restore. You will normally require the *.ldf and *.mdf files to restore an MS SQL Server from pure files. 4. Click Next. Select the restore location and finish the restore. After the pure files have been restored, you can use Microsoft SQL Management Studio to attach the databases to the destination MS SQL Server instance. Consult the Microsoft documentation for further instructions.
See Also
VSS-aware backup sets on page 161


Confidential.
Backup / Restore of Microsoft Exchange Server (VSSaware backup sets)

Summary
This article covers various backup / restore issues for Microsoft Exchange Server backups (using the VSS-aware backup set type). Database Backup Policy (VSS-aware sets) on page 640 Data integration issues on page 641 Truncate Transaction Log behavior with VSS-aware backup sets on page 641 Restore Issues on page 642 Exchange 2007 VSS backup set: File Restore to Recovery Storage Group (RSG) on page 642 Exchange 2010 VSS backup set: File Restore to Recovery Database (RDB) on page 642
Database Backup Policy (VSS-aware sets)

Database backup policy options can help reduce the backup time for very large databases (where the dump takes up significant time). You can configure the backup set to perform differential database backups. Differential backups contain all the changes to the database since the last full dump.
[Default] This is the default behavior for all MS Exchange Server backups. Each backup of the Exchange Server performs a full dump (VSS Snapshot) of each database. Performs a full dump (VSS Snapshot) of the database on first backup, followed by differential backups until another full backup is needed (*). Performs a full dump of the database on first backup, followed by incremental backups until another full dump is needed (*).
Full dump: Always Full dump: Plus Differential Full dump: Plus Incremental
(*) A full dump is needed (other than first time) when: a database has been backed up by another backup set (or manually from the Exchange tools); a database has been restored (either from another database or an earlier generation); the database properties have been modified (recovery model switched to simple); a set number of consecutive differential backups have been performed, unless over-ruled with the Do not start full dump option. This uses the same number set in the DS-Client Advanced Configurations MasterGenerations parameter (note: this parameter is also used for another purpose).
Note:
The DS-Client can only take advantage of the differential backup policy if the backup set (of the Exchange database) is the only process that backs up that target. If another backup set is used to backup the database (or the internal Exchange commands are used to perform manual backups / dumps), then the backup policy requires the next backup to be a full dump.
Confidential.

Database Backup Policy Full Backup Schedule Over-ride Rules: These rules are optional. They allow greater control over when a Full Backup can occur (e.g. not during business hours). Warning: Full dumps can be delayed, but a full database dump needs to be performed at some regular frequency to protect the integrity of the database backup. By default, DS-Client allows a full backup to be skipped a maximum of 120 consecutive times. This number is configurable in the DS-Client Advanced Configuration options MaxNonFullDumps parameter (see: DSClient Advanced Configurations on page 458). For more information about Database Backup Policy options, see Advantages and Disadvantages of different DB backup policies on page 563 in the Knowledge Base article Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560.

Each Exchange database is presented as a component by the Exchange VSS Writer. In the VSSbased Exchange restore, a component must be restored with all its contents (the file snapshot) based on the rules specified in its Metadata. These issues are similar to those in VSS-aware backups of Hyper-V. See Data integration issues on page 647 in the Knowledge Base article Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644.
Truncate Transaction Log behavior with VSS-aware backup sets

DS-User does not offer the Truncate Transaction Log option when creating or editing a VSSaware Microsoft Exchange backup set (Set Properties - Items tab). This is because when performing VSS backups of MS Exchange Servers, the truncation of transaction log files is controlled by Microsoft components. The truncation will be triggered based on the type of backup chosen: In non-DAG configurations, the Store Writer will truncate the transaction log files at the completion of successful Full or Incremental backups. In DAG replicated configurations, log truncation will be delayed by the Replication service until all necessary log files are replayed into all other copies. The Replication service will delete the backed up log files both from the active and the copy log file paths after it verifies that the to-be-deleted log files have successfully been applied to the copy database and both active database and the database copies checkpoint has passed the log files to be deleted. For more information, consult the Microsoft Developer Network article "Exchange VSS Writers for Exchange Server 2010".


Confidential.
Restore Issues
The DS-Client can only restore an MS Exchange Mailbox Database if the destination database for the restore is in mounted state. DS-Client performs the following steps during a restore of a VSS-aware Microsoft Exchange Server: 1. Check if the destination DB for restore is in mounted state. 2. Retrieve information from the mounted DB, including physical path and DB GUID. 3. Dismounts the database. 4. If restoring to the original location: Replace the DB files in the physical location. If restoring to an alternate location: Restore logs to a "restoredlogs" folder, then restore the Exchange DB files to the physical location. VSS Writers will apply the logs from the restoredlogs folder and then the directory will be removed. 5. Mount the MS Exchange Database.
Exchange 2007 VSS backup set: File Restore to Recovery Storage Group (RSG)
A direct VSS restore to an Exchange 2007 RSG is not supported. However, you can use the File Restore method to restore the backup files, then manually load those files to the RSG. 1. You must restore the Exchange files before creating the RSG. DS-User > Restore Now: In the Restore Wizard click the File Restore button. For each database you want to restore, select the entire backup folder (including all log files). Restore to the original or alternate location, as required. 2. When you create the RSG, specify the location where you have restored the database and log files. 3. Before mounting the database, run the eseutil in the database directory, which will reset the database to a clean shutdown state. For example:
eseutil /r e00 /i /d
4. Now you can mount the database in your RSG.
Exchange 2010 VSS backup set: File Restore to Recovery Database (RDB)
A direct VSS restore to an Exchange 2010 RDB is not supported. However, you can use the File Restore method to restore the backup files, then manually load those files to the RDB. 1. You must restore the Exchange files before creating the RDB. DS-User > Restore Now: In the Restore Wizard click the File Restore button. For each database you want to restore, select the entire backup folder (including all log files). Restore to the original or alternate location, as required. 2. When you create the RDB, specify the restored database name. 3. Before mounting the database, run the eseutil in the database directory, which will reset the database to a clean shutdown state. For example:
eseutil /r e00 /i /d
4. Now you can mount your RDB. Note: Only one RDB can be mounted at a time. If you try to mount more than one, you will get an error.


Confidential.
See Also


Confidential.
Backup / Restore of Hyper-V (VSS-aware backup sets)

Creation Date: March 25, 2010 Revision Date: November 17, 2011 Product: DS-Client (Windows)
Summary
This article covers various backup / restore issues for Microsoft Hyper-V backups (using the VSSaware backup set type). The DS-Client software allows you to perform on-line backups of Hyper-V Virtual Machines (VM). The DS-Client supports backup and restore of the following virtualized environments: Microsoft Hyper-V Server 2008 R2 Windows Server 2008 R2 with Hyper-V role. This article contains information in the following sections: Features Supported on page 644 Requirements for backup / restore support of Hyper-V VMs on page 644 Backup Policy on page 645 Restore policy on page 646 Data integration issues on page 647 Cluster Hyper-V backup requirements on page 648 Hyper-V Cluster issues on page 648
Features Supported
Features VSS-aware backup set (using Microsoft VSS writers) Microsoft Windows Server 2008 R2 with Hyper-V role + Operating System + + + + + + +
Online backup (of Hyper-V Server and at individual virtual + machine level) Hyper-V Server browsing Alternate Server restore (VSS Restore) Alternate Individual VM restore (VSS Restore) Alternate restore as pure files (File System restore) Visualize VSS Component details at virtual machine level during restore (VSS Component) + + + + +
Requirements for backup / restore support of Hyper-V VMs

In order to use Microsoft Hyper-V VSS Writer to perform backup / restore, the Hyper-V Virtual Machine Management service must be running on the target server. Each target virtual machine must have Integration Services installed, in order to be backed up using Microsoft VSS Writers (volume snapshot).


Confidential.
Backup Policy
The Asigra Cloud Backup solution is based on Microsoft Hyper-V VSS Writer for both backup and restore. The backup unit is the Hyper-V VM (not individual files within the VM). A Hyper-V VM is a group of files governed with strong data integration. The backup mechanism is called the "Saved State" method, where the VM is put into a saved state during the snapshot process. Snapshots are taken of the appropriate volumes, and the VM is returned to the previous state after the snapshot process is done. The GUID of Hyper-V VM is the identifier for the Hyper-V VM. This means, the GUID of Hyper-V VM is considered as the file name of the VM. The name of the VM may be saved as a description of the VM (note that the VM name may not be unique for all VMs in a Host). Hyper-V WMI APIs are used to search for the VMs in a host server. This is needed when creating a Hyper-V backup set, allowing users to browse for VMs to back up. Users can also select all VMs to be backed up. VSS provides a consistent interface that allows online backup of a Microsoft Hyper-V VM. VSS-related metadata is saved with the backup data to provide the rules for data integration in each backed up component (VM). Master / Delta and library files are supported for this type of backup set.


Confidential.
Restore policy
For Restore, two models are supported by the Asigra Cloud Backup application: VM-level restore Restore as files VM-level restore VM-level restore uses the Hyper-V VSS Writer to restore the whole VM and maintain data integration. For VM-level restore, the restore unit is a VM. All files (a snapshot at a particular moment) involved in the VM are provided based on the saved Metadata. Exactly one generation (or session) can be selected for restore. Restore as files Restore as files does not guarantee data integration. This method restores the selected individual files the same way as for a File System backup set. End-users (customers) are responsible for the result of the restore. This option is suitable for scenarios where VM-level restore is not possible (e.g. alternate restore, if some files are corrupted so that VM-level restore is not possible, etc.) or not necessary (usually for advanced users that understand Hyper-V very well and can manually manage the restored files, or the files are restored for other purposes than as part of a VM). Before performing an alternate restore, make sure that on the target machine there is no virtual machine with the same GUID (see Backup Policy above). If this is the case, the existing VM will be overwritten. For alternate restores, if you would like to change the path for the VM files you must use the "Restore Option File" option and specify the vssrestore.xml file. You can rename the .xml file as you wish ("vssrestore" is a generic name). The .xml file should be created under the DS-Client installation path. Sample .xml file:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE vss-restore SYSTEM "asigra_vss.dtd"> <vss-restore version="1.0"> <component logical-path="" component-name="D558DE24-956E-4E398C639F969FAB8097.VM (VmEx4)"> <file-restore-option original="d:\VMS\" target="d:\VMS_RESTORE\"/> </component> </vss-restore>


Confidential.

Each VM is presented as a component by the Hyper-V VSS Writer. In the VSS-based VM restore, a component must be restored with all its contents (the file snapshot) based on the rules specified in its Metadata. Components Each VM is presented as a component by the Hyper-V VSS Writer. In the VSS-based VM restore, a component must be restored based on the Backup Components Document and Writer Metadata Documents. The component data integration metadata file includes an entry for each individual file belonging to this component and the component itself. The entry may contain the following information: File ID Generation ID Backup Time Full Path (directory and file name)
DS-Client and DS-System use the combination of File ID / Generation ID to identify the backed up component generation. BLM uses the full path and backup time to identify the backed up component generation. A component (VM) is represented by the component data integration metadata. Retention, delete, BLM request and Disc/Tape request work at the component-level. Validation works at the level of the individual backed up files.
Component Restore Restore works both at the component-level (VM) and individual file level. This is selectable from the DS-User GUI. A component generation is considered complete if all its referenced contents exist. Otherwise it is considered an incomplete component by the DS-Client. A file that is not referenced by a complete component generation is called an unreferenced file. Incomplete Components Incomplete component generations are allowed in order to permit individual file restore from incomplete components. Files that are backed up in an incomplete component generation could be referenced by later generations of the same component (thereby avoiding rebackup of the unchanged file again). In the DS-Clients Retention Rules, options are provided to Delete incomplete components and Delete unreferenced files. Incomplete component generations are not visible in the restore tree for VMlevel restore. The component data integration metadata are backed up as separate files with the Hyper-V backup, and will be backed up the same way as data file (except that it is not encrypted). This is because the metadata will be parsed by DS-System / BLM / etc., without knowing the encryption keys.


Confidential.
DS-Client will save the component data integration metadata in its database. Metadata is required by activities like restore / delete / retention, etc. Synchronization is responsible for synchronizing them with the corresponding on-line file. BLM and components When a component generation is moved to BLM, all its referenced files (if any exist) must be copied to BLM. When generating a BLM restorable image, if a component generation is included, that images must also include all its referenced files.
Cluster Hyper-V backup requirements

Backup of Hyper-V in a clustered configuration is supported through the VSS-aware backup set type. The following requirements must be met to backup a Hyper-V Cluster: Add the IP address and computer name for all the nodes in the Hyper-V cluster to the DS-Client computer's "Hosts" file, which is usually found in:
C:\WINDOWS\system32\drivers\etc\Hosts
Create a VSS-aware backup set and select Microsoft Cluster Hyper-V. Specify the computer using the IP address of the cluster virtual node. (This is configured on the Hyper-V cluster itself.) If you can connect successfully to the specified computer, you will see an additional folder level named <HAVMs>. This contains the Clusters highly available Virtual Machines that can be selected for backup. All other steps are the same as for standalone Hyper-V backup sets.
Hyper-V Cluster issues

When restoring virtual machines, you must make sure that the same virtual machine (based on GUID) does not exist on any other node that is part of the same Hyper-V cluster (e.g. due to migration, failover, renaming, etc.).
See Also


Confidential.
Backup / Restore of Microsoft SharePoint 2007 (VSSaware backup sets)

Creation Date: May 19, 2010 Revision Date: January 27, 2012 Product: DS-Client (Windows)
Summary
This article covers various backup / restore issues for Microsoft SharePoint 2007 backups (using the VSS-aware backup set type). The DS-Client supports backup and restore of the following products: Windows SharePoint Services 3.0 SP2 (Standalone or Farm structure) Microsoft Office SharePoint Server 2007 SP2 (Standalone or Farm structure) This article contains information in the following sections: Features Supported on page 649 Requirements for backup / restore support of SharePoint 2007 on page 650 Backup Policy on page 651 Restore Policy on page 651 Alternate Location Restores on page 651 Post-Restore steps (on the target SharePoint server): on page 653 Required Account Permissions for Running VSS on page 654 TROUBLESHOOTING on page 654
Features Supported
Functionality Server farm, except the configuration and Central Administration databases Configuration and Central Administration databases Web applications Site collections Content databases Databases for Shared Services Providers Search databases for Shared Services Providers Search databases Windows SharePoint Service Search Office SharePoint Server Search DS-Client (VSS-aware Backup / Restore) Yes No (Microsoft does not support this capability) Yes Yes Yes Yes Yes Yes Yes Yes


Confidential.
Requirements for backup / restore support of SharePoint 2007

The following requirements must be met before you can backup / restore SharePoint servers with the DS-Clients VSS-aware backup set type. 1. On every target SharePoint machine you want to back up, you must manually start the Windows SharePoint Services VSS Writer service: Open Administrative Tools > Services and start the service. By default, this service must be manually started, however you can configure it with the Automatic startup type. Register the Writer in the Windows registry by running the STSADM -o registerwsswriter command from a command prompt. The executable is located in the <%Program Files%>\Common Files\Microsoft Shared\Web Server Extensions\12\Bin\ directory. 2. The Windows SharePoint Service Search (SPSearch) must be running on the SharePoint web server if you want to backup SPSearch. 3. The Office SharePoint Server Search (OSearch) must be running on the SharePoint web server if want to backup OSearch. 4. If backing up a SharePoint Farm (not a standalone machine), the following additional requirements must be met: Add the IP address and computer name for all the MS SQL Server(s) and SharePoint Web servers in the Farm to the DS-Client computers Hosts file, which is usually found in:
The Windows SharePoint Services VSS Writer service must be running on one of the SharePoint web servers. The SQL Server VSS Writer service must be running on every MS SQL Server machine in the SharePoint Farm. 5. You must manually document all the configuration settings in Office SharePoint Server in order to be able to correctly re-create the configuration database and the Central Administration content database of a SharePoint Farm. Microsoft (KB article #512815) recommends documenting the following settings:
Application pool settings, including service accounts (all accounts that run as Web applications, including the crawler account and the search account). Alternate access mapping settings. Farm-level search settings. External service connection settings. Workflow management settings. External service connection settings. Workflow management settings. E-mail settings. A-V settings. Usage analysis processing settings. Diagnostic logging settings. Content deployment settings. Timer job settings. HTML viewer settings. Recycle Bin settings and other Web application general settings. Administrator-deployed form templates. Default quota templates.

Confidential.
Database names and locations. Web application names and databases. Be sure to document the content database names associated with each Web application. Crawler impact rules. Activated features. Blocked file types.
Backup Policy
The backup set must be created on one of the Web Front End (WFE) servers. DS-Client must be able to resolve the computer name of the MS SQL server. DS-Client must be able to access all MS SQL server databases used by SharePoint. The MS SQL databases used by SharePoint can support differential backup (see the Knowledge Base Article for Microsoft SQL Server Database Backup Policy on page 562). During backup, OSearch and SPSearch will always be backed up using a Full dump.
Restore Policy
1. During a restore, there are two phases: The first phase restores the SharePoint servers MS SQL full dump. The second phase restores the SharePoint servers MS SQL differential backups (if applicable) as well as OSearch and SPSearch. 2. Before restoring a Web Application, any existing Web Application with the same name must be deleted from SharePoint Central Admin. 3. Before restoring OSearch, you must ensure the SharePoint Service provider (SSP), associated databases and index files do not exist in the original location. Do not remove the web application if the SSP is Administration site host for Shared Services. It is not possible to remove the last SSP by using Central Administration. You will need to use the stsadm command:
stsadm -o deletessp -title <SSP name> -deletedatabases -force
4. OSearch must be disabled on the target server. Run the following command to check the status:
stsadm -o osearch -action list
To disable OSearch if that status is online, run the following command:

stsadm -o osearch -action stop
Alternate Location Restores

The following considerations must be made if you want to restore a VSS-aware SharePoint backup to an alternate location. 1. A VSS-aware SharePoint backup set only supports renaming the SQL database component in an alternate restore. You can only rename the SQL database name. However, this will not rename the internal .mdf and .LDF files of this database. Therefore before performing the restore, make sure there is no file of the same name in the target data directory, otherwise the restore will fail.

Confidential.
For example: If the original database name is abcd123, then the internal database and log files will likely be abcd123.mdf and abcd123.LDF. If you restore the SharePoint server to an alternate location and rename the database to xyz1234, the internal files will still be abcd123.mdf and abcd123.LDF. Whatever name you want to change the database to, it must already exist in the SharePoint server. This is because the VSS-writers need to be able to link the restored data to the new database name. (In the previous example, this would mean linking the abcd123.mdf and abcd123.LDF files to the xyz1234 database.) 2. Renaming components: Normally, you must restore a VSS-aware SharePoint backup as it was originally backed up (i.e. by allowing the VSS writers on the target machine to perform their restore operations). It is only useful to rename the SQL Server component of a SharePoint server in the following scenarios. Scenario 1: The source database name already exists in the target SharePoint Farm (i.e. it is being used by another database). Restore Steps: 1. Create a new database in the database server of SharePoint Farm. 2. Alternate restore the SharePoint server and rename the database component to the database created in step 1. 3. After the alternate restore is finished, in the SharePoint server application, create a new web application using the restored database. Scenario 2: The target database has a different database name from the source, however it does have the same databaseid and siteid as the source. Restore Steps: 1. Alternate restore the SharePoint server and rename the database to the same name as on the target location (i.e. the database that has the same databaseid and siteid but different database name).


Confidential.
Post-Restore steps (on the target SharePoint server):

1. After restoring Web application: Go to the SharePoint Central Administration web page, click on 'Application management', 'create or extend web application', attach the content database to a new web application. 2. After restoring Osearch: Start Osearch service using "stsadm -o osearch -action start" For example:
stsadm -o osearch -action start -role IndexQuery -farmcontactemail "administrator@asigravss.com" -farmserviceaccount "asigravss\administrator" -farmservicepassword "P@ssw0rd"
Run "stsadm -o osearch -action list", make sure status is Online. Restore ssp using "stsadm -o restoressp" operation on a WFE and make sure to use the "KeepIndex" parameter. This "hooks up" the SharePoint Service provider (SSP) you restored to the SharePoint Farm". For example:
stsadm -o restoressp -title SharedServices1 -url "http://winsp2:3000" -ssplogin "asigravss\administrator" -ssppassword "P@ssw0rd" -mysiteurl "http://winsp2:3000/MySite" -indexserver winsp1 -indexlocation "C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications" -keepindex -sspdatabaseserver "winsql2008" -sspdatabasename "SharedServices1_DB" -searchdatabaseserver "winsql2008" -searchdatabasename "SharedServices1_Search_DB"
Restart the SharePoint Service VSS Writer from Administrative Tools > Services. 3. After restoring SPsearch: Restart the Windows SharePoint Services Search service from Administrative Tools > Services.


Confidential.
Required Account Permissions for Running VSS

Microsofts VSS has special requirements for the accounts running the writers on all target server instances for backup and restore: You can configure this account from the target computers by opening Administrative Tools > Services, highlighting the corresponding VSS Writer Service and right-clicking on Properties. In the Log On tab, you can configure the account that runs the writer. The account running the VSS writer must a member of the Domain Administrators group. The account must have permission to issue BACKUP DATABASE and RESTORE DATABASE commands to the target database servers. The account must have permission to access MS SQL Server, which requires it to be a member of the SQL Server sysadmin group.
TROUBLESHOOTING
Problem: After restoring from a SharePoint VSS-aware backup set, you try to create a new web application in the restored SharePoint server (for example, using WSS_Content_1080). When you do, SharePoint returns errors similar to the following:
The attach operation cannot continue because another object in this farm already contains the same ID. ... An object of the type Microsoft.SharePoint.Administration.SPApplicationPool named "SharePoint 1090" already exists under the parent Microsoft.SharePoint.Administration.SPWebService named "". Rename your object or delete the existing object. An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=Sharepoint -1080 Parent=SPWebService is being updated by <Domain>\<User>, in the OWSTimer process, on machine <Computer>. View the tracing log for more information about the conflict.
Reason: This is a known Microsoft issue. Before any SharePoint database is restored, you must ensure that there is no existing database ID (of the same number). If there is, it must be completely removed from SharePoint (including any shared applications). Solutions: 1. Refer to the Microsoft KB article 939308 (http://support/microsoft.com/kb/939308). This article explains how to clear the file system cache on all servers in the server farm on which the Windows SharePoint services timer service is running.
See Also
VSS-aware backup sets on page 161 Backup / Restore of Microsoft SharePoint 2010 (VSS-aware backup sets) on page 655


Confidential.
Backup / Restore of Microsoft SharePoint 2010 (VSSaware backup sets)

Creation Date: March 04, 2011 Revision Date: September 28, 2012 Product: DS-Client (Windows)
Summary
This article covers various backup / restore issues for Microsoft SharePoint 2010 backups (using the VSS-aware backup set type). The DS-Client supports backup and restore of the following products: Microsoft SharePoint Foundation 2010 (Standalone or Farm structure) Microsoft SharePoint Server 2010 (Standalone or Farm structure) This article contains information in the following sections: Features Supported on page 655 Requirements for backup / restore support of SharePoint 2010 on page 656 Backup Policy on page 656 Restore Policy on page 656 Alternate Location Restores on page 657 Post-Restore steps (on the target SharePoint server): on page 657 Required Account Permissions for Running VSS on page 658 Item-Level Restore of SharePoint 2010 (SP1 & up) on page 658
Features Supported
Functionality Server farm, except the configuration and Central Administration databases Configuration and Central Administration databases Web applications Site collections Content databases Databases of Search Service Application Search databases Windows SharePoint Service Search Office SharePoint Server Search DS-Client (VSS-aware Backup / Restore) Yes No (Microsoft does not support this capability) Yes No Yes No No No No


Confidential.
Requirements for backup / restore support of SharePoint 2010

The following requirements must be met before you can backup / restore SharePoint servers with the DS-Client's VSS-aware backup set type. 1. On every target SharePoint machine you want to back up, you must manually start the SharePoint 2010 VSS Writer service: Open Administrative Tools > Services and start the service. By default, this service must be manually started, however you can configure it with the Automatic startup type. Register the Writer in the Windows registry by running the STSADM -o registerwsswriter command from a command prompt. The executable is located in the <%Program Files%>\Common Files\Microsoft Shared\Web Server Extensions\14\Bin\ directory. 2. If backing up a SharePoint Farm (not a standalone machine), the following additional requirements must be met: Add the IP address and computer name for all the MS SQL Server(s) and SharePoint Web servers in the Farm to the DS-Client computer's "Hosts" file, which is usually found in:
3.
The SharePoint 2010 VSS Writer service must be running on one of the SharePoint web servers. The SQL Server VSS Writer service must be running on every MS SQL Server machine in the SharePoint Farm. Microsoft KB article #645391 describes how to use Windows PowerShell 2.0 to document the configuration settings for your SharePoint Farm. Documenting configuration settings is important both so that you can create scripted deployments for your environment and so that you can quickly re-create a set of configurations in the event of a failure.
Backup Policy
The backup set must be created on one of the Web Front End (WFE) servers. DS-Client must be able to resolve the computer name of the MS SQL server. DS-Client must be able to access all MS SQL server databases used by SharePoint. The MS SQL databases used by SharePoint can support differential backup (see the Knowledge Base Article for Microsoft SQL Server Database Backup Policy on page 562).
Restore Policy
1. During a restore, there are two phases: The first phase restores the SharePoint server's MS SQL full dump. The second phase restores the SharePoint server's MS SQL differential backups (if applicable). 2. Before restoring a Web Application to its original location, any existing Web Application with the same name and related Shared Service Application must be deleted from SharePoint Central Admin.


Confidential.
Alternate Location Restores

The following considerations must be made if you want to restore a VSS-aware SharePoint backup to an alternate location. 1. A VSS-aware SharePoint backup set only supports renaming the SQL database component in an alternate restore. You can only rename the SQL database name. However, this will not rename the internal .mdf and .LDF files of this database. Therefore before performing the restore, make sure there is no file of the same name in the target data directory, otherwise the restore will fail. For example: If the original database name is 'abcd123', then the internal database and log files will likely be 'abcd123.mdf' and 'abcd123.LDF'. If you restore the SharePoint server to an alternate location and rename the database to 'xyz1234', the internal files will still be 'abcd123.mdf' and 'abcd123.LDF'. Whatever name you want to change the database to, it must already exist in the SharePoint server. This is because the VSS-writers need to be able to link the restored data to the new database name. (In the previous example, this would mean linking the 'abcd123.mdf' and 'abcd123.LDF' files to the 'xyz1234' database.) 2. Renaming components: Normally, you must restore a VSS-aware SharePoint backup as it was originally backed up (i.e. by allowing the VSS writers on the target machine to perform their restore operations). It is only useful to rename the SQL Server component of a SharePoint server in the following scenarios. Scenario 1: The source database name already exists in the target SharePoint Farm (i.e. it is being used by another database). Restore Steps: 1. Create a new database in the database server of SharePoint Farm. 2. Alternate restore the SharePoint server and rename the database component to the database created in step 1. 3. After the alternate restore is finished, in the SharePoint server application, create a new web application using the restored database. Scenario 2: The target database has a different database name from the source, however it does have the same databaseid and siteid as the source. Restore Steps: 1. Alternate restore the SharePoint server and rename the database to the same name as on the target location (i.e. the database that has the same databaseid and siteid but different database name).
Post-Restore steps (on the target SharePoint server):

1. After restoring from DS-Client, manually create the Web application: Go to Central Admin > Manage Web Applications > Click 'New' Enter the name of the database that was restored from DS-Client. Alternatively, you can use Windows PowerShell by entering the following command:
New-SPWebapplication -name "Team 2000" -URL "http://spsp1:2000" applicationpool "sharepoint web services default" -applicationpoolaccount "asigra2010\administrator" -databasename "WSS_Content_2000" databaseserver "SPSQL"


Confidential.
Required Account Permissions for Running VSS

Microsofts VSS has special requirements for the accounts running the writers on all target server instances for backup and restore: You can configure this account from the target computer's by opening Administrative Tools > Services, highlighting the corresponding VSS Writer Service and right-clicking on "Properties". In the "Log On" tab, you can configure the account that runs the writer. The account running the VSS writer must a member of the Domain Administrators group. The account must have permission to issue BACKUP DATABASE and RESTORE DATABASE commands to the target database servers. The account must have permission to access MS SQL Server, which requires it to be a member of the SQL Server administrator group with db_creator and sysadmin roles.
Item-Level Restore of SharePoint 2010 (SP1 & up)

VSS-aware backups of SharePoint 2010 (SP1 and up) servers have a granular restore capability. This allows you to restore at the individual Item-Level from a backed up SharePoint 2010 database. Requirements: This feature works for backups of MS SharePoint 2010 SP1 servers. The backup must be made using the VSS-aware backup set type. The target MS SharePoint server where you want to peform the Item-Level restore must have DS-Recovery Tools installed and running. This is a separate installation (see DS-Recovery Tools Installation Guide). The DS-Recovery Tools service account must have access to the SQL Server instance and to the MS SharePoint server where the items are going to be restored. There are two steps to performing a granular restore: Step 1) Restore the database and Step 2) Restore Items. The first step restores the SharePoint database at the point-in-time that contains the items you want to restore. The second step involves connecting to that database and selecting the individual items you want to restore. 1. Browse the Backup Sets tree and highlight the one you want to restore. 2. Right-click. Click Restore Now.


Confidential.
3. In the Select the VSS Restore Method screen, select the Granular Restore option Step 1. Database Restore.
F1 Help: See Select the VSS Restore Method on page 852. Select the Granular Restore option, then choose Step 1. Database Restore. Note: If you are restoring from a BLM Restorable Image or Disc/Tape media, you can only perform Step 1 - the database restore from that media. Step 2 must always be peformed from the database restored in Step 1. 4. Click Next >. In the Select directories/files for restore screen, select the SharePoint database to restore.
F1 Help: See Select directories / files (Restore / BLM / Delete / Validation) on page 826.


Confidential.
5. Click Next >. In the Select database restore location screen, choose where you want to restore the SharePoint 2010 database. This must be to a MS SQL Server.
F1 Help: See Select database restore location screen (SharePoint) on page 826. You can restore to a different SQL instance or select a different SQL server (which does not have to be a SharePoint farm) but this SQL server must be in the same domain as (or a trusted domain of) the target SharePoint server you want to restore to (in Step 2 - Items-Restore). 6. Click Next >. The Restore Now Wizard switches to its Select restore performance options screen. F1 Help: See Select Restore Performance Options (Windows DS-Client) on page 847. These options are intended for large backup sets in high performance environments. In general, you should use the defaults and skip to the next screen. 7. Click Next >. In the Select restore options screen, select the SharePoint database restore options.
F1 Help: See Select Restore Options (VSS-aware SharePoint) on page 847.


Confidential.
8. Click Finish. The restore process begins. Once the SharePoint 2010 database has been restored to a MS SQL server, you can proceed to step 2 (restoring at Item-Level). 9. Browse the Backup Sets tree and highlight the same backup set. Right-click Restore Now. 10. In the Select the VSS Restore Method screen, select the Granular Restore option Step 2. Items Restore.
F1 Help: See Select the VSS Restore Method on page 852. 11. Click Next >. The Select SQL Server screen appears. Select the MS SQL Server where you restored the SharePoint 2010 database.
F1 Help: See Select the computer screen on page 850.


Confidential.
12. Click Next >. The Select database for restore screen appears. Select the MS SQL database containing the SharePoint 2010 database.
F1 Help: See Select Items for Backup Set screen on page 831. 13. Click Next >. The Select restore location screen appears. You can restore to the original source location or choose an alternate SharePoint server.
F1 Help: See Select restore location screen on page 840. The restore destination you select must be running the DS-Recovery Tools (separate installation required). 14. Click Next >. The Select a Site Collection / Sub-Site screen appears. This selection determines the granularity of the restore. It can be broad (e.g. restore the entire Site or a specific sub-site) or it can be extremely precise (e.g. restoring an individual item


Confidential.
from a list belonging to the site).
F1 Help: See Select a site collection / sub-site (SharePoint Item-Level) on page 820. In the Site Collection List, you can select the entire site (/), or a specific subsite by highlighting the folder and clicking Add. Your selection appears in the Restore Items section. You can hover the mouse pointer over a folder to see corresponding URLs and source database name. To restore a Full List, highlight the site folder (or sub-folder) containing the list you want and click Add Lists.
F1 Help: See Select a List / Customer List / Document Library (SharePoint Item-Level) on page 820. You can select one, several, or all of the items that appear. Each item is either a List, Customer List, or Document Library containing its own set of items from the SharePoint database.


Confidential.
Click Next >. If you are restoring at the List level, the Restore Wizard jumps to the Select restore options screen. Otherwise, click Finish. To restore a List-Item, highlight the site folder (or sub-folder) containing the list you want and click Add List Items. Select the List, Custom List, or Document Library Containing the item(s) you want and click Next.
F1 Help: See Select SharePoint List Item (SharePoint Item-Level) on page 849. Click on the list item(s) you want to restore (use CTRL + click for multiple items). - Click Finish. 15. When you have finished making your restore selections, click Next >. The Select restore options screen appears.
F1 Help: See Select restore options (SharePoint Item-Level) on page 847. You must supply the Web Application URL and Temporary Export Path. 16. Click Finish. The restore process begins.


Confidential.
See Also
VSS-aware backup sets on page 161 Backup / Restore of Microsoft SharePoint 2007 (VSS-aware backup sets) on page 649


Confidential.
Backup / Restore of NAS (Linux DS-Client)

Creation Date: December 02, 2011 Revision Date: September 18, 2012 Product: DS-Client (Linux)
Summary
This article describes the backup and restore process for NAS (Network Attached Storage) devices using the NAS, UNIX-SSH, NFS, Local File System backup set type. In order to backup/restore the NAS device, DS-Client utilizes a dedicated API from the NAS vendor. DS-Client uses the API for creating a volume based snapshot on the NAS device for the data selected in the backup set. After creating a snapshot, DS-Client temporarily mounts a NAS share and backs up the data from the snapshot. When the backup is finished, DS-Client unmounts the NAS share and deletes the snapshot. Note: CIFS shares or volumes with NTFS / Mixed security type are not supported.
Note:
NAS backup is only supported on Linux DS-Client (not on Mac DS-Client).
Creating a NAS backup set

1. Open DS-Client New Backup Set Wizard, select the NAS, UNIX-SSH, NFS, Local File System and click Next. 2. Select NAS and enter the NAS IP address or DNS name in the Path field (e.g. NAS\10.10.20.33). Check the Ask for credentials box if the current DS-Client user has no data access rights on the NAS device or if you want to use a different user. Click Next.


Confidential.
3. If the "Ask for credentials" option was selected the "Ask for credentials" windows appears. Provide a valid user name and password and click "OK". 4. By default, the Ask for NAS API credentials box is selected, and you are prompted to supply the NAS API connection credentials.
F1 Help: See Specify Credentials (Linux DS-Client) on page 886. Select the NAS type and the API access protocol. Specify the port for the API connection, API user credentials and a mount point to be used for mounting the NAS share during the backup. You can use an existing mount point or create a new one for a backup purpose. Click "OK". Note: Make sure the specified User has rights to execute the API commands on the NAS device. This usually means the user is a member in the Administrators group. 5. Browse the NAS shares and add data into the "Selected Items for Backup list and then click Next. 6. Follow the next steps as you would for the regular backup set type until the "Specify backup set options" Wizard screen appears. Choose the desired behavior for the "Continue backup on snapshot failure" option: If this option is selected (default), in case of snapshot failure the DS-Client will try to access the data selected in the backup set directly by skipping the snapshot functionality. If this option is un-checked, in case of a snapshot failure DS-Client will stop the backup process. 7. Finish creating the backup set by specifying the rest of the options as you would with a regular file system backup set.
NetApp configuration requirement

For NetApp NAS volumes, there is a volume configuration option that enables accessing the .snapshot file for NFS when browsing the NetApp volumes. This must be selected, otherwise the DS-Client cannot access the snapshot.
Snapdiff API
Linux DS-Client has the Use Snapdiff API option for (NetApp) NAS backup sets. This will appear if the DS-System is using NetApp storage, and is configured to support the NetApp Snapdiff. If selected, DS-Client will attempt to use the NetApp Snapdiff API to avoid re-scanning the whole NAS volume during an incremental backup. Snapdiff compares the current snapshot with the last snapshot of the target NAS volume and generates the list of new and changed files from that comparison. This can provide significant speed improvements to the backup process, especially on large volumes.

Confidential.
The following limitations exist. In all cases where the Snapdiff fails, DS-Client will attempt a full scan of the NAS volume. A previous snapshot must exist in order for the Snapdiff API to work. Snapdiff does not work on the first (baseline) backup. Snapdiff does not work if the current snapshot fails. Snapdiff does not work if any of the backup sets backup items have been changed (since the previous backup).
See also
NAS, UNIX-SSH, NFS, Local File System Backup (LINUX DS-Client) on page 112 Backup / Restore of NAS (Windows DS-Client) on page 669


Confidential.
Backup / Restore of NAS (Windows DS-Client)

Creation Date: December 22, 2011 Revision Date: May 15, 2012 Product: DS-Client (Windows)
Summary
This article describes the backup and restore process for NAS (Network Attached Storage) devices using the "File System" backup set type. In order to backup/restore the NAS device, DS-Client utilizes a dedicated API from the NAS vendor. DS-Client uses the API for creating a volume based snapshot on the NAS device for the data selected in the backup set. After creating a snapshot, DS-Client temporarily mounts a NAS share and backs up the data from the snapshot. When the backup is finished, DS-Client unmounts the NAS share and deletes the snapshot.
Note:
Currently only CIFS shares of volumes with NTFS security type are supported by Windows DS-Client.
Creating a NAS backup set

1. Open DS-Client New Backup Set Wizard, select the "File System" and click "Next". 2. Enter the NAS IP address or DNS name in the "Path" field (e.g. "10.10.20.123"). Check the "Ask for NAS API credentials" box. Click "Next".
3. The "Enter Network Credentials" windows appears. Provide a valid user name and password for data access on the NAS device and click "OK".


Confidential.
4. You are prompted to supply the NAS API connection credentials.
F1 Help: See Enter NAS API Parameters (Windows DS-Client) on page 777. Select the NAS type and the API access protocol. Specify the port for the API connection and API user credentials. Click "OK". Note: Make sure the specified User has rights to execute the API commands on the NAS device. This usually means the user is a member in the Administrators group. 5. Browse the NAS shares and add data into the "Selected Items for Backup list and then click Next. 6. Follow the next steps and finish creating the backup set by specifying the rest of the options as you would with a regular file system backup set.
NetApp configuration requirement

For NetApp NAS volumes, there is a volume configuration option that enables accessing the ~snapshot file for CIFS when browsing the NetApp volumes. This must be selected, otherwise the DS-Client cannot access the snapshot.
See also
Backup / Restore of NAS (Linux DS-Client) on page 666


Confidential.
Backup from the Cloud (Salesforce.com) Limitations

Creation Date: August 20, 2012 Revision Date: October 12, 2012 Product: DS-Client
Summary
This article contains additional information about the Backup from the Cloud (Salesforce.com) backup set type.
Force.com API Usage Limits

The DS-Client is using the Salesforce API for backup and restore. Salesforce.com balances transaction loads by imposing two types of limits on API calls: Concurrent API Request Limits Total API Request Limits When a call exceeds a request limit, an error is returned. This can impact the DS-Client with errors if your Salesforce.com account exceeds their specified limits. For more detailed information, see the article Force.com API Usage Limits, which as of the latest revision date of this article was located at:
https://login.salesforce.com/help/doc/en/integrate_api_rate_limiting.htm
Contact Salesforce about modifying the API limits associated with your account.
Password and Security Token

If you ever need to change your Salesforce.com password, this also means you must obtain a new Security Token. You can request the security token from the Salesforce.com website (Setup > My personal information > reset my security token). All existing Salesforce.com backup sets must be updated with the new credentials (username, password, and security token).
Restore Limitations
The DS-Client is using the Salesforce API for backup and restore. There is currently a limitation in the restore process: After backup, if you do restore two (2) times, you will have duplicate items because of the way the API compares the IDs of files to be restored.
Restore Limitations from BLM Restorable Images or Disc/Tape media

Salesforce.com backup sets that have been written to BLM Restorable Images or Disc/Tape media have a limitation during the Restore Wizard since those media are written without the credentials to the original backup target server (Salesforce.com database). In the Restore Wizards Select restore location screen, you must use the Alternate location field to specify the restore target (the Original location option is grayed out). This allows you to re-supply the credentials of the restore target in the Specify Credentials screen.


Confidential.
See also
Backup from the Cloud (Salesforce.com) on page 167 Restore a Backup from the Cloud (Salesforce.com) Backup Set on page 257 Cloud database upload tool (Salesforce.com) on page 258


Confidential.
Local DS-VDR backup set

Creation Date: June 21, 2012 Revision Date: August 27, 2012 Product: DS-Client (Windows) & Local DS-VDR Tool
Summary
This article provides additional information about the Local DS-VDR Tool. When installed and configured with DS-Client, this tool allows creation of Local DS-VDR backup sets that protect a VMware virtual machine by exporting the VM. The latest VM is exported through the vCenter to another host / datastore, which provides a standby VM that is always available for failover (with the same vCenter). Note: A Local DS-VDR backup set does not backup data to DS-System.
Local DS-VDR Tool configuration requirements

The following requirements must be met for the Local DS-VDR Tool: The Local DS-VDR Tool comes in a separate installation. This can be found on the installation DVD in the folder:
\Software\Tools\Local_DS-VDR\Windows_64_bit\setup.exe
You must install the Local DS-VDR Tool on a network computer that can connect to both this DS-Client and the target VMware vCenter. TCP Port 4407 must be open for the Local DS-VDR Tool to connect with the DS-Client.
DS-Client configuration requirements

The following requirements must be met on the DS-Client, in order to work with the Local DS-VDR Tool: The DS-Client must be configured to point to a Local DS-VDR Tool from Local DS-VDR menu > Configure Local DS-VDR Tool. The DS-Client must have at least one Local DS-VDR license count available. This is allocated by your Service Provider from DS-System. If the DS-Client cannot allocate a license, you will not be able to finish creating the backup set.
How Local DS-VDR works

Once you have created a Local DS-VDR backup set that identifies the Virtual Machines you want to protect, you can schedule it for backup. For Local DS-VDR backup sets, a backup triggered by DS-Client will have the DS-VDR Tool send the export instructions to the VMware vCenter. The latest version of the VM will be exported to the configured host and datastore. Remember that there is no data stored on DS-System for Local DS-VDR backup sets. The Virtual Disaster Recovery comes from the export of the VMs latest generation to another host / datastore on the vCenter for quick failover in the event the protected VM fails. The backup item generations (Max Gen) setting for a Local DS-VDR backup set determines how many versions of a Virtual


Confidential.
Machine will be exported on the vCenter. Once this limit is reached, the oldest exported VM is overwritten at the next backup.
Deleting a Local DS-VDR backup set

If you want to delete a Local DS-VDR backup set, the DS-Client must be able to connect to a Local DS-VDR Tool (configurable from DS-User > Local DS-VDR menu > Configure Local DS-VDR Tool).
Physical to Virtual Backup Sets

The Local DS-VDR Tool is required to enable the Physical to Virtual backup set option. For more information see the section 4 - Creating and Modifying Backup Sets on page 92.
See also
Local DS-VDR backup set (VMware VADP) on page 169


Confidential.
Physical-to-Virtual backup set

Creation Date: August 28, 2012 Revision Date: August 28, 2012 Product: DS-Client (Windows) & Local DS-VDR Tool
Summary
This article provides additional information about the Physical-to-Virtual backup set type. This backup set type allows you to backup a physical machine to a VMware virtual machine. Note: A Physical-to-Virtual backup set does not backup data to DS-System.
Physical-to-Virtual Requirements
The following requirements must be met in order to create Physical to Virtual backup sets: 1. Your DS-Client must be configured with the Local DS-VDR Tool feature and be pointing to a running instance of the tool (Local DS-VDR menu > Configure Local DSVDR Tool). 2. You must install the following VMware Plug-in on the Local DS-VDR Tool computer:
VMware vCenter Converter Standalone
This plug-in can be found on the vmware.com Web site. Run the installation and choose the Client-Server installation (advanced) Setup Type. 3. Make sure to export the physical machine to a datastore that has enough space.
Other details
As of the revision date of this article, Physical-to-Virtual conversion is supported for Windows physical machines only. Each Physical machine that is protected will cost one Local DS-VDR license count. The exported vm will be named with a pre-fix 'Local DS-VDR' and the backup timestamp as suffix, in the following format:
Local DS-VDR_physical_machine's_IP_TimeStamp
See also
Physical to Virtual backup set on page 172


Confidential.
Block-Level Resume
Creation Date: October 17, 2005 Revision Date: February 17, 2010 Product: DS-Client
Summary
If the backup is interrupted (e.g. the connection to DS-System is lost), DS-Client will attempt to reconnect for a specified number of times (DS-User Menu > Configuration > Parameters > Scheduled backups) in order to resume the backup. Block-Level Resume allows the scheduled backup to continue the backup from the last successful file block backed up in the session. The benefit increases with the size of the file being backed up. (For example: without this feature, backup of a large file that is interrupted because of a slow / poor connection would have to restart from the beginning of the file.) Block-Level Resume applies to: Big files (files larger than 100MB). Scheduled backups. For Windows DS-Client: This solution applies to File System backup sets, and to other backup sets that use the DS-Client Buffer (See DS-Client Buffer on page 500.): File System backup sets. Permissions backup sets. SQL backup sets using DS-Client buffer. Exchange backup sets using DS-Client buffer. Oracle backup sets using DS-Client buffer. E-Mail backup sets using DS-Client buffer. System i Server backup sets using DS-Client buffer. For Linux DS-Client: File System backup sets can resume at block-level for the following backup set types: Local File System UNIX-SSH NFS
Note:
When Block-Level Resume does not apply, the resume will occur at file-level.


Confidential.
Continuous Data Protection (Backup Set Option)

Creation Date: July 31, 2006 Revision Date: March 09, 2012 Product: DS-Client Summary on page 677. Details on page 677. Continuous Data Protection Requirements on page 678. Features and Limitations on page 678. CDP with other Activities on page 679. CDP Backup Sets that are Scheduled on page 680. Bandwidth considerations (catch-up, queueing, granularity): on page 680. Reconnection: on page 680. Switching a backup set from CDP to non-CDP on page 681.
Summary
Users often want their data to be protected as soon as it is in its final state. This means that scheduling backups weekly (or even daily) may not be sufficient, because data may not be backed up before the machine has a problem. Although hourly backups can provide a more robust backup strategy, they may consume too much system resources because a complete file system scan is required. Word processing or spreadsheet files are some examples of when users would like to have their data protected as soon as it is possible (or after a very small interval of time): once the document is saved to disk, it will be backed up by DS-Client and sent offsite. Continuous Data Protection is a backup solution that continuously monitors the changes on the target server and backs up the changes as soon as they are detected. It differs from the normal point-in-time backup - it is continuous data protection. It also differs from replication or mirroring, which only keep a snapshot of the latest image. Instead, Continuous Data Protection will also keep intermediate changes and be able to recover images from a specific time.
Details
Once a Continuous Data Protection backup is started (on demand or scheduled), the DS-Client continuously monitors the changes happening on the target backup server. As soon as a change happens, DS-Client will immediately backup the changes to the DS-System. DS-Client can also be configured with Local Storage for fast recovery purposes. It is not mandatory to backup a whole server with Continuous Data Protection. Like normal file system backup sets, customers can select specific parts of a server (any combination of share level, directory level, and file level filters). Extended Regular Expressions can be used to define complicated selections. The Retention feature can help you to manage the amount of online generations stored on the DSSystem. For more information, see About Retention Rules on page 85. In case the continuous backup is interrupted for any reason (by demand, hardware / software failure, network problems, target server not available, etc.), in the next backup (including the very first backup), the process will re-initialize and a full scan will be performed from the beginning.


Confidential.
Continuous Data Protection Requirements

Supports File System Backups of Windows or UNIX servers. Supports MS Exchange E-Mail backups (using DS-MLR and Windows DSClient). Supports pure file system backup items only. (System Status and Services Database are not supported, since they cannot be managed like pure files.) Works with all other DS-Client features, except Use Buffer and Pre-Scan. They are not available because they conflict with the logic of Continuous Data Protection.
Features and Limitations

1. A regular point-in-time backup process stops once all the backup items have been processed. The Continuous Data Protection process does not have a natural finished state. Once started (by schedule / on demand), the Continuous Data Protection process will not stop until one of the following conditions occurs: A demand stop is issued (i.e. click Stop). The scheduled time limit is reached. It is suspended by conflicting activities. (See CDP with other Activities on page 679.) It runs out of retry connect times to DS-System (including restart backup scenarios). Some other unexpected stop condition (Exceptions, failed to connect to target, etc.). 2. Windows 2000 & up options support with Continuous Data Protection: Follow Junction Point is NOT supported because DS-Client cannot be notified of changes that happen inside the junction point. Backup data in Remote Storage is supported. However, like normal backup, if the data on the remote storage is changed but not the placeholder, DS-Client cannot detect the change. Backup Single Instance Store file data is supported. 3. When migrating a Continuous Data Protection set, the new target server must meet the same requirements (See Continuous Data Protection Requirements on page 678.). 4. A normal backup set can be changed to a Continuous Data Protection set, if it satisfies all the conditions mentioned above. The Backup Options screen will only allow you to select Continuous Data Protection if this is true. 5. Even with the Continuous Data Protection process, the same file cannot be backed up more than one time in the same second. Continuous Data Protection is designed to support changes down to the second. For data that changes very often, CDP can be configured to wait a specified amount of time from the last change to a file before backing it up. 6. File Change Detection is configurable at the backup set level. Windows Built-in File Monitoring (Windows only): Interfaces with Windows Operating System functionality for notification of file changes. File Alteration Monitor (Linux only): Similar to the Windows Built-in File Monitoring. Interfaces with Linux Operating System functionality for notification of file changes. FAM will only be used if it is installed and working on the target machine (i.e. if the FAM daemon can be started). If FAM is not installed, DS-Client will try to copy and execute a FAM instance on a target Linux machine. Note: FAM may not be available for some UNIX platforms.

Confidential.
Generic Scanner (UNIX only): Loops the scanning function from regular backup sets. (This can be used if the File Alteration Monitor is not available. This permits CDP of any file data at the expense of a higher I/O load.) MLR E-Mail Monitoring (Windows only): Monitoring included with the DSMLR service installation. 7. Windows DS-Clients can only perform CDP if the target backup machine is supported (Windows NT 4.0 or later). It cannot support servers that are simulated as Windows machines (e.g. using SAMBA to backup a unix machine). 8. CDP with BLM (Infinite Generations) will start Archiving activities as needed. While an archiving activity is in progress, the BLM will deny access to the package that is currently open for activities like Browse, Create Restorable Image, Retention, etc. The DS-System will stop the current archiving activity after 5 minutes of inactivity, and restart a new one if needed. 9. The Process Window for CDP backup sets always shows the current data transfer rate. (For regular backup sets, this number is the average transfer rate achieved since the start of the backup.)
CDP with other Activities

Some activities are handled differently when interacting with CDP backup sets. Each CDP backup set has on/off settings to suspend the backup for scheduled Retention, Validation, and BLM (Backup Set Properties > Options Tab: Continuous Data Protection). If the suspend setting is off, the other (scheduled) activity will fail to run with an error. If the suspend setting is on, (or if you run an on demand activity), DS-Client will suspend the CDP and resume or restart after the other (scheduled / on demand) activity finishes. Suspend CDP, then resume Restore BLM Request Validation (without errors) Suspend CDP, then restart a new CDP Synchronization Retention Delete Validation (with errors) Daily Admin / Weekly Admin The strategy is configurable (DS-User > Setup Menu > Configuration > Parameters Tab: CDP Strategy). Skip: Admin will skip any running CDP backup sets Suspend: Admin will suspend any running CDP backup sets, then restart them once the Admin is finished. CDP must not be running The CDP backup set must not be in use if you run any of the following activities (you will not be allowed to proceed until the CDP backup is stopped): Assisted Delete (If a CDP backup is running, that backup set will be skipped) Remove Backup Set Disc/Tape Request


Confidential.
CDP Backup Sets that are Scheduled

A backup schedule can include the following tasks: 1. Perform Backup 2. Enforce Retention 3. Perform Validation 4. Perform BLM For regular backup sets, tasks 1-4 will run in sequence. If the schedule applies to a CDP backup set, tasks 2-4 are handled differently. The schedule will run those tasks in the following sequence, then the CDP backup will resume / restart: 1. Perform Backup: A full scan and backup of the changed items is performed once, then 2. Enforce Retention: Suspend CDP, enforce retention, then restart a new CDP 3. Perform Validation: If validation completed without errors, suspend CDP, then resume. If validation completed with errors, suspend CDP, then restart a new CDP. 4. Perform BLM: Suspend CDP, perform BLM, then resume 5. After the last task is run, the CDP backup is restarted / resumed. Note: The next day, when the CDP backup reaches the same scheduled start time, DS-Client will force a full scan of all files/folders in the CDP backup sets backup items.
Bandwidth considerations (catch-up, queueing, granularity):

If network bandwidth is slow, DS-Client queues the list of changed files. The backup is performed later, as network resources permit, using the latest change to the queued file. This means less granularity (dynamic adjustment to granularity). If there are too many queued changes, a pre-scan of the entire backup set will be performed.
Reconnection:
Both demand and scheduled CDP backup sets will use the reconnection settings from DS-Client Configuration > Parameters Tab: Scheduled backup section.
Unix DS-Client with File Alteration Monitor If the DS-Client cannot access a backup items parent folder when the backup starts, DS-Client will re-check if it can be accessed every 5 minutes.


Confidential.
Switching a backup set from CDP to non-CDP

In order to switch a CDP backup set to a non-CDP backup set the following steps must be taken: 1. If a CDP backup session for that backup set is in progress, it must be stopped. 2. Select that backup set in the DS-User Backup Sets Tab. 3. Right-click > Properties > Options. In the Set Properties Options Tab screen, uncheck Continuous data protection. 4. Click Apply, then OK close the Backup Set Properties screen.
See Also
Backup Set Options - Continuous Data Protection on page 98 About Retention Rules on page 85.


Confidential.
Memory Requirements for DS-Client During Incremental Backup Using Delta Algorithm
Creation Date: August 17, 2004 Revision Date: May 26, 2009 Product: DS-Client
Summary
This article describes the memory requirements for DS-Client when performing incremental backup files using the Delta algorithm.
Details
Processing files with Delta algorithm is very resource intensive (CPU, memory) and DS-Client needs to have enough memory in order to successfully complete. The memory requirements are about 0.25% from the size of the files processed at a given time (please note that a backup activity could process more than one file at once). For example, if DS-Client is processing a 100GB file, it will require 3 unfragmented memory blocks totalling about 0.25GB or about 250MB of memory. Sometimes the memory may become fragmented and DS-Client may not be able to allocate the necessary amount; in such scenarios DS-Client will report "Out of memory" exceptions. Here are a few things you can do if you encounter this situation: Add more physical memory. On a DS-Client backing up a big amount of data (either big files, or a big number of files, or both), SQL Server and the DS-Client service use most of that computers memory. Restarting these services will release some memory otherwise cached and it will reduce the memory fragmentation. MS SQL Server uses as much memory as it is allowed, therefore limiting this amount may be helpful for the other processes on that computer.
Delta processing of large files (up to 1024 TB) on DS-Clients

DS-Clients running on 32-bit Operating Systems support Master/Delta processing for files between 32 KB and 100 TB size. DS-Clients running on 64-bit support Master/Delta processing for files between 32 KB and 1 PB (1,024 TB) size. IMPORTANT NOTE: DS-Client will require a sufficient amount of RAM in order to process any large file. The raw processing overhead in RAM of a single such file is about 0.2-0.5% of the file size for the 32-bit DS-Client and 0.3-1% of the file size for the 64-bit DS-Client. For example: To protect a 1 TB file, the 64-bit DS-Client will require the amount of RAM+SWAP to be 1% x 1TB = 10GB for delta processing (about 0.3 x 1TB = 3GB of RAM minimum recommended).


Confidential.
Stop Backup (DS-User Initiated) behavior

Creation Date: February 9, 2004 Revision Date: October 29, 2009 Product: DS-Client
Summary
This article describes the behavior when a user manually stops a backup set (from the DS-User).
Description
When user stops a backup set, DS-Client is still waiting for the file confirmation. The WaitConfirmation parameter is set in the DS-Client Advanced Configurations (Setup Menu > Configuration > Advanced Tab: Miscellaneous). This is the time out value when waiting for file confirmation. The default value is 60 seconds. If DS-Client still did not receive all confirmations when the time out is reached, DS-Client will disconnect from DS-System and mark the backup set out of sync. In the above scenario for Exchange backup sets, DS-Client will not send the "retrieve deleted/overwritten generations" and the "Delete last session" request. The next synchronization will correct the problem caused by disconnection.


Confidential.
Troubleshooting: Tape Converter

Creation Date: November 12, 2007 Revision Date: February 01, 2010 Product: DS-Client (Windows)
Summary
This article provides some additional information about using the Tape to BLM Converter feature. It is assumed that the Tape Library is installed and properly configured. If the DS-Client does not recognize the Tape Library, it is most likely not properly configured.
Troubleshooting
If a tape library is not recognized: Try restarting the DS-Client computer. 1. If after installing the drivers for the Tape Library, the Library cannot be seen under "Computer Management / Storage / Removable Storage / Libraries", go to:
"My Computer / Properties / Hardware / Device Manager / Tape Drive"
2. Click on properties. If there is a message that you must restart the computer after installing the drivers, click OK and you will be prompted to restart the computer. 3. After you reboot, the Tape Library should be visible under Libraries in Computer Management. IMPORTANT NOTE ABOUT CHANGING TAPES The DS-Client Tape Converter depends on Windows to interface with the Tape Drives. Therefore, you must change tapes in a way that Windows will always be aware of your changes. To change a tape: Open the Tape Drive door, and take a tape out from its slot. Close the Tape Drive door. Let Windows perform its inventory, and the removed tape will be marked as off-line. Open the Tape Drive door again, and put the new tape in the empty slot. Close the Tape Drive door. Windows will identify the new tape. After Windows finishes its identification of the Tape, you must click Refresh in the Tape Conversion Wizard to update the DS-Clients list from the Tape Librarys memory.
See Also
Tape Conversion to BLM on page 294


Confidential.
Troubleshooting: Failure to backup of files from Windows 2008 / Windows 7 / Windows 8

Summary
This article describes failures that may occur when performing backup of remote Windows 2008, Windows 7, or Windows 8 computers from a Windows DS-Client running on VISTA or 2008.
Details
This article applies if your Windows DS-Client fails to back up files from Windows 2008, Windows 7, or Windows 8 computers with either of the following errors:
The request is not supported
or
operation not supported
Windows DS-Clients running on either Windows VISTA or Windows 2008 may encounter these errors when trying to back up files from remote Windows 2008, Windows 7, or Windows 8 computers. 1. This is a Microsoft bug (KB 973278), which can be fixed with their hot fix that is supplied at:
http://support.microsoft.com/kb/973278
2. Apply this hot fix to the DS-Client computer (that is running Windows VISTA or Windows 2008).


Confidential.
Knowledge Base: RESTORE


Confidential.
Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery)
Creation Date: November 11, 2002 Revision Date: February 26, 2008 Product: DS-Client (Windows)
Summary
Please read this whole article first before starting the recovery procedure (to an alternate Exchange Server).
Details
In order to perform a successful restore to an alternate location (different server) several conditions must be met: 1. The recovery server must be installed in a different Active Directory (AD) forest than the original server. The target Exchange server for the restore must be the same version and service pack as the Exchange server that was backed up. 2. The Organization name, the administrative group name, the Storage groups and their stores, and the file locations must be the same as on the original server. If the organization name and/or the administrative group name is not the same, you can use a tool called "legacydn". The tool can be found on the service pack CD in the directory \server\support\utils\i386\LegacyDn. Read the text file that comes with the tool for more information. If you use this tool to rename, you may have to restart "Exchange System Manager". By default, the installation of Exchange 2000 / 2003 server creates the mailbox and public folder stores. These are normally called "Mailbox store (SERVER_NAME)", "Public folder store (SERVER_NAME)". Make sure the recovery server has the same store names as the original server. You can rename the stores using "Exchange System Manager": Right-click on each store and select rename. If the location of the database directories and log file directories is not the same as on the original server, change it here at this stage. 3. The recovery server must have an account member of the administrative group that exists on the DS-Client computer. You can either create an account on the recovery server, or you can create an account on the DS-Client computer that matches the name and password of the administrator account. 4. The DS-Client computer must be able to resolve the fully qualified domain name of the recovery server. Since the recovery server will be on a different Domain (different AD), you can set the DS-Client NICs DNS settings to point to the recovery server. (Do not forget to change it back to the original settings once the restore is completed.) 5. Dismount all the stores. Right click on each store and locate the database and streaming database locations. Using Windows Explorer, delete all the files from these directories. In step 2, you made the location of the database and logs the same; if you have AD users with mailboxes, you may have to delete these mailboxes. Using "Active Directory users and computers" right click on the users, and select "Exchange tasks" > delete mailbox (remember all these actions are to be performed on a test/lab server). In "Exchange System Manager" click on the server and in the left pane right click on each storage group and select "Properties". This gives you the location for the logs. Delete them using Windows Explorer. Mount all the stores. Ignore the warning

Confidential.
for the missing database files and click "Yes" on it. If you get any errors mounting the stores, resolve them before going further. Usually if you had to rename stores or organizations, you have to restart all Exchange services. At this point you should be able to mount all stores without any problems. Right click on each store, select "Properties" and click on the "Database" tab. Select "This database can be overwritten by a restore" checkbox. 6. Once the above conditions are met, you can start the restore from DS-User. In the restore wizard, change the location from "Original location" to "Alternate location", and click on [>>]. Browse and select the recovery server. Check "Ask for network credentials". Once you have selected the server, double click on it or click on the "Select" button. You will be prompted to type a user name and a password. Use the same one from step 3 above. Keep all the rest of the settings unchanged and click "Finish". Note: If you get errors during the restore, it is likely that some of the conditions (1 to 5 above) were not met.
Once the restore is completed without errors you can perform a mailbox recovery if you want.
Mailbox Recovery
The mailbox recovery involves the following steps: 1. Create an Active Directory user account, but do not mailbox-enable the user account. None of the naming for the account needs to match the account that was previously linked to the mailbox. 2. In Exchange System Manager, locate the Mailboxes object under the database object, and then right-click the Mailboxes object to run the Mailbox Cleanup Agent. In the Mailboxes list, make sure that a red X is displayed next to the mailbox that you want to recover. This indicates the mailbox is not connected to an Active Directory user. 3. Right-click the mailbox that you want to recover, and then click Reconnect. A list of Active Directory accounts is displayed, and you can connect the mailbox to the account that you just created for the mailbox.
See Also
Backup / Restore of Microsoft Exchange Server on page 553 Alternate Location Restore of Microsoft Exchange Server 2007 (mailbox recovery) on page 689


Confidential.
Alternate Location Restore of Microsoft Exchange Server 2007 (mailbox recovery)

Creation Date: February 20, 2007 Revision Date: October 11, 2010 Product: DS-Client (Windows)
Summary
Please read this whole article first before starting the recovery procedure (to an alternate Exchange Server).
Details
In order to perform a successful restore to an alternate location (different server) several conditions must be met: 1. You can perform recovery on individual databases and storage groups or on all databases on a particular server. The recovery server must be installed in a different Active Directory (AD) forest than the original server. The target Exchange server for the restore must be the same version and service pack as the Exchange server that was backed up. 2. The Organization Configuration, the Server Configuration, the Recipient Configuration, the Storage groups and their mailbox databases, and the file locations must be the same as on the original server. By default, the installation of Exchange 2007 server creates the mailbox and public folder stores. These are normally called "Mailbox Database", and "Public Folder Database". Make sure the recovery server has the same Mailbox Database names and Public Folder Database names as the original server. You can rename the stores using "Exchange Management Console": Right-click on each database and select Properties. If the location of the database directories and log file directories is not the same as on the original server, change it here at this stage. Right-click on each store and select "Move Storage Group Path". 3. The recovery server must have an account member of the administrative group that exists on the DS-Client computer. You can either create an account on the recovery server, or you can create an account on the DS-Client computer that matches the name and password of the administrator account. 4. The DS-Client computer must be able to resolve the fully qualified domain name of the recovery server. Since the recovery server will be on a different Domain (different AD), you can set the DS-Client NICs DNS settings to point to the recovery server. (Do not forget to change it back to the original settings once the restore is completed.) 5. Dismount all the stores. Right click on each store and locate the database locations. Using Windows Explorer, delete all the files from these directories. In step 2, you made the location of the database and logs the same; if you have AD users with mailboxes, you may have to delete these mailboxes. Using "Exchange Management Console" under Recipient Configuration right click on the users, and select Remove. Delete all logs using Windows Explorer. Mount all the stores. Ignore the warning for the missing database files and click "Yes" on it. If you get any errors mounting the databases, resolve them before going further. Right click on each mailbox database or public folder database, select "Properties" and click on the "General" tab. Select "This database can be overwritten by a restore" checkbox.

Confidential.
6. Once the above conditions are met, you can start the restore from DS-User. In the restore wizard, change the location from "Original location" to "Alternate location", and click on [>>]. Browse and select the recovery server. Check "Ask for network credentials". Once you have selected the server, double click on it or click on the "Select" button. You will be prompted to type a user name and a password. Use the same one from step 3 above. Keep all the rest of the settings unchanged and click "Finish". Note: If you get errors during the restore, it is likely that some of the conditions (1 to 5 above) were not met. Once the restore is completed without errors you can perform a mailbox recovery if you want.
Mailbox Recovery
The mailbox recovery involves the following steps: 1. Create an Active Directory user account, but do not mailbox-enable the user account. None of the naming for the account needs to match the account that was previously linked to the mailbox. 2. Using Exchange Management Shell, connect the mailbox database you want to recover to the user account that you just created in AD.
See Also
Backup / Restore of Microsoft Exchange Server on page 553 Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery) on page 687


Confidential.
Restoring Microsoft Exchange 2007

Creation Date: February 02, 2008 Revision Date: October 11, 2010 Product: DS-Client (Windows)
Summary
There are two restore scenarios: Restoring WITHOUT a Recovery Storage Group on page 691 Restoring WITH a Recovery Storage Group on page 691
Restoring WITHOUT a Recovery Storage Group

If no Recovery Storage Group currently exists on the MS Exchange 2007 Server: 1. From the Exchange Management Console: Enable the option "this database can be overwritten by a restore" for the target restore database. 2. From DS-User: Open the restore wizard for the intended Exchange Server backup set. 3. Select the option "restore to original location" and any other desired options, then start and complete the restore.
Restoring WITH a Recovery Storage Group

If a Recovery Storage Group currently exists on the MS Exchange 2007 Server: 1. From the Exchange Management Console > Toolbox > Database Recovery Management > Manage Recovery Storage Group: Make sure the Recovery Storage Group has the exact name "Recovery Storage Group" on the target Exchange Server. Add the database you intend to restore to the Recovery Storage Group, then set it to allow overwrites. 2. From DS-User: Open the restore wizard for the intended Exchange Server backup set. 3. When you reach the "Select database restore location" screen, a pop-up message appears:
"Recovery Storage Group was found on target Exchange Server. The selected Exchange Database will be restored to Recovery Storage Group."
This confirms the restore location. Note: If you do not get this message, verify if the Remote Registry Service is stopped. If it is, restart the Remote Registry Service and retry the restore at which time the pop-up message will appear. You must get this pop-up message before proceeding. Proceed with the restore. 4. Mount the restored database in the Recovery Storage Group. 5. From Exchange Management Console > Toolbox > Database Recovery Management: Use the merge option that is available.


Confidential.
See Also
Backup / Restore of Microsoft Exchange Server on page 553 Alternate Location Restore of Microsoft Exchange Server 2000 / 2003 (mailbox recovery) on page 687


Confidential.
Bare Metal Restore of Windows (ALL VERSIONS)

Creation Date: February 11, 2003 Revision Date: May 25, 2010 Product: DS-Client
Summary
Bare Metal Restore is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade. You must have backed up the machines System State and Services Database. When you restore the System State, Services Database and Operating System files, everything must be selected and restored in one step (at the same time) because immediately afterwards a reboot is required. Microsoft recommends using the same hardware for the destination machine. You can restore Windows (2000 / 2003 / XP / 2008 / VISTA) machines to different hardware. Restoring a Windows NT4 machine to different hardware is not possible (unless some initial preparations are made). However, if the differences are minor (e.g. different SCSI controller, NIC) the restore may be successful. Switching between different computer types (ACPI to standard computer type and vice versa) is not allowed. For more information you can check Microsofts knowledge base article number 237556.
1. Determine your computer type:

Before starting the restore you can check your computer type. Here is how you can determine your computer type. Click Start, point to Settings, click Control Panel, and then double click System. Click the Hardware tab, and then click Device Manager to view what is listed under the computer branch. Here are the descriptions of the computer types and the associated hal.dll: ACPI Multiprocessor PC halmacpi.dll ACPI Uniprocessor PC halaacpi.dll Advanced Configuration and Power Interface (ACPI) PC halacpi.dll MPS Multiprocessor PC halmps.dll MPS Uniprocessor PC halapic.dll Standard PC hal.dll Compaq SystemPro Multiprocessor or 100% Compatible halsp.dll There are other types available but that would require Hardware vendor specific installation (involving customized hal.dll).
2. Restoring from one computer type to another:

In some cases it is necessary to perform bare metal restore to a machine of different type. In this case after successful restore, after the reboot you will not be able to start your machine. Regardless what backup software you are using the result would be the same your computer would not start properly or at all. Asigra Cloud Backup software has a solution for this problem: DS-Client will automatically save some critical files in order to preserve them. These will be saved with an extra extension, in the format *.asigra-date-time. The files are hal.dll, ntoskrnl.exe, ntkrnlpa.exe, kernel32.dll, ntdll.dll, win32k.sys, winsrv.dll, setup.log (in \WINNT\repair directory), and boot.ini.

Confidential.
After the restore is finished, you are prompted to reboot the target computer. Do so. If your computer boots normally, no intervention is required. If your computer does not boot, or crashes, you have to follow the steps outlined below: Reboot the computer from the Windows installation CD, and start a repair process using the recovery console. Once you have the command prompt, change to the system32 directory (by typing cd system32), and type dir *.*.asigra* You should see the 7 saved files. Copy each one of them to their original name. For example if you have hal.dll.asigra-022403-0800, you should type copy hal.dll.asigra-022403-0800 hal.dll. Confirm the overwrite and continue with the rest of the files. Type cd dllcache. Type dir *.*.asigra*. You may see 2 more files. Copy them to their original names. Change to the root of C:\ drive by typing cd \ Type dir *.*.asigra*. You will see one file. Copy it to the original name (boot.ini). Change to C:\WINNT\repair by typing cd \winnt\repair. If your %SystemRoot% is located on a different drive or has a different name, change to the proper location. Type dir *.*.asigra*. You will see one file. Copy it to the original name (setup.log). You will need this file in case you need to perform repair. After successfully copying all the files type exit, which would reboot the machine. Boot normally, and your machine should be up and running.
There would be a rebuild of the plug and play database, and you may be prompted to provide drivers for the new hardware found. Follow the instructions on the screen. When prompted to reboot, select NO and finish installing all drivers. Set the TCP/IP details for your network adapter(s). Now you have to fix your computer type. If you did not check the computer type of the destination machine (the one that you are restoring to), you can find out the type by checking the properties of the hal.dll. Open your Windows explorer and go to %SystemRoot%\system32 (%SystemRoot% is usually located in C:\WINNT). Locate the file hal.dll with the extra asigra extension. It could be something like hal.dll.asigra-022403-0800. Right click on it and select properties. Click on the "Version" tab, and from "Item name" select "Internal name". In the "Value" field you would see the original file name. In step 1 above there is a description for each computer type and its corresponding hal.dll. Now you have to change your computer type to the right one (if it is not already so). Click Start, point to Settings, click Control Panel, and then double click System. Click the Hardware tab, and then click Device Manager to view what is listed under the computer branch. Right click on the computer type, select Properties, and select "Driver" tab. Click on "Update driver" button. Click on "Display a list of the known drivers for this device so that I can choose a specific driver" radio button and click "Next". Select the right model for your computer (the one that you discovered by checking the original hal.dll properties) and click "Next". Finish and when prompted to reboot do so.
3. Restoring Active Directory in a multiple server tree.

Active directory is part of the System State and can be restored only as a System State restore. System State would restore the registry as well. You can perform 2 types of AD restore normal and authoritative. The AD objects restored through normal restore, would be overwritten by the AD replication. The restored objects would have their original "update sequence number". These USNs are used by the replication process to detect and propagate AD changes among the servers in the tree. Because of this the restored data would look old to the AD replication and the data

Confidential.
would never get replicated. In fact the replication process would overwrite it. When is the normal (nonauthoritative) restore useful? It is good for single server trees, or when you want to restore the registry, but not to overwrite the Active Directory. Microsoft has a default tombstone lifetime (DTL) value in an Active Directory forest which defines the number of days that a domain controller preserves knowledge of deleted objects. This value also defines the useful life of a system state backup that is used for disaster recovery or installation from backup media. Active Directory protects itself from restoring data that is older than the tombstone lifetime by disallowing the restore. The tombstone lifetime is stored in the tombstoneLifetime attribute of the object CN=Directory Service, CN=Windows NT, CN=Services, CN-Configuration, DC=ForestRootDomain. In a forest that is created on a domain controller that is running Windows Server 2003 without Service Pack 1 (SP1), the default tombstone lifetime is 60 days. In a forest that is created on a domain controller that is running Windows Server 2003 with SP1, Windows Server 2003 with Service Pack 2 (SP2), or Windows Server 2003 R2 or Windows 2008, the default tombstone lifetime is 180 days. Because the tombstone lifetime can be changed administratively, do not assume the default value. Be sure that you are aware of the tombstone lifetime that is in effect in your forest. For more information on this topic, refer to the following Microsoft Knowledge Base articles: http://support.microsoft.com/kb/198793 http://support.microsoft.com/kb/216993 However in case you need to restore an older version of the Active Directory, you have to perform an authoritative restore. Below is a description of each restore type: Authoritative restore - Select "Authoritative restore" in the last screen of the Restore Wizard. This will perform authoritative restore of both AD and FRS. The following list of requirements must be met before you perform an authoritative FRS restore: a) The FRS service must be disabled on all downstream partners (direct and transitive). b) Events 13553 and 13516 have been logged in the FRS event log. c) The computer that is configured for the authoritative restore is configured to be authoritative for all the data. d) All other partners in the replica set must be reinitialized with a non-authoritative restore. To reinitialize the partners with a non-authoritative restore, stop the FRS service, configure the BurFlags registry key, and then restart the FRS service. To do so: Click Start, and then click Run. In the Open box, type cmd and then press ENTER. In the Command box, type net stop ntfrs. Click Start, and then click Run. In the Open box, type regedt32 and then press ENTER. Locate the following subkey in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Param eters\Backup/Restore\Process at Startup In the right pane, double click BurFlags. In the Edit DWORD Value dialog box, type D2 and then click OK. Quit Registry Editor. Perform this on every partner. After rebooting the machine you just restored, start the FRS service on all the partners by typing "net start ntfrs" in the command box. They will synchronize from the restored machine. Normal restore - default - "Authoritative restore" is NOT selected. This will perform nonauthoritative restore for both Active Directory and NTFRS.


Confidential.
You can still perform Non-authoritative restore with DS-Client and then manually run ntdsutil. However this would not work if you are performing bare metal restore where the destination for restore doesn't have AD. If this is the case, let DS-Client perform authoritative restore. DS-Client is running several activities that you can not perform when running manually ntdsutil. Note: After successful restore you should reboot the machine. Once the machine is restarted the plug and play database is reinitialized and most probably you will be prompted for a reboot. Please do not reboot immediately, wait and make sure the Active directory and FRS are synchronized.
Please note that replication may take some time before the restored data would be propagated. If you are testing authoritative restore please note that objects added to the AD after the backup, would not be removed from AD after the authoritative restore. For more information see Microsofts knowledge base article 216243.
4. Restoring Active Directory on a server that is not the PDC when the PDC is missing.
There are some scenarios when you have to restore AD on a domain controller when the PDC is missing. In this case there are several steps that should be performed in order to get the AD in 100% running condition. If the destination machine is a domain controller already, you have to boot into Directory Services Restore Mode. If the destination machine is a stand-alone Windows 2000/2003 computer you can start the restore immediately. Select "Authoritative restore" in the last screen of the Restore Wizard. This will perform authoritative restore of both AD and FRS. After successful restore of the System State reboot the computer when prompted. Please note that you may have to perform the steps outlined above in case you are restoring to different computer type. There are a few articles from Microsoft describing the whole process: 216498 - HOW TO: Remove Data in Active Directory After an Unsuccessful Domain Controller Demotion 248410 - Error Message: The Account-Identifier Allocator Failed to Initialize Properly 234790 - HOW TO: Find Servers That Hold Flexible Single Master Operations Roles 223787 - Flexible Single Master Operation Transfer and Seizure Process Outlined below is the whole process described step by step. 4.1. Login to the restored machine (after the normal reboot) and start a command prompt. Start ntdsutil: Type "domain management" Type "connections" Type "connect to server ServerName" (where ServerName is your current computer name) Type "quit" Type "select operation target" Type "list roles for connected server" You should get information about what roles where associated with the server. Type "list sites" and note the number for the site you are dealing with Type "select site #" (where # is your site number. e.g. 0, 1, ...) Type "list domains in site" and note the domain number

Confidential.
Type "select domain #" (where # is your domain number. e.g. 0, 1, ...) Type "list servers in site" and note the number for the missing PDC Type "select server #" (where # is your server number. e.g. 0, 1, ...) Type "list naming contexts" and note the number for the CN=Configuration Type "select naming context #" (where # is your naming context number. e.g. 0, 1, ...) Type "quit" Type "quit" Type "roles" and you will be at the "fsmo maintenance:" prompt.
Now you must "seize" all 5 rows. ntdsutil will attempt to "safe transfer" the roles, but the transfer will fail since the PDC is missing. Just ignore the errors, because seizure will succeed: Type "seize domain naming master" Click "Yes" at the pop up message Type "seize infrastructure master" Click "Yes" at the pop up message Type "seize PDC" Click "Yes" at the pop up message Type "seize RID master" Click "Yes" at message prompting you to synchronize and "Yes' to confirm the operation Type "seize schema master" Type "quit" Type "quit" to exit ntdsutil 4.2. Now you have to delete all references to the missing server. This could be accomplished using "ADSI edit". This utility is free and is located on the Windows 2000 Server installation CD. It is in \support\tools. Just install the tools. Start ADSI Edit. If you launch ADSI edit immediately after logon, you may receive an error that the domain does not exist. Wait a minute or so and try again. In "Domain NC..." folder, expand until you reach "OU=Domain Controllers". Locate the missing server and delete it. Redo the delete if you get an error or partial delete. In "Configuration Container...", expand until you reach CN=Sites, CN=SiteName - CN=Servers. Locate the missing server and delete it. The last step is to set the Global catalog. In "Active Directory Sites and Services" expand the site all the way down until you reached NTDS settings for the server that you restored. Right click on "NTDS Settings" select "Properties", check "Global Catalog", click "Apply", and close this dialog box. 4.3. Now you are ready to reboot. Reboot the server. 4.4. Examine all the logs for any errors. You should not have any errors. If this is not the case you may have incompatible hardware or device drivers. Usually the error would give you an indication what the problem is and you must be able to solve them. 4.5. Your server is now ready. Note: If there are no other domain controllers to synchronize with, you will have problems. For an explanation of how to fix this, refer to the next paragraph 5 (Restoring Active Directory from a multi server to a single server environment, or when the rest of the domain controllers are missing).


Confidential.
5. Restoring Active Directory from a multi server to a single server environment, or when the rest of the domain controllers are missing:
You will have SAM errors if other domain controllers are missing. If you do not plan to ever start the other controllers, then you should remove them from Active Directory. Use ADSI Edit as explained in step 4 above. From "Active Directory Sites and Services" delete "Connection" from NTDS Settings. After Service Pack 3, the FSMO role holder would not assume its FSMO role unless it had successfully completed at least one sync. Microsoft changed this in order to avoid multiple FSMO owners in a domain, and to prevent the Domain Controller from issuing duplicate RIDs. As described in the previous steps if you seize the RID Master role it will not become authoritative until it synchronizes with another DC. During disaster recovery where you restore only one domain controller from backup, or when you remove domain controllers from AD, you may get "The account-identifier allocator failed to initialize properly..." errors in the System log. The error would be from source SAM and Event ID 16650. Dcdiag may report problems with RID Manager or corrupted data. There are 2 solutions: a) You can restore another domain controller, or b) You can delete the replication links In case you want to keep only one domain controller, you have to delete the replication links, otherwise the domain controller is not fully operational. Here are the instructions for deleting the replication links: 1. You need to use the repadmin tool. It is part of the "Windows 2000 Support tools". The installation of the tools is located in \SUPPORT\TOOLS on the Windows 2000 CD. 2. Open a command prompt and type "repadmin /showreps /v" 3. You need to find out the "guid-based-dns-name of replica partner", which is displayed after "Address:" of the deleted partner. 4. Here is an extract from repadmin:
-----------------------------------C:\>repadmin /showreps /v Default-First-Site-Name\SPEEDYNT4 DSA Options : IS_GC objectGuid : a089478f-cffb-409f-b74b-addb83a6e93e invocationID: a089478f-cffb-409f-b74b-addb83a6e93e ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=spdnt4,DC=local Default-First-Site-Name\TR1 DEL:b91cd853-6af0-4c3a-9586-b5dcc8f489f7 (deleted DSA) via RPC objectGuid: a48650dc-8ed0-4363-8c25-b41553f9248d Address: a48650dc-8ed0-4363-8c25-b41553f9248d._msdcs.spdnt4.local ntdsDsa invocationId: 8994f8c1-f71e-454c-ad3a-17b119621381 WRITEABLE SYNC_ON_STARTUP DO_SCHEDULED_SYNCS USNs: 3518/OU, 3518/PU ------------------------------------
5. In the example above, the FQDN is spdnt4.local and the "guid-based-dns-name of replica partner" is "a48650dc-8ed0-4363-8c25-b41553f9248d._msdcs.spdnt4.local" 6. The restored server is called SPEEDYNT4 and the deleted partner - TR1.

Confidential.
7. Now you can delete the replicas. The syntax is:

repadmin /delete <naming context> <restored server name> <guid-based-dnsname of replica partner> /localonly
8. <naming context> would be for the Schema, Configuration and Domain. 9. In our example to delete the links for the schema we would type:
repadmin /delete CN=Schema,CN=Configuration,DC=spdnt4,DC=local speedynt4.spdnt4.local a48650dc-8ed0-4363-8c25b41553f9248d._msdcs.spdnt4.local /localonly
10. To delete the links for Configuration we would type:

repadmin /delete CN=Configuration,DC=spdnt4,DC=local speedynt4.spdnt4.local a48650dc-8ed0-4363-8c25b41553f9248d._msdcs.spdnt4.local /localonly
11. To delete the links for Domain we would type:

repadmin /delete DC=spdnt4,DC=local speedynt4.spdnt4.local a48650dc-8ed04363-8c25-b41553f9248d._msdcs.spdnt4.local /localonly
12. You must reboot the server after deleting all the replication links. 13. Check the System Log after the reboot to make sure there are no errors from source SAM.
6. Common mistakes:
Slow clients logins Misconfigured DNS, DHCP If the missing server is your PDC, and also your main DNS and DHCP server, your client computers may experience slow logins or errors when trying to login to the domain. If you are using fixed IP addresses, make sure the clients DNS settings are correct. Check your DHCP server for proper settings.
7. Troubleshooting:
Problem: After performing BMR of a Windows machine, the computer fails to start with the following message:
"Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware."
Reason:
The computer fails to boot because of a different system disk configuration between the original backed up computer and the target restore machine.
Solutions: 1. Perform an alternate restore of only the boot.ini from the Windows BMR backup set. Compare this file with the boot.ini of a freshly prepared target restore machine. If they are different, save a copy of the target restore machines boot.ini (e.g. boot.ini.original), perform the BMR, then before restarting replace the restored boot.ini with the (i.e. boot.ini.original). 2. Restart the computer. If it still fails to start, perform the file renaming steps of the 7 automatically saved files described in this Knowledge Base Articles section 2. Restoring from one computer type to another: on page 693.


Confidential.
See also
Backing up Windows for Bare Metal Restore (BMR) on page 534. Bare Metal Restore of Windows XP on page 701. Important Notes for Bare Metal Restore on page 707.


Confidential.
Bare Metal Restore of Windows XP

Creation Date: September 17, 2004 Revision Date: November 05, 2007 Product: DS-Client
Summary
Bare Metal Restore is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade.
Details
The Windows XP Service Pack 2 disables some services, and removes or replaces some others. If performing a Bare Metal Restore on top of a basic Windows XP installation, those services disabled by XP Service Pack 2 may be enabled and the ones removed by the same Service Pack may still be found after the restore is completed. We have an open case with Microsoft to resolve this issue. Until we provide a fix, even though the conflicts described above can be manually resolved, we recommend applying the following workaround: When a Bare Metal Restore is needed, install first Windows XP on the destination machine, apply the Windows XP Service Pack 2 and then start the full restore.
See also
Backing up Windows for Bare Metal Restore (BMR) on page 534. Important Notes for Bare Metal Restore on page 707.


Confidential.
Bare Metal Restore of SBS 2008

Creation Date: January 29, 2010 Revision Date: November 01, 2010 Product: DS-Client
Summary
Bare Metal Restore (BMR) is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade.
Details
The Windows SBS 2008 has the following additional requirements in order to perform BMR: 1. You must have an existing, backed up File System Backup Set of the SBS machine you want to restore (including backup of C$, system state and services database). For more information, see the Knowledge Base Article Backing up Windows for Bare Metal Restore (BMR) on page 534. 2. Install Windows SBS 2008 on the target restore machine (where the BMR will be performed). 3. Restart the target machine with Directory Services Restore Mode (F8). 4. Login as a Local Administrator. 5. Uncheck User Account Control (UAC) from Control Panel > User Accounts. 6. Turn off the Firewall. 7. Go through the Windows services list and make sure only the following seventy-three (73) services are started (i.e. stop any other services that are running): Application Experience Application Host Helper Service Application Information Background Intelligent Transfer Service Base Filtering Engine Block Level Backup Engine Service Certificate Propagation COM+Event System Crytographic Services DCOM Server Process Launcher Desktop Window Manager Session Manager DFS Namespace DFS Replication DHCP Client Diagnostic Policy Service Diagnostic System Host Distributed Transaction Coordinator DNS Client File Server Resource Manager FSCController FSCMonitor FSCStatisticsService FSEMailPickup

Confidential.
Group Policy Client Human Interface Device Access IKE and AuthIP IPsec Keying Modules IP Helper IPsec Policy Agent KtmRm for Distributed Transaction Coordinator Microsoft Exchange Active Directory Topology Service Microsoft Exchange Transport Netlogon Network Connections Network List Service Network Location Awareness Network Policy Server Network Store Interface Service Plug and Play Print Spooler Remote Access Connection Manager Remote Procedure Call (RPC) Remote Registry RPC/HTTP Load Balancing Service Secondary logon Secure Socket Tunneling Protocol Service Security Accounts Manager Server Server Infrastructure License Service Shell Hardware Detection SQL Server VSS Writer SSDP Discovery System Event Notification Service Task scheduler TCP/IP NetBIOS Helper Telephony Terminal Services Terminal Service Configuration Terminal Service UserMode Port Redirector Update Services UPnP Device Host User Profile Service Virtual Disk Windows Error Reporting Service Windows Event Log Windows Management Instrumentation Windows Process Activation Service Windows Remote Management (WS-Management) Windows SBS manager Windows SharePoint Services VSS Writer Windows Time Windows Update WinHTTP Web Proxy Auto-Discovery Service Workstation
Confidential.

8. Perform the BMR to the target machine. 9. When the restore process has finished, restart the target machine.
See also


Confidential.
Bare Metal Restore of Windows 2008 R2

Summary
Bare Metal Restore is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade.
Details
Starting from Windows 2008, Microsofts Operating System installation includes a System Reserved Partition (usually 100MB): See System Reserved Partition (Windows 2008 & up) on page 535.
See also


Confidential.
Bare Metal Restore of SBS 2011 Standard

Creation Date: December 07, 2011 Revision Date: December 07, 2011 Product: DS-Client
Summary
Bare Metal Restore (BMR) is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade.
Details
The Windows SBS 2011 (Standard) has the following additional requirements in order to perform BMR: The target machine you are restoring to must be rebooted in Directory Services Restore Mode. This starts the Windows Domain Controller running Active Directory, which allows the Directory Services to be restored.
See also


Confidential.
Important Notes for Bare Metal Restore

Creation Date: November 05, 2007 Revision Date: January 29, 2010 Product: DS-Client (Windows)
Summary
Bare Metal Restore is a restore process when the whole machine is being restored. Usually this type of restore is performed after a complete hardware failure or hardware upgrade. This article explains the following: No Bare Metal Restore of 32-bit Operating System to 64-bit is possible on page 707.
No Bare Metal Restore of 32-bit Operating System to 64-bit is possible

You cannot perform a Bare Metal Restore of a 32-bit Operating System (OS) to a 64-bit OS. This is because there are significant differences between 32-bit and 64-bit operating systems, even if they are from the same version of Microsoft Windows. For example, the 64-bit Windows 2003 OS contains both the 64-bit compiled modules and most of the 32-bit compiled modules for backwards-compatibility. Microsoft put a great deal of effort to have 32-bit applications run transparently on the 64-bit OS. Those 32-bit modules are located under a special folder in the 64-bit OS (not under the regular one you would find on a 32-bit OS). Restoring the 32-bit files over the regular location would overwrite 64-bit modules and render the system inoperable. Similarly, the 64-bit Windows 2003 registry database contains both 64-bit specific and 32-bit specific keys. Therefore a registry backup from a 32-bit OS would be missing the 64-bit specific keys, and restoring to a 64-bit OS would overwrite the existing 64-bit keys with 32-bit ones, rendering the computer un-bootable. Moreover, the 64-bit OS cannot use 32-bit drivers at all. The list of differences goes on and on, therefore you cannot bare metal restore a 32-bit OS over a 64-bit one. The only option is to perform bare metal restore of a 32-bit OS over a 32-bit OS, or to perform bare metal restore of a 64-bit OS to a 64-bit OS.
See also
Backing up Windows for Bare Metal Restore (BMR) on page 534. Bare Metal Restore of Windows (ALL VERSIONS) on page 693. Bare Metal Restore of Windows XP on page 701. Bare Metal Restore of SBS 2008 on page 702.


Confidential.
Restoring Files from a specific time

Creation Date: April 30, 1997 Revision Date: April 11, 2002 Product: DS-Client
Summary
In some cases, you may wish to restore an older version of a backed up file. (e.g. If you discover that files after a certain date are corrupted, or if you wish to restore a project that requires files from the same backup session. The number of generation online depends on the backup set option settings, as well as the number of backups performed and the frequency of changes to the backup file.)
Details
The following dialogs are accessible from the Restore Wizard. (The path to get to the dialog is shown in parentheses beneath the dialog title.) Select by Generation Restore menu > Restore Now > Show Files > File Info Highlight the desired generation of the file from the list and click on Select. The Restore Wizard returns to the Select Files and Directories Tab, with your selection market with a checkbox. The directory list refreshes automatically to show files backed up at the time of the selected generation.
Select by Backup Time Restore menu > Restore Now > Advanced
Note
1. When you select a specific file generation, the display is changed to reflect only the backed up data from that selected generation.


Confidential.
Restoring MS SQL Server Transaction Logs

Summary
Note: The only time when this method is better than restoring from a full DS-Client backup is if there is a very specific transaction point you want to restore to (between two full backup sessions).
Asigra Cloud Backup DS-Clients special Microsoft SQL Server backup set type always performs a full database dump of the SQL Server, triggered by the DS-Client. After the first backup of a SQL database, the subsequent backups send incremental forever. Currently, the DS-Client does not support a separate backup of a databases transaction log. If you want to back up the transaction log, you must backup the corresponding database with the Backup Transaction Log backup item option selected (MS SQL 2005 and higher). The value of separate transaction logs is that they can be restored as separate dump files (to alternate location). The Microsoft SQL Server Enterprise Manager / SQL Server Management Studio tools can use these transaction log dumps to roll forward a restored database to a specific point-in-time (covered by the transaction log dump). To select a backed up transaction log from the Restore Wizard: 1. Open the Advanced Option screen and select Latest generation of all data. 2. Click Show Files.
3. If a transaction log was backed up, it will appear with the *.log extension. Select it and continue with the Restore Wizard.


Confidential.
Details
The following general steps are required if you want to restore transaction logs (and roll-up a database). 1. Restore the database as a dump file with the Windows DS-Client. 2. Using the physical file restored in step 1, restore it in the SQL Server using third party tools SQL Server Enterprise Manager / SQL Server Management Studio: Leave the DB in a non-operational state so that transaction logs can be rolled forward. 3. Restore additional transaction logs (since the backup restored in step 1) with the DSClient as dump files. 4. Use SQL Server Enterprise Manager / SQL Server Management Studio to roll-up (in sequence) the required transaction logs up to the point in time you want. 5. Set database in operational mode. 6. You can now start using the DB. Repeat steps 1-5 for additional databases you require.
See also
MS SQL Server Database Backups on page 116 Backing up Windows for Bare Metal Restore (BMR) on page 534 Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560


Confidential.
Restoring Locked Files on Windows

Creation Date: July 28, 1997 Revision Date: February 14, 2011 Product: DS-Client (Windows)
Summary
The DS-Client software can be instructed to restore locked files when the destination server is a Windows computer. This feature is vital when restoring operating system files that are locked and cannot be restored in any other way (e.g. most of the operating system kernel files).
Procedure to Restore a Locked File

Locked files are restored by registering a replace or remove operation with the operating system, which will occur on the next system boot. On Windows, this information is stored in the registry. There are two ways the locked file can be replaced with the restored file:
Locked File handling option Explanation Renames the (original) locked file (to 'dsrN.tmp', where N is system generated number), then restores to the original name and instructs operating system to remove the temporary file on the next system boot. This option allows you to restore files that must be loaded by the operating system before the process of replacing registered files takes place. The drawback of this method is the computer may become unbootable if the process of renaming and registering locked files is interrupted or not completed successfully. Restore locked file with a temporary name ('dsbN.tmp', where N is a system generated number) and instruct the operating system to replace the original with the temporary file on the next system boot.
Rename
Dont Rename
Restoring Locked Files to a FAT Partition

On a FAT partition, you should consider the following behavior when restoring locked files: 1. It is strongly recommended that you use the (default) Save method to restore. 2. A restore with the Use buffer or Fast methods selected might be able to immediately overwrite some locked files. In some cases (e.g. databases, services), these locked files will be overwritten AGAIN when the parent application is closed. Note: It is safer to restore WITHOUT the Use buffer or Fast methods (Select restore options screen).


Confidential.
Special Warning Regarding Restoring Locked Files with the Rename Option
When using the Rename Option, you must ensure a complete and successful restore session. 1. Open the Event Log for that restore session 2. If there is at least one Event # 32 "The process cannot access the file because it is being used by another process", then a successful restore MUST end with the message "N locked files were registered for restore". 3. If you do not see this message, do not reboot the computer. Re-run the restore until you see that message. 4. Once you have had a successful restore session, you must reboot your computer to complete the restore process.


Confidential.
Restoring NetWare Servers (5.1 and higher with NDS 8)

Creation Date: June 14, 2001 Revision Date: January 10, 2003 Product: DS-Client
Summary
In order to perform a bare metal restore of a NetWare 5.x server (NDS 8), the following requirements must be met.
Details
If you did not use DOSFAT.NSS (or any other tools) to backup the DOS partition, the latest support pack must be installed prior to restore. To execute a full NetWare server restore after hardware failure you must: 1. Install the NetWare server. Install the NetWare licenses. In NetWare 5.1 the "admin" account does not have rights to backup the licenses. Unless you granted these rights manually, the backup of NDS will not contain the licenses. However Novell does this on purpose. 2. During the installation, you must provide the same NDS tree, and the same server context, otherwise the DS-Client will not be able to restore (DS-Client cannot perform an alternate restore of NDS). 3. Apply the latest NetWare support pack. This step is necessary because NDS will fail to load if it is not in synch with the rest of the modules in NetWare 5.x. If you backed up the DOS partition, you can restore it, and in this case there's no need to apply the support pack. There are two scenarios when you perform a full restore: Scenario A - NDS tree with a single server. 1. Restore only NDS in a single session. This step is necessary because the NDS object(s) must exist prior to applying trustee assignments. 2. Add Name Space (if any). 3. Restore the file system in the next session, and then reboot the server (see Note 3). Scenario B - NDS tree with multiple servers. 1. Restore only NDS on the master replica in a single session. 2. Add Name Space (if any). 3. Restore the file system on the master replica in the next session (see Note 3). 4. Install the rest of the servers. When asked for the NDS tree name - select the existing one and connect to the master replica. 5. Add Name Space (if any). 6. Restore the file system on the rest of the servers (see Note 3). Note: Novell claims that for multiple server environments, you do not need to restore the NDS. The restored server will be able to pull NDS updates from the rest of the servers. However, in mass disasters (or when emulating a mass disaster) you may need to perform a full NDS restore to all of the servers.


Confidential.
Certificate Server
At the end of NDS restore you must perform some extra steps because of the inability to restore the certificate server. According to Novell there is no way of backing up and restoring the certificate server. This is done on purpose. To get around this problem you have to remove the certificate server first and then to reinstall it: 1. After successful restore of NDS you must delete the following items using ConsoleOne: All certificates the SAS object everything in the Security container (You may want to check TID 10056795 from http://support.novell.com - especially if you have a Multi-Server environment). 2. Run "NREPAIR.NLM". This utility can be downloaded from http://support.novell.com. This utility is the only way to remove the certificate server and properly initialize NICI: Follow the prompts from the screen After successful removal, mount the Certificate Server Installation CD Install the certificate server through the GUI 3. After steps 1 & 2 are complete, your server will have the proper NDS. The only exception would be any previously used certificates that are no longer valid. As it was mentioned earlier this is done on purpose. You can test the functionality of the certificate server by trying to create a new server key. Note: From now on the version of NDS that you restored will no longer be good since the certificate server and all the certificates are different. (i.e. you should backup NDS immediately after completing the restore.) 4. After applying all the necessary steps you can start restoring the file systems. You MUST unselect from SYS volume \SYSTEM\NICI subdirectory because it contains information related to the previous version of the certificate server and NICI. If you fail to remove this directory from the restore process, you will have to clean the certificates again and run NREPAIR, and then reinstall the certificate server.
Notes
1. When doing a full file system restore you may encounter some errors. They will be recorded in the DS-Client Logs. Once the restore is completed, check the Activity and Event Logs. If there were any errors, perform a restore for each of the files that had errors. This is a known problem and ASIGRA is working with Novell to resolve it. 2. If you had more than one NDS partition, you must reconfigure it manually. 3. If you encounter "The network name cannot be found" when trying to restore, this means the NetWare SERVER has been rebooted too many times. This has caused the NetWare CLIENT on the DS-Client computer to cache too much data. This can be fixed by either performing a "login" to a NetWare server, or rebooting the DS-Client computer. 4. After restoring NDS, CIFS may not function. This limitation is not only exhibited by DS-Client, but also SMS Backup. In order to fix CIFS, follow the directions described in Novell Support Knowledge base - TID 10071043. Basically all you have to do is recreate the login sequence.


Confidential.
Troubleshooting: Full Server (file system and registry) restores

Creation Date: March 25, 1999 Revision Date: February 01, 2010 Product: DS-Client
Summary
Because of the way Microsoft (and most other software providers) install their programs, a problem may occur if a computer's file system and Registry are restored.
Details
When Microsoft (and most other software providers') software is installed on a computer, the Windows 8.3 filename is used in the Registry. Some programs make associations with the file extensions, thereby allowing the program to launch automatically when and associated file is double clicked. Windows 8.3 filenames appear with first few characters of the long filename, followed by the tilde (~) and a number (e.g. MICROS~4). This method allows long file names to be limited to eight characters, while remaining unique. The problem is that the Windows 8.3 name is assigned chronologically (i.e. based on the order in which program files were installed on the computer). However, when the DS-Client restores files, the Windows 8.3 name may be different because files can be restored in a different order than they were originally installed. For example, the folder 'Microsoft Image Composer' might have originally had the 8.3 name 'MICROS~2' (since there may be several folders with long folder names, beginning with Microsoft). Upon restoration of the file system, it is possible that the 8.3 name could be something else (e.g. MICROS~5), depending on the order that it was restored to the computer by the DS-Client. If such a problem exists on the restored computer, it will appear when you try to open a file by double clicking on it. You will get a "Program Not Found" error dialog, prompting you to specify the location of the program that will launch the selected file. (For more info see Microsoft Knowledge Base article 240240.)
Resolution
ASIGRA has a solution for this problem that is applied automatically for Windows 2000 and higher. In the "Program Not Found" dialog, simply click the Locate button, and respecify the source program. The exact program name will be listed in the dialog. You can perform a filename search in the event you cannot remember where the source program is located. If the work around does not help, you may have to reinstall the failed program.


Confidential.
Knowledge Base: RECOVERY


Confidential.
Disaster Restores
Creation Date: November 4, 1997 Revision Date: December 6, 2005 Product: DS-Client See Recovering the DS-Client Database on page 718 See Disc/Tape on page 283
Summary
The DS-Client service is designed to perform automated backups to an offsite location. This approach requires an adequate communication link between the DS-Client and the DS-System. If a customer site needs to restore a large amount of data (due to a server crash or other disaster), the communication link between the DS-Client and the DS-System may not allow the restore process to be completed in a reasonable amount of time. In these cases, customers can use the Disc/Tape feature to have the required data written to media and shipped to their physical location. This can be done from the DS-Client, or by their Asigra Cloud Backup service provider.
Performing a Disaster Restore

The steps described here are general and assume that your network is functioning properly. Depending on your situation, you may need to do more things. 1. You need the DS-Client. If the DS-Client computer was destroyed, see Recovering the DS-Client Database on page 718 To reduce your down time, you can ask your Asigra Cloud Backup Service Provider to write the required data to Disc/Tape media (snapshot of latest generation only). This must be done for each backup set you need. (Otherwise, you can perform the Disc/Tape request with DS-User after the DS-Client computer is recovered.) 2. DS-System copies all requested files to Disc/Tape media. 3. Disc/Tape media is shipped to the DS-Clients physical location. 4. The required data is restored from Disc/Tape media attached to the DS-Client (or through the LAN).
Note
1. The data on Disc/Tape media is encrypted.


Confidential.
Recovering the DS-Client Database

Creation Date: March 18, 1999 Revision Date: October 10, 2007 Product: DS-Client
Summary
The DS-Client database contains the settings for backup sets, logs, and schedules. Asigra Cloud Backup has incorporated a DS-Client database recovery feature to speed up recovery if the DS-Client computer is destroyed, or if its database is somehow otherwise destroyed. The Delta database contains delta information for all files. If this database is not recovered, the next backup will force DS-Client to send a new Master file (full file). This will add a considerable amount of backup time to the next backup. If you restore the Delta database as well as the DSClient database, this will add to the time required to Recover (especially if the databases are large). In order to use this feature, your DS-Client must have been configured to backup its own database (see: Setup > Configuration > Parameters Tab - Database Options > DS-Client database backup). In other words, there must be a backed up DS-Client database on the DS-System to recover (this is the default setting). The recovered database will show data up to the time it was last backed up. Note it is quite possible that the recovered database is slightly out of synch with the actual 'up-to-the-last-minute' backups, therefore you should immediately run a Weekly Admin. to synchronize the recovered database with the actual DS-System storage. If you do not have a DS-Client database backup, you will have to recover each backup set on the DS-System individually. However, you will be unable to recover the backup schedules or any of the logs. (See Recovering 'Orphaned' Backup Sets on page 720.)
Recovery Steps
If the DS-Client computer was destroyed, you must: Assemble the hardware required for the replacement DS-Client computer and install the Operating system. If you must replace the database software, make sure you install the same version. Note: It is possible to recover the database from an MS SQL Server 2000 instance to an MS SQL Server 2005 instance, but you cannot recover from 2005 to 2000. However, it is best to recover to the same exact instance version to minimize the chance of problems. You must also recreate the user accounts (including the DS-Client account), and then Reinstall the DS-Client software to the computer. Recover the DS-Client database(s). To recover the DS-Client database(s): 1. Start the DS-Client Service and run DS-User. 2. From the Setup Menu, select System Activities. The System Activities Administration dialog box appears. 3. Click Repair. The Repair DS-Client dialog box appears. 4. Select either "DS-Client database" or "DS-Client & delta database". 5. Click OK. A recovery message appears, instructing you to restart the DS-Client service.


Confidential.
6. Stop and Restart the DS-Client service. The recovered Database will become active upon restart. 7. Run a Weekly Admin. process to ensure that the recovered DS-Client database data is not missing any backup sets. If it is, perform a backup set recovery. (See: Recovering 'Orphaned' Backup Sets on page 720) 8. Follow the steps to Take Ownership of each backup set (see: Change Backup Set Ownership in the DS-User Guide).
Notes
1. If you have reinstalled the Windows operating system on the DS-Client computer being recovered: The Security IDs (SIDs) of the users you create will be different from those in the recovered DS-Client database (even if they are the same name, the SIDs are unique for each instance a user is created). You must change ownership of the backup sets to the new user: See Change Backup Set Ownership on page 198. In the Select User dialog, you will see two users of the same name (because the DS-Client searches by SID). Select the lower one - the current user is closest to the bottom of the list. 2. Do not create any new backup sets before you have recovered the DS-Client's database.


Confidential.
Recovering 'Orphaned' Backup Sets

Creation Date: March 18, 1999 Revision Date: March 14, 2008 Product: DS-Client
Summary
If you encounter the following Event Log errors: "Backup Set not found in Backup Log", it means the Admin process encountered differences when it checked the DS-Client's database against the actual backup data on the DS-System. This means the backup data exists on the DS-System, but the backup set is missing from the DS-Client's database. These 'orphaned' backup sets can still be recovered by having the DS-Client reconstruct the backup set catalogs from the DS-System information. Orphaned backup sets must be recovered individually. However, recovering an orphaned backup set does not recover its configuration information (i.e. Computer Name, Connect As, Backup Schedule...). This information must be re-specified to the DS-Client database by performing the Migration process.
Recovery Steps
Follow these steps to recover a backup set (Perform these steps for each backup set individually): 1. From the Setup Menu, select System Activities > Repair. The Repair DS-Client dialog box appears. Select the Orphaned backup sets radio button. 2. Click OK. The Backup Set Recovery dialog box appears. 3. Select a backup set from the list. (When recovering a backup set, your current login credentials are used to assume ownership of the backup set. This means your current login ID will be the owner of all the recovered sets.) 4. Click OK to begin the process. The Synchronization Window appears as the backup set is synchronized with the DS-System's online storage. 5. Continue for as many backup sets there are to recover (i.e. until the list is empty). 6. Once the backup set is recovered, you may perform restores immediately. (To backup, see the following section on Migration.)
Migration
In order to resume backups, you must re-specify some of the backup set's configuration information (i.e. Network Provider, Computer Name, Connect As, Backup Items, and Backup Schedule information). Do this by Migrating or by manually changing the necessary settings. The easiest method is to migrate the backup set: 1. From the Backup Sets Tab, click on a set to highlight it. 2. Right-click to pop up the options menu. 3. Click on Migrate. The Migrate Backup Set Wizard appears, prompting you to select the new network/share path. 4. Browse through the network/node to specify the new path you want to migrate this backup set. 5. Check the Ask for Network Credentials box if you want to specify the credentials to the new network resource. 5a. If you use the Ask for Network Credentials checkbox, the Enter Network Credentials dialog box appears. Enter the User name, source server (if applicable), and password to connect with the selected network/node.

Confidential.
6. Once connected to the new network/node, the Migrate Backup Set Wizard switches to match the source/destination share. 7. Double Click on the corresponding Destination Cell to show all of the available shares on the selected node. 8. Select the share where the files have been moved and click Next >. 9. The specified backup items in the Selected Files for Backup Section will remain, however the share path will change according to the destination share selected in the previous tab. 10. Make sure that the path of the migrated files is correct. Otherwise, errors will occur. You may add more files, or leave this dialog unchanged. 11. Click Next >, when you are finished changing/specifying backup items. The Backup Item Options tab appears. 12. Select the options, as you would a normal backup set. Depending on which network you have migrated to, you may see more or less backup options than previously available for this backup set. 13. Click Finish to complete the migration. The Backup Sets dialog box returns. If you open to the migrated backup set, you will see any changes to the network, node, and/ or provider.


Confidential.
Restoring the MS SQL Database Server MASTER Database

Creation Date: May 28, 1999 Revision Date: October 12, 2012 Product: DS-Client (Windows)
Summary
If you need to restore an MS SQL Server's MASTER database, you need to perform some additional steps in order to ensure a successful restore. See SQL Server 2000 on page 722. See SQL Server 2005 & up (Full & Express versions) on page 723. Note: This article describes restoring the MS SQL Server MASTER Database for any instance, except the DS-Clients MS SQL database.
SQL Server 2000

1. Use the MS SQL Setup program to rebuild the master database. You must rebuild using the same MS SQL Server version, character set and sort order as the master database dump that will be reloaded. 2. Restart MS SQL Server in single-user mode using the sqlservr command. Stop MS SQL Server if it is already running. From a command prompt, type:
<path_to_executable>\sqlservr [-sinstance_name] -c -m
where
You can find the <path_to_executable> by viewing the Properties for this MS SQL Server Instance in Windows Services Specifies the MS SQL Server Instance Name that you wish to start in single-user mode. When starting an instance of SQL Server, you must use the sqlservr application in the appropriate directory for that instance. For the default instance, run sqlservr from the \MSSQL\Binn directory. For a named instance, run sqlservr from the \MSSQL$instance_name\Binn directory. NOTE: If you are starting a default (un-named) instance, skip this switch (type <path_to_executable>\sqlservr -c -m). Starts MS SQL Server independent of the Windows NT Service Control Manager. Specifies the single-user mode.
-sinstance_name
-c -m
3. Use Asigra Cloud Backup DS-Client to restore the master database directly into the restored instance. Note: When the load of the master database is complete, the server automatically shuts itself down. You can restart the MS SQL Server normally (from Enterprise Manager or SQL Server Service Manager). The SQL Server instance will start in multi-user mode.
4. Restore the msdb database and the rest of the databases, if applicable.


Confidential.
SQL Server 2005 & up (Full & Express versions)

1. Use the MS SQL Setup program to rebuild the master database. You must rebuild using the same MS SQL Server version, character set and sort order as the master database dump that will be reloaded. 2. Stop the SQL Server, if it is running. 3. Open the Registry on the SQL Server computer (use regedt32.exe). For 32-bit instances running on 32-bit Operating Systems & 64-bit instances running on 64-bit Operating Systems: Browse for the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\InstanceNames\SQL
You will find a list of all SQL instances installed on that machine. Locate the name of the Instance you want to start in single-user mode in the Name field. The Data field will contain a map of this Instance on the computer. Browse for the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<DATA VALUE>\MSSQLServer\Parameters
For 32-bit instances running on 64-bit Operating Systems: Browse for the following path:
HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Microsoft SQL Server\SQLServer\InstanceNames\SQL
You will find a list of all SQL instances installed on that machine. Locate the name of the Instance you want to start in single-user mode in the Name field. The Data field will contain a map of this Instance on the computer. Browse for the following path:
HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Microsoft SQL Server\<DATA VALUE>\MSSQLServer\Parameters
4. Add a new registry Value at the end of the list. Give it a Value Name of SQLArgn, where n in an incremental number of 1 over the current maximum. Make the Data Type REG_SZ, and for the string value enter -m. 5. Restart MS SQL Server in single-user mode using the Windows Services regular Start command. 6. Use Asigra Cloud Backup DS-Client to restore the master database directly into the restored instance. When the load of the master database is complete, the server automatically shuts itself down. 7. Delete the registry Value SQLArgn that you added in step 4. Now you can restart the MS SQL Server normally (from Enterprise Manager or SQL Server Service Manager). 8. Restore the msdb database and the rest of the databases, if applicable.
See also
MS SQL Server Database Backups on page 116 Restore MS SQL Server Backups on page 234 MS SQL Server Backup Sets (Alternate Location Restore) on page 266 Backup / Restore of Microsoft SQL Server (ALL VERSIONS) on page 560


Confidential.
Oracle Database Point-In-Time Recovery (DBPITR)

Creation Date: July 30, 2009 Revision Date: July 30, 2009 Product: DS-Client (Linux)
Summary
Starting from version 9.2, Linux DS-Client can perform a Point-In-Time Recovery for an entire Oracle database. Tablespace Point-In-Time recovery (TSPITR) is not supported, however the DSClient can prepare all the datafiles and archived logs in order for users to perform a manual TSPITR, when required. This article describes the steps for Oracle DBPITR on Linux DS-Client: 1. Performing DBPITR within the current database incarnation on page 725 2. Performing DBPITR to a non-current database incarnation on page 731
RMAN DBPITR Overview

RMAN (Oracle Recovery Manager) DBPITR restores the database from backups prior to the target time for recovery, then uses incremental backups and redo to roll the database forward to the target time. You can recover to a System Change Number (SCN), log sequence number, time, or restore point. The prerequisites for database point-in-time recovery are as follows: Your database must be running in ARCHIVELOG mode. You must have backups of all data files from before the target SCN for DBPITR and archived logs for the period between the SCN of the backups and the target SCN. For a full description of command prerequisites and usage notes, refer to the RECOVER entry in the Oracle Database Backup and Recovery Reference documentation. Steps involving DS-User are condensed. It is assumed the user knows how to get to each wizard screen displayed.


Confidential.
1. Performing DBPITR within the current database incarnation

You can perform DBPITR with the current control file or backup control file. During the DBPITR process, you may need to view your database version in Read Only mode. (To open a database in Read Only mode, you would normally use a backed up control file instead of the current control file.) If the DBPITR result is what you expected, then you can open database with the Resetlogs option. When you perform DBPITR with DS-Client, you have two options:
Do not execute RECOVER commands:
This option will not issue the Oracle RECOVER command. You must use RMAN to perform the DBPITR manually. See DBPITR using the Do not execute RECOVER commands option on page 728. This option will automatically recover the database to the target time and opens the database with the Resetlogs option. See DBPITR using the RECOVER DATABASE at ... option on page 726.
RECOVER DATABASE at:
NOTE: If you select both options, the option Do not execute RECOVER commands will override the other and no Recover Database command will be executed.


Confidential.
DBPITR using the RECOVER DATABASE at ... option This option will automatically recover the database to the target time and opens the database with the Resetlogs option. If you have all archived logs needed up to the target recovery time, you just need to restore the control file and all datafiles. 1. Because you are performing DBPITR with a backed up control file, you need to put the database in Nomount state with the following commands:
SQL>Shutdown immediate; SQL>Startup nomount;
2. From the DS-Users Restore Wizard, select the Oracle backup sets Control file and all datafiles.
Make sure that: You choose the correct backup set and generation which belong to the current incarnation. If you do not have all archived logs up to the target recovery time, you must also restore Archived Logfiles.


Confidential.
3. Continue to the Select Restore Options tab of the Restore Wizard.
4. Select the target time: Choose the option RECOVER DATABASE at. Input the target recovery point-in-time at which you want to recover your database. 5. After you click Finish, DS-Client will automatically recover the Oracle database to the target time and then it will open the database with the Resetlogs option.


Confidential.
DBPITR using the Do not execute RECOVER commands option This option will not issue the Oracle RECOVER command. This means the DS-Client will only restore the datafiles and archived logs back to the Oracle server. You must use RMAN to perform the DBPITR manually. 1. Put the database in Nomount state with the following commands:
SQL>Shutdown immediate; SQL>Startup nomount;
2. Select the Control file and all datafiles. The restore selection is the same as DBPITR using the RECOVER DATABASE at ... option on page 726. 3. Continue to the Select Restore Options tab of the Restore Wizard.
4. Select the option Do not execute RECOVER commands. 5. Click Finish. DS-Client will: Replicate the control file Mount the database Restore the database 6. Now you must manually perform DBPITR with Oracles RMAN. Your database will be in Mount state. You must use RMAN to connect to the target database and perform the DBPITR. 7. Perform the following operations within a RUN block:
RMAN>Run{ Set Until Time=TO_DATE(2009-07-09 21:28:00, YYYY-MM-DD HH24:MI:SS); Recover database; }


Confidential.
If you know the specific logseq# or SCN where you want to recover the database, you can use with the RMAN Set Until clause as in the following samples:
RMAN>Run{ Set Until logseq=8; Recover Database; }
OR
RMAN>Run{ Set Until SCN 2325039; Recover database; }
8. Review the recovery results. Open the database in Read Only mode with the following command to check if you are satisfied with the results:
SQL>Alter database open Read Only;
9. If satisfied, you can open the database with the Resetlogs option:
SQL>Alter database open Resetlogs;
If not satisfied, you can repeat the DBPITR procedure to a new target time.
EXAMPLES The following screenshots are RMANs outputs based on Time, Log Sequence Number, and SCN with the Set Until clause:
Screenshot 1: Recover Database until a target Time


Confidential.
Screenshot 2: Recover Database until a target Log Sequence Number
Screenshot 3: Recover Database until a target SCN


Confidential.
2. Performing DBPITR to a non-current database incarnation

Database Incarnation Overview A database incarnation is created whenever you open the database with the RESETLOGS option. After a complete recovery, you can resume normal operations without an OPEN RESETLOGS command. After a DBPITR or recovery with a backed up control file, however, you must open the database with the RESETLOGS option, thereby creating a new incarnation of the database. You may want to bring your database back to a time that is in a non-current incarnation (parent or ancestor incarnation). In this case, you must have: Backups of all datafiles from the specified non-current incarnation before the target SCN for DBPITR, and Archived logs for the period between the SCN of the backup until the target SCN. Recovery Scenario On the current date (July-14-2009), you realized that a table in your database was erroneously updated on July-09-2009 around 9:30 pm. You decide to restore your database to 2 minutes before that update was made. The target time you want to set is July-09-2009 at 9:28 pm. 1. Determine the incarnation at the target restore time: In order to determine which database incarnation was current at the time of the backup, you can use the Oracle List Incarnation command. This allows you to view incarnation history and find the primary key of the incarnation that was current at the target time:
RMAN>List incarnation;
The following output appears:


Confidential.
You can also query v$Database_Incarnation to get the incarnation information:
In this example: The current incarnation is the incarnation with the Key 9, assuming that the current time July-14-2009. The target time will be July-09-2009 21:28:00. Based on the incarnation history, you see that the incarnation with the Key 5 was the current incarnation at the recovery target time. 2. Replicate the control file: Put database in Nomount state:
SQL>Shutdown immediate; SQL>Startup Nomount;


Confidential.
Perform a restore of the control file.
Make sure that you choose the correct backup set and generation which belongs to current incarnation at the recovery target time. If you do not have all archived logs needed up to the recovery target time, you must also restore those archived logs. 3. Reset the database incarnation to the current incarnation at the recovery target time: After Control file is successfully replicated, your database is already in Mount state In this example, you must reset the database incarnation to 5 with the following command:
RMAN>Reset database to incarnation 5;
4. Perform a restore of all the Oracle datafiles.


Confidential.
5. Select the recovery target time.
After you click Finish, DS-Client will automatically recover database to the target time. However, the database is will remain in Mount state (it will not be opened). 6. Review the recovery results. Open the database in Read Only mode with the following command to check if you are satisfied with the results:
SQL>Alter database open Read Only;
7. If satisfied, you can open the database with Resetlogs option.

SQL>Alter database open Resetlogs;
If not satisfied, you can repeat the procedure of DBPITR to a new target time.
See also
Restore Oracle Server Backups on page 240


Confidential.
DS-User F1 Help for GUI (Context-Sensitive)
F1 Help provides descriptions for the contents of the different GUI screens of the Asigra Cloud Backup DS-User. It differs from the User Guide sections, which provide step-by-step instructions.


Confidential.
F1 (Context-Sensitive) Help
This section contains the alphabetical list of F1 Help screens for the Asigra Cloud Backup DSUser.
3D View Setting
(Win32 Only) This screen controls all of the 3-dimensional view settings for the Load Summary chart.
X-Gap Elevation Depth to height ratio Z-Gap Rotation Width to height ratio Bar-Gap
About DS-User
This screen shows the current version of this installation of the DS-User program. Click Info to bring up the DS-Client Version Info.
DS-Client Info Ports JRE Properties (Java DS-User only) Brings up the DS-Client Version Info screen. Brings up the Listening Ports screen. Brings up the Java Runtime Environment Properties screen with information on the local computer where DS-User is running.
See Also: What Is Asigra Cloud Backup?
Access Report screen

View by size View by number of files List New Report Shows the graphic sorted by size. Shows the graphic sorted by number of files Shows the files sorted by Access Time Allows you to search for specific file extensions.


Confidential.
Activity Log viewer screen

Use this screen to view the DS-Client Activity Log. To narrow your search, you can specify search parameters in the Select By section at the bottom. Some search combinations do not require certain fields/buttons. These will appear grayed out if unnecessary.
Activities List Icon User Name Activity Owner Customer Description Node ID (Grid DS-Client) Warnings Errors Start End Duration Files Icon shows the type of activity. Name of the user that performed the activity (if applicable). Type of activity. User Name of the Owner of the Backup Set (i.e. an administrator might perform an action on a set owned by someone else). [Multi-Tenant DS-Client mode only] Shows the customer associated with the corresponding backup set (if applicable). Identifies the backup set affected by the Type of activity performed. Contains the DS-Client node associated with the activity. Number of warnings that occurred during the activity (if any). Number of errors that occurred during the activity (if any). Shows the date and time the activity was started. Shows the time the activity was completed. Length of time between the activitys start and end times. Number of files that were actually transferred or processed. Note: CDP backup sets that are currently running will have this field updated every 30 minutes. Amount of data transferred to or from Online storage. (In Bytes) Note: CDP backup sets that are currently running will have this field updated every 30 minutes. Note: For activities that do not transfer data (e.g. LAN Scan Shares), the number in this column represents the amount of data processed (e.g. scanned, deleted, etc.). Shows the total amount of data transmitted between the DS-Client and DS-System (including encryption/compression). Note: For activities that do not need connection to DS-System (e.g. Local Cache, Initial Backup), this column will reflect the amount of processed data, after deduplication and compression (where applicable). Whether the activity was completed successfully. (Note: errors can occur, but the activity may complete successfully): Blank column: activity successfully closed connection with DS-System. No Connect: activity failed to connect to the DS-System. With errors: activity contained errors (but completed successfully). Incomplete: activity did not finish completely and/or failed to close its connection with DS-System properly. Activity's Identification number Shows additional information for the corresponding activity (if applicable).
Online
Transmitted Amount
Completion
ID Note
Description section Displays details about the highlighted line in the Activities List. Select by section Filter options that can be used to limit what is displayed in the Activities List. From field To field Type the date and time of the earliest activity you want to see. No earlier data will be displayed. Type the date and time of the latest activity you want to see. No newer data will be displayed.


Confidential.
Activity Type ID Node/Set Schedule Retention
You may search for a specific activity. If this list box appears, it allows you to choose between Demand and Scheduled activities (or both). Allows you to search for a specific Activity ID number. Each activity on DS-Client has its own unique (chronological) ID number. You may search for a specific node/backup set. Click [>>] to bring up the Select from Backup Sets screen. If you select Scheduled backups, this list box appears, allowing you to select a specific schedule. Allows you to filter for only activities associated with the selected retention rule. The default is <Any>, which disables this filter. You may specify a particular user in this field. Owner: Searches for activities belonging to a particular user (the backup set owner). Performed by: Searches for activities performed by a particular user. To view the activities from a specific Node, choose one from the list. The default is <All>. Click to update the activity log display based on the parameters in the Select By section. For backup sets that have the Detailed Log option activated (Set Properties - Options tab). Click to bring up the Detailed Log Viewer, which shows all the files that were backed up in the highlighted session. You can view more details about each activity by accessing the Event Log. The Select By options in the Event Log will match those of the highlighted activity. Click to bring up the Event Log Viewer screen.
User Node ID (Grid DS-Client) Find
Detailed Log
Event Log
Add / Edit Complexity Rule

Use this screen to add or edit a Complexity Constraint Rule for a Rotated Password.
Min. Length Character Set Select a set of characters or define your own. Letters Uppercase Letters Lowercase Letters Digits Special Characters Custom Shows the character set for the corresponding complexity rule choice. For Custom: you can edit the list of characters that can be used. The minimum number of characters from the selected Character Set to include in the rotated password.
Choice
Characters
Add / Edit Event Filter

This screen allows you to enter or modify an Event Filter.
Event # Category This must be the exact event number, as it appears in the Event Log Viewer screen. This must be the same category as the corresponding event number, as it appears in the Event Log Viewer screen.


Confidential.
Type
Select what Event Severity to apply. This over-rules the default for the corresponding event. Remember: this can affect the notifications that are sent. Information Warning Error Click to save this filter in the Event Filter List.
Description Shows the corresponding description for this event. This field cannot be edited. OK
Add / Exclude item from scanning result

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to add or exclude scan items that were discovered by the previous scan of the Unprotected LAN Resource Discovery Tool.
Item Tree Shows the items discovered by the previous scan. Add Exclude Adds the item. Excludes the item.
Add / Exclude Subnet

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to add or exclude items from the scan.
Subnet Address Subnet Mask Add Exclude Enter the first three parts of the IP address, followed by a 0 in the last part to signify the subnet (e.g. 12.34.56.0 searches all resources on the .56 subnet). This screen only uses the first three parts of the IP address entered. Read Only. Adds the subnet. Excludes the subnet.
Add / Modify address screen

Use this screen to add or modify a DNS host name or IP address.
Host name or an IP address IP range (Add only) Use this field to enter a specific DNS host name or IP address. Use this option to specify the start and end of an IP range (e.g. 10.20.30.40 to 10.20.30.43). This allows you to quickly populate a large list of sequential IP addresses.
Add / Modify DS-Client Connection Entry (Print Global Report)

(Java DS-User only) This screen allows you to enter or modify DS-Client connection entries.
Name Enter a descriptive name for the DS-Client.


Confidential.
IP Address User Name Password From
Enter the DS-Clients IP Address. Once you finish entering the IP Address, press TAB or highlight another field. Java DS-User will immediately verify if this DS-Client is running (the From list will activate). Type the user name of the account with access to the DS-Client. Type the corresponding account password. Select the domain or server on which the username and password will be verified. (i.e. DS-Client validates supplied credentials with this domain or server.).
Add / Modify Filter

This screen allows you to create a filter to apply to an E-Mail backup set. This filter will allow only E-Mails that fit the criteria to be backed up / restored. Some differences may exist, depending on the E-Mail server type, and if this filter is for backup or restore.
Filter Name Filter Conditions Field Select the field to search. The available selections depend on the E-Mail server type, and if this filter is for backup or restore. Select the criteria to apply to the search field: NOT checkbox - check to make this criteria negative. = equal > greater than < less than >= greater than or equal <= less than or equal Contains (Exchange, Restore) - searches Field for Value containing this string Begins with (Exchange, Restore) - searches Field for Value beginning with this string Ends with (Exchange, Restore) - searches Field for Value ending with this string Either enter the value manually, or select from the available value options. This field depends on the selection in the Field box. Select the boolean operator that applies for each filter condition: AND OR Use this with the right bracket for a complex filter. Use this with the left bracket for a complex filter. Click to add the filter condition. You may do this as many times as necessary to create the required filter. Shows the details of this filter. Each filter condition you have specified appears. Add a descriptive name for the filter.
Criteria
Value Logical ( Left Bracket ) Right Bracket Add Description
Add / Modify DS-Client (Java DS-User Initialization)

Add or modify a specific DS-Client entry (standalone or Grid) to search for on startup of the DS-User.
Single DS-Client Enter the DS-Client IP address or DNS address. If you select Grid DS-Client, the field expands into a list and the following buttons appear. Add: Add a new entry to the Grid DS-Client address. Modify: Edits the highlighted entry in the Address list. Delete: Deletes the highlighted entry from the Address list. Load: This allows you to load a text file containing a list of hostnames and / or IP addresses representing the nodes of a single Grid DS-Client.
Confidential.
Grid DS-Client

Port Use UDP protocol to discover DS-Client
The default setting is 4403. Normally you should not change this setting. The UDP protocol can display the list of DS-Clients faster, though with less certainty that a DS-Client is capable of accepting a connection.
Add a DS-Client
Add or modify a specific DS-Client entry (standalone or Grid).
Single DS-Client Enter the DS-Client IP address or DNS address. If you select Grid DS-Client, the field expands into a list and the following buttons appear. Add: Add a new entry to the Grid DS-Client address. Modify: Edits the highlighted entry in the Address list. Delete: Deletes the highlighted entry from the Address list. Load: This allows you to load a text file containing a list of hostnames and / or IP addresses representing the nodes of a single Grid DS-Client.
Grid DS-Client
Add / Edit Permissions for a User or Group screen

This screen allows you to add permissions for other users/groups to use the selected backup set.
List Icon Name Description Domain Permission Type Backup Restore Modify Delete Notes 1 2 Users and groups only appear if they have logged into the DS-Client at least once. The backup set owner and users with the DS-Client Administrator role automatically have all permissions to a backup set even though they are not listed here. Grants permission to perform backups. Grants permission to restore. Grants permission to modify the backup set. Grants permission to delete the backup set. Shows what the corresponding entry refers to: a specific user a group Shows the users and groups available. Shows a description (if any) of the corresponding user or group. [Windows only] Shows the domain or server where the user or group is from.
Add / Modify DS-System connection entry screen

Use this screen to add/modify DS-System connection setup entries.
DS-System connection entry Primary Check to indicate if this is the Primary connection. The DS-Client will use the Primary connection first, to connect to the DS-System. All other connection entries are considered alternate entries, to be used only if the primary connection fails. A list of the DS-Systems address(es) that can be used for this connection entry. You can enter an IP address or a DNS host name. Multiple addresses can be entered, if your Service Provider provides multiple addresses to connect to this DS-System.
DS-System address (IP or DNS)


Confidential.
Add / Modify / Delete
Click this button to add, modify, or delete entries from the DS-System address list.
Pre/Post This option can be used to run commands on DS-Client when connection to DS-System is required. This can help in some network situations, like dealing with firewalls. Pre-Command Post-Command Enter a command to run on the DS-Client computer before it connects to the DSSystem. Click Test to run the command and view the exit code it returns. Enter a command to run on the DS-Client computer after it disconnects from the DSSystem. Click Test to run the command and view the exit code it returns.
Specify a number. If the Pre-Command returns an exit code that meets this condiConsider connection tion, the DS-Client will: failed if pre-exit Not attempt to connect to DS-System. code Log the error. Check to run the specified Pre/Post commands for each activity that requires a conConsider Pre/Post nection to DS-System (even if the activities overlap). Uncheck to run the Pre-Comindividually for each mand before the first activity, and to run the Post-Command after the last activity connection has finished (if the activities overlap). Delay after executing pre-command Delay after executing post-command Enter a time (in seconds) to wait after executing the Pre-Command, before DS-Client connects to DS-System. Enter a time (in seconds) to wait after executing the Post-Command. No activities will run on DS-Client.
Add / Modify Subnet (Java DS-User)

(Java DS-User only) This screen allows you to enter or modify a subnet entry.
Address Port Use UDP protocol to discover DS-Client Enter the subnet address For example: 222.111.30 searches all resources on the .30 subnet. The default setting is "4403". Normally you should not change this setting. Scanning a subnet uses the UDP protocol. The UDP protocol can display the list of DS-Clients on a subnet faster, though with less certainty that a server is capable of accepting a connection (when compared with specifying the full IP address of a specific server).
Add Notification screen

This screen allows you to view and change the individual notification settings. For E-Mail and Pager notifications, the notification options must have been set in the DS-Client Configuration screen.
Notification Method E-Mail Pager Broadcast (Windows DS-Client) Event (Windows DS-Client) Recipient
Sends an E-Mail message to the specified recipient. Sends an E-Mail to the Pager E-Mail account (configured in the DS-Client Configuration). Sends a message to the messenger service on the specified recipient domain, workgroup or server. (Broadcasts to domains or workgroups are limited to 128 characters). Records the notification in the specified recipient server's Event Log.

Confidential.
Administrator (E-Mail) Other (E-Mail) Pager (Pager) Server(s) (Broadcast & Event) (Windows DS-Client)
Sends the E-Mail notification to the DS-Client Administrator (specified in the DS-Client Configuration - Notification Tab). Sends the E-Mail notification to the recipient identified in the field. Sends the notification to the Pager account (specified in the DS-Client Configuration - Notification Tab). Sends the notification to the selected Domain, Workgroup or Server. Use the [>>] button to browse and select the recipient. [Note: Feature is no longer supported on Windows DS-Clients running on Windows VISTA, Windows 7, Windows 2008 or higher.]
Completion All: Notification will be sent in any scenario: when Completed without errors, Completed with errors, and Incomplete. Successful: An activity that completed successfully (without errors or warnings). Completed with warnings: An activity that completed with at least one warning event. Completed with errors: An activity that completed with at least one error event. Incomplete: An activity that is not completed successfully. Detailed Notifications Attach detailed log Send E-Mail using HTML format (E-Mail only). Check this box to send more detailed backup set information. (E-Mail only). Check this box to include a file-level detailed backup log as an attachment. Compress: Select to compress the attached file. (E-Mail only). Check this box to send the E-Mail notification in HTML format. Otherwise, it will be sent in plain text format.
Advanced Connection Options (Linux DS-Client)

SSH Backup Sets only Use this screen to view or change connection options for the selected backup set.
Select the type of script language to run on the backup source computer. PERL Access interface PYTHON DIRECT: use only if you have a specific (i.e. custom-made) binary on the target computer that will perform the backup/restore. Enter the exact path to the PERL / PYTHON / DIRECT binary on the target computer. Interpreter / Program Path
Advanced Options screen

Use this screen to narrow down your selection in a Restore Wizard or in a Request Wizard. The Wizard will show only directories that meet these conditions. Notes: Restore Wizard includes regular on-demand restores, BLM Image Restores, and Disc/Tape Restores. Request Wizard includes BLM Requests, and Disc/Tape Requests.
Shows all data stored online. (Note that the Filter section is empty.) Filters out files that were deleted from the source, but not removed from the online storage as of the last backup session. (You probably do not need this 'expired' data.) (Note that the Filter section has the date of the latest backup session.)
Show section Latest generation of all data Latest generation of all data (except deleted data)


Confidential.
Selective data (from a certain period)
Allows you to specify the period from which you would like to restore. (Note that this activates the Restore Period and Filter sections.)
Period section This section is only active if the Selective data (from a certain period) radio button is selected. This will narrow the display of files for restore to only those files/directories that were backed up within the specified period. From To Click [>>] to select the earliest time. This opens the Select a Backup Session screen. Click [>>] to select the earliest time. This opens the Select a Backup Session screen.
Filter section This section appears if the Restore Wizard or Request Wizard can use the DS-Client database to perform the filtering. It does not appear for BLM Image Restore or Disc/Tape Restore since they have been written to media and are no longer synchronized with the DS-Client database. Show all data Hide data (dirs / files) deleted from source on / before: Show only data (dirs / files) deleted from source on / before: No filter is applied. This filter allows you to hide backed up data (directories and files) that was intentionally deleted from the source computer. Select a date and time in this field to screen out backed up data that was not scanned by the DS-Client since the filter date. This prevents you from restoring directories / files that were intentionally deleted. The inverse of the previous hide data option (above). This allows you to view and restore only those directories / files that were intentionally deleted from the source computer.
File overwrite section [Restore Wizard only] This section allows you to control the types of files that are restored, in order to minimize restore times. Restore all Restore newer Restore older Restore different Skip existing Restores all selected files to the destination directory. Any files of the same name will be overwritten. Restores only with files that have newer dates than those in the destination directory. Restores only with files that have older dates than those in the destination directory. Restores only with files that have different dates/sizes than those in the destination directory. Does not restore any existing files of the same name in the destination directory.
Assign to Retention
Use this screen to select a Retention Rule.
Name Description No Retention Rule: Use a specific Retention Rule: select from the list of the Retention Rules defined on the DS-Client. Shows a description of the selected Retention Rule.
Assign to Schedule screen

Not Scheduled Scheduled
Backup set is not set for unattended backup. Backup set will run based on the selected schedule:
Confidential.
Available schedules
Shows a list of the schedules available.
Assisted Delete - Select Backup Set / Directory

This screen appears with the automatic selection(s) for delete from online, based on the selections made in the Assisted Delete - Select how you want to delete screen.
Backup Set List Windows DS-Clients: Selected directories will be deleted. Linux/Mac DS-Clients: Files in the selected directories will be deleted. If the entire directory was deleted, the directory will also be removed from online.
Finish
Deselect a box to keep the corresponding directory. All other backup sets\directories (that cannot be selected) do not fit the Assisted Delete selection parameters. Click to have DS-Client connect to DS-System and delete the selected items from online storage.
Assisted Delete - Select how you want to delete

Assisted Delete allows you to delete obsolete online data from several backup sets in one process. Use this screen to specify the delete conditions. For Windows DS-Clients, the Assisted Delete Wizard will search all File System and DS-MLR (E-Mail level) backup sets on the DS-Client for directories that match these conditions. For Linux/Mac DS-Clients, the Assisted Delete Wizard will search all NAS, UNIX-SSH, NFS, Local File System backup sets on the DS-Client for files that match these conditions.
Time based data selection Delete Period From To The From and To dates create a delete period: directories backed up during this time will be displayed for delete. Select a starting time for the period you wish to delete. Select an ending time for the period you wish to delete.
Allows you to specify the number of generations to keep online (i.e. not select for delete) from the Delete Period. If you specify a number, you will only be Leave last ... generations able to select directories that have more generations available for delete than this number. Filter Windows DS-Client will compare directories in its logs with the directories backed up at DS-System. Linux/Mac DS-Client will compare files in its logs with the files backed up at DS-System. The date and time entered in this field filters for directories (or files) currently on the DS-System but not on your backup computer at that time. This allows you to remove backed up directories (or files) that were intentionally deleted from your source.
Show only items deleted on / before
Placeholder/stub selection [Windows DS-Clients only] This option can be used if you are using a third-party storage management solution that migrates infrequently used files from the source, and leaves a small (size) placeholder/stub in its place. This assumes that the third-party storage management solution is where you want to protect that data (and the DS-System storage is not necessary). If DS-Client detects a placeholder / stub is created on the source (by the Windows offline attribute), the corresponding file on DS-System will be deleted, based on the selected conditions (see below).

Confidential.
Keep the last placeholder / stub and subsequent generations The last placeholder or stub will be kept on DS-System, as well as any full file generations that appear after that latest placeholder/stub. Keep all placeholders / stubs All placeholders or stubs will be kept on DS-System, as well as any full file generations that appear after that latest placeholder/stub. Move to BLM A copy of all data deleted from DS-System during this Assisted Delete will be moved to BLM (Backup Lifecycle Management). This option only appears if the BLM Module is enabled by your Service Provider. Use new archive package: Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. Archive packages are specific to a particular backup set. Each BLM Request will be added to an Archive Package until it reaches a specified limit (# of files, size, time). Session Label: Each Archive Package is automatically time-stamped, but you must add your own label (alphanumeric string) to demand BLM requests. This will make it easier to search an Archive Package.
Audit Trail screen

Use this screen to view the audit trail. You can see who has made changes to the database, when, and what the changes were.
Audit Trail List Icon Time User Operation Table Description Select By From field To field Operation User Table Type the date and time of the earliest operations you want to see. No earlier data will be displayed. Leave this field blank to search as far back as possible. Type the date and time of the latest operations you want to see. No newer data will be displayed. By default, this is the current date and time. Action, Insert, Update, Delete, or <All>. You may type a specific user in this field. You may select a specific table from this list. Icon shows the type of operation. Shows the time the modification occurred. Shows the User Name of the user who performed the modification. Shows the type of modification performed. Shows the table that was modified. Describes the details of the modification that occurred.
Available Password Rotation Rules

Use this screen to select a Rotation Rule. It also allows you to add or configure the list of Rotation Rules.
Rotation Rule List ID: Internal DS-Client ID number. Name Min. Len.: The minimum length (in characters) of the rotated password. Max. Len.: The maximum length (in characters) of the rotated password. New Click to add a Rotation Rule to the list. Opens the New / Edit Password Rotation Rule.


Confidential.
Edit Remove Select
Click to edit the highlighted Rotation Rule from the list. Opens the New / Edit Password Rotation Rule. Deletes the highlighted Rotation Rule from the list. Click to select the highlighted Rotation Rule.
Axis Setting
(Win32 Only) This screen controls the axis settings for the Load Summary chart.
Font Size Style Label Standing Word wrap Rows seen Logarithmic base
Backup Generations for ... screen

Use this screen to view or select from the online generations of a particular file. This screen also shows all of the backup options applied to each generation. The file name and file ID are located in the screen header.
Backup Generations List Local Storage column (Restore only) Last Modified Backup Time This column only appears if the backup set is configured to use Local Storage. If an L appears, it means that generation of the file is also in Local Storage. Date and time of last modification of this file. Date and time of last backup of this file.
Compressed Size Disc/Tape restores can only have one generation of a file. (Disc/Tape only) This is the size of that file on the Disc/Tape media (as written by the DS-System). File Size Stream Size The protected size of each listed generation of the file. Shows the full transmission size of the file in Bytes (including file security, permissions, streams, etc.). Shows the corresponding backup options that have been applied to this particular generation of the file. These options correspond to the following key: E = Extended Attributes S = Backup Streams P = Permissions X = POSIX D = Daylight Savings Correction (some File Systems) D = DBCC (MS SQL Server backups) R = Reparse Point (Windows) C = Encrypted File (Windows) Z = Sparse File (Windows) O = Offline (Windows)
Options


Confidential.
Archive Time
Time when the corresponding generation was pushed to BLM from online (using the Archive Old Data to BLM feature from the Retention Rules). If this column appears, it means this generation has been Archived. You cannot restore the file from online (only from a BLM Image). An Archived Data Placeholder (a small archive stub containing only metadata) is left in place of the archived file to prevent DS-Client from backing up the file again (unless it is changed). Only the latest generation of an online file leaves an Archived Data Placeholder. All other archived generations are completely removed from DS-System and no reference is made to them by DS-Client. Corresponding Archive Package number for the generation.
Archive ID
Objects Opens the Backup Objects for ... (System i Server and Backup from the Cloud) (System i Server screen. backups) Select (Restore only) Click to select the highlighted generation for restore.
E-Mail Backups: The following apply to E-Mail backups only.

Backup Generations List SUBJECT ATTACH_NAMES ATTACH_NUMBER MAIL_SIZE RECV_TIME CREATION_TIME SENDON_TIME CATEGORIES COMPANIES IMPORTANCE TO_ADDR FROM_ADDR BCC_ADDR CC_ADDR FLAG Archive Time Archive ID Time when the corresponding generation was pushed to BLM from online. If there is a date in this field, this generation has been Archived. You cannot restore the file from online (only from a BLM Image). Corresponding Archive Package number for the generation.
Backup Objects for ... (System i Server and Backup from the Cloud)
Use this screen to view objects available for restore. For System i Server backup sets: Use the "Select"/"Deselect" buttons to selectively restore only the objects you need. Unselecting objects has no influence on the restore speed if the objects were backed up without the "Individual obj." option. For Backup from the Cloud backup sets (Salesforce.com): This screen appears in a Restore Wizard tab. By default, all tables are selected.


Confidential.
Backup Schedules Tab

Use this tab to manage the schedules for the DS-Client.
Schedules Tree Shows a tree of the existing schedules. The top-most container is <Not Scheduled>. Backup sets in this container will not run, except for demand backups initiated by the user. Expand a Schedule to show the backup set(s) associated with it. Opens the Schedule Calendar screen. Click to create a new schedule. This brings up the Schedule screen. Click to edit the highlighted schedule. This brings up the Schedule screen. Click to delete the highlighted schedule. Click to activate the schedule. Click to suspend the schedule. None of the backup sets associated with this Schedule will be backed up. Click to prioritize the backup order within the schedule. This brings up the Set Backup Set Priority screen. Expands the schedule branch. Collapses the schedule branch. If a backup set is highlighted, you can use this option to select a Schedule. You can also drag-and-drop the backup set into the Schedule container you want. You can drag & drop backup sets to other schedules.
Right-mouse click menu: Schedule Calendar New Schedule Edit Schedule Delete Schedule Activate Suspend Set Priority Expand Collapse Assign to Schedule (backup set level) Drag & Drop.
Backup Set Recovery screen

This screen allows you to recover backup sets to the DS-Client database in the event they become 'orphaned' on the DS-System. For example:If your DS-Client was destroyed, you would have to reinstall the software to a new computer. The replacement DS-Client database will be empty of backup sets, but the DS-System will still have all your backup data. At minimum, you must restore these backup set configurations by using this screen. (For DS-Clients with several backup sets it is much faster to use the DS-Client Database Recovery feature that will also recover all of the DS-Client's logs up to the last backup time of the database.)
Shows any backup sets that can be "recovered". In some cases, the Backup Sets will be recovered with default information (which you must correct). The Backup Set Owner's name may appear in different colors: Black - You may recover the set, then perform restores immediately. Red - You may recover the set, but afterwards you must migrate the backup set to specify the Network Provider or Computer information. (See: Migrate Shares screen) Gray - You must resolve an ambiguity concerning the owner's user name or the Network Provider name prior to Recovering the backup set. Click Set Info to open the Recovery Info screen. Click this button to select the highlighted backup set for recovery. Click this button to view the information that will be recovered for the highlighted backup set. This brings up the Recovery Info screen. Check the Activity Log to look for errors such as "Backup Set not found in Backup Log". This indicates the backup set exists on the DS-System's online storage, but not in the DS-Client's database.
Backup Set Tree
Recover Set Info Notes 1


Confidential.
2 3
The Activity Log will be updated with Recovery information (if applicable) each time a Daily or Weekly Admin is run. A synchronization is run on each recovered Backup Set.
Backup set type

Use this screen to select the types of backup sets you want to include in the Online File Summary.
Set Type You can select any or all of the following type(s) of backup sets to include: Regular: Includes data from all regular backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets.
Backup Sets Information

Use this screen to export the report data.
Export Options Save As File Format Field Delimiter Choose where you want the report information saved. Choose the format you want to save the report in from this drop down list. (.csv format only) Allows you to select different field separators (tab, comma, semicolon) for the exported data.
Backup Sets Tab

This tab appears in the DS-User screen. It allows you to manage the backup sets.
Backup Sets Tree Shows a tree of the existing Backup Sets (by default, sorted by computer). Expand a branch to show the backup set(s) associated with it. Detailed View (Win32 DS-User only) Group by User (Win32 DS-User only) Displays backup sets grouped in the order \Network\Node\Set\User. Activate from: Sets Menu > View > Detailed View Displays backup sets grouped in the order \User\Network\Node\Set. Activate from: Sets Menu > View > Group by User A backup set's color indicates its status. Black = active Blue = Local-Only Gray = suspended Red = needs synchronization Opens Demand Backup Wizard for the highlighted backup set. Click to back up the highlighted set immediately. This brings up the Select Demand Backup Items screen. Click to restore the highlighted set. This brings up the Select Items screen. Click to delete online backups from the highlighted set. (In Advanced Mode, you can delete the entire set.) Click to enforce the retention rules for the highlighted set. Allows you to request a Disc/Tape of the selected backup set/files (your Service Provider must be configured to support this service). (Backup Lifecycle Management module must be enabled) Allows you to request a BLM Archive Package of the selected backup set/files.
Confidential.
Color
Double click
Right-mouse click menu Backup Now... Restore Now... Delete... Enforce Retention Request Disc/Tape... BLM Request...

Validation... Synchronize Activate / Suspend Migrate... Clone
Allows you to perform a validation of the selected backup set/files on the DS-System online storage. Click to synchronize the backup log of the currently highlighted backup set with the DS-System online storage. This brings up the Synchronize Backup Set screen. Click to toggle the status of the currently highlighted backup set between Active and Suspended. Depending on the status, scheduled backups either will or will not be performed. Click to migrate a backup set from one computer to another. This brings up the Migrate Backup Set Wizard screen. Click to copy the highlighted backup set. This brings up the Clone Backup Set Wizard on the Schedule Tab. You must assign a new schedule and name for the backup set. (Local-Only sets) Click to convert the highlighted backup set from Local-Only to a Regular backup set that saves data to the DS-System. Cancel Convert only appears if conversion was interrupted for the highlighted backup set. Click to change the ownership of the selected backup set. The Change Backup Set(s) Owner screen appears. Click to change the permissions of the selected backup set. The Backup Set Permissions screen appears. Click to edit the backup properties (ex: name, backup options, schedule, etc.) for the highlighted backup set. The Backup Set Properties screen appears.
Convert / Cancel Convert
Change Owner Permissions Properties...
Bandwidth Throttle
Use this screen to apply a throttle to the outgoing and incoming bandwidth used by this DS-Client. There are two tabs, which have identical configurations except for the data direction where the throttling is applied: To DS-System (e.g. backups) From DS-System (e.g. restores)
Default Throttling Unlimited: (DEFAULT) No throttle is applied, unless listed in the Exceptions List. Limited to [...] KB/Sec: Throttle is applied at all times, except for periods defined in in the Exceptions List. Except (Exceptions List) Each line represents a different detail: a specific day and time window where the listed bandwidth throttle applies. This overrides the default throttling selection (above). Start Time End Time Bandwidth Throttle: Can be Unlimited or Limted to [...] KB/Sec. Add Modify Remove Select Group Click to add a new detail. Opens the New / Edit Bandwidth Throttle Schedule Detail screen. Click to edit the selected detail. Opens the New / Edit Bandwidth Throttle Schedule Detail screen. Removes the highlighted detail from the Exceptions List. You must highlight a Detail in the Exceptions List for this button to work. Click to highlight any other details (from other days) that share this Details Start Time, End Time and Bandwidth Throttle settings. This allows you to modify an entire group at the same time.


Confidential.
BLM Archive Rule

Use this screen to define a BLM Archive rule.
Select a number and the unit of time: Minute(s) Hour(s) Day(s) Week(s) Month(s) Year(s) Includes all files in all subfolders.
Archive files older than:
Archive Rule applies to All files Select a File Filtering Rule from the drop-down list. Specific files defined by the Add: adds a new rule to the list (Opens the File Filtering Rule screen) filtering rule: select from the Edit: edits the selected rule in the list (Opens the File Filtering Rule drop-down list screen) Remove: deletes the selected rule from the list Shows a list of each option in the selected File Filtering Rule. Description
Change Backup Set(s) Owner screen

From To Change Activity Log This backup set All backup sets Existing owner of this backup set. User you want to assign ownership of this backup set to. Changes the DS-Client database so the owner field in the Activity Log reflects the new owner. Only this set is changed to the new owner. All backup sets associated with this user will be changed to the new owner.
Chart Options screen

(Win32 Only) This screen controls all of the chart settings for the Load Summary. These advanced settings allow you to customize your chart.
Allows you to set general chart settings. Rows seen Logarithmic base Line thickness Stacking Auto Layout Guideline X-Grid Y-Grid Allows you to set the 3-dimensional view settings for the chart. X-Gap Elevation Depth to height ratio Z-Gap Rotation Width to height ratio Bar-Gap
General
3D View Setting


Confidential.
Title
Allows you to change the title settings for the chart. Text Font style Font size Word wrap X, Y, and Z correspond to Width, Height, and Depth. Standing Word wrap
Axis Labels
Choose the E-Mail Server type

Microsoft Exchange Server Microsoft Outlook Lotus GroupWise Backup Microsoft Exchange Server E-Mail messages. Backup Microsoft Outlook E-Mail messages. Backup Lotus Domino or Lotus Notes server E-Mail messages. Backup GroupWise E-Mail messages.
Choose the kind of backup set screen

This screen allows you to select the backup type you wish to create. Depending on your choice, the Wizard will guide you through the necessary backup specifications.
DS-Client Backup Sets Creates backup sets that the DS-Client will process. File System Microsoft SQL Server Microsoft Exchange Server Permissions Only Oracle Server The most common backup type. These include files, directories, and other operating system features. Backs up active Microsoft SQL servers on your network. Backs up active Microsoft Exchange Mail Servers. Backs up file and directory permissions. One dump file will be backed up for each backup item selected. Backs up Oracle server databases. [You must copy a DLL file to the target Server's system path, and make the configurations explained in that section of this section.] Backs up E-Mails from MS Exchange Server, MS Outlook, Lotus Notes / Domino Server and GroupWise at the individual message level. [You must install the DS-MLR Service on the target data source computer. This is a separate product that is a component of the DS-Recovery Tools installation.] Backs up the System i server. [For this option to be enabled, the IBM iSeries Access for Windows has to be installed on both the System i server and the PC on which the DS-Client is running.] Backs up MySQL server databases. Backs up Microsoft SharePoint Servers at Item-Level. [You must install the DS-Recovery Tools Service on the target data source computer. This is a separate product that is a component of the DS-Recovery Tools installation.] Backs up Lotus Domino Server databases. Backs up selected items using the target computers Microsoft VSS (Volume Shadow Copy Service) tools. Backs up selected items from a cloud service (Salesforce.com).
E-Mail Messages
System i Server MySQL Server Microsoft SharePoint Server Lotus Domino Server VSS-aware Backup Set Backup from the cloud


Confidential.
VMware VADP
Backs up a VMware vCenter Virtual Machine by exporting it on the vCenter. Requires a Local DS-VDR Tool. This type of backup set does not backup data to DS-System. Backs up a Physical computer to a VMware vCenter Virtual Machine. Requires a Local DS-VDR Tool. This type of backup set does not backup data to DS-System. This tab is skipped in the following circumstances: No other backup type (other than file system) is supported.
Physical to Virtual Note 1
Choose the kind of backup set screen (Linux DS-Client)

This screen allows you to select the backup type you wish to create. Depending on your choice, the Wizard will guide you through the necessary backup specifications.
DS-Client Backup Sets NAS, UNIX-SSH, NFS, Local File System Permissions System i MySQL PgSQL Oracle Server Oracle-SBT DB2 Server XenServer Sybase VMware VMware VADP Physical to Virtual Creates backup sets that the DS-Client will process. The most common backup type. These include files, directories, and other operating system features. Backs up file and directory permissions only from each backup item. You can select backup items at the directory level. One dump file will be backed up for each backup item selected. Backs up active System i servers on your network. Backs up active MySQL servers on your network. Backs up active Postgre SQL servers on your network. Backs up active Oracle servers on your network. Receives RMAN dumps via the Oracle SBT protocol. Backs up active DB2 servers on your network. Backs up at the Virtual-Machine-level from XenServers on your network. Backs up active Sybase databases at database-level. Backs up at the Virtual-Machine-level from VMware servers on your network. Backs up VMware servers on your network using the native VMware vStorage API for Data Protection. Backs up a Physical computer to a VMware vCenter Virtual Machine. Requires a Local DS-VDR Tool. This type of backup set does not backup data to DS-System.
SSH Notes: 1. The backup source machine must be a Unix system (Linux, Solaris, HP-UX, or AIX). 2. The source machine must have an OpenSSH compatible server installed and started. 3. The source machine must have either Perl5 (core function, 5.6 or beyond) installed, or Python (2.4) installed. [Alternatively, you can use the DIRECT option to run a specific script/binary located on the source machine.] 4. The SSH approach cannot scan the LAN to get an initial machine list. You must enter the IP of the source machine in the Path field (e.g. UNIX-SSH\10.20.30.100). The user or administrator can also put the initial machine list into the file hostlist_ssh located in the installation path (usually /opt/ CloudBackup/DS-Client). 5. For more details, see the Knowledge Base article Backup / Restore using UNIX-SSH.


Confidential.
Choose the name for this backup set screen

This tab allows you to specify a descriptive name for this backup set.
Set name Set type Regular Self-Contained Enter the name of the backup set Select the type Creates a full featured backup set of any kind (File System, Database, etc.). Creates a Self-Contained backup set that performs backup and restore using only local storage. The Local Storage Path must be set (Setup Menu > DS-Client Configuration > Parameters Tab) Creates a Local-Only backup set that performs backup and restore using only local storage. This is similar to Self-Contained, except there are no limits on the number of backup sets, and the total capacity stored is licensed from the DS-System. The Local-Only Tool must be enabled for this DS-Client (by your Service Provider from the DS-System). The Local Storage Path must be set (Setup Menu > DS-Client Configuration > Parameters Tab) Creates a "virtual backup set" one that collects backup statistics, but does not physically backup data.
Local-only
Statistical
This box appears when a Statistical Backup Set Type is selected. Calculate transmit amount Check to emulate an actual backup transfer process. During statistical back(Statistical Backup Sets) ups, specified backup files will be read from their source and processed for compression/encryption. BLM (Infinite Generations) (Backup Lifecycle Management module must be enabled) Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver.
Use Local Storage These options appear if you have the Local Storage Tool Enabled from your Service Provider, and you have specified a Local Storage Path in the DS-Client Configuration Parameters Tab screen. Save on Local Storage Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). Backup data will be sent to the location specified in the Local Storage Path field. Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). Backup data will be sent to the location specified in the Local Storage Path field. Click [>>] to choose a specific local storage path for this backup set. Opens the Enter Local Storage Path. If you do not make a selection, the path from the DS-Client Configuration Parameters Tab screen is used. (Multi-Tenant DS-Client only) Select from the list of available customers. This backup set will be grouped under the selected customer in the Backup Sets tree. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <Unspecified Customer> selection.
Transmission cache on Local Storage
Local Storage Path
Customer


Confidential.
Choose the name for this backup set screen (Linux DS-Client)
This tab allows you to specify a descriptive name for this backup set.
Set name Set type Regular Self-Contained Enter the name of the backup set Select the type Creates a full featured backup set of any kind (File System, Database, etc.). Creates a Self-Contained backup set that performs backup and restore using only local storage. The Local Storage Path must be set (Setup Menu > DS-Client Configuration > Parameters Tab) Creates a Local-Only backup set that performs backup and restore using only local storage. This is similar to Self-Contained, except there are no limits on the number of backup sets, and the total capacity stored is licensed from the DS-System. The Local-Only Tool must be enabled for this DS-Client (by your Service Provider from the DS-System). The Local Storage Path must be set (Setup Menu > DS-Client Configuration > Parameters Tab) Creates a "virtual backup set" one that collects backup statistics, but does not physically backup data.
Local-Only
Statistical
This box appears when a Statistical Backup Set Type is selected. Calculate transmit amount Check to emulate an actual backup transfer process. During statistical back(Statistical Backup Sets) ups, specified backup files will be read from their source and processed for compression/encryption. BLM (Infinite Generations) (Backup Lifecycle Management module must be enabled) Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver.
Use Local Storage These options appear if you have the Local Storage Tool Enabled from your Service Provider, and you have specified a Local Storage Path in the DS-Client Configuration Parameters Tab screen. Save on Local Storage Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). Backup data will be sent to the location specified in the Local Storage Path field. Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). Backup data will be sent to the location specified in the Local Storage Path field. Click [>>] to choose a specific local storage path for this backup set. Opens the Enter Local Storage Path. If you do not make a selection, the path from the DS-Client Configuration Parameters Tab screen is used. (Multi-Tenant DS-Client only) Select from the list of available customers. This backup set will be grouped under the selected customer in the Backup Sets tree. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <Unspecified Customer> selection.
Transmission cache on Local Storage
Local Storage Path
Customer


Confidential.
Clean Local-Only Trash

[Local-Only Backup Set data only] Use this screen to clean the Local-Only Trash from the Local Storage Paths defined on this DS-Client.
Clean data deleted at least: [x] Days Local Storage Path Clean Trash only permits data deletion from the Local Storage Paths recycle folder if a file qualifies based on this age. Valid valued: 1-999 (days) Dropdown list shows all the Local Storage Paths defined on the DS-Client. Select the specific Local Storage Paths Trash (recycle folder) that you want to clean.
Clean previous shares in list (Linux DS-Client)

LAN STORAGE DISCOVERY TOOL The Share Discovery Wizard helps you to identify all the available backup shares on your LAN.
A list of shares from the previous LAN Storage Discovery process. Icon: Date: Share Name: Shared Path: Description: Scanned Size: Check to remove any shares from the previous scan that returned a Scanned Size of 0.
Previous Shares List
Clean share list
Cloud database upload tool

Use this screen to upload the table(s) from any of the SalesForce.com backup set dump files in the Local Storage.
Select SalesForce DB File Location SalesForce DB Path Browse and select the Local Storage folder containing the specific SalesForce.com database dump file you want to use for the upload. This opens a browse selection window.
Select tables to upload The left column contains a list of all the tables in the selected database dump file. Highlight the table(s) you want to add and click the [+] button. Selected tables appear in the right column Select credentials of SalesForce.com Connect to SalesForce with Upload Click to supply the connection credentials to the SalesForce.com account. This opens the Specify Credentials (Windows DS-Client) screen If DS-Client can connect to Saleforce.com with the supplied credentials, this button activates. Uploaded table data is appended to any existing table.
Connect to DS-Client Service screen

Use this screen to connect to a particular DS-Client on your network. It displays a list of all available DS-Clients.
Connection Properties

Confidential.
Server
Protocol Credentials User Name Password From Remember Credentials
Shows the selected DS-Client computer Java DS-User: This is a read-only field, showing the selection from the DSClient(s) list. Win32 DS-User: The default is a drop-down list of the local DS-Client and all other DS-Clients on the same subnet. This behavior can be altered from the DS-User Initialization - Connection (Win32) screen. Encrypted: All communications between the DS-User GUI and DS-Client service are encrypted using a random encryption key. Standard: This option is only offered for backwards compatibility with old service/daemon versions that do not have this feature. Type your User Name. This is a valid account established on the DS-Client computer. Type your password. Select the domain or server on which the username and password will be verified. (i.e. DS-Client validates supplied credentials with this domain or server.) Check to have the DS-User reuse the supplied credentials on each login during the current session. This is reset once the DS-User application is closed. Activates the auto-connect feature for this DS-User GUI installation. Select this option to use your current logged on Windows Username and Password to connect to the DS-Client. The DS-Client that the GUI connects with depends on the Auto-Connection setting in the DS-User Initialization - Connection (Java) or DSUser Initialization - Connection (Win32) screen. Access to the DS-Client is restricted to Administrators and Backup Operators. Regular users must be permitted access by Administrators (in the DS-Client Configuration - Roles tab). User Names are required to restrict network access based on the credentials provided.
Use current security context (Windows DS-Client only) Note 1 2
Connection Configuration
(Optional - this screen can be left empty. If empty, the GUI will scan the local computer and the local computer's subnet for available DS-Clients. Applies to Win32 version only.) Use these settings to indicate a specific DS-Client or subnet to display in the Connect to DS-Client Service screen. This can speed up your login in larger network environments.
Allows you to select if this is a Single DS-Client or a Grid DS-Client. If you select Grid DS-Client, the Host field expands and the following buttons appear. Add: Opens the Host name or IP address (Win32 DS-User) screen Type Modify: Edits the highlighted entry in the Address list. (DS-Client only) Delete: Deletes the highlighted entry from the Address list. Load: This allows you to load a text file containing a list of hostnames and / or IP addresses representing the nodes of a single Grid DS-Client. Enter the IP address for the Host or Subnet. A Host can also be specified by its DNS host name. A Host can also be specified by HOSTNAME (computer name). This requires a corresponding entry to exist in the local computer's %systemroot%\system32\drivers\etc\hosts file (typically found in C:\WINNT\system32\drivers\etc\). Each entry must be on a separate line, with the IP separated from the HOSTNAME by at least one space (e.g. 10.20.30.111 C_Name). The default setting is 4403. Normally you should not change this setting.
Confidential.
Host / Subnet
Port

Continuous Data Protection Settings

When a scheduled or demand backup is started on a backup set flagged with the Continuous Data Protection option, the process will continue to run until explicitly instructed to stop (scheduled end time, user demand stop, etc.). While the Continuous Data Protection process is running, DSClient will detect when backup set items are changed on the source, and those changes will be backed up according to the settings in this screen. This screen allows some flexibility for a CDP backup set. You should have a good understanding of the type of data being backed up when configuring this screen.
[Windows DS-Clients]: This is automatically selected, depending on the type of backup set you are working with: Windows File System: Windows Built-in Monitoring MS Exchange E-Mail messages (DS-MLR): MLR E-Mail Monitoring [UNIX DS-Clients]: You can select the following: Generic Scanner - Loops the scanning function from regular backup sets. File Alteration Monitor (Linux Only) - Similar to the Windows Built-in File Monitoring. Interfaces with Linux Operating System functionality for notification of file changes. FAM will only be used if it is installed and working on the target machine (i.e. if the FAM daemon can be started). If FAM is not installed, DS-Client will try to copy and execute a FAM instance on a target Linux machine. FAM may not be available for some UNIX platforms.
File Change Detection
Specify the minimum interval that DS-Client must wait before backing up a changed file (that has been detected). This limit can be long if you do not want to backup file changes too Do not back up more often than frequently. [...] Seconds / Minutes / Hours This limit can be short (down to 1-second) if you want to provide precise backup granularity of changes. (The actual granularity achieved will depend on the speed of your network and hardware environment.) This option is for data that you know changes frequently. DS-Client will only backup a changed file after it detects it has not changed for the specified interval (i.e. the saved version is reasonBackup if file stops changing for ably stable.) [...] Seconds / Minutes / Hours Note: Because this is a time-sensitive operation, make sure the DSClient computer time and the backup source computer times are synchronized. Suspend Backup for Scheduled Select the scheduled activities that will suspend this CDP backup: Retention BLM Validation
Customer Information
[Multi-Tenant mode only] Use this screen to enter or update a customer for a Multi-Tenant DS-Client.
Name Contact Address Enter the customer name that you want to appear in the Backup Set tree Enter the name of the contact person for this customer. Enter the customer address.


Confidential.
Note
Enter any additional notes here.
Customer Management
[Multi-Tenant mode only] Use this screen to manage the list of customers that can be assigned to this DS-Clients backup sets. Once this list is defined, you can assign a customer to a backup set in either the New Backup Set Wizard or the Backup Set Properties (Set Info Tab).
Customer List Name - This is the name that appears in the Backup Set tree. Contact Address Note Add Modify Delete Click to add a new customer. Opens the Customer Information screen. Click to edit the highlighted customer. Opens the Customer Information screen. Click to delete the highlighted customer from the Customer List. (A customer can only be deleted if it does not have any backup sets assigned to it.)
Customized Data Wizard - Confirm Data Set Summary

Use this screen to review your selections. Click Finish to save and / or export the Data Set.
Customized Data Wizard - Enter Data Set Name

Use this screen to choose the Data Set Name.
Save data set settings Data Set Name Export data to file Saves the selections (except for Data Filters) in this DS-User installations .ini file. You can then access the same Data Set from the first Wizard screen. Shows the name of the Data Set. Exports the data to a file, based on the Data Set selections.
Customized Data Wizard - Select a Data Set

Use this screen to select the type of data you want to export for your custom report.
Data Set You have two options in the drop-down list: Create a <new> Data Set. Select from an existing Data Set (defined in this DS-Users .ini file). If you are creating a new Data Set, you must select the View. These are pre-defined groupings of tables. You can only select one view per Data Set. A list of all tables included in the view appears in the list below.
View


Confidential.
Customized Data Wizard - Select Display Columns

Use this screen to select the specific data fields you want to export for your custom report.
Available Columns The list of data fields that you can select to display. This list is based on the View selected in the Customized Data Wizard - Select a Data Set screen. Use the Add / Remove buttons to select from this list of data fields. Added items are removed from this list and moved to the Selected Columns list. The list of data fields that you have selected to display. Use the Up / Down buttons to select the order in which data fields will be written. The first item in the list is the first data field that will be written.
Selected Columns
Customized Data Wizard - Select Order

Use this screen to select the order in which this Data Set will be sorted.
Available Columns The list of data fields that can be selected to sort the Data Set. This list is based on the View selected in the Customized Data Wizard - Select a Data Set screen. Use the Add / Remove buttons to select from this list of data fields. Added items are removed from this list and moved to the Selected Columns list. The list of data fields that you have selected to sort by. Use the Up / Down buttons to select the sort order. The first item in the list is the first sort key. The next item is the second sort key, etc. If you do not select anything, data will be returned as it is read from the database.
Selected Columns
Customized Data Wizard - Set Data Filters

Use this screen to select any filters for this Data Set. TIP: If you are exporting a very big log and only want the structure to create a custom report template, you may want to filter (e.g. exporting all activity logs may be very large, but filtering for 1 week will contain the same structure with much less data).
Filter Column The list of data fields that can be filtered is based on the View selected in the Customized Data Wizard - Select a Data Set screen. Highlight the item you want to filter. The bottom of the screen displays the available filter options. Shows the filter that will be applied to the corresponding data field. If the value is blank, no filter will apply (all data for the field will be returned).
Filter Value
Customized Report Wizard - Confirm Report Summary

This screen shows a summary of the Customized Report you are about to view. You can select Close Wizard ... if you want to exit the Customized Report Wizard once the report is generated.
Customized Report Wizard - Select Report Template

Use this screen to select the Custom Report you wish to generate.
Template Name File Name Query String (Java DS-User only) Select from the available custom reports. Shows the path to the custom report template file. Shows the internal Query that was specified when the report was created in the third-party application.


Confidential.
View
Shows the original View that the Data Set was based on.
Customized Report Wizard - Set Data Filters

Use this screen to filter the Customer Report for specific data. Note that you do not need to make any selections in this screen.
Filter Column Filter Value A list of all fields appears. Highlight the item to add a filter. If blank, the default selection (usually <All>) applies. Otherwise, the filter value appears. You can specify the filter for this column in the bottom section of this screen.
Detailed Log Viewer

Use this screen to browse through the list of items processed by an activity.
Logged File(s) List Action: action applied to the corresponding file. Time: time the activity processed the file. Status: result of the activity processing. Last Modified: time the processed file was last modified (as a backup source). Size: (in bytes) Online Path: Path useful for troubleshooting with your Service Provider. Path: Path of the backup source file. This is the field that can be searched using the Path Filter. (For EMail backups, this contains the Subject line of the E-Mail.) Path Filter The string entered in this field used to search the Path field from the Logged Files(s) List. Default is *, meaning ALL. The filter is used alone, or with the selected options (Case Sensitive, REGEX, Negate). Check to apply the option to the filter. Case Sensitive REGEX: Perform a REGEX pattern check. You must know the REGEX syntax. (For a brief description of the syntax, see: Regular Expression screen.) Negate Click to search this Detailed Log for files matching the Path Filter.
Filter
Options
Find
Details screen
LAN STORAGE DISCOVERY TOOL / ONLINE FILE SUMMARY TOOL
File List Backup Set / Share Name Directory File Backup Time / Last Scan File Size Duplication Name of the backup set or share. Directory. Filename. Backup time (online files) or last scan time (LAN). Size in bytes. Level of duplication of the file (e.g. 10 means ten duplicates of the file exist Online or on the LAN).


Confidential.
Duplicate ID
Each file is scanned and an ID is generated for it. Any duplication (multiple instances of the same file elsewhere on the LAN or Online) will be identified by the same ID.
Last Modified (LAN File Summary Only) Time the file was last modified. Last Accessed (LAN File Summary Only) Time the file was last accessed. Description Show Duplicates Any additional details. Opens the Show Duplicates screen for the highlighted file. Allows you to view all the duplicates of a single file. Highlight a file in the list and click the Show Duplicates button.
Disc / Tape Mailing Information screen

Use this screen to enter your mailing information for your Disc/Tape shipment.
Name Phone Address This must be a valid street address where a major courier is able to deliver.
DS-Client Configuration Advanced Tab screen

Use this screen to view and change the Advanced DS-Client parameters. For details about each parameter, see the Knowledge Base Article DSClient Advanced Configurations on page 458. WARNING: Changing any of these parameters will have a significant impact on this DS-Clients performance.
A drop-down list that sorts the different types of parameters. Reset: Click to return all parameters in the selected category to their default setting. Category Note: Windows DS-Clients have additional radio buttons for Grid DS-Clients: Global: applies to all DS-Clients in a Grid DS-Client configuration. DS-Client Node: applies only to this specific Leaf-Node in a Grid DS-Client configuration. A drop-down list of the Parameter names. Reset: Click to return the selected parameter to its default setting. Depending on the type of Parameter, this can be a field or a drop-down list. Shows the current configuration for this Parameter. This field can help for Parameters that require a DS-Client restart. Since the Configured Value will not change when you click Apply, the Effective Value shows what the Parameter setting will be (after restart). Yes: DS-Client must be restarted before the changes take effect. No: Changes apply as soon as you click Apply in this screen. Click to return all parameters (in all categories) to their default setting. Contains a description of the parameter and value(s).
Parameter Value Configured Value Effective Value Restart DS-Client Reset all parameters Description


Confidential.
DS-Client Configuration Connections Tab screen

Use this screen to view and change the DS-System connection setup.
DS-System connection setup Each line in this list represents a DS-System connection entry. At least one entry must exist (Primary) in order for this DS-Client to connect to the DS-System. Primary: A Yes in this column indicates if the corresponding entry is the primary connection. The DSClient always attempts to connect to DS-System using the Primary connection first. All other entries on each different line in this list are alternates (indicated by No). Alternate DS-System connection entries are only attempted if the Primary DS-System cannot be reached (the alternate connection attempts will be made in the same order as they appear in this list). DS-System IP Address 1: This column shows the IP address or DNS host name the DS-Client will use to connnect to the DS-System. DS-System IP Address n: (OPTIONAL) DS-Systems with multiple nodes may require an address for each node. Additional addresses appear in incremental columns to the right for each additional addresss provided. This is only necessary if your Service Provider supplies you with the additional addresses. Add / Modify / Delete Test Connection Click this button to add, modify, or delete connection entries in the connection setup table. You must click OK in the Configuration screen to confirm any modifications. Click this button to test if the DS-Client can connect using the highlighted DS-System connection entry.
Internet Connection Configuration (For Backup from the Cloud Salesforce.com backup sets only.) This section allows you to configure the DS-Client to use a proxy server to access the Internet when connecting to the Salesforce.com site. Use a proxy server to access Internet: Select to enable this option. Address: Enter the address (DNS name or IP address) of the proxy server that the DS-Client will use. Port: You must specify the port that will be used to connect to the proxy server. (By default, this is port 80.)
DS-Client Configuration Defaults Tab screen

Use this screen to change the default options. New backup sets will carry these settings by default (which may be changed).
Generations setup Online ... generations Default Retention Rule Backup options Backup permissions Backs up the file permissions. (ex: ACL on NTFS volumes, or Trustees on NetWare volumes.) Indicates how many older generations of a backup file should be kept Online. You can select a default Retention Rule (or create a new one). Click [...] to open the Select Retention Rule screen.
Open files (Windows DS-Client)


Confidential.
Default Operation
Select from the list of operations: Try deny write: Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), place the backup file in 'Allow Write' mode. Deny write: This mode prevents any other process from writing to the backup file, while the DS-Client has it open. DS-Client will not back up the file, if another process has already opened it for write. (However, you may instruct the DS-Client to retry backing up the open file.) Prevent write: Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), then open in Allow Write mode and lock the file, thereby preventing any process from writing to the file. This ensures that the most recent version of the file is backed up. Allow write: Allow another process to read/write to the backup file (no restrictions). Since other applications can write to the file while it is being backed up, this may affect file consistency. Specifies the number of times you want the DS-Client to attempt to backup the file. (Maximum of 10 retries). Specifies the interval between retries. (Maximum of 999 seconds). Select from the list of defined schedules. Click to create a new schedule. You can add a single default notification that will apply to new backup sets. Click to add a new notification, or edit the existing default notification. Opens the Add / Edit Notification screen (See: Add Notification screen) Click to delete the existing default notification. You can select the default compression type that will be assigned to new backup sets: LZOP: A faster compression than ZLIB, that comes at the expense of less compression. ZLIB: This compression method will normally produce better compression than LZOP, but will take more time to compress.
Retry times Retry interval (sec) Backup schedule List New Notification Notification Add / Modify Delete Data Compression
Compression Type
Choosing the best default compression: ZLIB is a good default compression for backup environments where the bottleneck (the slowest transmission point during the backup activity) is the network. LZOP is a good default compression when the network is not the bottleneck. For example, when you are using a LAN speed connection and want backups to finish as fast as possible.
DS-Client Configuration Notification Tab screen

Use the Notification Tab to configure the way DS-Client will send notifications. DS-Client notifications (specified in backup set properties) are E-Mail reports or pager alerts that may be sent to the Administrator at the end of a backup session or, on a regular basis during Admin processes.
Outgoing E-Mail settings Send E-Mail through SMTP Server (SMTP only) None SMTP MAPI (Windows DS-Client only) Shows the SMTP server. Click [...] to configure this setting. Opens the SMTP settings screen.
Confidential.

From (E-Mail Address) (SMTP only) From (Display Name) (SMTP only)
Enter the E-Mail address from which you wish to send notifications. Recipients will see this address in the From field of their E-Mail notifications (their reply function will use this address). Enter the name (or other text) you would like to appear in the From field of the notification E-Mail. Recipients will see this text in the From field of their E-Mail notifications (before the E-Mail address). Select the Mail Profile for DS-Client to use. Mail Profiles are maintained by your mail client. DS-Client currently supports only one mail client: Microsoft Outlook. If no Profiles are listed, the mail client is not installed or no profiles were created under the DS-Client service account. To create a Mail Profile, see the Setting up DS-Client Notifications Knowledge Base article. Specify what appears in the subject line of notification E-Mails for backup activities. This field has a limit of 256 characters. You can enter any text and combine it with the Backup activity placeholders. When a notification is sent, any placeholder is replaced with the corresponding data from the DS-Client database. If you leave this field blank, a default subject line appears showing DS-Client ({DSC_NUMBER}): {BACKUP_RUN_RESULT} '\\{BACKUP_SOURCE}\{BACKUP_SET_NAME}({BACKUP_SET_OWNER})'. Placeholders are case-sensitive and must be entered between the { } brace characters. Backup activity placeholders: {DSC_NAME} // DS-Client computer name {DSC_NUMBER} // DS-Client Number {BACKUP_SET_NAME} {BACKUP_SET_OWNER} {BACKUP_SOURCE} // Backup source host name {BACKUP_RUN_RESULT} // Backup activity finished or not, with {N} errors. {USER_NAME} // user that initiated the activity {BACKUP_STATUS} // backup result will return one of the following: {ERROR}, {WARNING}, {SUCCESSFUL}, or {INCOMPLETE}. Specify what appears in the subject line of notification E-Mails for Admin activities (Daily and Weekly). This field has a limit of 256 characters. You can enter any text and combine it with the Admin activity placeholders. When a notification is sent, any placeholder is replaced with the corresponding data from the DS-Client database. If you leave this field blank, a default subject line appears showing DS-Client ({DSC_NUMBER}) {ADMIN_TYPE}. Placeholders are case-sensitive and must be entered between the { } brace characters. Admin activity placeholders: {DSC_NAME} // DS-Client computer name {DSC_NUMBER} // DS-Client Number {USER_NAME} // user that initiated the activity {ADMIN_TYPE} // admin activity type: Daily admin or Weekly admin
Profile (MAPI) (Windows DS-Client only)
E-Mail notification subject
Backup activity
Admin activity
Administrator Setup section


Confidential.
Admin E-Mail
Specify the Administrator's E-Mail address. DS-Client can send notifications to multiple E-Mail addresses if you separate them with a comma (,) or semicolon (;). Test: Click this button to test the notification configuration. DS-Client will send a notification to the destination E-Mail(s). Check the E-Mail account(s) to verify the configuration works. If the Administrator can be paged by E-Mail, specify the pager E-Mail address. The format of this field is the same as for Admin E-Mail. DS-Client can send notifications to multiple E-Mail addresses if you separate them with a comma (,) or semicolon (;). Test: Click this button to test the notification configuration. DS-Client will send a notification to the destination E-Mail(s). Check the pager(s) to verify the configuration works. This will send a summary E-Mail to the Admin E-Mail account. It will contain a summary of Admin process information and backups processes (since the last Daily / Weekly Admin process). Includes the backup details with the summary. (Send summary must be selected.)
Pager E-Mail
Daily / Weekly Admin Setup section Send summary Send backup details
Send E-Mail using HTML (E-Mail only). Check this box to send the summary in HTML format. Otherwise, it Format will be sent in plain text format.
DS-Client Configuration Parameters Tab screen

Use this screen to view and change the DS-Client parameters. You may schedule the Administrative process times (these processes should be scheduled to avoid conflict with the scheduled backups).
Admin Process Daily start field Weekly start field Every Reboot after admin Enter the time when you want to begin the Daily Admin. Process. Clear this field to disable scheduled Daily Admin. Processes. Enter the time when you want to begin the Weekly Admin. Process. Clear this field to disable scheduled Weekly Admin. Processes. Select the weekday to run the Weekly Admin. Check this box to reboot the DS-Client computer after an Admin. process is completed. Select how DS-Client handles CDP backup sets when the Daily Admin / Weekly Admin is scheduled: Skip: Admin will skip any running CDP backup sets Suspend: Admin will suspend any running CDP backup sets, then restart them once the Admin is finished. [Standalone Windows DS-Clients using the free Microsoft SQL Server Express for their database.] Select to enable this feature. This will allow the DS-Client database to grow beyond the stated Microsoft limits for individual databases (4GB for SQL Server Express 2005 / 2008; 10GB for SQL Server Express 2008 R2). For more information, see the Knowledge Base article: DS-Client Database (Automatic Expansion) on page 421. Use this drop down list box to select the DS-Client Database Backup option. This is a disaster recovery service option that saves the DS-Client database to the DSSystem. You may select with Daily, with Weekly, or None.
CDP Strategy
Automatically Expand DS-Client Database
Database options DS-Client Database Backup


Confidential.
DS-Client database dump file (MS SQL Server only)
Choose what to do with the DS-Client database dump file: Do not delete: The file remains in the DS-Client Buffer until it is overwritten. Delete after successful backup: The file is deleted after it has been successfully backed up to the DS-System. Always delete: The file is always deleted after a Daily Admin or Weekly Admin. For more information, see the Knowledge Base article: Administrative Processes on page 491. Choose the period that you would like to maintain System Logs on the DS-Client. You may select either six months, or from one to seven years. If the connection between the DS-Client and DS-System is lost during a backup, the DS-Client will automatically attempt to reconnect this number of times. (Note: A zero value means no reconnection will be attempted.) Note: This applies to Scheduled and On-demand backups. Shows the interval (in minutes) between reconnection attempts. On: (Default) If selected, DS-Client skips running a pre-scan on all scheduled backup sets (this makes the process faster). Off: Uncheck to force a pre-scan for all scheduled backup sets. Note the potential performance implications, however you will be able to view an estimated completion time for each scheduled backup set in the Process Window screen. Specify the local disk location that DS-Client will use to save Use Buffer dumps and its own Database dumps (from Daily/Weekly Admin activities). Grid DS-Clients: This is the Global Setting for all nodes of the Grid DS-Client. To change the buffer for each node individually, click on the Advanced Tab (DS-Client Configuration Advanced Tab screen). For more information see DS-Client Knowledge Base Article "DS-Client Buffer". Specify the default path that will be used for backup sets configured to use one of the features that require a local storage path (Self-Contained Backup Sets, Local-Only Backup Sets, Save on Local Storage, Use Local Storage Cache). This option is enabled per backup set (Set Properties - Options tab). IMPORTANT NOTE: Backup sets that use any local storage location require an extra table in the DS-Client database in order to manage the data stored on the DS-Client side. Make sure enough space is allocated for the DS-Client database when using any feature that requires a local storage path.
Keep DS-Client logs Backup Options Attempt to reconnect [...] times Intervals
Skip pre-scan for scheduled backups
DS-Client Buffer
Local Storage Path
DS-Client Configuration Roles Tab screen

Use this screen to view and change the User / Group Roles configuration.
Users & Groups Role A list of Users and Groups and the Roles assigned to them. Icon: Identifies if the Role applies to a User or Group. User / Group: Name of the User or Group. From: Computer or Domain from which the User or Group will be Authenticated. Role: Administrator, Backup Operator, or Regular User. Add Modify Delete Click this button to add a User or Group to the Users & Groups Role list. This opens the New / Edit User / Group Role. Click this button to modify the highlighted item from the Users & Groups Role list. This opens the New / Edit User / Group Role. Click to delete the highlighted item in the Users & Groups Role list. You must click OK in the Configuration screen to confirm any modifications.


Confidential.
DS-Client Configuration Setup Tab screen

Use this screen to view the configuration options for your DS-Client. These settings are established during the DS-Client Installation.
DS-Client setup section Account name Account # DS-Client # Modify (Linux / Mac DS-Client only) Your customer account name. Your customer account number on DS-System. This DS-Client's number on DS-System. Click to modify this DS-Clients customer registration information. This opens the Initial DS-Client Configuration / Modify DS-Client Configuration screen. Click to re-register this DS-Clients hardware installation with the DSSystem. This must be performed together with your Service Provider, who must permit the DS-Client to re-register. For details, see: Re-register the DS-Client with the DS-System on page 33.
Register Now
Encryption setup section This section shows whether the DS-Client's encryption keys are set. Once set, they cannot be changed. DS-Client private key set Account key Key used to encrypt files specific only to your DS-Client. Each DS-Client has a unique key, but DS-Clients from the same Customer share a common Account Key.
Encryption key safeguard section This section allows you to decide the Encryption Key safeguard policy. Enable encryption key forwarding to DS-System Forward Now Request Deletion Check to enable DS-Client to forward its encryption keys to the DSSystem. They will be stored in the DS-System database, in an encrypted format. DS-Client private key: indicates if this key has been forwarded. Account key: indicates if this key has been forwarded. Forward the key(s) immediately to the DS-System. Instruct DS-System to delete the forwarded encryption key(s) from its database.
DS-Client Configuration SNMP Tab screen

The SNMP tab allows you configure DS-Client to work with SNMP to send traps. (You need to have SNMP management software installed if you wish to receive and handle the trap information).
Destinations Section Community Add to List Remove Communities are groups of hosts to which a server running the SNMP service belongs. You can specify one or more communities to which the Windows NT computer that uses SNMP sends traps. The community name is placed in the SNMP packet when the trap is sent. Click Add to List / Remove to add or remove from the Community list. A list of Host Name(s) or IP Address(es) belonging to the Community selected from the list. Click the corresponding button to add, edit, or remove a destination host or IP address to the list. Check to activate. Select the frequency from the minutes list.
Destination Host List Add Edit Remove Send Traps as heartbeats every ...

Confidential.
Notes 1) Load the asigra.mib file (found in the DS-Client installation directory) with your SNMP software to receive the traps sent by DS-Client. 2) Trap Contents (For OID description, refer to "asigra.mib" file.) Trap Contents for heartbeat timestamp sender's IP Address sender's OID Varbind OID Type Data OID for the heartbeat Integer 0 trap time DS-Client IP OID for "DS-System Traps"
Trap Contents for others timestamp sender's IP Address sender's OID Varbind OID Type Data is a flag OID for the specific event Integer 0: New event, 1: Repeat event. trap time DS-System IP OID for "DS-System Traps"
DS-Client Grid Log

[Grid DS-Client] The Grid Log displays all events specific to the Grid configuration.
Icon - Shows the severity of the corresponding event. Time - Shows the date and time of the corresponding event. Node ID - Shows the Grid ID of the Node for the corresponding event. IP Address - Shows the IP address of the Node for the corresponding event. Event - Shows the event ID Text - Shows additional information for the corresponding event. From - Type the earliest date you want to display in this field. No events older than this time will be displayed. To - Type the latest date you want to display in this field. No events newer than this date and time will be displayed. Event Type - Select a specific event type if you want to see only messages of that type. The default selection is <All>.
Event List
Select by
DS-Client System Status screen

The DS-Client System Status screen allows an administrator the flexibility of viewing detailed information about Network and Database connections as well as message queues.


Confidential.
This screen also permits an administrator to send messages to users and disconnect users from the DS-Client System. It is important to note that this screen is a snapshot of the activities on the system at the current moment. This screen is useful as a troubleshooting tool.
Node ID (Grid DS-Client) Select which Node of the Grid DS-Client to view.
Cached Buffers Number of cached buffers. (Windows DS-Client) In KB/Sec Shows rate that data is being received to indicate the throughput on the DS-Client. (Windows DS-Client) Out KB/Sec Shows rate that data is being sent to indicate the throughput on the DS-Client. (Windows DS-Client) Refresh Click this button to update the display. This screen contains the following tabs: Network Connections Tab Database Connections Tab Message Queues Tab (Windows DS-Clients) Threads Tab (Windows DS-Clients) CORBA Connections Tab (Linux / Mac DS-Clients)
Tabs
Network Connections Tab Connection List Type: Type of connection that has been established (ex: Backup, Restore, User). Name: Name of the user associated with the network connection. In Queue: Position where the connection stands in the receive message queue (if applicable). Out Queue: Position where the connection stands in the send message queue (if applicable). Create Time: Time when the connection was established. Description: Shows more detailed information about the connection, such as backup destination (if applicable). ID: Connection ID number for the highlighted connection. Send Message Disconnect Cached Buffers (Linux DS-Client) In KB/Sec (Linux DS-Client) Out KB/Sec (Linux DS-Client) Click to bring up the Enter Message screen. A message will be sent to the highlighted user(s). Click to disconnect the highlighted user(s). Number of cached buffers. Shows rate that data is being received to indicate the throughput on the DS-Client. Shows rate that data is being sent to indicate the throughput on the DS-Client.
Database Connections Tab Connection List In Queue: Place where the process stands in the receive message queue (if applicable). Process Start: Time when the process began. Name: Name of the process in the message queue. Description: Contains details about the connection (if available). ID: Connection ID associated with the process. Message Queues Tab (Windows DS-Clients) Queue List In Queue: Place where the process stands in the receive message queue (if applicable). Process Start: Time when the process began. Name: Name of the process in the message queue. ID: Connection ID associated with the process.


Confidential.
Threads Tab (Windows DS-Clients) Thread List Thread ID: Unique thread ID. ID: Connection ID associated with the process. Description: Shows details of the process. CORBA Connections Tab (Linux / Mac DS-Clients) This tab is specific to SAP backup sets. CORBA Connection List User: User who is logged into DS-Client. Objects: Internal CORBA ID. IOR: Internal CORBA ID.
DS-Client Version Info

This screen shows additional information about the DS-Client and items that are associated with it.
Item List Item Value Shows the name of an item. Shows the corresponding value for the item (e.g. version number, build number, etc.).
DS-Clients Auto Search (Print Global Report)

(Java DS-User only) This screen displays all the running DS-Clients visible to the Java DS-User.
DS-Client List Add Selected To select multiple DS-Clients with your mouse, press the CTRL-key. DS-Clients - Computer name of the DS-Client Description - Shows the DS-Client Customer Account Name IP Address - IP address of the DS-Client Click to select the highlighted DS-Client(s).
DS-NOC Settings
This screen only displays information if this DS-Client is being monitored by a DS-NOC server. These settings are configured on the DS-NOC and pushed to this DS-Client through the DS-System.
DS-NOC Settings This section is Read-Only. Monitored by DS-NOC DS-NOC Address DS-System Name Connection Frequency (to DS-NOC) Retry When Failure (to connect to DS-NOC) Last Connection (to DS-NOC) Last Successful (connection to DS-NOC) Proxy Server Check New Settings Connect to DS-NOC Configure this DS-Client to use a proxy server to connect to the DS-NOC. Connects immediately to the DS-System to obtain the latest settings. (DS-Client will check for updated settings on every connection to DS-System.) Connects this DS-Client to the DS-NOC server to update its monitoring information.


Confidential.
DS-NOC Proxy Server Settings

This screen allows you to configure the DS-Client to use a Proxy Server when connecting to the DSNOC.
No proxy (Default) If selected, the DS-Client will connect directly to the DS-NOC.
Auto-detect proxy If selected, DS-Client will try to find the Proxy Server automatically. settings for this network For more details, see: Auto-detect Proxy Server on page 301. Manual proxy configuration If selected, you must enter the address of the Proxy Server in the corresponding fields, including the port number to use. Use the same proxy server for all protocols: Select to use only one Proxy Server address and port number for both HTTP and HTTPS connections. For more details, see: Manual Proxy Server Configuration on page 301. If selected, you must enter a URL to a Proxy Auto Configure file accessible to the DS-Client. The DS-Client will obtain the proxy server address and port number to use from this file. Enter the full URL in this field, starting with http:// For more details, see: Automatic Proxy Server Configuration URL on page 302.
Automatic proxy configuration URL
Server requires authentication If required, supply the credentials to the Proxy Server here. User Name Password Confirm
DS-User Initialization - Connection (Java)

(Optional this screen can be left empty. If empty, the GUI will scan the local computer and the local computers subnet. Applies to Java version only.) Use these settings to indicate a specific IP or DNS address for a DS-Client. This can speed up your login in larger network environments.
LAN search time ... Additional DS-Clients New Modify Remove Additional Subnets New Modify Remove Add a new subnet to the search list. This Java DS-User will search for any DS-Clients on the specified subnet(s). Opens the Add / Modify Subnet (Java DS-User) screen. Modify the highlighted subnet entry. Remove the highlighted subnet entry. Add a new DS-Client IP or DNS address to the search list. Opens the Add / Modify DS-Client (Java DS-User Initialization) screen. Modify the highlighted DS-Client entry. Remove the highlighted DS-Client entry. Time (in seconds) DS-User will spend scanning the LAN for DS-Clients. If you set this value to 0 the DS-User will not search the LAN. Only the local DS-Client will appear in the DS-Client(s) Connection List (if it is running).
Logon using security context These options are for Windows DS-Client only. The network credentials used are only for logging into the DS-Client (local or remote). They are not used for creating backup sets. Creating backup sets always requires input of specific user credentials. For more information, refer to the Knowledge Base Article Logon using security context on page 455.


Confidential.
Target Name
(Optional - this field can be left blank, particularly if you are only connecting to the local DS-Client.) The name in this field is only used if this DS-User GUI is connecting to a DS-Client located in a Windows Domain. The default Target Name is CloudBakSvc. You must have your network administrator create and register this Target Name (or any other name you choose to use) with Active Directory using a tool like Microsoft setspn.exe provided with Windows Support Tools. This is an advanced configuration option that requires the assistance of a network administrator. For more information, refer to the Knowledge Base Article Logon using security context on page 455. This configures how this installation of the DS-User GUI will behave when it launches. Last DS-Client: This DS-User GUI will search for the last DS-Client it successfully connected with. If that DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Local DS-Client: This DS-User GUI will search for the local DS-Client. If the local DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Last or Local DS-Client: This DS-User GUI will search for the last connected DS-Client first. If the last connected DS-Client is found, DS-User will attempt to connect using the already logged on user credentials from the current Windows login session (provided that the same username and password is provided). If however, the last connected DS-Client is not available DS-User will connect to the local DS-Client using the current security context. Local or Last DS-Client: (Default) This DS-User GUI will search for the local DS-Client first and connect using the current security context. If the local DSClient is not found, DS-User will attempt to connect to the last connected DSClient using the current security context (provided that the same user network credentials are used, and that the local user exists on the remote DSClient, and appropriate user permissions are there in the remote DS-Client). Disabled: Users can select this option to turn off the auto-connect functionality. Users will see the Connect to DS-Client Service screen at GUI startup.
Auto-connect
DS-User Initialization - Connection (Win32)

(Win32 only) By default (if this screen is left empty), Win32 DS-User automatically detects the local DS-Client and all other DS-Clients on the same subnet as this Win32 DS-User installation. This screen allows you to configure the specific IP address(es) or subnet(s) where this DS-User will look for additional DS-Clients (for remote management).
Additional DS-Clients New Modify Delete Additional subnets New Modify Delete Adds a new entry to the Additional Subnets list. Opens the Connection Configuration screen. Modifies the highlighted item from the Additional Subnets list. Opens the Connection Configuration screen. Deletes the highlighted item from the Additional Subnets list. Adds a new entry to the Additional DS-Clients list. Opens the Connection Configuration screen. Modifies the highlighted item from the Additional DS-Clients list. Opens the Connection Configuration screen. Deletes the highlighted item from the Additional DS-Clients list.


Confidential.
Logon using security context These options are for Windows DS-Client only. The network credentials used are only for logging into the DS-Client (local or remote). They are not used for creating backup sets. Creating backup sets always requires input of specific user credentials. For more information, refer to the Knowledge Base Article Logon using security context on page 455. (Optional - this field can be left blank, particularly if you are only connecting to the local DS-Client.) The name in this field is only used if this DS-User GUI is connecting to a DS-Client located in a Windows Domain. The default Target Name is CloudBakSvc. You must have your network administrator create and register this Target Name (or any other name you choose to use) with Active Directory using a tool like Microsoft setspn.exe provided with Windows Support Tools. This is an advanced configuration option that requires the assistance of a network administrator. For more information, refer to the Knowledge Base Article Logon using security context on page 455. This configures how this installation of the DS-User GUI will behave when it launches. Last DS-Client: This DS-User GUI will search for the last DS-Client it successfully connected with. If that DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Local DS-Client: This DS-User GUI will search for the local DS-Client. If the local DS-Client is not available, the DS-User will prompt the user to choose the desired DS-Client. Last or Local DS-Client: This DS-User GUI will search for the last connected DS-Client first. If the last connected DS-Client is found, DS-User will attempt to connect using the already logged on user credentials from the current Windows login session (provided that the same username and password is provided). If however, the last connected DS-Client is not available DS-User will connect to the local DS-Client using the current security context. Local or Last DS-Client: (Default) This DS-User GUI will search for the local DS-Client first and connect using the current security context. If the local DS-Client is not found, DS-User will attempt to connect to the last connected DS-Client using the current security context (provided that the same user network credentials are used, and that the local user exists on the remote DS-Client, and appropriate user permissions are there in the remote DS-Client). Disabled: Users can select this option to turn off the auto-connect functionality. Users will see the Connect to DS-Client Service screen at GUI startup.
Target Name
Auto-connect
DS-User Initialization - Fonts

(Optional JAVA Only this screen can be left empty) DS-Users default fonts may not be enough to display some Unicode characters. In these cases, you can add specific fonts that the DS-User will attempt to use (in order) to display such characters.
Additional Fonts Add Remove Move Up Move Down This is the list of fonts you have added to the DS-User. Add a new font. Opens the Select Font screen. Removes the highlighted font from the Additional Fonts list. Moves the highlighted font up in the Additional Fonts list. Moves the highlighted font down in the Additional Fonts list.


Confidential.
DS-User Initialization - Keep Alive

These settings limit the amount of idle time on DS-User, after which the connection with DS-Client will be terminated..
Keep Alive Settings Send "Keep Alive" probes when a If DS-User does not receive data from DS-Client for this period of time, connection is idle for [...] sec- DS-User will start to send "Keep Alive" probes to detect if the DS-Client onds is running. Send keep alive probes every [...] seconds Once DS-User starts sending "Keep Alive" probes, it will repeat sending probes at this interval until it receives a response, or the maximum number of probes is sent.
Terminate Connection after try- DS-User will terminate the connection with DS-Client after it has tried ing [...] times this number of "Keep Alive" probes without response.
DS-User Initialization - Language

(Win32 only) This screen controls the GUI language settings. Select from the available languages. You must restart DS-User before the new settings take effect. Note: You can only change the GUI language if the required files are installed. Otherwise, the radio buttons will be disabled.
DS-User Initialization - Look & Feel

(Optional this screen can be left empty.) Applies only to the Java version with the Metal theme selected (Setup > Look & Feel > Metal). Use these settings to customize the look of the GUI.
DS-User Initialization - Plugins

(Optional this screen can be left empty. Applies to Java version only.) Some plugins are automatically applied, depending on the DS-Client's configuration. Others can be manually enabled / disabled, and configured.
Enabled Description Configure Use the checkboxes beside each listed plugin to enable or disable that feature. Short description of the available plugin. Click to configure the highlighted plugin. (Some plugins do not have configuration options.)
DS-User Initialization - Regional

(Optional this screen can be left empty. Applies to Java version only.) Use these settings to change or customize the date and number formatting.
GUI Language Format Using Custom Formatting Date Format Strings Select a language from the list available. You must exit and restart DS-User before the new settings take effect. Select a language. The standard formatting conventions of that language will be used. Select to specify your own formatting for each of the available data types. You can customize these strings, as required.
Number Format Strings You can customize these strings, as required.


Confidential.
Duplicates screen
LAN STORAGE DISCOVERY TOOL / ONLINE FILE SUMMARY TOOL Shows the duplicate instances of a particular file version (same size, date, etc.). Use this list to manage the redundant data you have. If it is online, you can delete some versions. If it is on the LAN, you may choose to rearrange the location(s) to save space.
Backup Set / Share Name Directory File Backup Time / Last Scan Description Shows the backup set (online) or share (LAN) containing the duplicate file instance. Shows the directory where the file is located. Shows the filename. Shows the backup time (online) or last scan time (LAN). Additional information (if any).
Enter Database Credentials screen

Connect as Password Enter a valid user name to the selected database. Enter a valid password for the user name.
Specify the Service Name. You must know the name of the database you wish to Service (ORACLE) backup.
Enter Lock Key For Credentials (Print Global Report)

(Java DS-User only) This screen allows you to enter the key to lock / unlock the list of DS-Client Connection Entry credentials: Load: Unlocks the list of DS-Client Connection Entry credentials in this Java DS-User installation to the Select DS-Client (Print Global Report) screen. Save: Locks the list of DS-Client Connection Entry credentials in the Select DS-Client (Print Global Report) screen with this Java DS-User installation.
Enter Local Storage Path

This screen allows you to specify the Local Storage path for a specific backup set. If you do not specify a path, the Local Storage Path configured in the DSClient Configuration Parameters Tab screen will be used.
Enter Message screen

Send Message Send Type any message text Click to send the message.
Enter NAS API Parameters (Windows DS-Client)

This screen allows you to enter the NAS API credentials and parameters. You can click [...] beside any User Name field to browse for an encrypted key file (one that contains the user credentials). If

Confidential.
the file is valid, you must enter the correct key to unlock the file. Opens the Enter unlock key screen.
NAS NAS Type API Protocol Port Number User Name Password NAS API Parameters and Credentials Specifies the NAS device type, vendor or specific model. Currently supported types: NetApp FAS filers Specifies the protocol for accessing the API. Commonly used protocols are HTTP or HTTPS. The specific protocol must be enabled on the NAS device. Specifies the port number for accessing the API. The specific protocol must be open on the NAS device. Specifies the User Name for a user on the NAS device. This user requires permissions to execute the API commands on the NAS device and usually needs to be a member of the Administrators group. Specifies the corresponding password for the NAS user.
Enter Restore Path (MS SQL Server)

This screen allows you to specify the restore path for the databases log or data files.
Enter unlock key

Use this screen to provide the key to unlock the credentials stored in the file. For more information on this option, refer to the Knowledge Base article Encrypting your Network Credentials.
Event Filter
The Event Filter allows you to alter the Event Log by over-ruling an events default severity with your custom setting.
Event Filter List Icon Event # Category Description New Edit Remove OK Shows the severity of the event that occurred: Information message. Warning message. Error message. Contains an event ID code. Shows the category of the message. The category can be any of the categories listed in the event Category drop down list. Displays a description of the highlighted event. Click to add a new event filter. Opens the Add / Edit Event Filter screen. Click to edit the highlighted filter from the Event Filter List. Opens the Add / Edit Event Filter screen. Click to remove the highlighted filter from the Event Filter List. Click to save the settings as configured in the Event Filter List.


Confidential.
Event Log Viewer screen

Use this screen to examine the Event Logs. This displays the error, warning, and information messages that occurred during DS-Client activities for the period selected. If you highlight an event, the full text of the description column will appear in the description section.
Event List Icon Time User Category Event # ID Text Node ID (Grid DS-Client) Description Select By Section From To Type User Category ID Event # Exclude Find Type the earliest date you want to display in this field. No events older than this time forward will be displayed. Type the latest date you want to display in this field. No events newer than this date and time will be displayed. Select a specific event type if you want to see only messages of that type. The default selection is <All>. Enter the name of a particular user, if you want to search for only that one person's events. Select a specific type of event if you want to see only event of that type. The default selection is <All>. Enter a specific ID, to see only those events associated with that ID. Enter a specific Event Number, to see only those events of that type. Click to edit a list of error IDs to exclude from the list of Events. Opens the Exclude Event # screen. Updates the event log display based on the Select By parameters. Shows the severity of the event that occurred: Information message. Warning message. Error message. Shows the date and time that the event occurred. Shows the name of the user associated with the event (if any). Shows the category of the message. The category can be any of the categories listed in the event Category drop down list. Contains an event ID code. Contains the Session ID number associated with the event. This field may display the IP connection (if applicable). Contains the DS-Client node associated with the event. Displays a description of the highlighted event.
Exclude Event #
Use this screen to edit the list of events that will be excluded from Event Log searches. These exclusions only apply to the current Event Log that is open (it will be reset once you close that screen).
Event # Add Remove Clear You can manually enter an event number in this field. All events that you exclude appear in the exclude list underneath this field. Since event numbers tend to be long, you can use the Select button to choose from all events that occurred in the period covered by the Event Log. Click to add the number in the Enter # field to the exclude list. Click to remove the highlighted items from the exclude list. Click to clear the entire exclude list.


Confidential.
Select
Click to view all the events for the corresponding Select By period in the Event Log. Opens the Select Event # screen.
Exclude Old Files screen

Use this screen to exclude old files from backup for the corresponding backup set. (Note: The age of a file is determined by its Last Modified date.)
No exclusion At backup time, files older than the specified age will be excluded. Exclude files older than [...] days Note: If the backup fails, the exclude period will be extended to / weeks / months / years reflect the conditions of the failed backup, until a successful backup is completed. Exclude files older than [date] All files older than the specified date will be excluded from backup.
Export
(Win32 Only) Use this screen to select the file format, and destination where you would like to export the report data.
Format Destination Choose the format you want to save the report in from this drop down list. Choose where you want the report sent from this drop down list.
Export DS-Client configuration to XML

Windows DS-Clients: Use either Win32 DS-User or Java DS-User to export. (Note: The "Export to XML" feature is not supported for Local DS-VDR, Lotus Domino Server, or Permissions-Only backup sets.) Linux / Mac DS-Clients: Use Java DS-User to export.
Use this screen to export the DS-Client configuration, Backup Schedules, Backup Retention Rules, and Backup Sets to an XML file named config-update.xml.
DS-Client Configuration: exports all settings from the DS-Client Configuration screen tabs (Setup, Defaults, Notification, SNMP, Parameters, Connections, Roles). Backup Schedules: Exports all (or selective) Backup Schedules from this DS-Client. Retention Rules: Exports all (or selective) Retention Rules from this DSClient. Backup Sets: Exports all (or selective) Backup Sets from this DS-Client. [Note: Recovered orphaned backup sets that have not been migrated (or had their backup information for connection, backup items, and schedule re-specified) cannot be exported.] Expands or collapses the list in the Options window. Check to use a Meta Symbol wherever necessary. This will allow the XML file to be used interchangeably in different localization environments. For example: An XML configuration file made from an English installation of DS-Client will also work for a German DS-Client installation. Current Meta Symbols: %ComputerName% - the DS-Client computer name. %MSNetProvider% - the string representing the Microsoft Network Provider that is different depending on the localization of the operating system.
Options
Expand All / Collapse All
Meta Symbol (Windows DS-Client only)


Confidential.
Include Encryption Keys (Configuration must be checked) Save As
Check to include the DS-Client Encryption Key and Account Encryption Key in the XML file (they will be encrypted). Click to save the selected items to an XML file. To use this file, make sure it is named config-update.xml, and place it in the folder containing the DS-Client service.
Export Grid DS-Client Address

Exports the current Grid DS-Clients connection address information to a text file for quick distribution. The exported file can then be imported to any other DS-User installation using the Load button: For Java DS-User, use the Add a DS-Client screen. For Win32 DS-User, use the Connection Configuration screen.
Address Type Internal Address: This exports the internal (LAN) IP Addresses. This can be used to quickly configure other internal DS-User installations with this Grid DS-Client. External Address: This exports the external (WAN) IP Addresses (if they are configured). This can be used for DS-User installations or for other applications (like DS-Client SLA) if they need to connect to the Grid DS-Client from the WAN (external connection).
Extension Report screen

View by size List Top Report Customize Report Shows the graphic sorted by size. Shows the files sorted by extension specified. Allows you to search for the most frequent file extensions. Allows you to search for specific file extensions.
View by number of files Shows the graphic sorted by number of files
Failed Files During Backup

Use this screen to view files that failed to back up from the selected backup set.
File List Custom Exclude Exclude Shows a list of files that failed to back up. You can select all or some of the files from this list for exclusion. Select one of the failed files and check Custom Exclude. This will exclude all files in the same path with the same extension. You must click the Exclude button to apply this custom exclusion filter. Click to add the exclusion(s) to the backup set items.
File Filtering Option

Use this screen to define an individual option for a File Filtering Rule (for the list of Rule Options).
Rule for item Filter Rule
You must select one of the following: Inclusion - to include the files covered by the filter in the time-push. Exclusion - to skip the files covered by the filter (do not push).

Confidential.
File Filter
You must select one of the following: Filter - specify the filter pattern to apply. Directory - specify the online backup directory where you want to apply the filter. You must enter the full \\share_name\directory_path where the filter will be applied. For example C:\temp\files\ will archive files fitting the filter pattern from that specific path. Each filter must be applied to a specific directory path (do not leave this field blank). Include sub-directories - check to include all the sub-folders in the specified directory. Regular Expression can provide more specific filtering at the filename or file pattern level. However, you must learn the Regular Expression software syntax. Click [>>] to open the Regular Expression screen.
Regular Expression
File Filtering Rule

Use this screen to define a File Filtering Rule (for the list of Archive Rules).
Rule Name Enter a unique name to describe this File Filtering Rule. Make it as descriptive as possible, especially if you define several different rules.
Rule Options List Each item in the list is a separate file filtering option for this rule. Add Edit Remove Adds a new option to the list for this File Filtering Rule. Edits the selected option in the list for this File Filtering Rule. Deletes the selected option from the list for this File Filtering Rule.
File Size Report screen

List of large files discovered by the LAN Storage discovery tool: Share Directory Name Size Duplicates Modify Time Create Time Shows the largest [] number of files Searches only for files with many duplicates. This allows you to identify the location of the largest files on your network. In particular, you can see how many times they are duplicated on the LAN. Show results for all shares, or for a specific share. Click to search based on the options selected.
List
Select Top Duplicated at lest [] times Share Find
Files in Directory ... (Select Items for Backup) screen

This screen allows you to view / select specific: File(s) in a directory Database items (Linux DS-Client) Objects in a System i server library E-Mails in a directory


Confidential.
Tables in a database (Backup from the Cloud - Salesforce.com)

File Name: Shows the name of the file. File Size: Shows the original file size of the backup file. Last Modified: Indicates the date that the information in this file was last changed. Object Name: Shows the name of the System i Server object. Object Size: Shows the original object size. Last Modified: Indicates the date that the information in this object was last changed. E-Mail Subject: Shows the subject line of the E-Mail. E-Mail Size: Shows the original file size of the E-Mail. Received Time: Indicates the date that the E-Mail was received. File Name: Shows the name of the table in the Salesforce.com database.
File List / Item List
Object List (System i) E-Mail List (DS-MLR) Table List (Backup from the Cloud) Add / Select Exclude
Click to add the highlighted backup item(s) to the Selected Files for Backup List. If this button does not appear, it means this screen is read-only. Click to exclude the highlighted item(s) from the Selected Files for Backup List. (The parent directory must be selected for backup.)
File Info Click to view details about the highlighted file. (Show Archived Files only) Opens the Backup Generations for ... screen.
Find Backed Up File screen

The Find Backed Up File screen allows a user to search all of the files in the backup set for a specific file or file pattern.
Files List Generation Last Modified File Size File Name Directory Name File ID Shows the number of generations of the file stored online. Shows the last date and time that the file was modified. Shows the file size. Shows the file name. Shows the full directory path. Shows the ID of the file (automatically assigned by the DS-Client). Shows the ID of the directory (automatically assigned by the DS-Client). Note: File and Directory ID numbers are automatically generated by the DS-Client, and can be used for troubleshooting. This number is also the filename/ dirname used by the DS-System. [Default] Searches for files by name. Searches for files by their File ID. Enter the file name/ID number or file pattern (example: *.exe), in this field to search the selected backup set for that specified file/pattern. Check to search for only those files backed up from the selected session. (This option appears when searching from the Detailed Log.) Click to search the backup set for files of the specified pattern in the Name/ID field.
Directory ID
Search for File name File ID Name/ID From This Session Only Find
Select (Restore Only) Click to select the highlighted file.


Confidential.
Generate Global Report (Print Global Report)

(Java DS-User only) This screen allows you to view the progress as Java DS-User connects to each DS-Client and generates the Global Report. You can stop this process by clicking the Stop button.
Generate Reports screen

This screen lets you select the LAN Storage Discovery reports that you want to generate.
Select Reports Options Package all reports for DS-NOC Generate Check beside each report you wish to automatically generate. For each selected report (highlighted in the list), specify any required options in the right-side. [DS-NOC] Check to group a copy of all generated reports in a .ZIP file that can be uploaded to the DS-NOC. Generate selected reports. Opens a browse folder to select the location on the LAN where to save the reports.
Getting Started
Once you have successfully completed a full installation, you will find all the necessary applications in the corresponding Start Menu or Application folder. The two major applications on your system are DS-Client and DS-User. DS-Client is a service program. It is intended to run in the background at all times (this allows it to perform unattended backups when you are not at the computer). You can start and stop the DSClient with the DS-Client Service Manager. DS-User is the user interface that allows you to create Backup Sets and perform backups and restores using the DS-Client. To use DS-User, you must connect to a DS-Client that is running. You are prompted for your user credentials when you attempt to log into the DS-Client. Use the same credentials as you use to log in to your computer. The first time you successfully connect to the DS-Client, the New Backup Set Wizard pops up automatically. For more information, see Running DS-User and Connecting to a DS-Client on page 26.
Grid Status
[Grid DS-Client] The Grid Status screen gives you a visual display of the nodes on a Grid DS-Client.
This screen can display the following views: Graph View List View Grid Formation Main Node The Main Node will usually be the DS-Client service that started first. Once other Nodes that are configured as part of the Grid DS-Client start, they will join as Leaf Nodes. The Main Node instructs all Leaf Nodes about what activities to perform. It is the only one that listens for incoming DS-User connections. The Main Node also perform backup and restore activities with DS-System. A Leaf Node performs backup and restore activities with DS-System as instructed by the Main Node. It does not listen for incoming DS-User connections. A Leaf Node always maintains an open connection to the Main Node (via TCP port 4410).
Leaf Node


Confidential.
Graph View
Graph view shows a visual representation of the Grid status. Graph Layout: Select the layout for the graph (Linear or Star). List view shows information from the common Grid DS-Client database, sorted by node. ID: ID of the corresponding DS-Client node. Name: Server name of the corresponding DS-Client node. Address: IP Address of the corresponding DS-Client node. Type: Shows if the node is the Main Node, a DS-Client node (Leaf), or if it is not connected. Status CPU Usage (%) Activities Task Limits Memory Load (%) Memory Commit (MB) Send (Kilobytes/second) Receive (Kilobytes/second) At the bottom of the list is the Grid DS-Client database node.
List View
Stop Node (List View) Export Options
Allows you to stop the highlighted node in the list. Opens the Stop DS-Client Node screen. Allows you to export the IP Addresses of the current Grid DS-Client. Opens the Export Grid DS-Client Address screen. Refresh every [...] seconds: The graph or list is automatically updated at this interval.
Growth Report screen

View From To Interval Share Type Table of Time, Size, and number of Files Bar chart , sorted by size Bar chart , sorted by files Earliest date to search. Latest date to search. Interval between days in the list / chart. <All> or a specific share. Total or New files only.
Host name or IP address (Win32 DS-User)

Use this screen to add or modify a DNS host name or IP address.
Host name or an IP address IP range (Add only) Use this field to enter a specific DNS host name or IP address. Use this option to specify the start and end of an IP range (e.g. 10.20.30.40 to 10.20.30.43). This allows you to quickly populate a large list of sequential IP addresses.


Confidential.
Initial Backup Settings

This screen allows you to configure the Initial Backup path location where the backup data will be sent. The selected path is the one that is highlighted in the list.
Path List Icon: A key indicates the Initial Backup will encrypt the meta-data (green means DS-Client Key based / red means user-defined key). Path Total Space: Size of the volume where the path is located. Available Space: Free space remaining on the volume where the path is located. Add Delete Click to add a new path to the Path List. Opens the Select Initial Backup Destination Path screen. Click to delete the highlighted path from the Path List.
Initial Backup Status

This screen allows you to monitor Initial Backup Sets. Once an Initial Backup Set has been imported to the DS-System, it will disappear from this screen.
Backup Set List Each line represents a different Initial Backup Set, where the columns represent the following: Icon: Indicates the current status of the Initial Backup Set: incomplete or completed. Set ID: The Backup Set ID. Server Name: The corresponding computer name where the backup set is located. Set Name: The corresponding backup set name. Set Status: All Initial Backup Sets in the same Initial Backup Path must be completed before you send the buffer (physical media) to your Service Provider. Destination: The Initial Backup Path (Buffer) where the backup data is located. Refresh Mark Completed Mark Incomplete Click to update the list. Make the corresponding Initial Backup Sets status completed. You can do this if some backup data is in the buffer (for example: if the Initial Backup was interrupted). Removes the completed status from the highlighted Initial Backup Set. (This allows you to change the Initial Backup Path, or run another backup of the set.)
Initial DS-Client Configuration / Modify DS-Client Configuration

This screen allows you to make the initial DS-Client configurations required to connect to a DSSystem. It automatically appears after login to an unregistered DS-Client.
Customer Registration Info Browse An alternative to manually entering this information is to use a .CRI file supplied by your Service Provider. Click Browse to search for this file on your network. Enter a descriptive name for this DS-Client. This name appears in brackets after the computer name in the Java DS-User GUIs list of available DS-Client computers (when sorted by Name). Enter your Account number. This number is provided to you by your Service Provider. Enter your DS-Client number. This number is provided to you by your Service Provider. Enter an IP address or DNS name for the DS-System your DS-Client will be using. Multiple addresses can be entered, separated by a semi-colon (;). Click to add the address(es) in the Address field to the connection list.
Customer Name Account # DS-Client # DS-System Info Address Add


Confidential.
Remove
Click to remove the highlighted address from the connection list.
Encryption Keys An encryption key is case sensitive. Its length (in characters) depends on the type and level of encryption selected. DES requires 8 characters, AES-128 requires 16 characters, AES-192 requires 24 characters, and AES-256 requires 32 characters. For better security, do not use dictionary words or proper names, and try to randomly mix numbers in with the letters. Auto-complete feature: If you do not specify the full amount of characters in the Key field, the GUI will fill in the remainder by repeating the string of characters you have entered. (e.g. entering 123 with AES-128 will generate an encryption key of 1231231231231231, or entering a for DES will generate the encryption key aaaaaaaa). Keep the key(s) in a secure location. Your ability to select the same encryption type and re-enter the same key is necessary if you ever need to reinstall your DS-Client to a new computer (e.g. if the computer is destroyed in a disaster). You must set a private key for this DS-Client. Backup data from your DS-Client installation will be encrypted with this key. Type: Select from the available types. Stronger encryption requires longer keys. Key: Enter the key. Confirm: Re-enter the key to verify the string is correct. You cannot change this key once it is set. You must set an account key if more than one DS-Client belongs to your customer account. Common backup data from all your DS-Client installations will be encrypted with this key. Once the account key is set, all DS-Clients from this customer must be configured with that same account key. Type: Select from the available types. Stronger encryption requires longer keys. Key: Enter the key. Confirm: Re-enter the key to verify the string is correct. You cannot change this key once it is set.
Private Key
Account Key
Allow encryption key forwarding to DS-System Check to have DS-Client forward the encryption key(s) to the DS-System the first time it connects with DS-System. NOTE: If you forward the keys, they will remain encrypted on the DS-System. However, your Service Provider will be able to create a valid .CRI file containing the encrypted keys. This file will be able to recreate a working version of this DS-Client. Make sure this conforms to your security policies before enabling this option.
Input encryption key

This screen appears if USER-DEFINED encryption has been applied to the data on the media. Enter the key to proceed with decryption.
Meta data encryption key Enter the key to proceed to access the data. Import Export You can import from any valid file containing an exported key string. You can use this GUI to export the text in this field (in encrypted format) to a text file for distribution, if necessary.
Input the credentials

UNPROTECTED LAN RESOURCE DISCOVERY TOOL


Confidential.
The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to specify which credentials to use when connecting to the shares on the LAN.
Credentials List Lists the credentials to use for the Discovery Scan Process. It is highly recommended that you supply network administrator-level credentials in order to successfully scan the selected shares. Connect As: Shows the username. From: Shows the domain or computer name of the user credential. Leave blank to use the corresponding user account on the local computer (where the Discovery process is attempting to scan). Priority: Shows the order of credentials that the DS-Client will use to attempt to scan each share. If the highest priority credentials fail, the DS-Client tries the next in line until it succeeds (or runs out of additional credentials). Add Modify Delete Click to add a new credential entry. Opens the Set Credentials screen. Click to modify the highlighted credential entry. Opens the Set Credentials screen. Removes the highlighted credential from the list.
Java Runtime Environment Properties

This screen shows additional information about the computer where this instance of the DS-User GUI is running.
Item List Property Value Shows the name of an item. Shows the corresponding value for the item (e.g. version number, build number, etc.).
LAN STORAGE DISCOVERY TOOL

LAN Storage Discovery is a tool to analyze the LAN data available for backup. File redundancy (duplication), and frequency of data changes are identified by this tool.
Listening Ports
This screen shows the default port used by the listed Asigra Cloud Backup component.
Port List Listening Server Client Port This component listens on the corresponding default port for connections from the client-component. This component initiates connections on the corresponding default port to the server-component. This shows the default setting. It does not change if you modify the port.
Load Summary Activities screen

WIN32 Only This screen lists the activities that occurred during the selected period from the Load Summary screen. It is the same as the Activity Log, except there are no option selections.
Activities List Icon Username By default, activities are sorted by time. The most recent activity is located at the top of the list. Shows the an icon representing the activity performed. Shows the name of the user that performed the activity (if applicable).
Confidential.

Type Owner Description Errors Start End Files Online
Shows the type of activity. Shows the User Name of the Owner of the Backup Set (i.e. an administrator might perform an action on a set owned by someone else). Shows the node, and backup set name. Shows the number of errors that occurred during the activity (if any) in red. Shows the date and time the activity started. Shows the time of day the activity ended. Shows the number of files that were affected by the activity. Shows the amount of data affected by the activity. (This may be slightly more than the actual file size, due to file security, permissions or other backup options applied to the backup file.) Shows the completion status of the corresponding activity: Blank column: activity successfully closed connection with DS-System. No Connect: activity failed to connect to the DS-System. With errors: activity contained errors (but completed successfully). Incomplete: activity did not finish completely and/or failed to close its connection with DS-System properly.
Completion
Load Summary screen

The Load Summary can help administrators analyze the load on the DS-Client computer for a selected period of time. Use the Tool Bar at the top of this screen to modify the appearance of the graph
Chart Type From Date To Date Interval Select from Line or Bar Chart Select the first day in the period that you want to view. By default, this is set to 7 days prior to the current date and time. Select the last day of the period you wish to see. By default, this is set to the current date and time. Choose the interval for the horizontal axis of the graph. You may specify an interval of 5, 15, or 30 minutes, 1 hour or 1 day. The default is 1 day.
Node ID Select which Node of the Grid DS-Client to view. (Grid DS-Client) Series Allows you to add or remove information displayed in this screen. Opens the Load Summary Series screen.
Load Summary Series screen

This screen allows you to change the information that is displayed in the Load Summary.
Send: Receive: CPU Load: Memory Load: Memory Commit: Activities: The data throughput sent from the DS-Client (KB/sec). The data throughput received through the DS-Client (KB/sec). The processor time (% of the elapsed time that a processor is busy executing a nonIdle thread). The memory usage (%). The paging memory used (MB). The DS-Client number of activities.


Confidential.
Local DS-VDR Settings

These are optional settings. If supplied, DS-Client / Local DS-VDR Tool will use these credentials to connect to the Converter Server (where the VMware vCenter Converter is running).
Local DS-VDR Tool Setup

Use this screen to configure the Local DS-VDR Tool that this DS-Client uses.
Local DS-VDR Tool IP Enter the IP address of the Local DS-VDR Tool. It must be accessible by the DS-Client via TCP port 4407 (default).
DS-Client stores a hardware cookie of the Local DS-VDR Tool computer on the first connection from the tool. On each subsequent connection, DS-Client will verify the cookie to ensure connection from the same installation. Reset Hardware Cookie You only need to reset the cookie if you change the Local DS-VDR Tool (to another installation) or if you alter the hardware on the existing Local DS-VDR Tool machine. Test Connection Click to test the DS-Clients connection with the Local DS-VDR Tool at the IP address listed in the Local DS-VDR Tool IP field. The results of the test are displayed in a text message at the bottom of this screen. Click to update the Local DS-VDR Tools database with the DS-Clients current Local DS-VDR backup set configurations. This process is also run automatically with the DS-Clients Daily Admin or Weekly Admin.
Synchronize Database
Log Warning (Activity, Event, etc.)

This screen appears if the search returns a large number of logs.
All First [...] Display all logs. Enter a number. Only this number of logs will be displayed from the start of the list.
Maximum Online for ... screen

This screen allows you to set and adjust the online storage limits for users or groups. A Maximum Online limit is an administrative tool to control storage amounts (and invoice charges).
No Limit Assigns the user or group unlimited online storage capacity. Uncheck this box to set an Online storage limit.
You may specify a maximum online storage amount in this field. User limits apply to specific users, Group limits apply to each user who is a member of the specified Group (e.g. all Users in a Group with a 100MB limit would have a 100MB limit). To access this field, turn the No Limit check box off. Online storage limit Note: The online amount is tracked during backups, by taking the current online (MB) amount and adding the new backups. Once the online limit is reached, the backup will stop (even if it is not completed). However, if two backup sets of the same user are scheduled concurrently, the DS-Client will allow both backup sets to use up the full remaining online amount. This means it is possible for the online storage to exceed the maximum online limit.
Migrate Shares screen

Migrate Backup Set Wizard - Match shares / instances

Confidential.
The Migrate Backup Set Wizard uses the same dialogs as with creating a new backup set. You follow the same steps as creating a backup set, with the exception that you are in fact specifying a new path from which the DS-Client will look for the backup files. This screen is intended to match the share(s) on the source computer, with the share(s) on the destination computer. (In the case of databases, you must match each database instance from the source to the destination computer.)
Source Destination Shows the current source share of the selected backup set. Double click on this cell to bring up a drop down list, containing all of the shares on the selected destination node. Select the share where the source data has already been moved to.
Modify Applications (System i Server)

Use this screen to create or modify an application. An application is a specific list of libraries you create for backup.
Application Library Modify Libraries belonging to an application can be sorted by name. A list of the libraries on the System i Server. Click to modify the highlighted applications. Opens the Select Applications (System i Server) screen.
Modify DS-Client address

This screen allows you to modify an existing DS-Client DNS host name or IP address.
New / Edit Bandwidth Throttle Schedule Detail

Use this screen to add or edit details to the Bandwidth Throttles Exceptions List. Each Bandwidth Throttle Schedule Detail that you specify is an exception to the default throttle setting. Exceptions always over-rule the default setting.
Week Days Select the day(s) of the week when you want this Schedule Detail to apply. Starting At Ending At Bandwidth Throttle Start time of the Schedule Detail period. End time of the Schedule Detail period. (This must end on the same day.) Unlimited: No throttle is applied during the Schedule Detail period. Limited to [...] KB/Sec: Throttle of this amount of KB/Sec applies during the Schedule Detail period.
New / Edit Password Rotation Rule

Use this screen to add or edit a Password Rotation Rule.
Name Length Constraints Min. Len.: The minimum length (in characters) of the rotated password. Max. Len.: The maximum length (in characters) of the rotated password. Complexity Constraints Min. Count: The minimum number of characters from the corresponding character set that must be included in the rotated password. Character: Shows the character set for the corresponding complexity rule.

Confidential.
Add Edit Remove OK
Click to add a Complexity Constraint to the list. Opens the Add / Edit Complexity Rule. Click to edit the highlighted Complexity Constraint from the list. Opens the Add / Edit Complexity Rule. Deletes the highlighted Complexity Constraint from the list. Click to save or update this Password Rotation Rule.
New / Edit User / Group Role

Use this screen to add or change the User / Group Roles configuration.
User / Group User Name / Group Name From Select either a User or Group to add to a Role. Enter the name of the User or Group. Select the Computer or Domain from which the User or Group will be Authenticated. Assign the User or Group to one of these Roles: DS-Client Administrator DS-Client Backup Operator DS-Client Regular User For more information, refer to the DS-User Guide.
DS-Client Role
New Backup Sets Summary

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to view the new backup sets that were created by the last scan process.
New Backup Set List Server Name - Network name of the backup computer. Backup Set Name - Backup set name on this DS-Client. Owner - Backup set owner. Connect As - Credentials used to connect to the share. Select By Server Name - Allows you to filter for a specific computer. Refresh Update the list based on the Select by options.
New Backup Set Wizard - Input DB2 userexit log path

This Wizard screen only appears if you selected Online Backup in the Specify backup set options screen. If User Exit is OFF on the DB2 database server, you can leave this field empty. If User Exit is ON on the DB2 database server, you must enter the path for the DB2 Archive Logs.
Archive Log backup path This is the path where the DB2 Archive Log files are written by the User Exit program. Click [...] to specify the path. This opens the Select Directory screen.


Confidential.
New DS-Client address

This screen allows you to add a DS-Client address entry.
Host name or an IP address Use this field to enter a specific DNS host name or IP address. IP range (Add only) Use this option to specify the start and end of an IP range (e.g. 10.20.30.40 to 10.20.30.43). This allows you to quickly populate a large list of sequential IP addresses.
New Time Retention Option

Use this screen to create a time-based retention option.
Time Retention Option A time retention option keeps one generation from each time interval that fits into the retention span. Select the interval of time. When this rule is enforced, the most recent generation from the interval is kept, for as many intervals that can fit into the retention rules length. See note (at the end of this help screen) about the behavior of this option. When this rule is enforced, the most recent generation from each interval is kept.
Keep one generation every
Keep one generation every week on or before [day] at [time]
Keep one generation every month When this rule is enforced, the most recent generation from each on or before the [x] day at [time] interval is kept. Keep one generation every year on When this rule is enforced, the most recent generation from each or before the [x] day of [month] at interval is kept. [time] Select the retention options length (the time span it covers). At least one generation interval must fit into this retention length. By default, this period is 1 week. If you select a time retention option that spans a longer period, you should extend this value to at least match that period.
Retention option valid for
Note: When selecting the option Keep one generation every <n> years, the generations will be considered for the interval between January 2nd 00:00 until January 1st 23:59:59 next year. This may not be what is expected by users (e.g. January 1st 00:00 to December 31 23:59:59 same year). Instead, users can implement retention with the rule keep one generation every year..., where users can specify the start date and time of the interval (e.g. Last day of December at 23:59:59 for an interval between January 1st 00:00 and December 31st 23:59:59). Note that if you can specify the start date for a retention option, it will count backwards from that date by the specified interval.
Online / LAN File Summary screen

LAN STORAGE DISCOVERY TOOL This screen provides a list of the online or LAN files.
Global View Online File Summary: for each row, a file is only counted once (even if there are multiple generations of that file).


Confidential.
Category
Files Files (%) Size (MB) Size (%) Last ... days
All files Duplicate files - Total number of files that have more than one copy, minus one for each unique common file group. Duplicate groups (LAN File Summary only) - Number of unique common file groups. All identical files are members of a unique file group. Changed and new files - Files that are new or different from the start of the search period. Unchanged files - Files that have not changed since the start of the search period. Not accessed files - (LAN File Summary only) Files that have not been accessed since the start of the search period. Number of files. Percentage of the total number of files. Size of the files. Percentage of the total size. Displays results for the last number of days specified.
Filtered View The content of this section is based on the filters applied at the bottom of the screen (filter, category, duplication, totals, share/set). It is updated each time you click Find. Online File Summary: for each row, a file is only counted once (even if there are multiple generations of that file). All - Shows all the categories in the Filtered View list. All files - Shows the total number of files that fit the selected filter(s) in the corresponding backup set (Online File Summary) or share (LAN File Summary). Duplicate files - Total number of files that have more than one copy, minus one for each unique common file group. Duplicate groups (LAN File Summary only) - Number of unique common file groups for the corresponding scope. All identical files in the corresponding scope are members of a unique file group. The scope can be the sum of the whole Filtered View, or a more specific part, like an individual share. Changed and new files - Files that are new or different from the start of the search period. Unchanged files - Files that have not changed since the start of the search period. Not accessed files (LAN File Summary only) - Files that have not been accessed since the start of the search period. Number of files. Percentage of the total number of files. Percentage of the total number of files (from the Global View at the top of the screen). Size of the files. Percentage of the total size. Percentage of the total size (compared to the Global View at the top of the screen).
Category
Files Files (%) Files (% of Global) Size (MB) Size (%) Size (% of Global)
Backup Set / Share Shows the corresponding backup set or share name. Name Filter Category Duplication Totals only Share / Set Allows you to search exclusively for files matching the specified pattern (e.g. *.doc). Allows you to narrow your search by type of files (All, Duplicate, Changed & New, or Unchanged). Allows you to narrow your search by the duplication level (e.g. "2" means there must be at least two copies (duplicates) of the file on the selected share/set). Check this box to display only the totals (it will be faster). Allows you to search only a specific share/set (faster). Click the >> button to browse the network.


Confidential.
Set Types... (Online File Summary only) Options
Allows you to add an additional filter based on backup set type. Opens the Backup set type screen.
Status (Online File Shows the status of the online search. Summary only) Find Details Chart Click to search (update the screen) based on your selections. Opens the Details screen for the highlighted item in the list. Click to see a chart based on your selections.
Orders for Disc / Tape screen

Use this screen to view your Disc/Tape orders. You can also track the status of your order. Information in this screen comes directly from the DS-System. You should click Refresh after any activity to make sure you have the most up-to-date information.
Order ID Backup Set Time Issued Unique sequential order number. Shows the backup set you requested to be burned to a Disc/Tape. Shows the time the request was made. Shows the latest status message from the DS-System (in chronological order): Purchased - You have submitted the Disc/Tape order to the DS-System. Finished - Your order has been written to the requested media (Disc/Tape) by the DS-System. Mailed - Disc/Tape has been mailed to you. Shows the number of discs/tapes that will be sent. Shows the media type you have selected. Shows if the request is for a: Snapshot - the latest generation of all files in the backup set Selective Restore - customized request for specific files / folders Shows the number (if any) of files that were not successfully processed. Updates the list with the latest information from the DS-System.
Status
Media Type Options Files Failed Refresh
Password Management screen

Use this screen to manage the list of usernames that will have their passwords randomized. Once a password is rotated, no one will know what it is. This means the only way you can use this username is by applying it to a backup set through this feature.
Managed Passwords List User Name From Backup Sets Rotation Last Updated Add This is the actual user account name from a Windows computer or domain. This is the corresponding computer or domain where the user account is located. For accounts on the local computer (that is running the DS-Client), you can use the dot . character. The number of backup sets that are using these credentials. This association is done in the Password Management - Backup Sets Tab. The frequency at which the corresponding user account password is randomized. This is set from the Password Management - Password Rotation Tab. Shows the last time the password of the corresponding account was randomized. Click to add a user to the Managed Passwords List. Opens the Password Management - User Details Tab.


Confidential.
Edit Remove Rotate Now
Click to edit the highlighted user from the Managed Passwords List. Opens the Password Management - User Details Tab. Deletes the highlighted user from the Managed Passwords List. NOTE: You cannot remove a user if it is associated with any backup sets. Remove the backup set associations first. Click to rotate the highlighted users password immediately. The change is reflected in the Last Updated column.
Password Management - Backup Sets Tab

This screen allows you to select backup sets to use with this user account. Once applied, all associated backup sets will use this user account and its (rotated) password.
Associated Backup Sets Computer Set Name Owner Select This is the source computer for the backup set. This is the actual backup set name. Shows the current owner of the backup set. Select the backup sets to associate with this user account. This opens the Select Backup Sets (Password Management) screen.
Password Management - Password Rotation Tab

Use this screen to specify the password rotation settings.
Enable Automatic Password Rotation Rotation Settings Rotation Rule Rotation Frequency Select the Rotation Rule to apply to this user account. This opens the Available Password Rotation Rules screen. Select the frequency at which the corresponding user account password is randomized. Check this box to activate this option. If unchecked, you must manually rotate the password from the Password Management screen.
Password Management - User Details Tab

This screen allows you to add or view a users logon information.
Logon Information User Name From This is the actual user account name from a Windows computer or domain. This is the corresponding computer or domain where the user account is located. For accounts on the local computer (that is running the DS-Client), you can use the dot . character. [Add user only.] Enter the current valid password for this user. This is required when adding a user account for the first time, in order to enable the randomization. Once this users password becomes randomized, no one will be able to enter the credentials. (Only administrators can re-set the password from the Operating System.) [Edit user only.] Shows the last time the password of the corresponding account was randomized.
Password
Last Psw. Change
Note(s) This area allows you to enter text for any notes you wish to leave about this user account.


Confidential.
Permissions screen
Use this screen to view, add, or remove permissions for the selected backup set to other users / groups.
Permissions List Each entry in this list represents permissions for this backup set that are granted to that user or group. The backup set owner and users with the DS-Client Administrator role automatically have all permissions to any backup set even though they are not listed here. Users with the DS-Client Backup Operator role have backup permission to any backup set. Icon Name Description Domain Type Add Edit Remove Shows what the corresponding entry refers to: a specific user a group Shows the name of the user or group. Shows a description (if any) of the user's full name or the function of the group. [Windows only] Shows the domain or server where a user or group is defined. Shows the types of permissions allowed to the respective user or group. The codes represent (B)ackup, (R)estore, (M)odify, and (D)elete. Click to give a specific user or group permissions to this backup set. Opens the Add / Edit Permissions for a User or Group screen. Click to edit the user or group selected in the Permissions List. Click to remove the user or group selected in the Permissions List.
Pie Chart for

Shows a chart of the selected information.
Pre & Post Execution screen

Use this screen to specify a command to run before (Pre) and/or after (Post) execution of the backup/restore. See: Pre/Post Use Cases
Check this box to execute the Pre/Post commands on the remote machine where the backup set's files are located. Leave this box unchecked to perform Execute on remote system the Pre/Post commands on the local DS-Client computer. Note: This box is disabled if the backup set is on the local DS-Client computer. Perform this activity before backup / restore Runs the command entered in the Command field. You must type "cmd /c" before the command if it is not the name of an executable file. (This command must not run anything that requires user input.) Local machine - The DS-Client will terminate the process if it detects that the command requires user input. Remote Windows - The Backup Set's Connect As information must have administrator privileges, since the Schedule service is used to run the command on the remote Windows machine. (The DS-Client only knows if the command has started to execute, and not whether it has completed. Therefore, you may wish to delay the start of the backup if the command will take a few minutes to finish). UNIX - The rexec service must be running on the remote machine.
Confidential.
Run command

Stop service Start service
Stops the Service specified in the Command field. Starts the Service specified in the Command field. Runs the command batch file specified in the field on the remote NetWare server. All the rules for running NCF from the console are applied - if the NCF is not in the search path, you must provide the full path (sys:dir_name\name.ncf). The NCF file must be in 8.3 name format, since the console does not understand long file names. (Must have Console Operator Rights.) Unloads the NLM (NetWare Loadable Module) specified in the field. (Must have Console Operator Rights.) Loads the NLM (NetWare Loadable Module) specified in the field. (Must have Console Operator Rights.) Enter the command to perform. For Services, type the service name or use the >> button to select the service. Command Execution Results - You may specify conditions, based on the results of the command execution: On exit code (Local commands) - Specifies the condition to be = (equal) or <> (not equal) to the exit code in the field to the right. This is useful if you know that the command will produce a particular exit code when finished. On file existence - Specifies the condition to be whether a particular file exists or not. Enter the full path (include the drive on local machines; include the share but not the server on remote machines) in the field to the right. On output string (Local commands & UNIX only) - Specifies the conditions to be whether the command output contains a particular string or not. Enter the string (case sensitive) in the field to the right. (If the output is large, only the first 16K are checked for occurrences of the string.) On execution success - Specifies the condition applies if the command succeeds to execute. On execution failure - Specifies the condition applies if the command fails to execute. Or execution failure - Allows you to combine either the Exit Code, File Existence or Output String conditions with the Execution Failure condition. Will not perform the Post Activity on fulfillment of the Command Execution Results. Will not perform the backup/restore on fulfillment of the Command Execution Results.
Run NCF (NetWare)
Unload NLM (NetWare) Load NLM (NetWare) Command Field
Command Execution Results
Don't perform post activity Don't Perform Backup/ Restore
Allows you to delay the backup/restore. This is useful in cases where the Delay Backup/Restore [...] command activates background processes responsible for creating data for Sec backup. Also allows time for the pre activity to terminate properly. Perform this activity after backup / restore Each of the following activities are the same as for Pre-Backup: Run command. Stop service. Perform this Activity After Start service. Backup. Run NCF (NetWare). Unload NLM (NetWare). Load NLM (NetWare). Command Field Enter the command to perform. For Services, type the service name or use the >> button to select the service.


Confidential.
Will not perform the Post Activity if the backup / restore: Always perform - Will always perform the Post Activity. Don't perform Post activity Successful - Will not perform if the backup/restore was successful. if With errors - Will not perform if the backup/restore had errors. Incomplete - Will not perform if the backup/restore was incomplete. Click to test the command in the Pre or Post section. A results screen appears, displaying whether the command executed, the exit code, and the Execution condition. NOTES: 1. Do not use Test Pre with the Delay option, since a delay of over 60 seconds will result in a Timeout message. 2. Using Test with some Pre/Post commands like Stop Service/Start Service, will only accomplish the first part (i.e. only the Pre command), effectively rendering a service 'stopped' until manually restarted.
Test Pre Test Post
Pre & Post Execution screen (Linux DS-Client)

Use this screen to specify a command to run before (Pre) and/or after (Post) execution of the backup/restore. See: Pre/Post Use Cases
Before backup Execute Test On exit code Do not perform backup Enter the command to perform. Click to test command You may specify conditions, based on the results of the command execution: On exit code (Local commands) - Specifies the condition to be = (equal) or <> (not equal) to the exit code in the field to the right. This is useful if you know that the command will produce a particular exit code when finished. Will not perform the backup on fulfillment of the exit code condition.
Do not perform post activWill not perform the Post Activity on fulfillment of the exit code condition. ity After backup Execute Test Execute after data has been copied to DS-Client buffer (if applicable) Before restore Execute Test On exit code Do not perform restore Enter the command to perform. Click to test command You may specify conditions, based on the results of the command execution: On exit code (Local commands) - Specifies the condition to be = (equal) or <> (not equal) to the exit code in the field to the right. This is useful if you know that the command will produce a particular exit code when finished. Will not perform the restore on fulfillment of the exit code condition. Enter the command to perform. Click to test command (Only for backups sets with the Use buffer option selected.) Select to perform the Post command immediately after the data has been copied to the DS-Client buffer. The default setting (if not selected) is to perform the Post command after full backup completes.
Do not perform post activWill not perform the Post Activity on fulfillment of the exit code condition. ity After restore Execute Enter the command to perform.


Confidential.
Test
Click to test command
Pre/Post Use Cases

What you want to do: How to do it?
Leave all fields on the right blank. DS-Client will not Start a remote program. (Including programs that wait for the program to close. However, it will know require interaction.) DS-Client will not wait for the if the program has been submitted for execution. program to close: (This allows you to check for the exit code.) Start a remote program. (Including programs that Select "Don't perform Post" and/or "Don't perform require interaction.) DS-Client will wait for the pro- backup". If the program requires interaction, DS-Cligram to close: ent will wait until the program is closed. Leave all fields on the right blank. DS-Client will not Run a remote batch file. DS-Client will not wait for wait for the batch file to finish. However, it will the results: know if the batch file has been submitted for execution. Select either "Don't perform Post", or "Don't perform Run a remote batch file. DS-Client will wait for the backup", or both. DS-Client will wait until the batch results: file finishes the execution. Check for exit code, file existence, output string, etc. To apply an (unconditional) delay: To Start/Stop a service: Select from the appropriate radio button or checkbox. Select "On execution success" and check "Or execution failure", and select the delay in seconds. Enable the Stop / Start Service option. Select the Service using the >> button.
If you want to run a local program (on the DS-Client Call ASIGRA Inc. for assistance. machine):
Print Backup/Restore Summary & Backup Trends Report

This screen allows you to print the Backup/Restore Summary report and the Backup Trends report. A differently titled screen comes up depending on the selected report.
You may type the backup node, or backup node & backup set name that you want to view. By default, this field is blank, allowing you to see the activities of all users. Select: Click to choose a specific computer or backup set. By default, this field is blank, allowing you to view all backup sets (if you have sufficient authority). You may type the User Name whose activities you wish to see in this field. By default, this field is blank, allowing you to see the activities of all users. Type the earliest date you want to display in this field. No data older than this date will be displayed. Type the latest date you want to display in this field. No records newer than this date will be displayed. By default, this is set to the current date and time. The Backup Trends report can show either weekly or monthly statistics: Weekly: Select to view a weekly report. Monthly: Select to view a monthly report.
Node/Set
User From Date To Date Summary (Backup Trends only)


Confidential.
Set Type
You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Deleted: Includes data from all deleted backup sets (regular, statistical, self contained, and Local-Only). This uses data from the Activity Log. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). (Multi-Tenant DS-Client only) Select from the list of available customers. This report will show only data from the selected customers backup sets. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <N/A> selection.
Customer
Print Backup Groups screen

Use this screen to print the Backup Groups report, view the report and set up your printer. Only Administrators may view all backup group reports.
Group Name Type the name of the user group for which you want to create a report, or click >> to select from a list of the user groups. Leave this field blank to create a report that includes all users. You can select any or all of the following type(s) of backup sets to include in this report: Regular: Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). (Multi-Tenant DS-Client only) Select from the list of available customers. This report will show only data from the selected customers backup sets. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <N/A> selection.
Set Type
Customer
Print Global Report - Backup / Restore Report

(Java DS-User only) Use this screen to print or view the Backup / Restore report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection User From Date To Date You can search for a specific user (backup set owner). Leave blank to show all users. Enter the earliest date you want to display in this field. No data older than this date will be displayed. Enter the latest date you want to display in this field. No records newer than this date will be displayed. By default, this is set to the current date. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.


Confidential.
Set Type
You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Deleted: Includes data from all deleted backup sets (regular, statistical, self contained, and Local-Only). This uses data from the Activity Log. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). Opens a preview of the report. You can print from the preview.
OK
Print Global Report - Backup Groups Report

(Java DS-User only) Use this screen to print or view the Backup Group report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection Group Name You can search for a specific user group. The default is to leave this field blank, which will create a report that includes all users from each DS-Client. You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). Opens a preview of the report. You can print from the preview. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Set Type
OK
Print Global Report - Backup Items Report

(Java DS-User only) Use this screen to print or view the Backup Items report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply Opens a preview of the report. You can print from the preview. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Set Type
OK


Confidential.
Print Global Report - Backup Sets Report

(Java DS-User only) Use this screen to print or view the Backup Sets report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). Opens a preview of the report. You can print from the preview. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Set Type
OK
Print Global Report - Backup Trends Report

(Java DS-User only) Use this screen to print or view the Backup Trends report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection User From Date To Date Weekly / Monthly You can search for a specific user (backup set owner). Leave blank to show all users. Enter the earliest date you want to display in this field. No data older than this date will be displayed. Enter the latest date you want to display in this field. No records newer than this date will be displayed. By default, this is set to the current date. You must select whether to display the trends grouped by week or by month. You can select any or all of the following type(s) of backup sets to include in this report: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Deleted: Includes data from all deleted backup sets (regular, statistical, self contained, and Local-Only). This uses data from the Activity Log. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). Opens a preview of the report. You can print from the preview. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Set Type
OK
Print Global Report - Backup Users Report

(Java DS-User only) Use this screen to print or view the Backup Users report.


Confidential.
Note: You will only be able to print reports for backup sets to which you have sufficient rights.
Set Type
OK
Print Global Report - Export Backup Sets Information

(Java DS-User only) Use this screen to export Backup Sets information to a file. Note: You will only be able to export information for backup sets to which you have sufficient rights.
DS-Client(s) Export Options Save As File Format OK Choose where you want the report information saved. Choose the format you want to save the report in from this drop down list. Generates the report. Opens the Generate Global Report (Print Global Report) screen. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Print Global Report - Restorable Volume Report

(Java DS-User only) Use this screen to print or view the Restorable Volume report. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
Set Type
OK
Print Global Report - Statistical Summary Report

(Java DS-User only)


Confidential.
Use this screen to print or view the Statistical Summary report. This shows useful statistics and compression ratios for backups performed by the DS-Client. Note: You will only be able to print reports for backup sets to which you have sufficient rights.
DS-Client(s) Report Selection User From Date To Date You can search for a specific user (backup set owner). Leave blank to show all users. Enter the earliest date you want to display in this field. No data older than this date will be displayed. Enter the latest date you want to display in this field. No records newer than this date will be displayed. By default, this is set to the current date. Lists the DS-Clients you want to include in the Global Report. [...]: Opens the Select DS-Client (Print Global Report) screen.
Backup set type to include: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). Group report by: You must specify how the Statistical Summary will group the information: Machine Backup Set User Update Statistics: Gather new statistics before preview/print - Indicate if you want to update the statistics before you preview or print this report. If checked, each DS-Client will run an Update Statistics Process (part of the Daily/Weekly Admin). This may take some time, depending on the size of the database. OK Opens a preview of the report. You can print from the preview.
Print Report
This is a common print screen for the following reports: Backup Sets Backup Users Restorable Volume Backup Items Note: You will only be able to print reports for backup sets to which you have sufficient rights.
Report Selection You can select any or all of the following type(s) of backup sets to include in this report: Regular: Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Local DS-VDR: Includes data from all Local DS-VDR backup sets (DS-System data storage and transmission amounts do not apply). (Multi-Tenant DS-Client only) Select from the list of available customers. This report will show only data from the selected customers backup sets. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <N/A> selection.
Confidential.
Set Type
Customer

Win32 DS-User Java DS-User
Print: Sends the report directly to the printer. Print Preview: Opens a preview of the report. Printer Setup: Opens the Windows Print Setup OK: Opens a preview of the report. You can print from the preview.
Print Spreadsheet
Use this screen to print the contents of a spreadsheet. You can print all the rows, or only a selected range of rows.
Header Print All Print Selection Print Row Nums Print Colors From Row To Row Type a title for the printout. Select to print all of the rows of the spreadsheet. Select to print only a range of rows, as defined in the From Row and To Row fields. Check to print row numbers on the printout. Check to print the spreadsheet in color or shades of gray, depending on your printer. If this box is unchecked, there is very little shading; most of printout is black and white. Enter the first row you want to print. Leave this field blank to print all the rows. Enter the last row you want to print. Leave this field blank to print all the rows.
Print Statistical Summary

Use this screen to preview and/or print the Statistical Summary. This shows useful statistics and compression ratios for backups performed by the DS-Client.
Report Selection Node / Set User From Date To Date Leave blank to show all computers / backup sets. Click the Select button to browse for a specific backup set. Leave blank to show all users. Click the Select button to browse for a specific backup set. Specify a start date for the Report period. Specify an end date for the Report period. (Multi-Tenant DS-Client only) Select from the list of available customers. This report will show only data from the selected customers backup sets. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <N/A> selection.
Customer
Backup set type to include: Regular: [Default is on.] Includes data from all regular backup sets. Statistical: Includes data from all statistical backup sets. Self Contained: Includes data from all current self contained backup sets. Local-Only: Includes data from all Local-Only backup sets. Group report by: You must specify how the Statistical Summary will group the information: Machine Backup Set User Update Statistics: Statistics updated on - Shows the last time when the DS-Clients statistics were updated. Gather new statistics before preview/print - Indicate if you want to update the statistics before you preview or print this report. If checked, DS-Client will run an Update Statistics Process (part of the Daily/Weekly Admin). This may take some time, depending on the size of the database.


Confidential.
Java DS-User Win32 DS-User
OK - Previews the report, as it will appear when printed. A print icon appears in the preview. Print - Prints the entire report. Print Preview - Allows you to preview the report, as it will appear when printed. Printer Setup - Opens the Windows Print Setup screen.
Process Window screen

This screen displays the progress of DS-Client activities.
Stop Ready Click to attempt to stop the process. This cannot be undone. If the process is waiting for user input (e.g. a CD), this button will activate. Click to continue the process.
Working On Section Note: Since most processes are multi-threaded, they may finish faster than the GUI can refresh the screen. Shows the item currently being processed. Since only one item can appear in this field at a time, not all files processed can be displayed and only larger files have the probability of appearing. Percentage bar: Shows the progress of the current item being processed. This only appears if the files processing time is long enough to be visually represented. Shows the last directory scanned. Note: This is independent of the file that is displayed as being processed. Shows the backup set (including the network resource). Shows the total amount of data processed so far. Shows the total number of files processed so far. Shows the total amount of data left to process. Shows the total number of files left to process. Shows any relevant status comments about the activity If the percentage bar appears, it shows the progress for the overall process. Shows the number of warnings that occurred during the activity (if any). Shows the number of errors that occurred during the activity (if any). Click to view the event log, which shows any error information about the session. Shows the time that has elapsed since the beginning of the activity. If you chose to run PreScan in the Select Files for Demand Backup Dialog Box, a second time counter appears to display the estimated time remaining for the activity. Shows the data transfer rate between the DS-Client and the network resource. Note: For some processes (e.g. delete) this rate is measured in Files per second.
File
Dir Set Details Section Total Amount Total Files Amount Left Files Left Status Progress Warnings Errors Event Log Statistics Section Digital Time Counter(s) KB/sec
Recovery Info screen

Use this screen to view or change information about the backup set to be recovered. Some information may not be available. In such cases the backup set will be recovered with default values (i.e. <Unknown>).
Owner Network Provider Computer Shows the User Name of the Owner of the Backup Set. Shows the Network Provider on which the Backup Set's computer is located. Shows the source computer for the Backup Set's files and directories.
Confidential.

Set Name Note 1
Shows the Backup Set's name. You can change this field, to change the name of the backup set. In some cases you may be forced to choose an Owner or Network Provider (ex: if there are more than one user/network provider computer available with the same name).
Regular Expression screen

You should only use this option if you take the time to learn the Regular Expression syntax. Regular Expression provides more specific filtering than the regular exclude filter. For example, you can filter to exclude individual filenames or patterns. Use this screen to specify the Regular Expression to exclude from (or apply to) backups.
Edit Expression Pre-defined: Select from one of the pre-defined expressions in the list. Custom: Enter the Regular Expression string to exclude.
Match Options The default Match Options are to EXCLUDE the expression, with Case Sensitive filtering, against files and directories. Case Sensitive [Default is selected.] Indicates if the expression matching is CaSE sENsitIVe. Negates the expression. This means it will exclude any files not matching the Regular Expression. This has the effect of permitting the negated expression to be backed up. This option only works at the individual file level (not on directories). For example, negating the pre-defined .*\.tmp expression allows you to exclude any files that do not have the .tmp extension. Inverts the Regular Expression to filter for the specified pattern. If you add one Inclusion to a backup sets Selected Items for Backup List, only files matching the inclusion will be backed up. No other files will backed up, unless additional inclusion expressions are added. For example, selecting this option with the pre-defined .*\.tmp expression allows you to include all .tmp files from the shares and directories selected for backup. Add multiple Inclusion expressions to search for only the specified names or patterns. Select what this Regular Expression will filter: files and directories: Not available with the Negate option. files only Check the Regular Expression against a string you enter in this field. Click the check icon to verify if this string matches the Regular Expression.
Negate
Inclusion
Match Test Match against
Example: To exclude a specific filename from the backup, use \\filename\.ext$ (e.g. \\cache\.dsk$ will exclude the file cache.dsk). Source code and some documentation available from: http://www.boost.org (search the site for regex). Some of the syntax and semantics of the regular expressions supported by boost:regex are described below. Regular expressions are also described in the Perl documentation and in a number of other books, some of which have copious examples. Jeffrey Friedl's "Mastering Regular Expressions", published by O'Reilly, covers them in great detail. The description here is intended as reference documentation.


Confidential.
A regular expression is a pattern that is matched against a subject string from left to right. Most characters stand for themselves in a pattern, and match the corresponding characters in the subject. As a trivial example, the pattern The quick brown fox matches a portion of a subject string that is identical to itself. The power of regular expressions comes from the ability to include alternatives and repetitions in the pattern. These are encoded in the pattern by the use of meta-characters, which do not stand for themselves but instead are interpreted in some special way. There are two different sets of meta-characters: those that are recognized anywhere in the pattern except within square brackets, and those that are recognized in square brackets. Outside square brackets, the meta-characters are as follows:
\ ^ $ . [ | ( ) ? * + { general escape character with several uses assert start of string (or line, in multiline mode) assert end of string (or line, in multiline mode) match any character except newline (by default) start character class definition start of alternative branch start subpattern end subpattern extends the meaning of ( also 0 or 1 quantifier also quantifier minimizer 0 or more quantifier 1 or more quantifier also "possessive quantifier" start min/max quantifier
Part of a pattern that is in square brackets is called a "character class". In a character class the only meta-characters are:
\ ^ [ ] general escape character negate the class, but only if the first character indicates character range POSIX character class (only if followed by POSIX syntax) terminates the character class
Remove Backup Set

Confirm the delete by pressing the OK button.
Move to BLM Check to have DS-Client instruct DS-System to copy all this backup set's online data to the BLM Archive before deleting the backup set. [Note: If this option is grayed out but the checkbox is selected, it means the data must be moved to BLM. This occurs if the backup set has the BLM (Infinite Generations) option selected (Backup Set Properties > Options tab).] Use new archive package: Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. Archive packages are specific to a particular backup set. Session Label: Each Archive Package is automatically time-stamped, but you must add your own label (alpha-numeric string) to demand BLM requests. This will make it easier to search an Archive Package.
Confidential.

Rename Component screen

This screen applies to alternate location restores of VSS-aware backup sets. The content depends on what was backed up (SQL Server, Exchange Server, Hyper-V, or SharePoint).
Source : Target Mapping List Each line in the list shows a source component from the VSS-aware backup. By default, it will be restored to the alternate location with the same component name. This list allows you to rename individual components by editing the name or path in the target column. Load XML Save XML Loads the mapping contents from a previously saved XML file. A mapping will only be loaded if the Logical Path and Source Component columns from the XML file match exactly with those that are displayed in the list. Saves the contents from the current Source:Target Mapping List to an XML file for later use.
Repair DS-Client screen

These advanced options permit administrators to repair and/or recover the DS-Client database.
Recover DS-Client & delta databases (Windows DS-Client) DS-Client database (Windows DS-Client) Flags the DS-Client Database to be restored. The last backed up version of the dsclient and dsdelta databases will be restored. Refer to the User Guide instructions and related DS-Client Knowledge Base Articles before executing this option. Flags the DS-Client Database to be restored. The last backed up version of the dsclient database will be restored (without the dsdelta database). Refer to the User Guide instructions and related DS-Client Knowledge Base Articles before executing this option.
Flags the DS-Client Database to be restored. (On Linux/Mac DS-Clients, there is no separate dsdelta database.) The last backed up version of the dsclient database DS-Client database will be restored. (Linux/Mac DS-Client) Refer to the User Guide instructions and related DS-Client Knowledge Base Articles before executing this option. Opens the Backup Set Recovery screen, which displays any backup sets found by Orphaned backup sets the last Weekly Admin process to exist on the DS-System, but not in the DS-Client database. (Orphaned sets are found by the Weekly Admin. process.) OK Click to recover to specified radio button item. WARNING: Once you click OK for database recovery, the process starts, and your existing database(s) will be replaced. This operation cannot be undone.
Report Font Setup

(Win32 only) This screen controls the Fonts used in Win32 DS-User Reports. Select from the available fonts.


Confidential.
Retention Rules Tab

This tab appears in the DS-User screen. It allows you to manage the retention rules.
Retention Rules Tree Shows a tree of the existing Retention Rules. The top-most container is <No Retention>. Backup sets in this container have no Retention Rule assigned. Expand a Retention Rule to show the backup set(s) associated with it. Click to create a new Retention Rule. Click to edit the highlighted Retention Rule. Click to delete the highlighted Retention Rule (only if no backup sets are assigned to it). Expands the retention branch. Collapses the retention branch. If a backup set is highlighted, you can use this option to select a Retention Rule. You can also drag-and-drop the backup set into the Retention Rule container you want.
Right-mouse click menu: New Retention Edit Retention Delete Retention Expand All Collapse All Assign to Retention (backup set level)
Retention Rule Wizard - Archive Old Data to BLM Options

Use this screen to define the Archive to BLM options. This option is applied last, to the files that remain online after the Delete Options and/or Time Retention Options have run (if defined).
Each item in the list is a separate rule that will be applied in sequence. Online files that fall into the scope of the rule will be pushed to the BLM Archiver. Once files are pushed, they cannot be restored from the DS-System. They are moved to BLM and can only be written to a BLM Restorable Image if they need to be restored. If the last (latest) generation of a file is pushed, an archive stub (a small file containing only metadata) will be left on the DS-System online storage. This prevents that file from being backed up again by the DS-Client, unless the source file is changed. (Note for disambiguation purposes: In all other cases when a generation is archived to BLM, no such archive stub is kept online.) Click to add a rule to the list. Opens the BLM Archive Rule screen. Click to edit the highlighted rule in the list. Opens the BLM Archive Rule screen. Click to delete the highlighted rule from the list. By default, a files last modified time and its backup time are both used to determine if it qualifies as old data. (The oldest of the two times is used.) If this option is selected, only the backup time of a file is used to determine if it qualifies as old data. This means files that have not been modified for a long time will remain online until their last backup time qualifies them as old data.
Archive Rules List
Add Edit Remove Options
Compare backup time only
[Default is selected.] Special files are the separate items that can be selected when backing up a file sysArchive special files tem (System State, Services Database, NDS, etc.). (Windows DS-Client) If selected, the special files in a backup set that qualify as old data are allowed to be archived.


Confidential.
[Archive special files must be selected. Default is selected.] Do not archive latIf selected, the latest generation of all special files (e.g. System State) is kept est generation of online. If not selected, any special files that qualify as old data will be archived. special files Select this option if this Retention Rule will be applied to any backup set that is (Windows DS-Client) used for Bare Metal Restore (BMR).
Retention Rule Wizard - Choose a name

Use this screen to choose the name of this Retention Rule.
Name Retention Option Delete obsolete data Move obsolete data to BLM BLM Option Select to use a new archive package. Otherwise, this Archive request will be New Archive Package added to the current archive package on the BLM Archiver. Archive packages (only if Move obsolete are specific to a particular backup set. Each BLM Request will be added to an data to BLM is selected) Archive Package until it reaches a specified limit (# of files, size, time). Summary Shows a list of all the rules selected for this Retention Rule. If selected, all the data that is obsolete is deleted. WARNING: Once enforced, any deleted data is gone forever! If selected, a copy of all generations that are deleted will be sent to BLM. Note: This option does not apply to Local-Only or Self-Contained backup sets. Enter a name for this Retention Rule.
Retention Rule Wizard - Choose Retention Settings

Use this screen to select what types of retention options to include in this Retention Rule.
Online and Local-Only retention Selections in this section affect the data that is stored online on the DS-System and the data that is stored (locally) for Local-Only backup sets. Deletion of files removed from source / HSMed data Time-based retention Archive old data to BLM If selected, this wizard displays the Retention Rule Wizard - Delete Options screen. If selected, this wizard displays the Retention Rule Wizard - Time Retention Options screen. If selected, this wizard displays the Retention Rule Wizard - Archive Old Data to BLM Options screen (if applicable).
Local Storage retention This option is only available if the DS-Client has the Local Storage Tool enabled. Selections in this section affect the data that is stored in the local storage of the DS-Client. This option only applies to Regular Backup Sets configured with the Use Local Storage option. (It does not apply to Local-Only backup sets.) This option changes the behavior of the Local Storage Tool. Off: When this option is off, only the latest generation of a backup file is kept in the Local Storage directory. On: When you check this option, the DS-Client will store the same amount of generations in the Local Storage directory as are stored in the DS-Systems online storage. If selected, this wizard displays the Retention Rule Wizard - Local Storage Retention Options screen.
Enable Local Storage retention


Confidential.
Component data integration options for VSS-aware backup sets [Windows DS-Clients only] These options only apply to VSS-aware backup sets. VSS-aware backup sets are "component" based. A component is: a database for Microsoft SQL Server a Storage Group, database, or other components for Microsoft Exchange Server a Virtual Machine for Hyper-V an OSearch, SPSearch or SQL database component for SharePoint Unreferenced file: A component consists of a group of files that are "integrated" together. If an individual file is not referenced by any component, it is "unreferenced" and is useless for component-level restore. However, it can be restored as a pure file (for troubleshooting purposes, etc.). Incomplete component: If any referenced file is missing from a component, that component is "incomplete" and cannot be restored (however the included individual files can still be restored as pure files). Unreferenced files and incomplete components are usually useless and should be removed. However, you may want to keep them for some reason (e.g. to restore as pure files to manually fix the component, or if the files might be referenced later). Delete unreferenced files: If selected, this retention rule will delete any unreferenced files (see above). Delete incomplete components: If selected, this retention rule will delete any incomplete components (see above).
Retention Rule Wizard - Delete Options

The Delete Options (for files that have been removed from the backup source) will always apply. They are the first rules that are applied when a Retention Rule is enforced on a backup set.
Delete Options If files are removed from source after [...] Delete options only apply to files that the DS-Client detects have been removed from the backup source. Delete if a file was removed from the backup source, and this amount of time has passed since it was removed. Keep generations [...]: If specified, this number of generations of the file will be kept online (the latest generations are kept). This option can be used if you are using a third-party storage management (HSM) solution that migrates infrequently used files from the source, and leaves a small (size) placeholder/stub in its place. If DS-Client detects a placeholder / stub is created on the source, the assumption is that the file is already protected by the third-party solution, and does not need to be stored online. Only the backup of the placeholder/ stub will remain online. Delete generations prior to the stub: The latest placeholder or stub will be kept on DS-System. All generations prior to it will be deleted. Delete non-stub generations prior to the stub: Keeps only the generations that are placeholders or stubs. All other generations prior to the latest stub will be deleted.
If a placeholder/stub is detected on the source [Windows DS-Client only]
Retention Rule Wizard - Local Storage Retention Options

Use this screen to define the retention options for data in the local storage buffer. When this Retention Rule is assigned to a backup set that is configured for Local Storage, it changes the behavior of the Local Storage (for that backup set). Instead of a snapshot of the latest generation, local storage will backup the same number of generations as are online (on DS-System).


Confidential.
NOTE THE STORAGE IMPLICATIONS: The local storage could grow substantially, therefore the Retention Rule should be enforced regularly.
Time-based local retention Generations of a file that fit these categories will be kept on Local Storage. Everything else will be deleted from the Local Storage. Keep all generations The latest generation is always kept. All older generations that fall within this time for [...] period will be kept (while those that do not will be deleted). Deletion of files Check to enable this option. These options only apply to backed up files that DS-Client detects were deleted from the backup source. A backed up file qualifies for delete if: After [...]: DS-Client detects this amount of time has passed since the file was removed from the backup source. Keep generations: Specify the number of generations of the file to keep. The generations that are kept will be counted starting from the latest one. If 0 (zero), the entire file is deleted (all generations).
If files are removed from source
Retention Rule Wizard - Time Retention Options

Use this screen to define the time retention options. When a Retention Rule is enforced on a backup set, the process will delete all of that backup sets data, except for file generations that fall into one of these selected time-retention options. The retention options in a Retention Rule can overlap, with the result being that the option that leaves the most generations for the longest time is applied.
Time-based retention options Generations of a file that fit these categories will be kept. Everything else will be deleted. For Regular backup sets, this deletes data from online storage (on DS-System). For Local-Only backup sets, this deletes data from local storage (because Local-Only backup sets are exactly like Regular backup sets except that they backup to the DS-Clients local storage). The specified number of generations of a file will be kept. Keep most recent generations Any generations over this number will be deleted (unless they qualify [...] for another retention option). Keep all generations for the last [...] All generations that fall within this time period will be kept. Any generations outside this time period will be deleted (unless they qualify for another retention option). Each line in the list is a different time-based retention option that applies to this Retention Rule. This list allows you define more complex retention options. Add: Click to add a Time Retention Rule (Opens the New Time Retention Option screen.) Edit: Click to edit the highlighted Time Retention Option. Remove: Click to delete the highlighted Time Retention Option.
Time Retention Option List
Scales
(Win32 Only) Use this screen to adjust the scale for the associated Storage Summary information. This is useful if the difference in amounts between the scales are large, but you still want to have a meaningful graph.
Amount Files

Confidential.
Time
Scan Monitor screen

LAN STORAGE DISCOVERY TOOL The Scan Monitor displays the scanned shares on the LAN. It displays a snapshot of the latest share information scanned by the LAN Analyze process.
Scan List Enabled/Disabled Share Name Shared Path Follow File System Files Directories Size Last Scan Start Last Scan End Connect As Description Scan Monitor Options Show disabled shares Refresh every ... seconds Check to display any disabled shares. Uncheck to shorten the list to only those shares that are enabled. Set the interval to update the information in the Scan Monitor. List of scanned shares Icon shows whether the share has been enabled or disabled from the Scan Process. Shows the computer name and share name. Shows the path on the computer. Indicates if the scan will follow Reparse Points and scan their destination location (NTFS only). File system of the share. Number of files in the share. Number of directories in the share. Size of the share (in bytes). Date and time the share was last scanned. Date and time the share was last scanned. Shows the Username to connect to the share. Additional information regarding the share.
Scan Shares screen

LAN STORAGE DISCOVERY TOOL This screen searches the shares.
Share List Skip files smaller than [] KB Delete scanned files from DB (smaller than [] KB) Threads Scan Opens the Share List. Does not scan files smaller than the specified size (in KB). This will shorten the time to scan the majority of the LAN. Removes any files smaller than the specified size (in KB) from the database. Set the number of threads to use for the scan. The more threads, the faster the scan. Start the scan. The Activity Monitor opens for the Scan Process.
Schedule Calendar
Use this screen to view the backup sets scheduled to run on the DS-Client.
Schedule(s) Week Starting You may choose a specific Schedule to display, or select "All Schedules". Select the starting day of the week you would like to display. The default is the current week.
Confidential.

Display Interval
Select the interval of schedule cells to display. The default is per hour. The numbers that appear in each cell represent the number of backup activities scheduled / performed in that period. Numbers may appear different in the following cases: Bold (Scheduled only) - The number of activities in the period exceeds the Maximum Concurrent Activities (set in the Registry for Windows, set in the <DS-Client HOME>/ etc/dsclient.cfg file for Linux). The number in bold is the actual maximum concurrent amount allowed. Light Green (Scheduled / Performed) - A backup set in the period overlaps with an Admin process. Gray (Performed only) - A backup set in the period did not complete before the stop limit time. The calendar will change, depending on the selection in the Schedule(s) list. If you select All Schedules, the display will show every active schedule layered on top of each other. If you select an individual schedule, you will only see the time(s) when that schedule will run (and any Admin processes).
Cell Numbers
Cell Colors (Legend)
The color of a time cell represents the type of schedule that will run in that period: Admin (Dark Blue) - The schedule is a Daily or Weekly Admin. Regular (Yellow) - The schedule will run once during a fixed start and end period. Recurring (Dark Green) - The schedule is configured with a Detail Frequency that will run more than once during the scheduled period. No End (Light Blue) - The schedule is configured with no fixed Ending at time. Overlapped (Red) - More than one schedule will run in that period. Discontinued (White - Performed only) - The schedule no longer applies.
Schedule screen
This screen allows Administrators and Backup Operators to create or modify Schedules. A Schedule is composed of one or more Details. Each Detail represents one specific set of tasks that will run at the defined frequency for the schedule.
Schedule Name Enter or change the name of this Schedule. Administrator only Specifies that only Administrators can use this Schedule. (Windows DS-Client only) DS-Client on portable computer Indicates this schedule will be used by DS-Clients on laptops. The Schedule will check for a network connection to the DS-System. If it does not exist, the scheduled task(s) will not start. The DS-Client will launch a popup message if the portable schedule misses more than two scheduled backups. Allows you to set a CPU limit for the DS-Client service process. This is useful if the portable computer is in use for other processes. Use this list to select the detail you want to edit. New details will display <Detail_Type>:<new> until they are saved. An existing detail will have a unique number assigned to it (e.g. Daily:3). For Java DS-User, all details in the Detail List also appear in the tree on the left-hand panel of this screen. Check to create a "negative" detail this will specifically not run a backup (or any other tasks) at the time and date of the detail. It will override any other details that are scheduled to run at that time. Click to create a new detail.
Confidential.
Limit CPU Usage to [...]% Details
Detail List
Excluded New

Delete Copy Occurs One time Daily
Deletes the selected detail from the Detail List Copies an existing detail (from any of the existing schedules). Opens the Select Schedule Detail screen. Enter the date and time to run the scheduled task(s) once. Displays the Daily tab. To specify a daily schedule, enter the frequency of the Detail in the number field. (For example: if you enter "3", it means the Schedule will run every third day. The intervals are based on the Start Date of this Detail.) [Default] Displays the Weekly tab. To specify a weekly schedule, enter the frequency of the Detail in the number field. (For example: if you enter "2", it means the schedule will run every second week. The intervals are based on the Start Date of this detail.) You may also select the day(s) during the week that this schedule will run, by checking and unchecking the appropriate days. Displays the Monthly tab. To specify a monthly schedule, select the frequency of the Detail from the two radio button options: Day - Specify a day (from 1-28) of each month (or interval of months) to perform a backup The - Specify the day (1st, 2nd, 3rd, 4th, or last) and associated weekday (Sunday-Saturday, day, weekday, or weekend day), of each month (or interval of months) to perform a backup (For example "the last Friday of every 3 months"). [Default] Specifies a backup (or any other tasks) will occur once, during the time specified. Specifies that backups (or any other tasks) occur every n number of hours, during the time window specified. If you select this frequency, you must specify an Ending at time. Indicates the start time for this Detail. You can specify an end time to create a time window. The drop-down list allows you to specify the number of days in the window (from Same day up to in 9 days). Any scheduled task(s) will terminate if the Ending at time is reached. You must specify a start date. For new Details, the default is the current date. The start date is important, since it will be used to determine interval times like "every 3rd month". (Optional) You may specify an end date for the schedule period. This Detail will cease to apply to the Schedule after the end date.
Weekly
Monthly
Detail Frequency Occurs once Occurs every [...] hours Starting at Ending at Detail Period Start date End date
Tasks Shows the tasks (in order) that this schedule detail will perform. 1. Perform Backup 2. Enforce Retention Check to include a backup task for this detail. Check to enforce the Retention Rules for each backup set. For a description of this process, see About Retention Rules on page 85. Check to include a Validation task for this detail. The Verify Encryption Key screen appears and you must enter them before you can proceed. Once you have entered the Encryption Keys, you can click >> to open the Scheduled Validation Options screen. For a description of this process, see Validation of Online Storage on page 276.
3. Perform Validation


Confidential.
4. Perform BLM
Check to include a BLM task for this detail. Click >> to open the Select BLM Options screen. For a description of this process, see Backup Lifecycle Management (BLM) on page 289. Check to start the Scan of LAN Shares task for this detail. Since Scanning the Shares may take quite some time, this option for scheduling the task is provided. See: Step 2. Scan Shares on page 334 in the section LAN Storage Discovery Tool on page 329.
5. Start LAN Scan Shares
Click to include a Clean Local-Only Trash task for this detail. 6. Clean Local-Only Trash For a description of this process, see Deleting Local-Only backup set data & Clean Local-Only Trash on page 181.
Schedule (Win32 Only)

This screen allows you to create or modify the Schedule. This schedule will run at the appointed time(s) for each backup set that is associated with it. This feature allows unattended backups at user-specified times.
Name Perform backup on the following days Starting at Ending at Note 1 If you specify an Ending at time that is more than 12 hours from the Start time, it is possible that the Schedule could run the backup again, once 12 hours have elapsed Shows the name of the Schedule. Select the day(s) you would like to run a scheduled backup. Indicates the time the backup set will start. Specify an end time, in order to limit the backup session to a specific time screen.
Schedule Tab screen

This screen allows you to choose a schedule for this set, or designate the set for manual backups only.
Not Scheduled Scheduled Backup set is only run on demand. Backup set will run based on the selected schedule. Backup set can also be run on demand. Available schedules Contains a pull-down list of available schedules. Edit If you are an administrator or backup operator, you will be able to click this button to edit the selected Schedule. This brings up the Schedule screen with the current Schedule's settings. If you are an administrator or backup operator, you will be able to click this button to create a new Schedule. This brings up the Schedule screen. Note: Only Administrators or Backup Operators may add new schedules. This section shows a description of the frequency and times of the selected schedule.
New Description
Scheduled Delete Options

Use this screen to set the parameters for scheduled delete.


Confidential.
Scheduled Validation Options

Use this screen to set the Validation Options to be used for all backup sets using this Backup Schedule.
Validate last generation only Exclude files deleted from source Resume from previously interrupted location Select to validate only the latest generation of backup data for the selected backup set. Select to skip validation of files that have been deleted from the source computer. Select to configure this Schedule to resume validation from the point of interruption if the last scheduled Validation did not finish. This is useful for large backup sets that might not be completed in the Schedules time window.
Select a Backup Session

The Select a Backup Session screen allows you to choose the specific backup session that you would like to work with.
Selection Selected time Revert Shows the selected backup session. Click to revert to the default selection (when this screen was opened).
Known Backup Sessions List Click on a backup session to select it. Icon Start time End time Errors Files Online Amount Activity ID Note 1 You may see only Session Start information in a list. This can occur due to recovery of orphaned backup sets. This indicates the DS-Client does not have an Activity Log record for this session. Shows if the session was CDP. Shows the time that the backup session began. Shows the time that the backup session finished. Shows if any errors occurred during the backup session. Shows the number of files backed up during the session. Shows the size of online files. Shows the corresponding Session ID number.
Select a Deletion Time screen

Use this screen to select a backup session. Only backup sessions when deleted files were detected are displayed.
Deletion Time Deleted Files Select Date and time of the backup session when file(s) were detected as having been deleted from the source. Number of deleted files detected in that session. If those files are still backed up, they are flagged as deleted on the source. Select the highlighted session.


Confidential.
Select a List / Customer List / Document Library (SharePoint Item-Level)

After you have chosen a Site Collection or Sub-Site, you can use this screen to choose a specific List, Customer List or Document Library from the Sub-Site (or entire Site Collection).
Lists, Customer Lists, and Document Libraries The items that are displayed depend on the Sub-Site that was selected. If the entire Site Collection was selected, all the SharePoint items available for restore are visible. Each item is either a List, Customer List, or Document Library containing its own set of items from the SharePoint database. You can select one, several, or all of the items that appear. Next / Finish: If you are selecting an entire list, click the Finish button. If you are selecting a list item, click the Next button.
Select a schedule for scanning

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to choose a schedule for this scan, or designate it for manual scans only.
Not Scheduled Scheduled Scan is only run on demand. Scan will run based on the selected schedule. Scan can also be run on demand. Available schedules Contains a pull-down list of available schedules. If you are an administrator or backup operator, you will be able to click this button to edit the selected Schedule. This brings up the Schedule screen with the current Schedule's settings. If you are an administrator or backup operator, you will be able to click this button to create a new Schedule. This brings up the Schedule screen. Note: Only Administrators or Backup Operators may add new schedules. This section shows a description of the frequency and times of the selected schedule. The scan will be the sixth task to run (in order of precedence).
Edit
New Description
Select a site collection / sub-site (SharePoint Item-Level)

Use this screen to choose the entire Site Collection for restore or limit the selection to a specific sub-site.
Site Collection List You can make the following selections in this screen. Site Collection: Select the top folder / if you want to restore the from the entire SharePoint site collection. Sub-Site: Select any of the sub-folders if you only want to restore items from that particular sub-site. Lists: Highlight the folder containing the List, Customer List, or Document Library you want to restore, then click Add List. List Item: Highlight the folder containing the List, Customer List, or Document Library with the item(s) you want to restore, then click Add List Item. Add Add Lists Adds the highlighted folder (Site Collection or Sub-Site) to the Restore Items list. Selecting this level will prompt you with the following wizard pages: Select a List / Customer List / Document Library (SharePoint Item-Level) The most granular (specific) level. Selecting this level will prompt you with the following wizard pages: Select a List / Customer List / Document Library (SharePoint Item-Level) Select SharePoint List Item (SharePoint Item-Level)
Confidential.
Add List Item

Select Access Intervals screen

Color Access Time Add Remove Share Select the color this extension will display in the graph. Select the access time interval. Adds a new line to the extensions search list Removes the highlighted line from the extensions list. Select <All> or a specific share.
Select Applications (System i Server)

Use this screen to create or modify an application.
Application Name Enter a name or select from the list.
Select Backup Set

[This topic is not currently in use.] Use the Select Backup Set Tab to select the backup set that you want to work with. To search through the available backup sets, browse through the graphical tree by double clicking, where appropriate.
Backup Set Tree Detailed View This section shows the available backup sets. Displays backup sets grouped in the order \Network\Node\Set\User.
Group by User Displays backup sets grouped in the order \User\Network\Node\Set. (only with Detailed View checked) Properties Note 1 You will only be able to view sets to which you have sufficient rights. When you have highlighted a backup set in the graphical display, you can click this button to bring up the Backup Set Properties screen.
Select Backup Sets

Use this screen to browse and select a backup set to work with.
Select Backup Sets (Password Management)

Use this screen to edit the list of backup sets that will use the selected user credentials.
Available Backup Set Credentials Checkbox Computer Set Name Owner OK Select or remove a backup set association with this box. Shows the target backup computer. Shows the name of the backup set. Shows the current owner of the backup set. Click to associate the selected backup sets with the user.


Confidential.
Select BLM Options

Archive packages are specific to a particular backup set. The default (if these options are not selected) is for each BLM Request to be added to the current Archive Package on the BLM Archiver. Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. You must specify when the package will be closed: at session start - makes a new Archive Package. This means the previous package (if one exists) will be closed, and the new request will go to the new package. at session end - uses the current Archive Package. This means the new request will go to the current package, and after it finishes, the package will be closed. Once a package is closed, no new data will be added. Subsequent archiving requests will create a new archive package.
Archive Options
Select to allow the Archive Package to contain references to older packages. This may Reference previsave space by removing data redundancy. ous archive pack The default (if this option is not selected) is for each Archive Package to contain all ages of the required files. Latest generation - Creates a BLM Archive containing the latest generation of all Generations to items selected. include All generations - Creates a BLM Archive containing all the (online) generations of all items selected.
Select BLM Options (Request BLM Wizard)

Archive packages are specific to a particular backup set. The default (if these options are not selected) is for each BLM Request to be added to the current Archive Package on the BLM Archiver. Each Archive Package is automatically time-stamped. To make searching Archive Packages easier, you can add your own label (alphanumeric string). Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. You must specify when the package will be closed: at session start - makes a new Archive Package. This means the previous package (if one exists) will be closed, and the new request will go to the new package. at session end - uses the current Archive Package. This means the new request will go to the current package, and after it finishes, the package will be closed. Once a package is closed, no new data will be added. Subsequent archiving requests will create a new archive package.
Archive Options Archive Label
Select to allow the Archive Package to contain references to older packages. This may Reference previsave space by removing data redundancy. ous archive pack The default (if this option is not selected) is for each Archive Package to contain all ages of the required files. Latest generation - Creates a BLM Archive containing the latest generation of all Generations to items selected. include All generations - Creates a BLM Archive containing all the (online) generations of all items selected.


Confidential.
Select BLM Restore Path screen

Specify the path from which the DS-Client will read the restore data:
Computer Directory Click >> to open the Select the Computer screen. Click >> to open the Select Directory screen.
Select Columns
Use this screen to specify the columns you want to appear in the Monitor screen. Settings are saved, and will be maintained for the next time you work with DS-User. Simply highlight an item name, then click the appropriate arrow to move between sections. Use the up/down arrows to change the order of items in the column.
Available Columns Lists the column items that have not been selected for display in the Monitor screen. Selected Columns Lists the column items that are selected for display in the Monitor screen.
Select database restore location screen (DB2)

[Linux DS-Client] Use this tab to select the database restore and destination options.
Restore To Original Location: Alternate Location: Dump to [Default] Restores files to the original location from which they were backed up. Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server. This field shows the location for the database dump. Click >> to change the specified path. This brings up the Select Directory screen. This field only appears if the backup set was created with the DB2 Online Backup option selected (Set Properties Options Tab screen). This is the path where the DB2 Archive Log files (that you are about to restore) will be retrieved by the User Exit program. Click [...] to specify the path. This opens the Select Directory screen.
Archive Log Path
Shows a list of the selected databases for restore, and their restore destination(s). Database Mapping List If you select the Restore as Pure Files option, you can change the restore destination by modifying the appropriate column. Icon - Shows an icon to indicate whether the restore item is a database. Source - Shows the source database's name. Destination - Shows the database where the backup will be restored. Double Click on this cell to open a drop down list of all the available databases on the specified restore database server. Destination (Restore as Pure Files) - Shows the available shares where the dump can be restored. Restore to (Restore as Pure Files) - Shows the path on the destination share where the dump will be restored. This option will only restore the dump file to the specified location. The dump Restore as Pure Files will not be loaded to the database. Notes 1 See the Knowledge Base article: Backup / Restore of DB2 Database Servers.


Confidential.
Select database restore location screen (Microsoft Exchange)

Use this tab to select the database restore and destination options.
Restore To Original Location: Alternate Location: Restore Options Mount Database after Restore Restore via DS-Client pipe Dismount if Needed Keep existing files Check to automatically mount the database after restore. Check to open a named pipe through the DS-Client to the target database for restore. This avoids the need for a buffer directory. Check to automatically try to dismount database (if mounted). Keep all existing files in the restore directory. Renames the existing files, until all restore items are successfully restored. This takes more space, but avoids problems of failed restores (if a restore fails without this option, the Microsoft Exchange Server will not function). If this option is selected, then in case of failure, the original files will be renamed back and the Microsoft Exchange database will be mounted. This is a location on the destination Exchange computer. There must be sufficient space to accommodate the log and patch files. [Default] Restores files to the original location from which they were backed up. Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server.
Delete all existing files Delete all of the existing files in the restore directory.
Rename existing files
Temporary directory for logs
Select database restore location screen (MS SQL / PostgreSQL / MySQL)

Restore To Original Location: Alternate Location: Dump to (MS SQL) [Default] Restores files to the original location from which they were backed up. Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server. This field shows the location for the database dump. Click >> to change the specified path. This brings up the Select share & path for the database / data dump screen. Shows a list of the selected items for restore, and their restore destination(s). You can change the restore destination by modifying the appropriate column. Icon - Shows an icon to indicate the type of restore item. Source - Shows the source item's name. Destination - Shows the database where the backup will be restored. Double Click on this cell to open a drop down list of all the available databases on the specified restore database server.
Database Mapping List
Restore Options Restore only the dump This option will only restore the dump file to the specified location. The dump file(s) will not be loaded to the database. (This option is not available if DS-Client (Windows DS-Client) Buffer or DS-Client Pipe is specified in the Dump To field.) Restore as Pure Files (Linux DS-Client) Restore Path This option is available if "Alternate Location" is selected. It will restore only the data. This option will only restore the dump file to the specified location. The dump will not be loaded to the database. When restoring to an alternate location, you can specify the path for the log and data files separately. Opens the Select Restore Path screen.


Confidential.
This option only applies to restores to the original location. Off (default) - The restored files will be placed on the target instance's Preserve original datadefault path(s). base file location On - The restore files must be placed in their original path(s). If the original path(s) do not exist, the restore will fail. Ask for Network Credentials Prompts you to enter a valid user name and password for the selected computer. This option is available for BLM and Disc/Tape restores, since the original backup set may no longer be on the DS-Client. If you do not select this option, DS-Client uses its own (service) credentials to access the network location. Prompts you to enter a valid user name and password for the database server. This option is available for BLM and Disc/Tape restores, since the original backup set may no longer be on the DS-Client. For MS SQL: If you do not select this option, DS-Client uses its own (service) credentials to access the database server. For MySQL and PostgreSQL: You must select this option and provide credentials to access the database server. If restoring to an alternate location, the database and table must exist on the database server where you are restoring. Table restores will not restore indexes.
Ask for Database Credentials (Databases only)
Notes 1 2
Select database restore location screen (Oracle)

Restore To Original Location: Alternate Location: Dump to [Default] Restores files to the original location from which they were backed up. Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server. This field shows the location for the database dump. Click >> to change the specified path. This brings up the Select share & path for the database / data dump screen. Shows a list of the selected items for restore, and their restore destination(s). Icon - Shows an icon to indicate whether the restore item is a Tablespace, Archived Logs, or the Control File. Source - Shows the source item's name. Destination - Shows the database where the backup will be restored.
Database Mapping List
Restore Options Restore only the dump This option will only restore the dump file to the specified location. The dump file(s) will not be loaded to the database. (This option is not available if DS-Client (Windows DS-Client) Buffer or DS-Client Pipe is specified in the Dump To field.) Restore as Pure Files (Linux DS-Client) This option will only restore the dump file to the specified location. The dump will not be loaded to the database. (This option is not available if DS-Client Buffer or DS-Client Pipe is specified in the Dump To field.) [Applies to restores of the Control File] After restoring the control file, all temporary tablespaces with local extent management will not have any "temp" file. You must still manually add the "temp" file(s) after restore in order for the Oracle database to operate correctly. Check to have DS-Client automatically add a temp file for each of the tablespaces (in the default location). See the Knowledge Base article: Backup / Restore of Oracle Database Servers.
Create temp file(s)
Notes 1


Confidential.
Select database restore location screen (SharePoint)

Use this screen to choose the target MS SQL server where you will restore the SharePoint database.
Select Computer Instance Name Physical File Location You must select a computer Click [>>] to browse for the computer. Once you have selected the computer with the MS SQL database server, you must select the SQL Instance to restore to. You must select a physical location where the data will be restored on the selected target computer Click [>>] to browse for the destination folder. The mapping list is automatically filled, based on your target computer and instance selections. Source Database: This is the original SharePoint database name. Destination Database: This shows the name of the database as it will appear when restored to the selected target MS SQL server.
Database mapping
Select directories / files (Restore / BLM / Delete / Validation)

This screen displays the contents of the backup set you have chosen.
Directory / Database Tree Shows the files and directories (or databases) available, based on the Backup Range and Storage selection (see Change Date). Check or uncheck a box to select/unselect that item. Click to open or close the Files List section of this screen. A different list appears, depending on if you are in the Restore Wizard, BLM Wizard, Delete Wizard or Validation Wizard: Files List (Restore Wizard) Files List (BLM Wizard) Files List (Delete Wizard) Files List (Validation Wizard) - same as Files List (Restore Wizard) If selected, this Wizard will show the number of files selected and calculate the total amount selected (based on stream size) based on your selection in the Directory / Database Tree. In the Activity Monitor, the progress section will estimate the completion time. Note: By default, this option is off since very large selections may require some time for the GUI to perform the calculations. This box is checked by default. When you select a directory, all of its subdirectories will be automatically included with it. Uncheck to select only the files in a selected directory (and not any subdirectories). Enter a filter using the * character as a wildcard (ex: *.exe or dat*) if you want to narrow the list of files. Click Show Files to refresh the File List and show the files that correspond to the specified filter. This filter is case insensitive.
Show Files / Hide Files
Options
Calculate amount
Include SubDirs (File System Backups) Filter (File System Backups)
Click to change the filter you wish to apply for restore. Opens the Add / Modify Filter Change Filter screen. This filter will allow only those E-Mails that match the pattern specified to be (E-Mail Backups) restored. Selection Shows the items you have selected so far. This opens the Selection screen. Click to bring up the Find Backed Up File screen. This will allow you to search through Find File (File the backup set for a specific file or file pattern. (Note: you must open the Files List by System Backups) clicking the Show Files button first.) Advanced [If this button is enabled, you can make further selections.] Click to bring up the Advanced Options screen.
Confidential.

Files List (Restore Wizard) This list appears for the Restore Wizard when Show Files is clicked: Box: Check to select the listed file Local Storage column: This column only appears if the backup set is configured to use Local Storage. If an L appears, it means that generation of the file is also in Local Storage. If a generation in Local Storage is selected, that copy will be restored (which offers the fastest restore speed). The Selected total of ... counter at the bottom of the screen will contain an additional set of numbers in parentheses (). These represent the totals for files in Local Storage. Name: File Name Size: The protected size of this generation of the file. Last Modified: Date and Time file was last modified File Info You may select a specific generation of the highlighted file for restore. Opens the Backup Generations for ... screen. Show Modified: Shows any modified files in the selected directory. The DS-Client will scan the backup source, and compare the files with the backup log. Files in the list Show Modified / that do not exist on the source, or are different (changed), will be highlighted. Add Modified Add Modified: If modified files exist, this button changes to Add Modified. Click to add all of the modified files to the restore selection. Shows a list of any archived generations for the folder that is highlighted in the DirectoShow Archived ries / Database Tree. Opens the Files in Directory ... (Select Items for Backup) screen. Vss Component (VSS-aware backup sets) This button appears if you are restoring (or deleting) a VSS-aware backup set with the (default) VSS Restore method. (It does not appear for the File Restore method.) Opens a read-only Vss Component details for [...] screen, which displays the components of the selected restore item. This screen is for information only.
Files List (BLM Wizard) This list appears when Show Files is clicked in the Request BLM Wizard or BLM Restore Wizard: The list and buttons that appear have the same meaning as the Files List (Restore Wizard). Files List (Delete Wizard) This list appears for the Delete Wizard when Show Files is clicked: Box: Check to select the listed file. #: Number of Generations available to delete (based on your specifications of how many generations to leave) Size: The combined total size of the selected generations of the file for delete. Name: File Name Remove Time: Date and Time file was detected by DS-Client to have been removed from the source. File Info You view the generation of the highlighted file that you are going to delete. Opens the Backup Generations for ... screen.
Select Directory
Use this screen to browse through the tree and select the share\directory path you want to use.
Shares and Directories Tree Select Shows the available shares and directories. Click to select the highlighted directory.
Select Disc / Tape Restore Path screen

Specify the path from which the DS-Client will read the restore data:
Computer Directory Click >> to open the Select the Computer screen. Click >> to open the Select Directory screen.


Confidential.
Encryption Key
This field activates if USER-DEFINED encryption has been applied to the data. Enter the key to proceed with decryption. Import: You can import from any valid file containing an exported key string. Export: You can use this GUI to export the text in this field (in encrypted format) to a text file for distribution, if necessary.
Select DS-Client (Print Global Report)

(Java DS-User only) Use this screen to create a list of DS-Clients to include in the Global Report you wish to print.
DS-Client Connection Entry List Add Auto Search Modify Remove Load Name - Computer name (or other descriptive name) IP Address - IP address of the DS-Client User Name - User account to connect to the corresponding DS-Client computer. From - Server where the User Name and password will be authenticated. Click to add a DS-Client to the DS-Client Connection Entry List. Opens the Add / Modify DS-Client Connection Entry (Print Global Report) screen. Click to search for all visible DS-Clients on the network. Opens the DS-Clients Auto Search (Print Global Report) screen. Modify the highlighted DS-Client connection entry. Opens the Add / Modify DS-Client Connection Entry (Print Global Report) screen. Delete the highlighted DS-Client from the list. Loads the DS-Client Connection Entry List and credentials that are saved in this DSUsers user.ini file. Opens the Enter Lock Key For Credentials (Print Global Report) screen. Saves the current DS-Client Connection Entry List and credentials that are in this screen to this DS-Users user.ini file. Opens the Enter Lock Key For Credentials (Print Global Report) screen.
Save
Select Event #
This screen shows the events from the corresponding Select By period in the Event Log.
Event List Icon Event # Description First Time Count Ignore Select / Deselect Error, Warning or Information icon. Event number. Event description. Date and time of the first occurrence of this event in the corresponding period from the Event Log. Number of occurrences of this event in the corresponding period from the Event Log. Indicates if this event is part of the exclude list. Add or remove the highlighted event(s) from the exclude list.
Select Extensions (Customize Report) screen

Color Extension(s) Add Remove Select the color this extension will display in the graph. Enter the extension without a period "." (e.g.: txt, exe, dll, pdf) Adds a new line to the extensions search list Removes the highlighted line from the extensions list.
Confidential.

Include Total Share
Includes the total of all other files in the search share(s). Select <All> or a specific share.
Select Extensions (Top Report) screen

Select top [] file extensions With greatest size With biggest count Share Include Total Select the number of file extensions to display. Searches for the largest files. Searches for the greatest frequency (number) Select <All> or a specific share. Includes the total of all other files in the search share(s).
Select Filter
FIlter Add Modify Delete OK Select from the list of available filters. Create a new filter. Brings up the Add / Modify Filter screen. Edit the selected filter. Brings up the Add / Modify Filter screen. Deletes the selected filter from the Filter list. Select this filter.
Select Font
Use this screen to select from the available fonts.
Select Group / User screen

These screens allow you to choose a group/user from the listed selection. If you are editing a backup set's permissions, it allows you to specify permissions for other users with your backup set. Depending from where you have opened this screen, some options may appear different. All possible options are described below.
Group/Name Description/Full Name From Select Shows the available Groups and/or User Names. Shows the description of a group, or the full name of a User. Shows the server where the user or group is defined. Click to choose the highlighted selection.
Select how you want to delete screen

Use this screen to narrow the display of files and directories for delete.
Time based Delete Options From To Click [>>] to select the earliest time. This opens the Select a Backup Session screen. Click [>>] to select the earliest time. This opens the Select a Backup Session screen.


Confidential.
Leave last [] generations
Allows you to specify the number of generation to leave (i.e. not select for delete) from the specified period. If you specify a number, you will only be able to select files and directories that have more generations, than the number specified in this field. By default, this field is blank. This filter allows you to remove backed up directories and files that were intentionally deleted from the source computer. Enter a number in this field to show only directories and files that were deleted from the source computer more than that number of days ago.
Only data removed since (days ago)
Placeholder / Stub selection [Windows DS-Client] This option can be used if you are using a third-party storage management solution that migrates infrequently used files from the source, and leaves a small (size) placeholder/stub in its place. If DS-Client detects a placeholder / stub is created on the source, the corresponding file on DS-System will be deleted, based on the specified conditions. Keep the last placeholder / stub and subsequent generations The last placeholder or stub will be kept on DS-System, as well as any full file generations that appear after that latest placeholder/stub. Keep all placeholders / stubs All placeholders or stubs will be kept on DS-System, as well as any full file generations that appear after that latest placeholder/stub.
Select how you want to delete (Delete Options) screen

Use this screen to narrow the display of files and directories for delete and specify any delete options.
Archive Options These options relate to displaying generations that have already been pushed to BLM from online storage (i.e. the actual file has been removed from online to BLM). This selection determines if these placeholders (archive stubs) will be displayed in the next screen of the Delete Wizard: Archived Data Placeholders Include: Displays any qualifying placeholders. Exclude: No placeholders are displayed. Only: Only placeholders are displayed (if they meet the other data selection criteria). Regular online files (that have not been pushed to BLM) are not displayed. Delete Options A copy of all data deleted from DS-System during this Selective Delete will be moved to BLM (Backup Lifecycle Management). This tool is provided by your Service Provider from the DS-System. If this option is grayed out but the checkbox is selected, it means the data must be moved to BLM. This occurs if the backup set has the BLM (Infinite Generations) option selected (Backup Set Properties > Options tab). Each Archive Package is automatically time-stamped, but you must add your own label (alphanumeric string) to demand BLM requests. This will make it easier to search an Archive Package. Select to use a new archive package. Otherwise, this Archive request will be added to the current archive package on the BLM Archiver. Archive packages are specific to a particular backup set. Each BLM Request will be added to an Archive Package until it reaches a specified limit (# of files, size, time).
Move to BLM
Session Label
Use new archive package


Confidential.
Select Initial Backup Destination Path

Specify the path where the DS-Client will write the Initial Backup data.
This screen is slightly different, depending on the type of DS-Client: Windows DS-Client Linux DS-Client Windows DS-Client Computer Directory Click >> to open the Select the computer screen screen. Click >> to open the Select Directory screen. Dont Encrypt (NONE): The meta-data (the descriptive files used to manage the Initial Backup) will not be encrypted. Encrypt with DS-Client Private Key (CLIENT): The meta-data (and Initial Backup data) will be encrypted with a key based on this DS-Clients signature. The data can only be imported to the same registered DS-Client account on the DS-System. Encrypt with specified Key (USER-DEFINED): Enter (or import) your own alphanumeric key of up to 32 characters for the encryption. You can export this key (in encrypted format) to a text file for distribution, if necessary. Click >> to open the Select Directory screen.
Select encryption method
Linux DS-Client Backup Path Select an encryption method. NONE: The meta-data (the descriptive files used to manage the Initial Backup) will not be encrypted. CLIENT: The meta-data (and Initial Backup data) will be encrypted with a key Metadata Encryption based on this DS-Clients signature. The data can only be imported to the same registered DS-Client account on the DS-System. USER-DEFINED: Enter (or import) your own alpha-numeric key of up to 32 characters for the encryption. You can export this key (in encrypted format) to a text file for distribution, if necessary. This field activates if USER-DEFINED encryption is selected. Enter your own alphanumeric key of up to 32 characters for the encryption. Import: You can import from any valid file containing an exported key string. Export: You can export this key (in encrypted format) to a text file for distribution, if necessary.
Encryption Key
Select Items for Backup Set screen

Use this screen to browse and select what you want to back up (or restore).
Shares & Directories List / Databases List Shows the shares and directories available to the backup set. For database backups, this screen shows a list of databases. For SharePoint Granular Item-Level Restores, this screen shows a list of databases. You must select the database containing the restored SharePoint database you want to use for the Item-Level restore. Add To add an entire directory, browse through the Shares & Directories List until the directory you want appears and Click it. Note: You can add only one directory at a time. Subdirectories are automatically included, unless you clear the Include SubDirs check box. Excluding will prevent the selected directory from being backed up. Its parent directory must be selected for backup. For database backups this allows you to prevent the selected database from being backed up if the full database instance has been selected for backup.
Exclude


Confidential.
RegEx
Regular Expression is a more specific form of the Exclude function. It allows you to exclude at the filename or filepattern level. However, you must learn the Regular Expression software syntax. Opens the Regular Expression screen. To add specific files, browse through the Shares & Directories List until the directory the files are stored in appears. Click Files. A screen showing the list of files in that directory appears. Highlight the file(s) you wish to add to the backup set. Click to backup specific objects from a library (e.g. programs or data areas). Opens the Files in Directory ... (Select Items for Backup) screen. If you wish to be able to quickly restore individual objects, check this box before you press the "Add" button. (Note: this option will reduce the backup speed and increase the disk space required. The performance will also be affected if the libraries contain a large number of small objects.) The icon for "individual objects" contains an additional blue "+" sign. To add files that match a filter, in the Filter field, enter the file pattern that you would like to search for in the selected directory. (e.g. *.doc will search the directory for all files with the .doc file extension.) Subdirectories are automatically included, unless you clear this check box.
Files Objects (System i)
Individual obj (System i)
Filter Include SubDirs
Backup Items Selected Shows the Items selected for backup. The icon describes the type of item and whether its subdirectories are included. The share and path is listed, and the extension indicates if a filter is used. Remove Removes the highlighted item from the Selected Items for Backup list. Note: Removing a selected item for backup will not remove previous backups of that item. (You must use the delete function.) [Windows DS-Client - File System Backup Set only] Click to view a list of files that failed to back up. This opens the Failed Files During Backup screen. This is a cumulative list of files that failed since the backup set was created. Allows you to modify an existing Regular Expression. Opens the Regular Expression screen for the highlighted item. Click to define System i applications from a list of all the libraries on the target System i server. Opens the Modify Applications (System i Server) screen.
Failed Files (Edit Items) Modify Applications (System i)
Select Items for Backup (Linux DS-Client)

Use this screen to browse and select the items to back up.
Shares & Directories List / Databases List Shows the shares and directories available to the backup set. For database backups, this screen shows a list of databases. Add To add an entire directory, browse through the Shares & Directories List until the directory you want appears and Click it. Note: You can add only one directory at a time. Subdirectories are automatically included, unless you clear the Include SubDirs check box. Excluding will prevent the selected directory from being backed up. Its parent directory must be selected for backup. Adds all the database items in the list (including Tablespaces, Archive logs, and Control Files). To add specific files, browse through the Shares & Directories List until the directory the files are stored in appears. Click Files. A screen showing the list of files in that directory appears. Highlight the file(s) you wish to add to the backup set.
Exclude Add All (Oracle) Files


Confidential.
Items (Databases) RegEx
Click this button to view information about the items highlighted in the Databases List. A read-only Files in Directory ... (Select Items for Backup) screen appears. Regular Expression is a more specific form of the Exclude function. It allows you to exclude at the filename or filepattern level. However, you must learn the Regular Expression software syntax. Opens the Regular Expression screen. To add files that match a filter, in the Filter field, enter the file pattern that you would like to search for in the selected directory. (e.g. *.doc will search the directory for all files with the .doc file extension.) Click to backup specific objects from a library (e.g. programs or data areas). Opens the Files in Directory ... (Select Items for Backup) screen. If you wish to be able to quickly restore individual objects, check this box before you press the "Add" button. (Note: this option will reduce the backup speed and increase the disk space required. The performance will also be affected if the libraries contain a large number of small objects.) The icon for "individual objects" contains an additional blue "+" sign. Subdirectories are automatically included, unless you clear this check box.
Filter Objects (System i)
Individual obj (System i)
Include SubDirs
Selected Items for backup List Shows the Items selected for backup. The icon describes the type of item and whether its subdirectories are included. The share and path is listed, and the extension indicates if a filter is used. Remove Modify Removes the highlight the item from the Selected Items for Backup list. Note: Removing a selected item for backup will not remove previous backups of that item. (You must use the delete function.) Allows you to modify an existing Regular Expression. Opens the Regular Expression screen for the highlighted item.
Select items for demand backup screen

Use this screen to select all or part of a backup set for immediate backup.
Items & Options for backup Shows a list of the item(s) specified for backup. Checkbox Icon Items Allows you to select or remove items from the demand backup. Lists the type of backup item (directory, file, database, etc.) Lists the path of the backup item. The defaults are set in this backup sets Set Properties Items Tab. Some items may be grayed out (i.e. cannot be changed for demand backups). Letters that appear in this column correspond to the following options: P = Backup permissions / Backup ACL S = Backup Streams E = Extended Attributes X = POSIX ACL D = Run DBCC before backup S = Stop on DBCC errors T = Truncate Transaction Log / Truncate Archived Logs / Backup Transaction Log L = Logical Corruption Check B = Backup Only Current Archived Logs R = Backup Resource A = Backup File Attributes To add or remove an option, highlight the backup item from the list and check or uncheck the option box that appears beneath this list. See below for details about individual options.
Options


Confidential.
Generations (Linux / Mac)
Shows the number of generations configured for the corresponding backup item.
Options Highlight an item from the Items & Options for backup list, then click the checkbox of the option(s) you want to add. Backup permissions / Backup ACL Backup POSIX ACL (Linux) Check this box to backup the file permissions. (ex: ACL on NTFS volumes, or Trustees on NetWare volumes.) This only applies to backups of the Local File System (Linux DS-Client only). Check this box to backup the Extended ACL (if configured). These are the permissions set using the setfacl command (and viewed using the getfacl command). NTFS volumes support multiple streams of data associated with a particular file. Select this option if you have files that contain alternate data streams. To change this option, you must use the Backup Set Properties screen, Backup Set Items Tab. These are the Extended File Attributes. (ex: Transactional and Compressed). The Database Consistency Check (DBCC) verifies database integrity to ensure backup of a valid database dump. If this box is checked, an additional option appears. Truncates the transaction log. MS SQL Server 2000 & MSDE: Transaction Logs are truncated before the database dump. MS Exchange Server: Transaction Logs are truncated after the backup. The database must be configured with FULL or BULK_LOGGED recovery mode, otherwise this option will have no effect. If selected, the DS-Client will dump the Transaction Log and send it to the DS-System in addition to the database(s). Backup Transaction Log (Microsoft SQL 2005 and higher) If selected, the Transaction Logs will also be truncated. The timing of the truncation depends on the Database Backup Policy (see: Set Properties - Options tab). Full - Transaction Logs are truncated before the database dump. Differential - Transaction Logs are truncated before the database dump. Incremental - Transaction Logs are first backed up, and then truncated. If DBCC errors are detected, this option will skip backing up the dump file.
Backup streams (Windows) Backup Eattributes (NetWare) Run DBCC before backup (MS SQL) Truncate transaction log (Microsoft SQL 2000 & MSDE, MS Exchange Server)
Stop on DBCC errors (MS SQL)
Logical Corruption Check (Default is on) Will perform a corruption check on the database prior to (Oracle) backup. Truncate Archived Logs (Oracle) Backup Only Current Archived Logs (Oracle) Backup Resource (Mac) Backup File Attributes (Mac) Clear the Oracle Database logs associated with this item after backup. Check to backup only those logs that are necessary for the Oracle database. This saves backup space, by avoiding backup of any older logs. Leave this box unchecked if you want to backup all log files. Check to backup the Macintosh Resource Fork information. Check to backup the File Attributes for files on the Mac platform.
Select items for network share discovery screen

LAN STORAGE DISCOVERY TOOL


Confidential.
The Share Discovery Wizard helps you to identify all the available backup shares on your LAN. This screen allows you to select which items on your network(s) you wish to scan.
Path Network Tree Add Selected items for Discovery Remove Clean share list Enter a specific IP address or computer name (e.g. 10.10.10.10 or COMPUTER1). Select from the available list of networks, domains/workgroups, and computers. Adds either the Path or the highlighted item from the Network Tree to the Selected items list. Shows the list of items you have selected to scan. Removes the highlighted item from the Selected items list. Check to remove any shares from the previous scan that returned a Scanned Size of 0.
UNIX Support Limitations (Windows DS-Client): 1. The LAN Storage Discovery Tool accesses UNIX via Hummingbird software or via SAMBA software. 2. Soft links and device files will be silently skipped. 3. Hard links are treated like regular files. If two hard links point to the same file, they will be considered as duplicates of each other. 4. "Owner" field will always be empty.
Select items for network share discovery screen (Linux DS-Client)

LAN STORAGE DISCOVERY TOOL The Share Discovery Wizard helps you to identify all the available backup shares on your LAN. This screen allows you to select which items on your network(s) you wish to scan.
Browse Panel (Left Side) Path Network Tree Ask for credentials Enter a specific IP address or computer name (e.g. 10.10.10.10 or COMPUTER1). Select from the available list of networks, domains/workgroups, and computers. Prompts you to enter a valid user name and password for the selected network resource.
Shows the credentials that Linux DS-Client will use to access data on the network sudo' as an alternate resource. user After successful login to the remote source, "sudo" (switch user) will be per(UNIX-SSH only) formed for Linux DS-Client to use these credentials. Advanced Connection The default (if no selection is made) is for DS-Client to run a PERL script Option Click [...] to edit the settings. See Advanced Connection Options (Linux DS-Cli(UNIX-SSH only) ent) for more information. Add Adds either the Path or the highlighted item from the Network Tree to the Selected items list. Any errors will appear in the Message window.
Selection Panel (Right side) Selected items for Discovery Remove Message Window Shows the list of items you have selected to scan. Removes the highlighted item from the Selected items list. Shows any relevant messages.
Select items for scanning


Confidential.
The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. The scan will compare this DS-Clients backup set items with the network resources you choose in this screen.
Path Enter a specific IP address or computer name (e.g. 10.10.10.10 or COMPUTER1). Network Tree Select from the available list of networks, domains/workgroups, and computers. Ask for credentials Add Exclude Subnet Select Prompts you to enter a valid user name and password for the selected network resource. Adds either the Path or the highlighted item from the Network Tree to the Selected items list. Excludes the highlighted item from the Network tree. This only applies to subitems (i.e. the parent must already be selected for discovery in order for a subitem to be excluded). Opens the Add / Exclude Subnet screen. Opens the Add / Exclude item from scanning result screen.
Selected items for Discovery Shows the list of items you have selected to scan. Remove Removes the highlighted item from the Selected items list.
Select options for demand backup screen

Use this screen to specify options for the Demand Backup.
Backup Set Options This section allows you to view and modify the options available for the entire backup set. Use Buffer Detailed log Stop on errors Start at Uses the Use Buffer option. Files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Records all files that are backed up. Sets an error limit, at which a backup will be stopped. Enter the maximum number of errors in the Stop on Errors field to the right. Leave this field blank to start the demand backup immediately. Enter a time, if you wish to delay starting the demand backup until the time specified. Verifies the digital signature between the source and latest generation from online storage for unchanged files. In the (unlikely) event that the signature does not match, it means the online data is not what should be backed up. DS-Client will backup this file again in the current backup session. WARNING: Selecting this option will slow down the demand backup performance significantly, since the unchanged files are normally skipped by a backup. For more information, see the Knowledge Base Article: Digital Signature Verification. Performs a PreScan of all files in the backup set to estimate a time for completion of the backup.
Verify signature for unchanged files
Backup as POSIX PreScan
Open Files This information instructs the DS-Client about how to deal with Open (i.e. locked) files. (If the open file has been locked with Deny write by another process, the backup for this file will fail.) Try deny write Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), place the backup file in 'Allow Write' mode.


Confidential.
Deny write
This mode prevents any other process from writing to the backup file, while the DSClient has it open. DS-Client will not back up the file, if another process has already opened it for write. (You may, however, instruct the DS-Client to retry backing up the open file.) Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), then open in Allow Write mode and lock the file, thereby preventing any process from writing to the file. This ensures that the most recent version of the file is backed up. Allow another process to read/write to the backup file (no restrictions). Since other applications can write to the file while it is being backed up, this may affect file consistency. Specifies the number of times you want the DS-Client to attempt to backup the file. (Maximum of 10 retries). Specifies the interval between retries. (Maximum of 999 seconds).
Prevent write
Allow write Retry times Retry intervals
Windows 2000 & up options These options appear if supported by the backup set source computers Windows Operating System version. However, all selections are grayed out and cannot be changed from this screen. To change any of these selections, you must edit this backup sets properties (Set Properties Advanced Options tab (Windows DS-Client)). Backup data in Remote Storage Backup all data on remote media. Some Windows Operating Systems have the functionality to migrate infrequently accessed data from the local hard drive to directly attached tape libraries. The local disk usage is reduced by replacing the file with a link (shortcut). If disabled, only the link (shortcut file) will be backed up. Backup each instance of a file separately. Some Windows Operating Systems have an optional service 'Single Instance Store' to handle multiple copies of the same file on the computer. Local disk usage is reduced by placing one copy of the file in the Single Instance Store, with links (shortcuts) in all associated directories. If disabled, only the link will be backed up. If you have activated the Single Instance Store Service, check this option. Backup directories (all data) represented by the junction point. Junction points are file links to other directories. If disabled, DS-Client will backup only the link (shortcut). Notes: Junction points that are mounted FAT or FAT32 volumes are not supported.
Follow junction points
Select options for demand backup screen (Linux DS-Client)

Use this screen to specify options for the Demand Backup.
The options in this section are specific to the type of backup set: MySQL backup sets. PgSQL backup sets. Oracle backup sets. DB2 Server backup sets. SSH backup sets. If checked, files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Records all files that are backed up (you may view them in the Activity Log). Check this box to set an error limit, at which a backup will be stopped. Enter the maximum number of errors in the Stop on Errors field to the right.
Additional Backup Set Options
Backup set options Use buffer Detailed log Stop on errors


Confidential.
Start at PreScan
Leave this field blank to start the demand backup immediately. Enter a time, if you wish to delay starting the demand backup until the time specified. Performs a PreScan of all files in the backup set to estimate a time for completion of the backup. MySQL backup sets. Lock tables before inserting data on restore. (See the MySQL manual page for mysqldump for more information.) Prevent changes to data while backup is in progress. (See the MySQL manual page for mysqldump for more information.) Add MySQL specific extensions to the backed up database dump. (See the MySQL manual page for mysqldump for more information.) Specify the style of insert statement from the backed up database dump. (See the MySQL manual page for mysqldump for more information.) Extended - Fast insert. May not be useful for manual loading into non-MySQL databases. Delayed - Uses INSERT DELAYED when inserting rows. Normal - Standard insert. Slower, but may be more portable to other databases. PgSQL backup sets. Will backup only the data, not including the privileges of the database. Dumps data as INSERT commands (instead of COPY). This will make restores very slow, but it will make those backups more portable to other SQL database packages. Oracle backup sets. (Default is on) Will perform a corruption check on the database prior to backup. Check to backup only those logs that are necessary for the Oracle database. This saves backup space, by avoiding backup of any older logs. Leave this box unchecked if you want to backup all log files Clear the Oracle Database logs associated with this item after backup. DB2 Server backup sets. Delete entries from the history file or log files from the active log path. If unchecked, perform Offline DB2 backup. During an offline backup, applications cannot connect to the database. If checked, perform Online DB2 backup. An online backup allows applications to connect to the database and read and write to tables during database backup. Log retain or userexit must be enabled for an online backup. SSH backup sets. Check to backup only the Mount Point itself (not the data under any Mount Point).
Confidential.
Additional Backup Set Options Add locks around insert statements
Lock all tables for read Add MySQL specific table create options
Insert statement type
Additional Backup Set Options Do not backup privileges (Grant / Revoke) Backup data as INSERT, rather than COPY Additional Backup Set Options Logical Corruption Check
Backup only the schema, not the data Dump only the schema (data definitions).
Backup only current archived logs
Truncate archived logs Additional Backup Set Options Prune History / Logfile
Online Backup
Additional Backup Set Options Do not follow the Mount Point

Select options for demand backup screen (Windows database backup sets)
Use this screen to specify options for the Demand Backup of the following Windows database backup sets: Microsoft SQL Server VSS-aware Microsoft SQL Server VSS-aware Microsoft Exchange Server VSS-aware Microsoft SharePoint Server These settings are applied for this backup only.
Backup Set Options Options that appear grayed out cannot be selected from a demand backup. Use Buffer [View only.] This takes the Use Buffer setting from the Set Properties - Options tab (Windows database backup sets).
[View only.] BLM (Infinite Gen This takes the BLM (Infinite Generations) setting from the Set Properties erations) Options tab (Windows database backup sets). Detailed log PreScan Stop on errors Start at Local Storage Records all files that are backed up. If checked, the backup set is flagged to scan all files in the backup set prior to backup, in order to display an estimated completion time for the backup. Sets an error limit, at which a backup will be stopped. Enter the maximum number of errors in the Stop on Errors field to the right. Leave this field blank to start the demand backup immediately. Enter a time, if you wish to delay starting the demand backup until the time specified. [View only.] This takes the Use Local Storage - Save setting from the Set Properties - Options tab (Windows database backup sets). [View only.] This takes the Use Local Storage - Cache setting from the Set Properties Options tab (Windows database backup sets).
Cache
Database backup policy (Windows database backup sets) The default selection depends on the Database Backup Policy selected for this backup set in the Set Properties - Options tab (Windows database backup sets). Some options may not appear, depending on the backup set type and configuration. Default Policy Enforce Perform Full backup Differential backup Incremental backup Shows the configured Windows database backup policy for this set. Select if you want to specify what type of dump will be performed. The options available depend on the settings for this backup set. This backup will perform a full dump of each database. Performs a differential backup unless another full backup is needed (*). The database can be selected with or without the backup transaction log option. Performs an incremental backup unless another full dump is needed (*). The database should be selected without the backup transaction log option. (Even if backup transaction log is selected, that option will be ignored if this backup policy is selected.) The databases Recovery Model must be: full or bulk_logged. [Incremental backup only] [Default is off.] Select if you do not want DS-Client to truncate the Windows database transaction log.
Do not truncate transaction log


Confidential.
(*)
A full dump is needed (other than first time) when: a database has been backed up by another backup set (or manually from the SQL tools); a database has been restored (either from another database or an earlier generation); the database properties have been modified (recovery model switched to simple); local cache is used for the backup set (This can occur for Regular backup sets with the option Transmission cache on local storage, but only when a generation must actually pass through the local cache. If the connection to DS-System is down, then a full dump occurs and is written to the local cache. After that dump, DS-Client continues with the selected database backup policy.) the DS-Client requires a Master generation (configured in the MasterGenerations value of the DS-Client Advanced Parameters - Setup Menu > Configuration > Advanced Tab).
Select Path
Use this screen to select a path.
Computer Directory Path (Linux DS-Client) Click >> to open the Select the Computer screen. Click >> to open the Select Directory screen. Click >> to open the Select Directory screen.
Select restore level (VMware VADP)

Use this screen to select the type of VMware VADP restore you want to perform.
VM-level Restore Restore an entire Virtual Machine. This restore level is only possible if the entire Virtual Machine (including configuration files) was backed up. Restore individual virtual disks. This restore level can be performed for all backed up VMware VADP backup sets. It will not restore a functioning Virtual Machine, only individual virtual disks backed up from a VM. Disk-level restore attaches a backed up disk to the target Virtual Machine.
VM Disk-level Restore
Select restore location screen

Use this tab to select the restore options and/or restore destination. This process over-writes any existing files of the same name.
Original location Alternate location Share Name List Icon Source Destination This column displays different icons, depending on the item type. Shows the source share from where the backup set files originated. By default, the destination is the same as the source share. To change the destination share, double click on this cell and a drop down list allows you to select from all the available shares on the alternate location. Double click on this cell to select a location to restore to on the destination share. This brings up the Select Directory screen. You may also type the path directly into the cell. By default, backups are automatically restored to their original source location. This process over-writes existing files of the same name. You have the option to Restore to an Alternate Location in this screen.
Restore To


Confidential.
Share Path
This column appears if you need to select an alternate server. If the share path cannot be obtained due to user privilege restrictions, you must type a path in manually. Notes: Restoring to Windows: Share Path information appears automatically if you are restoring the Services Database, System State (Registry) or locked files. If the selected restore items contain a common path, you may shorten the common portion of the restore path by increasing the truncate level in the number field. Truncated portions of the restore path will disappear. Note: Alternate location security: If the entire path is truncated, the alternate location directory will inherit the security of the truncated parent directory.
Truncate
[Alternate location restores] Restore as Pure Files This option is available for some backup set types. It allows you to restore only the (Linux DS-Client) data files to the alternate location. This means no database loading or other special backup set type handling will be performed. Restore Option File This option only applies for VSS-aware backup sets, when restoring to an alternate location. This option allows you to specify an XML file that contains specific VSS rules to apply for alternate location restore of a VSS-aware backup set.
[VSS-aware backup sets] Rename Component This option is only available for alternate location restores. It allows you to rename (Windows DS-Client) individual components being restored. Opens the Rename Component screen. Restore database file only (DS-Client Buffer) (Windows DS-Client) [Backup from the Cloud (Salesforce.com) backup sets] Restores the backed up data as a single, pure database file to the DS-Client Buffer, then copies the file to the final destination you specify. Click [...] to open the Select Directory screen.
Virtual Machine List (VMware VADP backup sets only) These columns will be pre-populated with default restore suggestions, based on the selected restore server. Icon Datacenter Folder Path VM Name Host This column displays different icons, depending on the item type. Shows the source VMware Datacenter from where the backup set files originated. Alternate Location: Allows you to select a new Datacenter on the target The target restore location (folder) that will contain the target VM. The target VM where to restore. The ESX host where to restore. Opens / Hides the Files List for the highlighted Virtual Machine. This option only appears if you are restoring a full Virtual Machine (VM-level Restore). Virtual Disk: Shows the name of the individual Virtual Disk (*.vmdk). Datastore: Shows the name of the Datastore. For alternate location restores, this field provides a dropdown list of available Datastores on the destination host where you can restore the individual disk.
Show Datastores / Hide Datastores
Select restore location (System i Server)

Use this tab to select the restore destination. This process over-writes any existing objects of the same name.
Restore To Original Location: Alternate Location: [Default] Restores objects to the original location from which they were backed up. Click this radio button to specify an alternate destination for the restore items. Click >> to select an alternate server.
Confidential.

Dump to Library Mapping List Icon Source Library Destination Database
This field shows the location for the data dump. Click >> to change the specified path. This brings up the Select share & path for the data dump screen. Shows a list of the selected libraries for restore, and their restore destination(s). You can change the restore destination by modifying the appropriate column. Shows the source library's name. Shows the library where the backup will be restored. Double Click on this cell to open a drop down list of all the available libraries on the specified restore server.
Select restore media & options screen

You can request media containing either the last version of an entire backup set (Snapshot), or a selective restore of required files.
Media Snapshot Selective Choose from the restore media list (e.g. CD, DVD, Tape, HDD, USB Drive, etc.). This list is defined by your Service Provider (it comes from the DS-System). Creates a 'Snapshot' of the latest version of all files in the backup set. You will not need to select anything on the next tab. Allows you to pick-and-choose directories/files for restore to disc / tape. This is the same as for regular restores.
Select restore options screen

Use this tab to select the restore options and/or restore destination. This process over-writes any existing files of the same name. Options that do not apply to the selected backup set are either grayed out or do not appear.
Permissions (File System backup sets) Yes Restores permissions of the backed up files. Skips restoring file security information (if any) for the selected files and directories. Newly created files and directories will assume the security of the parent directory. Notes:If you have been assigned ownership of another person's backup set(s) and you want to restore files from those sets with ACL, the following will occur: 1 DS-User will check whether you have access rights to Take Ownership and Change Permissions of the restore file. 2 If you do not have access rights, you will not be able to restore the ACL. You must choose Skip Permissions Restore to restore the file. 3 If you have the access rights, but the file ownership is not yours, the file will be restored without ownership, and a corresponding error message will appear in the event log, describing the security error. Will restore permissions for the selected files and directories only. This will only apply permissions to existing files on the destination volume. Restores files to a temporary location first. If the file is restored successfully, then the original file is overwritten with the temporary file. This prevents partially restored files from overwriting an existing file. For Linux DS-Client restores of Hard Links, this is the default restore method. The restore will only link those hard linked files that are selected in the same restore session. For more information, see the Hard Links sections in the Knowledge Base article Backup / Restore of UNIX File Systems on page 539.
Confidential.
Skip
Only Method
Save (File System Backups)

Use buffer
Restores files to the DS-Client buffer first. Then, the files are transferred to the restore destination. This ensures that the files are restored as fast as possible, given the speed of your LAN. Notes:The DS-Client Buffer will inherit the permissions of its parent directory. For example, if you specify C:\TEMP as the buffer, then the C:\TEMP\buf directory will inherit the permissions of the \TEMP directory. All files copied to the \buf directory will be accessible by users with permissions to \TEMP. You must have sufficient disk space in the DS-Client buffer to accommodate the entire restore amount. Files are restored on a 'write-data-as-received' basis. Files are overwritten upon receipt of the first byte of data. For Linux DS-Client restores of Hard Links, choosing this method allows you to restore a single hard linked file while preserving the existing hard links on the restore target. For more information, see the Hard Links sections in the Knowledge Base article Backup / Restore of UNIX File Systems on page 539. A locked file will be renamed while still in use (intended for System files). The renamed file will be registered with the operating system for delete, on reboot. (This feature is necessary when restoring system files that are opened before the operating system has the chance to replace the locked file.) A locked file will be restored as a temporary file. This temporary file will be registered with the operating system to replace the locked file on reboot. For important information on this option refer to the DS-Client Knowledge Base article: Restoring Locked Files on Windows Skips restores of any files that are locked. An error will be reported in the Activity Log. Skips restores of any backed up stub files. Skips restore if the online file is a stub (a small placeholder/link file to the full file which was moved to other media). OFF (Drop database) - If a database selected for restore already exists on the restore server, DS-Client will drop the existing database before performing the restore. ON (Do not drop database) - If a database selected for restore already exists on the restore server, DS-Client will restore to that existing database. This option is useful if you want to keep any extra tables (and replace all existing tables) in the existing database.
Fast
Locked Files (Windows) Rename
Don't rename
Skip Skip offline files (stubs) (Windows)
Do not drop existing DB before restore (Linux DS-Client)
Overwrite junction point Replaces any junction points of the same name. Junction points are special (Windows 2000 & up) directories (like shortcuts) that link to another location. Load Cluster Quorum (Windows 2000 & up) Detailed Log Skip Pre/Post (This check box only appears if you are restoring a System State with a Cluster Quorum.) Automatically loads the Cluster Quorum after restore. For more information, refer to the DS-Client Knowledge Base Article: Backup / Restore of Windows 2000 Records all files that are restored. Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. This check box appears if you are restoring a Backup from the Cloud (Salesforce.com) backup sets database. Restore Schema is performed at Table-Level only (not at database level). This option is useful if you have made changes to a tables structure since the backup session you are restoring. If selected, the restore will wipe the entire table(s) selected for restore from the Salesforce.com database, then rebuild the table(s) with the backed up schema(s), then populate the table with the restore data.
Restore Schemas (Salesforce.com databases)


Confidential.
Authoritative Restore (System State)
This option forces authoritative restore for both Active Directory and NTFS. For more information, refer to the DS-Client Knowledge Base Article: Bare Metal Restore of Windows (ALL VERSIONS) This list only appears if the backup source and restore destination support file level compression (ex: NTFS, NetWare). Default Compression: Specifies that the restored files take on the compression attribute of the parent directory where they are restored. Preserve Compression: Specifies that the restored files retain their original compression setting (as when they were originally backed up). Force Compress: Specifies that the restored files are compressed using the destination file system's compression. Force Expand: Specifies that all restored files are to be expanded (no compression). (This check box only appears if the original volume does not support file level compression, but the restore destination does.) Compresses the restore files using the destination file system's compression. Specify the object (container or leaf) that you want to restore. The object name should be typeless and fully qualified from the Root (distinguished). (The default is to restore the whole NDS). Leave this field empty to restore all permissions backed up. Restores file and directory permissions for the specified path only. (e.g. \dir_path\(file_name) where file_name is optional). You must know the specific path name in order to use this option. Skips restore of subdirectory permissions from the directory listed in the Restore Permissions from field. This option is only applicable when restoring a Lotus Domino Server database in a clustered environment. Additional steps are required. Please refer to the Knowledge Base article Backup / Restore of Lotus Domino Server Databases on page 631.
Compression Options
Force Compress (Check Box) Restore NDS Object(s) from (NetWare NDS Restore) Restore Permissions from (Permissions Only Restore) Skip Subdirectories (Permissions Only Restore) Keep Replica ID (Lotus Domino Server Only)
Local Storage Restore Options This section only appears if this backup set has data stored in Local Storage and off-site on DS-System. DSClient always tries to restore from Local Storage first, but these options deal with the specific scenario where the DS-Client also needs to restore some data from DS-System. (Default) Stop, if connection to DS-System not available when needed. Continue, even if connection to DS-System not available. Try to connect to DS-System first. If connection fails, stop. Additional Restore Options (Linux - Permissions backup sets) Restore files that match Exclude files that match Allows you to specify a filename pattern whose permissions will be restored. Allows you to specify a filename pattern to exclude from the permissions restore.
Additional Restore Options (Linux - VMware VADP backup sets) The available restore options depend on the selected destination VMware server. For each Virtual Machine selected for restore, you can specify additional restore options to be performed. Power on VM after restore Unregister VM after restore Starts each virtual machine that is successfully restored. After successful restore, the virtual machine will be unregistered from the vCenter.
Appends the restore time to the end of the virtual machines name. For examAppend timestamp to VM ple: RestoreVM would be restored as RestoreVM_(yyyy-mm-dd-hh:mm:ss) name when you view it from the vCenter.


Confidential.
Select restore options screen (SQL / Microsoft Exchange / Oracle / System i)

Use this tab to select the restore options.
Restore Options Detailed Log Skip Pre/Post Pre/Post Records all files that are restored. Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. Opens the Pre & Post Execution screen (see Pre & Post Execution screen).
Leave Database(s) in RESTORING state (MS SQL Server backup sets only. Not valid for dump file only restores.) Off: (DEFAULT) The database will be brought online after the restore. On: DS-Client will not bring the database online after the restore has finished. Instead, it will leave the database in RESTORING mode to allow users to continue performing restore operations on the restored database. Do not drop existing DB before restore (MySQL backup sets only.) OFF (Drop database) - If a database selected for restore already exists on the restore server, DS-Client will drop the existing database before performing the restore. ON (Do not drop database) - If a database selected for restore already exists on the restore server, DSClient will restore to that existing database. This option is useful if you want to keep any extra tables (and replace all existing tables) in the existing database. Restore Private Authorities. (System i backup sets only.) Restores Private Authorities for objects (if they were backed up). This works for System i objects with the Private Authority (PVTAUT) parameter (This parameter was introduced since IBM i 6.1). When PVTAUT is set to *YES, you will be able to restore the private authorities attached to your saved objects. Restore Schemas (Salesforce.com databases) This check box appears if you are restoring a Backup from the Cloud (Salesforce.com) backup sets database. Restore Schema is performed at Table-Level only (not at database level). This option is useful if you have made changes to a tables structure since the backup session you are restoring. If selected, the restore will wipe the entire table(s) selected for restore from the Salesforce.com database, then rebuild the table(s) with the backed up schema(s), then populate the table with the restore data. Local Storage Restore Options This section only appears if this backup set has data stored in Local Storage and off-site on DS-System. DSClient always tries to restore from Local Storage first, but these options deal with the specific scenario where the DS-Client also needs to restore some data from DS-System. (Default) Stop, if connection to DS-System not available when needed. Continue, even if connection to DS-System not available. Try to connect to DS-System first. If connection fails, stop. Additional Restore Options (Linux)


Confidential.
Force pipe library path (Oracle)
If you are using DS-PIPE, this field appears. RMAN requires the Media Management Library libobk.so in order to backup / restore using a PIPE. The exact library name will be slightly different, depending on the platform. For more information, refer to the Oracle Server Requirements section of the Knowledge Base Article Backup / Restore of Oracle Database Servers. You can specify the exact path (including filename) to the corresponding libobk.so for the Oracle servers platform. These library files can be found in the DS-Client installation directory. If you do not specify a path, the default path will be used: $ORACLE_HOME/lib/libobk.so Make sure Oracle has full rights to read and execute in the library path. Note: DS-Client does not validate this path. It simply forwards it to RMAN. This option will not issue the RECOVER command. This means the DS-Client will only restore the control file, archive logs and tablespaces back to the Oracle server. This option will not open the database. You must use RMAN to perform the DBPITR manually. For more information, refer to the Knowledge Base Article Oracle Database Point-In-Time Recovery (DBPITR).
Do not execute RECOVER commands (Oracle)
This option will automatically recover database to the target time specified RECOVER DATABASE at: and open the database with the Resetlogs option. (Oracle) For more information, refer to the Knowledge Base Article Oracle Database Point-In-Time Recovery (DBPITR).
Select restore options screen (VSS-aware restores)

Use this tab to select the restore options when performing a VSS-aware restore.
Restore Options Detailed Log Skip Pre/Post Pre/Post Records all files that are restored. Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. Opens the Pre & Post Execution screen (see Pre & Post Execution screen).
Leave Database(s) in RESTORING state (MS SQL Server backup sets only. Not valid for dump file only restores.) Off: (DEFAULT) The database will be brought online after the restore. On: DS-Client will not bring the database online after the restore has finished. Instead, it will leave the database in RESTORING mode to allow users to continue performing restore operations on the restored database. Local Storage Restore Options This section only appears if this backup set has data stored in Local Storage and off-site on DS-System. DSClient always tries to restore from Local Storage first, but these options deal with the specific scenario where the DS-Client also needs to restore some data from DS-System. (Default) Stop, if connection to DS-System not available when needed. Continue, even if connection to DS-System not available. Try to connect to DS-System first. If connection fails, stop. Microsoft Exchange database restore options Mount database after restore Force allow overwrite database Check to automatically mount the database after restore. Check to automatically set the MS Exchange Servers allow restore to overwrite database parameter before restoring the database.


Confidential.
Existing file options
Delete (default): Delete all of the existing files in the restore directory. Keep: Keep all existing files in the restore directory. Rename: Renames the existing files, until all restore items are successfully restored. This takes more space, but avoids problems of failed restores (if a restore fails without this option, the MS Exchange Server will not function). In case of failure, original files will be renamed back and the Exchange database will be mounted.
Select restore options (SharePoint Item-Level)

Use this screen to choose the restore options for this SharePoint Item-Level restore request.
Restore Options Detailed Log Records all files that are restored (viewable from the Activity Log). OFF (default): Items that already exist on the SharePoint server are not overwritten. ON: If the selected restore item already exists on the target restore SharePoint server, it will be overwritten by the item being restored. (For ListField level restores, this does not apply and the restore will only succeed if the field does not currently exist on the target SharePoint server.)
Overwrite if exists
Remove database after restore is finished successfully Web Application URL Temporary Export Path You must supply the URL of the Web Application that you are restoring. This target URL must exist in the SharePoint Server Central Administration. You must supply a local path on the target SharePoint server where the restore will temporarily write files.
Select Restore Options (VSS-aware SharePoint)

Use this screen to choose the restore options for the SharePoint database.
Detailed Log Skip Pre/Post Pre/Post Send E-Mail notification when database restore finishes Records all files that are restored. Skips the Pre/Post restore process. Uncheck to display the Pre/Post button. Opens the Pre & Post Execution screen (see Pre & Post Execution screen). Select to have DS-Client send a notification when the database restore is finished. This is useful if the restore is large and will take a significant amount of time.
Select Restore Performance Options (Windows DS-Client)

This screen allows you to make some optional performance configurations. In general, you should use the defaults unless you have a high performance environment and the backup selected for restore is very large.
Maximum pending asynchronous I/O for a file This is the maximum I/O operations the DS-Client will queue for each file during the restore process. Use DS-Clients settings (Default) Uses the setting in the DS-Client Advanced Configurations > Category: Performance > Parameter: MaxPendingIOPerFile.


Confidential.
Use specific value
You can override the default and set a custom value that only applies for this backup set. This option is intended for high performance backup environments. You must be able to test the different settings to determine the optimal value. This is only useful if the target storage containing the backup data is fast and efficient enough to take advantage of the increased I/O. WARNING: Slower storage may suffer performance drops if this value is increased too much.
DS-System side read threads This setting affects the DS-System side of the process. It instructs the DS-System how many files to read simultaneously for this restore process. (Default) Uses the setting in the DS-Client Advanced Configurations > Category: Use DS-Clients settings Performance > Parameter: MaxRestoreReadThreads. Note: The actual value used maybe limited for some special backup sets. You can override the default and set a custom value that only applies for this backup set. You must be able to test the different settings to determine the optimal value. WARNING: Slower storage may suffer performance drops if this value is not properly set.
Use specific value
Select Restore Path screen

Use this screen to select the individual restore path(s) for MS SQL data and log files.
Source Database Destination Database Type Path Modify Shows the source database's name. Shows the database where the backup will be restored. Shows if it is the databases DATA or LOG file. Shows the path on the destination server where the corresponding item will be restored. Click to modify the highlighted restore path(s).
Select Retention Rule

Use this screen to select the retention rule to use.
Create a new retention rule Use an existing retention rule Select from the list by highlighting the rule to apply.
Select Schedule Detail screen

Use this screen to copy an existing detail from one of the existing Schedules. A tree of schedules is displayed, with branches representing each detail available.
Select Service
Use this screen to specify the Windows Service to backup.
Services List Select Browse through the list of available services and highlight your selection. Click to select the highlighted item in the Services List.


Confidential.
Select share & path for the database / data dump screen
Use this screen to specify dump location.
Database Dump This field displays the selection for the database dump location. Remote dump location (MS SQL Server): You can type a valid UNC path into this field, if you want to specify a different computer for the database dump. The MS SQL Server service account and the backup set user credentials must have administrator rights to access this UNC path (read-write permissions). Browse the database computer and select a directory. There must be enough space on the database computer to accommodate the dump file. Save the dump file to the local storage on the DS-Client computer. There must be enough space on the DS-Client computer to accommodate the dump file. This option does not consume any additional disk space. During backups, the DS-Client reads from the pipe on the source database. This method is useful if your database is too big to be dumped to a file on either the database server or the DS-Client buffer. [Microsoft SQL Server 2005 & up] This option is only available for backup of remote MS SQL Servers (not the local database). It allows you to specify the location on the remote computer where DS-Client will place and run the VDI tool. If no specification is made, DS-Client will run the tool from a default directory on the target computers c:\ drive. VDI allows users to select the DS-Client Pipe option for SQL Server 2005 versions (and higher). Use this screen to specify the location of the data dump. Highlight a folder in the System i Server ROOT file system and press "Next". The System i Server ROOT file system must be shared (with read-write permissions) for this operation to work.
Dump Path
Directory
DS-Client buffer
DS-Client Pipe
VDI Tool Directory
Data Dump (System i Server Backup Sets) System i Server
Select SharePoint List Item (SharePoint Item-Level)

After you have selected the List(s), Customer List(s) or Document Libraries for restore, you can use this screen to choose the specific list item you want to restore.
List Items This list contains all the items that can be restored from all the selected List(s), Customer List(s) or Document Libraries. Click on the list item(s) you want to restore (use CTRL + click for multiple items).
Select Synchronization Options screen

This screen allows you to check or synchronize between the DS-Client backup logs, and the DSSystem online storage.
Normal Select to compare and update where necessary, the DS-Client backup log (database) with the DS-System's Online storage information. Select to perform only a check of the synchronization between the DS-Client's backup log and the DS-System's Online storage. This will only identify whether inconsistencies exist (i.e. no corrective action will be taken.).
Check only


Confidential.
DS-System based
Select to update the entire DS-Client backup log with the DS-System's Online storage information. (Caution: A directory's "last seen" information is not recreated, since that information is not stored on the DS-System. The only difference this has is you cannot use the "...deleted from source..." filter option in either Delete or Restore operations for this backup set.) [Local Storage Tool Only] Select to compare and update where necessary, the DS-Client backup log (database) with the files in Local Storage. Click to start the Synchronization using the method selected. Since the DS-System does not store "last seen" information about directories, the DSSystem based option will update the DS-Client backup log without a directory's "last seen" information. The only difference this has is you cannot use the "...deleted from source..." filter option in either Delete or Restore operations.
Sync Local Storage Synchronize Note 1
Select the computer screen

This screen appears when you are required to select a network or computer. Use the tree to browse and make your selection.
Path DS-Client - Shows the network path of the item selected in the tree. System i - If this window is displayed for the first time, you must enter the IP address of the System i server into the Path field. SharePoint (Granular Restore): Enter the computer Name or IP address of the target MS SQL server (containing the restored SharePoint database) into this field. Prompts you to enter a valid user name and password for the selected computer. Note: For backup of Windows 2000 computers, you must connect to the Windows 2000 computer with an Administrator (or equivalent) account. Prompts you to enter valid connection information for the selected NAS. Opens the Enter NAS API Parameters (Windows DS-Client) screen. Prompts you to enter a valid user name and password for the database server. Oracle Note: Consult the User Guide (PDF) for more information on requirements to backup ORACLE database servers. Allows you to use the DS-Client services account credentials to connect to the local (DS-Client) computer. You must be logged in through DS-User using an Administrator account (or equivalent). This option is only available when you select My Computer (i.e. the local DS-Client computer).
Ask for Network Credentials Ask for NAS API credentials (NAS only) Ask for Database Credentials (Databases only)
Use DS-Client Account (Windows DS-Client only)
Select the computer screen (Linux DS-Client)

This screen appears when you are required to select a network or computer. Use the tree to browse and make your selection.
Shows the network path of the item selected in the tree. You can also type a path directly in this field in the same form as the following examples: Local File System\My Computer NAS\10.20.33.123 NFS\10.10.70.88
Path / IP Address


Confidential.
Ask for Credentials Ask for NAS API credentials (NAS only) sudo as an alternate user (UNIX-SSH only)
Prompts you to enter a valid user name and password for the selected source or database server. Prompts you to enter valid connection information for the selected NAS. Opens the Specify Credentials (Linux DS-Client) screen. Shows the credentials that Linux DS-Client will use to access data on the network resource. After successful login to the remote source, "sudo" (switch user) will be performed for Linux DS-Client to use these credentials. By default (if this is not selected), UNIX-SSH will run a PERL script on the target machine to perform backups. Click [...] to edit the settings. See Advanced Connection Options (Linux DS-Client) for more information. VMware backup sets have the following connection options: Ask for VMware logon credentials: Credentials to logon to the Virtual Center or ESX Server (whichever was specified in the Path/IP Address field). XenServer backup sets have the following connection option: Ask for XenServer API logon credentials: Prompts you to enter a valid user name and password for the selected XenServer.
Advanced connection options (UNIX-SSH only)
VMware
XenServer
Select the path for the database dump file (Linux DS-Client)
This screen appears when you are required to select a path for the database dump. Use the tree to browse and make your selection.
Select the protocol for dumping database file (Linux DS-Client)

In order to back up an active Oracle or DB2 database, a copy or "dump" of the database must be made. Use this screen to select the method to handle the database dump file.
Local File System The DS-Client will dump the database into the specified path on the local (for Oracle or DB2 servers on file system (on the DS-Client computer). The DS-Client transmits the files to the DS-Client computer). DS-System. NFS (for remote Oracle or DB2 Server) UNIX-SSH (for remote Oracle or DB2 Server) DS-Client will read the database dump files from the database server through the NFS transmission protocol, then sends them to DS-System. DS-Client will read the database dump files from the database server through the UNIX-SSH transmission protocol, then send them to DS-System. DS-PIPE is an alternative to the database dump for Oracle database server backups. This option does not consume any additional disk space. During backups, the DS-Client reads from the pipe on the source database. This method is useful if your database is too big to be dumped to a file on either the database server or the DS-Client buffer.
DS-PIPE (Oracle only)


Confidential.
Select the VSS-aware backup set type

This screen allows you to select the backup set type for VSS-aware backup sets. VSS only works with Windows DS-Clients, and the target Windows computer must have the Microsoft Volume Shadow Copy Service (VSS) components necessary to perform this type of backup.
Microsoft SQL Server Microsoft Exchange Server Microsoft Hyper-V Microsoft Cluster Hyper-V Microsoft SharePoint Server Performs online backup of a SQL server using the target computers Microsoft VSS components. Performs online backup of an Exchange server using the target computers Microsoft VSS components. Performs online backup of a Hyper-V (Virtual Machine) using the target computers Microsoft VSS components. Performs online backup of a Cluster Hyper-V using the target virtual nodes Microsoft VSS components. Refer to the Knowledge Base article Backup / Restore of Hyper-V (VSS-aware backup sets) on page 644 for specific instructions before proceeding. Performs online backup of a Microsoft SharePoint Server using the target computers Microsoft VSS components.
Select the VSS Restore Method

This screen appears when you select a VSS-aware backup set for restore. You must select the type of restore you want to perform.
VSS Restore File Restore Performs an online restore of the selected backup session to the original backup source using the target computers Microsoft VSS tools. Allows you to selectively restore individual files from a backup session. This option is only available for SharePoint 2010 VSS-aware backup sets. Step 1 Database Restore: Restores the backed up SharePoint 2010 database. Step 2 Items Restore: Restores individual items from a SharePoint 2010 database restored in step 1. Note: If you are restoring from a BLM Restorable Image or Disc/Tape media, you can only perform Step 1 - the database restore from that media. Step 2 must always be peformed from the database restored in Step 1.
Granular Restore (SharePoint 2010)
Selection screen
This screen displays the selection that you have made so far. This is useful if you have selected several items from different directories, and you want to review your selection.
Icon Column This column displays different icons, depending on the item type. File/Directory Name This column shows the corresponding file name or directory path.
Send Unprotected LAN Resource Discovery E-Mail

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to E-Mail the results of the last scan.
E-Mail Enter the E-Mail address of the recipient(s). Separate multiple addresses with a semi-colon (;) or a comma (,).


Confidential.
Format
Choose the E-Mail format: HTML Plain Text
Set Backup Set(s) Priority for Schedule ... screen

This screen allows you to set the priority for backup sets using this schedule. You may also limit the number of simultaneous backups that this schedule will perform.
Backup Set List # Name Backup set priority Shows a list of the backup sets using this schedule. Shows the priority of the corresponding backup set within this schedule. Shows the node\name (owner) of the backup set. Use this number field to increase or decrease a selected backup set's backup priority within the schedule. Higher priority items (i.e. lower numbers) will be run first. This counter allows you to limit the number of backup sets that will be run simultaneously by this schedule. (This is useful if some data must be backed up through a slower connection, and there is no benefit to running simultaneous backups. It also allows you to increase the concurrent backup sessions, if the DS-Client hardware has the required processing power.) Schedule ... backup Note: The DS-Client database has a parameter for Maximum Concurrent Activities sets at the time that affects the number of backups that can be scheduled at one time. This is set from Setup Menu > DS-Client Configuration: Advanced Tab For Windows DS-Clients, the parameter name is MaxSessions (in the Performance category). For Grid DS-Clients, the limit will be the sum of all the MaxSessions parameters from all running nodes. For UNIX DS-Clients, the parameter name is MaxSession Number
Set Budget Password screen

New Password Type your new password in the New Password field. Note: Windows Passwords are cAsE SensiTiVE
Verify new Password Type your new password again in the Verify new Password field.
Set Credentials screen

LAN STORAGE DISCOVERY TOOL / UNPROTECTED LAN RESOURCE DISCOVERY TOOL Use this screen to set the credentials used to scan LAN shares
Connect as Password From Type the User Name in this field. Type the corresponding password in this field. [If applicable] Select the machine where the DS-Client will verify your User Name and password. Normally this will be the same as the server that you are connecting to. However if the computer running DS-Client is a domain member, you may select from the available list of domains.
Priority (Share Dis- Enter the priority number - the lower the number, the higher the priority. The DS-Clicovery Wizard) ent will connect to the share(s) with the supplied credentials in this order.


Confidential.
Set Follow Option

LAN STORAGE DISCOVERY TOOL NTFS shares only.
Follow Don't Follow Reverse follow setting Will follow Reparse Points encountered in a scanned share. A Reparse Point is a link to a different location (directory or device). This will result in a larger amount scanned. Will not follow Reparse Points encountered in a scanned share. Inverts the highlighted share(s) setting.
Set Initial Backup Path

You must have at least one path configured to perform an Initial Backup.
Shows a list of all paths that you can assign for Initial Backup Set data. Icon: Shows the paths encryption configuration (plain icon = no encryption, green key icon = encrypted with DS-Client private key, red key icon = encrypted with user-defined key) Path: Location where the initial backup data will be written. Total Space: Size of the volume where the path is located. Available Space: Free space remaining on the volume where the path is located. Click to add a new path. Allows you to specify different credentials to the highlighted path. Opens the Specify Credentials (Windows DS-Client) screen.
Path List
Add Credentials (Windows DS-Client only)
Set Properties - Advanced Options tab (Windows DS-Client)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It applies to Windows File System and Microsoft Exchange Server backup sets.
Windows 2000 & up options (only if supported by the Windows Operating System version) Note: The defaults are OFF for all of these options. If you select any of these options, the backup data will increase. Backup data in Remote Storage Backup all data on remote media. Some Windows Operating Systems have the functionality to migrate infrequently accessed data from the local hard drive to directly attached tape libraries. The local disk usage is reduced by replacing the file with a link (shortcut). If disabled, only the link (shortcut file) will be backed up. Backup each instance of a file separately. Some Windows Operating Systems have an optional service 'Single Instance Store' to handle multiple copies of the same file on the computer. Local disk usage is reduced by placing one copy of the file in the Single Instance Store, with links (shortcuts) in all associated directories. If disabled, only the link will be backed up. If you have activated the Single Instance Store Service, check this option. Backup directories (all data) represented by the junction point. Junction points are file links to other directories. If disabled, DS-Client will backup only the link (shortcut) Notes: Junction points that are mounted FAT or FAT32 volumes are not supported.
Follow junction points
Volume Shadow Copy Windows computers only (if supported by the Operating System version)


Confidential.
Backup through volume shadow copies
DS-Client will initiate a VSS (Volume Shadow Copy Service) snapshot for the specified computer (for any local volumes included in the backup) and perform the backup from the VSS snapshot. If the VSS snapshot fails, DS-Client tries to backup like a regular File System backup set. For more information about VSS, refer to the corresponding Windows Help. By default, the DS-Client will make each writer commit its data before doing the VSS snapshot (e.g. Registry, SQL Server and other applications are VSS Aware and can freeze their own I/O while the snapshot is performed). If you check "Do not involve writers", it means that the DS-Client will not notify the VSS Aware applications that a backup is performed and the resulting backup will be only crash-consistent (i.e. it will contain whatever was on the hard disk during the backup). For more information about VSS, refer to the corresponding Windows Help. By default, VSS backups are performed with the process components option. Processing components means verifying if their files or their dependent component files are all included in the volumes selected for snapshot. By default, this option is off. If selected, the VSS snapshot will be performed without processing components. This option is useful if you have selected only a portion of a component for backup and do not want to encounter errors (because the VSS verification would otherwise detect missing files or dependencies).
Do not involve writers
Do not process components
Pure file data backup options This section only applies to Windows File System Backup Sets. The default is OFF. This option controls the automatic file filtering performed by the DS-Client during Windows file system backups. By default, the Windows DS-Client will exclude some files automatically out of the share-based backup of files, even if such files would be readable (e.g. when using VSS). The excluded files may include: temporary files (e.g. pagefile.sys) files that are being backed up as part of System State backups (e.g. Operating System DLLs, executable) Registry hive files Other files that may interfere with a successful Agentless BMR This option should usually remain unchecked, unless there are specific reasons why all such excluded data would need to be included in the share-based backup. Selecting this option will interfere with the ability to perform Agentless BMR without manual file filtering, however it may be used in conjunction with the VSS option in order to allow bootable-disk BMR (this requires 3rd-party BMR provisioning integration). It is recommended that unless BMR provisioning is supported by your installed DS-Client, you should leave this option unchecked. Backup strategy for backed up files This covers how DS-Client handles files that are already backed up. Force backup even if the If selected, DS-Client will force a re-backup of a file, even if its last modimodified time and size fied time and size have not changed since the last backup. did not change Exchange Cluster Options Microsoft Exchange Server only This option only applies to Microsoft Exchange 2007 Servers in CCR (Continuous Cluster Replication) configuration where there is a main node that handles transactions and a passive node that handles only replication.
Non-filtered share data backup


Confidential.
Backup Passive Node
If selected, this will backup the passive node. If not selected, this will backup the main node of the Exchange Server. NOTE: Do not change this setting once you have performed a backup of this set.
Set Properties - Backup from the Cloud (Salesforce.com) Parameters

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view or change information about the selected backup set.
Parameters [Local Storage Path must be configured (from the DS-Client Configuration Parameters Tab screen).] OFF: The database will be dumped to the DS-Client Buffer and removed after the backup process finishes. ON: The database will be dumped to the Local Storage Path and kept. Subsequent backups can use the previous DB dump for differential comparison, which may speed up the backup. This parameter specifies how long DS-Client will wait for a response from the Cloud Server before timing out (and failing the corresponding activity). Range 1-1000, default is 100 (seconds) The maximum size DS-Client will buffer for each query requested from / to the Cloud Server. If the buffer reaches this limit (before the Query Batch Size or Destination Batch Size is reached), the data will be immediately transferred to clear the buffer. Range 1-128, default is 20 (MB)
Keep DB dump for differential backup
Timeout
Buffer Size
Each time DS-Client needs to read from the Cloud Server, it queries the database to Query Batch Size return batches of this number of rows at a time (until the query is finished). Range 1-1000, default is 200 (rows) Destination Batch Size Each time DS-Client needs to write to the Cloud Server, it updates the database in batches of this number of rows at a time (until all data is written). Range 1-1000, default is 100 (rows)
Set Properties - Connection tab

Exchange Server Backup Sets Enter Connect As information in this field. Connect as (to Click >> to open the Modify Network Credentials screen. Database Server) See Specify Credentials (Windows DS-Client) for more information. This field shows the method and location for the database dump. DS-Client Buffer: dump to the DS-Client computer's disk storage. DS-Client Pipe: opens a named pipe to send the backup directly through the DS-Client to the DS-System without a database dump. Click >> to open the Select share & path for the database / data dump screen
Dump to
System i Server Backup Sets Enter Connect As information in this field. Connect as (to Click >> to open the Modify Network Credentials screen. System i server) See Specify Credentials (Windows DS-Client) for more information. Dump to This field shows the location of the data dump. Click >> to open the Select share & path for the database / data dump screen


Confidential.
Set Properties - Connection Options tab (Linux DS-Client)

Connection Options Ask for credentials Prompts you to enter a valid user name and password for the selected source or database server. Click [...] to edit the credentials. See Specify Credentials (Linux DS-Client) for more information. Shows the credentials that Linux DS-Client will use to access data on the network resource. After successful login to the remote source, "sudo" (switch user) will be performed for Linux DS-Client to use these credentials. The default (if no selection is made) is for DS-Client to run a PERL script. Click [...] to edit the settings. See Advanced Connection Options (Linux DS-Client) for more information. Prompts you to enter a valid user name and password for the Virtual Center. Click [...] to edit the credentials. See Specify Credentials (Linux DS-Client) for more information.
sudo as an alternate user (UNIX-SSH only) Advanced Connection Option (UNIX-SSH only) Ask for VMware logon credentials (VMware only)
Prompts you to enter a valid user name and password for SSH connection to the ESX Connect: Ask for VMware ESX Server. credentials Click [...] to edit the credentials. See Specify Credentials (Linux DS-Client) for (VMware only) more information. Shows the credentials that Linux DS-Client will use to access data on the VMware ESX Connect: sudo ESX Servers resources. as an alternate user After successful login to the remote source, "sudo" (switch user) will be per(VMware only) formed for Linux DS-Client to use these credentials. Ask for XenServer Prompts you to enter a valid user name and password for the selected XenServer. API logon credentials Click [...] to edit the credentials. See Specify Credentials (Linux DS-Client) for (XenServer only) more information. Dump Options (Oracle / DB2 / Sybase) Dump to Media management library name (Oracle Only) Archive log path (DB2 only) Shows the location where the database will be dumped. Oracle: Cannot be changed (protocol is set when backup set is created). DB2: Click [...] to edit the dump location. Sybase: Click [...] to edit the dump location. This is the full path on the Oracle Server where the file libobk has been copied. You must specify this path for Oracle running on the AIX platform. This field only appears if the backup set was created with the DB2 Online Backup option selected (Set Properties - Options tab). This is the path where the DB2 Archive Log files are written by the User Exit program. Click [...] to specify the path. This opens the Select Directory screen. This field only appears if the backup set was created with the DB2 Online Backup option selected (Set Properties - Options tab). This path will appear by default in the ArchiveLog Path field of the Restore Wizard for this backup set. This is the path where the DB2 Archive Log files will be retrieved by the User Exit program. Click [...] to specify the path. This opens the Select Directory screen.
Restore log path (DB2 only)
Prompts you to enter a valid user name and password for the dump location. Ask for network cre Click [...] to edit the credentials. See Specify Credentials (Linux DS-Client) for dentials more information.


Confidential.
sudo as an alternate user (DB2 only using UNIX-SSH protocol) Advanced Connection Option (DB2 only using UNIX-SSH protocol)
Shows the credentials that Linux DS-Client will use to access data on the network resource. After successful login to the remote source, "sudo" (switch user) will be performed for Linux DS-Client to use these credentials. The default (if no selection is made) is for DS-Client to run a PERL script. Click [...] to edit the settings. See Advanced Connection Options (Linux DS-Client) for more information.
Set Properties - Connections tab (E-Mail backup sets)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view or change connection information about the selected E-Mail Message Backup Set (MS Exchange, MS Outlook, GroupWise, Lotus).
Connection info Connect as (to DS-MLR computer) Enter Connect As information in this field. Click >> to open the Modify Network Credentials screen. See Specify Credentials (Windows DS-Client) for more information. Enter Connect As information in this field (to the GroupWise database). Click >> to open the Modify Database Credentials screen.
Database info (GroupWise only) Connect as (to database)
Set Properties - Database tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view information about the selected database backup set.
Database Info Character Set Sort Order Connect as (to Database) Shows the character set used by the Database. Shows the sort order used by the Database. Enter Connect As information in this field. Click >> to open the Modify Network Credentials screen. See Specify Credentials (Windows DS-Client) for more information.
Uses the share credentials for access to the database. When checked, this disables Access Inteselection of the Connect as (to Database). grated with Share Note: This option will not work if your network is using Windows Integrated Security. Dump Info This field shows the method and location for the database dump. Path: dump to the local database computer's disk storage. DS-Client Buffer: dump to the DS-Client computer's disk storage. DS-Client Pipe: opens a named pipe to send the backup directly through the DS-Client to the DS-System without a database dump. Click >> to open the Select share & path for the database / data dump screen Displays the user access credentials to the shared resource. Click >> to open the Modify Network Credentials screen.
Dump to
Connect as (to share)


Confidential.
Set Properties - Items tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the option settings for backup set items. These settings are applied each time the set is backed up.
Item & options for backup Items Max Gen Shows a list with the item(s) specified for backup. Click in this field to change the maximum generations settings of the highlighted backup item (that will be stored online). Letters that appear in this column correspond to the following options: P = Backup permissions S = Backup streams E = Extended Attributes D = Run DBCC before backup S = Stop on DBCC errors T = Truncate Transaction Log / Truncate Archived Logs / Backup Transaction Log B = Backup Only Current Archived Logs L = Logical Corruption Check To add or remove a backup item option, highlight the items row in the list and check or uncheck the option that appears beneath this list. See below for details about individual options. Backs up the file permissions. (ex: ACL on NTFS volumes, or Trustees on NetWare volumes.) NTFS volumes support multiple streams of data associated with a particular file. Select this option if you have files that contain alternate data streams. These are the Extended File Attributes (ex: Transactional and Compressed) The Database Consistency Check (DBCC) verifies database integrity to ensure backup of a valid database dump. Truncates the transaction log. MS SQL Server 2000 & MSDE: Transaction Logs are truncated before the database dump. MS Exchange Server: Transaction Logs are truncated after the backup. The database must be configured with FULL or BULK_LOGGED recovery mode, otherwise this option will have no effect. If selected, the DS-Client will dump the Transaction Log and send it to the DS-System in addition to the database(s). Backup Transaction Log (Microsoft SQL 2005 and higher) If selected, the Transaction Logs will also be truncated. The timing of the truncation depends on the Database Backup Policy (see: Set Properties - Options tab). Full - Transaction Logs are truncated before the database dump. Differential - Transaction Logs are truncated before the database dump. Incremental - Transaction Logs are first backed up, and then truncated. If DBCC errors are detected, this option will skip backing up the dump file(s).
Options
Backup permissions (Windows, NetWare) Backup streams (Windows) Backup EAttributes (NetWare) Run DBCC before backup (Microsoft SQL) Truncate transaction log (Microsoft SQL 2000 & MSDE, MS Exchange Server)
Stop on DBCC errors (Microsoft SQL)
If selected, this instructs DS-Client to backup the active databases Backup active database from the selected Microsoft Exchange item. (VSS-aware backup set; Microsoft This option is provided to allow you to make different selections if Exchange 2010) your backup set has multiple backup items.

Confidential.
If selected, this instructs DS-Client to backup the passive databases Backup passive database from the selected Microsoft Exchange item. (VSS-aware backup set; Microsoft This option is provided to allow you to make different selections if Exchange 2010) your backup set has multiple backup items. Logical Corruption Check (Oracle Server) Backup Only Current Archived Logs (Oracle Server) Truncate archived logs (Oracle Server) Filter (E-Mail level backup sets: MS Exchange, MS Outlook, Lotus Notes / Domino, GroupWise) Edit Verifies the database for corruptions. Check to backup only those logs that are necessary for the Oracle database. This saves backup space, by avoiding backup of any older logs. Leave this box unchecked if you want to backup all log files. Clear the Oracle Database logs associated with this item after backup. Click to add a filter to the E-Mail backup item. Opens the Select Filter screen. Click to add more backup items. Opens the Select items for backup set screen.
Set Properties - Items tab (Linux DS-Client)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the option settings for backup set items. These settings are applied each time the set is backed up.
Item & options for backup Items Max Gen Shows a list with the item(s) specified for backup. Click in this field to change the maximum generations settings of the highlighted backup item (that will be stored online). Letters that appear in this column correspond to the following options: P = Permissions (ACL) R = Resource Fork A = Backup File Attributes X = Backup POSIX ACL V = Verify during dump T = Truncate transaction log S = Backup SElinux To add or remove a backup item option, highlight the items row in the list and check or uncheck the option that appears beneath this list. See below for details about individual options. Backs up the Access Control List (file permissions) This only applies to backups of the Local File System. Check this box to backup the Extended ACL (if configured). These are the permissions set using the setfacl command (and viewed using the getfacl command).
Options
Backup ACL Backup POSIX ACL (Linux DS-Client)


Confidential.
Backup SElinux (Linux DS-Client)
Backs up the Security Enhanced Linux attribute of files or folders. Local File System and SSH backup sets only. For SSH backup sets with Perl (default), the target Linux machine must have the Linux-UserXAttr package installed in order for this option to appear. For SSH backup sets with Python, the target Linux machine must have the pyxattr package installed in order for this option to appear. Note: How to install xattr with python: Download python xattr from their website (http://pypi.python.org/pypi/ xattr). After extracting the downloaded package, open a terminal and run the command: python setup.py install After the installation finishes, you can use SSH to backup the selinux attribute with python. Backs up the Resource Fork of a file on the Mac platform. Backs up the File Attributes for files on the Mac platform. DS-Client will add the with verify option to the Sybase database dump command it sends when performing the backup. Truncates the database transaction logs before performing the backup. Opens the Directories or Database Tree, allowing you to add or remove backup items.
Backup Resource (Macintosh DS-Client) Backup File Attributes (Macintosh DS-Client) Verify during dump (Sybase) Truncate transaction log (Sybase) Edit (Properties Dialog only)
Set Properties - Notification tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the notification settings for individual backup sets. These settings are applied each time the set is backed up.
Notification List This list shows all of the specified recipients of notification messages for the backup set. Icon Completion Detailed Recipient Add Modify Delete This column displays different icons, depending on the notification type. A notification will be sent if the backup meets the specified completion status. Indicates that this backup notification contains a detailed log (i.e. File IDs). Indicates the recipient of the corresponding notification message. Opens the Add Notification screen. This allows you to add more notification recipients. Allows you to change the highlighted notification setting. Allows you to delete the highlighted notification setting.
Send SNMP traps when Check all that apply. Traps are sent according to the configurations in Setup > Configuration > SNMP Successful Completed with errors Incomplete Monitors this set for successful backups (completed without errors or warnings). Monitors this set for backups that are completed with errors. Monitors this set for backup failures (where the backup was stopped, interrupted or could not otherwise finish normally). Completed with warnings Monitors this set for backups that are completed with warnings.


Confidential.
Set Properties - Options tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the option settings for individual backup sets. These settings are applied each time the set is backed up.
Additional Backup Set Options Backup set options If checked, files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Note: This option cannot be used if Continuous Data Protection (CDP) is selected. Records all files that are backed up (you may view them in the Activity Log). Specifies that a backup stops if this number of errors are encountered. range 0-9999, 0 = no limit Note: The global default that appears in the New Backup Set Wizard can be configured using the Windows DS-Client MaxErrors Advanced Parameter. The options in this section are specific to the type of backup set: MySQL backup sets. System i backup sets. Local DS-VDR (VMware VADP) backup sets. Physical to Virtual backup sets.
Use buffer
Detailed log
Stop on errors
Check to access the Continuous Data Protection Settings screen. From there, you can instruct DS-Client how to monitor this backup sets source to immeContinuous Data Protection diately detect and back up changes. Note: This option cannot be used if the Use buffer option is selected. Initial Backup If checked, the backup set is flagged for Initial Backup. Click the [>>] button to select the Initial Backup Path. This box appears if the feature is activated by your Service Provider. If checked, the backup sets files will be excluded from Common File storage reduction. This means duplicate files will be encrypted and backed up individually, thereby potentially increasing the stored size. You can only set this feature in the New Backup Set Wizard. It cannot be changed afterwards. Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver.
Disable Common Files
BLM (Infinite Generations) (Backup Lifecycle Management module must be enabled)
Use Local Storage These options appear if you have the Local Storage Tool Enabled from your Service Provider, and you have specified a Local Storage Path in the DS-Client Configuration Parameters Tab screen. Save Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). Backup data will be sent to the location specified in the Local Storage Path field. Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). Backup data will be sent to the location specified in the Local Storage Path field.
Cache


Confidential.
Replicate (Lotus Domino backups only) This option is not supported if the DS-Clients Local Storage Path is configured using a UNC path.
Check this box to use the Lotus Domino replicate function when performing the database dump. This option can speed up the database dump. If selected, the Lotus Domino database dump file must be kept in the DSClient Local Storage location. (Make sure there is enough space to store it.) On each subsequent backup, the Lotus Domino database will only be required to dump the changes since the previous dump file. This can significantly improve the dump speed. After a successful dump, the backup will proceed normally (with master / delta processing, compression and encryption). Click [>>] to choose a specific local storage path for this backup set. Opens the Enter Local Storage Path. If you do not make a selection, the path from the DS-Client Configuration Parameters Tab screen is used. If checked, the backup set is flagged to scan all files in the backup set prior to backup, in order to display an estimated completion time for the backup. You can select the compression type: LZOP: A faster compression than ZLIB, that comes at the expense of less compression. ZLIB: This compression method will normally produce better compression than LZOP, but will take more time to compress. Four different ZLIB strengths are available (Global, High, Medium, and Low). ZLIB Global is the default value set in the DS-Client Advanced Configurations DefaultCompression parameter; ZLIB High corresponds to a value of 9; ZLIB Medium = 6; and ZLIB Low = 3. None: Disables compression for this backup set. (This will only apply to backups performed after this section is made. Any backups currently online will retain the compression type used at the time of backup.)
Local Storage Path
PreScan
Compression Type
Open Files (File System Backup sets) This information instructs the DS-Client about how to deal with Open (i.e. locked) files. (If the open file has been locked with Deny write by another process, the backup for this file will fail.) Try Deny Write Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), place the backup file in 'Allow Write' mode. This mode prevents any other process from writing to the backup file, while the DS-Client has it open. DS-Client will not back up the file, if another process has already opened it for write. (However, you may instruct the DS-Client to retry backing up the open file.) Attempt to open backup file in 'Deny Write' mode. If this fails (because the file is already open), then open in Allow Write mode and lock the file, thereby preventing any process from writing to the file. This ensures that the most recent version of the file is backed up. Allow another process to read/write to the backup file (no restrictions). Since other applications can write to the file while it is being backed up, this may affect file consistency. Specifies the number of times you want the DS-Client to attempt to backup the file. (Max. 10 retries). Specifies the interval between retries. (Maximum of 999 seconds). Click Pre/Post to access the Pre & Post Execution screen. For more information, see: Pre & Post Execution screen. Click to access the Exclude Old Files screen. For more information, see: Exclude Old Files screen. Note: This option is not available if the Windows System State or Services Database is selected for backup.
Deny Write
Prevent Write
Allow Write Retry times Retry intervals Pre/Post Exclude old files (File System Backup sets)


Confidential.
Additional Backup Set MySQL backup sets. Options Add locks around insert Lock tables before inserting data on restore. statements (See the MySQL manual page for mysqldump for more information.) Add MySQL specific table create options Add MySQL specific extensions to the backed up database dump. (See the MySQL manual page for mysqldump for more information.) Specify how table rows are inserted into the database dump (i.e. the style of the INSERT statement). (See the MySQL manual page for mysqldump for more information.) Extended - Fast insert. May not be useful for manual loading into non-MySQL databases. Delayed - Uses INSERT DELAYED when inserting rows. Normal - Standard insert. Slower, but may be more portable to other databases. Complete - Uses complete INSERT statements that include column names when inserting rows. Specify how tables are dumped. (See the MySQL manual page for mysqldump for more information.) Lock all tables - Prevent changes to data while backup is in progress (sets the tables to read-only mode for duration of backup). [This option is like using the --lock-tables dump option.] Single transaction - [only works with transactional tables] This dump approach also prevents changes to the backup data, but does not set tables to read-only mode. None - Dump will be performed using the mysqldump function with no special conditions. [This option is like using the --skip-lock-tables dump option.]
Table dumping option
Additional Backup Set System i backup sets. Options Backup Private Authorities. Saves any private authorities for objects with the Private Authority (PVTAUT) parameter (This parameter was introduced since IBM i 6.1). When PVTAUT is set to *YES on the System i server, DS-Client is able to save the private authorities attached to any saved objects. This feature allows backup / restore of Public Authorities, Owner and object authorities, Primary group and primary group authorities, and the names of authorizations lists linked to the saved object. NOTE: IBM cautions against using this option for individual objects only because PVTAUT increases the amount of time needed to save an object. It is not recommended that you select this option for large scale backup and recovery of user data.


Confidential.
(TGTRLS): Specifies the release of the operating system on which you intend to restore and use the object. *CURRENT: The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed. *PRV: The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed. Previous Target Release NOTES: For system Libraries, Q* Libraries and/or *IBM Libraries, only the current release can be the target release. Not all objects can be targeted to another release. To find out which objects are supported check your IBM System i documentation. If DS-Client cannot backup the object to a previous release, it will retry the command without the TGTRLS parameter; this operation will be show on the log with the message "System i returned previous release target error; trying to rerun the same command without TGTRLS(*PRV) flag." This parameter can only be specified when the backup set is created.
Additional Backup Set Local DS-VDR (VMware VADP) backup sets. Options Backup Virtual Machine Memory Backup Virtual Machines snapshots Export to host ON: Saves the VM state (running programs loaded in memory). OFF: Backs up the VM as if it were not running. ON: Backup will export the actual running VM and all its snapshots. OFF: Backup will export the actual running VM only (no snapshots).
This dropdown list contains the available ESX hosts where you can export the selected Virtual Machines. You must assign one as the target. Click [>>] to open the Specify Credentials screen. This is dropdown list of available Datastores on the destination host where you can export the individual VM disk. You must assign one as the target.
Export to datastore
Pause the applications, in order to guarantee a consistent and usable backup. Attempt to quiesce I/O This option requires that the VMware tools are properly installed and configbefore taking snapshot ured on the Guest Operating System of the Virtual Machine. Attempt to use Change vCenter version 4.0 (or higher) with Virtual Machine version 7 (or above). Block Tracking for Attempts to reconfigure the Virtual Machine to use Changed Block Tracking backing up Virtual (CBT). This monitors if the disk was changed between backup sessions, which Machines improves backup performance if the disk was not changed. For Windows DS-Clients, this is selected by default (it cannot be turned off). If selected, the normal backup (to DS-System) options are disabled. This option is only available when creating the backup set. It cannot be changed once it is set. This type of backup set will export the selected backup items (Virtual Machines) on the corresponding vCenter.
Use Local DS-VDR
Additional Backup Set Physical to Virtual backup sets. Options Enter vCenter IP Enter the IP address of the vCenter where you want to virtualize the selected physical computer. You must supply the credentials to the vCenter for a user with sufficient permissions to create a Virtual Machine. Click [>>] to open the Specify Credentials screen. Once DS-Client / Local DS-VDR Tool connects to the vCenter, this dropdown list displays the available datacenters. You can select a different one (if more than one are available).
Export to datacenter


Confidential.
Export to host
Once you select the datacenter, you will be able to select a specific hosts IP address where the virtualized machine will be created. You must supply the credentials to this host. Click [>>] to open the Specify Credentials screen. After selecting the destination host, you must select one of the defined vCenter datastores to which the new VM will belong. This option is selected by default when creating the backup set. It cannot be changed.
Export to datastore Use Local DS-VDR
Set Properties - Options tab (Linux DS-Client)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the option settings for individual backup sets. These settings are applied each time the set is backed up.
Backup set options If checked, files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Note: This option cannot be used if Continuous Data Protection (CDP) is selected. Records all files that are backed up (you may view them in the Activity Log). Specifies that a backup stops if this number of errors are encountered. The default is 0 (no limit). range 0-9999 If checked, the backup set is flagged for Initial Backup. Click the [>>] button to select the Initial Backup Path. Check to access the Continuous Data Protection Settings screen. From there, you can instruct DS-Client how to monitor this backup sets source to immediately detect and back up changes. Note: This option cannot be used if the Use buffer option is selected. This box appears if the feature is activated by your Service Provider. If checked, the backup sets files will be excluded from Common File storage reduction. This means duplicate files will be encrypted and backed up individually, thereby potentially increasing the stored size. You can only set this feature in the New Backup Set Wizard. It cannot be changed afterwards.
Use buffer
Detailed log Stop on errors Initial Backup
Continuous Data Protection
Disable Common Files
Use Local Storage These options appear if you have the Local Storage Tool Enabled from your Service Provider, and you have specified a Local Storage Path in the DS-Client Configuration Parameters Tab screen. Save Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). Backup data will be sent to the location specified in the Local Storage Path field. Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). Backup data will be sent to the location specified in the Local Storage Path field.
Cache


Confidential.
Local Storage Path
Click [>>] to choose a specific local storage path for this backup set. Opens the Enter Local Storage Path. If you do not make a selection, the path from the DS-Client Configuration Parameters Tab screen is used. If checked, the backup set is flagged to scan all files in the backup set prior to backup, in order to display an estimated completion time for the backup. Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver. You can select the compression type: LZOP: A faster compression than ZLIB, that comes at the expense of less compression. ZLIB: This compression method will normally produce better compression than LZOP, but will take more time to compress. Four different ZLIB strengths are available (Global, High, Medium, and Low). ZLIB Global is the default value set in the DS-Client Advanced Configurations Compression Type parameter; ZLIB High corresponds to a value of 9; ZLIB Medium = 6; and ZLIB Low = 3. None: Disables compression for this backup set. (This will only apply to backups performed after this section is made. Any backups currently online will retain the compression type used at the time of backup.)
PreScan
Compression Type
Additional Backup Set Options The options that appear in this section are specific to the type of backup set: NAS, UNIX-SSH, NFS, Local File System backup sets. System i backup sets. MySQL backup sets. PgSQL backup sets. Oracle backup sets. DB2 Server backup sets. VMware backup sets. XenServer backup sets. Sybase backup sets. VMware VADP backup sets. Physical to Virtual backup sets. Pre/Post Exclude old files Click Pre/Post to access the Pre & Post Execution screen. For more information, see: Pre & Post Execution screen. Click to access the Exclude Old Files screen. For more information, see: Exclude Old Files screen.
Additional Backup Set Options NAS, UNIX-SSH, NFS, Local File System backup sets. Do not follow the Mount Point (UNIX-SSH only) Check to backup only the Mount Point itself (not the data under any Mount Point).
Force backup even if the modi- If selected, DS-Client will force a re-backup of a file, even if its last fied time or size did not change modified time and size have not changed since the last backup. NAS backup sets automatically try to backup using a snapshot of the NAS volume, using the NAS devices native snapshot feature. This option determines the DS-Clients behavior if the NAS snapshot fails (for any reason). ON: (Default) DS-Client will continue the backup by trying to backup the selected volumes data directly from the NAS storage. OFF: DS-Client will stop the backup and report errors.
Confidential.
Continue backup on snapshot failure (NAS only)

Use Snapdiff API (NAS only)
NetApp has a Snapdiff API feature that can compare the current snapshot with the previous snapshot of a NAS volume in order to generate the list of new and changed files. If enabled, this can generate significant backup process speed improvements on large volumes with many files. If selected, DS-Client will attempt to use the Snapdiff API. A previous snapshot must also exist for comparison. If Snapdiff fails for any reason, DS-Client will proceed to scan the full NAS volume. Hard Links are created in Unix-based file systems with the ln function. By default, this option is selected for any new backup sets. This means the backup will handle backup of the file and hard link information in order for the hard links to be restored. If this option is not selected, this means any backed up hard link will be restored as a separate (individual) file. Even with this option selected, you must create a backup set that includes all the hard linked files. Otherwise a warning will appear in the Event Log for the backup activity and if you restore from that backup, your existing hard links will be broken. The same applies if you perform a partial restore of hard linked files. Saves any private authorities for objects with the Private Authority (PVTAUT) parameter (This parameter was introduced since IBM i 6.1). When PVTAUT is set to *YES on the System i server, DS-Client is able to save the private authorities attached to any saved objects. This feature allows backup / restore of Public Authorities, Owner and object authorities, Primary group and primary group authorities, and the names of authorizations lists linked to the saved object. NOTE: IBM cautions against using this option for individual objects only because PVTAUT increases the amount of time needed to save an object. It is not recommended that you select this option for large scale backup and recovery of user data. (TGTRLS): Specifies the release of the operating system on which you intend to restore and use the object. *CURRENT: The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed. *PRV: The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed. NOTES: For system Libraries, Q* Libraries and/or *IBM Libraries, only the current release can be the target release. Not all objects can be targeted to another release. To find out which objects are supported check your IBM System i documentation. If DS-Client cannot backup the object to a previous release, it will retry the command without the TGTRLS parameter; this operation will be show on the log with the message "System i returned previous release target error; trying to rerun the same command without TGTRLS(*PRV) flag." This parameter can only be specified when the backup set is created. Lock tables before inserting data on restore. (See the MySQL manual page for mysqldump for more information.)
Backup Hard Links
Additional Backup Set Options System i backup sets.
Backup Private Authorities.
Previous Target Release
Additional Backup Set Options MySQL backup sets. Add locks around insert statements


Confidential.
Add MySQL specific table create Add MySQL specific extensions to the backed up database dump. options (See the MySQL manual page for mysqldump for more information.) Specify how table rows are inserted into the database dump (i.e. the style of the INSERT statement). (See the MySQL manual page for mysqldump for more information.) Extended - Fast insert. May not be useful for manual loading into non-MySQL databases. Delayed - Uses INSERT DELAYED when inserting rows. Normal - Standard insert. Slower, but may be more portable to other databases. Complete - Uses complete INSERT statements that include column names when inserting rows. Specify how tables are dumped. (See the MySQL manual page for mysqldump for more information.) Lock all tables - Prevent changes to data while backup is in progress (sets the tables to read-only mode for duration of backup). [This option is like using the --lock-tables dump option.] Single transaction - [only works with transactional tables] This dump approach also prevents changes to the backup data, but does not set tables to read-only mode. None - Dump will be performed using the mysqldump function with no special conditions. [This option is like using the --skip-lock-tables dump option.]
Table dumping option
Additional Backup Set Options PgSQL backup sets. Backup only the schema, not the data Dump only the schema (data definitions).
Do not backup privileges (Grant Will backup only the data, not including the privileges of the database. / Revoke) Backup data as INSERT, rather than COPY Vacuum database before Backup Dumps data as INSERT commands (instead of COPY). This will make restores very slow, but it will make those backups more portable to other SQL database packages. Optimizes the PostgreSQL database before performing the backup (analyzes the database and performs garbage collection). Check to backup ownership of any objects within the database (e.g. tables). Note: By default, this option is off. However, the ownership of the entire database is always backed up by DS-Client (independent of this option). (Default is on) Will perform a corruption check on the database prior to backup. Check to backup only those logs that are necessary for the Oracle database. This saves backup space, by avoiding backup of any older logs. Leave this box unchecked if you want to backup all log files Clear the Oracle Database logs associated with this item after backup.
Backup ownership of database objects
Additional Backup Set Options Oracle backup sets. Logical Corruption Check Backup only current archived logs Truncate archived logs


Confidential.
Use RMAN Compression (Oracle 10g and above)
DS-Client will backup the Oracle database using the RMAN compression option backup as compressed backupset. This requires more CPU during backup, but results in a smaller output file (i.e. it can reduce the size and time of the DB dump). Using this compression will limit the Master / Deltas block-level incremental reduction, since the DS-Client will not find any repeated blocks in subsequent Delta generations. None: No RMAN compression. Archive Logs: RMAN compression applied only to Archive Logs. Archive Logs and Tablespaces: RMAN compression applied to both Archive Logs and Tablespaces. If you are using DS-PIPE, this field appears. RMAN requires the Media Management Library libobk.so in order to backup / restore using a PIPE. The exact library name will be slightly different, depending on the platform. For more information, refer to the Oracle Server Requirements section of the Knowledge Base Article Backup / Restore of Oracle Database Servers. You can specify the exact path (including filename) to the corresponding libobk.so for the Oracle servers platform. These library files can be found in the DS-Client installation directory. If you do not specify a path, the default path will be used: $ORACLE_HOME/lib/libobk.so Make sure Oracle has full rights to read and execute in the library path. Note: DS-Client does not validate this path. It simply forwards it to RMAN. (Multi-channel backups are only used for Dump. It does not apply when backing up through DS-PIPE.) The maximum number of channels DS-Client will allocate when backing up the database. DS-Client can support up to 32 channels. The actual number that will be used depends on the datafile count for a tablespace. Delete entries from the history file or log files from the active log path. If unchecked, perform Offline DB2 backup. During an offline backup, applications cannot connect to the database. If checked, perform Online DB2 backup. An online backup allows applications to connect to the database and read and write to tables during database backup. Log retain or userexit must be enabled for an online backup. Pause the applications, in order to guarantee a consistent and usable backup. This option requires that the VMware tools are properly installed and configured on the Guest Operating System of the Virtual Machine.
Force pipe library path
Max. backup channels
Additional Backup Set Options DB2 Server backup sets. Prune History / Logfile
Online Backup
Additional Backup Set Options VMware backup sets. Attempt to quiesce I/O before taking snapshot
Include Virtual Machine memory Include the Virtual Machines memory to be able to restore the VM in a in the backup snapshot running state. Wait after snapshot Time (in seconds) DS-Client will wait after the snapshot is taken before starting the backup. Default is 0, range is 0-600 Applies to each file in the backup set. This is the maximum number of backup re-tries if libcurl transmission errors are encountered during a backup session. Default is 0, range is 0-100
Confidential.
Maximum Backup Retries

Additional Backup Set Options XenServer backup sets. If a Virtual Machines status is not shutdown, then that VM is not able Skip Virtual Machines not ready to export as backup. Virtual Machines that are running or suspended for export will be skipped. This options appears if the XenServer supports a snapshot feature. If checked, the Virtual Machine will be backed up using XenServer's native Snapshot capability. This means the Virtual Machine can be backed up even if the Virtual Machine is running. If unchecked, the Virtual Machine must be stopped in order to perform a backup. Notes: 1) If editing an existing XenServer backup set, and DS-Client cannot connect to the XenServer, the message Unable to determine availability will appear. 2) If Use Snapshot is selected, any backed up generation can only be restored as a Template. If selected, instead of dump files, the DS-Client will create Pipes (FIFO files) in the dump directory and instruct Sybase to dump there. ON: Saves the VM state (running programs loaded in memory). OFF: Backs up the VM as if it were not running. ON: Backup will export the actual running VM and all its snapshots. OFF: Backup will export the actual running VM only (no snapshots).
Use Snapshot (XenServer 5.5 or higher)
Additional Backup Set Options Sybase backup sets. Use file-based pipes to backup the data
Additional Backup Set Options VMware VADP backup sets. Backup Virtual Machine Memory (Local DS-VDR backup set) Backup Virtual Machines snapshots (Local DS-VDR backup set) Export to host (Local DS-VDR backup set) Export to datastore (Local DS-VDR backup set) Attempt to quiesce I/O before taking snapshot
This dropdown list contains the available ESX hosts where you can export the selected Virtual Machines. You must assign one as the target. Click [>>] to open the Specify Credentials screen. This is dropdown list of available Datastores on the destination host where you can export the individual VM disk. You must assign one as the target. Pause the applications, in order to guarantee a consistent and usable backup. This option requires that the VMware tools are properly installed and configured on the Guest Operating System of the Virtual Machine. vCenter version 4.0 (or higher) with Virtual Machine version 7 (or above). Attempts to reconfigure the Virtual Machine to use Changed Block Tracking (CBT). This monitors if the disk was changed between backup sessions, which improves backup performance if the disk was not changed. [Local DS-VDR Tool must be configured.] If selected, the normal backup (to DS-System) options are disabled. This option is only available when creating the backup set. It cannot be changed once it is set. This type of backup set will export the selected backup items (Virtual Machines) on the corresponding vCenter. Enter the IP address of the vCenter where you want to virtualize the selected physical computer. You must supply the credentials to the vCenter for a user with sufficient permissions to create a Virtual Machine. Click [>>] to open the Specify Credentials screen.
Attempt to use Change Block Tracking for backing up Virtual Machines
Use Local DS-VDR
Additional Backup Set Options Physical to Virtual backup sets.
Enter vCenter IP


Confidential.
Export to datacenter
Once DS-Client / Local DS-VDR Tool connects to the vCenter, this dropdown list displays the available datacenters. You can select a different one (if more than one are available). Once you select the datacenter, you will be able to select a specific hosts IP address where the virtualized machine will be created. You must supply the credentials to this host. Click [>>] to open the Specify Credentials screen. After selecting the destination host, you must select one of the defined vCenter datastores to which the new VM will belong. This option is selected by default when creating the backup set. It cannot be changed.
Export to host
Export to datastore Use Local DS-VDR
Set Properties - Options tab (Local DS-VDR backup sets)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the Local DS-VDR option settings for a backup set. Note: A Local DS-VDR backup set does not backup data to DS-System.
Backup Virtual Machine Memory Backup Virtual Machines snapshots Export to host ON: Saves the VM state (running programs loaded in memory). OFF: Backs up the VM as if it were not running. ON: Backup will export the actual running VM and all its snapshots. OFF: Backup will export the actual running VM only (no snapshots).
This dropdown list contains the available ESX hosts where you can export the selected Virtual Machines. You must assign one as the target. Click [>>] to open the Specify Credentials screen. This is dropdown list of available Datastores on the destination host where you can export the individual VM disk. You must assign one as the target.
Export to datastore
Additional Backup Set Options (Backup Set Properties dialog only) Attempt to quiesce I/O before taking snapshot Pause the applications, in order to guarantee a consistent and usable backup. This option requires that the VMware tools are properly installed and configured on the Guest Operating System of the Virtual Machine. vCenter version 4.0 (or higher) with Virtual Machine version 7 (or above). Attempts to reconfigure the Virtual Machine to use Changed Block Tracking (CBT). This monitors if the disk was changed between backup sessions, which improves backup performance if the disk was not changed. This option is selected by default when creating the backup set. It cannot be changed. This type of backup set will export the selected backup items (Virtual Machines) on the corresponding vCenter.
Attempt to use Change Block Tracking for backing up Virtual Machines
Use Local DS-VDR
Set Properties - Options tab (Windows database backup sets)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the option settings for individual backup sets. It appears for the following Windows database backup sets, if they support options for incremental and / or differential backup: Microsoft SQL Server VSS-aware Microsoft SQL Server

Confidential.
VSS-aware Microsoft Exchange Server VSS-aware Microsoft SharePoint Server
These settings are applied each time the set is backed up.
Backup set options Some options may not appear or may be grayed out, depending on your backup selection and DS-Client configuration. If checked, files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Note: This option cannot be used if Continuous Data Protection (CDP) is selected. Records all files that are backed up (you may view them in the Activity Log). Specifies that a backup stops if this number of errors are encountered. range 0-9999, 0 = no limit Note: The global default that appears in the New Backup Set Wizard can be configured using the Windows DS-Client MaxErrors Advanced Parameter. If checked, the backup set is flagged for Initial Backup. Click the [>>] button to select the Initial Backup Path. [Properties Tab only] Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver. If checked, the backup set is flagged to scan all files in the backup set prior to backup, in order to display an estimated completion time for the backup. You can select the compression type: LZOP: A faster compression than ZLIB, that comes at the expense of less compression. ZLIB: This compression method will normally produce better compression than LZOP, but will take more time to compress. Four different ZLIB strengths are available (Global, High, Medium, and Low). ZLIB Global is the default value set in the DS-Client Advanced Configurations Compression Type parameter; ZLIB High corresponds to a value of 9; ZLIB Medium = 6; and ZLIB Low = 3. None: Disables compression for this backup set. (This will only apply to backups performed after this section is made. Any backups currently online will retain the compression type used at the time of backup.)
Use buffer
Detailed log
Stop on errors
Initial Backup
PreScan
Compression Type
Use Local Storage [Properties Tab only] These options appear if you have the Local Storage Tool Enabled from your Service Provider, and you have specified a Local Storage Path in the DS-Client Configuration Parameters Tab screen. [Properties Tab only] Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). Backup data will be sent to the location specified in the Local Storage Path field.
Save


Confidential.
Cache
[Properties Tab only] Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). Backup data will be sent to the location specified in the Local Storage Path field. [Properties Tab only] Click [>>] to choose a specific local storage path for this backup set. Opens the Enter Local Storage Path. If you do not make a selection, the path from the DS-Client Configuration Parameters Tab screen is used.
Local Storage Path
Database Backup Policy Some options may not appear, depending on your backup selection and DS-Client configuration. Full dump: Always [Default] This is the default behavior for all Windows database backups. Each backup of the target Server performs a full dump of each database. Performs a full dump of the database on first backup, followed by differential backups until another full backup is needed (*). [MS SQL Server backup sets] The database can be selected with or without the backup transaction log option. Performs a full dump of the database on first backup, followed by incremental backups until another full dump is needed (*). [MS SQL Server backup sets] The database should be selected without the backup transaction log option. (Even if backup transaction log is selected, that option will be ignored if this backup policy is selected.) [MS SQL Server backup sets] The databases Recovery Model must be: full or bulk_logged.
Full dump: Plus Differential
Full dump: Plus Incremental
(*)
A full dump is needed (other than first time) when: a database has been backed up by another backup set (or manually from the SQL tools); a database has been restored (either from another database or an earlier generation); the database properties have been modified (recovery model switched to simple); local cache is used for the backup set (This can occur for Regular backup sets with the option Transmission cache on local storage, but only when a generation must actually pass through the local cache. If the connection to DS-System is down, then a full dump occurs and is written to the local cache. After that dump, DS-Client continues with the selected database backup policy.) the DS-Client requires a Master generation (configured in the MasterGenerations value of the DS-Client Advanced Parameters - Setup Menu > Configuration > Advanced Tab).
Database Backup Policy Schedule Over-ride Rules [OPTIONAL] This entire section is optional. It provides more precise control over the full dump for large Microsoft databases in high performance environments. These over-ride rules are applied in addition to the regular backup schedule for this backup set. This means the backup set must be scheduled to run on the first day of the month, if the over-ride rule Full every month on 1st day... will apply. Prevents a full dump from being performed during the time window on the selected day(s). This skips performing a full dump of the database, for up to the maximum number of consecutive times specified in the MaxNonFullDumps parameter of the DS-Client Advanced Parameters (Setup Menu > Configuration > Advanced Tab). For database integrity reasons, a full dump should be performed before that amount is reached. DS-Client will automatically try to run one full dump (once a day) if this option is set. Forces a full backup to be performed at the specified interval. hour(s), day(s), week(s), month(s), or year(s)
Do not start full dump on
Full every


Confidential.
Full every week on Full every month on
Forces a full backup to be performed on a specific day of the week. You must specify a time, after which the full backup can be performed. Forces a full backup to be performed on a specific day of the month. You must specify a time, after which the full backup can be performed.
Pre/Post Click to access the Pre & Post Execution screen. For more information, see: Pre & Post Execution screen.
Set Properties - Performance tab (Windows DS-Client)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the Performance settings for individual backup sets.
Maximum pending asynchronous I/O for a file This is the maximum I/O operations the DS-Client will queue for each file from this backup set. Use DS-Clients settings (Default) Uses the setting in the DS-Client Advanced Configurations > Category: Performance > Parameter: MaxPendingIOPerFile. You can override the default and set a custom value that only applies for this backup set. This option is intended for high performance backup environments. You must be able to test the different settings to determine the optimal value. This is only useful if the target storage containing the backup data is fast and efficient enough to take advantage of the increased I/O. WARNING: Slower storage may suffer performance drops if this value is increased too much.
Use specific value
Read buffer size for backup This option adjusts the internal buffer amount that the DS-Client allocates for reading individual files for backup. Use DS-Clients settings (Default) Uses the setting in the DS-Client Advanced Configurations > Category: Performance > Parameter: FileReadBufferSize. You can override the default and set a custom value that only applies for this backup set. You must be able to test the different settings to determine the optimal value. WARNING: Slower storage may suffer performance drops if this value is not properly set.
Use specific buffer size (KB)
Set Properties - Retention tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view and change the Retention settings for individual backup sets. Retention Rules are only enforced if an Enforce Retention task is scheduled or it is run on demand for this backup set.
Name Description No Retention Rule: Use a specific Retention Rule: select from the list of the Retention Rules defined on the DS-Client. (Click [...] to edit or create a new Retention Rule.) Shows a description of the selected Retention Rule.


Confidential.
Set Properties - Set Info tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view information about the selected backup set.
Set Information Backup type Status Set name Shows the type of selected backup set (File System, MS SQL Database, etc...). Shows the Backup Set status (Active, Suspended, or Synchronize). Shows the Backup Set's name. You can change this field, to change the name of the backup set. Shows the type of backup set: Regular Self-Contained Local-Only Statistical Shows unique backup set ID number assigned by the DS-Client. (Multi-Tenant DS-Client only) Select from the list of available customers. This backup set will be grouped under the selected customer in the Backup Sets tree. If no customers have been defined (Setup Menu > Multi-Tenant: Customer Management), you will only have the <Unspecified Customer> selection. Displays the last date and time that this backup set was changed in the DSClient database. Activities that can update a backup set include: Backup Displays the last date and time that this backup set was changed in the DSClient database. Activities that can update a backup set include: Backup Delete Synchronization Displays the date and time of the last successful (i.e. without errors) scheduled backup. Displays the amount of online storage the selected backup set occupies (including all online generations). Note: CDP backup sets that are currently running will have this field updated every 30 minutes. Displays the number of files that make up the Online amount for the selected backup set. Each generation is counted as a separate file. Note: CDP backup sets that are currently running will have this field updated every 30 minutes. Displays the amount of local storage the selected backup set occupies (if applicable). The backup set must be configured to Save on Local Storage and data must be in the Local Storage Path. Displays the number of files that make up the Local Storage amount for the selected backup set (if applicable).
Set type
Set ID
Customer
Backup Information Last backup (Windows DS-Client) Last backup set update time (Linux DS-Client) Last successful
Online amount
Online files
Local Storage amount
Local Storage files


Confidential.
Set Properties - Share tab

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view information about the selected backup set shares.
Connect as Shows the connection information. Click [>>] to open the Specify Credentials (Windows DS-Client) screen.
Allows you to use the DS-Client services account credentials to connect to the local (DS-Client) computer. Use DS-Client Account You must be logged in through DS-User using an Administrator account (or (Windows DS-Client only) equivalent). This option is only available when you select My Computer (i.e. the local DS-Client computer). Ask for NAS API credenPrompts you to enter valid connection information for the selected NAS. tials Opens the Enter NAS API Parameters (Windows DS-Client) screen. (Windows DS-Client only) Disk share File system Maximum filename length Case preserved File compression Case sensitive Volume compressed Persistent ACL Shows the selected disk share on the provider\node, where the backup items are located. If there are more than one shares included in this backup set, then you may switch between them by selecting the share from the drop down list. Shows the file system name associated with the selected disk share. Shows the maximum number of characters in any filenames originating from the share. A check indicates the share's file system preserves the case of the filenames when it places a name on disk. A check indicates the share's file system supports file-based compression. A check indicates the share's file system supports case-sensitive filenames. A check indicates the share's volume is a compressed volume. A check indicates the file system preserves and enforces ACLs (Access Control List, file security).
Set Properties - Share tab (Linux DS-Client)

This screen can appear in a New Backup Set Wizard or in a Properties Dialog. It allows you to view information about the selected backup set shares.
Connect as Change to (UNIX-SSH only) Shows the credentials used to access the network resource. Shows the credentials that Linux DS-Client will use to access data on the network resource. After successful login to the remote source, "sudo" (switch user) will be performed for Linux DS-Client to use these credentials. Shows the selected disk share on the provider\node, where the backup items are located. If there are more than one shares included in this backup set, then you may switch between them by selecting the share from the drop down list. Shows the file system name associated with the selected disk share. Shows the maximum number of characters in any filenames originating from the share.
Disk share File system Maximum filename length
Set the scanning options



Confidential.
The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to select additional options that can apply once any unprotected network resource(s) have been discovered.
Create new backup sets for unprotected computers\shares If selected, a new backup set will be created for each unprotected computer the scan identifies. Owner Schedule Add System State Add Services DB Select the user that will become the owner of any backup set created by this process. This list comes from the Users & Groups screen on the DS-Client computer. Select the schedule (or None) to apply to any backup set created by this process. If a backup set is created for a new computer, this option includes the Windows System State backup item. If a backup set is created for a new computer, this option includes the Windows Services Database backup item.
Send notification If selected, a notification E-Mail is sent on completion of the scan. E-Mail Format Enter the E-Mail address of the recipient. Choose the E-Mail format: HTML Plain Text
Set the scanning parameters

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen allows you to specify scanning parameters.
Attempt to reconnect Number of threads for scanning Start Scan Now Select the number of times the scan process will try to reconnect and the interval between attempts. Select the number of scan threads to be used by the process. (Default is on.) Starts the scan immediately after finishing this Wizard.
Share List screen

LAN STORAGE DISCOVERY TOOL The Share List displays the shares on the LAN that were discovered by the Share Discovery process. Each new Share Discovery process will add any new shares to grow this list.
Share List Enabled/Disabled Date Share Name Shared Path Follow (Windows DS-Client only) File System (Windows DS-Client only) Icon shows whether the share has been enabled or disabled from the Scan Process. By default, a share may be enabled or disabled from scanning depending on information in the Description section. Shows the date of the last scan. Shows the computer and share name. Shows the path on the computer. Indicates if the scan will follow Reparse Points and scan their destination location (NTFS only). Shows the type of File System for the share.


Confidential.
Connect As (Windows DS-Client only) Description Scanned Size Options Enable Disable Set Credentials
Shows the username of the credentials used to connect to that share. Shows additional information about the share (if any). Shows the size of the share (in bytes). Allows the highlighted share(s) to be scanned. Removes the highlighted share(s) from the scan process. The Share Discovery Process automatically disables shares that it detects to be redundant or inaccessible. Highlight individual shares and click Enable/Disable to add/remove from the Scan. Opens the Set Credentials screen. Removes the highlighted share from the list (along with all associated scan settings for that share).
Remove
Opens the Set Follow Option screen (NTFS only) for the highlighted share(s): Follow - Will follow Reparse Points encountered in a scanned share. A Reparse Follow Reparse Point Point is a link to a different location (directory or device). This will result in a (Windows DS-Client larger amount scanned. only) Don't Follow - Will not follow Reparse Points encountered in a scanned share. Reverse follow setting - Inverts the highlighted share(s) setting.
Share Usage Report screen

Owner Size Files Share Share (dropdown list) User name of the share owner. Total size of the files in the share. Total number of files in the share. Path of the share on the LAN. Search <All> or individual shares.
Shutdown DS-Client Computer screen

It may become necessary for a system administrator to force a shutdown of the DS-Client computer. This can be accomplished from the System Activities Administration screen.
Shutdown in [] seconds Reboot Send message Shutdown Specify the shutdown interval (30-900 seconds). Click to reboot the DS-Client computer after shutdown. Enter a message to send to connected users. Click to initiate the Shutdown.
SMTP settings
This screen allows you to configure the SMTP notification settings.
SMTP Server Settings SMTP Server Port Type the DNS name or IP address of the SMTP server to use. Enter the port number to use. (The default is 25.)


Confidential.
Server requires authentication
Check to configure authentication settings (if required): Account name: Username to connect to SMTP server. Password: Enter password. Confirm: Confirm password. Select if the SMTP server you are using requires the SSL (Secure Sockets Layer) protocol for communication. Public E-Mail servers that support SSL include: Gmail server Yahoo server Select if the SMTP server you are using requires the TLS (Transport Level Security) protocol for communication. Public E-Mail servers that support TLS include: Gmail server Yahoo server Hotmail server
Server requires SSL
Server requires TLS
Snapshot Transfer - Register Storage Management screen

This screen contains the list of Storage Devices this DS-Client is configured to connect with for Snapshot Transfer purposes.
Storage Device List Each line represents a different Storage Device that can be used for Snapshot Transfer. New Edit Remove Add a new Storage Device to the list. Opens the Snapshot Transfer - New / Modify Storage screen. Edit the highlighted Storage Device from the list. Opens the Snapshot Transfer - New / Modify Storage screen. Remove the highlighted Storage Device from the list. (To be removed, the Storage Device must not be in use.)
Snapshot Transfer - Snapshot Retention Management screen

This screen contains the list of Retention Policies this DS-Client can apply to the snapshots taken by each Snapshot Transfer configuration.
Retention Policy List Each line represents a different Retention Policy that can be applied to a Snapshot Transfer configuration. Note that Retention Policies are applied at volume-level (all Snapshot Transfers on the same destination volume use the same Retention Policy). New Edit Remove Add a new Retention Policy to the list. Opens the Snapshot Transfer - New / Modify Snapshot Retention screen. Edit the highlighted Retention Policy from the list. Opens the Snapshot Transfer - New / Modify Snapshot Retention screen. Remove the highlighted Retention Policy from the list. (To be removed, the Retention Policy must not be in use.)


Confidential.
Snapshot Transfer - Snapshot Schedule Management screen

This screen contains the list of Snapshot Schedules this DS-Client can apply to each Snapshot Transfer configuration.
Snapshot Schedule List Each line represents a different Snapshot Schedule that can be applied to a Snapshot Transfer configuration. Note that Schedules are applied at volume-level (all Snapshot Transfers on the same destination volume use the same Schedule). New Edit Remove Add a new Snapshot Schedule to the list. Opens the Snapshot Transfer - New / Modify Snapshot Schedule screen. Edit the highlighted Snapshot Schedule from the list. Opens the Snapshot Transfer - New / Modify Snapshot Schedule screen. Remove the highlighted Snapshot Schedule from the list. (To be removed, the Schedule must not be in use.)
Snapshot Transfer - New / Modify Storage screen

This screen contains the list of Registered Storage that this DS-Client can connect to for Snapshot Transfer related activities.
Vendor Name Address Port User Name Password Use HTTPS Protocol Specifies the Storage Device type, vendor or specific model. Currently supported types: NetApp Enter a descriptive name for this Storage Device. Enter the IP address of the Storage Device. Specifies the port number for accessing the API. The specific port must be open on the Storage Device. Specifies the User Name for a user on the Storage Device. This user requires permissions to execute the API commands on the Storage Device and usually needs to be a member of the Administrators group. Specifies the corresponding password for the Storage Device user. Specifies the HTTPS protocol for accessing the API. The specific protocol must be enabled on the Storage Device. If this is not selected, the HTTP protocol is used.
Snapshot Transfer - New / Modify Snapshot Retention screen

This screen allows you to define different Retention Policies that DS-Client can instruct to use with different Snapshot Transfer configurations.
Name Enter a descriptive name for this Retention Policy. Number of snapshots to keep Each field represents a different Retention Rule. Each rule defines what snapshots to keep, and the combination of rules can overlap. The sum of all the rules is the Retention Policy. When enforced, all snapshots that do not fit into any of these rules are deleted. Latest Hourly Daily This number of the latest snapshots is kept. One snapshot per hour is kept, going back this number of hours. Hour Start / Hour End: same as above, except the interval is in hours. One snapshot per day is kept, going back this number of daily copies. Day Start / Day End: same as above, except the interval is in days.


Confidential.
Weekly Monthly
One snapshot per week is kept, going back this number of weekly copies. Week Start / Week End: same as above, except the interval is in weeks. One snapshot per month is kept, going back this number of monthly copies. Month Start / Month End: same as above, except the interval is in months. One snapshot per year is kept, going back this number of yearly copies. Year Start: The snapshot that is kept is the first one from the beginning of the calendar year. Year End: The snapshot that is kept is the last one from the end of the calendar year.
Yearly
Snapshot Transfer - New / Modify Snapshot Schedule screen

This screen allows you to define the different Snapshot Schedules that can be assigned to each Snapshot Transfer defined on this DS-Client.
Name Enter a descriptive name for this Snapshot Schedule. Weekdays tab Select the days of the week when the schedule will run. AM tab Select the AM hour(s) when you want this schedule to trigger the Snapshot Transfer to run. PM tab Select the PM hour(s) when you want this schedule to trigger the Snapshot Transfer to run.
Snapshot Transfer Setup Wizard - Select Storage screen

This screen allows you to select one of the configured Storage Devices (from DS-User > Snapshot Manager > Register Storage).
Storage Device List Select the source or destination Storage Device to use for this Snapshot Transfer configuration. [...] - Click to open the Snapshot Transfer - Register Storage Management screen. Description Additional information about the selected Storage Device appears in this section.
Snapshot Transfer Setup Wizard - Select Snapshot Retention screen

This screen allows you to select or configure a Snapshot Retention Policy for this Snapshot Transfer. Note: Only one Retention Policy per destination volume is permitted (this panel is skipped if already defined for the same destination volume). Select one of the configured Retention Policies from the list. A description of the selected policy appears. To configure a new Retention Policy, click [...] to open the Snapshot Transfer - Snapshot Retention Management screen.
Snapshot Transfer Setup Wizard - Select Snapshot Schedule screen

This screen allows you to select or configure a Snapshot Schedule for this Snapshot Transfer. Note: Only one Schedule per destination volume is permitted (this panel is skipped if already defined for the same destination volume). Select one of the configured Snapshot Schedules from the list. A description of the selected schedule appears.

Confidential.
To configure a new Snapshot Schedule, click [...] to open the Snapshot Transfer - Snapshot Schedule Management screen.
Snapshot Transfer Setup Wizard - Select Volume screen

This screen allows you to select a volume on a Storage Device. Depending on when this screen appears, it can be either to select the source or destination volume. You can only select one volume per Snapshot Transfer configuration.
Snapshot Transfer Setup Wizard - Specify Snapshot Transfer Name screen

This screen allows you to set the Snapshot Transfer configuration name and some optional configurations.
Name Bandwidth Description Give this Snapshot Transfer configuration a name (a default suggestion is provided). (Optional) Unlimited: Data will be transferred from Source to Destination as fast as possible. Limited to (KB/sec): Throttle the snapshot data transfer rate from Source to Destination to this speed. You can add additional descriptive text here.
Snapshot Transfer Manager

The Snapshot Transfer Manager screen contains the list of defined Snapshot Transfer configurations managed by this DS-Client.
Snapshot Transfer tree This tree contains a list of all Snapshot Transfer configurations managed by this DS-Client. Storage Device level Volume level qtree level Storage device level No options are available at this level. This level contains settings for a specific volume on the destination Storage Device. Right-click options: Start Update: Starts the incremental transfer for all qtrees (Snapshot Transfer configurations) contained in this volume. List Snapshots: All snapshots of this volume that currently exist are displayed. Opens the Snapshot Transfer - Snapshots - Storage:Volume screen. Properties: Opens the Snapshot Transfer Property (destination volume) screen Each qtree is a unique container for a Snapshot Transfer source:destination mapping. Right-click options: Start Update: Starts the incremental transfer for this specific qtree. Delete Snapshot Transfer: Deletes this Snapshot Transfer (both the configuration and the data in the destination volume). Properties: Opens the Snapshot Transfer Property (source vault) screen Create a new Snapshot Transfer configuration on this DS-Client. Opens the Snapshot Transfer Wizard: Snapshot Transfer Setup Wizard - Select Storage screen.
Volume level
qtree level
Snapshot Transfer Setup


Confidential.
Snapshot Transfer Property (destination volume) screen

This screen shows the configured Retention Policy and Schedule that apply to a specific destination volume. All Snapshot Transfers on this destination volume will use these Retention and Schedule configurations.
Retention tab Select one of the configured Retention Policies from the list. A description of the selected policy appears. To configure a new Retention Policy, click [...] to open the Snapshot Transfer - Snapshot Retention Management screen. Schedule tab Select one of the configured NAS Schedules from the list. A description of the selected schedule appears. To configure a new NAS Schedule, click [...] to open the Snapshot Transfer - Snapshot Schedule Management screen.
Snapshot Transfer Property (source vault) screen

This screen shows properties for a specific Snapshot Transfer configuration.
Source Destination Source path where the data originates. Storage Device name: volume [/ qtree] Destination path where the data is copied. Storage Device name: volume [/ qtree] (Optional) Unlimited: Snapshot will be transferred from Source to Destination as fast as possible. Limited to (KB/sec): Throttle the snapshot data transfer rate from Source to Destination to this speed. You can add additional descriptive text here.
Bandwidth
Description
Snapshot Transfer - Snapshots - Storage:Volume screen

This screen shows a list of the snapshots in the target destination Storage:volume.
Specify Credentials (Windows DS-Client)

Use this screen to provide or modify credentials to network resources, including database credentials. You can click [...] beside any User Name field to browse for an encrypted key file (one that contains the user credentials). If the file is valid, you must enter the correct key to unlock the file. Opens the Enter unlock key screen.
Network Credentials: Network Credentials Database Credentials: MS SQL GroupWise Oracle Server MySQL Lotus Domino Server Backup from the Cloud


Confidential.
Network Credentials User Name Password Enter a valid User Name. Enter the corresponding password. Select the Server where the User Name is defined. This field appears if the sever you want to connect to can require additional information. This field can appear in two forms: An editable drop down list appears. You can type or select the server/ domain where the specified user account is defined. An edit field appears if the server you are connecting to can have "From" information (ex: context in NDS authentication). For NetWare servers, you should supply a context. If you provide From information, NDS authentication will be used as .username.from. Otherwise, bindery authentication will be performed.
From
Notes NetWare
MS SQL User Name Password
Database Credential Information Enter a valid database User Name. Enter the corresponding password.
GroupWise User Name Password
Oracle Server User Name Password Service Name
Database Credential Information Enter a valid database User Name. Enter the corresponding password. Type the name of the Oracle service database you wish to backup. The DS-Client computer must be running the Oracle client with Recovery Manager. The target Oracle server must have the file ORASTBT.DLL in its System Root path.
MySQL User Name Password
Lotus Domino Server
Database Credential Information You must search for the notes.ini file that specifies the user.id credentials for this specific Lotus Domino Server Database. The user.id file is provided by the Lotus Notes Administrator. (The password must also be supplied by the Lotus Notes Administrator.) The notes.ini file is generated by the Lotus Notes (client) installation on the DS-Client computer. If you move these files, make sure to edit the notes.ini file to reference the exact current path (as seen from the DS-Client computer) to the user.id file in its KeyFileName parameter. Enter the corresponding password.
Confidential.
Connect As
Password

Backup from the Database Credential Information Cloud Username Password Enter the Salesforce.com username and password. Enter the corresponding password. Note: If you ever need to change this password, you must also update your security token from Salesforce.com (by obtaining a new one from them). Select the target database for backup: Production (default): This the live, functioning version of the Salesforce.com database. Sandbox: This is the developer / testing version of the Salesforce.com database. The security token that was E-Mailed to you by Salesforce.com.
Target Token
Specify Credentials (Linux DS-Client)

Use this screen to provide or modify credentials to network resources, including database credentials. You can click [...] beside any User Name field to browse for an encrypted key file (one that contains the user credentials). If the file is valid, you must enter the correct key to unlock the file. Opens the Enter unlock key screen.
Network Credentials: Network Credential Information sudo as an Alternate User Database Credentials: MySQL / PgSQL DB2 Server Oracle Server Sybase Server Ask for NAS API credentials: NAS
Network Credential Information User Name Password / Passphrase Enter a valid User Name. Enter the corresponding password (or passphrase). Passphrase is for UNIX-SSH only, when you select or specify a Private Key File. The passphrase will be used for public key authentication. This feature allows you to backup/restore using SSH public-key authentication. 1. If no private key file is specified: If a default private key file is found on the DS-Client machine, try public-key authentication first. If that fails, try password authentication. If no default key file is found, try password authentication only. 2. If a private key file is specified for the backup set: The SSH connection will use public-key authentication only.
Private Key File (UNIX-SSH only)


Confidential.
sudo as an Alternate User (UNIX-SSH & ESX Connect)
User Name Password
These credentials will be used to access the data. For security reasons, you may not want to use a super user for remote login to a source machine. Linux DS-Client will login to the source machine as a regular user, and then use sudo to execute a shell as an alternate user with higher access permissions. Linux DS-Client will login to the source machine with the supplied network credentials (or Java DS-User login user if none are supplied). When accessing data, Linux DS-Client will use sudo to execute a shell as this alternate user. Enter the User Name of the alternate user on the source machine This is the user that DS-Client will use to perform the command (e.g. root). For this to work, the user that connects to the source machine must be granted permission on that machine to perform sudo. Enter the password of the user that connects to the source machine.
MySQL / PgSQL User Name Password Port Number
Database Credential Information Enter a valid database User Name Enter the corresponding password Enter the port that will be used to connect to the database. Use the default, unless you know for certain the database is configured to allow backup / restore on a different port.
DB2 Server User Name Password Node Name Port Number DB2 Client Instance
Database Credential Information Enter a valid database User Name on the DB2 database server you want to back up. Enter the corresponding password Enter the local alias of the target DB2 server node. This is the name on the DS-Client computer that is used to identify that node. This is only required for remote DB2 server backup and restore (i.e. if the DB2 is not on the same machine as the DS-Client). Enter the TCP/IP port number of the DB2 Server Database Manager instance. Enter the local DB2 instance name installed on the DS-Client computer.
Oracle Server User Name Password Service Name
Database Credential Information Enter a valid database User Name. This user must have the SYSDBA privilege, otherwise you will get an ora-1031 error. Enter the corresponding password. Enter the Service Name of the Oracle database you wish to backup. The Service Name is the TNS alias that is specified in the tnsnames.ora file on your Oracle client.
Sybase Server User Name Password
Database Credential Information Enter a valid database User Name Enter the corresponding password
NAS NAS Type
NAS API Credential Information Specifies the NAS device type, vendor or specific model. Currently supported types: NetApp FAS filers


Confidential.
API Protocol Port Number User Name Password Mount-point
Specifies the protocol for accessing the API. Commonly used protocols are HTTP or HTTPS. The specific protocol must be enabled on the NAS device. Specifies the port number for accessing the API. This port must be open on the NAS device. Specifies the User Name for a user on the NAS device. This user requires permissions to execute the API commands on the NAS device and usually needs to be a member of the Administrators group. Specifies the corresponding password for the NAS user. Specifies the mount point that DS-Client will use to mount the NAS share during the backup/restore.
Specify network credentials for LAN Share Discovery screen

LAN STORAGE DISCOVERY TOOL The Share Discovery Wizard helps you to identify all the available backup shares on your LAN. This screen allows you to specify which credentials to use when connecting to the shares on the LAN.
Additional credentials section Lists the credentials to use for the Share Discovery Scan Process. It is highly recommended that you supply network administrator-level credentials in order to successfully scan the selected shares. Connect As: Shows the username. From: Shows the domain or computer name of the user credential. Priority: Shows the order of credentials that the DS-Client will use to attempt to scan each share. If the highest priority credentials fail, the DS-Client tries the next in line until it succeeds (or runs out of additional credentials). Add Modify Delete Overwrite existing share credentials Click to add a new credential entry. Opens the Set Credentials screen. Click to modify the highlighted credential entry. Opens the Set Credentials screen. Removes the highlighted credential from the list. If you have already scanned the LAN, each scanned share has been assigned the best suited credentials for scanning. Click to overwrite these credentials (the DSClient will retest from the list of credentials you provided in the Additional Credentials section.).
Stop DS-Client Node

[Grid DS-Client] This screen allows you to stop the selected Grid Node. This stops the DS-Client service on that node.
Wait for all running activities to complete: Stops the DS-Client on the selected node, after all the current activities have completed. No new activities will be allowed once you click OK. Stop when all activities complete or force stop after [...] minute(s): Stops the DS-Client on the selected node after all the current activities have completed, or forces a stop after the specified time has elapsed. No new activities will be allowed once you click OK. Stop Type: Shut down the node Reboot the node Only stop the DS-Client service (keep the computer running) OK Proceed with stopping the node. Warning: Once you press this button, the action cannot be reversed.


Confidential.
Storage Summary screen

The Storage Summary can help administrators analyze the trends for Online amount, number of files and backup time. The default is a chart, but a list is available (and is easier to read if you are viewing more than 3 series). In Win32 DS-User, you can use the Tool Bar at the top of this screen to modify the appearance of the graph.
Chart options Select by section From To Click to select the date where you wish to begin viewing storage summary information. Click to select the last day for which you wish to view storage summary information. By default this is set to the current date. Allows you to specify a particular user. The default is blank, which searches for all users of the DS-Client. You can type in this field or click [>>] to open the Select Backup Sets screen. If you select a backup set, the owner of the backup set is automatically selected for this field. Allows you to specify a particular computer or backup set. The default is blank, which searches for all backup sets of the DS-Client. You can type in this field or click [>>] to open the Select Backup Sets screen. Click to specify a user, server, and/or backup set to view in the Graph/List. Opens the Storage Summary Selection screen. Click to update the display. You must refresh every time you change a parameter in the Select by section. Choose from one of the following radio buttons: Daily, Weekly (Default), Monthly Choose from either Chart or List views for this screen. Select the backup set type(s) whose information you want to display: Regular Statistical Self Contained Local Only Local DS-VDR Click to change the information displayed in the storage summary. This brings up the Storage Summary Series screen. Win32 DS-User: The top row contains option icons and drop down lists for you to customize the screen. Java DS-User: Chart Type selection (Line or Bar Chart)
User (Java DS-User)
Node / Set (Java DS-User) Select (Win32 DS-User) Refresh Chart options section Interval View (Java DS-User)
Backup set type section
Series
Storage Summary Selection

This screen allows you to select a particular user, node, and/or set.
User Node/Set Specify a particular username. Specify a particular server, computer, or backup set. Click the >> button to bring up the Select from Backup Sets screen. You may browse through and select the node, or node/set that you would like a summary. Leave this field blank to see a summary of all backup sets.


Confidential.
Storage Summary Series screen

This screen allows you to change the information that is displayed in the Storage Summary.
Time statistics (in minutes) Average Time Actual Time Files statistics Total Files Inc Files New Files Backup Files Inc Backup Files Amount statistics (MB) Total Online Inc Online New Online Transmitted Inc Transmitted Online Backup Inc Online Backup Total amount stored Online. This is a derived figure, showing the increment to the Total Online. Total amount for the new backed up files. Amount of data transmitted to Online (including compression/encryption, etc.). This is a derived figure, showing the increment to the Transmitted amount. Total amount of data backed up for the selected period. This is a derived figure showing the increment to Online Backup. Total number of files stored Online (including the generations). This is a derived figure, showing the increment to the Total files. Total number of new backed up files (i.e.: not including files with previous generations). Total number of files backed up for the selected period. This is a derived figure, showing the increment to the Backup Files. An average of the backup time for Scheduled Backups. Actual backup time duration of both Scheduled and Demand Backups for the selected period.
System Activities Administration screen

The System Activities Administration screen allows an administrator or backup operator to perform different administrative tasks on the DS-Client.
DS-Client Activities Toggle to activate or suspend operation of all scheduled activities Scheduled activities Enable/Disable on the DS-Client. (This will reset to Enabled if the DS-Client service is restarted). Demand activities Enable/Disable DS-Client Operations Shutdown DS-Client Computer Repair DS-Client database Administrative Processes Statistics updated on Daily Admin. Weekly Admin. System Click Update Now to run the Update Statistics process immediately. Click Run Now to run the Daily Admin. process immediately. Click Run Now to run the Weekly Admin. process immediately. Opens the Weekly Admin Options screen Click to open the System Status screen. See: DS-Client System Status screen Click to initiate or abort the shutdown of the DS-Client. Click to recover or repair the DS-Client database. See: Repair DS-Client screen Toggle to allow or prevent users from performing demand activities. (This will reset to Enabled if the DS-Client service is restarted).


Confidential.
Tape Converter - Options

[Windows DS-Client] This screen lets you specify the conversion options.
Before Conversion Tape Password The current implementation does not require any input. If the tape is in MTF, DS-CliBackup Set Password ent can convert the data without entering any password(s). For each conversion process, you must specify a the target path. DS-Client will automatically create a unique sub-folder in this path for the conversion. Once written, ship that folder to the BLM Archiver location for import. Click [...] to select a path. This opens the Initial Backup Settings screen. Each Archive Package is automatically time-stamped. To make searching Archive Packages easier, you can add your own BLM Session label (alphanumeric string) By default, this is the same as the set name from the Tape.
After Conversion Target Path
BLM Session Backup Set Name
Tape Converter - Select the backup set

[Windows DS-Client] In this screen, you can select the tape you want to convert.
Identify Tape Refresh Instruct DS-Client to try to identify the contents of the highlighted tape. Updates the screen with the latest information that DS-Client has from the Tape Librarys memory. A list of the tapes that the DS-Client can recognize in the attached Tape Library. Unidentified Tapes: Shows a list of recognized tapes (the Tape Label appears). This is fast, since it draws the information from the Tape Librarys memory. Identified Tapes: Shows a tree of the identified Computer > Backup Set Name > Tape(s). You only need to identify a tape once, unless you change the tapes or restart the DS-Client service. Depends on the item highlighted in the Tape List. Tape: Shows the Tape Label, and corresponding description (from the tape itself). Backup Set: Shows the Backup Set Name, Backup Time, and Size.
Tape List
Description
Tape Converter - Select the directories

[Windows DS-Client] This screen shows a tree of the backup files. You can select items at the folder-level. By default, the entire backup set is selected for conversion.
Tape Converter - Summary

[Windows DS-Client] This screen shows a summary of the tape data that is about to be converted.
Test DS-System Connection

This screen shows the test results for the selected DS-System connection.


Confidential.
Title Setting
(Win32 only) This screen controls the title settings for the Load Summary.
Text Font Size Style Word wrap
Unprotected LAN Resource Node Summary

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resource (shares) on your LAN. This screen displays the results of the last scan, sorted by computer (server).
Last Scan The data and time the Unprotected LAN Resource Discovery process last scanned the LAN. The contents of this screen come from that process.
Node List Server Name - Network name of the computer. IP Address - Network IP address of the computer. Version - Operating System version running on the computer. Revision - Operating System service pack / update level. New - Indicates if the computer is new (was not backed up prior to the last scan). Note - Additonal notes, if available. E-Mail Exclude Shares Backup Set E-Mail the results of the last Unprotected LAN Resource scan. Opens the Send Unprotected LAN Resource Discovery E-Mail screen. Exclude the highlighted computers (nodes) from the next scan. View a list of the unprotected resources, sorted by share. Opens the Unprotected LAN Resource Share Summary screen. View a list of the new backup sets automatically created by the last scan process. Opens the New Backup Sets Summary screen.
Select By Server Type - Display the list of unprotected computers that fit the selected category. Refresh Update the list based on the Select by options.
Unprotected LAN Resource Share Summary

UNPROTECTED LAN RESOURCE DISCOVERY TOOL The Discovery Wizard helps you to identify all the unprotected resources (shares) on your LAN. This screen displays the results of the last scan, sorted by share.
Last Scan The data and time the Unprotected LAN Resource Discovery process last scanned the LAN. The contents of this screen come from that process.
Node List Server Name - Network name of the computer. Share Name - Share name on the computer. Share Path - Share path on the computer. Connect As - Credentials used to connect to the share. File System - File system running on the corresponding share. New - Indicates if the share is new (was not backed up prior to the last scan). E-Mail E-Mail the results of the last Unprotected LAN Resource scan. Opens the Send Unprotected LAN Resource Discovery E-Mail screen.
Confidential.

Exclude
Exclude the highlighted computers (nodes) from the next scan.
Select By Server Name - Allows you to filter for a specific computer. Share Type - Allows you to filter for shares that are protected or unprotected. Refresh Update the list based on the Select by options.
Users / Groups for ...

This screen will specify users if you have highlighted a group, or groups if you have highlighted a user in the Users/Groups screen.
Group/Name Shows the Groups associated with the selected user, or the users associated with the selected group. Shows the server/domain where the user or group is defined.
Description/Full Name Shows the description of a group, or the full name of a user. From
Users & Groups screen

This screen displays the users and groups using the DS-Client. The DS-Client records information about users. This information is used to enforce Maximum Online limits, Permissions, as well as to apply ownership to backup sets.
User / Group Icon Name Full Name From Max Online (MB) Effective (MB) Used (MB) Show Users / Show Groups Delete Max Online Shows whether the corresponding entry refers to a specific user or a group. Displays the user or group's name. May display a more descriptive name about the user or group. Displays the server/domain where the user or group is defined. Shows the maximum online storage amount allocated to the user or group (if any). Shows the maximum online storage amount for a user based on Group limit (if any) - the lower of the Group or User limit will apply. Shows the storage amount used by the user or group (if any). Depending on whether you have highlighted a User or a Group, this button brings up another screen that shows the groups or users associated with highlighted user or group. Click to remove the highlighted User or Group from the list of available accounts. You can not delete if the user has active backup sets. (Note: the user or group will return to the list if the user logs on to the DS-Client again). Allows you to apply or change an online limit to the highlighted user or group. This brings up the Max Online for '...' Dialog Box.
Validation Wizard - Set Validation Settings

Use this screen to enter the Encryption Key(s) for a demand validation.
Encryption Key Private Key Account Key Selections All online data Selective Select to validate all online data of the selected backup set. Select to choose specific items to validate. Enter the DS-Client Private Key. Enter the Customer Account Key (if this has been set).


Confidential.
Verify Encryption Key

Use this screen to enter the Encryption Key(s) in order to configure this Backup Schedule to run a Validation Process.
Encryption Key Private Key Account Key Enter the DS-Client Private Key. Enter the Customer Account Key (if this has been set).
View Quotas
This screen shows if, and what the storage quota(s) are for your Customer Account, and for this DSClient. This information is view-only (configured by your Service Provider from the DS-System side).
Customer Storage Quota Quota Shows the amount (number in MB or GB). This is the total storage quota for all DS-Clients (including this one) of this customer account. Based on Protected Size (Size of the files as they were backed up. This counts the original file size of each generation of a file backed up.) Based on Stored Size (Size on the DS-System) Based on Native Size ('Restorable' Size of the backed up data, including files deleted from source. This only counts the original size of the latest generation of all backed up files.) Storage amount at which the DS-System will stop all backups for this customer. E-Mail will be sent for each checked event, if it occurs. You must tell your Service Provider which E-Mail address in advance. Warning Level 1 Warning Level 2 Warning Level 3 Stop Backup level Quota used (number and percentage) Shows if there is a quota, and the amount (number in MB or GB). This is the total storage quota for all backup sets on this DS-Client. Based on Protected Size (Size of the files as they were backed up. This counts the original file size of each generation of a file backed up.) Based on Stored Size (Size on the DS-System) Based on Native Size ('Restorable' Size of the backed up data, including files deleted from source. This only counts the original size of the latest generation of all backed up files.) Storage amount at which the DS-System will stop all backups for this DS-Client. Warning Level 1 Warning Level 2 Warning Level 3 Stop Backup level Quota used (number and percentage) Shows if there is a quota, and the amount (number in GB). This is the total storage quota for all Local-Only backup sets on this DS-Client.
Calculation method
Stop Backup level
Send E-Mail when the following are reached
Used Quota
DS-Client Storage Quota Quota
Calculation method
Stop Backup level Send E-Mail when the following are reached Used Quota
DS-Client Local-Only Storage Quota Quota


Confidential.
Calculation method
Used Quota
Based on Protected Size (Size of the files as they were backed up. This counts the original file size of each generation of a file backed up.) Based on Stored Size (Size in the Local-Only storage) Based on Native Size ('Restorable' Size of the backed up data, including files deleted from source. This only counts the original size of the latest generation of all backed up files.) Quota used (number and percentage) Shows how many licenses have been allocated to this DS-Client. If the used amount reaches or exceeds this number, you must ask your Service Provider to increase the pool for this DS-Client. Total number of Virtual Machines using Local DS-VDR. This is a counter that increases each time a Local DS-VDR backup set is used to export a Virtual Machine. (Each VM counts as one license, against the allocted pool for this DS-Client.)
DS-Client Local DS-VDR License Total Pool
Used
Weekly Admin Options screen

The Weekly Admin Options screen appears when you run Weekly Admin on demand.
If selected, this Weekly Admin will force a synchronization of all backup sets. This will increase the amount of time it takes to complete the Weekly Admin. If not selected, this Weekly Admin will skip synchronizing backup sets, as long as no database inconsistencies are detected. A number between 1-8 (default is 1). This is the maximum number of simultaneous synchronizations that will run (if synchronizations are required). Note: This number is also limited by the maximum concurrent activities supported by Number of DS-Client configured from the DS-Client Configuration Advanced Tab screen (Setup Menu simultaneous > Configuration > Advanced). synchronizations For Windows DS-Clients, the parameter name is "MaxSessions", and is found in the "Performance" category. For UNIX DS-Clients, the parameter name is "MaxSession Number". Synchronize all sets


Confidential.

Asigra Dsuser Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Asigra Dsuser Guide

Hochgeladen von

Copyright:

Verfügbare Formate

DS-Client User Guide

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 1

About Asigra Cloud Backup

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 2

DS-Client User Guide Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Running DS-User and Connecting to a DS-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Initial DS-Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 - Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Generated on: 10/15/12 Page: 3

3 - Schedules and Retention Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4 - Creating and Modifying Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

112 112 112 113 113 113

Generated on: 10/15/12 Page: 4

Generated on: 10/15/12 Page: 5

Generated on: 10/15/12 Page: 6

Generated on: 10/15/12 Page: 7

172 172 172 173 173 174 174

5 - Backup Set Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

6 - Working with Backup Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

7 - Deleting Backup Sets and Online Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

8 - Demand Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Generated on: 10/15/12 Page: 8

Initial Backup (Premium Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

9 - Restoring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Restore Oracle Server Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Generated on: 10/15/12 Page: 9

Generated on: 10/15/12 Page: 10

Cloud database upload tool (Salesforce.com) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

10 - Premium Backup and Recovery Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Generated on: 10/15/12 Page: 11

11 - Logs and System Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Online File Summary Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Generated on: 10/15/12 Page: 12

Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

DS-Client Knowledge Base Contents . . . . . . . . . . . . . . . . . . . . . . . . . 403

Generated on: 10/15/12 Page: 13

Knowledge Base: SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Knowledge Base: SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Knowledge Base: ADMINISTRATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Generated on: 10/15/12 Page: 14

Knowledge Base: BACKUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

Generated on: 10/15/12 Page: 15

Generated on: 10/15/12 Page: 16

Knowledge Base: RESTORE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686

Knowledge Base: RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

DS-User F1 Help for GUI (Context-Sensitive) Contents . . . . . . . . . . 735

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 17

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 18

Document Revision History Table

v12.0 [Revision Date: October 15, 2012]

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 19

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 20

What Is Asigra Cloud Backup?

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 21

How It Works: Major Asigra Cloud Backup Components

DS-Client User Guide v12.0 [Revision Date: October 15, 2012]

Generated on: 10/15/12 Page: 22