IBM Tivoli Storage FlashCopy Manager Version 3.2.x Documentation Updates

Product documentation


Abstract

This document describes the documentation updates for IBM Tivoli Storage FlashCopy Manager Version 3.2.x

Content

Click the following links to view updates to the Tivoli Storage FlashCopy Manager Installation and User's Guides Version 3.2.x:

Tivoli Storage FlashCopy Manager for UNIX and Linux updates
Tivoli Storage FlashCopy Manager for VMware updates
Tivoli Storage FlashCopy Manager for Windows updates


Updates for IBM Tivoli Storage FlashCopy Manager for UNIX Version 3.2.x,

Section: Appendix A: Examples, Examples (native Oracle), Example of the RMAN backup script

Additional guidance has been added for the RMAN backup script, as follows:

The RMAN backup script must be specified in the profile with the DATABASE_BACKUP_SCRIPT_FILE parameter. The example shows the required syntax of the RMAN backup script. The keyword backup must be entered on a single line of text without any other text as shown in this example. There must be a line break after the backup keyword. The keyword database must be enclosed in brackets, and both keywords must be in lower-case text.
run
{
   allocate channel 'c1' type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/home/oracle/tdpo.opt)';
   backup
   (database);
   release channel c1;
}

readmefcm_enu.htm file

For all translations of the file readmefcm_$lang.htm, the link to the IBM Tivoli Storage FlashCopy Manager Release Notes Version 3.2 is incorrect. The link is listed as: http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/help/topic/com.ibm.itsm.fcm.doc/relnote_fcm32.html. The correct link to the IBM Tivoli Storage FlashCopy Manager Release Notes Version 3.2 is:

http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/com.ibm.itsm.relnotes.doc/relnote_fcm32.html
The correct link is listed in the IBM Tivoli Storage FlashCopy Manager for UNIX Version 3.2.0.1 readmefcm_enu.htm file.

Updates for IBM Tivoli Storage FlashCopy Manager for UNIX and Linux Version 3.2

Chapter 2. Planning

Preparing backup and cloning servers > Installation prerequisites for backup and clone server section, requires an update.

The following paragraph:
For FlashCopy cloning, the database instances and application agents are required to be installed and configured on the clone server. For Oracle, only one clone instance is required. For DB2, two instances are required: the instance with the same name as the production instance, and a second instance with the name of the cloned instance where the cloned database is created.

Should be replaced by:
For FlashCopy cloning, the database instances and application agents are required to be installed and configured on the clone server. For Oracle, only one clone instance is required.
For DB2 and DB2 in an SAP environment:Two database instances must be installed on the clone server. These database instances must be the same version as the database instance on the production server. One of the two database instances is assigned the same name as the production instance (on the production server). The other database instance is assigned the clone database instance name. If the clone database name is the same name as the production database name, only one database instance with this common name is required on the clone server.

In the Storage Solutions > IBM System Storage N series and NetApp storage systems section, remove the the following paragraph:


During the reconciliation process, snapshots that are created by the Tivoli Storage FlashCopy Manager software, but are not stored in the Tivoli Storage FlashCopy Manager repository, are also removed. The removal occurs although the snapshots are not deleted. This unlikely scenario occurs when the Tivoli Storage FlashCopy Manager repository is removed or restored to a prior point in time. To avoid the accidental deletion of snapshots, the reconciliation process bypasses snapshots created within the time interval specified with the GRACE_PERIOD parameter.

Replace the sample profile for IBM System Storage N series and NetApp storage solutions with the following example:
>>>
DEVICE_CLASS N6240
COPYSERVICES_HARDWARE_TYPE SAN_NSERIES
COPYSERVICES_SERVERNAME n6240_hostname
COPYSERVICES_USERNAME root
RECON_INTERVAL 12
BACKUP_HOST_NAME backup_host
<<<

Chapter 4. Configuring

Replace step 2, for the task activating additional database or custom application instances that are not selected during a global installation, in the "Configuring" topic.


    The following text in step 2:
    Run the appropriate command to activate the database or custom application instance:
    DB2®
      ./setup_db2.sh -a install -d <DB2 instance owner $HOME directory> /sqllib/acs/
    SAP on Oracle
      ./setup_ora.sh -a install -d <Oracle instance owner $HOME directory> /acs/
    Oracle
      ./setup_ora.sh -a install -d <Oracle instance owner $HOME directory> /acs/


    Should be replaced by:
    Run the appropriate command to activate the database or custom application instance:
    DB2®
      ./setup_db2.sh -a install -d <DB2 instance owner $HOME directory> /sqllib/
    SAP on Oracle
      ./setup_ora.sh -a install -d <Oracle instance owner $HOME directory>
    Oracle
      ./setup_ora.sh -a install -d <Oracle instance owner $HOME directory>

Chapter 6. Restoring data

In the Restoring DB2 databases section add the following information:

The default behavior when you restore data from a snapshot image is a full database offline restore of all paths that make up the database. This restore includes all containers, the local volume directory, and the database path but does not include the database log files. To restore a snapshot, issue the following command:

db2 restore db DBNAME use snapshot taken at TIMESTAMP

Where TIMESTAMP is a string that represents the time stamp of the backup image and is optional if there is only one backup image in the source specified. The log files are excluded by default from the restore unless you specify the logtarget include option. To restore log files, table spaces, and directories, issue the following command:

db2 restore db DBNAME use snapshot taken at TIMESTAMP logtarget include

For more information about DB2 commands, see the DB2 Information Center home and search for restore database commands.

Chapter 7. Cloning databases

In the Tivoli Storage Manager cloning command section, update:

Table 24. Cloning options for the Tivoli Storage FlashCopy Manager fcmcli command

The following row:

Option Description Default value
-C clone database name Specifies the name of the cloned database residing on the clone system. Specify a valid DB2 or Oracle
database name for the clone database name value. The clone database name can be the name of the production database or a different name. When a
name that is the same as the production database name is used, the cloned database is not renamed.
This command line option must be specified for all cloning functions.

Should be replaced by:

Option Description Default value
-C clone database name The name of the cloned database on the clone system must be specified for all cloning functions.
Specify a valid DB2 or Oracle database name. The clone database name can be the name of the production database or you can specify an alternative name.
Note: For DB2, the cloned database is only renamed and moved to the clone target instance, if the clone database name is different from the production database name.
This command line option must be specified for all cloning functions.

Add the following example to the end of this section:


For a DB2 database the cloned database is not moved to the clone target instance, when the target database name is identical to the production database name. If required to move the cloned database, rename the database by providing an alternative name. For example, two database instances are created on the clone server, the production instance that is named db2prodins and the clone instance named db2cloneins. To clone the production database PROD and move it to the clone target instance, issue the following command:

fcmcli -f create_clone -C CLONE -u db2cloneins -d PROD

Chapter 9. Troubleshooting

Update the troubleshooting section with information about how to recover from a socket connections time out problem.

When the production server and backup server are separated by a firewall, socket connections might time out

Question
After a successful snapshot backup operation, why is it not possible to mount or unmount this snapshot backup on a backup or clone server?

Answer
The socket connection failure can result from a mismatch between the firewalls connection timeout setting and the operating systems frequency of sending keep alive network packets. When a firewall or other network devices such as a router or switch exists between the production and backup server, the daemon connection can time out. A similar situation can exist between a production and clone server. To prevent connections from timing out, the management agent acsd on the production server, requests that the operating system sends out network packets. These packets keep the connection between the servers alive.

The tcp_keepidle operating system parameter specifies the interval of inactivity. Depending on the operating system, this parameter might vary. After this interval of inactivity, the TCP generates a keep alive transmission for the application that requests it. This interval is measured in half seconds. For AIX® operating systems, the keep alive default value for this parameter is 14400 (2 hours). This frequency is sufficient for many environments. Decrease this value when the following conditions exist:

    • A firewall or other network device exists between the production and backup or clone server.
    • If the device connection timeout is less than 2 hours.
For AIX operating systems, issue the following network command to reduce the tcp_keepidle parameter value and send a keep alive transmission every 5 minutes:

no -o tcp_keepidle=600

This change remains in effect until you restart the production server. To permanently modify this parameter, add the command to the /etc/rc.net file.

Appendix A. Configuration files

In the profile overview, CLIENT section update the description of the DEVICE_CLASS parameter.

Add the following note after the conditional statement:

[USE_AT days of week] [FROM time TO time]
(partioned DB2 databases) [ON_DBPARTITIONNUMS list of partitions]

Note: The time period that is specified cannot span midnight for a device class. If a device class time period is required to span midnight, you must specify two time periods for the device class. The first time period must end with a value 1 minute before midnight and the second time period must start at midnight. The following example shows how to specify a time period that spans midnight for a device class:

DEVICE_CLASS myClass FROM 20:00 TO 23:59
DEVICE_CLASS myClass FROM 00:00 TO 06:00

In the profile overview, DEVICE_CLASS device section update the description of the following parameters:

STORAGE_SYSTEM_ID
Specify the storage system ID of the cluster when the storage system is used in an AIX® Logical Volume Manager mirrored environment. This parameter is required in LVM mirrored environments but must not be used in non-mirrored environments. If several device classes refer to the same target volumes file in a mirrored environment, this parameter must also be specified in the target volumes file. In Oracle ASM mirrored environments, this parameter is required if the failure groups are distributed across multiple storage systems.

For XIV®, the STORAGE_SYSTEM_ID refers to the four digit hexadecimal XIV system ID. For SAN Volume Controller or Storwize V7000, the system ID refers to the SAN Volume Controller Cluster ID. For IBM System Storage N series and NetApp storage systems, specify the system ID as displayed for example in the system status pane of the filer interface.

When the value VOLUMES_DIR is specified for the TARGET_SETS parameter, then the STORAGE_SYSTEM_ID parameter must also be specified in the target volumes file (.fct).

Default

    None
Advanced mode only
    None
Note: This parameter might be needed for ASM. For information about ASM failure group environments, see the "LVM mirroring and ASM failure group environments" in the configuring section of the guide.

GRACE_PERIOD
This parameter specifies the period of time, in hours, to wait before reconciling the snapshot. For example, if the option is set to the default, 24, the software reconciles the snapshot to the snapshot repository on the storage solution 24 hours after the snapshot is created.

To reconcile all snapshots, this option is set to 0.

This parameter can be used when the COPYSERVICES_HARDWARE_TYPE parameter is set to XIV.

Default

    24
Advanced mode only
    Yes

COPYSERVICES_SERVERNAME
This parameter applies not only to IBM XIV Storage System, IBM System Storage N series, and NetApp storage systems but to all storage systems.


Updates for IBM Tivoli Storage FlashCopy Manager for VMware Version 3.2

Chapter 2. Preparing your Tivoli Storage FlashCopy Manager for VMware environment
Update information in the Storage Solutions > IBM System Storage N series and NetApp storage systems section.

  • Remove the following bullet point:
    Removes snapshots on storage devices created by Tivoli Storage FlashCopy Manager and that are not in the Tivoli Storage FlashCopy Manager repository.
  • The following text:
      This process is called reconciliation. The reconciliation interval can be specified in the profile parameter RECON_INTERVAL. This time interval is specified in hours. Removing snapshots occurs only when the Tivoli Storage FlashCopy Manager for VMware repository is removed or restored to a prior point in time. To avoid accidentally deleting these snapshots, the reconciliation process bypasses snapshots created within the time interval specified with the GRACE_PERIOD parameter

      Should be replaced by:
      This process is called reconciliation. The reconciliation interval can be specified in the profile parameter RECON_INTERVAL. This time interval is specified in hours.

Update information in the Preparation of storage devices > Storage solutions > Examples of target volume files setup section.

    Replace figure 4 in the topic "Examples of target volume files setup". This example shows a setup where three datastores are protected by three dedicated backup operations. The storage volume layout provides three target volumes for each of the source volumes. This configuration results in a complex setup with three DEVICE_CLASS parameters that are specified in the profile. In each of the DEVICE_CLASS parameters, the parameter VOLUMES_FILE points to the target volumes file. In the target volumes file, there are three target sets defined for each of the DEVICE_CLASS parameters. Each DEVICE_CLASS parameter represents one datastore.
    To clarify this situation replace Figure 4, Tivoli Storage FlashCopy Manager for VMware target volumes files example 2 with the following figure:

    Figure 4. Tivoli Storage FlashCopy Manager for VMware target volume files example 2


Chapter 4. Configuring Tivoli Storage FlashCopy Manager for VMware

  • Replace text in the section "Configuring Tivoli Storage FlashCopy Manager for VMware".

      The following text:

      The target volumes files

      You must create and edit the target volumes files that are needed to specify the target volumes for Tivoli Storage FlashCopy Manager for VMware backups on DS8000, SAN Volume Controller and Storwize V7000.

      Note: Target volume files are not required for the XIV system and SAN
      Volume Controller 5.1 and later.

      Should be replaced by:

      The target volumes file
      You must create and edit the target volumes file for DS8000® systems. The
      target volumes file is required and specifies the target volumes to be used
      for a Tivoli Storage FlashCopy Manager for VMware backup operation. For Storwize
      V7000 and SAN Volume Controller storage systems, you can use either the
      TARGET_NAMING parameter or target volumes file. The target volumes file is not
      required for other storage systems.


Update information in the Tivoli Storage FlashCopy Manager for VMware target set definitions section
  • Add the following prerequisite text to this section:
      To schedule backup operations successfully for multiple target disks on storage systems, ensure that the following configuration prerequisites are met:
      • A dedicated DEVICE_CLASS section in the Tivoli Storage FlashCopy Manager for VMware profile file for each datastore or group of datastores that you want to back up together.
      • A unique list of target set names must be associated with each DEVICE_CLASS section. The TARGET_SETS parameter specifies the target volumes or lists the target set names to use in the copy operation. The names must be unique to all device class sections in the profile file.

      Each backup schedule that is run must use a dedicated DEVICE_CLASS section that is specified for each datastore or datastores in the Tivoli Storage FlashCopy Manager for VMware profile file.
      For more information, see "Examples of target volume files setup" and "Examples of target naming setup".

Chapter 5. Operating the Data Protection for VMware command-line interface

  • Replace text in the section "Operating the Data Protection for VMware command-line interface".

      The following text:
      A list of parameters IBM® uses to perform snapshot backups.

      Should be replaced by:
      IBM® uses a list of parameters to perform snapshot backups.

  • Replace text in the section "Deleting a backup".
      The following text:
      If a backup is deleted, this command returns the delete task and the corresponding
      run. The -F parameter forces a delete even if the corresponding task is still running
      or if a backup is not completed. The -F parameter also triggers the deletion of the source or target relations in the storage system. Only Tivoli Storage FlashCopy
      Manager for VMware backups and backup schedules can be deleted. When
      specifying a delete object list file

      Should be replaced by:
      If a backup is deleted, this command returns the delete task and the corresponding
      run. The -F parameter forces a delete even if the corresponding task is still running
      or if a backup is not completed. The -F parameter also triggers the deletion of the source or target relations in the storage system. Only Tivoli Storage FlashCopy
      Manager for VMware backups and backup schedules can be deleted.

    • Replace text in the section "Creating a backup".
      The following text:
      To specify the data mover to use to offload a backup to Tivoli Storage Manager use
      the -o parameter. For example, ./vmcli -f backup -t FCM_TSM_LATEST -I
      backupInfile --name FCM_TSM_backup --runnow -o datamovernode1.

      Should be replayed by:
      To specify the data mover to use to offload a backup to Tivoli Storage Manager use
      the -o parameter. For example, ./vmcli -f backup -t FCM_TSM_LATEST -I
      backupInfile --name FCM_TSM_backup --runnow -o datamovernode1.

      Note: Before, running an offloaded backup to Tivoli Storage Manager that has a backup type of incremental, you must enable changed block tracking (CBT) manually for all virtual machines. Alternatively, run a Tivoli Storage Manager for Virtual Environments backup that includes these virtual machines before you run the first offloaded backup to Tivoli Storage Manager.

Chapter 7. Tivoli Storage FlashCopy Manager for VMware configuration files
  • Update information in Table 15. Tivoli Storage FlashCopy Manager for VMware profile parameters - VMWARE section
      The following row:

      Device Description Default value Advanced
      mode only
      MAX_VERSIONS ADAPTIVE
      The maximum number varies depending on the available space. Tivoli Storage FlashCopy Manager for VMware reuses the oldest target set as the target for the current backup.

      The maximum number of snapshot versions to be maintained. When this number is reached, the oldest version is deleted.
      Adaptive No

      Should be replaced by:

      Device Description Default value Advanced
      mode only
      MAX_VERSIONS This parameter specifies the number of Flashcopy or snapshot backups of a data store to be retained on a storage device. Specify one of the following options:

      ADAPTIVE
      The maximum number varies depending on the available space. Tivoli Storage FlashCopy Manager for VMware reuses the oldest target set as the target for the current backup.

      n
      Specify the maximum number of flashcopy or snapshot versions to be maintained. When this number is reached, the oldest version is deleted.
      Adaptive No

  • Update information in Table 17. Tivoli Storage FlashCopy Manager for VMware profile parameters - DEVICE_CLASS section.
      The following row:

      Device Name Description Default value Advanced
      mode only
      • IBM XIV Storage Systems
      • IBM System Storage N series
      • NetApp storage systems
      GRACE_PERIOD This parameter specifies the period of time, in hours, to wait before reconciling the snapshot. For example, if the option is set to the default, 24, the software reconciles the snapshot to the snapshot repository on the storage solution 24 hours after the snapshot is created.
      To reconcile all snapshots, this option is set to 0.
      This parameter can be used when the COPYSERVICES_HARDWARE parameter is set to XIV, NAS_NSERIES, or SAN_NSERIES.
      24 hours Yes

      Should be replaced by:

      Device Name Description Default value Advanced
      mode only
      IBM XIV Storage Systems GRACE_PERIOD This parameter specifies the period of time, in hours, to wait before reconciling the snapshot. For example, if the option is set to the default, 24, the software reconciles the snapshot to the snapshot repository on the storage solution 24 hours after the snapshot is created.
      To reconcile all snapshots, this option is set to 0.
      This parameter can be used when the COPYSERVICES_HARDWARE_TYPE parameter is set to XIV.
      24 hours Yes

      COPYSERVICES_SERVERNAME
      This parameter applies not only to IBM XIV Storage System, IBM System Storage N series, and NetApp storage systems but to all storage systems.

Appendix A. The Data Protection for VMware command-line interface

      • Replace text in the section "VMCLI delete command".

        The following text:

        This function runs a Tivoli Storage FlashCopy Manager for VMware delete
        operation. You can use the -B and include the backupID, or the -B and include the taskID to specify the backup or the backup schedule.

        Should be replaced by:

        This function runs a Tivoli Storage FlashCopy Manager for VMware delete
        operation. You can use the -B parameter and include the backupID, or the -T parameter and include the taskID to specify the backup or the backup schedule.

      • Update text in the section "VMCLI backup command".
        Add the TSM_IFFULL and TSM_IFINCR option to the -t backupType parameter of the vmcli -f backup command:

        TSM_IFFULL
        Creates an incremental forever full backup of the specified backup
        objects. When TSM_IFFULL is specified, template VMs that are
        unchanged since the last backup are also included.

        TSM_IFINCR
        Creates an incremental forever incremental backup of the specified
        backup object. This option backs up only the data that has changed
        since the last backup.


Updates for IBM Tivoli Storage FlashCopy Manager for Windows 3.2

(IT03801) For users of Tivoli Storage FlashCopy Manager for Microsoft SQL legacy backups, when changing Log and Set backups to a new management class, the new management class setting takes effect only for new backups. Existing backups are not rebound to the new management class. Therefore, schedule a new FULL backup after changing the management class for either Log or Set backups.
-----------------------------------------------------------------------------------------------------------------------------

The following information is to be added to the 'Protecting SQL data' section ->

    Restoring databases with full-text catalogs and indexes

    When protecting SQL Server 2005 and the full-text index is part of a full-text catalog note that the full-text catalog has a physical path. In this scenario, the full-text catalog is treated as a database file.

    When protecting SQL Server 2008 and later data, a full-text catalog is either a logical or virtual object that contains a group of full-text indexes. This full-text catalog does not have a physical path. In this scenario, the full-text catalog is part of the filegroup.

    To restore a database with the SQL Server 2005 physical full-text catalog file from the command-line interface, use the /RELocate and /TO parameters. For example:
    Restore DATABASE full /relocate=database,sysft_docindex,database_log /TO={database_dir}\database.mdf,{database_dir}\docindex,{database_log_dir}\database_log.ldf

    From the GUI, for SQL Server 2005 physical full-text catalog files, you can use the Relocate files individually option. From the command-line interface, use /relocate and /TO instead of /RELOCATEDir.

    To restore a database with SQL Server 2008 and later full-text catalog files, no data is explicitly stored. The file is automatically backed up and restored as part of the filegroup.

Throughout the document: The specification for the DATEformat values are not consistent.

Correct specification for DATEformat values:

DATEformat= dateformatnum


The /DATEformat parameter selects the format you want to use to
display
dates.


The dateformatnum
variable can range from 1 to 7. The initial
value is 1.


The number values specify the following formats:
    1 MM/DD/YYYY

    2 DD-MM-YYYY

    3 YYYY-MM-DD

    4 DD.MM.YYYY

    5 YYYY.MM.DD

    6 YYYY/MM/DD

    7 DD/MM/YYYY

Incorrect specification for DATEformat values:

DATEformat= dateformatnum


The /DATEformat parameter selects the format you want to use to
display
dates.


The dateformatnum
variable displays the date in one of the following formats. Select the format number that corresponds to the format you want to use.

The number values specify the following formats:
    1 MM/DD/YYYY. This is the default.
    2 DD-MM-YYYY

    3 YYYY-MM-DD

    4 DD.MM.YYYY

    5 YYYY.MM.DD
-----------------------------------------------------------------------------------------------------------------------------
Chapter 5. Protecting data with Tivoli Storage FlashCopy Manager --> Scheduling tasks

A sentence is missing from the third paragraph. At the end of the third paragraph, add the following sentence: The following character is not supported: %

These updates also affect content published in the following Information Center topic -> http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/index.jsp?topic=%2Fcom.ibm.itsm.fcm.win.doc%2Ft_fcm_scheduling.html
-----------------------------------------------------------------------------------------------------------------------------
Add the following topic to the Planning section:

Planning protection for custom application and file system data

Tivoli Storage FlashCopy Manager helps to protect and to manage environments by facilitating the backup, restore, and recovery of custom application and file system data.

When a Tivoli Storage FlashCopy Manager local backup operation begins, the first step initiates the reconciliation process. The copies of the snapshot that are valid for expiration and local snapshots that have been deleted are reconciled.

From the Tivoli Storage Manager server database, the value of VSS data container VSSDC_xx is identified. The mapping to target storage volume is identified in the adsm.sys folder. The default location for this folder is the installation path used by the Tivoli Storage Manager backup-archive client.

After a successful reconciliation, the metadata that is stored on the Tivoli Storage Manager server is deleted, the target storage volume is reused for the new snapshot, and the TargetSetsState file is updated with the current mapping.

In the x:\adsm.sys\vss_staging directory, the LSM_REP_LOG_VOL_SNAP and .TsmFmDatabases subfolders are required. Do not manually delete these folders.

To protect the data in these folders, regularly back up the folders. To back up the folders, use the TSM archive function and not the incremental backup function. If you complete an incremental backup, the contents of these folders are not included in the backup. If you do not want to archive, use the xcopy command to copy the content to a directory that can be processed with an incremental backup.
-----------------------------------------------------------------------------------------------------------------------------
Add the following topic to the Planning section:

Planning for data protection

For Microsoft SQL Server data protection, one of the most important tasks that you need to complete is the routine full database backup of the master database. You can schedule routine full database backups so you frequently protect the data to meet your business needs.

If the master database is damaged while a server instance is running, fix the damaged database by restoring a recent full master database backup. If a server instance cannot start because the master database is damaged, the master database needs to be rebuilt. When you rebuild a master database, all system databases revert to their original state. For more information about rebuilding the master database, see the Microsoft SQL Server documentation.
-----------------------------------------------------------------------------------------------------------------------------
Replace the Restoring the master database topic in the Protecting data section with the following topic:

Restoring the master database

To restore a master database, start an instance of SQL Server in single-user mode. You cannot restore a master database when the SQL Server instance is set to multi-user mode.

When the SQL Server instance is in single-user mode, the command line interface, tdpsqlc.exe, should be used. The Microsoft Management Console (MMC) GUI, included with FlashCopy Manager for SQL / Data Protection for SQL, does not support interacting with a SQL server instance started in single-user mode.

To restore the master database, complete the following steps:
1. Click Start > All Programs > Tivoli Storage Manager > Data Protection for Microsoft SQL Server > SQL Client - Command Line.
2. Start the SQL Server in single-user mode. For more information about SQL Server startup options, see the Microsoft SQL Server documentation. For example, the following link might provide useful information: http://technet.microsoft.com/en-us/library/ms190737.aspx
3. Use Data Protection for SQL to restore the master database. When the master database finishes the restoration process, the SQL Server shuts down and an error message is displayed. The message indicates that the connection to the SQL Server is lost. This loss of connection is expected.
4. Restart the Database Engine to restore SQL Server to the typical multi-user mode.
5. Manually reapply any changes that were made to the master database after the date of the database backup used to do the restore operation.

After the master database is restored, the MMC can be used to back up and restore individual databases that are operating in single-user mode.


The following information is an addition to the content published for IBM Tivoli Storage FlashCopy Manager for Windows Version 3.2, Installation and User's Guide.

(IT03558) Mailbox history retention

Even if a mailbox user is deleted from Active Directory and backups that contained that mailbox are expired, Tivoli Storage FlashCopy Manager for Windows retains the mailbox history information indefinitely on the Tivoli Storage Manager server. Therefore, the mailbox history information for deleted mailboxes can still be seen within the restore search views even though the associated backups might be expired. The mailbox restore list, which is populated from the mailbox history, is not intended to be an all-inclusive list of mailboxes that can be restored. It is made available for ease of use.

Updates to the Tivoli Storage FlashCopy Manager for Windows: Installation and User's Guide will be incorporated in the next revision of the publication.

----------------------------------------------------------------------------------------------------------------------------
(IT05115) Clarification regarding VSS restore of a master database

Microsoft SQL Server only supports offline VSS restores of the master database. Data Protection for Microsoft SQL Server does not support offline restore operations. As such, the software cannot cannot be used to restore the master database.

To restore a VSS backup of a master database, complete the following steps:
  1. Ensure that the SQL Server is online.
  2. Restore the master database to a new database in the Microsoft Management Console (MMC), or at the command line. For example: Enter the tdpsqlc command with the /recovery=no option.
  3. After the restore operation is complete, verify that all data files are restored successfully.
  4. Stop the SQL Server instance, and rename all data files of the master database.
  5. Copy all data files from the new master_restore database to the location of the master database. Verify that all data files are copied.
  6. Start the SQL Server instance. Verify that the master database is restored successfully.

The aforementioned clarification belongs in the following topics (PDF and Knowledge Center).
  • Restoring the master database
  • Setting single-user mode for restore operations
  • Restore command

-----------------------------------------------------------------------------------------------------------------------------------------------
(IT03710) Clarification regarding supported backup operations on replica AlwaysOn availability databases

For this documentation update, the following note belongs in the locations identified under "Knowledge Center", and "Installation and User's Guide".
    Microsoft does not support legacy full backups on secondary replicas. Data Protection for Microsoft SQL Server, however, does allow a full backup of a secondary replica to be completed based on Tivoli Storage Manager policy.

    When a user initiates a full backup of a secondary replica, the underlying implementation of Data Protection for SQL Server is to back up the data as copyfull . However, Data Protection for SQL Server detects the intended full backup operation and applies the Tivoli Storage Manager policy associated with the full backup type. The Microsoft Management Console (MMC) and CLI views honor the TSM policy that applies to the backup type and in this instance, show the backup type as full. For more information, see this Microsoft article: http://msdn.microsoft.com/en-us/library/hh245119.aspx

Knowledge Center:
(1) V6.4 - Data Protection for Microsoft SQL Server > Data Protection for Microsoft SQL Overview > Microsoft SQL Server 2012 Protection > Always On Availability Groups > Backups of availability databases
https://www.ibm.com/support/knowledgecenter/SSTFZR_6.4.0/com.ibm.itsm.db.sql.doc/c_dpfcm_ovw_bup_sqladb_sql.html?lang=en

(2) V7.1 - Data Protection for Microsoft SQL Server > Planning > Always On Availability Groups > Backups of availability databases
http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.db.sql.doc/c_dpfcm_ovw_bup_sqladb_sql.html

(3) V3.2 - Tivoli Storage FlashCopy Manager for Windows > Windows overview > Microsoft SQL Server2012 protection > Always On Availability Groups > Backups of availability databases
https://www-01.ibm.com/support/knowledgecenter/SS36V9_3.2.0/com.ibm.itsm.fcm.win.doc/c_dpfcm_ovw_bup_sqladb_fcmw.html

(4) V4.1 - Tivoli Storage FlashCopy Manager for Windows > Planning > Planning protection for Microsoft SQL Server data > Always On Availability Groups > Backups of availability databases
https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.win.doc/c_dpfcm_ovw_bup_sqladb_fcmw.html

Installation and User's Guide:
(1) V6.4 - Page 17 (Backups of availability databases)
(2) V7.1 - Page 28 (Backups of availability databases)
(3) V3.2 - Page 16 (Backups of availability databases)
4) V4.1 - Page 32 (Backups of availability databases)


Updates to the Data Protection for Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server, and Tivoli Storage FlashCopy Manager for Windows, Installation and User's Guides will be incorporated in the next revision of the publication.

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage FlashCopy Manager

Software version:

3.2

Operating system(s):

AIX, HP Itanium, Linux/x86, Solaris, Windows

Software edition:

All Editions

Reference #:

7035972

Modified date:

2013-04-26

Translate my page

Machine Translation

Content navigation