IBMTivoli Storage Manager forWindows Backup-Archive ... · Backup-archive client operations and security rights 99 Backup Operators group operations .....101 Considerations before

IBM Tivoli Storage Manager for Windows Backup-ArchiveClientsVersion 7.1.2

Installation and User's Guide

��

Note:Before you use this information and the product it supports, read the information in “Notices” on page 767.

Third edition (April 2015)

This edition applies to version 7, release 1, modification 2 of IBM Tivoli Storage Manager (product numbers5608-E01, 5608-E02, and 5608-E03) and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright IBM Corporation 1993, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . xi

About this publication . . . . . . . . xiiiWho should read this publication. . . . . . . xiiiPublications . . . . . . . . . . . . . . xiiiConventions used in this publication . . . . . xiiiReading syntax diagrams . . . . . . . . . xiv

New for IBM Tivoli Storage ManagerVersion 7.1.2. . . . . . . . . . . . xvii

Chapter 1. Installing the Tivoli StorageManager backup-archive clients . . . . 1Upgrading the backup-archive client . . . . . . 1

Upgrade path for clients and servers . . . . . 1Considerations for migrating between processorarchitectures x32 and x64 . . . . . . . . . 1Additional upgrade information . . . . . . . 2Automatic backup-archive client deployment . . 3

Client environment requirements . . . . . . . 5Windows client environment requirements . . . 6

Windows client installable components . . . 6System requirements for Windows clients. . . 6Windows client communication methods . . . 6Backup-archive client features that are availableon Windows platforms . . . . . . . . . 7Windows supported file systems. . . . . . 7

NDMP support requirements (Extended Edition only) 8Installation requirements for backing up andarchiving Tivoli Storage Manager FastBack client data 8Client configuration wizard for Tivoli StorageManager FastBack . . . . . . . . . . . . 9Installing the Tivoli Storage Manager Windows client 9

Windows client installation might require a reboot 9Installation types . . . . . . . . . . . 10

Installing the Windows client for the first time 10Upgrading the Windows client . . . . . . 14Reinstalling the Windows client . . . . . 18Silent installation . . . . . . . . . . 18Modifying, repairing, or uninstalling theWindows client . . . . . . . . . . . 22

Troubleshooting problems during installation . . 24Software updates . . . . . . . . . . . 25

Chapter 2. Configure the Tivoli StorageManager client . . . . . . . . . . . 27Creating and modifying the client options file . . . 27Create a shared directory options file . . . . . . 29Creating multiple client options files . . . . . . 29Environment variables. . . . . . . . . . . 30Configuring the web client . . . . . . . . . 31Configuring the scheduler . . . . . . . . . 33

Comparison between client acceptor-managedservices and traditional scheduler services . . . 33

Configuring the client to use the client acceptorservice to manage the scheduler . . . . . . 34

Starting the client scheduler . . . . . . . . . 36Scheduling events using the GUI . . . . . . 36

Configuring Tivoli Storage Manager client/servercommunication across a firewall . . . . . . . 36Configuring Tivoli Storage Manager client/servercommunication with Secure Sockets Layer . . . . 39

Certificate Authorities root certificates . . . . 42Configure your system for journal-based backup . . 42

Configuring the journal engine service . . . . 42JournalSettings stanza (Windows) . . . . . 44JournalExcludeList stanza . . . . . . . 46JournaledFileSystemSettings stanza . . . . 47Overriding stanzas . . . . . . . . . . 50

Client-side data deduplication . . . . . . . . 50Configuring the client for data deduplication . . 54Excluding files from data deduplication . . . . 56

Automated client failover configuration and use . . 57Automated client failover overview . . . . . 57

Requirements for automated client failover . . 58Restrictions for automated client failover . . 59Failover capabilities of Tivoli Storage Managercomponents . . . . . . . . . . . . 60

Configuring the client for automated failover . . 60Determining the status of replicated client data 62Preventing automated client failover . . . . . 63Forcing the client to fail over . . . . . . . 63

Configuring the client to back up and archive TivoliStorage Manager FastBack data . . . . . . . . 64Configuring Tivoli Storage Manager to protectFastBack client data . . . . . . . . . . . 65Configuring the backup-archive client in a clusterserver environment . . . . . . . . . . . . 66

Protecting data in MSCS clusters (WindowsServer clients) . . . . . . . . . . . . 67

Configuring cluster protection (WindowsServer clients) . . . . . . . . . . . 67

Configure the Web client in a clusterenvironment . . . . . . . . . . . . . 68

Configure the Web client to process clusterdisk resources . . . . . . . . . . . 68

Frequently asked questions . . . . . . . . 75Configuring online-image backup support . . . . 78Configuring Open File Support . . . . . . . . 78Configuring NetApp and Tivoli Storage Managerfor snapshot difference incremental backups . . . 79

SnapMirror support for NetAppsnapshot-assisted progressive incremental backup(snapdiff) . . . . . . . . . . . . . . 80

Register your workstation with a server . . . . . 83Closed registration . . . . . . . . . . . 83Open registration . . . . . . . . . . . 84

Creating an include-exclude list . . . . . . . 84Include-exclude options . . . . . . . . . 85

Exclude file spaces and directories. . . . . 85

© Copyright IBM Corp. 1993, 2015 iii

|||

Include-exclude statements for networked filesystems. . . . . . . . . . . . . . 87Exclude files and directories from ajournal-based backup . . . . . . . . . 88Control processing with exclude statements . 88System files to exclude . . . . . . . . 89Exclude files with UNC names . . . . . . 90Include and exclude files that containwildcard characters . . . . . . . . . . 90Include and exclude groups of files withwildcard characters . . . . . . . . . . 91Examples using wildcards with include andexclude patterns . . . . . . . . . . . 92

Determine compression and encryptionprocessing . . . . . . . . . . . . . . 93Preview include-exclude list files . . . . . . 94Include and exclude option processing . . . . 95Processing rules when using UNC names . . . 97

Explicit use of UNC names for remote drives 97Conversion of DOS pathnames for fixed andremote drives. . . . . . . . . . . . 97Character-class matching examples . . . . 97

Chapter 3. Getting started . . . . . . 99Backup-archive client operations and security rights 99

Backup Operators group operations . . . . . 101Considerations before you start using a BackupOperators group account . . . . . . . . 101

Permissions required to restore files that useadaptive subfile backup . . . . . . . . . . 102Permissions required to back up, archive, restore orretrieve files on cluster resources . . . . . . . 102Tivoli Storage Manager client authentication . . . 102User account control . . . . . . . . . . . 103

Enabling client access to network shares whenUAC is enabled . . . . . . . . . . . 103

Starting a Java GUI session . . . . . . . . . 104Tivoli Storage Manager password . . . . . 105Setup wizard . . . . . . . . . . . . 105

Starting a command-line session . . . . . . . 105Using batch mode . . . . . . . . . . . 105Issuing a series of commands by usinginteractive mode . . . . . . . . . . . 106Displaying Euro characters in a command-lineprompt . . . . . . . . . . . . . . 106Use options on the DSMC command . . . . 107

Specifying input strings that contain blank spacesor quotation marks . . . . . . . . . . . 107Starting a web client session . . . . . . . . 108

User privileges . . . . . . . . . . . . 109Start the client scheduler automatically . . . . . 109Changing your password . . . . . . . . . 109Sorting file lists using the Tivoli Storage ManagerGUI . . . . . . . . . . . . . . . . 111Displaying online help . . . . . . . . . . 112Ending a session . . . . . . . . . . . . 112Online forums . . . . . . . . . . . . . 113

Chapter 4. Backing up your data . . . 115Planning your backups (Windows) . . . . . . 115

Which files are backed up . . . . . . . . . 116Open file support for backup operations . . . . 117Backing up data using the GUI . . . . . . . 119

Specifying drives in your domain . . . . . 120Backing up data using the command line . . . . 120Deleting backup data . . . . . . . . . . . 122When to back up and when to archive files . . . 123Pre-backup considerations (Windows) . . . . . 124

LAN-free data movement . . . . . . . . 124LAN-free prerequisites . . . . . . . . 124LAN-free data movement options . . . . 124

Unicode file spaces (Windows) . . . . . . 125Incremental backups on memory-constrainedsystems . . . . . . . . . . . . . . 125Incremental backups on systems with a largenumber of files . . . . . . . . . . . . 126Performing a backup with limited bandwidth 127Control processing with an include-exclude list 127Data encryption during backup or archiveoperations . . . . . . . . . . . . . 128Maximum file size for operations. . . . . . 129How Tivoli Storage Manager handles long userand group names . . . . . . . . . . . 129

Incremental, selective, or incremental-by-datebackups (Windows) . . . . . . . . . . . 130

Full and partial incremental backup . . . . . 130Journal-based backup. . . . . . . . . 132

Incremental-by-date backup . . . . . . . 134Comparing incremental-by-date, journal-based,and NetApp snapshot difference to fullincremental and partial incremental backups . . 134Snapshot differential backup with an HTTPSconnection . . . . . . . . . . . . . 136

Running a snapshot differential backup withan HTTPS connection . . . . . . . . 137

Selective backup . . . . . . . . . . . 137Backing up files from one or more file spaces for agroup backup (Windows) . . . . . . . . . 138Backing up data with client-node proxy support(Windows) . . . . . . . . . . . . . . 138

Enabling multiple node operations from theGUI . . . . . . . . . . . . . . . 139Setting up encryption . . . . . . . . . 140Scheduling backups with client-node proxysupport . . . . . . . . . . . . . . 140

Associate a local snapshot with a server file space(Windows) . . . . . . . . . . . . . . 141Backing up Windows system state . . . . . . 142Backing up Automated System Recovery files . . 143Preparation for Automated System Recovery . . . 144

Creating a Tivoli Storage Manager options filefor Automated System Recovery . . . . . . 144Backing up the boot drive and system drive forAutomated System Recovery . . . . . . . 145

Image backup . . . . . . . . . . . . . 146Performing prerequisite tasks before creating animage backup . . . . . . . . . . . . 147Utilizing image backups to perform file systemincremental backups . . . . . . . . . . 148

Method 1: Using image backups with filesystem incremental backups . . . . . . 148

iv IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

Method 2: Using image backups withincremental-by-date image backups . . . . 149Comparing methods 1 and 2 . . . . . . 150

Performing an image backup using the GUI . . 150Performing an image backup using thecommand line . . . . . . . . . . . . 151

Back up NAS file systems using Network DataManagement Protocol . . . . . . . . . . 151

Backing up NAS file systems with the webclient GUI using NDMP protocol . . . . . . 153Back up NAS file systems using the commandline. . . . . . . . . . . . . . . . 154Methods for backing up and recovering data onNAS file servers accessed by CIFS protocol . . 156

Support for CDP Persistent Storage Manager . . . 157Backing up VMware virtual machines . . . . . 157

Preparing the environment for full backups ofVMware virtual machines . . . . . . . . 160Creating full backups for VMware virtualmachines . . . . . . . . . . . . . . 163Preparing the environment for file-level backupsof VMware virtual machines . . . . . . . 164Creating file-level backups for VMware virtualmachines . . . . . . . . . . . . . . 166Parallel backups of virtual machines. . . . . 167

Back up virtual machines on a Hyper-V system 171Hyper-V backup support limitations. . . . . 173

Back up and archive Tivoli Storage ManagerFastBack data . . . . . . . . . . . . . 174Backing up Net Appliance CIFS share definitions 175Display backup processing status. . . . . . . 175Backup (Windows): Additional considerations . . 178

Open files . . . . . . . . . . . . . 178Ambiguous file space names in filespecifications . . . . . . . . . . . . 178Management classes . . . . . . . . . . 179Deleted file systems . . . . . . . . . . 179Removable media backup . . . . . . . . 180Fixed drives . . . . . . . . . . . . . 181NTFS and ReFS file spaces . . . . . . . . 181Universal Naming Convention names . . . . 181

Examples: UNC names in domain lists . . . 181Examples: Universal Naming Conventionbackup . . . . . . . . . . . . . 181

Microsoft Dfs file protection methods . . . . 183

Chapter 5. Restoring your data . . . . 185Duplicate file names . . . . . . . . . . . 185Universal Naming Convention names restore. . . 186Active or inactive backup restore . . . . . . . 186Restoring files and directories . . . . . . . . 187

Restoring data using the GUI . . . . . . . 187Examples for restoring data using the commandline. . . . . . . . . . . . . . . . 187

Examples: Restoring large amounts of data 189Standard query restore, no-query restore, andrestartable restore . . . . . . . . . . 189

Restoring Windows system state . . . . . . . 191Restoring Automated System Recovery files . . . 192Restoring the operating system when the computeris working . . . . . . . . . . . . . . 193

Recovering a computer when the Windows OS isnot working . . . . . . . . . . . . . . 193

Creating a bootable WinPE CD . . . . . . 193Restoring the Windows operating system withAutomated System Recovery . . . . . . . 194

Microsoft Dfs tree and file restore . . . . . . 194Restoring an image . . . . . . . . . . . 194

Restoring an image using the GUI . . . . . 195Restoring an image using the command line . . 196

Restore data from a backup set . . . . . . . 197Restore backup sets: considerations andrestrictions . . . . . . . . . . . . . 199Backup set restore . . . . . . . . . . . 200Restoring backup sets using the GUI . . . . 201Backup set restores using the clientcommand-line interface . . . . . . . . . 202

Restore Net Appliance CIFS shares . . . . . . 202Restoring data from a VMware backup . . . . . 203

Restoring full VM backups . . . . . . . . 204Scenarios for running full VM instant access andfull VM instant restore from the backup-archiveclient command line . . . . . . . . . . 205

Full VM instant restore cleanup and repairscenarios . . . . . . . . . . . . . 208Recovering from non-standard errorconditions . . . . . . . . . . . . 210

Scenario: Restoring file-level VM backups . . . 210Restoring full VM backups that were createdwith VMware Consolidated Backup . . . . . 213

Restore Windows individual Active Directoryobjects. . . . . . . . . . . . . . . . 215

Reanimate tombstone objects or restoring from asystem state backup . . . . . . . . . . 215Restoring Active Directory objects using theGUI and command line . . . . . . . . . 216Restrictions and limitations when restoringActive Directory objects . . . . . . . . . 217Preserve attributes in tombstone objects . . . 218Modifying the client acceptor and agent servicesto use the Web client . . . . . . . . . . 218

Restoring or retrieving data during a failover. . . 219Authorizing another user to restore or retrieveyour files . . . . . . . . . . . . . . . 220Restoring or retrieving files from another clientnode . . . . . . . . . . . . . . . . 221Restoring or retrieving your files to anotherworkstation . . . . . . . . . . . . . . 222Deleting file spaces . . . . . . . . . . . 223Restoring data to a point in time . . . . . . . 224Restore NAS file systems . . . . . . . . . 225

Restoring NAS file systems using the Web client 225Restoring NAS files and directories using theWeb client . . . . . . . . . . . . . 226Options and commands to restore NAS filesystems from the command line . . . . . . 228

Chapter 6. Archive and retrieve yourdata (Windows) . . . . . . . . . . 231Archive files. . . . . . . . . . . . . . 231

Snapshot backup or archive with open filesupport . . . . . . . . . . . . . . 232

Contents v

Archiving data with the GUI . . . . . . . 232Archive data examples by using the commandline. . . . . . . . . . . . . . . . 233

Associate a local snapshot with a server filespace (Windows) . . . . . . . . . . 234

Archiving data with client node proxy . . . . 234Deleting archive data . . . . . . . . . . 236

Retrieve archives . . . . . . . . . . . . 236Retrieving archives with the GUI . . . . . . 237Retrieve archive copies by using the commandline. . . . . . . . . . . . . . . . 237

Chapter 7. Tivoli Storage Managerscheduler overview . . . . . . . . . 239Examples: Blank spaces in file names in scheduledefinitions . . . . . . . . . . . . . . 240Preferential start times for certain nodes . . . . 240Scheduler processing options . . . . . . . . 241

Evaluate schedule return codes in schedulescripts . . . . . . . . . . . . . . . 242Return codes from preschedulecmd andpostschedulecmd scripts . . . . . . . . . 243

Client-acceptor scheduler services versus thetraditional scheduler services . . . . . . . . 244Set the client scheduler process to run as abackground task and start automatically at startup . 244Examples: Display information about scheduledwork . . . . . . . . . . . . . . . . 246Display information about completed work . . . 248

Examples: event logs . . . . . . . . . . 249Specify scheduling options . . . . . . . . . 252Enable or disable scheduled commands . . . . 252Change processing options used by the schedulerservice. . . . . . . . . . . . . . . . 253Manage multiple schedule requirements on onesystem . . . . . . . . . . . . . . . 253

Chapter 8. Client return codes . . . . 257

Chapter 9. Storage managementpolicies . . . . . . . . . . . . . . 259Policy domains and policy sets . . . . . . . 259Management classes and copy groups . . . . . 260Display information about management classesand copy groups . . . . . . . . . . . . 261

Copy group name attribute. . . . . . . . 261Copy type attribute . . . . . . . . . . 261Copy frequency attribute . . . . . . . . 262Versions data exists attribute . . . . . . . 262Versions data deleted attribute . . . . . . 262Retain extra versions attribute . . . . . . . 262Retain only version attribute . . . . . . . 263Copy serialization attribute . . . . . . . . 263Copy mode parameter . . . . . . . . . 264Copy destination attribute . . . . . . . . 264Retain versions attribute. . . . . . . . . 264Deduplicate data attribute . . . . . . . . 265

Select a management class for files . . . . . . 265Assign a management class to files . . . . . . 265Override the management class for archived files 266

Select a management class for directories . . . . 267Bind management classes to files . . . . . . . 267Rebind backup versions of files . . . . . . . 268Retention grace period . . . . . . . . . . 268Event-based policy retention protection. . . . . 269

Archive files on a data retention server . . . . 270

Chapter 10. Tivoli Storage ManagerClient Service Configuration Utility . . 271Install the backup-archive scheduler service . . . 271

Using the Client Service Configuration Utility(Windows) . . . . . . . . . . . . . 271

Examples: Automating backups . . . . . 271Examples: Configuring the CAD to managean existing scheduler service . . . . . . 273Creating a new scheduler and associating aCAD to manage the scheduler. . . . . . 274

dsmcutil command . . . . . . . . . . . 274Dsmcutil commands: Required options andexamples . . . . . . . . . . . . . . 275Dsmcutil valid options . . . . . . . . . 282

Chapter 11. Processing options . . . 287Processing options overview . . . . . . . . 287Communication options . . . . . . . . . . 288

TCP/IP options . . . . . . . . . . . 288Named Pipes option . . . . . . . . . . 289Shared memory options . . . . . . . . . 289

Backup and archive processing options . . . . . 289Restore and retrieve processing options. . . . . 298Scheduling options . . . . . . . . . . . 301Format and language options . . . . . . . . 302Command processing options . . . . . . . . 302Authorization options . . . . . . . . . . 303Error processing options. . . . . . . . . . 303Transaction processing options . . . . . . . 304Web client options. . . . . . . . . . . . 305Diagnostics options . . . . . . . . . . . 305Using options with commands . . . . . . . 305

Entering options with a command . . . . . 306Initial command-line-only options . . . . . 311Client options that can be set by the TivoliStorage Manager server . . . . . . . . . 312

Client options reference . . . . . . . . . . 313Absolute . . . . . . . . . . . . . . 314Adlocation . . . . . . . . . . . . . 315Archmc . . . . . . . . . . . . . . . 315Asnodename . . . . . . . . . . . . . 316Asrmode . . . . . . . . . . . . . . 318Auditlogging . . . . . . . . . . . . 319Auditlogname . . . . . . . . . . . . 321Autodeploy . . . . . . . . . . . . . 323Autofsrename . . . . . . . . . . . . 325Backmc . . . . . . . . . . . . . . . 326Backupsetname . . . . . . . . . . . . 327Basesnapshotname . . . . . . . . . . . 328Casesensitiveaware . . . . . . . . . . 329Changingretries . . . . . . . . . . . 330Class . . . . . . . . . . . . . . . 331Clientview . . . . . . . . . . . . . 332

vi IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

Clusterdisksonly . . . . . . . . . . . 333Clusternode . . . . . . . . . . . . . 335Collocatebyfilespec . . . . . . . . . . 337Commmethod . . . . . . . . . . . . . 338Commrestartduration . . . . . . . . . . 339Commrestartinterval . . . . . . . . . . 339Compressalways . . . . . . . . . . . . 340Compression . . . . . . . . . . . . . 341Console . . . . . . . . . . . . . . 342Createnewbase . . . . . . . . . . . . 344Datacenter . . . . . . . . . . . . . 345Datastore . . . . . . . . . . . . . 346Dateformat . . . . . . . . . . . . . 346Dedupcachepath . . . . . . . . . . . . 348Dedupcachesize . . . . . . . . . . . . 349Deduplication . . . . . . . . . . . . 350Deletefiles . . . . . . . . . . . . . 351Description . . . . . . . . . . . . . 351Detail . . . . . . . . . . . . . . . 353Diffsnapshot . . . . . . . . . . . . 354Diffsnapshotname . . . . . . . . . . . 355Dirmc . . . . . . . . . . . . . . . 356Dirsonly . . . . . . . . . . . . . . 357Disablenqr . . . . . . . . . . . . . 358Diskbuffsize . . . . . . . . . . . . 359Diskcachelocation . . . . . . . . . . 360Domain . . . . . . . . . . . . . . . 361Domain.image . . . . . . . . . . . . 364Domain.nas . . . . . . . . . . . . . 365Domain.vcd . . . . . . . . . . . . . 366Domain.vmfile . . . . . . . . . . . . 368Domain.vmfull . . . . . . . . . . . . 371Enable8dot3namesupport . . . . . . . . . 376Enablearchiveretentionprotection . . . . . 377Enablededupcache . . . . . . . . . . . 379Enablelanfree . . . . . . . . . . . . 380Encryptiontype . . . . . . . . . . . . 381Encryptkey . . . . . . . . . . . . . 382Errorlogmax . . . . . . . . . . . . . 384Errorlogname . . . . . . . . . . . . 385Errorlogretention . . . . . . . . . . 386Exclude options . . . . . . . . . . . 388

Controlling compression processing . . . . 391Adaptive subfile backup processing . . . . 391Processing NAS file systems . . . . . . 392Virtual machine exclude options . . . . . 392

Fbbranch . . . . . . . . . . . . . . 394Fbclientname . . . . . . . . . . . . 395Fbpolicyname . . . . . . . . . . . . 397Fbreposlocation . . . . . . . . . . . 398Fbserver . . . . . . . . . . . . . . 399Fbvolumename . . . . . . . . . . . . 400Filelist . . . . . . . . . . . . . . 402Filename . . . . . . . . . . . . . . 405Filesonly . . . . . . . . . . . . . 406Forcefailover . . . . . . . . . . . . 407Fromdate . . . . . . . . . . . . . . 408Fromnode . . . . . . . . . . . . . . 408Fromtime . . . . . . . . . . . . . . 409Groupname . . . . . . . . . . . . . 410Guitreeviewafterbackup . . . . . . . . . 410

Host . . . . . . . . . . . . . . . 411Httpport . . . . . . . . . . . . . . 411Hsmreparsetag . . . . . . . . . . . . 412Ieobjtype . . . . . . . . . . . . . 413Ifnewer . . . . . . . . . . . . . . 414Imagegapsize . . . . . . . . . . . . 415Imagetofile . . . . . . . . . . . . . 416Inactive . . . . . . . . . . . . . . 416Inclexcl . . . . . . . . . . . . . . 417

Considerations for Unicode-enabled clients 418Include options. . . . . . . . . . . . 419

Compression, encryption, and adaptivesubfile backup processing . . . . . . . 423Processing NAS file systems . . . . . . 424Virtual machine include options . . . . . 425

Incrbydate . . . . . . . . . . . . . 433Incremental . . . . . . . . . . . . . 434Incrthreshold . . . . . . . . . . . . 435Journalpipe . . . . . . . . . . . . . 436Lanfreecommmethod . . . . . . . . . . 437Lanfreeshmport . . . . . . . . . . . . 438Lanfreetcpport . . . . . . . . . . . . 439Lanfreessl . . . . . . . . . . . . . 439Lanfreetcpserveraddress . . . . . . . . 440Language . . . . . . . . . . . . . . 441Latest . . . . . . . . . . . . . . . 442Localbackupset . . . . . . . . . . . . 443Managedservices . . . . . . . . . . . 443Maxcmdretries . . . . . . . . . . . . 445Mbobjrefreshthresh . . . . . . . . . . 446Mbpctrefreshthresh . . . . . . . . . . 447Memoryefficientbackup . . . . . . . . . 448Mode . . . . . . . . . . . . . . . 449Monitor . . . . . . . . . . . . . . 454Myprimaryserver . . . . . . . . . . . 454Myreplicationserver . . . . . . . . . . 455Namedpipename . . . . . . . . . . . . 457Nasnodename . . . . . . . . . . . . . 457Nodename . . . . . . . . . . . . . . 459Nojournal . . . . . . . . . . . . . 460Noprompt . . . . . . . . . . . . . . 460Nrtablepath . . . . . . . . . . . . . 461Numberformat . . . . . . . . . . . . 462Optfile . . . . . . . . . . . . . . 464Password . . . . . . . . . . . . . . 464Passwordaccess . . . . . . . . . . . . 466Pick . . . . . . . . . . . . . . . 468Pitdate . . . . . . . . . . . . . . 468Pittime . . . . . . . . . . . . . . 469Postschedulecmd/Postnschedulecmd . . . . . 470Postsnapshotcmd . . . . . . . . . . . 472Preschedulecmd/Prenschedulecmd . . . . . 473Preservelastaccessdate . . . . . . . . . 475Preservepath . . . . . . . . . . . . 476Presnapshotcmd . . . . . . . . . . . . 478Queryschedperiod . . . . . . . . . . . 480Querysummary . . . . . . . . . . . . 481Quiet . . . . . . . . . . . . . . . 482Quotesareliteral . . . . . . . . . . . 483Replace . . . . . . . . . . . . . . 485Replserverguid . . . . . . . . . . . . 486

Contents vii

Replservername . . . . . . . . . . . . 487Replsslport . . . . . . . . . . . . . 489Repltcpport . . . . . . . . . . . . . 490Repltcpserveraddress . . . . . . . . . 491Resetarchiveattribute . . . . . . . . . 493Resourceutilization . . . . . . . . . . 494

Regulating backup and archive sessions . . 495Regulating restore sessions . . . . . . . 496Multiple client session considerations . . . 496

Retryperiod . . . . . . . . . . . . . 497Revokeremoteaccess . . . . . . . . . . 498Runasservice . . . . . . . . . . . . 498Schedcmddisabled . . . . . . . . . . . 499Schedcmdexception . . . . . . . . . . 500Schedlogmax . . . . . . . . . . . . . 501Schedlogname . . . . . . . . . . . . 503Schedlogretention . . . . . . . . . . 504Schedmode . . . . . . . . . . . . . 506Schedrestretrdisabled . . . . . . . . . 507Scrolllines . . . . . . . . . . . . . 508Scrollprompt . . . . . . . . . . . . 509Sessioninitiation . . . . . . . . . . 510Shmport . . . . . . . . . . . . . . 512Showmembers . . . . . . . . . . . . . 512Skipmissingsyswfiles . . . . . . . . . 513Skipntpermissions . . . . . . . . . . 514Skipntsecuritycrc . . . . . . . . . . 515Snapdiff . . . . . . . . . . . . . . 515Snapdiffhttps . . . . . . . . . . . . 520Snapshotproviderfs . . . . . . . . . . 522Snapshotproviderimage . . . . . . . . . 523Snapshotroot . . . . . . . . . . . . 524Srvoptsetencryptiondisabled . . . . . . . 526Srvprepostscheddisabled . . . . . . . . 527Srvprepostsnapdisabled . . . . . . . . . 528Ssl . . . . . . . . . . . . . . . . 529Sslfipsmode . . . . . . . . . . . . . 530Sslrequired . . . . . . . . . . . . . 531Ssldisablelegacytls . . . . . . . . . . 532Stagingdirectory . . . . . . . . . . . 533Subdir . . . . . . . . . . . . . . . 534Subfilebackup . . . . . . . . . . . . 536Subfilecachepath . . . . . . . . . . . 537Subfilecachesize . . . . . . . . . . . 538Systemstatebackupmethod . . . . . . . . 539Tapeprompt . . . . . . . . . . . . . 540Tcpadminport . . . . . . . . . . . . 541Tcpbuffsize . . . . . . . . . . . . . 542Tcpcadaddress . . . . . . . . . . . . 543Tcpclientaddress . . . . . . . . . . . 543Tcpclientport . . . . . . . . . . . . 544Tcpnodelay . . . . . . . . . . . . . 545Tcpport . . . . . . . . . . . . . . 546Tcpserveraddress . . . . . . . . . . . 546Tcpwindowsize . . . . . . . . . . . . 547Timeformat . . . . . . . . . . . . . 548Toc . . . . . . . . . . . . . . . . 550Todate . . . . . . . . . . . . . . . 551Totime . . . . . . . . . . . . . . . 552Txnbytelimit . . . . . . . . . . . . 553Type . . . . . . . . . . . . . . . 554

Usedirectory . . . . . . . . . . . . 554Useexistingbase . . . . . . . . . . . 555Usereplicationfailover . . . . . . . . . 556V2archive . . . . . . . . . . . . . 557Vappmc . . . . . . . . . . . . . . . 558Vcdhost . . . . . . . . . . . . . . 559Vcdpw . . . . . . . . . . . . . . . 559Vcduser . . . . . . . . . . . . . . 560Verbose . . . . . . . . . . . . . . 561Verifyimage . . . . . . . . . . . . . 562Virtualfsname . . . . . . . . . . . . 562Virtualnodename . . . . . . . . . . . 563Vmautostartvm . . . . . . . . . . . . 564Vmbackdir . . . . . . . . . . . . . 565Vmbacknodelete . . . . . . . . . . . . 566Vmbackuptype . . . . . . . . . . . . 567Vmmc . . . . . . . . . . . . . . . 568Vmbackvcbtransport . . . . . . . . . . 569Vmchost . . . . . . . . . . . . . . 570Vmcpw . . . . . . . . . . . . . . . 570Vmctlmc . . . . . . . . . . . . . . 571Vmcuser . . . . . . . . . . . . . . 572Vmdefaultdvportgroup . . . . . . . . . 573Vmdefaultdvswitch . . . . . . . . . . 574Vmdefaultnetwork . . . . . . . . . . 575Vmdiskprovision . . . . . . . . . . . 576Vmenabletemplatebackups . . . . . . . . 577Vmexpireprotect . . . . . . . . . . . 578Vmiscsiadapter . . . . . . . . . . . . 579Vmiscsiserveraddress . . . . . . . . . 580Vmlimitperdatastore . . . . . . . . . . 581Vmlimitperhost . . . . . . . . . . . . 582Vmlist . . . . . . . . . . . . . . . 583Vmmaxparallel . . . . . . . . . . . . 583Vmmountage . . . . . . . . . . . . . 584Vmnoprdmdisks . . . . . . . . . . . . 585Vmnovrdmdisks . . . . . . . . . . . . 586Vmprocessvmwithindependent . . . . . . . 587Vmprocessvmwithprdm . . . . . . . . . . 588Vmrestoretype . . . . . . . . . . . . 589Vmskipctlcompression . . . . . . . . . 592Vmskipmaxvmdks. . . . . . . . . . . 592Vmstoragetype . . . . . . . . . . . . 593Vmtempdatastore . . . . . . . . . . . 594Vmverifyifaction . . . . . . . . . . . 595Vmverifyiflatest . . . . . . . . . . . 597Vmvstortransport . . . . . . . . . . . 598Vssaltstagingdir . . . . . . . . . . . 599Vssusesystemprovider . . . . . . . . . 600Vmtimeout . . . . . . . . . . . . . 601Webports . . . . . . . . . . . . . . 602Wildcardsareliteral . . . . . . . . . . 602

Chapter 12. Using commands . . . . 605Start and end a client command session . . . . 608

Process commands in batch mode . . . . . 608Process commands in interactive mode . . . . 609

Enter client command names, options, andparameters . . . . . . . . . . . . . . 609

Command name . . . . . . . . . . . 609Options . . . . . . . . . . . . . . 610

viii IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

||||||

||||

Options in interactive mode . . . . . . 610Parameters . . . . . . . . . . . . . 610File specification syntax . . . . . . . . . 611

Wildcard characters . . . . . . . . . . . 612Client commands reference . . . . . . . . . 613Archive . . . . . . . . . . . . . . . 613

Open file support . . . . . . . . . . . 615Archive FastBack . . . . . . . . . . . . 616Backup FastBack . . . . . . . . . . . . 619Backup Group . . . . . . . . . . . . . 621Backup Image . . . . . . . . . . . . . 624

Offline and online image backup . . . . . . 626Utilizing image backup to perform file systemincremental backup . . . . . . . . . . 627

Backup NAS . . . . . . . . . . . . . 628Backup Systemstate . . . . . . . . . . . 630Backup VAPP . . . . . . . . . . . . . 632Backup VM . . . . . . . . . . . . . . 637Cancel Process . . . . . . . . . . . . . 648Cancel Restore . . . . . . . . . . . . . 648Delete Access . . . . . . . . . . . . . 649Delete Archive . . . . . . . . . . . . . 650Delete Backup . . . . . . . . . . . . . 652Delete Filespace . . . . . . . . . . . . 655Delete Group . . . . . . . . . . . . . 656Expire . . . . . . . . . . . . . . . . 658Help . . . . . . . . . . . . . . . . 659Incremental . . . . . . . . . . . . . . 661

Open file support . . . . . . . . . . . 664Journal-based backup. . . . . . . . . . 665Backing up NTFS or ReFS volume mount points 666

Backing up data on NTFS or ReFS mountedvolumes . . . . . . . . . . . . . 667

Back up Microsoft Dfs root . . . . . . . . 667Incremental-by-Date . . . . . . . . . . 668Adaptive subfile backups . . . . . . . . 668Associate a local snapshot with a server filespace . . . . . . . . . . . . . . . 668

Loop . . . . . . . . . . . . . . . . 669Macro . . . . . . . . . . . . . . . . 670Monitor Process . . . . . . . . . . . . 670Preview Archive . . . . . . . . . . . . 671Preview Backup . . . . . . . . . . . . 672Query Access . . . . . . . . . . . . . 673Query Adobjects . . . . . . . . . . . . 674Query Archive . . . . . . . . . . . . . 675Query Backup . . . . . . . . . . . . . 678

Query NAS file system images . . . . . . 681Query Backupset . . . . . . . . . . . . 681

Query Backupset without the backupsetnameparameter . . . . . . . . . . . . . 683

Query Filespace . . . . . . . . . . . . 684Query NAS file spaces . . . . . . . . . 686

Query Group . . . . . . . . . . . . . 686Query Image . . . . . . . . . . . . . 688Query Inclexcl . . . . . . . . . . . . . 690Query Mgmtclass . . . . . . . . . . . . 691Query Node. . . . . . . . . . . . . . 692

Query Options . . . . . . . . . . . . . 693Query Restore . . . . . . . . . . . . . 694Query Schedule . . . . . . . . . . . . 695Query Session . . . . . . . . . . . . . 695Query Systeminfo . . . . . . . . . . . 696Query Systemstate . . . . . . . . . . . 698Query VAPP . . . . . . . . . . . . . 699Query VM . . . . . . . . . . . . . . 703Restart Restore . . . . . . . . . . . . . 707Restore . . . . . . . . . . . . . . . 708

Restoring NTFS or ReFS volume mount points 713Restoring data on NTFS mounted volumes 713

Restore Microsoft Dfs junctions . . . . . . 714Restore active files. . . . . . . . . . . 714Universal Naming Convention restores . . . . 714Restore from file spaces that are notUnicode-enabled . . . . . . . . . . . 715Restore named streams . . . . . . . . . 715Restore sparse files . . . . . . . . . . 715

Restore Adobjects. . . . . . . . . . . . 716Restore Backupset . . . . . . . . . . . 717

Restore backup sets: considerations andrestrictions . . . . . . . . . . . . . 720Restore backup sets in a SAN environment . . 721Restore Backupset without the backupsetnameparameter . . . . . . . . . . . . . 722

Restore Group . . . . . . . . . . . . . 724Restore Image . . . . . . . . . . . . . 726Restore NAS . . . . . . . . . . . . . 729Restore Systemstate . . . . . . . . . . . 731Restore VAPP . . . . . . . . . . . . . 733Restore VM . . . . . . . . . . . . . . 736Retrieve . . . . . . . . . . . . . . . 744

Retrieve archives from file spaces that are notUnicode-enabled . . . . . . . . . . . 747Retrieve named streams . . . . . . . . . 747Retrieve sparse files . . . . . . . . . . 748

Schedule . . . . . . . . . . . . . . . 748Selective . . . . . . . . . . . . . . . 749

Open file support . . . . . . . . . . . 752Adaptive subfile backups . . . . . . . . 752Associate a local snapshot with a server filespace . . . . . . . . . . . . . . . 753

Set Access . . . . . . . . . . . . . . 753Set Event. . . . . . . . . . . . . . . 756Set password . . . . . . . . . . . . . 758

Appendix. Accessibility features forthe Tivoli Storage Manager productfamily. . . . . . . . . . . . . . . 765

Notices . . . . . . . . . . . . . . 767

Glossary . . . . . . . . . . . . . 771

Index . . . . . . . . . . . . . . . 773

Contents ix

x IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

Tables

1. Windows client communication methods . . . 62. Supported features on Windows platforms 73. Stoppable services . . . . . . . . . . 154. Client acceptor-managed services versus

traditional scheduler services. . . . . . . 345. Data deduplication settings: Client and server 536. Options for excluding file spaces and

directories . . . . . . . . . . . . . 877. Options for controlling processing using

include and exclude statements . . . . . . 888. Wildcard and other special characters . . . . 919. Specifying a drive specification using

wildcards . . . . . . . . . . . . . 9210. Using wildcard characters with include and

exclude patterns . . . . . . . . . . . 9311. Options for controlling compression and

encryption processing . . . . . . . . . 9312. UNC name patterns and DOS patterns 9713. Required user security rights for Tivoli Storage

Manager backup and restore services . . . . 9914. Working with your files using the Tivoli

Storage Manager GUI . . . . . . . . . 11115. Planning your backups . . . . . . . . 11516. Command line backup examples . . . . . 12017. Maximum file size . . . . . . . . . . 12918. Comparing incremental image backup

methods . . . . . . . . . . . . . 15019. NAS options and commands . . . . . . 15420. Backup and restore capabilities for VMware

virtual machines on Windows platforms . . 15821. Comparison of full backups and file-level

backups for VMware virtual machines onWindows systems . . . . . . . . . . 160

22. Client command line informational messages 17523. UNC examples . . . . . . . . . . . 18224. Command-line restore examples . . . . . 18725. Backup set GUI restore restrictions . . . . 19826. Backup set command-line restore restrictions 19927. Components for the restore command when

you restore files to the same computer . . . 21228. Components for the restore command when

you restore files to a different computer. . . 21229. NAS options and commands . . . . . . 22830. Command-line archive examples . . . . . 23331. Command line examples of retrieving

archives . . . . . . . . . . . . . 23732. Sample classic query schedule output 24733. Sample enhanced query schedule output 24834. Client return codes and their meanings 25735. Default attribute values in the standard

management class . . . . . . . . . . 26136. TCP/IP options . . . . . . . . . . . 28837. Named Pipes communication option 28938. Shared memory communication options 28939. Backup and archive processing options 28940. Restore and retrieve processing options 298

41. Scheduling options. . . . . . . . . . 30142. Format and language options . . . . . . 30243. Command processing options . . . . . . 30344. Authorization options. . . . . . . . . 30345. Error processing options . . . . . . . . 30346. Transaction processing options . . . . . . 30447. Web client options . . . . . . . . . . 30548. Diagnostics options . . . . . . . . . 30549. Client command options . . . . . . . . 30750. Options that are valid on the initial command

line only . . . . . . . . . . . . . 31251. Options that can be set by the Tivoli Storage

Manager server . . . . . . . . . . . 31352. Setting the value of the asnodename option to

distribute backups.. . . . . . . . . . 31653. Clusternode and clusterdisksonly

combinations. . . . . . . . . . . . 33554. Interaction of domain definitions from several

sources. . . . . . . . . . . . . . 36455. System services components and

corresponding keywords . . . . . . . . 39056. Other optional parameters . . . . . . . 42257. Incremental command: Related options 51758. Effects of server and client SSL settings on

success or failure of login attempts . . . . 53259. Commands . . . . . . . . . . . . 60560. Wildcard characters . . . . . . . . . 61261. Archive command: Related options . . . . 61462. Archive FastBack command: Related options 61763. Backup FastBack command: Related options 62064. Backup Group command: Related options 62365. Backup Image command: Related options 62566. Backup NAS command: Related options 63067. Backup VAPP command: Related options 63468. Delete Archive command: Related options 65169. Delete Backup command: Related options 65470. Delete Filespace command: Related options 65671. Delete Group command: Related options 65772. Expire command: Related options. . . . . 65973. Incremental command: Related options 66274. Query Adobjects command: Related options 67475. Query Archive command: Related options 67676. Query Backup command: Related options 67977. Query Backupset command: Related options 68278. Query Backupset command: Related options 68479. Query Filespace command: Related options 68580. Query Group command: Related options 68781. Query Image command: Related options 68982. Query Mgmtclass command: Related options 69283. Query Node command: Related options 69384. Query Options command: Related options 69385. Query Systeminfo command: Related options 69786. Query Systemstate command: Related options 69887. Restore VAPP command: Related options 70188. Query VM command: Related options for

VMware virtual machine queries. . . . . . 703

© Copyright IBM Corp. 1993, 2015 xi

89. Query VM command: Related options forHyper-V virtual machine queries. . . . . . 706

90. Restore command: Related options . . . . 71191. Restore Adobjects command: Related options 71692. Restore Backupset command: Related options 71993. Restore Group command: Related options 72594. Restore Image command: Related options 72895. Restore NAS command: Related options 73096. Restore Systemstate command: Related

options . . . . . . . . . . . . . 732

97. Restore VAPP command: Related options 73598. Restore VM command: Related options when

restoring VMware virtual machines . . . . 73999. Restore VM command: Related options when

restoring Hyper-V virtual machines . . . . 742100. Retrieve command: Related options . . . . 745101. Schedule command: Related options . . . . 749102. Selective command: Related options . . . . 751

xii IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

About this publication

IBM® Tivoli® Storage Manager is a client/server licensed product that providesstorage management services in a multiplatform computer environment.

The backup-archive client program enables users to back up and archive files fromtheir workstations or file servers to storage, and restore and retrieve backupversions and archived copies of files to their local workstations.

In addition to the backup-archive client, Tivoli Storage Manager includes thefollowing components:v A server program that acts as a backup and archive server for distributed

workstations and file servers.v An administrative client program that you can access from a web browser or

from the command line. The program enables a Tivoli Storage Manageradministrator to control and monitor server activities, define storagemanagement policies for backup, archive, and space management services, andset up schedules to perform those services at regular intervals.

v An application programming interface (API) that you can use to enhance anexisting application with storage management services. When an application isregistered with a server as a client node, the application can back up, restore,archive, and retrieve objects from storage.

v A web backup-archive client that enables an authorized administrator, help deskperson, or other users to perform backup, restore, archive, and retrieve servicesby using a web browser on a remote system.

Who should read this publicationThis publication provides instructions for a user to install, configure, and use theTivoli Storage Manager client.

Unless otherwise specified, references to Windows refer to all supported MicrosoftWindows operating systems.

PublicationsThe Tivoli Storage Manager product family includes IBM Tivoli StorageFlashCopy® Manager, IBM Tivoli Storage Manager for Space Management, IBMTivoli Storage Manager for Databases, and several other storage managementproducts from IBM.

To view IBM product documentation, see www.ibm.com/support/knowledgecenter.

Conventions used in this publicationThis publication uses the following typographical conventions:

Example Description

autoexec.ncfhsmgui.exe

A series of lowercase letters with an extension indicates program filenames.

© Copyright IBM Corp. 1993, 2015 xiii

http://www.ibm.com/support/knowledgecenterhttp://www.ibm.com/support/knowledgecenter

Example Description

DSMI_DIR A series of uppercase letters indicates return codes and other values.

dsmQuerySessInfo Boldface type indicates a command that you type on a command line,the name of a function call, the name of a structure, a field within astructure, or a parameter.

timeformat Boldface italic type indicates a Tivoli Storage Manager option. Thebold type is used to introduce the option, or used in an example.

dateformat Italic type indicates an option, the value of an option, a new term, aplaceholder for information you provide, or for special emphasis in thetext.

maxcmdretries Monospace type indicates fragments of a program or information as itmight appear on a display screen, such a command example.

plus sign (+) A plus sign between two keys indicates that you press both keys at thesame time.

Reading syntax diagramsTo read a syntax diagram for entering a command, follow the path of the line.Read from left to right and from top to bottom.v The ��─── symbol indicates the beginning of a syntax diagram.v The ───� symbol at the end of a line indicates that the syntax diagram continues

on the next line.v The �─── symbol at the beginning of a line indicates that a syntax diagram

continues from the previous line.v The ───�� symbol indicates the end of a syntax diagram.

Syntax items, such as a keyword or a variable, can be:v On the line (required element)v Above the line (default element)v Below the line (optional element)

Symbols

Enter these symbols exactly as they appear in the syntax diagram.v * Asteriskv { } Bracesv : Colonv , Commav = Equal Signv - Hyphenv () Parenthesesv . Periodv Spacev " quotation markv 'single quotation mark

xiv IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

Variables

Italicized lowercase items such as indicate variables. In this example,you can specify a when you enter the cmd_name command.

�� cmd_name ��

Repetition

An arrow returning to the left means that the item can be repeated. A characterwithin the arrow means that you must separate repeated items with that character.

��

,

repeat ��

A footnote (1) by the arrow refers to a limit that tells how many times the item canbe repeated.

��

,(1)

repeat ��

Notes:

1 Specify repeat up to 5 times.

Required choices

When two or more items are in a stack and one of them is on the line, you mustspecify one item.

In this example, you must choose A, B, or C.

�� cmd_name ABC

��

Optional choices

When an item is below the line, that item is optional. In the first example, you canselect A or nothing at all.

�� cmd_nameA

��

When two or more items are in a stack below the line, all of them are optional. Inthe second example, you can choose A, B, C, or nothing at all.

About this publication xv

�� cmd_nameABC

��

Repeatable choices

A stack of items followed by an arrow returning to the left indicates that you canselect more than one item, or in some cases, repeat a single item.

In this example, you can select any combination of A, B, or C.

��

,

cmd_name ABC

��

Defaults

Defaults are above the line. The default is selected unless you override it, or youcan select the default explicitly. To override the default, include an option from thestack below the line.

In this example, A is the default. Select either B or C to override A.

��A

cmd_nameBC

��

xvi IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

New for IBM Tivoli Storage Manager Version 7.1.2

Tivoli Storage Manager backup-archive client version 7.1.2 contains new featuresand changes.

Changed and new information is indicated by a vertical bar (|) to the left of thechange. Ensure that you are using the correct edition for the level of the product.v For VMware backup operations, an INCLUDE.VMSNAPSHOTATTEMPS client option has

been added. This option determines the total number of snapshot attempts to tryfor a VMware virtual machine that fails during backup processing, due to asnapshot failure.For a description of the option settings, see theINCLUDE.VMSNAPSHOTATTEMPTS topic.

v The documentation has been updated to include information from APARs.

© Copyright IBM Corp. 1993, 2015 xvii

|

|

||

||

||||

||

|

xviii IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide

Chapter 1. Installing the Tivoli Storage Managerbackup-archive clients

The IBM Tivoli Storage Manager backup-archive client helps you protectinformation on your workstations.

You can maintain backup versions of your files that you can restore if the originalfiles are damaged or lost. You can also archive infrequently used files, preservethem in their current state, and retrieve them when necessary.

The Tivoli Storage Manager clients work in conjunction with the Tivoli StorageManager server. Contact your Tivoli Storage Manager server administrator toobtain backup or archive access to the server, or refer to the server publications toinstall and configure a Tivoli Storage Manager server.

Upgrading the backup-archive clientThe following sections explain what you need to do if you are upgrading to IBMTivoli Storage Manager backup-archive client Version 7.1.2 from a previous version.

Upgrade path for clients and serversTivoli Storage Manager clients and servers can be upgraded at different times. Thecombination of servers and clients that you deploy must be compatible with eachother.

To prevent disruption of your backup and archive activities while you upgradefrom one release to another, follow the compatibility guidelines for Tivoli StorageManager clients and servers. These guidelines are available on the web; to view theguidelines browse to http://www.ibm.com/support/docview.wss?uid=swg21053218.

Considerations for migrating between processor architecturesx32 and x64

When migrating between the Tivoli Storage Manager processor architectures (x32and x64), there are some items that you need to consider for a successful migrationfrom one architecture to another.

Consider the following items when migrating from one processor architecture toanother:v The restore of DFS links backed up from 32-bit Windows environments to 64-bit

Windows environments, is not supported.v The restore of DFS links backed up from 64-bit Windows environments to 32-bit

Windows environments, is not supported.v System state data is incompatible between different processor architectures.

Therefore, when migrating client data between different processor architectures,avoid backing up the system state data from one architecture into the same filespaces containing the system state data from another architecture. To avoidcommingling the data, you can do either of the following before the migration:– Ask your Tivoli Storage Manager administrator to rename the existing system

state file spaces. Once the migration is complete and you have new backups

© Copyright IBM Corp. 1993, 2015 1

http://www.ibm.com/support/docview.wss?uid=swg21053218http://www.ibm.com/support/docview.wss?uid=swg21053218

of the system state data, your Tivoli Storage Manager administrator can deletethe renamed file spaces. The file spaces to rename include one or more of thefollowing:- SYSTEM STATE- SYSTEM SERVICES- ASRAsk your Tivoli Storage Manager administrator to delete the existing filespaces for your node.

v Renamed file spaces remain on the server and managed as stabilized file spaces.These file spaces contain all the original data, which can still be restored untilthe file spaces are deleted.

v When an existing file space is renamed during Unicode conversion, any accessrules defined for the file space remain applicable to the original file space. Newaccess rules must be defined to apply to the new Unicode file space, if necessary.

v When backing up files to a file space that is not Unicode-enabled, theUnicode-enabled client skips the files and directories with names containingcharacters from a code page other than the current locale.

v If files and directories with names containing characters from a code page otherthan the current locale were previously backed up with a client that was notUnicode-enabled, Tivoli Storage Manager expires them in the file space that isnot Unicode-enabled. However, the Unicode-enabled client can back up orarchive these files to a Unicode-enabled file space.

v When migrating from a client that is not Unicode-enabled to a Unicode client,file names with double-byte characters mixed with single-byte characters mightbe restored in mixed single-byte character set (SBCS) format. This is only adisplay issue.

v When a client performs a selective backup of an object and the original filespace is renamed, the new Unicode-enabled file space contains only that object.Tivoli Storage Manager backs up all other directories and file spaces during thenext full incremental backup.

v The Unicode-enabled client has a file and directory name size limitation of 504bytes. Depending on the Unicode characters (2-byte, 3-byte, or 4-byte) used, thistranslates to a maximum of 126 to 252 characters.

Important:If you do not follow the migration instructions properly, you might have two filespaces, one Unicode and one non-Unicode, with different file space identifiers(fsID) for the same client volume. In this case, the Tivoli Storage Manager clientuses the non-Unicode file space as the default file space for backup and restoreoperations.

Additional upgrade informationWhen you upgrade a Tivoli Storage Manager client, there are additional things toconsider before you use the new client software.

When you install the web client, you must install the web-client language files thatcorrespond to those languages you want to use. To view the online help from theweb client applet in languages other than English, you must install the languageversions of the help files on the agent, the system where the Tivoli StorageManager backup-archive client was installed. If the language versions are notinstalled or are not available, the online help is displayed in English.

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

The size of the buffer to record change notifications for a particular journal filesystem (DirNotifyBufferSize) has changed. The default value is 16 KB.

For a list of new and changed messages since the previous Tivoli Storage Managerrelease, see the client_message.chg file in the client package.

Automatic backup-archive client deploymentThe Tivoli Storage Manager server administrator can automatically deploy abackup-archive client to workstations that already have the backup-archive clientinstalled.

When you schedule automatic Backup-Archive client deployments, the updatedclient packages (which include the client components and the API library) areinstalled on the workstations that receive them. A dependency check is performedby the client installation program to ensure that the API library does not conflictwith the client package that is already installed.

Tivoli Storage Manager for ERP applications do not use the same installationtechnology that is used by the client installation program. Because of that, theclient installation dependency check is not able to detect whether the API librarythat is being used by the Tivoli Storage Manager for ERP applications iscompatible with the API library that will be installed by automatic clientdeployments. If a client package is automatically deployed to and installed on aworkstation, the API library that is installed might not be compatible with the APIlibrary that was installed by the Tivoli Storage Manager for ERP application. Thenewly deployed API library can cause the Tivoli Storage Manager for ERPapplications to fail.

Do not schedule automatic client deployments to workstations that have a TivoliStorage Manager for ERP application installed on them.

The Tivoli Storage Manager server can be configured to automatically upgradebackup-archive clients on Windows computers. The existing clients must be atversion 5.4, or later.

You can use the autodeploy option to conditionally enable automatic clientdeployment, if the deployment does not require a restart of the client workstation.

By default, the autodeploy option is enabled, and the client workstation is restartedif required.

The autodeploy option can be set in the following places:v In the Administration Center. However, starting with Tivoli Storage Manager

Version 7.1, the Administration Center component is no longer included in TivoliStorage Manager distributions. If you have an Administration Center from aprevious server release, you can continue to use it to set the autodeploy optionon schedules that deploy client updates. If you do not already have anAdministration Center installed, you can download the previously-releasedversion from ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATEST. For information about theAdministration Center, see the Tivoli Storage Manager Version 6.3 serverdocumentation.

v On a schedule definition. Schedules are defined on the server. Scheduledefinitions that deploy client software updates have an action=deploy statement.

Chapter 1. Installing the Tivoli Storage Manager backup-archive clients 3

ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATESTftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATEST

On those schedules, you can include the autodeploy option as part of thecommand that you include on the –postnschedulecmd statement.

v On the client node, in an options file that is associated with the client scheduleror client acceptor daemon. The deployment manager detects options files thatare associated with the scheduler or client acceptor daemon. If there are multiplescheduler or client acceptor daemon processes running on the same computer atthe same time, and the processes use different options files, the deploymentmanager uses the autodeploy value that is set in one of the options files.

v On the client in the client options file (dsm.opt). The autodeploy option that isset in the client options file overrides any other autodeploy setting.

To use automatic deployment but not restart the system, specify the autodeploynoreboot option.

Important: For automatic client deployment to be operational, the followingconditions apply:v The client computer must have a minimum of 2 GB free disk space.v The passwordaccess option must be set to generate.

To store the password in the local Windows registry, a user must log on from thelocal workstation once, to provide the password. If the client automaticdeployment process cannot find the node password in the registry, the followingevents occur:– The deployment process does not start.– A warning message is logged in the setup.log file.

The following messages are examples of the messages that can be loggedduring a deployment.Sun 10/11/2009 10:16:04.35 The deployclient.bat script is started.Sun 10/11/2009 10:16:04.37 deployclient.bat is removing the deployment

manager and temporary files possibly left from the previous installation.Sun 10/11/2009 10:17:10.53 WARNING: Still waiting for the result of query

system information.Ensure that "PASSWORDACCESS GENERATE" is set in the client options fileand that a connection to the server can be made without being promptedfor a password.

If you see these errors and PASSWORDACCESS is set to GENERATE, the errors areprobably caused by a network problem (the client cannot be reached) or theremight be a problem with the digital rights management subkey. The digitalrights management key is in the registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM.

– The dsmc query systeminfo command is left running.– The deployment process cannot start, so no messages are sent to the server.

v The client is deployed from the server as a scheduled task; the client schedulermust be running.The scheduler must be started as a Windows service and not from the commandline. To minimize the chance of a restart, the deployment manager shuts downthe scheduler service before the new client is installed, and restarts the schedulerservice after the installation. If the scheduler is not run as a Windows service, arestart is required when the client is deployed.

v The automatic client deployment feature stops and restarts scheduler and CADprocesses on the client, but it does not stop or restart any client operations, suchas a backup or a restore. It is possible that in-process client operations could beaffected during an automatic deployment. To prevent an automatic deployment


from interfering with client operations, schedule automatic client deployments tooccur when it is not likely that the client is performing a backup or restore, orarchive or retrieve operation.

v The client is deployed as a postschedule operating system command; scheduledoperating system commands must be enabled on the client.You must configure your server to perform backup-archive client automaticdeployments. See the Tivoli Storage Manager server documentation forinstructions.

v The command-line Windows registry utility (reg.exe) is required. This tool isgenerally installed as part of the operating system installation on supportedWindows platforms.

v The Windows cluster services environment is not supported.v To turn off automatic client deployment, add autodeploy no to the client options

file.The autodeploy option is only available for Tivoli Storage Manager clientsversion 6.2 and later.

When you perform automatic client deployments from the Tivoli Storage ManagerServer, the scheduler installs the updated client by running a command that isspecified on a postschedulecmd option that is associated with the schedule. Bydefault, the log and trace files for a deployment operation are written to the client'sdisk in C:\Program Files\Tivoli\TSM\IBM_ANR_WIN\Vxxxx\log; where xxxxrepresents the version for the newly deployed client.

If you did not use the default installation directory when you installed the client,when an automatic client deployment is performed, the log and trace data for thedeployment operation are still copied to the IBM_ANR_WIN\Vxxxx\log folder, andthis folder is created one directory level up (../) from where the client executablefiles (dsm.exe, dsmc,exe, dsmcad.exe, and so on) were installed. For example, if youoriginally installed the client into E:\IBM\Tivoli\baclient, the log and trace filesresulting from the automatic deployment are created in E:\IBM\Tivoli\IBM_ANR_WIN\Vxxxx\log folder.

A lock file is also created on each client to prevent a client from being updated bydifferent deployment managers at the same time. Before a deployment begins, thedeployment manager looks on the client for the lock file. If the file exists and isless than 24 hours old, the deployment is canceled. If the lock file is more than 24hours old or does not exist, the deployment is started. The lock file is deletedwhen the deployment completes. If the deployment manager fails to delete thelock file, you can manually delete it from the client’s disk. The lock file location isinstall_dir\..\IBM_ANR_WIN\mutext.txt.Related reference:“Autodeploy” on page 323

Client environment requirementsEach of the Tivoli Storage Manager clients has hardware and softwarerequirements.

The following list shows the location of the environment prerequisites for eachsupported platform.v “NDMP support requirements (Extended Edition only)” on page 8


For current information about the client environment prerequisites for all of thesupported Tivoli Storage Manager client platforms, go to the website athttp://www.ibm.com/support/docview.wss?&uid=swg21243309

Windows client environment requirementsThis section contains client environment information, Tivoli Storage Manager clientcomponents, and hardware and software requirements for the supported Windowsplatforms.

Windows client installable componentsThe Tivoli Storage Manager backup-archive client is comprised of severalinstallable components.

The installable components for the Windows client are as follows:v Tivoli Storage Manager backup-archive command line clientv Tivoli Storage Manager administrative clientv Tivoli Storage Manager backup-archive client Graphical User Interface, which

uses Oracle Java™ technologyv Tivoli Storage Manager backup-archive web clientv Tivoli Storage Manager API (32-bit and 64-bit)v VMware vStorage API runtime files. These files are required if you are using a

backup-archive client node to act as a data mover node that protects VMwarevirtual machines. Windows data mover nodes must have the 64-bit Windowsclient installed on them.

System requirements for Windows clientsThe Tivoli Storage Manager Windows client requires a minimum amount of diskspace for installation and a supported operating system.

For software and hardware requirements for all supported versions of TivoliStorage Manager Microsoft Windows clients, including the most recent fix packs,see Microsoft Windows Client Requirements athttp://www.ibm.com/support/docview.wss?uid=swg21197133.

Windows client communication methodsThe TCP/IP and shared memory communication methods are available for theWindows backup-archive client.

You can use the following communication methods with the Tivoli StorageManager Windows client:

Table 1. Windows client communication methods

To use this communicationmethod:

Install this software: To connect to these TivoliStorage Manager servers:

TCP/IP TCP/IP (Standard with allsupported Windows

AIX®, HP-UX IA, Linux,Solaris, Windows

Named Pipes Named Pipes (Standard withall supported Windowsplatforms)

Windows

Shared Memory TCP/IP (Standard with allsupported Windowsplatforms)

Windows


http://www.ibm.com/support/docview.wss?&uid=swg21243309http://www.ibm.com/support/docview.wss?uid=swg21197133

Backup-archive client features that are available on WindowsplatformsThis topic lists which features are supported or not supported on the variousWindows platforms.

Table 2 shows the supported and unsupported features on the various Windowsplatforms.

Table 2. Supported features on Windows platforms

Features32-bit:

Windows 7

64-bit:

Windows 7

32-bit:

Windows 8

WindowsServer 2008

WindowsServer Core2008

64-bit:

Windows 8

WindowsServer 2008

WindowsServer 2008 R2

WindowsServer 2012



Journal-based backup yes yes yes yes

Online image backup yes yes yes yes

Offline image backup yes yes yes yes

System state support with VolumeShadowcopy Services (VSS)

yes yes yes yes

LAN-free operations no no yes yes

Automated System Recovery (ASR) yes BIOS: yes

UEFI: yes

yes BIOS: yes

UEFI: yes

Open File Support (OFS) yes yes yes yes

Windows supported file systemsThe Tivoli Storage Manager Windows backup-archive client is supported onspecific file systems.

The Tivoli Storage Manager Windows Backup-Archive Client supports thefollowing types of file systems:v GPFS™

Important: The Tivoli Storage Manager Windows backup-archive client canbackup or restore files in a Windows-only GPFS cluster. If the GPFS clustercontains mixed nodes (some AIX, some Linux, and some Windows), you mustuse the AIX or Linux clients to protect data in the cluster.

v File Allocation Table (FAT and FAT32)v Microsoft New Technology File System (NTFS)v Microsoft Resilient File System (ReFS). ReFS was introduced on Windows Server

2012 systems.


NDMP support requirements (Extended Edition only)You can use the Network Data Management Protocol (NDMP) to back up andrestore network attached storage (NAS) file systems to tape drives or libraries thatare locally attached to Network Appliance and EMC Celerra NAS file servers.

NDMP support is available only on IBM Tivoli Storage Manager Extended Edition.

NDMP support requires the following hardware and software:v Tivoli Storage Manager Extended Editionv Tape drive and tape library. For supported combinations, go to:

http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.html

Installation requirements for backing up and archiving Tivoli StorageManager FastBack client data

Before you can back up or archive your FastBack client data, you must install therequired software.

You must install the following software:v Tivoli Storage Manager FastBack V6.1v Tivoli Storage Manager client V6.1.3.x (where x is 1 or higher) or V6.2 or laterv Tivoli Storage Manager server V6.1.3 or higherv Tivoli Storage Manager Administration Center V6.1.3

– Required only if you want to use integrated Tivoli Storage Manager FastBack- administration.Starting with Tivoli Storage Manager V7.1, the Administration Centercomponent is no longer included in Tivoli Storage Manager distributions.FastBack users who have an Administration Center from a previous serverrelease, can continue to use it to create and modify FastBack schedules. If youdo not already have an Administration Center installed, you can downloadthe previously-released version from ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATEST. If you do notalready have an Administration Center installed, you must create and modifyFastBack schedules on the Tivoli Storage Manager server. For informationabout creating schedules on the server, see the Tivoli Storage Manager serverdocumentation.

The Tivoli Storage Manager FastBack environment must be running. Forinformation about installing and setting up Tivoli Storage Manager FastBack, seeTivoli Storage Manager FastBack Installation and User's Guide, at:http://www.ibm.com/support/knowledgecenter/SS9NU9

For information about integrating Tivoli Storage Manager and Tivoli StorageManager FastBack, see the IBM Tivoli Storage Manager Integration Guide for TivoliStorage Manager Fastback.

You can install Tivoli Storage Manager client in one of the following ways:v Install Tivoli Storage Manager client on a workstation where the FastBack server

is installed. In this case, the prerequisites are: the FastBack server, the FastBackshell, and the FastBack mount.


http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.htmlftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATESTftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATESThttp://www.ibm.com/support/knowledgecenter/SS9NU9

v Install Tivoli Storage Manager client on a workstation where the FastBack DRHub is installed. In this case, the prerequisites are: the FastBack DisasterRecovery Hub setup, the FastBack shell, and the FastBack mount.

v Install Tivoli Storage Manager client on a workstation where neither theFastBack server or the FastBack Disaster Recovery Hub is installed. In this case,ensure that the FastBack shell and the FastBack mount are installed.

Related concepts:“Configuring the client to back up and archive Tivoli Storage Manager FastBackdata” on page 64

Client configuration wizard for Tivoli Storage Manager FastBackThe IBM Tivoli Storage Manager Backup-Archive client provides a wizard toconfigure the backup-archive client for Tivoli Storage Manager FastBack.

The wizard is available in a remote application (the Web client) and in a localapplication (the Java GUI). The wizard helps you set the options to send FastBackclient data to the Tivoli Storage Manager server on a scheduled basis.

You can use the Tivoli Storage Manager Client Configuration wizard for TivoliStorage Manager FastBack on 32-bit Windows systems that are supported by bothTivoli Storage Manager and FastBack. The configuration wizard must be installedon the same workstation where the FastBack server resides, or where a FastBackDisaster Recovery Hub is deployed. You can use the client configuration wizard forTivoli Storage Manager FastBack with Tivoli Storage Manager FastBack V5.5.1 orlater versions.Related concepts:“Configuring Tivoli Storage Manager to protect FastBack client data” on page 65

Installing the Tivoli Storage Manager Windows clientYou can install the Tivoli Storage Manager Windows client from the product DVD,or other installation media.

Before you begin a Tivoli Storage Manager Windows client installation, ensure thatthe system that you want to install the client on meets the client requirements.Then, determine the type of installation that you need to perform, and follow thesteps in the appropriate procedure.

Hardware and software requirements for the Tivoli Storage Manager for WindowsBackup-Archive Client are maintained on the web at http://www.ibm.com/support/docview.wss?uid=swg21197133

Windows client installation might require a rebootAs part of the Windows client installation process, one or more Microsoft C++redistributable packages are installed, if they are not already installed on theWindows workstation. These packages can also be automatically updated by theWindows Update service. If the packages are updated, the update can cause thesystem to reboot when you start the Windows client installation program.

The reboot that is triggered if the C++ redistributable packages are updated canoccur, even under any of the following conditions:v An automatic client deployment pushes a client upgrade to a node, and the

client or the scheduler sets the AUTODEPLOY=NOREBOOT option.


http://www.ibm.com/support/docview.wss?uid=swg21197133http://www.ibm.com/support/docview.wss?uid=swg21197133

v A manual installation or upgrade of the client is started.v A client silent installation is started, even if the options to suppress reboot

prompts, and the client reboot itself, are set.

Additionally, because the Microsoft Visual Studio C++ redistributable package is ashared Windows component, other applications that have dependencies on thepackage might be stopped or restarted by Windows as part of the installation orupgrade of the C++ redistributable package. Schedule client installations andupgrades during a maintenance window when other applications will not beadversely affected if they are stopped or restarted when the C++ redistributablepackage is installed. Monitor other applications after the client is installed to seewhether there are any applications that were stopped and not restarted.

Installation typesThe procedure that you follow to install the Tivoli Storage Manager Windowsbackup-archive client depends on the type of installation that you want to perform.

Procedures are provided for each of the following installation types:

Installation type Installation description

Installing the Windows client for the firsttime

Describes how to install the Tivoli StorageManager Windows backup-archive client forthe first time. This procedure presumes thatthe Windows computer that you areinstalling the client on has never had aprevious version of the client installed on itbefore.

Upgrading the Windows client Describes how to upgrade an earlier versionof the Tivoli Storage Manager Windowsbackup-archive client to Version 7.1.2.

Reinstalling the Windows client Describes how to reinstall the Version 7.1.2Windows backup-archive client if youuninstalled it.

Silent installation Describes how to install the Version 7.1.2client silently, without user interactionduring the installation procedure.

Repairing, modifying, or uninstalling theWindows client

Describes how to add or remove featuresfrom an installed client (modify), replacedamaged files or missing registry keys(repair) or uninstall the Windows client.

Installing the Windows client for the first timeComplete this procedure to install the Tivoli Storage Manager Windowsbackup-archive client for the first time.

If you have an earlier version of the Tivoli Storage Manager Windowsbackup-archive client that is already installed on a node and you want to upgradeit to version 7.1.2, see “Upgrading the Windows client” on page 14.

Important: You must know the host name or IP address of the Tivoli StorageManager server, the port number that the server listens on for clientcommunications, and the communications method to use when the clientcommunicates with the server. Obtain this information from your Tivoli StorageManager server administrator before you start this procedure.


1. Install the product by using the installation DVD or by using the compressedinstallation file that you download from IBM.

Option Description

Install from a DVD 1. Insert the DVD into the DVD drive.

2. If the installation program does notautomatically start, browse the DVD tolocate the setup.exe file. Double-click thesetup.exe file.

Install by using a compressed installationfile

1. The Tivoli Storage Manager version 7.1.2release notes contain a link to adocument that describes how todownload the Windows backup-archiveclient distribution package from the IBMPassport Advantage® website. Follow thedirections in that document to obtain therequired files.

2. Copy the compressed installation file thatyou downloaded from PassportAdvantage a local disk or to anetwork-accessible share.

3. Double-click the compressed installationfile.

4. Specify a directory location for theuncompressed files and click Next. Bydefault, this directory is the current diskdrive, in drive:\tsm_images\TSM_BA_Client directory. If theinstallation program detects files fromanother client installation attempt in thisdirectory, you are prompted to determinewhether you want to overwrite the oldfiles. If you receive this prompt, selectYes to All to overwrite the existing files;this selection ensures that only the filesfrom the current installation are used.

2. Select a language to use for this installation and click OK.3. If the installation wizard indicates that one or more Microsoft C++

redistributable files must be installed, click Install. These files are needed torun the Windows client.

4. On the Tivoli Storage Manager client welcome screen, click Next to begininstalling the client software.

5. Accept the default installation directory by clicking Next, or specify a differentinstallation directory. The default installation directory is C:\ProgramFiles\Tivoli\TSM.

6. Select the installation type: Typical or Custom.


Option Description

Typical A typical installation installs the followingcomponents:

v The backup-archive client GUI files(needed to use the Java GUI)

v The backup-archive client web files(needed to use the web client)

v The client API files (as needed by yourclient and operating system)

Custom A custom installation installs the same filesas a typical installation. However, you canchoose to install the following optionalcomponents:

v The API SDK files (only needed if you aredeveloping applications that work withthe Tivoli Storage Managerbackup-archive client

v The Administrative Client command-linefiles (required to remotely runadministrator functions on the TivoliStorage Manager server

v VMware vStorage API runtime files(needed if you are using this client toback up VMware virtual machines)

7. Click Next, then click Install.8. When the installer completes the installation, click Finish.9. Verify the installation. Click Start > All Programs > Tivoli Storage Manager.

The client components that you installed are shown in the list of TivoliStorage Manager startable programs. The administrative command-line client,backup-archive command-line client, and the backup-archive GUI are the onlycomponents that are displayed in this list. The administrative command-lineclient is only shown if you perform a custom installation and you include theadministrative command-line client. If you installed other components, suchas the API, SDK, or VMware vStorage API runtime files, they are not shownin this list.

10. Click Backup-Archive GUI to start the client GUI. The TSM Client OptionsFile Configuration Wizard starts. Click Next to start the wizard.

11. On the Options File Task screen, select Create a new options file and clickNext.

12. On the TSM Node Name screen, specify a node name. A node name uniquelyidentifies your node to the Tivoli Storage Manager server. The default nodename is the short host name of the Windows computer that you are installingthe client on. Accept the default node name or specify a new node name.Click Next.

13. On the TSM Client/Server Communications screen, specify thecommunications method to use when the client communicates with the serverand click Next. This information must be provided to you by your TivoliStorage Manager administrator. If you are not sure what to select, accept thedefault setting (TCP/IP). If the default setting does not work when the clientattempts to connect to the server, contact the Tivoli Storage Manager serveradministrator to determine which communications method to specify.


14. On the TCP/IP Options screen, specify the server address and portinformation that your Tivoli Storage Manager administrator provided to you.In the Server Address field, specify the IP address or host name of the TivoliStorage Manager server. In the Port Number field, specify the port numberthat the server listens on for client communications. Click Next.

15. The Recommended Include/Exclude List screen contains a list of system filesand directories that are typically included, or excluded from client operations.The excluded files are typically not required to restore your system. You canselect or clear all default selections. Alternatively, you can use the Shift andCtrl keys to selectively include objects. To facilitate the installation process,click Select All; you can add or remove files from this list later, if you wantto. Click Next.

16. The Common File Exclusion Selection screen provides a default list of fileextensions that you can exclude from client operations. The file extensions thatare provided in this list are typically large files, like graphics or multimediaextension. These files consume server disk space but they might not berequired to restore critical data. Click Select All to exclude all of the defaultfile extensions. Alternatively, you can use the Shift and Ctrl keys to selectivelychoose which extensions to exclude from client operations. Click Clear All toclear any extensions that you selected. You can modify these extensions later ifyou want to. Click Next.

17. The Domains for Backup screen specifies the default file systems and objectsto include in client operations for incremental and image backups.a. In the Backup Type field, select Incremental. By default, Back up all local

file systems is selected. If you do not want to back up all local file systemsas the default action during incremental backups, clear this option andindividually select the file systems to include. You can override the defaultselection when you initiate an incremental backup operation.

b. In the Backup Type field, select Image. By default, Back up all local filesystems is selected. If you do not want to back up all local file systems asthe default action during image backups, clear this option and individuallyselect the file systems to include. You can override the default selectionwhen you initiate an image backup operation.

c. Click Next.18. On the Confirm and apply your configuration screen, click Apply. The Login

into a TSM server screen displays and prompts you to enter a user ID andpassword to log on to the Tivoli Storage Manager server. The user ID defaultsto the node name that you specified in step 12 on page 12.

19. You can accept the default user ID or specify a different user ID. Specify thepassword that you will use when you log on to the server. Click Login. Whathappens next depends on whether the Tivoli Storage Manager server isconfigured for open or closed registration.


Option Description

Server is configured for open registration The Register New Node screen prompts youfor contact information and it prompts youagain for the password.

Adding text to the Contact Information fieldis optional, but suggested; specify yourname.

Re-enter your password, twice, in the twoPassword fields. If the password that youenter and confirm in these Password fieldsdoes not match what you previouslyspecified in the Login into a TSM serverscreen, the password that you specify andconfirm here becomes the password that isrequired to log on to the server.

Click Register to register this node on theserver.

Click Finish. The graphical user interfaceopens and is ready for use. You can alsostart any of the other installed clientcomponents from the Start menu.

Server uses closed registration Click Finish. Provide the information thatyou specified in the client configurationwizard to your Tivoli Storage Managerserver administrator. Provide theadmi

Documents

IBMTivoli Storage Manager forWindows Backup-Archive ... · Backup-archive client operations and security rights 99 Backup Operators group operations .....101 Considerations before