administration guide windows file system...

Administration GUIDE

Windows File System iDataAgent

Published On: 11/19/2013 V10 Service Pack 4A of 311

User Guide - Windows File System iDataAgent

System Requirements

Getting Started

Overview

Deployment

Configuration

Backup

Restore

Advanced Options

Configuration

Backup

Restore

Data Aging

Additional Operations

Command Line

Configuration

Backup

Restore

Add-On Components

1 - Touch for Windows

OnePass Agent for Windows File System

Advanced Reporting

Primary Storage Reports - Windows File System iDataAgent

Best Practices

FAQ

Troubleshooting

Table of Contents


System Requirements - Microsoft Windows File System iDataAgent

The following requirements are for the Microsoft Windows File System iDataAgent:

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

1 GB minimum of hard disk space for installing the software.

500 MB of free disk space is required for job result directory.

500 MB of free disk space is required for log directory.

All Windows-compatible processors supported

Live Communications Server 2005

Office Communication Server 2007

Office Communication Server 2007 R2

Lync Server 2010

.NET Framework

.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.

System Requirements Supported Features License Requirements

Operating System

Windows 8 Microsoft Windows Client 8Microsoft Windows Client 8.1

See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information.

Windows Server 2012Microsoft Windows Server 2012 EditionsMicrosoft Windows Server 2012 R2 Editions

See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information.

Windows 7Microsoft Windows 7 32-bit and x64 Editions

Windows Server 2008Microsoft Windows Server 2008 EditionsMicrosoft Windows Server 2008 R2 Editions

Windows VistaMicrosoft Windows Vista 32-bit and x64 Editions

Windows XPMicrosoft Windows XP Home Editions with a minimum of Service Pack 3Microsoft Windows XP Professional 32-bit and x64 Editions with a minimum of Service Pack 3

WindowsMicrosoft Windows Server 2003 32-bit and x64 Editions* with a minimum of Service Pack 2

* Special configuration considerations apply. See Installing 32-bit Components on a Microsoft Windows x64 Platform for more information.

Cluster - Support

Hard Drive

Processor

Communication Server

Miscellaneous


Microsoft Visual C++

Microsoft Visual C++ 2010, 2008 and 2005 Redistributable Packages are automatically installed. Note that these Visual C++ Redistributable Packages can co-exist with other versions of this software.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable


Getting Started - Windows File System

Introduction

Key FeaturesSimplified Data ManagementPoint-In-Time RecoverySystem StateOffice Communications ServerBackup and Recovery FailoversEfficient Job Management and ReportingBlock Level Deduplication

Add-On Components1-TouchOnePass Agent

Terminology

The Windows File System iDataAgent provides unified protection and recovery for file system data residing on Windows clients. In addition to complete protection of file system data for disaster recovery, the Windows File System iDataAgent also provides more granular backup and recovery options that operate seamlessly with your data protection. Further options for deduplication, job-management and reporting help to make sure that all of your file system data are easily traceable and retrievable whenever the need arises.

The Windows File System iDataAgent offers the following key features:

Simplified Data Management

The Windows File System iDataAgent enables easy management of all the Windows systems in your environment, by providing a singular approach to manage the data using the same unified console and infrastructure.

Point-In-Time Recovery

In the event of a serious system failure, such as the breakdown of hardware, software, or operating systems, the Windows File System iDataAgent provides point-in-time recovery of files at any given time.

System State

The Windows File System system state contains many components and services that are critical to recovery of the Windows operating system. The system state is backed up and restored as part of Windows File System iDataAgent backup and restore.

Office Communications Server

The Office Communications Server contains data, settings, and metadata that are critical to data protection operations residing in both the File System and SQL databases. In order to fully protect the Office Communications Server, the OCS data settings and the OCS metadata must be backed up.

Backup and Recovery Failovers

In the event that a MediaAgent used during a backup or recovery operation fails, the operation will automatically resume on an alternate MediaAgent from the point of failure. This is especially useful for backups and restores of large amounts of file system data.

In the event, that a network goes down, the backup and recovery jobs are resumed on alternate data paths. Similarly, in the event of a device failure, the jobs are automatically switched to alternate disk and tape drives.

Efficient Job Management and Reporting

You can view and verify the status of the backup and recovery operations from the Job Controller and Event Viewer windows within the CommCell Console. You can also track the status of jobs using reports, which can be saved and easily distributed. Reports can be generated for different aspects of data management. You also

Overview Deployment Deployment - Microsoft Cluster Deployment - Non-Microsoft Cluster Configuration Backup Restore

Table of Contents

Introduction

Key Features


have the flexibility to customize the reports to display only the required data and save them to any specified location in different formats. For example, you can create a backup job summary report to view completed backup jobs at-a-glance . In addition, you can schedule these reports to be generated and sent by email without user intervention.

Block Level Deduplication

Deduplication provides a smarter way of storing data by identifying and eliminating the duplicate items in a data protection operation.

Deduplication at the data block level compares blocks of data from multiple files against each other. For example, if two or more files contain blocks of data that are identical to each other, then block level deduplication eliminates storing the redundant data thereby reducing the size needed for storage. This way also dramatically reduces the number of backup data copies on both disk and tapes.

1-Touch

1-Touch recovery helps to recover a crashed system in the least amount of time. By automatically rebuilding the operating system, you can recover systems with defective components such as inaccessible volumes or crashed disks. You don't need to reinstall the individual software packages or operating systems manually.

Simpana OnePass

The Simpana OnePass is an integrated File System agent that backs up and archives the qualified data. Simpana OnePass also reclaims backup storage space when files and stubs are deleted on the primary storage.

The Windows File System documentation uses the following terminology:

Add-On Components

Terminology

ClientThe computer in which the iDataAgent is installed and contains the data to be secured.

BackupsetA group of subclients which includes all of the data backed up by the iDataAgent.

SubclientThe Windows file system data to be backed up.



Install the software on a Windows computer that you want to backup.

The computer will be added as a client in the CommCell as soon as the installation completes successfully.

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Download Software Packages

Download the latest software package to perform the install.

1. Open CommCell Console:

Click Start and point to All Programs.

Click HDPS .

Click Backup and Recovery Administrative Console.

2. From the CommCell Browser, click Tools | Add/Remove Software | Install Software.

3. Click Next.


Where to Install

Before you Begin

Installation

The software can be installed using one of the following methods:

Method 1: Remote Install Using CommCell Console

Use this procedure to install remotely on a client computer.

Method 2: Interactive Install - Standard

Use this procedure to install the software using the standard installation options.

Method 3: Interactive Install - Custom

Use this procedure to install the software by specifying installation settings and options.

Method 1: Remote Install Using CommCell Console


4. Click Next.

5. Click Manually Select Computers.

Click Next.

6. Enter the fully qualified domain name of the client computer.

For example: mycomputer.mydomain.mycompany.comClick Next.


Do not use space and the following characters when specifying the Host Name:

\|`~!_@#$%^&*()+=<>/?,[]{}:;'"

7. Choose one of the following:

Click Next if you want to use the default cache location

Click Override Software Cache and specify a new location in the Software Cache box and then click Next

8. Specify the User Name and Password that must be used to access the client computer, and then click Next.

The software cache is the location from where the remote install program installs the software. This screen will not appear if the remote cache is not configured. For more information, see Managing Cache -Remote Cache.

The user must be an Administrator or a member of the Administrator group on that computer. Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on that client, click Next without specifying the account information.


9. Click File System, and then click Next.

10. Select one of the following:

From the Storage Policy to use list, select a storage policy, and then click Next.

From the Subclient Policy to use list, select a subclient policy, and then click Next.

If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later in step 17.

If you want to add this computer to a client group, select a client group from the Available list and click Add >.This option will be displayed only if client groups are configured in the CommCell Console. For more information, see Client Computer Groups. Select the Configure For Laptop Backups option to install Backup Monitor utility. This utility allows you to view the backup job summary from the client computer without opening the CommCell Console. See Monitor - LaptopUser for more information.


11. Click Next.

If necessary you can select optional settings. Click the Help button to get more information on the available options.

12. Click Next.

If necessary you can select optional settings. Click the Help button to get more information on the available options.


If firewall configuration is not required, click Next.


If this computer and the CommServe is separated by a firewall, click Configure firewall services.

For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

14. Select Immediate.

Click Next.

15. Click Finish.

This screen will reflect the components you selected for install, and may look different from the example shown.


16. You can track the progress of the job from the Job Controller window of the CommCell console.

From the Home menu, click Job Controller.

Once the job is complete, view the job details from the Admin Job History.

Right-click the <CommServe>, point to View and then click Admin Job History.

Click Select Install/Upgrade/Remove/Repair Software.

Click OK.

You can view the following by right-clicking the job:

Details of the job

Option to Resubmit the job

Events associated with the job

Logs associated with the job

Option to send the Logs associated with the job


17. To create a storage policy, you must have configured a library in the CommCell.

If you do not already have a library configured, go to Disk Library Creation.

If you have a library configured, go to Storage Policy Creation.

DISK LIBRARY CREATION:

1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Add and then click Disk Library...

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library...

2. From the Add Disk Library dialog box, specify the following:

In the Name box, specify name of the disk library.

From the MediaAgent list, select the MediaAgent.

Perform one of the following:

Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder.

Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Password and Verify Password box, type the password to access the network share.

In the Folder box, type the mount path or click button to select a mount path.

Click OK.

3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Click to proceed to the Configuration section.

Storage Policy Creation

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:

Select the Storage Policy type as Data Protection and Archiving and click Next.

Enter the name in the Storage Policy Name box and click Next.

From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

Ensure that you select a library attached to a MediaAgent operating in the current release.

From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.

For the device streams and the retention criteria information, click Next to accept default values.

Select Yes to enable deduplication for the primary copy.

From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next.

Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Click to proceed to the Configuration section.


Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.

1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer.

2. Run SetupAll.exe from the Software Installation Discs.

3. Click I accept the terms in the license agreement.

Click Next.

4. Click Standard.

Click Next.

Method 2: Interactive Install - Standard


5. Click Join an Existing CommCell.

Click Next.

6. Click File System.

Click Next.

7. Verify the default location for software installation.

Click Next.

If necessary, click Browse... to change the default location.


Do not install the software to a mapped network drive

Do not use the following characters when specifying the destination path: / : * ? " < > | #

It is recommended that you use alphanumeric characters only

8. Click Install.

9. Click Yes.

10. Click Next.

The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.






12. Enter the fully qualified domain name of the CommServe in the CommServe Host Name box.

Do not use space and the following characters when specifying the CommServe Host Name:

\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.


13. Enter the following:

The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

If necessary you can also type a new (friendly) name for the client in this box. This name will be used in the CommCell and will also be displayed in the CommCell Console.

Do not use spaces when specifying a new name for the client.

The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card).

If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe.

Click Next.

14. Select one of the following options:

If you do not want to disable Windows Firewall, click Next.

If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

15. Select a Client Group.Click Next.

If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the same name as previously specified.

This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.


16. Select a storage policy from the Storage Policy list.

Click Next.

17. Click Finish.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 18. Select the Configure for Laptop or Desktop Backup option to install Backup Monitor utility. This utility allows you to view the backup job summary from the client computer without opening the CommCell Console. See Monitor - Laptop User for more information.



















Click OK.












If you already have a storage policy selected in step 16, click to proceed to the Configuration section.

If you do not have Storage Policy created, continue with the following step.








Default options selected during Standard Install

Listed below are the default options that are automatically selected while performing the Standard Install.

Components installed by default during Standard Install

Listed below are the components that are installed by default while performing the Standard Install of File System.




Click Next.

OPTION ENABLED / DISABLED DESCRIPTION

Add programs to the Windows Firewall Exclusion List Disabled This option allows you to add Data Protection Suite programs to the Windows Firewall exclusion list.

This option is not selected.Global Filter Options Enabled This option is used to filter out specific directories or files from the

backups within the CommCell. The filters are set using the Control Panel in the CommCell Console and, if enabled, they will be effective for the default subclient.

Cell level policy is automatically selected.

SELECTED PACKAGE COMPONENTS INSTALLED

File System Windows File System

File System Core

Method 3: Interactive install - Custom


4. Click Custom.

Click Next.

5. Click Select components to install on this computer and click Next.

6. Expand File System, and then click File System.

Click Next.



Click Next.





8. Click Install.



9. Click Yes.

10. Click Next.








\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.







Click Next.



14. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers.

Click Next.




16. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List.

This screen will not appear if the default port numbers are not used for CommCell communication.


Click Next.

17. Select a Client Group.Click Next.


Click Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.

Click Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

Select Do not use Global Filters if you plan to define specific filters for the Agent.

Click Next.

This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list.

It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time.

This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.



Click Next.

20. Click Finish.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 21. Select the Configure for Laptop or Desktop Backup option to install Backup Monitor utility. This utility allows you to view the backup job summary from the client computer without opening the CommCell Console. See Monitor - Laptop User for more information.



















Click OK.





















Custom Package

Create a compact software package for quick deployment to multiple clients.

Decoupled Install

Install the software first and later register the client in the CommCell.

Remote Install

Deploy the software from CommCell Console on multiple clients.

Installing Restore only Agents

Setup a client in the CommCell for restore purposes.

Silent Install

Deploy the software silently on multiple clients.

Additional Installation Methods



You must create a Subclient to define the data that you want to backup.

Use the following steps to create a new Subclient.

1. From the CommCell Console, navigate to Client Computers | <Client> | File System | defaultBackupSet.

Right-click the defaultBackupSet, point to All Tasks and click New Subclient.

2. Enter the name of the Subclient in the Subclient Name box.

3. Click the Content tab.

Click the Browse button.


Creating a Subclient


4. Navigate through the list of folders and select the files and folders you want to backup.

Click Add.

Click Close.

5. Click the Storage Device tab.

In the Storage Policy box, select a Storage Policy name.

Click OK.

The subclient content must contain data that resides on the storage device volume. Do not include local drives or UNC paths as subclient content.


6. Click Do Not Schedule and then click OK.

7. If you do not have Storage Policy created, follow the step given below to create a storage policy.

a. Click Create Storage Policy.

b. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:

i. Select the Storage Policy type as Data Protection and Archiving and click Next.

ii. Enter the name in the Storage Policy Name box and click Next.

iii. From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.


iv. From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.

v. For the device streams and the retention criteria information, click Next to accept default values.

vi. Select Yes to enable deduplication for the primary copy.

vii. From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse to select the folder, and then click Next.

viii. Review the details and click Finish to create the Storage Policy.



Once a subclient is created and a storage policy is configured, you are ready to perform your first backup.

The following section provides step-by-step instructions for performing your first backup:

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | defaultBackupSet.

Right-click the subclient and click Backup.

2. Click Full as backup type and then click Immediate.

Click OK.

3. You can track the progress of the job from the Job Controller window of the CommCell console.

4. If you are unable to view the job controller window, click Job Controller from the toolbar.

5. Once the job is complete, view the job details from the Backup History. Right-click the Subclient and select Backup History.


Perform a Backup


6. Click OK.

7. You can right-click the job and view the following details:

Items that failed during the job

Details of the job

Events of the job

Log files of the job

Media associated with the job


What Gets Backed Up

What Does Not Get Backed Up

Component What Gets Backed UpFile System File Allocation Table (FAT) file systems

New Technology File Systems (NTFS)

Transactional File Systems

Distributed File System (DFS) data

Oracle ASM Cluster File System (Oracle ACFS)

Resilient File System (ReFS) on Windows Server 2012File System Elements Universal Naming Convention (UNC) Paths

Mount Points

Encrypted files

Compressed Data

Shared Volumes

Share with Macintosh data

Single Instance Storage

Remote Storage ServiceSystem State

System State is backed up automatically for the defaultsubclient. For more information on how to enable System State on user-defined subclients, see Configuring System State Backups.

System File Protection catalog and files

Performance monitor configuration files

Active Directory

Registry

Quotas

SYSVOL (if this is a domain controller)

Certificate Services database (if this is a certificate server)

Cluster database (if this server is part of a cluster)

COM+ database

Terminal Server Licensing database

RSM database

WMI database

DHCP

WINS

IIS

UDDI (only with Windows Server 2003 using VSS)

Disk quota information

Event logs

Content Indexing catalogs

Network Policy Server (NPS)

1-Touch Component Office Communication Server (OCS) OCS Data

OCS Settings

Component What Does Not Get Backed UpFile System Locked Files - Files that are locked by applications or system programs while they are in use.Office Communication Server (OCS) OCS data and settings - You must enable the OCS backup and configure a subclient for OCS.

For more information, refer to Configuring Backup of Communication Server. OCS Metadata - Use SQL Server iDataAgent to backup the OCS Metadata.

Lync Server Lync data and settings - You must enable the OCS backup and configure a subclient for Lync Server. For more information, refer to Configuring Backup of Communication Server. Lync Metadata - Use SQL Server iDataAgent to backup the OCS Metadata.

System State Offline files will not get backed up if the client computer has UEFI.Web Server on Windows Server 2012 Data from the Web Server will not get backed up.



It is recommended that you perform a restore operation immediately after your first full backup to understand the process. The following section explains how restore the Temp folder to a new location.

1. From the CommCell Browser, navigate to Client Computers| <Client> | File System | defaultBackupSet

Right-click the subclient and then click Browse and Restore.

2. Click View Content.

3. Expand the defaultBackupSet and navigate to the Windows folder.

For the first restore job, select any folder with a small data size.

Click Recover All Selected.

4. Clear the Overwrite Files and Restore to same folder options.

Specify the destination path by clicking the Browse button.

This will ensure that the existing files are not overwritten.

Click OK.


Perform a Restore


5. Click the Job Initiation tab.

Select Immediate to run the job immediately.

Click OK.

6. You can monitor the progress of the restore job in the Job Controller window of the CommCell Console.

7. Once the restore job is complete, right-click the defaultBackupSet , point to View, and then click Restore History.

8. Click OK.


9. You can right-click the job and view the following details:

View Restore Items

You can view them as Successful, Failed, Skipped or All.

View Job Details

View Events of the restore job

View Log files of the restore job

Congratulations - You have successfully completed your first backup and restore.

If you want to further explore this Agent's features read the Advanced sections of this documentation.


Advanced Configuration - Windows File System

Understanding the CommCell Console

Creating an On Demand Backup Set

Creating a Subclient to Backup Specific FilesCreating a Subclient to Backup Predefined ContentCreating a Subclient to Backup UNC Paths

Configuring Backups for Recently Modified or Created Data

Using VSS for BackupsUse VSS to Backup All FilesUse VSS to Backup Locked Files

Using QSnap to Backup Locked Files

Configuring System State Backups

Configuring Backup of Communication ServerEnabling Communication Server BackupConfiguring Subclient for Communication Server

Configuring Filters for BackupsFiltering Files from a BackupFiltering System State Components from a BackupConfiguring Exceptions to FiltersExcluding CommCell Console DirectoriesDeleting a Filter

Enabling ACLs (Access Control Lists) during Backups

Configuring the Scan Method for Detecting Changed FilesConfiguring Change Journal Scan Configuring Recursive ScanConfiguring Optimized Scan

Configuring Multiple Streams for Backups

Configuring Deletion of Backed Up PST Files

Configuring Pre/Post Processing for BackupsSetting up Pre/Post ProcessesSetting up Pre/Post Processes to Run During Failures

Configuring User AccountsConfiguring Windows Users on an Individual ServerConfiguring Windows Users on a Domain ControllerConfiguring Windows Users for Specific FoldersConfiguring Credentials for UNC Path ContentConfiguring Credentials for Restricted Drives or Directories

Configuring Retention for Deleted Items

Retaining Additional Versions of a File During Synthetic Full Jobs

Configuring File Level Information for a Subclient

Managing Encryption Pass-PhraseSetup Encryption Pass-PhraseExport an Encryption Pass-PhraseReset a Pass-PhraseSetup the Pass-Phrase for Synthetic Full Backups

Modifying an Agent, BackupSet or Subclient

Deleting an Agent, BackupSet or Subclient

Windows File System iDataAgent uses the following main components to perform backup and restore operations from the CommCell Console.

Backup Set - collective information about all the data that needs to be backed up for the client.

Subclient - defines the data to be backed up.

Table of Contents

Understanding the CommCell Console


On Demand backups allow content to be specified as an external input when initiating a backup. Whereas traditional backups are performed using subclients, which contain fixed content configured prior to performing the operation, On Demand backups allow you to specify content each time you perform a backup.

Content for On Demand backups is defined through two entities:

a Content File, which is a text file that defines the location of the data that you want to protect. Each Content File contains the fully qualified paths from the root directory to files, links, and devices to be backed up.

a Directive File, which is a text file that defines where each Content File is located. The Directive File contains the fully qualified paths from the root directory to one or more Content Files. Only one Directive File is needed for a single On Demand backup.

Once these entities are defined, an On Demand Backup Set is then created. Backups performed from this Backup Set will allow you to select the Content and Directive Files to be included.

Formatting Content and Directive Files

Content File entries should be in the following format:

\\client1\shares\ondemand_content\test1.txt

c:\data\datafile.txt

Similarly, Directive File entries should be in the following format:

c:\temp\ContentFile1.txt

Filters, wildcards, regular expressions and blank lines should not be included in Content or Directive files.

Configuring On Demand Backups

Create one or more Content Files defining the content to be backed up.

1. From the CommCell Browser, navigate to Client Computers | <Client>.

2. Right-click the File System, point to All Tasks and then click New On Demand Backup Set.

3. In the New Backup Set Name box, type a name (up to 32 characters).

4. Click OK.

Create a Directive File defining the locations of each Content File.

Creating an On Demand Backup Set

Once an On Demand Backup Set has been created, it cannot be changed into a traditional backup set.


Adding Files and Folders with Unicode Characters to Content Files

If the path or the filename contains Unicode characters, the Content File must be converted to a format that can be used by the data protection operation. The Unicode Conversion utility must be used to convert the Content File to a format that can be provided as input.

1. Using a text editor, create a file that contains a list of files/folders with Unicode characters. Make sure to save the file as a Unicode text file.

2. From the Command Line, navigate to the <software install folder>/base folder and type the following:

cvconvertunicode <source file> <destination file>Where:

<source file> is the full path and name of the file created in Step 1.

<destination file> is the full path and name of the destination file. The file will automatically be created by the utility.

3. Use the destination file as the content file to perform an On-Demand backup.

Preventing Duplicate Backups of Files

On-Demand Backups explicitly back up the files listed in the Content File. If the Content file has two entries for the same file, the file will be backed up twice.

For example, consider a Content File that lists the following entries:

/usr/

/usr/textfile

In this scenario, the textfile folder will be backed up twice because the Content File also has an entry for the parent folder usr.

It is recommended that Content Files avoid such duplicate entries. If you are unable to avoid duplicate entries, use the following steps to prevent the duplication of data.

Configuring Content File to Exclude Duplicate Entries

1. From the CommCell Browser, navigate to Client Computers.

2. Right-click the <Client> on which you want to add the additional setting, and then click Properties.

3. Click Advanced.

4. Click the Additional Settings tab.

5. Click Add.

6. In the Name field, type OnDemand_AutoExpandDir.

7. The Category and Type fields are populated automatically.

8. In the Value field, type 0.

9. Click OK.

You can create an user defined subclient to manage and back up specific data files.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | Backup Set.

2. Right-click the Backup Set, point to All Tasks and then click New Subclient.

3. In the Subclient Name box, type a name.


Creating a Subclient to Backup Specific Files


5. In the Storage Policy list, click a storage policy name.


7. Click Browse.

8. Select the directory or file to be backed up and click Add.

Repeat this step to include all the files and directories to be backed up.

You can also select Add Paths to enter the paths of the directories or files to be backed up.

9. Click Close.

10. Click OK.

You can also use wildcards to define content and filters for a subclient. The following table describes how to use wildcards while defining the subclient content/filters:

If the subclient content consists of wildcard characters and no eligible files are found for backup, then the backup operation will complete successfully even though no files were backed up.

Wildcards Description Example* Any number of characters

This wildcard is used in following scenarios:

Back up all files of a specific extension Backup all files under a specific directory Backup all files of a specific extension where the file name starts with a specific pattern.

*.doc will backup all files with the extension .doc (e.g., status.doc, mission.doc) on all drives on the client computer.

C:\Test\*.doc will backup all .doc files only in the C:\Test\directory

a*.dll will backup all files with the extension .dll (e.g., alsvc.dll, advdcc.dll) on the client computer which has the name beginning with the letter "a".

C:\Finance\Test\* will backup only the files in the "Test" folder under the "Finance" folder on the C drive. Any sub-folder under the "Test" folder will not be backed up.

** Any directory level. C:\**\move.cpp - the file named move.cpp located at any directory level under the c: drive. (e.g., c:\info\com\move.cpp) C:\sys*\** - all folders and files under C drive that start with "sys" will be included. All the sub-folders and files under these folders will also be included.

? Any one character

This wildcard can be used to backup following files or folders:

All files (or folders) for which any one character in the file name or the folder name is variable.

access? will backup any folder/file on the C drive for which the name begins with- "access" followed by any one character such as access1 or access5. However, access12 or access15, for example will not backup because the last two characters in the name are variable. To backup access12 or access15, you must specify access?? in the subclient content.

Class?report will backup any folder/file for which the character in the place of ? is variable. For example: Class1report and Class2report will backup. However, Class15report will not get backed up.

[ ] Set or range of characters. C:\[a-m]*.doc will backup any file with .doc extension on the C drive for which the name begins with the letters "a" through "m”.

C:\[AEIOU]*.doc will backup any file name that ends with .doc and begins with the letters A, E, I, O, or U.If you want to treat [] as literal characters and not as wildcards, you must use a special syntax. This will be useful when you want to add a file which has [] in the file name. The special syntax allows you to define an escape character. Each character immediately following the escape character will then be treated literally and not as a wildcard.

For example: You want to backup a file with the name report[finance].doc on the C drive. In order for the square brackets to not be treated as wildcards, you must define an escape character. In the following example, the escape character is defined as the apostrophe (‘). The "e=" syntax is used to define the escape character. Since the square brackets are to be treated as literals, they both must be preceded by apostrophes. The content entry in the subclient


Creating a Subclient to Backup Predefined Content

The Content Library folder on any client will automatically collect frequently accessed data such as images, audio, video etc.You can select the required content category under the Content Library and add to the subclient content. The following predefined content categories are available:

Audio

Executable

Image

Office

System

Video

Use the following steps create a subclient to backup predefined content:







7. Click Browse.

8. Navigate to <Client> | Content Library.

9. Click the desired file type.

For example, click Audio to select all the audio files on a client.

10. Click OK.

should look like this:

<P:e='>C:\report'[finance'].doc

Any character can be used as the escape character, as long as it is defined after the “e=” in the syntax and it precedes any character that is to be treated as a literal.

In addition, the escape character can itself be used as a literal. This can be achieved by prefixing it with another escape character. To backup a file with the name Test[Report]’2011’Financials.doc on the C drive, the following syntax should be used:

<P:e=’>C:\Test’[Report’]’’2011’’Financials.doc[ ! ] The negation of a set or range of

characters. You can use the wildcard in following scenario:

Back up all files in a directory except the files for which the name starts with any character from the specified set or range of characters.

C:\Windows\[!AEIOU]*.doc would backup all .doc files in the C:\Windows directory that start with a letter other than A, E, I, O, or U.


Creating a Subclient to Backup UNC Paths

A UNC path describes the location of a volume, directory, or file. You can add UNC paths as a content in a subclient.

Before adding UNC paths as a content in a subclient, make sure that the UNC path is from the same domain as that of the client's domain.







7. Click Add Paths and enter the UNC path of the files and directories that you want to backup.

You can also use wildcards to define the content from a UNC path. Ensure that the UNC path starts with \\<Computer Name>\<Share>\ .

For example: \\mycomputer.testdomain.com\C\*.doc will backup all the .doc files from the C: drive of mycomputer in the testdomain domain.

8. Click As User to provide user name and password required to access the UNC path.

9. Click Close.

10. Click OK.

You can configure backups only for the data that has been modified or created after a specified date. This option is useful if you need to filter out data that was modified before a certain date.

Note the following before configuring backups for recently modified or created data.

After enabling the date option for an existing subclient if you do not run a full backup, the data filtered out based on date rule will be marked as deleted.

After moving the date forward for a configured subclient if you do not run a full backup, the data backed up by the previous jobs will be marked as deleted.

A full backup is mandatory after disabling the date option or after moving the date backward.

This option is applicable to file system backups and laptop backups only.

1. From the CommCell Browser, navigate to the <CommServe>.

2. Right-click the <CommServe>, and then click Properties.

3. On the CommCell Properties dialog box, click the Additional Settings tab.

4. Click Add.

5. On the Add Additional Settings on Windows Client dialog box, perform the following:

Configuring Backups for Recently Modified or Created Data


a. In the Name box, type bAllowBackupFilesCreatedOrModifiedOnAfter. The Category and Type details will be automatically populated.

Alternatively, you can click Lookup and search for the additional setting using the Find box.

b. In the Value box, select TRUE.

c. Click OK.

6. Click OK to close the CommCell Properties dialog box.

7. Restart the CommCell Console.

8. From the CommCell Browser, navigate to Client Computers | <Client> | File System | <Backup Set>.

9. Right-click the <Subclient>, and then click Properties.

10. On the Subclient Properties of <Subclient> dialog box, click the Content tab.

11. Select the Only Backup files created or modified on and after check box.

12. In the Time Zone box, select the time zone.

13. In the Date box, type or select the date after which the data modified or created has to be backed up.

14. Click OK.

By default, the Windows File System iDataAgent will perform the backup from the live volume and not from the Snapshot of the volume.

Microsoft Volume Shadow Service is the default and only supported VSS software provider. The VSS software provider takes a snapshot of the source volume, database or file, which is then used to create backups.

You can use VSS as follows:

Use VSS to Backup All Files

The action of backing up a file will cause the file access time to change to the time of the backup. This action may have an undesired effect on the application that utilizes file access time. For example: The Simpana OnePass archive files based on access times. In this situation, you can use a software snapshot to perform the backup of all the files.

Follow the steps given below to perform the file system backup using VSS:

Using VSS for Backups


1. From the CommCell Console, navigate to Client Computers | File System | <Backupset>.

2. Right-click the subclient and click Properties.

3. Select the Use VSS for all files option from the Use VSS options.

4. A software snapshot creation may fail if the VSS service is unavailable or it is unable to quiesce a volume. Select one of the following options to control the actions in such scenario:

Fail the job

If you select this option the backup job will fail and not continue in the case where the software is unable to create the snapshot. Use this option, if you want to perform the backup using only the software snapshot.

Continue and reset access time

If you select this option, the File System iDataAgent will perform the backup from the live volume . After backing up the file, the access time will be reset to its original time before the backup occurred. Use this option, if you are archiving files based on access time. Note that resetting the access time may slow down the backup operation.

Continue and do not reset access time

This is the default option. The File System iDataAgent will perform the backup from the live volume. After backing up the file, the access time will NOT be reset to its original time. Use this option, if you are NOT archiving files based on access time.

5. Click OK.

Use VSS to Backup Locked Files

Some applications and system programs lock certain files while in use (open). Files that are locked are skipped during the backup job. The Windows File System iDataAgent automatically attempts to obtain any skipped files in the next backup job.

In some cases, it may be desirable to allow write operations on data being backed up to continue while the backup runs. In such a situation, you can backup using VSS for locked files and live volume for all other files.

Follow these steps given to enable VSS for backup of only the locked files:



3. Select the For locked files only option from the Use VSS options.

4. Click OK.


When enabling VSS for the backup of files, keep in mind:

VSS can be enabled for backups of local volumes in both clustered and non-clustered environments.

VSS can only be enabled on NTFS and ReFS volumes and not on the FAT or FAT32 volumes. If the operating system fails to create a shadow copy of the data a traditional backup of the data will be performed, and a corresponding message will appear in the Event Viewer.

When you are have enabled VSS for a subclient, the locked database files are backed up in an inconsistent state. You can filter the Exchange and SQL database files by creating the FilterSqlExchFiles registry key in the client computer where Windows File System iDataAgent is installed.

VSS is supported on all the Windows operating systems listed in the System Requirements, except Windows 2000.

For Windows XP clients, you can use QSnap to perform the backup of locked files. Before you enable this option, install QSnap on the client. Follow these steps given below to use QSnap as a snap engine and backup locked files:

Using QSnap to Backup Locked Files

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | Backupset.

2. Right-click the <Subclient> in the right pane and then click Properties.

3. Select Use QSnap to handle backup of locked files.

4. Click OK.


You can ignore the file lock detection and backup the files with mandatory locks using these steps:


2. Right-click the <Client>, and then click Properties.

3. Click Advanced and select the Additional Settings tab.

4. Click Add.

5. In the Name field, type nOverrideVSSSnapSelection.

6. The Category and the Type field will be populated automatically.


8. Click OK.

By default, System State data is backed up along with file system data by the default subclient. System State data includes the following:

System File Protection catalog and files


Active Directory

Configuring System State Backups


Quotas


Certificate Services database (if this is a certificate server))


Registry

COM+ database

DHCP

WINS

IIS

UDDI (only with Windows Server 2003 using VSS)


Event logs

RSM database

WMI database



File Server Resource Manager (FSRM)

Network Policy Server (NPS)

Offline Files (only when the client computer does not have UEFI)

You can also create a separate subclient to back up the System State. Within any backup set, however, only one subclient can back up the System State. To back up the System State data, the service user must be either an administrator or a backup operator. Also, System State backups require backup operator group permissions on the HKLM\SYSTEM\SETUP key to enable system-protected file backups.




4. Select the Backup System State check box.

Ensure that the Backup System State check box is not selected on the Content tab of any other subclient in the backupset.

If you do not want to perform backup of the system state during the incremental backup , select the Only with Full backup check box. If you want to restore any system state component, the latest full backup will be used for restore.

If you clear this check box, a full backup of the system state data will be performed with the incremental backup of the file system data.

5. Click OK.

This subclient will be used to backup the system state. Additionally, system state data will be removed from all subsequent backups of the default subclient.

Make a note of the following: VSS services are mandatory to perform system state backups if you are using Windows Vista or later versions of the operating system. System State backups cannot be performed on the virtual nodes of a cluster.


You can use the File System iDataAgent to backup and restore the data on the Communication Servers. If the communication server is setup across multiple computers, you must install Windows File System iDataAgent on all computers.

Enabling Communication Server Backup

Follow the steps given below to enable communication server backup using the Windows File System iDataAgent:

1. From the CommCell Console, navigate to Client Computers.

2. Right-click the File System and select Properties.

3. In the General tab of the File System Properties dialog box, select the Enable Office Communication Server Backup check box.

4. Click OK.

If the communication server is setup across multiple computers, enable communication server backup on all computers.

Configuring Backup of Communication Server

Server What Gets Backed Up

What Does Not Get Backed Up

Live Communications Server

Office Communication Server (OCS)

OCS data and settings

OCS Metadata

Lync Frontend Server

Lync Backend Server

Lync Archiving Server

Lync Monitoring Server

Lync data and settings

Lync Metadata

Response Group Configuration

Lync Metadata

Lync Archiving Database

Lync Monitoring Database

Use SQL Server iDataAgent to backup and restore these databases. For performing backup and restore of these databases refer to:

Creating User-Defined SubclientsRestoring a Database


Configuring a Subclient for Communication Server

You can configure a default or a user defined subclient for OCS and Lync server. Follow the steps given below to configure a subclient for communication server:

1. From the CommCell Console, navigate to Client Computers | File System | <Backup Set>.

2. Right-click the subclient in the right pane and select Properties.

3. In the the Subclient Properties dialog box, click Content.

4. Select the Backup Office Communication Server check box.

The OCS or Lync Server credentials are displayed. If they are incorrect, click Edit to change the credentials.

Enter the User Name and Password for OCS or Lync Server and click OK. The user must have read permissions on the Lync server.

5. Click OK on the Subclient Properties dialog box.

Prior to backups, you can set filters to prevent specific type of files from being backed up. Filters can also be used to exclude certain system-related files and database application files which consistently fail during a backup operation and are not integral to the operation of the system or application.

See Content, Filters, and Regular Expressions for comprehensive information on filtering data from backup.

Filtering Files from a Backup

Subclient-level backup filters are available for the File System iDataAgent to exclude specified directories and files from being backed up. Follow the steps given below to configure filters on a subclient:


2. Right-click the Subclient in the right pane and then click Properties.

3. Click the Filters tab.

Configuring Filters for Backups


4. Under Exclude these files/folders/patterns, click Browse.

5. Click the file, folder, or directory that you want to exclude from backup operations and click Add.

6. Optionally, click Add under Exclude these files/folders/patterns and type the path to files and folders that you want to exclude. You can also enter patterns of files or folders using wild cards.

You can also filter files and folders from a UNC path and use wildcards to define the filters. Ensure that the UNC path starts with \\<Computer Name>\<Share>\ .

For example: \\mycomputer.testlab.com\C\*.doc will exclude all the .doc files from the C drive of mycomputer in the testlab domain.

7. Click Close.

8. Click OK.

Supported Wildcards

You can use the following wildcards to specify the pattern of files as a filter:

wildcard definition example* Any number of characters.


filter all files of a specific extension filter all files when the file name starts with a specific pattern filter all files under a specific directory

C:\*.log will filter all files with the .log extension on root of the C drive. If you want to filter files with the .log extension from a folder on the C drive, you must include the path to the folder in the filter. (e.g. C:\Test\*.log)

ntuser* will filter all files for which the file name starts with the word ntuser.

C:\Finance\Test\* will filter only the files in the "Test" folder under the "Finance" folder on the C drive. Any sub-folders under the "Test" folder will get backed up.

**All files under a specific directory C:\Test\Data\** will filter all files and

subdirectories under and including C:\Test\DataC:\**\Data\** will filter all files and subdirectories below and including any directory called "Data" at any level in the C: volume

G:\Users\**\xpprofile\*.log will filter all files with the .log extension from any xpprofilesubdirectory under Users directory

G:\Users\**\xpprofile\ntuser* will filter all filenames starting with ntuser from any xpprofile subdirectory under Users directory

? Any one character

This wildcard can be used to filter following files or folders:


To filter files:

C:\access?.doc will filter any files with the extension .doc on the C drive for which the name begins with- "access" followed by any one character such as access1.doc or access5.doc. However, access12.doc or access15.doc will not be filtered because the last two characters in the name are variable. To filter access12 or access15, you must specify access?? in the subclient filters.

To filter folders:

Class?report will filter any folder for which the character in the place of ? is variable. For example: Class1report and Class2report will be filtered. However, Class15report will get backed up.


Filtering System State Components from a Backup

By default, the system state is backed up along with file system data by the default subclient of a Backup Set. A system state backup is always a full backup whether you select full, incremental, or differential backup for the subclient that includes the system state. You can, however, filter out some components from system state backup.

1. From the CommCell Console, navigate to Client Computers | File System | Backup set.

2. Right-click the subclient in the right pane and click Properties.


4. Click Add from the Exclude these files/folders/patterns group.

5. Enter the path within curly brackets. Following are the entries that can be made:

{System Protected Files}

{IIS}

{COM+ Database}

{Event Logs}

{One Touch Files}

{RSM}

{Terminal Services Licensing}

{Disk Quotas}

{Content Indexing Catalogs}

{WMI Database}

{DHCP}

{WINS}

{UDDI Database}

[ ]Set or range of characters. C:\[a-m]*.doc will filter any file with .doc

extension on the C drive for which the name begins with the letters "a" through "m”.

C:\[AEIOU]*.doc will filter any file name that ends with .doc and begins with the letters A, E, I, O, or U.If you want to treat [] as literal characters and not as wildcards, you must use a special syntax. This will be useful when you want to filter a file which has [] in the file name. The special syntax allows you to define an escape character. Each character immediately following the escape character will then be treated literally and not as a wildcard.

For example: You want to filter a file with the name report[finance].doc on the C drive. In order for the square brackets to not be treated as wildcards, you must define an escape character. In the following example, the escape character is defined as the apostrophe (‘). The "e=" syntax is used to define the escape character. Since the square brackets are to be treated as literals, they both must be preceded by apostrophes. The filter entry in the subclient should look like this:



In addition, the escape character can itself be used as a literal. This can be achieved by prefixing it with another escape character. To filter a file with the name Test[Report]’2011’Financials.doc on the C drive, the following syntax should be used:

<P:e=’>C:\Test’[Report’]’’2011’’Financials.doc

[!]The negation of a set or range of characters. You can use the wildcard in following scenario:

Filter all files in a directory except the files for which the name starts with any character from the specified set or range of characters.

C:\Windows\[!AEIOU]*.doc will filter all .docfiles in the C:\Windows directory that start with a letter other than A, E, I, O, or U.


{Remote Storage Database}

{Certificate Services}

{Offline Files}

{Active Directory Application Mode}

{Active Directory}

{File Server Resource Manager}

{NPS Database}

6. Click Add.

7. Click OK to save your changes.

Configuring Exceptions to Filters

Once you set the filters, you can also provide exceptions for the filters. The files or folders added to the exception list will be included in the backup operations. For example, if you want to exclude from your back up operation all the files in the /Ops directory except the Maintenance file. You can add a subclient filter to exclude the /Ops directory from being backed up and also provide an exception to allow the Maintenance file to be backed up.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | Backup set.

2. Right-click the <Subclient> in the right pane and click Properties.


4. Under Except for these files/folders/patterns, click Browse.

5. Click the file, folder, or directory that you want to include in the backups and then click Add.

Otherwise, select Add and enter the paths of the directories or files which you want to backup.

You can also use wildcards to define exceptions to filters. For more information on available wildcards, refer to Creating a Subclient to Backup Specific Files. The wildcards available for defining content of a subclient can be used for defining exceptions to filters.

6. Click Close.

7. Click OK.

Excluding CommCell Console Directories

Software Installation, Index Cache, Job Control, and Job Results directories are by default included in the backups performed by the Windows File System iDataAgent. To exclude them from data protection operations follow the steps given below:


2. Right-click the <Client>, and then click Properties.

3. Click Advanced.



5. Click Add.

6. In the Name field, type nFilterGalaxyDirectories.

7. In the Location and Type list will be populated automatically.


9. Click OK.

Deleting a Filter

You can remove a filter by deleting it from the exclusion list.


2. Right-click the <Subclient> in the right pane, and then click Properties.


4. Under Exclude these files/folders/patterns, select the filter that you want to delete.

5. Click Delete.

6. Click OK.

Catalog ACL (end user access control list) option ensures that ACLs are included in the backup, which in turn, allows users to access only those files and folders for which they have permissions. Other files and folders will be filtered and made invisible during Find, Browse, Restore, and Erase Data operations.

Enabling ACLs (Access Control Lists) during Backups

This option is only available for users who log in with their Active Directory credentials.


Also, Find, Browse, Restore, and Erase Data operations are dependent on the user capabilities to display only the content that is accessible to the specific user. Specifically, only the End User Access capability must be assigned to these users.

Assigning the End User Access capability helps to maintain multiple user profiles on the same laptop (or desktop) and ensures that each user has the ability to access only the data to which he or she has access.

The following section describes how to enable this option:

1. Make sure that only End User Access capability is configured on the client computer. For instructions, see Configuring End-User Operations on Client Computers.



4. Click the Advanced Options tab and select Catalog ACL (end user access control list).

5. Click OK.

You can use one of the following scan methods to determine which files in a backup set have changed and/or have been backed up.

Configuring Change Journal Scan

Change Journal is selected as the method for scanning files to determine which files have changed and/or have been backed up. When using this method of scanning the incremental backup will backup all the new or changed data since the last incremental or full backup, ignoring any differential backups performed prior to the current backup.



3. Click Advanced Options tab

If the users have Browse capabilities set up, then they can restore all files even if they do not have the necessary ACL permissions. Hence, make sure to assign only End User Access permissions to limit the ability to allow users to access only those files and folders for which they have permissions.

If you select/clear the Catalog ACL (end user access control list) option between backup jobs, it is recommended to run a full backup for the selected option to take effect.

Configuring the Scan Method for Detecting Changed Files


4. Select Change Journal.

5. Click OK.

Configuring Recursive Scan

There are some instances in which the Recursive Scan is always used, including but not limited to:

When backing up FAT Volumes.

When files or file level wildcards are used to define subclient content.

Follow the steps given below to configure Recursive Scan:



3. Click Advanced Options tab.

4. Select Recursive Scan.

5. Select Preserve File Access Time. Enabling this option maintains the file access time during backups making sure that they are not modified at the time of backup. Selecting this option may however increase the time required to complete a backup.

6. Select Check archive bit during backups. Enabling this option checks whether files are considered modified and therefore backed up based on either the state of the archive bit or the file modification time. In addition, the system resets the archive bit of every file it backs up. This option influences the way incremental backups are conducted for all backups within a subclient.

7. Click OK.

Refs file systems do not support Change Journal scan method. If you specify Change Journal scan, it would automatically convert to Recursive scan and run the backup operation successfully.


Configuring Optimized Scan

By default, Optimized Scan is selected as the default method for scanning files to determine which files have changed and/or have been backed up. However Optimized Scan is the preferred method of scanning the files during a regular and IntelliSnap Backup, as this method is much faster as compared to the Recursive Scan.

Before selecting Optimized Scan as the scan method, consider the following:

Use Optimized Scan method for NTFS volumes but not for the FAT volumes.

Do not use Optimized Scan method if the subclient content has any mount points.

1. From the CommCell Console, navigate to <Client> | <Agent> | defaultBackupSet | Subclient.

2. Right-click the Subclient and select Properties.

3. Click Advanced Options.

4. Click Optimized Scan.


File System Multi-Streaming employs multiple data streams per subclient for data protection operations. This enables the subclient's contents to be distributed to all the streams, transmitting them in parallel to the storage media. Hence a subclient whose data is secured using three data streams, utilizes more of the available network resources, and can complete in as little as one third the time that the same data would require using a single stream.

Note that, you do not have to enable multi-streaming if you have multiple mount points pointing to the same physical drive. Do not use multiple streams if you have added UNC paths to the subclient content.

Before enabling multi streaming, ensure that you can use multi-streaming when you restore the data and create an auxiliary copy.

Follow the steps given below to configure multi-streaming.



3. In the Advanced Options tab, type or select the number of data streams in the Number of Data Readers box.

4. Select the Allow multiple data readers within a drive or mount point checkbox.



7. Click OK.

Configuring Multiple Streams for Backups

The number of streams configured in the Storage Policy should be equal to, or greater than the specified Number of Data Readers .


You can choose to delete backed up PST files from your client computer if these files are not modified since the last backup.

Follow the steps given below to enable deletion of PST files.



3. In the Advanced Options tab, select the Delete protected PSTs check box.

Configuring Deletion of Backed Up PST Files


Setting Up Pre/Post Processes

You can add and modify Pre/Post processes for a subclient. These are batch files or shell scripts that you can run before or after certain job phases. For example, you can use an echo command to check the level of a backup. Similarly, you can include a case statement within a script to run specific operations based on the level of the backup job.

A Save As Script file can also be run as a pre/post process, if you include the absolute path of the associated input file in the script file.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | BackupSet.


3. Click the Pre/Post Process tab.

4. Depending on the process you want to set up, click the corresponding Browse button.

5. Select the process and then click OK.

Setting Up Post Processes to run during Failures

By default, a specified post process command is executed only on successful completion of the scan or backup operation or if the job is killed.

Use the following steps to run a post process even if the scan or backup operation did not complete successfully. For example, this may be useful to bring a database online or release a snapshot.



3. Click the Pre/Post Process tab.

4. Select the Run Post Scan Process for all attempts check box.

5. Select the Run Post Backup Process for all attempts check box.

6. Click OK.

Configuring Pre/Post Processing for Backups


Users performing backups must be either an administrator or a backup operator. Backup operators (or Service Users) are designed to have full control to the registry and the installation folder.

If you are not an administrator or backup operator, you must be the owner of the files and folders you want to back up or have one or more of the following permissions:

Read

Read and execute

Modify

Full Control

The following sections describe the procedures for modifying user permissions and rights.

Users can be configured at the server and domain control levels to perform backups using the following procedures:

Configuring Windows Users on an Individual Server

To add a user to the Backup Operators Group, perform the following steps on an individual server:

1. Navigate to Start | Settings | Control Panel | Administrative Tools.

2. Double-click Computer Management.

3. Navigate to Local User and Groups | Users.

4. Right-click the user who will be performing backups and click Member of.

5. Add the Backup Operators group to the User.

6. Click OK.

7. Log off and log in as the domain controller Administrator for the policies to take effect.

Configuring Windows Users on a Domain Controller

To add a user to the Backup Operators Group, perform the following steps on the domain controller:

Configuring User Accounts

ROLE PRIVILEGESAn administrator or a backup operator in a local group

Able to back up any file and folder on the local computer to which the local group applies.

An administrator or backup operator on a domain controller

Able to back up any file and folder on: a computer in the domain a computer in a domain where a two-way trust relationship exists


1. Create or prepare to manage a Windows user who will run the services.

2. Navigate to Active Directory Users | Computers | Users.

3. Right-click the user who will be performing backups and click Member of.

4. Add the Backup Operators group to the User.

5. Click OK.

6. Log off and log in as the domain controller Administrator for the policies to take effect.

Configuring Windows Users for Specific Folders

1. Right-click the folder to be backed up and select Properties.

2. Select the Security tab

3. Enable Add Backup Operators with full control rights.

4. Click OK.

Configuring Credentials for UNC Path Content

The user must have privileges to:

Access the share to which the UNC Path is pointing.

Log on to the client machine that is running the backup.

The logs on the client machine.

To perform backup or restore operations using a UNC Path as either the content of the subclient or the destination for a restore, the user account should have Administrative privileges.

Use the following steps to change the User Account for the UNC Path content:

1. From the CommCell Browser, navigate to Client Computers | <Client> | Agent.

2. Right-click the <Subclient> and click Properties.

3. Click Content tab.

4. Click Add Paths and type in the UNC path of the share that you want to add.

Repeat this step if you want to add more files and/or folders to the content.

5. Click As User.

6. Type the new user name in the User Name box.

7. Type the new password in the Password box and retype it in the Confirm Password box.

8. Click OK.


Configuring Credentials for Restricted Drives or Directories

You can define a user or an account with permissions to restore data to either mapped/shared network drives or directories to which you have no write privileges.

1. From the CommCell Browser, right-click File System, click All Tasks, and then click Browse and Restore.

2. From the Restore Options dialog box, click Advanced.

3. Select Impersonate Windows User.

4. Enter the appropriate user name and password.

5. Click OK to save the settings.

You can specify the time period for which you want to retain the deleted files in the backup cycle. This enables you to restore the deleted files from the latest backup cycle and avoid point-in-time restores. This is useful to view (and restore) the deleted files from clients (like, laptop clients) that have backup cycles with frequent & numerous incremental backups after a full backup.

By default, when you delete any files from the source, they will be removed from the backup cycle during the next backup. You can specify the retention period for each subclient. When you run the synthetic full backup at the end of specified retention period, the deleted files will be removed from the backup cycle.

However, if a full backup is performed during the retention period, the deleted files may get removed from the backup cycle earlier.

1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent> | <BackupSet>.

2. Right-click the Subclient on the right pane, and then click Properties.

3. Click the Retention tab.

4. Select from one of the following options:

Immediately

Select to delete the deleted items immediately from the backup cycle.

After n days

Select and enter the number of days for which you want to keep the deleted items available in the backup cycle after deletion.

Never

Select to retain deleted items in the backup cycle forever.

5. Click OK.

The retention criteria set at the storage policy level takes a higher precedence over the one set at the subclient level.

By default, synthetic full backups only keep the latest version of files.

Use the following procedure to retain additional versions of a file during a synthetic full backup:

1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent> | <BackupSet>.

2. Right-click the Subclient on the right pane, and then click Properties.


4. Select Keep at least and enter a value for the number of versions you want to maintain.

5. Click OK.

File Level Analytics provides granular file level details of files in the backup. The granular details include information like:

The name and location of each file.

The size of each file.

The time at which it was last modified.

Configuring Retention for Deleted Items

Data moved from one subclient to another is also considered as deleted item and would be included for deleted items backup.

Retaining Additional Versions of a File During Synthetic Full Jobs

Configuring File Level Information for a Subclient


The time at which the file was last accessed.

The time at which the file was created.

The name of the primary user of the file.

The name of the primary user group of the file.

For detailed information on File Level Analytics see, File Level Analytics documentation.

Enable this option at the subclient level before performing a backup to collect information about files, volumes, and directories within the subclient being backed up.

Follow the steps given below to enable this option:

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | <backupset>.


3. Click the Advanced Options tab and select Catalog additional file and system attributes.

4. Click OK.

Data encryption for backups can be enabled with a pass-phrase, which would be required for restoring the data. The following sections describes the various operations related to the pass-phrase.

Setup Encryption Pass-Phrase

Data encryption keys can be protected with a pass-phrase before being stored in the database. The pass-phrase will be required for restoring the data.

If the database is accessed by unauthorized users, and the media is stolen, the data will still not be recoverable without the pass-phrase.

Use the following steps to enable the encryption pass-phrase:

1. From the CommCell Console, right-click the Client and click Properties.

2. From the Client Computer Properties for <client> dialog box, click Advanced button.

3. From the Advanced Client Properties dialog box, select the following:

a. Click the Encryption tab.

b. Click the Encrypt Data check box.

c. In the Cipher box, select the encryption algorithm.

Managing Encryption Pass-Phrase


d. In the Key Length box, select a key length.

e. From the Direct Media Access (External Restore Tools) area, click either the Via Pass-Phrase or the No Access option.

f. From the Restore Access area, click the With a Pass Phrase option.

A Warning message will be displayed. Click OK.

g. In the Enter Pass-Phrase dialog box, specify the Pass-Phrase and click OK.

h. Click OK to close the Advanced Client Properties dialog box.

4. Click OK to close the Client Computer Properties for <client> dialog box.

Export an Encryption Pass-Phrase

You can export the file containing the scrambled pass-phrase. This is useful for restore operations, especially scheduled restores, to complete successfully.

A <hostname>.pf file is copied to the <software installation path>\PF folders and is named for the source client.

Exporting the pass-phrase will also facilitate immediate restores, bypassing the need to enter the pass-phrase for each restore operation.

When using pass-phrase security for:

Migration Archiver Agents - you must export the pass-phrase to the destination client before you can run a Stub data recovery.

Image Level iDataAgents - you must export the pass-phrase to the MediaAgent as well as the destination client, since a portion of the volume information is restored to the MediaAgent Index Cache. When using Alternate Data Paths (GridStor), this would apply to any MediaAgent involved in the restore.





b. Click the Export button.

c. In the Destination Computer, select the name of the destination client.

d. Enter the pass-phrase and click Export.

4. Click OK to close the Advanced Client Properties dialog box.



Reset a Pass-Phrase

Pass phrases can be changed using the reset option.

When a pass-phrase is reset, it can be used to recover data - both from the current and past backups. For example, if you ran a few encrypted backups with the pass-phrase set to “violet”, and then changed the pass-phrase to “purple”, you will need to enter “purple” when recovering that data. It works like this because pass-phrase is used to lock encryption keys rather than encrypt the data itself. When pass-phrase is modified, the keys are re-locked with the new pass-phrase.





b. Click the Reset button.

c. Enter the old and new pass-phrase and then click the Reset button.

4. Click OK to close the Advanced Client Properties dialog box.



Setup the Pass-Phrase for Synthetic Full Backups

Explicitly enabling synthetic full backups in the CommCell Console will create a copy of unlocked encryption keys in the database, which will be accessible only to synthetic full backup operations. In this case the regular restore operations will continue to prompt for a pass-phrase, but synthetic backups will not prompt for the pass-phrase.





b. Click the Encrypt Data check box.

c. In the Cipher box, select the encryption algorithm.

d. In the Key Length box, select a key length.

e. From the Direct Media Access (External Restore Tools) area, click either the Via Pass-Phrase or the No Access option.

f. From the Restore Access area, click the With a Pass Phrase option.

A Warning message will be displayed. Click OK.

g. Click the Enable Synthetic Full check box.

h. In the Enter Pass-Phrase dialog box, specify the Pass-Phrase and click OK.

i. Click OK to close the Advanced Client Properties dialog box.



The following table describes the properties that can configured from the agent, backup set and subclient levels.

Modifying an Agent, Backup Set or Subclient

OPTION DESCRIPTION RELATED TOPICS

Preserving the File Access Time

This option allows you to prevent the file access time from being changed as a result of running data protection operations on the client. When this option is selected, the file access time will be preserved.

1. From the CommCell Browser, right-click the backup set, and then click Properties.

2. Select the Preserve File Access Time check box.

3. Click OK. Change Storage Policies You can modify the storage policies in any of the following situations:

To include a different media for the backup operation. To use a storage policy with a different retention criteria.

You can change the storage policies from the subclient level.

1. From the CommCell Browser, right-click the subclient.

2. Click Properties.

3. Click Storage Device.

4. Select the Storage policy from the drop-down menu.

5. Click OK.

Refer to Storage Policies.

Rename a Backup Set or Subclient

You can rename backup sets and subclients.

Renaming BackupSet:

1. From the CommCell Bowser, navigate to Client Computers | <Client> | File System.

2. Right-click the <Backup Set>, and then click Properties.

3. In the Backup Set box, type a name.

4. Click OK.

Renaming subclient:


2. Right-click the <user-defined Subclient>, and then click Properties.


4. Click OK. Data Transfer Options You can efficiently configure the available resources for transferring data secured by data

protection operations from the subclient level. This includes the following: Enable or disable Data Compression either on the client or the MediaAgent. Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

You can configure the data transfer options.


Refer to Data Compression and Network Bandwidth Throttling.


The following sections describe the steps involved in deleting an agent, archive set or subclient.



4. Click the Data Transfer Option tab.

5. Choose the appropriate software compression option for this subclient.

6. Select the Throttle Network Bandwidth check box, and set the required bandwidth.

7. Click OK.View Data Paths You can view the data paths associated with the primary storage policy copy of the selected

storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.





5. Click Data Paths. Configure Activity Control You can enable backup and restore operations from the agent and subclient level. However, you

can enable restore operations only from the agent level.

1. From the CommCell Browser, navigate to Client Computers | <Client>

2. Right-click the <Client> or <Subclient> in the right pane, and then click Properties.

3. Click the Activity Control tab and select or clear option(s) as desired.

4. Click OK.

Refer to Activity Control.

Configure User Security You can configure user security from the agent or subclient level.

You can perform the following functions:

Identify the user groups to which this CommCell object is associated. Associate this object with a user group. Disassociate this object from a user group.

1. From the CommCell browser, right-click the subclient.


3. Click Security.

4. Select the appropriate user groups to which you want to associate to the CommCell object from the Available Groups pane, and then move the user group to the Associated Groupspane.

5. Click OK.

Refer to User Administration and Security.

Enable/Disable Data Encryption

When you configure encryption at the client level, it is configured automatically for all the subclients associated with all the agents installed on that client. If you want to disable or change the encryption at the subclient level, follow the steps given below:

1. From the CommCell browser, right-click the subclient.


3. Click Encryption.

4. Select the desired encryption.

5. Click OK.

Refer to Data Encryption.

View Software Version and Installed Updates

The Version tab, at the Agent level displays the software version and post-release service packs and updates installed for the component.

1. From the CommCell browser, right-click the agent.


3. Click Version.

4. Click OK.CommCell Configuration Report

The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, subclients, and storage policies within the CommCell based on the selected filter criteria.

1. On the CommCell Console menu bar, select the Reports tab.

2. Click Configuration.

The Report Selection dialog box appears.

3. Click Run.

Refer to CommCell Configuration.

Deleting an Agent,BackupSet or Subclient

When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell


Deleting an Agent

You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

You cannot delete an agent while operations for that agent are running.


2. Right-click the <Agent>, and then click Delete.

3. A confirmation message is displayed with the following message:

This operation will permanently delete the data backed up from this level and it cannot be restored.

4. Click OK to continue with the deletion operation or click No to abort the deletion.

Deleting a BackupSet

Consider the following before deleting a Backup Set:

You cannot delete a default Backup Set.

Schedules associated with the Backup Set are also automatically deleted.

1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>.

2. Right-click the <Backup Set>, and then click Delete.

3. A confirmation message is displayed, asking if you want to delete the Backup Set.

Click No to cancel the deletion and retain the Backupset, or click Yes to continue the deletion.

Deleting a Subclient

Consider the following before deleting a subclient:

You cannot delete a default subclient.

Schedules associated with the subclient are also automatically deleted.

1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent> | <Backup Set>.

2. Right-click the <subclient> that you want to delete, and then click Delete.

3. A confirmation message is displayed, asking if you want to delete the subclient.

Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.

Back to Top

Console for recovery purposes.

Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.


Advanced Backup – Windows File System

Full Backup

Incremental Backups

Differential Backups

Synthetic Full BackupsRunning Synthetic Full BackupsRunning an Incremental Backup Before or After a Synthetic Full BackupIgnoring Errors in Synthetic Full BackupsAccelerated Synthetic Full Backups (DASH Full)

Backing Up Mount Points

Backing up System Protected Files

Backing up HotFix Information

Scheduling A Backup

Performing An On Demand Backup

Additional Backup Options for Windows 2003Backing up Remote Storage DataExcluding WINS and DHCP data from Backups

Managing JobsRestarting JobsControlling JobsViewing List of Backed Up Files in a Job

Additional Options

Full backups provide the most comprehensive protection of data.

1. From the CommCell Browser, navigate to <Client> | File System | defaultBackupSet.

2. Right click the <Subclient> and click Backup.

3. Select Full as backup type and Immediate to run the job immediately.

4. Click OK.

You can track the progress of the job from the Job Controller or Event Viewer window. When the backup has completed, the Job Controller displays Completed.

An incremental backup contains only data that is new or has changed since the last backup, regardless of the type. On average, incremental backups consume less media and use less resources than full backups.

The illustration clarifies the nature of full and incremental backups.

Follow steps given below to perform an incremental backup:

Table of Contents

Full Backup

Incremental Backup




3. Select Incremental as backup type and Immediate to run the job immediately.

4. Click OK.

You can track the progress of the job from the Job Controller. When the backup has completed, the Job Controller displays Completed.

A differential backup contains only the data that is new or has changed since the last full backup. Like incremental backups, differential backups also consume less media and use less resources than full backups. Differential backups are cumulative. This means that each differential backup contains all changes accumulated since the last full backup. Each successive differential backup contains all the changes from the previous differential backup.

The illustration on the right demonstrates the nature of differential backups. For simplicity, assume there is a file system that contains six files as represented in the figure.



3. Select Differential as a backup type and Immediate to run the job immediately.

4. Click OK.

You can track the progress of the backup job from the Job Controller. When the backup has completed, the Job Controller displays Completed.

Differential Backup


A synthetic full backup is a synthesized backup, created from the most recent full backup and subsequent incremental and/or differential backups. The resulting synthetic full backup is identical to a full backup for the subclient.

Unlike full, incremental, and differential backups, a synthetic full backup does not actually transfer data from a client computer to the backup media. Therefore, they do not use any resources on the client computer.

Synthetic full backups are media-based; they read backup data from one media and simultaneously write (restore) the result to the new active media within the same media group. As a result, synthetic full backups require that at least two media drives for the same storage policy be available at the time the job is started. Synthetic full backups cannot be performed on subclients where the storage policy is associated with a stand-alone drive.

Running Synthetic Full Backups

Synthetic full backups can either be started manually or scheduled to occur at regular intervals. Do not concurrently run more than one synthetic full backup, especially synthetic full backups with multiple streams.

1. From the CommCell Console, navigate to <Client> | File System | defaultBackupSet.


3. From the Backup Options window, select Synthetic Full for Backup Type.

4. Select Immediate for Job Initiation.

5. Click OK.


Running an Incremental Backup Before or After a Synthetic Full Backup

An incremental backup can be run either before or after a synthetic full backup.

Running an incremental backup before the synthetic full ensures that any new or recently changed data is included in the synthetic full.

Running an incremental backup after the synthetic full ensures that any new or recently changed data since the backup that occurred prior to the synthetic full, but was not included in the synthetic full, is backed up by the incremental.

The sections below describe the steps to run an incremental backup before or after a synthetic full backup:



Synthetic Full Backup


3. From the Backup Options window, select Synthetic Full for Backup Type.

4. Select Run Incremental Backup and then select Before Synthetic Full or After Synthetic Full options.

5. Select Immediate for Job Initiation.

6. Click OK.


Ignoring Errors in Synthetic Full Backups

Errors encountered in synthetic full backups can be ignored, even if backup media is partially corrupted. Errors such as inability to read data (bad tape, files missing on disk media, etc.) will be ignored when this option is enabled.


2. Right click the subclient and click Backup.

3. From the Backup Options dialog box, select Synthetic Full.

4. Click Advanced.

5. In the Advanced Backup Options dialog box, click the Data tab.

6. Select Ignore Error in Synthetic Full.

7. Click OK to close the Advanced Backup Options dialog box.

8. Click OK .

Accelerated Synthetic Full Backups (DASH Full)

When a storage policy copy is deduplicated, synthetic full backups can be created in an accelerated mode to significantly reduce the copy duration. This is done by identifying and transferring the data signatures (instead of the data itself) to the target wherever possible.

Learn more...

Backups follow mount points by default, backing up both the configuration and the data on the mounted volume. You can use another subclient to backup the data on the mounted volume. In such case, you can exclude the data on the mounted volume from the default backup.

1. From the CommCell Browser, navigate to <Client> | File System |defaultBackupSet.

2. Right click the default <Subclient> and click Backup.


Backing Up Mount Points


4. Click Advanced and select the Advanced Backup Options dialog box.


6. Select (or clear) Follow Mount Points to include (or exclude) mount point data from the subclient.

7. Click OK.

Depending upon your selection, the mount point data will be included or excluded from the default subclient backup.

The system protected files are the critical files that are installed as a part of windows operating system installation. For example, files with a .dll, .exe, .ocx, and .sys extension and some True Type fonts.

The system protected files are backed up by default via System State. Follow the steps given below to exclude these files from a backup:


2. Right click the default subclient and click Backup.




6. Select (or clear) Back up Files Protected by System File Protection to include (or exclude) system protected files from the subclient.

7. Click OK.

The system protected files will be excluded from the subclient when you run the backup.

The Hot Fix information is backed up by default. You can include or exclude the Hot Fix information from a subclient.





When backups are run from multiple nodes on clustered file systems, the same content is backed up multiple times. Backups should be run on only one node to avoid such duplicate content backups. However, the other nodes can also be configured to run backups but make sure that the clustered file system mount point is added to the file system exclusion list of the physical machine's subclients.

For VERITAS Cluster File System, the clustered file system mount point is added automatically to the file system exclusion list when backup is run for the first time on the virtual node/s.

Backing Up System Protected Files

If you exclude the system protected files from the backup, you cannot use the backup for full system restore or system state restore.

Backing Up HotFix Information



6. Select (or clear) HotFix Information to include (or exclude) Hot Fix information from the subclient.

7. Click OK.

8. You can track the progress of the job from the Job Controller.

Depending upon your selection, the Hot Fix information will be included or excluded from the subclient when you run the backup.

Follow the steps given below to schedule a data protection operation:

1. From the CommCell Console, navigate to Client Computers | <Client> | File System | defaultBackupSet.

2. Right click the default <Subclient> and click Backup.

3. Click Schedule.

4. Click Configure.

5. Select the appropriate scheduling options. For example:

Click Weekly.

Check the days you want the run the restore job.

Change the Start Time to 9:00 PM

Click OK to close the Schedule Details dialog

Click OK to close the Backup Options dialog

The backup job will execute as per the schedule.

See Scheduling for a comprehensive information on scheduling jobs.

1. From the CommCell Console, navigate to <Client> | File System | <On Demand Backup Set>.


3. Click Browse.

4. Navigate to the Directive file or Content file that you want to use.

5. Click OK.

6. Select Immediate to run the job immediately.

Scheduling a Backup

Performing an On Demand Backup


7. Click OK.

You can track the progress of the job from the Job Controller.

Backing up Remote Storage Data

Remote Storage is used to extend disk space on your server without adding more hard disks. It automatically copies eligible files on your local volumes to a library of magnetic tapes disks and monitors the amount of space that is available on your local volumes.

By default, when you back up the data in Remote Storage, the pointers to the remotely stored data and the data gets backed up. If you want to conserve disk space, you can backup only the pointers and exclude the actual data from the backup.

1. From the CommCell Console, navigate to <Client> | File System |defaultBackupSet.





6. Select (or clear) Backup data in Remote Storage to include (or exclude) the remote storage data from the subclient.

7. Click OK.

Depending upon your selection, the remote storage data will be included or excluded from the subclient when you run the backup.

Backing up WINS and DHCP Services

You can backup the WINS and DHCP services during the system state backup. You must stop these services to include them in the system state backup.




4. Click Advanced.


6. Select (or clear) Stop DHCP Service when Backing up System State Data to include (or exclude) the DHCP services in the system state backup.

7. Select (or clear) Stop WINS Service when Backing up System State Data to include (or exclude) the WINS services in the system state backup.

8. Click OK.

Depending upon your selection, the WINS and DHCP services will be included or excluded from the subclient when you run the backup.

Additional Backup Options or Windows 2003


Jobs can be managed in a number of ways. See Job Management for a comprehensive information on managing jobs.

The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel. Keep in mind that changes made to this configuration will affect all jobs in the entire CommCell.

To Configure the job restartability for a specific job, you can modify the retry settings for the job. This will override the setting in the Control Panel. It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.

Configure Job Restartability at the CommServe Level

1. From the CommCell Browser, click Control Panel icon.

2. Select Job Management.

3. Click Job Restarts tab and select a Job Type.

Select Restartable to make the job restartable.

Change the value for Max Restarts to change the maximum number of times the Job Manager will try to restart a job.

Change the value for Restart Interval (Mins) to change the time interval between attempts for the Job Manager to restart the job.

4. Click OK.

Configure Job Restartability for an Individual Job

1. From the CommCell Console, navigate to <Client> | File System | <Backup Set>.

2. Right-click the Subclient and select Backup

3. Click Advanced.

Managing Jobs

Backup jobs for this Agent are resumed from the point-of-failure.


4. In the Advanced Backup Options dialog box, click the Job Retry tab.

5. Select Enable Total Running Time and specify the maximum elapsed time before a job can be restarted or killed.

Select Kill Running Jobs When Total Running Time Expires to kill the job after reaching the maximum elapsed time.

6. Select Enable Number Of Retries and specify the number of retries.

7. Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspending a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.

2. The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Resume.

2. As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Kill.

2. Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

Viewing List of Backed up Files in a Job

Use the ListFilesForJob utility to generate a list of files which are backed up during a specific job. Follow the steps give below to create a file which contains the list of files:

1. Open the Command Prompt and navigate to following location:

<Software_Installation_Directory>\hds\Base\

2. Enter the following command:

ListFilesForJob.exe -job <JOBID> -ma <MAName> [-vm <Instance>] [-flag <ArchiveBitFlag>] [-tmpdir <TMPDIRPATH>] [-o <OUTFILENAME>]

Where:

SuspendTemporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.

ResumeResumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting.

KillTerminates a job.

JobID the job id of the job for which you are generating the list.MAName Name of the MediaAgent which is used to perform the backup job.Instance Name of the instance which you have used to instal the Windows File System iDataAgent

This is an optional argument. If you do not specify any value, the job in Instance001 will be used by default to generate the list of files.ArchiveBitFlag 1 to set the Archive Bit

0 to reset the Archive Bit

This is an optional argument. If you do not specify any value, the archive bit will not change and the file that contains the list of files can not bdeleted.

TMPDIRPATH The directory in which you want to create the file.

This argument is optional. If you do not specify any directory, the file will be created in the default temporary directory.

The default temporary directory for the software is set using the dGALAXYTEMPDIR registry key. When you install Windows File System


3. Navigate to the directory specified in TMPDIRPATH and open the <OUTFILENAME> file to view the list of files.

The following table describes the available additional options to further refine your backup operations:

iDataAgent, the dGALAXYTEMPDIR registry key gets created at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance<xxx>\BaseOUTFILENAME The name of the file in which you want to store the list

Additional Options

OPTION DESCRIPTION RELATED TOPICS

Startup Options The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows:


2. Right-click the Subclient in the right pane and click Backup.

3. Click Advanced and click Startup tab.

4. Select the Change Priority checkbox.

5. Enter a priority number - 0 is the highest priority and 999 is the lowest priority.

6. Select the Start up in suspended State check box to start the job in a suspended state.

7. Click OK.

Refer to Job Priority and Priority Precedence.

Alerts This option enables users or user groups to get automatic notification on the status of the data protection job. Follow the steps given below to set up the criteria to raise notifications/alerts:



3. Click Advanced and select the Alert tab.

4. Click Add Alert.

5. From the Add Alert Wizard dialog box, select the required threshold and notification criteria and click Next.

6. Select the required notification types and click Next.

7. Select the recipients and click Next.

8. Click Finish.

9. Click OK.

Refer to Backup (Data Protection) for a list of Available Alerts.

Refer to Alerts and Notificationsfor comprehensive information on setting up Alerts.

Command Line Backups Command Line Interface enables you to perform backups or restore from the command line. The commands can be executed from the command line or can be integrated into scripts.

You can also generate command line scripts for specific operations from the CommCell Browser using the Save As Script option.

Refer to Command Line Interface.

CommCell Readiness Report

The CommCell Readiness Report provides you with vital information such as connectivity and readiness of the Client, MediaAgent, and CommServe. It is useful to run this report before performing a backup or a recovery operation. Follow the steps given below to generate the report:


2. Click Readiness.


3. If necessary, select Reports | CommServe | CommCell Readiness in the left pane.

4. Select the Computers tab, and then click Modify below the Computers list.

5. In the dialog box that appears, clear Include All Client Computers and All Client Groups.

6. Select the appropriate client from the Exclude list, and then click Include >.

7. Click OK.

8. Select the MediaAgent tab, and then clear Include All MediaAgents.

9. Select the appropriate MediaAgent from the Exclude list, and then click Include >.

10. Click Run.

The report appears in your default Web browser.

Refer to CommCell Readiness Report.

Backup Job Summary Report

The Backup Job Summary Report provides you with information about all of the backup jobs that are run in last 24 hours for a specific subclient. You can get information such as status, time, data size, and so on for each backup job. It is useful to run this report after performing the backup. Follow the steps given below to generate the report:


2. Click Summary.


3. If necessary, select Reports | Jobs | Job Summary in the left pane.

Refer to Backup Job Summary Report.


4. On the General tab, select Data Management.

5. Select the Computers tab.

6. Select Subclient, and then select the Edit sub tab.

7. Navigate to Client Computers | <Client> | File System | Backup Set | <Subclient>.

8. Click Run.

The report appears in your default Web browser.Data Path Options Data Protection operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data

Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path:



3. Click Advanced and select the Data Path tab.

4. Select the MediaAgent and Library.

5. Select the Drive Pool and Drive for tape library.

6. Click OK.

Refer Change Data Path.

Index Cache Server Index Cache Server provides the facility to automatically continue data protection operations when there are job failures due to loss of connectivity to the index. You can configure the Index Cache Server as follows:

1. From the CommCell Browser, navigate to Storage Resources | MediaAgent.

2. Right-click the <MediaAgent> and click Properties.

3. Click the Catalog tab and ensure that the Index Cache Server is configured.



6. Click Advanced.

7. Make sure that the Use shared profile if present with transaction logging option is selected.

8. Click OK.

Refer to Index Cache Server for more information.

Start New Media The Start New Media option enables you to start the data protection operation on a new media. This feature provides control over where the data physically resides.Use the following steps to start the data protection operation on a new media:



3. Click Advanced and select the Media tab.

4. Select the Start New Media check box.

5. Click OK.

Refer to Start New Media.

Mark Media Full This option marks the media as full, two minutes after the successful completion of the data protection job. This option prevents another job from writing to this media. Follow the steps given below:



3. Click Advanced and select Media tab.

4. Select the Mark Media Full on Success check box.

5. Click OK.

Refer to Export Media.

Allow other Schedules to use Media Set

The Allow Other Schedules to use Media Set option allows jobs that are part of the schedule or schedule policy and using the specific storage policy to start a new media. It also prevents other jobs from writing to the same set of media.




4. Select the Allow Other Schedules To Use Media Set check box.

5. Click OK.

Refer to Creating an Exportable Media Set.

Reserve Resources Before Scan

Media is reserved for a job when the job is ready to write data. You can use this option to reserve the media during the initial phase of the job. Follow the steps given below to reserve media:





4. Select the Reserve Resources before Scan check box.

5. Click OK. Extended Data Retention This option allows you to extend the expiration date of a specific job. This will override the default

retention set at the corresponding storage policy copy. Follow the steps given below to extend the expiration date:




4. Select one of the following options: Infinite - Select this option to extend the expiration date by infinite number of days Number of day - Select this option to specify the number of days to extend the expiration date and then enter the number of days.

5. Click OK.

Refer to Extended Retention Rules.

Vault Tracker This feature provides the facility to manage media that is removed from a library and stored in offsite locations. Depending on your VaultTracker setup, select the required options. Use the following steps to access and select the VaultTracker options.



3. Click Advanced and select the VaultTracking tab.

4. Select the required options.

5. Click OK.

Refer to VaultTracker or VaultTracker Enterprise.


Advanced Restore Data - Windows File System

Performing an Out-of-Place RestoreRestore to Different Folder on the Same ClientRestore to a Different Client

Performing a Cross-Platform Restore

Restoring to a UNC Path/NFS-Mounted File System

Renaming Files on Restore

Overwriting Data During Restore

Restoring Only When It Exists in the Destination

Restoring by JobsRestore All the Data Backed Up During a JobRestore Specific Data Backed Up During a Job

Restoring From a Failed or Killed Job

Resubmitting a Restore Job

Filtering Data from RestoresSupported Wildcards in Filters

Restoring Data Using a Map FileCreate a Map FileAdd Files and Folders with Unicode Characters to a Map FileRestore Using a Map FileCombine Browse and Restore With the Map File Restore

Restoring Deleted Files

Setting Up Pre-Post ProcessesSet up a Pre/Post Process to Run After Each Attempt

Restoring the Full System

Restoring the System StatePrerequisitesRestore the System State in-PlaceRestore the System State Out-Of-PlaceCross Hardware Restore of the System StateRestore Specific System State Objects

Restoring Data on Storage Pools for Windows Server 2012

Restoring Communication Server DataRestore Lync Server Data and SettingsRestore the Office Communications Server (OCS) Data and Settings

Restoring ACLsRestore Only the ACLsRestore Only the Data

Restoring Virtual MachinesMicrosoft Virtual ServerMicrosoft Hyper-V

Listing Media

Scheduling a Restore

Managing Restore JobsRestarting Jobs Controlling Jobs

Additional Restore Options

You can restore the data to following locations:

Different folder on the same computer from which the data was backed up

Different computer

Restore Data Browse and Restore Find Data

Table of Contents

Performing an Out-of-Place Restore


Keep in mind that the destination computer must reside in the same CommCell as the client whose data was backed up.

Restore to Different Folder on the Same Client

Follow the steps given below to restore data to a different folder on the same client from which data is backed up:


2. Right-click the <Subclient> in the right pane and then click Browse and Restore.


4. Select the data that you want to restore and click Recover All Selected.

5. Clear the Restore to same folder check box and click Browse.

6. Click OK.

7. Use the options in the Preserve Source Paths area to exclude folders (and its contents) from the source path.


6. Click OK.

7. Use the options in the Preserve Source Paths area to exclude folders (and its contents) from the source path.

For Example: If the selected data is Documents\Users\Memos\Sales, and you want to restore data only from the Sales folder, set the Preserve <n> level from end of source path option to 1.

If the selected data is Documents\Users\Memos\Sales, and you want to restore the data from Memos and Sales folders, set the Remove <n> level from beginning of source path option to 2.

8. Click OK.

Restore to a Different Client

Follow the steps given below to restore data to a different client:





5. Clear the Restore to same folder check box.

6. In the Destination Client list, select the client. You can select any client that is in the same CommCell as that of the client from which the data was backed up.

7. Select the Restore to same folder check box to restore to the same folder on the destination.

8. Click OK.

Make sure that the following are excluded while performing the restore operation:

1. *:\drivers\*

2. *:\win*\inf\*


You can restore data to the following platforms:

All supported versions of Windows

All supported versions of Unix, Linux and Macintosh

You cannot restore encrypted files from a windows client to the Unix client.

Follow the steps given below to perform a cross-platform restore:





5. In the Destination Client list, select the client. You can select any client that is in the same CommCell as that of the client from which the data was backed up.


7. Select the destination folder and click OK.

8. Click OK.

The data will be restored to a different client. The location of the data will remain same as the source client. If you restore a shared folder from one client computer to another client computer, the share status of the folder will be restored.

If you select the Restore to same folder check box, the data will be restored to the same folder on the destination client. All the existing data in that folder will be overwritten during the restore operation.

Performing a Cross-Platform Restore


Follow the steps given below to restore data to a UNC path (Windows) or NFS-mounted file system (Unix).





5. In the Destination Client list, select the computer that hosts the share or mounted file system.


7. In the Destination Client list, click the client computer that hosts the mounted file system.

8. In the Specify Destination Path, enter the network share or click Browse.

9. In the Browsing for destination folder on <client> dialog box, select the destination folder and click OK.

For example: /finite/nftest/test

10. Enable Impersonate User Checkbox.

11. Enter a username and password that has all permissions for the folder to which the data will be restored. This user should be allowed to create files in the destination folder of the client where you are restoring the data.

12. Click OK.

If you do not want to overwrite the existing files during restores, you can append a suffix to the filenames and restore them as new files. (This suffix is appended to the filename before the extension.)

Follow the steps given below to rename files during the restore:


Restore to a UNC Path/ NFS-Mounted File System

Renaming Files on Restore






6. In the Destination Client list, select the client.

7. Click Advanced.

8. In the Advanced Restore Options dialog box, select the Map tab.

9. Enter the desired string that you want to append as a suffix to the filenames in Rename all restore files with suffix and click OK. For Example: Enter the string temp will rename file.txt to filetemp.txt.

10. Click OK.

11. Click OK to start the restore.

By default, the data in the destination is overwritten when the restored version is newer than the one in the destination.

Use the following steps to overwrite data irrespective of the destination version:





5. Ensure that the Overwrite Files check box is selected.

6. Click Unconditional Overwrite.

7. Click OK.

Overwriting Data during Restores


Follow the steps given below to restore the only data that already exists in the destination computer. This ensures any data removed from the destination computer is not reintroduced by the data recovery.





5. Ensure that the Overwrite Files check box is selected. (If it is not selected, only those files that do not exist on the destination will be restored.)

6. Select the Restore only if target exists check box.

7. Click OK.

Restoring Data only when it exists on the Destination


You can select a specific backup job for a restore. This method of restoring data is faster and useful in the following scenarios:

To restore point-in-time data associated with a specific backup job

To restore multiplexed data from the same client

Restore All the Data Backed Up During a Job

Following the steps to restore all the data data backed up during the selected job:

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System.

2. Right-click the <Backup Set> and select All Tasks | Restore by Jobs.

3. Enter the Start Time and End Time and click OK. The list of backup jobs, completed in the specified time period is displayed.

4. Right click the job you wish to restore and select Restore Selected Jobs.

5. Click OK.

Restore Specific Data Backed up During a Job

You can restore specific files and folders from the data backed up during the selected job. Follow the steps given below to restore specific files and folders from the selected backup job:



3. Enter the Start Time and End Time and click OK. The list of backup jobs, completed in the specified time period is displayed.

4. Right click the job you wish to restore and select Browse.

5. Click OK in the Browse Options dialog box.

6. Select data that you want to restore and click Recover All Selected.

7. Click OK.

You can restore from a failed or killed job. When restoring from a failed or killed job, the data backed up to the point of failure will be restored.

Failed or killed backup jobs are immediately aged regardless of their defined retention rules, therefore, these jobs can only be restored if the media is not yet overwritten. You can restore aged data from tape media but cannot restore from disk libraries.

Restoring by Jobs

Restoring from a Failed or Killed Job




3. Select Failed or Killed in the Job Status area of the Restore by Jobs Filter dialog box.

4. Enter the Start Time and End Time to specify the time period in which the job was failed or killed.

5. Click Advanced.

6. Select the Include Aged Data check box and click OK.

7. Click OK on the Restore Jobs Filter dialog box. The list of backup jobs, completed in the specified time period is displayed. The list also includes Failed or Killed jobs.

8. Right click the job you wish to restore and click Restore Selected Jobs.

9. Click OK.

You can rerun a failed or completed restore job. This is useful when you want to use all the options and settings configured for the original job.

Follow the steps given below to rerun a restore job:


2. Right-click the <Client> and click View | Job History.

3. Click Data Recovery Operations.

4. Select the Browse and Restore check box and clear all other check boxes.

5. Click OK.

6. Right-click the restore job that you want to resubmit from the Data Recovery Job History tab and click Resubmit Job.


Resubmitting a Restore Job

Filtering Data from Restores


During a restore operation, you can specify the files, directories, and file name patterns that you want to filter and exclude from restoring.





5. In the Recover Options for All Selected Items dialog box, click Advanced.

6. Select the Paths/Filters tab.

7. If you want to remove any files or folders from restore operation, click Add for Filter Item list and enter the path of the data. Wildcard entries must be expressed as complete paths.

You can also click Delete to remove existing source or filter items.

8. In the Advanced Recover Options dialog box, click OK.

9. In the Recover Options for All Selected Items dialog box, click OK.

Supported Wildcards in Filters

The following wildcards can be used in filters to include or exclude data when restoring data.









G:\Users\**\xpprofile\*.log will filter all


You can restore individual files and folders to different locations using a map file containing a list of files to be restored, with their corresponding restore paths.

Create a Map File

The map file is a text file in the CSV (Command Separated Value) format. Follow the steps given below to create a map file:

1. Create a text file on the client computer where you want to restore the data.

2. Add the mapping information in the file in the following format:

"<source path>","<destination path>"

files with the .log extension from any xpprofilesubdirectory under Users directory


? Any one character



To filter files:


To filter folders:













Restoring Data using a Map File


If the specified destination folder is not available, the necessary destination folder will be created during the restore.

The specified paths for both the source and destination should be absolute paths within the same client computer.

You can provide following information in a map file:

Add Files and Folders with Unicode Characters to a Map File

If the path or the filename contains Unicode characters, the Map File must be converted to a format that can be used by the data protection operation. The Unicode Conversion utility must be used to convert the Map File to a format that can be provided as input.

1. Using a text editor, create a file that contains a list of files/folders with Unicode characters. Make sure to save the file as a Unicode text file.

2. From the Command Line, navigate to the <software install folder>/base folder and type the following:

cvconvertunicode <source file> <destination file>Where:

<source file> is the full path and name of the file created in Step 1.

<destination file> is the full path and name of the destination file. The file will automatically be created by the utility.

3. Use the destination file as the Map File to perform the restore.

Restore Using a Map File

Use the following procedure to restore a list of files and folders from a computer and each of these files have a different destination.





5. Click Advanced.

6. Select the Map tab.

7. Select the Use map file check box and click Browse to navigate to the map file.

8. Clear the Restore unmapped file check box.



Information ExampleFile to File mapping "C:\dir1\file1.txt","E:\dir2\file1.txt"Folder to Folder mappings "C:\dir2","E:\dir2"Drive to Drive mappings "C:\","E:\"Renaming files/folder "C:\dir4\file2.txt","F:\dir5\file3.txt"Filtering files "C:\dir5",""File to File mapping with UNC path for source to UNC path for destination

When restoring to/from an UNC path, prefix the path with "UNC-NT"

"UNC-NT_Filer\Share\source2","UNC-NT_Filer\Share\destination2"

File to File mapping using UNC path for source "UNC-NT_Filer\Share\source2","E:\dir2"


Combine Browse and Restore with the Map File Restore

Use the following procedure to restore a set of files to a specified location with some files within that set to different destinations:





5. Click Advanced.

6. Select the Map tab.

7. Select the Use map file check box and click Browse to navigate to the map file.

8. Select the Restore unmapped file check box.




Follow the steps given below to restore deleted files:





5. Click Advanced.

6. Select the Browse Options tab.

7. Select the Restore deleted items check box and then select the Specify Time Range check box.

8. Select the time range to restore the files, deleted in that period of time.



You can run batch files or shell scripts before and/or after restore jobs. Follow the steps given below to setup a process before or after the restore job:





5. Click Advanced and then click the Pre/Post tab.

6. If you want perform a process before the restore job, enter the path for the batch file in the Pre Recovery Command box or click Browse to select the batch file.

7. If you want perform a process after the restore job, enter the path for the batch file in the Post Recovery Command box or click Browse to select the batch file.


Use Local Accounts - Select this option if the local account has permissions to execute the processes on the destination client.

Impersonate User - Select this option and enter the username and password, that has the permissions to execute the processes on the destination client.

9. Click OK.

Restoring Deleted Files

Setting Up Pre-Post Processes



Set up a Pre/Post Process to Run After Each Attempt

By default, a specified post process command is executed only on successful completion of the restore operation. Use the following steps to run a post process even if the restore operation did not complete successfully. For example, this may be useful to bring a database online or release a snapshot.





5. Click Advanced and then click the Pre/Post tab.

6. Enter the path for the batch file in the Post Recovery Command box or click Browse to select the batch file.

7. Select the Run Post Process for all attempts check box.

8. Click OK.



You can restore any one or all of the following components during full system restore:

File System

System State


Before performing a full system restore, make sure that the backup jobs are disabled for the client so that any scheduled backups for the client will not start until the full system backup is complete.

Follow the steps given below to disable backups at the client level:

1. From the CommCell Browser, right-click the <Client> and select Properties.

2. Click the Activity Control tab.

3. Clear the Enable Backup check box. This will disable backup jobs for the client and any scheduled backup jobs for the client will not start during the full system restore.

4. Click OK.

Follow the steps given below to perform full system restore:

1. From the CommCell Browser, navigate to Client Computers| <Client> | File System.

2. Right-click the <backupset> that contains the System State data and all the drives, point to All Tasks and then click Browse and Restore.

3. Select the required options from the Restore Options dialog box and click View Content.

4. Select the <BackupSet> box from the CommCell Browser which contains system state data and all the drives.

Restoring the Full System


5. Click Recover All Selected.

Select the required options from the Restore Options for All Selected Items dialog box and click OK.

For more information on Full System Restore on a Non Domain Controller, see Full System Restore of Non-Domain Controller.

For more information on Full System Restore of a Domain Controller on Windows Server 2003 and 2008, see Full System Restore of a Domain Controller on Windows Server 2003 and Full System Restore of a Domain Controller on Windows Server 2008 respectively.

System State components can be restored as follows:

Prerequisites

Install Microsoft .NET Framework 3.5 and 4 on the client computer. This is not required if the client computer has Windows 2003 or Windows XP.

If you have excluded any critical system state component from the backup, you cannot use that backup for the system restore. Ensure that the following critical system state components are not excluded from the backup:

Registry

System Protected Files

Active Directory

Cluster DB

Sysvol (For 2000 or 2003 domain controllers level)

DFSR (Windows 2008 Domain controller level)

Restore the System State In-Place

Before performing the system state restore ensure that the service user is a local administrator or services are running on a local system. The unconditional overwrite option is not applicable to system protected files.

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System | defaultBackupSet .

2. Right-click the default subclient in the right pane and then click Browse and Restore.

Restoring the System State

SYSTEM STATE CATEGORY COMPONENTS TYPE OF RESTORE

ComponentsSystem File Protection catalog and files


Active Directory

Quotas


Certificate Services database (if this is a certificate server)


Registry

COM+ database

1-Touch component


You can do an in-place and out-of place restore of all components together. Individual components can only be restored out-of-place. 1-Touch component will be used to perform 1-Touch Recovery. You cannot perform the Direct Restore or Browse and Restore of 1-Touch component.

ServicesDHCP

WINS

Event logs


RSM database

WMI database



All services except Content Indexing Catalogs can be restored together or individually in place or out of place. Content Indexing Catalog service will be included when you restore the entire system state but cannot be restored individually.


3. Click View Content in the Restore Options dialog box.

4. Expand the items in the defaultBackupSet in the left pane of the Client Browse tab and click the System State box.


6. Click OK.

Restore the System State Out-Of-Place

You can perform an out-of-place restore of the following entities in system state:

SYSVOL to restore deleted group policy objects (GPOs) back to the Active Directory server without having to do a full system restore.

Registry hives. This can be helpful if the server has crashed and you need a version of the registry. Once these hives are restored, you can manually replace the hives that exist on your server. You can also load them into the registry to view the contents before replacing them on server.

IIS metabase file to repair a IIS server using Microsoft procedures.


2. Right-click the backup set that includes the system state, click All Tasks and then click Browse and Restore.


4. Expand the items for the backup set in the left side of the Client Browse tab.

5. Click the System State box on the left.


7. If you want to restore the data to another client, select the client from Destination client list. The source client and destination client must reside in the same CommCell.

8. Clear the Restore to same folder option.

9. Enter the destination path in the Specify destination path box.

Optionally, click Browse to browse and select the path.

10. Click OK.

These methods require advanced skills. Be sure to visit the Microsoft support website and look for articles that describe these methods in more detail. By default, the system state data is unconditionally overwritten. However, for Windows Vista and higher versions of Windows Operating System, the system state data is overwritten only when the data on the media is newer than the data in the restore destination.


Cross Hardware Restore of the System State

The system protected files are always overwritten during the system state restore. When you are performing cross hardware restore, the drivers on the destination computer may be different than the drivers on the source computer. Therefore, it is recommended not to overwrite any data under %SYSTEMROOT%\System32\Drivers folder. For Windows Vista and higher versions of Windows, you can avoid overwriting any data under %SYSTEMROOT%\System32\Drivers folder.

Follow the steps given below when you want to perform the cross hardware system state restore for Windows Vista and higher versions of Windows:


2. Right-click the subclient that includes the system state, click Browse and Restore.



5. Click the System State box on the left.


7. Select a client from Destination client list. The source client and destination client must reside in the same CommCell.

8. Click Advanced.

9. Select Cross Hardware restore.

10. Click OK.

11. Click OK on the Restore Options for All Selected Items dialog box.

All the system state components and services data on the destination client will be overwritten, except the %SYSTEMROOT%\System32\Drivers folder.

Make sure that the following are excluded while performing the restore operation:

1. *:\drivers\*

2. *:\win*\inf\*

For Windows Vista and higher versions of Windows, the system protected files are overwritten only if the file on the media is newer than the file in the destination computer.


Restore Specific System State Objects

Follow the steps given below to restore individual system state components:

1. From the CommCell Browser, navigate to <Client>.

2. Right-click the backup set that includes the system state, click All Tasks | Browse and Restore.



5. In the left pane, expand [System State] to display the two main objects: Components, Services.

6. Select the Components and Services that you want to restore from the right pane of the Client Browse tab.


8. If you want to restore the data to another client, select the client from the Destination client list. The source client and destination client must reside in the same CommCell.

9. Clear the Restore to same folder option.

10. Enter the destination path in the Specify destination path box.

Optionally click the Browse button to browse and select the path.

11. Click OK.

You can restore the storage pool and data included in it using the following steps:




4. Select System State and C drive and then click Recover All Selected.

5. Reboot the computer after the restore completes. The storage pool will be restored automatically. After the restore operation, if you find that the drive letter is different from what it was initially you can manually change the drive letter.

6. Perform a separate restore operation for the data included in the storage pool.

Restoring Data on Storage Pools for Windows Server 2012


You can restore data and settings for OCS and Lync Server. The metadata for OCS and Lync server is backed up and restored with the SQL Server iDataAgent.

Restore Lync Server Data and Settings

Follow the steps given below to restore Lync Server data and settings:




4. In the right pane, expand the defaultbackupSet and navigate to the required data or setting under [OCS] | [Lync] folder.

5. Select the required data and settings to be restored and click Recover all Selected.

6. Click OK on the Recover Options for All Selected Items dialog box.

By default the selected data or setting will be restored to the source location.

If you want to perform out-of-place restore, the settings will be restored as files. Select the client from the Destination client list and specify the Destination path on the Recover Options for All Selected Items dialog box. If the destination client is a Lync server, the settings on the destination server will not be affected.

If you perform out-of-place restore of the settings, the settings will be restored as files.

7. Click OK.

Restore the Office Communications Server (OCS) Data and Settings

Follow the steps given below to restore OCS data and settings:




4. Select the OCS data and settings to be restored and click Recover all Selected.

5. Click OK on the Recover Options for All Selected Items dialog box.

By default the selected data or setting will be restored to the source location. If you want to perform out-of-place restore, select the client from the Destination client list and specify the Destination path on the Recover Options for All Selected Items dialog box. If the destination client is a Office Communication server, the settings on the destination server will not be affected.

6. Click OK.

Restoring Communication Server Data


The ACLs are restored by default when you restore a data. You can choose to restore only the data or the ACLs.

Restore Only the ACLs

You can restore only the ACLs and apply it to an existing data in the destination. Follow the steps given below to restore only the ACLs and apply it to the existing files in the destination:





5. Select Restore ACLs Only.

6. Click OK.

Restore Only the Data

You can restore only the data and inherit permissions from the parent directory in the destination. Follow the steps given below to restore only the data, without restoring the ACLs:




Restoring ACLs



5. Select Restore Data Only.

6. Click OK.

5. Select Restore Data Only.

6. Click OK.

Data secured by the Windows File System iDataAgent can be restored to a virtual machine running Windows.

Microsoft Virtual Server

To restore virtual machines on Microsoft Virtual Server using the Windows File System iDataAgent:

1. Shut down the virtual machine(s).

2. Remove the virtual machine(s) using the Virtual Server Web admin utility.

3. Remove the configuration files from the virtual machine directories.

4. Restore all files for each virtual machine backup to that machine's virtual machines configuration directory. (The directory with the machine DNS name can be restored in place.)

5. Using the Virtual Server Web admin utility, add a virtual machine. Use the full path for the vmc file of the machine you want to restore.

6. Select the option to restore from saved state.

The virtual machine(s) should restore and display as running.

Microsoft Hyper-V

To restore virtual machines on Microsoft Hyper-V using the Windows File System iDataAgent:

1. Shut down the virtual machine(s).

2. From the command prompt, run net stop vmms. You can also run this as a batch job in a PreRestore Process in the Advanced Restore Option dialog box.

3. Browse the backed up data and select the VM to be restored.

4. Run an in-place restore using the Unconditional Overwrite option.

5. From the command prompt, run net start vmms. You can also run this as a batch job in a PostRestore Process in the Advanced Restore Option dialog box.

6. Select the restored virtual machine in the Hyper-V Manager.

Restoring Virtual machines


7. Select the Start option of the virtual machine.

The virtual machine(s) should restore and display as running.

Before restoring any file or folder, you can review all the media that is associated with the selected data. Use this option to ensure that the media required to restore the selected data is available. You can also predict the total size of the data that you want to restore. Follow the steps given below to display the media and the size:

See List Media comprehensive information on media management and prediction.

1. In the CommCell Browser, navigate to Client Computers | <client> | File System

2. Right-click a <backupset> and click All Tasks | Browse and Restore.

4. Click OK.

5. Select the data that you want to restore and click List Media and Size.

6. Click OK.

The media associated with the selected data is displayed. If required, you can recall the required media from the export location.

1. From the CommCell Console, navigate to Client Computers | <Client> | File System.

2. Right-click a <Backup Set> and click All Tasks | Browse and Restore.


4. Select the data to restore and click Recover All Selected.

5. Click the Job Initiation tab and click Schedule.

6. Click Configure.

7. Select the appropriate scheduling options. For example:

Click Weekly.

Check the days you want the run the restore job.

Change the Start Time to 9:00 PM

Click OK to close the Schedule Details dialog

Click OK to close the Restore Options dialog

The restore job will execute as per the schedule.

Listing Media

Scheduling a Restore


See Scheduling for a comprehensive information on scheduling jobs

Once you initiate the restore operation, a restore job is generated in the Job Controller. Jobs can be managed in a number of ways. See Job Management for a comprehensive information on managing jobs.

The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel. This configuration can be changed at any time; however, changes to this configuration will affect all jobs run in the entire CommCell.

It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.

Configure job restartability at the CommServe level

1. In the CommCell Console, click the Control Panel icon, then double-click Job Management.

2. In the Job Restarts tab of the Job Management dialog box, select a job type from the Job Type list, and then select the Restartable check box.

3. To change the maximum number of times the Job Manager will try to restart a job, select a number in the Max Restarts box.

4. To change the time interval between attempts by the Job Manager to restart the job, select a number of minutes in the Restart Interval (Mins) box.


Managing Restore Jobs

Restore jobs for this Agent are re-started from the beginning.


Configure Job Restartability for an Individual Job

1. From the Restore Options dialog box, click Advanced, then select the Job Retry tab and specify the following as desired:

Total Running Time - The maximum elapsed time, in hours and minutes, from the time that the job is created.

Number of Retries - The number of times that Job Manager will attempt to restart the job.

Kill Running Jobs When Total Running Time Expires - Option to kill the job when the specified Total Running Time has elapsed, even if its state is "Running".

2. Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspending a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.

2. The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Resume.

2. As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

1. From the Job Controller of the CommCell Console, right-click the job and select Kill.

2. Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while

SuspendTemporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.

ResumeResumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting.

KillTerminates a job.


the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

The following table describes the available additional options to further refine your restore operations:

Additional Restore Options

OPTION DESCRIPTION RELATED TOPIC

Skip Errors and Continue This option enables you to to continue the restore job regardless of media errors and create a file that lists the full path names of the files that failed to get restored. Follow the steps given below to set this option:

1. From the CommCell Browser, click Client Computers | File System.

2. Right-click the <Backup set> that contains the data you want to restore, point to All Tasksand then click Browse Backup Data.

3. In the Browse Options dialog box, click OK.

4. In the Client Browse tab, select the data to be restored and click Recover all Selected.

5. In the Restore Options for All Selected Items dialog box, click Advanced.

6. In the Advanced Restore Options dialog box, click General.

7. On the General tab, select the Skip errors and continue check box.

8. Click OK. Use Exact index This option enables you to use the index associated with the data protection operation performed

at a specific time or the latest index. By default, the system uses the index associated with the most recent data protection operation when your Browse the data.

This option allows you to associate the media with the most recent index available in the CommCell. Follow the steps give below to use exact index:






6. In the Advanced Restore Options dialog box, click General.

7. On the General tab, select the Use Exact Index check box.

8. Click OK. Startup Options The Startup Options are used by the Job Manager to set priority for resource allocation. This is

useful to give higher priority to certain jobs. You can set the priority as follows:






6. In the Advanced Restore Options dialog box, click Startup.

7. On the Startup tab, select Change Priority.

8. Enter a priority number - 0 is the highest priority and 999 is the lowest priority.

9. Select the Start up in suspended State check box to start the job in a suspended state.

10. Click OK.

Refer to Job Priority and Priority Precedence.

Copy Precedence By default, the system retrieves data from the storage policy copy with the lowest copy precedence. If the data was pruned from the primary copy, the system automatically retrieves data from the other copies of the storage policy in the lowest copy precedence to highest copy precedence order. Once the data is found, it is retrieved, and no further copies are checked.

You can retrieve data from a specific storage policy copy (Synchronous Copy or Selective Copy). If data does not exist in the specified copy, the data retrieve operation fails even if the data exists in another copy of the same storage policy. Follow the steps given below to retrieve the data from a a specific storage policy copy:






Refer to Recovering Data From Copies.


6. In the Advanced Restore Options dialog box, click Copy Precedence.

7. On the Copy Precedence tab, select the Restore from copy precedence check box.

8. Enter the copy precedence number.

9. Click OK. Data Path Options The data recovery operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data

Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path:






6. In the Advanced Restore Options dialog box, click Data Path.

7. On the Data Path tab, select the MediaAgent and Library.

8. Select the Drive Pool and Drive for tape library.

9. Select the name of the Proxy server if you wish to restore using a proxy server.

You can select the Proxy server only when you are restoring from a snapshot. This option is not available for a regular restore.

10. Click OK.

Refer to Change Data Path.

Encryption If the client's data is encrypted with a pass phrase, you must enter the pass-phrase to start the data recovery operation. Follow the steps given below to enter the pass-phrase:






6. In the Advanced Restore Options dialog box, click Encryption.

7. Enter the Pass Phrase.

8. Click OK.

Refer to Data Encryption.

Alerts This option enables users or user groups to get automatic notification on the status of the data recovery job. Follow the steps given below to set up the criteria to raise notifications/alerts:

6. In the Advanced Restore Options dialog box, click Alerts.

7. Click Add Alert.

8. From the Add Alert Wizard dialog box, select the required threshold and notification criteria and click Next.

9. Select the required notification types and click Next.

10. Select the recipients and click Next.

11. Click Finish.

12. Click OK.

Refer to Alerts and Notifications.

Command Line Restores Command Line Interface enables you to perform backups or restore from the command line. The commands can be executed from the command line or can be integrated into scripts.

You can also generate command line scripts for specific operations from the CommCell Browser using the Save As Script option.

Refer to Command Line Interface.

CommCell Readiness Report

The CommCell Readiness Report provides you with vital information such as connectivity and readiness of the Client, MediaAgent, and CommServe. It is useful to run this report before performing a backup or a recovery operation. Follow the steps given below to generate the report:


2. Click Readiness.


3. If necessary, select Reports | CommServe | CommCell Readiness in the left pane.

4. Select the Computers tab, and then click Modify below the Computers list.

5. In the dialog box that appears, clear Include All Client Computers and All Client Groups.

6. Select the appropriate client from the Exclude list, and then click Include >.

7. Click OK.

8. Select the MediaAgent tab, and then clear Include All MediaAgents.

Refer to CommCell Readiness Report.


Back to Top

9. Select the appropriate MediaAgent from the Exclude list, and then click Include >.

10. Click Run.

The report appears in your default Web browser.Restore Job Summary Repport The Restore Job Summary Report provides you with information about all the data recovery jobs

that are run in last 24 hours for a specific client and agent. You can get information such as failure reason, failed objects, job options, and so on. It is useful to run this report after performing the restore. Follow the steps given below to generate the report:


2. Click Summary.


3. If necessary, select Reports | Jobs | Job Summary in the left pane.

4. On the General tab, select Data Recovery Jobs.

5. Select the Computers tab.

6. Select the appropriate client and the appropriate agent.

7. Click Run.

The report appears in your default Web browser.

Refer to Restore Job Summary Report.


Browse and Restore - Windows File System

Understanding the Restore Options Window

View Pie charts and Size Distribution during BrowseShow Distribution Pie Chart

Browse and Restore Latest Data

Browse and Restore Data Before a Specified Backup Time

Browse and Restore Data Between a Specified Backup Time

Browse and Restore Data Backed up in Past n Days

Browse and Restore Troubleshooting Folders

Browse and Restore from Copies

List Media

Image/No-Image Browse and Restore

Browse and Restore Multiple Versions of a File

Establish the Page Size for a Browse

Browse and Restore Using a Specified Path

Browse and Restore Using MediaAgent

Browse and Restore Using Filters/WildcardsSupported Filters

Frequently Asked QuestionsHow are filters applied to file names and folders?Can I use any MediaAgent while Browsing Using Filters?Can I use Wildcards to specify a pattern of File Names in the Browse Filters?Why don't I see the Pie chart representation in the browse Results?Why do I see Folders when I only specified File Name filters?How do I optimize my browse?How do I Distinguish the Deleted Files in my Browse Results?Why don't I see the file size of failed files? Why don't I see deleted files when I browse using Modified Date filter?

Browse provides an easy-to-use convenience to search and restore data.

You can open the browse and restore window from backup-set or subclient level. The sub levels displayed in the result window is based on where you start the browse operation.

Selecting Objects From the Restore Window for Restore

The restore window displays objects and consists of two parts:

The left pane displays the object tree at the selected level.

The right pane displays the contents of the selected object.

Note that the window displays only the data that was obtained by a backup. Data that is excluded by a filter, or data which did not exist as of the specified browse time does not appear in the window.


Table of contents

Understanding the Restore Options Window


Selections follow these rules:

All selections are recursive.

Clicking a box again causes the selection to be cleared.

If you select an object in the left pane, then all of its contents are selected.

You can select a specific object in the right pane.

Selection status is revealed by the selection icons as follows:

The Show Size Distribution option displays the sizes of files and folders, as both a list and a pie chart. The depiction shows the nine largest single entities (files and folders) sorted by size (largest first), followed by a tenth item showing the sum of the remaining entities. If this option is selected, the browse results are sorted by file and folder size, largest first. If this option is not selected, the results are sorted as for Windows Explorer (folders by name on top, then files by name).

This option is applicable to File System and OnePass-enabled clients.

Show Distribution Pie Chart

To view the pie chart and see size distribution:



3. In the Browse and Restore Options dialog box, click the Advanced tab.

4. Select the Show size distributions option.

5. To export the chart as a file, click one of these icons to the left of the chart:

PDF

HTML

Excel

6. Select a Paper Size and Zoom if you wish.

7. Select Orientation as Landscape or Portrait.

8. Select a Table Overflow Mode.

9. Click OK.

Follow the steps given below to view the latest data backed up by a backup set:




The latest data backed up by all the subclients is displayed in the Client Browse tab.

Indicates that the object is not selected for restoration.Indicates that a portion of the object is selected for restoration. i.e., only some of the child object(s) within the selected object.Indicates that the entire object, including all of its child objects, are selected for restoration.

View Pie charts and Size Distribution during Browse

You can view any folder's pie chart and size distribution by selecting that folder.

Browse and Restore Latest Data


Follow the steps given below to browse the data backed up before specified time. This will display data from all cycles that fall under the specified time range.



3. Select Time Range.

4. Under Absolute Time select End Time and enter a date and time to browse and restore data before it.


Follow the steps given below to browse data between specified time:



3. Select Time Range.

4. Under Absolute Time do the following:

Select Start Time and enter a date and time.

Select End Time and enter a date and time.

Data in between the time specified here will be browsed and restored.


Browse and Restore Data Before a Specified Backup Time

Browse and Restore Data Between a Specified Backup Time


You can specify a relative time for Browsing data for Restores. This provides flexibility in trawling backed up data from a wider time span rather than the need to remember an exact time range in which something was backed up.

Follow the step given below to Browse Data from a relative time:



3. Select Time Range and click Relative Time.

4. Enter a number in the Last field and select Day, Week, Month or Year to browse and restore data.


By default, when a browse operation is requested, information about collect files or job specific metadata files of a file system is not included in the browse results. These files are mainly useful at the time of Troubleshooting.



3. From the Restore Options dialog box, click the Advanced Options tab.

4. Select Include Troubleshooting Folders checkbox.


Browse and Restore Data Backed up in past n Days

Browse and Restore Troubleshooting Folders


By default, when a browse operation is requested, the software attempts to browse from the storage policy copy with the lowest copy precedence. If the data that you want to browse was already pruned from the primary copy, the software searches the other copies of the storage policy, starting from the copy with the lowest copy precedence to a copy with the highest copy precedence.

This feature is useful in the following conditions:

The media containing protected data for a particular copy has been removed from the storage library, you can choose to browse from a copy whose media are inside the library.

Allows browsing from a copy that accesses faster disk media rather than slower tape media.

When media drives used by a particular copy are busy with another operation, this helps in browsing from a different copy to avoid resource conflicts.




4. Select Browse from copy precedence checkbox and specify the preference number.


List media option is useful to predict media required to restore the index required to browse data. This is useful when the index is not available in the index cache. This option is also used to list media associated with data protection operations up to the specified date and time range.

Browse and Restore from Copies

If you specify a copy precedence number for a browse operation, the software searches only the storage policy copy with that precedence number in all storage policies used for securing the data. If data does not exist in the specified copy, the browse operation fails even if the data exists in another copy of the same storage policy.

List Media


The following section describes how to perform this operation.



3. Click List Media.

You can use the Latest Data to list media associated with the most recent data protection cycle.

Or Specify Browse Time to list media associated with data protection operations up to the specified date and time range.

4. From the List Media dialog box, click List Media for restore within specified time range.

5. Click OK.

6. The appropriate media is listed in the Media dialog box.

Image browse displays the structure of the entity as it existed as of some specified time. When you browse data in the image mode, the system by default returns the requested data based on the latest image available. The image browse can only restore the latest version. If the requested version was deleted before the most recent full backup, the default browse will not find the data.

The no-image browse is useful for retrieving data that may have been deleted at some unknown time. It is also useful to retrieve a previous backup version and show deleted files across cycles.



3. From the Restore Options dialog box, click the Advanced Options tab and select one of the following options:

Click and select the Show Deleted Items option to perform a no-image browse of the data.

Clear the Show Deleted Items option to perform an image browse of the data.


Image/No-Image Browse and Restore


By default, the system allows you to browse and recover previously backed up versions of data. This feature allows you to restore more than one version of the same file by restoring each version individually.

If a time range browse is performed, versions are shown across cycles.




4. From the Browse Window, right-click the file with multiple versions and then click View All Versions.

The All Version dialog box displays the available versions for the file.

The Page Size option allows you to specify the number of objects to be displayed in the browse window. You can browse through each page list by selecting the appropriate page number in the Browse window. Once the default is changed, it uses the same page size which was used in previous browse request until changed again.




4. Enter a value for Page Size.


Browse and Restore Multiple Versions of a File

Establish the Page Size for a Browse


The Browse Path option allows you to specify the starting point for the browse operation.



3. In the General tab, enter the browse path in Starting Path text area.


Data can be restored from any compatible library and drive type in the CommCell. By default, the system automatically identifies and restores data from any configured library in the CommCell, even if the media is not available in the original library in which the data protection operation was performed. Use this procedure to Browse using a specific MediaAgent.



3. From the Restore Options dialog box, click the Advanced Options tab and choose the MediaAgent that must be used to perform the browse.


Browse and Restore Using a Specified Path

Browse and Restore Using MediaAgent

If a MediaAgent is selected for browse, the library and media that are required for restore operation must be accessible to this MediaAgent for restore. The Restore may fail if it is not accessible.


Filters allow you to specify parameters to include specific files and folders when browsing data. You can specify filters for filename, modified date, file size, stubbed files, failed files and folder size for the files you need to browse.

Wildcard expressions can be used with filters to match specific file name patterns. This function provides the ability to restore files and/or folders/directories that have a common naming convention. For example, msde2.txt and msj4j.txt.

Note that a combination of wildcards in a single expression (e.g., access?.h*) can also be used. If the expression is specified by itself, without a path (*.txt), the system searches for and returns all data within the backup set that satisfies the expression. By preceding the expression with a path, the scope of the restored data can be narrowed. For example, specifying sys:\data\*.txt, would restore only those files and directories within the sys:\data directory with extensions of .txt.

When restoring directories, if a wildcard pattern that matches the name of a directory was specified, the system restores the directory, but none of the directory's contents. For example, if the wildcard restore string is tem?, the system restores any and all data named with a four-character string starting with the letters t, e, and m. If a directory name satisfies the wild card condition (e.g., sys:\temp) then only the directory would be restored; however, none of the files or any subdirectories contained therein are restored.

See Supported Wildcard Characters for a list of wildcards supported.

Use the procedure below to browse using the available filters:



3. From the Restore Options dialog box, click the Filter tab.

4. Select Add from Filter Criteria and choose a desired filter.


Browse and restore Using Filters/Wildcards

If more than one filter is used in the browse request, the objects qualifying all the filters will be displayed in the browse results.


Supported File System Filters

The following filters can be used to include files and folders when browsing data:

FILTERS DESCRIPTION EXAMPLE

File NameThis can be used to filter files with specific name patterns such as:

*.doc *.* data*.*

Multiple keywords can be specified together using “AND” and “OR” operators, for example:

*.docx AND data* *.txt OR *.xlsx Windows* OR Name*

You can specify an exact keyword using double quotation marks ("). For example, to find my_data, enter the following:

"my_data"

This will display all files with .doc as extension.

Modified DateThis can be used to filter files based on modification date such as:

Today Yesterday This Week This Month This Year

All folders that satisfy the modified date filter will be displayed in the result.

This will display files that have been modified yesterday.

File SizeThis can be used to filter files based on a specific size range in KB, MB or GB.

The following operators can be used to specify the file size:

greater than less than greater than equal to less than equal to

This will display all files that are Greater than 20 MB

Stubbed ObjectsThis can be used to filter stubbed files that were backed up.

This will show stubbed files along with other types of files that specify the browse criteria.

However, selecting Show Only will display only the stubbed files specifying the browse criteria.


Supported Wildcard Characters

ContainsThis can be used to filter content with specific wordings. The results differ with different combinations of backup and content indexing jobs that ran on the client.

If Content Indexing is enabled and at least one Content Indexing jobs has been run after the last backups job, this filter retrieves more precise results as the results are retrieved from the content indexed data. If Content Indexing is enabled and other filters are used along with this filter, the results are retrieved from the combination of what got backed up and content indexed. If Content Indexing is not enabled, this filter works like File Name filter. If Content Indexing is not enabled and both Contains and File Name filters are used, then the Contains filter is ignored.











? Any one character



To filter files:


To filter folders:





How are filters applied to file names and folders?

Filters for folder level property are applied first. Once a folder is shown for browse other filters for file level properties will be applied. However, you can specify only one item in each filter you select, multiple items in a single filter (with use of operators) will not be honored.

Can I use any MediaAgent while Browsing Using Filters?

Filtered browse is supported with MediaAgent of versions 10.0 and above. If a MediaAgent from a previous version of the software is used, all browse data would be shown and no filters will be applied to the browse results.

Can I use Wildcards to specify a pattern of File Names in the Browse Filters?

Yes, you can use wildcards in file names while specifying browse filters.

However, if file names or folder names have wild card characters as part of their name and the same are being used in the file name filter while browsing, it will not yield desired results.

How can I know if one or more index is not available?

Why do I see Folders when I only specified File Name filters?

Matching folder names will also get displayed when file name filters are specified as it will display everything matching the specified name.

How do I optimize my browse?

The performance of filtered browse operations may be slow while drilling down multiple folders. To get faster results, make sure to enter the path of the data in the Specify Browse Path in the browse window.

How do I Distinguish the Deleted Files in my Browse Results?










Frequently Asked Questions

A caution icon is displayed at the root level when one or more index is not available at the time of browse.


Why don't I see the file size of failed files?

File size is not recorded for failed files, hence if you specify both Failed Files and File Size filters together, it may yield unexpected results.

Why don't I see deleted files when I browse using Modified Date filter?

If a file was deleted in between backups, the deleted version of the file is not considered in modified date filter results. Hence, the file will not show up in the browse results.

Deleted files appear with a cross icon in the Browse results.


Find Data - Windows File System

Understanding The Find Options Window

Find Files With Specific File Names

Find Files With Specific Modified Date

Find Files With Specific File Size

Find Files That Were Stubbs

Find Files With Specific Wording As Their Content

Add Items to a Selected List

Find provides an easy-to-use convenience to search and restore data.

You can open the Find window from backup-set or subclient level. The sub levels displayed in the result window is based on where you start the browse operation.

Selecting Objects From the Find Window for Restore

The find window displays the contents of the selected object.

Note that the window displays only the data that was obtained by a backup. Data that is excluded by a filter, or data which did not exist as of the specified browse time does not appear in the window. Find allows you to search for a given file name, directory name, or a name pattern, modification date, file size, etc. from a backup.

Selections follow these rules:

All selections are recursive.

Clicking a box again causes the selection to be cleared.

Selection status is revealed by the selection icons as follows:

Find results work differently when Content Indexing Engine is installed and a Content Indexing job has been run after the last backup job.

If Content Indexing is enabled on the client and jobs are Content Indexed, all Find results will be displayed from Content Indexed data.

If Content Indexing is not enabled, all Find results will be displayed from what got backed up.

You can find files with specific names or name patterns. Wildcard expressions can be used to match specific file name patterns. This function provides the ability to find and restore files and/or folders/directories that have a common naming convention. For example, msde2.txt and msj4j.txt.

Note that a combination of wildcards in a single expression (e.g., access?.h*) can also be used. If the expression is specified by itself, without a path (*.txt), the system searches for and returns all data within the backup set that satisfies the expression. By preceding the expression with a path, the scope of the restored data can be narrowed. For example, specifying sys:\data\*.txt, would restore only those files and directories within the sys:\data directory with extensions of .txt.

If a wildcard pattern that matches the name of a directory was specified, the system restores the directory, but none of the directory's contents. For example, if the wildcard restore string is tem?, the system restores any and all data named with a four-character string starting with the letters t, e, and m. If a directory name satisfies the wild card condition (e.g., sys:\temp) then only the directory would be restored; however, none of the files or any subdirectories contained therein are restored.


Table of contents

Understanding the Find Options Window

Indicates that the object is not selected for restoration.Indicates that the entire object, including all of its child objects, are selected for restoration.

Find files with specific File Names


See Supported Wildcard Characters for a list of wildcards supported.

Use the following steps to find files with specific name or name pattern:

1. From the CommCell Browser, navigate to Client Computers | <Client> | File System

2. Right-click a Backup Set and click All Tasks | Find.

3. Click Add and select File Name filter from the Filters tab.

4. Add a file name or name pattern in the box, e.g. *.doc or *.*.

Multiple filters can be specified together using spaces in between.


Supported Wildcard Characters

You may also specify additional options to run the Find Operation, e.g. Time Range, Copy Precedence, Starting Path, Page Size etc. For detailed information on these options, see the corresponding Browse and Restorepage for your Agent.











? Any one character



To filter files:

C:\access?.doc will filter any files with the extension .doc on the C drive for which the name begins with- "access" followed by any one character such as access1.doc or


Use the following steps to find files with specific modification time:



3. Click Add and select Modified Date filter from the Filters tab.

4. Select a modification time from the drop down list, e.g. Last Month.


access5.doc. However, access12.doc or access15.doc will not be filtered because the last two characters in the name are variable. To filter access12 or access15, you must specify access?? in the subclient filters.

To filter folders:













Find Files with specific Modified Date



Use the following steps to find files that satisfy a specific file size:



3. Click Add and select File Size filter from the Filters tab.

4. Select an operator from the drop down list and enter the file size in the box provided, e.g. Greater than 2 MB.


Use the following steps to find files that existed as stubs when backed up:



3. Click Add and select Stubbed Objects filter from the Filters tab.

4.


Find Files with specific File Size


Find files that were stubs

You may also specify additional options to run the Find Operation, e.g. Time Range, Copy Precedence, Starting Path, Page Size etc. For detailed information on these options, see the corresponding Browse and Restore page for your Agent.


Use the following steps to find the backed up files with specific wording in their content:



3. Click Add and select Contains filter from the Filters tab.

4. Enter the content of the file you want to find, e.g. file system.


Use the following steps to add the desired file or files from the search results to the selected items list and then to restore the respective file or files:

1. From the results of Find Options window list, right-click the desired file name and click Add to Selected List.

2. Click Selected Items tab and right-click the desired file or files.

3. Click Restore.

Find files with specific wording as their content

This filter will work only if the Content Indexing Engine is installed and a Content Indexing job has been run after the last backup job.


Add Items to a Selected List


Data Aging - Windows File System

Getting Started

Extended Retention Rules

Data Aging is the process of removing old data from secondary storage to allow the associated media to be reused for future backups.

By default, all backup data is retained infinitely. However, you should change the retention of your data based on your needs. Note that if you continue to have infinite retention, you will also need infinite storage capacity.

1. From the CommCell Browser, navigate to Policies | Storage Policies | <Storage Policy>.

Right-click the <Storage Policy Copy> and click the Properties.


Under Basic Retention Rules for All Backups, click the Retain For.

Enter number of days to retain the data.

Enter number of cycles to retain the data.

Click OK.

3. Confirm Basic Retention dialog box will be displayed.

Click Yes.

Table of Contents

Getting Started


4. From the CommCell Console, click the Reports tab.

Click the Forecast icon.

5. Under Reports, Data Retention Forecast and Compliance is selected by default.

Click Run.

6. The report will display the data to be pruned when a data aging job is run.

7. From the CommCell Console, right click the <CommServe> icon, point to All Tasks and then click Data Aging.

To ensure only data intended for aging is actually aged, it is important to identify the data that will be aged based on the retention rules you have configured. Hence, ensure this report includes only the data you intend to age.

If necessary, fine-tune your rules so that only the intended data is aged.

Once you run a data aging job, the data will be pruned.


8. Under Job Initiation, by default Immediate is selected to run the job immediately.

Click OK.

9. You can track the progress of the job from the Job Controller window. When the job is completed, in the Job Controller the Status will be displayed as Completed.

Make sure that the job completes successfully. If the job did not complete successfully, rerun the job.

Extended retention rules allow you to keep specific full (or synthetic full) backups for longer periods of time.

Extended retention rules can be used in the following circumstances:

If you have a single drive tape library

If you want to create a hierarchical retention scheme (grandfather-father-son tape rotation)

In all other cases, it is recommended that the Auxiliary Copy feature be used for extended storage as it actually creates another physical copy of the data, thereby reducing the risk of data loss due to media failure.

Understanding Extended Retention Rules

Extended Retention Rules


Extended retention allows you to retain a specific full (or synthetic full) backup for an additional period of time. For example, you may want to retain your monthly full backups for 90 days.

Extended retention rules allow you to define three additional "extended" retention periods for full (or synthetic full) backups. For example:

You may want to retain your weekly full backups for 30 days.

You may want to retain your monthly full backup for 90 days.

You may want to retain your yearly full backup for 365 days.

A backup job will be selected for extended retention based on its start time. For example: If a backup job starts at 11:55 pm on August 31st and ends at 1 am on September 1st, then it will be selected as the last full backup for the month of August and will be picked up for extended retention.

Setting Up Extended Retention Rules

Use the following steps for setting up the extended retention rules:

1. Right-click the storage policy copy and click Properties.


3. Set the basic retention rules by clicking Retain for and entering the number of days and cycles appropriate for your organization.

4. Set the extended retention rules as follows:

a. Click the For button.

b. Enter the number of Days Total to retain the backup.

c. Click the Keep drop-down list, and select the desired backup criteria (e.g., Monthly Full, Weekly Full).

d. Click the Grace Days drop-down list and select the number of days (e.g., 2).

This allows you to consider the additional number of days along with the Extended Retention rule. For example, if the last full backup job fails with in the defined extended retention criteria, then the next full backup job that ran in the specified grace days will be selected for retention.

5. Repeat Step 4 to configure additional extended retention.

6. Click OK.

Advanced Topics

Data Aging - AdvancedProvides comprehensive information on additional Data Aging capabilities.


Disaster Recovery - Windows File System

Planning for a Disaster RecoveryCreating a Checklist

What Gets Restored

What Does Not Get Restored

Full System Restore of Non-Domain ControllerRestoring Teaming Network Adapters

Full System Restore of a Domain Controller on Windows Server 2003Replicating Active Directory Data to all the Domain Controllers in a Domain

Full System Restore of a Domain Controller on Windows Server 2008Replicating Active Directory Data to all the Domain Controllers in a Domain

Full System Restore of an RIS Server With SIS Common Store

Restoring a Cluster on Windows Server 2000 for Windows Server 2003Non-Authoritative RestoreAuthoritative RestoreRestoring Program Files for Virtual Server when Registry Keys are MergedRestoring Program Files for Virtual Server when Registry Keys are Not Merged

Restoring a Cluster on Windows Server 2008Restoring Cluster ServicesAuthoritative Restore of Cluster on Windows Server 2008Non-Authoritative Restore of Cluster on Windows Server 2008

Before you begin a disaster recovery, make sure to do the following:

Perform regular backups of the Windows file system or schedule the backups to run at regular intervals.

Install Microsoft .NET Framework 3.5 and 4 on the client computer. This is not required if the client computer has Windows 2003 or Windows XP.

On a Windows 2003 Server, restore to the same platform that you used for performing the backup. For example, You cannot do a full system restore on an x64 platform if you are using a 32-bit iDataAgent for backup.

If you have excluded any critical system state component from the backup, you cannot use that backup for the system restore. Ensure that the following critical system state components are not excluded from the backup:

Registry


Active Directory

Cluster DB

Sysvol (For 2000 or 2003 domain controllers level)

DFSR (Windows 2008 Domain controller level)

Creating a Checklist

If the operating system of your client is corrupted, you need to re-build the operating system.

During the rebuild you will be prompted for the following system information. Since the computer will be down during the operating system rebuild, you may not be able to access necessary information about the system. It is important to record such information before a disaster occurs.

Table of Contents

Planning for a Disaster Recovery

System Information How to Get itWindows Operating System Use Windows installation discs, CD, required service packs (SPs) and Hot fixes to install the Windows Operating System.Windows File System iDataAgent

Use Windows File System iDataAgent installation disc to install the Windows File System iDataAgent.

Drives Use the Disk Management utility to record the volumes and sizes of the hard drives in the system, which are needed to recreate the disk configuration in case of hard drive failure. Hard drives must be configured before restoring System State or file system data.

Computer name Use the same computer name and avoid changing other configuration settings.Network Interface Card configuration and settings 1. Click Start | Programs | Accessories | System Information.

2. In the System Information dialog box, click Components | Network |Adapter.

3. Note down the Network Adapter and Drivers information. TCP/IP Settings On the command prompt give following commands:


You can restore any one or all of the following components during full system restore:

File System

System State


By default, the Data Protection Suite files and registry entries are excluded from the restore. After the full system restore, when you install Data Protection Suite, all the latest patches will be available.

If the backup contains all the latest patches, create the nDisableGalaxyMerge registry key and set the value to 1 to restore the registry entries for Data Protection Suite.

1. Rebuild the system hardware if necessary.

2. Configure hardware devices such as disk arrays and ensure connectivity to all drives.

3. Using the instructions provided with the software, install Windows operating system and include any previously installed Service Packs and Hot Fixes.

Do not install IIS Services. These services will be restored automatically during the restore.

4. Format and partition the hard drives to match their previous configurations.

5. If the client was installed with a fully qualified domain name, perform the following tasks, otherwise, skip to the next step.

Change the Computer name to the fully qualified domain name to avoid a naming resolution conflict when the client is restored.

Add the IP address and the fully qualified domain name and a short name of the Client, MediaAgent and CommServe to the host file of the client in the following format:

<ip address> <fully qualified domain name> <short name>

Until the DNS server is restored, there is no domain name resolution and the client will be unable to communicate with the CommServe and MediaAgent computers unless this information is added to the host file.

Similarly, add the CommServe, MediaAgent and Client names and their IP addresses to the Host file of the MediaAgent, and CommServe when restoring a Domain Name Server.

6. Enable and configure TCP/IP support.

7. Configure the Network Interface Card(s).

Ensure that the Network Interface Card used is the first card listed in the network binding order when restoring a client with multiple Network Interface Cards.

8. Run the following command to verify network communications between the client computer and the CommServe:

ping <CommServe name>

9. Run the following command to verify network communications between the client computer and the MediaAgent:

ping <MediaAgent name>

10. Install the Windows File System iDataAgent all applicable updates on the default install partition of the client computer.

11. Open the CommCell Console.



hostname - Note down the fully qualified network name ipconfig - Note down the IP address, Subnet mask, TCP/IP domain name for the network, IP address of the domain name server (DNS) settings.

Video settings Note down the video settings if the resolution and color depth are important. Domain information Note down the domain in which this computer resides.Domain password Note down this information if you are restoring a domain controller.Local admin password Note down this information to log on to the computer once it is restored.

What Gets Restored

What Does Not Get Restored

Full System Restore of a Non-Domain Controller

When recreating partitions, you can Browse the backup data to determine the previous size of the partitions. When you browse the backup set, each drive letter will have its size noted in the Browse window.



15. Click OK.






21. Select the required options from the Restore Options for All Selected Items dialog box and click OK.

If the hardware of the destination computer is drastically different than the hardware of the source computer, do not select Unconditional Overwrite option.

22. Click Compare to view the Service Pack information of source and destination computer.

23. Note down the service packs that are not installed on the destination computer and click Close.

The Include Hotfix check box will be available for the source computer if you have chosen the Include Hotfix Information option during the backup.

24. Click No if the source computer and the destination computer has different service packs. Install the required service packs and hot fixes on the destination computer.

25. Click Yes if all the service packs on the source and destination computer are same. The full system restore starts.

26. Click OK to restart the computer.

27. Re-install any agents that were previously installed on the restored client computer.

28. Enable the backup jobs for the client by selecting the Enable Backup check box from the Activity Control tab of the Client Properties dialog box.

On a Windows Server 2008, select Configure Refresh from the Server Manager main page and update Features and Roles as they are not updated during a restart.


Restoring Teaming Network Adapters

If you are using teaming network adapters, follow the steps given below:

1. Uninstall the teaming software.

2. Restart the computer.

3. Install the teaming software.





Do not include the server in the domain. Keep it in the workgroup.
















Restart the computer in Directory Services mode after installing Windows File System iDataAgent.

Full System Restore of a Domain Controller on Windows Server 2003







15. Click OK.






21. Select one of the following from the Restore option for SYSVOL list:

Primary - Select this option when you are restoring for a standalone domain controller or the first domain controller restored in the network

Non-Authoritative - Select this option to restore the domain controller without replicating any changes to the other domain controllers on the network

Authoritative - Select this option to restore the domain controller and also replicate any changes to the other domain controllers on the network. You must run the ntdsutil to replicate the changes to the other domain controllers.


Select the other required options and click OK.






25. Click Yes if all the service packs on the source and destination computer are same. The full system restore starts.





Replicating Active Directory data to All the Domain Controllers in a Domain

The system performs a non-authoritative restore of the Active Directory by default, ensuring that any Active Directory data that has changed since the last backup is not replicated to other domain controllers. However, you can force an authoritative restore of the Active Directory and replicate all the restored data to all the remaining domain controllers in the domain by running the ntdsutil.

It is recommended that you review all Microsoft instructions and methods before replicating the data to all domain controllers.

Follow the steps given below to run the ntdsutil :

1. Perform the Authoritative full system restore of a domain controller.

2. Restart the computer in the Directory Services mode.

3. From the Command Prompt, type ntdsutil.

4. At the ntdsutil prompt, type Authoritative Restore.

5. At the Authoritative Restore prompt, type Restore Database.

6. Click Yes to confirm this operation.

7. Type quit to exit the Authoritative Restore prompt.

8. Type exit to end the ntdsutil session.

9. Type exit to exit the command prompt.

10. Restart the computer in normal mode and wait for replication to complete.

If you are performing an Authoritative restore of the SYSVOL without performing the full system restore, you must run the ntdsutil. When you run this utility, the policies and scripts will be accessible from Active Directory Users and Computers.










Until the DNS server is restored, there is no domain name resolution and the client will be unable to communicate with the CommServe and MediaAgent

Full System Restore of a Domain Controller on Windows Server 2008



computers unless this information is added to the host file.










Restart the computer in Directory Services mode after installing Windows File System iDataAgent.





15. Click OK.






21. Select one of the following from the Restore option for SYSVOL list:

Primary - Select this option when you are restoring for a standalone domain controller or the first domain controller restored in the network

Non-Authoritative - Select this option to restore the domain controller without replicating any changes to the other domain controllers on the network

Authoritative - Select this option to restore the domain controller and also replicate any changes to the other domain controllers on the network. You must run the ntdsutil to replicate the changes to the other domain controllers.


Select the other required options and click OK.






Click Yes if all the service packs on the source and destination computer are same. The full system restore starts.




28. Select Configure Refresh from the Server Manager main page and update Features and Roles as they are not updated during a restart.


Replicating Active Directory data to All the Domain Controllers in a Domain

The system performs a non-authoritative restore of the Active Directory by default, ensuring that any Active Directory data that has changed since the last backup is not replicated to other domain controllers. However, you can force an authoritative restore of the Active Directory and replicate all the restored data to all the remaining domain controllers in the domain by running the ntdsutil.

It is recommended that you review all Microsoft instructions and methods before replicating the data to all domain controllers.

Follow the steps given below to run the ntdsutil :

1. Perform the Authoritative full system restore of a domain controller.

2. Restart the computer in the Directory Services mode.

3. From the Command Prompt, type ntdsutil.

4. At the ntdsutil prompt, type Activate instance NTDS.

5. At the ntdsutil prompt, type Authoritative Restore.

6. At the Authoritative Restore prompt, type Restore Subtree DistinguishedName.

where DistinguishedName is the name of the subtree that is to be marked authoritative.

For example: Restore subtree DC=DomainName,DC=COM will restore domainname.com.

7. Click Yes to continue.

The restore process will complete and a message confirming the creation of one text and 2 LDAP Data Interchange Format (LDIF) files will be displayed.

8. Restart the computer in normal mode and allow time for replication to complete.

9. To run an LDIF file to recover back-links, type the following command at the command prompt.

ldifde -i -k -f FileName (where the FileName is the name of the LDIF file)

10. Repeat step 5 and 6 for each additional domain.





4. Add Remote Installation Services component.

5. Reboot your computer.

6. Manually add the computer to the original domain it was in.

7. Reboot your computer.

8. Recreate the drive letter where RIS (Remote Installation Services) and SIS (Single Instance Storage) were residing.

9. Run the following command:

Full System Restore of an RIS Server With SIS Common Store


10. Follow the command prompts and specify the original drive letter that contained the RIS and SIS.

Install the Windows File System iDataAgent all applicable updates on the default install partition of the client computer.





15. Click OK.






21. Select the required options from the Restore Options for All Selected Items dialog box and click OK.

Do not select Unconditional Overwrite option.

22. Restart your computer.

23. Remove the computer from the domain and add it to the Workgroup.

Non-Authoritative Restore

Performed a non-authoritative restore in the following scenarios:

Single node in a cluster fails completely (no boot) and the shared disks are still functional

Complete loss of all nodes and storage

Prerequisites

If you are restoring a cluster node running SQL or Exchange servers, see the Microsoft disaster recovery documentation for restoring SQL and Exchange servers before restoring the node.

When you are recovering primary node, turn off all cluster nodes except the primary node to be recovered.

Follow the steps given below to perform the Full System Restore of a Primary Node or Passive node:



risetup -check

Restoring a Cluster on Windows Server 2003


Configure all disk array devices with access to the shared array














Bind the public Network Interface Card before the Private network interface card.










15. Click OK.








21. Select the required options from the Restore Options dialog box and click OK.










28. Restore Program files for the virtual server. Use one of the following methods to restore the program files:

Restoring program files when registry keys are merged during the restore.

Restoring program files when registry keys are not merged during the restore.

Authoritative Restore

Perform the authoritative restore when all the cluster nodes are running and you want to restore the cluster database and restart the cluster services on all the nodes.

Follow the steps given below to perform the Full System Restore of a node that has the cluster database:



Configure all disk array devices with access to the shared array















Bind the public Network Interface Card before the Private network interface card.










15. Click OK.


















28. Restore Program files for the virtual server. Use one of the following methods to restore the program files:

Restoring program files when registry keys are merged during the restore.

Restoring program files when registry keys are not merged during the restore.

29. Enter Y (yes) for the following message:

Full iDataAgent Restore job completed. Do you want to reboot?


New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?


32. After the computer restarts, from a command prompt, navigate to <Install Directory>\base folder and enter the following command :

authorutil.exe -cluster

This command will stop the cluster services on all the nodes, replicate the cluster database information on all the nodes and then restart the services.

Restoring program files for Virtual Server when registry keys are merged

If the registry key nDisableGalaxyMerge is enabled before starting the full restore of primary node, the registry keys on a primary node are merged during the full system restore. As a result, the following resources are restored during the full system restore:

The CommVault Communications Service (GxCVD)

CommVault Client Event Manager (GxEvMgrC) cluster


The program files are required to start and run these resources. Perform one of the following steps to restore program files for a virtual server to the physical node that owns the virtual disk:

Select all the virtual disk data and restore it.

Restore only the program files in order to get the services started. Then restore the rest of the data using the virtual server's File System iDataAgent.

Restoring program files for Virtual Server when registry keys are not merged

If you haven't enabled the registry key nDisableGalaxyMerge before starting the full restore of primary node, the registry keys on a primary node are not merged during the Full System Restore. Follow the steps given below to restore program files on a virtual server:

1. Uninstall all iDataAgents from the virtual server.

2. Re-install File System iDataAgent and all other required iDataAgents on the virtual server

3. Restore the virtual server's data using the File System iDataAgent.

Restoring Cluster Services

On a Windows Server 2008 computers, the cluster services will be restored automatically in any of the following scenarios:

Authoritative Restore of Cluster on Windows Server 2008

Perform the Authoritative Restore of cluster on Windows 2008 if you alter the cluster configuration or delete a large number of resources. You can perform the authoritative restore only if all cluster nodes and services are running. Follow the steps given below to revert to the original cluster configuration:





5. Click OK.








Restoring the Cluster on Windows Server 2008

Situation Corrective ActionCluster files on witness disk/Quorum Disk) are corrupt Files in the \Cluster directory will be re-created.

Cluster configuration will be ‘pushed’ to the Witness Disk Cluster database (ClusDB) on a single node is missing or corrupt Healthy nodes will be contacted and an updated ClusDB will be downloaded.Complete loss of Witness Disk/LUN occurs If using Disk Only quorum model you need to use /ForceQuorum recovery

switch. Use Cluster Quorum Wizard to change quorum disk designation.


12. Select Authoritative from the Allow Authoritative for Cluster Database list.

13. Select the other required restore options and click OK.











19. Ensure that the cluster services are stopped on all the other nodes of the cluster. If required, stop the cluster services on all the other nodes.



21. Start the services on all the other nodes in the clusters.

Non-Authoritative Restore of Cluster on Windows Server 2008

Performed a non-authoritative restore in the following scenarios:

Single node in a cluster fails completely (no boot) and the shared disks are still functional

Complete loss of all nodes and storage

Follow the steps given below to perform the non-authoritative restore:





5. Click OK.









12. Select Non-Authoritative from the Allow Authoritative for Cluster Database list.

13. Select the other required restore options and click OK.













Additional Operations - Windows File System

Audit Trail

Auxiliary Copy

Enabling Laptop Backup for a Desktop Client

Erasing Backup Data

Global Filters

Online Help Links

Operating System and Application Upgrades

Operation Window

Reference Copy

Schedule Policy

Storage Policy

Subclient Policy

Uninstalling Components

The Audit Trail feature allows you to track the operations of users who have access to the CommCell. This capability is useful if a detrimental operation was performed in the CommCell and the source of that operation needs to be determined.

Audit Trail tracks operations according to four severity levels:

Critical: This level records operations that will result in imminent loss of data.

High: This level records operations that may result in loss of data.

Medium: This level records changes to the general configuration of one or more entities. Such changes may produce unintended results when operations are performed.

Low: This level records changes to status, addition of entities, and other operations that have minimal impact on existing CommCell functions.

To set Audit Trail retention periods:

1. From the Home tab in the CommCell Console, click Control Panel. The Control Panel dialog box appears.

2. From the Monitoring options, click Audit Trail.

3. From the Audit Trail dialog box, select the desired retention time (in days) for each severity level.

4. Click OK.

For details, see Audit Trail.

An auxiliary copy operation allows you to create secondary copies of data associated with data protection operations, independent of the original copy.

1. Expand the Policies node, right-click storage policy for which you want to perform an auxiliary copy, click All Tasks, and then click Run Auxiliary Copy.

2. If you are starting the auxiliary copy operation from the CommServe level, select the storage policy for which you wish to perform the auxiliary copy.

3. If the source copy is configured with a shared library, select the Source MediaAgent for the auxiliary copy.

4. Click OK to start the auxiliary copy operation. A progress bar displays the progress of the operation.

For details, see Auxiliary Copy.

The Laptop Backup feature provides access to a webconsole which you can use to manage data protection and data recovery operations for a desktop client. Follow the steps given below to use the webconsole:

Table of Contents

Audit Trail

Auxiliary Copy

If you are starting the auxiliary copy operation from the Storage Policy level, the Storage Policy field is already populated with the name of the Storage Policy you selected.

Enabling Laptop Backup for a Desktop Client


Disabling laptop Backup For a Desktop Client

The Erase Data feature allows you to permanently erase any data that can be backed up. Using Erase Data, you can erase data such as file system, system state, and office communications server (OCS) data.

1. Ensure that the File System iDataAgent is installed on a client computer.

2. Open the Command prompt and navigate to the following location:

Windows: <Software_Installation_Directory>\hds\Base\

Linux: /<install_path>/hds/Base/

3. Login to the CommServe using the qlogin command and commcell credentials.

Windows: C:\Company\Software\Base\> qlogin -cs commserve_name -u user_nameLinux or Macintosh: [root@localhost Base]# ./qlogin -cs commserve_name -u user_name

4. Run the following execscript operation using qoperation:

Usage:

Windows:

qoperation execscript -sn enableLaptopBackup -si ON -si <client name>Linux:

./qoperation execscript -sn enableLaptopBackup -si ON -si <client name>Where:

<client>: Specify the client name for which you want to enable laptop backup.

Example:

Enable Laptop Backup for desktop client xyz.

Windows: qoperation execscript -sn enableLaptopBackup -si ON -si xyzLinux: ./qoperation execscript -sn enableLaptopBackup -si ON -si xyz

5. Navigate to following location:

<Software_Installation_Directory>\hds\Base\

6. Run the Laptop2Taskbaricon.exe to launch the Backup Monitor.

7. Click Web Console and enter CommCell credentials.

8. Use the web console to manage data recovery and data protection operations for the desktop client. For more information about the operations which you can perform, refer to Restore -Laptop Users and Advanced Options - Laptop Users.

Follow the steps given below to disable the Laptop Backup feature for a desktop client:

1. Open the Command prompt and navigate to the following location:

Windows: <Software_Installation_Directory>\Base\

Linux or Macintosh: /<install_path>/hds/Base/

2. Login to the CommServe using the qlogin command and commcell credentials.

Windows: C:\Company\Software\Base\> qlogin -cs commserve_name -u user_nameLinux or Macintosh: [root@localhost Base]# ./qlogin -cs commserve_name -u user_name

3. Run the following execscript operation using qoperation:

Usage:

Windows:

qoperation execscript -sn enableLaptopBackup -si OFF -si <client name>Linux or Macintosh:

./qoperation execscript -sn enableLaptopBackup -si OFF -si <client name>Where:

<client>: Specify the client name for which you want to enable laptop backup.

Example:

Disable Laptop Backup for desktop client xyz.

Windows: qoperation execscript -sn enableLaptopBackup -si OFF -si xyzLinux or Macintosh: ./qoperation execscript -sn enableLaptopBackup -si OFF -si xyz

Erasing Backup Data


Configuring Erase Data

To erase data, you need to first assign a Filter Storage Policy for Erasing Data. Follow the steps given below to assign a Filter Storage Policy:

1. From the CommCell Browser, right-click the storage policy that you want to use as a filter storage policy, then click Properties.

2. From the General tab of the Storage Policy Properties dialog box, select the Allow Erase Data check box.

3. Click OK.

4. From the CommCell Browser, right-click the <Agent> and then click Properties.

5. From the Storage Device tab of the agent Properties dialog box, select a filter storage policy from the Filter Storage Policy list.

6. Click OK.

Running an Erase Data Job

After the configuration has been completed, you can now browse and erase data. Keep in mind that the erase data operation only erases the backup data - the source data will remain on the local hard drive. Therefore, it is recommended to delete the data from the source first so that it will not be backed up again. However, the stubs must be deleted from the source before running the erase data operation so that they are not backed up again. Otherwise, the synthetic full backup jobs will fail.

1. From the CommCell Browser, right-click the <Backup Set>, select All Tasks and then click Erase Data By Browsing.

2. You are warned that the data will be permanently removed. Click Yes to continue.

3. From the Erase Data by Browsing dialog box, click Browse.

4. In the Browse Options dialog box, select a browse time range and any advanced browse options, and click OK.

5. From the browse selection window, select the data objects that you want to erase, and click OK.

6. In the Job Initiation tab, select Immediate to run the job immediately.

You can track the progress of the job from the Job Controller or Event Viewer.

For details, see Erasing Backup Data.

Global Filters are exclusions that filter data from backups across all Agents in a CommCell that support the feature. Global Filters serve as a template for files, folders, and entities that should always be excluded from all (or most) backups in a CommCell, such as temporary data a computer does not retain or data that is recoverable by means other than a restore. This saves space on media and enhances backup performance.

By default, filters configured for a particular subclient override any Global Filters configured for the CommCell. You can, however, configure subclients to include global filters along with any filters already configured for the subclient.

For details, see Global Filters.

Configure Global Filters

1. From the CommCell Browser, right-click the CommServe, click Control Panel, and then click Global Filters.

2. Select Use Global Filters on All Subclients.

3. Click Browse to locate the files or folders to be excluded from backups and click OK.


Enable/Disable Global Filters for a Subclient

1. From the CommCell Browser, right-click the subclient for which you want to enable Global Filters and click Properties.


3. Select one of the following values from the Include Global Filters list:

ON to enable Global Filters for this subclient.

OFF to disable Global Filters for this subclient.

Use Cell Level Policy to enables or disables Global Filters for this subclient.

Global Filters

If the Use Global Filters on All Subclients option is enabled, then the Use Cell Level Policy option will enable Global Filters on this subclient.

If the Use Global Filters on All Subclients option is disabled, then the Use Cell Level Policy option will disable Global Filters on this subclient.


4. Click OK.

Use the following links to view the online help for the corresponding tabs in the CommCell Console:

Operating system upgrades are only supported when upgrading from one version of an OS to a different version of the same OS (e.g., Win2003 to Win2008). The two methods of upgrading are:

Seamless Upgrade - This involves uninstalling the Agent software, upgrading the operating system, and then re-installing the Agent software.

Online Help Links

Operations Entity Online Help Links Sub Links

ConfigurationAgent Windows File System Properties (General)

Windows File System Properties (Version)

Windows File System Properties (Security)

Windows File System Properties (Activity Control)BackupSet Windows File System BackupSet (General)

Windows File System BackupSet (Security)

Subclient Windows File System Subclient Properties (General)

Windows File System Subclient Properties (Content)

Windows File System Subclient Properties (Filters)

Windows File System Subclient Properties (Pre/Post Process)

Windows File System Subclient Properties (Encryption)

Windows File System Subclient Properties (Security)

Windows File System Subclient Properties (Storage Device)

Windows File System Subclient Properties (SnapProtect Operations)

Windows File System Subclient Properties (Activity Control)

Windows File System Subclient Properties (Open Files Failure Actions)

Windows File System Subclient Properties (Advanced Options)

Windows File System Subclient Properties (Add Multiple Content)

BackupBackup Options Windows File System Backup Options

Save As Script

Advanced Backup Options

Windows File System Advanced Backup Options (Data)

Windows File System Advanced Backup Options (Startup)

Windows File System Advanced Backup Options (Job Retry)

Windows File System Advanced Backup Options (Media)

Windows File System Advanced Backup Options (Data Path)

Windows File System Advanced Backup Options (VaultTracking)

Windows File System Advanced Backup Options (Alert)

RestoreRestore Options Windows File System Restore Options (General)

Windows File System Restore Options (Job Initiation)

Save As Script

Advanced Restore Options

Windows File System Advanced Restore Options (General)

Windows File System Advanced Restore Options (Startup)

Windows File System Advanced Restore Options (Pre/Post)

Windows File System Advanced Restore Options (Copy Precedence)

Windows File System Advanced Restore Options (Data Path)

Windows File System Advanced Restore Options (Paths/Filters)

Windows File System Advanced Restore Options (Encryption)

Windows File System Advanced Restore Options (Job Retry)

Windows File System Advanced Restore Options (Map)

Windows File System Advanced Restore Options (Browse Options)

Windows File System Advanced Restore Options (Alert)Operation Window Operation Window Windows File System Operation Window

Operating System and Application Upgrades


Full OS Replacement - This involves performing a clean install of a new version of the OS, re-installing any application software, then re-installing the CommServe, MediaAgent, and/or Agent software.

For Full OS Replacement, the client computer must be configured to have the CommServe, MediaAgent, and/or Client software re-installed to the same location, the same Fully Qualified Domain Name or short domain name, the same partitions, disk drive format (FAT, NTFS, et. al.), and IP configuration as previously.

Use the following strategy to upgrade the operating system software:

Identify the computers you want to upgrade and the CommCell components installed on each of these computers.

Choose the type of upgrade procedure you want to use on each computer: seamless or full replacement.

CommServe, MediaAgent, and Client computers can be upgraded in any order.

For details, see Operating System and Application Upgrades.

By default, all operations in the CommCell can run for 24 hours. To prevent certain operations from running during certain periods of the day, you can define operation rules so that these operations are disabled during those times.

When operation rules are configured, operations that are started within the time window specified will go to a queued (as opposed to pending) state. Once the time window specified in the operation rule has elapsed, these queued or running operations will resume automatically.

1. In the CommCell Browser, right-click the appropriate entity, click All Tasks, and then click Operation Window.

2. Click Add.

3. From the Operation Window dialog box:

Enter the name of the rule in the Name field.

Select either an administration, data protection (either full or non-full), and/or a data recovery operation from the Operations pane.

4. Click OK.

For details, see Operation Window.

Reference copy is a filtered backup of content from existing backups. You can run reference copy jobs on backed up data from Windows File System and Unix File System clients.

See Reference Copy - Configuration for step-by-step instructions.

An agent specific data protection schedule policy can be used as a scheduling template for data protection operations for Backup iDataAgents in a CommCell.

This type of data protection policy is useful when there are many clients or subclients within the CommCell that require same schedules for specific data protection operations. Additionally this policy provides the ability to granularly define advanced data protection options specific to the Backup iDataAgents.

Use the steps given below to create a data protection schedule policy:


2. Right-click Schedule Policies and click New Schedule Policy.

3. Type a name for the schedule policy in the Name box.

4. From the Agent Type list, expand Files | Protected Files and select the specific agent. For example, Windows File System.

5. Type an appropriate description in the Description box.

6. Click Add.

7. Type a name in the Schedule Name box and select the appropriate scheduling options.

8. Click the Backup Options tab and select the type of backup and other options that apply to your environment.

Optionally, you can click Advanced to define advanced backup options for the agents.

If it is necessary to remove Agent software to facilitate an operating system or application upgrade, do not delete the icon for the Agent from the CommCell Console, or all associated backed up data will be lost.

Operation Window

Reference Copy

Clients of the same Agent type can be specified as the subclient content.

Example: Windows File System clients can be specified as subclient content for a Windows File System Reference Copy client.

Schedule Policy


9. Click OK.

10. Click the Associations tab.

11. Select the client computer or client groups that you want to associate with the schedule policy. You can also associate the schedule policy to a specific Agent, backup set or subclient of a client computer by expanding the client node.

12. Click OK.

A Storage policy defines the data lifecycle management rules for protected data. Storage policies map data from its original location to a physical storage media and determine its retention period.


2. Right-click Storage Policies, and then click New Storage Policy.

3. Click Next.

4. Select Data Protection and Archiving to create a regular storage policy or CommServe Disaster Recovery Backup to backup the CommServe database and click Next.

5. In the Storage Policy Name box, specify the name of the storage policy, and then click Next.

6. From the Library list, select a library for the primary copy, and then click

7. From the MediaAgent list, select the MediaAgent, and then click Next.

8. Enter number of data streams and set the retention period for the policy, and then click Next.

9. Click Next.

10. From the MediaAgent Name list, select the MediaAgent.

11. In the Location box, type or click Browse to your designated deduplication database location, and then click Next.

Storage Policy


12. Confirm your selections, and then click Finish.

For details, see Storage Policy.

Subclient policies allow you to configure multiple subclients within a CommCell from a centralized template. This alleviates the need to manually configure each subclient that shares a similar configuration.

1. Expand the Policies node, right-click Subclient Policies and click New Subclient Policy.

2. Enter policy name in the Name entry field, then select the appropriate file system type from the iDataAgent drop-down list.

3. In the Subclient pane, assign a storage policy for each subclient template by clicking in the drop down box under the Storage Policy column.

4. Click OK.

For details, see Subclient Policies.

You can uninstall the components using one of the following method:

Method 1: Uninstall Components Using the CommCell Console

1. From the CommCell Browser, right-click the desired Client Computer and click All Tasks -> Add/Remove Software and click Uninstall Software.

2. Uninstall Software Options dialog will appear.

3. In the Uninstall Software tab, select Uninstall All to uninstall all the software packages.

4. In the Job Initiation tab, select Immediate to run the job immediately.

You can track the progress of the job from the Job Controller or Event Viewer.

Method 2: Uninstall Components from Add or Remove Programs

1. Click the Start button on the Windows task bar and then click Control Panel.

2. Double-click Add/Remove Programs.

For Windows Vista/Windows 2008, click Uninstall a Program in the Control Panel.

3. Click Remove to uninstall the components in the following sequence:

1. <Agent>

2. File System iDataAgent

3. Base Software

For details, see Uninstalling Components.

Back to Top

Subclient Policy

Uninstalling Components

Method 1: Uninstall Components Using the CommCell Console

Method 2: Uninstall Components from Add or Remove Programs


Command Line Interface - Windows File System

Log On to the CommServe

Backup Set Configurationqcreate backupsetqdelete backupset

Subclient ConfigurationCreating a SubclientModifying a SubclientRenaming a SubclientDeleting a SubclientGetting Subclient PropertiesAvailable Parameters for Subclient Configuration

Log Off from the CommServe

To run command line operations, you must first login to the CommServe.

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:

For example, to log on to CommServe 'server1' with username 'user1':

Use the following qcommands to configure backup sets for the Windows File System iDataAgent:

qcreate backupset

Description

This command creates a new backup set under the given client and agent.

The qcreate backupset command also allows the user to create default backup sets and on-demand backup sets. The default subclient created under the backup set can also be associated with a storage policy. If a storage policy name is not included, the subclient remains unassigned.

Upon successful completion, qcreate backupset displays the message "Created backupset successfully" on the command prompt. In case of an error, an error code and description are displayed as: "backupset: Error errorcode: errordescription"

Usage

Options

Configuration Backup Restore

Table of Contents


qlogin -cs <commserve name> -u <user name>

qlogin -cs server1 -u user1

Backup Set Configuration

qcreate backupset -c client -a dataagenttype -i instance -n backupset [-sp storagepolicy] [-t NORMAL|DEFAULT|ONDEMAND] [-tf tokenfile] [-tk token] [-af Argument Filepath] [-h]

-c Client computer name -a Agent type installed on client computer (see Argument Values - Agent Types)-i Instance name, required for certain agents -n Name of the backup set to be created -t Type of backup set (NORMAL, DEFAULT, or ONDEMAND)-sp Storage policy name with which default subclients are to be associated -tf Reads token from a file-tk Token string-af Reads arguments from a file -h Displays help


Argument File

Diagnostics

Possible exit status values are:

0 - Successful completion.

1 - CLI usage failures, due to the use of an unsupported option or missing argument.

2 - Any other failure.

qdelete backupset

Description

This command deletes a given backup set.

When the backup set to be deleted contains archived data, the command asks the user to confirm the deletion. This prevents the user from accidentally removing backup sets that may have archive jobs. If you want to skip the confirmation prompt, you can use the "-skc" option.

Upon successful completion, the qdelete backupset command displays the message "Deleted backupset successfully" on the command prompt. In case of an error, an error code and description are displayed as: "backupset: Error errorcode: errordescription"

Usage

Options

Argument File

Diagnostics





Example

Delete a backupset with name bs1 under client client1 and Agent MyDataAgent.

client Client computer name dataagent Agent type installed on client computer (see Argument Values - Agent Types)backupset Backup set name to be created sp Storage policy name to be associated with all subclients in the backup setbackupsettype Backup set type (NORMAL, DEFAULT, or ONDEMAND)compressionat Compression at client or MediaAgent (CLIENT|MA)networkagents Number of network agentsprebackup Prebackup command namepostbackup Postbackup command nameprescan Prescan command namepostscan Postscan command name

qdelete backupset -c client -a dataagenttype -b backupset [-skc] [-tf tokenfile] [-tk token] [-af ArgumentFilepath] [-h]

-c Client computer name -a Agent type installed on client computer (see Argument Values - Agent Types)-b Name of the backup set to be deleted -skc Skips the confirmation prompt to delete the backup set if archived data is found on the backup set.-tf Reads token from a file-tk Token string-af Reads arguments from a file -h Displays help

client Client computer name dataagent Agent type installed on client computer (see Argument Values - Agent Types)backupset Backup set name to be deleted

qdelete backupset -c client1 -a MyDataAgent -b bs1

Subclient Configuration


Creating a Subclient

1. Download the create_subclient_template.xml file and save it on the computer from where the command will be executed.

2. Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameter values.

Modifying a Subclient

1. Download the update_subclient_template.xml file and save it on the computer from where the command will be executed.


Renaming a Subclient

1. Download the update_subclient_template.xml file and save it on the computer from where the command will be executed.


Deleting a Subclient

1. Download the delete_subclient_template.xml file and save it on the computer from where the command will be executed.


Getting Subclient Properties

1. Download the get_subclient_template.xml file and save it on the computer from where the command will be executed.


Available Parameters for Subclient Configuration

The following table displays all the parameters you can use with the commands mentioned in the above sections. To add a parameter to your command, use the following syntax: (Some examples are provided at the end of the table.)

qoperation execute -af create_subclient_template.xml -appName 'File System' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -contentOperationType ADD -content/path 'xxxxx'

qoperation execute -af update_subclient_template.xml -appName 'File System' -clientName xxxxx -backupSetName xxxxx -subclientName xxxxx -contentOperationType xxxxx -content/path 'xxxxx'

qoperation execute -af update_subclient_template.xml -appName 'File System' -clientName xxxxx -backupSetName xxxxx -subclientName xxxxx -newName xxxxx

qoperation execute -af delete_subclient_template.xml -appName 'File System' -clientName xxxxx -backupSetName xxxxx -subclientName xxxxx

qoperation execute -af get_subclient_template.xml -appName 'File System' -clientName xxxxx -backupSetName xxxxx -subclientName xxxxx

qoperation execute -af <template XML file> -<parameter name> <value>

PARAMETER DESCRIPTION OF PARAMETER VALUESclientName Name of the client computer.backupsetName Name of the backup set. If the backup set name is not specified in the command query, the default backup set is used

by default.appName Name of the application. In this case it would be 'File System'.subclientname Name of the subclient.newName New name of the subclient.


enableBackup Option to enable/disable backup.

Valid values are True/False.encryptionFlag Option to set the encryption points during backups. Valid values are:

ENC_MEDIA_ONLY, to encrypt the backup data after transmission and prior to storage on the media. ENC_NETWORK_AND_MEDIA, to encrypt the backup data before transmission. The data is stored encrypted on the media. ENC_NETWORK_ONLY, to encrypt the backup data for transmission and then decrypt the data prior to storage on the media. ENC_NONE, to disable data encryption.

networkAgents Number of Network Agents.softwareCompression Option to enable compression on the Client or MediaAgent computer. Valid values are:

ON_CLIENT, to enable software compression on the client. ON_MEDIAAGENT, to enable software compression on the MediaAgent. USE_STORAGE_POLICY_SETTINGS, to use the software compression options defined on the storage policy. OFF, to disable software compression.

throttleNetworkBandwidth Enhancing backup performance by reducing network bandwidth overhead.

Valid values are 0/1.enableDeduplication Option to enable deduplication on subclient.

Valid values are True/False.generateSignature A component of deduplication performed on the client or MediaAgent computer. Valid values are:

ON_CLIENT, to enable signature generation on the client. ON_MEDIA_AGENT, to enable signature generation on the MediaAgent. OFF, to disable signature generation.

dataBackupStoragePolicy/storagePolicyName Name of the Storage Policy to be associated for backup.useGlobalFilters Option to enable the use of global filters. Valid values are:

ON, to enable global filters for the subclient. USE_CELL_LEVEL_POLICY, to enable the use of global filters if the Use Global Filters on All Subclients option is enabled on the Control Panel (Global Filters) dialog. If the option is disabled, USE_CELL_LEVEL_POLICY will disable global filters for the subclient. OFF, to disable global filters.

useVSS Option to enable/disable VSS for backing up the file system data.

Valid values are True/False.useVSSForSystemState Option to enable/disable VSS for backing up the system state.

Valid values are True/False.backupSystemState Option to enable/disable the back up of system state. This option should not be enabled in more than one subclient

per backup set to avoid system state backup failures.

Valid values are True/False.postBackupCommand Path to the post process script that will be run after the backup.postScanCommand Path to the post process script that will be run after the scan phasepreBackupCommand Path to the pre process script that will be run before the backup.preScanCommand Path to the pre process script that will be run before the scan phaserunAs Option to specify the user name who has permissions to run the pre/post process scripts. Valid values are:

USE_IMPERSONATION, to specify a user with enough privileges to run the scripts. When using this value, you also need to provide the user credentials:

USE_LOCAL_SYS_ADMIN, to use the administrator account to run the scripts.

-prepostUserName/userName <user name> -prepostUserName/password <password>

content/path Location of the content to be backed up. This parameter must be used along with the 'contentOperationType' parameter, for example:

Note the following:

If you want to specify a wildcard to the content path, you must add '\/\/" (back and forward slash) at the end of the path to enable the detection of wildcard characters:

If you are using a UNC path to specify the subclient content, you must also use the 'impersonateUser/userName' and 'impersonateUser/password' parameters to provide the credentials of a user account that has the required privileges to access the network share (where the content resides).

-contentOperationType <value> -content/path '<path value>'

-content/path 'datapath*\/\/'

content/excludepath Location of the content to be excluded from backup. This parameter must be used along with the 'contentOperationType' parameter, for example:

-contentOperationType <value> -content/excludepath '<path value>'


Examples

The following examples show how to add a parameter for a command:

Once you have completed the command line operations, you can logout from the CommServe using the following command:

For example, to log out from the CommServe 'Server1'.

content/includepath Location of the content to be included in the backup from the excluded list. This parameter must be used along with the 'contentOperationType' parameter, for example:

-contentOperationType <value> -content/includepath '<path value>'

impersonateUser/userName User name of the account that has the required privileges to access the data on a network share when specifying UNC paths for the subclient content.

impersonateUser/password Password of the account that has the required privileges to access the network share. This parameter must be used along with the 'impersonateUser/userName' parameter.

contentOperationType Modification type. Valid values are ADD, to add content to the subclient OVERWRITE, to overwrite contents to the subclient. DELETE, to delete the contents from the subclient.

Adding Content To update the location for the subclient content, add the 'path' parameter to the following command:

qoperation execute -af update_subclient_template.xml -appName 'File System' -clientName client1 -backupSetName backupset1 -subclientName subclient1 -contentOperationType ADD -content/path 'c:\temp'

Setting a Storage Policy To assign a storage policy to a subclient, add the 'storagePolicyName' parameter to the following command:

qoperation execute -af update_subclient_template.xml -appName 'File System' -clientName client1 -backupSetName backupset1 -subclientName subclient1 -dataBackupStoragePolicy/storagePolicyName sp1

Log Off from the CommServe

qlogout -cs commserve

qlogout -cs Server1



Perform the Backup

Generate the Command Line Script from the CommCell Console

In order to run the backups from command line, you need an input xml file which contains the parameter values for configuring the backup options. This input xml file can be obtained from one of the following ways:

Download the input xml file template and save it on the computer from where the backup will be performed.

Generate the input xml file from the CommCell Console and save it on the computer from where the backup will be performed.

Use the following steps to perform the backup:

1. Download the backup_template.xml file and save it on the computer from where the command will be executed.

2. From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:

3. Execute the saved .xml script using qoperation execute command.

4. Verify the status of the job using the following command:

5. Once the job completes, logout from the CommServe using the qlogout command.

Examples

In addition to the parameter values provided in the template xml file, if you want to include additional options for the backup, you can do so by selecting the required options from the CommCell Console and generate the command line xml script for the backup.


Table of Contents

Perform the Backup


qoperation execute -af backup_template.xml -appName 'File System' -clientName xxxxx -backupsetName xxxxx -subclientName xxxxx -backupLevel FULL

qlist job –j JOBID

qlogout [-cs commserver] [-all] [-tf tokenfile] [-tk token] [-h]

Performing a Full Backupqoperation execute -af backup_template.xml -appName 'File System' -clientName client1 -backupsetName backupset1 -subclientName subclient1 -backupLevel FULL

Performing an Incremental Backup qoperation execute -af backup_template.xml -

appName 'File System' -clientName client1 -backupsetName backupset1 -subclientName subclient1 -backupLevel INCREMENTAL

Performing a Synthetic Full Backup

When you run a Synthetic Full backup, an incremental backup is automatically ran first to ensure that new data since the last backup is included in the synthetic full.

qoperation execute -af backup_template.xml -appName 'File System' -clientName client1 -backupsetName backupset1 -subclientName subclient1 -backupLevel SYNTHETIC_FULL



Follow the steps given below to generate a script which you can use to perform a backup from the command line interface:



3. Select the required backup options which you want to execute using the script.

4. Click Save as Script.

5. Enter the location to save the script along with the file name and extension. For example, "C:\scripts\myscript.bat" on Windows and "/usr/scripts/myscript.sh" on Unix. Alternatively, you can also click Browse and navigate to the location.

The script will be saved as a .xml file and .bat/.sh file.

If a file with the same name already exists in the specified location, both the .xml and .bat/.sh files will be overwritten.

6. Enter the username and password for the user account which you want to use to perform the backup.

By default, the user account which you have used to login to CommCell console is used for performing the backup. However, if the user account does not have access to any application or database, click Use a different account.

7. Click OK.




Browse and Restore DataBrowsing DataSupported Parameters and possible values Browsing Data Using FiltersBrowsing Data Using OperatorsBrowsing Data Using FunctionsBrowsing Multiple Versions of a FileSupported Parameters and possible Values for Filters, Operators and Functions

Perform the Restore


Find Data

To run command line operations, you must first login to the CommServe.

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:

For example, to log on to CommServe 'server1' with username 'user1':

You can now perform Browse operations using Command Line interface. It takes input from an XML file and enters the output in another XML file.

Browsing Data

Below is an example of Browsing data between a specific time range using a command line XML.

1. Download the input_template.xml file and save it on the computer from where the command will be executed.

Modify the xml template as per your setup.

You may use the image below to understand what parameters the xml file uses and what can be the possible values.

2. Execute the following command from the /Base folder after substituting the parameters values in the input file.


Table of Contents



qlogin -cs server1 -u user1

Browse and Restore Data


Make sure to provide the name and path of the output xml file in which you want to retrieve your browse results.

3. Verify the results in the output_template.xml.

Supported Parameters and possible Values

The above input XML file provide displays browsing data between a specified time.

The following table displays the various command line parameters, their values and options that are used in the above XML query:

Browsing Data Using Filters

Below is an example of browsing data using filters like file name and file type using a command line XML.

1. Download the input_filter.xml file and save it on the computer from where the command will be executed.


You may use the image below to understand what parameters the xml file uses and what can be the possible values. The image below displays the mandatory parameters only, however the attached xml file has more options specified



qlist backupfiles -af input_template.xml -dpath output_template.xml

PARAMETER VALUES DESCRIPTION

opTypeThe following values can be used to define the given parameter. For the above example Browse has been selected.

Browse Find Versions IndexPrediction

This parameter is used to define the type of operation that you would perform during the XML request.

Entity The following values need to be defined for this parameter:

appName="Windows File System" backupsetName="backupset1" clientName="client1" subclientName="subclient1"

appName: This the type of Agent on which the Browse operation is performed and the value can be obtained form APP_iDAtype table.

backupsetName: Name of the backupset on which the browse operation will be performed. If no name is specified, defaultBackupSet s used.

clientName: Name of the client to which the backupset belongs.

subclientName: Subclient that was backed up. The browse operation will yield results on this subclient.

pathsThe path to the actual folder level on which the browse operation will be performed.

For example:

<paths path="E:\"/>

You must provide the exact path to the folder which contains the backed up files.

timeRangeThe following values can be used to define the given parameter:

Latest Point in time TimeRange

The above example uses TimeRange. The Time range can be specified in the below formats:

<timeRange fromTime="Dec 21, 2010" toTime="Dec 31, 2010"/>

<timeRange fromTime="2012-06-09 10:00:00" toTime=": 2012/10/02 14:06:29 "/>


3. Verify the results in the output_filter.xml.

Browsing Data Using Operators

Below is an example of browsing data using operators like file size greater than certain value, using a command line XML.

1. Download the input_operator.xml file and save it on the computer from where the command will be executed.



The image below displays the mandatory parameters only, however the attached xml file has more options specified



3. Verify the results in the output_operator.xml.

Browsing Data Using Functions

Below is an example of browsing data using functions like aggregate using a command line XML.

1. Download the input_function.xml file and save it on the computer from where the command will be executed.



The image below displays the mandatory parameters only, however the attached xml file has more options specified



qlist backupfiles -af input_filter.xml -dpath output_template.xml

qlist backupfiles -af input_operator.xml -dpath output_template.xml



Browsing Multiple Versions of a File

You can use command line to view a particular backed up file version for restores. If a time range browse is performed, versions are shown across cycles.

1. Download the input_version.xml file and save it on the computer from where the command will be executed.



The image below displays the mandatory parameters only, however the attached xml file has more options specified.




Supported Parameters and possible Values for Filters, Operators and Functions

The above XML files helps in browsing data using specific filters, functions and operators.

The following table displays the various command line parameters, their values and options that are used in the above XML queries:

qlist backupfiles -af input_function.xml -dpath output_template.xml

Make sure to use correct value for the mode tag in your input xml.

If an incorrect or empty value is passed, you may not get browse results. However, you may skip passing this parameter altogether.

qlist backupfiles -af input_version.xml -dpath output_template.xml

PARAMETER VALUES DESCRIPTION

queryIdThe following values can be used to define the given parameter:

QueryType

This has a string value that is used to identify each query. The response for each query also has the same id.

Each query type can have one of the following values:

Data

Response is returned as a list of browseData structures. A string value as dataParam can be passed.

Aggregate

This is used to compute aggregate data on a desired result set . aggrTypecan be set to one of the following values

MAX MIN AVG SUM COUNT

TopBottom

For TopBottomParam, the count is number of items. topBottomParam topBottomParam can have one of the following values:

FilteretedBrowseField count Ascending

aggregateParam aggregateParam can have one of the following values: aggregateParam

This is used to compute aggregate data on a desired result set . aggrTypecan be set to one of the following values

MAX MIN AVG SUM COUNT


In order to run the restores from command line, you need an input xml file which contains the parameter values for configuring the restore options. This input xml file can be obtained using one of the following ways:

Download the input xml file template and save it on the computer from where the restore will be performed.

Generate the input xml file from the CommCell Console and save it on the computer from where the restore will be performed.

Use the following steps to perform the restore:

1. Download the restore_template.xml file and save it on the computer from where the command will be executed.

2. From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:

3. Execute the saved xml script using qoperation execute command.

4. Verify the status of the job using the following command:

5. Once the job completes, logout from the CommServe using the qlogout command.

Examples

FilteretedBrowseField FilteretedBrowseField Group By

dataParam dataParam can have one of the following values: fileFilteretedBrowseField browsePpging can further have the following values:

firstnode SkipNode Pagesize

OptionsAll options mentioned below are set to “false” by default. The behavior changes when they are set to “true”.

The description column describes the behavior when the value is set to "true".showDeletedFiles This parameter displays the deleted files along with existing files in the browse

results.restoreIndex This parameter restores the index automatically, if it is not available in cache.caseInsensitive This parameter enforces a case insensitive search for case-sensitive platforms.skipIndexRestore This parameter ensures not to restore the index and displays partial or no resultsincludeMetadata This parameter enables inclusion of troubleshooting folders in the browse results.

Troubleshooting folders include collect files or job specific metadata files of a file system.

whereClause A query can have multiple where clauses . For example:

<whereClause> <criteria dataOperator="IN" field="ModifiedDate"> <values val="thisMonth"/> </criteria> </whereClause>

Perform the Restore


qoperation execute -af restore_template.xml -appName 'File System' -clientName xxxxx -backupsetName xxxxx -destPath 'xxxxx' -sourceItem 'xxxxx'

qlist job –j JOBID

qlogout [-cs commserver] [-all] [-tf tokenfile] [-tk token] [-h]

Restoring from a Current Backupqoperation execute -af restore_template.xml -appName 'File System' -clientName client1 -backupsetName backupset1 -destPath 'C:\temp' -sourceItem 'C:\test'

Restoring Files to a Point in Time (date) qoperation execute -af restore_template.xml -

appName 'File System' -clientName client1 -backupsetName backupset1 -destPath 'C:\temp' -sourceItem 'C:\test' -toTimeValue 2011-11-28

Restoring Files to a Point in Time


In addition to the parameter values provided in the template xml file, if you want to include additional options for the restore, you can do so by selecting the required options from the CommCell Console and generate the command line xml script for the restore operation.

Follow the steps given below to generate a script which you can use to perform a restore from the command line interface:


2. Right-click the <Backup Set> and click All Tasks | Browse and Restore.


4. In the right pane of the Browse window, select the data that you want to restore and click Recover All Selected.

5. Select the required restore options which you want to execute using the script.

6. Click Save as Script.

7. Enter the location to save the script along with the file name and extension. For example, "C:\scripts\myscript.bat" on Windows and "/usr/scripts/myscript.sh" on

(date and time)qoperation execute -af restore_template.xml -appName 'File System' -clientName client1 -backupsetName backupset1 -destPath 'C:\temp' -sourceItem 'C:\test' -toTimeValue 2011-11-28 15:40:00

Restoring by Jobs

where: jobids is the backup job ID sourceItem is the CommCell D and the backup job ID separated by a colon (':'). By default, the CommCell ID is 2. striplevel is the number of folder levels to exclude from the source path. This parameter is optional.

For example, if you have a directory structure (source path) as /a/b/c and you select strip level 2, the data will be restored from folder c, while folders a and b are excluded. Ensure that the strip level is always less than the source path level.

qoperation execute -af restore_by_job_template.xml -jobids 52 -sourceItem 2:52 -striplevel 1

Step-by-step restores should be performed from the CommCell Console.

Generate the Command Line script from the CommCell Console


Unix. Alternatively, you can also click Browse and navigate to the location.

The script will be saved as a .xml file and .bat/.sh file.

If a file with the same name already exists in the specified location, both the .xml and .bat/.sh files will be overwritten.

8. Enter the username and password for the user account which you want to use to perform the restore.

By default, the user account which you have used to login to CommCell console is used for performing the restore. However, if the user account does not have access to application and database, click Use a different account.

9. Click OK.

The following command is available for finding backed up data.

qoperation find

Description

This command performs a wildcard search for a specific file in the backed up content. This command also allows you to search data from multiple indexing cycles. For example, consider a scenario where a user has backed up the following:

*.txt files in the first cycle

*.pdf files in the second cycle

*.doc files in the third cycle

Even when the backup cycle is in a time frame beyond the third cycle, you can search the backed up data from all the three cycles without any additional input parameters.

Usage

Options

Argument File

Find Data

qoperation find -af argsfile [-rf resultfile][-tf tokenfile] [-tk token] [-h]

-af Reads arguments from an input file-rf Saves results to a file-tf Reads token from a file-tk Token string-h Displays help

server CommServe host name


Diagnostics





Example

Use the following steps to perform a wild card search operation on backed up content using find command:

1. Create an input parameter file with the required arguments and values.

For example, see the sample input parameter sample.ini on the right.

2. Run the qoperation from the command prompt.

user User name (prompted if not specified)password Password (prompted if not specified)sourceclient Name of the client computer on which you want to perform search operation.dataagent Agent type installed on source client computer (see Argument Values - Agent Types)backupset Backup set namesourcepaths File/Directory to be restored (using wildcard characters)options Restore options (see Argument Values - Restore Options)browsefrom Start date/time to be considered for search operation. Format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss].browseto End data/time to be considered for search operation. Format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss]

[sourceclient]silver

[dataagent]Q_FILESYSTEM

[backupset]defaultBackupSet

[sourcepaths]C:\*.xml

[browsefrom]2011/8/22 00:25:00

[browseto]2011/8/22 06:28:00

[options]QR_BROWSEQR_NORECURSEQR_NOIMAGEQR_WILDCARD

C:\Data Protection Suite\Base>qoperation find -af "SAMPLEFILE.INI" -rf C:\out_find03.txt1: Wed Aug 10 10:44:47 2011 1312987487 Unknown 237 \C:\1.xml


1-Touch for Windows

1-Touch recovery feature enables quick recovery of a computer by restoring the operating system and the file system. You don't need to reinstall the operating system and individual software packages manually. To perform 1-Touch recovery , you need to setup the following entities:

1. 1-Touch Server

2. 1-Touch Client

The 1-Touch server is required to create the Live CD. The Live CD will be used to boot the client and initiate the 1-Touch recovery of the client.

Perform the following steps to setup a 1-Touch Server:

1. Install 1-Touch Server Software

2. Configure a Remote Cache for 1-Touch Server

3. Download and Install Updates on 1-Touch Server

4. Apply updates in 1-Touch Server Cache to 1-Touch Live CD Boot image

Install 1-Touch Server Software

Install the 1-Touch server software on any Windows computer.


Before you Begin

System Requirements




Perform the following steps to install 1-Touch server software:


2. Run SetupAll.exe from the Disc 2.


Click Next.

4. Click Custom.

Click Next.

Deployment Configuration Recovery FAQ Troubleshooting Options

1-Touch Server



6. Expand File System, and then click 1-Touch Recovery.

Click Next.


Click Next.






8. Click Install.

9. Click Yes.

10. Click Next.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.








Click Next.







Click Next.





Click Next.




17. Click Next.

18. Verify the default location for Distribution Folders.

Click Next.






19. Click Finish.

Configure a Remote Cache for 1-Touch Server

When the 1-Touch Server software is not installed on a CommServe, you must configure a remote cache for the 1-Touch server. A remote cache will store all the updates for 1-Touch Server software, Windows File System iDataAgent and WinPE.

1. From the CommCell Console, right click the CommServe computer and click All Tasks | Add/Remove Software | Add/Remove Software Configuration.

2. Select Remote Software Cache tab.

Click Add.


You can skip this configuration if 1-Touch server is installed on the CommServe.


3. Select the client Computer.

Click Enable Remote Software Cache.

Enter the path to Cache Directory.

Click OK.

Download and Install Updates on 1-Touch Server

Before creating the 1-Touch Live CD, download all the software updates for 1-Touch Server software, Windows File System iDataAgent and WinPE.

1. From the CommCell Browser, right-click on the CommServe computer node, and click All Tasks -> Add/Remove Software -> Download Software.


2. Click OK.

3. Click Job Initiation tab.

By default Immediate option is selected.

Click OK.

4. You can track the progress of the job from the Job Controller window. The software updates are stored automatically in the CommServe Cache and 1-Touch Server cache.


5. From the CommCell Browser, right-click on the CommServe computer node, and click All Tasks -> Add/Remove Software ->Install Updates



Click OK.

7. From the CommCell Browser, right-click on the 1-Touch Server computer node, and click All Tasks -> Add/Remove Software -> Install Updates




Click OK.

Apply updates in 1-Touch Server Cache to 1-Touch Live CD Boot image

Follow the steps given below to mount the 1-Touch Live CD and apply the software updates to the ISO:

1. From the CommCell Console, navigate to <Client Computers> | < 1-Touch Server>.

Right-click and click All Tasks | Add/Remove Software | Copy Software.

2. Select Mount and Apply updates in 1-Touch Cache to 1-Touch Live DVD Boot images.

Click OK.

All the software updates are copied to 1-Touch server cache and then integrated with 1-Touch ISO for each type of processor.


Any client computer for which you want to perform 1-Touch restore, must have Windows File System iDataAgent installed on it.

Where to Install

Install the software on a Windows computer that you want to backup.


Before You Begin

System Requirements




Installation




Click Next.

4. Click Custom.

1-Touch Client


Click Next.


6. Expand File System, and then click File System.

Click Next.


Click Next.






8. Click Install.

9. Click Yes.

10. Click Next.







You cannot perform 1-Touch restore and VirtualizeMe operations if you configure firewall between CommServe and the client computer.



\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.








Click Next.







Click Next.





Click Next.





Click Next.

18. Click Finish.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 19.




















Click OK.




















20. If you have installed on a clustered computer, make sure to install the software on all the physical nodes and then follow the steps described in Cluster Configuration.


Configuration - 1-Touch for Windows

The windows system state backup includes all the information required for 1-Touch recovery. Follow the steps given below to perform the system state backup of a 1-Touch client:

1. From the CommCell Console, navigate to <1-Touch Client> | File System iDataAgent | defaultBackupSet.

Right-click a <subclient>, and click Properties.


Select the Backup System State check box.

Ensure that the entire C drive is included in the content of the subclient.

Click OK.


In the Storage Policy box, select a Storage Policy name.

Click OK.


If you are performing backup of a Windows 7 client, ensure that the Administrator account is enabled. You cannot perform the 1-Touch recovery of the client if administrator account is not enabled while performing the backup.


4. From the CommCell Console, navigate to <Client> | File System iDataAgent | defaultBackupSet.

Right-click the subclient which you have configured for the system state backup, and click Backup.

5. Select Full.

Select Immediate.

Click OK.

6. You can track the progress of the backup job from the Job Controller window. When the backup job has completed, the Job Controller displays the status as Completed.


Recovery - 1-Touch for Windows

Prepare for RecoveryCreate a Live CDAdd Drivers to Windows Driver ManagerAdd Mass Storage Drivers to Live CDAdd NIC Drivers to Live CDRemove Drivers from WinPE Driver Manager

1-Touch RecoveryNon Interactive RestoreInteractive RestoreCustomizing Disks During 1-Touch Recovery (Dissimilar System Restore)Adding Drivers During 1-Touch Recovery (Cross Hardware Restore)

Restoring a MediaAgentNon-interactive RestoreInteractive Restore

Cloning a Client ComputerNon-interactive RestoreInteractive Restore

Restoring from a Point-in-TimeNon-Interactive RestoreInteractive Restore

Restoring from a User Defined BackupsetNon-Interactive RestoreInteractive Restore

Modifying the Network Configuration of a ClientNon-Interactive RestoreInteractive RestoreConfiguring WINS and DNS During an Interactive Restore

Selecting Volumes on a ClientNon-Interactive RestoreInteractive Restore

Using an End-User Account for 1-Touch RecoveryNon-Interactive RestoreInteractive Restore

Additional OptionsCreating a Response FileAccessing the Response File From an UNC Path During an Offline Non-Interactive RestoreUsing an USB Drive Instead of a Live CDRestoring the Teaming Network Adapters

Cluster Recovery

A Live CD will be required to boot a client and initiate the 1-Touch recovery of the client.

Create a Live CD

You can create a Live CD image using 1-Touch Wizard on 1-Touch server. Before creating a Live CD image, consider the following prerequisites:

All the software updates for 1-Touch Server software, Windows File System iDataAgent and WinPE are downloaded to remote cache on 1-Touch server and applied to 1-Touch Live CD. For more information refer to Download and Install Updates on 1-Touch Server.

Client computers may have different types of operating systems and processors. You must create a Live CD for each type of processor.

Follow the steps given below to create a Live CD:

1. Login to 1-Touch Server.

2. Click Start | Programs |HDPS | Data Protection Suite | 1-Touch.

3. Click 1-Touch Boot CD Wizard.


Table of Contents

Prepare for Recovery


4. Click Next.

5. Select the processor type from the list. The processor type must match with the processor of the computer where you are restoring the client.


6. Click Next.

By default the the Mass Storage drivers from WinPE package for Windows 7 are automatically added to the Live CD.

If the target computer has any drivers which are not included in the WinPE package for Windows 7, click Add to manually add the drivers to the Live CD.

Click Select All to select all the drivers in the list.

For more information about how to add driver, refer to Add Mass Storage Drivers to Live CD.

The list of all the added drivers appears in the 1-Touch Boot CD Wizard. You can select multiple drivers from the list.

7. Click Next.

By default the the NIC drivers from WinPE package for Windows 7 are automatically added to the Live CD.

If the target computer has any drivers which are not included in the WinPE package for Windows 7, click Add to manually add the drivers to the Live CD.

Click Select All to add all the drivers listed to the Live CD.

For more information about how to add driver, refer to Add NIC Drivers to Live CD.


The list of all the added drivers appears in the 1-Touch Boot CD Wizard. You can select multiple drivers from the list.

8. Click ... to browse and select the location where you want to save the 1-Touch_<processor type>.iso file.

Do not select the Skip mounting image check box if you have manually added any drivers to the Live CD.

Click Done.

The 1-Touch_<processor type>.iso will be stored at the selected location. You can use this ISO image to create a Live CD.

Add Drivers to Windows Driver Manager

The Windows Driver Manager wizard, available on 1-Touch server, enables you to add drivers before creating the Live CD. Use the Windows Driver Managerwhen you want to add multiple drivers and select the required drivers while creating the Live CD. Follow the steps give below to add mass storage drivers:



3. Click Windows Driver Manager.


4. Select the Drivers listed.

5. Select the OS Architecture.

You can add drivers for Windows 7 OS.

6. Click Add.

7. In the Location box, click ... and browse and open the driver files (.oem, or .inf files).

The name of the driver appears in the Folder box.


8. The path of the driver appears in the Location box.

9. Click Add.

10. Click Done on the Driver Manager dialog box.

The added drivers will appear in the list of Mass Storage Drivers when you start the 1-Touch Boot CD wizard.

You can select the required drivers while creating the Live CD.

Add Mass Storage Drivers to Live CD

WinPE 3.0 is based on the kernel for Windows 7. For some hardware, the Mass Storage Drivers in WinPE are included on the Live CD. If the target computer requires any drivers that are not included on the Live CD, you can manually add the drivers to the Live CD. The manually-added drivers must be compatible with Windows 7.

Follow the steps given below to add mass storage drivers:





4. Click Next.



6. Click Next.

7. Select the Driver listed.

Click Add to add another driver.

8. In the Location box, click ... and browse and open the driver files (.oem, or .inf files).


The path of the driver appears in the Location box.


9. Click Add.

The added driver will appear in the list of Mass Storage Drivers on the 1-Touch Boot CD dialog box.

Select the check box for the driver .

10. Click Next.

11. Click Next.


Do not select the Skip mounting image check box.

Click Done.

Add NIC Drivers to Live CD

By default the the NIC Drivers from WinPE package for Windows 7 are automatically added to the Live CD. If the target computer has any drivers which are not included in the WinPE package for Windows 7, you can manually add the drivers to the Live CD. Follow the steps given below to add mass storage drivers:





4. Click Next.


Click Next.


6. Select the Drivers listed.

Click Next.

7. Click Add.

In the Location box, click ... and browse and open the driver files (.oem, or .inf files).


The path of the driver appears in the Location box.


8. Click Add.

The added driver will appear in the list of NIC Drivers on the 1-Touch Boot CD dialog box.

Select the check box for the driver.

9. Click Next.


Do not select the Skip mounting image check box.


11. Click Done.

Remove Drivers from WinPE Driver Manager

You can remove drivers that have been added to the WinPE using the following steps.



3. Click WinPE Driver Manager.

4. Select the list of drivers that need to be removed.

Click Remove.


Once you have a boot CD ready, you can initiate the 1-Touch recovery of a client. You can perform following types of restores:

Non-Interactive Restore - Perform this restore when you don't want to manually specify the client information during the restore. The information will be available in a response file.

Interactive Restore - Perform this restore when you want to monitor the restore or want to alter any client configuration during the restore. You have to manually enter the client information.

Non-Interactive Restore

Follow the steps given below to restore the client computer when the target computer has the same hardware and disk configuration as that of the backed up computer:

1. Create 1-Touch Live CD. For more information, refer to Create a Live CD.

2. From the CommCell Console, navigate to <Client>

Right-click the <Client> and click All Tasks | 1-Touch Recovery Point

3. By default the response file will be created using the client configuration backed up by default backupset in the most recent backup.

1-Touch Recovery


Click Next.

4. Click each of the following tabs to review the client configuration:

General tab

Configuration tab

Disk Configuration tab

Restore Options tab

Advanced tab

Click Finish.

5. By default, the response file will be saved on the computer where you are running the CommCell console.

Click Save to save the response file at its default location.

If you want to save the response file on any other location on the computer or in the domain, specify the location and then click Save.


6. Copy the response file to a USB drive or a removable disk or a network location.

7. Connect the USB drive or the removable disk to the client that you want recover.

If you want to use a network location to access the response file during the restore, follow the steps given in Accessing the Response File From an UNC Path During a Non-Interactive Restore.

8. Use the 1-Touch Live CD to boot the client.

9. Select the language from the list

Click OK.

10. Click OK to start the full system restore.

11. Click OK.

Remove the Live CD and restart the computer.


Interactive Restore

Follow the steps given below to restore the client computer when the target computer has the same hardware and disk configuration as that of the backed up computer:


Use the 1-Touch Live CD to boot the client.

2. Select the language from the list.

Click OK.

3. Click Cancel to start the interactive restore.


4. Click Next.

5. Click Yes if all disk devices are detected.


6. Enter the CommServe Host Name and IP Address.

Enter the CommCell User Name and Password.

Select the Network Connection from the Connection drop-down combo box.

Click Get Clients to get the list of all file system clients on which the system state backups have been performed.

In the Client Name list , select a client for which you want to perform the Interactive Restore.

Click Next.

7. Click Next.


8. By default, the client configuration, backed up by default backupset in the most recent backup, will be used to restore the client.

Click Next.

9. Review the Restore Options and click Next.


10. Click Next.

11. Click Next.

If you want to exclude any folder or driver from the full system restore, enter the path of the folder or driver and click Add.


12. Review Client Internet Protocol (TCP/IP) Properties and Click OK.

The Full System Restore starts.

13. Click OK.

Remove the Live CD and restart the computer.


Customizing Disks During 1-Touch Recovery (Dissimilar System Restore)

When the target computer has the disk layout different than the disk layout of backed up computer, then you have to customize the disk layout of target computer during 1-Touch recovery. Follow the steps given below to map disks and customize the disk partitions during the Interactive or Non-interactive restore:

1. During the Interactive or Non-interactive restore, when the disk layout on the target computer is different than the disk layout of backed up computer, the Customize the Disks dialog box appears by default. It displays the Source Disk Layout and Destination Disk Layout.

The Source Disk Layout is the disk layout of the client computer at the time of the backup

The Destination Disk Layout is the disk layout of the target computer.

Before creating disk partitions on the destination disk, you must initialize the disk. Right-click any disk in the Destination Disk Layout and select one of the following options:

Initialize as MBR Basic Disk

Initialize as MBR Dynamic Disk

Initialize as GPT Basic Disk

Initialize as GPT Dynamic Disk

2. Click Yes.


3. Repeat steps 1 and 2 for the required disks in the Destination Disk Layout. Once all the required disks are initialized, you can map the volumes from the source disk to the destination disks.

4. Right-click a volume in the Source Disk Layout and select Map.

5. In the Customize the Volumes dialog box, select a disk from the Available Disk List. The volume selected in step 3 will be created on the selected disk.

Click OK.

6. Repeat steps 4 and 5 for all the volumes from the Source Disk Layout, which you want to create in the Target computer.

Once all the required volumes are mapped, click OK on the Map the Disks dialog box. The Full System Restore starts.

Adding Drivers During 1-Touch Recovery (Cross Hardware Restore)


If the target computer does not have any drivers, which are required by the client, you must provide the location those drivers during 1-Touch recovery. Follow the steps given below to provide the required drivers during an interactive restore or a non-interactive restore:

1. Copy all the required Mass Storage Drivers and NIC Drivers to a network location. For example: If the target system requires Adaptec Ultra160 mass storage driver, then copy the driver.inf for Adaptec Ultra160 to a network location.

2. Note down the license key for the operating system installed on the client.

3. During the Full System Restore, specify the UNC path where you have copied the drivers.

4. Enter the password required to access the network location.

5. Select file(s) required to install the drivers.

Click Open.

6. Click OK.

7. Click OK.

The full system restore starts.


It is recommended that you install the latest hardware drivers after the restore completes.

If you are restoring a Windows 2003 client, the Windows Mini-Setup runs automatically after the full system restore. At the end of the Windows Mini-Setup, enter the valid license key for the restored Windows Operating System.

When a computer where you have installed the MediaAgent becomes unavailable, all the storage resources configured for the MediaAgent become unavailable and you may have to reconfigure all the storages policies which are using the MediaAgent. Now you can avoid such scenario by performing 1-Touch recovery of the MediaAgent if the MediaAgent backup is available on the PnP disk library or library in a Network location.

The magnetic library, located on any volume of the MediaAgent, will not be restored automatically.

Prerequisites

Ensure that the Windows File System iDataAgent is installed on the MediaAgent.

Ensure that the PnP disk library or library in a Network location is used to perform the backup of the MediaAgent and the backup is not stored on a disk library. For more information on how to configure a PnP library, refer to PnP (Plug and Play) Disk Libraries.

Perform the full backup of MediaAgent using the Windows File System iDataAgent. Ensure that at least one subclient is configured to backup the system state. For more information, refer to Configuration.

Depending upon the type of processor of the computer, create the required Live CD to boot the MediaAgent. For more information, refer to Create a Live CD.

You can perform one of the following 1-Touch recovery to restore the MediaAgent.


1. From the CommCell Console, navigate to Client Computers | <MediaAgent>.

2. Right-click the <MediaAgent> and click All Tasks | 1-Touch Recovery Points.

3. Click Next.

4. Click the Advanced tab.

5. Select the Client is a MediaAgent check box.

6. Specify the location where you want restore the index. By default, the index will be restored to a USB drive. If you want to restore the index to a Network location, click Network Share and specify the following details:

User Name - User name for the user account which will be used to access the network location.

Password - Enter the password for the user account.

Index cache path - Enter the location where you want to restore the index. Click to specify the location.

If you are restoring from a secondary copy, ensure that the secondary copy is available on the same MediaAgent where primary copy is available. For more information about how to recover the MediaAgent from the secondary copy, refer to this FAQ.

7. Click Finish.

8. Save the recovery response file as onetouchresponse.xml.

9. Connect the formatted USB drive to the computer where recovery response file is stored.

10. Copy the recovery response file to the formatted drive.

Do not copy the response file on the same USB drive which is used for the PnP library attached to the MediaAgent. During the 1-Touch recovery, the the USB drive is scanned to locate the onetouchresponse.xml. The scanning process will take long time if the size of the disk is huge. Use a USB drive (USB stick) with a smaller size to copy the response file. Alternatively, you can use a use a network location to copy the response file.

11. Connect the USB drive to the client that you want recover.

12. Perform the Non-interactive restore.

Restoring a MediaAgent


Interactive Restore


2. Select the language from the list and Click OK.

3. Click Next.


5. Enter CommServe Host Name.

6. Enter CommServe IP address.

7. Enter the CommCell User Name.

8. Enter the CommCell Password.

9. Select the Network Connection from the Connection drop-down combo box.

10. Click Get Clients.

11. Select the client host name from the Client Name list.

12. Select the Client is a MediaAgent check box.

13. Specify the location where you want restore the index. By default, the index will be restored to a USB drive. If you want to restore the index to a Network location, click Network Share and specify the following details:

Index Cache Directory - Enter the location where you want to restore the index.

User Name - User name for the user account which will be used to access the network location.

Password - Enter the password for the user account.

14. Click Next.

15. Review network information for CommServe and restored client.

16. Click Next.

17. Enter CommCell User Name.

18. Enter CommCell Password. Enter the credentials that are used to login to CommCell from the client.

19. Click Next.

20. Complete the steps to start the 1-Touch recovery.


Cloning is the process of creating a replica of a client computer from its backup. You can create a clone of a client computer during 1-Touch restore.

This feature allows the user to seamlessly set up a cloned computer with a different hostname/ IP configuration while the source computer is still up and running. This comes handy when setting up a standby server during disaster recovery testing.

If protection for the cloned machine is required, backup schedule(s) need to be set up. The settings on the source client such as the subclient and backupset options, schedules, storage policies etc. will not be preserved on the cloned client. If required, additional iDataAgent can be installed and configured from the CommCell Console.

Prerequisites

Before creating a clone of the client computer, ensure that the client computer has only one instance of Windows File System iDataAgent installed on it.


Follow the steps given below to create a clone of a client computer:


2. Right-click the <Client> and click All Tasks | 1-Touch Recovery Point.

3. Click Next.

4. Click the Advanced tab.

5. Select the Clone Machine check box.

6. Type the client name for the clone in the New Client Name box.

The Client Name is the name of the client which will be created for the clone computer in the CommServe. Ensure that the client name is not used by any other client in the CommServe.

7. Type the name of the clone computer in the New Hostname box. Do not enter the fully qualified domain name or the IP address of the computer.

8. Click Finish and save the response file.

9. Perform the Non-interactive 1-Touch restore on a computer different than the client computer.

Cloning a Client Computer


Interactive Restore

Follow the steps give below to create a clone of the client copmputer:



3. Click Next.






9. Click Next.


11. Click Next.



14. Click Next.

15. Click the Clone Machine check box and enter the New Client Name and New Hostname for the clone computer.

The Client Name is the name of the client which will be created for the clone computer in the CommServe. Ensure that the client name is not used by any other client in the CommServe.

16. Complete the steps to start the 1-Touch recovery.


By default, the latest data and configuration of the client computer, backed by the default backup set, will be used to restore the client computer. However, you can restore the client using the data and client configuration backed up at any point-in-time.


Use the following steps to create a response file using a point in time backup:

1. From the CommCell Console, navigate to <Client>.

2. Right-click the <Client> and click All Tasks | 1-Touch Recovery Points.

3. Click Select Point in Time.

4. Select a date and time to specify the point-in time. All the data backed up before the specified point in time will be used to create the response file.

The default time zone of the CommServe is used to determine the point in time. If you want to restore data backed up in a different time zone, select the required Time Zone.

5. Click Next.

6. Click Finish.




Restoring from Point-in-Time

Review all the hardware configuration options selected under different tabs of the Review Recovery Optionsdialog before clicking Next.


10. Perform the Non-Interactive restore.

Interactive Restore



3. Select the language from the list and click OK.

4. Click Cancel to start the interactive restore

5. Click Next.





Click Next.

8. Click Next.


Select the Restore from the backup before option and specify the date and time.

Click Next.


10. Perform the Interactive Restore.

Restoring from a User Defined BackupSet

By default, the data and configuration of the client computer, backed up by default backupset is used to restore the client computer. You can create a backupset to backup data and configuration for the 1-Touch recovery. You can create a backupset to backup data and configuration for the 1-Touch recovery. This will be useful when you want to backup only selected data on the client computer and restore it during 1-Touch recovery.


Use the following steps to create a response file using the data backed up by a user defined backupset:

1. From the CommCell Console, navigate to <Client>.

2. Right-click the <Client> and click All Tasks | 1-Touch Recovery Points.

3. Select a non-default backupset from the Backup Set list.

4. Click Next.

5. Click Finish.




Interactive Restore

Follow the steps given below to restore the client configuration and data backed by a user defined backupset:





5. Click Next.





Click Next.

8. Click Next.


Review all the hardware configuration options selected under different tabs of the Review Recovery Optionsdialog before clicking Next.


Select a user defined backupset from the BackupSet list..

Click Next.


Before restoring the client, you can change the network configuration of the client such as IP address, default gateway etc.


You can change the network configuration before creating a response file and then use the modified response file for a non-interactive restore. Follow the steps given below to change the network configuration of a client:



3. Click Next.

4. Click Configuration tab. It displays a list of current network configurations of the client.

5. Select a network configuration which you want to modify and click Edit.

6. Modify the IP address or any other network configuration details.

Click Use DHCP if you want to use DHCP instead of static IP address.

7. If you want to use DNS, click Add and enter the IP address of the DNS Server.

If you want to use WINS, click Add and enter IP address of the WINS Server.

When the client computer and CommServe are in the same domain, DNS will be used for name resolution between client computer and CommServe.

WINS will be used for name resolution in the following scenarios:

CommServe and Client computer are in different networks.

CommServe is registered in a workgroup

8. Click OK.


10. Perform the non-interactive restore using the response file. The client will be restored with modified network configuration.

Modifying the Network Configuration of a Client


Interactive Restore

You can change the network configuration during the Interactive Restore as follows:





5. Click Next.





Click Next.

8. Click Next.


Enter the CommCell console credentials and Click Next.

10. Review the Restore Options and click Next.

11. Modify the IP address or any other network configuration details.

Click Use DHCP if you want to use DHCP instead of static IP address.

12. Perform the Interactive Restore. The client will be restored with modified network configuration.


Configuring WINS and DNS during an Interactive Restore

When the client computer and CommServe are in the same domain, DNS will be used for name resolution between client computer and CommServe.

WINS will be used for name resolution in the following scenarios:

CommServe and Client computer are in different networks.

CommServe is registered in a workgroup

During the Interactive Restore, you can configure the WINS as follows:





5. Click Next.



Enter the CommCell User Name and Password.

Select the Network Connection from the Connection drop-down combo box.



Select the Use the following IP address option.

Enter IP address, Subnet mask, Default gateway.

Enter the Preferred DNS in which CommServe is registered.

Enter the Primary WINS.

8. Perform the Interactive Restore. The specified WINS and DNS will be used for name resolution of the client.

You can restore specific volumes on the client computer. You can select only system volumes during restore and add the non-system volumes later. This feature is

Selecting Volumes


useful in the following scenarios:

The non system volumes reside on disks provisioned by iSCSI or SAN.

You do not want to restore the data from the non system volumes.


You can select volumes before creating a response file and then use the modified response file for a non-interactive restore.



3. Click Next.

4. Click the Disk Configuration tab.

The list of volumes available on the client computer is displayed.

5. Select the required volumes from the list. The Selected volumes will be restored during the Non-interactive restore.

6. Click in the Capacity column and enter the volume size for each volume.

If you are decreasing the volume size, ensure that the volume size is greater than the actual data size on the volume.


8. Perform the non-interactive restore using the response file. The client will be restored with selected volumes.

Interactive Restore

Follow the steps given below to select volumes during interactive restore:





5. Click Next.



Click Get Clients to get the list of all file system clients on which the system state backup have been performed.


Click Next.

8. Click Next.


Enter the CommCell console credentials and Click Next.

10. Select Dissimilar Disk Mapping and click Next.


11. Review Client Internet Protocol (TCP/IP) Properties and Click OK.

12. The Customize the Disks dialog box appears by default. It displays the Source Disk Layout and Destination Disk Layout.

The Source Disk Layout is the disk layout of the client computer at the time of the backup

The Destination Disk Layout is the disk layout of the target computer.

Before creating disk partitions on the destination disk, you must initialize the disk. Right-click any disk in the Destination Disk Layout and select one of the following options:

Initialize as MBR Basic Disk

Initialize as MBR Dynamic Disk

Initialize as GPT Basic Disk

Initialize as GPT Dynamic Disk

13. Click Yes.

14. Repeat steps 1 and 2 for the required disks in the Destination Disk Layout. Once all the required disks are initialized, you can map the volumes from the source disk to the destination disks.

15. Right-click a volume in the Source Disk Layout and select Map.

16. In the Customize the Volumes dialog box, select a disk from the Available Disk List. The volume selected in step 3 will be created on the selected disk.


Click OK.

17. Repeat steps 4 and 5 for all the volumes from the Source Disk Layout, which you want to create in the Target computer.

Once all the required volumes are mapped, click OK on the Map the Disks dialog box. The Full System Restore starts.

The client will be restored with

Administrator can create a separate end-user account to perform the 1-Touch recovery. The end-user account must be assigned the following capabilities in order to perform 1-Touch Recovery:

Administrative management

Browse

End User Access

Out of place Recover

In Place Recover

Installation

Agent Management

Follow the steps given below to assign the end-user capabilities:

1. From the CommCell Browser, navigate to Security.

2. Right-click CommCell User Groups and click New User Group.

3. In the General tab, type the user group name in the Name box.

4. Enter the description about the user group in the Description box.

5. Click the Capabilities tab and assign following capabilities to the user group:

Using an End-User Account for 1-Touch Recovery



By default, the user account which you have used to login to CommCell console will be used to perform the non-interactive restore. If you are using Active Directory User account to login to the CommCell console, you must enter the password for the user account while creating the response file . If you have logged in as CommCell console administrator, the password is not required while creating the response file.

Follow the steps given below to use an alternate user account for non-interactive restore:


Right-click the <Client> and click All Tasks | 1-Touch Recovery Point

2. Click Next.

3. Click the Use a different user account option.

4. Enter the credentials for the user account which you want to use to perform the non-interactive restore.

5. Click Finish.

Interactive Restore

Follow the steps given below to use an alternate user account for interactive restore:






5. Click Next.





Click Next.

8. Click Next.

9. In the CommCell Credentials area, enter the credentials for the user account which you want to user for for 1-Touch recovery.

10. Click Next and complete the steps for Interactive Restore.

Creating a Response File

A response file is required to perform the non-interactive restore of a client. This file stores the client configuration information backed up on a specific point-in-time. You can save the response files and use it later to restore the client.

Follow the steps given below to create and save the response file:


Right-click the <Client> and click All Tasks | 1-Touch Recovery Point.

Additional Options


2. By default the response file will be created using the client configuration backed up by default backupset in the most recent backup.

Click Next.

3. Click each of the following tabs to review the client configuration:

General tab

Configuration tab

Disk Configuration tab

Restore Options tab

Advanced tab

Click Finish.


4. By default, the response file will be saved on the computer where you are running the CommCell console.

Click Save to save the response file at its default location.

If you want to save the response file on any other location on the computer or in the domain, specify the location and then click Save.

You can copy the response file to a network location or on a USB drive and use it later to perform the non-interactive restore.

Accessing the Response File From An UNC Path During a Non-Interactive Restore

You can access the recovery response file from a network location during the non-interactive restore. Follow the steps give below to perform the non-interactive restore when the recovery response file is stored in a network location::

1. Boot the client using the 1-Touch Live CD.

2. Select the language from the list

Click OK.

3. Click OK.

A temporary DHCP IP will be assigned automatically to the client that you are recovering.


4. If the temporary DHCP IP is not assigned automatically, you have to provide the Static IP, Subnet Mask Default Gateway, Primary DNS and WINS.

5. Enter the UNC path of the location where the response file is located and click Open. The full system restore starts.

The permanent IP address of the client will be the IP address that is stored in the response file.

Using AN USB Drive Instead of Live CD

You can use an USB drive to boot the client. Follow the steps given below to create an USB drive for booting the client:

1. Connect the USB drive with the computer where you have stored the 1-Touch ISO image.

2. Open the Command Prompt and enter the following commands:

DISKPART

lis disk

3. Identify the disk number of the USB drive that you want to use to boot the client and enter the following commands:

sel <disk number>

clean

create partition primary

select partition 1

active

format fs=ntfs quick

assign

exit

4. Using the command prompt, navigate to the SystemRecovery\Images\Windows X64\BOOT_IMAGE\ISO\boot location and enter following command:

BOOTSECT.EXE/NT60 <assigned drive letter for USB drive>:


5. Copy the content in ISO folder (SystemRecovery\Images\<processor type>\BOOT_IMAGE\ISO) to USB Drive.

6. Connect the USB drive to the client that you want to boot.

7. Change the BIOS Settings on the client to boot from the USB drive.

Restoring the Teaming Network Adapters

To restore the teaming network adapter:

1. Uninstall the teaming software.


3. Install the teaming software to restore the teaming net.

You can perform 1-Touch recovery to restore a single node or the entire cluster. Before performing the 1-Touch recovery, ensure that the following prerequisites are satisfied:

PrerequisitesWindows File System iDataAgent is installed on all the physical nodes of the cluster. For more information, refer to Install the Components.

The Windows Cluster Client is created in the CommCell Console. For more information, refer to Create the Cluster Group Client.

One Full backup of the default subclient of the Windows Cluster Client is performed. For more information, refer to FAQ.

Once all the prerequisites are satisfied, you can perform 1-Touch recovery in one of the following scenario:

Recover any One Node in the Cluster

When any one node (passive or active) of the cluster is down, you can restore the node as follows:

1. Use the 1-Touch Live CD to boot the node.

If a active node of the cluster is down, once you boot the node, the quorum disk and shared disks will move to the other node of the cluster. The other node will become the active.

2. Perform Interactive Restore or Non-interactive restore to restore the node.

Recover All the nodes of the cluster

If all the nodes are down and quorum disk is uncorrupted, you can follow the steps given below to restore the nodes:

Restoring Active Node

You must perform an interactive restore of the active node. Follow the steps give below to restore the active node:

1. Use the 1-Touch Live CD to boot the active node.


3. Click Next.






9. Click Next.


11. Click Next.



14. Click Next.

15. Select Dissimilar Disk Mapping.

Cluster Recovery


16. Manually clean and create system disk. Do not format shared or quorum disk.

17. Complete the Interactive Restore.

Recovering Passive Nodes

You can perform interactive restore or non-interactive restore to recover the passive nodes. For more information, refer to Interactive Restore or Non-interactive Restore.

Recover all the Nodes of the Cluster and Quorum Disk

If all the nodes of a cluster are down and the quorum disk also inaccessible, follow the steps given below to restore the nodes and quorum disk:

Recover Active Node


Recover quorum disk

Once the Active Node is restored, you can restore the data on the quorum disk or shared disk from the CommCell console. Follow the steps given below:

1. From the CommCell Console, navigate to Client Computers | <Windows Cluster Client> | File System.

2. Right-click defaultBackupSet and click Browse and Restore.

3. Select the data that you want to restore on the quorum disk or shared disk and click Recover all selected.

4. Specify the location where you want to restore the selected data.

5. Click OK.


Recover Passive Nodes


Back to Top


Frequently Asked Questions - 1-Touch Windows

What License is Required to perform the 1-Touch Recovery?

Can I Convert a Client Computer into a Virtual Machine?

Can I Convert A Virtual machine into a Physical Machine?

How to add 1-Touch ISO image to a PXE Server?

How Can I manually add software updates to 1-Touch Server Cache?

How can I perform backup of a Cluster Client?

How do I restore data post-upgrade from a 1-Touch computer?

Can I Perform 1-Touch Recovery if the client and the CommServe are separated by a firewall?

Can I Perform 1-Touch Recovery if there is a port restriction between the Client and the MediaAgent?

Can I Perform 1-Touch Recovery of a client computer with UEFI?

I have migrated a client computer to a new CommCell. Can I perform the 1-Touch Restore of the Client?

Can I restore Dynamic Disks on the Client Computer by 1-Touch Restore?

Can I perform 1-Touch recovery of the data which is encrypted using the McAfee Endpoint Encryption?

Can I restore a MediaAgent from a secondary copy which is available on the different MediaAgent?

Following licenses are required to perform 1-Touch recovery of any client:

Yes. When a CommServe is connected to an ESX server, you can convert convert a physical machine (computer) into a virtual machine using the 1-Touch backup data. You can also modify the hardware and network configuration of the client while converting it into a virtual machine. For more information, refer to Virtualize Me -Getting Started.

Can I Convert A Virtual machine into a Physical Machine?

Yes. Follow the steps given below to convert a virtual machine into a physical machine:

1. Ensure that you have enabled 1-Touch backup on the virtual machine and you have performed atleast one full backup.

2. Create a response file for the virtual machine and perform the Non-Interactive Restore using the response file.

For more information about creating response file for a Windows machine, refer to Non-Interactive Restore.

For more information about creating response file for a Linux machine, refer to Non-Interactive Restore.

During Non interactive restore, copy the response file on a USB drive and connect the USB drive to a physical machine.

How to add 1-Touch ISO image to a PXE Server?

1. Create the 1-Touch ISO image using the 1-Touch Boot CD Wizard.

2. Configure the PXE Server and add the 1-TOUCH ISO image to it.

3. Use a remote monitoring console to start the client and select a PXE boot.

4. Change the CMOS boot sequence to boot from the hard disk.


6. Once the restore completes, set the CMOS back to PXE or the preferred boot method.


Table of Contents

What License is Required to perform the 1-Touch Recovery?

AGENT/COMPONENT LICENSE TYPE LICENSE CONSUMPTION

Microsoft Windows File System (Desktop Class)

Laptop and desktop

Microsoft Windows File System (Server Class)

Server File system

1-Touch for Windows 1-Touch Server for MS Windows 1 license per CommCell

Can I Convert a Client Computer into a Virtual Machine?


How Can I manually add software updates to 1-Touch Server Cache?


2. Navigate to <software_install_directory>/Base/

3. Double-click CopyToCache.exe.

4. Enter or Browse to the location where updates are available.

5. Select Copy to Cache to copy the updates to CommServe Updates Cache

6. Select Copy to 1-Touch to copy the updates to 1-Touch Server Updates Cache.

7. Click Copy to start the copying process.

How can I perform backup of a Cluster Client?

Follow the steps given below to perform the backup of Windows Cluster Client:

1. From the CommCell Console, navigate to Client Computers | <Windows Cluster Client> | File System | defaultBackupSet.

2. Right-click default subclient and click Properties.

3. Click the Storage Device tab and select a Storage Policy.

4. Click OK.

5. Right-click default subclient and click Backup.

6. Select Full as the backup type and click OK.

The backup operation will start for the default subclient of Windows Cluster Client.

How do I restore data post-upgrade from a 1-Touch computer?

We recommend you to upgrade the MediaAgent, 1-Touch Server and Client after upgrading the CommServe, and then run a new backup before performing a restore using the Version 10 1-Touch Live CD or Virtualize Me.

However, if it is not possible to follow the above mentioned recommendation then, use the following steps to restore data post-upgrade:

Restoring data is supported if you upgrade from Version 9 to Version 10.Restore of data from Version 8 is not supported. In this case, you need to run a first full backup after the upgrade.

Scenarios Offline Interactive Recovery Offline Non-Interactive Recovery

Online Recovery Virtualize Me

Only CommServe is upgradedIf 1-Touch server and MediaAgent are not upgraded, you cannot create version 10 Live CD. In such scenario, you can use version 9 Live CD to restore the client. Contact your software provider for more information.

If you perform the recovery using version 9 Live CD, any new features from Version 10 are not supported.

Not supportedNot supported

Not supported

CommServe and MediaAgent are upgraded

1. Upgrade the 1-Touch server.

2. Create a new Version 10 Live CD to boot the client computer.

1. Upgrade the 1-Touch server.


Not supported1. Upgrade the 1-Touch

server.



Can I Perform 1-Touch Recovery if the client and the CommServe are separated by a firewall?

No. You cannot perform 1-Touch Recovery (Interactive, Non-Interactive, or Online Restore) when firewall is configured between the client and the CommServe.

Can I Perform 1-Touch Recovery if there is a port restriction between the Client and the MediaAgent?

No. You cannot perform 1-Touch Recovery (Interactive, Non-Interactive, or Online Restore) when there is a port restriction between the client computer and the MediaAgent.

Can I Perform 1-Touch Recovery of a client computer with UEFI?

No. 1-Touch Recovery is not supported if the client computer is configured with UEFI or EFI BIOS.

I have migrated a client computer to a new CommCell. Can I perform the 1-Touch Restore of the Client ?

Yes. After migrating the client into a new CommCell, you can perform the 1-Touch restore (Non-Interactive or Interactive). The backup performed in the old CommCell can be used for the restore the client.

Can I restore Dynamic Disks on the Client Computer by 1-Touch Restore?

3. Start the Offline Interactive recovery of the client.

3. Start the Offline Non-Interactive recovery of the client.

3. Start the recovery of the client.

CommServe, MediaAgent, 1-Touch Server and client are upgraded

Before running the first backup



3. Reboot the client computer after the restore is completed successfully.

4. Uninstall the Data Protection Suite software from the client.

5. Logon to the CommCell Console and release the license of the client. However, do not delete the client from the CommCell.

6. Install latest version of the Data Protection Suite software on the client.







Not supported1. Create a new Version 10

Live CD to boot the client computer.







After running the first backup

Supports all new features available for Version 10 Data Protection Suite software.

Supports all new features available for Version 10 Data Protection Suite software.

Not supportedSupports all new features available for Version 10 Data Protection Suite software.


After running the first backup but data has to be restored from an older version backup













Not supported1. Create a new Version 10

Live CD to boot the client computer.







Yes. You can restore dynamic disks by 1-Touch restore.

Can I perform 1-Touch recovery of the data which is encrypted using the McAfee Endpoint Encryption?

No. If the data on a client computer is is encrypted using the McAfee Endpoint Encryption, 1-Touch recovery is not supported.

Can I restore a MediaAgent from a secondary copy which is available on the different MediaAgent?

Yes. You can restore a MediaAgent using a secondary copy and the secondary copy is available on the different MediaAgent. Follow the steps given below to restore the MediaAgent:

1. From the CommCell Console, navigate to Client Computers | <MediaAgent>.

2. Right-click the <MediaAgent> and click All Tasks | 1-Touch Recovery Points.

3. Click Next.

4. Click Restore Options tab and specify the Copy Precedence of the secondary copy.

5. Click Advanced tab and ensure that the Client is a MediaAgent check box is not selected.

6. Click Finish.


8. Copy the recovery response file to the formatted USB drive. Use a USB drive (USB stick) with a smaller size to copy the response file. Alternatively, you can use a use a network location to copy the response file.

9. Perform the Non-interactive restore.


Troubleshooting - 1-Touch for Windows

The following section provides information on some of the troubleshooting scenarios related to 1-Touch Recovery:


Symptom/Error SolutionA full system restore of a Microsoft Windows 2008 Server requires the administrator to provide the product license key. This message will appear on the Windows login screen after a full system recovery from a backup that contained an activated product key:

An unauthorized change was made to Windows. You must retype your Windows Server Product Key to activate the license.

Provide the activated product key again in order to log in to the recovered client.

Failure during Windows Server 2003 Cluster Recovery When the cluster disks are repartitioned, a failure message may appear because the disk GUIDs for the quorum have been changed.

1. View the System Event Log.

2. If you see Event ID 1034 in the System Event Log, refer to the KB 305793 and KB 280425 in the Microsoft Knowledge Base articles on http://support.microsoft.com/.

System State Backup fails The 1-Touch component of system state backups will fail whenever you run services as a backup operator. As a workaround, either skip backing up 1-Touch information during system state backups by using the SKIP_1TOUCH_BACKUP registry key, or run the backups using the local system account.

During the mini setup stage the following error message appears:Windows could not complete the installation. To install Windows on this computer, restart the installation.

1. Open Command Prompt

2. Navigate to %systemdrive%\Windows\Panther.

3. Open diagerr.xml file.

4. Ensure that the diagerr.xml file displays the following error message:

5. EnableLocalUserAccount: Unable to enable local account [Administrator]; status = 0x8c5

6. Perform the administrator backup of the client.

The mini-setup fails during the offline restore because only the administrator can run the mini-setup.

7. Perform the offline restore. Windows Management Instrumentation (WMI) Service are not recovered after an Interactive or Non-interactive restore.

The WMI services cannot be restored using the Interactive or Non-interactive restore method if the VSS is not enabled before performing the system state backup. For more information about enabling VSS for system state backup, refer to Configuring System State Backups.

To restore WMI services, browse the default subclient and select WMI from the System State. For more information about Browse and Restore method, refer to Getting Started - Windows File System Restore.

Interactive Restore fails if you manually reboot the client after the Data Protection Suite install.

After the Data Protection Suite install, the client IP address is added to the CommServe database and when you initiate the Interactive Restore with the same IP address and hostname, the restore fails. Follow the steps given below before starting the interactive restore:


2. Identify and right-click the client and select All Tasks | Release License.

3. Right-click the client and select All Tasks | Delete.

4. Start the Interactive Restore. During the Offline Restore the CommCell Console displays the following message:

Please check the Windows Server service. Windows share permissions will not be backed up or restored. [[2114] The Server service is not started.

This message appears because Windows in not running on the target computer. The Share permissions will be restored automatically during the Offline Restore. You can ignore this error message.

Distributed Component Object Model (DCOM) component appears disabled after the 1-Touch restore of the client computer

Run the following command from the command prompt on the client computer after 1-Touch restore operation is complete:

%windir%\system32\msdtc.exe –resetLog

Microsoft Distributed Transaction Coordinator (DTC) Service does not start after 1-Touch Recovery

Follow the steps given below to restart the Microsoft Distributed Transaction Coordinator (DTC) Service:

1. Navigate to the following folder:

%SystemRoot%\System32\DtclogIf the Dtclog folder does not exist, create the folder.

2. Check if a Msdtc.log file exists and ename it to Msdtc.old.

3. Create a new Msdtc.log file using Notepad and save it at the following location:


%SystemRoot%\System32\Dtclog4. Open the command prompt and enter the following command:

msdtc -resetlogSystem State Backup fails while backing up 1-Touch components. Ensure that the 1-Touch client is not using SAN over Fiber channel as a boot disk.

If the client computer has any disks which are in SAN over Fiber channel, you cannot perform 1-Touch recovery. You must perform Full System Restore for such clients.

For more information, refer to Disaster Recovery - Windows File System.1-Touch Client does not reboot automatically after the full system restore.

If the client computer has 2 disks, the disk drive numbers may not correspond as expected during the full system restore. As a result, the system disk will be restored as a second disk and client computer fails to reboot. For more information about issues in disk enumeration, refer to http://support.microsoft.com/kb/937251.

Change the order of the disks from the BIOS Settings after the restore completes. Full System Restore goes to pending state during 1-Touch Recovery of Windows XP SP2.

If the 1-Touch client has Windows XP Service Pack 2 (SP2) installed on it, Windows Firewall is turned on by default. A full iDataAgent Restore job will go to a pending state if the client firewall is turned on.

When the job state goes to pending perform the following:

1. On the command line, type CTRL+C and press Enter.

2. Turn off the firewall on the client.

3. Resume the job from the CommCell Console.

The restore operation will recover the firewall settings from the backup data.

You can view the firewall settings on the client computer:

1. Click Start and then click Control Panel.

2. In the Control Panel, click Windows Security Center and then click Windows Firewall. While creating Live CD, you may get following error:

Could not contact server, AttachPreInstall failed.

This error appears because the network card without an IP has got more priority in the 1-Touch server.s Follow the steps given below to change the priority of the NIC card:

1. Click Start | Run.

2. Type ncpa.cpl and then click OK.

You can see the available connections in the LAN and High-Speed Internet section of the Network Connections window.

3. On the Advanced menu, click Advanced Settings, and then click the Adapters and Bindings tab.

4. In the Connections area, select the connection that you want to move higher in the list.

5. Use the arrow buttons to move the connection. Unable to setup remote connection to the SQL Server on a Clone Computer

SymptomAfter creating the clone of a computer which hosts the SQL server, you can login and query the SQL server database on the clone computer. However, the remote connection to the SQL server on the clone computer fails. The applications, which use @@SERVERNAME function, may have problem in connecting to the SQL server.

CauseThe SQL Server stores the local computer name in sys.servers table in the master database. This name is reported by the system function @@SERVERNAME. When you create the clone, you specify the new name for the clone computer. Therefore, the local computer name in the sys.servers table will not march with the new name.

SolutionYou can directly replace the <old computer name> with the <new computer name> in the database directly using proper queries. Otherwise, if you are using the stand-alone SQL server and not the SQL Server failover cluster, follow the steps given below to update the database with the new name:

1. Disconnect any remote logins to the SQL servder. Use the following commands to disconnect the remote logins:

Remote logins to default instance:

Remote logins to a named instance:

2. On the clone computer that hosts the default instance of the SQL server, run the following commands:

sp dropremotelogin <old name>

sp dropremotelogin <old name\instancename>


Press Enter.

Press Enter

Or

If the Clone computer hosts the named instance of the SQL server, run the following commands:

Press Enter.

Press Enter.

3. Restart the SQL server instance.

When you Clone the computer which hosts the SQL server, keep in mind:

SQL Server does not support renaming computers that are involved in replication. After cloning a machine that is configured to use Reporting Services, Reporting Services might not be available on the Cloned machine. Refer Renaming a Report Server Computer on msdn library. If you have created a Windows group to access the SQL server and that group uses a hard-coded reference to the computer name, update the Windows group to specify the new computer name. Otherwise, users in that group will not be able to connect to the SQL server. Linked server configurations will be affected by the cloning operation. Client aliases that use named pipes will be affected by the cloning operation.

sp_dropserver <old_name>

sp_addserver <new_name>, local

sp_dropserver <'old_name\instancename'>

sp_addserver <'new_name\instancename'>, local

All the Links referring to the SharePoint instances on a clone computer are broken

SymptomAfter creating the clone of a computer which hosts the Sharepoint server, all the links which refer to the SharePoint instance on the clone computer are not working.

CauseWhen you create the clone, you specify the new name for the clone computer. The SharePoint database is not updated automatically with new name. Thus all the site references with SharePoint will refer to the site with the old name.

SolutionUpdate the SharePoint database with the new computer name.

Update SharePoint Server 2007

Follow the steps given below to update the database of the SharePoint Server 2007:

1. Login to the SharePoint Server. You should be the member of Administrators group on the local computer.

If the clone computer hosts SQL server and SharePoint server, you must use the same user account to update SQL server database and SharePoint sever database.

2. Open a command prompt window and navigate to the folder where stsadm.exe is available.

Generally the STSADM tool is available at the following location:


where <newname> is the name of the clone computer

<oldname> is the name of the original computer.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o renameserver -newservername <newname> -oldservername <oldname>


This operation will change the server name only within the SharePoint system. It will only replaces the SharePoint system entries for old server name with new name in SharePoint databases.

4. Open Central Administration.

5. Click on the Operations tab

6. Click on the Alternate access mappings link under the Global Configuration.

7. Modify each mapping item to reflect your new server name, make sure to keep port numbers unchanged.

8. Rename all the old server names with the new server name.

9. Reboot the machine.

You may also run the SharePoint Product Configuration wizard.

Update SharePoint Server 2010

1. Login to the SharePoint Server. You should be the member of Administrators group on the local computer.

If the clone computer hosts SQL server and SharePoint server, you must use the same user account to update SQL server database and SharePoint sever database.

2. Open a command prompt window and navigate to the folder where stsadm.exe is available.

Generally the STSADM tool is available at the following location:


where <newname> is the name of the clone computer

<oldname> is the name of the original computer.

This operation will change the server name only within the SharePoint system. It will only replaces the SharePoint system entries for old server name with new name in SharePoint databases.

4. Run the SharePoint Product Configuration wizard. This wizard modifies all the old server names with the new server name and keeps the port numbers unchanged.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o renameserver -newservername <newname> -oldservername <oldname>

1-Touch Restore Fails with the following Error:

Windows returned no error string for error 8004240f

You will get this error when a new partition cannot be created on the unused space on a disk. For more information about other VDS errors, refer to http://msdn.microsoft.com/en-us/library/dd208031.aspx


1-Touch Restore for Windows - Options

Use this wizard to create the response file for the client computer which you want to restore. A response file saves the client configuration, which can be used later forNon-interactive 1-Touch Restore.

Select Recovery PointsThis is the first step in the Recover To wizard. In this step you can select the backup data which you want to use to create the response file.

Backup Set

By default the data and client configuration backed by the default backupset is used to create the response file.

If you want to use the data and configuration backed up by any other backupset, select the backup set from the list.

Recover from the latest backup and configuration

This option is selected by default. The latest backup data and client configuration is used to create the response file. You can create the response file using a backup performed at a specific point-in-time.

Select Point in Time

Select this option to specify the specific point-in-time. The backup performed at the specific point-in-time will be used to create the response file.

You can specify the point-in-time as follows:

Restore Data Before:

Select a date and specify the time.

Time zone

The default time zone of the CommServe is selected automatically. Select the Time zone if you want to use the backup performed in a different time zone.

Next

Click this button to go to next step.

Review Recovery OptionsIn this step you can change the client configuration. The response file will be created with modified client configuration.

Following options are available to modify the client configuration:

Host Name

The host name of the CommServe which is used to backup client.

Client Name

The name of the CommServe Client.

IP Address

Enter the IP Address of the CommServe which is used to backup the client.

Use the currently logged in user account

This option is selected by default. The user account which you have used to login to CommCell console will be used to perform the restore job.

If you are using Active Directory User account to login to the CommCell console, enter the password for the user account.

If you have logged in as CommCell console administrator, the password is not required to perform the job.

Use a different user account

Select this option if you want to use a different user account to perform the virtualization or restore job. Administrator can create a separate user account to perform this job.


Recover To

General tab


Enter the credentials for the user account.

Ensure that the user account has the following capabilities: Administrative management, Out of place Recover, In Place Recover.

Following options are available to modify the client configuration:

Network Configuration

Displays a list of all Network Interfaces available in the client. Select the interface which you want to use after the restore.

Add

Click this option to add a new Network Interface.

Edit

Click this option to change an existing Network Interface.

Delete

Click this option to delete a Network Interface.

The Disk Configuration tab displays a list of volumes available on the client computer. The list has following columns

Volume

Displays the drive letters assigned to the volume.

Disk Name

Displays the name of physical disk associated with the volume.

Capacity

Displays the volume size. Double-click in this column to change the size of any volume.

Selected

Select the check box in this column to select a volume. The selected volume will be added to the client during the 1-Touch restore . You can select only system drives and add the non-system drives later.

Following options are available to to restore the client configuration:

Copy Precedence

If you want to use the client configuration and data available in a specific storage policy copy, enter copy precedence number for the specific copy.

Do not Use Windows Mini-Setup

Select this check box if you do not want to run the Windows Mini-Setup Wizard. If you are performing a cross hardware restore, the Mini-Setup wizard runs after the Full System Restore.

User Account

If the client computer is member of a domain, click Change to enter the credentials of the domain in which you want to add the client after 1-Touch restore.

License Key

If you are restoring the Windows 2003 client, enter the license key for Windows 2003 operating system.

You can create a clone of a client computer during 1-Touch restore. This will be useful when you are performing 1-Touch restore on a computer different than the original client computer.

Clone Machine

Select this check box to create the replica of the client computer. The client computer can be a physical computer or a virtual machine.

The clone computer will be a virtual machine.

Configuration Tab

Disk Configuration Tab

Restore Options tab

Advanced tab


New Client Name

The clone computer will automatically become the client of the CommServe. Enter the client name for the clone computer.

New Hostname

Enter the hostname for the clone computer.

Client is a MediaAgent

Select this check box when you are performing the 1-Touch recovery of a MediaAgent.

USB drive

This option is selected by default. By default, the index will be restored to the USB drive attached to the computer where you are performing the 1-Touch recovery.

Network Share

Select this option if you want to restore the index to a network location.

User Name

Enter the user name for the user account which will be used to access the network location. This user account must have the following capabilities: Administrative management, Out of place Recover, In Place Recover

Password

Enter the password for the user account.

Index cache path

Enter the location where you want to restore the index. Click to specify the location.

Finish

Click this button to generate the response file.


Primary Storage Reports - Windows File System

ConfigurationEnabling Data Collection for SubclientsRunning a Backup

Reports

Reports can be generated from the data collected during a backup job. After the backup job runs, the collected data is stored. This post processing might take some time. Therefore, data for reports is not immediately available after a backup job completes.

Prerequisites

The File System Advanced agent must be installed on the client in order for the data collection option to appear. The data collection option does not appear on clients that are installed only with File System Core.

Enabling Data Collection for Subclients

To enable collection of file and system data:

1. From the CommCell Browser, locate the correct client computer node, and right-click the subclient for which you want to catalog file and system attributes, and then click Properties.

2. Click the Advanced Options tab.

3. Click Catalog additional file and system attributes.

4. Click OK to save your settings.

Running a Backup

A full backup contains all the data that comprises a subclient's contents. If a client computer has multiple agents installed, then the subclients of each agent require a full backup in order to secure all of the data on that client. If a new subclient is added, a full backup is required on all subclients.

To perform a full backup:

1. From the CommCell Browser, navigate to <Client> | <Agent> | defaultBackupSet.

2. Right click the <Subclient>, and then click Backup.

3. Under Select Backup Type, select Full, and then under Job Initiation, select Immediate to run the job immediately.

4. Click OK.

5.

After performing a first full backup you may select any other backup type for performing Data Collection operations.

6. You can track the progress of the backup job from the Job Controller window. When the backup has completed, the Job Controller displays Completed.

After performing a first full backup you may select any other backup type for performing Data Collection operations.

Table of Contents

Configuration

You cannot enable cataloging for additional file and system attributes on IntelliSnap subclients. Although the option might appear selected, file and system data is not collected.


Primary Storage Reports are no longer available in the CommCell Console, but data is still collected using the SRM integrated agents. In order to view reports based on the collected data, you must create a report with the Build-Your-Own Reports feature. For more information, see Transition from Primary Storage Reports to Build-Your-Own Reports.

Reports


Best Practices - Windows File System

Eliminating Backup Failures

Re-configuring Default Subclient Content

Restore by Job

Restoring to a Rebuilt or New Computer

Restoring Data from a Specific Copy

Restoring to a Computer with Different Hardware Configuration

Replicating Active Directories to Other Domain Controllers

Restoring Domain Controllers in Virtual Machines Without Inconsistencies

Installing Windows during Full System Restore

Enabling VSS to Backup Locked Files

Filtering Exchange/SQL Files from Backup

System State Restore for Windows Server 2008

Restore from deduplicated volumes on Windows Server 2012

Eliminating Backup Failures

You can use filters to exclude items which consistently fail and that are not integral to the operation of the system or applications. Some items fail because they are locked by the operating system or application and cannot be opened at the time of the data protection operation. This often occurs with certain system-related files and database application files. Also, keep in mind that you will need to run a full backup after adding failed files to the filter in order to remove them.

Re-configuring Default Subclient Content

We recommend that you do not re-configure the content of a default subclient because this would disable its capability to serve as a catch-all entity for client data. As a result, some data will not get backed up or scanned.

Restore by Job

Avoid running restores by jobs for jobs associated with the default backup set, if you do not want to restore the operating system files or directories. The entire content of the backed up client will be restored and the client where you are restoring might run out of space.

Restoring to a Rebuilt or New Computer

If you are restoring to a different computer, perform the following checks to make sure the target computer is similar to the source computer:

Make sure the target computer has the same fully qualified network name as the original.

Try to match the general hardware configuration (i.e., IDE, SCSI) of the original computer.

Match the local disk drive configuration as closely as possible to that of the client being restored.

Make sure the computer's disk(s) can accommodate the quantity of data being restored.

If possible, use the same network interface card (NIC) as that of the client being restored.

The CommCell Console requires 256 colors to run. When you open the CommCell Console on a rebuilt computer, you may need to install the correct video driver to increase the color depth of the client computer or run the console from another computer.

Restoring Data from a Specific Copy

If you specify a copy precedence number for a restore, the software searches only the storage policy copy with that precedence number in each of the storage policies through which the data was secured. If data does not exist in the specified copy, the data recovery operation fails even if the data exists in another copy of the same storage policy. Therefore, it is recommended to specify the copy precedence for a restore operation in the following scenarios:

The primary copy is no longer available for a restore operation due to a hardware failure.

You know that the media containing the data for a particular copy have been removed from the storage library. In this case, you can choose to restore from a copy whose media are inside the library.

You want to restore from a selective copy.

You want to restore from a copy that accesses faster disk media rather than slower tape media.

You know that the media drives used by a particular copy are busy with another operation and want to restore from a different copy to avoid resource conflicts.

Restoring to a Computer with Different Hardware Configuration

Table Of Contents


If you are performing a full system restore to a computer with a different hardware configuration (mass storage device, network interface card, video card, etc.), do not restore the system state data. Restoring system state data includes restoration of the hardware entries in the registry.

Replicating Active Directories to Other Domain Controllers

The Active Directory uses a Tombstone mechanism to delete objects from its directory on Windows 2000 and Server 2003 clients. When an Active Directory object is deleted from a domain controller, it is initially marked as tombstoned and is not fully removed from the directory. During Active Directory replication, the tombstone attribute is replicated to the other domain controllers, temporarily deleting the object from all the domain controllers. Once the tombstone lifetime is reached, the object is permanently removed from the directory. The Active Directory Tombstone has a default lifetime setting of 60 days.

When performing restore operations, you must consider the Active Directory tombstone lifetime. Restoring from a backup that was secured more than a lifetime before the restore may result in Active Directory inconsistencies. The restored domain controller may have objects that are not replicated on the other domain controllers. These objects will not be deleted automatically, as the corresponding tombstones on the other servers have already been deleted. Therefore, when you restore from a backup that is older than the tombstone lifetime, you may have to manually delete each unreplicated object on the restored computer in order to resolve inconsistencies.

Restoring Domain Controllers In Virtual Machines without inconsistencies

It is highly recommended to backup system state of the virtual machine with domain controllers. This is because the Active Directory data, log files, registry settings, system volume folder and other various operating system elements that are mandatory for Domain Controllers are not backed up in any other backup process other than system state backup, thereby resulting in several issues after the restore. System State includes all the mandatory elements for physical and virtual machine domain controllers.

You must backup a minimum of one domain controller in the forest every tombstone number of days. For more information, refer to Running Domain Controllers in Virtual Hosting Environments.

Installing Windows during Full System Restore

Windows must be installed in the same directory as that of the original computer; otherwise, full system restores will not work. For machines that have been upgraded to Server 2003 from Windows 2000, Windows must be installed in the WINNT directory.

Enabling VSS to Backup Locked Files

When you have enabled VSS for a default subclient, the Locked database files are backed up in an inconsistent state and some system protected data will get backed up.

For example, you may have an Exchange database installed on the client. The Exchange database should not be backed up by the Windows File System iDataAgent because it will not be able to restore the database. Furthermore, this will increase your media usage. It is recommended to use the Exchange Database iDataAgent to backup the Exchange database.

If you have locked files that you would like to back up using VSS, it is recommended that you create a subclient for them and enable VSS on that subclient.

Filtering Exchange/SQL Files from Backup

By default, Windows File System iDataAgent will backup SQL or Exchange databases if they are part of a subclient content. However, if these databases are backed up using the corresponding Exchange Database iDataAgent or SQL Server iDataAgent, you can exclude them from Windows File System backups by creating the FilterSqlExchFiles additional setting on the client computer.

System State Restore for Windows Server 2008

The system state restore for Windows Server 2008 may take a long time to complete. On Windows Server 2008 treats more files are System Protected files as compared to any other Windows operating systems. Large System Protected Files backups can require additional disk space for recovery while the files are being moved.

It is recommended to keep at least 10-15GB free space on the following drives:

The drive where job results folder is located

The drive where Windows is installed

Restore from deduplicated volumes on Windows Server 2012

Windows Server 2012 has a deduplication feature that can be enabled. Data from deduplicated volumes will be backed up in its original state (uncompressed). Therefore, during a restore, ensure that you have enough storage space on the volume to restore the full data size.


Frequently Asked Questions - Windows File System

GeneralCan I create multiple subclients and backupsets to organize the data?How do I backup the Quorum data in a cluster setting?Why are my snapshots missing from the backup?Why Am I not able to see the newly added data in the backed up files?Why does my backup and recovery display inconsistent data?Do I need to Install QSnap while performing the Full System Restore?Do we stage components in the Job Results folder during the System State Restore?Backup Operation is Slow. How do I troubleshoot the slowness?How to Backup the Source Data for a Directory Junction Point?When does a Non-Full Backup Automatically get Converted to a Full Backup?Why does the backup job complete after the Scan phase?Can I backup the data which is encrypted using the McAfee Endpoint Encryption?Why are the number of objects shown higher than the number of objects actually backed up?Which retention criteria takes the maximum precedence?Why do I see HSM Recaller Services running on my computer when I have not enabled archiving?Can I set the archive attribute for files?How can I collect information about file access time and file modified time?Can I perform backup of subclients whose content is non-existent?Why is IIS (Internet Information Server) not restored during a Full System Recovery?Can we filter SIS common store from backup?Does Data Protection Suite modify last access time on files?Does modified time of a file get backed up? If yes, are the files restored with the same time?Does a full system restore override all the contents on the server and restore the server to the state it was before the backup?Why am I unable to backup or restore subclients with UNC paths as content?Why are my incremental backups same size as that of full backup?Can we filter the page file from backup?Can we back up only those files that have been recently modified or created?How will I view the files that were skipped during backup?WFS0020: Can I restore files with special characters in their names?WFS0021: Why do encrypted files take longer time to backup?WFS0022: Why am I prompted to reboot the computer after performing a restore operation?WFS0023: What are the critical and non-critical system state components on Windows operating system?

Scan MethodsHow does the Optimized Scan enhance the scanning capabilities of an iDataAgent?What is the default Location of the Meta database?How to turn off the Optimized Scan?How much hard disk space is consumed by the Metadata Database?Does the backup include all the source files associated with a hard link?Can I change the Scan Method for a subclient?

VSSHow much disk space is required on a volume for the VSS shadow copy?Why does the differential or incremental backup becomes a Full backup when VSS is enabled?Can I use VSS to backup files on a virtual server?When I am performing backup of a data, what happens to the system state component?

Lync ServerCan I backup Response File Group Configuration on a Lync Server?Can I Use restore By job option to restore the Lync server data?

Can I create multiple subclients and backupsets to organize the data?

You can create different subclients to organize the data on a client computer. The data that is backed up by any default subclient is the complement of the data that is backed up by its sibling subclients. In effect, the data associated with a default subclient is implicitly determined by the user defined subclients within the same backup set.

For example: A client computer called onyx has only one drive, c:\ which has the following folders which you want to backup:\international\forecasts\international\hr\domestic\hr

Using backup sets, you can establish different subclient groups, which will enable you to back up and restore all of the data relating only to international operations or all of the data relating only to human resource operations. You can organize the data as follows:

Table of Contents

General


Note that while the default subclients in BK1 and BK2 have the same name (i.e., default), they back up different data subsets.

How do I backup the Quorum data in a cluster setting?

The Windows File System iDataAgent on a physical node of the cluster includes the quorum data during a system state backup. It is essential for quorum data to be backed up, as it includes recovery logs as well as cluster configuration and state data. To back up the quorum data on a regular basis, you must ensure that a data protection operation is scheduled for a Windows File System iDataAgent subclient on the physical nodes, with the Backup System State option selected; a system state backup will automatically include quorum data.

Why are my snapshots missing from the backup?

When backing up a snapshot of a client computer, ensure that the operating system of the backup server is either same or higher version than the client computer.

Why am I not able to see the newly added data in the backed up files?

It is recommended to perform a full backup after changing or adding and subclient content to ensure that the newly added or modified data is completely backed up.

Why does my backup and recovery display inconsistent data?

Ensure that the volume, network or the user quota for an object are not set lower than the amount already used.

Do I need to Install QSnap while performing the Full System Restore?

Depending upon the backup from which you are restoring the system, install the QSnap either before the full system restore or after the full system restore. The following table explains the scenarios to reinstall the QSnap:

How to Backup the Source Data for a Directory Junction Point?

By default, the directory junction point gets backed up but the source data (data linked to junction point) is not backed up. This prevents undesired backup and restore of system created directory junction points. To back up the source data of a junction point that is not part of a subclient contents, the source data must be explicitly added to a subclient's content.

When does a Non-Full Backup Automatically get Converted to a Full Backup?

A non-full backup is automatically converted to a full backup in the following situations:

First backup of the subclient.

Re-associating a subclient to another storage policy.

Promote a secondary storage policy copy that is not synchronized with a primary copy (for all the subclients of a storage policy).

If a backup job within the most recent backup cycle is pruned or disabled from a primary copy.

If you switch from a IntelliSnap backup to a traditional backup or vice versa.

CommCell Migration operation.

Do we stage components in the Job Results folder during the System State Restore?

During the system state restore some components are staged in the job results folder and then get deleted once the restore of that component is complete. If a file needs to be moved during reboot, the file will not be deleted from the job results folder until the computer reboots.

Backup Operation is Slow. How do I troubleshoot the slowness?

You can view the log files of an active backup job and use performance counters in the logs to check the performance bottle necks. For more information about how to View the Log Files of an Active Job. A log has following IDs

File Open Time - Time taken to open a file

Disk Read Time - Time taken to read the file from a disk

Backup Sets Subclient Subclient Content Storage PolicyBK1 default C:\ Storage Policy A

International \international Storage Policy BBK2 default C:\ Storage Policy C

HR \domestic\hr

\international\hr

Storage Policy D

Backup Install QSnapQSnap Enabled Backup Install QSnap before performing the full system restore. QSnap was installed on the source computer after the backup was performed.

Install the Windows File System iDataAgent and then perform the full system restore. Then install QSnap after the client is restored and has rebooted. If you are not rebuilding the operating system, uninstall QSnap, restore the registry, and then reinstall QSnap.


Pipeline Allocation time and Pipeline Write Time - Time taken to write data on a media and time taken to transfer data over network.

A log displays time take by each of this process. For example, a log snippet may look as follows:

ID=File Open time, Bytes Read = 0, Total time = 0.011359, Average = 0.011359, Samples = 1

ID=Disk Read time, Bytes Read = 20, Total time = 0.013465, Average = 0.001417, Samples = 1

ID=Pipeline Allocation time, Bytes Read = 0, Total time = 0.000010, Average = 0.000010, Samples = 1

ID=Pipeline Write time, Bytes Read = 1160, Total time = 0.000004, Average = 282.587336, Samples = 1

The time value is in seconds. The highest "Total time" indicates that the majority of the time is spent in that operation. Generally it is the Disk Read Time.

If the time taken by Disk Read operation is high, the disk is the bottle neck. You can use Disk Read utility to verify the disk read performance.

If multiple reads are enabled on the disk, ensure that the hardware supports multiple reads. Enabling multiple reads degrades the performance if the hardware does not support. On the other hand if you have Raid disks or disks that allow multiple simultaneous reads, allowing multiple reads can improve the backup performance.

Slowness can be because of either the network or the media. For troubleshooting this slowness, you can use the testport, DiskRead and tapetest utilities. If the mediais a tape, use tapetest utility. If the media is a disk, use DiskReadWrite utility in the write mode. For more information about all the utilities, refer to Tools and Utilities.

Why does the backup job complete after the Scan phase?

If no files from the subclient content are added or changed since the last backup, the backup job will complete after the scan phase. The backup and archive index phases will not be performed for such backup jobs. However, if you include the system state backup in a subclient content the backup operation will go through all the phases of scan, except when you select the Only with Full backup option along with it.

However, if you want the backup job to go through all phases of scan irrespective of whether the subclient content has been changed or not, enable the bRunAllJobPhases additional settings on the computer where the File System iDataAgent has been installed.

To view the jobs that were marked complete after the scan phase, select Include Media Deleted Jobs in the Selection tab of the Job Summary Report.

Can I backup the data which is encrypted using the McAfee Endpoint Encryption?

Yes. You can perform the backup and restore of the data which is encrypted using the McAfee Endpoint Encryption.

Why are the number of objects shown higher than the number of objects actually backed up?

The total number of objects shown will be more than the actual number of objects backed up because empty folders with no files/content are also considered during the count.

For example, if you have 10 files and 1 empty folder under the root directory, the total number of objects backed up would be shown as 11 as the empty folder was also counted as an object backed up.

Which Retention Criteria Takes The Maximum Precedence?

You can specify the time period for which you want to retain the deleted files in the backup cycle. This enables you to restore the deleted files from the latest backup cycle and avoid point-in-time restores. This is useful to view (and restore) the deleted files from clients (like, laptop clients) that have backup cycles with frequent & numerous incremental backups after a full backup.

By default, when you delete any file from the source, they will be removed from the backup cycle during the next backup. You can specify the retention period for each subclient. When you run the synthetic full backup at the end of specified retention period, the deleted files will be removed from the backup cycle.

The retention criteria set at the storage policy level takes a higher precedence over the one set at the subclient level.

Example 1:

1. A subclient named <subclient 1> is associated to a storage policy with a retention value set for 4 days and 2 cycles.

2. A retention value of Keep For 5 days is set in the Retention tab of <subclient 1> properties dialog box.

3. On Day 1, perform a full backup of <subclient 1>.

4. On Day 2, run an incremental backup.

5. On Day 3, delete a file manually.

6. On Day 4, perform a full backup. You will find that the deleted file has been dropped in this backup cycle.

7. However, the deleted file will be available in the media for a period of 4 days and up to 2 backup cycles according to storage policy copy retention. After 4 days and 2 backup cycles, the data will be pruned from the media.

Example 2:

1. A subclient named <subclient 1> is associated to a storage policy with a retention value set for 4 days and 2 cycles.

2. A retention value of Keep For 5 days is set in the Retention tab of <subclient 1> properties dialog box.


3. On Day 1, perform a full backup of <subclient 1> .

4. On Day 2, perform an incremental backup.

5. On Day 3, delete a file manually during an Incremental backup.

6. On Day 4, run a synthetic full backup. Since the deleted file does not meet the retention criteria set at the subclient level, the file is carried forward.

7. On Day 5, perform an incremental backup.

8. On Day 8, perform a synthetic full backup. Since this job is run after five days of deletion (exceeds the retention criteria set at the subclient level), you will find that the deleted file will be dropped backup cycle.

Why do I see HSM Recaller Services running on my computer when I have not enabled archiving?

HSM Recaller Services are installed as part of the Windows File System iDataAgent installation. It works differently with the following agents.

Can I set the archive attribute for files?

No. You cannot set the archive attribute for files. During a file system backup, there may be a message logged in clbackup.log indicating you are unable to turn off thearchive attribute after the backup operation. This happens because the user does not have the rights to write to this folder (e.g., C:\Program Files\).

How can I collect information about file access time and file modified time?

Enable Catalog additional file and system attributes check box in the Advanced Options tab of the Subclient Properties dialog box before performing a backup. This collects the following information about files, volumes, and directories within the subclient:

The name and location of each file.

The size of each file.

The time at which it was last modified.

The time at which the file was last accessed.

The time at which the file was created.

The name of the primary user of the file.

The name of the primary user group of the file.

For more information, see Configuring File Level Information for a Subclient.

Can I perform backup of subclients whose content is non-existent?

If all the contents included in your subclient are non-existent, then the backup of that subclient fails.

Why is IIS (Internet Information Server) not restored during a Full System Recovery?

When an operating system is re-installed , IIS is not installed again. After a full system restore, IIS would fail to start or open in Internet Services Manager or Computer Management because the old keys are not replaced by the new keys.

Uninstall and Re-install IIS to resolve this issue.

Can we filter SIS common store from backup?

Yes. You can add SIS (Single Instance Storage) common store to be filtered from the backup job. However, if SIS links are found in any of the files, then that file residing in the common store is backed up. SIS links do not fail during backup since they are automatically detected.

Windows File System iDataAgent OnePass Agent for Windows Driverless OnePass Agent for WindowsYou can backup and restore data by installing Windows File System iDataAgent on your computer.

HSM Recaller Services get installed as part of the installation process.

For more information, see

Getting Started - Windows File System - Install

You can archive and restore/recall data residing in your computer by installing Windows File System iDataAgent and Driver for File Recalls.

HSM Recaller Services aids the driver in triggering recall of the archived files.

For more information, see

Getting Started - Deployment - OnePass Agent for Windows

You can archive and restore/recall data residing in your computer by installing Windows File System iDataAgent and enabling the Explorer Plugin on your client computer.

When you enable the archiving option on your client, you will be able to archive your data.

HSM Recaller Services aides in triggering recall of these archived files.

For more information about the installation process, see

Getting Started - Deployment - Driverless OnePass Agent for Windows File System

For more information about enabling the Explorer Plugin, see

Getting Started - Explorer Plugin - Driverless OnePass Agent for Windows File System


Does Data Protection Suite modify last access time on files?

Yes. If you use Change Journal scan method, then the access time of files are modified during the scan phase. If you are backing up an existing snapshot, then the last access time will not be modified. Also, if you switch to Recursive Scan method, last access time of files are not modified during the scan phase.

Does modified time of a file get backed up? If yes, are the files restored with the same time?

Yes. The last modified time of a file is backed up and the file is restored with the same time it had before the backup was performed. However, the last modified time of a parent directory may not be restored properly. This mainly depends on the order in which the files and directories are restored.

In Change Journal scan method, files and directories are backed up randomly based on the time in which the file was last modified.

In Recursive Scan method, files inside a directory are backed up first and then the directory is backed up. The files and directories are then restored in the same order in which the files were backed up.

Does a full system restore override all the contents on the server and restore the server to the state it was before the backup?

Yes. A full system restore would override all the contents on the server and restore the server to the state it was before the backup. Most of the registry keys are restored in the same state it was before the backup. Existing files are replaced only if the Unconditional overwrite option is selected from the Restore Options for All Selected Items dialog box. However, some system files may require a reboot.

Prior to performing a full system restore, make sure that the latest security, server image and service pack updates are installed.

Why am I unable to backup or restore subclients with UNC paths as content?

1. Verify that the user account given has access to perform the backup or restore operation. Backing up or restoring to an admin share would require administrator rights.

2. Identify the Job ID having issues in clbackup.log or clrestore.log. Use net helpmsg to identify the error code. For example, when you run this command, you may notice the following in the logs:

Why are my incremental backups same size as that of full backup?

Incremental backups may be the same size as that of a full backup due to any one of the following reasons:

1. A third party software or antivirus scanner installed on your system is modifying the files every time they are backed up. In this process, these files are picked up in the subsequent backups increasing the size of incremental backups.

2. Oracle Fusion Middleware (OFM) is configured on your computer with incorrect settings. This could prevent the directory change rename after the full backup. This could also result in synthetic full backup failure.

3. Backups are performed from a Snap (hardware snap, QSnap, VSS snap) using recursive scan method with Check archive bit during backups option enabled. Selecting Check archive bit during backups picks up all the files from the snap for backup. FAT volumes and volumes with mount points that do not have an associated volume letter would also be picked up for backup.

As a workaround, change the scan method to Change Journal or disable Check archive bit during backups option in the Subclient Properties dialog box.

Can we filter the Page File from backup?

Yes. You can filter the Page File from backup.

Can we back up only those files that have been recently modified or created?

Yes. You can configure backups only for the data that has been modified or created after a specified date. This option is useful if you need to filter out data that was modified before a certain date.

For more details, refer to Configuring Backups for Recently Modified or Created Data.

How will I view the files that were skipped during backup?

Certain files found during scan phase might be missing during backup. By default, the backup job skips these missed files during backup so that these files are not counted as failed objects. However, if you do not want these missing files to be skipped during backup, enable nDoNotSkipMissingFilesOnBackup additional setting. Additionally, these missing files will be counted as failed objects.

WFS0020: Can I restore files with special characters in their names?

584 27c 10/04 17:53:05 50640 CVArchive::ReadBuffer() -PL_FS_OPEN_AFILE(2, 4, 259821) 584 27c 10/04 17:58:59 50640 FsRestoreNTObject::handleError() - Write data error = 5 net helpmsg 5 Access is denied.


No. You cannot directly restore a file or a folder that has special characters like square brackets([ ]) in their names. You can restore the parent directory in which these files or folders reside.

WFS0021: Why do encrypted files take longer time to backup?

Encrypted files take longer time to backup due to the processes used to back them up. Encrypted data has to communicate with the software that was used to encrypt the files. This communication happens throughout the backup process. Hence, the backup software has to provide a call back function in a different thread forthese encrypted files to be backed up thereby slowing down the backup process.

WFS0022: Why am I prompted to reboot the computer after performing a restore operation?

After a file system or a System State restore, you may be prompted to reboot the computer to which the data was restored. This is because the data that was attempted to be rebooted was in use or locked by another process.

In such cases, the following is observed:

1. The file is restored into the same directory. For example, filename.txt would be restored as ~filename.txt~ in the same directory.

2. An entry for this file is created in the PendingFileRenameOperations key in the registry.

At the end of the restore operation, the restore process will report to the CommServe that the system must be rebooted which in turn would display message in the CommCell Console to reboot the computer.

When the server is rebooted, Microsoft Windows operating system will overwrite the locked files with the temporary files created in the PendingFileRenameOperations registry key.

For more information on PendingFileRenameOperations, see Microsoft KB 181345.

For more information on a third party tool made by Microsoft that will show the pending files to be renamed, see Microsoft Windows Sysinternals.

Critical Components

Critical components are components that are essential and necessary for the operating system to come back alive after the restore of system state.

If a critical component fails during the backup of system state, the backup job fails with an error code as the backed up data is not sufficient for a restore of the operating system.

Cluster Database

Registry

System Info Archive


System Volume

Non-Critical Components

Non-Critical components are components that are part of system state but are not essential for the operating system to come back alive after the restore of system state.

If a non-critical component fails during the backup of system state, the backup job completes with an error code as the backed up data is sufficient for a restore of the operating system. However, the non-critical components do not get restored.

Active directory application Mode (ADAM)

BITS service

Certificate services

COM+ database

Content indexing catalogs

DDR explicit content

DFS replication services

DHCP

You may be prompted for a reboot while restoring System State components and the restore operation is not considered complete until the server is rebooted.

WFS0023: What are the critical and non-critical system state components on Windows operating system?

You may filter critical system state components from a backup operation. However, you cannot restore the server to the state in which it was at the time of backup thereby leading to a incomplete restore of the server and system state.


Disk quotas

Event logs


IIS

Metadata

NPS database

Offline files

One touch files

Remote storage database

RSM

Terminal service licensing

UDDI database

WMI database

WINS

For more information on system state, see Microsoft Articles on Backing Up and Restoring System State, Microsoft Backing Up and Restoring System State in Windows Server 2003 R2 and Windows Server 2003 SP1, and Backing Up and Restoring the Failover Cluster Configuration Using VSS.

How does the Optimized Scan enhance the scanning capabilities of an iDataAgent?

When you enable the Optimized Scan for a File System, a meta database is created. The meta database contains information about the files in the associated volume. This Optimized service constantly updates the databases to track file additions, volume additions, content update to files, etc. Journals from the FSF driver are used to keep track of the updates to each meta database.

What is the default Location of the Meta database?

On each volume, the meta database is created at the following location:

System Volume Information\HDPS\Data Classification

It is named as dc_<instance_number>.db

For example: On the C drive, it would be C:\System Volume Information\HDPS\Data Classification\dc_<instance_number>.db

You cannot relocate the database.

How to turn off the Optimized Scan?

Use the ServiceEnabled registry key to enable or disable the Optimized Scan monitoring threads for all volumes on a client computer as follows:

If you want to disable Optimized Scan for selected volumes, use the VolumeFilters registry key to provide the list of volumes as follows:

Scan Methods


2. Right-click the <Client> in which you want to add the registry key, and then click Properties.

3. Click the Registry Key Settings tab.

4. Click Add.

5. In the Name box, type ServiceEnabled.

6. In the Location list, type HKEY_LOCAL_MACHINE\Software\CommVault Systems\Galaxy\Instance<xxx>\Data Classification\Configuration

7. In the Type list, select REG_DWORD.

8. In the Value field, type 1 to enable or 0 to disable the data classification monitoring for all the volumes.

9. Click OK.


2. Right-click the <Client> in which you want to add the registry key, and then click Properties.

3. Click the Registry Key Settings tab.

4. Click Add.


How much hard disk space is consumed by the Metadata Database?

The meta databases created by Optimized scan method usually consume about 5% of the total space on the hard disk. Depending on the type of data and folder layout, the metafiles may consume additional space.

Does the backup include all the source files associated with a hard link?

If a subclient contains a hard link and the selected scan method is Change Journal, then only the first source file is included in the backup. However, if you select Optimized or Recursive Scan, all the source files associated with a hard link are included in the backup.

Can I change the Scan Method for a subclient?

Yes. You can change the scan method for a subclient. Before changing the scan method for a subclient, consider the following scenario:

If the scan method is optimized for FAT Volumes, UNC Paths, mount points to free spaces and you change to any other scan method, the the next incremental backup for the subclient will become a full backup.

If the the scan method is optimized for Whole Volume or Whole Volume (using Optimized Scan) and you change to the scan method optimized for FAT Volumes, UNC Paths, mount points to free spaces, the backup cycle will continue as it is.

How much disk space is required on a volume for the VSS shadow copy?

During a VSS backup, the free space needed on a volume for the shadow copy is related to the duration of the backup and the amount of changes being made to the data objects (files, databases) that are being backed up. VSS snapshots capture and copy disk blocks that are being changed by other processes while the backup for a particular object is running. If the backup runs longer, or there is a lot of disk activity (files or databases being changed). This causes VSS to copy more data blocks and therefore, use more disk space.

Why does the differential or incremental backup becomes a Full backup when VSS is enabled?

If you Use Scan Method Optimized for FAT Volumes, UNC Path, mount point to free spaces and the select the Check archive bit during backups option, then all backups by VSS on subclients will be converted to full backups. If you want to perform incremental or differential backup, you must use the Use Scan Method Optimized for Whole Volumes. If you want to Use Scan Method Optimized for FAT Volumes, UNC Path, mount point to free spaces scan, do not select the Check archive bit during backups option.

Can I use VSS to backup files on a virtual server?

Use of VSS on virtual servers controls the backup method for file system data only, not system state components; system state data is backed up by the physical node(s), not by the virtual server(s). Note that the physical cluster node will automatically filter all shared disk resources, and the virtual server will automatically filter all physical disk resources from backup operations.

When I am performing backup of a data, what happens to the system state component?

When you want to backup only data, ensure that the the Backup System State check box is not selected on the Content tab of the Subclient Properties dialog box. Now when you perform the backup for any such subclient, the VSS will filter any system state component from the backup data. VSS will be used for this operation even when Use VSS option is not selected on the General tab of the of the Subclient Properties dialog box.

Can I backup Response File Group Configuration on a Lync Server?

5. In the Name box, type VolumeFilters.

6. In the Location list, type HKEY_LOCAL_MACHINE\Software\CommVault Systems\Galaxy\Instance<xxx>\Data Classification\Configuration

7. In the Type list, select REG_DWORD.

8. In the Value field, type Drive Letter for the volume that you want to filter.

9. Click OK.

VSS

Lync Server


No. Response File Group Configuration does not get backed up when you perform the Lync Server backup. For more information about backing up Response File Group Configuration, refer to http://technet.microsoft.com/en-us/library/hh202170.aspx.

Can I Use restore By job option to restore the Lync server data?

No. The Restore by Job option is not supported for the Lync Server backup jobs. You must perform the browse and restore operation to restore the Lync server data.


Troubleshooting - Windows File System

WFS0001: Backup Failure while backing up Large Files or System Volumes

WFS0002: Backup Goes to pending state while backing up an unformatted volume and mount points

WFS0003: Backup Goes to pending state for Polyserve (Non-Microsoft Clusters)

WFS0004: Backup of subclient that contains only files and no folders

WFS0005: Completed with One or More Errors

WFS0006: Full backup of Lync Server when Incremental or Differential Backup is performed

WFS0007: Lync Server data and settings are not backed up

WFS0008: File System scan failed - there is nothing to backup

WFS0009: Failure of File System scan

WFS0010: Synthetic Full backup failed

WFS0011: Files appear corrupted

WFS0012: Potential Sparse File Corruption on Windows operating system

WFS0013: Incremental or Differential backups are of the same size as that of a Full backup

WFS0014: Data Protection Error: [Err:1450]"Insufficient system resources exist to complete the requested service"

WFS0015: Backup Failures on Windows 2008, Windows 2008 R2 or Windows 7

WFS0016: Backups may fail to backup Windows System State "Event Logs"

WFS0017: Backup Job Pending with error: "File Scan failed to write to dirchange file"

WFS0018: System State Backup Components Fails

WFS0019: VSS Errors

WFS0032: Skip Deleted or Missing Files During Backup

WFS0033: Contents are not backed up although the backup completes successfully

UFS:0002: Error registering Job with the Communications Service

UFS:0005 After an authentication failed error if a MediaAgent or Client cannot communicate with CommServe it will disable itself immediately

WFS0034 Windows Operating System Failures

Cause

When backing up large files and/or system volumes, the Windows memory pool resources may run low and the backup may fail with errors reported in the Windows Event Viewer and the iDataAgent logs.

Solution

Review the Microsoft documentation for increasing the maximum memory pool usage and paged memory pool size.

Symptom

The Event Viewer displays following message: Cannot scan <path>

Solution

Add the NSkipDirErrors Registry Key and set the value at 1 (or any value other than 0)

Symptom

The backup job for a Polyserve goes to pending state

Backup Restore

Table Of Contents

WFS0001: Backup Failure while backing up Large Files or System Volumes

WFS0002: Backup Goes to pending state while backing up an unformatted volume and mount points

WFS0003: Backup Goes to pending state for Polyserve (Non-Microsoft Clusters)


Solution

Exclude the following folders from the backup and anti-virus scan:

During Disaster Recovery, open up the Polyserve Configuration Utility and export the configuration to the node that was rebuilt. This will ensure complete synchronization prior to introducing a rebuilt node again into the matrix.

Cause

When a subclient contains only files and no folders, the backup can fail if you select Optimized Scan as the scan method.

Solution

When a subclient contains only files and no folders, always use Recursive Scan as the scan method.

Backup jobs from Windows File System iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

For subclient containing only system state backup:

Fails to backup critical component - the job status is failed

Fails to backup non-critical component - the job status is completed w/ one or more errors

For subclient containing system state backup along with File system data:

Failure to backup critical component - marks the job as completed w/ one or more errors, so the data can continue to backup.

Failure to backup non-critical component - marks the job as completed w/ one or more errors

When a subclient is configured for a Lync server, always a full backup of the data and settings is performed, irrespective of the backup type selected for the subclient.

The Lync server must be running when you perform backup of the subclient configured for the Lync server.

Cause

Synthetic full backup will fail with the error message File System scan failed - There is nothing to backup if the Check for deleted stubs option was enabled in the Advanced Backup options dialog box.

Solution

Make sure that the Check for deleted stubs option is not selected while initiating a synthetic full backup. To disable this option use the following steps:


2. Right click the subclient and point to Backup.

3. In the Backup Options for Subclient dialog box, select synthetic full option.

4. Click Advanced and make sure that the Check for deleted stubs option is not selected in the Advanced Backup options dialog box..

Cause

Backup operation will fail at the scan phase if you have OPSWAT Secure RAM disk software installed on your computer that is being backed up. This is because the virtual disk created by the OPSWAT Secure RAM disk software is not being identified as a RAM disk thereby causing the file system scan to fail.

For backup c:\program files\polyserve\matrixserver\conf\mounts For anti virus scans c:\program files\polyserve\matrixserver\conf

<Data Protection Suite install directory>/Base

WFS0004: Backup of subclient that contains only files and no folders


WFS0006: Full backup of Lync Server when Incremental or Differential Backup is performed

WFS0007: Lync Server data and settings are not backed up

WFS0008: File System scan failed - there is nothing to backup

WFS0009: Failure of File System Scan


Solution 1

The virtual disk created by the OPSWAT Secure RAM disk software must be excluded from the subclient content by adding the virtual drive to the list of filters. For more information on adding content to filters, see Configuring Filters for Backups.

Solution 2

Specify the drives that need to be backed up manually in the subclient content.

If an absolute path is given as the subclient content and the path does not contain any files/folders, then the full backup would complete successfully but the subsequent synthetic full backup would fail.

Backup files that are created by using the Windows Volume Shadow Copy feature are corrupted in Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2.

This is a Microsoft known issue, see Microsoft KB 2748349 for more information.

Symptom

Data corruption occurs on a computer operating on Windows 7 or Windows 2008 R2 when a sparse file undergoes random write stress, and the data in the sparse file is overwritten with 64 KB of zeros. This happens due to a rare condition in the NTFS file system driver. This behavior causes data corruption under heavy write stress for sparse files.

You may receive the following error codes:

The Tag Header for all logs will always return a NULL or =Blankspace value as follows:

For a restore or a synthetic full job, the following errors would appear in CVD.log on the MediaAgent

For an Auxiliary Copy job, the following errors would appear in AuxCopy.log on the MediaAgent

WFS0010: Synthetic Full backup failed

WFS0011: Files appear corrupted

WFS0012: Potential Sparse File Corruption on Windows operating system

Error Code 9:30

[...]:Remote system [...]. The socket is in an invalid state [...] for desired action

Error Code 13:127

Error occurred while processing chunk [...] in media [...] for storage policy [...] copy [...]: Backup job [ ... ]. Data read from media appears to be corrupted.

Error Code 62:469

Data read from media appears to be corrupted

8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] **ERROR** DataMoverSingleInstancer::ReadTagHeader: Failed to convert the tag header to Host byte order. Tag header got = 8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] The current Read offset into the chunk Physical 11602 Logical 0 8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Metadata file [F:\Backup\CV_MAGNETIC\V_1211796\CHUNK_5018060\CHUNK_META_DATA_5018060].8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Data file [F:\Backup\CV_MAGNETIC\V_1211796\CHUNK_5018060\SFILE_CONTAINER_001]. Version [2], SFile Number [1], Last Seek Offset [904877]8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Current data file offset [904973]

8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ]


Additional logs available on the MediaAgent

CVD.log

FSIndexedRestore.log

Solution

We recommend you to obtain the Microsoft hot fix for this issue. Refer to Microsoft KB 270881 to obtain the hotfix.

**ERROR** DataMoverSingleInstancer::ReadTagHeader: Failed to convert the tag header to Host byte order. Tag header got = 8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] The current Read offset into the chunk Physical 11602 Logical 0 8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Metadata file [F:\Backup\CV_MAGNETIC\V_1211796\CHUNK_5018060\CHUNK_META_DATA_5018060].8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Data file [F:\Backup\CV_MAGNETIC\V_1211796\CHUNK_5018060\SFILE_CONTAINER_001]. Version [2], SFile Number [1], Last Seek Offset [904877]8484 2368 07/12 14:23:57 549154 7225349-7257065 [DM_BASE ] Current data file offset [904973]

1896 164 07/25 08:53:02 1007062 #--1 [DM_BASE ] Opening the Chunk =6322105, ArchFileId = 1008183, FileMarker=623, ArchFilePhysSizeInChunk=2146389541 VolId=7445251896 164 07/25 08:53:02 1007062 #--1 [MEDIAFS ] Magnetic Mount Path :- KBRemaning 560559808, Minimum space MB to be left [2048], maximum space MB to be filled [-1]1896 164 07/25 08:53:02 1007062 #--1 [MEDIAFS ] RealMagneticFS Opened file1896 160c 07/25 08:53:16 1007062 [UNCOMPRESS ] #UNCOMPRESSION ERROR! rc = -3 BN = 0 Scheme = 0 InputSize: 62974 UncompressedSize: 63392 ExpectedSize: 633921896 164 07/25 08:53:26 ####### [CVD ] STOP_PL Control Message Received 0 (Pipeline Thread self-terminated)1896 1408 07/25 08:53:26 1007062 [DECRYPT ] STOP_PL while allocating a buffer1896 164 07/25 08:53:26 1007062 [FSRESTHEAD ] [FsRestoreHead::stopPipeline]: Received STOP_PL control message. Bailing out…

1896 1df8 08/10 08:33:35 #######[ NULL] invalid tag header 1896 1df8 08/10 08:33:35 1016869 #--1 [DM_BASE ] ERROR DataMoverBase::Read: Failed to convert the tag header to Host byte order. Tag header got = 1896 1df8 08/10 08:33:35 1016869 #--1 [DM_BASE ] The current Read offset into the chunk Physical 1077840646652 Logical 1183781091958 1896 1df8 08/10 08:33:35 1016869 [DM_READER ] DataReader::Read: Failed to READ data from ARCHIVE FILE [1010462] COPY [134]. PHYSICAL LEN = [96] LOGICAL LEN =[0]. TAGHEADER = [1]1896 1df8 08/10 08:33:35 1016869 [FSRESTHEAD ] Encountered error when reading data from the media.

3164 1250 07/25 08:53:32 1007062 CVRestoreFiles::restoreFile() - Sending FSR_MSG_OPEN_ARCHIVE (2,18,1009296)3164 1250 07/25 08:53:32 1007062 CVRestoreFiles::sendMsgToClient() - CVSession::sendMessage() returned error [900001e=[CVSession::sendMessage]: Remote system [...]. The socket is in an invalid state [CVS_STATE_INIT] for desired action.]3164 1250 07/25 08:53:33 1007062 RSTCALLBACK: error restoring '\D:\Users\...\My Documents\DOCUMENTS\documents for publication\filename' afile id (2,18,1009296) offset hi 0 lo 11733552863164 1250 07/25 08:53:33 1007062 RSTCALLBACK: cannot restore node 1571547 version 0 afile 352 offset 11733552863164 1250 07/25 08:53:33 1007062 0 RESTORE: ERROR: Restore Failed for ...\Windows File System\defaultBackupSet\D Users(CommCell:AppNum).3164 1250 07/25 08:53:33 1007062 0 RESTORE: Source path [\] ([1] of [1]).

WINFS:0013 Incremental or Differential backups are of the same size as that of a


Symptom

When an incremental or differential backup is performed followed by a full backup, you may notice that the size of the Incremental or Differential backup is same as that of the Full backup.

Solution

This issue may be due to the Anti-Virus software installed on the client computer. Contact your Anti-Virus vendor to resolve this issue and check if there are any specific configurations to be set on your client computer.

If Symantec is installed on your client computer, see Symantec Endpoint Protection scan causes incremental backups to perform full backups for more information.

Symptom

Data protection jobs may run slowly, fail, or fail to backup some large file with the following errors.

From clbackup.log on the client server.

Operating system Application Event Logs (When you use a third party backup software that uses NT Backup API)

Solution

This is a Microsoft known issue. Refer to Microsoft KB article 304101 for more information.

Additionally, you can also look at Microsoft KB articles 2002606 and 967351 for more details.

Symptom

The following errors may be generated during the backup operation:

From CommCell Console Event Viewer or Job Details dialog box:

From the FileScan.log file on the Client server:

Full backup

WINFS0014: Data Protection Error: [Err:1450]"Insufficient system resources exist to complete the requested service"

Error [1450] during BackupRead. Err:[1450] Insufficient system resources exist to complete the requested service.

ERROR 1130: Not enough server storage is available to process this command.

ERROR 1450: Insufficient system resources exist to complete the requested service.

ERROR 1450: / hex 0x5aa ERROR_NO_SYSTEM_RESOURCES

Operating system error 1450 Insufficient system resources exist to complete the requested service.

Write on "device" failed, status = 1450

ERROR 1130: Not enough server storage is available to process this command.

ERROR 1130 / hex 0x46a ERROR_NOT_ENOUGH_SERVER_MEMORY

Backup or restore operation terminating abnormally.

WINFS0015: Backup Failures on Windows 2008, Windows 2008 R2 or Windows 7

Error Code 17:55: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan. FileScan Error:Cannot scan [\]


Once the FileScan.log shows the above error, then system state VSS snap is started for the file scan and the following error message is seen when the files scan or backup fails.

You may observe the following in the logs:

Microsoft Application or System Event Logs may display the following Event IDs:

Solution

CsVolumeList::Add() - VolGUID path (\\?\Volume{0c022041-ff03-11de-8b2f-806e6f6e6963}\Boot) too long. Truncating.GetVolumeMountPointsForVolumeGUID() - Found no path matching vol name [\\?\Volume{0c022041-ff03-11de-8b2f-806e6f6e6963}\].CsVolumeList::Add() - Not able to get volume mount points for vol [\\?\Volume{0c022041-ff03-11de-8b2f-806e6f6e6963}].CsVolumeList::Add() - Added [\\?\VOLUME{0C022041-FF03-11DE-8B2F-806E6F6E6963}\] to volume list

The cause for the failure is that VSS is unable to create a SNAPSHOT of the volume identified.

CsSnapRequestor::StartSnapshotSet() - Starting a new Snapshot SetEntering [CsVssBackupComponents::StartShadowSet]CsSnapRequestor::StartSnapshotSet() - Created shadow set e4875fdb-5caa-48ed-abfc-da5a3cb34950Entering [CsSnapRequestor::AddVolumesToSnapshotSet]CsSnapRequestor::AddVolumesToSnapshotSet() - Volume [\\?\VOLUME{0C022041-FF03-11DE-8B2F-806E6F6E6963}\] not supported by providerCall AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] - Code = 0x80320305, Description = Unknown errorCall CreateSnapshotSet() [FAILED, throwing CV exception] - Code = 0x80320305, Description = Unknown errorEntering [CsSnapRequestor::BackupComplete]Entering [CsSnapRequestor::DeleteFolderMetadata]CsSnapRequestor::DeleteFolderMetadata() - Not attempting to delete folder metadataEntering [CsSnapRequestor::DeleteSnapshot]CsSnapRequestor::DeleteSnapshot() - Shadow not created!CsSnapRequestor::BackupComplete() - Deleted snapshot setCsSnapRequestor::BackupComplete() - Aborting backup!Entering [CsVssBackupComponents::Delete]Entering [CsVssBackupComponents::FreeWriterMetadata]CsVssBackupComponents::FreeWriterMetadata() - Free'd all writer metadataFindWorkThreadWrapper::createVssSnap() - Not using writers for backupFindWorkThreadWrapper::ProcessSysStateComp() - Failed to create a VSS snapshot and it is required to run a system state backup. Failing the scan

Event IDs 12290 and 16387 are logged when system state backup fails on a Windows Server 2008-based computer. Log Name: Application Source: VSS

Event ID: 12290 Level: Warning Description: Volume Shadow Copy Service warning: ASR writer Error 0x80070001. hr = 0x00000000.Log Name: Application Source: SPP

Event ID: 16387 Level: Error Description: Shadow copy creation failed because of error reported by ASR Writer. More info: Incorrect function. (0x80070001).


Make sure that the drive that hosts the snapshots has sufficient space to post the new snapshot.

To resolve this issue,

1. Verify if there is an Active, Primary Partition that is not an NTFS file system and does not have a Volume drive letter assigned.

The following image is an example of an Active, Primary Partition that is not NTFS (New Technology File System).

Run mountvol command from the Command Prompt at the administrator level. This will list the volumes available and their names.

You can also view this list under the registry key located at HKLM\System\MountedDevices.

Look for a data set without a matching\DosDevice\Volume drive letter. The following is an example of a data set without a matching DosDevice\Volume drive letter:

Review this with your Server Vendor or Server Image Provider to determine what volume is this for.

If this does not resolve the issue, refer to Microsoft KB 968128 for more information.

Symptom

In hds software where VSS is used to backup the server, you may observe the following errors:

From CommCell Console:

From Clbackup.log

\\?\Volume{0c022041-ff03-11de-8b2f-806e6f6e6963

WFS0016: Backups may fail to backup Windows System State "Event Logs"

Error Code: [82:128]Description: The job is pending because: Network receive failed: The network connection was lost unexpectedly.

FsBackupTw::BackupComponentTemplate[Event Logs]() - Backing up [Event Logs]


Error 9000012 is a hds Software Hex error which corresponds to the following error:

Solution

To resolve this issue, see Microsoft KB article 970219.

Additionally, refer to Microsoft Blog OpsMgr 2007: Backup programs may fail to backup the event log when the 64-bit agent is installed for more information.

Symptom

Backup job goes to a pending state with the following error:

Solution

This issue is caused by a problem writing to the Job Results directory on the client computer.

1. From the CommCell Console, navigate to Client Computers | <Client>.

2. Click Advanced.

3. Click Job Configuration tab. The Job Results Directory box contains the path where the job results files are listed.

Make sure that the given path exists.

FsBackupTw::BackupComponentTemplate[Event Logs]() - ---->>>Entering [CDefaultWriterBackup::Backup]Entering [CDefaultWriterBackup::BackupWriter]Entering [CDefaultWriterBackup::GatherFlags]Entering [CDefaultWriterBackup::GatherWriterExcludes]CDefaultWriterBackup::GatherWriterExcludes() - Exclude file count [1] for writer [eee8c692-67ed-4250-8d86-390603070d00].CDefaultWriterBackup::BackupWriter() - Event Logs has 7 files, 0 logs, and 0 databasesEntering [CWinBackup::IsFileExcluded]CWinBackup::IsFileExcluded() - Backup file [`g] matches writer exclude file pattern.CDefaultWriterBackup::BackupFileDesc() - Skipping filtered file [C:\WINDOWS\system32\config\AppEvent.Evt].Entering [CWinBackup::IsFileExcluded]CWinBackup::IsFileExcluded() - Backup file [ ^] matches writer exclude file pattern.CDefaultWriterBackup::BackupFileDesc() - Skipping filtered file [C:\WINDOWS\System32\Config\Internet Explorer.evt].CsTools::IsVolumeDevicePathForm() -Invalid arguments.** CVSession::sendBytes(...) iSocketMember=860 send failed, err=[1][10093][Either the application has not called WSAStartup, or WSAStartup failed.].

** CVSession::sendMessageInt(...):- RemoteHost=ServerName.- RemoteProcess=AppMgrSvc.exe.- sendBytes() failed. Error=9000012.

** CVSession::disconnect (void)- RemoteHost=ServerName.- RemoteProcess=AppMgrSvc.exe.- sendMessageInt CVS_PM_DISCONNECT_REQ failed. Error=9000012.

Error Code 9:18 []:Remote system []. The socket send failed. Error returned [=].

WFS0017: Backup Job Pending with error: "File Scan failed to write to dirchange file"

Error Code 17:40 File Scan failed to write to dirchange file [...] . Possible reasons nonexistent path/file, hardware problems or full disk.


4. Login to the Client Computer and verify if the current free space available is sufficient for hosting the Job Results Directory.

For more information on how to determine the free space for Windows 2008 and Windows 2008 R2, see Microsoft KB article 2021748.

5. Navigate to the path provided in the Job Results Directory box and check the size of the JobResults folder.


6. Explore the options required to reduce the space or move JobResults folder to another location.

WMI

Symptom

Backup of WMI component may fail during system state backups and you may observe the following errors:

CommCell Console

clbackup.log

Resolution 1

To resolve the hang, run the following command to register the system performance libraries with WMI.

Windows 2008, Windows 2008 R2, type the following command:

For more information on this command, refer to Microsoft KB article 2554336.

Windows 2003, Windows XP, and Windows 2000, type the following command:

For more information on this command, see Microsoft article wmiadap.

WFS0018: System State Backup Components Fails

Error Code 6:64 System State Backup of component [...] failed.

<--- ADDING COMPONENT ---> 5600 1474 07/08 09:45:31 {Job ID} Entering [CWinBackupJob::AddComponent] 5600 1474 07/08 09:45:31 {Job ID} Entering [CWmiBackup::GatherActiveStatus]

WINMGMT.EXE /RESYNCPERF

WINMGMT.EXE /RESYNCPERF


Windows 2000 and NT, type the following command:

For more information on this command, see Microsoft article winmgmt.

For more information on how to build the WMI repository and Performance Counter Library values, see Rebuilding the WMI Repository and Microsoft KB article 300956.

Resolution 2

Filter the WMI data from the backup content if it is not necessary to be backed up.

For more information on how to filter system state components from a backup, see Filtering System State Components from a Backup.

RSM

Symptom

Backup of RSM component may fail during system state backups and you may observe the following errors:

CommCell Console

Event Viewer

You may also receive the following error:

clbackup.log

Reports

To verify the failed component using reports, follow the steps given below:

1. Open CommCell Console.

2. On the CommCell Console menu bar, select the Reports tab and then click Summary.

3. The Report Selection dialog box appears with Data Management selected by default.

4. Click Selection tab. Select Failure Reason and Failed Objects.

5. Click Run.

Look for Files failed to backup to determine the failed files.

Solution

Disable RSM service or filter RSM component from the system state backup.


Content Indexing Catalogs

Symptom

Backup of Content Indexing Catalogs may fail during system state backups and you may observe the following errors:

CommCell Console

winmgmt /resyncperf <winmgmt-service-process-id>

Completed w/ one or more errors

System State Issue: At least one non-critical component has failed, see client logs for details. see clbackup.log for details.

Error Code 6:64:System State Backup of component [] failed.

<--- COMPONENT BACKUP REPORT ---> Component Type Status --------- ---- ------RSM SYSTEM SERVICE FAILED


Event Viewer

clbackup.log

Reports






5. Click Run.


Solution

To resolve this issue, restart the Indexing Service and make sure that the existing Catalogs are configured properly.

To verify indexing service configuration on computer, navigate to Computer Management | Services and Applications | Indexing Service.

NPS

Symptom

System state backup may fail with the following error:

Resolution 1

To resolve this issue, make sure that the NPS (Network Policy Server) components are installed and actively used. If NPS is used actively, then you need to restore the database as it is a critical component of System State backup. For more information on critical and non-critical components on Windows operating system, see What are the critical and non-critical system state components on Windows operating system?

For more information, see Microsoft KB article 949470.

Resolution 2

Filter NPS (Network Policy Server) components from system state backup.


Additionally, you may also refer to the following references:

Network Policy Server (NPS Database)

Microsoft KB article 951005

Microsoft KB article 2182466

Configure Log File Properties



Error Code 6:64:System State Backup of component [] failed.

<--- COMPONENT BACKUP REPORT ---> Component Type Status --------- ---- ------RSM SYSTEM SERVICE FAILED

Error Code 6:64System State Backup of component [NPS Database] failed.


1-Touch Files

Backup of 1-Touch files may fail during system state backups and you may observe the following errors:

CommCell Console

Event Viewer

clbackup.log

Reports






5. Click Run.


Solution 1

Filter 1-Touch components from system state backup.


Solution 2

Make sure that the system state backup is not failing due to operating system error. The primary Windows component that causes 1-Touch failure is Windows VDS Basic Provider. The following is an example of an error that appears in Windows event logs:



Error Code 28:243Failed to collect disk, volume or partition information for 1-Touch Backup . 1-Touch recovery cannot be done. See client logs for details.

Error Code 6:64:System State Backup of component [One Touch Files] failed.

Error Code: 6:66System State Backup of component [One Touch Files;] failed[OneTouchError:Failed to backup 1-Touch file].

Error Code 6:69:OneTouchError:Failed to backup 1-Touch file

<--- COMPONENT BACKUP REPORT ---> Component Type Status --------- ---- ------One Touch Files ARCHIVE SUCCESS

Log Name: System Source: VDS Basic Provider Date: date timeEvent ID: 1 Task Category: None


Cluster Database

Symptom

System state backup of Cluster Database component may fail with the following errors:

CommCell Console

clbackup.log

Reports






5. Click Run.


Solution

Follow the steps given below to resolve this issue:

1. Make sure that the Use VSS options is enabled in the General tab of the Subclient Properties dialog box prior to performing system state backup.

2. Make sure that \\computername\ClusterLegacyBackup share is accessible from the node that is being backed up.

3. Make sure that the correct computer name and is given in the UNC path and that it resolves to the correct IP address.

4. If the client being backed up is a virtual machine, disable system state backups for that machine.

5. Make sure that the Cluster services are up and running.

Additional Information

System state backups are capable of backing up both the active and passive nodes in a cluster database. When a system state backup is initiated, the active owner generates a dump of the Cluster database and places it on a network share. This dump is then retrieved and backed up by the node that performs the backup.

Cluster Database backup failures are caused mainly due to an inability to access these shares during the backup. You will observe the following error in clbackup.log:

Level: Error Keywords: Classic User: N/A Computer: computer nameDescription: Unexpected failure. Error code: 490@01010004

Error Code 6:64System State Backup of component [Cluster Database] failed .

Error Code 28:105System State Issue: At least one non critical component has failed, see clbackup.log for details.

<--- COMPONENT BACKUP REPORT ---> Component Type Status --------- ---- ------Cluster Database SYSTEM STATE FAILED

For cluster computers operating on Windows 2003, you can use only Legacy method to backup the cluster component.

<--- STARTING BACKUP OF Cluster Database ---> Cluster dump at [\\computername\ClusterLegacyBackup] and backup path [C:\Program Files\{Software Dir}\Data Protection


Error codes 52, 53 and 1214 are all connectivity errors.

System Protected Files on Windows 2008 Server

Symptom

System state backup performed on Windows 2008 servers may fail to backup System Protected Files.

This error is caused by Access Denied Errors during backup for Cryptographic Service. You may observe the following errors:

CommCell Console

clbackup.log

filescan.log

Suite\iDataAgent\FileSystemAgent\2\123\clusterdb] [::clusterBackup]: Name: NAME ::clusterBackup() - BackupClusterDatabase call failed with following error code [51] <--- ENDING BACKUP OF Cluster Database - [FAILED] --->

Error Code 17:55:Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.

FsBackupTw::BackupComponentTemplate[System Protected Files]() -FsBackupTw::BackupComponentTemplate[System Protected Files]() -Backing up [System Protected Files]FsBackupTw::BackupComponentTemplate[System Protected Files]() -

Entering [CSystemProtectedFilesWriterBackup::Backup]Entering [CDefaultWriterBackup::Backup]Entering [CDefaultWriterBackup::BackupWriter]Entering [CDefaultWriterBackup::GatherFlags]Entering [CDefaultWriterBackup::GatherWriterExcludes]Entering [CsVssBackupComponents::CsVssBackupComponents]Entering [CsVssBackupComponents::Delete]Entering [CsVssBackupComponents::GetWriter]Entering [CsVssBackupComponents::GetWriter]Call GetWriter(writerGUID, pWriter) [FAILED, throwing CV exception] - Code=0x80004005, Description=E_FAILCDefaultWriterBackup::GatherWriterExcludes() -vss.GetExcludeFiles(writerGuid, lExcFiles) - [FAILED] 0x80004005Entering [CsVssBackupComponents::~CsVssBackupComponents]Entering [CsVssBackupComponents::Delete]CsVssBackupComponents::Delete() - Assigned set, so not freeing metadataCDefaultWriterBackup::BackupWriter() - GatherWriterExcludes(args, writerGuid) - [FAILED] 0x80004005FsBackupTw::BackupComponentTemplate[System Protected Files]() -FsBackupTw::BackupComponentTemplate[System Protected Files]() -Failed to backup System Protected FilesFsBackupTw::BackupComponentTemplate[System Protected Files]() -FsBackupTw::DoSystemStateBackup() - Critical error detected in component [System Protected Files]. Failing system state backupPrintReport() - Component Method Status

Entering [CSystemProtectedFilesWriterBackup::Backup]Entering [CDefaultWriterBackup::Backup]Entering [CDefaultWriterBackup::BackupWriter]Entering [CDefaultWriterBackup::GatherFlags]Entering [CDefaultWriterBackup::GatherWriterExcludes]Entering [CsVssBackupComponents::CsVssBackupComponents]Entering [CsVssBackupComponents::Delete]Entering [CsVssBackupComponents::GetWriter]Entering [CsVssBackupComponents::GetWriter]Call GetWriter(writerGUID, pWriter) [FAILED, throwing CV exception] - Code=0x80004005, Description=E_FAILCDefaultWriterBackup::GatherWriterExcludes() -vss.GetExcludeFiles(writerGuid, lExcFiles) - [FAILED] 0x80004005Entering [CsVssBackupComponents::~CsVssBackupComponents]Entering [CsVssBackupComponents::Delete]


Application or Event logs

Solution

These errors appear more than once if they are caused by a permission issue or when any of the system writers is missing from the list of writers.

These writers are required to backup System Protected Files.

Run the following command and review the output.

For more information, see Microsoft article Vssadmin.

The output on Windows 2008 server would look similar to the one given below.

CsVssBackupComponents::Delete() - Assigned set, so not freeing metadataCDefaultWriterBackup::BackupWriter() - GatherWriterExcludes(args, writerGuid) - [FAILED] 0x80004005

Product: Windows Operating System ID: 512 Source: Microsoft-Windows-CAPI2 Version: 6.0 Symbolic Name: MSG_SYSTEMWRITER_INIT_FAILURE Message: The Cryptographic Services service failed to initialize the VSS backup "System Writer" object.%1.

Product: Windows Operating System ID: 513 Source: Microsoft-Windows-CAPI2 Version: 6.0 Symbolic Name: MSG_SYSTEMWRITER_ONIDENTITY_FAILURE Message: Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.%1.

Log Name: ApplicationSource: Microsoft-Windows-BackupEvent ID: 517Level: ErrorDescription:Backup started at '...date/time..' failed with following error code '2155348226' (System writer is not found in the backup.). Please rerun backup once issue is resolved.

vssadmin list writers > c:\vssadmin.txt

Writer Instance Id: {1754f85c-8bb4-4928-8b54-9536c984298c}State: [1] StableLast error: No error

Writer name: 'Registry Writer'Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}Writer Instance Id: {8c32dbe3-f944-4150-be3e-4bfc02b7295e}State: [1] StableLast error: No error

Writer name: 'COM+ REGDB Writer'Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}Writer Instance Id: {cd07fee3-a9f6-4424-b42e-2dad49d8a311}State: [1] StableLast error: No error

Writer name: 'Shadow Copy Optimization Writer'Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}Writer Instance Id: {ba399c41-f034-40c4-904d-9ae102c8bb1c}State: [1] StableLast error: No error

Writer name: 'WMI Writer'Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}Writer Instance Id: {199b8675-695c-4c62-9a55-5230b31d69bc}State: [1] StableLast error: No error


For more information on system writers, see Microsoft KB article 2009272.

For Application or Event ID solutions, see Event ID 512 and Event ID 513.

For more information on missing system writers, see DPM 2007 Server 2008 System State Backup System Writer missing.

For more information on how VSS works, see How Volume Shadow Copy Works.

This is a collection of issues and resolutions of several VSS errors generated by Microsoft Windows operating system.

There are several VSS errors that generate the following errors:

CommCell Console

JobManager.log

Symptom 1

System state backup of an active partition that is not NTFS formatted can result in backup failure.

Resolution 1

See Backup Failures on Windows 2008, Windows 2008 R2 or Windows 7 for more information.

Symptom 2

The following errors appear when the writers are in a bad or missing state.

Writer errors

Writer name: 'BITS Writer'Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}Writer Instance Id: {6a8ac8d7-c598-4efd-913b-971148e89500}State: [1] StableLast error: No error

WFS0019: VSS Errors

Error Code 17:55Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.

Scheduler Set pending cause [Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.]::Client [server name] Application [FileScan] Message Id [285212727] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].Scheduler Phase [Failed] message received from [server name] Module [FileScan] Token [37376:4:1] restartPhase [0]JobSvr Obj Phase [4-Scan] for Backup Job Failed. Backup will continue with phase [Scan].

Writer name: 'System Writer'Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}Writer Instance Id: {a9e9ad80-b17f-43fc-abde-693530722a5f}State: [9] FailedLast error: Timed out

Writer name: 'WMI Writer'Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}Writer Instance Id: {3ded1ea5-65c9-4e2b-bc0a-3064690a3eea}State: [9] FailedLast error: Timed out

Writer name: 'Cluster Database'Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}Writer Instance Id: {448f854c-ed09-439e-aeae-0e35e952ddab}State: [5] Waiting for completionLast error: No error


FileScan.log

Resolution 2

Use writers.txt file to determine the writer causing the problem. For more information, see System Protected Files on Windows 2008 Server.

Symptom 3

This issue is mainly caused by a Diskshadow with a malformed path. For example, the following are registry keys available at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services where the file path is malformed.

Filelist.txt

FileScan.log

CsSnapRequestor::GatherWriterStatus() - Gathering writer status After DoSnapshotSet... CsSnapRequestor::GatherWriterStatus() - 10 writers respondedSTABLE status for writer 'Task Scheduler Writer'. code S_OKSTABLE status for writer 'VSS Metadata Store Writer'. code S_OKSTABLE status for writer 'Performance Counters Writer'. code S_OKFAILED_AT_FREEZE status for writer 'ASR Writer'. code VSS_E_WRITERERROR_TIMEOUTCsSnapRequestor::GatherWriterStatus() - Signaling bad state returned for writer [ASR Writer] engaged in backup.FAILED_AT_FREEZE status for writer 'System Writer'. code VSS_E_WRITERERROR_TIMEOUTCsSnapRequestor::GatherWriterStatus() - Signaling bad state returned for writer [System Writer] engaged in backup.FAILED_AT_FREEZE status for writer 'Shadow Copy Optimization Writer'. code VSS_E_WRITERERROR_TIMEOUTFAILED_AT_FREEZE status for writer 'COM+ REGDB Writer'. code VSS_E_WRITERERROR_TIMEOUTCsSnapRequestor::GatherWriterStatus() - Signaling bad state returned for writer [COM+ REGDB Writer] engaged in backup.WAITING_FOR_BACKUP_COMPLETE status for writer 'Registry Writer'. code S_OKWAITING_FOR_BACKUP_COMPLETE status for writer 'Cluster Database'. code S_OKFAILED_AT_FREEZE status for writer 'WMI Writer'. code VSS_E_WRITERERROR_TIMEOUTCsSnapRequestor::GatherWriterStatus() - Signaling bad state returned for writer [WMI Writer] engaged in backup.Call GatherWriterStatus("After DoSnapshotSet") [FAILED, throwing CV exception] - Code = 0x80004005, Description = E_FAILEntering [CsSnapRequestor::DeleteFolderMetadata]CsSnapRequestor::DeleteFolderMetadata() - Not attempting to delete folder metadataCall DoShadowSet() [FAILED, throwing CV exception] -Code = 0x80004005, Description = E_FAILCall CreateSnapshotSet() [FAILED, throwing CV exception] -Code = 0x80004005, Description = E_FAILEntering [CsSnapRequestor::BackupComplete]

- File List: Path = c:/progra~2/plixer~1\cgi-bin, Filespec = eventlogd.exe - File List: Path = archivemanagerremoteinstaller, Filespec = remoteinstallerservice.exe - File List: Path = c:/program files (x86)/ibm_ds/ibmstoragemanagerprofiler server\bin, Filespec = tomcat5.exe - File List: Path = c:\windows\\systemroot\system32\drivers, Filespec = lsi_sas.sys - File List: Path = \systemroot\c:\windows\system32, Filespec = svchost.exe

316 440 07/03 12:48:04 42346 CsSnapRequestor::AddVolumesToSnapshotSet() - Call m_vss->IsVolumeSupported(m_shadowProvider.GetProvider(), vol, &bSupported) [FAILED, throwing CV exception] - Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND316 440 07/03 12:48:04 42346 CsSnapRequestor::CreateSnapshotSet() - Call AddVolumesToSnapshotSet(ids) [FAILED, throwing CV exception] - Code = 0x80042308, Description = VSS_E_OBJECT_NOT_FOUND


Resolution 3

1. Use shadow.txt to check for incorrect statements in the File Path section.

2. Correct the malformed paths registry keys. Make sure to contact the Vendors owning the files as their installation has caused the malformed path.

For example:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\servicesHKEY_LOCAL_MACHINE/SOFTWARE\Wow6432Node

Any path that has a / instead of \ does not conform to Windows LFS path standard. When the system writer identifies any malformed path, it cannot quiesce the file system for the VSS provider to take the snapshot.

Symptom 4

The following errors appear due to space issues with the Volume Shadow Service.

Server operating system Event Log File

FileScan.log

Resolution 4

Follow the steps given below to resolve this issue.

1. Open My Computer on the client computer.

2. Right-click on the <volume> and point to Properties.

3. Click on Shadow Copies tab.

4. Click Settings.

5. In the Storage area, select Maximum Size as No Limit or the set the space limit required for the VSS copies. You can also move the holding section to another volume.

TYPE] Error [TIME] 2011/09/23 09:03:04 [SOURCE] volsnap [COMPUTER] server name [DESCRIPTION] When preparing a new volume shadow copy for volume ?:, the shadow copy storage on volume ??: could not be located in non-critical space. Consider using a shadow copy storage volume that does not have any shadow copies.

23924: [PID] [Thread] 09/23 09:03:05[JobID] CsVssAsync::WaitUntilDone() - Async status returned code = 0x8004231f, Description = Unknown status.23924: [PID] [Thread]09/23 09:03:05 [JobID] CsSnapRequestor::DoShadowSet() - Call asyncShadow.WaitUntilDone() [FAILED, throwing CV exception] - Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE23925: [PID] [Thread]09/23 09:03:05 [JobID] CsSnapRequestor::CreateSnapshotSet() - Call DoShadowSet() [FAILED, throwing CV exception] - Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE23926: [PID] [Thread]09/23 09:03:05 [JobID] CsSnapRequestor::Snap() - Call CreateSnapshotSet() [FAILED, throwing CV exception] - Code = 0x8004231f, Description = VSS_E_INSUFFICIENT_STORAGE


For Command Line, see Microsoft article Vssadmin add shadowstorage.

Symptom 5

When multiple VSS Providers are active on the server, you will notice the following in FileScan.log.

Cause

Run the following commands from the Command Prompt as an administrator for Windows 2008 and Windows 2008 R2 client computers.

For Windows 2003 run the following commands:

Description = VSS_E_UNEXPECTED_PROVIDER_ERRORFindWorkThreadWrapper::w2kRecurse(4276): -Debug-: "C:\Users\addmtool\AppData\Local\History" is a junction point for "C:\Users\addmtool\AppData\Local\Microsoft\Windows\History".Call CreateSnapshotSet() [FAILED, throwing CV exception] - Code = 0x8004230f, Description = VSS_E_UNEXPECTED_PROVIDER_ERROR Resolution 5

vssadmin list writers > c:\writers.txt

vssadmin list providers > c:\providers.txt

vssadmin list volumes > c:\volumes.txt

diskshadow /L c:\shadow.txtlist writers detailedexit

vssadmin list writers > c:\writers.txt

Mountvol > C:\moutvol.txt

VSSADMIN List SHADOWS > C:\Shadows.txt


Verify if the commands run from the command prompt display results similar to the following:

Volumes.txt

Writers.txt

Providers.txt

DiskShadow.txt

Resolution 5

These issues are caused mainly due to VSS Services not starting or running properly.

Follow the steps given below to resolve these issues:

1. Make sure that the following services are not disabled.

Microsoft Software Shadow Copy Provider

Remote Procedure Call (RPC)

Volume Shadow Copy

2. Check the Application and System event logs for VOLSNAP/VSS errors.

3. Check the Providers installed using the following command:

4. Check the status of writers using the following command:

If you are still unable to resolve this issue, contact Microsoft.

For more information, see Volume Shadow Copy Service, Volume Shadow Copy Service Operations for Windows 2008 R2, Volume Shadow Copy Service Operations for Windows 2008 R2.

Symptom 6

When multiple VSS Snap Providers are active on the server, you will notice the following in FileScan.log.

VSSADMIN List SHADOWSTORAGE > C:\ShadowStorage.txt

VSSADMIN list providers > C:\providers.txt

Error: Unexpected failure: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error: A Volume Shadow Copy Service component encountered an unexpected error.Check the Application event log for more information.

Error: Unexpected failure: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

DISKSHADOW> list writers detailed COM call "(*vssObject)->InitializeForBackup" failed. The last operation failed.- Returned HRESULT: 80042302- Error text: VSS_E_UNEXPECTED DISKSHADOW> exitriters detailed

VSSADMIN LIST PROVIDERS

VSSADMIN LIST WRITERS

Entering [CsSnapRequestor::DeleteFolderMetadata]


When you run the VSSADMIN PROVIDERS LIST from the command prompt, the output would be similar to the following:

Resolution 6

nUseVSSSoftwareProvider additional settings must be added on the Client computer which has multiple VSS Providers on it. If the client machine has more than one iDataAgent installed on it, then this additional setting must be created multiple times under the corresponding agents.

For more information on this additional setting, see nUseVSSSoftwareProvider.

Additional information

You may refer to the following links for more information.

Vssadmin List

DiskShadow List

Vssadmin list writers

Vssadmin list volumes

Vssadmin list shadows

Vssadmin list providers

Volume Shadow Copy Service Operations

Volume Shadow Copy Service for Windows 2008

Volume Shadow Copy Service for Windows 2008 R2

Troubleshoot VSS issues which occur with Windows Server Backup (WBADMIN) on Windows Server 2008 and Windows Server 2008 R2.

Volume Shadow Copy Service

Symptom

Backup fails with these error messages under the main error code 19:857.

Additional error messages seen from Events tab in the Backup Job Details window.

Filescan.log file on the client will show this error:

CsSnapRequestor::DeleteFolderMetadata() - Skipping delete of folder metadata.Call DoShadowSet() [FAILED, throwing CV exception] - Code = 0x80042306, Description = VSS_E_PROVIDER_VETOCall CreateSnapshotSet() [FAILED, throwing CV exception] - Code = 0x80042306, Description = VSS_E_PROVIDER_VETO

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool(C) Copyright 2001-2005 Microsoft Corp. Provider name: 'Microsoft Software Shadow Copy provider 1.0'Provider type: SystemProvider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}Version: 1.0.0.7 Provider name: 'Data ONTAP VSS Hardware Provider'Provider type: HardwareProvider Id: {ddd3d232-a96f-4ac5-8f7b-250fd91fd102}Version: 6. 3. 0. 4601

UFS0002: Error registering Job with the Communications Service.

19:210"Error registering job with the Communications Service."

17:2"File system scan Failed"

Failed to translate "servername" to an IP address. Host ignored.Find::impersonateUser()() - No user id found from the registry [VMName = ... ]. Trying getting it from the CS::GetSubclientDir() - The Subclient directory is [d:\Program Files\Hitachi Data Systems Systems\Galaxy\iDataAgent\JobResults\CV_JobResults\iDataAgent\FileSystemAgent]GetCommServerName() - CS name is [...]Overiding CommServer name [server name] with registry value


JobManager.log file on the CommServe will show this error:

From the logs these additional error codes are part of the message:

In the Filescan.log file on the client

Error message variations based on iDataAgent:

In the JobManager.log file on the CommServe

Error message variations based on iDataAgent/ MediaAgent/ or CommServe involved:

In the EvMgrC.log file:

[registry server name]JM Client CVBkpJobClient::init(): Initializing job object with token [...].CVJobCtrlClient::registerJob() CVD replied with a non-zero error code [1] for the job registration message. Error = [Failed to get host name for client [...] for job [...]]Init() - Error registering JOB with the Communications Service for JobID [...]Init() - registerJob failed. Returning failureCould not initialize job control.BKP CALLED COMPLETE (PHASE Status::FAIL), ... . Token [...]

Scheduler Set pending cause [Failed to get host name for client [...] for job [...]]::Client [...] Application [FileScan] Message Id [318767961] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].Scheduler Ignored pending cause [Insufficient information to start the job. Possibly mismatched version with CommServe or corrupted install.]::Client [...] Application [FileScan] Message Id [285212706] RCID [0] Reservation Id [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].Scheduler Phase [Failed] message received from [...] Module [FileScan] Token [...] restartPhase [0]AppManager JMAppMgr::getValidateArchiveIndexPhase() failed. Returning falseJobSvr Obj Phase [4-Scan] for Backup Job Failed. Backup will continue with phase [Scan].

30:98 Failed to initialize Job Control.

7:28 Could not initialize job control object.

39:37 Could not initialize job object.

17:34 Insufficient information to start the job. Possibly mismatched version with CommServe or corrupted install.

19:1033 Failed to get the host name.

19:104 Failed to get the target MediaAgent name for job [].

19:1102 Failed to get the MediaAgent name. Please verify that the MediaAgent version is compatible with the client version.

19:249 Failed to get the CommServe host name from the platform information.

16:3 [] on computer [] failed to start; Failed to get local host name.


For a restore job, you may receive this error in the clrestore.log file:

When testing connectivity to the client computer with issues make sure to test name resolution in the following communications paths:

CommServe to Client, and from Client to CommServe

CommServe to MediaAgent, and from MediaAgent to CommServe

Client to MediaAgent ,and from MediaAgent to Client

The error is caused by DNS name resolutions not functioning properly in all directions. DNS or equivalent Lookup and Reverse Lookup must be functioning.

Local Windows Server Resolver Cache on each computer in the environment must be checked and Hosts files must be reviewed.

Resolution

Check the configuration in the CommCell Console for the CommServe, MediaAgent and the Client with issues. Different phases of the backup or restore operations require reviewing different communications paths. Also, check the registry entries on the CommServe, MediaAgent and the Client.

The example below will cover the CommServe and the client computers.

1. From the CommCell Browser, right click the CommServe and click Properties. Check the CommCell Host Name.

2. From the CommCell Browser, right click the Client computer and click Properties. Check the Host Name and CommServe Host Name.

16:5 [] on computer [] failed to start. Host Name for this computer may not be configured properly.

23:84 Restore: Wrong parameters for the job. Possibly mismatched version with CommServe or corrupted install.


3. The registry on the CommServe (CS) will have two locations that show the CS Host Name when it also has a Client (CL) installed.

For the CommServe Name used by the Clients other then the CommServe Client the registry entry for sCSHOSTNAME is located under \HKLM\Software\Hitachi Data Systems Systems\Galaxy\Instance001\CommServe

For the CommServe with a Client (CL) File System iDataAgent installed, the name is hosted at this registry location.

Registry entry for wDefaultHostName is located under \HKLM\Software\Hitachi Data Systems Systems\Common


4. Now to get the information for the MediaAgent (MA) or the Client (CL), locate the MA or CL in the CommCell Browser window, right click, and then click Properties. On the General tab, the following will be displayed.

Client used as example here:

5. Now once the MediaAgent (MA) and/ or Client (CL) CommCell information is confirmed, go to the MA and/or CL and review the registry entries for the Name.

Client computer is used for example here.

To confirm the CL Host Name, check the registry on the CL for the entry wDefaultHostName located under \HKLM\Software\Hitachi Data Systems Systems\Common.


Now confirm the CommServe Hostname on the CL in the registry for the entry sCSHOSTNAME located under \HKLM\Software\Hitachi Data Systems Systems\Galaxy\Instance001\CommServe

For UNIX/ Linux based MA or CL, running the hds status command will display the CommServe (CS) name as it appears in the /etc/Hitachi Data SystemsRegistry/Galaxy/Instance001/CommServe folder. The .properties file at this location contains the setting.

6. Now that the CommServe Hostname and the Host Name are confirmed, first confirm DNS supports Lookup and Reverse Lookup for the names. If this is correct and communication works in all directions based on ping, ping -a and nslookup, retry the backup or restore operation.

If this does not resolve the issue then review the Name Management documentation to get the names matching in the environment.

If this does not resolve the issue then move to first using IP addresses between the CS, MA and CL instead of names.

If this fails to resolve the issue then use host file entries to populate the Resolver cache with the name translations.

Enter in this format

[[root@lx5 ~]# hds status--------------------------------- Instance001 ----------------[ General ]Version = 10(BUILD116) SP3aCommServe = ameba.id.locHome Directory = /opt/hds/BaseLog Directory = /var/log/hds/Log_FilesCore Directory = /opt/hdsTemp Directory = /opt/hds/Base/TempPlatform Type = 4Cvd Port Number = 8400EvMgrC Port Number = 8402[ Package ]1002/CVGxBase 10(BUILD116) = File System Core1101/CVGxIDA 10(BUILD116) = File System1112/CVGxDC 10(BUILD116) = Data Classification Enabler- Cache Root Directory = /opt/hds/iDataAgent/jobResults/cvdccache1113/CVGxFSF 10(BUILD116) = File System Filter Driver[ Physical Machine/Cluster Groups ]Display Name = doclx5- Client Hostname = doclx5- Job Results Directory = /opt/hds/iDataAgent/jobResults[root@lx5 ~]#


<IP Address> <Short Name> <FQDName>

Confirm the issue is resolved by running a backup or restore job and checking the Filescan.log, JobManager.log and clRestore.log files.

Symptom:

During Backup:

Error Code19:1327

Error Code 9:90

Error Code 40:52

Error Code 22:30

Error Code 19:1131

Error Code 19:1597

Error Code 7:77

Error Code 7:102

Error Code 7:111

UFS0005: After an authentication failed error if a MediaAgent or Client cannot communicate with CommServe it will disable itself immediately

Attempt start error: [...]

Authentication failed for host [...]. Network password does not match.

Failed to contact CommServe Services from the MediaAgent[...] during the start of the Data Transfer operation. Please check the network connectivity from this MediaAgent to the CommServe and make sure services are running on the CommServe.

Could not establish connection to [...] on attempt [...].

Waiting for the services on the client [...] to come online.

Failed to start phase [...] on [...] due to network error [...]. Will attempt to restart. Please check if this product's services are running on the remote host.

Unable to run [...] on the client. [CVSession::authenticateClient]:Remote system [FQDNservername]. Failed authentication returned from server.

Unable to run [...] on the client.

Unable to run [...] on the client. [...]

Error Code 9:36 [...]:Remote system [...]. Could not get the password from platform information or the database -authentication failed.

Error Code 9:37 [...]:Remote system [...]. Could not find the client password in the database - authentication failed.

Error Code 9:38 [...]:Remote system [...]. Failed authentication


During Restore:

Error Code 23:98

Additional Log Cuts:

From the JobManager.log file on the CommServe:

From the CVD.log file on the Client:

Resolution:

If the nChatterFlag additional setting is set to 1, normal Communication and Connection testing will work properly but communication between MediaAgent or Client and the CommServe will continue to fail.

returned from server.

Error Code 9:39 [...]:Remote system [...]. Failed authentication returned from client.

Error Code 9:40 [...]:Remote system [...]. Unexpected message type received [...=...] - authentication failed.

Error Code 9:41 [...]:Remote system [...]. Could not encrypt challenge string when connecting - authentication failed.

Error Code 9:42 [...]:Remote system [...]. Password received from client did not match the database password for that client - authentication failed.

Error Code 9:89 Authentication failed for host [...]. Could not find the client entry in database.

Error Code 9:90 Authentication failed for host [...]. Network password does not match.

Error Code 9:91 CVSession Authentication failed for host [...]. Password is not available on the host.

Seek failure happened

6956 2764 07/23 16:00:21 53303 Servant [---- SCHEDULED BACKUP REQUEST ----], taskid [84] Clnt[...] AppType[Windows File System][33] BkpSet[defaultBackupSet] SubClnt[default] BkpLevel[Incremental][2]6956 27dc 07/23 16:00:24 53303 Scheduler Phase [4-Scan] could not start on [CLFQDNservername] due to Network Failure

8000 1f64 07/25 13:14:33 ### Unable to resolve remote host_Disabled_CSFQDNServerName to any IP family: [1][11001][No such host is known.]8000 1f64 07/25 13:14:33 ### ** CVSsession::attach(ulPortArg):- RemoteHost=_Disabled_CSFQDNServerName. - RemoteProcess=. Port =65535,65535- getConnection() failed. Error=900004b.8000 1f64 07/25 13:14:33 ### ** CVSession::getClientPassword ():- RemoteHost=_Disabled_CSFQDNServerName.- RemoteProcess=JobMgr.exe.- commServerAttach (ePlatformTypeMember) failed. Error=900004b.8000 1f64 07/25 13:14:33 ### ** CVSession::replyAttach (PlatformType)- RemoteHost=CSFQDNServerName.- RemoteProcess=JobMgr.exe.- authenticateServer failed. Error=9000024.


NOTE: The core issue is the MediaAgent or Client realized it was getting nowhere trying to talk (authenticate) to the CS and stops talking by setting the nChatterFlag and other registry key changes. The cause of this type of behavior is outlined above but may also be caused by transient or extended CVD communication issues between elements of the CommCell and the CommServe.

To fix the issue, check the additional settings on the CommCell Components affected.

On Windows:

1. Check the nChatterFlag additional setting.

From the CommCell Browser, navigate to Client Computers.

Right-click the <Client> or <MediaAgent>, and then click Properties.

Click Advanced and then click Additional Settings tab.

Click Add.

In the Name box, type nChatterFlag.

The Category and Type fields are populated automatically.

In the Value box, type 0.

This enables communication to the CommServe.

Click OK.

2. Check the sCSHOSTNAME additional setting.




Click Add.

In the Name box, type sCSHOSTNAME.


In the Value box, if the current string value has _Disabled_ appended at the front of the string value, remove it to allow communication to the CommServe.

Click OK.

3. If there is a firewall between the MediaAgent or Client and the CommServe, check the nDISABLE_CVFWD additional setting.




Click Add.

In the Name box, type nDISABLE_CVFWD.



This enables controlled connection to the CommServe.

Click OK.

4. Use the SCM utility to restart Data Protection Suite services.

On UNIX:

It is recommended to stop Data Protection Suite services on the MediaAgent(s) and/or Client(s) before modifying additional settings.

1. Check the nChatterFlag additional setting.




Click Add.

In the Name box, type nChatterFlag.



This enables communication to the CommServe.

Click OK.


2. Check the sCSHOSTNAME additional setting.




Click Add.

In the Name box, type sCSHOSTNAME.


In the Value box, if the current string value has _Disabled_ appended at the front of the string value, remove it to allow communication to the CommServe.

Click OK.

3. If there is a firewall between the MediaAgent or Client and the CommServe, check the nDISABLE_CVFWD additional setting.




Click Add.

In the Name box, type nDISABLE_CVFWD.



This enables controlled connection to the CommServe.

Click OK.

4. Restart Data Protection Suite services.

5. Test Backups and Restores to confirm data protection has been restored.

Special Case Scenario:

There is a specific scenario where this resolution will not be able to resolve the issue until the pNET password mismatch is fixed.

Should the pNET password on the MediaAgent or Client not match the entry in the CommServe database:

1. Check the CVD.log on the MediaAgent or Client for these entries:

2. Check for a matching entry with same Date/Time stamp in the CVD.log file on the CommServe:

3756 d98 04/25 16:17:23 ### [ClientSessionWrapper::connectToCS] Error connecting to svc [AppManager network access] on CS. [150994982-[CVSession::authenticateClient]:Remote system [servernameFQDN]. Failed authentication returned from server.]3756 d98 04/25 16:17:23 ### ClientInterfaceNet::lookup() -[ClientSessionWrapper::connectToCS] Error connecting to svc [AppManager network access] on CS. [150994982-[CVSession::authenticateClient]:Remote system [servernameFQDN]. Failed authentication returned from server.]3756 d98 04/25 16:17:23 ### ::UpdateClientInfo() - Failed to do the client lookup for CLHostName3756 d98 04/25 16:17:23 ### ::UpdateClientInfo() - Session connect failed with error code 150994982 -[CVSession::authenticateClient]:Remote system [servernameFQDN]. Failed authentication returned from server., Generic error 1509950343756 d98 04/25 16:17:23 ### ::UpdateClientInfo() - Setting nChaterFlag to 1 to stop all communications3756 d98 04/25 16:17:23 ### ::UpdateClientInfo() - Setting nDISABLE_CVFWD to 1 to stop all communications3756 d98 04/25 16:17:23 ### ::UpdateClientInfo() - CS Host Name set to _Disabled_servernameFQDN to avoid any contact from this client to CS

4532 92c 04/25 15:08:33 ### EvSANVolMgr::DiscoverFLRSupportedApps() - CVSession::attach() to [ipaddress*CLHostName*8400*8402] returned error 90000264532 92c 04/25 15:08:33 ### ::sendResponse() - FAILED [Failed to connect to remote host [ipaddress*CLHostName*8400*8402].]3196 bc0 04/25 16:17:23 ### [CVD ] ** CVD_CVSESSION_ERROR: RemoteHost=ipaddress? Error replying to attach on socket: 900002a=[CVSession::authenticateServer]:Remote system


Symptom

If certain files are found during scan phase and are missing during backup, backup of these files would fail with the following errors. Also, these files would be counted as failed objects.

Resolution

Enable the nSkipFileNotFoundOnBackup additional settings to resolve this issue. When this key is enabled, backup job skips the missed files and these files are not counted as failed objects. Make a note that this key is applicable only for missing files and not for missing directories. Any missing directory found would be counted as an failed object.

Follow the steps given below to enable this additional setting:


2. Right-click the <Client> on which you want to add the additional setting, and then click Properties.

3. Click Advanced.


5. Click Add.

6. In the Name field, type nSkipFileNotFoundOnBackup.

7. The Category and Type fields are populated automatically.


9. Click OK.

Symptom

When a backup operation is performed on Windows 32-bit computers, some content may not get backed up although the backup job completes successfully with no errors.

Resolution

[ipaddress]. Password received from client did not match the database password for that client - authentication failed.

WFS:0032 Skip Deleted or Missing Files During Backup

ERROR_FILE_NOT_FOUND

ERROR_PATH_NOT_FOUND

WFS0033: Contents Are Not Backed Up Although the Backup Completes Successfully


This is a Microsoft Windows 2003/Windows XP known issue. Open and Close the registry key located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM.

For more information, see Microsoft KB 927389 and ANS1009W DRM FilesNotToBackup RC 13.

Symptom

Files backed up using VSS services and restored using Windows File System iDataAgent might be corrupted.

Cause

Data Protection Suite leverages Microsoft Windows Volume Shadow Copy services (VSS) to generate snapshots of the data residing on the client computer.

Resolution

Contact Microsoft to obtain hot fixes for this issue. For more information, see Microsoft KB article 2748349.

Additional information

For additional information, see Potential Sparse File Corruption on Windows operating system.

WFS0034: Operating System Service Failures


Troubleshooting - Windows File System

WFS0024: Error messages during Browse operation

WFS0025: Files prevented from overwriting

WFS0026: Cluster Services are not Started Automatically during Disaster Recovery

VMW0019:Recovering data associated with deleted clients and storage policies

WFS0027: Error during the Full System Restore of Windows Vista or Windows Server 2003

WFS0028: An unauthorized change was made to Windows. You must retype your Windows Service Product Key to activate the license

WFS0029: Files on the Single Instance Storage linked volumes appear corrupted after Restore


Updating Features and Roles on Windows Server 2008

Restore operation goes to a pending state

Unable to Open Encrypted Files After an Out-Of-Place Restore Operation

Distributed Component Object Model (DCOM) Component Appears Disabled after a Restore

WFS0031: BSoD Error after a Full Restore Operation

CC0008: Users have access to files and folders belonging to others users

When you are browsing the backup data, one of the following error condition can occur:

Symptom

Failure to connect the MediaAgent

Solution

Check the connectivity between MediaAgent and the client computer. Add the client host name and IP address in the host file on the MediaAgent.

Symptom

Index Cache Inaccessible

Solution

Check the connectivity between MediaAgent and the client computer. Add the client host name and IP address in the host file on the MediaAgent.

Cause

When a file is in use by the operating system or open with exclusive read access by an application, the file is locked and cannot be overwritten.

Solution

The system automatically restores the file with another file name within the same directory and records the instance in the Windows registry. These are restored automatically at the time when the computer is restarted.

These files can be viewed from the Restore Job Summary Report They have a "Needs Reboot" tag attached to it. They can be viewed in the Restore History from the CommCell Console. In order to view these files you need to select the Failed Objects check box in Job Summary Selection tab. These files are displayed as Skipped files.

Cause

If the cluster disks were repartitioned, a failure message may appear because the disk GUIDs for the quorum may have been changed.

Solution

Backup Restore

Table Of Contents

WFS0024: Error messages during Browse operation

WFS0025: Files prevented from overwriting

WFS0026: Cluster Services are not Started Automatically during Disaster Recovery


If the cluster service does not start, or if you see Event ID 1034 in the System Event Log, reference the KB 305793 and KB 280425 Microsoft Knowledge Base articles on http://support.microsoft.com/ to get the cluster service back online.

If the cluster service does not start automatically, start it manually in the service control manager.

Symptom

In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:

Deleted storage policy

Deleted client, agent, backup set or instance

Before You Begin

This procedure can be performed when the following are available:

You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.

Media containing the data you wish to recover is available and not overwritten.

If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:

IP Address Change license

CommCell Migration license

See License Administration for more details.

A standby computer, which is used temporarily to build a CommServe.

Resolution

Recovering Deleted Data

1. Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.

Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.

If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.

If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:

If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.

If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.

2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.

3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool - Getting Started for step-by-step instructions.)

4. Verify and ensure that the HDPS Client Event Manager HDPS Communications Service (EvMgrS) is running.

5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Changelicense and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.

6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

8. If you have additional data that was backed up after the disaster recovery backup and before the deletion of the entity, use the procedure described in Import Metadata from a Tape Media to obtain the necessary information.

9. You can now browse and restore the data from the appropriate entity.

Recovering data associated with deleted clients and storage policies

When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.


Symptom

During the Disaster Recovery of Windows Vista or Windows Server 2003, you may get the following error:

An unauthorized change was made to Windows

Solution

When rebuilding an entire computer, it is required that the Windows service pack and hotfixes in the backup are also applied on the target computer. The service pack on the target must always match the backup prior to a restore. To restore the hotfix from the backups, select the Overwrite Files check box on the Restore Options dialog box and then select the Unconditional Overwrite option.

Select this option if the source computer had Internet Explorer 8.0 and the target computer has Internet Explorer 7.0.

Symptom

During the Disaster Recovery of Windows Vista or Windows Server 2003, you may get the following error:

An unauthorized change was made to Windows. You must retype your Windows Service Product Key to activate the license.

Solution

If the Windows product license key is not activated on the target computer prior to a full restore, you will receive the following message, and you will be required to provide the product license key after the restore. Refer to the check list that you have creating while planning for disaster recovery.

Symptom

After the full system restore, the SIS-linked files are not be accessible, and they appear to be corrupted. The name and size of a SIS-linked file appear as normal. However, the file is a zero-length file and it does not have access to the data it should contain.

Solution

Before starting the restore, ensure the following

The source and target drive letter are the same.

The SIS/Groveler are running and attached to the volume to which you are restoring data.

For more information on How to restore a volume that is managed by Single Instance Storage, refer the KB 263027 Microsoft Knowledge Base article on http://support.microsoft.com/.

Restore jobs from Windows File System iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

For subclient containing only system state restore:

Fails to restore critical component - the job status is failed

Fails to restore non-critical component - the job status is completed w/ one or more errors

For subclient containing system state restore along with File system data:

Failure to restore critical component - marks the job as completed w/ one or more errors, so the data can be recovered.

Failure to restore non-critical component - marks the job as completed w/ one or more errors

On Windows Server 2008, when you perform the Full System Restore, the Features and Roles do not get updated.

As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.

WFS0027: Error during the Full System Restore of Windows Vista or Windows Server 2003

WFS0028: An unauthorized change was made to Windows. You must retype your Windows Service Product Key to activate the license.

WFS0029: Files on the Single Instance Storage linked volumes appear corrupted after Restore


Updating Features and Roles on Windows Server 2008


Select Configure Refresh from the Server Manager main page and update Features and Roles as they are not updated during a restart.

When there is no change in the data during the time interval between an incremental prior to and after a synthetic full backup, the subsequent incremental backup will complete successfully even though no data got backed up. But the restore operation may go to a pending state. To complete the restore operation successfully, set the bUseRestoreFileCountToFailOnEmptyBackup additional settings to zero. Use the following steps to enable the additional settings:

1. From the CommCell Browser, navigate to the CommServe.

2. Right-click the <CommServe>, and then click Properties.

3. On the CommServe Properties dialog box, click Advanced.


5. Click Add.

6. In the Name box, type bUseRestoreFileCountToFailOnEmptyBackup. The Category and Type details will be automatically populated.

Alternatively, you can click Lookup and search for the additional setting using the Find box.

7. In the Value box, type 0.

8. Click OK to save the additional setting configuration.

9. Click OK.

When you restore encrypted files to a different computer, you may not be able to open these files unless the keys or certificates to decrypt them are available in the destination computer.

To open the restored encrypted files, make sure that the private keys or certificates used to encrypt the files are available on the computer where the files are restored.

For more information, see Restoring Files to a Different Computer.

Symptom

Distributed Component Object Model (DCOM) component appears disabled after a restore operation is performed on the client computer.

Solution

Run the following command from the command prompt on the client computer after the restore operation is complete:

Restore operation goes to a pending state

Unable to open Encrypted files after an out-of-place restore operation

Distributed Component Object Model (DCOM) Component Appears Disabled After a Restore Operation

%windir%\system32\msdtc.exe –resetLog


Symptom

After the full system restore, the computer reboots with a BSoD error screen.

Resolution

Make sure that the following are not filtered while performing the full system restore operation:

1. *:\drivers\*

2. *:\win*\inf\*

Symptom

Users are able to Browse, Find and Restore files and folders associated with other users from all user-interfaces such as the CommCell Console, Web Console, etc.

Cause

ACLs (Access Control Lists) are not included in the backup, and/or

The user has Browse capability instead of only the End User Access capability.

Resolution

1. Make sure that only End User Access capability is configured on the client computer. For instructions, see Configuring End-User Operations on Client Computers.

Assigning End User Access capability helps to maintain multiple user profiles on the same laptop (or desktop) and ensures that each user has the ability to browse and restore only the data to which he or she has access.

2. Make sure that the Catalog ACL (end user access control list) option is enabled in the subclients before performing a backup as described in:

Subclient level - Enabling ACLs (Access Control Lists) during Backups.

Subclient Policy level - Enabling End User Access Control During Backups.

Once enabled, this option ensures that ACL s are included in the backup, which in turn, allows users to access only those files and folders for which they have permissions.

WFS0031: BSoD Error after a Full System Restore Operation

CC0008: Users have access to files and folders belonging to others users

Specifically ensure that Browse capability is not assigned to these users.

This option can be enabled only for users who log in with their Active Directory credentials.

After enabling this option, make sure to run a Full backup subsequently. This will ensure that ACLs are available in the backup data.

Conversely, if you run a Differential or Incremental backup after enabling this option, only the newer data will include ACLs.
