EVault Software Agent 7.1 for Microsoft Windows User Guide

(1)

EVault Software

Agent 7.1 for Microsoft Windows

User Guide

(2)

Revision: This manual has been updated for Version 7.1 (December 2012). Software Version: 7.10

EVault, A Seagate Company, makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, EVault reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of EVault to notify any person of such revision of changes. All companies, names and data used in examples herein are fictitious unless otherwise noted.

No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval System or translated into any language including computer language, in any form or by any means electronic, mechanic, magnetic, optical, chemical or otherwise without prior written permission of:

EVault, A Seagate Company c/o Corporation Trust Center 1209 Orange Street

Wilmington, New Castle Delaware 19801

EVault, EVault Software, EVault SaaS, and EVault DeltaPro, are registered trademarks of EVault Inc. All other products or company names mentioned in this document are trademarks or registered trademarks of their respective owners. Acknowledgements: Two encryption methods, DES and TripleDES, include cryptographic software written by Eric Young. The Windows versions of these algorithms also include software written by Tim Hudson. Bruce Schneier designed Blowfish encryption.

“Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright 2001-2006 Robert A. van Engelen, Genivia Inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.”

The EVault Software Agent, EVault Software CentralControl, and EVault Software Director applications have the encryption option of AES (Advanced Encryption Standard). Advanced Encryption Standard algorithm (named Rijndael, pronounced “Rain Doll”) was developed by cryptographers Dr. Joan Daemen and Dr. Vincent Rijmen. This algorithm was chosen by the National Institute of Standards and Technology (NIST) of the U.S. Department of Commerce to be the new Federal Information Processing Standard (FIPS).

The EVault Software Agents and EVault Software Director applications also have the added security feature of an over the wire encryption method.

(3)

Agent 7.1 for Microsoft Windows User Guide Contents

The Director vault, Agents, and CentralControl are the primary components of the data protection application. You use these components to back up and restore system and file data from your network computers to a local or remote vault. These applications protect your data without the need for tape devices or other non-disk backup media.

(9)

1.2 Windows Agent Features

Here are some recent Agent features:

• The Agent now has the ability to share 2007/2010 Exchange VSS DR backup safesets for use with the Granular Restore for Microsoft Exchange application. Once a DR safeset is shared, the Granular Restore application can be used to restore individual mailboxes and messages to a .pst file. This eliminates the need to have additional MAPI jobs, thus reducing your storage costs and backup demands.

• Backup and Restore support for Windows Server 2012.

• The 2012 SQL Plug-in uses VSS for improved performance and functionality (legacy VDI still supported). o This feature is now supported on a Windows Cluster.

• Backup and Restore support for SQL Server 2012.

• ReFS for data files and folders are supported. ReFS Metadata and attributes are not supported.

• The Agent now supports Oracle 64-bit backup and recovery.

• Supports Bare Metal Restore (BMR) type backup Jobs, including support for GUID Partition Table (GPT) drives and OEM partitions. For full BMR recovery, EVault System Restore 1.50 or newer is required.

• To improve performance in a replication environment, the Agent supports backup and recovery of data on GPT drives.

• French and German language support has been updated on Web CentralControl.

• To complete backups and restores on 64-bit Agents with the Microsoft Exchange 2010 DR Plug-in, you must install EVault Software Director version 6.0 or newer. In addition, you must be using Windows CentralControl version 6.80 or newer.

• The Microsoft Exchange 2010 DR Plug-in supports Database Availability Groups (DAGs). Microsoft Exchange 2007 and Microsoft Exchange 2003 are not supported.

• The Microsoft Exchange 2010 DR Plug-in does not support MAPI backups.

1.3 About the Windows Agent

You install the Agent software on every computer that you want to back up. You use Windows or Web

CentralControl and the Windows Agent to back up data from network computers to a remote Data Protection vault. The applications provide an automated, unattended method for protecting your valuable computer data without using removable backup media devices.

The Agent includes these components:

• VV.exe – Performs backup and recovery functions in conjunction with a vault.

• VVAgent.exe – Used for scheduling, configuration, and communication with Windows CentralControl. It runs as a Windows Service on supported Windows operating systems.

• BUAgent.exe – Used for scheduling, configuration, and communication with Web CentralControl. It runs as a Windows Service on supported Windows operating systems.

(10)

Each computer that you want to back up must meet these requirements:

• The Agent software must be installed and running.

• The computer and the Agent must be connected to a network.

• The Agent must be able to access a vault.

Each backup is considered a full backup because you can use it to perform a restore without using incremental or differential backups. The Agent runs on the computer as a background service. It starts automatically when the system starts.

You use CentralControl to set up Agents, Jobs, scheduling, and monitoring. The backup data moves from the Agent computer to the vault computer. Backup data does not go through CentralControl. To receive Agent commands and data, you must create an account for the Agent on the vault.

After you configure the Agent and create schedules, backups occur automatically. You do not need to keep Windows CentralControl running. Use Windows CentralControl to configure the Agent, check the progress of backups, and to view error logs.

1.4 About CentralControl

You use Windows or Web CentralControl to manage all of the computers that are running the Agent software. You do not require a license to use CentralControl. However, you must have Administrator privileges to create and modify backups and manage restores.

Web CentralControl runs on a web server and has the same functionality as Windows CentralControl. However, it uses an Internet browser to connect to the network.

It is recommended that you use only one type of CentralControl to manage an Agent.

1.5 About EVault Software Director

The primary purpose of the Director application is the management of storage pool data at a remote secure vault location. Data is sent from the Agent to the Director over a Wide Area Network (WAN) or Local Area Network (LAN) connection, the Internet, or imported from media.

The Director does not interact with CentralControl. CentralControl communicates with and manages the remote Agents.

1.6 Supported 32-Bit Agent Plug-ins

Some ins are optional and require an extra license. When you install the Agent, you can install the Plug-ins and activate them later through the Repair or Upgrade option.

(11)

The 32-bit Agent supports these Plug-ins:

• SQL Server

• Exchange DR and MAPI

• SharePoint

• Cluster Support

• Oracle

If you install the Oracle Plug-in, you must install the Oracle Instant Client for Windows after you install the 32-bit Agent. The Oracle Instant Client for Windows is available on the EVault Support website (csp.EVault.com).

1.7 Supported 64-Bit Agent Plug-ins

You can install a 64-bit Agent on a supported 64-bit Windows operating system. For a list of supported operating systems, see the release notes.

You use the same CentralControl to control 64-bit and 32-bit Agents. When you check the Agent status after you configure a 64-bit Agent, the operating system version is listed as one of the supported platforms.

Some ins are optional and require an extra license. When you install the Agent, you can install the Plug-ins and activate them later through the Repair or Upgrade option.

The 64-bit Agent supports these Plug-ins:

• SQL Server

• Exchange DR and MAPI

• Cluster Support

• SharePoint

• Oracle

When you connect the Agent to a vault version 5.53 or newer, the vault supplies the license automatically. See the CentralControl Operations Guide and the Plug-in guides for more information about licensing and

installation.

1.8 Plug-in Behavior

The Agent treats a Plug-in as a separate component. This is the behavior when a component fails:

• One-component backup – When the component fails, the Job fails.

• Two-component backup – When one component fails, and another finishes (with or without errors or warnings), the Job finishes successfully. If both components fail, the Job fails.

(12)

1.9 About the Exchange Plug-in

You can use the Exchange Plug-in for full Microsoft VSS disaster recovery (DR) of Microsoft Exchange databases. You can also use it to back up and restore specific mailboxes and folders with MAPI.

Note that the Agent now has the ability to mount and share an Exchange DR backup safeset for use with the Granular Restore for Microsoft Exchange application. Once a DR safeset is mounted/shared, the Granular Restore application can be used to browse Exchange mailboxes, emails, attachments, contacts etc… which can then be selected as desired and restored as .pst file(s). This new ability eliminates the need to run MAPI backups, thus reducing your storage costs and backup demands.

1.10 About the Oracle Plug-in

You can use the Oracle Plug-in to back up Oracle databases.

Oracle Instant Client support is supplied as a separate component from the Plug-in. In some cases, you must install it separately. The application will provide a warning to install Instant Client support if it is not already there.

The Oracle Instant Client kit (available from csp.EVault.com) will only place the Instant Client in the installation directory of the Agent. If the Agent has not already been installed, the installation process will terminate gracefully.

1.11 About the SQL Server Plug-in

You can use the SQL Server Plug-in to back up a Microsoft SQL Server database. See the Agent release notes for supported combinations of SQL versions with Windows operating systems as well as supported cluster information.

1.12 About the Cluster Support Plug-in

The Cluster Support Plug-in allows you to configure an Agent and Jobs on the Virtual Node of the Cluster. This allows Jobs to redirect the workflow to the active node when a failover happens on the Cluster.

For more information on configuring and working with the Cluster Support Plug-in, see the section "Working with the Cluster Plug-in" in this document as well as the Agent release notes.

(13)

1.13 About the SharePoint Plug-in

You can use the SharePoint Plug-in to complete brick-level backups and restores of SharePoint items including webs, lists, libraries, folders, and documents. This granularity allows you to complete backups and restores of the entire site, including individual document versions. You can restore a document to the file system as a document or as a document version.

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 SharePoint Plug-in installs directly on the Agent computer.

1.14 Additional Resources

Release notes for this product are available from your service provider. Release notes contain the most current information about the product, including an overview of new features, any known defect (bug) fixes

incorporated since the last release, and a description of any known issues.

The Web CentralControl application provides online help that contains information from this manual, as well as information about other products.

(14)

Agent 7.1 for Microsoft Windows User Guide Installing and Modifying the Agent

2 Installing and Modifying the Agent

This chapter provides information and procedures for installing the Agent on a computer with a supported Microsoft Windows operating system installed. For a list of the supported operating systems, see the Agent release notes.

To configure and manage the VVAgent, you must install the Web or Windows CentralControl application on a supported Microsoft Windows computer and make it accessible to the Agent.

If you are using vault replication, you can configure the Agent to use alternate Vaults. To assign an alternate vault, you modify the list of alternate vaults that is kept in the installation folder. This file has an .ALT extension.

2.1 Hardware Requirements

The computer on which you install the Agent should meet the minimum hardware requirements for the operating system specified by Microsoft. In addition, a minimum of 100 MB of free disk space is required for the installation and operation of the Agent. More disk space might be required if your backups are large, or if you install Plug-ins.

For the specific requirements for each operating system, see the Shipping Products Chart or the release notes.

2.2 Permission Requirements

To install the Agent, you must have Administrator or equivalent permissions.

To manage an Agent from Windows CentralControl and Web CentralControl, the user identities and the BUAgent and VVAgent service accounts must be the same. If the service accounts are not identical, the BUAgent cannot perform status or administration functions. Use the VVAgent and BUAgent logs to determine the account under which the services are running.

If you are using Encrypting File System (EFS), you need additional permissions to back up files. If you do not have the correct permissions, you are denied access. ACLs for all subsequent files might not be backed up, and error messages might appear in the log. After you install the Agent, you need to change local security settings, or the default domain policy. To allow backups on an Agent using EFS, set the user right to Act as part of the operating system and add the Logon as a service right to the account.

2.3 Operational Modes

(15)

Ad-Hoc A user can use the CentralControl application to configure backup and restore Jobs on an Agent. To configure backup and restore Jobs, the user must have Back Up Files and Directories permission.

Scheduled A user can use the CentralControl application to schedule backup and restore Jobs on an Agent. The user does not need special privileges to run scheduled Jobs when the VVAGENT.EXE program is run as a system service by the system account user.

CLI A user can use the command line interface (CLI) to execute backups and restores directly from the command line, or a batch file. To use the command line, a user must have Back Up Files and Directories permission. These permissions are automatically applied if the user is a member of the BackupOperators or Administrators groups.

2.4 Default Installation Directories

These are the default installation directories:

C:\Program Files\EVault Software\Agent

C:\Program Files\EVault Software\Agent Assistant

If the top-level directory is not empty, it is not removed when the installation completes.

2.5 Agent Licensing

On vault versions 5.53 and later, a quota system is used to control Agent licensing. When an Agent connects to a vault, the vault automatically supplies the license. Licenses are required for most Agents, Plug-ins, and other Agent products that use a vault. These Agent applications require a license:

• Vault Backup Agent (VBA)

• Exchange Plug-in

• SQL Server Plug-in

• SharePoint Plug-in

• Cluster Support Plug-in

• Oracle Plug-in for Windows

• Bare Metal Restore (BMR)

If an Agent connects to a vault and a license is unavailable, the backup for the new Agent fails. However, you can still complete a restore. Previously licensed Agents are unaffected by the failure. Contact your service provider to purchase additional licenses.

These error messages might appear when you connect an Agent to a vault:

• Vault storage limit exceeded,

(16)

• Vault limit for Plug-in type exceeded, or type not found,

• Customer Quota for Plug-in type exceeded (Agent 5.6 and above only).

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

If customer quota 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)

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

* If the Agent already has a claim on the necessary licenses (it has previously done a backup of that type), the backup or restore operation is allowed.

“Client Key” refers to an older license key for the Agent. The vault does not use this key. When you successfully register an Agent with a vault, you can perform backups and restores.

2.6 Installation Wizard Fields

These fields appear in the Agent installation wizard:

Field Description

(17)

Custom Allows you to select the program options to install.

Install EVault Software Agent to The path where the EVault Software Agent is installed. Click Change to select another location.

Register Agent with Web CentralControl

Registers the Agent with Web CentralControl. If you do not register the Agent with Web CentralControl, you manage it through Windows CentralControl.

Network Address The IP address or Domain Name System (DNS) name for the Web CentralControl computer.

Port The port used to communicate with the Web CentralControl computer.

Username The user name used to access the Web CentralControl computer.

Password The password used to access the Web CentralControl computer.

Skip Registration Select this option if you want to manage the Agent with Windows CentralControl only.

Use ‘Local System’ Account Uses a local system account.

Create account automatically Creates an account to access and run Agent services automatically.

Use custom account Creates a custom account to access and run Agent services.

Leave unchanged Leaves the account credentials for Agent services unchanged.

Backup Agent Installs or uninstalls the Backup Agent.

Agent Assistant Installs or uninstalls the Agent Assistant.

Cluster Support Plug-in Installs or uninstalls the Cluster Support Plug-in.

Exchange 2003 Plug-in Installs or uninstalls the Exchange 2003 Plug-in.

Oracle Plug-in Installs or uninstalls the Oracle Plug-in.

SharePoint Plug-in Installs or uninstalls the SharePoint Plug-in.

SQL Server Plug-in Installs or uninstalls SQL Server Plug-in.

You are currently registered to Web CentralControl at the following address

Displays the Web CentralControl registration information.

Keep my current registration Keeps the Web CentralControl registration.

Change registration Changes the Web CentralControl registration.

Program files only Removes the Agent program files.

(18)

2.7 Installing the Agent

You can install the Agent from the Internet or a CD. You can run the installation on the Internet, or save the Agent Windows .exe file locally and then run the installation.

Before you start the Agent installation, install and configure the Microsoft operating system. You use the same installation procedure for 32-bit and 64-bit Agents.

To install the Agent:

1. Log on to the computer on which you want to install the Agent.

2. Double-click the Agent Windows .exe file. To obtain the self-extracting installation file, contact your licensed service provider of EVault Software products.

3. Select a language for the installation.

4. Complete the Agent installation wizard. For field descriptions, see Installation Wizard Fields. 5. Click Finish.

2.8 Silently Installing the Agent

To silently install the Agent from the command line:

1. Log on to the computer on which you want to install the Agent.

2. Open a command prompt, and navigate to the location of the Agent Windows .exe file. The default location for the file is C:\Program Files\EVault Software\Agent.

3. Run a command similar to this: setup.exe /s /v" /qn"

2.9 Customizing a Silent Installation

To customize your silent Agent installation, you specify the properties on the command line. For example, to install the Agent in a different directory, you run this command:

setup.exe /s /v" SILENTINSTALLDIR=\"C:\Program Files\Acme Software\" /qn" To install a different language, run a command similar to this:

(19)

To install an Agent and register it with Web CentralControl, run a command similar to this:

setup.exe /s /v" REGISTERWITHWEBCC=True AMPNWADDRESS=123.456.com AMPUSERNAME=test@test.com AMPPASSWORD=LetMeIn3 /qn"

To install an Agent with the Agent Assistant, and then register the Agent with Web CentralControl, run a command similar to this:

setup.exe /s /v" FEATUREMAESTRO=on REGISTERWITHWEBCC=True

AMPNWADDRESS=123.456.com AMPUSERNAME=test@test.com AMPPASSWORD=LetMeIn3 BCKLOGINURL=http://123.456.com/login/login.aspx

BCKHELPURL=http://123.456.com/help\help.htm /qn" To install an Agent and the SQL Plug-in:

setup.exe /s /v" FEATURESQL=On /qn"

This table lists the optional properties that you can specify when you silently install the Agent from the command line:

Property Default Value Description

ACCOUNTTYPE LocalSystem Possible values are LocalSystem, AutoCreate, and Custom.

AMPNWADDRESS If REGISTERWITHWEBCC is True, this field is required.

AMPPASSWORD If REGISTERWITHWEBCC is True, this field is required.

AMPPORT 8086

AMPUSERNAME If REGISTERWITHWEBCC is True, this field is required.

BCKHELPURL If FEATUREMAESTRO is True, this field is required.

BCKLOGINURL If FEATUREMAESTRO is True, this field is required.

EXTRACTMSI False Turns on/off extraction of the Microsoft Installer (MSI) package.

FEATURECLUSTER Off Turns on/off installation of the Cluster Plug-in.

FEATUREEXCHANGE Off Turns on/off installation of the Exchange 2003/2007 Plug-in.

FEATUREEXCHANGE2010 Off Turns on/off installation of the Exchange 2010 Plug-in.

FEATUREMAESTRO Off Turns on/off installation of the Agent Assistant.

FEATUREORACLE Off Turns on/off installation of the Oracle Plug-in.

FEATURESHAREPOINT Off Turns on/off installation of the SharePoint Plug-in.

(20)

KEEPAMPREGISTRATION True Set this property to True to retain the previous Web

CentralControl registration.

MSIPATH C:\ If EXTRACTMSI is True, this property denotes the location of

the extracted MSI and MST files.

REGISTERWITHWEBCC False Turns on/off registration of the Agent with Web

CentralControl.

SERVICEACCOUNTNAME If ACCOUNTTYPE is Custom, this field is required.

SERVICEACCOUNTPASSWORD If ACCOUNTTYPE is Custom, this field is required.

SILENTINSTALLDIR C:\Program Files\EVault Software\

TOTALUNINSTALL False If this property is False, uninstalling will only remove the

program files.

2.10 Modifying an Agent Installation

To change the language of an Agent, uninstall the Agent program files and then re-install the Agent. To modify the Agent:

1. Log on to the computer on which you want to modify the Agent.

3. Click Next. 4. Select Modify.

5. Complete the Agent installation wizard. For field descriptions, see Installation Wizard Fields. 6. Click Install.

2.11 Repairing an Agent Installation

To repair an Agent installation:

1. Log on to the computer on which you want to repair the Agent.

(21)

5. Complete the Agent installation wizard. For field descriptions, see Installation Wizard Fields. 6. Click Install.

(22)

2.12 Uninstalling an Agent

To uninstall the Agent under Windows:

1. Log on to the computer on which you want to uninstall the Agent.

3. Click Next. 4. Select Remove. 5. Select Total Uninstall. 6. Click Remove.

7. Click Finish.

2.13 Silently Uninstalling an Agent

To silently uninstall an Agent:

1. Log on to the computer on which you want to uninstall the Agent. 2. Open a command prompt and run this command:

(23)

Agent 7.1 for Microsoft Windows User Guide Upgrading the Agent

3 Upgrading the Agent

For information about silent upgrades, see Silently Installing the Agent.

This chapter provides information and procedures for upgrading to Agent 7.10 for Microsoft Windows. You can upgrade these Agents to version 7.10:

• Version 7.00

• Version 6.85

• Version 6.84

• Version 6.82

• Version 6.7x

• Version 6.6x

• Version 6.50

• Version 6.4x

• Version 5.6

If you are upgrading an Agent that is earlier than version 5.6, you must upgrade the Agent to version 5.6, and then upgrade to version 7.10.

These conditions can cause your backups to reseed:

• Microsoft Exchange mailbox names in Agent 7.0 and above use the same name as the Exchange System Manager Console. If the mailbox names are not identical, a reseed occurs.

• This condition only applies if you upgrade older Agents with Jobs that were created and backed up with 4 kB blocks (from 4.x to 5.6 to 6.0) to 6.01 to 6.10, 6.3, 6.5, or 6.6. During the upgrade from 6.0 to 6.01 to 6.10, 6.30, 6.5, or 6.60, the older 4 kB blocks change to the newer 32 kB blocks, causing a reseed on the next backup.

3.1 Hardware and Software Requirements

The computer on which you install the Agent should meet the minimum hardware requirements for the operating system specified by Microsoft. In addition, a minimum of 100 MB of free disk space is required for the installation and operation of the Agent. More disk space might be required if your backups are large or you install Plug-ins.

For specific requirements for each operating system, see the Shipping Products Chart or the release notes.

3.2 Preparing the Computer

(24)

• Back up all files and subdirectories in the Agent installation directory. Do not attempt an upgrade without a backup.

• Remove unused server profiles in Global.vvc.

• Delete or reassign all Jobs that back up to a vault you deleted from Global Settings.

Do not delete or reassign Jobs that back up to a directory on disk. When you upgrade the Agent, the Jobs are registered on the first vault listed in Global Settings.

• Synchronize all backup Jobs.

• Check the backup logs for each Job for Validation failed errors. Verify the validity of the error messages. If the latest backup log does not contain error messages, synchronize with the vault and check the Synch log.

• Verify that you have the correct version of EVault Director Software installed. See the Agent release notes for the specific requirements for each operating system.

3.3 Upgrading Program and Configuration Files

Do not run multiple upgrade processes at the same time.

To upgrade the Agent program and configuration files:

1. Log on to the computer on which you want to upgrade the Agent program and configuration files.

3. Click Yes.

6. Open the log file and verify that the upgrade was successful. If the upgrade failed, the

Global.vvc, Job vvc, and Delta files revert to the previous versions. However, they do not work with new executables unless you manually replace them with the backup files. Try the upgrade again. If it fails, contact your service provider.

7. Create a backup for each Job. This uploads new configuration files from the Agent to the Director.

3.4 Upgrading an Agent that Uses OTM

(25)

1. Log on to the computer on which you want to upgrade the Agent.

3. Click Yes.

VSS open file manager becomes the default open file manager and OTM is disabled. However, otmlapi.dll/otman5.sys is still on the upgraded system. Backups created after you upgrade the Agent are deltas and complete successfully. New Jobs use VSS open file manager, but you can select OTM.

3.5 Upgrading the Microsoft Exchange Server MAPI Plug-in

If you have installed the Exchange 2003 Plug-in with an Agent version 5.6, 6.0, or 6.1, you might need to replace or remove older Exchange mailbox names when you upgrade the Agent.

After an upgrade, mailbox names identified as LegacyExchangeDN do not match the newer Exchange System Manager Console (Active Directory) names. Before you upgrade the Agent, the MDB mailbox names start with a number. The upgraded Agent uses Active Directory names and the mailbox names start with a letter. As a result, the old mailboxes are not included with the Job parameters. The Upgrade log file lists the mailbox names that do not match. Edit the Job and change the mailbox name from a number to a letter.

1. Log on to the computer on which you want to upgrade the Agent.

3. Click Yes.

4. Select I want to proceed with the upgrade of this Agent.

(26)

Agent 7.1 for Microsoft Windows User Guide Configuring the Agent

4 Configuring the Agent

This chapter provides information and procedures for configuring the Agent. To configure an Agent to run a backup, complete these tasks:

• Create an Agent profile

• Save the workspace

• Configure the vault

• Create a Job

• Schedule a Job

You use CentralControl to manage and configure the Agent. You can use a single CentralControl instance to control multiple Agents. Before you can perform backups and restores:

• You must install an Agent on the computer that you want to back up.

• You must connect CentralControl to the Agent.

• You must supply a Name, IP or DNS address, and user and password credentials.

• You must register the computer on which the Agent is installed on the vault. Registration allows the Agent to connect to the vault.

If you are restoring from another computer, you must re-register the Agent computer on the vault.

4.1 Agent Properties Dialog Fields

These fields appear in the Agent Properties dialog:

Field Description

Description The Agent profile name.

Network address The IP address or Domain Name System (DNS) name for the Agent computer.

Default port The default port used to communicate with the Agent computer.

Custom port A custom port used to communicate with the Agent computer.

User name The user name used to access the Agent service.

Password The password used to access the Agent service. This field is case sensitive.

Save password Saves the password used to access the Agent service.

Domain The Microsoft Windows domain on which the Agent computer is installed. If you are not using a domain name, enter a period (.).

(27)

4.2 Creating an Agent Profile

You create an Agent profile for every computer that you want to back up. To create an Agent profile: 1. Open CentralControl.

2. Right-click Workspace (untitled) in the left pane and select New Agent.

3. Complete the fields in the Agent Properties dialog. For field descriptions, see Agent Properties Dialog Fields.

4. Click Get Status to test the Agent profile.

a. In the DNS or IP information is incorrect, the message Failed to connect to <...> appears. If the authorization information is incorrect, the messageFailed to

authorize user () or user () possesses insufficient privilege appears. Contact your service provider

5. Click OK. 6. Click OK.

4.3 Adding an Agent Group

To save time, you can use a text file to apply Agent information to multiple Agents. For more information about this process, see the Windows CentralControl Operations Guide.

To add an Agent group: 1. Open CentralControl.

2. Right-click Workspace (untitled) in the left pane and select New Group. 3. Enter a name for the Agent group in the Group name field. Click OK. 4. Right-click the group in the left pane and select Import Agents.

5. Browse to the location of the Agent comma separated values (CSV) file. 6. Click Open.

(28)

4.4 Renaming the Workspace

To save Agents, Jobs, and other settings you must save your workspace. You can change the workspace name, or keep the default name MyWorkspace. You can save multiple workspaces, but you can only open one workspace at a time.

You use workspaces to organize your Agent connections into logical groups. For example, you can create a workspace for individual company departments.

To rename and save a workspace: 1. Open CentralControl.

2. Select Workspace (untitled) in the left pane. 3. Click File and then Save Workspace As.

4. Enter a name for the workspace in the File name field. 5. Click Save.

4.5 Encrypting a Workspace

Workspaces contain user names and passwords. It is recommended that you encrypt your workspaces to prevent unauthorized access. To encrypt your workspace:

1. Open CentralControl.

2. Select a workspace in the left pane. 3. Click File and then Workspace Password.

4. Select an encryption type in the Encryption type list. 5. Enter a password in the New password field.

6. Enter the password in the Confirm password field. 7. Click OK.

(29)

4.6 Options Dialog Fields

These fields appear in the Options dialog:

Field Description

Automatically reload last workspace on startup

Automatically loads the last saved workspace when you start the CentralControl application. If you do not select this option, you must select one manually.

Auto-refresh display for selected agent every <#> minutes

The number in minutes that the Agent is polled for updated information. Valid numbers are 1 to 15. To refresh data manually, click Refresh, or press F5. Do not add a separator, such as a decimal point, or comma in the field.

Update progress display every <#> seconds

The number in seconds information in the Progress Monitor updates. Valid numbers are 5 to 10000.

Do not add a separator, such as a decimal point, or comma in the field.

Return maximum <#> of files and directories

The maximum number of files and directories returned when you select to view them. Valid numbers are 10 to 10000000. This setting optimizes the system when there are large directories, and you have to wait while the filenames are read and displayed. If more entries are returned than the specified number, a prompt appears asking if f you want to see them all.

Do not add a separator, such as a decimal point, or comma in the field.

Default Text Viewer This is the viewer that is used to show logs (XML based), and other text based files

4.7 Setting Workspace Options

To set workspace options:

2. Select a workspace in the left pane. 3. Click Tools and then Options.

4. Complete the fields in the Options dialog. For field descriptions, see Options Dialog Fields. 5. Click OK.

(30)

4.8 Vault Configuration Wizard Fields

These fields appear in the Vault Configuration wizard:

Field Description

Register as a new computer Registers the Agent as a new computer on the vault.

Re-register previously registered computer

Changes existing Agent connection settings.

Profile name for the new vault The name of the Agent profile.

New address The IP address or Domain Name System (DNS) name for the Agent computer.

New ports The Agent computer communication port.

Try to reconnect every <> seconds The time in seconds that the vault attempts to reconnect to an Agent when a connection is interrupted.

Stop reconnection attempts after <> minutes

The time in minutes that the vault stops trying to reconnect to the Agent.

Enable over the wire encryption for transmission to/from the vault

Applies over the wire encryption to secure data sent from the Agent to the vault.

Account The name of the vault.

User name The user name used to access the vault.

Password The password used to access the vault. This field is case sensitive.

4.9 Configuring a New Vault Connection

To configure a vault connection:

2. Right-click an Agent in the left pane and select AgentConfiguration. 3. Click the Vaults tab.

4. Click New.

5. Complete the fields in the Vault Configuration wizard. For field descriptions, see Vault Configuration Wizard Fields.

(31)

4.10 Reregistering an Agent

When you delete an Agent from a vault, the Agent profile is deleted on the computer on which the Agent is installed. If you add an Agent to the vault with a name that you deleted, the vault recognizes it and prompts you for a re-registration. You must reregister an Agent when you restore from another computer.

When the original Agent profile is downloaded from the vault to the Agent, these fields are removed:

• The encrypted password.

• The domain, username, and password of the account used to perform a MAPI backup.

• The domain, username, and password of the account used to back up SQL server.

• The domain, username, and password of the account used to back up a networked drive

When a reregistration or restore from another computer occurs, and the backup or restore fails, messages similar to this appear in the error log:

PARS-W-0002 Due to a computer registration, configuration file “weekend” is missing the following information:

PARS-W-0002 Enc_Password (Encryption Password)

please use the CentralControl to re-enter the missing information. The Agent reregistration process creates a Register log file that lists missing Job file settings.

You must reconfigure the Job file before you can perform a backup or restore on a Job file with missing settings. The backup or restore log files indicate which Job settings are missing.

(32)

4.11 Improving Agent Performance

When you install the Agent on a computer with dual processors you can use multi-threading to improve the performance of backups and restores for files larger than 32 KB. You can use these threading models:

• Single threading – A single thread is used for all data processing.

• Combined threading – Two threads are used for all data processing.

• Block Processor threading – Four or more threads are used for all data processing.

This table lists the threading options that you can specify for a backup or a restore in the Job CFG file or the command line with VV.EXE:

Option Description

Default The Agent checks the both backup settings and the current hardware to determine which model it should use. This is the default setting.

On a single CPU system, the single threading model is used.

On a multi-CPU system the threading model used is dependent on the backup settings. If compression or encryption is turned ON, the Block Processor threading model is used, otherwise the Combined threading model issued.

Single A Single threading model is used.

Combined The Combined threading model is used.

Block Processor The Block Processor threading model is used with up to four processing threads.

Maximum Block Processor The Block Processor threading model is used with up to five processing threads. You cannot specify this option for a restore.

(33)

Agent 7.1 for Microsoft Windows User Guide Creating Jobs

5 Creating Jobs

This chapter provides information about creating and scheduling backup Jobs.

5.1 Creating a New Job

To create a Job:

1. Open Windows CentralControl.

2. Right-click an Agent in the left pane and select New Job.

3. Complete the fields in the New Job wizard. For field descriptions, see New Job Wizard Fields. 4. Click Finish.

5.2 New Job Wizard Fields

These fields appear in the New Job wizard:

Field Description

Backup source type The source of the data to back up.

ANSI: Files with filenames not in the current language may not be backed up

Excludes files with filenames that are not in the current language from the backup.

Unicode: All files will be backed up. Some filenames will display improperly in the file selection screens.

Includes all files in the backup.

Destination Select an existing vault profile, or click New and create a new profile.

Job name The name of 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). 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.)

Data Files Backs up data files.

Bare Metal Restore Back up the entire drive.

System State Back up system files.

RSM database Back up Removable Storage Media (RSM) database.

(34)

Quick file scanning

Disable deferring

Backup time window The time in hours that the backup runs.

Encryption type The encryption type for the Job.

Password The encryption password. Data cannot be recovered if you lose or forget the password.

Verify password The encryption password.

Create log file Creates a log file. Sets the log file options.

Log detail level The amount of detail included in the log file.

Automatically purge expired log files only Deletes log files when the safeset expires.

Keep the last <> log files The number of log files to keep.

Run the Job immediately Runs the Job immediately.

Schedule a backup Creates a schedule to complete the Job weekly or monthly.

Just exit from this wizard Saves the Job without running it.

5.3 Adding Files and Directories to a Job

Exclude any files and directories that do not need to be backed up, and files and directories that will be open during the backup. This includes the Agent installation directory. Although the backup works, error messages such as

error opening file

are added to the log file.

To add files and directories to a Job: 1. Open Windows CentralControl.

2. Right-click a Job in the left pane and select Properties. 3. Click the Source tab.

4. Select Data Files in the top pane. 5. Click Add.

6. Select files or directories in the top pane. 7. Click Include.

(35)

If you include a directory, the Confirm Include dialog appears. Select Recursive to include all files in the directory, or create a filter to specify the files you want to include. Use an asterisk (*) to include files that match the partial name or extension, or the start, middle, or end of a directory name. 8. Click OK.

9. Click OK again.

5.4 Wildcards in Directory Paths

EVault Software Director does not support or recognize wildcard folder selections for restores. However, the Agent supports wildcards in paths for both inclusion and exclusion.

For example, assume you have on your server, a directory named Users, and below it are directories for each user’s name, in alphabetical order (C:\Users\<all the A’s>, C:\Users\<all the B’s> and so on until <all the Z’s>. You want to be able to back up all these user directories. If you select “C:\Users” and Recursive, you will get everything in one backup. However, as more users are added, the backup takes longer. You need to break the Job into separate backups, each taking part of the data. For instance, one takes all the A to E, another takes all the F to J, or whatever “balance” you decide.

If you use a wildcard with each letter, A*, B*, C*, D*, E*, (and recursive) for one backup, you can get all the data, automatically including any new ones added, and excluding old ones deleted. Another backup Job may use F*, G*, H*, I*, J* (for example).

You can filter further using ”include only files matching this filter”.

When you have finished selecting (and including) all the files and directories you want for this backup Job, click

Yes and you will return to the Source screen. Here, you can click Next to continue to the next step of the New Job Wizard.

5.5 Wildcard Rules for Directories

In these examples, a path element is a part of the path (\ …\) of a directory. If the wildcards are not used in this way, you will see an error message. Note that the *.* at the end of the selection represents wildcards for the files. This is different from the wildcards for the folders.

• Only the last path element of the selection can contain a wildcard:

• Supported: C:\Projects\A*\.\*.*

• NOT supported: C:\P*\Active\.\*.*

• A path element of a selection can only contain one wildcard:

(36)

• NOT supported C:\P*j*\.\*.*

• The wildcard can appear anywhere in the path element:

• Supported: C:\Project*\.\*.*

• Supported: C:\*rojects\.\*.*

• The Agent supports one path element with a wildcard per selection:

• Supported: C:\Projects\User*\.\*.*

• NOT supported: C:\P*\U*\.\*.*

5.6 Selection Rules

The more specific path is selected first if the file specification is the same. For example: C:\DIR1\DIR2\.\*.DAT wins over C:\DIR1\.\*.DAT The more specific path is selected first if the file specification is the same. For example:

C:\DIR1\.\*.DAT wins over C:\DIR1\.\*.*

If there is a conflict, and one has a more specific path and the other has a more specific file, then the exclude wins. For example:

Exclusion of C:\.\*.DAT wins over inclusion of C:\DATA\.\*.*. However inclusion of C:\.\*.DAT does not win over exclusion of C:\DATA\.\*.*

5.7 Removing Files and Directories from a Job

To remove files or directories from a Job:

4. Select a file or directory in the lower pane. 5. Click Remove.

(37)

7. Click OK.

5.8 Backing Up System State Files

You can back up System State files. System and state files are critical to the recovery of the operating system. Your operating system determines what files are necessary for a System State backup. Typically, a System State backup includes these files:

• COM+ Class Registration database

• Registry

• Boot files (except for Boot Configuration Data (BCD))

• Windows system files

• Performance Counter To back up System State files:

4. Select System State in the top pane. 5. Click OK.

5.9 Backing Up System Files

System and state files are critical to the recovery of the operating system. Including system files with your backup allows you to recover from a corrupted file system, unintentionally removed service packs, or a bare metal restore. When you back up the system files, you can return to the state of the backup without

reinstalling the operating system and service packs.

The operating system and service packs that you install determine what files are included with the system files backup. Windows makes a dynamic list of these DLLs when you include them in your backup.

To back up system files:

(38)

5. Click Options.

6. Select Backup system files. 7. Click OK.

8. Click OK again.

5.10 Additional Backup Options

When you create a new Job and select Network UNC Share as the backup source type, you can only include data files in the backup.

When you create a new Job and select Local Drive Only as the backup source type, you can include these items in your backup:

• Data Files – Select this option to back up files and directories.

• Bare Metal Restore – Select this option to create a BMR-type backup.

• System State – Select this option to back up System State and system files.

• RSM database – Select this option to back up the Removable Storage Manager(RSM) database. An RSM database allows multiple applications to share local robotic media libraries and disk drives, and manage removable media within a single-server system. The RSM database store persistent data. The RSM database option is available as a Job option if the RSM service is installed and functioning on the client.

• Event logs – Select this option to back up the Windows event logs. Event logs store events that you can view with the Windows Event Viewer program.

• IIS Metabase – Select this option to back up the Internet Information Services (IIS) Metabase. The IIS Metabase is a database similar in structure to the Windows Registry. The IIS Metabase is optimized for IIS, and provides hierarchical storage and fast retrieval of IIS configuration properties for websites, virtual directories, FTP sites, SMTP, and NNTP sites.

• Terminal Services Licensing Database – Select this option to back up the Terminal Service licensing database. This option is available when Terminal Services is installed and licensed on Windows Server 2003 or a Windows Server 2008 server.

• Active Directory – Select this option to back up the Windows Active Directory. It supports the recovery of replicated data where the target is the primary Active Directory server.

5.11 BMR-Type Backup Jobs

You can use data from a Bare Metal Restore (BMR) type backup to apply a complete system backup to a new computer. You use the EVault System Restore (ESR) application to apply the BMR data. See the ESR User Guide for more information.

(39)

To create a BMR-type Job, you include the Bare Metal Restore directory in a local backup Job. When you select Bare Metal Restore, the information necessary for an EVault System Restore is added to your backup.

BMR Jobs consume an EVault System Restore license when they run.

Note: Encrypted volumes (BitLocker, TrueCrypt, etc.) are not supported with BMR Jobs.

5.11.1 Creating a BMR Job with Windows CentralControl

To create a BMR-type backup Job:

1. Make sure that the appropriate license is available on the vault account. 2. Open Windows CentralControl.

3. Create a new Job. Select Local Drive Only and Unicode on the Backup Source Type menu. See Creating a Job.

4. Select a vault. 5. Name your Job.

6. From the New Job Wizard - Source page, select Bare Metal Restore. 7. If you wish, add more data to the backup (even if it is not part of BMR). 8. Proceed and finish creating the Job as you normally would.

5.11.2 Creating a BMR Job with Web CentralControl

To create a BMR-type backup Job:

1. Make sure that the appropriate license is available on the vault account. 2. Open Web CentralControl.

3. Highlight a Windows Agent, and select Add > Job.

4. Name your Job. Select Local System for the Backup Source Type. 5. On the data selection page, select Bare Metal Restore.

6. If you wish, add more data to the backup (even if it is not part of BMR). 7. Proceed and finish creating the Job as you normally would.

(40)

5.12 Converting an Existing Job to a BMR Job

You can change an existing local system Job to a BMR Job. Selecting Bare Metal Restore does not alter existing data selections.

To convert to a BMR-type backup Job:

1. Make sure that the appropriate license is available on the vault account. 2. Open Windows CentralControl.

3. Right-click on a Job and select Properties. 4. Click the Source tab.

5. Select Bare Metal Restore in the top pane. If the data in Data Files overlaps with BMR data, clear the Data Files selection.

6. Save the Job and run it to create the BMR safeset.

7. Check the Job log to make sure that the backup does not reseed.

Note: If the pre-existing Job is a System State backup, you need to edit the job.vvc file in order to convert to BMR:

• Open the job.vvc file with Notepad or a similar editor.

• Remove Include = "C:\Data\"

• Change the values of System_1State_Opt_SysFiles and System_State from True to False

• Change the value of Support_BMR_Recovery from False to True

• Save the file.

• Highlight the Job, right-click, and select Properties. Make sure the New Job Wizard – Source screen shows that only Bare Metal Restore is selected.

The job.vvc file is located in the C:\Program Files\EVault Software\Agent directory.

5.13 Scheduling a Job

To schedule a backup or synchronize Job to run at a scheduled time: 1. Open Windows CentralControl.

(41)

3. Click New.

4. Complete the fields in the Schedule wizard. 5. Click Finish.

6. Click OK.

5.14 NTFS Hard Links, Symbolic Links, Mount Points and Junctions

5.14.1 Hard Links

Backing up and restoring hard links locally, correctly preserves the link. When restoring remotely, the link is preserved only if the files are both restored to their original location and overwrite the existing files. If the original files are not overwritten, or if the incoming files are restored to an alternate location, the link breaks.

Note: Remote hard links are not supported (e.g. UNC paths).

5.14.2 Symbolic Links

Restored symbolic links point to their target’s new location, if the target is also part of the backup and restore.

5.14.3 Mount Points

The above functionality also applies to Mount Point recovery.

Note: Remote mount points are not supported (e.g. UNC paths).

5.14.4 Junctions

If junctions are restored to their original location, all link functionality will be preserved. If restored to an alternate location, the junction will revert to a normal, empty directory. If recovery to an alternate location is desired, the junction must be explicitly selected for backup and will duplicate the contents of its target directory without preserving junction functionality.

(42)

Agent 7.1 for Microsoft Windows User Guide Manual Data Backup

6 Manual Data Backup; Process, Properties, Logs and Emails

This chapter provides information and procedures for running a manual or ad-hoc backup as well as viewing process details, safeset properties, logs and email notifications.

6.1 About Seeding and Reseeding

When you run your first backup, a full safeset is created on the vault. This first safeset is called a seed and it contains all of the selected backup data. Subsequent backups are deltas that are applied to the first full backup to create subsequent safesets. This way a current full backup is always available.

If the Agent detects a change, such as the encryption type or password changing, the next backup is a reseed. With a reseed, your backup takes longer to complete and a message about reseeding is added to the log file.

6.2 Running an ad hoc Backup

To run an unscheduled or ad hoc backup:

2. Right-click a Job in the left pane and select Backup. 3. Complete the fields in the Backup wizard.

4. Click Finish. 5. Click Close.

6.3 V iewing Process Details

Processes are the backups, synchronizations, and restores performed by the Agent. Process information is normally deleted within an hour. To delete process information manually, click Delete Entry. Information about the job is retained in the log files. To view process information:

1. Open Windows CentralControl. 2. Expand an Agent in the left pane. 3. Click Processes.

(43)

Agent 7.1 for Microsoft Windows User Guide Manual Data Backup

5. Click Close.

6.4 V iewing Safeset Properties

Safesets are sets of sequentially numbered backup data on the vault. Safesets remain on the vault until their retention date expires. To view safeset properties:

1. Open Windows CentralControl. 2. Expand an Agent in the left pane. 3. Expand a Job.

4. Click Safesets.

5. Double-click a safeset in the right pane. 6. Click OK.

6.5 V iewing Log Files

Log files provide details of events that occurred during a backup, synchronization, or restore. To view log files: 1. Open Windows CentralControl.

2. Expand an Agent in the left pane. 3. Expand a Job.

4. Click Logs.

5. Double-click a log in the right pane.

6.5.1 Notes on Agent Logs Behavior

1. XLOG files - updating:

a. Backup removes the backup logs (log and xlog) based on the log setting. If a log setting is not specified, retention settings are used.

b. Synchronization does NOT remove any logs (log and xlog).

c. Restore removes restore logs (log and xlog) based on the log setting. If a log setting is not specified, restore logs are not removed.

EVault Software Agent 7.1 for Microsoft Windows User Guide

EVault Software

Agent 7.1 for Microsoft Windows

User Guide

Contents

1

Overview

1.1

Product Overview

1.2

Windows Agent Features

1.3

About the Windows Agent

1.4

About CentralControl

1.5

About EVault Software Director

1.6

Supported 32-Bit Agent Plug-ins

1.7

Supported 64-Bit Agent Plug-ins

1.8

Plug-in Behavior

1.9

About the Exchange Plug-in

1.10

About the Oracle Plug-in

1.11

About the SQL Server Plug-in

1.12

About the Cluster Support Plug-in

1.13

About the SharePoint Plug-in

1.14

Additional Resources

2

Installing and Modifying the Agent

2.1

Hardware Requirements

2.2

Permission Requirements

2.3

Operational Modes

2.4

Default Installation Directories

2.5

Agent Licensing

2.6

Installation Wizard Fields

2.7

Installing the Agent

2.8

Silently Installing the Agent

2.9

Customizing a Silent Installation

2.10

Modifying an Agent Installation

2.11

Repairing an Agent Installation

2.12

Uninstalling an Agent

2.13

Silently Uninstalling an Agent

3

Upgrading the Agent

3.1

Hardware and Software Requirements

3.2

Preparing the Computer

3.3

Upgrading Program and Configuration Files

3.4

Upgrading an Agent that Uses OTM

3.5

Upgrading the Microsoft Exchange Server MAPI Plug-in

4

Configuring the Agent

4.1

Agent Properties Dialog Fields

4.2