MBS Windows Agent Console 6.82 Operations Guide

Transcription

1 MBS Windows Agent Console 6.82 Operations 10

2 Agent Console Introduction and Overview Agent Console Introduction and Overview The Agent Console program provides a centralized point of control for managing backups and restores for computers on small or large networks. The Agent Console application can remotely configure, monitor and manage all backup and restore activities for a Vault). Backups can be configured to copy only selected files, databases, or a complete system, to a remote Vault via a local network (intranet) or the Internet (as well as to local tape or dis k). Backups can occur on a regularly scheduled basis, or they can be run immediately (unscheduled, or "ad hoc"). All backup and restore functions are monitored and recorded in log files. Users can also be notified via if a backup succeeds or fails. What s New in Windows Central Control 6.82? Support for Exchange 2010 MAPI. Support for version 6.82 Agents and Plug-Ins on Windows. Overview of the Product Set This diagram shows the relations between the various products. Page 1

3 Agent Console Introduction and Overview Overview of this Operations This manual is for the customer/user responsible for installing, configuring and using the Agent and Agent Console software (and any applicable Plug-Ins). The chapters in the manual cover the following topics: Installing the main Agent Console software (GUI). Using the Agent Console GUI Workspace, Agents, Agent Configurations, Jobs, backups, Catalogs and Log files. Performing Backups Types, Seeding, Network UNC Shares and databases, Options, Retentions, Notification, Expiration, Scheduling and ad-hoc backups. Report Logs Creating and Managing Log files. Data Security User Authentication and Encryption. Open File Backup Shared files: VSS, OTM and OFM. Troubleshooting and Command-Line Interface (CLI). The Agents and Plug-Ins have separate User s. They provide more details than this Operations. Release Notes Release notes contain up to the minute information about the released product. They also provide an overview of new features, any known defect (bug) fixes incorporated since the last release, a description of any known issues, and a section on product support. Release notes are availa ble from your service provider. Online Help The Agent Console application (GUI) provides online help, which contains information similar to this manual. Access the help from the main pull-down menu, or through the F1 key. There is also context-sensitive What s This help on each GUI screen. If you click the question mark icon on the GUI screen, the mouse pointer turns into a question mark. Move this over the area/field for which you want help, and click there. A pop-up message will show a brief description of the area/field. Note: If the F1 help screen is open (even minimized), the What s This help will not be active. The F1 help must be closed for the What s This help to function properly. Page 2

4 Agent Console Introduction and Overview How the Agent Console Works The Vault, Agent Console, and Agents comprise a data protection software suite that securely backs up and restores file data from servers across a network to a remote data Vault. The applications provide an automated lights-out method for protecting your valuable computer data without the need for tape devices or other local backup media. The Agent User s explains how to install, configure and manage the Agents installed on individual computers (Windows, NetWare, Linux/Unix, and their Plug-Ins). It also covers how to do an Agent configuration, and then a typical Backup and Restore. This Agent Console Operations explains how to use the Agent Console GUI application to configure Backups from those computers running the Agent software. The Operations has more detail and background than the User s s, and better describes the how and why of the Backup/Restore process. Agent Console Software The Agent Console provides a centralized point of control for managing all computers running the Agent software on a large computer network. Generally within an organization, the configuration of Backup and Restore Jobs, and scheduling of Backups is done through the computer running the Agent Console software. The Agent Console software connects to an organization s computers running the Agent software, configuring that computer s Backup Job. The Agent Console only communicates with the Agent. The Agent sends its backup data to the Vault. No user data goes through the Agent Console. Agent Software The Agent software runs on the individual computers (Win dows, Linux, Unix and NetWare) to be backed up. Backups and Restores on the Agent computers are configured and scheduled through the Agent Console computer. The Agent communicates its Backup data directly to the Vault. Each Agent consists of the following two components: The VVAgent part does the scheduling and communication with the Agent Console. Depending on the type of operating system, it runs [continuously] in the background as a Windows Service, a NetWare NLM, or a Unix daemon. The VV part performs the actual Backup and Restore functions. It is started and stopped by the VVAgent process. Note: See the appropriate release notes for the currently supported versions of the Agents and Operating Systems. Note: The following products are not part of the Agent Console, and require an extra license. They are only mentioned here for completeness. See the appropriate user manuals for more information. Agent and Plug-In Software The following Plug-Ins are briefly described here, but are not shown on the Product Set Overview diagram. Page 3

5 Agent Console Introduction and Overview The Windows platform can optionally have: Exchange Plug-In; Oracle Plug-In; MS SQL Plug-In; Cluster Plug-In, and SharePoint Plug-In. Unix (Solaris and Linux) can only have the Oracle Plug- In. Note: See the appropriate release notes for the currently supported versions of the Agents, Plug- Ins, and Operating Systems. Exchange Plug-In The Exchange Plug-In is an add-on to the Windows Agent. It allows for full disaster recovery capabilities on Microsoft Exchange databases as well as for backing up and restoring individual mailboxes and folders (with MAPI). Exchange 2007 can now be backed up with a 64-bit Agent using VSS (Volume Shadow Copy Services). This applies to new Jobs created with VSS only. Previously existing DR Jobs are not upgraded to use VSS. The Exchange 2010 DR Plug-In supports DAG (Database Availability Groups) and DR only of Mounted/Healthy 2010 databases. The Exchange 2010 DR Plug-In will only support Backup and Restore with version 6.0 and above of the Director. It requires Windows Agent Console version Support for Exchange 2010 MAPI. This Exchange 2010 DR Plug-In release does not support Exchange 2007 or Exchange Oracle Plug-In The Oracle Plug-In is an add-on to the Windows, Solaris or Linux Agent. It allows a user to perform a database Backup on an Oracle database. The Plug-In is installed on top of the Agent on the database host to perform the Backups. The Oracle Plug-In for Windows is installed via the Server Agent installation kit. It will appear as a new option in the Select Plug-Ins to install page. The Server Agent kit does not contain the Oracle Instant Client required by the Oracle Plug-In for Windows. The Oracle Instant Client will be made available through a separate kit. The Server Agent kit, however, will detect when the Oracle Instant Client has not been installed, and direct the user to the appropriate installation kit. The Oracle Instant Client kit, created with InstallShield, is dedicated to installing Oracle s Instant Client. The kit will only install the Oracle Instant Client into the installation directory of the Server Agent. If the Agent has not already been installed, the installation will terminate gracefully. The Oracle Plug-In provides ARCHIVELOG-based backups of whole online database instances. All non-temporary tablespaces and instance parameter files are automatically backed up. The database to be backed up must run on a single host. The Agent and the Oracle Plug-In must be together on the same system running Oracle. Full and partial databases are restored through normal user- managed Oracle recovery mechanisms. MS SQL Server Plug-In The MS SQL Server Plug-In is an add-on to the Windows Agent. It allows a user to perform a database Backup on an MS SQL Server database. The Plug-In is installed on top of the Agent on the database host to perform the Backups. Page 4

6 Agent Console Introduction and Overview Upgrades of earlier Plug-In versions are supported, and do not require any reconfiguration and/or reseeding of existing data. Cluster Plug-In The Cluster Plug-In supports clustering on Windows systems. Vault Backup Agent (VBA) The Vault Backup Agent (VBA) allows a user to perform a full or partial Vault backup. The backup may be to another Vault, or a disk or tape device, or a Tape Library. (Note: Only VBA s before version 6.72 (i.e.: version 5.63) managed with a Agent Console before version 6.72 can backup to tape drives.) VBA is installed on a Vault, and managed the same as other Agents, through the Agent Console. Note: VSS is not supported for VBA Agent for VMware ESX Server The Agent for VMware ESX Server is installed in the Server Console on individual VMware ESX 3.0/3.5 or vsphere 4 servers. The Agent can quiesce the Virtual disks of a running Virtual machine, back up the Virtual machine, and restore the Virtual disks to normal running mode. See the Software Agent for VMware ESX Server User for more information. Note: Older versions of VMware Agents required a VMware Plug-In. These versions are still supported. MS SharePoint 2003/2007 Plug-In The SharePoint Plug-In enables brick-level backups and restores of SharePoint items such as webs, lists, libraries, folders and documents. This high level of granularity enables backups and restores of the entire site, down to different individual document versions. You can also restore a document as a document or a document version to the file system. The SharePoint Plug-In, on a restore, allows browsing and selection to the file level. You can also search for a file to restore. The MS SharePoint Server Plug-In with the Agent installs directly on the Server hardware. See the MS SharePoint Plug-In User for more information. Overview of System Restore System Restore is a separate application used for bare metal recovery of systems in case of a disaster. System Restore does not include a backup Agent to create system backups. It relies on Agent 6.x to create a system backup as a part of the 'BMR' type Job. At the time of Restore, the System Restore should be used to connect to BMR type backups (safeset) to initiate a System Restore. System Restore enables seamless recovery to a similar, dissimilar or a virtual machine. This type of recovery is described as Bare Metal Restore (BMR). Page 5

7 Agent Console Introduction and Overview Note that for full BMR type restores, ESR software version 1.1 (or greater) is required. The Windows Agent with BMR is installed the same as a regular Windows Agent. A version 6.03 (or later) Vault is required to supply the licensing for BMR, for use with System Restore. The Agent will only check the Vault for a System Restore license when starting a Backup. No checking will occur during either the creation or modification of a Job. A BMR type Backup is done through the regular Agent Console application, similar to other Backup Jobs. A System Restore cannot be done from the Agent Console application. Note: Files and folders contained within a BMR type backup safeset can be restored with Windows or Web Agent Console in the same manner as a regular backup safeset. Selections can be made from a BMR type backup safeset and a restore Job can be run. This is not the same function as performing a Bare Metal Restore by the System Restore application for a complete system recovery. The System Restore application enables bare metal recovery. This is made available as an ISO or WIM image, and it is the customer s responsibility to create a bootable image by either burning the ISO image to a CD/DVD, or copying it to a bootable USB device. To enable network starts, you are required to download the WIM Image and follow the Microsoft instructions to create a PXE server for network starts. The System Restore will allow you to browse to the Vault, select BMR-style safesets, and retrieve one or more volumes from the selected safeset. Backup Options: Bare Metal Restore is an option that captures the information necessary for the System Restore. The Bare Metal Restore option is mutually exclusive of the existing System State option. Selecting one will disable the other. When the Bare Metal Restore choice is selected, you are presented with the list of volumes that contain System State information. You are not able to select volumes from this list. They are for visual feedback only. The list will be automatically included with the backup. By default, as well as system information, the BMR Backup will also perform regular file and folder backup/restores of the entire disk (except for any TEMP folders or files, and any folders or files (on non system disks) specifically excluded by the user). Although VSS is enabled by default, you should make sure that it is enabled for these types of Jobs. Backup Selections: For inclusion, the Agent Console will only allow the user to browse and select volumes under the Local System. The volumes containing System State information will be automatically included. You are not required to manually select these volumes. You have the option to include additional data volumes with the backup. Any data volumes included will also be backed up using VSS snapshot technology. For exclusion, the Agent Console will allow the exclusion of files and folders with some restrictions. If a volume contains System State information, the Agent Console will not allow you to exclude the volume. During backup, any file and/or folder exclusion will be overridden if the excluded item is required by System State. Backup Example: Page 6

8 Agent Console Introduction and Overview When you create a Job, you must select Local Drive only in Backup Source Type, to be able to use the Bare Metal Restore field. In the next screen, Source you can select the Bare Metal Restore checkbox. If you do this, the buttons below Bare Metal Restore (System State, RSM Database, Event Logs and Terminal Services) become grayed out and unavailable. The Data Files selection (above Bare Metal Restore) is still available. If you select Bare Metal Restore, it will back up the entire system volume. This includes the system information as well as all data (except certain unnecessary temp files). If you also click on Data Files you will be able to include in the backup other data files from other volumes. You can also choose to not select (that is, to un-select ) data files from the System Volume. Note that if these are required for the System Restore, they will be backed up anyway, regardless of your choices. Restore Selections: There are no BMR-specific options for restore. The options are identical to those of a regular local system backup without System State. (See the System Restore User.) The Recovery Application will also fix/upgrade the Registry, if necessary, on the newly Recovered system, since the hardware (e.g. disk size) might be different from the original. Migrating an existing Job to a BMR style Job: The Agent Console will allow an existing Local System Job to be changed into a BMR-style Job. When the option is selected the following options will be disabled: The System State option will be ignored. The RSM Database option will be ignored. The Event Logs option will be ignored. The Terminal Services Licenses option will be ignored. This option will not alter any of the existing Job file selections. However, a file exclusion that affects BMR-style System State files will be ignored. Also, when the BMR option is selected, the Job will consume a System Restore license on the Vault when the Job is saved. If there are no BMR licenses on the Vault, the Agent Console will post a warning but the Job will still be saved. Turning off the BMR option will not release the BMR license on the Vault. Page 7

9 Agent Console Introduction and Overview Overview of Licensing Vaults (versions 5.53 and above) implement licensing via a quota system. Agent licenses are used (consumed) by Agents during registration. When an Agent connects to a Vault, the license is automatically supplied from the Vault. The Agent Console does not require a license. Note: If an Agent registers to a Vault and license quotas are exceeded on the Vault, backups for that new Agent will fail to complete. This will not affect previously licensed Agents. Additional licenses can be acquired and applied to the quota. Contact your service provider for further details. Licenses are required for these software products: Windows Agents Desktop Agents Agent Linux Agent AIX-IBM Agent IBM i Agent HP-UX Agent Sun Solaris Agent Novell NetWare Agent Vault Backup Agent for VMware ESX Server Exchange Plug-In MS SQL Server Plug-In MS SharePoint Plug-In MS Cluster Support Plug-In Oracle Plug-In for Linux Oracle Plug-In for Solaris Oracle Plug-In for Windows System Restore ArcWare OFM/OTM License Behavior: Depending on your licenses, there may be warnings or some functionality may be disallow ed. The conditions for Warnings and Disallowing include: Page 8

10 Agent Console Introduction and Overview Vault storage limit exceeded, Vault limit for Agent type exceeded, Vault limit for Plug-In type exceeded, Customer Quota for Plug-In type exceeded (Agent 5.6 and above only). Agents may be either pre-version 5.6, or 5.6 and later: Depending on the license conditions encountered you may be: Allowed/Disallowed on Job creation, Allowed/Disallowed on Backups, Allowed/Disallowed on Restores. There may also be Warning Messages. Warning and Disallowed messages are displayed in the Agent Console and Agent Logs. Agent Licensing This table displays the tasks you can perform on the Vault when an error or warning message appears: Agent (pre-5.6) If Vault base license is invalid If Vault storage limit is exceeded If Vault limit for Agent type is exceeded If Vault limit for plug-in type is exceeded Registration Allow Allow Allow Client Key N/A Job Creation Disallow Allow Disallow Client Key N/A Backup Allow Allow N/A Client Key N/A Restore Disallow Disallow N/A Client Key N/A Agent (5.6 and above) If customer quota for plug-in type is exceeded Registration Allow Allow Allow Allow Allow Job Creation Disallow Allow Warn Warn Warn Backup Disallow* Allow Disallow* Disallow* Disallow* Restore Disallow Disallow Disallow* Disallow* Disallow* System I (pre- 5.6) Registration Allow Allow Client Key N/A N/A Job Creation Disallow Allow Disallow N/A N/A Backup Allow Allow N/A N/A N/A Restore Disallow Disallow N/A N/A N/A Figure 1. - License Behavior for Agents * If the Agent already has a claim on the necessary licenses (it has previously done a Backup of that type), the backup or restore operation is allowed. Page 9

11 Agent Console Introduction and Overview Client Key refers to the older license key that was installed on the Agent. The Vault did not see or use this key. Scenarios If an end user can successfully register an Agent to a Vault, then that Agent will be able to perform Backups and Restores. Successful registration means that the Vault accepts the Agent s credentials and can supply the licenses that the Agent needs. After this, it is up to the Vault Administration to ensure that Vault disk space and quotas are available for all properly licensed users. Quotas restrict Customers to some configurable amount of disk space and number of licenses (by the Vault). So, even though there may be more licenses and disk space available on the entire Vault, individual Customers can be restricted to a limited amount. If an end user is rejected because of license or space restrictions, it is up to the user ( Customer ) to acquire more licenses. A Vault Administrator may disable a User s account, for example, for Accounting problems. This will stop the user from accessing the Vault even though they have previously Registered and performed Backups and Restores. Note: Job Registration is always allowed. Backups will fail if the licenses are not present, or are insufficient (exceeded). If an Agent already has a claim on the necessary licenses (it has previously done a Backup of that type), the operation (Backup or Restore) will be allowed. Overview of the Agent Console This section provides an overview of all the components of the Agent Console application. It describes what each piece does and how and where to use it, to perform Backup a nd Restore Jobs on the Agent. Readers for this Overview section may include people who are new to the Agent Console application or those who may not regularly use the application but need to know more about what it is, and how to use it. This Operations also describes the details of each Wizard, screen, function, selection, and option. Installation of the Agent Console application is covered in Chapter 8 of this manual. Installation of the Agent software for Windows, Unix, and NetWare is covered in the appropriate Agent User s. The Agent Console application can be launched in several different ways: Double-click on the desktop icon (shortcut) created during installation. From the Start menu, select: Programs/Agent Console Software/Agent Console Software Agent Console Page 10

12 Agent Console Introduction and Overview Method 3: Find the folder where your Agent Console application was installed. The default location is Program Files/Agent Console Software. Locate the application file called VVAdmin.exe and double-click it. The Agent Console application launches. Wizards A Wizard is a user-friendly program, or set of screens that the user can navigate through and set parameters to accomplish a Job. If you do not perform some functions very often, a Wizard will take you through the steps, ask you questions, and give you choices about performing that Job or function. At any point in the Wizard you may go Back to change something, or Cancel to get out of the Wizard without changing anything. All Wizards come with a Welcome Screen (Welcome to the <name> Wizard) which tells you what the Wizard does before you actually start. There is a checkbox on these screens, labeled Skip this screen in the future. If you select this checkbox, the next time you launch this Wizard, the welcome screen will be skipped. You will notice that the second screen has the < Back button enabled. This will allow you to go back one step to the Welcome screen should you want to re-enable the Welcome screen. Page 11

13 Agent Console Introduction and Overview Overview of Wizards Most of the functionality of the Agent Console is controlled through Wizards. These are workflow applications that take you through a set of questions and responses, before running (executing) the result. You may change your mind and quit while inside the Wizard, before the end, without causing any changes. Options and Parameters are typically entered in separate screens, chosen by choices in the pulldown menus of the GUI. Wizards are usually started from a GUI menu choice, but sometimes they may be called from inside another Wizard, or from a utility screen. Wizards use the same screens (Options and Parameters) that c an be accessed throughout the Agent Console GUI. So you can perform the same functions as the Wizard, by doing the steps manually. All the Wizard gives you is an organization to the function that you want to perform, by asking questions and giving choices. The following list (in alphabetical order) briefly describes the Wizards that are available throughout the Agent Console. Their functionality is described in more detail in various other sections of the, and the online Help. Backup Wizard allows you to run an ad-hoc backup of an existing job. New/Edit Job Wizard allows you to go through the steps to create a new Backup Job. These steps include: Job name; Vault profile; Backup type; choose the files/data to backup; set options; set encryption type; configure the logs. Import Job Wizard import a Job backed up by another computer so you will be able to restore data. Restore Wizard restores a backup to the original, or a different, location. The steps include: Select a Source; Enter the password (if encrypted); Select the Restore files; Enter the Restore Destination; Select other Restore options. Retention Wizard Choose: Retention information: Name of the retention; Retention days and copies; Archive retention days. Schedule Wizard Choose: Command Cycle (Weekly, Monthly, Custom); Command to schedule ( Backup, Synchronize, Custom); Select the Job to schedule. Vault Configuration Wizard Choose: Vault machine name; Vault network address; Authentication information; Connection information. Page 12

14 Agent Console Introduction and Overview Vaults A Vault is a computer system that receives a user s Backup data from a LAN or the Internet and securely stores the data on disk. Workspace A workspace is a uniquely named, user-defined environment in which specific computers running the Agent software are represented, defined, and where Jobs (for Backup and Restore) are created for those Agents. Agents The Agent is an application that runs on the host system as a local component service. The Agent scans that Server for changed data and delivers those changes to a remote electronic Vault. Changes are then added to the Backup on the Vault to complete a full Backup of the Server. You can manage and control many Agents through one Agent Console application. An Agent may have many Jobs shown in the Agent Console screen. Agent names must be unique within a Agent Console workspace. Jobs A Job defines the parameters associated with a Backup, Restore, or another command. Examples include: file selections, filters, compression, and encryption settings. A Job always belongs to only one Agent. Job names are unique on that Agent. Safesets / Backups Each time a Backup command is successfully performed, a safeset is sent to the Vault. The safeset contains the data protected in that backup session. The safeset also carries the associated Backup type, data options, and retention settings. This information is used to help manage the safeset until it (optionally) expires. The list of safesets is maintained on the Vault (if this is the destination) as well as on the Agent. Over time, a pool of safesets will develop based on the values specified in the retention settings. This safeset pool makes up the Backup history for a specific Job. The safeset pool, when stored on a Vault, is very dynamic in nature. For instance, each time a new Backup is performed o r a safeset expires, the pool changes. Typically, this happens automatically after each Backup is performed. On occasion, such as before a Restore, this information may require synchronization with the local Agent. Depending on the destination of your Backup, you may or may not see the safeset file locally. Each Backup operation creates a safeset image (*.ssi) into which the contents of selected disk files, directories or volumes are placed. The contents reflect the Job settings for the Backup operation. The Backup process creates a safeset file called XXXXXXXX.ssi, where X represents the Backup number. The safeset for the first Backup is named ssi. This number inc rements after each Backup of the Job. Page 13

15 Agent Console Introduction and Overview Should you need to reconstruct data that has been accidentally deleted or corrupted, you can perform a Restore. Each Restore operation reads the Backup image and places the contents of selected safeset files, directories, or volumes back to their original (or alternate if you choose) locations on disk. Safeset Catalog Format Safeset catalog information is displayed in the Safesets folder under the Job name. The following information is displayed for each safeset: Backup Age (greater than one year; greater than three months; or new). The Safeset number (SSI). The date and time of the Backup (shown with GMT offset). The type of Backup (e.g. Full, or Delta). The status of the Safeset (e.g. Online or Offline). The specific location of the safeset (e.g. the address of the Vault) Safeset Catalog Properties To view the Safeset properties, double-click on the desired catalog number in the Safeset folder (or use the right-click, or F2). The Safeset Properties window opens. The following information is displayed for each safeset catalog: Job - The name of the Job that created this safeset. Catalog Number - The number (1,2,3, etc.) of the catalog. Location - The place (e.g.: Vault name or IP address) where the safeset is stored. Status - The current storage type (e.g.: online). Backup Time - The date and time the Backup was created. This is the local time of the Agent/Server, not the Vault s time. Storage Size - The size of the Backup in its original, deltized and compressed forms. Backup Type - The type of the Backup (e.g. Full). Retention - The retention settings based on days online, copies online and days archived. Encrypted - A yes or no value indicating whether or not the Backup was encrypted. Compressed - A yes or no value indicating whether or not the Backup was compressed. Media Type - The media used (e.g.: disk). Tape Label - The tape label. This is blank if the Backup was not to tape. Expiry - The user-defined date that the safeset expires. Page 14

16 Agent Console Introduction and Overview Security Data security can be applied by the user (or system) in several places: In versions 4.x and above, all data going to/from the Agent and Vault is encrypted by the system. You can choose to turn off this Over The Wire (OTW) encryption, if you are inside a secure network. A user may choose to encrypt the workspace to prevent unauthorized access. A user may choose to encrypt the data that is stored on the Vault. Agent Console Passwords Agent Properties The Agent password is used to connect for configuration and authentication information. See section in this. This allows the Agent Console to access the Agent machine to be able to communic ate with the Agent Jobs there. This is a Windows authentication. Vault Password. Used by an Agent Job to execute backups and restores. Created by the Vault Operator and given to the user. If the user loses/forgets the password, the Vault operator can issue a new one. This connection is an application authentication, as opposed to a Windows authentication. There can be many different users with different passwords, in the same Vault Account. Workspace password protects all the other passwords and access to user information on the Agent Console. It is set on Workspaces in the Agent Console GUI application. See section 2.4 in this. If the password is lost, the user must recreate the workspace and settings. Encryption password secures the data stored on a Vault. The password is not stored on the Agent Console or the Vault. It must be remembered and recorded by the user. See Section in this. File-Lock and Open File Management Utilities Note: Agents 6.70 or greater use VSS (Volume Shadow Copy Services) by default for open file management. The following descriptions of OTM and OFM products are applicable to Agents 6.61 and older. OTM can still be used with older Jobs or in a custom manner, but are not used by default. Open Transaction Manager (OTM ) from Columbia Data Products and Open File Manager (OFM ) utilities allow backups to read any files that may be open and in use during the backup process. Typically, OTM is used on small to medium size d servers, while OFM is used on large servers. See section Open Files in this for more information. For Agents 6.6x and lower, if you have installed Open Transaction Manager (OTM) or Open File Manager (OFM), you can configure the software through the Open File tab (in Agent Configuration). Note: Agent Console installation directories (and any anti-virus directories, as well) should be excluded from open file protection. Do not back these up using OTM/OFM file-lock management utilities. Page 15

17 Agent Console Introduction and Overview Encryption You can choose whether or not to encrypt your data. One of the following encryption types may be selected: None 56-bit Data Encryption Standard (DES) 56-bit Blowfish 112-bit Triple DES 128-bit Blowfish 128-bit Advanced Encryption Standard (AES)* 256-bit AES* *128 bit AES is available when connecting to version 4.x and above Agents, Agent Consoles, and Vaults. 256 bit AES is only available on 5.30 and above. Optionally, choose one of these methods to secure your data while it is being transported and stored on the remote Vault. If you choose to encrypt your data, you need to select an encryption password. When making your selection, keep in mind that the password is not maintained anywhere else. Note: Losing the password means you cannot recover your data! The restoration of files requires you to remember the encryption password that was entered when the files were backed up. Note that the password is case sensitive. Choosing to encrypt your data means that all backup safesets for that Job will be encrypted with that encryption password, from this point forward. If you change the encryption options (in Job Properties) it will force a new full backup. The next backup session will take longer than previous delta backups, and will increase the amount of data stored on the Vault. Page 16

18 Agent Console Introduction and Overview Seeding Seeding the Backup is a phrase used to describe the process of getting the initial full copy of the data to the Vault. After the Vault has received an initial full copy, the built-in Delta processing technology will reduce the subsequent Backup traffic so that further Backup procedures will be completed in a shorter period of time, and use less disk space on the Vault. Note that each subsequent backup is still considered a full backup. Seeding the First Backup There are two techniques for establishing the initial seed of data to the Vault. The first technique is to perform a Full Backup over the Internet or a local network, within a framework established by your Backup Time Window. The second is called Removable Media Seeding. Each technique has its pros and cons. You will determine the best approach for your system based on available resources, communications bandwidth and scheduling requirements. Creating a Seed Using the Backup Time Window Option This method of seeding your Backup is to perform a Full Backup after you have set the Backup Time Window. This setting is used to maintain a suitable time window in which the Backup must be completed. Any files that are not backed up within the specified Backup window will be deferred until the next Backup. This window can be used to help a Full Backup grow over a period of days. When setting up your Backup, you need to establish your time window. Using the Job Wizard, you set the time window from the Options dialog. After your Job has been created, you can edit this option on the Advanced tab (in Job Properties). Enter the number of hours or minutes after which all new Backup files will be deferred. For instance, trying to back up 5 GB of data over a 128 Kb ISDN connection could take 40 hours. By setting a Backup Time Window of 9 hours, you can spread the growth of the Backup over a period of about a week. The time window you choose is important, and the number of minutes must be larger than the time required to perform the Full Backup of the 5GB of data. After the Backup has been executed a few times, you can look at the log file summary to determine if your Backup time window is sufficient to complete a typical Full Backup with the Delta processing option. This technique has the advantage that you do not permanently need removable media connected to the Agent system. In addition, there is no need to transport media to your Vault, and thus you avoid a transportation charge. The disadvantage is that the seeding process can take several days to complete if your communication bandwidth is limited. During this time, you have only partia lly completed Backups that may or may not suffice in a crisis. In this case, it is recommended that you continue regular local disk Backups until your system is fully seeded. Page 17

19 Agent Console Introduction and Overview Removable Media Seeding If your communications bandwidth is limited, it may be faster to perform Removable Media Seeding. This is the process of creating your first full Backup to a disk, or other type of removable media. The media is then transported to the Vault where the Vault processes it and initializes your Backup data. Subsequent Backups can be performed over the network connection to the Vault directly. To create the seed: 1. Create your Backup Job as if you were to going to back up over the network directly to the Vault. 2. Before defining your Backup schedule, execute an ad hoc (immediate) Backup. 3. When the Backup Wizard starts, temporarily redirect your Backup by choosing the Directory on Disk as the target destination. This will not affect your permanent settings for the Job. Seeding with a Mobile Vault A specialized type of removable media seeding is called Mobile Vault. The following outlines the steps required for a customer to use a Mobile Vault to seed a main Vault. See the Vault Operations for a diagram of seeding, and more operational details. Briefly, the steps are: Step A: Vault responsibility: 1. The Mobile Vault should be initialized, to cleanse it of any previous seeding data. 2. Connect the Mobile Vault to the same network as the primary Vault. 3. Set up the profile. 4. Export the customer account info to the Mobile Vault. 5. Transport/send the Mobile Vault to the customer system. Step B: Customer responsibility: 1. Customer plugs the Mobile Vault into their local network. The Mobile Vault system should be assigned an IP address via the DHCP Server. 2. In the Agent Console > Agent Configuration > Vaults, edit the Server entry, and change the network address to either the Host Name or IP of the Mobile Vault. 3. Start the ad hoc Backup to the Mobile Vault. 4. When finished, transport/send the Mobile Vault back to the main Vault. Step C: Vault responsibility: 1. Change the network address back. 2. Import the Mobile Vault data into the main Vault. Page 18

20 Agent Console Introduction and Overview Report Logs The reporting logs provide you with important information. The information comes in the form of a log file, which contains various details about your Backups and Restores as well as process information. Creating and Managing Log Files For each Job executed, you can create a printable log file that contains the start-connectcompletion and disconnect times, file names (i.e., the names of all files that were copied during a Backup process), and any processing errors. Log files can be identified by relating the file name to the Job performed (e.g. Restore.log). However, the activities of a successful Backup Job will be recorded into a file called XXXXXXXX.xlog where X is the number of the Job. For example, the first Backup will generate a log file with the name xlog. Activities of failed Backup will be noted in the Backup.log. This log is useful for troubleshooting purposes. A successful Restore log file is renamed to RSTYYYYMMDD-HHMMSS.xlog. That is, with the date and time appended to the name, to make the log file unique. Note: Older Agents \will have.log as the file extension. Creating Log Files You can set your log file options when you are creating a Job. You can also modify these options from the Log tab (Job Properties). To create log files from the Job Wizard: 1. From the Log dialog on the Job Wizard, select Create Log File. 2. To preserve disk space, the application allows you to specify how much information is displayed in the log file. From the Log Detail Level drop-down list, choose the None, Files, Directories or Summary options to specify the amount of detail required in your log files. For example, the file level option would be used for a Restore, but the directories and/or summary options would be used for Backups. 3. Also, to preserve disk space the application allows you to specify the number of log files to save. Select Automatically Purge Expired Log Files Only to have all files saved. To specify a specific number of files to keep, enter a number in the Keep the last <X> Log Files textbox. 4. Click Next and complete the Job Wizard process. Note: For Restore Jobs performed through the Agents, a full format Restore log with file level logging is generated regardless of which log options are selected. Viewing Log Files With the Agent Console application, you can view log files by opening the Logs folder. Log folders are automatically created under each Job. Log files can be identified by relating the file name to the action performed. See the chart below. However, Backup log files are renamed to the number Page 19

21 Agent Console Introduction and Overview of the catalog created if the Backup was completed successfully (without serious error). If the Backup Job failed, it will not be renamed and will be called Backup.xlog. Double-click the log file to open for viewing. Job File Description Backup Backup.xlog Log of Backup Job. Renamed to <catnumber>.xlog upon Backup completion without errors. Restore Restore.xlog Log of Restore Job. Renamed to RSTYYYYMMDD-HHMMSS.xlog upon a successful restore. Synch synch.xlog Log of Synchronize Job. The default log viewer is called LogViewer. (See section 2.5.) It can display the logs in one of four languages. This is independent of which language was used for the Agent installation. Older Agents that do not use.xlog format cannot view log files in multiple languages. Service Log Files When the Windows Agent system runs a service, a VVAgent-#.XLOG file is created. The # (number) is replaced by the numbers 1 through 4, in rotation. They change over when they reach a certain (non-configurable) size. The remaining three older logs are kept for reference only. The logs, which are kept on the Agent computer in the Agent installation directory, contain service start and stop information, and any errors, such as being unable to start a scheduled backup. This means that there are a maximu m of four log files maintained called VVAgent -1.XLOG, VVAgent-2.XLOG, VVAgent-3.XLOG and VVAgent-4.XLOG. Each program will always append to these files until the log file reaches its maximu m size. At that point, it will write to the next higher number file. The old data there is removed. When the fourth file has been filled, the numbering returns to 1 again. The log files can be viewed from the right hand screen (click on one of the xlog files) when you select an Agent in the Agent Console. Overview of the GUI Menus The main (top level) menu structure in the Agent Console GUI is broken down into: File Edit View Tools Actions Help Page 20

22 Agent Console Introduction and Overview Below each of these are pull-down submenus with which the user can create workspaces, Agents, and Jobs, and perform Backups and Restores. Also, it is possible in many cases to access a short -cut menu by right-clicking on selected items to achieve the same choice as going back to the main pull-down menus. These will be described in this manual as alternate ways of performing a function. Frequently used icons are shown below the menu choices. These are short -cut duplicates of menu choices. Up One - Go up one level from where you are in the hierarchy tree. Refresh - Update the data on the screen (console). Delete - Remove the object that you have selected in the tree. Properties - Show parameters of the object that you have selected. Backup - Start a backup of the selected Job. Restore - Start a restore of the selected Job. Synchronize - Update the local Agent catalog information to the Vault. You must have the appropriate item (such as Agent, Job, safeset, and so forth) selected for these to become active (not grayed out). These icons cannot be created, deleted or modified by the user. But you can turn the toolbar display off or on, or move it around on the screen. See Sections and in this. Page 21

23 Agent Console Introduction and Overview File Menu The File menu contains commands used to manage the workspace. With a workspace highlighted, the available commands are as follows: Expand opens subdirectories. New Agent opens the Agent Properties Window from which you can create a new Agent. New Group creates a new grouping place for Agents. New Workspace creates a new workspace. Open Workspace opens an existing workspace. Save Workspace saves a workspace to its existing name. Save Workspace As saves a workspace to a specified name. Recent Workspaces lists workspaces most recently opened. Workspace Password sets the password and encryption type for a workspace. Exit exits the Agent Console program. With the exception of New Agent and New Group, all of the commands listed above are available when an Agent is highlighted. In addition, the following commands are available: Delete removes an Agent. New Job creates a new Job. Properties opens the Agent Properties window. When a Group is highlighted, additional commands are: Expand shows the Agents in a group. Delete Group removes an Agent group. Import Agents add multiple Agents through a csv file. Add/Delete Agents to a Group add or delete agents. Edit opens the Agent Group properties window. View Menu The View menu contains commands and options used to customize the display to accommodate your needs. These commands are listed below. Toolbar displays/hides the toolbar. Status Bar displays/hides the status bar. Use Single Click performs actions as a result of a single click, rather than a double-click. Refresh refreshes the display. Page 22

24 Agent Console Introduction and Overview Moving the Toolbar Menu The Toolbar can be grabbed by an edge, and moved around (dragged) to the top, bottom or either side of the Agent Console windows. Or it may be moved outside the GUI window. Page 23

25 Agent Console Introduction and Overview Tools Menu The Tools menu contains the following functions. These functions are also accessible from the Toolbar. Agent Configuration - settings include Vaults, Retentions, Open Files, Notification, Others (Windows priority, and bandwidth throttling), and Plug-Ins (optional). Schedule Entries summary list of currently scheduled entries. Lets you view or modify an entry. Options - includes Automatically Reload Last Workspace on Startup, Auto-Refresh Display for Selected Agent, Update Progress Display and Default Text Viewer Actions The Actions menu contains Backup, Restore, Restore from another computer, and Synchronize. Backup - Performs an immediate Backup. Restore - Restores files directly from a safeset for the currently active Job. Restore from another computer Allows you to import a Job backed up by another computer so you will be able to Restore data. Synchronize - Connects the current Job window to the remotely defined Vault, updates your local catalogs with Server information and then disconnects. Help Menu Help Topics is a Winhelp help system that provides extensive information regarding the Agent Console application. Search the help by table of contents, alphabetical index or Find. Note: Agent Console features Windows style What s This help. To see a What s This definition, right click on any field, textbox or button in the Agent Console application. Click the What s This button that appears and the definition pops up. Alternately, click on the? in the upper right corner of a window and then click on the field in question. If the F1 Help screen is open (even minimized) the What s This help will not be active. The F1 help must be closed for the What s This help to function properly. Getting Support displays a contact telephone number, address and Web page. Product s enables you to access PDF versions of the Agent Console, and Agent s. About displays the version and build number of the application currently operating on your system. Page 24

26 Working with Workspaces Working with Workspaces To get started after a new Agent Console installation, you must: Create (and optionally save) a Workspace ( MyWorkspace.vws is the default after installation), Create and configure the Agent, and Create a Job and configure its properties. After this, you can perform Backups and (subsequent) Restores. A workspace is a convenient means to organize your Backup environment into manageable pieces. You can create as many workspaces as necessary to represent logical groups in your network Backup environment. For example, a workspace might be created for each physical location or depart ment in a large company. Within each workspace, Agents and Jobs are created. Each of these organizes and defines various parameters of the Backup process. They manage the regular Backup activities within a network. Workspace files are given the file type.vws. By default, these files are saved in the installation directory (Program Files > <directory> Software). From File > Workspace, you can: Create a new workspace, Save a workspace, Open a new workspace, Put a password on a workspace. Creating a Workspace When you launch the Agent Console application for the first time, you immediately enter the default workspace MyWorkspace. We recommend you rename this workspace to something meaningful to you. To create another workspace: 1. Choose: File > New Workspace. 2. To name the workspace, choose File > Save Workspace As. Enter a name in the File Name textbox. 3. Click on Save. Once you have a workspace, you may wish to secure it by setting password restrictions. This will protect all of the other passwords (to Agents and Vaults) and access to user information on Agent Console. Renaming the Default Workspace To save and rename the default workspace: 1. Choose: File > Save Workspace As 2. Specify a new workspace name. Choose a name that has significance to you. Page 25

27 Working with Workspaces 3. Click on Save. The next time the Agent Console application is opened, your new default workspace appears. You can create as many workspaces as are required for your environment. Opening a Workspace File > Open Workspace takes you to the directory where the *.vws files are kept (usually the installation directory). File > Recent Workspaces shows you a list of the recent workspaces that you have created and used. You cannot delete a workspace from the Agent Console application itself. To remove a workspace, you must delete the workspace file (.vws) from the product directory. Workspace Password Workspaces often contain system names, user names, and privileged passwords that allow access to the remote Agents through the Agent Console application. Password protection can be imposed on the workspace through encryption of the workspace. Figure 2. - Set Password for Workspace To encrypt a workspace: 1. Choose File > Workspace Password. This opens the "Set Password for Workspace" textbox. 2. Choose an encryption type from the Encryption Type dropdown list. You may choose: None DES (56-bit) Blowfish (56-bit) TripleDES (112-bit) Page 26

28 Working with Workspaces Blowfish (128-bit) AES (128-bit) AES (256-bit) 3. Enter a password in the New Password textbox and confirm the password. If this is the first time that you are using a password on the workspace, leave the Old password field blank. If you are changing the existing password, you must enter the old (existing) password. 4. Click OK to set this password. You are prompted for this password each time you open the workspace. If you lose the password, you will have to recreate the workspace. Setting Workspace Options From the Tools > Options menu, you can set options for the workspace, as well as set other functions. Automatically Reload Last Workspace on Startup: Automatically loads your last saved workspace when you start the Agent Console application. If not set, you must select one manually. If there is a password on the workspace, it will prompt you for it on every startup. Auto- Refresh Display for Selected Agent every <#> minutes: This global value applies to all Agents, but only refreshes the one that is selected (highlight ed). It will be polled for changed information every <#> of minutes (an integer value from 60 to 1440), to refresh the screen display. You may also refresh the screen at any time with the Refresh button, or with the F5 function key. Update Progress Display every <#> seconds: Specifies the number of seconds (an integer from 5 to 10000), after which the Progress Monitor Display will poll the Agent for changed information. Return maximu m <#> of files and directories: Shows the maximum number of files and directories (from 10 to ) that will be returned at one time when you select to view them. This optimizes the system in cases w here there may be large directories, and you have to wait while the file names are read and displayed. If there are more returned than the number here, you will be prompted if you want to see them all. Page 27

29 Working with Workspaces Note: In the above three <#> fields do not use a separator, such as a decimal point, or comma in the fields. Default Text Viewer: This is the viewer that is used to show logs (XML based), and other text based files. The logs can be shown in one of four languages. Page 28

30 Working with Agents Working with Agents Within a Agent Console workspace, Agents representing individual computer systems are configured. The Agent program residing on a computer system enables configuration and status communication between the system and the Agent Console application. Later the Agent sends it backup data to the Vault, without interacting with Agent Console. Created through the Agent Console application, an Agent represents a specific computer running the Agent software. Before communication starts, the Agent program must be installed on each individual computer system to be managed by the Agent Console application. The Agent program runs as a Windows service, a NetWare NLM or a Unix daemon. It uses local authorization information to protect it from unauthorized access. To configure and manage an Agent system from the Agent Console application, you must connect with an account on the Agent system that is suitably privileged. Agent Access Privileges The different operating systems (Windows, NetWare, and Unix) have different access privileges. Windows Agent System This needs a user with Backup Operator or Administrator privileges (if run from the Scheduler, or Agent Console). To specify the domain property of the Agent, type its domain name in the Domain box. The domain can optionally be left blank if: a) you are not specifying a Windows Agent; b) you belong to the same domain as the Windows Agent system, or: c) your network does not utilize a domain controller. Vault Backup Agent (VBA) A VBA is an Agent that only resides on a Vault. It requires its own license, and it must be the only Agent on that machine. It can back up all or part of the Vault data to another Vault, or to a disk. (Note: Only earlier VBA versions such as 5.63 can backup to tape.) From Agent Console VBA looks and acts similar to a regular Windows Server Agent. The VBA program needs Network Credentials (user name and password) to run with "Local Administrator" rights on the Vault, to be able to access all data. There is a separate manual, "Vault Backup Agent - Installation and Configuration " for the VBA. NetWare Agent System NetWare requires: A user with the security equivalent to Administrator, A user with Administrator privileges, Page 29

31 Working with Agents A user with Supervisor rights to the [root] object of the NDS Tree. If the NetWare Server does not support Bindery emulation, the user name must be specified using the following format:.cn=commonname.ou=organizationalunit.o=organization For example, the user Smith located in the Accounting organizational unit at Acme organization would be entered as follows:.cn=smith.ou=accounting.o=acme Custom scheduling of NetWare NCF files using the NetWare Agent is disabled for NetWare only. Note: To perform an NDS Backup, a user name and password must be provided through Agent Console. In order to back up the whole NDS tree, Agent Console must have Supervisor rights to the root object of the tree. Unix Agent System The Unix Agent requires full root group (gid 0) access privileges to run. Installation and configuration require authentication by users with root group privileges. Installation with "su <command>" is not recommended. If the Agent is not run as the root user, the user that runs it must be part of the root group. The Agent Service account must also belong to this group. VMware ESX Server The Agent for VMware ESX Server requires full root group (gid 0) access privileges to run. Installation and configuration require authentication by users with root group privileges. Installation with "su <command>" is not recommended. If the Agent is not run as the root user, the user that runs it must be part of the root group. The Agent Service account must also belong to this group. Page 30

32 Working with Agents New Agent Either use File > New Agent, or, using the right mouse button, click on your workspace. Click on New Agent. The Agent Properties window opens. Agent Properties You get here from New Agent (above), or with an existing Agent selected, choose File > Properties, or Right Click on the Agent, or use F2. Agent Information Enter the Description (your name for the Agent), the Network Address, and a Port address. The Network Address must be a valid IP address, or a valid host name. The Default port (socket) for version 6.8 and above Agents is This is the port that Agent Console uses to communicate with the Agent. Older Agents will continue to use port 808. Agent Console will automatically try to connect to each Agent and use the correct port number, for that Agent version. If your system uses a different port number than these defaults, you can enter it here, as a Custom port. Note: The Agent uses another, separate (non-dynamic) port to communicate with the Vault. Page 31

33 Working with Agents Authentication Information Enter the User Name and Password (and optional Domain name for Windows Systems) to get access to the Agent system. Note that the password is case sensitive. To permanently save the user name and password entered in the Authentication information section to your workspace, select the Save Password checkbox. Saved passwords are stored in an encrypted format to help prevent unauthorized use of this information. Caution: if you decide to Save Passwords, any user who runs this program and opens your workspace file will have the ability to access the Agent systems through this program. You may want to protect the workspace with its own password. See the previous section on Workspaces. Get Status You may click Get Status after the Agent Information and Authentication data has been entered, to test if it is valid. This information is case sensitive. If the information is validated, your data is displayed in the Agent Status window. If the information is not validated, a message from the Agent Console application appears. Check your information and revise it as required. Once again, click Get Status. When configuring the Agent Console application to connect with a remote Agent, you need to specify a particular user name and password under this dialog. Note: If an authentication password changes (i.e. the user listed on the Agent Properties dialog changes his or her system password, and that is also the one that the Agent uses), then the Agent Properties dialog will have to be updated. Windows Cluster Support Microsoft provides Server Clustering Services (MSCS). Multi-node clusters can be configured using different combinations of Active and Passive nodes. When a node is Active, it is actively handling requests. When a node is Passive, it is idle, on standby waiting for another node to fail. From a GUI perspective, there is one Server for each physical node and also one Server in the GUI for each cluster Virtual Server. Virtual servers are marked with a different icon in the Agent Console GUI. Features: A user can connect to an Agent (with a Plug-In and proper license) on a Virtual Server or Local machine (a node) via IP or name. The Virtual Server Agent can backup Virtual Server shared data without re-seeding, or in case of a failover. Once created, Jobs (on a shared drive belonging to a Virtual Server) can be used by all Agents on the cluster. Scheduling of Virtual Server backups is handled between node Agents without schedule overlapping. The configuration files are located on the drive owned by the Virtual Server. Each physical node in a cluster configuration requires a separate installation of the Agent, each with a separate Cluster Plug-In and license. You also need to enter licenses for the Plug-Ins on the Virtual Server as well. Page 32

34 Working with Agents Agent Groups You can organize your Agents into groups. Normally, when you create (add) a single New Agent, you enter six pieces of information (not counting the Save Password checkbox): Description Network address Port User name Password Domain When you first create a group to logically hold Agent names, it is empty. Instead of adding the names individually, as if they were new, the Group function allows you to add a block of them using a csv (Comma Separated Value) text file that you create. See section Import Agents to a Group. Later you can propagate the Agent configuration (Vault registration, retention and notification), and Job and schedule configuration to all of the Agents in that group. Notes/Rules about Agents and Groups: The Agent must either exist first, to be moved into the Group, or be created by the Agent Import function in the Group. If you move an Agent (with Add/Delete Agents from Group) from the workspace to a group, it will still exist in the workspace. If you move an Agent from a Group to the workspace, it will move it if it does not exist there. If it does exist, the move is a non-event (that is, nothing happens). You may appear to have duplicate Agents in the workspace and/or a Group. These are only the Agent Information Description fields. The other information about network address, port, user name, password and domain must be unique. So, if you have two Agent configurations with the same name (Description) but different address, port, user or password, and you move one into or out of a group, it will overwrite the one with the same name. There is no prompt, and the information will be changed. You cannot move an Agent directly from one Group to another. You have to first move it to the workspace, then to the other Group. Deleting a Group only deletes the Agents in that Group, even if they are also duplicated in the workspace, or another group. If you delete Agents in the workspace, it does not affect any Agents in a Group. They will still be there, even if they are duplicates (copies). If you want to totally delete an Agent, you must delete it from the workspace and the Group (if it exists in both places). As in adding a New Agent manually, adding Agents into a group does not check the validity of network address, passwords, etc. Only when you do a Check Status or click on the Agent icon does it go out and try to connect to that Agent. Page 33

35 Working with Agents New Groups A new Group can be created from the drop-down menu command, when a Workspace is selected. Or it can be created by right clicking on the workspace. You will be prompted for a new Agent Group name. This can be up to 32 alphanumeric characters. The name is not case sensitive, but must be unique with respect to other Groups (with no leading or training blanks). It may be the same name as a single Agent in the workspace, or an Agent in another group. Page 34

36 Working with Agents The new Group appears in the left pane of Agent Console. From here, by right clicking on the Group name, you can expand the view of the group to see all the Agents listed. You can also delete the Group name only, without affecting any existing Agents. You can Refresh the list, if you have added or deleted Agents. And you can Add or Delete Agents from the Group (that is, move Agents in and out of the Group). Delete Groups Deleting a Group removes the Agent Group name entry from your local workspace. All Agent names in the group are also deleted. If the names were also in the workspace or in another group, they do not get deleted from there. Any data on the Agent computer (the Server that gets backed up) is not affected. Import Agents to a Group When you right click on the Group name, you can choose Import Agents from that menu. What the Import Agent function does is use the csv lines in a text file to fill in the properties of the New Agent screen. The csv file allows you to automate the process of adding many Agents where a lot of the information is duplicated, while still allowing for any differences to be entered manually. You manually create and save a text file. The Import Agents function will read the csv file and populate new Agents with the information there. The first field (Network Address) is required. If other fields are missing, the Agent Properties screen will prompt you for values. The fields are positional in that if you do not enter one, but want the next one you still have to have the commas there to indicate the order/position of that field. See the example below. The Import Agent process reads the csv file sequentially, processing each one as it goes along. If there are any errors, they will be reported in a log file, in the Logs folder under the Agent Group name. If any of the fields in the csv file are not supplied, the Import Agent process will stop and prompt you for a response. Page 35

37 Working with Agents CSV File Format The csv file is created with a name of your choosing. It can have from one to six fields per line, representing (in this order): Network address Description Port User name Password Domain Notice that in the csv file the Network Address comes first, and the Description comes second. The Network Address is required, where the other five fields are not always required. Each line represents one Agent to be added to the Group. You may skip over field entries after the first one in a line, or not mention them at all. In that case you will be prompted for the entry on the Imported Agent Properties screen. You do not need to enter a final Enter key (CR/LF) after the last entry. If you do, it will show as an error in the log: Can t find an address in line <#>., which can be ignored in this case. The system expects to have a password. If you skip over that field, it will prompt you for a password, even if you want the password to be null. You may use the Use as default for all the following imported Agents box to automatically assign a null password to all the following Agents. A typical csv line in a file might be: , Agent_1 in Group_B, 808, User211, Password, corp.company.com or: Page 36

38 Working with Agents or: , Agent_1 in Group_B, 808, User211 or: ,, 808,,, corp.company.com Adding and Removing Agents from Groups The Add/Delete Agents to Group function can be started by right clicking, or with the F2 key, when a Group is selected in the Agent Console. It allows you to move one or more Agents to and from the Workspace and Group. The << and >> buttons will move all of the Agents across from one side to the other, regardless of what is selected. The < and > buttons will move one or more selected Agents across. You can select multiple Agents by clicking on them while holding down the Ctrl key. Propagate Agent Configuration If you select an Agent inside a group, you can select Propagate Agent Configuration. This allows you to first configure one Agent, and then copy that information to all of the Agents in that group. When you have an Agent in a group selected, and right -click on it, you can choose the Propagate Agent Configuration menu choice. Page 37

39 Working with Agents The screen displays the name of the Agent you want to propagate from, and the name of the group you are propagating to. Select one, two or three of the choices for Vault Registration, Retention, or Notification. These are the same as described in the section on adding a New Agent. Click OK to continue. A Propagation Progress screen will appear next.. Propagate Job Configuration When you have a Job in an Agent in a group selec ted, and right-click on it, you can choose the Propagate Job Configuration menu choice. The Propagate Job Configuration is similar to the Propagate Agent. It shows the name of the Job you are propagating from, the name of the Agent that has the Job, and the name of the group that you are propagating to. Optionally you may choose to select to Propagate the Schedule(s) for that Job to the others in the group. Click OK to continue. A Propa gation Progress screen will appear next. Note: Job propagation is supported only on file based Jobs on similar Operating System platforms, such as Windows to Windows, or Linux to Linux. You cannot propagate an MS Windows-based Agent Job to a Unix-based Agent, for example. Job propagation is not supported for Agent Plug-Ins such as Exchange and MS SQL Server. Page 38

40 Working with Agents Vault Backup Agent Job configuration for propagation. Vault Backup Agent is a Plug-In that supports the backup of a Vault. See the Vault Backup Age nt Installation and Configuration for a description. Vault Backup Agent Job propagation is supported if the destination of the backup is to a Vault. If the destination of the backup is local, that is to a directory on disk, or a tape device, then the Propagate Job Configuration option will be grayed out (that is, invalid). Propagation Progress When you click OK from Propagate Job Configuration, the progress screen is shown. At the finish of the Progress screen, you may choose to view the log file with the View Log button. Log Files A log file is created for each session of Agent Imports and Propagation. It gives you information about the csv file, and whether each import and propagation was successful or not. Example: Mar05 14:01 GCFG-I Mar05 14:01 GCFG-I Copyright(c) All rights reserved. Mar05 14:01 GCFG-I Agent Version Mar :05:17 Mar05 14:01 GCFG-I Agents import started at 5-Mar :01: Mar05 14:01 GCFG-I Group name: New1, Import file name: C:\Program Files\Agent Console\Import1.csv Mar05 14:01 GCFG-I Agent 'Agent1' from line 1 successfully imported. Mar05 14:01 GCFG-I Agent 'Agent2' from line 2 successfully imported. Page 39

41 Working with Agents Mar05 14:01 GCFG-I Agent 'Agent3' from line 3 successfully imported. Mar05 14:01 GCFG-I Agent 'Agent4' from line 4 successfully imported. Mar05 14:04 GCFG-I Agent ' ' from line 5 successfully imported. Mar05 14:04 GCFG-I Can't find an address in line 6. Mar05 14:05 GCFG-I Agent 'Agent21' from line 7 successfully imported. Mar05 14:05 GCFG-I Import of Agent ' ' from line 8 was canceled by user. Mar05 14:05 GCFG-I Agent 'Agent5' from line 9 successfully imported. Mar05 14:05 GCFG-I Agent 'Agent22' from line 10 successfully imported. Mar05 14:05 GCFG-I Agent 'Agent22' from line 11 successfully imported. Agent Configuration After you have created an Agent, and set the Agent Properties, you will be able to perform the Agent Configuration. Note that you must have a valid Agent connection (via IP or host name) and a valid Authorization to that system. Agent Configurations are specific to an Agent and affect all Jobs run under that Agent. Many of the settings can be defined when you are creating a Job. However, you can manually set or modify the settings through the Agent Configuration file. Use Tools > Agent Configuration (for an existing Agent), or with the Agent highlighted, click on the Agent Configuration file. There are six tabs: Vault s, Retentions, Open File, Notification, Others and Plug-In (optional). These tabs are described in the next few sections. Page 40

42 Working with Agents Vaults (New) In the New Job Wizard Vault, select the New button. Or, from Agent Configuration > Vault tab, select New. Vault Registration If this is a new Vault, you must register the computer as a new computer. For re-registration, see below. To be able to change the host name, see Editable Host Names below. Profile Name Enter the Vault profile name here. It will be used for all operations with the newly created Vault. Vault Network Address Enter a network host name or an IP address. For a multi-home Server, you may enter multiple network addresses. That is, if the Vault has multiple Network cards (NICs) and IPs, you can list the addresses here in order of which to use first. You may move them up or down in priority by the using the buttons: Add, Move Up, Move Down, or Remove. Port Settings The nature of backup software is to have secure, long-term sessions of activity each day. Network transports such as TCP are notoriously poor at providing stable connectivity. In an effort to overcome this issue, BRTP (Backup Restore Transport Protocol) has added network connectivity resumption support to the protocol. This means that, in the event of any kind of network failure, a Backup or Restore Job will recover and resume its functions from where it left off. Enter the port values to which the new Vault is listening. This table lists any currently configured ports. The default port for new installs is For upgrades, port 807 is used. Shou ld you create multiple ports, the ports will be attempted in descending order. The software can be configured to utilize the HTTP (80) and FTP (21) ports instead of the traditional BRTP (807 or 2546) port. Quite often, these ports are open to outbound connectivity with a remote system since many companies permit browsers on the desktops. Alternatively, any other port can be used but you need to have your service provider's approval. The maximum port entry in the Custom field is If the port you select is used by another service, a message notifies you and offers the opportunity to continue or use another port. A port may be added through the "New Ports" field and the "Add" button. Note: If you choose to add a new port, you may need to discuss the options with your Service Provider. After selecting a port, click Next. This takes you to the Connection Settings screen. Page 41

43 Working with Agents Connection Settings The default connection/re-connection settings are optimized for most network situations, and can be accepted. If you wish to change them, follow these steps: In the Try to reconnect every field, enter the maximu m number of seconds your system should try to reestablish connection to the Server before terminating/failing the Job. This value should be between 3 and 3600 seconds. In the Stop reconnection attempts after field, enter the number of minutes to stop trying to reconnect. This value must be between 1 and 1440 minutes. Default shown is 60 minutes. This time value (entered in minutes) must also be greater than the value (entered in seconds) in the try to connect every field above. NOTE: In both of these fields, you must enter integer numbers (positive numbers, with no fractions, decimals or commas). See Section ( Seeding with Deferring ) in this for more information of the use of these settings. Over The Wire Encryption Settings : Check this box to enable OTW encryption for transmission to and from the Vault. The default mode is ON, using AES encryption. The OTW encryption functionality is applied to any Job that uses that profile. Users may turn this off if security is not an issue. That is, when unauthorized users would not be able to see network traffic (say, with a Sniffer type device), as the network is secure. OTW turned off will also gain the user a little more speed/efficiency with backups and restores. Click Next to continue. Authentication Panel From the Authentication panel, enter the account, user name and password as supplied by your Service Provider. Note that the password is case sensitive. Click on Next. Click Finish. This completes your Server configuration. Once a Server has been configured, its settings may be edited. To change the Agent Host Name, use the Advanced button. This information is case sensitive. This takes you to the Agent Host Name screen. Clicking the Change Agent Host Name allows you to be able to re-enter the host name in the Agent Host Name field. See Editable Host Names. Vaults (Existing) If you have an existing Vault configured, it will show in the list of servers here. If you want to create a new Vault entry, see the section on Vaults (New). If you want to edit an existing Vault, also see Vaults (New) for a description. Editing a Server: 1. From the Servers tab (Agent Configuration), click the target Server. 2. Click the Edit button. The Server Entry panel opens. 3. Alter the Server specifications as required. Page 42

44 Working with Agents 4. Click OK. Deleting a Server Before you can delete a Server entry, it must be empty of all Jobs. 1. Highlight the target Server. 2. Click Delete. 3. Click Yes to confirm the deletion. If there are still Jobs associated with this Vault, you will see a screen List of Jobs associated with <name> Vault entry, and a message You cannot proceed until you have deleted all the Jobs. The Copy to Clipboard button allows you to copy the list of Job names to somewhere else, such as a text file in Notepad, or to an . This allows you to be able to see and keep all the names that must be deleted, if you have a long list of them. The Cancel button takes you back to the Vaults tab in Agent Configuration. Retentions Retentions are defined and set manually through the Retentions tab (Agent Configuration). There are three pre-defined retentions. The retentions can be modified as necessary but are useful when creating a retention scheme for the first time. You can create more retentions (up to 10 total, including these three). The pre-defined (default) retentions are as follows: Retention Days Online Copies Online Days Archived Daily 7 7 OFF Weekly 31 5 OFF Monthly OFF Days Online is the number of days a safeset is kept on the Vault before expiring. Copies Online indicates how many copies of the Backup safeset are stored online. Days Archived indicates if, and how long the data will be stored offline. Note: Days Online and Copies Online work in conjunction. So, both conditions have to be met before any backups are deleted. For example, if both Days and Copies are 7, then there can never be less than 7 backups. If Days goes over 7, there will still be 7 Copies. If Copies goes to less than 7, there will still be 7 Day s worth. It must be over 7 Days with more than 7 Copies before any are expired. Editing a Retention Schedule To manually edit a pre-defined retention from the Agent configuration file: 1. From the Retentions tab (Agent Configuration), click on the retention name. 2. Click the Edit button. This starts the Retention Wizard. 3. Make changes as required. From the Name dialog, the name of the retention can be edited. Retention names can be up to thirty-two (32) alphanumeric characters in Page 43

45 Working with Agents length. No spaces are allowed. Names are not case sensitive. Underscores (_) and dashes (-) may be used. 4. From the Online dialog, the number of days and the number of copies can be modified. The number of days can be from 1 to 9999 and the number of copies can be from 1 to From the Archive dialog, choose whether you want to archive your data. Data can be archived from 365 to 9999 days. If you would like to archive data, discuss this with your service provider. 6. From the Finish dialog, click Finish. Note: Changing a particular retention definition affects only the retention number and its application to future (yet to be created) safesets. You may also want to create a new retention. A retention is defined through the Retention Wizard. Activate this Wizard by clicking the New button on the Retention tab (Agent Configuration) or by clicking the New Retention button on the Retention dialog (New Job Wizard). Creating a New Retention To create a new retention from the Agent Configuration file: 1. From the Retentions tab (Agent Configuration), click New. The Retention Wizard launches. 2. From the Welcome dialog, click Next. 3. From the Name dialog, enter the name of the retention. Retention names can be up to thirty-two (32) alphanumeric characters in length. No spaces are allowed. Names are not case sensitive. Underscores (_) and dashes (-) may be used. Click Next. 4. If desired, enter a number between from 1 to 9999 in the Days Online textbox. This number defines the number of days a safeset is to be kept on the Vault Server before expiring. Once the expiry date is reached, a safeset is automatically deleted. 5. If desired, enter a number from 1 to 999 in the Copies Online textbox. This number defines the minimum number of copies of a particular safeset (as defined by a Job) that will be maintained online. It functions in a first in, first out manner. Once the number of copies is exceeded, the oldest copy will automatically expire or be deleted. This process occurs until the actual number of copies matches the definition. This setting does not apply to archived data. 6. If desired, enter a number from 365 to 9999 in the Days Archived textbox. This number defines the number of days a safeset will be maintained on removable media at the Vault (typically tape) before it expires and is deleted. 7. From the Finish dialog, click Finish. 8. To save the retention, you must click OK on the Retentions dialog before exiting from the Agent Configuration file. Page 44

46 Working with Agents Open Files Agents 6.70 or greater use VSS (Volume Shadow Copy Services) by default for open file management. The following descriptions of OTM and OFM products are applicable to Agents 6.61 and older. OTM can still be used with older Jobs or in a custom manner, but are not used by default. For Agents 6.6x and lower, if you have installed Open Transaction Manager (OTM) or Open File Manager (OFM), you can configure the software through the Open File tab (in Agent Configuration). For Agents 6.6x and older: You may install OTM after an initial Agent installation, by running the installation again, and choosing "Modify" to select to add or remove specified software components. Select to install the OTM feature. Under Product, select the Open File product from this menu, depending on which one you have installed: None or OTM None or OFM Note: You cannot run both OTM and OFM together. Note: A successful backup of Windows Server 2008 System State requires either OFM or OTM to be used during the backup. OFM Features: Typically used on large servers. Separate installation; configured through its own GUI. Has dynamic cache, and its own log files. Displays its cache as a file; can select drives to cache; can release cache before end of backup. Can run concurrent, multiple backups. OTM Features: Typically used on small to medium sized servers. Configured and installed through the Agent. Uses a single cache, with pre-allocated maximum size; caches all drives. Logs to the Agent Backup log. Only allows one backup at a time. Releases cached data at end of backup. Note: With OFM versions above 9.1 you must use the OFM Manager GUI (Configuration > Properties) to explicitly exclude directories and subdirectories. This is found within the OFM GUI under, System > (Server name) > Properties > Files tab > (browse to the Agent installation directory) > Files to be ignored by OFM (select checkbox: Include Subdirectories). OFM versions prior to 9.1 will automatically exclude any directories that cannot be open during a backup. In the following Settings, you will be able to select all the following for OTM, but only Abort Processing Options (and possibly the License Key field) for OFM. Page 45

47 Working with Agents License key Enter your license, supplied by your service provider or authorized reseller, in the License Key textbox. If you installed OTM with the Agent, you will have a 30-day trial license. Validate Key You may click on Validate Key to validate (check) that your license will work. If the license does not validate, check the information carefully and make any necessary changes. Once validated, click OK. Note: If you are configuring a 5.53/6.02+ Vault the OTM License field, and the Validate Key field is shown as available to be changed, and used (that is, not grayed out). You cannot modify these with a 5.53/6.02+ Vault, and the Validate Key is not applicable, but you can use them on an earlier Vault. Cache File Size The cache file size is related to how many unique writes occur to the Server during the Backup. As a rough guideline, for every write there are ten reads. As such, for 100MB read during one hour, a 10MB cache is suffic ient. There is a maximu m limit on the size of the cache file. Depending on the O/S used, it may be up to 4 or 7 GB. If you exceed the maximum size, you will get an error: OTM failed to start up and insufficient system resources exist to complete the requested service in the Agent log file, and the backup will fail. Reduce the cache file size and re-try the backup. Cache File Location Use this parameter to specify the placement of the cache file. Use Agent Product Directory: If this option is selected, a cache file is created where the Agent Console Software is installed. Use OTM Auto Placement: If selected, the OTM software places the cache file on a non-otm drive, provided one is available with enough disk space. If no non-otm drives exist, or there is not enough space, the first OTM drive with enough space is used. If the drive is the same driv e in which the temp directory resides, the file will be placed in the temp directory; otherwise, it is created at the root of the drive. Note: You may use one of these two choices or you can enter another path name of your choice. For instance, you may want to direct the cache to the fastest disk drive, with the most space. If your choice is invalid for any reason (such as space limitation on the disk or an invalid path name, OTM will not start. There will be a message in the log. Whether the backup will continue depends on what you have entered in the Abort Processing Options below. Page 46

48 Working with Agents Quiescent Wait Period The Quiescent Wait Period is the minimum period of idle disk(s) activity (no writes) that OTM requires before its cache file is created and the Virtual drive(s) are mapped. The default setting is 5 seconds. No Activity Timeout The No Activity Timeout is a period of time that OTM will wait to attain the Quiescent Wait Period. After the set period of inactivity has passed, the software logs and continues, or logs and halts the program as specified. Abort Processing Options The Abort Processing Options pertain to open file processing errors, such as synchronization problems. Select your abort processing options. You have two choices. You can select Log and Continue or Log and Halt. Log and Continue will log any error (such as not being able to achieve the quiescent wait period to create a snapshot of an open file) and continue with the Job. Log and halt will halt the Job after logging any error. Notification You can receive notification after a successful and/or failed Backup procedure. 1. To configure the notification: 2. With the Agent highlighted, click the Agent Configuration file. 3. Select the Notification tab. 4. Click the Send on Successful Completion and/or Send on Failure and/or Send on Error checkboxes to select/deselect these options. 5. In the From Address, enter the address from which the notification is sent. This can be any valid address. 6. In the SMTP Server Network Address field, enter the network address of the SMTP Server that will send the . Note: If you are operating under NetWare, you may have to specify the mail Server s address as an IP address. For example, you may have to use instead of some_company.com. A name can be used but only if it has already been defined in the System HOSTS file in the SYS:\ETC directory. 7. Enter the recipient addresses, separated by commas. 8. Click OK. Page 47

49 Working with Agents Explanation of Notifications Send on successful completion: There may be Warnings (in the log file), but you can still recover any file from this backup (safeset). Send on error: There are Errors (in the log file). You cannot recover those files that have the errors, but you can restore others in that backup (safeset). Send on failure: No backup occurred. You cannot recover any files in that backup (safeset). Note: If you have one, two or all three checked on, you will only receive one for each backup session. Therefore it is recommended that you have all three checked on, if you want to see all conditions. Check the backup log file to see if the notification (the send) was successful. SMTP Credentials If the Agent is version 6, and Agent Console is also version 6, you can see the additional SMTP port, and SMTP Credentials fields. In the outgoing SMTP Port field enter the port number assigned to this SMTP Server. The default is port 25. Depending on your SMTP Server security, you may need to enter authentication to allow the Agent to access the Server to send s. Enter a valid User Name, Password and (if required) a Domain name. This does not get c hecked or tested until it actually goes to send an . Advanced This tab has an Execution Priority function, and "Bandwidth" settings, for version 6 (and above) Agents. Execution Priority Drag the slider to select your preferred Execution Priority value (for Windows and Unix operating systems). This affects the priority of the Agent program on a computer, running the backup (or restore). "HIGH" is the highest priority, and "LOW" commands the least CPU priority usage. T he "NORMAL" (middle) value is usually adequate depending on the number of concurrent applications being run on the computer during the assigned Job. Page 48

50 Working with Agents Bandwidth This allows the user to control the amount of network bandwidth consumed by the Agent (Windows or Unix) during Backups and Restores. For example, you might want restrictions on daytime ad-hoc backups/restores so that on-line users are not affected, and then unlimited usage at night so that scheduled backups will run as fast as possible. This configuration includes: Maximum bandwidth (upper limit), in kilobits per second, to be consumed during each Backup and Restore. Page 49 Period of time during the day that throttling is in effect. Only one time window can be specified, and outside the window, no throttling takes place. The day(s) of the week that throttling is in effect. The time period will appear as either a 24 hour format, or an AM/PM format, depending on how the clock is set, on the system running the Agent. The setting is determined at the start of the Job. The setting is adjusted dynamically if the Job crosses a throttling window boundary. The throttling setting is applied globally to all backup and restore Jobs, but it may be over-ridden, for ad hoc Backups (for example), by temporarily resetting the bandwidth to "Use all available bandwidth". Restores can override the setting, with the Use all available bandwidth setting in Advanced Restore Options.

51 Working with Agents Bandwidth Throttling is applied across multiple Jobs running on a single Agent. So, more than one Job running on the same Agent will each share the allocated bandwidth equally. Plug-Ins This tab is only shown if you have one or more Plug-Ins installed. See the appropriate User for each separate Plug-In, for more information. Use Agent > Properties > Get Status to see what Plug-Ins you have installed on the respective Agents. An Agent only backs up files, but databases, mailboxes, pool systems and others are seen as objects to the system. A Plug-In (which is application specific) understands objects and translates them to files, so that the Agent can back them up. From the Plug-In tab, select a Plug-In from the drop-down list. If you have just installed the Agent and Plug-In, you will have to enter a valid license key (from your Vault Service Provider). Click Test to make sure that it is correct, then c lick Set to save it, and allow the Plug-In to be used for backups. Note: You would only enter and set a license key here if you are connecting this Agent (at any time) to a Vault that is version 5.3 or less. If you are connecting to a 5.53/6.02+ Vault, you do not need to set a license key here as licensing for Agent Plug-Ins is supplied from the Vault. Set The Set button saves the license information (key), and any Options (see below) you have entered. You must also click on the "OK" key to permanently save any changes. Test The Test button is used to determine the validity of the license information. If your license does not verify, check for any extra blanks or that all the UPPER and lower case characters in the "License key" field have been entered properly. Note also that the Password is case sensitive. Options for Exchange The Options button (for Exchange Plug-In only) takes you to a separate screen where you may enter a "Run As" User name, password, Domain and valid Exchange profile that the MAPI Backup needs to access mailboxes. (Note that this information may have been entered at installation time.) If you click OK from the Options screen, you must also click "Set", and then "OK", from this Plug-In screen to save the information. Power Management for Windows Operating Systems This screen allows you to specify what you want to happen regarding your backups (on Windows Agents only) if: they have been missed, or failed, the system wants to shutdown, Page 50

52 Working with Agents the system wants to hibernate, the system detects a network loss/presence. You will be notified of the status of your backups and the network, with the System Tray icon (Agent Assistant). The icon may show Ready (not processing and the network is up), Processing (a backup is running) or Not Ready (network connectivity is down). If you hover the mouse pointer over the system tray icon on the Agent machine, the current status of the Agent will be displayed. Hibernate and Standby Agent users should NOT enable hibernation or standby on their desktops or laptops. If the computer is powered down, or off, scheduled backups will not occur at the scheduled time. If the computer has been powered off (or in hibernate or standby mode), you can configure it to automatically start or restart scheduled backup Jobs, if they were missed or failed to run. This will occur when the computer is powered on/up. You may log off, but the computer must still be running the Operating System and stay connected to the network for the backups to run properly. Note that if you are logged off, there will not be any prompt messages on the Agent machine from the Agent Assistant. It will run as if the prompts for missed/failed backups, shutdown, and standby/hibernation were turned off. Page 51

53 Working with Agents Advanced Schedule Options You have two choices when deciding how to handle scheduled backups that may have been missed or failed. This is usually due to Hibernation or Standby being on, or the network was down, or the PC was powered off (Shutdown). 1. Start scheduled backup jobs if they have been missed. If this box is checked, the scheduler will attempt to start any backups that are still waiting to run. Note: If backup schedules overlap, only the last one will have its status reported. 2. Restart scheduled jobs if they have failed. If any backup Jobs have started, but failed to finish, because of network failure or the PC shutting down, those Jobs will be started again. In either of these cases, you may choose to be prompted (asked for confirmation) before the backup Jobs are started or re-run. Select the checkbox below each line/prompt. Note: If the same Job has been missed several times in a row, only one occurrence of it will be run when the backup does occur. So, for example, if you have a backup (the same Job) scheduled for midnight every day, and your computer is off for three days, you will only get one backup missed and re-run, not three. Shutdown Options The first checkbox in this section, when set, prevents the computer from going into shutdown mode if there are backup Jobs running. The next time the Shutdown tries to run, and there is no backup running, the Shutdown will occur. Prevent Shutdown when backups are running. The second checkbox which depends on the first one being set - prompts the user at the time of shutdown. Ask the logged on user what to do if backups are running. The third checkbox prompts to see if the user wants to do a backup before the system shuts down. This is not dependent on the first choice. Ask the user to do a backup before shutdown. Note: In the second and third boxes ( Ask the user ) the operating system will attempt to stop all running tasks before shutdown. You will see a message that it is attempting to end a program called Maestro.exe. This is the Agent Assistant part of the Agent that is trying to prevent the shutdown. Do not click the End Now button for Maestro.exe. Wait until it says that the program is not responding, and then click the Cancel button. If you do click End Now, it will shut down and not do a backup, if that is what you intended. Also, if you stop the backup and a shutdown is pending, it will not shutdown. Page 52

54 Working with Agents Hibernation Options Check this box to prevent the computer from going into sleep or hibernation mode if there are backup Jobs running. Prevent Standby/Hibernation when backups are running. The next time the Standby/Hibernation tries to run, and there is no backup running, the Standby or Hibernation will occur. Miscellaneous - Detect Network Presence If the network goes out, the Agent Assistant pauses the scheduler. It resumes when the network is back up. This stops scheduled backups from starting and failing to connect to the Vault. When the network comes back the scheduler will be resumed, and depending on the scheduler options that are set, any missed or failed backups will run. The time to check for the network presence is: Never, 1 minute, 5 minutes, or 10 minutes. Never means that the Agent Assistant will not detect network outage, so backups will still run and will fail. That is, the scheduler will not be stopped. The Never choice is normally used for troubleshooting. You should specify checking for network availability every 1, 5 or 10 minutes. If a backup does fail because of the network being out the backup can be restarted, if you have the Scheduler Options missed/failed fields checked. Normally, every 5 minutes is a good default value, as it does not incur much overhead on the system, and it means that your backups can start/continue when the network presence is detected. The Tray Icon will change to a Not Ready if the network connection is lost for longer than the period defined. Page 53

55 Working with Agents Registration Registration is the process that occurs when you first configure an Agent. You supply parameters such as your use rid, password, and Vault address (which were given to you by the Vault personnel) so that the Vault knows that the Agent computer is valid. This connection to the Vault registers that computer (with its Agent) on the Vault. You know the registration was successful if the Vault allows you to connect, and proceed. The Vault then sends an ID back to the Agent computer. This ID includes t he Vault name, and a unique Agent Computer identifier. This part happens without your intervention or knowledge. Next you would configure Jobs to that Vault. There can be multiple Jobs associated with an Agent computer, but an Agent computer is only registered once. Jobs are registered onto the Vault as well, to validate that Job coming from that specific Agent computer. Now, the Agent knows about the Vault, and the Vault knows about the Agent. This information is kept on the Agent side and on the Vault side. If something happens to the Agent computer (e.g., it crashes), when you do a Disaster Recovery, the Vault information about the Agent computer is sent back to the Agent computer. This re-registration is necessary in order to recover all of the Agent's parameters, such as schedules and Job files. So, when you attempt to re-connect to the same Vault with the same Agent computer name, and with your user ID and password, the Vault sees that name in its list and asks if you want to re - register. When you do, you are able to recover that Agent's Job information, which had been stored on the Vault. Editable Host Names When you first use an Agent to connect to a Vault, you must register that Agent to that Vault, so the Vault will recognize that Agent and computer for future Backups and Restores. Steps 1a and 1b below show a normal registration using the default computer/host name. If, for conflict reasons, you need to change (edit) the host name, step 1c shows the optional Agent Host Name screen. Later, if you need to re-register a computer (say, after a bare-metal Restore) when the Vault already recognizes that name, you can re-enter or change the authentication information (step 2) but only view, and not change the host name. Registration To register (first time) an Agent (i.e.: computer) to a Vault, you use the Registration Wizard under Agent Configuration > Vault > New and it will ask you to register the computer to the Vault. You are asked for Authentication information. This information is case sensitive. Normally the system name will be used to register with a Vault. If you want to change it, to avoid host name conflicts, use the Advanced tab, to go to the Agent Host Name screen. (Not for re-registering a computer (i.e.: after a bare-metal Restore) - see #2 below.) The System Name of the Agent PC (Server) is the DNS name of that machine. It must be registered on the Vault to allow that machine access to the Vault, under that account. But what happens if two machines, say in different locations have the same name? Both of them cannot be registered on the same Vault, as the name must be unique across the Vault. Page 54

56 Working with Agents In Agent Console, under Agent Configuration > Vault > New, you can Change Agent Host Name to avoid any naming conflict. This only changes the alias name of the Agent computer on the Vault, so that the two machines are now unique. The real System Name of the computer does not change. Re-Registration/Edit Under Agent Configuration > Vaults > Edit > Authentication, you can change the Account, Name and Password (the password is case sensitive) on a registered computer, but not the Agent Host Name (it is display only, here). Note: Select the Re-Register radio button to Re-Register to the Vault a previously registered computer. This option is grayed out when trying to create a New Vault connection from within the New Job Wizard. If you wish to create a New Vault connection and Re-register a previously registered computer, use "Agent Configuration... > New". Page 55

57 Working with Jobs Working with Jobs Each Agent defined within the Agent Console application manages a collection of elemental Jobs. A Job defines the default parameters associated with a Backup, Restore or other command. Some of the parameters included are the file selections, compression and encryption settings, log file location and other advanced settings. To create Jobs, select (highlight) an Agent, and use: File menu > go to New Job, or, From an Agent, right-click on New Job. You can get to Properties of an existing Job, with F2, or File > Properties. Notice that you must have a valid Job selected. Creating a New Job Once you have created an Agent, you can create a Job. A Job is initially made using the Job Wizard. Right-click on the target Agent. Choose New Job. This starts the New Job Wizard. From the Welcome dialog, choose Next. The Welcome screen may not appear if it has been de-selected previously, with Skip this screen in the future. Backup Source Type Backup source type may be Local Drive Only, "Network UNC Share" or Mapped Network Drive Only. There may also be Plug-Ins shown. Depending on your installed Plug-In options, you may have Exchange Server (Database Backup only), or Exchange Server (mailboxes and public folders only), or Oracle (database), or MS SQL Server (database) or SharePoint, in the pull-down list, to choose from. These are discussed separately, in their respective s. Select the source of the data that will be backed up by this Job. What you select here will affect the following screens in terms of Source selection. Local Drive Only Local Drive Only allows you to include Data Files and, optionally, System State, RSM Database, BMR, or Event Logs. You will only be able to back up from the drives that your local computer can see (for example "C:"). Following are the main steps that this backup type will follow. They are described further in this section, and also in the appropriate Agent. 1. Welcome screen. This may not be shown if you have checked "Skip the screen in the future." 2. Backup Source Type. Choose "Local Drive Only" from the dropdown list. Choose one of the "Filename Encoding" buttons, discussed in section later. 3. Select a destination Vault. Or create a New profile if you want. Page 56

58 Working with Jobs 4. Create a Job Name. This can be up to 30 characters for a 5.6+ Agent and Agent Console on a 5.5+.Vault, but only up to 8 characters for previous versions. 5. Source. This is where you select files and directories to be backed up. You may also optionally select to include System State, RSM database, or Event Logs. When you select Data Files, and click Add, you are shown your local drives, and you can make your choices. You will also see a filter for recursion and matching. You may include and exclude as many directories and files as you want. Click OK, when you are done, choose more sources if you want, and finally click Next. (Note: You may see a Bare Metal Restore option in this list. You need a license for this to be able to back up. See Overview of System Restore in this.) 6. Choose options for the Job: Quick File Scanning; and Backup Time options. 7. Optionally choose to use Encryption, for the backed up data on the Vault. 8. Choose the level of logging you want, and number of copies to keep. 9. When finished, you can select to exit the Wizard, or to schedule or run the Job immediately. Network UNC Share for Windows Agents This allows you to Browse and backup network resources via UNC paths (for Windows Agents only). The UNC share will be the root for the browse, instead of a device letter. Using UNC gives you more flexibility with remote files and directories, than using mapped network drives. Both "Network UNC Share" and "Mapped Network Drives" only allow you to select files and directories. Then you are presented with the Source screen, with the Network Share as the "root" of the hierarchy, and not a drive letter. When you select to "Add", you are prompted for the path of the UNC Share to Browse to (for example: \\ \MyShare). If the path or credentials are not valid, you will see an error message: "An error occurred during the Browse." Now you can select files and directories to include/exclude, and Options, Encryption Type, and Logs. Mapped Network Drive Only "Mapped Network Drive Only" (for Agents below version 5.6) allows you to choose files and directories from a drive that you have mapped to your Agent System. Agent versions 5.6+ have only Network UNC Share. Both "Network UNC Share" and "Mapped Network Drives" only allow you to select files and directories After you have chosen a Job Name (as before), you must choose Network Account information that will enable the Backup process to "Run As " (those credentials). Then you are presented with the Source screen, with the Mapped Drive as the "root " of the hierarchy. Now you can select files and directories to include/exclude, Options, Encryption Type, and Logs. Page 57

59 Working with Jobs Filename Encoding - Unicode The encoding method selected will impact the data being backed up. With ANSI encoding, any filenames with characters not in the ANSI namespace will not be backed up. An Agent can back up and restore files whose names contain characters outside of the ANSI set. Note that Plug-Ins (Exchange and MS SQL Server) do not use UTF-8 Encoding for the object names they create. Unicode is the default representation for file names if you use multiple languages on your system. This includes Asian character sets. These file names may not display correctly in the include/exclude screen. All files will be displayed, with some showing the question mark character (?) in some locations. But the files will be backed up. ANSI is the normal representation of most single languages. If you always use only o ne language on your Server, such as English, Swedish, Russian, etc. this will display your file names and allow you to select them for backup. However, if you have file names with other languages, they may be displayed but may not be selected for backup. Unicode and UTF-8 defined: Unicode: Unicode is the international standard whose goal is to provide the means to encode the text of every document people want to store in computers. Unicode is considered the most complete character set and one of the largest, and has become the dominant encoding scheme in internationalization of software and multilingual environments. UTF-8: 8-bit Unicode Transformation Format is a lossless, variable length character encoding. It uses groups of bytes to represent the Unicode standard for the alphabets of many of the world s languages. It uses 1 to 4 bytes per character, depending on the Unicode symbol. For example, only one UTF-8 byte is needed to encode the bit US-ASCII characters in the Unicode range U+0000 to U+007F. Destination Vault From the Target dialog, select a Vault from the drop-down list, for the Backup. Choose Next. You may also create a new Vault profile from here. This is described in the section of this manual on Agent Configuration, Vaults (New). Job Copied to another Vault The Vault Operator may determine that a Job needs to be moved to another Vault, either because of space problems, failing hardware, or other technical or logistical problems. If a Job is copied (moved) on the same Vault, the user does not notice this as the unique Job ID is retained. But a Job on a new Vault will generate a new Job ID. So, if a Job is copied to another Vault, the user, from Agent Console, must do two things to ensure that the Job will work properly: Re-register the Agent (to recover the Jobs), and Manually change the IP address - and username/password, if necessary - (under Agent Configuration ) to point to the new Vault. Page 58

60 Working with Jobs New Job Name From the New Job Name dialog, enter a name for the Job. The name must be 1-30 characters in length and must consist of letters (A-Z and a-z), numbers (0-9) and/or _, -, $ (underscore, dash, dollar sign). Click Next. Note: If the version of Agent is 5.5 or lower, you will only be allowed 1-8 characters for the Job Name. The following names cannot be used as Job names when connected to an Agent: PRN, CON, LPT1, LPT2, LPT3, LPT4, COM1, COM2, COM3, COM4, NUL, AUX, Register, or Global. "Register" or "Global" will give you a message that the Job name already exists, even though you did not create it yourself. The others will give a message that those Job names are reserved by the system. Page 59

61 Working with Jobs Source Select the Data Files checkbox to open the Include/Exclude panel (see below). Use this option to specify which files will be backed up in this Job. If available, select System State to add system specific information to your Backup (see below). This is different for MS Windows and for NetWare. Note: Vault profiles, schedules and Jobs that are associated with a physical node in a cluster can have the system volume and System State backed up, and restored. If available, select RSM database to add information about the Removable Storage Manager (see below). If available, Select Event Logs to back up the system logs. If available, Select BMR to create a BMR type backup. Include/Exclude Exclusion Tree Scanning: In previous versions, if a file selection contained nested exclusions and inclusions, the exclusions would always take precedence. Now, the selection with the most detail will take precedence. This allows for nesting of multiple inclusions and exclusions. In these cases, the filtering will avoid traversing excluded directories. Folder/Container Wildcards: Wildcards are supported on file folders and MAPI containers, for use during backup only. * (asterisk) - signifies a wildcard string up to the next separator character.? (question mark) - signifies a single wildcard character.. (period) signifies a recursive directory. Examples: *.txt - selects all files that have the txt file type. C:\.\*.doc - selects all files on drive C that have the doc file type. t*.* - selects all files that begin with the letter t. Note: Not all Plug-Ins (for example VMware) support multiple wildcards in-line. Page 60

62 Working with Jobs From the Source dialog, select the files and/or directories you wish to include/exclude from the Backup by clicking the Data Files checkbox. Click the Add button to open the Include/Exclude dialog. From this dialog, browse for files and/or directories and select them. To include a file or directory, highlight it and click Include (or double-click it). To exclude a file or directory, highlight it and click Exclude. You must select at least one file to include in your Backup Job. If you selected single files, the Confirm/Include Files confirmation panel appears. Click Yes to include the selected files in your Backup. If you have chosen to back up an entire directory, the Confirm/Include Directory panel appears. Select Recursive if you want to include/exclude all subdirectories and files in your Backup. If the directory you want to back up contains a large number of files, the graphical Include/Exclude panel may take a long time to display the directories. If you have a large numbe r of files in a directory, use the manual Include/Exclude panel. This panel enables you to directly enter the file names you want to back up. To open the Manual Include/Exclude panel, hold down the shift key and click the Add button on the Source tab. Using a format like the following example, enter the directory that your Backup files are in: C:\Windows Using a format like the following examples, enter the name of the file(s) you want to back up: sample.txt *.txt *.* Back up the file called sample.txt Back up all.txt files Back up all files in the selected directory A list of files can be entered using a semi-colon to separate the file names. *.txt;*.exe;*.htm Note: A wildcard search cannot be done on file names that contain semicolons. Select Recursive subdirectories if you want to include/exclude all subdirectories and files in your Backup. For more information on Recursive Backups, see section Click the Include button. The files you have selected are added to the Backup Job. After you finish making your selections, click Yes. The Source dialog returns. Choose OK and Next. Under Windows, any files or directories that contain reparse points are displayed in red. Note: One of the new capabilities added to NTFS version 5 was the ability to create special file system functions and associate them with files or directories. This enables the functionality of the NTFS file system to be enhanced and extended dynamically. The feature is implemented using objects that are called reparse points. Page 61

63 Working with Jobs File Backup Options If you select Data Files > Options, you can specify File Backup Options. Backup Files opened for write: The Backup Files Open for Write option enables you to back up files that are open while the Backup is in progress. Files that are open for write, and also opened for shared read can be backed up. However, files open only for exc lusive write cannot be backed up. The danger in backing up files that are open is that you are not guaranteed to get a copy of the file at that time. Therefore, an open file might be modified during the Backup process producing inconsistencies in the Backup copy. Note: Agent 6.70 or greater use VSS (Volume Shadow Copy Services) by default for open file management. The following descriptions of OTM and OFM products are applicable to Agent 6.61 and older Agents OTM can still be used with older Jobs or in a custom manner, but are not used by default. A third-party application such as OTM or OFM can be used to properly back up open files. See section of this manual, as well as the corresponding Agent User s. Suppress Archive bit processing: When a file is created or modified, an archive attribute (depending on the O/S) can sometimes be placed in that file. The archive bit tells some programs that the file requires Backup. By default, the application clears the archive bit once it backs up a file. If you are using other Backup programs that rely on archive bits, select the Suppress Archive Bit Processing option. This will leave the archive bit intact. Support NetWare file compression: If this checkbox is selected, the software backs up the NetWare file in compressed format. This feature is useful for files that are rarely modified. Note however, that the Backup Delta processing feature does not work on compressed files. Each time the compressed file is accessed, the Backup sees the entire file as new and must reseed it. Advantages Backing files up in their native compressed form ensures that they will be Restored in compressed form, reducing or eliminating the possibility of a disk full situation. Backing files up in their native compressed form reduces CPU overhead by not having to compress and decompress on-the-fly during Backup and Restore. Disadvantages Files can only be backed up in their native compressed form if the O/S supports NetWare compression and compression is enabled on the volume that the files are Restored to. When files change from compressed to uncompressed, or from uncompressed to compressed, the application must Backup that file in its entirety. If the compression settings in NetWare are too aggressive (meaning a lot of compression state changes are occurring) the Delta processing will be inefficient. Currently, natively compressed files cannot be Restored to an NSS volume. The Support NetWare File Compression checkbox is unselected by default. NetWare files are backed up in uncompressed form, enabling full Delta processing and often saving storage costs over the long term. Be aware, however, that you will require significantly more room on your system for the Restored files if your original files were compressed. Page 62

64 Working with Jobs If you have selected to support NetWare compression, you can detect changes during Quick File Scanning. This detects if the data has been converted by the O/S from non-compressed to compressed, and causing a re-seed. Any file streams that are deemed unchanged since the last backup are skipped over. The default is to read files in their entirety. Unix options Backup single instance of hard-linked files: With "Backup single instance" set (the default is "checked"), the backup is slower, but smaller, as only the actual data (one copy) and the hard links are backed up. On a restore the data and all the hard links are restored. If "Backup single instance" is NOT set (checked off), the backup is faster, but the backup size may be larger, as each link and the data are copied separately, and restored separately. The hard links are not re-established in this case. System State MS Windows If "System State" is available in the Job Configuration selection screen, select it to add systemspecific information to your backup. Note: Vault profiles, schedules, and Jobs that are associated with a physical node in a cluster can have the System Volume (SYSVOL) folder and System State backed up and restored. If available, select the RSM database to add information about the Removable Storage Manager. The following objects are backed up with System State in: Windows Server 2008 Registry COM+ Class Registration database Boot files Windows System Files Performance Counter.NET Framework IIS Metabase If Installed: Certificate Services database Active Directory SYSVOL folder Cluster database and Quorum disk Terminal Services database Volume quotas WMI-specific state and data DHCP database WINS database Page 63

65 Working with Jobs Windows VISTA / Windows 7 Registry COM+ Class Registration database Windows System Files Performance Counter IIS Metabase.NET Framework Note: For Windows Vista / Windows 7 and Windows Server 2008 backups that include System State, Windows System Files will be included. Windows 2003 Server/XP Professional Registry COM+ Class Registration database Boot files Windows System Files Performance Counter IIS Metabase If Installed: Certificate Services database Active Directory SYSVOL folder Cluster database and Quorum disk If you click Options for System State, you can choose whether or not to include the System Files in the backup. By not selecting Backup system files you will see a red negation circle on the System Files icon, and they will not be included in the backup. The default is to include them. System files vary by system O/S and service packs. Usually there are several thousand of them. MS Windows makes a dynamic list of these DLLs when you include them in the backup. Including the system files allows you to recover from corrupted system files, or if you accidentally uninstall some service packs, or want to recover with a bare metal restore. It allows you to return to the state of the backup without having to reinstall the O/S from the installation kit, and then installing each service pack separately. You should include the System State files in a backup whenever you modify the Operating System. Note: If you have a customized Windows Server set up with certain services disabled, a System State or BMR Backup may fail. These VSS Writers are required on all healthy Windows XP/2003/2008 computers: COM+ REGDB Writer, Registry Writer, and System Writer. Page 64

66 Working with Jobs System State - NetWare If you select System State, you can choose NDS Backup Settings. Under NetWare 4.2 or greater, the user needs an ADMIN account, an account with security equal to ADMIN or an account with Supervisor rights to the [root] object of the NDS Tree. Enter a valid User name and Password under NDS login information. Select one of the three options for backing up the Novell Directory Service (NDS). You may choose to back up the entire NDS tree, or a subtree of the NDS. To back up the entire Novell Directory Service (NDS) tree, select Backup Entire NDS Tree. This backs up the NDS tree from the [root] object on down. This option requires that the NDS user specified have supervisor object rights to the tree root. Backup NDS for selected user backs up a selected user, which means that the backup commences from the partition root that the NDS user is on. Backup NDS from a specified location backs up any valid container or leaf object within the NDS tree. If the object is a container, then its descendant will also be backed up. This option requires that the NDS user have supervisor object rights to the object specified. Enter a location to start the NDS backup from. RSM Database Removable Storage Manager (RSM) facilitates communication among applications, robotic changers, and media libraries. It enables multiple app lications to share local robotic media libraries and tape or disk drives, and manage removable media within a single-server system. RSM uses a database to store its persistent data. To backup/restore RSM database the Agent uses a Local Drive Only Job (t he same one as used for files or System State backup) but it has a special selection option called RSM. Page 65

67 Working with Jobs This option is always available on the Agent Console backup/restore interface if RSM service on the client is installed and functioning. To back up the RSM database, check the RSM option. Note: Tape is not supported in version 6.7 (or above) of the Agent. If you upgrade to Agents 6.7or above, the upgrade will remove tape functions from the Jobs. But older Agents (not upgraded) will still support tape. A successful backup will contain the following entry in the backup log: RSM -I-0001 RSM backup completed A successful restore will contain the following entry in the restore log: RSM -I-0001 RSM restore completed. You will have to manually restart NtmsSvc service to complete the restore. After the system is restarted, the restore will continue and should complete with no errors in Windows Event Viewer. Note that the RSM option might turn red if you are editing an existing RSM Job and RSM service is currently not functioning on the client. Event logs Event log databases store events that are viewed by using the Windows Event Viewer program. The Event log service, located in Event Viewer, records events in the system, security and application logs. These events include services starting and stopping, users logging on and off and accessing resources. IIS Metabase The backing up of IIS involves the backup of the IIS Metabase. The IIS Metabase is a database similar in structure to the Windows Registry. The IIS Metabase is optimized for IIS and provides a hierarchal storage and fast retrieval of IIS configuration properties for Web sites, Virtual directories, FTP Sites, SMTP and NNTP sites. If you have IIS on your Server, you will see this source option. Terminal Services Licensing Database Terminal Service licenses are stored in a database that needs to be properly handled during backup/restore. If Terminal Service is installed and licensed on a Windows 2003 Server, you will see this source option. Windows 2003 Active Directory The Agent supports backups and restores of the Windows 2003 Active Directory. It supports restoration of replicated data where the target is the primary AD Server. Page 66

68 Working with Jobs Quick File Scanning Quick File Scanning reduces the amount of data read during the Backup process. Any file streams that are deemed unchanged since the last Backup, are skipped over. The default is to read files in their entirety. Disable Deferring Normally, when the Backup time window expires, all Jobs that have not yet been backed up are put on hold until the next Backup time window. This process is known as deferring. When deferring is disabled for a specific Job, that Job is backed up in its entirety, even if this means extending the Backup beyond the prescribed Backup time window. Backup Time Window You may set a time frame in which a Backup occurs. Any new files are deferred until the next Backup if they are not completed within the specified Backup window. This option can be used to help a Full Backup grow over a period of days or even weeks. The Backup Window must be at least fifteen minutes and no more than forty-eight hours. You may want to not use the Backup Time Window option, if you let the backup run from start to finish, and use Bandwidth Throttling. This allows the backup to still run (slower) during times when other users need the bandwidth. See Section of this. Encryption If you choose to encrypt your Backup, enter an encryption Password in this field. You must remember the password in order to Restore your data. Make sure you make a note of your password and keep it in a secure location. There is no way of recovering your data if you lose your password! Note that the password is case-sensitive. 1. From the Encryption dialog, select the desired encryption type. Choose from the following: None DES 56-bit Triple DES 112-bit Blowfish 56-bit Blowfish 128-bit AES 128-bit* AES 256-bit* * (128 bit AES is available when connecting to version 4.x and above Agents, Agent Console, and Vault. 256 bit AES is only available on 5.30 and above.) Page 67

69 Working with Jobs 2. If you choose to encrypt your Backup, you need to enter an encryption password and then verify the password. Choose Next. Local Catalog Files Local catalog files are created automatically. A catalog file is used to view and analyze your Backup files. Also, it is used to select your Backup files for restoration without having to load a tape or connect to a remote Server. A local catalog is created in a safeset subdirectory in the product s working directory with the name XXXXXXXX.cat, where X is the number of the Backup. The first Backup will be created with the number cat. Note: A catalog file cannot exceed the system limit of 4GBytes. This represents a catalog with 2 to 3 million files, or more. Create Log File/Detail Level Selecting this checkbox tells the system to generate log files for each Job executed. These printable log files contain the start-connect-completion and disconnect times, file names (i.e. the names of each file that was copied during a Backup process) and any processing errors. You can select the detail of logging to go from least to most: None, Summary, Directory, Files. More detailed logging creates larger log files, and is normally used only for troubleshooting problems. Changing the logging detail level only affects log files that will get created from that point on. It does not affect any previously created log files. Automatically purge expired log files only You have a choice of either automatically purging expired log files, or keeping a selected number of them before they get deleted (oldest one first). Automatic purging will delete the log file associated with a Backup, when that Backup (safeset) is deleted. Keep the last number of log files You may select a number here, whereby the system will keep that number of log files, which are associated with that Backup. When that number is reached, the oldest log file will be deleted to make room for the newest one. Note: The default choice to automatically purge expired log files means that when a safeset expires, the log files will also be deleted. If you want to delete log files before the s afeset expires, you can choose to keep the last X number of days of logs. In both cases you cannot keep the logs for longer than the safeset unless you copy them manually. Page 68

70 Working with Jobs Example log This is an example of a good log file sent from a normal backup, to show the meaning of these lines in the log. These s are optional. The actual (full) log file is found under the Job name in Agent Console. Note: In this example the line numbe rs have been added for this example only. Normally there are no line numbers. 01. Agent: EXAMPLE1 02. Job: BACKUP Retention: daily 04. Job start time: 05-Oct :30: Job end time: 05-Oct :46: Elapsed Time: 01:15: SafeSet: Errors encountered: Warnings encountered: Files/directories examined: 491, Files/directories filtered: 40, Files/directories deferred: Files/directories backed-up: 450, Files backed-up: 425, Directories backed-up: 25, Data stream bytes processed: 85,664,629,239 (79.78 GB) 17. All stream bytes processed: 85,752,048,987 (79.86 GB) 18. Pre-delta bytes processed: 6,649,699,821 (6.19 GB) 19. Deltized bytes processed: 830,521,523 ( MB) 20. Compressed bytes processed: 527,557,613 ( MB) 21. Approximate bytes deferred: 0 (0 bytes) 22. Reconnections on recv fail: Reconnections on send fail: 0 01: This is the name that you (i.e.: the Administrator) have assigned to this particular computer that will be backing up. Page 69

71 Working with Jobs 02. This is the Job name you have assig ned to a Job on this computer (Agent). There may be more than one Job associated with an Agent. Each Job will create separate s and log files. 03. This is the Retention schedule that you chose for this Job : The Job s start/end time is taken from the Agent. The Agent Console, or Vault, may be in a different time zone. (In this example, shows the GMT offset.) 06: Elapsed time (start to end) is the total time that the backup took. 07. Each successive Backup Job creates a new Safeset number, starting from This does not necessarily mean that there are X number of safesets on the Vault (like 389 in this example). Depending on Retentions (how many safesets are kept), there may be less Number of Warnings and Errors encountered. As well, the actual log files will have the warnings and errors listed. The Log Detail Level in Job Properties will give you different log files. With None you will still get a short log file, with Warnings and Errors. With Files and/or Directories you will see all the files and directories used for your Backup, plus the Warnings and Errors. With Summary you will see the totals of your Backup Job, plus the Warnings and Errors. Note that a Job may have Warning and Errors and still complete. Also note that if a Job is not successful (that is, it Fails for whatever reason) then the Backup is not completed. There is never a partial backup. It must complete and be committed before it can be called successful Files/directories examined/filtered: You select what Files and Directories you want to backup. Your selection may include nesting of multiple inclusions and exclusions. In these cases, the filtering will avoid traversing excluded Directories. 12. Files/Directories deferred: If you have enabled deferring, in Backup time options and chosen a Backup time window, the Backup will be deferred after that t ime, if it has not completed. It will continue at the (usually scheduled) next backup time. This line shows how many files and directories are yet to be backed up This shows the totals of Files/Directories that were backed up Data stream/all stream bytes processed. Depending on the Operating System, some files have other streams included, along with the data stream. (For example: Security streams, Extended Attributes, and Access Control Lists.) You cannot include/exclude these at Backup time, but you may be able to exclude them during a Restore. Note: If this Backup was an initial seed, then the numbers in lines 16 and 17 will be approximately the same. That is, all files will be looked at, and all blocks are new (no deltas). (See the partial log example below.) 18. Pre-delta bytes processed: The Agent has examined (with Quick File Scan) all the files and this number is the total size (bytes) of all files that have been flagged as changed by QFS. 19. Deltized bytes processed: If QFS finds any files that have changed (size, date, attributes), the Agent examines them further, looking for changed blocks. Only those changed (delta) blocks (in 32 K bytes) will be included in this current Backup. 20. These deltized bytes are then compressed and sent to the Vault. Notice that this number could be the same size, or smaller than the All stream bytes processed. 21. Bytes deferred: If the Backup could not complete in the time allocated, the remaining portion (Bytes deferred) will be inc luded in the next Backup time window. Note that if Backups keep getting deferred, with more and more data not being backed up, your system may not be protected properly. You should allow sufficient time and resources for the backups to complete Reconnections on Receive/Send Fail: If you lose your communication link (to the Vault) temporarily while a Backup is running, the system will recover and continue, as long as the backup is not too lengthy, and there are not too many failures. You can change parameters to decide how long to wait, and how many times, before a Backup will fail. Page 70

72 Working with Jobs This exam 16. Data stream bytes processed: 108,715 ( KB) 17. All stream bytes processed: 108,903 ( KB) 18. Pre-delta bytes processed: 108,903 ( KB) 19. Deltized bytes processed: 108,903 ( KB) 20. Compressed bytes processed: 66,320 (64.76 KB) Finished The last screen in this Wizard gives you three choices regarding what to do with this Job that you have created. Run the Job immediately The Backup Job will be saved, and the Backup Wizard will be launched. This is also called an ad hoc Backup, a special one-time Backup for a specific reason. The Job is saved, though, and may be re-used or scheduled. You may also take a scheduled Job and run it ad hoc (immediately). Schedule the Job This calls up the Schedule List screen to allow you to schedule the Job. See the section on Schedule List. Exit without running the Job You leave the New Job Wizard, and still keep the Job. You can come back afterwards to run it directly (ad hoc), or schedule it for later. Job Properties The Job Properties function allows you to change the parameters that were previously created with a new Job. Choose File > Properties (with a Job selected), right -click (with a Job selected), or use F2. Destination This displays the name of the Vault that registered this Job. It is the Vault that will receive the Backup (if, in the Backup Wizard - Destination a Vault was selected.) Options Retention Choose a retention type from the drop-down list. You may choose a pre-defined retention (Daily, Weekly or Monthly) or you may choose a retention definition that you create (see Schedule List ). The pre-defined retention types are as follows: Page 71

73 Working with Jobs Daily: 7 copies of the Backup safeset will be stored online for 7 days. Weekly: 5 copies of the Backup safeset will be stored online for 31 days. Monthly: 12 copies of the Backup safeset will be stored online for 365 days. Compress File data Choose a Compression type: None, Minimum, Normal, Better, Maximum. These choices allow the user to optimize the volume of data sent against the speed of transmission. In some cases it might be better to take the time and CPU cycles to compress the data before sending it at a slower rate, as opposed to not compressing it and sending it at a faster rate. Also, the more the data is compressed, the smaller will be the footprint (size) when it is stored on the Vault. Compression types available are: NONE Do not compress any data. MINIMUM Minimize CPU consumption, possibly at the expense of a larger safeset size. NORMAL Balance CPU consumption against safeset size. BETTER Minimize safeset size, possibly at the expense of extra CPU consumption. MAXIMUM Always minimize safeset size, regardless of the amount of CPU consumption required. Advanced This allows you to select Quick File Scanning, Disable Deferring, and Backup Time Window options. Logs This allows you to select Log File Detail Level, Automatically Purge Expired Log Files, and Keep Log Files.. Source Select the Data Files checkbox to open the Include/Exclude panel. Use this option to specify which files will be backed up in this Job. Bare Metal Restore is an option that captures the information necessary for an System Restore. The Bare Metal Restore option is mutually exclusive of the System State option. Selecting one will disable the other. Select System State to add system specific information to your Backup. All system files included in the System State Backup are listed in the lower pane of this panel. Select RSM database to add information about the Removable Storage Manager. The Event Logs option backs up the Windows Event Logs. Event log databases store events that are viewed by using the Windows Event Viewer program. To back up all Event logs currently available on the system, select the Event Logs checkbox. Encryption If you choose to encrypt your Backup, enter an encryption Password in this field. You must remember the password in order to Restore your data. Make sure you make a note of your password and keep it in a secure location. There is no way of recovering your data if you lose your password! Note that the password is case sensitive. See section for more information. Page 72

74 Working with Jobs Tape Tape is not supported in version 6.7 (and above) of the Agent. If you upgrade to Agent 6.7 or above, it will remove tape functions from the Jobs. But older Agents (not upgraded) will still support tape. Monitoring Jobs After starting an immediate Backup or Restore, the Agent Console application begins to monitor the progress of the Job. The progress display indicates the activity being performed. During an immediate Backup or Restore Job, file names are displayed with a percent -completed indicator. The percent-completed indicator is only displayed for larger files. Completion status is provided so that the Agent Console application is aware of whether the Job was successful or not. Viewing Process Information The Process Information dialog (Job status) can be viewed while a scheduled Job is running. To view the Process Information while a Job is running: 1. Expand the target Agent. 2. Click on the Processes folder. 3. Click on the target Job. This opens the Process Information dialog. The progress of the Job can be viewed from here. Stopping a Job A scheduled Job can be halted while the Job is running. To stop a Job while it is running: 1. Expand the target Agent. 2. Click the Processes folder. 3. Click the target Job. The Process Information dialog opens. 4. Click Stop Process. Removing an Entry from the Process Folder When a command is completed, its status is displayed in the Processes folder and the Stop Process button changes to a Delete Entry button. Jobs are visible under the Processes folder within the Agent Console application for up to an hour after their completion. This provides an opportunity to check the command s final status without having to look at the log files. All entries are automatically removed after an hour, but can be manually deleted at any time. To remove an entry: 1. Expand the target Agent. 2. Click on the Processes folder. Page 73

75 Working with Jobs 3. Click on the target Job. The Process Information dialog opens. 4. Click the Delete Entry button. Page 74

76 Working with Scheduled Entries Working with Scheduled Entries In order to perform regular automated commands, the Agent includes an integrated scheduling feature. Backups and synchronizations can be scheduled for any or all of your Agent Jobs from the Agent Console application. New schedules are created using the Schedule Wizard. This allows many useful pre-defined options that support the most common scheduling scenarios. Additionally, customized commands and time schedules can be entered to help support more sophisticated scheduling requirements. Existing schedules can be modified from t he Schedule Entry dialog. Each Agent system monitors the Backup schedule file for changes and prepares to initiate scheduled commands at the specified times. This Scheduler runs as a service under Windows, as an NLM under NetWare and as a daemon under Unix. This program is started or loaded at system start time on all Agent systems. To start: Tools > Schedule Entries, or right-click on the Agent. Schedule List This list shows a summary of currently scheduled entries. To view or modify an entry, double-click the entry or select the entry and click the Edit button. Each entry is summarized using the following headings. Command: Command scheduled for execution Job: Name of Job for this command Retention: Name of retention for this command Time: Scheduled time to execute this command Days: Scheduled days to execute this command Creating a New Scheduled Entry You can add a schedule entry when you are creating a Job. You can also add a schedule entry directly to the Schedule file. 1. With the target Agent highlighted, click the Schedule file. The Schedule List dialog opens, displaying all scheduled Jobs. 2. Click the New button to launch the Schedule Wizard. The Wizard guides you through the process of creating a schedule for a specific Job. Command Panel The Command panel of the Schedule Wizard offers a selection of actions to schedule: Backup - Create a schedule to back up data for a specified Job. Synchronize - Create a schedule to update local catalogs with Server information for a specified Job. Page 75

77 Working with Scheduled Entries Custom - Advanced users can create a schedule to run custom commands. Custom commands can be any third party executable. For Windows, such a command could be: > vv Backup Jobname </param=parameter.files> (Under NetWare, the custom commands option is grayed out.) Job List The Job List panel of the Schedule Wizard presents the list of Jobs in your current workspace. Select the Job you wish to perform a command on, and click Next. Retention Panel There are three pre-defined retentions: Retention Name Days Online Copies Online Days Archived Daily 7 7 OFF Weekly 31 5 OFF Monthly OFF The number of days online defines the number of days a safeset is kept on the Vault. Once the expiry date is reached, a safeset is deleted. Online storage is used to store data so that it is readily accessible. When data is stored online, restoration operations are initiated immediately without any operator intervention on the Vault side. The number of copies online indicates how many copies of the Backup safeset are stored online. It functions in a first in/first out manner. Once the number of copies is exceeded, the oldest copy(s) are automatically deleted until the actual number of copies matches the definition. The number of days archived indicates how long the data is stored offline. Archive storage is used to store data offline for long periods of time. This data is not immediately accessible since it is stored on tape and in a secure location. The time required to Restore from archive media can be lengthy (from hours to days). Typically, only long-term data archives are stored offline. The parameters for archived data are from 365 to 9999 days. Assuming that at least one successful Backup has been completed for the Job, there will never be less than one copy of its safeset online. This is true even if all retention settings for expiry conditions have been met, and the Job definition is deleted from your system. Deleting the Job does not affect data on the Vault. Only your Service Provider can remove Jobs and their associated data from the Vault. This is a safeguard against accidental or malicious destruction of data. Note: Days Online and Copies Online work in conjunction. So, both conditions have to be met before any backups are deleted. For example, if both Days and Copies are 7, then there can never be less t han 7 backups. If Days goes over 7, there will still be 7 Copies. If Copies goes to less than 7, there will still be 7 Day s worth. It must be over 7 Days with more than 7 Copies before any are expired. Page 76

78 Working with Scheduled Entries Options Panel Users can choose Quick File Scanning from the Options panel of the Schedule Wizard. This feature is used to reduce the amount of data read during the Backup process. Any file streams unchanged since the last Backup are skipped. If this option is not selected, files are read in their entirety. You may also enter a Backup time option. This is the duration of time you want your Backup to run. The default Backup window is eight hours. The Backup will terminate at the end of this time period, regardless of whether the process is complete or not. Any files not backed up are deferred until the next scheduled Backup. When Disable Deferring is selected for a specific Job, that Job is backed up in its entirety, even if this means extending the Backup beyond the prescribed Backup time window. Command Cycle The Command Cycle panel of the Schedule Wizard enables you to define the frequency of your scheduled command. You have the option of scheduling By Days of the Week (Weekly), By Days of the Month (Monthly) or creating a Custom command cycle. Selecting a Weekly command cycle means the entry will execute on the same day(s) every week. Selecting a Monthly command cycle means the entry will execute on the same day(s) every month. If you choose to create a Custom command cycle, follow the format indicated at the top of the Custom Date/Time panel. Custom Date/Time If you elected to create a custom command cycle on the Command Cycle panel, you are presented with the Custom Date/Time panel. You may specify your own custom schedule by entering time and date information. A custom schedule entry requires a specific syntax that must be adhered to in order to function properly. Use the following format to ent er your custom schedule data: min/hour/day/month/dow (days of the week). Values: Minutes (0-59), Hours (0-23), days (1-31), months (1-12), dow(0-6, 0=Sunday) Keywords: * means every time, Last means last day of the month. 0/18/*/*/1-5 This example tells the backup to start at 6pm on Monday through Friday. Weekly/Monthly Panel This panel is used to define the days of the week or days of the month for the appropriate noncustom command cycle. For a Weekly cycle, select the days of the week on which the entry should execute. For a Monthly cycle, enter the days of the month on which the entry should execute. Start Time This field is used to define the time of day the scheduled Job will commence. To schedule more entries on the same day, create a separate schedule entry at a different time of the day. Page 77

79 Working with Scheduled Entries The software displays time in 12-hour (AM/PM) mode or 24-hour mode. The time mode displayed depends on the time mode set on your computer. To change the time mode on your computer, select Regional Settings from the Control Panel and click on the Time tab. To select 24-hour mode, use this format: HH:mm, where HH is 0-23 and mm is 0-59 To select 12-hour mode, use this format: hh:mm, where hh is 0-12 and mm is Select either the AM or PM radio button. Editing a Scheduled Entry To edit a schedule: 1. Select an Agent and click the Schedule file. 2. Click the target schedule entry. 3. Click Edit. The Schedule Entry panel appears, displaying the details of the selected schedule. 4. Edit the information. 5. Click OK. 6. Click OK. Removing a Scheduled Entry Select an existing schedule from the list, and click the Remove button. You will be prompted to make sure that you want to permanently remove this schedule. Enabling a Scheduled Entry 1. Select a disabled entry on the Schedule List. 2. Click the Enable button. The entry displays a scheduled symbol to the left of the entry. 3. Click OK. Disabling a Scheduled Entry 1. Select an enabled entry on the Schedule List. 2. Click the Disable button. The entry displays a halted symbol to the left of the entry. 3. Click OK. Prioritizing Scheduled Entries The Scheduler uses a prioritization scheme that permits you to override entries under certain circumstances. If the following conditions are met by the schedule entries, the Scheduler will only execute the highest prioritized entry: Page 78

80 Working with Scheduled Entries Both commands must start with "VV" or "VV.EXE". Both command verbs after the "VV" or "VV.EXE" must be the same (for example, "Backup"). Both Job names must be the same. Both execution times must be the same. Note: The VV.exe component on the Agent performs Backup and Restore functions to the Vault. The priority of the entry is determined by the order in which the entries reside in the Schedule.cfg file. The first entry is given a higher priority over the entries that follow it and meets the conditions specified above. If two entries conflict, the entry that is higher on the list takes priority. The entry with lesser priority does not run and is rescheduled. See the example below. To move an entry up, use the Up button. To move an entry down the list, use the Down button. Page 79

81 Installation and Troubleshooting Example 1 The following entries meet all prioritization conditions even though the retention parameters are different (day versus week): both end with some form of "vv", the verb is the same "Backup" and the Job name is the same "full". When the two Backups conflict (this occurs if the third day of the month is ever a Monday, Wednesday or Friday), the second one is rescheduled to its next available time. 0/1/3/*/* vv Backup full /retention=day 0/1/*/*/1,3,5 c:\agent\vv.exe Backup full /retention=week Example 2 The following entries meet all prioritization conditions as both end with some form of "vv": the verb is the same "Backup", and the Job name is the same "system". When the two Backups conflict (which occurs on the LAST day of every month), the second entry is rescheduled to its next available time. 0/23/LAST/*/* vv Backup system /retention=year 0/23/*/*/* vv Backup system /retention=week Scheduler Log Files The Scheduler creates a log file during its execution. As commands are scheduled and executed, each activity is logged into one of three VVAgent -#.log files located in the Agent Console Directory. The Scheduler will w rite to the first file until it reaches about 32K in size. At this point, it will write to the second file. When all three files reach capacity, the scheduler deletes the first file and begins writing the log again. The current log file version is the one with the latest modification date. Effects of Time Changes The Scheduler checks the Server clock and determines if it has been changed by more than seventy-five minutes. A change forward or backward within seventy-five minutes would typically be as a result of Daylight Savings time or a simple clock adjust ment. Example 1 If there is a change greater than seventy-five minutes, all scheduled entries are re-scheduled to their next available times. Example 2 A Job is scheduled to run at 1:15 a.m. At 1:00 a.m., the Server clock is changed to 2:00 a.m. The Job scheduled for 1:15 a.m. then runs immediately. This happens because the time change is within seventy-five minutes and constitutes a daylight savings time change or a clock adjust ment. Example 3 A scheduled Job runs at 1:30 a.m. At 2:00 a.m. the Server clock is changed to 1:00 a.m. The Job will not run twice. When the schedule file is reloaded, it only updates the next scheduled time of each existing entry. Page 80

82 Installation and Troubleshooting Time Zones Scheduled Jobs use the time of the local machine (Agent). If Agent Console is in one time zone, and the Agent is in another, the starting time of the Job depends on the local machine s clock. The log files, safeset creation and last modified dates also show the local machine s time. These times also display the offset (difference) from Greenwich Mean Time. In the example, means the time zone is 4 hours behind GMT, which is defined as zero. Time Zone offset from GMT. Page 81

83 Working with Backups Working with Backups You can run a Backup from the drop-down menu under Actions, or by selecting the Backup icon in the Toolbar menu. Backup is a process that copies data to a Vault, disk, or tape. A Backup may be scheduled or run ad hoc, which is a Backup not on a scheduled time. Usually, it is a one-time Backup, for a specific reason. You can either run a regularly scheduled Backup Job as a special ad hoc Backup, or create a new Job to be run immediately. A full Backup copies, in whole, all files and directories. This includes user data, system data, and applications/programs. A first Backup (initial seeding) is a full Backup. Subsequent deltized Backups are also regarded as full Backups. That is, you can do a complete Restore from a deltized Backup. Note: It is not recommended to back up the Agent or Agent Console installation directories. These directories should be excluded from any backup Jobs. Seeding Seeding is the process of getting an initial Backup to a Vault. From then on, any changes to the data are applied to that initial Backup as deltas (changes). This results in each Backup being a full Backup. You do not have to apply any Differential or Incremental changes to do a Restore. Seeding may be accomplished across the network (LAN/WAN) or you may want to create a disk or tape to be physically transported to the Vault, and imported. Seeding with Deferring The Agent has several options to specify network reconnection/retry window (Vault specific) and Backup time window (Job specific). Depending on how these values are set, you may see errors such as the deferring failing because the Vault process is no longer available. Retry connection attempts after provides the maximum time (24 hours) that your system should try to re-establish connection to the Vault before terminating/failing the Job. This value also specifies how much time the Vault is waiting for the Agent before it terminates the Job from the Vault side. Try to reconnect every provides the number of seconds (3 to 3600) to delay between consecutive retries to re-establish connection to the Vault. Backup Time Window defines a window of time in which to perform the backup procedure. Choosing this option will limit the backup time window to the period of time specified. Any new files that are not completely backed up within the available window will be deferred until the next backup session. If the Backup Time Window is less than Retry connection attempts after then the value of Backup Time Window will be used to specify the runtime value of Retry connection attempts after value. Example A Job is configured with Retry connection attempts after = 3 hours, Try to reconnect every = 3 minutes and Backup Time Window (deferring time) is 5 minutes. Page 82

84 Working with Backups As the Backup Time Window is less than Retry connection attempts after, the new Retry connection attempts after value will be 5 minutes. This value causes the Vault to wait for a backup Job to finish for up to 5 minutes. The Vault log will show a message such as: VVLT-I Agent override for client reconnection settings: attempts = 1, timeout delay = ms Once the Agent stops the backup (due to the defer window), it continues scanning the file system to find or check deferred files for the next backup. It may take more than 5 minutes to complete (it depends on the input file specification, Job type, hard drive speed and other factors). As a result, the Vault terminates the backup session after 5 minutes and the Agent is not able to complete the Job. Backup Wizard The Backup Wizard takes you through the process of choosing: Destination Backup type and options Retention types Other options Before starting a backup, it is assumed that you have correctly configured an Agent and Job (see the previous chapters in this manual). When you start the Backup Wizard, you may not see the Welcome screen. It can be turned off by clicking on the "Skip this screen in the future" button. It can be turned on again, by going Back from the second screen, and clicking the button Off. Destinations Choose from a Vault or directory on disk. Note that if you choose Directory on Disk it will force a re-seed (complete Backup image). If you choose a Vault, and want to Backup Now, it will start the Backup immediately, and shows Processing Information. Otherwise you can choose the Next button. Vault This references the Vault that was configured with this Job. If the destination is a Vault, you do not see a backup type selection (by default it is always Full). Click Next to go to Retention Scheme. Directory on Disk Choose Select Directory [ ] and choose a Directory (for the destination). Note: For a restore from a Directory on Disk to work properly, you must first Import the safeset into the Vault (from the Directory on Disk location). You then must Export it back out to the same (or different) Directory on Disk location and then you can Restore it back to the Server, just like a Restore directly from a Vault. Click Next to go to Retention Scheme. Page 83

85 Working with Backups Retention Scheme Your choices for the retention are Daily, Weekly, Monthly or another retention that you have previously defined. The retention settings manage the lifecycle of the data. The settings specify if the Backup is stored online or archived. They also specify the length of time the Backup is stored and the number of copies of the Backup that are stored. Options This allows you to choose Quick File Scanning or Backup Time options. See Jobs - Options. Finish Click Finish to start the Backup immediately, or use Cancel or Back. Page 84

86 Working with Backups Windows Registry The Windows Registry (or Local Registry) stores virtually all of the custom data that Windows uses. Every time a program starts and every time Windows performs an operation, the Registry fills in all of the variables with your computer s custom settings. If you select System State the Registry will be backed up. Active Directory Active Directory is a Windows directory service designed for distributed computing environments. It allows organizations to centrally manage and share information on network resources while acting as the central authority for network security. In addition to providing comprehensive directory services in a Windows environment, Active Directory is designed to be a consolidation point for isolating, migrating, centrally managing, and reducing the number of directories that companies require. If you select System State the AD will be backed up. NDS In NetWare, the NDS is a multi-platform, distributed database that stores information about hardware and software resources that are available within a given network. The information may be shared by several servers in the form of a tree. If you select System State the Novell Directory Service will be backed up. You must have the proper credentials (system rights) to be able to do this. Locked/Open Files Files that are locked are busy (in use) by the system or another application. Files that are locked may not be backed up properly (if at all). To ensure open or locked files are backed up properly VSS is used. Older Agents and Jobs can use products such as Open Transaction Manager or Open File Manager can be used with the backup applications. Backup after Re-registration If you have re-registered a computer, the Job credentials are intentionally not moved across to the new computer. This means that you cannot use that Job for a Backup unt il you have successfully re-entered the proper credentials. To do this, you must Edit the Job (in Agent Console), enter the proper credentials, and save the Job. Page 85

87 Working with Restores Working with Restores You can Restore from any Backup that you have created. Restores must be run manually, from the GUI. If a Backup has a password on it for encryption, you must know that password. It is not kept anywhere on the system. Restores can be either a complete file system, or one or more files and/or directories. You can search, select and restore from multiple Backup catalogs, from a single Restore Wizard session. Previous versions of Agent Console only permitted the search and selection of files from a single backup catalog. Restores are not scheduled. You can run multiple individual Restores at the same time. Each one will start a new process, which you can monitor. Bare Metal Restores A bare metal Restore refers to a computer system that starts with an original, new state, with nothing (O/S, apps, or data) stored on its disks. This may be the case after a system hardware crash, where new disks are installed. The Restore then recreates everything back on the system. This is not the same as re -installing everything, as with this, you would lose any customization and parameters of applications, system, and service packs. There are two possible scenarios that would follow to Restore your Backups from a Vault. The first would be used to Restore everything using network communication lines. You would reinstall your operating system and then the Client Agent/Agent Console. With the Client Agent, you would Restore your data by using the Synchronize option to Restore your catalogs from the Vault. The second option is to request that your Backup be sent to disk and delivered, along with a copy of the Agent Console and Agent software. After restoring (re-installing) your operating system and Agent Console software, you would recover directly from local media. BMR with System Restore A bare- metal restore (BMR) is not a menu choice in the Agent Console program. Rather, it is a way of restoring a complete Backup to a new System. System Restore is a separate, licensed application used to do a Bare Metal Restore. BMR with System Restore will completely restore a Windows Server 2008 system. This is different from using the Agent and System State to do a Bare Metal Restore, as mentioned above. See the System Restore User for more information. You would want to do this BMR, for example, if a System has crashed, and the disk has been replaced. Now you want to recover all the System and User data back to that disk. Note that reinstalling the O/S and applications and then the data is possible (as mentioned above), but you may not be able to recreate the exact state of the System that you would get with a Restore of a full drive Backup that included data files, System State, and System Files. Bare Metal Restore is a licensed option (Agent version 6.4 and greater) that captures the information necessary for the System Restore (ESR) application. System Restore is a separate application used for bare metal recovery of systems in case of a disaster. Page 86

88 Working with Restores Note: Bare Metal Restore type backup safesets (which can be used by "System Restore" to perform a Bare Metal Restore for DR purposes) can also be used via Agent Console to restore individual files and folders in the same manner as regular Agent backup safesets are used. Operating System Independence You can Restore data independent of the operating system. NetWare data can be Restored to Windows and Windows data can be Restored to NetWare. However, there are limitations with this kind of action. Specifically, you can only Restore the data stream and the basic file information attributes, such as create date, modify date, etc. Security, extended attributes and alternate data streams are not Restored properly. Both recreating catalogs and restoring files are described below. Restoring from CD, DVD, or USB The Agent allows restores directly from a CD or DVD drive, or other media such as USB drives, without having to copy safesets to the hard disk first. CDs typically can store around 700 MB, while a DVD will store about 4 GB. There are several ways the safesets can be stored on the media: a single SSI on a single CD/DVD. SSI files that are divided into many SSI files with a fixed length, but the whole set fits on a single medium. CDs or DVDs that contain a single backup that spans more than one media. The user specifies Directory on Disk and then browses to the folder containing the SSI file. The SSI file on the CD/DVD must correspond correctly to the safeset number that is specified under Restore from the following safeset. If not, Agent Console will show an error when the restore operation begins, saying that the medium is not the right one. When the Restore operation begins it will request for a certain CD/DVD to be mounted in the drive, if there is no media mounted. If a second (or more) media is required, you will be prompted. You will not be prompted if the requested SSI is on a CD/DVD that is already in use (i.e.: mounted). If there are multiple SS I files on the same DVD, you will be prompted for a selection. About the Restore Wizard You use the Restore wizard to complete these tasks: Select the source for Restores Enter the password if the backup is encrypted Select Restore files Enter the Restore destination Select other Restore options Page 87

89 Working with Restores Selecting a Source Choose a device from which to Restore: Vault or disk. Cross Catalog Searches You can search through all available catalogs when restoring files, without switching Restore Wizards. In the Restore Wizard, when you select a source, you can specify a single safeset, or a range of safesets. Since cross catalog searches are done on all available safesets, all corresponding catalogs are loaded in case they are not present. The number of safesets could be high, so in case too many catalogs fail to load, you have the ability to "break" the search and display only the files that were found so far. You cannot select System State when restoring from multiple safesets. If you use renaming on Restores, it will only allow you to rename incoming files. Restores are performed in order of older to newer ones. Vault If you choose Vault, you must select a single safeset from the drop-down list, or choose a range of safesets. Directory on Disk If you choose directory on disk, you must enter the name of, or browse to, a directory, and then select a safeset from the drop-down list, or choose a range of safesets. Note: To restore from disk, you must request your vault service provider to export your requested safeset. Backups that were done directly to disk cannot be restore from directly. Choose a Safeset, or Range of Safesets All the safesets that were created in Backups, and that are still valid, are shown here. For a single safeset, you must know from the Job, date and safeset properties, which safeset you want to Restore. Page 88

90 Working with Restores For a range of safesets, you may choose a "from" and "to" in the two dropdown lists, to show multiple catalog entries. Note that the "from" must be earlier than the "to", or you will see a message: "In the range of safesets the "from" cannot exceed the "to"." Encryption Password If you had used an encryption password on the Backup (see Section 4.2.5) you must enter it here, to be able to perform the Restore. The password is not recorded anywhere on the Backup, or the system. It is the user s responsibility to retain this password. Note that the password is case sensitive. Select Restore Objects You may select some or all of the files/directories that were backed up with this Job. Data files add, include/exclude Agent Console distinguishes between full and partial directory Backups because, if the entire directory was not backed up, hidden file data such as security and reparse information is not backed up. To include files, click the Add button, select your files and then click the Include button. When prompted to confirm the inclusion, click OK. To exclude files, click the Add button, select your files and then click the Exclude butt on. When prompted to confirm the exclusion, click OK. If you are not sure which directory your files are in, you can search the Backup catalog for the files you want to Restore. The search feature allows wild-card searches using the asterisk (a wildcarded string) and question mark (a wild-carded character) characters. Page 89