IBM Support

IBM Tivoli Storage FlashCopy Manager Version 4.1 Documentation Updates

Product Documentation


Abstract

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

Content

Beginning with Version 4.1.4, IBM Tivoli Storage FlashCopy Manager is renamed IBM Spectrum Protect Snapshot. Some applications such as the software fulfilment systems and IBM License Metric Tool use the new product name. However, the software and its product documentation continue to use the Tivoli Storage Manager product name.

To learn more about the rebranding transition, see http://www.ibm.com/support/docview.wss?uid=swg21963634.

------------------------------------------------------------------------------------------------------------------------------------------
Click the following links to view updates to the Tivoli Storage FlashCopy Manager Installation and User's Guides Version 4.1:

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 Tivoli Storage FlashCopy Manager for UNIX and Linux V4.1

(Version 4.1.4) FlashCopy Manager for Oracle, and FlashCopy Manager for Oracle in an SAP Environment/ What's new

Version 4.1.4 is compatible with Oracle 12c for non-Container Databases (CDB).



(All versions) FlashCopy Manager for DB2, Cloning databases
Guidance to show that each clone target must have a unique database name should be added.
  • You can have several cloned databases of one source database that are running on one host. Each clone target requires a unique database name.
  • The cloned database can also be renamed to any valid database name during the IBM Spectrum Protect Snapshot cloning process. Each clone target requires a unique database name.

In the following section: Configuration files/Profile configuration file/CLONING the example showing how to specify a time period that spans midnight for a device class is formatted as follows:
DEVICE_CLASS myClass1 USE_FOR_CLONING CL1 FROM 20:00 TO 23:59
DEVICE_CLASS myClass2 USE_FOR_CLONING CL2 FROM 00:00 TO 06:00

In the syntax diagram in Commands and scripts/Cloning commands and FlashCopy cloning function-clauses the following guidance is needed for DB2:
  • -d database-name is the name of the source database.
  • The -i instance_name and -B clone_ID are not available.

(All versions) FlashCopy Manager for Oracle and Oracle in an SAP Environment, Cloning databases
Guidance to show that each clone target must have a unique database name should be added.
  • You can have several cloned databases of one source database that are running on one host. Each clone target requires a unique database name.
  • The cloned database can also be renamed to any valid database name during the IBM Spectrum Protect Snapshot cloning process. Each clone target requires a unique database name.

In the following section: Configuration files/Profile configuration file/CLONING the example showing how to specify a time period that spans midnight for a device class is formatted as follows:
DEVICE_CLASS myClass1 USE_FOR_CLONING CL1 FROM 20:00 TO 23:59
DEVICE_CLASS myClass2 USE_FOR_CLONING CL2 FROM 00:00 TO 06:00

In the syntax diagram in Commands and scripts/Cloning commands and FlashCopy cloning function-clauses the following guidance is needed for Oracle products:
  • -d database-name is not available.
  • The -i instance_name and -B clone_ID are not available.

(All versions) FlashCopy Manager for UNIX and Linux For DB2/Configuration Files/Offload/DB2_OPTIONS

The following note is added,


Note: If you use DB2_OPTIONS in combination with NUM_BUFFERS, BUFFER_SIZE or PARALLELISM, errors that relate to incorrect order of options are sent for the DB2 backup operation. Resolve the errors by not using the NUM_BUFFERS, BUFFER_SIZE, and PARALLELISM parameters with the DEDUP_DEVICE option in the DB2_OPTIONS string. If this cannot be avoided, then specify the corresponding DB2 options WITHnum-buffersBUFFERS, BUFFERbuffer-size, and PARALLELISMn with the DB2_OPTIONS parameter and the DEDUP_DEVICE option. Ensure to use the correct order of options that is defined in the DB2 documentation for the DB2 BACKUP command.

(All versions) FlashCopy Manager for UNIX and Linux all components

The profile parameter, BACKUPIDPREFIX in the CLIENT section is ignored by the software. You should not enter a value for this parameter during the setup and configuration of the product; accept the default value. (IT13757)

(All versions) FlashCopy Manager for UNIX and Linux all components

The DEVICE_CLASS parameter STORAGE_SYSTEM_ID for the Storwize and San Volume Controller profile is incorrectly listed as the Cluster ID. If you enter the Cluster ID for STORAGE_SYSTEM_ID, an error message occurs. The value for this parameter for Storwize and San Volume Controller is the Cluster Name. (IT14700)

(4.1.3 and after) Section: Configuration tasks > Configuring storage environments > Select the FLASHCOPY_TYPE, Table1, Note 1.

FLASHCOPY_TYPE COPY is missing from the second sentence of this note. The second sentence in Note 1 should read as follows,

If fully allocated source volumes are used in combination with space-efficient target volumes, then Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY.

(4.1.1 only) Section: Configuration tasks > Configuring storage environments > Select the FLASHCOPY_TYPE

In the table entitled Selecting the FLASHCOPY_TYPE for DS8000, SAN Volume Controller, and Storwize family, Note 1 in the table has been updated as follows:



Note 1: If space-efficient source volumes are used in combination with space-efficient target volumes, Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY. If fully allocated source volumes are used in combination with space-efficient target volumes, then Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE NOCOPY only

This note is referenced for both FLASHCOPY_TYPE COPY, and FLASHCOPY_TYPE INCR.

(4.1.1 only) Section: Planning > Storage solutions > SAN Volume Controller, DS8000, and Storwize family > SAN Volume Controller and Storwze family

In the paragraph entitled Recommendations for setting up the environment, the first bullet point has been updated as follows:

If space-efficient source volumes are used in combination with space-efficient target volumes, Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY. If fully allocated source volumes are used in combination with space-efficient target volumes, then Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE NOCOPY only.

(4.1.1 only) Section: Configuration tasks > Running the setup script for a DB2® pureScale environment

In the Results section of this procedure, the final bullet point should read as follows:

The configuration wizard registers the Tivoli Storage FlashCopy Manager management daemon acsd and generic device agent acsgen in /etc/inittab, or it creates and starts the upstart jobs. These processes are started automatically even after a system restart.

In the Results section, remove the note concerning installing Tivoli Storage FlashCopy Manager in an HA environment.

Section: Restoring data > Restoring data with remote mirroring

In the procedure, Restore Oracle in an SAP® environment database data the example provided in step 5 should read as follows: backint -f inquire_detail.

Section: Appendix B > Examples > Examples (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;
      }
Section: New for Tivoli Storage FlashCopy Manager for UNIX and Linux V4.1

KVM support has been added as follows:



KVM support
Tivoli Storage FlashCopy Manager V4.1 adds support for backup, restore, and cloning operations inside KVM guests.

Section: Planning > Preparing for installation>Preparing applications that run on VMware virtual machines

This topic has been updated as follows:

Preparing applications that run on VMware or KVM virtual machines

Before, you install Tivoli® Storage FlashCopy® Manager on VMware or KVM virtual machines that run Linux guest operating systems, you must verify the configuration of the application that you want to protect.

Before you begin

There are specific configuration requirements for different applications. For more information about requirements, see Planning.

Procedure

VMware

  • Before you back up data or clone databases on VMware virtual machines, ensure that all source LUNs in the backup or clone operations are attached to the virtual machine with one of the following methods:
    • VMware physical mode raw device mapping (pRDM)
    • iSCSI
    • Network file system (NFS)
  • Run a Tivoli Storage FlashCopy Manager restore operation from a snapshot to an existing pRDM disk. The operation does not create a virtual machine or pRDM definition as part of the restore process.

KVM
  • Before you back up data or clone databases on KVM virtual machines, ensure that all source LUNs in the backup or clone operations are attached to the virtual machine with one of the following methods:
    • Block device mapping (BDM)
    • iSCSI
    • Network file system (NFS)
    • PCI Passthrough
  • Run a Tivoli Storage FlashCopy Manager restore operation from a snapshot to an existing BDM disk. The restore operation does not create a virtual machine or BDM definition as part of the restore process.

Section: Planning > Preparing for installation

A new topic has been added called Checking the KVM setup, as follows:


Checking the KVM setup

Ensure that when the Tivoli® Storage FlashCopy® Manager KVM setup uses Block Device Mapping, the LUNs are mapped to the KVM guest as multipath devices. The LUNs must be visible as multipath devices inside the KVM guest. Run the multipath command to check your setup for KVM.

Procedure


To verify your KVM setup, run the multipath command from within the KVM guest. The command output looks similar to the following example:
kvm-guest:~ # multipath -ll
mpathat (360050768018205de4000000000001949) dm-7 IBM ,2145
size=2.0G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=50 status=active
`- 3:0:0:3 sdf 8:80 active ready running

In the example, 360050768018205de4000000000001949 is the LUN identifier. It is a unique number that must not be overwritten by the KVM stack. The product storage identifier must be visible inside the KVM guest. In the example, this identifier is IBM ,2145.

Section: Planning > Preparing backup or cloning servers for applications running on VMware virtual machines

This topic has been updated as follows:

Preparing backup or cloning servers for applications running on VMware or KVM virtual machines

If a backup or clone server you are using is a VMware or KVM virtual machine, the storage device must be attached to the virtual machine with either iSCSI or Network file system.

Before you begin

If physical hosts are used as backup or clone servers, see Installation prerequisites for backup and clone servers.

Procedure


Verify that all target LUNs in backup or clone operations are attached to the virtual machine with one of the following attachment methods:
  • iSCSI
  • Network file system (NFS)

Section: Planning > Preparing backup and cloning servers > Installation prerequisites for backup and clone server

The section "DB2 and DB2 in an SAP environment" requires an update to the first paragraph. Replace the first paragraph with the following information:

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.



See Installation prerequisites for backup and clone server for details.

Section: Restoring data > Restoring DB2 databases

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

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


Section: Commands and scripts > Backup, restore, cloning commands, and utilities > Cloning commands

The section "function-clause: FlashCopy cloning operations" requires an update to Table 2. Cloning options for the Tivoli Storage FlashCopy Manager fcmcli command.

Update the -C clone database name description with the following text:



OptionDescriptionDefault value
-C clone database nameThe 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

See Cloning commands for details.

For more information about Tivoli Storage FlashCopy Manager for UNIX and Linux, see http://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.unx.doc/t_protect_fcmul.html.

Updates for Tivoli Storage FlashCopy Manager for VMware V4.1



When a user does not have sufficient permissions for any datacenter, access to the Tivoli Storage FlashCopy Manager for VMware GUI is blocked. The Tivoli Storage FlashCopy Manager for VMware GUI issues error message GVM2013E to advise that the user is not authorized to access any managed datacenters due to insufficient permissions. Other new messages are also available that inform users of issues that result from insufficient permissions.

To resolve permissions issues, system administrators can assign the required permissions to VMware users as documented in the following information center topic: Configuring the environment for the installation (http://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.vm.doc/c_fvm_ins_prepare.html)

Section: Installing and upgrading > Configuring the environment for the installation

The section "Setting up a role with minimum privileges to access the vCenter Server" requires an update to Table 1. Objects and Privileges to assign to the FCM for VMware role for backup and recovery operations. You must create a role with associated privileges on the vCenter Server to back up and restore virtual machines. This table describes the minimum privileges that are required by this role.

Add "Move datastore" privilege to the minimum list of Datastore privileges that are required by Tivoli Storage FlashCopy Manager.
See Configuring the environment for the installation for details.

Section: Configuring > Tivoli Storage FlashCopy Manager for VMware target set definitions > Target set definitions

The section "Examples of target volume files setup" requires an update to example 2. 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 5, Tivoli Storage FlashCopy Manager for VMware target volumes files example 2 with the following figure:

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


Section: Operating the Data Protection for VMware command-line interface

The following restriction notice requires an update:
Restriction: Support for virtual machine backup and restore operations is limited to virtual machine names and datacenter names, that contain English 7-bit ASCII characters only. Virtual machine names and datacenter names that use other language characters are not supported currently.

The restriction to use only English 7-bit ASCII character names also applies to virtual machine disk names. Therefore, add virtual machine disk names to the list of names that require English 7-bit ASCII characters:

Restriction: Support for virtual machine backup and restore operations is limited to virtual machine names, datacenter names, and virtual disk names, that contain English 7-bit ASCII characters only. Virtual machine names, datacenter names, and virtual disk names that use other language characters are not supported currently.
See Operating the Data Protection for VMware command-line interface for details.

Section: Tivoli Storage FlashCopy Manager for VMware configuration files > DEVICE_CLASS and VMWARE sections

For IBM System Storage N series and NetApp storage systems that use an iSCSI host connection add the following information to:
  • Table 1. Tivoli Storage FlashCopy Manager for VMware profile parameters - DEVICE_CLASS section.

    For the COPYSERVICES_HARDWARE_TYPE parameter, update the description for the SAN_NSERIES option. This option should state that you specify the SAN_NSERIES when the VMware datastores are stored on SAN-attached or iSCSI-attached N series or NetApp storage systems.
  • Table 1. Tivoli Storage FlashCopy Manager for VMware profile parameters - VMWARE section

    For the HOST_NAME_MAPPING parameter update the description to include the following information:
    The HOST_NAME_MAPPING parameter represents how an auxiliary ESX server host name in the vSphere environment is mapped to the host name as defined on the storage subsystem. Use the following format when you specify a value for this parameter:
    Auxiliary ESX host name:storage subsystem host name

    For N series or NetApp storage systems that are accessed by using a storage area network (SAN), assign the NetApp initiator group name to the storage subsystem host name option. This assignment applies when the storage system is accessed through transport protocols such as Fibre Channel (FC) or iSCSI.

For more information about Tivoli Storage FlashCopy Manager for VMware, see http://www.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.vm.doc/t_protect_fcmvmw.html.

The following information is an addition to the content published for IBM Tivoli Storage FlashCopy Manager for VMware Version 4.1.1, Installation and User's Guide.
This information is available online at
http://www.ibm.com/support/knowledgecenter/SS36V9_4.1.1/com.ibm.itsm.fcm.vm.doc/t_protect_fcmvmw.html

Section: Overview > Supported storage systems > SAN Volume Controller, DS8000, and Storwize family devices

The section "SAN Volume Controller, DS8000, and Storwize family devices" requires an update to Table 1. FlashCopy types and supported devices

FlashCopy types and supported devices

Type
Description
Supported devices
COPY
A COPY type FlashCopy is a point-in-time copy of a volume, followed by a subsequent background copy operation that creates a physical copy of the source volume. DS8000®[1]
SAN Volume Controller[2]
Storwize® family[2]
INCR
An INCR type FlashCopy is similar to a COPY type except that less data is copied between two consecutive FlashCopy backups. After the first FlashCopy, only the changed blocks are copied to the target.DS8000 [1]
SAN Volume Controller [2]
Storwize family [2]
NOCOPY
A NOCOPY FlashCopy is a copy-on-write from the source to the target. The copy occurs when a data block is initially changed on the source volume. There is no background copying. Only changed data blocks are present on the target volume. Any unchanged data blocks are referenced from the source volume. DS8000 [1]
SAN Volume Controller [2]
Storwize family[2]
Note:
[1]
For DS8000 storage, the following restrictions apply:
  • Only one incremental FlashCopy mapping per source volume is allowed.
  • When you specify an incremental FlashCopy, you can have one target set only in the target volumes file (.fct file). If more than one target set is specified, Common Information Model (CIM) errors can occur.
  • A FlashCopy to a space efficient volume is not supported.
[2]
For SAN Volume Controller and Storwize family storage, if you use space efficient volumes the following restrictions determine the FlashCopy type to use:
  • When the source and target volumes are both space efficient volumes, there is no restriction on the type of copy operation.
  • When the source volume is a fully allocated volume that is not space efficient and the target volume is space efficient, then Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY. These options are available when the profile parameter ALLOW_ALL_FLASHCOPY_TYPES is set to YES. The default value of ALLOW_ALL_FLASHCOPY_TYPES is NO. When the default value is used, only FLASHCOPY_TYPE NOCOPY is possible.

With a space efficient FlashCopy, the amount of physical space that is consumed by the target volume is limited to the minimum amount of space that is required to maintain the copy.


(Version 4.1.3 and after) Section: Configuring Tivoli Storage FlashCopy Manager for VMware > Configuring storage environments > Selecting the FLASHCOPY_TYPE

The section "Selecting the FLASHCOPY_TYPE" requires an update to Table 10. Selecting the FLASHCOPY_TYPE for SAN Volume Controller, DS8000 and Storwize family :

Note 2: If space-efficient source volumes are used in combination with space-efficient target volumes, Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY.
If fully allocated source volumes are used in combination with space-efficient target volumes, then Tivoli Storage FlashCopy Manager can be configured to use FLASHCOPY_TYPE COPY, INCR, or NOCOPY. These options are available when the profile parameter ALLOW_ALL_FLASHCOPY_TYPES is set to YES. The default value of ALLOW_ALL_FLASHCOPY_TYPES is NO. When the default value is used, only FLASHCOPY_TYPE NOCOPY is possible.

Note 3: If you use SAN Volume Controller and Storwize family dynamic target allocation
then FLASHCOPY_TYPE INCR is not available.


Section: Configuration files > DEVICE CLASS section > Storwize family and SAN Volume Controller: Static Target Allocation

Add the following parameter to the section "DEVICE_CLASS parameters for static target allocation":

ALLOW_ALL_FLASHCOPY_TYPES

Use this parameter when Tivoli Storage FlashCopy Manager is to be
configured with FLASHCOPY_TYPE FULL, or FLASHCOPY_TYPE INCR. Use the
parameter when the source volumes are fully allocated and the target volumes
are space-efficient. The following list identifies the available options:

YES Allows Tivoli Storage FlashCopy Manager to be configured to use
FLASHCOPY_TYPE FULL, or FLASHCOPY_TYPE INCR when the source volumes
are fully allocated and the target volumes are space-efficient.

NO If the source volumes are fully allocated and the target volumes are
space-efficient then the parameter FLASHCOPY_TYPE can be set to NOCOPY
only.

Default
NO

Advanced mode only
Yes

Section: Configuration files > VMware section >

HOST_NAME_MAPPING parameter

Represents how an ESX server host name in the vSphere environment is mapped to a host name on the storage subsystem.
Use the following format when you specify a value for this parameter:

ESX host name:storage subsystem host name [USE_FOR device class names]

Where:
ESX host name
The ESX host name that is specified on the vCenter Server.

storage subsystem host name
The storage system host name that is specified on the storage system.

Depending on the storage system and configuration, it might be necessary to use one of the following values:

  • For IBM® System Storage® N series and NetApp storage systems that are accessed by using network-attached storage, specify the IP address of the VMkernel interface of the ESX host. If the VMkernel port for NFS traffic is configured on the same network interface that connects to the ESX host in the vSphere environment, specify the ESX host name.
  • For N series and NetApp storage systems that are accessed by using a storage area network (SAN), specify the NetApp initiator group name. This requirement applies when the storage system is accessed through transport protocols such as Fibre Channel (FC) or iSCSI.
  • For Storwize® family or SAN Volume Controller storage systems, the optimum method is to use dynamic volume mapping to the ESX hosts. Tivoli Storage FlashCopy Manager for VMware automatically assigns the FlashCopy target volumes to the ESX hosts when required. With this method, the backup time is decreased. Specify the host name that is used on the storage system. However, if you use static volume mapping, you must specify PREASSIGNED_VOLUMES as the storage system host name.
  • For configurations where hosts are in a cluster on the storage system, specify the cluster name for all ESX hosts that are part of the cluster.
  • For IBM XIV® Storage Systems and other third-party storage systems, specify the storage system host name.
USE_FOR device class names
Specifies the applicable device class for this mapping. This attribute is optional. You can specify more than one device class, separate each name by using a space character.
Tip: To apply different mappings to different storage systems, use the USE_FOR option . A mapping statement for a device class that uses the USE_FOR attribute overrides a general mapping statement that does not use the attribute.

The following example maps the fully qualified ESX host name on the vCenter Server esxserv1.domain.com to the ESX host name esxserv1_SVC on the Storwize family storage:


HOST_NAME_MAPPING esxserv1.domain.com:esxserv1_SVC

Restriction: For DS8000® systems, do not use the HOST_NAME_MAPPING parameter as an internal mapping to PREASSIGNED_VOLUMES[...] is assigned for all ESX hosts.


Installing and upgrading > VMware vCenter Server user privilege requirements
Additions to Table 1. Privileges that are required for the role assigned to the Tivoli Storage FlashCopy Manager for VMware user ID


vCenter Server objects
Associated privileges that are required
Virtual machine > ConfigurationAdd existing disk, Add new disk, Add or remove device, Advanced, Change CPU count, Change resource, Disk change tracking, Disk Lease, Host USB device, Memory, Modify device setting, Raw device, Reload from path, Remove disk, Rename, Reset guest information, Settings, Swap file placement, Upgrade virtual machine compatibility
Virtual machine > InteractionAnswer question, Back up operation on virtual machine, Power off, Power on, Reset, Suspend
Virtual machine > InventoryCreate new, Register, Remove, Unregister
Virtual machine > ProvisioningAllow disk access, Allow read-only disk access, Allow virtual machine download, Allow virtual machine files upload
Virtual machine > Snapshot management Create snapshot, Remove snapshot, Revert to snapshot


The following information is an addition to the content published for IBM Tivoli Storage FlashCopy Manager for VMware Version 4.1.2, Installation and User's Guide.
This information is available online at
http://www.ibm.com/support/knowledgecenter/SS36V9_4.1.2/com.ibm.itsm.fcm.vm.doc/t_protect_fcmvmw.html

Section: Configuration files > VMware section
The storage subsystem host name definition for IBM® System Storage® N series and NetApp storage systems is updated.

HOST_NAME_MAPPING parameter

Represents how an ESX server host name in the vSphere environment is mapped to a host name on the storage subsystem.
Use the following format when you specify a value for this parameter:

ESX host name:storage subsystem host name [USE_FOR device class names]

Where:
ESX host name
The ESX host name that is specified on the vCenter Server.

storage subsystem host name
The storage system host name that is specified on the storage system.

Depending on the storage system and configuration, it might be necessary to use one of the following values:

  • For IBM® System Storage® N series and NetApp storage systems that are accessed by using network-attached storage (NAS), specify the IP address of the ESX hosts VMkernel port for NFS traffic.

Updates for Tivoli Storage FlashCopy Manager for VMware GUI online help

The task "Backing up VM data with Tivoli Storage FlashCopy Manager (Step 8d)" requires the following update:

In the Date and time of the last backup field, specify when you want to stop the schedule from running. If you do not specify the date and time of the last backup, the schedule creation cannot continue.

Note: This step is not optional. A date and time must be specified (as correctly documented in the hover help).

Updates for Tivoli Storage FlashCopy Manager for Windows V4.1


(Version 4.1.4.2) Features to support Microsoft Exchange 2016 added


With IBM Tivoli Storage FlashCopy Manager: Data Protection for Microsoft Exchange Server 4.1.4.2, features that support Microsoft Exchange 2016 have been added to enable you to protect and manage your Microsoft Exchange 2016 environment.

For information about the new features, see http://www.ibm.com/support/docview.wss?uid=swg27047624

-----------------------------------------------------------------------------------------------------------------------



(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.

-----------------------------------------------------------------------------------------------------------------------

If you apply IBM Tivoli Storage FlashCopy Manager for Windows V4.1.0.2, the following topic is added to the Tivoli Storage FlashCopy Manager V4.1.0 -> IBM Tivoli Storage FlashCopy Manager for Windows -> Configuring section. This information is available online at
http://www.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.win.doc/t_configuring_fcmw.html

Configuration and options files in non-default locations (IC98441)
The Tivoli Storage FlashCopy Manager software uses default configuration and options files. If you want to use non-default configuration and options files, use command line parameters when starting Microsoft Management Console (MMC) graphical user interface to specify alternate configuration and option files when you start Tivoli Storage FlashCopy Manager.

The MMC graphical user interface used for Tivoli Storage FlashCopy Manager software is started with the flashcopymanager.exe file. The flashcopymanager.exe file accepts the following parameters:
    /mscFilename=filename # Name of the MMC snap-in control file
    /author # Opens the MMC console in author mode

For example:
    flashcopymanager.exe parameter1=filename parameter2=filename ...

The flashcopymanager.exe file accepts the following parameters to set the configuration files:
    /FSCONFigfile=filename # File system configuration file
    /SQLCONFigfile=filename # SQL configuration file
    /EXCCONFigfile=filename # Exchange configuration file
    /FSOPTfile=filename # File system OPT file
    /SQLOPTfile=filename # SQL OPT file
    /EXCOPTfile=filename # Exchange OPT file
    /FCMCUSTConfigfile=filename # Custom configuration file
    /SQLINSTancenames=Instance1,Instance2,... # SQL instances to show in the MMC

The following example shows you how to start the MMC with the parameters using flashcopymanager.exe :
    flashcopymanager.exe /FSCONFigfile=newcfg.xml /SQLCONFigfile=altsql.cfg
    /SQLINSTancenames=mysql1,mysql2

You can also start and run multiple instances of the MMC concurrently. With the aforementioned command line parameters, each instance operates using a different configuration based on the configuration and option files specified. The information is this section does not apply when managing remote Tivoli Storage FlashCopy Manager installations.

---------------------------------------------------------------------------------------------------------------------------
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.

Addition to the "Protecting Exchange data" section:
    Restoring an Exchange Server mailbox

    To restore mail to a Unicode PST file, the user credentials used to log on to Tivoli Storage FlashCopy Manager must have the Microsoft Exchange Server Mailbox Import Export management role. By default, users in the Exchange Organization Management role group do not have this Mailbox Import Export management role.

    You can add the Mailbox Import Export management role for the Exchange user by entering the following Exchange PowerShell cmdlet:

    New-ManagementroleAssignment -Role "mailbox Import Export" -User "DOMAIN\USER"

Addition 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.

Addition to the "Protecting SQL data" section:
    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.

Replace the following topic -> 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 vital to operations correctly completing and Tivoli Storage FlashCopy Manager has no mechanism to rebuild them. Do not manually delete these folders.

As a best practice, regularly back up these folders. If the folders become damaged and unusable, restore the latest copy. When the TargetSetsState has a mapping entry, the reconciliation process can detect the inconsistency between TargetSetsState and metadata that is stored on the Tivoli Storage Manager server, and synchronize. For example, if there is an orphan VSSDC_xx value in the Tivoli Storage Manager server and the value does not exist in TargetSetsState, reconciliation deletes the orphan metadata from the Tivoli Storage Manager server.

with this topic -> 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.

For more information about Tivoli Storage FlashCopy Manager for Windows, see http://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.win.doc/t_protect_fcmw.html.

Addition to the Reference information -> Commands for SQL Server -> Backup command -> Backup syntax

The syntax diagram should include /OFFLOAD as an optional parameter.

Addition to the Reference information -> Commands for SQL Server -> Backup command -> Backup optional parameters

The section should include the following description:
    /OFFLOAD
    Specify this option if, after the VSS snapshot is complete, you want to offload the transfer of the data from the Tivoli Storage Manager server to the system specified by the REMOTEDSMAGENTNODE parameter. This option is only valid when the BACKUPDESTination parameter is set to either TSM or BOTH. The default is to not offload data.
Correction to the "Query managedcapacity command" topic:

Query managedcapacity command

Change '/Details' to '/Detailed'. For example: fcmcli query managedcapacity /detailed 

-----------------------------------------------------------------------------------------------------------------------
The following information is an addition to the content published for IBM Tivoli Storage FlashCopy Manager for Windows Version 4.1, 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

-----------------------------------------------------------------------------------------------------------------------
Addition to the Reference information -> Commands for Exchange Server -> Restoremailbox command -> Restoremailbox syntax

The syntax diagram should include the following parameters as optional parameters:
  • /CLIENTACcessserver
  • /MAILBOXRestoreunread
  • /Quiet
  • /TEMPMAILBOXAlias
The syntax diagram should exclude the /MOUNTWait parameter as an optional parameter.

Addition to the Reference information -> Commands for Exchange Server -> Restoremailbox command -> optional parameters

The section should exclude the /MOUNTWait parameter as an optional parameter, and include the following descriptions:
/CLIENTACcessserver

Use the /CLIENTACcessserver parameter to specify the name of the Client Access Server (CAS) that you want to use. This parameter is available only if you use Microsoft Exchange 2010 or later versions.
By default, Tivoli Storage FlashCopy Manager uses the local server as the CAS if the CAS role is installed on the local server. If the CAS role is not installed on the local server, Tivoli Storage FlashCopy Manager uses the mailbox database that the user is logged into.
To determine the name of the CAS in use, run this Exchange Management Shell command:
Get-MailboxDatabase -Identity <logon user mailbox database> | select RpcClientAccessServer
You can also specify a different CAS.

/MAILBOXRestoreunread
Use the /MAILBOXRestoreunread parameter to specify whether Data Protection for Microsoft Exchange marks restored mail messages as unread.
You can specify the following values:
Yes
Mark restored mail messages as unread. This option is the default.
No
Do not mark restored mail messages as unread.

/Quiet
This parameter prevents the display of status information but does not affect the level of information that is written to the activity log.

-----------------------------------------------------------------------------------------------------------------------
Correction to the command-line interface help display for the restoremailbox command

When you enter this command on the command-line interface, tdpexcc help restoremailbox, the following command output is displayed.

TDPEXCC RESTOREMailbox mailbox-name[,mailbox-name2,mailbox-name3,...]
where mailbox-name can be:
an alias or display name
[/CLIENTACcessserver=client-access-server-name]
(default: local Client Access Server)
[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)
[/DAGNODe=nodename]
[/FCMOPTFile=dsm.opt|filename] (default: dsm.opt)
[/KEEPRdb=Yes|No] (default: No)
[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)
[/LOGPrune=60|n|No] (default: 60)
[/MAILBOXFilter=filter-name,filter-criteria[,filter-time-criteria]]
where filtername can be:
ATTACHMENTNAME|ENDDATETIME|FOLDER|MESSAGEBODY|
SENDER|STARTDATETIME|SUBJECT|ALLCONTENT
[/MAILBOXOriglocation=server-name,db-name]
[/MAILBOXRESTOREDAte=date-stamp]
[/MAILBOXRESTOREDESTination=dest[,dest-parms]]
where dest can be:
EXCHANGE|PST|UNICODEPST
[/MAILBOXRESTORETIme=time-stamp]
[/MAILBOXRestoreunread=Yes|No] (default: Yes)
[/Quiet]
[/TEMPLOGRESTorepath=pathname] (default: TEMP environment var)
[/TEMPMAILBOXAlias=alias] (default: mailbox alias of the current admin user)
[/TEMPDBRESTorepath=pathname] (default: TEMP environment var)
[/USEExistingrdb=Yes|No] (default: Yes)

------------------------------------------------------------------------------------------------------------------------------------------
(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 legacy 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)

------------------------------------------------------------------------------------------------------------------------------------------
(IT03539) "ANS1025E (RC137) Authentication failure" received when PASSWORDAccess set to prompt

For this documentation update, the following note belongs in the locations identified under "Knowledge Center", and "Installation and User's Guide".

Add the the following text at the end of step 4c:

Note: If you configure DSM Agent node (the backup-archive client node) manually, make sure that PASSWORDAccess option in dsm.opt file for Tivoli Storage Manager backup-archive client is set to generate and stored password for DSMAGENT Node is valid.

You can manage the password as stored in the registry by using a utility program named dsmcutil.exe. This utility program is distributed with the Tivoli Storage Manager backup-archive client package. For more information about using the dsmcutil program, see the dsmcutil.hlp file or the dsmcutil.txt file that are distributed with the Tivoli Storage Manager backup-archive client package.

Knowledge Center
4.1.0 -> Tivoli Storage FlashCopy Manager for Windows > Configuring > Configuring for the TSM Configuration option -> https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.win.doc/t_fcm_config_tsmsupport.html
4.1.1 -> Tivoli Storage FlashCopy Manager for Windows > Configuring > Configuring for the TSM Configuration option -> https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.1/com.ibm.itsm.fcm.win.doc/t_fcm_config_tsmsupport.html

Installation and User's Guide
4.1.0 -> Chapter 4. Configuring ->Configuring for the TSM Configuration option
https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.0/com.ibm.itsm.fcm.win.doc/b_fcm_win_guide.pdf

4.1.1 -> Chapter 4. Configuring ->Configuring for the TSM Configuration option

PDF files in English for Tivoli Storage Manager V7.1.1 and Tivoli Storage FlashCopy Manager V4.1.1 products are available only in the V7.1.1_V4.1.1_ compressed file .

To access IBM FlashCopy Manager Installation and User's Guide for Windows version 4.1.1, open the V7.1.1_V4.1.1_ compressed file and choose guide b_fcm_win_guide.pdf.

------------------------------------------------------------------------------------------------------------------------------------------
Clarification to the Configuring a Tivoli Storage FlashCopy Manager for SQL Server stand-alone configuration in a SQL Failover Cluster environment with shared disks or cluster shared volumes topic

Step 4 of the procedure in this topic requires this clarification:
    If this node is the first cluster node that you are configuring, open the Microsoft Failover Cluster Manager. Go to the cluster resource group that you are configuring. Right-click the resource group and select Add a resource > Generic Service. From the New Resource Wizard dialog that is displayed, select the CAD service that is named, by default, TSM Client Acceptor,and complete the wizard configuration. From the Failover Cluster Manager, bring the TSM Client Acceptorservice resource online. If you are repeating this procedure for another cluster node, the TSM Client Acceptorservice resource is already configured. In this scenario, go to the resource group and open the service resource online.
    Tip: Ensure that the CAD service name is the same on all cluster nodes so that it can be started by a generic cluster service.

This information is additional to the following topics, and will be incorporated in the next revision of the Tivoli Storage FlashCopy Manager for Windows: Installation and User's Guide (PDF and Knowledge Center publications).

v4.1.1
http://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.1/com.ibm.itsm.fcm.win.doc/t_fcm_config_cluster_fcm_standalone.html

v4.1.2
http://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.2/com.ibm.itsm.fcm.win.doc/t_fcm_config_cluster_fcm_standalone.html

------------------------------------------------------------------------------------------------------------------------------------------
(v4.1.2 only) Clarification regarding backup and restore operations on archive mailboxes

If you enable a user mailbox to be archived, ensure that the user is logged on to that mailbox at least once before you complete a backup and restore operation on the mailbox.

This information is additional to the following topics, and will be incorporated in the next revision of the Tivoli Storage FlashCopy Manager for Windows: Installation and User's Guide (PDF and Knowledge Center publications).

- Protecting data ->Protecting Exchange Server data -> Restoring mailbox data
https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.2/com.ibm.itsm.fcm.win.doc/t_fcm_exc_gui_res_mailbox2007.html?lang=en

- Reference information -> Commands for Exchange Server -> Restoremailbox command
https://www.ibm.com/support/knowledgecenter/SS36V9_4.1.2/com.ibm.itsm.fcm.win.doc/r_fcm_exc_cmd_restoremailbox.html

------------------------------------------------------------------------------------------------------------------------------------------
(v4.1.2 only) Tivoli Storage FlashCopy Manager for Windows > Protection of Microsoft Exchange Server data hosted in VMware environments > Installing and configuring for Microsoft Exchange Server data protection in a VMware environment > Configuring Data Protection for Microsoft Exchange Server

Update starting with step 4 through the end of the topic. Correction to step 4 through the end of the topic is provided here:

4. Configure Data Protection for Microsoft Exchange Server using the Tivoli Storage Manager configuration wizard. When you navigate to the Tivoli Storage Manager Node Names page of the wizard, enter the datacenter node name, Exchange node name, and VSS requestor node name. If the datacenter node name field is disabled, the Data Protection for VMware recovery agent is not installed correctly.

5. After Data Protection for Microsoft Exchange Server is configured, verify that the Configuring Recovery Agent rule status indicates Passed. Configure Recovery agent CLI to work Recovery agent on your vm:

a. Open Recovery Agent CLI:Start->Tivoli Storage Manager->Tivoli Storage For Virtual Environments->Recovery Agent CLI b. Run the following command: RecoveryAgentShell.exe -c set_connection mount_computer vm_name

Sample: RecoveryAgent\shell>RecoveryAgentShell.exe -c set_connection mount_computer vm_exc10

6. Log on to one of the data mover instances and complete the following steps. Do not repeat these steps for all data mover instances.


    a. For backup-archive client that has been configured as the VSS requestor node on TDP for Exchange, give access to the virtual machine backups using the backup-archive client command-line interface command 'set access'. This step is required because the VSS requestor node acts on behalf of Data Protection for Microsoft Exchange Server node, when it accesses vm backups.

    This command is run directly from one of the data mover nodes (datamover10 and datamover20). Create a temporary options file dsm.setaccess.opt from dsm.opt and run 'set access' command using the following steps:


      1) Copy the dsm.opt file to the dsm.setaccess.opt file.

      2) Edit the dsm.setaccess.opt file. For any line that contains ASNODE, delete the line.

      3) Edit the dsm.setaccess.opt file to set the NODENAME to your data center node name NODENAME datacenter_node

      Sample: NODENAME datacenter10


    b. Run 'set access' command:

    dsmc set access backup -type=VM vm_name vss_requestor_node -optfile=dsm.setaccess.opt

    Sample: dsmc set access backup –type=VM vm_exc10 EXC10_VSS –optfile=dsm.setaccess.opt

    ANS1148I “Set Access” command successfully completed.

    c. Run 'query access' command to verify that VSS requestor node obtained access to VM backups:


    dsmc query access -optfile=dsm.setaccess.opt

    Node name: datacenter10
    Type Node User Path
    -------------------------------------------------------

    Backup EXC10_VSS * \VMFULL-vm_exc10\*\*

    ANS1148I “Query Access” command completed successfully

    If the datacenter node name password is unknown, the Tivoli Storage Manager server administrator has to reset the password to run the set access command.


------------------------------------------------------------------------------------------------------------------------------------------
(v4.1.2 only) Clarification to the Tivoli Storage FlashCopy Manager for Windows > Protection of Microsoft Exchange Server data hosted in VMware environments > Backup management > Verifying backups topic

For individual mailbox restore and database restore, VMVSS restore is not supported if database path changed after the virtual machine backup was taken. Old virtual machine backups can not be used to restore the moved database.

This same limitation should be remembered when you read the Restoring and recovering data > Recovering data by using the command-line interface topic.

------------------------------------------------------------------------------------------------------------------------------------------
(v4.1.2 only) Clarification to the Tivoli Storage FlashCopy Manager for Windows > Planning > Protection of Microsoft Exchange Server data>Mailbox restore guidelines topic

The options TEMPLOGRestorepath and TEMPDBRestorepath are not supported with individual mailbox restore from a virtual machine backup.

Remove these options from the TDP configuration file to ensure successful individual mailbox restore from a virtual machine backup.

To override the default TSMRDB location for recovery from VMVSS backups, use Windows System environment variable TSMMOUNT instead of TEMPLOGRestorepath and TEMPDBRestorepath.

Recycle the virtual machine after setting the TSMMOUNT variable. Recycling the virtual machine gives the 'Remote Client Agent' service access to this environment variable.

Example:
TSMMOUNT=C:\MyCustomVMMountPoint

Note that there is no no trailing directory separator.

The virtual machine volume is mounted and the TSMRDB is created at the location specified by TSMMOUNT. The
TEMPLOGRestorepath and TEMPDBRestorepath options cannot coexist with TSMMOUNT.

This information is also applicable when you reference the following commands ->
Tivoli Storage FlashCopy Manager for Windows > Reference information > Commands for Exchange Server >
  • Restore
  • Restoremailbox
  • Set
------------------------------------------------------------------------------------------------------------------------------------------
Addition of -/BACKUPTAILLOG- optional parameter to Backup command syntax

In the Commands for SQL Server > Backup command section of the Tivoli Storage FlashCopy Manager for Windows book, the -/BACKUPTAILLOG- optional parameter is added to the Backup command line syntax.

The following IBM Knowledge Center topic was updated:

Backup syntax: https://www-01.ibm.com/support/knowledgecenter/SS36V9_4.1.4/fcm.win/r_fcm_sql_cmd_backupsyn.html?lang=en

------------------------------------------------------------------------------------------------------------------------------------------
Update to syntax diagrams of the Update Configand Setcommands for Capacity Licensing positional parameters

Two new positional parameters, CAPACITYINFOINTerval and CAPACITYINFOLOCation, enable you to generate capacity licensing reports.

The syntax for these parameters should be written as follows:

>--+---------------------------------+-------------------------->
'-CAPACITYINFOINTerval=--numdays-'

>--+----------------------------------+------------------------><
'-CAPACITYINFOLOCation=--pathname-'

Note: There is no leading “/” in the syntax, for example, as in the following: '-/CAPACITYINFOINTerval=--numdays-'

The syntax diagrams of the following commands include these new parameters:

SQL Server:
Reference information for IBM® Tivoli® Storage FlashCopy® Manager > Commands for SQL Server > Set command

Exchange Server:
Reference information for IBM® Tivoli® Storage FlashCopy® Manager > Commands for Exchange Server > Set command

Custom applications and file systems:
Reference information for IBM® Tivoli® Storage FlashCopy® Manager > Commands for custom applications and file systems > Update config command

------------------------------------------------------------------------------------------------------------------------------------------
(IT11348) Database and mailbox names with commas are not supported

The comma (,) character has special meaning to IBM Spectrum Protect™ Snapshot for Microsoft Exchange and IBM Spectrum Protect™ Snapshot for Microsoft SQL and causes the following naming limitations:

1. Mailbox Display Names that contain commas cannot be used as mailbox names in the 'restoremailbox' command.
2. Database names that contain commas are not supported.
The following statements have been updated in the documentation:
BEFORE:
If any < database, mailbox, ...> name contains commas or blanks, enclose the < database, mailbox, ...> name in double
quotation marks.

AFTER:
If any < database, mailbox, ...> name contains blanks, enclose the < database, mailbox, ...> name in double quotation
marks.

The amended information is published with the Tivoli Storage FlashCopy Manager for Windows 4.1.4 documentation.

https://www.ibm.com/support/knowledgecenter/en/SS36V9_4.1.4/fcm.common/welcome.html

------------------------------------------------------------------------------------------------------------------------------------------
(IT12760) Parameter limitations in the Restorefiles commands for Data Protection for both Microsoft Exchange and Microsoft SQL

Data Protection Microsoft Exchange - The /INTO parameter in the Restorefiles command is limited to local disks
The IBM Tivoli Storage FlashCopy Manager: Data Protection for Microsoft Exchange Server 4.1.0 documentation includes topics entitled: Restorefiles command and Restorefiles optional parameters, which contain details on the /INTO parameter. However, the details do not highlight that the /INTO parameter is limited to local disks.

In addition to the IBM Tivoli Storage FlashCopy Manager: Data Protection for Microsoft Exchange Server 4.1.0 documentation, the documentation for 4.1.x also omits this parameter information.

The complete information will be published in the next release of the documentation in the topics entitled: Restorefiles command and Restorefiles optional parameters.

Data Protection Microsoft SQL - The /RELOCATEDir parameter in the Restorefiles command cannot use a mapped network drive as a destination directory
The IBM Tivoli Storage FlashCopy Manager: Data Protection for Microsoft SQL Server 4.1.0 documentation includes topics entitled: Restorefiles command and Restorefiles optional parameters, which contain details on the /RELOCATEDir parameter. However, the details do not highlight that the /RELOCATEDir parameter cannot use a mapped network drive as a destination directory.

In addition to the IBM Tivoli Storage FlashCopy Manager: Data Protection for Microsoft SQL Server 4.1.0 documentation, the documentation for 4.1.x also omits this parameter information.

The complete information will be published in the next release of the documentation in the topics entitled: Restorefiles command and Restorefiles optional parameters.

------------------------------------------------------------------------------------------------------------------------------------------


(IT18215) Clarification of local and remote DSMAGENT node requirements when running offloaded backups to Tivoli Storage Manager

When you run offloaded backups to Tivoli Storage Manager, for each FlashCopy Manager instance, each local DSMAGENT node must have a dedicated remote DSMAGENT node.

The following topics in the Tivoli Storage FlashCopy Manager for Windows book are updated with this information and these updates will be published in release V8.1.0.
  • Specifying Configuration Parameters for Spectrum Protect
  • Required node names for basic VSS Offloaded backup
  • VSS Options

-----------------------------------------------------------------------------------------------------------------------------------------


/SQLSERVer optional parameter - clarifications on port value and variable description

· Default port value for TCP protocols used with /SQLSERVer parameter

If you choose to use a TCP protocol when specifying the /SQLSERVer parameter (to establish communication with SQL Server instances), you have the option of defining a port. If you choose not to specify a port value, a default value is used. The default port value is 1433.


· /SQLSERVer parameter variable

The variable description for the /SQLSERVer parameter has been updated to "sqlserver-connection" because the format of the SQL Server connection differs depending on the communication protocol that is configured for the SQL Server instance. For example, a port is not relevant for all communication protocols.

Example:

Communication ProtocolExample Usage
lpc/sqlserver=lpc:<servername>\<instancename>
np /sqlserver=np:<servername>\pipe
tcp /sqlserver=[tcp:]<servername>[\<instancename>][,port]

Updated variable description:

BeforeAfter
/SQLSERVer=sqlprotocol:sqlservername/SQLSERVer=sqlserver-connection

These updates will be published with the next version of IBM Spectrum Protect Snapshot for Windows documentation and will be added to the /SQLSERVer parameter information in the following topics.
  • Reference information > Commands for SQL Server > Backup command > Backup optional parameters
  • Reference information > Commands for SQL Server > Query SQL command > Query SQL optional parameters
  • Reference information > Commands for SQL Server > Restore command > Restore optional parameters

-----------------------------------------------------------------------------------------------------------------------------------------
(IT19728) Clarification on communication between applications and SQL Servers in an AlwaysOn Availability Group (AAG) cluster

With Microsoft SQL Server 2012, Microsoft implemented the use of AlwaysOn Availability Group (AAG) listeners to enable applications to connect to an AAG instance using the listener name (or listener name and port number).

However, Microsoft does not support this feature for 3rd party backup applications, such as IBM Spectrum Protect Snapshot. Instead, for backup and restore operations, 3rd party backup applications must use the SQL Server instance name (or instance name and port number) and not the AAG listener to communicate with the server instance.

Example:

· Local Instance name = MySQLServer\SQLInstance1


· Local Instance port = 1600

In this example, to communicate with the SQL server, you specify the following values for the \SQLSERVer option.

/SQLSERVer=MySQLServer\SQLInstance1,1600

This clarification will be published with the next version of IBM Spectrum Protect Snapshot for Windows documentation.

[{"Product":{"code":"SSERFV","label":"IBM Spectrum Protect Snapshot"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF010","label":"HP-UX"}],"Version":"4.1.3;4.1.4;4.1.6","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
17 June 2018

UID

swg27039330