atos...features - microsoft sql server idataagent table of contents overview system requirements -...

Features - Microsoft SQL Server iDataAgent

Table of Contents Overview

System Requirements - Microsoft SQL Server iDataAgent

Installation

Install the Microsoft SQL Server iDataAgent

Install the Microsoft SQL Server iDataAgent - Clustered Environment - Virtual Server

Backup - Microsoft SQL Server

Restore Data - Microsoft SQL Server

Configuration

Instances - Microsoft SQL Server

Subclients - SQL Server

Management

Backup Job History

Restore Job History

Use Cases

Restore Latest Backup Data (Hot Server Restore)


of 108

Overview - Microsoft SQL Server iDataAgent

Choose from the following topics:

Introduction

Supported Data Types

Tree Levels in the SQL iDataAgent

License Requirement

Auto Discover Instances

Client Terminology

System Databases

Transaction Logs

SQL Database Backups Using Volume Shadow Service (VSS)

SnapProtect

Other Important Notes

Disaster Recovery Considerations

Introduction

Microsoft SQL Server software comprises several system databases, as well as user databases, that are backed up by the SQL Server iDataAgent. SQL Server system databases (master, msdb, and model) contain information that SQL Server needs to operate, such as user database characteristics, file locations, and other information. For more information on the types of data in system databases, refer to your SQL Server documentation from Microsoft. SQL Server user databases contain your enterprises data, related administrative files and transaction logs.

Back to Top

Supported Data Types

Data Protection Operations for the following data types are supported by the SQL Server iDataAgent:

SQL Server system databases

SQL Server user databases

Data Protection Operations for all other data types not mentioned in the above list are not supported by the SQL Server iDataAgent, including:

full text indexes (can be handled by the File System iDataAgent)

SQL analysis server database (refer to vendor documentation)

databases on removable media

tempdb database

Databases in single-user mode, suspect, loading, standby, and offline.

The SQL Server iDataAgent is responsible for backing up and restoring SQL Server databases. This iDataAgent is just one of several iDataAgents which provide backup and restore support for different kinds of data in what is often a mixed network environment. Remember that this product only secures the SQL Server databases (e.g., system and user databases). To secure SQL Server application files that reside on a local hard drive or file system data that resides on an SQL Server computer, you must use the File System iDataAgent.

The following figure shows how iDataAgents fully secure a heterogeneous computing environment.


of 108

Back to Top

Tree Levels in the SQL iDataAgent

When the SQL iDataAgent is installed, the following levels are automatically created in the CommCell Browser.

bulldog: Client

SQL Server: Agent

<user_defined_instance>: Instance

After installing the Microsoft SQL Server iDataAgent, you must use the system to add an instance to the SQL Server iDataAgent to run the first backup. (See Add a SQL Server Instance for step-by-step instructions). The system creates a default subclient for each instance you add named default which is designed to back up all the databases for the instance.

This default subclient is always of the "Database" type. However, you can create additional subclients (user-defined subclients) of both the "Database" and "File/FileGroup" type. Type "Database" user-defined subclients allow you to back up individual databases. Type "File/File Group" subclients allow you to back up data files and file groups. Whenever you assign data to these user-defined subclients, this data is removed from the content of the default subclient. For more information on default and user-defined subclients, see Subclient Backups.


of 108

Back to Top

License Requirement

To perform a data protection operation using this Agent a specific Product License must be available in the CommServe® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

The license is consumed during the installation of the SQL Server iDataAgent software. Each configured instance does not consume an additional license

Back to Top

Auto Discover Instances

If selected during installation, this option will also be selected at the Agent level after the install is complete. When selected, instances are automatically discovered every 24 hours or whenever the Communications Service (GxCVD) service is restarted. The default 24 hours can be overridden with the nAutoDiscoverSQLInstanceTimeout registry key.

If a storage policy is associated with the File System default subclient, then the same storage policy will be associated with the default subclients created for newly discovered instances. If a File System storage policy does not exist, a policy will not be assigned.

Client Terminology

The following definitions are offered to prevent the confusion that may arise from the use of the term 'client':

SQL Server clients are computers that access SQL Server databases, but which are not themselves the server. Both SQL Server application binary files and file system data on these computers can be backed up using the File System iDataAgent.

A client is a computer whose data is backed up via an iDataAgent. This may include SQL Server, File System, etc.

System Databases

There are four system databases in every SQL Server instance: master, msdb, model, and tempdb. Since SQL Server re-creates tempdb every time the server is started, it does not normally get backed up, while master, msdb, and model databases need to be backed up. When referred to, the term 'system databases' includes only the master, msdb, and model databases.

Back to Top

Transaction Logs

A transaction log is a file containing a record of changes to a database. Each database, including system databases, has its own transaction log.

For Express installations, an option does not appear during installation but instances are automatically discovered. By default, this option is automatically selected at the Agent level.


of 108

Truncation of transaction logs follows these rules for the SQL Server iDataAgent:

Transaction logs will be truncated at the completion of a Transaction Log backup.

Transaction logs will be truncated every time a checkpoint is processed, if the database is in truncate mode.

Full and Differential backups do not truncate transaction logs.

Back to Top

SQL Database Backups Using Volume Shadow Service (VSS)

VSS is a seamless method of backing up the database files. See VSS for SQL Server iDataAgents for more information.

Back to Top

SnapProtect

The SnapProtect feature enables you to create a point-in-time snapshot of data to be used for various data protection operations. An effective way to backup live data is to temporarily quiesce it, take a snapshot, and then resume live operations. For more information, see SnapProtect™ feature.

Back to Top

Other Important Notes

The following are important items of which you should be aware when using the SQL Server iDataAgent:

Support for [ and ] brackets in database names

The SQL Server iDataAgent does not support the use of embedded brackets '[' and ']' in database names.

CommServe and SQL Server time synchronization

It is recommended that the CommServe and the SQL Server client be synchronized in time as close as possible with the SQL Server client being ahead of the CommServe. Improper time synchronization may cause discrepancies in browse operations and in the database file listing in the Advanced SQL Restore Option dialog box.

Moving database files back to original location after a move

If, during a restore, database data files are moved to a new location, and if a subsequent restore of the database to the original location is then performed without taking a backup first, the database files are not moved back to the original location. There are several workarounds you can use in this situation:

Detach and re-attach the database

Drop the database from the SQL Server Instance and perform a restore with the default values

Take a full backup in between moves

VSS backups convert to VDI backups after client name change

If the SQL Server client name changes after SQL Server installation, then the SQL instance may be considered remote.

To determine whether an instance is local or remote, check the srvid column in the sysservers table by running select * from sysservers in the master database. An instance listed with the srvid as "non-zero" is considered remote.


of 108

If the instance is considered remote, VSS backups convert to VDI backups. To run VSS backups, we recommend running the following stored procedures:

sp_dropserver 'oldservername'

sp_addserver 'newservername', 'LOCAL'

Support for Microsoft Windows Vista

Backups using the the SQL Server iDataAgent on Windows Vista are supported as long as the same User account (and not the local system account) is used to run the Bull Calypso Communications Service (GxCVD) and for the SQL instance. See Running Services Using a Windows User and User Accounts for more details.

Back to Top

Disaster Recovery Considerations Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs. See Disaster Recovery for more information regarding your agent.

Back to Top


of 108

System Requirements - Microsoft SQL Server iDataAgent

The following requirements are for the Microsoft SQL Server iDataAgent:

Application

The Microsoft SQL Server iDataAgent is supported the following Microsoft SQL Server versions:

Microsoft SQL Server 2000 Editions up to the latest Service Pack



Microsoft SQL Server 2008 R2 Editions up to the latest Service Pack

Operating System

The Microsoft SQL Server iDataAgent is supported the following operating systems as supported by the Microsoft SQL Server.

Microsoft Windows XP Editions

Microsoft Windows Vista Editions

Microsoft Windows 7 Editions

Microsoft Windows Server 2003 Editions with a minimum of Service Pack 1

Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1*

Microsoft Windows Server 2008 R2 Editions*

*Core Editions not supported

Cluster Support

See Clustering - Support

Processor

All Windows-compatible processors supported

Memory

32 MB RAM minimum required beyond the requirements of the operating system and running applications

Hard Disk 170 MB minimum of hard disk space for software/ 498 MB recommended

50 MB of additional hard disk space for log file growth

80 MB of temp space required for install or upgrade (where the temp folder resides)

Peripherals DVD-ROM drive

Network Interface Card

Miscellaneous


of 108

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for 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.

TCP/IP Services configured on the computer.

The File System iDataAgent will be automatically installed during installation of the Microsoft SQL Server iDataAgent if it is not already installed. For System Requirements and install information specific to the File System iDataAgent, refer to System Requirements - Microsoft Windows File System iDataAgent.

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

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

Notes on Microsoft SQL Server iDataAgent Installation Special configuration considerations applies to the installation of Microsoft SQL Server 32-bit components on a Microsoft Windows x64 platform. See Installing 32-bit Components on a Microsoft Windows x64 Platform for more information.

For more information on backing up SQL on Windows Vista , see Support for Microsoft Windows Vista.

If the option to install SQL Server is disabled make sure there is at least one network protocol enabled. For SQL 2000 run SVRNETCN.exe and add the protocols. For SQL 2005 go to SQL Server Configuration Manager and enable protocols for each instance.

Microsoft SQL Server Management Objects (SMO) is required on the client machine. SMO is installed by default when SQL Server 2005 or later versions are installed.


of 108

Install the Microsoft SQL Server iDataAgent

Click on a link below to go to a specific section of the software installation:

Install Requirements

Install Checklist

Before You Begin

Install Procedure

Getting Started

Select Components for Installation

Firewall Configuration

Configuration of Other Installation Options

Client Group Selection

Storage Policy Selection

Verify Summary of Install Options

Schedule Automatic Update

Install Remaining Cluster Nodes

Setup Complete

Post-Install Considerations


The Microsoft SQL iDataAgent is installed on the computer on which the SQL server software resides. (This computer is referred to as the Client computer in this install procedure.)

NOTES

Optionally, the GalaxyInstallerFlags registry key can be used to install the Microsoft SQL iDataAgent on a computer that does not have the Microsoft SQL server software installed.

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - Microsoft SQL Server iDataAgent and in System Requirements - Microsoft Windows File System iDataAgent.

The following procedure describes the steps involved in installing the Windows File System and SQL Server iDataAgents. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary.

Review the following Install Requirements before installing the software:

General Agents should be installed only after the CommServe and at least one MediaAgent have been. Also, keep in mind that the CommServe® software and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.

This software should be installed in a CommCell component with current versions of the CommServe Server and MediaAgent software.

Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation.

Ensure there is an available license on the CommServe software for the Agent.

Verify that you have the software installation disc that is appropriate to the destination computer’s


of 108

operating system. Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Firewall

If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Ensure port 8400 is allowed connections through the firewall.

In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):

Identify a range of outbound ports (consecutive or discrete) for use by the software.

For information on configuring the range of ports, see Port Requirements for One-way Firewall.

If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

Install Checklist

Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder.

1. Install folder location:________________________________________________________________

See Select Components for Installation for more information.

2. If the CommServe Server and the client computer communicate across a firewall:

Firewall ports: ______________________________________________________________________

Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________

Keep Alive Interval minutes:____________________________________________________________

Hostname for outgoing tunnel connections:_________________________________________________

Tunnel Initialization Interval seconds:_____________________________________________________

See Firewall Configuration for more information.

3. CommServe Host Name or the CommServe IP address:______________________________________

See Configuration of Other Installation Options for more information.

4. Client computer's Host name (NetBIOS name) or IP address____________________________________


5. Job result folder location:________________________________________________________________

If necessary, Name and Password for the specified


of 108

folder:_______________________________________


6. Client Group to which this Client will be associated:_____________________________________________

See Client Group Selection for more information.

7. Storage Policy used by the default subclient:________________________________________________

See Storage Policy Selection for more information.

8. Time and frequency for Install of Automatic Updates:_________________________________________

See Schedule Automatic Update for more information.

Before You Begin

Log on to the client as the local Administrator or as a member of the Administrators group on that computer.

Install Procedure

Getting Started

1. Place the software installation disc for the Windows platform into the disc drive.

After a few seconds, the installation program is launched.

If the installation program does not launch automatically:

Click the Start button on the Windows task bar, and then click Run.

Browse to the installation disc drive, select Setup.exe, click Open, then click OK.

NOTES

If you are installing on a x64 version of Windows 2008 Server Core R2, go to the AMD64 folder and run Setup.exe.

2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue.

3. Select the option to install software.

NOTES

This screen will only appear when the bAllow32BitInstallOn64Bit registry key has been created and enabled on this computer.

4. Select the option to install software on this computer.


of 108

NOTES

The options that appear on this screen depend on the computer in which the software is being installed.

5. Read the Welcome screen.

Click Next to continue, if no other applications are running.

6. Read the virus scanning software warning.

Click OK to continue, if virus scanning software is disabled.

7. Read the license agreement, then select I accept the terms in the license agreement.

Click Next to continue.


8. Select the component(s) to install.

NOTES

Your screen may look different from the example shown.

Components that either have already been installed, or which cannot be installed, will be dimmed. Hover over the component for additional details.

The Special Registry Keys In Use field will be enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set, as well as their values. For more information, see Registry Keys.


To install the Microsoft SQL Server iDataAgent expand the Client Modules folder, the iDataAgents folder and the Database Agents folder and select the following:

iDA for SQL Server

When you select the SQL iDataAgent for install, the appropriate Windows File System iDataAgent is automatically selected for install.

9. Click Yes to install the SQL Backward Compatibility Package. This applies to all SQL versions.

If you click No, the installation will be aborted.

10. When Auto Discover Instances is selected,


of 108

instances are automatically discovered every 24 hours or whenever the Communications Service (GxCVD) service is restarted. For more information, see Automatically Discovered Instances.

11. Click Yes to set up the required privileges for the local administrators group.

NOTES

This option will only appear if the Windows user account used to install the software does not have the required administrator rights (e.g., if the operating system was newly installed).

If you choose to click Yes, the install program will automatically assign the required rights to your account. You may be prompted to log off and log back on to continue the installation.

If you choose to click No, the installation will be aborted.

You will be prompted at the end of the installation to decide if you want these privileges to be revoked.

The install program checks your Windows user account for the following necessary operating system rights:

Right to increase quotas (this is referred to as adjust memory quotas for a process on Windows Server 2003).

Right to act as a part of the operating system.

Right to replace a process level token.

12. Specify the location where you want to install the software.

NOTES

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.

If you intend to install other components on this computer, the selected installation directory will be automatically used for that software as well.


of 108

If a component has already been installed, this screen may not be displayed if the installer can use the same install location as previously used.

If you intend to use the SnapProtect™ feature for Windows File System iDataAgent, the agent should be installed on a non-system drive and not a filer volume.

Click Browse to change directories.



13. Select from the following:

If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select Yes, configure firewall services, and then click Next to continue. Proceed to the next Step.

If firewall configuration is not required, click No, do not configure firewall services and then click Next to continue. Proceed to the next section.

NOTES

Operating systems, such as Windows 2008 and Windows Vista, may have more than one profile present. When you select No to configure firewall services, verify that firewall settings are not enabled in the profile(s).

If the system detects firewall settings are present in the profile(s), you must select from the following:

Disable firewall for ALL profiles: Employ caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot.

No, Firewall is not enabled: Select this option if your firewall settings allow communication with the CommServe computer. Click Back to configure firewall services.

14. Click the Specify list of machine across the firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa).

For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port


of 108

filtering, skip this step.


NOTES

Consider the following:

On the CommServe Server, this list should include all the MediaAgents and Clients that are on the other side of the firewall.

On the MediaAgents/Clients this should include the CommServe computer, and any other Clients/MediaAgents on the other side of the firewall with which communications will be established.

For each machine on the other side of the firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options:

Click on 2-way firewall if you can open certain ports as bi-directional ports.

Click 1-way firewall; host is reachable from this machine on the machine that is on the secure side of the firewall.

Click 1-way firewall; host is NOT reachable from this machine on the machine that is on the public / DMZ side of the firewall.

If you wish to communicate with computers in a clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed.

Type the host name or the IP address and the GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List.

15. Click the Specify list of restricted open ports option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed.

If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step.

Note that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured.

NOTES

Typically in a two-way firewall, the open ports


of 108

must be indicated for all computers. In a one-way firewall, the ports must be specified on computers in the open side, if they are open in a restricted way. Note that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent.

In a clustered environment, make sure the firewall ports specified here are open for communication on all the physical nodes as well as the virtual nodes.


16. If desired, modify the Keep Alive interval.


17. Optionally, select Advanced Firewall Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS.


18. If desired, modify the Tunnel Initialization interval.



of 108


19. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com)

NOTES

Do not use spaces when specifying a new name for the CommServe Host Name.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same Server Name as previously specified.


20. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

This window is only displayed when the Require Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs.


21. Enter the following:

The local (NetBIOS) name of the client computer.

The TCP/IP IP host name of the NIC that the client computer must use to communicate with the CommServe Server.

NOTES

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. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server.

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


22. Specify the following and click Next to continue:


of 108

Type the location of the client's job results directory, or click Browse.

NOTES

The Agent uses the job results directory to store the client's backup and restore job results.


23. Select a Client Group from the list.


NOTES

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


24. Select the storage policy through which you want to back up/archive the indicated component (subclient, instance, etc.)

NOTES

A storage policy directs backup data to a media library. Each library has a default storage policy.

When you install an Agent, the install program creates a default subclient for most Agents.

If desired, you can change your storage policy selection at any time after you have installed the client software.

If applicable, enable Global Filters for the default subclient.

If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents.


25. Select Download Pack(s) and Install to


of 108

download and install the latest service packs and post packs from the software provider.

NOTES

Internet connectivity is required to download updates.

This step is applicable when installing on the first instance.

Updates are downloaded to the following directory: <software installation>/Base/Temp/DownloadedPacks. They are launched silently and installed automatically for the first instance.



26. Verify the summary of selected options.

NOTES

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

Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take several minutes to complete.

27. The System Reboot message may be displayed. If so, select one of the following:

Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time.

Reboot Now If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot.

Exit Setup If you want to exit the install program, click Exit Setup.


of 108


28. If necessary, select this option to schedule an automatic installation of software updates.

NOTES

Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console.

To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates.

You may be prompted to reboot the computer before restarting services.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously specified.



29. If you are installing/upgrading the software on the physical node in a clustered environment, use this option to install/upgrade the software on the remaining physical nodes of the cluster.

To install/upgrade the software on the remaining nodes of the cluster, click Yes.

To complete the install/upgrade for this node only, click No.

See Install/Upgrade Remaining Cluster Nodes for step-by-step instructions.

Setup Complete

30. Click Next to continue.

NOTES

Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling.

31. Click Yes to remove the privileges that were


of 108

assigned earlier by the install program. If you do not wish to remove them, click No.

NOTES

This option will only be displayed if you were prompted to assign the privileges earlier in the installation.

32. Setup displays the successfully installed components.

NOTES

The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the example shown.

If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents.

If Reboot Now button is displayed make sure to reboot the computer before performing any other operations from the computer.

Click Finish to close the install program.

The installation is now complete.


General Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

After installing the Agent, you may want to configure the Agent before running a data protection operation. The following list includes some of the most common features that can be configured:

Configure your subclients - see Subclients for more information.

Schedule your data protection operations - see Scheduling for more information.

Configure Alerts - See Alerts and Monitoring for more information.

Schedule Reports - See Reports for more information.

The software provides many more features that you will find useful. See the Index for a complete list of supported features.

Agent Specific

After the installation, you must use the system to add an instance for the iDataAgent so that you can back up the SQL databases. To add an instance, see Add a SQL Server Instance for step-by-step instructions. Instances are automatically discovered if enabled during installation or in the agent Properties dialog box. For more information, see Automatically Discovered Instances.

For information on backing up the Microsoft Virtual Server, see Considerations for backing up the Microsoft Virtual Server.

Disaster Recovery Considerations


of 108

Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs. See Disaster Recovery for more information regarding your agent.


of 108

Install the Microsoft SQL Server iDataAgent - Clustered Environment - Virtual Server

Click on a link below to go to a specific section of the software installation:


Install Checklist

Before You Begin

Install Procedure

Getting Started

Cluster Selection






Download and Install Latest Packs




Setup Complete



The Windows File System iDataAgent must be first installed onto all of the physical nodes of the cluster. See Install the Microsoft Windows File System iDataAgent if you have not installed it on all of the physical nodes. Once it has been installed onto the physical nodes, the SQL Server iDataAgent and the Windows File System iDataAgent can be installed from the active node to the virtual server using the following procedure. The software can also be automatically installed on all available passive nodes when the software is installed onto the virtual server, or you can choose to install any passive node(s) separately.

For an overview of deploying the software components in a clustered environment, see Clustering Support.

Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in System Requirements - Microsoft SQL Server iDataAgent and in System Requirements - Microsoft Windows File System iDataAgent.

The following procedure describes the steps involved in installing the SQL Server iDataAgent and the Windows File System iDataAgent. If you choose to install additional components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary.

Review the following Install Requirements before installing the software:

General Agents should be installed only after the CommServe and at least one MediaAgent have been. Also, keep in mind that the CommServe® software and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.

This software should be installed in a CommCell component with current versions of the CommServe Server and MediaAgent software.


of 108

Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation.

Ensure there is an available license on the CommServe software for the Agent.

Verify that you have the software installation disc that is appropriate to the destination computer’s operating system. Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Firewall

If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Ensure port 8400 is allowed connections through the firewall.

In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):

Identify a range of outbound ports (consecutive or discrete) for use by the software.

For information on configuring the range of ports, see Port Requirements for One-way Firewall.

If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

If a MediaAgent or Client on a Microsoft Windows MSCS virtual server needs to communicate with other CommCell components across a firewall, you must:

Install File System iDataAgent or MediaAgent on all the physical nodes of the cluster. During the installation, use the firewall related prompts to establish the firewall settings required by the software to communicate across the firewall.

Then install the software components on the virtual nodes. (It is not necessary to configure the firewall settings again in the virtual nodes.)

If the cluster communicates with the CommServe across a one-way firewall, you must add both the physical and virtual nodes' host names (or the IP addresses) in the CommServe computer before installing the software.

Cluster Check the following on the cluster computer in which you wish to install the software:

Cluster software is installed and running.

Active and passive nodes are available.

Disk array devices configured with access to the shared array.

Public Network Interface Card is bound first, before the private Network Interface Card. (Does not apply to NetWare Cluster.)

Microsoft SQL Server software must be installed and clustered prior to installing the iDataAgent. (For information on supported versions, see System Requirements - Microsoft SQL Server iDataAgent.)

Install Checklist

Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder.

1. Name of the disk group in which the virtual server resides ____________________________________

See Cluster Selection for more information.


of 108

2. Install folder location:________________________________________________________________

See Select Components for Installation for more information.

3. If the CommServe Server and the client computer communicate across a firewall:

Firewall ports: ______________________________________________________________________

Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________

Keep Alive Interval minutes:____________________________________________________________

Hostname for outgoing tunnel connections:_________________________________________________

Tunnel Initialization Interval seconds:_____________________________________________________

See Firewall Configuration for more information.

4. CommServe Host Name or the CommServe IP address:______________________________________


5. Client computer's Host name (NetBIOS name) or IP address____________________________________


6. Job result folder location:________________________________________________________________

If necessary, Name and Password for the specified folder:_______________________________________


7. Client Group to which this Client will be associated:_____________________________________________

See Client Group Selection for more information.

8. Storage Policy used by the default subclient:________________________________________________

See Storage Policy Selection for more information.

9. Time and frequency for Install of Automatic Updates:_________________________________________

See Schedule Automatic Update for more information.

Before You Begin

Log on to the active node as the Domain User with administrative privileges to all nodes on the cluster.

Install Procedure


of 108

Getting Started

1. Place the software installation disc for the Windows platform into the disc drive.

After a few seconds, the installation program is launched.

If the installation program does not launch automatically:

Click the Start button on the Windows task bar, and then click Run.

Browse to the installation disc drive, select Setup.exe, click Open, then click OK.

NOTES

If remotely installing to other physical nodes of the cluster, ensure you mount the software installation disc on a UNC path or a shared location (e.g., \\machine_name\shared_directory_name).

2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue.

3. Select the option to install software.

NOTES

This screen will only appear when the bAllow32BitInstallOn64Bit registry key has been created and enabled on this computer.

4. Select the option to install software on this computer.

NOTES

The options that appear on this screen depend on the computer in which the software is being installed.

5. Read the Welcome screen.

Click Next to continue, if no other applications are running.

6. Read the virus scanning software warning.

Click OK to continue, if virus scanning software is disabled.

7. Read the license agreement, then select I accept the terms in the license agreement.


Cluster Selection

8. Select Configure a Virtual Server.



of 108

9. Select the disk group in which the virtual server resides.



10. Select the component(s) to install.

NOTES

Your screen may look different from the example shown.

Components that either have already been installed, or which cannot be installed, will be dimmed. Hover over the component for additional details.

The Special Registry Keys In Use field will be enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set, as well as their values. For more information, see Registry Keys.


To install the Microsoft SQL Server iDataAgent expand the Client Modules folder, the iDataAgent folder and the Database Agents folder and select the following:

iDA for SQL Server

When you select the SQL Server iDataAgent for


of 108

install, the appropriate Windows File System iDataAgent is automatically selected for install.

11. Click Yes to set up the required privileges for the local administrators group.

NOTES

This option will only appear if the Windows user account used to install the software does not have the required administrator rights (e.g., if the operating system was newly installed).

If you choose to click Yes, the install program will automatically assign the required rights to your account. You may be prompted to log off and log back on to continue the installation.

If you choose to click No, the installation will be aborted.

You will be prompted at the end of the installation to decide if you want these privileges to be revoked.

The install program checks your Windows user account for the following necessary operating system rights:

Right to increase quotas (this is referred to as adjust memory quotas for a process on Windows Server 2003).

Right to act as a part of the operating system.

Right to replace a process level token.

12. Specify the location where you want to install the software.

NOTES

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.

If you intend to install other components on this computer, the selected installation directory will be automatically used for that software as well.

If a component has already been installed, this screen may not be displayed if the installer can use the same install location as previously used.

If you intend to use the SnapProtect™ feature for Windows File System iDataAgent, the agent should be installed on a non-system drive and not a filer volume.

Click Browse to change directories.



of 108

Proprietary disk resources will not appear in the browse window. To install to a proprietary disk resource, manually enter the path.

After installing to a proprietary disk resource, the error message CVD failed to set dependency may be generated. To set the dependency, open the Cluster Administrator and select the CVD that has just been installed. Click on the Properties Dependencies tab, and click Modify. Select the proprietary disk resource and click OK.

Do not select the same destination drive in which the MSCS resides.


13. Select from the following:

If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select Yes, configure firewall services, and then click Next to continue. Proceed to the next Step.

If firewall configuration is not required, click No, do not configure firewall services and then click Next to continue. Proceed to the next section.

NOTES

Operating systems, such as Windows 2008 and Windows Vista, may have more than one profile present. When you select No to configure firewall services, verify that firewall settings are not enabled in the profile(s).

If the system detects firewall settings are present in the profile(s), you must select from the following:

Disable firewall for ALL profiles: Employ caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot.

No, Firewall is not enabled: Select this option if your firewall settings allow communication with the CommServe computer. Click Back to configure firewall services.

14. Click the Specify list of machine across the firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa).

For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port filtering, skip this step.



of 108

NOTES

Consider the following:

On the CommServe Server, this list should include all the MediaAgents and Clients that are on the other side of the firewall.

On the MediaAgents/Clients this should include the CommServe computer, and any other Clients/MediaAgents on the other side of the firewall with which communications will be established.

For each machine on the other side of the firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options:

Click on 2-way firewall if you can open certain ports as bi-directional ports.

Click 1-way firewall; host is reachable from this machine on the machine that is on the secure side of the firewall.

Click 1-way firewall; host is NOT reachable from this machine on the machine that is on the public / DMZ side of the firewall.

If you wish to communicate with computers in a clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed.

Type the host name or the IP address and the GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List.

15. Click the Specify list of restricted open ports option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed.

If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step.

Note that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured.

NOTES

Typically in a two-way firewall, the open ports must be indicated for all computers. In a one-way firewall, the ports must be specified on


of 108

computers in the open side, if they are open in a restricted way. Note that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent.

In a clustered environment, make sure the firewall ports specified here are open for communication on all the physical nodes as well as the virtual nodes.


16. If desired, modify the Keep Alive interval.


17. Optionally, select Advanced Firewall Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS.


18. If desired, modify the Tunnel Initialization interval.



of 108

If any of the above prompts for firewall configuration is not displayed, you must configure communication across firewall(s) using the Firewall Configuration Wizard before running any operations on this computer. (See Configure or Modify Firewall Settings on Windows Computers for step-by-step instructions on using the Firewall Configuration Wizard.)


19. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com)

NOTES

Do not use spaces when specifying a new name for the CommServe Host Name.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same Server Name as previously specified.


20. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

This window is only displayed when the Require Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs.


21. Enter the following:

The local (NetBIOS) name of the client computer.

The TCP/IP IP host name of the NIC that the client computer must use to communicate with the CommServe Server.

NOTES

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. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server.

If a component has already been installed, this screen will not be displayed; instead, the


of 108

install program will use the same name as previously specified.


22. Specify the following and click Next to continue:

Type the location of the client's job results directory, or click Browse.

NOTES

The Agent uses the job results directory to store the client's backup and restore job results.


23. Select a Client Group from the list.


NOTES

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


24. Select the storage policy through which you want to back up/archive the indicated component (subclient, instance, etc.)

NOTES

A storage policy directs backup data to a media library. Each library has a default storage policy.

When you install an Agent, the install program creates a default subclient for most Agents.

If desired, you can change your storage policy selection at any time after you have installed the client software.

If applicable, enable Global Filters for the default subclient.

If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy


of 108

association for each of the installed agents.


Download and Install Latest Packs

25. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider.

NOTES

Internet connectivity is required to download updates.

This step is applicable when installing on the first instance.

Updates are downloaded to the following directory: <software installation>/Base/Temp/DownloadedPacks. They are launched silently and installed automatically for the first instance.



26. Verify the summary of selected options.

NOTES

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

Click Next to continue or Back to change any of the options.

The install program now starts copying the software to the computer. This step may take several minutes to complete.

27. The System Reboot message may be displayed. If so, select one of the following:

Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time.

Reboot Now If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option,


of 108

reboot the computer at this point. The install program will automatically continue after the reboot.

Exit Setup If you want to exit the install program, click Exit Setup.


28. If necessary, select this option to schedule an automatic installation of software updates.

NOTES

Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console.

To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates.

You may be prompted to reboot the computer before restarting services.

If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously specified.



29. To install/upgrade the software on the remaining nodes of the cluster, click Yes.

To complete the install for this node only, click No.

30. Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list.

NOTES

The list of Preferred Nodes displays all the nodes found in the cluster; from this list you should only select cluster nodes configured to host this virtual server.

Do not select nodes that already have multiple instances installed. For more information, see Multi Instancing.

When you have completed your selections, click Next to continue.

31. Type the User Name and Password for the


of 108

Domain Administrator account, so that the installer can perform the remote install/upgrade of the cluster nodes you selected in the previous step.


32. The progress of the remote install for the cluster nodes is displayed; the install can be interrupted if necessary.

Click Stop to prevent installation to any nodes after the current ones complete.

Click Advanced Settings to specify any of the following:

Maximum number of nodes on which Setup can run simultaneously.

Time allocated for Setup to begin executing on each node, after which the install attempt will fail.

Time allocated for Setup to complete on each node, after which the install attempt will fail.

NOTES

If, during the remote install of a cluster node, setup fails to complete or is interrupted, you must perform a local install on that node. When you do, the install begins from where it left off, or from the beginning if necessary. For procedures, see Manually Installing the Software on a Passive Node.

33. Read the summary for remote installation to verify that all selected nodes were installed successfully.

NOTES

If any node installation fails, you must manually install the software on that node once the current installation is complete. (See Manually Installing the Software on a Passive Node for step-by-step instructions.)

The message displayed on your screen will reflect the status of the selected nodes, and may look different from the example.


Setup Complete


of 108

34. Click Next to continue.

NOTES

Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling.

35. Click Yes to remove the privileges that were assigned earlier by the install program. If you do not wish to remove them, click No.

NOTES

This option will only be displayed if you were prompted to assign the privileges earlier in the installation.

36. Setup displays the successfully installed components.

NOTES

The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the example shown.

If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents.

If Reboot Now button is displayed make sure to reboot the computer before performing any other operations from the computer.

Click Finish to close the install program.

The installation is now complete.


General Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

After installing the Agent, you may want to configure the Agent before running a data protection operation. The following list includes some of the most common features that can be configured:

Configure your subclients - see Subclients for more information.

Schedule your data protection operations - see Scheduling for more information.

Configure Alerts - See Alerts and Monitoring for more information.


of 108

Schedule Reports - See Reports for more information.

The software provides many more features that you will find useful. See the Index for a complete list of supported features.

Agent Specific

After the installation, you must use the system to add an instance for the iDataAgent so that you can back up the SQL databases. To add an instance, see Add a SQL Server Instance for step-by-step instructions. Instances are automatically discovered if enabled during installation or in the agent Properties dialog box. For more information, see Automatically Discovered Instances.

Disaster Recovery Considerations Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs. See Disaster Recovery for more information regarding your agent.

Cluster If the passive node was not available while installing the software, you must manually install the software on the passive node now. (See Manually Installing the Software on a Passive Node for step-by-step instructions.)

By default, a failure of MediaAgent or Agent software on the active node in a Windows, Veritas, or HP Scalable NAS/PolyServe Cluster will not cause a failover to be initiated. For information on how to change this default behavior, see Clustering Support - Failovers.


of 108

Backup - Microsoft SQL Server Topics | How To | Related Topics

Overview

Supported Backup Types

SQL Backup Jobs

Subclient Backups

Instance Backups

File and File Group Backups

Jobs Restricted During Backups

Volume Shadow Service (VSS) Enabled Backups

Transaction Log Backups

Backing up the Transaction Log of a Damaged Database (Do Not Truncate Log)

Specify Number of Log Backups Before Running Full

Run Log Backups Only Without a Full

Run Log and Full Backups Simultaneously

SnapProtect

Backup Considerations

Advanced Backup Options

Overview

Plan your backup jobs for this agent by reviewing the following information:

For an overview of backup jobs, see Backup Data.

For a list of supported data types for this agent, see Supported Data Types.

For information on subclients, see Subclients

For information on configuring subclients for this agent, see Subclients - SQL Server.

Supported Backup Types

The Microsoft SQL Server iDataAgent supports the following backup types:

Full Backups

Differential Backups


Do Not Truncate Log

SQL Backup Jobs

This agent has the following unique functionality. The Microsoft SQL Server iDataAgent backs up very specific sets of data depending upon what type of operation you choose. Review the following information to understand exactly what will be backed up when you perform a backup job at the indicated level.

Subclient Backups

Instance Backups


of 108





SnapProtect

Subclient Backups

Through the creation of subclients, you have a flexible way to manage how databases, data files, and file groups get backed up by the Microsoft SQL Server iDataAgent. Subclient backups support the following:

Database backups for the default subclient and user-defined subclients.

File and File Group backups for user-defined subclients.

The job that is performed when you perform a full, transaction log, or differential backup for a subclient depends on the type of subclient you are backing up:

Default subclient

When a full backup job is performed for the default subclient, the system performs a discover on the instance and executes a full backup of:

all the databases that are already configured within the subclient.

unconfigured databases within the instance (discovered).

When a transaction log or differential backup job is performed for the default subclient, the system performs a discover of the instance, and executes:

a full backup of unconfigured databases (discovered).

a full backup of any database manually added since the last backup.

a transaction log or differential backup of all databases already configured within the subclient. See Default Subclient Backup Conversion Rules for more information.

User-defined subclients

When a full backup job is performed for a user-defined subclient, the system executes a full backup of:

that subclient's databases.

When a transaction log or differential backup job is performed for a user-defined subclient:

a transaction log or differential backup is performed for all databases already configured.

a full backup is performed for any database that was not part of this subclient on the last backup (that is, any databases manually added since the last backup).

Instance Backups

Through the creation of instances, you have a flexible way to manage how databases, data files, and file groups get backed up by the Microsoft SQL Server iDataAgent. Instance backups support the following:

Database backups for the default subclient and user-defined subclients.

File and File Group backups for File/File Group subclients.

When a full backup job is performed for an instance, the following actions take place:

New databases that are not yet configured for backup are added to the default subclient.

All databases that are already part of the subclient in the instance are backed up.

When a transaction log or differential backup job is performed for an instance, the following actions take place:

New databases that are not yet configured for backup are added to the default subclient.

If a new database is discovered, a full backup is performed on that database.


of 108

A transaction log or differential backup is performed for all databases already configured in all subclients. See Default Subclient Backup Conversion Rules for more information.

See Instances - Microsoft SQL Server for more information.


Through the creation of additional subclients, the SQL Server iDataAgent allows individual files or file groups to be backed up. For especially large databases, this functionality can be critically important.

Whereas a Full database backup captures all files of a given database, file and file group backups allow you to back up selected portions of a database individually. As with database backups, the system provides the option of performing full, differential, and transaction log backups of file and file groups. Note that file and file group backups only support full and differential, and when running a transaction log backup for a File/File Group subclient, the database log is backed up.

A file and a file group backup are technically the same. If the subclient content is defined as a file group, the backup command issued will be to back up the group. All files defined in the group are backed up. If the subclient content is defined as one or more files, the backup command issued will be to back up only the files listed in the contents. SQL Server permits only one file or file group backup to run at a time.

If you choose to use file and file group backups, keep in mind the requirement that you must also run transaction log backups in order to restore files and file groups. You have the option of running a transaction log backup automatically upon successful completion of a Full or Differential backup. See Start Log Backup after Successful Backup for more information.


While backups can proceed while a database is online and being accessed, there are a few jobs that SQL Server restricts during a backup. If one of these jobs is initiated while a backup is already in progress, the job terminates. If a backup is initiated while one of these jobs is in progress, the backup terminates. These jobs are:

creating or deleting database files

creating an index

performing any non-logged job

shrinking the database.


When using SQL on Windows Server 2003 or later, you can enable VSS for backup jobs, see VSS for SQL Server iDataAgents for more information.


A transaction log backup is a backup of the transaction log of the database. This backup captures the transaction log which contains a record of all transactions whether the transaction was committed or not. Transaction log backups are consistent to the start time of the backup.

The use of transaction log backups make point in time recovery possible. You can restore to any point in time within the transaction log. If you use only full and differential backups, you will be able to restore to the time of the backup, but not to a point in time between backups.

A transaction log backup is similar to a traditional incremental backup you might perform on a file system because the transaction log backup contains only the new changes since the full or another transaction log backup.

Each time a transaction log is backed up it is truncated to the exact time of the backup. No checkpoint is issued at this time, therefore dirty pages are not written to disk before or after a transaction log backup. If there are dirty pages, any completed transactions will need to be rolled forward if a transaction log

When a backup is performed at the instance level, File/File Group subclients are not backed up.


of 108

restore is performed. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup.

Backing up the Transaction Log of a Damaged Database (Do Not Truncate Log)

In the scenario of a database failure where it is unacceptable to lose any data, you will want to restore to the point of failure. To do so means you will need to capture all transaction log events that occurred after the last backup job was run.

Tail-log Backup (database is left in restoring state)

This advanced backup option is only available if the Transaction Log option was selected in the Backup Option dialog box. Specifies to back up the tail of the log and to leave the database in the RESTORING state.

Specify Number of Log Backups Before Running Full

By configuring the nLogThreshHoldValue registry key, a minor event will be generated to remind users to run a full backup after the specified number of transaction log backups have run. By default, 24 log backups are run and then a full backup is taken. Specify a number with the registry key if you want to run a different number of log backups other than the default. The event can be viewed with the Event Viewer. This is useful since log backups are typically scheduled, but scheduling full backups may be inadvertently missed. Full backups also reduce the chance of data loss if log backups become corrupted.

Run Log Backups Only Without a Full

You can configure the SQL Server iDataAgent to run log backups only without having to run full backups in the software. To do this:

1. Disable backup consistency checking with the nCvdLogChainConsistencyCheck registry key.

2. Disable the backup rules in the subclient.

3. Run a full backup using software other than Calypso.

4. Commence running log backups using Calypso.

Run Log and Full Backups Simultaneously

Full and log backup operations can run simultaneously for the same subclient. However, a full backup needs to exist prior to running them together. After a full has been run, subsequent parallel backups will work since the risk of breaking the chain will be lessened. Note that running full and differential backups at the same time is not supported.

SnapProtect

You can use the SnapProtect feature to perform various data protection operations. For more information, see SnapProtect™ feature.

Backup Considerations

Before performing any backup procedures for this agent, review the following information:

A SQL backup job for a subclient with multiple databases will not retry backing up a single database if it fails. However, the job status will be "Complete". If the job goes into pending state, the job will restart from the point where it failed and if an attempt to back up the failed database has already been made, another attempt will not be performed.

For databases that are defined in a subclient but that are inaccessible (e.g., it is not recognized, has been deleted, etc.), the job status for the backup will be "Completed". An event will be created for the inaccessible database during backup. If the inaccessible database is not needed, it can be deleted from

When full and log backup operations are run simultaneously, the conversion rules will not be honored. See Backup Conversion Rules for more information.


of 108

the subclient using the Subclient Properties (Content) dialog box.

When running backups using the Microsoft SQL Server iDataAgent, do not concurrently perform backups using other applications (e.g., Microsoft SQL Server Enterprise Edition). Doing so may compromise future restore operations.

When File/File Group subclient jobs are scheduled and the instance property Use VSS is selected, backups for File and File Group subclients run successfully as scheduled.

In order to perform a Transaction Log backup the following is required:

SQL Server database must be in full or bulk-logged recovery mode.

After having run VSS-enabled backups, if you clear the Use VSS check box, all full backups for all databases within the instance will revert to traditional (non-VSS) full backups.

Multiple streams are supported for data protection and recovery operations with this agent; however, before utilizing multiple streams, you should understand how their use affects operations. For more information, see Streams.

If you change the recovery model from Simple Recovery Model to either Bulk-Logged or to Full, it is recommended that you run a full database backup.

If the Override Datapaths option is selected in the Data Paths dialog box for a Log Storage Policy, an "All data paths for the subclient are offline or busy" error message will display while the Transaction Log backup operation waits for resources. To work around this issue, deselect the Override Datapaths option.

To increase the speed of SQL backups, you can increase the number of streams used by the backup to a number greater than 1 and enable software compression at the subclient level. See Set Stream Numbers for Backup and Restore and Enable Software Compression for a Subclient respectively.

When running a backup, a check is made to verify if the backup is restorable. If the log chain is broken (e.g., when a log backup is ran outside of the software) or if there are no full backups for a corresponding differential backup then the backup of the database fails and the job will complete with errors. A Job Pending Reason (JPR) explains why the backup failed. In the next backup attempt, this database will be backed up as a full database. An alert can also be configured for this job.

Even though differential and log backups are supported for system databases (msdb, model), restore operations can only be performed for full VSS-enabled backups. When Use VSS is selected, only full backups can be restored. See VSS for SQL Server iDataAgents for more information.

To successfully backup a SharePoint Database in a Windows SharePoint Services (WSS) environment, where the instance name of the Windows Internal Database resembles something like MachineName\Microsoft##SSEE, you need to:

1. Change the flag Hide Instance to No in SQL Server Configuration Manager→Protocols for MachineName\Microsoft##SSEE.

2. Ensure that the SQL Server Browser service is running in SQL Server Configuration Manager→SQLServer 2005 Services.

3. Ensure that Named Pipes is enabled in SQL Server Configuration Manager→Protocols for MachineName\Microsoft##SSEE.

The default time allocated for backup and restore operations of SQL databases is 0 (infinite). If a backup or restore operation fails due to a timeout being reached, you can configure the nSqlQueryTimeout registry key to increase the amount of allocated time for backup or restore operations.

You can discover offline SQL Server databases in one or more states by configuring the sDiscoverDatabaseStates registry key. This will discover the databases on the client on which the registry key is configured. Alternatively, you can use a qoperation execscript command to globally discover databases for all clients as follows:

Example:

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si DatabaseStateString -si y -si standby;restoring;suspect;offline;


of 108

Back to Top

Backup - Microsoft SQL Server - How To Topics | How To | Related Topics

Start a Backup

Schedule Backups

Start a Transaction Log Backup

Start a Backup in the Suspended State

Start a Backup on New Media

Start a Backup that Marks Media Full on Completion

Start a Backup with a Set Job Priority

Start a Backup with Vault Tracking enabled

Enable (Disable) SnapProtect for a Subclient

Enable VSS on a SQL Instance

Start a Backup

Before You Begin

You can perform the following types of backup operations: Full, Incremental, Differential or Synthetic Full.

Read Full Backups before performing a Full Backup.

Read Incremental Backups before performing a Incremental Backup.

Read Differential Backups before performing a Differential Backup.

Read Synthetic Full Backups before performing a Synthetic Full Backup.

Required Capability: See Capabilities and Permitted Actions

To start an immediate backup job:

1. From the CommCell Browser, expand Client Computers by double-clicking Client Computers | iDA File System | defaultBackupSet. The default and other subclients (if available) are displayed on the right-hand windowpane.

2. To back up the default subclient, right-click the subclient, and click Backup.

3. From the Backup Options dialog box, select Run Immediately.

4. Select Full, Incremental, Differential or Synthetic Full backup.

In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full

When this registry key is configured on the client, it will override the global setting set by the qoperation command.

If suspect or shutdown state is specified, both suspect and standby databases are discovered.


of 108

Backup.

5. Click OK. You can track the progress of the backup job from the Job Controller window. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically. Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary.

6. When the backup has completed, the Job Controller displays Completed.

After running a backup, you may want to verify the backup data. You can do this by viewing the Backup History. For more information, see Backup Job History.

Schedule Backups

You can schedule backups to occur with the following procedure. You will be prompted to create a schedule for the data protection operation after selecting your data protection options.

Before You Begin

All Agents

Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to secure all of the data for the agent. Note this does not apply to archive operations.


To schedule a backup operation:

1. From the CommCell Browser, select one of the following:

To back up a subclient, right-click the subclient and click Backup.

To back up a backup set or instance, right-click the backup set or instance, click All Tasks, and click Backup All Subclients.

To back up the default backup set, right-click the agent or instance node, click All Tasks, and click Backup Default Backup Set.

For the Lotus Notes Document iDataAgent, to back up a partition, right-click the partition you

You can also run backups of the following:

For a user-defined backup set or instance, right-click the backup set you want to back up, click All Tasks, and click Backup All Subclients.

For the Lotus Notes Document iDataAgent, to back up a partition, right-click the partition you want to back up, click All Tasks, and click Backup Default Backup Set. For the Lotus Notes Database iDataAgent, to back up a partition, right-click the partition you want to back up, click All Tasks, and click Backup All Subclients.

For Agents that do not have backup set or instance levels, to back up all subclients, right-click the agent icon, click All Tasks, and click Backup All Subclients.

If you chose a level higher than subclient (i.e., backup set, etc.), you are prompted to confirm that you want to back up all the subclients below that level/node. Click Yes.

Starting a data protection operation on a backup set, instance or agent level causes the system to start individual data protection operations for each subclient contained therein. If the subclients are associated with the same storage policy, then their operations will run sequentially unless that storage policy is configured to accommodate multiple data streams.


of 108

want to back up, click All Tasks, and click Backup Default Backup Set. For the Lotus Notes Database iDataAgent, to back up a partition, right-click the partition you want to back up, click All Tasks, and click Backup All Subclients.

For Agents that do not have backup set or instance levels, to back up all subclients, right-click the agent icon, click All Tasks, and click Backup All Subclients.

2. If you chose a level higher than subclient (i.e., backup set, etc.), you are prompted to confirm that you want to back up all the subclients below that level/node. Click Yes.

3. From the Backup Options dialog box, select the type of backup that you want to initiate. In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup.

4. Click Schedule. Click OK to continue.

5. From the Schedule Details (Schedule Details) dialog box, create a schedule for this operation. For step-by-step instructions, see Create a Job Schedule. Click OK to continue.

6. Your backup operation will execute according to the specified schedule.


Use this procedure to backup Transaction logs.

SQL Server Transaction Log Backups can be automatically performed immediately after a full or differential backup by selecting the Start Log Backup after Successful Backup advanced backup option.

Before You Begin

Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to secure all of the data for the agent.


To start an immediate backup job:


To backup a subclient, right-click the subclient to want to backup and click Backup.

To backup a user-defined backup set or instance, right-click the backup set you want to backup, click All Tasks, and click Backup All Subclients.

To backup the default backup set, right-click the agent or instance node, click All Tasks, and click Backup Default Backup Set.



4. Select Transaction Log backup. In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup.

5. Click OK. You can track the progress of the backup job from the Job Controller window.

6. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If



of 108

you are using a library, you will not receive this prompt. The system loads the tapes automatically.

7. When the backup has completed, Job Controller displays Completed.

NOTES

All Agents

Starting a backup on a backup set, instance or agent level causes the system to start individual backup jobs for each subclient contained therein. If the subclients are associated with the same storage policy, then their jobs will run sequentially unless that storage policy is configured to accommodate multiple data streams.

Microsoft SQL iDataAgents

When File/File Group subclient jobs are scheduled and the instance property Use VSS is selected, backups for File and File Group subclients run successfully as scheduled.

In order to perform a Transaction Log backup the following is required:

SQL Server database must be in full or bulk-logged recovery mode.

When running a transaction log backup through the CommCell Console, the system default is to truncate the log. To override the default, select Do not truncate log from the Backup Options dialog box. When running a transaction log backup through the command line, the system default is to not truncate the log. To override the default, run the backup job with an -af input file containing the argument file [options] QB_TRUNC_LOG.

Start a Backup in the Suspended State

Use the following procedure to start a backup in the suspended state.

Before You Begin



To start an immediate backup job with advanced backup options:





For Lotus Notes iDataAgent, to backup a partition, right-click the partition you want to backup, click All Tasks, and click Backup Default Backup Set.

For Agents that do not have backup set or instance levels, to backup all subclients, right-click the agent icon, click All Tasks, and click Backup All Subclients.



4. Select the type of backup that you want to initiate. In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full

Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary.


of 108

Backup.

5. Click the Advanced button to open the Advanced Backup Options dialog box.

6. Click on the Advanced Backup Options (Startup) tab, and select Startup in suspended state and click OK.

7. From the Backup Options dialog box, click OK. You can track the progress of the backup job from the Job Controller window.

8. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically.


Start a Backup on New Media

Use the following procedure to start a backup on new media.

Before You Begin












4. Select the type of backup that you want to initiate. In certain circumstances a non-full backup may automatically be converted to a full backup. For a listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup.


6. Click on the Advanced Backup Options (Media) tab, and select Start new media and click OK. If you would like jobs with other Job IDs to use this new media, also select the Allow other




of 108

schedule to use media set option.




Start a Backup that Marks Media Full on Completion

Use the following procedure to start a backup that marks media full on completion.

Before You Begin














6. Click on the Advanced Backup Options (Media) tab, and select Mark media full after successful operation and click OK.


8. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If




of 108

you are using a library, you will not receive this prompt. The system loads the tapes automatically.


Start a Backup with a Set Job Priority

This option allows you to manually set a job priority. This is useful if you have jobs that are very important and must complete, and/or jobs that can be moved to a lower priority. For more information, see Job Priorities and Priority Precedence.

Before You Begin














6. Click on the Advanced Backup Options (Startup) tab, and select Change Priority and then enter a value. Click OK to continue.





Your cartridges should be appropriately labeled. This will enable you to


of 108


Start a Backup with Vault Tracking enabled

Use the following procedure to start a backup with Vault Tracking enabled.

For additional information, see the following:

VaultTracker

VaultTracker Enterprise

Before You Begin

Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to secure all of the data for the agent.



1. select one of the following:










6. Click on the Vault Tracking tab, and select the vault tracking options you want to use and click OK.



locate the correct cartridge for a restore job, if necessary.


Your cartridges should be appropriately labeled. This will enable you to


of 108


Enable (or Disable) SnapProtect for a Subclient

Before you Begin

When you enable SnapProtect for a subclient, all the backups performed for the selected subclient will be using the SnapProtect feature. Review SnapProtect, for more information.

To switch from SnapProtect to a traditional backup for this subclient, you must disable SnapProtect for the subclient.


To enable (or disable) SnapProtect for a subclient:

1. From the CommCell Browser, right-click the subclient for which you wish to perform a SnapProtect operation and click Properties.

2. From the Snap Backups tab, select (or clear) the Snap backup option to enable (or disable) SnapProtect for the selected subclient.

3. Select the relevant snap engine from the Available Snap Engines.

4. Click OK.

Enable VSS backups on a SQL Instance

Related Topics:

Volume Shadow Services (VSS)

Use this procedure to enable VSS backups on a Microsoft SQL iDataAgent instance. For more details, see VSS for SQL Server iDataAgents.


To enable VSS on a subclient:

1. From the CommCell Browser, right-click the instance for which you want to enable VSS, then click Properties.

2. From the General tab of the Instance Properties dialog box, click the Use VSS checkbox.

3. Click OK to save your changes.

This task is now complete.

Back To Top

locate the correct cartridge for a restore job, if necessary.

You should select the snapshot engine applicable to your environment.


of 108

Restore Data - Microsoft SQL Server Topics | How To | Full System Restore | Related Topics

Overview

Default Database Restore

Limitations of Default Browse/Restore Job

Understand Restore Chains

Restore a Database to the Point of Failure

Restore System Databases

Restore Files or File Groups

Recover SQL Server Databases

Apply SQL Server Transaction Logs (Step Restore)

Restore SQL Server Databases to a Point in Time

Restore SQL Server Databases to a Transaction Mark

Partial ("Piecemeal") Restore SQL Server 2005 and later

Restore Latest Backup Data (Warm Database Restore)

Skip Full Backup

Unconditionally Overwrite Existing Database or Files

Set the VDI Timeout Value for Large SQL Database Restores

Restore Multiple SQL Server Databases to a Consistent Time

Restore Considerations for this Agent

Restore Destinations

In-Place Restore

Out-of-Place Restore

Cross-Platform Restores

Cross-Application Restore

Overview

The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.

The SQL Server iDataAgent restores:

Single Database Restore - brings back one database in its entirety using either database restores or file group restores.

Multiple Database Restore - can be run from the instance level, use this to restore multiple databases simultaneously. Note that multiple database restores cannot be performed at the file group level.

Additionally, the SQL Server iDataAgent restores:

File and File Group Restores - require transaction log backups. Can be used to bring back individual files that may have been damaged. When you restore all the file groups within a database, it is effectively a database restore.

Point in Time Restores - require transaction log backups, allowing you to restore a database to any


of 108

time down to the second. See Understand Restore Chains.

Transaction Mark Restore - require transaction log backups, allowing you to restore a database to any SQL transaction mark. For multiple databases, the transaction mark must be common to all databases. See Understand Restore Chains.

Restores of VSS backups - must be restored to the same computer.

The SQL Server iDataAgent has additional restore options to facilitate the customization of your restores.

Step Restore - Allows you to append incremental, individual transaction log backups to a database that has already been restored. Allowing you to scan through the changes that have been committed between each log backup. Saving you from having to perform multiple full restores when you are not sure of the point of restore required.

Restoring with a Different Data File Path - You can change the path for data files being restored for any level of restore. This is useful in situations in which you are performing a restore and the default path cannot be used for any reason.

Setting Recovery states during restores:

Recover: database is online, up and running, and available for use

Standby: database is up and readable, but not fully online and write protected

NoRecover: database is offline and not accessible.

VDI Timeout - From the SQL Server iDataAgent's instance properties in the CommCell Console you can modify the VDI Timeout, if required, to facilitate restores involving deleted databases or files.

When utilizing the VSS full backup for a SQL client on Windows Server 2003 or later, the unsupported restore options will be disabled.

SQL Server iDataAgent restores for upgraded versions:

If a SQL Server instance on which backups have been taken is upgraded to a newer version of SQL Server, and a restore is then performed to a time prior to the SQL Server upgrade, then perform a full backup of the database.

Default Database Restore

When you browse or restore data, the system by default returns the requested data based on the latest backups available. This is usually the information that users are interested in. The system does this by using the current date and time as the effective date. The following example discusses how databases are restored.

In the examples that follow, assume that backups are scheduled daily with the first backup occurring on May 10. (The clock times of the backups are unimportant for our purposes.) The figures show which data objects have changed and consequently have been backed up over time.

Assume that on May 16 we request the restoration of the database as it existed in its most recent state (i.e., the default). In response, the system retrieves the most recent full, most recent differential, and all subsequent transaction log backups that occurred prior to the effective date for each database comprising what we refer to as the restore chain. The system then restores these backups for all selected databases.


of 108

In this case, the job would return:

Database A from 5/13

Database B from 5/15 (note the differential backups on 5/11 and 5/12 are skipped)

Database C from 5/10

Limitations of Default Browse/Restore Job

The default manner of the restore job (i.e., restoring data from the current full backup cycle) may not meet your needs in all circumstances. It can only restore the database(s) to the time of the most recent backup. Further, if the requested data was deleted before the most recent full backup, it cannot be restored by the default mode of operation.

The system provides various restore options which extend its restore capabilities and allow you to control the browse and restore processes.

Understand Restore Chains

Once you pick a restore time, the system determines the optimal combination of full, differential and log backups necessary to bring back the database(s) to the selected time. This combination of backups is the restore chain.

For basic database restores, the restore chain consists of the most recent full, the latest differential (if any), and all subsequent log backups (if any) taken prior to the selected restore time.

When restoring databases to a Transaction Mark or when using a Point in Time restore, the restore chain consists of the most recent full, the latest differential (if any), all subsequent log backups taken prior to the selected browse time, and, transparently, the next log backup after the browse time. The transparent inclusion enables restores to a selected point in time.

Restore a Database to the Point of Failure

In the event of a SQL Server database failure, if it is unacceptable to lose changes made to your database since the last backup, it is possible to restore your database to the very moment of failure.

Determine your recovery needs, and select the appropriate restore operation. For any of these operations, you must Back up the Tail of the Transaction Log as a prerequisite.

For SQL Server you can:

Restore the database and log tail. See Browse and Restore.

Restore the database to a time immediately before the failure. See Restore to a Point in Time.


of 108

Restore the database to a Transaction Mark immediately before the failure. See Restore to a Transaction Mark.

Restore only the damaged Files and log tail. See Restore One or More Files or File Groups.

Restore all Files/File Groups and log tail. See Restore the Entire Database at the File/File Group Level.

Restore all Files/ File Groups to a time immediately before the failure. See Restore to a Point in Time.

Restore all Files/ File Groups to a transaction mark immediately before the failure. See Restore to a Transaction Mark.

Restore System Databases

When restoring the master database, the SQL Server service must be stopped and restarted in single-user mode. The system informs you of this and gives you the option to continue (i.e., stop and restart the SQL Server service in single-user mode, or to cancel the restore job). If you continue the restore job, the system stops and restarts the SQL Server service in single-user mode as part of the restore job.

When restoring the msdb database on a SQL Server, the system displays a message stating that the SQL Server Agent service cannot be running during the restore.

To shut down the SQL Server Agent and continue, click Yes.

To abort the job, click Cancel.

To continue the job without shutting down the SQL Server Agent service, click No. If you click No and the SQL Server Agent service is running, the job fails; if it is not running, the job continues normally.

After restoring the msdb database, the SQL Server Agent service is not automatically started. It must be manually restarted.

Restore Files or File Groups

File/File Group restores give you the ability to restore only the files that have been compromised in the event of a failure. The system enables you to restore specific files and file groups from both:

database backups

file and file group backups

As part of a File/File Group restore job, the system applies all necessary Transaction Log backups. If you will be executing File/File Group restore jobs, plan to back up Transaction Logs regularly, because File/File Group restores cannot run without them.

In addition, File/File Group restore jobs can be used to recover the database in its entirety. See Restore the Entire Database at the File/File Group Level for step-by-step instructions.

File/File Group restores are commonly used for situations in which perhaps only individual data files on a database has become damaged. Imagine the time savings in being able to restore only one 100 gigabyte file group versus the entire 1,000 gigabyte database.

To restore files and file groups, the databases on which the file/file groups reside must be configured for

System databases cannot be moved.

System databases cannot be restored on top of exiting system databases on a different instance (also considered a move operation).

System databases can restore on top of the same database on the same instance provided the database name and filenames are not changed (i.e., an in-place restore).

System databases can be restored to any SQL instance provided both the database name and filenames are changed.

In a clustered environment, the SQL Server Agent service should be stopped from the Cluster Administrator.


of 108

transaction log backups. The system restores the most recent full and differential backups, then replays the transaction logs up to the specified restore time.

For a single data file, the file/file group restore chain consists of the most recent full backup, the most recent differential (if any), and all subsequent transaction log backups that occurred prior to the restore time. See Restore one or more Files or File Groups for step-by-step instructions.

For multiple files or file groups, the same rules apply for each data file, and the log backups to be restored will be determined by the file requiring the oldest log.

SQL Server requires that the primary data file (.mdf) be present when restoring a secondary (.ndf) file. When data files are backed up having the .mdf and .ndf extensions, the system automatically restores the primary (.mdf) file first, and then the secondary (.ndf) files. If no .mdf file is present or if you have changed the database naming scheme, you will need to restore the files in two steps, the primary data file first followed by the secondary files.

Keep in mind that for file and file group restores, it is the transaction log that determines the end point of the restore.

In this example, if you browse data before 5/10 and restore from that same browse time, the system:

Database A - selects the full backup run on 5/5 and the differential from 5/8

Database B - selects the full backup run on 5/5 and the differential from 5/7

Replays the transaction logs of 5/7 and 5/8.

Note that the differential backup on 5/9 will not be included in this file/file group restore even though it is in the browse interval since it occurred after the 5/8 log backup.

Since the file and file group browse searches back in time to the most recent full, when the system presents the results of its browse operation, the tree will include files that existed as of that most recent full even if those items were later deleted. If you are aware of these deletions and do not need the data as part of your restore, you do not have to include those files when selecting what is to be restored. It is in the replaying of the logs that file deletions are captured and removed from the database. Conversely, if a file had not yet been created as of the most recent full backup, the browse results will not present this file for selection. It is the transaction log that will re-create this file for you as part of the restore.

Recover SQL Server Databases

When you run a SQL database restore job, you can select the state in which the database is to be left:

Recover


of 108

No Recover

Standby

By recovering a database you can change the state of that database from No Recover or Standby to Recover. This puts the database back into production mode where it is fully accessible and consistent.

Recover status is reflected in the SQL Restore dialog box when the database or SQL Server state reads ONLINE.

For example, suppose you are applying transaction logs to a database and have decided that the transaction log you just applied is the last you want to apply. To make the database available to the users, restore the database to a RECOVER recovery type. You can recover a single database or all configured databases in a single instance.


The SQL Server iDataAgent allows you to apply transaction logs to a database that was previously restored to a standby state without having to reapply all previous backups. This type of restore job is called a Step Restore.

A Step Restore can be used when you are not sure at what time an event took place. It allows you to restore a transaction log and then view the database offline to determine whether to apply additional logs. If you decide to apply another log, you start the next restore where the last left off.

This option is available only under the following conditions:

Single database restore

The selected database was previously restored to a standby state

The database backup and restore histories have not been removed from the SQL Server's history tables

This option is not available for:

Instance restores

Multiple database restores

SQL Server File/File Group restores

When restoring data protection operations that used VSS to create the snapshot

Restore SQL Server Databases to a Point in Time

A point in time restore job allows you to restore your database to a specific point in time, and, typically, this point in time would be just before an undesired transaction or update to your database. In order to restore a database to a point in time, a transaction log backup must exist.

See Transaction Log Backups for step-by-step instructions for performing a Transaction Log backup.

When you select the Point in Time option, all necessary backups that are required to restore the database to the indicated time are restored. No further actions are necessary. The database is automatically set to a recovered state.

When restoring multiple databases, the Point in Time functionality will apply only to databases that have log backups that include the selected Point in Time. Other databases have to use the most recent backup prior to the selected time. All databases are recovered.

If you have changed a storage policy for a default subclient, and want to restore to a point in time prior to the change (i.e., restore from previous storage policy), perform a Full backup of the database as soon as possible. Data on the old storage policy is not considered as the most recent cycle and when it exceeds its retention period, it can be pruned.


of 108

Restore SQL Server Databases to a Transaction Mark

For SQL Server clients, the agent provides the ability to restore databases to transaction log marks. This can be useful in situations where a transaction has caused undesirable results on a database and you need to go back to the point before that occurred.

For any databases that have transaction marks in the transaction log, you can restore to a point directly before a transaction mark or at the marked transaction. When you select a transaction mark, the system restores all necessary backups to restore the database(s) to the indicated transaction mark. No further restores are necessary.

Partial ("Piecemeal") Restore for SQL Server 2005 and later

Partial restores, known as "Piecemeal Restore" in SQL Server 2005 and later, allow databases that contain multiple filegroups to be restored and recovered in stages. The process starts with a restore of the primary filegroup using the Partial Restore option, then a restore or recover of one or more secondary filegroups.

For more information, refer to SQL Restore Options (General).


The system allows you to perform restores of the latest backup data of one or more non system secured databases in the SQL Server. This functionality enables you to easily maintain a spare of one or more databases (hot standby server) in the event of a database or server failure of the main SQL Server computer.

You can also schedule these latest backup restores so that they automatically occur at a specified interval. Matching the restore schedule with a backup schedule on the source database keeps the restored databases up to date automatically.

Restore Latest Backup Data works by restoring the most recent full backup and then performing a search to determine if any further backups exist. If any further backups do exist, they are applied in order. If the discovered backup is a transaction log, then the log is applied. If the discovered backup is a differential, then all transaction logs between the full and the differential are ignored. So long as a new full database backup is not discovered, only Transaction Log and or Differential backups are applied to the database.

The restore jobs can be left in STANDBY mode to continually apply logs and allow you to view the database between restores. Recovery from STANDBY mode requires more processing than recovery in NORECOVER mode.

You can choose NORECOVER as the recover mode for the restore jobs. This brings the database online quicker and saves disk space that would be taken by the UNDO files associated with STANDBY mode.

Choosing RECOVER mode leaves your backup server in an online state when completed. With this online status selected, subsequent restores cannot be performed.

See Restore Latest Backup Data (Warm Database Restore) for more information.

Skip Full Backup

Select this option to NOT restore the last full backup since the specified date and time, but to instead restore only the transaction log backups. This option can be useful if the latest full backup has already been restored by third-party software and thus a restore of the SQL iDataAgent full backup is not necessary. Note that in such a case, this option only needs to be selected if a SQL iDataAgent full backup exists which is later than the full backup currently restored on the client by a third-party software.

See Skip Full Backup for step-by-step instructions.


of 108


When this option is checked, data being restored is unconditionally written to the specified location and will overwrite the files of any database that is currently using the database name specified by you. This implements the T-SQL REPLACE command.

When the option is unchecked, restore prevents the accidental data files overwrite by failing the job.

See Unconditionally Overwrite Existing Database or Files for step-by-step instructions.

Set the VDI Timeout Value for Large SQL Database Restores

For SQL Server, you may have to administer this value during the restore of a SQL database that has been dropped or does not exist on the SQL server. This is especially true for large databases. The VDI Timeout setting is applied to all SQL Server Agents on the affected client.

During the restore of a SQL database that has been dropped or does not exist on the SQL Server being restored to, the SQL Server automatically re-creates and initializes the database files before any data is actually read from the tape and written to the database. This file re-creation time can take as long as the initial time to create the database. This is due to the Windows operating system C2 requirement of initializing the file during creation. Re-creation times of database files for a 30gig database of nearly one hour have been seen. (This depends greatly on your hardware.) The actual restore of data occurs after this initialization.

The system uses the API (application interface) called VDI (Virtual Device Interface) to communicate with the SQL server for all backup and restore operations. When restoring a database, the VDI timeout represents the time the system must wait for the SQL server to become ready to accept data into the database. If the database files do not exist, a restore command to the SQL server will automatically create them. The time required to create the file(s) will be the same as when you first created the database or altered the database and added the file(s).

When issuing a VDI command to the SQL server, the system software must wait for the command to complete before issuing another command. By default, the system will wait 50 minutes (10 retries of five minutes each) for the SQL server to respond to a VDI command before giving up. If the SQL server takes longer then this timeout value, the system assumes that the command failed, and it aborts the operation.

If the database you are attempting to restore is particularly large, it may become necessary to increase this time-out value. (This can be seen by observing VDI time-outs in the cvsqlcommand.log file located in the install\Log Files directory on the SQL Client computer).


For some SQL server environments, you may have multiple databases for which absolute synchronization of the databases after a restore is critical.

Transaction Mark restores and Point In Time restores are two means of keeping your databases in sync.

For transaction mark restores, you must administer and maintain your Microsoft SQL server transaction marks so that they are available for use by the SQL iDataAgent.

Point in time restores use log backups to get your databases back to a specific minute and second. Backing up the tail of the log will be critical if you are restoring to just before the point of failure.

Restore Considerations for this Agent

Before performing any restore procedures for this agent, review the following information.

Review the general restore requirements described in What You Need to Know Before Performing a Restore.


of 108

Keep in mind that for this or any SQL restore to take place, you must first have a SQL server instance up and running.

When restoring databases backed up using VSS:

VSS-enabled backup jobs for this agent must be restored to the original instance.

When using the new SQL 2005 VSS Writer, databases can be moved to a new location on the server and can be renamed. Data files cannot be renamed.

To restore any system database that was previously backed up using VSS, the SQL Server services have to be stopped and restarted in single user mode.

If the database is installed on the system drive, non-system databases will need to be manually brought back online after the restore.

For the SQL Server iDataAgent, understanding how backups are scheduled across multiple databases is crucial to obtain the desired restore results.

When performing a SQL Server Agent restore job, the difference between how an instance restore works, versus a multiple database restore, is content-based:

Instance Restore. If you perform an instance restore, all the databases are restored in one simultaneous job. If your instance has never had its system databases backed up and you perform an instance restore, the remaining databases are restored as individual jobs.

Multiple Database Restores. If you select all the databases of an instance, the restore is one simultaneous job. If you select multiple databases that are not system databases, they restore as multiple jobs.

When restoring to the point of failure, you must first backup the tail of the transaction log. See Restore a Database to the Point of Failure for an overview.

If the database is upgraded, the next backup that is run detects the new version. The version is refreshed and displayed in the instance Properties dialog box and for the SQL Server iDataAgent, it is displayed during a browse operation. For more information, see Browse Databases.

From the SQL Restore dialog box:

For multiple database restores: enter the Restore Time that will work for all the databases within your instance.

For single database restores: From the Restore Time list, select the backup you want to restore. Based on the selected Restore Time options, the necessary backups are restored.

The default time allocated for backup and restore operations of SQL databases is 0 (infinite). If a backup or restore operation fails due to a timeout being reached, you can configure the nSqlQueryTimeout registry key to increase the amount of allocated time for backup or restore operations.

Restore Destinations

By default, the SQL Server iDataAgent restores data to the client computer from which it originated; this is referred to as an in-place restore. You can also restore the data to another Client computer in the CommCell. Keep in mind the following considerations when performing such restores:

The destination client must reside in the same CommCell as the client whose data was backed up.

Note that when you perform restores other than in-place restores, the restored data assumes the rights (i.e., permissions) of the parent directory.

The following section enumerates the types of restore destinations that are supported by the SQL Server iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.

In-Place Restore Same path/destination


of 108

Out-of-Place Restore Same path/destination

Different path/destination

Keep in mind that out-of-place restore operations are also subject to the conditions described in Cross-Application Restores.

Cross-Platform Restores Same Operating System - Different Version

Cross-Application Restore

Support for restoring/recovering/retrieving data from one application version to another generally follows the same compatibility support provided by the associated third-party application vendor, unless otherwise noted.

Back to Top

Restore Data - Microsoft SQL Server - How To Topics | How To | Full System Restore | Related Topics

Recovering a Database

Recovering All Configured Databases in a Single Instance


Restore a SQL Server Database to a Point in Time

Restore a SQL Server Database to a Transaction Mark

Performing a Partial ("Piecemeal") Restore of a SQL Server Database


Skip Full Backup


Restore Destinations:

Restore with a Different Data File Path (Copy a Database)

Restore to a Different SQL Server Instance

Back Up the Tail of the Transaction Log

Restore a Single Database Without Browsing

Restore SQL Server Files/File Groups

Restore One or More Files or File Groups

Restore the Entire Database at the File/File Group Level

Restore a SQL Server Database with a Different Name (Move a Database)


Set the VDI Time-out Value for Large SQL Database Restores

Recovering a Database


of 108

Before You Begin:

Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore operation.


To RECOVER a database:

1. From the CommCell Browser, right-click the database you want to recover, click All Tasks and then click Recover Only.

2. Click OK to confirm that you want to Recover the database. The SQL iDataAgent recovers the selected database to an ONLINE status.

Recovering All Configured Databases in a Single Instance

Before You Begin:



To RECOVER all configured non-system databases in a single instance:

1. From the CommCell Browser, right-click the instance node, click All Tasks and then click Recover SQL Server.

2. Click OK to confirm that you want to Recover all non-system databases. The SQL iDataAgent recovers the SQL Server to an ONLINE status.


Before You Begin



To perform a Step Restore on a database:

1. Begin any SQL Server restore procedure.

2. When you reach the SQL Restore (General) dialog box:

a. Select the desired Destination Server.

b. Select Database Restore as the Restore Type.

c. Select the Full backup from the Restore Time.

d. Select NORECOVERY or STANDBY as the Recovery Type.

3. When restoring encrypted data, refer to Data Encryption.

4. Click OK to start the database restore.

5. When the database restore is completed, repeat Step 1 in order to return to the SQL Restore (General) dialog box.

The Step Restore option is only available when the database is already in a NORECOVERY or STANDBY state and an additional log is available for restore.


of 108

a. Select the desired Destination Server.

b. Select Step Restore as the Restore Type

c. Select the desired LOG backup from the Restore Time.

d. Select NORECOVERY or STANDBY as the Recovery Type

6. Start the restore. The SQL Server iDataAgent applies the next log in the sequence.

7. To apply additional transaction logs, repeat steps 5 and 6 as needed.

8. When you are applying the last transaction log, select RECOVER as the Recovery Type. This returns the database to a recovered state.

Restore a SQL Server Database to a Point in Time

Before You Begin


In order to restore a database to a point in time, a transaction log backup must exist.


To restore to a point in time:

1. Begin any restore procedure.

2. When you reach the SQL Restore (General) dialog box, select Point in Time and select a Restore Time.

3. Continue your restore.

NOTES

After performing a point in time restore job, the next backup job for that database is automatically converted to a full backup.

Restore a SQL Server Database to a Transaction Mark

Before You Begin



To perform a transaction mark restore job:

1. Begin any restore procedure. For file/file group restore jobs, you must perform a complete restore of all database files in order to restore to a Transaction Mark.

2. When you reach the SQL Restore (General) dialog box, select Transaction Marks and select a marked transaction from the list. When multiple databases are being restored, the list of transaction marks includes only those marks that are common in name and timestamp to all the selected databases within the selected backup cycle.

3. Select Stop at Mark or Stop Before Mark.

If you have already applied the last transaction log and the database is in NORECOVERY or STANDBY mode, and you want to return the database to a ready state, you can manually recover the database.


of 108


NOTES

After performing a transaction mark restore job, the next backup job for that database is automatically converted to a full backup.

Performing Partial ("Piecemeal) Restore of a SQL Server Database

Before You Begin


In order to restore a database to a point in time, a transaction log backup must exist.


To restore to a point in time:


2. When you reach the SQL Restore (General) dialog box, select Partial Restore.


NOTES

After performing a partial ("piecemeal") restore job, the next backup job for that database is automatically converted to a full backup.


Before You Begin


To schedule a restore of pass-phrase protected, encrypted data, you must first export the pass-phrase to the specific destination client using the Client Properties Encryption tab.

Be sure to confirm the database and file locations on the receiving server. These locations do not need to exist prior to performing the latest backup data restore job.


To restore the latest backup data:

1. From the CommCell Browser, right-click the SQL server or database you want to restore, click All Tasks, and click Browse SQL Server or Browse SQL Instance as appropriate.

2. From the Browse Options dialog box, click Database, make any other desired selections in the dialog box, and then click OK.

3. From the Latest Data window, click the database that you want to restore and then click Recover All Selected.

4. From the SQL Restore Options dialog box, select the destination server that is to receive the database.

5. From the Restore Types list, click Latest Backup Data. Then make any other selections in this dialog box as appropriate.

If you do not need to view the database you can select a recover type of NORECOVER.


of 108

6. Click Advanced | Options to verify that the destination drive appears in the Advanced Restore Options dialog box. Click OK to return to the SQL Restore Options dialog box.

When restoring encrypted data, refer to Data Encryption.

7. After completing your selections, you can schedule the restore.

Click the Job Initiation tab from the SQL Restore Options dialog box, click Schedule, click OK, and enter your selections in the Schedule Details (Schedule Details) dialog box. Note that clicking OK from this dialog box saves your schedule. See Scheduled Data Recovery Operations for an overview of this feature.

You can track the progress of the restore job using the Job Controller. While the job is running, you can right-click the job in the Job Controller and select Detail to view information on the job.

8. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

NOTES

When scheduling, remember to coordinate backup jobs and restore jobs such that there are no resource conflicts.

Skip Full Backup

Before You Begin



To skip the restore of the last full backup:


2. When you reach the SQL Restore (General) dialog box, select Skip Full Backup.


NOTES

Even if a full backup is displayed in Restore Time, the last full backup will not be restored.


Before You Begin



To unconditionally write to the specified location and overwrite the files of any database:


2. When you reach the SQL Restore (General) dialog box, select Unconditionally overwrite existing database or files.


Restore with a Different Data File Path (Copy a Database)


of 108

Before You Begin


You can change the path for data files being restored for any level of restore. This is useful in situations in which you are performing a restore and the default path cannot be used for any reason, such as the following examples:

a destination server does not have the corresponding path

when restoring the database to the same server, but restoring the database under a different name.

Note, that if the database file path is changed, without changing the name of the database, then the existing database will be overwritten and will point to the new location.


To restore with a different data file path:


2. When you reach the SQL Restore (General) dialog box, click Advanced.

3. From the Options tab of the Advanced Restore Options dialog box, in the Physical Path column, click each of the files of the database you want to redirect and change the path and/or filename to a new value. If there are many files in the database you want to move, click Find & Replace and enter the necessary values to change them all at once. If the path entered does not exist, it will be automatically created during the restore operation.

4. Continue the restore procedure.

Restore to a Different SQL Server Instance

Before You Begin


When this restore takes place it attempts to restore the data files to the same path on the destination server as it was using on the original server. If you want to change the path, refer to Restore with a Different Data File Path (Copy a Database).


To restore to a different SQL Server instance:


2. When you reach the SQL Restore (General) dialog box, select the target server from the Destination Server list.

3. Continue the restore procedure.

Back Up the Tail of the Transaction Log

In the event of a database failure, if it is unacceptable to lose changes made to your database since the last backup, you need to back up the tail of the transaction log prior to running a restore.

Before You Begin



of 108

The requirements to accomplish this are:

SQL Server database must be in full or bulk-logged recovery mode

Microsoft SQL Server iDataAgent: Transaction log file(s) must be intact


To back up the Log Tail:

1. Right-click the database, click All Tasks (if appropriate), and click Backup or Backup SQL Server.

2. Select Run Immediately, the Transaction Log backup type, the Do Not Truncate Log check box, and click OK.

The use of a log tail backup in your restore job is no different than using a standard log backup and, in fact, appears in your Restore Options dialog box as a standard log backup.

Now you're ready to restore. Refer to Restore a Database to the Point of Failure to select the appropriate restore job.

Restore a Single Database Without Browsing

Use this procedure when you want to retrieve the latest backup job.


To restore a database without browsing:

1. From the CommCell Browser, right-click the database that contains the data you want to restore, click All Tasks and then click Restore Database.

2. In the SQL Restore (General) dialog box, from the Restore Time list, select the backup you want to restore. Based on the selected Restore Time options, the necessary backups are restored.

3. When restoring encrypted data, refer to Using Data Encryption.

4. Start the restore.

5. If you are restoring the master database, you are informed that the SQL server must be stopped. Click Yes to continue or No to cancel the restore job without shutting down SQL server.

Restore One or More Files or File Groups

Before You Begin:


Review the discussion Restore Files or File Groups.

Make sure you have backed up the log tail. See Back up the Tail of the Transaction Log for step-by-step instructions.

For a client on a Windows Server 2003 platform or later, if you are running VSS backups, the Restore Files/File Groups command is unavailable.


To perform a SQL Server file/file group restore job:

1. From the CommCell Browser, right-click the database that contains the files or file groups you want to restore, click All Tasks and then click Browse SQL Instance.

2. In the Browse Options dialog box, click File/File Groups. Then click OK to accept all defaults to browse the latest backups for the selected data or see Browsing Data for a list of customized browse


of 108

operations and their step-by-step instructions.

3. From the Browse window, select one or more files or file groups. See Select Objects From the Browse Window for Restore/Recover for more information.

4. Continue with your restore. When restoring encrypted data, refer to Data Encryption.

5. Click OK to start the restore.

Restore the Entire Database at the File/File Group Level

Before You Begin:

Make sure you have backed up the log tail if you want to restore the database to the point of failure. See Select Objects From the Browse Window for Restore/Recover for step-by-step instructions.

For a client on a Windows Server 2003 platform or later, if you are running VSS backups, the Restore Files/File Groups command is unavailable.


To restore an entire SQL Server database through File/File Groups:

1. From the CommCell Browser, right-click the database you want to restore, click All Tasks and then click Browse SQL Instance.

2. In the Browse Options dialog box, click File/File Groups, select the appropriate browse time option, and click OK.

3. In the Browse window, select the database in the left pane, and click Recover All Selected.

4. In the SQL Restore dialog box, the Database Restore option should be already selected. Select additional restore options as needed.

5. When restoring encrypted data, refer to Data Encryption.

6. Click OK to start the restore.

Restore a SQL Server Database with a Different Name (Move a Database)

Before You Begin


VSS-enabled backup jobs must be restored to the exact server, database, and file name from which they originated.

If you are attempting to rename a database and keep its original path, you must first delete the original database from SQL Server before performing this restore. This procedure attempts to restore the renamed database to the same path as the original database. Should the original database still exist at this path, the restore will fail. Alternately, you can rename the database and change its path without deleting the original database. For this option, refer to Restore with a Different Data File Path (Copy a Database).

For File/File Group restore jobs, you must perform a complete restore of all database files in order to restore to a different SQL Server instance.

If you are planning to restore only certain files or file groups, use Restore One or More Files or File Groups procedure.

System databases cannot be moved.


of 108


To restore a SQL Server database with a different name:


2. When you reach the SQL Restore (General) dialog box, click Advanced.

3. From the Options tab of the Advanced Restore Options dialog box, in the Database column, click each database you want to rename, and change the name to the new value. When a change is made to one database in this column, the change is automatically propagated to the other files of the same database.



Before You Begin


Run log backups for each database

Run log tail backup on all databases to be synchronized, refer to Restore a Database to the Point of Failure


To restore multiple databases to a consistent time:

1. For each instance: From the CommCell Browser, right-click an instance, click All Tasks and then click Browse SQL Instance.

2. Browse for databases based on the criteria correct for your situation. For more information, refer to Browsing Data.

3. Select the non-system databases you want to restore and click Recover All Selected.

4. In the SQL Database Restore Options dialog box, follow the procedure you want to execute:

Restore to Transaction Marks

Restore to a Point in Time


Before You Begin

The VDI Timeout setting will be applied to all SQL Server iDataAgents on this client.


To set the VDI time-out value:

1. From the CommCell Browser, right-click the SQL Server instance that contains the data files you

System databases cannot be restored on top of exiting system databases on a different instance (also considered a move operation).

System databases can restore on top of the same database on the same instance provided the database name and filenames are not changed (i.e., an in–place restore).

System databases can be restored to any SQL instance provided both the database name and filenames are changed.


of 108

want to restore, and click Properties from the shortcut menu.

2. From the General tab, increase the VDI Timeout, and click OK.

3. After changing the VDI Timeout setting, begin any restore procedure as usual.

Basic Restore Topics | How To | Related Topics

Overview

Time Range Options

Overview

There are two functions that help you retrieve backed up data from the backup media: Browse and Restore. Browse operations allow you to view the data that has been backed up for a client computer without actually restoring the data. Restore operations retrieve the data from the backup media and restore it to the desired location.

In the CommCell Browser, the Browse and various Restore commands appear in the right-click menus at the agent, instance and/or backup set levels, depending on agent.

Using the Restore commands, i.e., restoring without browsing, is most appropriate when you want to restore the latest backup job for an agent, instance or backup set and want to retain the current file structure.

In certain situations and for supported agents, Restore operations can run without utilizing the Browse feature. For example, if you know the path/name of the volume of the data that you want to restore, you can restore it without browsing. In these agents, this procedure is most appropriate when the number of paths for the data that you want to restore is small or when the data that you want to restore is at a single volume. If you want to restore data from many different paths or volumes, you should probably select the data from the Browse window.

Time Range Options

In a Basic Restore, point-in-time data can be restored by specifying time range options in the Advanced Restore Options (Time Range) dialog box. See Time Range Options for Basic Restore for step-by-step instructions. When a time range is specified for a Basic Restore, the latest version of the backup job within the given time range will be restored.

Basic Restore - How To Topics | How To | Related Topics

Basic Restore

Advanced Restore Options

Time Range Options for Basic Restore


of 108

Basic Restore

Before You Begin:



To restore data without using browse:

1. From the CommCell Browser, right-click the agent, instance or backup set that contains the data you want to restore, click All Tasks and then click the available Restore command (command names vary by agent).

2. In the Restore dialog box, type the starting path of the data you want to restore.

3. From the Restore Options and Advanced Restore Options dialog boxes, select the restore options that you want to use. When you accept all the default settings, you will be restoring the selected data to its original location. See Restore Backup Data for complete information on the agent-specific restore options.

4. After completing your selections, you can either start an immediate restore or schedule the restore.

If you want to schedule the job, click the Job Initiation tab from the Restore Options dialog box, click Schedule, and enter your selections in the Schedule Details (Schedule Details) dialog box. Clicking OK from this dialog box saves your schedule. See Scheduled Data Recovery Operations for an overview of this feature.

If you want to run the job now, accept or click Run Immediately in the same tab and then click OK.

You can monitor the progress of the restore job in the Job Controller. While the job is running, you can right-click the job in the Job Controller and select Detail to view information on the job.

After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

Time Range Options for Basic Restore

Before You Begin:



To provide time range options for basic restore:

1. From the CommCell Browser, right-click the agent, instance or backup set that contains the data you want to restore, click All Tasks and then click the available Restore command (command names vary by agent).

2. In the Restore dialog box, type the starting path of the data you want to restore.

3. From the Restore Options and Advanced Restore Options dialog boxes, select the Time Range tab.

4. In the Advanced Restore Options (Time Range) dialog box select Image Browsing option, if required.

In the Specify Restore Time area select the Time Zone for the time range options. Select the Exclude Data Before option and select the start date and time from which you wish to restore data, and select the Browse Data Before option and select the end date and time until which you wish to restore data.


of 108

5. Click OK in the Advanced Restore Options dialog box.

6. Click OK in the Restore Options dialog box to execute the restore.

Back To Top

Browse and Restore Topics | How To | Related Topics

Overview

There are two functions that help you retrieve backed up data from the backup media: browse and restore. In the CommCell Browser, the browse and variously-named restore commands appear, depending on agent, in the right-click menus at the agent, instance and/or backup set levels.

Browse operations allow you to view data that has been backed up by the agent on the client computer and select all or some of that data. Depending on the agent, there are several options available to customize your browse. See Browse Data for comprehensive information on Browse operations.

Restore operations allow you to retrieve data from backup media and restore it to the desired location. Restoring without browsing is most appropriate when you want to restore the latest backup job for an agent, instance or backup set and want to retain the current file structure. See Basic Restore for more information on restoring without using browse.

Browse and Restore

The Browse and Restore procedure is a sequential procedure that combines the two procedures. When you select a Browse command from the CommCell Browser, you can define and run one of many potential browse sequences. At the end of the browse, when you are looking at the resulting information presented in the Browse window, you can continue with a restore procedure simply by selecting data and clicking the Recover All Data button. As with the browse, depending on the agent, there are several options available to customize your restore.

Perform a browse and restore operation when you want to:

restore from an earlier backup

restore only select files/objects

restore deleted files/objects

when you don't want or don't need to retain the current file structure

to utilize browse options

Browse and Restore - How To Topics | How To | Related Topics

Browse and Restore

Browse and Restore

Before You Begin:




of 108

To browse and restore data:

1. From the CommCell Browser, right-click the agent, instance, backup set, or Legal hold set (for Legal Hold data) that contains the data you want to restore, click All Tasks and then click the available Browse command (command names vary by agent).

2. Run a browse operation. See Browse Data for a list of customized browse operations and their step-by-step instructions. If you accept all defaults, you will be browsing the latest backups for the selected data.

3. From the Browse window, Select Objects From the Browse Window for Restore.

4. From the agent's Restore Options and Advanced Restore Options dialog boxes, select the restore options that you want to use. For agents with multiple tabs, do not click OK until you have used all of the desired tabs. When you accept all the default settings, you will be restoring the selected data to its original location. See Restore Backup Data for access to complete information on the agent-specific Restore Destination options and procedures available.

5. When restoring encrypted data, refer to Data Encryption for comprehensive feature information and procedures for using the Encryption tab of the Advanced Restore Options dialog box.

6. After completing your selections, you can either start an immediate restore or schedule the restore.

If you want to schedule the job, click the Job Initiation tab from the Restore Options dialog box, click Schedule, schedule the job, and then click OK.

If you want to run the job now, accept or click Run Immediately in the same tab and then click OK.

While the job is running, you can right-click the job in the Job Controller and select Detail to view information on the job. After the data has been restored, you will see a job completion message in the Job Controller and Event Viewer.

Back To Top


of 108

Instances - Microsoft SQL Server Topics | How To | Related Topics

Overview

Configurable Properties

Overview

In the CommCell Console, you can add and configure an instance for each available SQL Server. Each configured SQL Server instance automatically spawns a default Database subclient that can include three SQL Server system databases as well as user-defined databases. See Subclients - SQL Server for an overview. Note that the system databases are just like user-defined databases in the system.

See Instances for an overview of Instances. Given below is a list of what you need to provide before creating a SQL Server 2000 or 2005 instance.

Local administrator with SQL sysadmin role

Account password

Default database storage policy

Default log storage policy

Use the procedures within Add an SQL Server Instance for the following instance scenarios:

When you are adding instances in any cases not covered by the previous two bullet items.


Once installed, the agent is configured and is therefore able to manage the data or volumes on the client computer. However, you can change certain aspects of the instance configuration to manage the data in the manner that best suits your needs.

You can view or change the instance configuration from the Instance Properties dialog box. The following information can be configured.

Setting the VDI Time-out Value for Large SQL Database Restores

For Microsoft SQL Server iDataAgents, you may have to administer this value during the restore of a SQL database that has been dropped or does not exist on the SQL server. This is especially true for large databases. See Set the VDI Timeout Value for Large SQL Database Restores for an overview.

Using VSS

Available for SQL Server clients running on Windows Server. When left cleared, all full backups for all databases within the instance will use the traditional backup methods. When selected, traditional full backups for all databases within the instance will be switched to VSS full backups. When cleared after having been selected, subsequent backups will run as their designated type. See VSS for SQL Server iDataAgents for more information.

User Accounts

Use the Accounts tab to identify the account that the system uses to access the associated instance.

See the Microsoft SQL Server iDataAgent section in User Accounts and Passwords for more information.

The following pertains to SQL Server and SQL Server 2005:


of 108

Back to Top

Instances - Microsoft SQL Server - How To Topics | How To | Related Topics

Modify an Instance

Delete an Instance

Add a SQL Server Instance

Change Account for Accessing Instances

Change Account for Executing Pre/Post Commands (Data Protection)

Change Account for Executing Pre/Post Commands (Data Recovery)


Enable VSS of a SQL Instance

Modify an Instance

Required Capability: See Capabilities and Required Actions

To modify an Instance

1. From the CommCell Browser, right-click the instance you want to modify, and then click Properties from the shortcut menu.

2. Click the General tab of the Instance properties box to change the required access information for this instance.

3. If your agent uses the Accounts tab, use this tab to specify the Windows account used by the system. For MySQL iDataAgent, use this tab to specify the MySQL Server user account.

4. If your agent uses the Restore View Names tab, use this tab to enter or modify a list of text patterns for the view through which the system displays a database's data documents when you browse.

5. If your agent has the Security tab, you can view CommCell resource associations to enable or disable user groups that can perform system operations on associated resources.

6. For an Oracle instance, click the Details tab to change the database connect string and other optional parameters.

7. For an Oracle RAC instance, go to the next step. Otherwise, go to Step 12.

8. Click the Details tab, and type or select values for the fields at the bottom of the dialog box as appropriate. For the DB2 DPF instance, to associate a database partition with a different client, click the affected partition in the DB2 Partition Clients field, click Modify, and click from the list in the Edit Directory Share Name Pair dialog box the name of the new client for the partition. Then click OK.

9. Click the Oracle instance (Client/Instance/Status) that you want to modify. Then click Modify.

10. In the Update Instance dialog box, update the desired field values by typing or browsing as appropriate. Then click OK.

One or more of the agents of this type use one or more accounts that are configured from a non-Properties dialog box. See the appropriate section for your agent(s) in User Accounts and Passwords for more information.


of 108

11. Repeat the previous two steps for each Oracle instance that you want to modify.

12. From the Storage Device tab(s), select storage policy copies to be used for, as applicable, data backups, command line data backups and log backups. Within these tabs you can click Data Paths to display the details of the data paths associated with the primary storage policy copy of the selected storage policy.

For the MySQL iDataAgent, select the storage policy for the log backups from the Log Backups tab.

13. If your agent uses the Software Compression tab, and you want to enable software compression for the selected backups, click the tab and select the appropriate option.

14. If you want to enable data encryption, from the Encryption tab select encryption settings for third-party or RMAN command line backups.

15. Click OK to save the configuration changes.

16. A message advises you to schedule backups for your new instance. It is recommended you elect to set a schedule now. If you click No, this procedure is now complete. If you click Yes, a dialog box prompts you to back up all subclients of this instance.

17. Click Yes. The Backup Options dialog box appears, which allows you to create the necessary schedules.

18. From the Backup Options dialog box, select the type of backup that you want to schedule.

19. If you want to access Advanced Backup Options, click Advanced.

20. After selecting the backup type and any advanced options, click OK. The Schedule Details dialog box appears.

21. From the Schedule Details tab of the Schedule Details dialog box, select the scheduling options that you want to apply, then click OK.

Delete an Instance

Before You Begin

For most agents except Oracle and SQL Server, you cannot delete an instance if there is only one instance present for an agent. To delete the final instance for most agents except the ones identified, you must first remove the agent software from the client computer. For Oracle RAC, which does not involve agent software, you can delete the instance under the RAC pseudo-client.

When you delete a specific instance positioned in the level below the corresponding agent or pseudo-client in the CommCell Console, the following actions occur:

The corresponding backup data for that instance becomes immediately unavailable, thus making it inaccessible for restore purposes. In effect, the backup data is deleted.

All child levels contained within the level are deleted in the CommCell Browser.

All job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.

If you delete an Oracle iDataAgent instance included within an Oracle RAC instance (node), the backup data is not deleted, and it is available for restore by another eligible client.

You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.


To delete an instance positioned in the level below the corresponding agent or pseudo-client

1. From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.


of 108

2. Click Yes to confirm the deletion. (Clicking No cancels the deletion and retains the node.)

3. Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

To delete an Oracle iDataAgent instance included within an Oracle RAC instance (node)

1. Right-click the Oracle RAC instance, click Properties, and click Details.

2. Click the instance that you want to delete within Client/Instance/Status and click Delete.

3. Repeat the previous step for each Oracle iDataAgent instance (except the last one remaining) within the Oracle RAC instance that you want to delete.

4. Click OK. This should delete the Oracle iDataAgent instance(s).

Add a SQL Server Instance Before You Begin

You must create a Windows user who has Local Administrator rights to the computer and who is a member of the SQL sysadmin fixed server role for the instance. This account is used to perform jobs on the SQL Server instance, including backups, restores, accessing the Windows registry, and stopping SQL services during system database restores.

The Local rights are needed for system database restore because the sqlserver is brought down in single user mode. They are also needed for VSS restores of the system database because the sqlserver will be stopped and then restarted after the restore. And they are needed to see if VSS services are enabled. SQL rights are needed to connect to a SQL instance.

If the SQL server to which you are installing is also a Windows Domain Controller, you must use an account other than the domain administrator. Create a new user account which has both administrator and SQL 'sa' permissions and use that account.

If the SQL Server service is running using any account other than the Local System account, you will need the user name and password of that account.

For non-Microsoft cluster installations, the instance name must be manually entered in the New SQL Server dialog box.


To add a SQL Server instance to the iDataAgent

1. From the CommCell Browser, open Client Computers, and then the client whose instances you need to add.

2. Right-click the SQL Server icon to open the shortcut menu; click All Tasks, and then click New SQL Server.

3. From the New SQL Server dialog box, click in the Server Name list any SQL instance that is not yet configured within the iDataAgent.

4. Within the Properties section, enter the required account and password.

5. Within the Storage Policies section, select the default storage policies to be used by the default subclient.

6. Click OK to complete the procedure.


With the exceptions noted above, you can no longer access the corresponding backup data for restore purposes.


of 108

Change Account for Accessing Instances


To change a user account for accessing an instance:

1. From the CommCell Browser, expand the tree to view the instance for the affected agent. Then right-click the instance, click Properties, and click Accounts.

2. In the Instance Properties (Accounts) tab, enter (for SQL, MySQL, or Sybase) the user name information. For Sybase and MySQL, also enter SA-related information.

3. Click OK to save the settings.



To change a user account for executing pre/post commands for Data Protection jobs:

1. From the CommCell Browser, expand the tree to view the appropriate level icon for the affected agent.

From the agent, instance/partition, or backup set/archive set level, right-click the appropriate icon, click All Tasks, and click New Subclient from the short-cut menu.

From the subclient level, right-click the subclient icon and click Properties from the short-cut menu.

2. From the Subclient Properties dialog box, create and/or configure the subclient as appropriate. Then click the Pre/Post Process tab.

3. From the Pre/Post Process tab, click Change.

4. From the User Account dialog box, select one of the account options. If you select Impersonate User, type the appropriate user name and password.


Change Account for Executing Pre/Post Commands (Data Recovery)


To change a user account for executing pre/post commands for Data Recovery jobs:

1. From the CommCell Browser, expand the tree to view the appropriate level icon for the affected agent. Then right-click the icon and click All Tasks from the short-cut menu.

2. Click the appropriate Browse or Restore option. Then populate, select, and click as appropriate to access the Restore Options dialog box.

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

4. From the Advanced Restore Options, click the Pre/Post tab.

5. From the Pre/Post tab, select one of the account options in the Pre/Post Impersonation area. If you select Impersonate User, type the appropriate user name and password.



Before You Begin


of 108

The VDI Timeout setting will be applied to all SQL Server iDataAgents on this client.


To set the VDI time-out value:

1. From the CommCell Browser, right-click the SQL Server instance that contains the data files you want to restore, and click Properties from the shortcut menu.

2. From the General tab, increase the VDI Timeout, and click OK.

3. After changing the VDI Timeout setting, begin any restore procedure as usual.

Enable VSS backups on a SQL Instance

Related Topics:

Volume Shadow Services (VSS)

Use this procedure to enable VSS backups on a Microsoft SQL iDataAgent instance. For more details, see VSS for SQL Server iDataAgents.


To enable VSS on a subclient:

1. From the CommCell Browser, right-click the instance for which you want to enable VSS, then click Properties.

2. From the General tab of the Instance Properties dialog box, click the Use VSS checkbox.



Back to Top


of 108

Subclients - SQL Server Topics | How To | Related Topics

Overview


Things to Consider when Creating and Configuring SQL Server Subclients

All SQL Server iDataAgents

Overview

The following table shows subclient creation and configuration details specific to the SQL Server iDataAgents.


Once installed, the agent is configured and is therefore able to manage the data or volumes on the client computer. However, you can change certain aspects of the subclient configuration to manage the data in the manner that best suits your needs.

You can view or change the subclient configuration from the Subclient Properties dialog box. The following information can be configured.

Activity Control

You can enable or disable all operations for this CommCell object and all objects below it. For more information, see Activity Control.

Backup Streams

You can set the number of backup streams. For more information, see Streams.

Agent Type of

Data Default

Subclient created during

install of the

Agent

Supports Default

Subclient

Supports User-

Defined Subclient

Contents of the default

subclient when user-

defined subclient is present

Other Types of

subclients supported

by the Agent

Notes

SQL Server 2000/2005 iDataAgents

SQL Server

2000/2005 databases;

database files;

database file groups

No Yes Yes Databases that are

not assigned to the user-defined

subclients, unless

otherwise configured*

File/File Group

Default subclient is always a "Database" type subclient

*See Caution Against Re-configuring Default Subclient Content.


of 108

Content/Databases

You can define the content of the subclient. Most agents include a configure button that displays a dialog where you can add or modify the data included as subclient content. For step-by-step instructions, see Configure Subclient Content.

Data Transfer Options

Several configurable options to efficiently use available resources for transferring data secured by data protection operations are provided in the subclient. 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.

Data Encryption

You can enable or disable the encryption of data for transmission over unsecure networks and for storage on media. For more information, see Data Encryption.

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 for the subclient including their priority. For additional information, see Configuring Alternate Data Paths for Subclients.

Pre/Post Processes

You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases. For more information, see Pre/Post Processes.

Storage Policies

You can associate the subclient to a storage policy. For more information, see Storage Policies.

Subclient Name

You can rename a subclient. For step-by-step instructions, see Rename a Subclient.

User Accounts

You can define an account with permissions to execute Pre/Post commands for the agent's archive, backup, or volume creation jobs.

See Microsoft SQL Server iDataAgent: Other User Accounts in User Accounts and Passwords for more information.

Backup Conversion Rules

You can prevent backup failure conditions if you enable conversion rules. See Default Subclient Backup Conversion Rules for more information.

Things to Consider when Creating and Configuring SQL Server Subclients

When creating and configuring subclients for SQL Server agents, keep in mind the following considerations:

All SQL Server iDataAgents

When a full or differential backup is performed outside of the system, for example, from Enterprise Manager, the next log backups performed using SQL Server iDataAgent are not converted to a full backup. Therefore, it is recommended to run a full backup with the SQL Server iDataAgent.


of 108

After installing the Microsoft SQL Server iDataAgent, you must use the system to add an instance to the SQL Server iDataAgent to run the first backup. (See Add a SQL Server Instance for step-by-step instructions). The system creates a default subclient for each instance you add named default which is designed to back up all the databases for the instance.

This default subclient is always of the "Database" type. However, you can create additional subclients (user-defined subclients) of both the "Database" and "File/FileGroup" type. Type "Database" user-defined subclients allow you to back up individual databases. Type "File/File Group" subclients allow you to back up data files and file groups. Whenever you assign data to these user-defined subclients, this data is removed from the content of the default subclient. For more information on default and user-defined subclients, see Subclient Backups.

If at some later time you decide to change the way a client computer is backed up, you can always change the configuration, in whole or in part. For example, you can change the associated storage policy for the subclient to back up a database to a different library (which is useful for making backups for offsite storage); or, you can change the number of backup streams.

You can also add new databases to be secured by the system, and remove databases currently secured. As a best practice, it is recommended that you add only a few small databases to each subclient and add larger databases into separate subclients. On a restart condition, the system will back up all databases in the subclient from the beginning. For this reason, you would not want a large database that has completed its backup successfully to be backed up again only because a smaller one has caused a restart to occur.

Caution Against 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 "catch-all" entity for client data. As a result, the likelihood that some data will not get backed up or scanned for archiving would increase.

Back to Top

Subclients - SQL Server - How To Topics | How To | Related Topics

Associate a Subclient to a Storage Policy


Configure a Subclient for Pre/Post Processing of Data Protection Operations

Configure SQL Server 2000/2005 Databases

Configure SQL Server 2000/2005 Files and File Groups

Configure Subclient Content

Configure the Subclient for Data Encryption

Create a New Subclient

Delete a User-Defined Subclient

Enable or Disable Operations

Enable Software Compression for a Subclient

Remove a Process from Pre/Post Processing of Data Protection Operations

Rename a Subclient

Set the Network Bandwidth and Network Agents for a Data Protection Operation


of 108

Set Stream Numbers for Backup and Restore

Associate a Subclient to a Storage Policy


To associate a subclient to a storage policy:

1. From the CommCell Browser, right-click the subclient whose associated storage policy you want to change, then click Properties from the shortcut menu.

2. Click the Storage Device tab of the Subclient Properties dialog box.

3. From the Storage Policy list of the Data Storage Policy tab, select a data storage policy to associate with this subclient. If necessary, click the Create Storage Policy button to create a new storage policy to which the subclient can then be associated.

4. From the Changing a Storage Policy window select the next type of backup operation. Click OK.

5. If applicable for your agent, you can change the number of data streams from the Number of Data/Database Backup Streams field.

6. If applicable for your agent, click the Log Storage Policy tab and select a storage policy to associate with this transaction log subclient from the Transaction Log Storage Policy list. Also, you can set the Number of Transaction Log Backup Streams from this tab.

7. Click OK to save your changes and close the Subclient Properties Storage Device tab.



To change a user account for executing pre/post commands for Data Protection jobs:

1. From the CommCell Browser, expand the tree to view the appropriate level icon for the affected agent.

From the agent, instance/partition, or backup set/archive set level, right-click the appropriate icon, click All Tasks, and click New Subclient from the short-cut menu.

From the subclient level, right-click the subclient icon and click Properties from the short-cut menu.

2. From the Subclient Properties dialog box, create and/or configure the subclient as appropriate. Then click the Pre/Post Process tab.

3. From the Pre/Post Process tab, click Change.

4. From the User Account dialog box, select one of the account options. If you select Impersonate User, type the appropriate user name and password.


Configure a Subclient for Pre/Post Processing of Data Protection/Archive Operations

Before You Begin

We recommend not configuring a pre/post process for a subclient that is currently running a data protection or archive operation.

Verify that there are no pre/post processes already assigned for the subclient.


of 108

Review the Overview and Agent-Specific Guidelines for your agent before configuring pre/post processes for data protection/archive operations.

Pre-process commands for the iDataAgents will be executed only when the necessary resources (e.g., media, library, drive, etc.) are available.

Required Capability: Capabilities and Permitted Actions

To configure a subclient for Pre/Post processing of data protection/archive operations:

1. From the CommCell Browser, right-click the subclient for which you want to configure a pre/post process, and then click Properties from the shortcut menu.

2. Click the Pre/Post Process tab of the Properties dialog box.

3. For an agent other than the Oracle RAC iDataAgent, click inside the space that corresponds to one of the following phases and type the full path of the process that you want executed during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces). For the Oracle RAC iDataAgent, click Browse for the corresponding process, click the name of the control node client in the Select Client for Browse dialog box, and click OK. Then browse for and click the process.

PreBackup

PreScan

PreArchive

PreCopy

PreSnap

PostBackup

PostScan

PostArchive

PostCopy

PostSnap

Click OK.

4. If you want to run a Post Process for all attempts to run that job phase, then select the corresponding checkbox.

5. For subclients on Windows platforms, if Run As displays Not Selected, or if you want to change the account that has permission to run these commands, click Change.

a. In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter a user name and password. Click OK.

b. If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.

6. Click OK to save your changes and close the Pre/Post Process tab of the Properties dialog box.

Configure SQL Server 2000/2005 Databases

Related Topics


Before You Begin

Review Things to Consider when Creating and Configuring SQL Server Subclients.

When running on Windows Server 2003 and VSS is enabled, the New Subclient command is not available.



of 108

To configure SQL Server 2000/2005 databases:

1. From the CommCell Browser, if you are creating a new subclient, right-click the instance for which you want to create a new subclient, click New Subclient from the shortcut menu, and click Database. If you are modifying an existing Database subclient, right-click the subclient, click Properties, and go to Step 3.

2. In the General tab of the Subclient Properties dialog box, type the name (up to 32 characters) of the subclient that you want to create.

3. From the Content tab, click Configure to discover and associate databases to the subclient.

4. From the Database Configuration dialog box, click the name of each database that you want to include in your subclient. For each database selected, be sure to click the appropriate subclient in the Subclient Name list, or use the Change all selected databases to list. Click Discover to find and associate additional items.

5. Click OK to save your entries. The selected databases appear in the Database List pane.

6. Select a storage policy on the Subclient Properties (Storage Device) tab to finalize the configuration process.

7. Click OK to commit your configuration.

Configure SQL Server 2000/2005 Files and File Groups

Related Topics


Before You Begin

Review Things to Consider when Creating and Configuring SQL Server Subclients.

When running on Windows Server 2003 and VSS is enabled, the New Subclient command is not available.


To configure SQL Server 2000/2005 files and file groups:

1. From the CommCell Browser, if you are creating a new subclient, right-click the instance for which you want to create a new subclient, click New Subclient from the shortcut menu, click File/File Group, and go to the next step. If you are modifying an existing File/FileGroup subclient, right-click the subclient, click Properties, and go to Step 3.

2. In the General tab of the Subclient Properties dialog box, type the name (up to 32 characters) of the subclient that you want to create.

3. From the Content tab, click Configure to associate database elements to the subclient.

4. From the FileGroup Configuration dialog box, click in the Database list the name of the database whose file groups you want to include in your subclient.

5. Select the desired file(s) or file group(s) to be backed up by this subclient. The physical names are available to assist in identifying the correct content. For each file/file group selected, be sure to click the appropriate subclient in the Subclient list, or use the Change all selected FFG to list. Click Discover to find and associate additional items.

6. Click OK to save your entries. The file group information appears in the Database pane.

7. Repeat Steps 3 through 6 for each affected database.

8. Select a storage policy on the Subclient Properties (Storage Device) tab to finalize the configuration process.


of 108

9. Click OK to commit your configuration.

NOTES

Files and file groups that are configured as content of other subclients are unavailable for selection.

Configure Subclient Content

Before You Begin

Review Subclients.

Do not configure the content of a subclient while the parent node or any sibling subclient has a data protection or archive operation currently running on it.

Exchange Mailbox iDataAgents and Exchange Mailbox/Public Folder Archiver Agents: If you change the contents of the default backup set or archive set then the auto-discover feature will be disabled. If you disable the auto-discovery feature, newly created mailboxes will not be backed up/archived unless they are manually discovered and assigned to a subclient.

NAS NDMP iDataAgents: You must ensure there is no overlap in content between all subclients. Overlap in subclient content will result in loss of data. An existing subclient's contents are not automatically changed when another subclient is added with overlapping contents.

SharePoint Server iDataAgent: The Site Content Database, the Site Collection Database, the Site Database, and the Site Index for the virtual server must all be assigned to the same subclient.

Lotus Notes Document iDataAgent: Review Assigning Restore View Names to Newly-discovered Databases

QR Agent: Follow these guidelines when adding a volume to a QR Agent subclient:

The volume must correspond to a physical disk or RAID array.

A volume created by volume management software other than VxVM is not valid subclient content.

Subclients may have overlapping content; however, if two or more subclients overlap, they all must use the same snapshot engine. If the QR policies associated with the subclients are configured to use different snap engines, they must be reconfigured to use the same snap engine in this scenario.

Caution Against 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 "catch-all" entity for client data. As a result, the likelihood that some data will not get backed up or scanned for archiving would increase.


To configure subclient content:

1. From the CommCell Browser, right-click the subclient for which you want to configure content, click All Tasks (if applicable) and then click Properties.

2. Follow the procedure below that is applicable for your agent:

For File System, Active Directory, File Archiver, Exchange Public/Web Folder iDataAgents, NDS, and SharePoint Server iDataAgents click the Subclient Properties (Content) tab and configure content for the subclient as described below for your agent:

For File System, Active Directory, File Archiver, NDS, and SharePoint Server iDataAgents: Type the full path of the data that you want to include as subclient content in the Enter New Content field, then click Add. Optionally, click Browse to enter the content. When browsing content while configuring SharePoint subclients, you can add content via multiple selections with the CTRL or SHIFT keys. For Windows, when specifying a UNC Path, click As User, and enter the user account information for the domain user with permissions for that path. For NetWare/DNS, see the Notes section below for content path examples. For Unix File Systems, you can enter the mount point of an NFS-mounted file system, see the Notes section below for examples.

For Exchange Public/Web Folder iDataAgents: Click Browse, select folders to include as


of 108

content, then click Add.

For NAS NDMP iDataAgents, configure the Backup Content Path field(s) as described below, then click Add:

Click the drop-down list arrow to display the root volumes on the file server. To change the root volume, click one in the list. If you want to refine the content path further, use the space to the right of (or below) the root volume list to enter additional path information. Note the following:

For NetApp, the root volume is the mount path of each volume. Example: for volume FS1 the root volume will be /vol/FS1.

For EMC Celerra, the root volume is the mount point created for a volume. Example: for volume FS1 with mount point /FS1 the root volume will be /FS1.

For Hitachi, no root volumes are shown in the drop down list. Type the full path of the root volume. Example: for volume FS1 with mount point /mnt/FS1 the root volume will be /mnt/FS1.

For BlueArc, the root volume is a combination of a descriptor of the path and the volume name. Example: for volume FS1 with a mount point of / the root volume will be /__VOLUME__/FS1.

Optionally, for NetApp NAS NDMP, click Browse to enter the content.

For Exchange Mailbox and Exchange Mailbox/Public Folder Archiver Agents follow the procedure to Discover and Assign New Mailboxes or Assign Mailboxes to Another Subclient.

For DataArchiver for Exchange Agents follow the procedure to Discover and Assign New Journal Mailboxes or Assign Journal Mailboxes to Another Subclient.

For Lotus Notes Database and Document iDataAgents follow the procedure to Discover and Assign New Databases or Assign Databases to a Subclient.

For DB2, DB2 DPF, Exchange Database, Novell GroupWise, SharePoint Server, SQL Server 2000 Database, Sybase, and MySQL iDataAgents, click the Subclient Properties (Content) tab and configure content for the subclient as described below for your agent:

For the DB2 iDataAgent, specify whether you want to include the entire database or a subset of this data as content for the subclient. For the DB2 DPF iDataAgent, specify whether you want to include all the affected database partitions or a subset of this data as content for the subclient.

For Exchange and GroupWise iDataAgents: Click Configure. From the Add/Modify Subclients dialog box click the subclient entry for the database element/Storage Group that you want to add to the new subclient and select the name of the destination subclient from the list that appears. Alternatively, you can select and assign a range of databases/storage groups using the Change all selected databases/storage groups to list. Note that you must have at least one database element/Storage Group assigned to this subclient in order to save the configuration.

A database/Storage Group that is not configured for a subclient does not appear in the list. This can be the case if the subclient containing the database/Storage Group was deleted. If this happens, click Discover to display all databases/Storage Groups.

For the SharePoint Server iDataAgent, follow the procedure to Discover and Assign New Data Types.

For the SQL Server 2000 Database iDataAgent, follow the procedure to Configure SQL Server 2000/2005 Databases or Configure SQL Server 2000/2005 Files and File Groups.

For the Sybase iDataAgent, follow the procedure to Configure Sybase Databases.

For the MySQL iDataAgent, follow the procedure to Configure MySQL Databases.

For the Informix iDataAgent, click the Subclient Properties (Content) tab and define the contents of the subclient. Specifically, establish the backup mode for the data to be backed up, set the backup level, and decide whether to back up the emergency boot file and/or the ONCONFIG file.

For the Oracle, SAP for Oracle, or Oracle RAC iDataAgent, click the Subclient Properties (Content)tab and define the contents of the subclient. To configure this subclient for specialized types of


of 108

backups, follow the appropriate procedure below:

Create Subclient for Backing Up Archived Redo Log Files

Create Subclient for Backing Up Offline Databases

Create Subclient for Backing Up Online Databases

Create Subclient for Backing Up Online Subsets

Create Subclient for Performing Selective Online Full Backups

For SAN iDataAgents, click the Subclient Properties (Content) tab and configure content for the subclient as described below for your agent:

Image Level on Unix iDataAgent: Click Add. From the Add Content Path dialog box, select the volume(s) that you want to back up (use CTRL + click to select multiple volumes). Click OK. The selected volumes are added to the Contents of subclient list. These volumes are automatically configured to be CXBF devices. Alternatively, use Volume Explorer per specific scenarios to configure CXBF devices.

To configure an unmounted block device or raw device as content, first use Volume Explorer to configure the device as a CXBF device. Then select the configured CXBF device as subclient content. You can ignore the warning that is displayed.

For more information, see When to Use Volume Explorer. For a step-by-step procedure, see Configure a CXBF Device in Volume Explorer.

Image Level and Image Level ProxyHost on Windows iDataAgents: Click Add. Then in the Add Content dialog box, type the full path of the volume or mount point that you want to include as subclient content, then click Add. Optionally, click Browse to select the content. Click OK. The volume or mount point is added to the Contents of subclient list. Add additional content by repeating this step.

ProxyHost iDataAgent: Select a backup host from the Backup Host list. This is the computer to which the BCV is connected. Click Add. In the Content field of the Add/Edit Content for Subclient dialog box, type the primary host path of the content that you want to back up, or click Browse to find and select this data. In the Backup Host BCV Path field of the Add/Edit Content for Subclient dialog box, type the path through which the backup host accesses this data on the BCV, or click Browse to find and select this path. Click OK. The primary host data path and corresponding backup host BCV path are added as a single entry in the Contents of subclient list. To add additional entries, repeat these steps. Refer to Notes below for more information.

For Quick Recovery Agents, click the Subclient Properties (Content) tab and configure the following options:

Click Add Volume. From the Adding Volume dialog box, select volume(s) that you want to add to the subclient content (use CTRL + click to select multiple volumes). You can add/edit additional advanced options for the selected volume by select Advanced on the Adding Volume dialog box. Click OK.

Click Add App to select an application and associated volumes. Click OK.

Any instances you intend to protect and recover with the QR Agent must be configured in the QR Agent properties Authentication tab. They will not appear in the Add App dialog box if they are not configured. Only volumes containing datafiles and archive log files will be detected by Add App. Volumes containing control files and redo log files will not be detected.

For a clustered Exchange Server, if you are not using VSS to perform an online quiesce, sufficient permissions are required in order to be able to perform an offline quiesce; in such cases, ensure that the User Name specified has Exchange Administrator rights.

See also Configure Subclients for Overlapping Content.

3. Click OK to save your content configuration.

NOTES

Content examples for NetWare are OU=prospects.O=engineering.[Root], (for NDS content), and SYS:\public (for File System content).


of 108

Content examples for adding an NFS-mounted file system to subclient content of a Unix File System iDataAgent:

/mountpointA to include the entire file system at mountpointA

/mountpointA/projects for only the projects directory within the file system at mountpointA.

Informix subclients include one or more dbspaces. As databases are added to the dbspaces, the subclients are updated automatically.

SQL Server 2000 Database iDataAgents: The logical and physical names are available to assist in identifying the correct content. Files and file groups that are configured as content of other subclients are unavailable for selection.

Exchange Mailbox iDataAgents and Exchange Mailbox/Public Folder Archiver Agents: Initially, all unconfigured mailboxes are assigned to the default subclient. You can create a new subclient and reassign mailboxes to this new subclient (within the same backup set/archive set). Once assigned, the mailboxes become part of the content of the new subclient.

SharePoint Server iDataAgent: Initially, all unconfigured data types are assigned to the default subclient. You can create a new subclient and reassign data types to this new subclient. Once assigned, they become part of the content of the new subclient.

ProxyHost iDataAgent: The primary host data path is backed up by the subclient and is the path through which the backup host accesses this data on the BCV. A primary host path and its corresponding backup host path are listed in the following format:

<primary_host_path> --> <backup_host_path>

For example, assume that you want to back up the D:\data directory from your primary host and D:\is mirrored by a BCV, which is mapped to the backup host as F:\. Consequently, the path to this data on the backup host is F:\data. When you add this directory to a subclient, it is listed in the Contents of subclient pane as D:\data --> F:\data.

Configure the Subclient for Data Encryption

Encryption settings made at the subclient level are for data protection and recovery operations run from the CommCell Console and are not related in any way to settings made at the instance level which is for third-party Command Line operations only.

See Data Encryption - Support for a list of supported products.

Before You Begin

Encryption must be enabled at the client level prior to configuring any subclients residing on that client. See Configure the Client for Data Encryption.

If you are attempting to configure for third-party Command Line operations, do not use this procedure. See Configure Third-party Command Line Operations for Encryption.


To configure the subclient for data encryption:

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

The primary host path in the Content field is used for browse and restore purposes. However, it is the data in the Backup Host BCV Path which is actually backed up. If these two paths do not accurately correspond, the path that appears when data is browsed for restore does not accurately reflect the data that will be restored. In the example given above, assume that D:\data is entered in the Content field, while F:\data1 is accidentally entered in the Backup Host BCV Path. If you browse and select D:\data to be restored, it is actually D:\data1 that is restored. (Remember, F:\Data1 is the path on the backup host that corresponds to D:\data1 on the primary host.)


of 108

2. From the Subclient Properties (Encryption) tab, select an option based on the criteria described in the Encryption tab help.

3. Click OK to save your settings and close subclient properties.

Create a New Subclient

Before You Begin

Review Subclients.

Do not create a subclient while the parent node or any sibling subclient has a data protection or archive operation currently running on it.

In cases where a new subclient is created with the same name as a deleted subclient, the system will append a Unix time stamp to the deleted subclient's name in data protection job history reports and views to distinguish the two subclients. For example, subclientname_1104257351.

Informix iDataAgents: If you will be using the Informix ONBAR utility to create backup and restore scripts, you need not create subclients. Otherwise, if you will be using the CommCell Console to back up and restore Informix database objects (subsets/dbspaces), then you will need to create a subclient.

ProxyHost iDataAgents: If you are using a BCV, you must prepare a batch file or a shell script file on the backup host containing commands to synchronize and split the BCV. The Resource Pack includes information on configurations for these batch files or shell scripts, as well as examples that apply to specific applications and hardware (e.g., Exchange databases in an EMC Symmetrix environment). See Tools and Utilities for more information on the Resource Pack.

The ProxyHost iDataAgent also requires that you set permissions for the batch/shell script file on the backup host.

SQL Server 2000/2005 Database iDataAgents: When running on Windows Server 2003 and VSS is enabled, the New Subclient command is not available.


To create a new subclient:

1. From the CommCell Browser, right-click the node (agent/backup set/archive set/instance) for which you want to create a new subclient, click All Tasks (if applicable), and then simply click New Subclient for most agents.

For the SQL Server iDataAgent, expand New Subclient and click either Database to include individual databases or File/File Group to include database elements.

For the File Archiver Agent for Windows with Data Classification, right-click the DataClassSet, expand All Tasks, and then click Create DataClassSet (subclient).

2. Click the General tab or General (Quick Recovery Agent) tab of the Subclient Properties dialog box and type the name (up to 32 characters) of the subclient that you want to create.

For supported agents identified in Support Information - Snapshot Engines, you can select a QSnap option to snap data and then perform a data protection operation on the data.

For QR Agents, you must also select a QR Policy from the QR Policy list.

For the Windows iDataAgents that support VSS, you can optionally Enable VSS on a Subclient.

3. Select other options from the General tab as appropriate for the agent.

4. Click the Content or Databases tab of the Subclient Properties dialog box and Configure Subclient Content as appropriate for your agent.

5. For all agents (except QR), click the Storage Device (Data Storage Policy) tab of the Subclient Properties dialog box, then select a data storage policy to associate with this subclient from the storage policy list.

For the DB2 and DB2 DPF iDataAgents, you can also change the number of data backup streams. For the DB2 DPF iDataAgent, the default stream threshold should be equal to the total number of


of 108

database partitions for the subclient.

For SQL Server iDataAgents, you can also click the Storage Device (Log Storage Policy) tab of the Subclient Properties dialog box, then select a log storage policy to associate with this subclient from the storage policy list and select the number of backup streams for transaction log backup jobs.

For 1-Touch for Unix, it is strongly recommended that the storage policy that you select for the subclient configured for 1-Touch use a MediaAgent on a different computer. If you do this, and if the system crashes, the media will not have to be exported to another MediaAgent in order to recover the system.

6. For Oracle and DB2 iDataAgents, click the Backup Arguments (Oracle) or Backup Arguments (DB2, DB2 DPF) tab of the Subclient Properties dialog box and Configure Backup Arguments as appropriate for your agent. Note that the backup arguments for Informix are located on the Content tab.

7. For Migration Archiver Agents, click the Archiving Rules or Rules tab of the Subclient Properties dialog box and configure archiving rules as appropriate for your agent. In order to perform rules-based migration archiving operations, the Disable All Rules checkbox must be cleared.

If the File Archiver for Windows supports Data Classification, several filter-like configuration fields are defined as archiving rules and are available from the Subclient Properties (Rules) tab. If you want to define content and archiving rules based on file attributes other than volumes, size, and modified time (i.e., if you want to customize your rules), click the Advanced tab and configure as appropriate. Also, stub management options can be configured from the Stub Rule tab. See Configure Archiving Rules - File Archiver Agents for step-by-step instructions.

8. For ProxyHost and Image Level ProxyHost iDataAgents, click the Pre/Post Process tab of the Subclient Properties dialog box. In the PreScan field, type the path to the batch file/shell script file that contains those commands that are to run before each backup of the subclient, or click Browse to locate and select this file. For ProxyHost and Image Level ProxyHost, the file must reside on the backup host or primary host.

9. Optionally (if supported for your agent) you can:

Add a Data Protection or Discovery Filter for a Subclient on the Filters tab.

Configure a Subclient for Pre/Post Processing of Data Protection/Archive Operations on the Pre/Post Process tab.

Enable Software Compression for a Subclient on the Software Compression tab of the Storage Device tab.

Configure the Subclient for Data Encryption on the Encryption tab.

Enable or Disable Operations for this subclient on the Activity Control tab.

Configure Mailbox Stores for Auto-Discovery on the Auto-discovery tab.

Configure the Subclient for 1-Touch on the 1-Touch Recovery tab.

View or change the user group security associations for this subclient from the Security tab.

Determine location from where archive logs will be backed up or deleted from the Log Destinations tab.

Enable backups using a snap engine from the Snap Backups tab.

10. Click OK to save the subclient configuration. For QR Agents, this procedure is now complete. For all other agents, continue on to the next step.

11. The Backup Schedule dialog box advises you to schedule data protection operations for your new subclient. It is recommended you elect to set a schedule now. You can also associate this subclient with an All Agent Types schedule policy (which is automatically created by the system, or can be a user defined Data Protection schedule policy). If you have already associated a schedule policy at a previous level (Backup Set/Instance, Agent, Client, or Client Computer Group) the schedules defined in the Schedule Policy will be automatically applied to the new subclient. See Schedule Policy for more information.

If you want to associate this subclient with an All Agent Types schedule policy, click Associate with Generic Schedule Policy, and then select that schedule policy from the drop-down list


of 108

box. Click OK.

If you want to associate this subclient with a specific schedule policy, click Associate to schedule policy, and then select the schedule policy from the drop-down list box. Click OK.

If you have selected to define a schedule for this subclient:

Click Schedule.

From the Backup/Archive Options dialog box, select the type of data protection operation that you want to schedule.

If you want to set Advanced Backup/Archive Options, click Advanced.

After selecting the data protection type and any advanced options, click OK. The Schedule Details dialog box appears.

From the Schedule Details tab, select the scheduling options that you want to apply, then click OK.

If you don't want to create a data protection schedule at this time, click Do Not Schedule, and then click OK.


Delete a User-Defined Subclient

Related Topics:

Command Line Interface - qdelete subclient

Subclients


To delete a user-defined subclient:

1. From the CommCell Browser, right-click the user-defined subclient that you want to delete, and then click Delete from the shortcut menu.

2. 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. If you click Yes:

the subclient, and any data that may have been protected/archived by the subclient are logically deleted, and you can no longer access the corresponding data for recovery/retrieve purposes. However, the data remains valid for the length of time specified by the associated retention period. Some agents allow you to browse data from a deleted subclient provided that the Browse Data Before date and time precedes the time that the user-defined subclient was deleted.

for agents that support a default subclient, once the user-defined subclient is deleted its contents are automatically reallocated to the default subclient the next time a data protection/archive/discovery operation is run on the default subclient to ensure data protection coverage.

the system deletes the selected subclient node and removes it from the CommCell Browser.

the system deletes any data protection/archive and recovery/retrieve job schedules that are associated with the subclient.

Enable or Disable Operations


Level Capability

CommCell Administrative Management with CommCell level association

Client Computer Group

Administrative Management with Client Computer Group level association


of 108

To enable or disable activity control at the CommCell, client computer group, client, agent, or subclient levels:

1. From the CommCell Browser, right-click the CommServe, client computer group, client computer, agent, or subclient, and then click Properties from the short-cut menu.

2. From the Activity Control tab of the associated Properties dialog box, select or clear option(s), as desired.

3. Click OK.

Enable or Disable Software Compression for a Subclient

Before you Begin

Do not enable/disable software compression for a subclient that is being backed up/archived.


To enable software compression for a subclient:

1. From the CommCell Browser, right-click the subclient for which you wish to enable software compression and then click Properties.

2. Click the Storage Device tab and from the Data Storage Policy tab, select the storage policy from the Storage Policy list.

If applicable for the selected agent, click the Log Storage Policy tab and select a storage policy from the Transaction Log Storage Policy list.

3. Then click the Storage Device (Data Transfer Option) tab and choose the appropriate compression option for this subclient.



Remove a Process from Pre/Post Processing of Data Protection/Archive Operations

Before You Begin

We recommend not removing a pre/post process for a subclient that is currently running a data protection or archive operation.

Review the Overview and Agent-Specific Guidelines for your agent before removing pre/post processes for data protection/archive operations.


To remove a process from Pre/Post processing of data protection/archive operations:

1. From the CommCell Browser, right-click the subclient for which you want to remove a pre/post process, and then click Properties from the shortcut menu.

Client Agent Management with Client level association

Agent Agent Management with Agent level association

Subclient Agent Management with Subclient level association

Disabled data management and/or data recovery operations are displayed with client and/or agent icon changes in the CommCell Browser. For a comprehensive list of all icons in the CommCell Console, see CommCell Console Icons.


of 108

2. Click the Pre/Post Process tab of the Subclient Properties dialog box.

3. Click the text inside the space that corresponds to one of the following phases for which you want a pre/post process removed, then press the Delete key:

PreScan

PreArchive

PreCopy

PreSnap

PostBackup

PostScan

PostArchive

PostCopy

PostSnap

4. Repeat Step 3 for any additional processes that you want to remove.

5. Click OK.

Rename a Subclient

Before You Begin

You can rename a subclient at any time. However, we recommend that you don't rename a subclient while a data protection or archive operation is running on that subclient.

In cases where a subclient is renamed using the same name as a deleted subclient, the system will append a Unix time stamp to the deleted subclient's name in data protection job history reports and views to distinguish the two subclients. For example, subclientname_1104257351.


To rename a subclient:

1. From the CommCell Browser, right-click the subclient that you want to rename, and then click Properties from the shortcut menu.

2. From the Subclient Properties (General) tab, or the QR Agent Subclient Properties (General) tab, type the new name in the Subclient Name field, and then click OK.

The CommCell Browser updates the subclient with its new name. The new name will also be reflected in any associated schedules and reports.

Set the Network Bandwidth and Network Agents for a Data Protection Operation

Before you Begin

Do not modify the network bandwidth and network agents for a subclient or instance that is being backed up.


To Set the Network Bandwidth and Network Agents for a Data Protection Operation:

1. From the CommCell Browser, right-click a subclient and then click Properties.

For the DB2, DB2 DPF, Informix, Oracle, Oracle RAC, SAP, or Sybase iDataAgent, right-click an instance and then click Properties.

2. Click the Storage Device Data Transfer Option tab.


of 108

For the QR Agent:

To control network bandwidth settings, use the Throttle Network Bandwidth section in the General tab of the Subclient Properties dialog box.

To control the number of network agents, you must create a nQRNetworkAgents registry key.

3. Enter a number of Network Agents that must be used to perform data protection operations on the subclient/instance.

4. Click the Throttle Network Bandwidth (MB/HR) option and then enter the throughput as needed. Note that throttling is done on a per Network Agent basis.

5. Click OK to save the changes.


Set Stream Numbers for Backup and Restore

Related Topics:


Data stream numbers for database backups and for transaction log backups can be set from the Storage Policy tab in the Subclient Properties dialog box. The maximum number of data streams required for a restore job is the same as the number of streams used in the backup job.


To set data stream numbers for database or transaction log backups:

1. From the CommCell Browser, right-click the subclient whose properties you want to set, then click Properties.

2. Click the Storage Device tab of the Subclient Properties dialog box.

3. From the Data Storage Policy tab or the Log Storage Policy tab, select the respective storage policy from the Storage Policy list.

4. Select a value for the Number of Backup Streams. If you are using the auxiliary copy feature of combining streams, the number of database backup streams selected here must be set to one.

5. Optionally, you can click the Software Compression tab and choose a necessary compression option.


Back to Top


of 108

Backup Job History Topics | How To | Related Topics

Overview

Items That Were Backed Up

Items That Failed

Pruning Backup History Information

Supported Features

Content Indexing History Information

Overview

You can view the backup and restore history of iDataAgents, BackupSets/Instances, and subclients.

The Backup Job History Filter dialog box allows you view detailed, historical information about backup jobs. Once you have chosen your filter options, they are displayed in the Backup Job History window.

For information on Job Details displayed in the Job History, see Viewing Job Information.

From this window, you can right-click a backup job to:

Browse the data backed up by the backup set or instance from the Backup Job History window. This is provided as right-click option for each job. (This menu option, when selected, initiates the Browse Options dialog box preset with the values needed to browse the data.)

Browse the snapshots created during SnapProtect

View items that failed during the backup job

View details of the backup job

View files that were not indexed during a backup job that performed content indexing

View associated media

View events of the backup job

View a list of items that were backed up

View a list of items that were moved to media for a SnapProtect job

View the log files of the backup job.

View the RMAN log of an Oracle backup job.

Items That Were Backed Up

The View backup file list option allows you to view a list of the files that were backed up during a backup job, along with the data sizes of each backed up file. The View backed up messages option allows you to view a list of messages that were backed up by using, along with the alias name, display name, email address, sender name, and recipient of each message.

From these windows you can conduct searches based on a particular string, allowing to find particular files quickly and easily.

It is not recommended that this option is used to view a very large list of items that were backed up (such as lists that total over 100,000 items). It is suggested that the Browse option is used to find a list of backed up items in such cases.


of 108

See View the Items That Were Protected During a Data Protection Operation for step-by-step instructions.

Items That Failed

The items that failed for a data protection operation include individual files that may fail the job even though a particular job completed successfully. You can determine the degree of success for these jobs using this window.

Filters can be used in conjunction with the "Items That Failed" list on the data protection Job History Report to eliminate backup or archive failures by excluding items which consistently fail 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.

See View the Items That Failed For a Data Protection Operation for step-by-step instructions.

Pruning Backup History Information

You can prune backup history information based on the number of days established in the Days to keep the backup job histories option from the Media Management Configuration (Service Configuration) dialog box available in the Control Panel.

Supported Features The NAS NDMP iDataAgents do not support the ability to view items that failed.

The Image Level and Image Level ProxyHost iDataAgents do not support the ability to Browse the data of a selected backup job in Backup Job History.

Content Indexing History Information

Content Indexing history can also be viewed of iDataAgents, BackupSets/Instances, and subclients. The following information is displayed:

Items that were Successfully Content Indexed

A listing of files and folders that failed is not available for the Quick Recovery Agent, or the Image Level and Image Level ProxyHost iDataAgents. These agents do not perform a file level backup/copy.

Certain application related files can never be backed up by the File System iDataAgent due to the nature of the data. For example, Microsoft SQL Server database files cannot be backed up by the File System iDataAgent. In this and other similar circumstances, consider entering files such as these as exclusions in the corresponding subclient filter.

If you have installed the SQL Server iDataAgent, do not use the stored procedure sp_delete_backuphistory, sp_delete_database_backuphistory and sp_delete_backup_and_restore_history provided by Microsoft clean up backup history. By default backup history is automatically pruned from the CommServe database and the Microsoft SQL Server, as necessary.


of 108

You can view the list of items that were successfully content indexed during a Content Indexing operation for a particular job. for step-by-step instructions, see View the Items that Were Successfully Content Indexed.

Content Indexing Failures

Content Indexing failures allows you to look at the messages, files and documents that could not be indexed during a content indexing operation. Content Indexing looks at each file (of the supported data types) and indexes its contents allowing advanced searches of backed up/archived/migrated data.

Files that were not indexed, (perhaps because the file’s content could not be read) are added to the Content Indexing Failures list, and are viewable from the View Content Index (Failed Items) option in the Job History window. For step-by-step instruction, see View the Items that Failed to Content Index.

Back to Top

Backup Job History - How To Topics | How To | Related Topics

View Backup Job History

View the Items That Were Protected During a Data Protection Operation

View the Items That Failed For a Data Protection Operation

View Job History Details

View the Media or Mount Paths of a Job History

View the Events of a Job History

View the Items that were Moved to Media during SnapProtect

View the Log Files of a Job History

View the Items that Were Not Indexed During Content Indexing

View the Items that Were Successfully Content Indexed

View Backup Job History

To view backup history:

1. From the CommCell Browser, right-click the entity (client computer, iDataAgent, backup set or subclient) whose backup history you want to view, click View, and then click View Backup History.

2. From the Backup History filter window select the filter options, if any, that you want to apply, and then click OK. The system displays the Backup Job History window.

3. Click OK.

View the Items That Were Protected During a Data Protection Operation

Required Capability: none required

This option is available for File System-like agents.


of 108

To view the list of items that were protected during a data protection operation.

1. From the CommCell Browser, right-click the entity whose history of data protection operations you want to view, click View, and then click the necessary options to view a job history.

2. From the Job History Filter dialog box, select the filter options, if any, that you want to apply, and then click OK.

3. From the Job History window, right-click the operation whose list of protected items you want to view, and then select View backup file list/View Backed Up Messages. The Backup file List window displays a list of the backed up files/messages that were included in the backup job. You can use the Search option to find items in the window.

4. Click File -> Exit.

5. Click Close from the Job History window.

View the Items That Failed For a Data Protection Operation

To view the list of items that failed for a data protection operation:

1. From the CommCell Browser, right-click the entity whose history of data protection operations you want to view, click View, and then click to view a job history.


3. From the Job History window, right-click the operation whose list of failed items you want to view, and then select View Failed Items. The Unsuccessful Backup Files window (for DataArchiver Agents, Items On Which Archive Failed) displays those items that failed. If no items failed, a message to that effect is displayed.

4. Click Close.

View Job History Details


To view the details of a job history:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click job history.

2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK.

3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Job Details.

4. The Job Details dialog box appears, displaying detailed job history in General, Details, Phase Details and Attempts tabs for the selected job.

5. Click OK.

A listing of files and folders that failed is not available for the Quick Recovery Agent, nor the Image Level and Image Level ProxyHost iDataAgents. These agents do not perform a file level backup/copy.

If viewing the details of a job with a pending or failed status, the Reason for Job Delay field will contain an Error Code, which, if clicked, will launch the customer support website displaying troubleshooting article(s) related to the specific issue.


of 108


To view media or mount paths associated with a job history:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then select the appropriate history.

2. From the Job History window select the filter options, if any, that you want to apply, and then click OK.

3. From the job history widow, right-click the backup whose media or mount paths you want to view, and then click View Media.

4. The Media Used By Job ID window displays a list of media or mount paths used by the operation.

5. Click OK.



To view the events associated with a job:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click Job History.


3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Events.

4. The All Found Events window gets displayed. If no events where found for the back up, a message is displayed to that effect.

5. Click Close.

View the Items that were Moved to Media during SnapProtect

To view the list of items that were moved to tape during SnapProtect backup.

1. From the CommCell Browser, right-click the entity whose history of data protection operations you want to view, click View, and then click the necessary options to view a job history.


3. From the Job History window, right-click the operation whose list of items moved to media you want to view, and then select View Backup Copy file listing. The Backup file List window displays a list of the backed up files that were included in the backup copy job. You can use the Search option to find items in the window.

4. Click File -> Exit.

This option is available for the SnapProtect feature.

To view the files moved to media for a backup copy job, right-click the SnapProtect backup job corresponding to the Backup Copy job and select View Backup Copy file listing.

View backup items will not display anything for a Backup Copy job.


of 108




To view the log files of a Job History:

1. From the CommCell Browser, right-click the entity whose job history you want to view, and then click to view a job history.

2. From the job history filter window select the filter options, if any, that you want to apply, and then click OK.

3. From the job history window, right-click the job whose log files you want to view, and then click View Logs.

4. The contents of the log file related to the selected job history are displayed in the Log File for Job n window.

View the Items that Were Successfully Content Indexed

To view the list items that were not indexed during content indexing:

1. From the CommCell Browser, right-click the entity whose operations you want to view, click View, and then click the necessary options to view a job history.


3. From the Job History window, right-click the job for which you want to view the successfully content indexed items, select View Content Index, and click Successful Items.

4. Click Close.


View the Items that Failed to Content Index

To view the list of items that failed to content index:

1. From the CommCell Browser, right-click the entity whose operations you want to view, click View, and then click the necessary options to view a job history.


3. From the Job History window, right-click the job for which you want to view the list of items failed to content index, select View Content Index, and click Failed Items.

4. Click Close.


This option is available for operations that performed content indexing.

This option is available for operations that performed content indexing.


of 108

Back to Top


of 108

Restore Job History Topics | How To | Related Topics

Overview

Items That Restored

Supported Features

Overview

The Restore History Filter dialog box allows you to view detailed, historical information about restore jobs.

For information on Job Details displayed in the Job History, see Viewing Job Information.

Once you have chosen your filter options, they are displayed in the Restore Job History window. From this window you can right-click a restore job to:

View Restore Items; items in the job that were Successful, Failed, Skipped or All. These items, if any, will be listed in the Restored Files window.

View Job Details of the restore job. The job details will be listed in the Job Details window.

View Events of the restore job. The job events will be listed in the All Found Events window.

View Log files of the restore job. The job log files will be listed in the Log File window.

View the RMAN Log of an Oracle restore job. The RMAN Log will be listed in the Oracle Restore Log window.

Items That are Restored

When viewing files that are restored in the Restored Files window, each of the files is listed with the restore status level appended at the end of the file path. The possible status levels are: RESTORED, FAILED and OLDER.

Successfully restored files will be listed with RESTORED appended to the file path. If files are not restored/recovered due to errors, the file paths will be appended with FAILED. Under some circumstances, the system may not restore/recover certain files because they are older versions of the same files already present in the files system; these files are appended with the word OLDER.

Supported Features

Consider the following.

The NAS NDMP iDataAgents do not support the ability to view failed/successful item lists.

Restore Job History will not display Oracle rman_util jobs at the instance level.

Back to Top

Restore History - How To Topics | How To | Related Topics

View Restore Job History


of 108


View the Media of a Job History


View Restore Job History

To view the restored items associated with a job:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job restore history you want to view, click View, and then click Restore History.

2. From the Job History filter window, select the filter options, if any, that you want to apply, and then click OK.

3. From the Job History window, right-click the job whose restored items you want to view; click View Restore Items, and select from the type of items to view: Successful, Failed, Skipped or All.

4. The Restored Files window will display the selected type of restored items for the job.

5. Click OK.



To view the events associated with a job:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click Job History.


3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Events.

4. The All Found Events window gets displayed. If no events where found for the back up, a message is displayed to that effect.

5. Click Close.


To view media or mount paths associated with a job history:

1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then select the appropriate history.

2. From the Job History window select the filter options, if any, that you want to apply, and then click OK.

3. From the job history widow, right-click the backup whose media or mount paths you want to view, and then click View Media.

4. The Media Used By Job ID window displays a list of media or mount paths used by the operation.

5. Click OK.



of 108


To view the log files of a Job History:

1. From the CommCell Browser, right-click the entity whose job history you want to view, and then click to view a job history.

2. From the job history filter window select the filter options, if any, that you want to apply, and then click OK.

3. From the job history window, right-click the job whose log files you want to view, and then click View Logs.

4. The contents of the log file related to the selected job history are displayed in the Log File for Job n window.

Back to Top

Warm Database Restore

This use case implements what was formerly known in previous releases as “Hot Server Restore”. It makes use of the restore option called “Restore latest backup data”.

By keeping up-to-date copies of production databases on alternate servers, the system helps to minimize down time in cases where the production database server has failed.

You can use this feature to create spare copies of one or more non-system secured databases on SQL servers within the same domain, a different domain, or across a Wide Area Network (WAN).

This feature is similar to the traditional “Log Shipping” feature of Microsoft SQL Server in that it involves a backup of the primary server database and a restore to a secondary server database. It differs slightly in that transaction log backups are stored on the Media Agent and not copied directly to the target server thereby eliminating the disk space needed for “staging” data. The setup process for Warm Database Restore is also somewhat simpler.

The advantages of Warm Database Restore over a traditional restore scenario is that the database is always kept in a near ready state. In the case of disaster, users do not need to wait for the time it would take to restore the database in its entirety. Only the latest backup may need to be applied to the target database before turning the application over to use it.

The following procedure describes the steps involved in creating a Warm Database Restore:

Procedure

Requirements

Review the following requirements before performing a Warm Database Restore:

The primary SQL server and hot standby server must be clients of the same CommServe and have the SQL Server iDataAgent installed on each computer.

The primary SQL server must be able to communicate with the hot standby server with one of the following network configurations:

Local Area Network (LAN) in the same domain

Local Area Network (LAN) in a different domain

Wide Area Network (WAN)

Two licenses for SQL Server iDataAgent are required.


of 108

Set Up the Primary SQL Server

1. Install the Microsoft SQL Server iDataAgent on the primary SQL server computer.

See Deployment - Microsoft SQL Server iDataAgent for more information.

Set Up the Hot Standby Server

2. Install the Microsoft SQL Server iDataAgent on the hot standby server computer.

See Deployment - Microsoft SQL Server iDataAgent for more information.

Backup the SQL Server Database(s) on the Primary Server

3. Perform a full backup of the SQL Server database(s) on the primary server.

NOTES

If the primary SQL server and hot standby server are connected using a slow Wide Area Network (WAN) connection, you can make a secondary copy of the data to a tape or a removable storage device using the Auxiliary Copy operation. The tape can then be sent to the hot standby server's location and restored locally, thereby preserving your WAN resources.

See Start a Full/Incremental/Differential Backup for step-by-step instructions.

See Start an Auxiliary Copy for step-by-step instructions if you wish to copy the backed up database to tape.

Restore the SQL Server Database(s) to the Hot Standby Server

4. Perform a restore of the last full backup of the primary database(s), as well as any differential or transaction log backups completed since the database’s last full backup.

See Restore Latest Data (Warm Database Restore) for step-by-step instructions.

Schedule Routine Backup/Restore Operations for the SQL Server Database(s)

5. Schedule routine differential or transaction log backups of the SQL Server database(s) on the primary server.

Then, schedule routine restore operations using the Latest Backup Data option. All backup jobs completed since the last restore operation will be restored.

Matching the restore schedule with a backup schedule on the source database keeps the restored databases up to date automatically.

If you wish to include only the transaction log backups completed since the last restore operation, you must select the Apply Log Backups Only option after selecting Latest Backup Data in the SQL Restore Options dialog box. The restore operation will then skip any full backup jobs completed since the last restore operation.

If you do not select the Apply Log Backups Only option and the database already exists, all backup jobs completed since the last restore operation will automatically be restored.

If you do not select the Apply Log Backups Only option and the database does not already exist, the software will automatically perform a full restore of the database.

See the following procedures for step-by-step instructions:

Start a Full/Incremental/Differential Backup


Schedule Backups


of 108

If you wish to retain the capability to view the database(s) contents on the hot standby server, ensure that the database(s) are restored in STANDBY mode. If you do not wish to retain this capability, you can restore the database(s) in NO RECOVER mode.

Using the SQL Server Database(s) on the Hot Standby Server

6. If you wish to use the database(s) on the hot standby server, you must first bring the database(s) online by selecting the Recover Only option in the SQL Restore Options dialog box.

NOTES

You can also bring the database(s) online by recovering the database from the SQL Server Enterprise Manager.

No further restore operations may be performed to the hot standby server’s database(s) once the database(s) have been recovered. If you wish to perform more restore operations to the hot standby server after recovering the database(s), you must setup the hot standby server again as described in this procedure.

Perform Disaster Recovery Operations for the Primary SQL Server Database(s)

7. If the primary server's database(s) is lost, you can restore the database(s) from the hot standby server's database(s) by performing the appropriate in-place restore operation.

If the entire primary server is lost, you must perform a full system restore.

NOTES

Once the full system restore has completed, you will need to set up the hot standby server again by repeating the steps outlined in this procedure.

See Restore Data - Microsoft SQL Server for step-by-step instructions.

See Restore Data - Microsoft SQL Server - Full System Restore for step-by-step instructions.


of 108

atos...features - microsoft sql server idataagent table of contents overview system requirements -...

Documents