Updates for IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide V6.2

Product documentation


Abstract

This document contains updates for "IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide V6.2". These updates are not yet published in the IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter/SSGSG7_6.2.0/com.ibm.itsm.ic.doc/welcome.html)

Content

Tivoli Storage Manager client documentation updates

Corrections for Version 6.2.5

Per APAR IC94432
Backup-archive client options and commands > Processing options > Client options reference->DOMAIN.VMFULL and DOMAIN.VMFILE

The value that you specify for the vmhost parameters on these options must match the host name, as it is displayed in the vCenter server, in the Hosts and Clusters view.

The new descriptions read as follows:

Description for DOMAIN.VMFULL

vmhost=hostname
Process all virtual machines that are defined to the Virtual Center or to the ESX server that is specified on the vmchost option. The host name that you specify must match the fully qualified host name or IP address, as it is displayed in the vCenter server in the "Host and Clusters" view.

All virtual machines that are added to this host are automatically included in backup and restore processing.

This parameter can include multiple ESX servers that are separated by commas. When the Virtual Center contains multiple ESX servers, this option does not determine the ESX server from which a snapshot is taken. The ESX server from which a snapshot is taken is determined by the VMware VirtualCenter web service.

When you connect directly to an ESXi or ESX host, the vmchost option applies only if the vmhost is the server that you connect to. If it is not, a warning level message is issued to the console and is recorded in the client dsmerror.log; it is also recorded as a server event message.

If the vmenabletemplatebackups option is set to yes, and VM templates are part of the domain, they are included in the backup.

Restriction: VMware templates for virtual machines cannot be backed up when they are in an ESX or ESXi host because ESX and ESXi hosts do not support templates.


Description for DOMAIN.VMFILE

vmhost=hostname
Process all virtual machines that are defined to the Virtual Center or to the ESX server that is specified on the vmchost option. The host name that you specify must match the fully qualified host name or IP address, as it is displayed in the vCenter server in the "Host and Clusters" view.

All newly added to this host are automatically included in backup and restore processing. To be included, the virtual machines must also be running on the ESX server that is specified by the host name.

This parameter can include multiple ESX servers separated by commas. When the Virtual Center contains multiple ESX servers, this option does not determine the ESX server from which a snapshot is taken. The ESX server from which a snapshot is taken is determined by the VMware VirtualCenter web service.

When you connect directly to an ESXi or ESX host, the vmhost keyword applies only if the vmhost is the ESXi you connect to. If it is not, a warning level message is issued to the console and is recorded in the client dsmerror.log file; it is also recorded as a server event message.


Corrections for Version 6.2.4

Per APAR IC79447
Chapter 12: Postschedulecmd/Postnschedulecmd
The list of notes near the beginning of this topic needs additional information. Note 3 (below) needs to be added.

Note:

  1. If the postschedulecmd command does not complete with return code 0, the client reports that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). If you do not want the postschedulecmd command to be governed by this rule, you can create a script or batch file that invokes the command and exits with return code 0. Then configure postschedulecmd to invoke the script or batch file. The return code for the postnschedulecmd command is not tracked, and does not influence the return code of the scheduled event.
  2. The server can also define the postschedulecmd option (and the postnschedulecmd option).
  3. If the scheduler action couldn't start and PRESCHEDULECMD has run with RC=0, the command specified by the POSTSCHEDULECMD option is run.

Corrections for Version 6.2.2

Per APAR IC79126
Installing the Tivoli Storage Manager backup-archive clients (UNIX, Linux, and Windows) > Installing the Tivoli Storage Manager Windows client>Upgrading, modifying, reinstalling, or uninstalling the Tivoli Storage Manager Windows client

This topic has been updated to include a link to a Wiki site that contains an article that explains how to remove the client from a Windows system if you do not intend to use Tivoli® Storage Manager on a Windows computer in the future. The list of stoppable services has also been revised to include the service display names, and not the executable file names. The new topic is as follows:

Windows operating systems
Upgrading, modifying, reinstalling, or uninstalling the Tivoli Storage Manager Windows client

The Windows Backup-Archive Client can be upgraded, modified, reinstalled, or uninstalled.

Note: Using the Windows Control Panel option to uninstall the client (see step 3) removes the client software but does not remove client services, log files, and other items created outside of the software installation process. This is not an issue if you intend to reinstall the client at a later date. However, if you do not intend to use Tivoli® Storage Manager on a Windows computer in the future, see the following article for instructions to thoroughly remove the client and related files and settings:
https://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/How+to+completely+remove+the+Backup-Archive+client+from+Microsoft+Windows

If you have previously installed the client and you want to reinstall it into a different directory, uninstall the older client files before you install the new client files.

Wait for any in-process Backup-Archive Client tasks to complete before you uninstall or modify the backup-archive Windows client.

Stop any running services before reinstalling or modifying the client. Use the Windows control panel or service manager commands to display the services that are running. Stop the services shown in Table 1 using either the control panel or a command prompt window.


Table 1. Stoppable services

Control panel display name
Command line procedure
TSM Journal Service net stop "tsm journal service"
TSM Client Acceptor net stop "tsm client acceptor"
TSM Client Scheduler net stop "tsm client scheduler"
TSM Remote Client Agent net stop "tsm remote client agent"

To remove any of these services without uninstalling the client, use the Help me configure options in Utilities > Setup wizard in the GUI (dsm.exe). You can also use the setup wizard to remove configuration information for online image support and open file support.

The following files are not overwritten if you upgrade or reinstall a client by installing it into the same directory used by the previous installation:

  • dsm.opt
  • dsmerror.log
  • dsmsched.log
  • dsmwebcl.log
The configuration settings from the previous version, are in the dsm.opt file, and are preserved for use with the new client software.

During a reinstallation, you are prompted to see if you want the installer to overwrite existing exe, ini, mst, dll, xml, and .properties files. Select Yes to all to overwrite these existing files to ensure that you have the current libraries and initialization files.

Follow these steps to uninstall or modify the IBM® Tivoli Storage Manager Backup-Archive Client:
1. Open the control panel feature used to add, modify, or remove programs. Click Start > Control Panel > Programs and Features.
2. Select the IBM Tivoli Storage Manager client from the list of installed programs.
3. To uninstall an existing client, click Uninstall.
4. To fix missing or corrupted files, shortcuts, and registry entries, select the Repair option.
5. To remove individual components, select Change and then click Next. Next to the installable features that you want to uninstall, select This feature will not be available
6. Complete and close the setup wizard.
7. Reboot the computer if you are prompted to do so. Rebooting removes locked files that must be removed before you upgrade or reinstall the client. Rebooting also updates locked files that must be preserved and reused when you reinstall or upgrade the client.


Per APAR IC76747
Back up and restore data with backup-archive clients > Restoring your data>
Recovering a computer when the operating system is not working (Windows Vista, Windows 7, and Windows Server 2008)

The documentation has been rewritten, corrected, expanded, and moved from the product manuals to the IBM Tivoli Storage Manager Wiki.
The updated documentation can be found at the following URL: https://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/
Best+Practices+for+Recovering+Windows+Server+2008%2C+Windows+Server+2008+R2%2C+Windows+7%2C+and+Windows+Vista


Per APAR IC79757
Backing up your data > Back up NAS file systems using Network Data Management Protocol>Methods for backing up and recovering data on NAS file servers when using CIFS

A new bullet item has been added the paragraphs that begin with "These are some limitations of NAS file server data when using CIFS:" The new bullet text is as follows:

  • File and directory security information might be inaccessible when the Windows account performing the backup is not a member of the Domain Administrators group of the domain the NAS file server is a trusted member of. It is also possible that these security access failures might prevent the entire file or directory from being backed up.

Per APAR IC76774
Reference >Backup-archive client options and commands>Backup VM command
Attention: Tivoli Storage Manager Backup-Archive Client cannot back up vCenter virtual machine templates. Also, virtual machines that are deployed as vApps are not included in full VM backups.

Per APAR IC74769:
Automated System Recovery (ASR) is not supported on 64-bit architectures running Extensible Firmware Interface (EFI) on Windows Vista, Windows 7, Windows Server 2008. When you back up and recover system state for these computers, you do not back up and recover ASR data.


Per APAR IC75909:
Restoring your data > Restoring data from a VMware backup > Restoring file-level VM backups

The steps for restoring a file-level backup to a VMware guest is modified as follows:

1. From the off-host backup server, query the Tivoli Storage Manager server for available backups by entering the following command:
dsmc q   MyFilePath -asnode= myVMName  
where MyFilePath is the location of the backups.
2. Restore the full VMware backup that was listed in step 1 by entering one of the following commands:
  • If you are restoring with a backup-archive client on the VMware guest from which the file was backed up, a file on a Tivoli Storage Manager client that is installed on a VMware guest , enter the following command:
dsmc restore myFileName
  • If you are restoring with a backup-archive client on the off-host backup server (the backup proxy server), you can restore the file to off-host backup server, then copy the file to the VMware guest. To restore the file to the off-host backup server, a file from the off-host backup server onto the VMware guest , enter the following command:
dsmc restore myFileName   fileLocation  -asnode= myVMName  

See the following parameters for the values that are specific to your environment:
myFileName
Specifies the path and file name in storage that you want to restore. Use wildcard characters to specify a group of files or all the files in a directory.
fileLocation
Specifies the path and file name where the file is stored on the off-host backup server.
myVMName
Specifies the Tivoli Storage Manager node name of the VMware guest from which the file was backed up. The off-host backup server restores the file to the off-host backup server as a proxy for the VMware guest node. that you are restoring the file to.




Per APAR IC75866:
Processing options > Using commands > Restore VM

The following example is added to command restore vm:

    Task:
    Restore the most recent backup version of myvm. Restore to a datacenter mydatacenter. The datacenter is within the vCenter; the relative path within the vCenter is dirA/datacenters/.

    Command: dsmc restore vm myvm -vmname="Test Machine" -datacenter="dirA/datacenters/myDatacenter" -host="myHostName" -datastore="myDatastore"



Corrections for Version 6.2.0 (applies to all modifications of version 6.2)

Global changes (changes that affect several topics in one or more sections of the publication)

Per APAR IC90806, remove all references to Network File System (NFS). NFS is not valid in Windows environments.

Installing

Per APAR IC79546

Chapter 1: Installing Tivoli Storage Manager clients
>Automatic client deployment

Customers running Tivoli Data Protection for Enterprise Resource Planning applications should not schedule automatic deployments of the backup archive client.

Text has been added to the topic entitled Automatic client deployment to explain why this is. The new text reads as follows:


    The Tivoli® Storage Manager server administrator can automatically deploy a Backup-Archive Client to workstations that already have the Backup-Archive Client installed.

    When you schedule automatic Backup-Archive client deployments, the updated client packages (which include the client components and the API library) are installed on the workstations that receive them. A dependency check is performed by the client installation program to ensure that the API library does not conflict with the client package that is currently installed.

    Tivoli Data Protection for Enterprise Resource Planning applications do not use the same installation technology that is used by the client installation program. Because of that, the client installation dependency check is not able to detect whether the API library that is being used by the Tivoli Data Protection for Enterprise Resource Planning applications are compatible with the API library that will be installed by automatic client deployments. If a client package is automatically deployed to and installed on a workstation, the API library that is installed might not be compatible with the API library that was installed by the Tivoli Data Protection for Enterprise Resource Planning application. The newly deployed API library can cause the Tivoli Data Protection for Enterprise Resource Planning applications to fail.

    Do not schedule automatic client deployments to workstations that have a Tivoli Data Protection for Enterprise Resource Planning application installed on them.

Per APAR IC68224:
Chapter 1. Installing the Tivoli Storage Manager clients
Topic: Client environment requirements
Subtopic: Windows client environment requirements
Sub-subtopic: Hardware requirements

The section is changed as follows:

Hardware requirements

This section contains client hardware requirements for the supported Windows® platforms.


The client runs on the following computers:

  • An Intel® Pentium® or compatible processor, or multiprocessor based computer
  • An AMD64/EM64T (x64) processor or multiprocessor based computer

The client installation requires 1.5 GB of free disk space and 128 MB of memory.
The client GUI (graphical user interface) and client web GUI require a minimum screen resolution of 600 by 800 pixels.

Section: Installing
Topic: Uninstalling the Tivoli Storage Manager AIX client
Per APAR: IC75638:
The documentation is missing instructions for uninstalling the journal-based backup components. In step 3 of this procedure, note that the journal-based backup feature is comprised of two file sets. Select both tivoli.tsm.client.jbb.xxxx and tivoli.tsm.filepath.rte.xxxx (where xxxx is the version information). If you uninstall the file sets one at a time, uninstall the tivoli.tsm.client.jbb.xxxx file set first.

Section: Installing
Topic: Silent installation
Per APAR IC70021, the installation of language pack files is separate from the installation of the client.
Per APAR IC69920, VMware backup tools can be installed silently.
The topic is updated as follows:

Silent installation on Windows 2003 systems

When you place a customized version of the msiexec command (which invokes the Microsoft® Software Installer) in a script or batch file, you can perform installations on multiple Windows systems. The following is a sample command to install the backup-archive command-line client, GUI client, Web client, API, and Administrative command-line client. You might need to customize this example to run correctly on your system. While the command is physically spread across multiple lines on this page, it is one single command.

msiexec /i "Z:\tsm_images\TSM_BA_Client\IBM Tivoli Storage Manager Client.msi"
RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1
INSTALLDIR="d:\program files\tivoli\tsm"
ADDLOCAL="BackupArchiveGUI,BackupArchiveWeb,ApiRuntime,AdministrativeCmd,LVSA"
TRANSFORMS=1033.mst /qn /l*v "c:\log.txt"

After you install client features, you can install a language pack. You must install client features before you install a language pack. Install a language pack with a command like the following. While the command is physically spread across multiple lines on this page, it is one single command.

msiexec /i
"Z:\tsm_images\TSM_BA_Client\IBM Tivoli Storage Manager Client - French.msi"
RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1
INSTALLDIR="d:\program files\tivoli\tsm"
ADDLOCAL="LanguageFiles" TRANSFORMS=1036.mst /qn /l*v "c:\log.txt"


The command parameters are as follows:
...
(all parameters except ADDLOCAL are omitted)
...

ADDLOCAL="BackupArchiveGUI,BackupArchiveWeb,ApiRuntime,AdministrativeCmd,LVSA,VMwareBackupTools"
Specifies the features to install. Specify all the components on a single line within quotation marks, separated by commas, with no spaces before or after the commas. The backup-archive features are available as shown in the following table:

Windows 32 bit client features Windows 64 bit client features Feature description
BackupArchiveGUI BackupArchiveGUI Graphical user interface
BackupArchiveWeb BackupArchiveWeb Backup-archive Web client
ApiRuntime Api32Runtime
Api64Runtime
API Runtimes
ApiSdk ApiSdk API SDK
AdministrativeCmd AdministrativeCmd Administrative Command Line
LVSA LVSA Online image backup and OFS
VMwareBackupTools VMwareBackupTools VMware backup tools

ADDLOCAL="LanguageFiles"
After you install client features, you can install a language pack. You must install client features before you install a language pack.
Windows 32 bit client features Windows 64 bit client features Feature description
LanguageFiles LanguageFiles Language-specific files

Section: Installing
Topic: Upgrading, modifying, or reinstalling the Tivoli Storage Manager Windows client.
Per APAR: IC75638:

This topic omits the steps necessary to stop Tivoli Storage Manager services before reinstalling or modifying the client. The following text replaces the existing text in this topic:

Upgrading, modifying, reinstalling, or uninstalling the Tivoli Storage Manager Windows client

The Windows Backup-Archive Client can be upgraded, modified, reinstalled, or uninstalled.

If you have previously installed the client and you want to reinstall it into a different directory, uninstall the older client files before you install the new client files.

Wait for any in-process Backup-Archive Client tasks to complete before you uninstall or modify the backup-archive Windows client.

Stop any running services before reinstalling or modifying the client. Use the Windows control panel or service manager commands to display the services that are running. Stop the services shown in Table 1 using either the control panel or a command prompt window.

The stoppable services are listed below, with the Control Panel diplay name and executable file name:
  • TSM Journal Service net stop tsmjbbd.exe
  • TSM Client Acceptor net stop dsmcad.exe
  • TSM Client Scheduler net stop dsmcsvc.exe
  • TSM Remote Client Agent net stop dsmagent.exe

To remove any of these services without uninstalling the client, use the Help me configure options in Utilities > Setup wizard in the GUI (dsm.exe). You can also use the setup wizard to remove configuration information for online image support and open file support.

The following files are not overwritten if you upgrade or reinstall a client by installing it into the same directory used by the previous installation:
  • dsm.opt
  • dsmerror.log
  • dsmsched.log
  • dsmwebcl.log

The configuration settings from the previous version, are in the dsm.opt file, and are preserved for use with the new client software.

During a reinstallation, you are prompted to see if you want the installer to overwrite existing exe, ini, mst, dll, xml, and .properties files. Select Yes to all to overwrite these existing files to ensure that you have the current libraries and initialization files.

Follow these steps to uninstall or modify the IBM Tivoli Storage Manager Backup-Archive Client:
  1. Open the control panel feature used to add, modify, or remove programs. Click Start > Control Panel > Programs and Features.
  2. Select the IBM Tivoli Storage Manager client from the list of installed programs.
  3. To uninstall an existing client, click Uninstall.
  4. To fix missing or corrupted files, shortcuts, and registry entries, select the Repair option.
  5. To remove individual components, select Change and then click Next. Next to the installable features that you want to uninstall, select This feature will not be available
  6. Complete and close the setup wizard.
  7. Reboot the computer if you are prompted to do so. Rebooting removes locked files that must be removed before you upgrade or reinstall the client. Rebooting also updates locked files that must be preserved and reused when you reinstall or upgrade the client.


Configuring


Per APAR IC74987:
Configuring
Section: Getting started
Topic: Backup Operators group operations

Add the following caveat:

On Windows Vista, Windows 7, and Windows 2008, you must be a
member of the Administrators group to back up ASR writer data.


Chapter 2: Configure the Tivoli Storage Manager client > Configure your system for journal-based backup > Configuring the journal engine service

    Per APAR IC85285, a note is added after the second paragraph:

    Configuring the journal engine service

    Journal-based backup can be used for all Windows clients. If you install the journal engine service and it is running, then by default the incremental command automatically performs a journal-based backup on selected file systems that are being monitored by the journal engine service.

    Journal-based backup is enabled by installing and configuring the Tivoli® Storage Manager journal service. The Tivoli Storage Manager journal service can be installed with the GUI Setup wizard or with the dsmcutil command. Basic journal service configuration can be done with the GUI Setup wizard, more advanced configuration can be done by editing the journal service configuration file, tsmjbbd.ini.

    Important: The default location for tsmjbbd.ini is C:\Program Files\Tivoli\TSM\baclient. If this is the first time you are configuring the journal engine service and a copy of tsmjbbd.ini does not already exist, copy the sample file C:\Program Files\Tivoli\TSM\config\tsmjbbd.ini.smp to C:\Program Files\Tivoli\TSM\baclient, naming it tsmjbbd.ini.



    Per APAR IC85873, the default journal name is corrected as follows:

    ...JournalPipe=pipename
    Specifies the pipe name of the journal service session manager to which backup clients initially connect, when establishing a journal-based backup session. This setting is used in conjunction with the backup client option of the same name. The default pipe name is \\.\pipe\jnlSessionMgr1. For example, in dsm.opt:
      JournalPipe \\.\pipe\jnlSessionMgr1   

    Under tsmjbbd.ini [JournalSettings] stanza:

      JournalPipe=\\.\pipe\jnlSessionMgr1

Per customer input from the feedback link on the Tivoli Storage Manager 6.2 Information Center:

Chapter 2: Configure the Tivoli Storage Manager client > Backups in a cluster server environment > Configure the backup-archive client to process cluster disk resources > Step 4: Create a generic service resource for failover

Under the Backups in a cluster server environment heading, there is a subheading for Microsoft Cluster Service (MSCS). The description in step 6 incorrectly instructs users to start the registry location for the node name and server with "HKEY_LOCAL_MACHINE". In the Registry Replication dialog, the on-screen text states correctly states that the location should be the path under HKEY_LOCAL_MACHINE.

The correct description for step 6 is as follows.

6. In the Registry Replication dialog, add the registry key corresponding to the Tivoli® Storage Manager node name and server name. The format for this key is: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\ <nodename>\<TSM server instance name>, where nodename is the name of your Tivoli Storage Manager node, and server instance name is the name of the Tivoli Storage Manager server that the node connects to. For example, if the node name is mscs-cluster-group-a and the Tivoli Storage Manager server name is tsmsv1, then enter the following registry key in the Registry Replication dialog:  
SOFTWARE\IBM\ADSM\CurrentVersion\Nodes\mscs-cluster-group-a
\tsmsv1.

This entry matches an existing key in the Windows Registry.

Per APAR IC85460

Configuring backup-archive clients > Getting started>Backup-archive client operations and security rights

The table of user security rights is updated:

Operating system Account What can I back up and restore?
Windows 2008, Windows 2008 R2, Windows 7, and Windows Vista Member of Administrators group
  • Back up and restore all files and directories
  • Back up and restore system state
Windows 2008, Windows 2008 R2, Windows 7, and Windows Vista Member of Backup Operators group
  • Back up and restore all files and directories
  • Back up system state, except for ASR Writer

    Note: Backup Operator group members cannot restore system state.
Windows 2008, Windows 2008 R2, Windows 7, and Windows Vista Member of Users or other group
  • Back up and restore all files and directories
    Note: Users must have the following Microsoft Windows security privileges in order to back up and restore files and directories:
    • Back up files and directories
    • Restore files and directories

    Attention: These privileges represent a potential security risk since they allow the user to back up any file, or restore any file for which a backup copy exists. The privileges should be granted only to trusted users. Refer to the Microsoft Windows documentation for further information about these privileges.

    Note: System state cannot be backed up or restored.
Windows 2003 Member of Administrators group or member of Backup Operators group
  • Back up and restore all files and directories
  • Back up and restore system state
Windows 2003 Member of Users or other group
  • Back up and restore all files and directories to which the account has access
    Note: Users must have the following Microsoft Windows security privileges in order to back up and restore all files and directories on the system:
    • Back up files and directories
    • Restore files and directories

    Attention: These privileges represent a potential security risk since they allow the user to back up any file, or restore any file for which a backup copy exists. The privileges should be granted only to trusted users. Refer to the Microsoft Windows documentation for further information about these privileges.
    Note: System state cannot be backed up or restored.

    Note: System Access Control Lists (SACL) used for auditing entries are not backed up or restored
Note: The information in this table assumes that the default privileges for the "Administrators", "Backup Operators", and "Users" groups have not been altered.



Per APAR IC70767:
Configuring
Section: Configuring backup-archive clients
Topic: Configuring the Tivoli Storage Manager client
Item: Configuring Tivoli Storage Manager client/server communication with Secure Socket Layer

Add the -populate option to the example command:

gsk8capicmd -keydb -create -populate -db dsmcert.kdb -pw password -stash


Per defect 66268:
Configuring
Section: Configuring backup-archive clients
Topic: Backups in a cluster server environment
Subtopic: Configuring the backup-archive client to process cluster disk resources
Item: Step 3: Configure the schedule service

The documentation erroneously states that you can configure the scheduler service for a cluster group by using the Tivoli Storage Manager scheduler setup wizard, by choosing "This is a cluster node".
To configure scheduler service for a cluster group, you must use the Client Service Configuration Utility, dsmcutil.


Per APAR IC74987:
Configuring
Section: Getting started
Topic: Backup-archive client operations and security rights

For Windows 2008, indicate that members of the Backup
Operators group cannot backup ASR writer data.

For Windows Vista and Windows 7, indicate that members of the
Backup Operators group cannot backup ASR writer data.




Backing up and restoring data

Per APAR IC79529
Chapter 4: Backing up your data
>Scenario: Backing up your virtual machines

A new step is added to this procedure to illustrate how to override a default management class by adding the management class name to an include statement the identifies the virtual machine and files.

The follow text is added after step 6.

6a. Optional: If you want to override the default management class when backing up files, use an include statement and add the name of the management class to use instead of the default management class. Identify the virtual machine and files that you want to use a different management class for when performing backups. In this example, the new management class is used when performing a backup of all files on the C disk of the virtual machine identified by "vm-name".

include "\\vm-name\c$\*" new_management_class_name


Per APAR IC69676:
The Tivoli Storage Manager information center incorrectly indicates that NAS backup and restore is supported on the Mac OS X, Linux, and HP-UX backup-archive clients. NAS backup and restore is supported only on the AIX, Solaris, and Windows backup-archive clients.


Per APAR IC75540 and IC70146:
Tivoli Storage Manager client support of ONTAP, and non-7-bit ASCII data is documented in the following table:

NetApp Data ONTAP version TSM client version 6.2 support ONTAP non-7-bit ASCII (Unicode) support TSM Client non-7-bit-ASCII (Unicode) support
earlier than 7.3.0 None No No
7.3.0, 7.3.1, 7.3.2 Any 6.2 No No
7.3.3 6.2.0, 6.2.1 Yes No
7.3.3 6.2.2 and later Yes Yes
later than 7.3.3 and earlier than 8.0 6.2.2 and later (Best effort only) Yes Yes
8.0.0 6.2.2 and later (Best effort only) No No
later than 8.0.0 6.2.2 and later (Best effort only) Yes Yes

"Best effort" support means the following

* IBM Support will accept calls for client issues when using any version of ONTAP not explicitly excluded from support
* IBM Support will not require that the customer recreate the problem with fully supported versions of ONTAP before calling in for support
* At the discretion of IBM Support, problem determination may cease if the problem is determined to be unique to the version of ONTAP.



Per APAR IC67583:

Chapter 4. Backing up your data
Topic: Understanding which files are backed up

The topic is updated as follows:

When you request a backup, Tivoli Storage Manager backs up a file if some requirements are met.

The following are the requirements that must be met for Tivoli® Storage Manager to back up a file.

  • The selected management class contains a backup copy group.
  • The file meets the serialization requirements defined in the backup copy group. If serialization is static or shared static, and the file changes during backup, the file will not be backed up.
  • The file meets the mode requirements defined in the backup copy group. If the mode is modified, the file must have changed since the last backup. If the mode is absolute, the file can be backed up even if it does not change.
  • The file meets the frequency requirements defined in the backup copy group. The specified minimum number of days since the last backup must elapse before a file is backed up.
  • The file is not excluded from backup by an exclude statement.
  • The file is not excluded from backup by the operating system. These excluded files can be found in registry subkey
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup

Files that are part of the Windows system state (system objects on Windows XP) are eligible for backup only when performing a system state backup. You can back up the system state only as a single entity because of dependencies among the system state components. You can not back up or restore the files individually. For example, because C:\windows\system32\ntoskrnl.exe is part of the Windows system state, it is not backed up during an incremental or selective backup of the C: drive.


Per APAR IC77216
Chapter 4: Backing up your data
Topic: Backing up VMware virtual machine data
Subtopic: Preparing the environment for VMware backup processing

Step 2 needs new information to include SAN policy configuration for Windows clients.
      2. Configure the vStorage backup server using the following steps:

      a) If you are configuring the backup proxy server to directly access the storage volumes, turn off automatic drive letter assignment.. If it is not turned off, the vStorage backup server might corrupt the Raw Data Mapping (RDM) of the virtual disks and the backup will fail. For vStorage backup servers that run on Windows Server 2008 or Windows Server 2008 R2, the Windows SAN policy must be changed to OnlineAll. Setting the SAN policy to OnlineAll enables the operating system to bring new disks online, and make them available to the backup server. The SAN policy must be set to OnlineAll to allow restore operations to use the vmbackvcbtransport hotadd or san methods to restore data. Run diskpart.exe and enter the following commands to turn off automatic drive letter assignment and change the SAN policy:

      diskpart
      automount disable
      automount scrub
      san policy OnlineAll
      exit
Per APAR IC79443
Chapter 4. Backing up your data
Topic: Running full virtual machine backups using the VMware Consolidated Backup framework
The following bullet item has been added to this topic immediately after the introductory text that states:

"Consider the following prerequisites before starting this procedure:"
  • Each virtual machine that you are going to back up must be accessible by an IP address or a DNS name. VMware tools must be installed in the guest operating system and the virtual machine must be powered on before you can perform a backup operation.


Per defect 61741, plus additional updates October 2011:

Chapter 4. Backing up your data
Topic: Backing up virtual machines on a Windows Hyper-V system

Add the following information

Hyper-V backup support limitations
    Due to the tight integration of Microsoft Failover Clustering with Cluster Shared Volumes and Hyper-V, the following limitations apply when using Tivoli® Storage Manager.

    Microsoft Hyper-V support is provided for the following configurations:
    • A dedicated Hyper-V system
    • A Hyper-V configuration that is part of Microsoft Failover Clustering
    • A Hyper-V configuration that is part of Microsoft Failover Clustering with Cluster Shared Volumes

    VM backups can only be performed by a backup-archive client installed on the cluster node that is the current owner of the VM. To see which VMs are owned by the node, navigate the Windows menu items: ServerManager->Roles->Hyper-V Manager.

    A VM should be restored only by a backup-archive client installed on the cluster node that is the current owner of the VM. To determine the VM configurations of the cluster, navigate the Windows menu items: ServerManager > Features > Failover Cluster Manager > cluster name > Services and Applications.. Use the Services and Applications window to change which node is the owner of the VM before you restore the VM.

    VMs currently owned by different nodes which have files on a common Cluster Shared Volume cannot be backed up simultaneously when using the default system VSS provider. The second backup will fail as the shared volume will be owned by the first node. You can reduce the amount of time that the first node owns the shared volume to just a few seconds by using hardware snapshots through the VSS provider supplied by your storage hardware vendor. Once the hardware snapshot is completed, the backup process can be initiated from the second node, therefore the backups can be running concurrently from both nodes. To determine which node owns the volume, navigate the Windows menu items: ServerManager > Features > Failover Cluster Manager > cluster name > Cluster Shared Volumes. The Cluster Shared Volume windows displays the status of the volume, including ownership, and if a backup is in progress (with redirected I/O enabled).

    If your cluster environment typically has all VMs owned by a single node, and other nodes only provide failover support, the following applies:

    •Consider using CLUSTERNODE YES for backup from the active node and restore to failover nodes (if needed).
    •Consider running the Tivoli Storage Manager scheduler as a failover service to periodically backup all VMs. For example: dsmc backup vm * -vmbackuptype=hypervfull. A failover will start the scheduler on the failover node.
    If your cluster environment typically has some VMs owned by one node, and other VMs owned by other nodes, the following applies:

    •Consider using the Asnodename option to allow for backup from multiple nodes and restore to failover nodes (if needed).
    •Consider running the Tivoli Storage Manager scheduler as active on each node to periodically backup the VMs owned by each node. The schedules need to be defined with non-overlapping start times to avoid contention for common shared volumes. If the scheduler on each node backs up with -vmlist=*, there is no need for the scheduler service to failover since the scheduler service on the other node will automatically pick up nodes which move over on the next backup.


Per APAR IC66105:
Chapter 4. Backing up your data
Section Backing up off-host VMware virtual machine data, after Step 14 insert:

Restriction:
The original names of Windows mount points in the VMware guest, which do not have a drive letter assignment, cannot be determined when running a Tivoli Storage Manager VMware off-host backup using the BACKUP VM command. These mount points are backed up to a filespace name. The name includes a number assignment that is provided by the VMware vStorage APIs. The filespace names, created for mount points, do not correspond to the actual volume mount points. Therefore, restoring these backups require selecting an alternate restore location. To support a restore to the original location from within the guest machine for these Windows mount points, convert the mount point to a mapped drive or assign a drive letter to the mount point.

When using mount points without drive letter assignments, use the following syntax when adding an include statement for that volume:
exclude \\machine\3$\dir1\...\*.doc



Per APAR IC66115:
Chapter 4. Backing up your data
Section Backing up off-host VMware virtual machine data, after Step 14 insert this note:

Migrating from backup-archive clients running inside a virtual machine to file-level, off-host backups from a backup proxy

The following is a migration consideration when you are making a transition from Backup-Archive clients running inside virtual machines, to file-level, off-host backups from a backup proxy. This consideration applies if you use a non-default node name inside the virtual machine, such as the fully-qualified hostname that includes the DNS suffix.

Because the backup vm command will use the shortened hostname as the default nodename, backup data will be stored under a different node name on the TSM server. The backup vm command can replace the TSM node name with the fully-qualified hostname. However, the file space names that are created in this case will include the fully-qualified hostname and will not match the file space names currently on the TSM server.

To avoid this problem, change the node name from the full-qualified hostname to the default hostname prior to performing any backup vm commands. Use the rename node command on the TSM server.

To illustrate this point, consider the following example.

The node name inside the virtual machine is machine1.us.ibm.com. The original file space name is \\machine1\c$. You back up with this command:
backup vm -vmlist=9.22.88.100[machine1.us.ibm.com]
The backup vm command creates a redundant file space \\machine1.us.ibm.com\c$.
To avoid the redundant file space, change the node name with this command:
rename node machine1.us.ibm.com machine1
Then back up and specify the original file space name with this command:
backup vm -vmlist=9.22.88.100[machine1]




Per APAR IC71690:
Chapter 4. Backing up your data
New Topic: Ambiguous file space names in file specifications

Ambiguous file space names in file specifications

If you have two or more file spaces such that one file space name is exactly the same as the beginning of another file space name, then an ambiguity exists when you try to restore, retrieve, query, or do another operation that requires the file space name as part of the file specification.

For example, consider the following file spaces and the backup copies they contain:

File space name File name
\\storman\home amr\project1.doc
\\storman\home\amr project2.doc
Notice that the name of the first file space, \\storman\home, matches the beginning of the name of the second file space,  \\storman\home\amr. When you use the Tivoli Storage Manager command line client interface to restore or query a file from either of these file spaces, by default the client will match the longest file space name in the file specification, \\storman\home\amr. To work with files in the file space with the shorter name, \\storman\home, use braces around the file space name portion of the file specification.

This means that the following query command finds project2.doc but does not find project1.doc:

  dsmc query backup "\\storman\home\amr\*"

This is because the longer of the two file space names is \\storman\home\amr and that file space contains the backup for project2.doc.

To find project1.doc, enclose the file space name in braces. The following command finds project1.doc but does not find project2.doc:

   dsmc query backup "{\\storman\home}\amr\*"

Similarly, the following command restores project1.doc but does not restore project2.doc:


  dsmc restore {\\storman\home}\amr\project1.doc




Per defect 61741:

Chapter 4. Backing up your data
Topic: Displaying backup processing status

Add the following information about deduplication processing status:


Total bytes before deduplication:
Specifies the number of bytes to send to the Tivoli Storage Manager server if the client does not eliminate redundant data. Compare this amount with Total bytes after deduplication.

Total bytes after deduplication
Specifies the number of bytes that are sent to the Tivoli Storage Manager server, after deduplication of the files on the client computer.


Per APAR IC87966
Back up and restore data with backup-archive clients > Backing up your data > Backup (Windows): Additional considerations > Microsoft Dfs file protection methods

The method of protecting DFS file systems applies to Windows Server 2003 and Windows Server 2008.


Scheduler


Per APAR IC83229
Chapter 7: Tivoli Storage Manager scheduler overview
Topic: Client-acceptor scheduler services versus the traditional scheduler services

The traditional scheduler services text (last two list items) has been updated as follows:

Tivoli Storage Manager traditional scheduler services
· Started with command dsmc sched command.
· Remains active, even after scheduled backup is complete.
· Requires higher use of system resources when idle.
· Tivoli Storage Manager client options and Tivoli Storage Manager server override options are only processed once when dsmc sched is started; if you delete an option from a client options set, you must restart the scheduler so the scheduler is made aware of the changes.
· You must restart the scheduler process for updated Tivoli Storage Manager options to take effect.

Tip: Restart the traditional scheduler periodically to free system resources
previously used by system calls






Processing options


Per APAR IC76788

Chapter 10. Processing Options
Topic: Filelist

The description for the filelist option has changed to include the following information:

The files (entries) listed in the filelist must adhere to the following rules:

Start of change

  • Each entry must be a fully-qualified or a relative path to a file or directory. Note that if you include a directory in a filelist entry, the directory is backed up, but the contents of the directory are not.
  • Each path must be specified on a single line. A line can contain only one path.
  • Paths must not contain control characters, such as 0x18 (CTRL-X), 0x19 (CTRL-Y) and 0x0A (newline).
  • Paths must not contain wildcard characters. Do not include * or ? in a path.
  • Mac OS X operating systemsWindows operating systemsThe filelist can be an MBCS file or a Unicode file with all Unicode entries. For Mac OS X, the filelist can be encoded in the current operating system language or UTF-16.
  • If a path or file name contains a space, enclose the entire path in quotation marks (") or single quotation marks ('). For example "C:\My Documents\spreadsheet.xls" or 'C:\My documents\spreadsheet.xls'.
  • If a path contains one or more single quotation marks ('), enclose the entire entry in quotation marks ("). If a path contains one or more quotation marks, enclose the entire path in single quotation marks. File list processing does not support paths that include a mix of quotation marks and single quotation marks.

The following examples illustrate the correct and incorrect use of quotation marks and single quotation marks in paths:

This path example contains a single quotation mark, so the path must be enclosed in quotation marks:
"/home/gatzby/mydir/gatzby's_report.out"
This path example contains quotation marks, so it must be enclosed in single quotation marks:
'/home/gatzby/mydir/"top10".out'
This path example contains a space character, so it must be enclosed in either quotation marks or single quotation marks:
"/home/gatzby/mydir/top 10.out"
or
'/home/gatzby/mydir/top 10.out'

This path example is not supported for filelist processing because it contains unmatched delimiters (" and ’):

/home/gatzby/mydir/andy's_"top 10" report.out
These paths are not supported for filelist processing because they contain wildcard characters:
/home/gatzby*
/home/*/20??.txt

  • Any Tivoli Storage Manager filelist entry that does not comply with these rules is ignored.



Per APAR IC77609
Chapter 12. Processing options
Topics vmchost, vmcuser, vmcpw
The documentation for these options states that they can be used on Backup VM and Query VM commands. They can also be used with Restore VM commands.

Per defect 63529:
Chapter 12. Processing options
Section asnodename (this update is contained in the revise topic introduced by APAR IC77315)

Add this restriction when using asnodename to back up an image:
  • When backing up image, you must identify the volume by using the UNC name. You cannot use the drive letter.

Per APAR IC77315
Chapter 12. Processing options
Section asnodename (Entire topic was revised)

Asnodename

Use the asnodename option to allow an agent node to back up, archive, restore, retrieve, and query data on behalf of a target node.

An agent node is a client node that has been granted authority by a Tivoli® Storage Manager administrator to perform client operations on behalf of a target node, which is a another client node. The administrator uses the grant proxynode command on the Tivoli Storage Manager server to grant this authority.

When you back up or archive data without the asnodename option, the backed up data is stored in a file space on the Tivoli Storage Manager server that matches the Tivoli Storage Manager nodename of the drive on which the original data exists. For example, if a computer with a nodename of "TAURUS" backs up data on its F: drive, then the data is stored in a server file space named \\taurus\f$; node Taurus owns the file space.

When you use the asnodename option to back up data on behalf of a target node, the data is stored in a file space owned by the target node. For example, if computer having a Tivoli Storage Manager nodename of TAURUS backs up data on its F: drive using -asnodename=scorpio, the data is stored in a file space named \\scorpio\f$, and the files are owned by the SCORPIO node.

When you restore or retrieve data, the default behavior is to restore or retrieve the data to a location that matches the file space name. Continuing with the preceding example, if node TAURUS uses the option -asnodename=scorpio to restore data from \\scorpio\f$, Tivoli Storage Manager attempts to restore the data to the F: drive on a computer named SCORPIO. This might not produce the expected result, especially if the SCORPIO computer does not exist or if you do not have access to it.

To restore files, specify a destination for the restored files. In the following example, the restore command is entered on the TAURUS node. The command restores all files and subdirectories from the Users\taurus\education directory in the \\scorpio\f$ file space to the local F: drive.
dsmc restore \\scorpio\f$\users\taurus\education\* f:\ -subdir=yes
-asnodename=scorpio

Restrictions:

· You cannot use the asnodename option with -fromnode and you cannot perform NAS backup using asnodename.

· asnodename can be used for clustered systems, although no specific cluster software is supported.

· You cannot use the asnodename option with system state components.

· When backing up an image, you must identify the volume by using the UNC name. You cannot use the drive letter.

· Tivoli Storage Manager does not track the originating system for the files. Because the asnodename option can cause data to be stored in the same file space name, regardless of the system from which the backup was taken, you will need to make sure you know which files should be restored to each system.

Supported Clients

This option is valid for all Windows clients.

Options File

Place this option in the dsm.opt file. You can set this option on the General tab of the Preferences editor.

Syntax

>>-ASNODEname- --targetnode------------------------------------><

Parameters

targetnode
Specifies the node name on the Tivoli Storage Manager server under which you want to back up or restore data.

Examples

Options file:
asnodename scorpio
Command line:
dsmc incr f:\* -subdir=yes -asnodename=scorpio
This command backs up the entire F disk to the server file space called \\scorpio\f$.

This option is not valid in interactive mode, but it can be defined in the options portion of a schedule definition.


Per APAR IC90417
Chapter 12. Processing options
Section: Clusterdisksonly
The following scenario is removed:

Scenario 2: Back up a node which manages the local (non-clustered) drives and
the system state information in a clustered environment using volume mount
points as cluster resources. This node is dedicated to the restoration of the physical system
if there is a hardware failure. There are clustered drives which appear as volume
mount points in this environment (for example, IBM Tivoli SANergy,
Windows Server operating systems). Also, be sure to remove any volume
mount points from the incremental processing domain.


Per defect 62183:
Chapter 12. Processing options
Section: dateformat

In addition to the 5 formats listed in the documentation, there are two additional date formats:

6 YYYY/MM/DD
7 DD/MM/YYYY

Per defect 63691:
Chapter 12. Processing options
Section: domain.image
domain.image option is supported on Win 2003 server 64-bit in addition to 32-bit.

Per APAR IC83510
Chapter 12. Processing Options
Section: Include options
The text that describes how to associate a management class with a backup group on an include statement was not clear. It has been replaced with the following description:

optional_parameter
management_class_name
Specifies the name of the management class to assign to the objects. If a management class is not specified, the default management class is used. To associate a management class with a backup group on an include statement, use the following syntax:

Windows operating systems
include virtual_filespace_name/group_name management_class_name

where:

virtual_filespace_name
Specifies the name of the Tivoli Storage Manager server virtual filespace that you associated with the group, on the Backup Group command.

group_name
Is the name of the group that you created when you ran the Backup Group command.

management_class_name
Is the name of the management class to associate with the files in the group.

For example, to associate the TEST management class with the group named MyGroup. MyGroup files are stored on the server in the virtual file space named MyVirtualFileSpace, use the following syntax:

Windows operating systems
include MyVirtualFileSpace\MyGroup TEST

Additional text updates for IC83510 are included in Chapter 13: Using commands->Backup Group

Per APAR IC85873:
Chapter 12. Processing options
Section journalpipe
The default journal name is corrected as follows:

    ...
    Place this option in the client options file (dsm.opt).

      JournalPipe \\.\pipe\jnlSessionMgr1

    You can also specify this option in the journal configuration file (tsmjbbd.ini).

      [JournalSettings]
     JournalPipe=\\.\pipe\
    jnlSessionMgr1





Per APAR IC85304 :
Chapter 12. Processing options
Section: Lanfreeshmport

The default value of the port_address parameter is 1510 for all clients except Windows. The documentation is changed as follows:
    ...
    Parameters

    port_address
    Specifies the number that is used to connect to the storage agent. The range of values is 1 through 32767; the default is 1 for Windows and 1510 for all other platforms.


Per defect 79403
Chapter 12. Processing options
Section Lanfreetcpport
The abbreviated form for the LANFREETCPPORT option is incorrect in the product documentation. The correct abbreviation for LANFREETCPPORT is LANFREETCPPort.

Chapter 12. Processing options
Per APAR IC77687, the description of postschedulecmd/postnschedulecmd has been revised to clarify how return codes can affect scheduled events.

The new description is as follows:

Postschedulecmd/Postnschedulecmd

The postschedulecmd/postnschedulecmd option specifies a command that the client program processes after it runs a schedule.

If you want the client program to wait for the command to complete before it continues with other processing, use the postschedulecmd option. If you do not want to wait for the command to complete before the client continues with other processing, specify the postnschedulecmd option.

Notes:
1. For scheduled operations where the scheduled action is something other than COMMAND:
If the postschedulecmd command does not complete with return code 0 (zero), the return code for the scheduled event is either 8, or the return code of the scheduled operation, whichever is greater. If you do not want the postschedulecmd command to be governed by this rule, you can create a script or batch file that invokes the command and exits with return code 0. Then configure postschedulecmd to invoke the script or batch file.
2. For scheduled operations where the scheduled action is COMMAND:
The return code from the command specified on the postschedulecmd option does not affect the return code that is reported to the server when the scheduled event completes. If you want the results of postschedulecmd operations to affect the return code of the scheduled event, include the postschedulecmd operations in the scheduled action command script instead of using the postschedulecmd option.
3. The return code from an operation specified on the postnschedulecmd option is not tracked, and does not influence the return code of the scheduled event.
4. The server can also define the postschedulecmd option (and the postnschedulecmd option).

Supported Clients

This option is valid for all clients. The Tivoli® Storage Manager client API does not support this option. The server can also define this option.

Options File

Place this option in the client options file (dsm.opt). You can set this option on the Scheduler tab, Schedule Command button of the Preferences editor.

Syntax
Read syntax diagramSkip visual syntax diagram
>>-+-POSTSChedulecmd--+-- --
cmdstring--------------------------><
   '-POSTNSChedulecmd-'                 


Parameters
cmdstring
Specifies the command to process. You can enter a command to be run after a schedule with this option. Use only one postschedulecmd option.

Specify the command string just as you would enter it from the operating system command prompt. If the command string contains any blank spaces, enclose the command string in single quotation marks. For example:
'net stop someservice'

Use a blank, or null, string for cmdstring if you want to prevent any commands from running that the Tivoli Storage Manager server administrator uses for postschedulecmd or preschedulecmd. If you specify a blank or null string on either option, it prevents the administrator from using a command on both options.

If your administrator uses a blank or null string on the postschedulecmd option, you cannot run a post-schedule command.

Examples
Options file:
posts startdb.cmd
posts 'rename c:\myapp\logfile.log logfile.new'
posts 'net start "simple service"'
posts 'rename "c:\myapp\log file.log" "log file.new"'
posts '"C:\Program Files\MyTools\runreport.bat"
  log1.in log2.in'

Command line:
-postschedulecmd="'restart database'"

This option is valid only on the initial command line. It is not valid in interactive mode.

Chapter 12. Procesing options
Section Query Inclexcl

The command description in the published manual was incomplete. The complete command description is provided here:

Windows operating systems
Query Inclexcl

The query inclexcl command displays a list of include-exclude statements in the order in which they are processed during backup and archive operations. The list displays the type of option, the scope of the option (archive, all, and so on), and the name of the source file.

Tivoli® Storage Manager excludes some files from file system backup and restore operations. You can use the query inclexcl command to display a list of these files. In the output of the command, these files have Operating System next to the path.

You can test the validity of patterns you want to use in your include-exclude list before you actually insert them in your options file. See the test pattern explanation.

Use the detail option to display the management class that is associated with an include-exclude statement.

Windows operating systemsUse the display option to display the files that are included or excluded from a file system back up operation.

Supported Clients

This command is valid for all clients.

Syntax
Windows operating systems
>>-Query INCLexcl-+----------------+--+----------+--+--------+><
                 '-test pattern-'    '- -DETail-'  .-basic--|
                   '--DISPLAY=--------------+--'  '-vssexcl-'
                                                   '-all-'
Skip visual syntax diagram
    
Parameters
test pattern
Use for testing the validity of patterns you want to use in your include-exclude list. When you use a test pattern with this command, the following occurs:

  • The internal include-exclude list is not displayed
  • The pattern is processed as if it came from an include-exclude statement, including all the usual error checking
  • The pattern is displayed as it would appear in the include-exclude list
If the test pattern has no errors, the compiled pattern result is the same as the test pattern.

-DETail
Displays the management class that is associated with the include-exclude statement.


Windows operating systems-DISPLAY=basic | vssexcl | all
-DISPLAY=basic displays the files and directories that have been included or excluded by one of the following methods:
  • The objects were included or excluded in the client options file.
  • The objects were included or excluded in a server-side client option set.
  • The objects were excluded by the operating system because they are contained in the HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\BackupRestore\FilesNotToBackup registry key.
  • The objects were explicitly excluded by IBM® Tivoli Storage Manager.
This is the default if a display value is not specified.

-DISPLAY=vssexcl displays a list of files that are excluded from a file system backup, because they are included when a system state backup is performed. Files that are backed up by a backup systemstate operation are protected by the VSS writer; you cannot include these files in a file system backup by adding them to an include statement in the dsm.opt file, or client option set.

-DISPLAY=all displays all files that are included or excluded during a file system backup.
Examples
Windows operating systemsTask
Exclude a file from deduplication by excluding it in the client options file:
Exclude Dedup *\...\file2

Windows operating systemsTask
Display a basic list of include-exclude statements. Command:
query inclexcl

Windows operating systemsTask
Display a list of files that are excluded from file system backups because the VSS writer includes them in system state backups.
query inclexcl -display=vssexcl

Windows operating systemsTask
Display a list of include-exclude statements. Display the management class that is associated with each statement.
query inclexcl -detail

Windows operating systemsTask
Test the validity of this pattern: ..\?x?\*.log
query inclexcl ..\?x?\*.log


Per defect 62183:
Chapter 12. Processing options
Section timeformat

In addition to the 4 formats listed in the documentation, there is one additional time format:

5 A/P 12:00:00



Per APAR IC67043 and defect 61611:

Chapter 12: Processing options

Section: Skipmissingsyswfiles

Use the Skipmissingsyswfiles option to specify whether the Tivoli
Storage Manager client skips certain missing VSS writer files and continues
the system state backup.



Setting the skipmissingsyswfile option to yes causes certain VSS writer files
that are not found during a system state backup to be skipped. This option is effective
only for missing files from the following VSS writers:

* System Writer
* Windows Deployment Service Writer
* Event Log Writer


Consider the following items before you use the skipmissingsyswfile
option:

* Setting the skipmissingsyswfile option to yes enables backups that
might have failed with previous versions of Tivoli Storage Manager to
complete.
* There is a small risk of an inconsistent backup because a file is
skipped.
* This risk is minimized by these factors:
* The backup can be done only when the system is running.
* Critical system files are protected from deletion by Microsoft
Windows.


Supported Clients

This option is valid for Windows Server 2008, Windows Server 2008 R2,
Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows
7 clients only.



Options File

Place this option in the client options file (dsm.opt).



Syntax

.-Yes-.
>>-SKIPMISSingsyswfiles--+-----+-------------------------------><
'-No--'




Parameters

Yes
Specifies that you want the Tivoli Storage Manager client to skip files that are
not found during the backup of the System Writer files. The files that are not
found are logged to both the error log and the server activity log. The final
return code is set to 8. This is the default.

No
Specifies that you want the Tivoli Storage Manager client to stop the
backup when files are not found during system state backup. The files that are not found are logged to the error log and to the server activity log..
The final return code is 12.




Examples

Options file:

SKIPMISSingsyswfiles yes


Command line:

-SKIPMISSingsyswfiles=yes


Related reference
2.18, "Backup Systemstate"
Use the backup systemstate command to back up all startable system state
and system services components as a single object, to provide a
consistent point-in-time snapshot of the system state.

Per APAR IC68737, in version 6.2.1.2 and later:
Chapter 12. Processing options
Add the following section for a new option:


Hsmreparsetag

The hsmreparsetag option specifies a unique reparse tag that is created by an HSM product installed on your system.

Many HSM products use reparse points to retrieve or recall migrated files. After a file is migrated, a small stub file, with the same name as the original file, is left on the file system. The stub file is a reparse point that triggers a recall of the original file when a user or application accesses the stub file. The reparse point includes a unique identifier called a reparse tag to identify which HSM product migrated the file.

If the Tivoli Storage Manager backup-archive client does not recognize the reparse tag in a stub file, the backup-archive client causes the HSM product to recall the original file. You can prevent files from being recalled if you specify the reparse tag with the hsmreparsetag option.

The backup-archive client recognizes the reparse tag of HSM products from the following companies:

Company name
International Business Machines Corp.
Wisdata System Co. Ltd.
BridgeHead Software Ltd.
CommVault Systems, Inc.
Data Storage Group, Inc.
Enigma Data Solutions, Ltd.
Enterprise Data Solutions, Inc.
Global 360
GRAU DATA AG
Hermes Software GmbH
Hewlett Packard Company
International Communication Products Engineering GmbH
KOM Networks
Memory-Tech Corporation
MoonwalkTM Universal
Pointsoft Australia Pty. Ltd.
Symantec Corporation



If the HSM product you use is not in the preceding list, use the hsmreparsetag option to specify the reparse tag. Ask your HSM product vendor for the reparse tag used by the product.

Supported Clients
This option is valid for all Windows clients.

Option File
Place this option in the client options file (dsm.opt).

Syntax
>>---HSMREPARSETAG---reparse_tag_value------------------><

Parameters
reparse_tag_value
A decimal (base 10) or hexadecimal (base 16) value that specifies the reparse tag.

Examples
Options file:
Specify the HSM reparse tag in decimal format:
hsmreparsetag 22

Specify the HSM reparse tag in hexadecimal format:
hsmreparsetag 0x16

Command line:
Does not apply.



Chapter 12. Processing options
Topics: Subfilebackup

Per APAR IC72719, the subfilebackup option is valid for all Windows backup-archive clients.



Chapter 12. Processing options
Topics: Schedlogmax and Schedlogretention

Per APAR IC71383, the Web client log (dsmwebcl.log) is pruned according to the settings of options schedlogmax and schedlogretention.





Commands



Chapter 13. Use commands
Topic: Backup Group
Per defect 65628, this command is not restricted to authorized users.

Per APAR IC83510
The description of the processing rules used during a group backup has been revised to add a new list item ("Management class rebinding for grouped objects") that describes how a management class is rebound to objects that are included in a group backup. The new list of processing rules now reads as follows:

A group backup allows you to create a consistent point-in-time backup of a group of files that is managed as a single logical entity. Objects in the group are subject to the following processing rules:

  • Management class rebinding for grouped objects:
    • During full backups, all objects in a backup group are assigned to the same management class.
    • During differential backups, if a new management class is specified on an include statement for an existing backup group, the following behavior occurs:
      • Any new and changed objects in the backup group are bound to the new management class.
      • Any member objects of the group that are not changed appear as though they have not been bound to the new management class. These unchanged objects are not included in the "Total number of objects rebound" statistics that are displayed when the Backup Group command completes.
      • The unchanged objects are reassigned to a newly created backup group, and the new backup group is bound to the new management class. However, the original management class name is still displayed for the unchanged group objects.

        Even though the original management class name is still displayed for the unchanged objects, they are effectively bound to the new management class of the backup group.
  • Existing exclude statements for any files in the group are ignored.
  • All objects in the group are exported together.
  • All objects in the group are expired together as specified in the management class. No objects in a group are expired until all other objects in the group are expired, even when another group they belong to gets expired.
  • If you are performing full and differential group backups to a sequential device, during a restore the data is in no more than two locations. To optimize restore time, perform periodic full backups to back up the data to one location on the sequential media.
  • During a full group backup, all objects in the filelist are sent to the server. During a differential group backup, only data that has changed since the last full backup is sent to the server. Objects in the filelist that have not changed since the last full backup are assigned as members of the differential group backup. This data is not resent to the server, reducing backup time.


Chapter 13. Use commands
Topic: Delete Access
    Per defect 64647, when typing indexes of authorization rules, do not enclose the indexes with parentheses. The following example is modified:

     
    Index  Type      Node     Owner    Path  
    _____  ______    ____________________________________
    1      Backup    node1    daisy   c:\dev\proja\list.c
    2      Archive   node3    marm    c:\fin\budg\depta.jan
    3      Backup    node4    susie   c:\plan\exp\deptc.feb
    4      Archive   node5    susies  c:\mfg\invn\parta.wip
    Enter Index of rule(s) to delete, or quit to cancel:

    To delete the authorization rules that allow marm and susies to access your files, type 2 4 or 2,4 then press Enter.



Chapter 13. Use commands
Topic: Delete Archive
Per APAR IC72510, only 1 filespec parameter is permitted. The filespec parameter can indicate more than one file by using wildcard characters.


Chapter 13. Use commands
Topic: Delete Backup
Per APAR IC72510, only 1 filespec parameter is permitted. The filespec parameter can indicate more than one file by using wildcard characters.

Reference
> Backup-archive client options and commands
> Use commands
Topic: Delete Backup
Per APAR IC72510, only 1 filespec parameter is permitted. The filespec parameter can indicate more than one file by using wildcard characters.

Per APAR IC78415
Reference
> Backup-archive client options and commands
> Use commands
Topic: Delete Backup
The syntax diagram is incomplete for deltype=ALL. The correct syntax (and description is as follows:

>>-Delete BAckup--+------------+-------------------------------->
'- --options-'

.-objtype=FILE--.
>--+- --filespec----------------------+----+---------------+---->
'- --{--filespacename--}--filespec-' '-objtype=IMAGE-'

.-deltype=ACTIVE---.
>----+------------------+--------------------------------------><
+-deltype=INACTIVE-+
'-deltype=ALL------'

ALL
Delete all active and inactive objects below a given directory, including all subdirectories and their files.

Note: The parent directory of the deleted files and subdirectories is not deleted. If you specify deltype=ALL, you cannot use the pick option because deltype=ALL and the pick option are mutually exclusive.

Chapter 13. Use commands
Topic: Delete Group
Per defect 65628, this command is not restricted to authorized users.



Chapter 13. Use commands
Topic: Query Group

    Per defect 65628, this command is not restricted to authorized users.

    Per defect 64344, the examples are modified as follows:

    If you perform a full and differential group backup, a query of this group using the -inactive option displays two active backups of the same name, one of type FULL and one of type DIFF.

    These backups inactivate any previous full and differential backups:

    tsm> q group {\fs}\v1 -inactive

    Size Backup Date          Mgmt Class A/I Group
    —––– –––––––––––          –––––––––– ––– ––––––
    978 B 06/02/2007 11:57:04  DEFAULT   A  FULL \fs\v1
     32 B 06/05/2007 13:52:04  DEFAULT   A  DIFF \fs\v1

    If you query a group backup without the -inactive option, the query displays only the latest group backup, whether it is type FULL or type DIFF:

    tsm> q group {\fs}\v1

    Size Backup Date          Mgmt Class A/I Group
    —––– –––––––––––          –––––––––– ––– ––––––
     32 B 06/05/2007 13:52:04  DEFAULT   A  DIFF \fs\v1



Chapter 13. Use commands
Topic: Restore Group
Per defect 65628, this command is not restricted to authorized users.

Chapter 13. Use commands
Topic: Restore VM
Per defect 72053_1 the Restore VM command's datacenter option description needs additional information added about folder names and restoring VMs using the GUI. Add the following information to the existing description of the datastore option:
      If a datacenter is contained within a folder, the datacenter name, complete with the folder name, must be specified.

      Start of changeIf the datacenter is contained in a folder, you must specify the -datacenter option when you restore the virtual machine and include the folder structure of the datacenter in the datacenter name.
      -datacenter=folder_name/datacenter_name
      End of change

      When you restore a virtual machine using the GUI, you must restore the virtual machine to a different location. If you restore to the original location, you cannot specify the folder name of the datacenter. Without a folder name to help locate the original datacenter, the restore fails.

Per APAR IC89466, the datastore parameter on the Restore VM command does not describe how VM files, that might be in different datastores, are restore to the datastore specified by the datastore parameter on the Restore VM command. The correct description reads as follows:

DATASTORE
Specifies the datastore to restore the virtual machine files to. The datastore can be on a SAN, NAS, or iSCSI device. If you backed up a virtual machine that had disks in multiple datastores, the disks are restored to the datastore that is specified by this parameter. This parameter is only valid when restoring virtual machines backed up using the VSTORAGE API.





Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager
Client

Software version:

6.2

Operating system(s):

Windows

Reference #:

7017798

Modified date:

2011-11-01

Translate my page

Machine Translation

Content navigation