White Papers

17 TR1081 | Microsoft SQL Server Database Protection Using EqualLogic Auto-Snapshot Manager / Microsoft Edition
5 Creating SQL Server Database Smart Copies
Your business needs will determine the type of Smart Copy to create using ASM/ME.
If the objective is fast recovery of SQL Server databases, use snapshot Smart Copies because they
consume minimal storage resources and can be used for a complete recovery strategy.
If the objective is to create a copy of a SQL Server database for longer duration, clone Smart Copies are
recommended because they mirror the original database volume structure.
If there is a remote site available and you want the ability to bring the latest version of SQL Server database
information online in the event of a disaster at the primary site or enable the ability to offload reporting or
data mining operations from the production site, use replica Smart Copies.
5.1 Steps to Create Smart Copy Sets
All Smart Copies can be created using the same wizard either by right-clicking an object or using the
Actions pane in ASM/ME. Once created, Smart Copies are listed under the Smart Copies Object in the
ASM/ME GUI. The Create Smart Copy wizard will display options allowed by the object based on what
type of Smart Copy operation is supported (snapshot, clone, or replica as in Figure 9). After you choose
the Smart Copy type, you can choose the application behavior (called the backup type).
5.1.1 Smart Copy Behavior with SQL Server
SQL Server database Smart Copies have two options for backup types (Figure 9) that determine the
behavior of the Smart Copy operation on a SQL Server database. The following backup types are available
with ASM/ME:
Full – This backup type notifies the SQL Server that there was a backup operation. The operation applies a
checkpoint and timestamp to the database log file. For SQL Server environments that use log file backups,
this backup type allows log backup files to be applied to the restore process to add additional granularity
during the restore process. For more information on applying additional log backup files during a smart
copy restore operation, see SQL Server Database Restore with Apply Logs Option.
Copy – This backup type creates a COPY_ONLY version of the volume or SQL Server database, and
specifies an “out-of-band” backup operation that has no effect on other backup operations. This backup
type is supported only with SQL Server 2005 and later.
Note: ASM/ME does not truncate the SQL log file. To manage database log growth, individual log
backups can be done or the database recovery model can be changed to minimize log growth. For more
information on SQL Server database recovery models see: http://msdn.microsoft.com/en-
us/library/ms189275.aspx.