ARCA Administration Guide

Zenith Infotech, Ltd

www.zenitharca.com www.zenithinfotech.com

Zenith ARCA Administration Guide

Administration & Troubleshooting the Zenith ARCA

Date: 9/14/2009

ARCA Administration Guide.doc Copyright 2009 Page 2 of 274

Table of Contents 1.1 WHO SHOULD USE IT.................................................................................................................................................................................4 1.2 TYPOGRAPHICAL CONVENTIONS................................................................................................................................................................5

2 SYSTEM OVERVIEW ...................................................................................................................................................................................6

2.1 PURPOSE ....................................................................................................................................................................................................6 2.2 SCOPE ........................................................................................................................................................................................................6 2.3 CHANGE LOG .............................................................................................................................................................................................7

3 DESCRIBING THE SYSTEM .......................................................................................................................................................................8

3.1 KEY FEATURES ..........................................................................................................................................................................................8 3.2 INVENTORY................................................................................................................................................................................................8 3.3 ENVIRONMENT...........................................................................................................................................................................................9 3.4 SYSTEM OPERATIONS ..............................................................................................................................................................................10

4 INSTALLATION ..........................................................................................................................................................................................12

4.1 LOGGING IN FOR THE FIRST TIME.............................................................................................................................................................12 4.2 ARCA COMPUTER MANAGEMENT AND INSTALLED APPLICATIONS ........................................................................................................12

5 ARCA UTILITIES – SERVER BACKUP AGENT ...................................................................................................................................14

6 BACKUP JOB CONFIGURATION & MODIFICATION - ARCA.........................................................................................................29

6.1 VERIFYING BACKUPS ...............................................................................................................................................................................35 6.2 ARCA BACKUPS EXPLAINED ..................................................................................................................................................................37 6.6 ON-DEMAND BACKUP JOBS.....................................................................................................................................................................41 6.7 EDITING BACKUP JOBS ............................................................................................................................................................................41 6.8 CONFIGURE BACKUP ALERTING ..............................................................................................................................................................48

7 RESTORING FILES AND FOLDERS .......................................................................................................................................................50

7.1 MOUNTING A BACKUP IMAGE, MOUNT POINT, READ-ONLY ...................................................................................................................50 7.2 MOUNTING BACKUP IMAGES USING THE CONTEXT MENU..................................................................................................................51 7.3 RESTORING FILES AND FOLDERS...........................................................................................................................................................52 7.4 RESTORING BACKUP IMAGE FILES........................................................................................................................................................55 7.5 DISMOUNTING BACKUP IMAGE FILES ...................................................................................................................................................56

8 ARCA ADMINISTRATION ........................................................................................................................................................................59

8.1 EXCHANGE RECOVERY TOOL ..................................................................................................................................................................60


9 EXCHANGE RESTORATION (DATABASE ONLY)..............................................................................................................................77

10 SQL DATABASE RESTORATION........................................................................................................................................................80

11 ACTIVE DIRECTORY RESTORATION (DATABASE ONLY) ........................................................................................................81

11.1 ARCA HEALTH CHECK ...........................................................................................................................................................................83 11.2 BACKUP MANAGEMENT CONSOLE...........................................................................................................................................................87 11.3 EXCHANGE RECOVERY TOOL ................................................................................................................................................................100 11.4 BACKUP CHAIN CONTINUITY CHECK.....................................................................................................................................................117 11.5 CHAIN VERIFICATION ............................................................................................................................................................................121 11.6 EMERGENCY CLEAN UP .........................................................................................................................................................................127 11.7 FILE VERIFICATION................................................................................................................................................................................131

12 VIRTUAL MACHINE............................................................................................................................................................................137

12.1 STANDBY SERVER..................................................................................................................................................................................137 12.2 MANAGING VIRTUAL SERVERS..............................................................................................................................................................145

13 SUPPORT ................................................................................................................................................................................................198

13.1 ARCA SUPPORT PORTAL.......................................................................................................................................................................198

14 REPORTING DASHBOARD ................................................................................................................................................................200

14.1 BACKUP ANALYSIS ................................................................................................................................................................................200 14.2 BACKUP HISTORY ..................................................................................................................................................................................218

15 SERVER FAILOVER PROCESSES.....................................................................................................................................................224

15.1 ONSITE SERVER FAILURE.......................................................................................................................................................................224 15.2 SITE LEVEL FAILURE .............................................................................................................................................................................224

16 BARE METAL RESTORE ....................................................................................................................................................................226

16.1 BARE METAL RESTORE EXPLAINED .....................................................................................................................................................226

17 TROUBLESHOOTING..........................................................................................................................................................................242

18 TABLES ...................................................................................................................................................................................................266

19 APPENDIX A – REFERENCE DOCUMENTS ...................................................................................................................................272

20 APPENDIX B – GLOSSARY OF TERMS ...........................................................................................................................................273

About this guide


This document is divided into the following chapters:

• Chapter 1, “System Overview”.

• Chapter 2, “ARCA Administration”, reviews common administrative tasks.

• Chapter 3, “ARCA Troubleshooting” gives common errors and resolutions.

• Chapter 4, “Best Practices”, explain best practice deployments.

• Appendix A – Reference Documents

• Appendix B – Glossary of Terms

1.1 Who Should Use It

This guide is intended for administrators with advanced knowledge and experience with system infrastructure and backup

systems:

• Administrators: The administrator will learn how to administer and troubleshoot the ARCA.

This guide assumes that you have knowledge of Windows and backup concepts.


1.2 Typographical Conventions

This document uses the following typographical conventions:

• Command and option names appear in bold type in definitions and examples. The names of directories, files,

machines, partitions, and volumes also appear in bold.

• Variable information appears in italic type. This includes user-supplied information on command lines.

• Screen output and code samples appear in monospace type.

In addition, the following symbols appear in command syntax definitions.

• Square brackets [ ] surround optional items.

• Angle brackets < > surround user-supplied values.

• Percentage sign % represents the regular command shell prompt.

• Pipe symbol | separates mutually exclusive values for an argument.


2 System Overview

2.1 Purpose

This chapter includes the following topics:

• About the Zenith ARCA

• Describing the System

• Administration

• Troubleshooting

• Best Practices

• Appendix

2.2 Scope

We will learn about maintenance and administration of the Zenith ARCA.


2.3 Change Log

Date Changes

06.17.2009 Document created

06.26.2009 Added advanced editing of backup jobs and Ontrack, added event log tables

07.06.2009 Added Virtualization Troubleshooting section

07.15.2009 Added Failover Scenarios

09.14.2009 Clarified VM troubleshooting and added BDR Failover


3 Describing the System

The Zenith ARCA is an all-in-one business continuity appliance which includes all the software and hardware necessary to

protect your Windows Server infrastructure.

3.1 Key Features

The Zenith ARCA is intended for use in Windows Server environments (Windows 2000 Server and above). The features

include:

• Standby Server - Allows the user to perform server virtualization directly from backup files in the event of a disaster.

The sandbox modes allow for testing against your servers and validating images.

• Backup & Recovery – Allows for partition level snapshots as often as every 15 minutes for multiple recovery points. We

utilize a customized version of Storagecraft’s Shadowprotect to perform block level backups and recover using drag &

drop functionality.

• Mailbox & Message Level Recovery – Using Ontrack PowerControls, restore Exchange databases and objects by only

backing up the partition where your databases reside. No message level backup required. Restore to a .pst or live

Exchange Server via the easy to use GUI interface.

• Centralized Management Console – Configure backup and disk alerting, view reports, and perform administrative tasks

from one central dashboard.

• Bare Metal Restore – Utilizing our included Bare Metal Restoration CD, boot to a restore environment to run disk checks

and restore your backups to identical or dissimilar hardware, even virtual environments.

• Replication – Copy and synchronize your backups to a local or network destination. Our included replication software

allows replication to and from another ARCA or vault.

3.2 Inventory

The following components must be pre-installed on the ARCA:

• ARCA Software Suite

• Breakthrough Copy System

• Breakthrough Vault

• Sun xVM VirtualBox

• Zenith Business Continuity System


• KeyFile Maker

• Ontrack Power Controls 4.2

The following components must be installed on the Vault server. If you have a Vault from Zenith, this software will be pre-

installed:

• Breakthrough Copy System

• Breakthrough Vault

• ARCA Software Suite

• Sun xVM VirtualBox

• KeyFile Maker

• Ontrack Power Controls 4.2

On the target backup server the following must be installed after running the Backup Agent Install:

• ARCA Backup Agent

• Zenith Business Continuity System On the target backup server the following services must be started after running the Backup Agent Install:

• ARCAScheduler

• ClStateBackAsst (Clean State Backup Assistant)

• ShadowProtect Service

• StorageCraft Shadow Copy Provider You must have an administrative account to install and authenticate to the target backup servers. The server must have

access to the D$ share on the ARCA for writing backup files.

Please contact support if any components are missing or not installed.

3.3 Environment

Before continuing, check to verify that you have:

• Local or Remote Access to the ARCA

• Internet Connection


• LAN Connectivity to the destination servers

• WAN Connectivity for replication to ARCA or Vault

3.4 System Operations

General Operational Guidelines

• To backup your servers from the ARCA, a backup agent must be installed. For installation instructions see the Ze-

nith ARCA Implementation Guide.

Warning: The ARCA cannot backup itself or other ARCA appliances. To protect your ARCA, backup the configuration settings

via “Restore Configuration”. If the ARCA backup agent software is installed on the appliance, settings will be overwrit-

ten and you must contact support.

• .Application logs are created in “C:\Program Files\ZenithARCA\ApplicationLog”.

• You must have network connectivity on the LAN when backing up servers. We do not recommend backing servers

up over the WAN.

• You will need to open port 16450 for the web service to post data (NIC configuration, replication alerts, etc.) on repli-

cated configurations.

• For replication, you will need to open ports in your firewall. The default client port is 39002 (BTP – Breakthrough

Transfer Protocol).

• Default vault ports are 39000 (TCP and UDP) and 39002 (BTP).

• The ARCA is setup in a workgroup configuration (recommended), but it can be joined to a domain.

• The default admin user accounts and passwords are: “administrator” and “restore”, password “arca”. We recom-

mend changing the default passwords for security. You can use any administrative account to login, but a dedicated

virtualization account is recommended.

The ARCA software runs under the “Local System” account on the ARCA.


Any administrative account can be used to create the backup and authenticate to the backup agents. We

recommend using the same account for ease of administration.

After the backup agent is installed on destination servers, the backup agent runs under the “Local Sys-

tem” account.

For email alerting, you will need an SMTP server to relay messages. The ARCA does not include an

SMTP server.

Documentation is available from our website www.zenitharca.com

Support is available through our portal https://support.zenitharca.net


4 Installation

4.1 Logging in for the First Time

The ARCA will boot to the Windows login screen. You can login with one of the default accounts, administrator or restore,

password arca. You will be prompted to change the password. Do not forget the password if you decide to change it. Once

you login you will presented with the Windows user interface.

Warning: A dedicated account is recommended when performing server virtualization tasks. See the Standby Server sec-

tion for details.

Configure your Network Settings by assigning static IP addresses to the LAN Connections

Verify all pre-installed applications.

Please see the Zenith ARCA Getting Started Guide for initial setup information.

4.2 ARCA Computer Management and Installed Applications

We will review the system services and event viewer settings.

• ZenithARCA Event Log – A custom event log which reports all triggered ARCA events.

• Installed Applications

ARCA

Breakthrough Copy System

KeyFile Maker

Ontrack PowerControls 4.2

Sun xVM VirtualBox

Zenith Business Continuity System


• Installed Services – These services should be in a “Started” state for proper operation:

ARCAScheduler

Breakthrough Scheduler

Storagecraft Image Manager

• Event Viewer

Double-click each event to view its properties.


5 ARCA Utilities – Server Backup Agent

These utilities are installed on servers with the ARCA Backup agent. For installation instructions please see the ARCA

Implementation Guide.

5.1.1 ARCA Backup Agent Doctor Run ARCA Backup Agent Doctor to verify list of backup agent components and services.

To run:

• Go to “Start > All Programs > Accessories > System Tools > ARCA Backup Agent > ARCA Backup Agent Doctor >

ARCA Backup Agent Doctor”


Agent Doctor launches

• Click “Start” to verify agent components.

• Blue status = success or service running

• Red = fail or service stopped

• Click “Finish” to close health check, following prompt appears.


• Click “Yes” to close exit prompt.

If errors are found:

• Attempt to restart any stopped services.

• Reregister failed componenets using “regsvr32” in the command line.

Example: Register zrVBox.dll

Note: If errors cannot be resolved contact support.

5.1.2 Standby Server Helper Run Standby Server Helper according to the virtualization mode. The Standby Server Helper ensures your IP and MAC

address settings match the original server. Run the utility when machines are in virtual mode.

To run:

• Go to “Start > All Programs > Accessories > System Tools > ARCA Backup Agent > Standby Server Helper”


• Select “Live Mode”. This can be run in Sandbox Mode but it is not required.

• “Is server running in virtual mode?” prompt appears, click “Yes”.

Operation completed successfully.

• If “No” or “Cancel” is selected, no operation is performed.

5.1.3 Agent Connectivity Check Verify IP connectivity from the server backup agent to ARCA via Agent Connectivity Check.

To run:

• Go to “Start > All Programs > Accessories > System Tools > ARCA Backup Agent > Agent Connectivity Check”


The “Connectivity Check” window opens.

• Verify the ARCA Name. If the name is incorrect, type the correct name and click “Test Connection”. You can also check

by IP address.


Note: If you are receiving backup or communication errors, after the connection is successful click “Update Setting” to update ARCA configuration settings.

Note: If you receive a “Connected successfully” prompt, retry your backup job. You may have an authentication failure from the ARCA.

• Login to the ARCA and verify connectivity through the Backup Management Console and re-authenticate to the server.


• If it fails with “ERROR in connection”, retry the steps above.

Note: If you still cannot connect, archive your current backups, reinstall the backup agent and retry the backup job.

If the issue is not resolved after retrying these steps contact support.

5.1.4 Backup Job Creator Verify backup job was created during backup agent setup

To run:

• Go to “Start > All Programs > Accessories > System Tools > ARCA Backup Agent > Backup Job Creator”

Backup Job Creator launches.


• Click “Next” to start job creator.

• Verify the “Backup job is already present” prompt appears (the job was configured during agent install)

• Click “OK” to close.


5.1.5 Clean State Backup Assistance Clean state backup (CBSA) must be configured on the server side. CBSA is Zenith’s version of VSS (Volume Shadow Copy

Service). If an application is not VSS-aware, run CSBA to force applications to flush in-memory transactions to disk. It is

disabled by default.

Launch “Clean State Backup Assistance” from Start Menu > All Programs > Accessories > System Tools > ARCA Backup

Agent > Clean State backup Assistance

This launches “Clean State backup Assistance” (CBSA). CBSA is disabled by default.


If there are no applications that require CSBA, click “Close”. To verify if an application is VSS aware check with your applica-

tion vendor. Common applications that are VSS aware include the Windows System State, most system services, and Mi-

crosoft Back Office 2003 and above (this includes Exchange and SQL). Version of Back Office 2000 applications and earlier

are not VSS aware.

If any applications require CSBA click “Proceed”. This opens “Clean State Backup Configuration”.


Define Schedule: Daily or Weekly

If “Weekly” is selected, “Schedule Day” option appears. Choose a day of the week to run.

View “Essential Services” or “View All Services”, essential services are highlighted yellow.


Clicking the help “?” button explains Essential vs. All Services. After CSBA stops the services, they will auto start within

seven minutes.


Check the service or services to enable CSBA (IIS Admin Service in the below example)

Click “Save”, the CSBA Backup Configuration window stating the following services have been selected appears:

• Confirm you choice and click “Save & Close”. Saving enables CSBA for the selected services.


To return to scheduler click “Cancel”.

When CSBA is reopened the state is enabled with the services selected.

Click “Proceed” to view status

Verify “ARCAScheduler” service is started. The service runs under the “Local System” account.

If CSBA is enabled, ensure the “ClStateBackAsst” service is running.



6 Backup Job Configuration & Modification - ARCA

After server configuration is complete, you must make a connection to the server, verify the backup job schedule, and enable

the backup job. The backups are disabled by default.

Login to the ARCA

Launch the “Backup Management Console” from Start > All Programs > ARCA > Backup Management Console or through

the ARCA Dashboard, “ARCA Administration” section.


This launches “Backup Management Console”. Connect to servers and manage backup jobs from this interface.

If not servers are added to the console the above prompt appears.


You can also open the Backup Management Console via the system tray “shield icon”

The shield is blue when connected to a server, red when disconnected

To connect to the installed server, it must be added under Network View. This adds a default node called “New node

%number% in a disconnected state.


Enter the following information to connect to the server under “Server Properties”:

Server Name – NetBIOS Name

Server Address – NetBIOS Server Name or IP (can be same as server address)

Domain Name – leave blank if the server is connected to a workgroup

User Name – admin user account name

Password – admin user account password


After server information is entered click “Connect”, this changes the Status from “Disconnected” to “Connected” and

the server connects to the management console (see below screenshot).


After the server is connected, navigate to the “Backup Jobs” tab. You will see the backup job created in a “disabled”

state.

The next step is to enable the backup job. To enable, right click the job and select “Enable”.


Job status changes from “disabled” to “enabled”.

Backups will start running based on the specified schedule defined during agent setup. You can view and edit the

job schedule by right-clicking “Edit Schedule”. The job status changes to disabled.

If “Use VSS” is checked under “Additional Incremental Backups” every backup will be VSS.

Please refer to the Zenith ARCA Administrator’s Guide for additional job configuration options.

6.1 Verifying Backups

After backups are enabled you must verify that they are running according to schedule. If alerting was configured, you will

receive backup alerts depending on the template configuration. Backup Jobs have the following statuses:

Disabled – job disabled, “on hold”

Initializing – job initialing (changing state)

Queued – job queued, job is in this state between scheduled job runs

Running – job running

Aborting – job cancelled

Successful – job completed successfully

Failed – job failed


Job Schedule

Job Status


To view backup history:

Click “Backup History” tab

Click “Details” for additional job information.

For troubleshooting failed backups, please see the Zenith ARCA Troubleshooting Guide

Backup logs are written to the server under:

\\%servername%\c$\Program Files\Zenith\Zenith Infotech\Logs

The Backup Management Console is just a console to view those logs. For archive purposes, logs can be copied and

parsed separately. The capacity to view the last backup is available through the ARCA Reporting Dashboard and emailed

via template configuration.

6.2 ARCA Backups Explained

The ARCA utilizes ShadowProtect for backup snapshots. All backups reside on the ARCA under “D:\Backup”. Folders are

named with a UID (unique identifier) followed by server name. Files within each folder are named with the partition name

followed by a UID based on run.


Examples: Server Names: “pmg-win2k3” and “zenexch”

Folder contents “zenexch”

The first backup of a server is the “base” or full backup or *.spf file,

Subsequent backup files are incremental files based upon the full backup.

If you selected backup encryption, an *.spk (keyfile) will be in each directory

Any files with the word “Migration” in them were used for Standby Server Virtualization

ARCA Backup Retention Policy:

• Base Full backup (*.spf)

• All Monthly Incremental backups (*.cm.spi)

• Five weekly incremental backups (*.cw.spi)


• Fourteen daily incremental backups (*.cd.spi)

• Two days of intra-daily incremental backups (*.cd)

The following chart explains each file type:


The following chart explains each compression level:

6.2.1 Backup Encryption When you create a backup image file, either manually or through a scheduled job, you can choose to protect the file using password protection and encryption of the backup image file. This is useful if the backup image files will be stored on a network or removed off-site and you need to protect against unauthorized access and use. If you select to protect the backup image file, you must specify the correct password in order to mount or restore the backup image.

When you enter a password for the backup image file, you may use alpha and numerical characters. You must confirm the password by typing it again.

Note: Passwords are case sensitive. When you mount or restore a password encrypted backup image file, you will be prompted for the password.

Note: If you do not enter the correct password, or you forget the password, you will not be able to access the backup im-age file. Make sure the password is stored in a secure location. Zenith has no method for gaining access to en-crypted backup image files.

You can select from three methods when encrypting a backup image file.

RC 4 128 bit (Fast) – this encryption option is faster than AES 128 bit, but the resultant image is less secure.

AES 128 bit (More Secure) – this encryption option is more secure than RC 4 128 bit, but will require longer to encrypt the image.

AES 256 bit (Most Secure) – this encryption option is the most secure but will also require the most time to en-crypt the image file.

In addition to bit strength, the password used can affect the security. The following guidelines apply to ensure greatest security with password encrypted backup image files.

• Use at least eight characters. • Use a random mixture of characters, upper and lower case and numbers. • Don’t use a word found in the dictionary. • Change your password regularly or if you suspect your password has been compromised.


6.6 On-Demand Backup Jobs

If a backup has failed, or you want to run a backup on-demand. Connect to the Backup Management Console and connect

to the server in question.

Select the “Backup Jobs” tab

Right click the server and select “Execute (Incremental)”

• The only time “Execute (Full)” should be selected is if the first full backup failed or you want to start a

new backup chain.

Warning: If another full backup is run all subsequent incremental backups will run off of this new full backup. Your current

backup chain will stop.

• Files can still be restored from the older chain but the disk space on the ARCA will fill quicker than

anticipated.

6.7 Editing Backup Jobs

After a backup job is configured you can edit the schedule or edit the job properties. Connect to the Backup Management

Console.


6.7.1 Edit Schedule Console and connect to the server in question.

Select the “Backup Jobs” tab

• Right click the backup job and select “Edit Schedule”

Job gets disabled automatically at this point.

• “Edit Job Schedule” window appears. The job schedule is based on agent install settings.

After job schedule changes are made click “OK” to apply settings.

• Backup job is automatically re-enabled.

6.7.1.1 Edit Job Options: VSS Incremental Backups


Additional Incremental Backups

Start taking backups at this time

Stop taking backups at this time

Minutes between backups – interval between job execution

Recommend setting: same schedule for VSS and Additional Incremental Backups.

Note: Notice the “Schedule” options are greyed out, this is by design. The ARCA does one full backup and scheduled point in time incremental backups appended to the full backup (see ARCA Backups Explained)

6.7.2 Edit Backup Job Properties After a backup job is configured you can edit the schedule or edit the job properties. The backup job settings are defined

during agent setup. Connect to the Backup Management Console.

The job will be automatically disabled and re-enabled during the editing process.

• Select the “Backup Jobs” tab

• Select the backup job and press “Edit”


• “Backup Job Editor” launches. Press “Next”.

• This will bring up the volumes to backup screen. You can select/deselect volumes to backup. Press “Next” to

continue.

• Now you can select a backup image destination. Click “Browse” to manually edit or use the drop down to select

pre-defined destinations. Press “Next” to continue.


Warning: For alerting and replication you must match the backup destination to the following settings:

\\%ARCAName%\%Volume%\%Backup%\%Servername%

• Specify the backup schedule screen appears. You can select the backup schedule (see Edit Schedule section

for details). Press “Next”.


• Backup options screen is displayed. Options are compression, password, and advanced. These values are

predefined during agent setup and are grayed out by design. Press “Next” after options are defined.

Advanced Options – default options are recommended

• Backup – throttle system resources (performance throttling)

• Image – caching, self-healing

• Commands

Warning: Editing “Advanced” options is not recommended.


• This brings up the Wizard Summary. Review the backup job summary and click “Finish” to complete your edits. You are

returned to the backup job.

Warning: Do not select “Execute Now”. If this option is selected you will start a new full backup and your existing chain will be stopped.

6.7.2.1 Editing Destination To edit a backup job destination, select the Destinations tab from the center panel of the main screen.

Console and connect to the server in question.

• Select the “Destination” tab

• Highlight the “Network Share” and click “Edit”. The “Destination” window appears.

• Click “Browse” to edit the backup destination.

• Select “Connect” radio buttons to change authentication credentials.


6.8 Configure Backup Alerting

If you require an email alert sent after every job success and/or failure you may configure it through the Backup Management

Console directly. There are no additional filters with this option. The ARCA does not include an SMTP server. You must

have access to a valid SMTP server to relay alerts. Depending on your SMTP server configuration, the ARCA IP address

may need added to the “allow” relay list.

To setup email alerts:

1. Backup Failures are sent from the ARCA Configuration Panel. You must assign an alert template to each job to en-able this functionality.

2. Enable Agent Options through the Backup Management Console

a. Open the Backup Management Console from the ARCA Dashboard > ARCA Administration.

b. Connect to your server under Network View

c. Go to the "Options" menu and select "Agent Options"

d. Fill out the required information

1. SMTP Server

2. Email From Address (This can be any address)

3. Email To Address


4. User Name (optional)

5. Password (optional)

6. Non-default SMTP Port (optional)

7. Send Email on Success (On/Off)

8. Send Email on Failure (On/Off)

e. Click "OK". This sends a test email to the defined email address. You will receive an email for every suc-cess/failure of the job by server partition depending on the options selected above. Depending on how often your backups run, you will receive multiple emails a day.

Example subject of success: ShadowProtect backup success on PMG-WIN2K3

Body:

start time: 3/29/2009 4:51:22 AM

finish time: 3/29/2009 4:52:29 AM

source path: (C:\) NTFS

destination path: \\ZNAS-PMGTRAININ\D$\Backup\97F1DE95C8D2422D-pmg-win2k3\C_VOL-b001-i015.spi Example subject of failure: ShadowProtect backup failure on PMG-WIN2K3

Body:

29-Mar-2009 04:53:43 service 100 service (build 42) started job manually as incremental

29-Mar-2009 04:53:43 service 104 3.3.0.16 1C25-1975 50F0- 716F-A575-A3CD

29-Mar-2009 04:53:43 service 100 backup volume C:\ (NTFS)

29-Mar-2009 04:53:43 service 509 Cannot get access to destination object


7 Restoring Files and Folders

You can restore individual files and folders using two methods. You can restore files and folders by using the Explore Backup Wizard while running in Windows, or you can restore files and folders from the Recovery Environment.

The Explore Backup wizard allows you to restore files and folders from an existing backup image. This wizard can be run from Windows or from the Recovery Environment. If the operating system is unable to boot, you must boot to the recovery environment to mount and restore files and folders. Table 11 below shows the restore method options and when a particu-lar option should be used based on the state of the computer.

Note: To mount and restore data from an incremental backup image, you must have all previous incremental backup image files and the initial full backup image. If any backup images are missing from the set, mounting and restoring will be impossible.

Note: Backup Management will automatically associate the files required to browse and restore a specific point-in-time backup image. You are only required to select the point-in-time you want to explore.

7.1 Mounting a Backup Image, Mount Point, Read-Only

The mount utility can mount a backup image file as a drive letter on your computer. When a backup image is mounted as a drive letter, the backup image will appear and behave as a drive letter on the computer with all the properties of the original volume.

The mount utility can mount a backup image file as a mount point, which is a directory on an NTFS file system. Mount points overcome the limitation on the number of available drive letters and allow more logical organization of files and folders.

The mount utility mounts the backup image as read-only. By mounting a backup image as read-only you can be assured that the backup image can not be changed while providing access to the image file to end users for file or folder recovery. Mount a backup image as read-only when: • You want to recover files from an existing backup

• You want to view the contents of a backup

• You want to run other applications on an existing backup image such as a storage resource manager.

7.1.1 Mounting a Backup Image as Writeable You can also mount backup image files as writeable. By mounting a backup image as writeable, you have the ability to remove files from the backup image, such as viruses or other malware. You can also add files to the backup image file. Mount a backup Image as Writeable when: • You want to update the security on the image file;


• You want to update an existing image file, such as removing a virus.

• You have access issues when restoring data.

7.2 Mounting Backup Images Using the Context Menu

When exploring files using Windows Explorer, the Mount and Quick Mount options are available when right clicking on any backup image file, for a previously mounted image file, you can right click and choose Dismount or Quick Dismount.

7.2.1 Quick Mount When you right click on a backup image and select Quick Mount, the backup image will be mounted as read-only using the next available drive letter.

You can select multiple image files to quick mount, each image file will be assigned the next available drive letter.

7.2.2 Mount When you right click on a backup image and select Mount, the Browse or Restore Files Wizard will initiate. Using the Wizard to mount the backup image, you will be provided with the options of mounting as a mount point or drive letter and the read-only options.

• If your backup file is encrypted a prompt appears to enter the password before the file is mounted.

Note: You can simultaneously mount multiple backup image files, however, you must go through the Mount Wizard for each backup image you wish to mount, or alternatively, you can select to quick mount multiple backup images at once.


7.3 Restoring Files and Folders

1. To explore a backup image, select Explore Backup under Tasks in the left panel of the main screen or select Explore Backup from the center panel of the main screen. The third method to start the wizard is to select Tasks > Explore Backup from the Menu Bar. This will start the Explore Backup Wizard. Press “Next “ to Continue.

2. This will bring up the Backup Image File Name dialog screen. Select the image file you want to browse. You can either provide a path name to the file or click the Browse button to locate a file.


• If your backup file is encrypted a prompt appears to enter the password before the file is mounted.

• Enter the encryption password and click “OK’. To view the image properties.

Note: Once you have selected a backup image file to browse, the properties for that backup image will be displayed. You can view information about the image file, originating partition, disk information and originating machine information.

Note: If you have selected a backup image file to which you have already saved changes, you will see a list of the depend-encies of that image file, along with further information about the image and the originating machine from which the backup came. You can also view the original disk layout from the image file you selected.

3. This brings up the Backup Image Dependencies dialog screen. This dialog presents all the points-in-time in the backup image set you selected. You can verify your selection or select another point-in-time from the image set. You can view information about the image file, originating partition, disk information and originating machine information. After select-ing the point-in-time, press the “Next” button to continue.


4. This will bring up the Specify Options for Exploring an Existing Backup Image dialog screen. Select the radio button cor-

responding to the method you wish to use to mount the image. We recommend mounting the file as the next drive letter for ease of use.

• Select your explore options and press “Next”.


Note: To mount the backup image as a writeable volume, simply uncheck the box beside Mount Backup as Read-Only.

5. This brings up the Wizard Summary (see Figure 34). Review the summary and press “Finish” to mount the

backup image. After the backup image has been mounted, the image will automatically be brought up in Win-dows Explorer as a mounted volume.

6. With the backup image mounted, you may browse the contents of the volume as you would a regular volume, se-lecting files and folders you wish to copy and restore to a previous point-in-time.

7.4 Restoring Backup Image Files

To restore volumes boot to the Recovery Environment to perform the restore. This option must be used when restoring the system volume where the operating system resides.

You can start the Restore Wizard by clicking the Restore button in the left panel of the main screen or clicking on the Restore Wizard from the center panel of the main screen. This can be done from the Recovery Environment CD. 1. To start the Restore Wizard, select Restore under Tasks in the left panel of the user interface or select Restore Wizard

from the center panel of the main screen. This will start the Restore Wizard. Click Next to Continue. 2. This will bring up the Backup Image to Restore dialog screen. You will need to locate the image file you wish to restore

from a destination location. These destination locations can be a local directory or network share.

Note: If the image file you wish to restore is located in a previously defined destination location, then select the destination and locate the backup image set from the list. The next dialog screen will let you select the specific point-in-time as-sociated with the backup image set.


Note: If the image file you wish to restore is not located in a previously defined destination location, you will need to browse to the location of the image file you want to restore.

7.5 Dismounting Backup Image Files

Once a backup image file has been mounted using the mount utility, it will remain mounted until it is dismounted. You can dismount a mounted backup image using the Backup Image Dismount Wizard, which is available through the management console or through a context menu option that is available on mounted backup image files.

This wizard guides you through dismounting a backup image you have previously mounted and assigned a drive letter or mount point location. The wizard will also help you save changes made to backup images that were mounted as a write-able image file.

7.5.1 Dismounting Backup Images Using the Context Menu You can dismount a mounted backup image file by right clicking on the mounted drive or mount point from Windows Ex-plorer and selecting one of two dismount options from the context menu. The options are Dismount or Quick Dismount which are described below.

7.5.1.1 Dismount When you select Dismount from the context menu of a mounted backup image file, the Backup Image Dismount Wizard will start and walk you through the steps of dismounting the image file and giving you the option to save changes made to the mounted backup image file if it was mounted as a writeable image.

7.5.1.2 Quick Dismount When you select Quick Dismount from the context menu of a mounted backup image file, the dismount utility will dismount the mounted backup image file without any further action or dialog. The image will be dismounted without saving any changes made to the mounted image file.


Note: Quick Dismount will dismount a backup image file without saving any changes made while the backup image file was mounted. If you wish to save changes, you must mount the backup image file as writeable and then dismount using the Backup Image Dismount Wizard and save changes.

7.5.2 Dismounting a Backup Image File Using the Backup Image Dismount Wizard

1. To start the wizard click Dismount Backup Image from the left pane of the main screen or select Tasks > Dis-mount Backup Image from the menu bar. This will bring up the Backup Image Dismount Wizard welcome screen.

1. Press “Next” to continue. This will bring up the Mounted Backup Images dialog screen. 2. Select the backup image volume you want to dismount by placing a check in the box next to the volume. You can also

view the properties of the mounted image file in the lower window. Press “Next” to continue.


3. This will bring up the Backup Image dismount Options dialog screen. If you have selected a volume that was writeable, you will have the option to save the changes you have made to that volume while it was mounted. You can save the changes to an incremental file upon dismount.

4. Select whether you want to save the changes made to the mounted volume by placing a check mark in the Save changes to incremental file box. You can rename the file by double clicking on it under the Incremental Name section of the screen. Press “Next” to continue.

5. This will bring up the Backup Image Dismount Summary dialog screen. View the summary to ensure everything is cor-rect and press “Finish” to dismount the volume.

Note: Backup images that have been mounted will be dismounted after a reboot or by using the Backup Image Dis-mount Wizard from the main screen.


8 ARCA Administration

ARCA Administration utilities are accessed via the ARCA Dashboard. This section contains includes the Backup

Management Console, Exchange Recovery Tool, Verification Tools, and Emergency Clean Up

• Exchange Recovery Tool - Ontrack Power Controls, view and restore exchange objects

• Backup Management Console – view and edit backups, restore backup files

• ARCA Health Check – verifies all system services and processes are running for proper operation

• Chain Verification - verifies the backup chain of a selected file. This runs a chain dependency verification of all files in the backup chain up to the selected file for consistency.

• Emergency Clean Up – deletes files that are no longer needed per server

• File Verification – verifies the consistency of a selected backup file.

• Backup Chain Continuity Check - matches all the GUID entries of a selected backup file up to the base to en-sure the chain is valid.


8.1 Exchange Recovery Tool

View and restore exchange objects using the Exchange Recovery Tool. The ARCA utilizes Ontrack Power Controls. For the

utility to access backups, a point in time backup file must be mounted, see section 12.2 Backup Management Console – Ex-

plore Backup for instructions. We will go over the options and how to browse and restore objects and databases.

To launch the exchange recovery tool navigate to the Start Menu > All Programs > ARCA > ARCA Administration > Ex-

change Recovery Tool.

The Exchange Recovery Tool can also be launched through the ARCA Dashboard. From the dashboard:

• Click “ARCA Administration”

• Launch “Exchange Recovery Tool”



• This launches Ontrack Power Controls. Close the “Data Wizard” if it launches on start-up.

Icon View – Source

Icons (left to right)

• Open Source – open source backup file

• Open Target PST – open target pst file

• Open Target Exchange Server – connect to target Exchange Server

• Open Target CAS – open target content analysis file

• Copy – copy selected exchange objects

• Paste – paste selected exchange objects

• Export – export selected exchange objects in msg or txt format

• Find – search exchange objects by specified criteria

• Message authors or readers

• Subject

• Date

• Keyword(s)

• Attachment(s)

• Preview Pane – enable/disable message preview pane

• View Help – launches PowerControls help

• Kroll Company on the Web – launches www.kroll.com (makers of Ontrack)

• Message Table View – shows all folders that reference a single message

• Attachment Table View – shows all messages that reference a single attachment

• Conversation View – allows the administrator to see a histogram of all replies or forwards associated with a

given message to analyze the conversation thread

Note: Source PST and CAS files are not supported in the ARCA version of Ontrack PowerControls


8.1.1 Exchange Recovery - Source Options In the following sections we will review how to restore messages or mailboxes. After you have successfully mounted a

backup file that contains your Exchange database file and log files you can restore data. After a source is opened, you can

restore data, search the message store, view store properties and create reports.

• Launch Ontrack PowerControls

• Ontrack PowerControls opens. To begin open the source file.

• Click “Open Source” button, or File > “Open Source”

“Select Source Files” window opens.


Browse to the source (*.edb) and log file path (*.log). You can also open an existing pst file.

Note: Multiple source files can be open at one time

• The log file path should be automatically filled in if the matching logs are where the database expects them to

be and that location is mounted. If the “Temporary File Path” is empty recreate it when prompted.

• Exchange default installation path on source server: “C:\Program Files\Exchsrvr\MDBDATA”

• The default mount path will be the drive letter selected when mounting, in our example: “F:\Program Files\Exchsrvr\MDBDATA”

• Default Exchange database files (you may have additional databases depending on your environment):


• priv1.edb – default private store – contains user mailboxes

• pub.edb – default public store – contains public folders

• tmp.edb – temporary workspace for processing transactions, contains temporary information that is

deleted when all stores in the storage group are dismounted or the Exchange Information Store

service is stopped

Warning: DO NOT SELECT TMP.EDB FOR RESTORE (you will receive an error)

The Exchange database will load in the “Source” window. Additional icons are now available.

Expand the source database to browse to an individual mailbox, message or other object.


Double-click an object to open it. View the message details including any attachments.

• Click the “paperclip” icon to save attachments.

8.1.1.1 Message Options Right click a message, options are:

• Integrity Check – checks object integrity

• Open – open object

• Copy – copy object

• Select All – select all objects


• Export – export object to .msg or .txt file

• Message Views – change views (see views explanation in above section)

• Message Table View

• Attachment Table View

• Conversion View

• Export any Exchange object up to the database (example below) to a selected location by typing the path or browsing to

the export destination.

• Choose to export in .msg or .txt format and click “Export”

• “Export Progress” window appears. When the export is finished, you can “Print” or “Save” the report.

• Click “Close” to return to PowerControls


Note: If you are exporting more than once the files WILL be overwritten if the path is not changed.

These options are also available from the menus and icons above and apply to all Exchange objects (including stores).

8.1.1.1.1 Additional Store options:

o Stores (source database) – Properties and “Create Reports”

• Parent Objects (Calendar, Contacts, Inbox, etc.) – Properties


• To close the source store right click and select “Close Store” or go to the root “Sources” and click “Close All

Stores”. You can also close stores via the “File” menu.

8.1.2 Exchange Recovery - Target Options After a target destination is opened, you can restore data from opened source files to a .pst, content analysis file (.cas), or

target Exchange Server.

Icon View – Target

• Expand the source database to browse to an individual mailbox, message or other object.

• Double-click an object to open it. View the message details including any attachments.





• Delete – open object – confirm prompt appears on delete

• Paste – paste object

• Paste Special – paste object – maintain the directory structure of restored items

• Select all – select all objects at the current level

Delete Prompt


8.1.2.1.1 Additional Store options

Rename & New Folder

• To restore to a target ensure the source file is open. Then open the destination target. Multiple destinations

can be open at one time. You can connect to only one live Exchange Server at a time. If you attempt to

connect to an additional live Exchange Server while a server is already open, the current server connection

closes.

8.1.2.2 Target Types:

a. PST

• To open a target .pst click the “Open Target PST” icon or through the file menu

• Browse to the .pst file and click “Open”

b. CAS • To open a target .cas click the “Open Target CAS” icon or through the file menu.

• Browse to the .cas file and click “Open”


c. Exchange Server • Click “Open Target Exchange Server” button, or File > “Open Target Exchange Server”

• The “Connect to Exchange Server” window opens

• Type the mailbox and server name to connect to and click “OK”. Click “Cancel” to close.

• The “Connect To Public Folders” option is selected by default. This feature allows you to open public

folders as a target for restoring public folders or messages. If you do not want to restore to public

folders, deselect this check box.


• If this is the first time authenticating to the Exchange Server, the following connection prompt appears

while processing the target file.

• Enter administrative credentials for the Exchange Server mailbox and click “OK”. The prompt may appear again,

which requires you to reenter this information.


• After the target file is processed, the Exchange Server opens in the target window. This is the live Exchange

Server and any changes made here will affect the live server.

• To restore from the source to the destination, export or copy and paste the Exchange Object(s).

• Hold down the “Ctrl” button to select multiple objects at one time.


• “Copy Progress” window appears. When the export is finished, you can “Print” or “Save” the report.

• Click “Close” to return to Powercontrols


• To close target store right click and select “Close Store”. If multiple target stores are open, they must be closed

individually. You can also close stores via the “File” menu.

8.1.3 Connecting to Exchange 2007 Mailboxes

To connect to an Exchange 2007 mailbox, the following steps must be followed:

1. Create a test account in Active Directory. 2. Assign the test account full permission on the mailbox you with to open.

a. Open the Exchange Management Console. b. Go to Recipient Configuration. c. Select the mailbox you want to be able to connect to. d. Choose Assign, Manage Full Access permission. e. Add the test account.

3. Use the test account credentials to open the destination mailbox in the Exchange Recovery Tool while connecting to the Exchange server.


9 Exchange Restoration (Database Only)

To recover the Exchange database, a soft recovery must be performed.

Types of Recovery

There are two forms of recovery:

• Soft recovery A transaction log replay process that occurs when a database is re-mounted after an unexpected stop, or when transaction logs are replayed into an offline file copy backup of a database.

• Hard recovery A transaction log replay process that occurs after restoring a database from an online backup.

Note: For more details on Soft Recovery and Hard Recovery in Exchange Server 2003, please refer to: http://technet.microsoft.com/en-us/library/aa997761(EXCHG.65).aspx

1. Logon and mount the appropriate backup image of the drive where the Exchange database is located.

2. If the Exchange transaction logs are on a different drive, also mount the image of the drive where the log files are

located.

3. Create a temporary folder on the NAS to restore the files to. In this example, name the folder “restore” on the root of

the C: drive “C:\restore”.

4. Copy the Exchange database and logs from the mounted images into one folder i.e. “C:\restore”.

5. Copy the following files from the Exchange server’s bin directory (normally “C:\Program Files\Exchsrvr\bin\”) to

“C:\restore” on the NAS.

• Eseutil.exe • Ese.dll • Jcb.dll • Exosal.dll • Exchmem.dll

6. One you have copied the database, log files and binaries, proceed with the soft recovery.

7. Open a command prompt and switch to your temporary restore directory, C:\Restore and run following command.

a. C:\Restore>eseutil /r e00 /i /d


9.1.1 Common Eseutil switches Eseutil mode Switch Description

Defragmentation /D

Defragments the database offline but leaves the new, defragmented database in the tempo-rary location with or without overwriting the original database. This mode reduces the gross size on the disk of the database (.edb) by discarding most empty pages and by rebuilding indexes.

Repair /P

Repairs a corrupt offline database by discarding any pages that cannot be fixed. In repair mode, the Eseutil tool fixes individual tables but does not maintain the relationships be-tween tables. Use the Information Store Integrity Checker (Isinteg.exe) tool to check and fix links between tables if the repaired database is a mailbox or public folder database.

Restore /C Displays restore log file (Restore.env file) and controls hard recovery after restoration from legacy online backups.

Recovery /R Replays transaction log files or rolls them forward to restore a database to internal consis-tency or to bring an older copy of a database up to date.

Integrity /G Verifies the page level and ESE level logical integrity of the database. Does not verify integ-rity at the application level. Application-level logical integrity can be verified with Isinteg for mailbox and public folder databases.

File Dump /M Displays headers of database files, transaction log files, and checkpoint files. Also displays database page header information, and database space allocation and metadata.


Checksum /K Verifies checksums on all pages in the database, log files, and checkpoint files.

Copy File /Y Performs a fast copy of very large files.

8. Once the soft recovery is completed, rename the production server’s mdbdata folder to mdbdata.old. Create a new

folder call mdbdata using the same directory structure, typically “C:\Program Files\exchsrvr\mdbdata” (this can be

a different location depending on where Exchange is installed).

9. Only copy the database files (EDB and STM) to the production server’s Exchange database location “C:\Program Files\exchsrvr\mdbdata”.

10. Do not copy the logs and other files.

11. Mount the database from ESM (Exchange System Manager). Once the stores are mounted successfully, delete the

“C:\Restore” folder from the NAS and dismount all images.


10 SQL Database Restoration

1. Mount a point in time backup image containing the database ldf and mdf files.

2. Copy the ldf and mdf files to the server running SQL Server (default location is “C:/Program Files/Microsoft SQL Server/MSSQL/Data”).

3. Restore the ldf and mdf files using SQL Enterprise Manager.

For more information, reference the links below:

http://msdn.microsoft.com/en-us/library/ms177429.aspx http://www.databasedesign-resource.com/sql-server-restore-database.html http://msdn.microsoft.com/en-us/library/aa237568(SQL.80).aspx


11 Active Directory Restoration (Database Only)

1. First mount your point-in-time restore volume for your Windows volume. See Mounting a Restore Volume for instruc-tions. In a standard installation the location is “C:\Windows\NTDS”.

2. Copy the NTDS folder from mounted image to physical server at a temporary folder, i.e. “C:\Temp”.

3. Dismount the image.

4. Request the client to reboot the physical server into Active Directory Restore Mode. To do this, reboot the server and press F8 to go into boot options and choose “Directory Services Restore Mode”

5. After booting into DSRM, you will be asked for credentials. Do not provide the Domain Administrator’s password here. You will require the Directory Services Restore Mode password. This was created when the server was pro-moted to a DC. Have the client enter the password obtain it from the client. If the client doesn’t have the password, this needs to be reset by following the Microsoft KB KB322672 “How To Reset the Directory Services Restore Mode Administrator Account Password in Windows Server 2003”

6. Once you boot into DSRM, rename the “C:\Windows\NTDS” folder to “C:\Windows\NTDS.OLD”. 7. Copy the “C:\Temp\NTDS” folder to “C:\Windows”. 8. Switch to the directory where the database is located “C:\Windows\NTDS”.


9. In a command prompt run the command

a. C:\Windows\NTDS>esentutl /r edb /d /8

10. If the soft recovery is unsuccessful or terminates with an error, the Active Directory database needs to be repaired. Proceed with the next step.

11. To repair the Active Directory database, switch to the active directory database folder (C:\Windows\NTDS) and run

following command from a command prompt

a. C:\Windows\NTDS>esentutl /p ntds.dit

12. You will be prompted with following warning, click OK to proceed.

13. The repair process will start. 14. Once the repair process is completed, delete or move all the .log files from C:\Windows\NTDS and reboot the server

in normal mode. The Directory Services will now start normally.


11.1 ARCA Health Check

Run “ARCA Health Check” to verify the list of installed ARCA components and that all required processes are running and

system services are started.

To launch ARCA Health Check navigate to the Start Menu > All Programs > ARCA > ARCA Administration > ARCA

Doctor. You can also access the health check under the “ARCA Administration” of the ARCA Dashboard.


ARCA Health Check launches.


Click “Start” to run health check.

o Blue status = success or service running

o Red = fail or service stopped


• Click “Finish” to close health check, following prompt appears.

• Click “Yes” to close exit prompt.


If errors are found:

• Attempt to restart any stopped services.

• Reregister failed componenets using “regsvr32” in the command line.

Example: Register zrVBox.dll

Note: If errors cannot be resolved contact support.

11.2 Backup Management Console

We reviewed the backup management console in section 8.3 Backup Job Configuration.

You can also mount and restore backup files from here. Backup files can also be mounted and dismounted directly from

Windows explorer by right clicking the file and select “Mount” (wizard) or “Quick Mount” (enter password only). When

dismounting right –click the mounted drive and select “Dismount” or “Quick Dismount”.


For additional Backup Management configuration please see the ARCA Administrator’s Guide.

11.2.1 Explore Backup Mount existing backup files.

• Launch “Backup Management Console” from ARCA Dashboard, ARCA Administration.

Backup Management Console opens.


• Click “Explore Backup” under the “Tasks” menu or go to the “Tasks” menu, “Explore Backup”.


This launches the “Explore Backup Wizard”.

• Click “Next” and browse to the backup file.


• Select the backup file and click “Open”


• If the backup is encrypted enter the backup image password and click “OK”.

a. If the password was entered incorrectly, click “Retry” to retype password or “Cancel” to return to the previous

screen.

Warning: If you forget this password encrypted backups cannot be restored and data cannot be recovered. The password can-

not be recovered if it is lost.

After the password is entered, the wizard searches for dependent files in the backup chain to restore to the point in

time backup file selected.


The next screen shows the backup image dependencies.

• Verify the current selection and click “Next” or click “Back” to select another point in time backup file.


The next screen is “Explore Options”.

• Specify options for exploring an existing backup image and click “Next”.

Explore Options Recommended settings

• Assign the following drive letter – mounts the backup file as a drive letter on the ARCA

• Mount Backup as Read-Only – this option leaves the backup file untouched. Only uncheck this option if you come

across permission errors accessing backup files.


• Wizard Summary – verify settings and click “Finish” to mount the backup file.

a. Click “Back” to return to the previous screen or click “Cancel” at any time to close the “Explore Backup” wizard.

Backup file mount process – waiting for arrival


The mounted drive opens in Windows explorer.

• To restore files and folders drag & drop from the mapped backup file to any of the following destinations:

a. Local drive b. Mapped drive c. Network location

11.2.2 Backup Management Console – Dismount Backup Image After you have finished with the point in time backup file, you should dismount the backup image through the Backup

Management Console or directly from the mapped drive.


• Click “Dismount Backup Image” under the “Tasks” menu or go to the “Tasks” menu, “Dismount Backup Image”.

This launches the “Dismount Backup Image Wizard”

• Click “Next” to continue.


The “Mounted Backup Image” screen is displayed with any mounted backup images.

• Select the backup images you want to dismount.


• Click “Next”.

The “Backup Image Dismount Options” summary screen appears.

• Click Next.


• On the “Dismount Backup Image Summary” - verify settings and click “Finish” to dismount the backup file.

a. Click “Back” to return to the previous screen or click “Cancel” at any time to close the “Dismount Backup Image”

wizard.

Verify the backup image is no longer mounted through Windows explorer. In this case “F:\”

11.3 Exchange Recovery Tool

View and restore exchange objects using the Exchange Recovery Tool. The ARCA utilizes Ontrack Power Controls.

For the utility to access backups, a point in time backup file must be mounted, see section 11.2.1 Backup Man-

agement Console – Explore Backup for instructions. We will go over the options and how to browse and restore

objects and databases. For additional options please refer to the Zenith ARCA Administrator’s Guide.

To launch the exchange recovery tool navigate to the Start Menu > All Programs > ARCA > ARCA Administration >

Exchange Recovery Tool.


The Exchange Recovery Tool can also be launched through the ARCA Dashboard. From the dashboard:


• Launch “Exchange Recovery Tool”


• This launches Ontrack Power Controls. Close the “Data Wizard” if it launches on start up.

Icon View – Source

Icons (left to right)

• Open Source – open source backup file

• Open Target PST – open target pst file

• Open Target Exchange Server – connect to target Exchange Server

• Open Target CAS – open target content analysis file

• Copy – copy selected exchange objects

• Paste – paste selected exchange objects

• Export – export selected exchange objects in msg or txt format

• Find – search exchange objects by specified criteria

• Message authors or readers

• Subject

• Date


• Keyword(s)

• Attachment(s)

• Preview Pane – enable/disable message preview pane

• View Help – launches PowerControls help

• Kroll Company on the Web – launches www.kroll.com (makers of Ontrack)

• Message Table View – shows all folders that reference a single message

• Attachment Table View – shows all messages that reference a single attachment

• Conversation View – allows the administrator to see a histogram of all replies or forwards associated with a

given message to analyze the conversation thread

Note: Source PST and CAS files are not supported in the ARCA version of Ontrack PowerControls

11.3.1 Exchange Recovery - Source Options In the following sections we will review how to restore messages or mailboxes. After you have successfully mounted a

backup file that contains your Exchange database file and log files you can restore data. After a source is opened, you can

restore data, search the message store, view store properties and create reports.

• Launch Ontrack PowerControls


• Ontrack PowerControls opens. To begin open the source file.

• Click “Open Source” button, or File > “Open Source”

“Select Source Files” window opens.

Browse to the source (*.edb) and log file path (*.log). You can also open an existing pst file.

Note: Multiple source files can be open at one time


• The log file path should be automatically filled in if the matching logs are where the database expects them to

be and that location is mounted. If the “Temporary File Path” is empty recreate it when prompted.

• Exchange default installation path on source server: “C:\Program Files\Exchsrvr\MDBDATA”

• The default mount path will be the drive letter selected when mounting, in our example: “F:\Program Files\Exchsrvr\MDBDATA”

• Default Exchange database files (you may have additional databases depending on your environment):

• priv1.edb – default private store – contains user mailboxes

• pub.edb – default public store – contains public folders

• tmp.edb – temporary workspace for processing transactions, contains temporary information that is

deleted when all stores in the storage group are dismounted or the Exchange Information Store

service is stopped

Warning: DO NOT SELECT TMP.EDB FOR RESTORE (you will receive an error)


The Exchange database will load in the “Source” window. Additional icons are now available.

Expand the source database to browse to an individual mailbox, message or other object.


Double-click an object to open it. View the message details including any attachments.



• Integrity Check – checks object integrity


• Copy – copy object

• Select All – select all objects

• Export – export object to .msg or .txt file

• Message Views – change views (see views explanation in above section)

• Message Table View

• Attachment Table View

• Conversion View

• Export any Exchange object up to the database (example below) to a selected location by typing the path or browsing to

the export destination.


• Choose to export in .msg or .txt format and click “Export”

• “Export Progress” window appears. When the export is finished, you can “Print” or “Save” the report.

• Click “Close” to return to PowerControls

Note: If you are exporting more than once the files WILL be overwritten if the path is not changed.

These options are also available from the menus and icons above and apply to all Exchange objects (including stores).

11.3.1.1.1 Additional Store options:

o Stores (source database) – Properties and “Create Reports”


• Parent Objects (Calendar, Contacts, Inbox, etc.) – Properties

• To close the source store right click and select “Close Store” or go to the root “Sources” and click “Close All

Stores”. You can also close stores via the “File” menu.


11.3.2 Exchange Recovery - Target Options After a target destination is opened, you can restore data from opened source files to a .pst, content analysis file (.cas), or

target Exchange Server.

Icon View – Target

• Expand the source database to browse to an individual mailbox, message or other object.

• Double-click an object to open it. View the message details including any attachments.





• Delete – open object – confirm prompt appears on delete

• Paste – paste object

• Paste Special – paste object – maintain the directory structure of restored items

• Select all – select all objects at the current level

Delete Prompt


11.3.2.1.1 Additional Store options

Rename & New Folder

• To restore to a target ensure the source file is open. Then open the destination target. Multiple destinations

can be open at one time. You can connect to only one live Exchange Server at a time. If you attempt to

connect to an additional live Exchange Server while a server is already open, the current server connection

closes.

11.3.2.2 Target Types:

d. PST

• To open a target .pst click the “Open Target PST” icon or through the file menu

• Browse to the .pst file and click “Open”

e. CAS • To open a target .cas click the “Open Target CAS” icon or through the file menu.

• Browse to the .cas file and click “Open”


f. Exchange Server • Click “Open Target Exchange Server” button, or File > “Open Target Exchange Server”

• The “Connect to Exchange Server” window opens

• Type the mailbox and server name to connect to and click “OK”. Click “Cancel” to close.

• The “Connect To Public Folders” option is selected by default. This feature allows you to open public

folders as a target for restoring public folders or messages. If you do not want to restore to public

folders, deselect this check box.


• If this is the first time authenticating to the Exchange Server, the following connection prompt appears

while processing the target file.

• Enter administrative credentials for the Exchange Server mailbox and click “OK”. The prompt may appear again,

which requires you to reenter this information.


• After the target file is processed, the Exchange Server opens in the target window. This is the live Exchange

Server and any changes made here will affect the live server.

• To restore from the source to the destination, export or copy and paste the Exchange Object(s).

• Hold down the “Ctrl” button to select multiple objects at one time.


• “Copy Progress” window appears. When the export is finished, you can “Print” or “Save” the report.

• Click “Close” to return to Powercontrols


• To close target store right click and select “Close Store”. If multiple target stores are open, they must be closed

individually. You can also close stores via the “File” menu.

11.4 Backup Chain Continuity Check

Backup Chain Continuity Check does an image QP (Queue Pair) verification that matches all of the GUID entries of a se-lected backup file up to the base to ensure the chain is valid. Backup Chain Continuity Check runs daily and is setup via the ARCA Configuration Panel.

• Launch the ARCA Dashboard



• Click the “Backup Chain Continuity” icon. This launches “Backup Chain Continuity Check”.

• Click “Select File” to browse to a point-in-time backup file in the backup chain. The path defaults to the backup directory.


• Drill down to the full (.spf) or incremental (.spi) backup file to verify.

• Double-click or click “Open” on the selected file to propagate the “Select Backup File” field.


• Click “Verify” to start continuity check.

Chain verification can only be run on one file in the backup chain at a time.

• When file verification is complete, view the status. In the example above verification was successful.

• “Press any key to continue” to close the command prompt and return to continuity check.

• Click “Close” and confirm the prompt by clicking “OK” to return to ARCA Dashboard.

11.4.1 Errors For additional error codes and troubleshooting steps refer to the ARCA Troubleshooting Guide :

• No file selected


• Invalid file selected

11.5 Chain Verification

Chain Verification verifies the backup chain of a selected file. This runs a chain dependency verification of all files in the backup chain up to the selected file for consistency. Chain verification runs once per week and is setup via the ARCA Con-figuration Panel.




• Click the “Chain Verification” icon. This launches “Chain Verification”.

• Click “Browse” to select a point-in-time backup file in the backup chain. The path defaults to the backup directory.



• Double-click or click “Open” selected file to propagate the “Image File” field.

• If the backup image is not encrypted, a password file is not required. Click “Verify” to start chain verification.


• If the backup image is encrypted, browse to the backup key file. This file is located in the same directory as the backup

file selected. Each partition has its own key file (.spk).

• File verification can only be run on one file at a time. This can be a time consuming process.

• Double-click or click “Open” selected file to propagate the “Password File” field.


• Click “Verify” to launch chain verification command line utility or click “Close” to cancel.

• When chain verification is complete, view the status. In the example above verification was successful.

• “Press any key to continue” to close the command prompt.


• Click “Close” to exit “Chain Verification” and confirm the prompt by clicking “Ok” to return to the ARCA Dashboard.

11.5.1 Errors For additional error codes and troubleshooting steps refer to the ARCA Troubleshooting Guide:

• No file selected for verification

• Invalid backup file selected

• Invalid password file selected


504 - Key file error – key file not specified for encrypted backup file.

500 - Bad decryption password (incorrect key file specified)

11.6 Emergency Clean Up

The Emergency Clean Up utility deletes files that are no longer needed by the existing backup chain. Run this utility if the

ARCA “D:\” partition is running low on free space. Do not attempt to manually delete files from the backup chain as multiple

errors could result.




• Click the “Emergency Clean Up” icon. This launches “ARCA – Emergency Cleanup”.

• This process will delete the incremental(s) which are not part of the existing backup chain.

• Selection is not provided for the virtual server(s).

• Select servers for cleanup and click “Clear incremental” to clear data

• Select/deselect servers for cleanup via checkbox.

• Servers are listed by color – refer to legend

• The following information is available:

• Server Number – order in which servers were added for backup

• Clear Files

• All - delete the respective folder(s) permanently


• Marks non-empty directories “All” by default

• Orphan – deles only files which are not part of existing backup chain –

• Marks empty directories “Orphan” by default

• Server Name – server name

• Root Folder Path – server directory root path

• Size of Folder – current backup folder size (virtualized servers size not shown)

• Root – “D:\Backup” or “D:\Replica”

• Cleanup – “D:\Cleanup”

• View files – click book icon to view server backup and cleanup folder contents

Note: Greyed out for Virtualized servers

• Click “Close” to return to “Emergency Cleanup”

• Click “Clear incremental” to start cleanup or “Close” to exit the utility.


• Clicking “Clear Incremental” brings up “Are you sure…”

• Click “Yes” to continue, “No” to return to emergency cleanup.

Note: “Clear incremental” and “Close” buttons are grayed out while cleanup is running.

• After cleanup finishes cleanup prompt appears.

• Click “OK” to incremental removed prompt and return to the main cleanup window.


• Click “Close” and confirm the prompt by clicking “OK” to return to ARCA Dashboard.

Note: Verify redundant files are deleted.

11.7 File Verification

The File Verification utility verifies the consistency of a selected backup file. If the backup is encrypted you must enter the password file. File verification runs upon backup file creation. Alerting is setup via the ARCA Configuration Panel.




• Click the “File Verification” icon. This launches “ARCA - File Verification”.

• Click “Browse” to open the “Image File”. The path defaults to the backup directory.




• Double-click or click “Open” selected file to propagate the “Image File” field.

• If the backup image is not encrypted, a password file is not required. Click “Verify” to start file verification.

• If the backup image is encrypted, browse to the backup key file. This file is located in the same directory as the backup

file selected. Each partition has its own key file (.spk).

• File verification can only be run on one file at a time.

• Double-click or click “Open” selected file to propagate the “Password File” field.


• Click “Verify” to launch file verification command line utility or click “Close” to cancel.

• When file verification is complete, view the status. In the example above verification was successful.

• “Press any key to continue” to close the command prompt.

• Click “Close” to exit “File Verification” and confirm the prompt by clicking “OK” to return to the ARCA Dashboard.


11.7.1 Errors For additional error codes and troubleshooting steps refer to the ARCA Troubleshooting Guide:

• No file selected for verification

• Invalid backup file

• Invalid password file

504 - Key file error – key file not specified for encrypted backup file.

500 - Bad decryption password (incorrect key file specified)


12 Virtual Machine

Perform virtualization of servers in a live or sandbox environment for disaster recovery purposes. Servers can also be

virtualized on a remote ARCA or Vault if replication is enabled.

Warning: A dedicated account is recommended when performing server virtualization tasks.

Warning: The VirtualBox hard disk xml files run from the local “Documents and Settings” folder; “C:\Documents and Set-tings\%username%\.VirtualBox”. Virtual machine disk corruption can occur the VM is improperly shutdown.

Any backups made to the virtual machine past the corruption will be invalid.

Warning: Virtual Servers are not intended to run for more than a few days in “Live” Mode. We recommend peri-odically shutting them down and perform a virtualization on a later backup if the server needs to run for an extended period. The sparse and cache files grow over time which can lead to corruption.

Warning: To permanently recover, perform a Bare Metal Restoration to new hardware. This can be to identical or dissimilar hardware or dedicated virtual environment.

12.1 Standby Server

Configuring Standby Server virtualizations in a live, sandbox, and sandbox network environment – the virtualizations run

directly from the backup file and write changes to a sparse file. Virtual servers are used as a temporary solution or testing


mechanism. To recover servers to another physical or virtual machine perform Bare Metal Restore (BMR). For additional

information refer to the ARCA Administrator’s Guide.

• The following virtualization configuration limitations apply:

• Assigned RAM per Virtual Machine (VM) – resources are shared between the ARCA and any created virtual

machines.

• Subtract ARCA system RAM and RAM allocated to existing VM

• RAM allocated to existing VM (even if the VM is stopped) is not available to new VM

• Maximum RAM per VM is 16 GB – this is a VirtualBox software limitation

• Only one instance of the Standby Server Wizard can run at one time under one user account

• Multiple virtual machines can run under this instance dependant on ARCA resources

• Dual boot operating systems are not supported for virtualization

• OEM Software – Windows operating systems must be relicensed due to hardware changes, there may be a grace

period. Contact the software vendor for licensing requirements

• Multi-homed servers (servers with multiple IP addresses) – must bind the virtual Network Interface Cards (NIC)

when creating the VM

• Volumes can be cached for performance – caching is enabled by default and is recommended

To launch the Standby Server Wizard:




• Click the “Virtual Machine” icon. This launches “Standby Server Wizard”.


• Icons (left to right)

• Create – define a virtual server

• Start – start an existing virtual server

• Purge – purge existing virtual server

• Settings – edit allocated RAM for existing virtual server

• Notes – enter notes for any virtual server regardless of state

• Exit – exit Standby Server Wizard


12.1.1 Virtual Server States Backup Server Image and Replicated Backup Server Image - Virtual Server States (left to right)

a. Server available for virtualization – detail fields undefined

• For a server to appear in this list, its backup folder must be located in the “%Volume%:\Backup” directory

along with the full (*.spf) backup file

• In the case of “Replicated Backup Server Image”, the backup must be located in the “%Volume%:\Replica”

directory (only populated in ARCA replication scenarios)


b. Virtual server defined (stopped) – detail fields populated, VM defined but powered off

c. Virtual server running – detail fields populated, VM defined and running


d. Virtual server running under another user account – VM defined under another user account and can only be started

from the account that defined the VM.

Warning: If you logoff the other user account with the VM running, the virtualized server will crash and there is a high pos-

sibility of file corruption.

Warning: If you attempt to manage the server while it is running under another account, the VM will have a “recycle bin”

icon and cannot be accessed by the current user.

To manage the virtual server, logout and login with the user account that defined the VM.


12.1.2 Virtualization Modes

Warning: Virtualization mode cannot be switched or migrated after the VM is defined.

a. Sandbox Mode

• Zero network connectivity

• Use for testing backup images, applying patches, hot fixes, etc

• Backups do not occur in this mode, any changes made are discarded when VM is purged

b. Live Mode

• Network connectivity

• The server that the “Live” virtualization was performed on must be offline

• Backups continue in this mode

• You must perform a Bare Metal Restore to bring back the production server


• Network connectivity with machines on sandbox network – no LAN or WAN connectivity

• Test a group of virtual machines while the production servers are online

i. Example: Exchange and Active Directory on the same private network (firewalled off)

• Test network connectivity and dependent services between sandbox network machines

Note: DHCP does not work in this mode, you must statically assign IP addresses to machines on the same subnet. The gateway is not accessible – this is a private switched network.

Note: Each server is on the 169.254.x.x (APIPA addressing) subnet by default

Example: Two servers running in “Sandbox Private Network”, “zenexch” and “pmg-win2k3”

12.2 Managing Virtual Servers

This section goes through Standby Server interface tasks, from creating and editing a virtual server, to purging and cleanup.

Launch the Standby Server Wizard if not already open. If you attempt to open multiple instances, you will receive an error

message that it’s already running. If the Standby Server Wizard is running under another session, you will also receive this

error. Multiple instances cannot be run at one time.


Note: If there is a backup server and replicated backup server folder with the exact same name and one of them is defined, the below error occurs if another virtualization is attempted with another machine with the same pair name.

Note: If you receive the below error when launching Standby Server, you must register zrVBox.dll.


• To register open a command prompt

• Change to the “C:\Program Files <x86>\ZenithARCA\Vbox\z64” directory

• Type the following command “regsvr32 zrVBox.dll” and press <Enter>

• Re-launch Standby Server


Note: Under “Backup Server Image” you will see the list of servers configured for backup.

Note: Under “Replicated Backup Server Image” you will see the list of replicated servers if replication is setup between sites

12.2.1 Rebooting the ARCA – Defined Virtual Machines If a virtual machine is defined (started or stopped) the following steps must be performed when restarting or shutting down

the ARCA appliance.

VM information is stored via the following policy:

The VM should use base + 001 002 003 004 005 (110, 002, etc = incremental files)

1. Power down the VM if running.

2. Stop and disable ARCA “StorageCraft ImageManager” service (imagemanager.exe).


3. Restart ARCA.

4. If VM needs restarted, power on the VM.

5. Start “StorageCraft ImageManager” service and change the Startup type from “Disabled” to “Automatic”.

Note: If imagemanager.exe is not running, collapsing of backup images will not occur.

Warning: If the above steps are not followed the VM will fail to boot upon restart.

For example, 004 005 are out of retention

When ARCA is rebooted imagemanager.exe will reinitialize and delete 004 005

When the user tries to start VM, incremental 004 005 are deleted (VM boot failure), all changes will be lost

12.2.2 Create a Virtual Machine Create a virtual machine:

• Select the backup folder name and click “Create”

• The Standby Server Wizard launches on the “Enter the password for the backup set screen”.

Note: Click “Home” to return to the main Standby Server screen or “Back” at anytime to go back one screen or “Next” to go forward one screen.


Warning: If multiple base backups exist for a single partition, a warning message appears, to move the old backup chain use the

provided ARCA Copy and Sync utilities.

• Type and verify the backup set password. Click “Next”.

• If the backup file is NOT encrypted leave the password fields blank.

• If there are multiple partitions, all files will be listed.


If the password is correct, the icons change to icons.

• If the password is incorrect or missing, a “Wrong password” message is displayed.


Warning: If any image files are incorrect or corrupted you will receive the following error message and those files will remain in

status. If those files are selected the migration will fail.

After the password is verified the Machine Information screen is displayed with host and guest machine information.

Available and used RAM for the virtual machines is also displayed.

Note: The RAM resource pool is “defined RAM for all Virtual Machines”, not for VMs that are running.


• Define RAM for the virtual server (in mb) and click “Next”.

• If you enter an invalid (too high or low) RAM size you will receive an error. Closing the error returns you to

the previous screen to edit the RAM size.


RAM Overage

Insufficient RAM


• After the RAM is entered the virtual server details screen is displayed. Select the appropriate radio button if

the server is 32 or 64-bit and click “Next”.

Warning: If the incorrect architecture is selected the VM will blue screen when Windows attempts to start.


• The next screen allows an “NTFS disk check” to run before starting the Hardware Independent Restore (HIR).

• Use this option if a previous virtualization attempt failed. Click “Next”.


The next screen shows virtual server mode options.

Virtualization Mode

Sandbox

1. This mode is for testing only.

2. The defined virtual server will not have network access.

3. No backups will occur in this mode.

Live 1. This mode will configure the virtual server to replace a failed server on your network. 2. Only use this mode if you want to use the virtual server as a production server. 3. Backups will continue in this mode. 4. Modifications made while the virtual server is running will be contained in the next backup.


5. Live Mode is not supported for BDR replicated images. These files reside in the “Replica” folder.

i. If attempting to bring up a server in Live Mode to an ARCA or Vault the following message

appears:

Note: To bring up a replicated server replicated from a BDR a complete site failover must be completed. For detailed failover steps please see the Site Level Failover section of this guide.

Sandbox Private Network

1. This mode is for testing multiple machines in a sandbox.

2. Create virtual machines in their own private network.

3. Machines in this mode can only interconnect to each other.

4. This sandbox network cannot access the LAN or WAN.

5. Changes made to the virtual server will be lost when the virtual machine is purged.

6. No backups will occur in this mode.


VIrtualBox Network Adapter in “ARCAPrivateNetwork”

Multi-Disk Mode: Creates a separate virtual hard drive per volume, default is “No”. Select “Yes” for troubleshooting.

• Multi-Disk mode creates a separate virtual hard drive per volume.

• A maximum of 3 volumes are supported in this mode.

Host Interfaces

• Do you want to connect all VM Network Cards to a single Host Interface? Yes/No

Note: If the ARCA has more than one network card this option is enabled.

Warning: Virtualization mode cannot be switched or migrated past this step.

• After all options are selected click “Next”.

• If “Live” mode is selected and the production server is online, you will receive the below error. Resolve by removing

the production server from the network or changing the IP addressing and NetBIOS name.


The next screen is “Hardware Independent Restore”. Add the backup files for migration here.

• You can either add these files manually or use “Time Machine” to select a point in time which selects the same

timestamp for each server partition. Only incremental files are available through the time machine feature. You

must add the full backup manually.

• Clicking “Close” displays “HIR process unsuccessful or user has clicked cancel”.


12.2.2.1 Add files manually Manually add backup files to HIR

• Click the “Add” button.

Windows explorer opens to the server directory selected for virtualization.

• Select a point in time backup file and click “Open” or right click the file and choose “Select”.


• The system partition is required for virtualization. If additional server partitions need added to the virtualiza-

tion repeat the above steps.

• You must select the same point in time backup by time stamp, not necessarily file name.

Warning: If one partition wasn’t backed up during the same time as the other, the virtual server could be in an incon-sistent state.

• “Time Machine” selects the appropriate timestamps automatically.

• After all partitions are added click “Set Boot” on the system partition.

• To remove a partition from the list select it and click “Remove”.

12.2.2.2 Add files using “Time Machine” Use Time Machine to add files to HIR. Only incremental backup files are supported.

Note: If the server backup only contains the full backup file, time machine is not available and the files must be added manually.

• Click the “Time Machine” button.


Please wait creating time machine…

ARCA Recovery Time Machine Console loads with the following tabs (backups saved per retention policy)

• Intraday - point in time intraday backups (3 days)

• Daily - point in time daily backups (14 days)


• Weekly - point in time weekly backups (5 weeks)

• Monthly - point in time monthly backups (all)

• Click the appropriate backup type tab.

• Find & Expand the appropriate date

• Select the appropriate timestamp to view the backup files for that point in time

• Verify the backup file(s) and click “Ok” to add to the HIR window or click “Cancel” to exit the console.


• After all backup files are added, highlight the system partition and click “Set Boot”.

• After files are verified click “Migrate” to start Hardware Independent Restore


12.2.3 Hardware Independent Restore

Warning: “Yes” is auto selected to “HIR has been run before” prompt. Do not click “No”.

• If a driver is not found during the HIR, browse to the appropriate driver or ignore and install it after the VM starts if neces-

sary.


Note: If you receive the above error during HIR, navigate to the description path and delete the root backup directory if the VM is not needed. If issue still occurs contact support.

• For additional errors and troubleshooting steps, refer to the Troubleshooting section of this guide.


12.2.4 Virtual Machine Caching After the HIR (Hardware Independent Restore) migration is complete you are returned to the Standby Server Wizard Cache screen. When the virtual machine is created it runs from two files:

1. Backup Image – copy of the backup file 2. Sparse File – file that captures any virtual machine images

The first screen enables you to enable/disable and select the cache volumes for the virtual machine instance. Caching is enabled by default and is recommended.

Note: Creates “Cache” directory in specified volume – the copy of the backup file must be taken into consideration for total file size. If space is not available, the caching option will be disabled.

Note: While performing caching on a removable drive, ensure the drive remains connected. Virtualization will continue without caching if drive is disconnected.


Note: These files are discarded after the virtual machine is purged. (pair name folder and files). If the VM was defined in “Live” mode, changes are captured and written to the existing backup directory for the server.

Note: If the VM still exists the files are locked “in use” and cannot be deleted manually.

• Check/uncheck the “Enable Caching” options to enable/disable caching of backup images, sparse images, or both. If

caching is unchecked, additional settings will be grayed out. o Select one or multiple drives.

If the virtual machine has multiple partitions hold down the <Ctrl> key to select more than one drive

• If caching is selected, select a “cache drive”. Only one drive can be selected per virtual machine.

o All non-system drives will be listed.

• After caching options are selected click “Next” to go to the “select images” screen.

• Select Primary Backup Images For Caching (all incremental files – spi) • Select Secondary Backup Images For Caching (all collapse files – cd, cw, cm)


• Check/uncheck primary and secondary files for caching and click “Next”.

Note: All the primary files are selected for caching by default but can be selected / deselected.

Note: The secondary files are selected depending on the amount of files available. By default only 25% of the files on each drive are selected.

• The next screen shows the MD5 checksum option.

Note: Selecting “Yes” compares the MD5 checksum which will increase cache processing time.


Press “Start” to begin the caching process.

• The next screen starts the caching process and shows the progress along with the number of files and status.

o Statuses Waiting Processing Done


• The button is automatically enabled if any files fail to cache. You have the option to proceed without retry-ing by pressing “Next”. o Press “Retry” to reattempt the caching process on the failed files. o Press “Cancel” to skip the caching process.


Note: Files that fail to cache are indicated by a check box which is automatically checked for retry.

• Press “Next” to continue to the “Notes” screen.

Note: If “Cache Sparse Volumes Only* is selected the only screen that appears is the “complete” prompt.


12.2.5 Virtual Machine – First Boot Steps

• After cache options are set you are returned to the “Notes” screen.

• Type any notes for the defined VM and click “Next”.

• Selecting the VM again displays previously added notes.


• Message box (with instructions to perform on first boot) is displayed for 15 seconds – top number is system time, bottom

number is the boot countdown (see above screenshot)

• Virtual Machine starts.

• If the VM is running off of an encrypted file, the “enter password” prompt is automatically filled in and the server boots

to Windows without user intervention.


a. For Windows 2003 – Select “Microsoft Windows” b. For Windows 2000 – Select “Microsoft Windows (WINNT)”

• Press “Ctrl-Alt-Delete” in the VM menu “Machine > Insert Ctrl-Alt-Del” to login.


• Type your password and click “OK” to login.


Note: In VirtualBox the default “Input” key to switch from the VM to the physical server is “Right Ctrl”.

Note: On first boot in Live Mode choose “Safe Mode”. This will allow you to install VM Guest Additions and run Standby Server Helper.

• When you first login to a defined VM you may receive an “unexpected shut down” message. This is expected.


• Select a meaningful reason or type a comment regarding shutdown and click “OK”.

Warning: Once you login, you may be prompted to Activate Windows again due to significant underlying hardware changes. If

Windows is not activated, you will not be able to login.


12.2.5.1 Sandbox Virtualization – additional steps

12.2.5.1.1 Standby Server Helper Install

Run Standby Server Helper according to the virtualization mode. The Standby Server Helper ensures your IP and MAC

address settings match the original server.

To run:


• Select “Sandbox Mode”.





Note: DHCP does not work in this mode, you must statically assign IP addresses to machines on the same subnet. The gateway is not accessible – this is a private switched network.

Note: Each server is on the 169.254.x.x (APIPA addressing) subnet by default

12.2.5.2 Live Virtualization – additional steps

When booting up for the first time in live mode, press “F8” to boot into “Safe Mode with Networking”. This will allow you to

confirm network setting and run “Standby Server Helper” after the VM is booted.

Once the VM boots: Install VM Guest Additions and run Standby Server Helper.

12.2.5.2.1 VM Guest Additions

VM Guest Additions is software that can be installed inside virtual machines to improve performance and make integration

much more seamless. Among the features provided by these Guest Additions are mouse pointer integration and arbitrary

screen solutions (e.g. by resizing the guest window). Guest additions also increase the speed of the VM Network Interfaces.


To install:

• In the VM click go to “Devices > Install Guest Additions”

The “Virtual Box Guest Additions Welcome” window loads.


• Click “Next”.

• Select the “I accept the terms in the License Agreement” radio button and click “Next”.

• Select the “Destination Folder” location and click “Install”.


Note: You may receive notifications that the software has not passed Windows Logo testing. Click “Install” to continue. You may need to <Alt+Tab> through the prompts that appear.

Note: You may also receive notifications that the software is signed with Authenticode technology. Click “Yes” to con-tinue.


• Once the installation is finished select “Reboot Now” radio button and click “Finish”, or manually reboot after

installing running Standby Server Helper.

12.2.5.2.2 Standby Server Helper Install

Run Standby Server Helper according to the virtualization mode. The Standby Server Helper ensures your IP and MAC

address settings match the original server.

To run:



• Select “Live Mode”.




12.2.5.3 Windows 2008 – additional steps

1. When booting a Windows 2008 virtual server for the first time, boot into the Storagecraft Recovery Environment. The .iso is already attached as default in the virtual server.

2. Select the recommended option, [1] Start Vista-based Recommended Recovery Environment and press <Enter> to run.


3. Press CTRL + SHIFT + F12 keys. 4. Click menu "Tools" "Command Shell" to set the boot manager. If you do not see the Command Shell in the Tools menu,

another way to get there is to browse the file explorer via “Tools” “File Browser”.


5. If you need to go through the File Brower to launch the command prompt, navigate to:

CD Drive (D:\)SHADOWPROTECT/I386/SYSTEM32 and run CMD.exe.


6. In the command prompt run: X:\Windows\System>C:

C:\>bcdedit /set {bootmgr} device "partition=C:"

C:\>bcdedit /set {default} device "partition=C:"

C:\>bcdedit /set {default} osdevice "partition=C:"

C:>exit

7. Perform a clean reboot of the Virtual server through menu "File" "Exit" or else the backup within the Virtual server will be a differential.

8. You will be taken to a “Windows Error Recovery” screen. Boot the server hard disk and select Safe Mode with Networking. This may take a few minutes to start up.


9. If you are prompted to run a check disk you must let the check disk complete before continuing with the Virtual Server boot process.

10. You will boot directly to Windows.

12.2.6 Shutdown a Virtual Machine To properly close a virtual machine:

From the VM go to “File > Close” or close the window via the “Close” button (in blue).

Warning: The “Take Snapshot” option is not supported as we do not utilize .vhd files (virtual hard drive). The ARCA uses a

sparse file which shows as a custom hard drive.

After “Close” is selected, the following options are available:

• Save the machine state – saves any changes and shuts down

• Send the shutdown signal – proper shutdown (Start > Shut Down in Windows)


• Power off the machine – improper shutdown (hard reboot)

12.2.7 Start a Virtual Machine To start a defined virtual machine that is not running:

• Select the backup folder name of the defined server and click “Start”

• If VM is not in a defined state or if it is currently running “Start” is grayed out.


Standby Server Wizard opens

• Enter and confirm the password, click “Next”.


• If the backup is encrypted, the password is auto-filled and the VM starts.

12.2.8 Purge a Virtual Machine After you are done with the Virtual Machine and you do not need to use it again, purge the VM to save resources. The VM

must be defined and in a “stopped” state.

Select the backup folder name of the defined server and click “Purge”

Note: If VM is not in a defined state or if it is currently running “Purge” is grayed out.

Standby Server Wizard opens.


• Enter and confirm the password, click “Next”.

The VM is purged and you are returned to the main menu.

Note: Verify the server state has changed to undefined.

12.2.9 Virtual Machine Settings Virtual Machine settings and notes

a. Settings – change defined virtual machine RAM settings (VM must be in a stopped state otherwise the

settings option is grayed out)

1. Select defined virtual machine and click “Settings”.


Standby Server password screen appears

2. Type and confirm encryption password (leave blank if password is not encrypted) and click “Next”

Backup image password is confirmed


VM Information screen appears.

3. View and specify new RAM size (in mb) if required.

4. Click “Next” to update RAM size and return to Standby Server.

b. Notes – add notes to a virtual machine in any state

1. Select virtual machine in any state and click “Notes”


Notes screen appears

2. View defined notes in the top half of the screen

3. Add notes by directly typing them in the bottom field “Click Here to Add the Notes”

4. After notes are added click “Next” to return to Standby Server.

c. Exit – Exit Standby Server

1. Click “Exit” button in Standby Server


13 Support

Direct links to the ARCA Support Portal and Remote Support Web Site

13.1 ARCA Support Portal

Launch ARCA Support Portal website

From the ARCA Dashboard:

• Click “Support”

• Click the “ARCA Support Portal” icon.


https://support.zenitharca.net support website link opens in a web browser

• Enter your support credentials to continue and receive support including:

• Ticketing

• Online Support

• RMA Requests

Note: Please see the ARCA Quick Start Guide for support portal details.


14 Reporting Dashboard

The Reporting Dashboard shows available ARCA Reporting.

• “Backup Analysis” shows Backup Status and detailed reporting against backup jobs.

• “Backup History” - select backup detail report by date

14.1 Backup Analysis

View latest backup report.


• Click “Reporting Dashboard”.

• Click the “Backup Analysis” icon.


ARCA – Backup Analysis launches to “Backup Status” page


Buttons (left to right)

• Go Back – go back one screen

• Go Forward – go forward one screen

• Home – go home

• Refresh – refreshes report screen

• Email – email report

• Print to PDF – print PDF report

• Export to Excel – exports report to Excel format

• Print Current Report – prints report

• Help – report help

• Close – closes backup analysis

Server States

• Server setup creation successful – server name pink

• Server setup creation failed – server name brown

• Server installed successfully – server name blue

• Server installation failed – server name black

• Server uninstalled – server name gray

Backup Status

• Last backup status success – backup schedule green

• Last backup status failed – backup schedule red


14.1.1 Navigating Backup Analysis Click “Back”, “Next”, and “Home” buttons to navigate between report screens. Microsoft Excel is not preinstalled with the

ARCA.

14.1.1.1 Device Information Click “Server” link to open device information

• Last Backup Status

• VSS Incremental Backups (schedule)

• Incremental Backups (schedule)

14.1.1.2 Backup Image Analysis Click “Last Backup Date” link to open Backup Image Analysis (last 100 Backups)

• Backup Status


• View Details

• Click anywhere on this page to view backup details


14.1.2 Backup Image Details • Creation Date

• File Name Status

• Reason for failure (if failed)

14.1.3 Email Email Backup Analysis Reports

• Click “Email” button

ARCA – Backup Analysis Email opens


Report options:

• PDF Format

• Excel Format (only available if Excel is installed – not included)

Clicking “?” help button brings up the above prompt if Excel is not installed.

Reports available:

• Current Backup Status

• Entire Servers

• Choose report format and type and click “Proceed”.


Email Report window appears.

Specify the following fields:

• TO

• CC (optional)

• Subject (editable)

• Message Body (optional) Click the “Address Book” icon beside the “To” or “CC” fields to bring up email addresses and groups previously configured in “Configuration” section.


• Select an address and click “To” or “CC” buttons to add to recipient fields.

• Click “OK” to return to email.

After fields are specified click “Send”


If “To” field was not specified, the following error occurs:

Mail sent successfully

• Click “OK” to return to “Backup Analysis”

Recipient will receive the report via email in zip format.


14.1.4 Print to PDF Print Backup Analysis Report to PDF, no PDF viewer is installed by default.

• Click “Print to PDF” button

ARCA – Backup Analysis PDF Report opens

Reports available:


• Entire Servers

• Click “Browse” folder to specify a location to save the file.


• Name the file and click “Save”

File path populated

• After file path is specified click “OK” to print PDF or “Close” to cancel.


• Click “OK” to successful prompt and browse to file saved location to access report.

Select file location prompt appears if no file path was selected on save.

If filename exists, overwrite prompt appears.

o Click “Yes” to overwrite

o Click “No” to specify another filename.


14.1.5 Export to Excel Export Backup Analysis to Excel (not installed by default). This option is only available if Excel is installed.

• Click “Export to Excel” button

ARCA – Backup Analysis Excel Report opens

Reports available:


• Entire Servers

• Click “Browse” folder to specify a location to save the file.


• Name the file and click “Save”

File path populated

• After file path is specified click “OK” to export or “Close” to cancel.


• Click “OK” to successful prompt and browse to file saved location to access report.

Select file location prompt appears if no file path was selected on save.

If filename exists, overwrite prompt appears.

o Click “Yes” to overwrite

o Click “No” to specify another filename.


14.1.6 Print Current Report Print Current Report to installed printers.

• Click “Print Current Report” button. This prints the current onscreen report

Print dialog screen appears

o Click “Print” to print current page.

If no printer is installed the below prompt appears, install a printer to continue.


14.1.7 Report Help View backup analysis report help. Each section has a description of each report and the report options.

• Click “Help” button to view report help file.

Report Help Contains the following sections:

o Backup Status o Device Information o Backup Image Analysis o Backup Image Details

Backup Analysis Help

14.1.8 Exit Backup Analysis Exit Backup Analysis

Click “Exit” button

• Click “Yes” to confirm and close Backup Analysis


14.2 Backup History

View historical backup report by date range.


• Click “Reporting Dashboard”.

• Click the “Backup History” icon.

ARCA – “Backup History” launches


Buttons (left to right – buttons activated after a report is generated)

• Email – email report in PDF or Excel format

• Print to PDF – print PDF report

• Export to Excel – exports report to Excel format

• Print Current Report – prints report

• Help – report help

• Close – closes backup analysis

14.2.1 Navigating Backup History Run “Backup Analysis” report options above by server and date range:

• Server – select drop-down arrow to filter by server

• From Date – select drop-down arrow to specify from date

• To Date – select drop-down arrow to specify to date


After all options are specified click “Generate Report” to display report results and run report options to email/export.

Example Backup History Report

If no backups are configured the below prompt is displayed.


14.2.1.1 Backup History Export Options

14.2.1.1.1 Email – email report in PDF or Excel (if installed) format

Click “Email” button

Email Report option window launches.

Select report format, PDF or Excel (if installed) and click “Proceed”.


Fill in required email fields per “Backup Analysis” section.

• Click “Send” to email report to defined recipients.

Mail sent successfully

14.2.1.1.2 Additional Options

• Print to PDF – print PDF report (opens “Save As” dialog)

• Export to Excel – exports report to Excel format (opens “Save As” dialog)

• Print Current Report – prints report (opens printer dialog)

14.2.1.2 Backup History Help File • Click “Help” button to view report help file.


Backup History Help

Backup History Help Detail

14.2.1.3 Exit Backup History Click “Exit” button

• Click “Yes” to confirm and close Backup Analysis


15 Server Failover Processes

15.1 Onsite Server Failure

Example: Onsite Server Failure

Follow the “Live Mode” virtualization steps as defined in section 9.2.2 Create a Virtual Machine. Ensure that “Standby Server

Helper” is run in “Live Mode” to migrate your server network settings. No additional configuration is required. The virtual

server retains all network and system settings. Your IP and MAC address remain the same.

Online Video Demonstration: Live Rapid Failover

15.2 Site Level Failure

Example: 2 Sites, 1 ARCA at each site backing up local servers, onsite ARCA down or inaccessible

Failover Process

1. Site 2: Replicated ARCA: virtualize “site 1” servers in Live Mode.

2. Add the Virtual Servers to the Backup Management Console and change the backup path (destination) to "D:\Replica\servername" (changed Backup).

Restore Back to Site 1

Once the replacement ARCA and Servers are received:

1. Replicate the backup data from Site 2 to Site 1

o Execute incremental backup manually from the Backup Management Console (right click the job and click execute incremental) to ensure last minute changes are recorded.

2. Shut down the virtual machines on Site 2 to verify you have the latest replica.


3. Perform a Bare Metal Restore (BMR) on the replacement servers from the latest backup.

4. Restore the backup configuration to Site 1 ARCA from backup.

Warning: Restoring a configuration file from another ARCA with different settings will overwrite your original configuration.

5. Disable the Backup Job for Site 1's servers on Site 2 ARCA.

6. Add the Servers to the Backup Management Console and change the backup path (destination) to "D:\Backup\servername"

7. Execute new full base image

Warning: Once the servers have been virtualized from replicated data and a BMR is performed on new servers, the existing backup chain cannot continue. A new full backup should be executed manually (old backup images from D:\backup should be copied to external/network drive for future use if required).

15.2.1 BDR Site Failover – Additional Steps

If you are replicating BDR images to Vault additional steps are required. You cannot bring up a virtual server in “Live” mode from

the “Replica” directory on a Vault. You must failover to another BDR, the Vault cannot be used. If you attempt to copy the images

to the “Backup” directory all portal reporting and NOC management will be invalidated. The VM will already have a backup agent

installed.

This limitation exists due to the way BDR agents are configured to communicate with our collocation. If you are replicating BDR to

BDR no additional steps are required.


16 Bare Metal Restore

16.1 Bare Metal Restore Explained

Bare Metal Restore (BMR) allows you to restore a backup image to identical or dissiliar hardware or virtual machine. You cannot

access BMR through the ARCA interface. However an .iso version of the disk is mounted for virtual servers.

You will need the BMR DVD/CD that shipped with the ARCA to run BMR, along with access to the backup files via the network or

external media.

The BMR disk has a “best match” for most drivers. We recommend having the latest drivers on hand to update. To complete the

BMR the following drivers are required and we recommend having the latest version for your hardware:

• NIC Drivers

• RAID Controller Drivers

16.1.1 Precautions For additional options and troubleshooting see the ARCA Administrator’s Guide.

• Even after the restore completes you will need to update all of the drivers on the server. The software does a best driver match available, but the server could have performance issues or limited features until the most up-to-date vendor specific drivers and utilities and downloaded and installed.

• Cannot restore to a partition smaller than the original volume. You must restore to either the same size partition or a larger partition.

• For multi-partition restorations you should complete all of the partition restorations before exiting the Recovery Console. Additional partition restorations can be performed from the Windows OS but this IS NOT recom-mended as there can be severe performance related delays during additional partition restoration.

• If you are restoring a Domain Controller in a multi-Domain Controller Active Directory Environment after complet-ing the BMR process you will need to boot the server in Active Directory Recovery Mode. This ensures that the recently recovered server synchronizes properly with the existing Active Directory systems.

• For Bare Metal Recoveries to dissimilar hardware you should remove your old management software (Dell, IBM, HP, etc) and install the new management software for the new hardware. Management software will not work and will not be supported on hardware it was not intended for.


• Bare Metal Recoveries are not guaranteed to work across all configurations and setups. If you are keeping a cold-state server on-hand for Bare Metal Recoveries it is recommended that you perform tests for the servers that could be recovered noting any issues or problems that occur during the restoration.

16.1.2 BMR From Recovery CD

• Boot the target server for Bare Metal Restore with the ARCA CD or DVD. • On the StorageCraft Recovery Environment (Zenith Edition) select:

1. Start Vista-based Recommended Recovery Environment Contains commonly distributed drivers and provides a quicker boot. Boots into Vista PE allowing for dynamic drivers

and hot plug disk drivers.

Other Recovery Environment Options:

2. Start 2003-based Legacy Recovery Environment– Contains all of the drivers from Recommended and less

commonly distributed drivers.

3. Boot from Hard Disk – boots into bootable system partition

4. Reboot Computer – reboot


Windows Boot Manager appears after boot environment is selected

• Select “Windows Setup [EMS Enabled]” option.

Windows is loading files

Recovery Environment initializes and prompts for network support.


• Click “OK” for network support to map a drive to ARCA when recovery console loads.

Recovery Environment installs network adapters if a driver can be found.

Note: If Recovery Environment cannot find a NIC driver you will be prompted to install one at this time.

Recovery Environment loads (similar to Backup Management Console)


1. Click the Disk Map tab to verify the RAID Drivers loaded properly.

a. If the RAID Drivers loaded correctly, skip to Step 8. b. Only if the RAID Drivers did not load under the Tools group or go to “Tools > Load Drivers”. c. Click on the Load Drivers link.

i. Create a mapping to a network resource that hosts the RAID Drivers (recommended).

ShadowProtect – Load Drivers


Note: The RAID Drivers can also be copied to a Floppy (if present), CD / DVD, or USB drive.

ii. Click on the Add Path button and browse to the location of the RAID Drivers. iii. Click on the Load button.

Note: Other drivers besides RAID can be added in this fashion if you need additional hardware loaded into the Recovery Environment. These are not permanent loads as the environment is from a Boot CD / DVD. You will need to reload drivers each time you enter the Recovery Environment.

2. Click “Network Configuration” under “Tools” or go to “Tools > Network Configuration”

StorageCraft Recovery Environment – Network Configuration Utility


Note: If you did not receive a DHCP address, specify IP Address information.


3. Click “Network Drives”. 4. On the Network Drives window you will need to create a mapping to the ARCA device:

a. Drive – Select a free drive letter from the drop-down menu. b. Network Path – Enter in \\ARCANAME\D$ c. Username – administrative ARCA user (administrator - default) d. Password – administrative ARCA password (arca - default)

Note: You can also use the “Browse Network” option

5. Click “Map Drive” button.


You will receive the following error if the drive mapping fails:

Note: If mapping fails, ensure an IP address was obtained from DHCP or set manually.

Note: For DNS issues attempt to use an IP address instead of a NetBIOS name.

Note: If mapping still fails, check your Network Card driver and network connections.


6. After drive is mapped click “Close” 7. Close the Network Configuration Utility. 8. Under “Tasks” click “Restore Volume”.

9. On the Welcome screen click “Next”.

10. On the “Backup Image to Restore” screen click “Browse”

.


11. From the drop-down menu select the drive mapping you created.

12. Click on the Backup folder. 13. Click on the {Unique ID}-SERVERNAME folder. 14. From the list select the point-in-time incremental (or base) file for restoration.

15. Enter in the Backup Image Password and click “OK”.


16. Click “Next”. 17. On the Backup Image Dependencies window click “Next”. 18. On the Restoration Destination window:

a. If you already have partitions in place on the server select the checkbox next to the partition you want to re-store data to. Then click the Next button.

b. If you have Unallocated space you can right click and either: i. Create exact primary partition at the beginning

1. Select this option if you want the software to create the partition for you based on the restora-tion file you selected.

ii. Enter a size of a new primary partition and create 1. Select this option if you want to manually enter in a size for the partition. 2. YOU CANNOT RESTORE TO A PARTITION SMALLER THAN THE RESTORATION

VOLUME. 3. Enter in the size in Megabytes. 4. Click the OK button. 5. Right click and select Refresh Volume Info. 6. Click the checkbox next to your new volume. 7. Click on the Next button.


16.1.2.1.1 SYSTEM PARTITION OPTIONS

19. On the Specify the restoration options ensure: a. Set Partition Active is checked. b. Restore MBR is checked.

i. Restore original Windows XP MBR is checked ii. Restore disk signature is not checked.

c. Restore Disk Hidden Track is checked.

d. If the local RAID Drivers load correctly, please skip to Step 27. e. Only if the local RAID Drivers load incorrectly will you will need to perform the following:

i. Use Hardware Independent Restore is checked. ii. Click “Advanced”. iii. Click “New”. Browse to the location of you SYS and INF files. You can create multiple search directo-

ries and move the directories up and down the search list. iv. From the drop-down menu you should select: LOW matches will be installed if no better matches are

found. v. The final two options are only used if the Bare Metal Restore failed the first time or if the target server

is a domain controller. vi. Click on the OK button.

20. Click “Next”. 21. Click “Finish”. 22. The Bare Metal Restoration will begin. This is a variable restoration based on the amount of data being restored, the

server resources, ARCA resources, and the network.


23. Once the Bare Metal Restoration completes click on the HIR Configuration. The HIR Configuration will verify the hardware drivers. If a driver is missing you will be prompted for the location of the driver files (SYS, INF) or asked to ignore.

a. Select the Drive the Bare Metal Restoration destination and click “Start”. b. You may be prompted to install drivers. If you do not have the drivers you can select the Ignore option.

24. Once the HIR completes a summary report will show. You can save the report.


25. Click “Close”.

16.1.2.1.2 Configuring Additional Partition Options

o If you are doing a multi-partition restoration it is highly recommended that you complete the other partition restora-tions before exiting the Recovery Console and booting up the restored server.

1. Go back to step 14 and follow until step 25. 2. Next, on the Specify the restoration options window make sure that:

a. Set Partition Active is not checked. b. Restore MBR is not checked.

i. Restore original Windows XP MBR is not checked ii. Restore disk signature is not checked.

c. Restore Disk Hidden Track is checked. 3. Skip to step 27 and continue.

26. Finally, click on “File > Exit”. This will exit the Recovery Console. 27. It is recommended to boot into Safe Mode first to verify your IP settings. In some cases the IP information will port

over without a problem. Other times the IP information does not correctly port over and needs updated manually. 28. On server restart in the StorageCraft Recovery Environment make sure to select the Boot from Hard Disk option.

16.1.3 Bare Metal Restore Clean-up

• Windows will attempt to load with the configuration you selected. If the boot process blue screens you will have to reboot into the Recovery Console. Most often this error is caused by not going through the HIR Configuration link.


• After Windows boots successfully you will need to update all of the Windows drivers to ensure functionality and performance.

Warning: IF YOU DO NOT INSTALL VENDOR SPECIFIC DRIVERS YOU WILL HAVE PERFORMANCE ISSUES.

• Client networks can affect restoration speeds. Sometimes after a Bare Metal Restore you will need to adjust the NIC settings for performance.

• If you have performed a Bare Metal Restore from a Virtual Server you will need to: o Restart any hardware services that were stopped when the Virtual Server was created.


17 Troubleshooting

This section goes over various troubleshooting methods for the ARCA. These are not all inclusive. Please reference the

Frequently Asked Questions and our support team for items not referenced here.

17.1.1 Troubleshooting Backups

This section reviews the various errors that can happen during backup and how to resolve and troubleshoot those errors.

Backup Failures: Errors: Common backup failure errors

1. Cannot get access to destination path 2. Decompression failed. 3. There is not enough space on the disk 4. Full backup must be created before incremental backups 5. Network Errors 6. Server network connections lost after install 7. Error connecting to server. Class not registered.

Error 1:

1. ShadowProtect Error 509 - Cannot get access to destination path – This issue commonly happens if a backup job was re-created or the same destination server was removed and re-added to the same ARCA. This issue can also occurs when access to the destination folder on the ARCA fails due to network or permission error or the destination folder does not exist or an invalid file path is specified.

Resolution:

• Ping the ARCA from destination server configured for backup • Verify the admin share (d$) is accessible from the destination server. Attempt to connect to the share via the “Run”

menu in windows by going to Start Run. Type To verify connectivity type: \\arcacomputername\d$


• Check the backup job destination for the server through the Backup Management Console. Go to the "Desti-nation" tab and click "Edit". Under the "Connect using specific user credentials” re-authenticate to the NAS and verify the destination. Then retry the backup job. If the issue still recurs, contact support (see the be-low screenshot).

o Refresh if the destination is not shown - Destination path should be: \\<ARCAname>\D$\Backup\<Pairname>

Where <ARCAname> is the machine name of ARCA device and <Pairname> is the pairname configured on

server added for backup and will be the name of the server backup folder.

If the Destination path is incorrect, update to the above UNC path.

Error 2:

2. Decompression Failed: Deep verification process fails

Resolution:

1. If the "Decompression Failed" error is reported for the base image (.spf) delete all the previous images and execute a new full backup.

2. If the failure is not for the base image, mark the backup image which is reported in the “Decompression Failed” error. a. Error occurred “ Decompression Failed” for filename: C_Vol-b001-i006.spi b. Reported “C_Vol-b001-i006.spi” file as failed. c. Follow the diffgen process below.


DIFFGEN PROCESS

Diffgen is the process by which a differential backup of the specified volume is created. A differential backup is a point-in-

time backup of only the system and data changes made since the last full backup. Differential files are smaller however they can only be used in conjunction with full backup files.

Diffgen Generation process:

Generate Diffgen:

1. Disable the Backup job in the Backup Management Console: a. Authenticate and connect to the server in network view. b. Right click the job and select “Disable” (refer to above screenshots).

2. Stop “ShadowProtectsvc.exe” service on the server in question. 3. Rename the extension of the backup image file (.spi) with the "Decompression Failed" error, including all of the

backup images created after the reported image to .spo.

Example: Corrupted file is “C_Vol-b001-i006.spi”

Procedure:

1. Rename files: C_Vol-b001-i006.spo/C_Vol-b001-i007.spo/C_Vol-b001-i008.spo 2. Login to the server and open a command prompt 3. Change the path to: C:\Program Files (x86)\ZenithARCA 4. Execute the command: C:\Program Files <x86>\ZenithARCA\>vdiff -0 C


5. Repeat the command for additional volumes: C:\Program Files\ZenithARCA\>vdiff -0 D 6. After all volumes are complete, start the “ShadowProtectsvc.exe” service. 7. Enable the Backup job and run an incremental backup. 8. Perform another Image QP Verification for the latest incremental created. 9. If this fails contact Technical Support.

Error 3:

3. There is not enough space on the disk: This error occurs if the D:\ drive on ARCA doesn't have enough space to continue backups or runs out of space.

Resolution:

1. Run the “Emergency Cleanup” utility from the ARCA Dashboard.

Go to: Start All Programs ARCA ARCA Dashboard.

This launches the ARCA Dashboard.

Then go to: ARCA Administration Emergency Cleanup


Select the server(s) and click “Clear Incremental”. This runs a backup chain continuity check for the selected servers and

removes any extra incremental images which are not a part of the current backup chain. This will free up any disk space that

the extra images were taking up.

2. Check if the collapsed daily files are of larger than anticipated or if the intra-daily files created are exceptionally large.

If so, check the following: a. Are any existing backup files being backed up by the ARCA? For example, NTFS Backup files or database

backup files. i. After the issue is resolved, disable the backup job, archive and then remove backup files of the target

server(s), and start a fresh backup chain.

3. Check if there are older backup files and/or there are maintenance or defragmentation tasks scheduled on the server.

b. Backup Files - Either archive the old backup files to a volume not being backed up by the ARCA or remove the current volume where the backups are stored.

c. Maintenance Tasks – Edit or stop the maintenance schedule, then execute an incremental backup and check the status and size of the completed backup.

i. Archive the existing images and then start a fresh backup chain.

Error 4:

4. Full backup must be created before incremental backups: As long as the full image remains in the destination directory, this error will not occur.

Resolution: Verify that the base backup file for the server is in the backup destination folder.

1. If the base file is there verify that the server is able to access the backup directory via UNC Path.

2. If the base file is not there execute a new full backup. The existing incremental backup files are invalid and data cannot be restored from those files.

3. If you still receive an error contact technical support.

Error 5:

5. Network Errors: These errors are reported on the destination server operating system, not the ARCA itself.

Typical error messages include:

Error 55: "The specified network resource is no longer available" (ERROR_DEV_NOT_EXIST).

Error 64: "The specified network name is no longer available" (ERROR_NETNAME_DELETED).


Error 121: "The semaphore timeout period has expired" (ERROR_SEM_TIMEOUT).

Error 1231: "The remote network is not reachable by the transport" (ERROR_NETWORK_UNREACHABLE).

Resolution:

For resolutions please refer to the following article: http://support.microsoft.com/kb/325487

Error 6:

6. ShadowProtect Error: “Server network connections lost after install" - Users cannot access files on a server after ShadowProtect has been installed.

Event ID 2011 shows in the System Event log with the following message: "The server's configuration parameter "irpstack-

size" is too small for the server to use as a local device. Please increase the value of the parameter."

Users attempting to connect to network shares on the server receive the message "Not enough server storage is avail-

able to process this command."

Resolution: This is a common problem on Servers with lots of storage. Windows does not dynamically adjust the irpstack-

size beyond 15 in most cases. For servers with a large number of file system drivers, you will need to increase this value

manually.

If you are running other applications such as a virus scanner there is probably limited irp stack space left. Each application

that uses a driver (including the OS) will use up the irp stack. The more storage on the system, the more irp stack space

these applications will use. Since the server is close to the limit, ShadowProtect pushed the server over the limit and other

services started to fail, in this case, “Lanman Server”. This is the service which handles user shares. If the registry key for

IRPStackSize mentioned in the Microsoft KB articles below does not exist, then Windows is using the default setting of 15,

and you should create the registry DWORD value as instructed and try increasing its value to 20 (decimal) to start, and then

higher if problems still occur. After changing the setting, a reboot may be required before the changes will take effect.

Please read the following Microsoft KB Articles before adjusting these values:

http://support.microsoft.com/kb/106167

http://support.microsoft.com/kb/329717/en-us




Error 7:

7. ShadowProtect Error: Error connecting to server. Class not registered.

Resolution: When using the console to connect remotely to another machine, this error usually means that ShadowProtect

is not installed on the remote machine. Install the backup agent on the server to resolve.

17.1.1.1 ARCA Alerts

17.1.1.2 Backup Failure If you receive Backup not occurring alert, backups are not occurring for severs/volumes per the defined schedule.

Examples of email alert scenarios:

a. Schedule for scheduled synchronization of backup is disabled. Hence backups will not synchro-

nize.

========================================

Server Name: pmg-win2k3

Pair Name: 97F1DE95C8D2422D-pmg-win2k3

========================================

b. -------------------------------------------------------------------

Backups are failing for - pmg-win2k3

-------------------------------------------------------------------

ARCA: ZNAS-PMGTRAININ

Server: pmg-win2k3

Backup Folder Name: 97F1DE95C8D2422D-pmg-win2k3

Volume: F

Time: 3/24/2009 9:45:12 AM

Error: Cannot get access to destination object

-------------------------------------------------------------------

Backup Prerequisites:


1. Network Connectivity - ARCA and servers should be able to communicate with each other via LAN/WAN.

a. Ping the server from ARCA and vice versa

b. Use the “Agent Connectivity Check” utility on servers.

2. ARCA and servers system time should be the same.

a. If the system time is not the same it needs to be synchronized. If the time is different, there will be issues with the backup schedule. This is because schedule backup jobs are created on the ARCA but executed on the server.

3. Sufficient disk space needs to be available on destination backup partition.

a. To execute the backup chain you need sufficient free space. The backup destination on the ARCA is D:\Backup. The Emergency Cleanup utility can be used as a temporary message to free up space.

4. Server must be restarted after backup agent installation.

a. After the backup agent is installed, the server needs to be restarted to propagate the backup job settings. This is part of the installation, and you will be prompted to reboot after the install. If the server is not restated, backups will fail.

5. Backup job destination should be: //<ArcaComputername>/D$/Backup/<Pairname>.

a. <Pairname> is the GUID value which is allocated to the server when the backup agent is created.

b. Backups are created on this network path during the backup agent setup. If the destination path is incorrect backups may fail.

c. If the destination path does not exist or the path is incorrect then a false alarm Backup Not Occurring alert will occur, and this may suppress other alerts. For example: Backup chain continuity check failure, Deep verification failure, etc.

d. The Backup Job destination can be verified and updated via the ARCA Backup Management Console,

“Destinations” tab. Click “Edit” to modify.


6. Backup Job should not be disabled, unless you want/need to pause backups. Right click the backup job and select “Enable” to re-enable backups.


If the backup prerequisites are met, check other possible backup failure reasons.

1. Check alert for server/ volume. 2. Launch ARCA Backup Management Console 3. Connect to server via network view. 4. Go to the “Backup History” tab and check the latest job execution status for alerted volume.

5. If last execution status is successful and the and last run time of job is correct, issue is resolved. 6. If last execution status is failed, view job details for failure message. See the below errors and resolutions for

troubleshooting steps.

Common errors for backup failure are:


a. Cannot get access to destination path b. Decompression failed. c. There is not enough space on the disk d. Full backup must be created before incremental backups e. Network Errors f. Server network connections lost after install g. Error connecting to server. Class not registered.

Error:

1. ShadowProtect Error 509 - Cannot get access to destination path – This issue commonly happens if a backup job was re-created or the same destination server was removed and re-added to the same ARCA. This issue can also occurs when access to the destination folder on the ARCA fails due to network or permission error or the destination folder does not exist or an invalid file path is specified.

Resolution:

1. Ping the ARCA from destination server configured for backup 2. Verify the admin share (d$) is accessible from the destination server. Attempt to connect to the share via the “Run”

menu in windows by going to Start Run. To verify connectivity type: \\arcacomputername\d$ 3. Check the backup job destination for the server through the Backup Management Console. Go to the "Destination" tab and click "Edit”. Under the "Connect using specific user credentials" re-authenticate to the ARCA and verify the desti-nation. Then retry the backup job. If the issue still recurs, contact support.

1. Refresh if the destination is not shown - Destination path should be: \\<ARCAname>\D$\Backup\<Pairname>

Where <ARCAname> is the machine name of ARCA device and <Pairname> is the pairname configured on

server added for backup and will be the name of the server backup folder.

1. If the Destination path is incorrect, update to the above UNC path.

17.1.1.3 Communication Failure

If you receive an email alert with subject: Server unable to communicate with ARCA.

The server in question has lost connection with the ARCA and will be named in the alert. This could occur in the following

scenarios:

Loss of network connectivity – switch/router down or bad port ARCA not accessible Server not accessible Server backup agent uninstalled Server IP information changed and has not been updated on ARCA


Example: Server unable to communicate with ARCA. Please check the connectivity with ARCA.

=================================================

Server: pmg-win2k3

=================================================

With regards,

[email protected]

Solutions: 1. Ping the server. If you do not receive a reply, check that the server is powered on and booted to Windows. Also

verify the network cable is connected and that you have a link light on the server and whatever port the other end is cabled into.

a. If the ping is successful, attempt to connect to the server locally or remotely. If you cannot RDP, attempt to remotely manage it and check that the “Terminal Services” service is started.

b. After connecting to the server, verify the following applications are installed by going through Add or Remove Programs:

i. ARCA Backup Agent ii. Zenith Business Continuity System

iii. If they are not installed, go to Start Run and connect to the ARCA Tools Share by typing: \\arcaname\Tools. The Tools share window opens.


iv. Verify an agent install folder exists for you server. If it does, open the folder and run the server setup exe and reboot. If it does not, connect to the ARCA and run the “Add Server” wizard.

c. If they are installed, verify the following services are started, if they are not started, start the services and retry the job:

i. ARCAScheduler ii. ShadowProtect Service iii. Storagecraft Shadow Copy Provider

2. If it still fails, login to the server and run the Agent Connectivity Check. a. Go to: Start Programs Accessories System tools ARCA Backup Agent Agent Connectivity

Check


b. The “Connectivity Check” window will open. Verify the ARCA Name”. If the name is incorrect, type the correct name and click “Test Connection”. You can also check by IP address.

c. If you receive a “Connected successfully” prompt, retry your backup job. You may have an authentication failure from the ARCA. Login to the ARCA and verify connectivity through the Backup Management Console and re-authenticate to the server.


d. If it fails with “ERROR in connection”, retry the steps above. If you still cannot connect, archive your current backups, reinstall the backup agent and retry the backup job.

e. If the issue is not resolved after retrying these steps contact Technical Support.

17.1.2 Verification Troubleshooting

This section reviews the various chain and file verification tasks and how to troubleshoot the various issues and error

encountered.

Terms to know:

Queue Pair (QP): This is a "query path" or a "query of the pair" chosen to ensure the chain is valid. Types of Verifications:

File Verification: Utility that enables you to verify the consistency of a selected backup file.

QP Verification: Utility that matches all the GUID entries of a selected backup file up to the base to ensure the chain is valid.

Chain Verification: Utility that enables you to verify the backup chain of a selected file. This runs a chain dependency verification of all files in the backup chain up to the selected file for consistency.

Deep Verification Failure: Deep verification is the process of verifying complete backup chain. It first checks chain continuity of backups. If the chain

verification check is successful, then individual image verification is executed for all images listed in the backup chain.

If the process fails at any intermediate step, deep verification process is counted as failed. The process may fail during the

chain verification check or during verification of backup images.


1. Backup chain continuity check failed One or more backup image files are corrupted, possible causes are

a. Issue: Multiple backup jobs are configured for a server. Solution: If multiple backup jobs are configured for the server, delete all jobs but one.

b. Issues: Unexpected reboot of ARCA Hardware problem on ARCA, network switch, switch port or cables

Disk/NTFS errors on ARCA hard drive

Solution: On ARCA, execute chkdsk on D: drive

• If errors are found then execute chkdsk /f to fix file system errors. • Manually execute Image QP Verification check provided on ARCA Dashboard • Start from the latest backup image to identify which image has broken the backup chain

Example: The following files are backup images for a server. o C_Vol-b001.spf o C_Vol-b001-i001.spi o C_Vol-b001-i002.spi o C_Vol-b001-i003.spi o C_Vol-b001-i004.spi o C_Vol-b001-i005.spi o C_Vol-b001-i006.spi o C_Vol-b001-i007.spi o C_Vol-b001-i008.spi

Go to: Start--->All Programs-->ARCA-->ARCA Dashboard. This launches the ARCA Dashboard.

Then go to: ARCA Administration-->Image QP Verification, The below window will open.

Note: This tool will enable you to verify the backup chain continuity for the selected image.


Select C_Vol-b001-i008.spi and perform Image QP Verification by clicking the “Verify” button. If the output is blank, select

C_Vol-b001-i007.spi and perform the verification again.

Repeat until the output has output text similar to:

D:\Backup\B4D8C36BD7494B96-EXCHANGE>PROGRA~2\Zenith\ZENITH~1\image.exe qp D:\Backup\B4D8C3~1\C_B760~1.SPI "\\?\D:\BACKUP\B4D8C36BD7494B96-EXCHANGE\C_VOL-B001.SPF" "C_VOL-B001-i001.spi" "C_VOL-B001-i002.spi" "C_VOL-B001-i003.spi" "C_VOL-B004-i004.SPI" D:\Backup\B4D8C36BD7494B96-EXCHANGE>Pause Press any key to continue . . .

From the above text we can assume that Image QP Verification is successful from before C_Vol-b001-i003.spi. Mark this

image as failed.

Repeat the check for all the volumes that have reported Backup chain continuity check failure.

After marking the failed images for all volumes that reported failures, perform a “Diffgen Process” for all reported volumes.

2. Decompression Failed: Issue: If the Deep verification process fails with error "Decompression Failed": Solution:

a. If a "Decompression Failed" error is reported for base image (.spf) delete of all the previous images and

execute a new full backup.


b. If a “Decompression Failed” error is reported for images other than the base (incremental files .spi), note the

file.

c. Check the file for errors via Diffgen.

Example: “Decompression Failed” for filename: C_Vol-b001-i006.spi. Report the “C_Vol-b001-i006.spi” file.

Follow the Diffgen Generation process given below.

DIFFGEN PROCESS Diffgen is the process by which a differential backup of the specified volume is created. A differential backup is a point-in-

time backup of only the system and data changes made since the last full backup. Differential files are smaller; however they can only be used in conjunction with full backup files.

Follow the Diffgen Generation process below:

Generate Diffgen:

1. Disable the Backup job in ARCA box via the backup management console by: a. Authenticate and connect to the server in network view. b. Right click the job and select “Disable”.

2. Stop “ShadowProtectsvc.exe” service on the server in question. 3. Rename the extension of the backup image file (.spi) that has reported "Decompression Failed" including all of the

backup images created after the reported image to .spo.


Example: Corrupted file is “C_Vol-b001-i006.spi”

Solution:

1. Rename files: C_Vol-b001-i006.spo/C_Vol-b001-i007.spo/C_Vol-b001-i008.spo 2. Login to the server and open a command prompt 3. Change the path to: C:\Program Files (x86)\ZenithARCA 4. Execute the command: C:\Program Files <x86>\ZenithARCA\>vdiff -0 C 5. Repeat the command for additional volumes: C:\Program Files\ZenithARCA\>vdiff -0 D 6. After all volumes are complete, start the “ShadowProtectsvc.exe” service. 7. Enable the Backup job and run an incremental backup. 8. Perform another Image QP Verification for the latest incremental created. 9. If it fails contact Technical Support.

3. Deep verification fails with error:

1. Sbcrypt 504 Key file error (-87 the parameter is incorrect).

Issue: The password does not match or .spk file is missing.

Solution: Copy the SPK file to the D:\Backup\<Pairname> folder.

Rename the Spk file.(e.g. - C_vol-b001.spk) or any volume in given server C”D”E” etc.

The SPK file can be copied from:

• C:\BDRTemplte\pass.spk • D:\Backup\<Pairname> where <pairname> is the folder on another server If more than one server is configured

on the ARCA device • C:\Program files(x86)\ZenithArca

2. -1450 Insufficient system resources exist to complete the requested service.

Issue: ARCA is running low on kernel memory resource.

Solutions:

• If a VM is not running reboot the ARCA. • If a VM is running, save the state and reboot. Move the VM to a physical machine and purge the VM if

possible.

3. -2 The system cannot find the file specified.


Issue: An intermediate backup image in the chain is corrupted or missing.

Solution:

1. Mark the corrupted or missing backup image. i. Erorr occurred “(-2 The system cannot find the file specified.)” for filename :C_Vol-b001-i006.spi ii. Mark file: “C_Vol-b001-i006.spi”

b. Follow the Diffgen process defined above in the “Decompression failed” section. c. If the "(-2 The system cannot find the file specified.)" error is reported for the base image (.spf) execute a new

full backup and archive or delete the previous backup chain.

Chain Verification: A: (-109 The pipe has been ended.)

Issue: You receive the above error.

1. Reboot the ARCA and perform the chain verification process on the latest incremental file.

Go to: Start--->All Programs-->ARCA-->ARCA Dashboard. This launches the ARCA Dashboard.

Then go to: ARCA Administration-->Chain Verification.

a. Select the latest incremental image and .spk file if a password has been specified. b. Click “Verify” button to execute chain verification,

a. This will open a command prompt which shows the chain verification process. Wait for completion and check the output.

c. If the output window displays same error (-109 the pipe has been ended) then contact technical support.


e. If the output window displays success then the issue is resolved

f. If the output window contains some other error then follow below steps:

B: (-13 the data is invalid)

• Mark backup image which is reported in “(-13 the data is invalid)”

Example: Error occurred “(-13 the data is invalid)” for filename: C_Vol-b001-i006.spi. Mark “C_Vol-b001-i006.spi” as an

invalid file

• Follow the Diffgen process defined above in “Decompression failed” section. a. If the "-13 the data is invalid" error is reported for base image (.spf). delete all the previous backup

images and execute a new full backup. • For additional errors contact Technical Support.


17.1.3 Virtualization Troubleshooting

17.1.3.1 Windows Server 2008

Windows Vista and Server 2008 use a new boot mechanism called “Windows Boot Manager” to load the Operating System stack. The BCD store is created when you install the OS.

If the operating system will not boot after virtualization of Windows 2008 Server, you will need to apply the “BCD Patch” if the

boot and system volume are different.

Example:

C: - Windows Installation drive D: - BCD Store (Boot) volume & it's an active partition

“BCD Patch” stands for Boot Configuration Database Patch. If patching does not resolve the issue perform the following

steps:

1. Boot the Virtual Machine with the Windows 2008 DVD or ISO.

2. Click “Next” at the first prompt:


3. You will see a link in the lower left-hand side for “Repair your computer”. Select this option.

4. The installation process will attempt to find your win2k8 installation directory. If more than one is found,

select the correct listing and click “Next”.

Note: If you do not see any operating systems in the list, click “Next” to continue.


5. The next step is “Choose a recovery tool”. Select “Command Prompt”.

6. Execute the following commands:

cd X:

BootRec.exe /RebuildBcd

D:

attrib -r -h -s bootmgr

copy bootmgr C:\ /v

attrib +r +h +s bootmgr

C:

attrib +r +h +s bootmgr

exit

7. Restart the virtual machine. Windows will now boot normally.


18 Tables

Chart 13.1 Backup File Types

File Type Extension Description

.spf Full image files. These are the files associated with full images.

.spi Incremental image files. These files are generated when you create an incremental backup image. These files are dependent upon the full image and any prior incremental image files. These image files represent only the changed sectors relative to the image file they are generated against.

-cd.spi

-cw.spi

-cm.spi

Image files that have been automatically collapsed by the CollapseManager will have this type of extension. The files will be either daily, weekly, or monthly collapsed backup files.

.spk This file is created when you use password key files to encrypt data.

Chart 13.2 ARCA Common Events

EventID Event Type Event Description Reason / Solution

9 Information No servers added to ARCA for backup No servers added to ARCA for backup

10 Error Invalid system license. Contact technical support. Run ARCA Health Check to resolve this issue. If it still persists then contact technical support.

11 Error ZenithARCA registry value not found or is invalid.

ZenithARCA registry missing, any value is blank in registry

12 Error %Program Files% directory path not found.

Program Files directory path not found in regis‐try

13 Error ARCA data file is invalid. Nasdata.ini is missing or blank values in ini

14 Error ARCA mobile file is invalid. ARCAMobile.ini is missing or blank values in ini

15 Error ARCA license file is invalid. ARCA license file is missing or has been modified

16 Error ARCA configuration panel setting is invalid.

ARCA configuration file is missing or has been modified


17 Error ARCA email configuration is invalid.

ARCA email configuration file is missing or has been modified

18 Error Server alert configuration is invalid.

Server configuration file is missing or has been modified

19 Error Failed to register logparser.dll or the file is missing from the ZenithARCA installation directory.

Run ARCA Health Check to resolve this issue. If it still persists then contact technical support.

20 Error

Failed to register email components ( ZMailer.dll, dartmail.dll, dartutil.dll, dartsock.dll ) or the file(s) are missing from the ZenithARCA installation direc‐tory.


21 Error Failed to register ARCAWbPost.dll. This dll is essen‐tial for server to ARCA communication.


22 Error

Image.exe or its dependency dll is missing. This com‐ponent is essential for backup chain continuity check.


23 Error sbhard.exe or its dependency dll is missing. This component is essential for backup image verification.


24 Error Failed to send email alert. Reason ‐ ( error desc re‐turned from dll ) Mail to be sent ‐ (mail body)

Check the reason for the mail failure.

25 Error

Failed to communicate with Zenith licensing server.

Failed to send license status while add‐ing/removing a server from ARCA, and during Replication activation. Possible reasons: Internet connection failure.

Chart 13.2 ARCA Module Events

Process Event

ID Event

Category Event Type

Event Description Solution

Backup job details 100 JBDETL Warning

Multiple backup jobs are configured for server - ServerName.

Remove the manual backup job cre-ated for the server from the Backup Management Console.

Backup fail-ure 125 FLRBUP Error

Backup failed for server - [Servername] - [Error Description]

Need to login to server and trouble-shoot.

VSS & CSBA check

150 BKPVSC Error

One of the following services are dis-abled for server - [ServerName] : MS Software Shadow Copy Provider, Vol-ume Shadow Copy.

These are essential services required for taking a vss-integrated snapshot for vss backups. Need to enable these services for vss backups to occur.


151 BKPVSC Error

Failed to create vss-integrated snapshot for vss backup scheduled at [time] or vss backup schedule did not trigger for server - [ServerName]

Need to check the status of [MS Soft-ware Shadow Copy Provider] and [Volume Shadow Copy] services.

152 BKPVSC Information

MSExchangeIS Service is disabled for server - [ServerName]

If MSExchange is configured, then this service should not be disabled, else MSExchange will not function properly.

153 BKPVSC Error

Failed to retrieve MS Exchange Storage Group details for server [ServerName] : Storage Group = [StorageGroupName]

Failure to read eventlog entry for Event IDs 224 & 225. Check if event log is corrupt.

154 BKPVSC Warning

MSExchange EventID 224/225 not generated for server [ServerName] : Storage group = [StorageGroupName] - Volume = [VolumeName].

??????????????????????????


SQLServer Service is disabled for server - [ServerName]

If SQLServer is configured, then this service should not be disabled, else SQLServer will not function properly.

156 BKPVSC Warning

SQLServer EventID 18264 not gener-ated for server - [ServerName]

Generation of this event indicates that a full database backup has com-pleted successfully. If this event is not generated, it means the backup was not successful. ??????????????????????????


No services configured for Clean State Backup Assistance for server - [Server-Name]

Need to configure essential services for Clean State Backup using the Clean State Backup configuration.


Some services not configured for Clean State Backup Assistance for server - [ServerName]

Need to configure essential services for Clean State Backup using the Clean State Backup configuration.


159 BKPVSC Warning

Clean State Backup Assistance status not available for server - [Servername]

Need to check the status of [ClState-BackAsst] service. Also check the LastRunTime value in Ze-nithARCA\Configuration\JobStat.ini. This value gives the date & time for the last backup of the day. If this value is incorrect, this event will be generated

160 BKPVSC Error

Error while taking a clean state backup for server - [ServerName]. Reason : [Reason]

Check the reason mentioned. It is possible that some particular service could not be auto stopped / started through the Clean State Backup con-figuration, while taking a clean state backup.

175 HISBKP Warning

Job details file not found for server - [Servername]

Check if showjobs.exe exists in Ze-nithARCA and is in good health

200 BKPSTA Error

Free disk space on drive C = 400MB. Minimumm free disk space required = 500MB.

Need to free up disk space so that the agent can send backup image status to the ARCA.

300 FLINCK Information Invalid folder [folder name]

301 FLINCK error

Backup chain continuity failed Server Name : win2003 Display Name : Win-2003 Folder Name : 803NJFW3HJ6A67C-win2003 Volume Name : C File Name : C_VOL-b001-i183.spi Error Reason : 18 (There are no more files.)

Schedule QP Check

302 FLINCK Information

Backup chain continuity successful Server Name : win2003 Display Name : Win-2003 Folder Name : 803NJFW3HJ6A67C-win2003 Volume Name : C File Name : C_VOL-b001-i183.spi

Backup Not Occurring 305 NOBAKC error

Failed to retrieve backup job configura-tion for server [server name]


306 NOBAKC error Multiple backup jobs are configured for server - Win2003-64.

307 NOBAKC error Backup job not found for server []

309 NOBAKC error

New incremental backup image is not created for last 300 minutes for server Win-2003 Server Name : Win-2003 Backup Folder : 803NJFW3HJ6A67C-win2003

Synchronize ARCA 315 SNRCBX Information

Application log reached 10MB limit logs purged.

320 SCSNBK error

External drive or Network destination synchronization schedule is disabled for server Win-2003

321 SCSNBK error

error connecting to network destination for backup image synchronization[error reason]

322 SCSNBK error No external drive connected through USB port

323 SCSNBK error External drive connected is not format-ted in NTFS

324 SCSNBK error

Not enough free disk space to synchro-nize backup images on external drive or network destination

325 SCSNBK Information

Backup image synchronization to exter-nal drive or network destination com-pleted successfully for Server Win-2003

Schedule USB Syn-chronize

326 SCSNBK error

Backup image synchronization to exter-nal drive or network destination failed for Server Win-2003

330 VRFBFL error Application error : failed to retrieve new backup image file list for server []

File Verifica-tion

331 VRFBFL error

verification of backup image failed Folder name : 803NJFW3HJ6A67C-win2003 File Name : C_VOL-b002-i007.spi Failure code : [Failure reason]

Collapse Check EXE 500 NOCLBK Information

Email alert suppressed as per alert noti-fication interval period configured by user

Deep Verifi-cation EXE 504 DPVRCH Information

Virtual machine configuration exist backup chain deep verification cannot continue.

Export Set-tings 510 SRIPSN ERROR

Failed to register ChilkatZip2.dll or the file is missing from the ZenithARCA in-stallation directory.

Request Configuration 600 GTSCFG Information

Email alert suppressed as per alert noti-fication interval period configured by user


601 GTSCFG Error Error in communicating with ARCA gateway service from server [server]

ARCA Web-post 602 SNDTAS Error

Error in communicating with ARCA gateway service from server [server]

610 GTSINF ERROR Unable to download settings from ARCA. ARCA

Download exe

611 GTSINF ERROR

Failed to register ARCADwnJob.dll or the file is missing from the ZenithARCA installation directory.

ARCA Event Check 700 AEVTCK Error

ARCAEvt.xml file is invalid. This file is essential for reporting ARCA health.

Generate MD5 File 705 ABMDGN Error

Failed to generate MD5 hash backup image [backup image name]

786 BKMNCK Error

Virtual machine configuration exist, mounting backup cannot continue for server [server]

781 BKMNCK Error Err in Verifying MountDir....For pairname = [server]

785 BKMNCK Error Backup Image Mounting failed due to [Reason]

783 BKMNCK Error Encryption File does not exist..

ARCA MountDir

784 BKMNCK Error Backup password file is missing

710 ARMDCK Error MD5 checksum failed for filename : [] on vault : [] Compare

MD5 Check Sum 773 ARMDCK Error Failed to get MD5 destination

715 CHDARC Error failed to perform check disk for ARCA drive [c] ARCA Check

Disk 716 CHDARC Error Drive [] dose not exists on ARCA

Schedule Reporting

901 SENREP Error

Failed to generate scheduled EXCEL/PDF report [Mail body] [Description]

ARCA Health Check 761 SNRCBX Information Testing ARCA Health Check.

Server HealthCheck 761 TESTIN Information Testing Agent Health Check.


19 Appendix A – Reference Documents

Identify any documents references in this guide. List the document number and the title separated by a comma.

1, ARCA Getting Started Guide

2, ARCA Implementation Guide

3, ARCA Replication Guide


20 Appendix B – Glossary of Terms

Term Meaning

ARCA Advanced Recovery and Continuity Appliance

BCD Boot Configuration Data – used in Windows Vista/Server 2008 in place of the boot.ini file found in earlier version of the Windows operating system.

BMR

Bare Metal Restore - Bare Metal Restore - A restore of your entire system to new or existing hardware. To restore a system volume, you will need to do

so from the Recovery Environment

(Boot to the recovery CD shipped with the ARCA).

CSBA Clean State Backup Assistant - Our version of VSS. If your application is not VSS-aware, run CSBA to force applications to flush in-memory transactions

to disk.

Diffgen Diffgen Incremental – Crash proof (DIFF/DIFFGEN) - ensure that the backup job will generate another incremental when it does a backup after a system

crash or hard power-off.

HIR Hardware Independent Restore - restore to identical or dissimilar hardware

Hypervisor Also known as a virtual machine monitor (VMM), a computer

software/hardware platform virtualization software that allows multiple operating systems that run on a host computer concurrently.

QP Verification Query Pair or "queue of the pair" To determine the chain of dependent files use the chain verification utility.

Sandbox Virtualization Test Mode – can be used in Private Network

SPI ShadowProtect Incremental Backup File

CD.SPI ShadowProtect Compressed Daily Backup File

CW.SPI ShadowProtect Compressed Weekly Backup File


CM.SPI ShadowProtect Compressed Monthly Backup File

VM Virtual Machine - a software implementation of a machine (computer) that executes programs like a real machine using a hypervisor.

VSS Volume Shadow Copy Service (Shadow Copy) - A feature introduced with Windows Server 2003 and all subsequent releases that allows manual or

automatic snapshots of a volume at a specific point in time.

ARCA Administration Guide

Documents

program filesexchsrvrmdbdata

program files

program fileszenitharcagt

bare metal

arca administration

bare metal

content analysis

reregister