IBM Tivoli Storage Manager for Windows Backup-Archive ... · Upgrading the backup-ar chive client ... Chapter 2. Configure the T ivoli Storage ... Issuing a series of commands by

IBM Tivoli Storage Manager for Windows Backup-ArchiveClientsVersion 7.1.3

Installation and User's Guide

IBM

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

Fifth edition (September 2015)

This edition applies to version 7, release 1, modification 3 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 . . . .. xivReading syntax diagrams . . . . . . . .. xiv

New for Tivoli Storage ManagerVersion 7.1.3. . . . . . . . . . .. 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 . . . . . . . .. 6Windows supported file systems. . . . .. 7

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

Windows client installation might require a reboot 9Installation procedures . . . . . . . .. 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

Installing the client management service to collectdiagnostic information. . . . . . . . . .. 25

Chapter 2. Configure the Tivoli StorageManager client . . . . . . . . . .. 27Client options file overview . . . . . . . .. 27

Creating and modifying the client options file .. 29Create a shared directory options file . . . .. 31Creating multiple client options files . . . .. 31

Environment variables. . . . . . . . . .. 32

Web client configuration overview. . . . . .. 32Configuring the web client on Windows systems 33

Configuring the scheduler . . . . . . . .. 35Comparison between client acceptor-managedservices and traditional scheduler services . .. 35Configuring the client to use the client acceptorservice to manage the scheduler . . . . .. 36

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

Configuring Tivoli Storage Manager client/servercommunication across a firewall . . . . . .. 38Configuring Tivoli Storage Manager client/servercommunication with Secure Sockets Layer . . .. 41

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

Configuring the journal engine service . . .. 44JournalSettings stanza (Windows) . . . .. 46JournalExcludeList stanza . . . . . .. 48JournaledFileSystemSettings stanza . . .. 48Overriding stanzas . . . . . . . . .. 52

Client-side data deduplication . . . . . . .. 52Configuring the client for data deduplication .. 56Excluding files from data deduplication . . .. 58

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

Requirements for automated client failover .. 60Restrictions for automated client failover .. 61Failover capabilities of Tivoli Storage Managercomponents . . . . . . . . . . .. 62

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

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

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

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

Configure the web client in a cluster environment 70Configure the web client to process clusterdisk resources . . . . . . . . . .. 70

Frequently asked questions . . . . . . .. 77Configuring online-image backup support . . .. 80Configuring Open File Support . . . . . . .. 80Configuring NetApp and Tivoli Storage Managerfor snapshot difference incremental backups . .. 81

Protection for clustered-data ONTAP NetApp fileserver volumes . . . . . . . . . . .. 82SnapMirror support for NetAppsnapshot-assisted progressive incremental backup(snapdiff) . . . . . . . . . . . . .. 84

Copyright IBM Corp. 1993, 2015 iii

|||

Register your workstation with a server . . . .. 87Closed registration . . . . . . . . . .. 87Open registration . . . . . . . . . .. 88

Creating an include-exclude list . . . . . .. 88Include-exclude options . . . . . . . .. 89

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

Determine compression and encryptionprocessing . . . . . . . . . . . . .. 97Preview include-exclude list files . . . . .. 98Include and exclude option processing . . .. 99Processing rules when using UNC names . .. 101

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

Chapter 3. Getting started . . . . .. 103Backup-archive client operations and securityrights . . . . . . . . . . . . . . .. 103

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

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

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

Starting a Java GUI session . . . . . . . .. 108Tivoli Storage Manager password . . . .. 109Setup wizard . . . . . . . . . . .. 109

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

Specifying input strings that contain blank spacesor quotation marks . . . . . . . . . .. 111Starting a web client session . . . . . . .. 112

User privileges . . . . . . . . . . .. 113Start the client scheduler automatically . . . .. 113Changing your password . . . . . . . .. 113Sorting file lists using the Tivoli Storage ManagerGUI . . . . . . . . . . . . . . .. 115

Displaying online help . . . . . . . . .. 116Ending a session . . . . . . . . . . .. 116Online forums . . . . . . . . . . . .. 117

Chapter 4. Backing up your data . .. 119Planning your backups (Windows) . . . . .. 119Which files are backed up . . . . . . . .. 120Open file support for backup operations . . .. 121Backing up data using the GUI . . . . . .. 123

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

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

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

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

Full and partial incremental backup . . . .. 134Journal-based backup. . . . . . . .. 136

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

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

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

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

Associate a local snapshot with a server file space(Windows) . . . . . . . . . . . . .. 146Backing up Windows system state . . . . .. 146Backing up Automated System Recovery files .. 147Preparation for Automated System Recovery . .. 148

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

Image backup . . . . . . . . . . . .. 150

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

Performing prerequisite tasks before creating animage backup . . . . . . . . . . .. 151Utilizing image backups to perform file systemincremental backups . . . . . . . . .. 152

Method 1: Using image backups with filesystem incremental backups . . . . .. 152Method 2: Using image backups withincremental-by-date image backups . . .. 153Comparing methods 1 and 2 . . . . .. 153

Performing an image backup using the GUI .. 154Performing an image backup using thecommand line . . . . . . . . . . .. 155

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

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

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

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

Back up virtual machines on a Hyper-V system 175Hyper-V backup support limitations. . . .. 177

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

Open files . . . . . . . . . . . .. 182Ambiguous file space names in filespecifications . . . . . . . . . . .. 183Management classes . . . . . . . . .. 183Deleted file systems . . . . . . . . .. 184Removable media backup . . . . . . .. 184Fixed drives . . . . . . . . . . . .. 185NTFS and ReFS file spaces . . . . . . .. 185Universal Naming Convention names . . .. 185

Examples: UNC names in domain lists . .. 185Examples: UNC name backup . . . . .. 186

Microsoft Dfs file protection methods . . .. 187

Chapter 5. Restoring your data . . .. 189Duplicate file names . . . . . . . . . .. 189Universal Naming Convention names restore. .. 190Active or inactive backup restore . . . . . .. 190Restoring files and directories . . . . . . .. 191

Restoring data by using the GUI . . . . .. 191Examples for restoring data using the commandline. . . . . . . . . . . . . . .. 191

Examples: Restoring large amounts of data 193

Standard query restore, no-query restore, andrestartable restore . . . . . . . . .. 193

Restoring Windows system state . . . . . .. 195Restoring Automated System Recovery files . .. 196Restoring the operating system when the computeris working . . . . . . . . . . . . .. 197Recovering a computer when the Windows OS isnot working . . . . . . . . . . . . .. 197

Creating a bootable WinPE CD . . . . .. 197Restoring the Windows operating system withAutomated System Recovery . . . . . .. 198

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

Restoring an image using the GUI . . . .. 199Restoring an image using the command line .. 200

Restore data from a backup set . . . . . .. 201Restore backup sets: considerations andrestrictions . . . . . . . . . . . .. 203Backup set restore . . . . . . . . . .. 204Restoring backup sets using the GUI . . .. 205Backup set restores using the clientcommand-line interface . . . . . . . .. 206

Restore Net Appliance CIFS shares . . . . .. 206Restoring data from a VMware backup . . . .. 207

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

Full VM instant restore cleanup and repairscenarios . . . . . . . . . . . .. 212Recovering from non-standard errorconditions . . . . . . . . . . .. 214

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

Restore Windows individual Active Directoryobjects. . . . . . . . . . . . . . .. 219

Reanimate tombstone objects or restoring from asystem state backup . . . . . . . . .. 219Restoring Active Directory objects using theGUI and command line . . . . . . . .. 220Restrictions and limitations when restoringActive Directory objects . . . . . . . .. 221Preserve attributes in tombstone objects . .. 222Modifying the client acceptor and agent servicesto use the web client . . . . . . . . .. 222

Restoring or retrieving data during a failover. .. 223Authorizing another user to restore or retrieveyour files . . . . . . . . . . . . . .. 224Restoring or retrieving files from another clientnode . . . . . . . . . . . . . . .. 225Restoring or retrieving your files to anotherworkstation . . . . . . . . . . . . .. 226Deleting file spaces . . . . . . . . . .. 227Restoring data to a point in time . . . . . .. 228Restore NAS file systems . . . . . . . .. 229

Restoring NAS file systems using the web client 229Restoring NAS files and directories using theweb client . . . . . . . . . . . .. 230Options and commands to restore NAS filesystems from the command line . . . . .. 232

Contents v

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

Snapshot backup or archive with open filesupport . . . . . . . . . . . . .. 236Archiving data with the GUI . . . . . .. 236Archive data examples by using the commandline. . . . . . . . . . . . . . .. 237

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

Archiving data with client node proxy . . .. 238Deleting archive data . . . . . . . . .. 240

Retrieve archives . . . . . . . . . . .. 240Retrieving archives with the GUI . . . . .. 241Retrieve archive copies by using the commandline. . . . . . . . . . . . . . .. 241

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

Evaluate schedule return codes in schedulescripts . . . . . . . . . . . . . .. 246Return codes from preschedulecmd andpostschedulecmd scripts . . . . . . . .. 247

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

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

Chapter 8. Client return codes . . .. 261

Chapter 9. Storage managementpolicies . . . . . . . . . . . . .. 263Policy domains and policy sets . . . . . .. 263Management classes and copy groups . . . .. 264Display information about management classesand copy groups . . . . . . . . . . .. 265

Copy group name attribute. . . . . . .. 265Copy type attribute . . . . . . . . .. 265Copy frequency attribute . . . . . . .. 266Versions data exists attribute . . . . . .. 266Versions data deleted attribute . . . . .. 266Retain extra versions attribute . . . . . .. 266Retain only version attribute . . . . . .. 267Copy serialization attribute . . . . . . .. 267Copy mode parameter . . . . . . . .. 268

Copy destination attribute . . . . . . .. 268Retain versions attribute. . . . . . . .. 268Deduplicate data attribute . . . . . . .. 269

Select a management class for files . . . . .. 269Assign a management class to files . . . . .. 269Override the management class for archived files 270Select a management class for directories . . .. 271Bind management classes to files . . . . . .. 271Rebind backup versions of files . . . . . .. 272Retention grace period . . . . . . . . .. 272Event-based policy retention protection. . . .. 273

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

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

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

Examples: Automating backups . . . .. 275Examples: Configuring the CAD to managean existing scheduler service . . . . .. 277Creating a new scheduler and associating aCAD to manage the scheduler. . . . .. 278

dsmcutil command . . . . . . . . . .. 278Dsmcutil commands: Required options andexamples . . . . . . . . . . . . .. 279Dsmcutil valid options . . . . . . . .. 286

Chapter 11. Processing options . .. 291Processing options overview . . . . . . .. 291Communication options . . . . . . . . .. 292

TCP/IP options . . . . . . . . . .. 292Named Pipes option . . . . . . . . .. 293Shared memory options . . . . . . . .. 293

Backup and archive processing options . . . .. 293Restore and retrieve processing options. . . .. 302Scheduling options . . . . . . . . . .. 305Format and language options . . . . . . .. 306Command processing options . . . . . . .. 307Authorization options . . . . . . . . .. 307Error processing options. . . . . . . . .. 308Transaction processing options . . . . . .. 308Web client options. . . . . . . . . . .. 309Diagnostics options . . . . . . . . . .. 309Using options with commands . . . . . .. 310

Entering options with a command . . . .. 310Initial command-line-only options . . . .. 315Client options that can be set by the TivoliStorage Manager server . . . . . . . .. 316

Client options reference . . . . . . . . .. 318Absolute . . . . . . . . . . . . .. 318Adlocation . . . . . . . . . . . .. 319Archmc . . . . . . . . . . . . . .. 320Asnodename . . . . . . . . . . . .. 320Asrmode . . . . . . . . . . . . .. 322Auditlogging . . . . . . . . . . .. 323Auditlogname . . . . . . . . . . .. 325Autodeploy . . . . . . . . . . . .. 327Autofsrename . . . . . . . . . . .. 329Backmc . . . . . . . . . . . . . .. 330

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

Backupsetname . . . . . . . . . . .. 331Basesnapshotname . . . . . . . . . .. 332Casesensitiveaware . . . . . . . . .. 333Changingretries . . . . . . . . . .. 334Class . . . . . . . . . . . . . .. 335Clientview . . . . . . . . . . . .. 336Clusterdisksonly . . . . . . . . . .. 337Clusternode . . . . . . . . . . . .. 339Collocatebyfilespec . . . . . . . . .. 340Commmethod . . . . . . . . . . . .. 341Commrestartduration . . . . . . . . .. 343Commrestartinterval . . . . . . . . .. 343Compressalways . . . . . . . . . . .. 344Compression . . . . . . . . . . . .. 345Console . . . . . . . . . . . . .. 346Createnewbase . . . . . . . . . . .. 347Datacenter . . . . . . . . . . . .. 349Datastore . . . . . . . . . . . .. 350Dateformat . . . . . . . . . . . .. 350Dedupcachepath . . . . . . . . . . .. 352Dedupcachesize . . . . . . . . . . .. 353Deduplication . . . . . . . . . . .. 354Deletefiles . . . . . . . . . . . .. 355Description . . . . . . . . . . . .. 355Detail . . . . . . . . . . . . . .. 356Diffsnapshot . . . . . . . . . . .. 358Diffsnapshotname . . . . . . . . . .. 359Dirmc . . . . . . . . . . . . . .. 360Dirsonly . . . . . . . . . . . . .. 361Disablenqr . . . . . . . . . . . .. 362Diskbuffsize . . . . . . . . . . .. 363Diskcachelocation . . . . . . . . .. 363Domain . . . . . . . . . . . . . .. 365Domain.image . . . . . . . . . . .. 368Domain.nas . . . . . . . . . . . .. 369Domain.vcd . . . . . . . . . . . .. 370Domain.vmfile . . . . . . . . . . .. 372Domain.vmfull . . . . . . . . . . .. 374Enable8dot3namesupport . . . . . . . .. 380Enablearchiveretentionprotection . . . .. 381Enablededupcache . . . . . . . . . .. 382Enablelanfree . . . . . . . . . . .. 384Encryptiontype . . . . . . . . . . .. 385Encryptkey . . . . . . . . . . . .. 386Errorlogmax . . . . . . . . . . . .. 387Errorlogname . . . . . . . . . . .. 389Errorlogretention . . . . . . . . .. 390Exclude options . . . . . . . . . .. 391

Controlling compression processing . . .. 395Adaptive subfile backup processing . . .. 395Processing NAS file systems . . . . .. 396Virtual machine exclude options . . . .. 396

Fbbranch . . . . . . . . . . . . .. 398Fbclientname . . . . . . . . . . .. 399Fbpolicyname . . . . . . . . . . .. 400Fbreposlocation . . . . . . . . . .. 402Fbserver . . . . . . . . . . . . .. 403Fbvolumename . . . . . . . . . . .. 404Filelist . . . . . . . . . . . . .. 405Filename . . . . . . . . . . . . .. 408Filesonly . . . . . . . . . . . .. 410

Forcefailover . . . . . . . . . . .. 410Fromdate . . . . . . . . . . . . .. 411Fromnode . . . . . . . . . . . . .. 412Fromtime . . . . . . . . . . . . .. 413Groupname . . . . . . . . . . . .. 414Guitreeviewafterbackup . . . . . . . .. 414Host . . . . . . . . . . . . . .. 415Httpport . . . . . . . . . . . . .. 415Hsmreparsetag . . . . . . . . . . .. 416Ieobjtype . . . . . . . . . . . .. 417Ifnewer . . . . . . . . . . . . .. 418Imagegapsize . . . . . . . . . . .. 419Imagetofile . . . . . . . . . . . .. 420Inactive . . . . . . . . . . . . .. 420Inclexcl . . . . . . . . . . . . .. 421

Considerations for Unicode-enabled clients 422Include options. . . . . . . . . . .. 422

Compression, encryption, and adaptivesubfile backup processing . . . . . .. 427Processing NAS file systems . . . . .. 428Virtual machine include options . . . .. 428

Incrbydate . . . . . . . . . . . .. 437Incremental . . . . . . . . . . . .. 438Incrthreshold . . . . . . . . . . .. 438Journalpipe . . . . . . . . . . . .. 440Lanfreecommmethod . . . . . . . . .. 440Lanfreeshmport . . . . . . . . . . .. 442Lanfreetcpport . . . . . . . . . . .. 442Lanfreessl . . . . . . . . . . . .. 443Lanfreetcpserveraddress . . . . . . .. 444Language . . . . . . . . . . . . .. 445Latest . . . . . . . . . . . . . .. 446Localbackupset . . . . . . . . . . .. 446Managedservices . . . . . . . . . .. 447Maxcmdretries . . . . . . . . . . .. 449Mbobjrefreshthresh . . . . . . . . .. 450Mbpctrefreshthresh . . . . . . . . .. 451Memoryefficientbackup . . . . . . . .. 452Mode . . . . . . . . . . . . . .. 453Monitor . . . . . . . . . . . . .. 457Myprimaryserver . . . . . . . . . .. 458Myreplicationserver . . . . . . . . .. 459Namedpipename . . . . . . . . . . .. 460Nasnodename . . . . . . . . . . . .. 461Nodename . . . . . . . . . . . . .. 462Nojournal . . . . . . . . . . . .. 463Noprompt . . . . . . . . . . . . .. 464Nrtablepath . . . . . . . . . . . .. 465Numberformat . . . . . . . . . . .. 466Optfile . . . . . . . . . . . . .. 467Password . . . . . . . . . . . . .. 468Passwordaccess . . . . . . . . . . .. 470Pick . . . . . . . . . . . . . .. 471Pitdate . . . . . . . . . . . . .. 472Pittime . . . . . . . . . . . . .. 473Postschedulecmd/Postnschedulecmd . . . .. 474Postsnapshotcmd . . . . . . . . . .. 476Preschedulecmd/Prenschedulecmd . . . .. 477Preservelastaccessdate . . . . . . . .. 479Preservepath . . . . . . . . . . .. 480Presnapshotcmd . . . . . . . . . . .. 482

Contents vii

Queryschedperiod . . . . . . . . . .. 484Querysummary . . . . . . . . . . .. 485Quiet . . . . . . . . . . . . . .. 486Quotesareliteral . . . . . . . . . .. 487Replace . . . . . . . . . . . . .. 489Replserverguid . . . . . . . . . . .. 490Replservername . . . . . . . . . . .. 491Replsslport . . . . . . . . . . . .. 493Repltcpport . . . . . . . . . . . .. 494Repltcpserveraddress . . . . . . . .. 495Resetarchiveattribute . . . . . . . .. 497Resourceutilization . . . . . . . . .. 498

Regulating backup and archive sessions .. 499Regulating restore sessions . . . . . .. 500Multiple client session considerations . .. 500

Retryperiod . . . . . . . . . . . .. 501Revokeremoteaccess . . . . . . . . .. 502Runasservice . . . . . . . . . . .. 502Schedcmddisabled . . . . . . . . . .. 503Schedcmdexception . . . . . . . . .. 504Schedlogmax . . . . . . . . . . . .. 505Schedlogname . . . . . . . . . . .. 507Schedlogretention . . . . . . . . .. 508Schedmode . . . . . . . . . . . .. 510Schedrestretrdisabled . . . . . . . .. 511Scrolllines . . . . . . . . . . . .. 512Scrollprompt . . . . . . . . . . .. 513Sessioninitiation . . . . . . . . .. 514Shmport . . . . . . . . . . . . .. 516Showmembers . . . . . . . . . . . .. 516Skipmissingsyswfiles . . . . . . . .. 517Skipntpermissions . . . . . . . . .. 518Skipntsecuritycrc . . . . . . . . .. 519Snapdiff . . . . . . . . . . . . .. 519Snapdiffhttps . . . . . . . . . . .. 524Snapshotproviderfs . . . . . . . . .. 526Snapshotproviderimage . . . . . . . .. 527Snapshotroot . . . . . . . . . . .. 528Srvoptsetencryptiondisabled . . . . . .. 530Srvprepostscheddisabled . . . . . . .. 531Srvprepostsnapdisabled . . . . . . . .. 532Ssl . . . . . . . . . . . . . . .. 533Sslfipsmode . . . . . . . . . . . .. 534Sslrequired . . . . . . . . . . . .. 535Ssldisablelegacytls . . . . . . . . .. 536Stagingdirectory . . . . . . . . . .. 537Subdir . . . . . . . . . . . . . .. 538Subfilebackup . . . . . . . . . . .. 540Subfilecachepath . . . . . . . . . .. 541Subfilecachesize . . . . . . . . . .. 542Systemstatebackupmethod . . . . . . .. 542Tapeprompt . . . . . . . . . . . .. 544Tcpadminport . . . . . . . . . . .. 545Tcpbuffsize . . . . . . . . . . . .. 546Tcpcadaddress . . . . . . . . . . .. 547Tcpclientaddress . . . . . . . . . .. 547Tcpclientport . . . . . . . . . . .. 548Tcpnodelay . . . . . . . . . . . .. 549Tcpport . . . . . . . . . . . . .. 550Tcpserveraddress . . . . . . . . . .. 550Tcpwindowsize . . . . . . . . . . .. 551

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

Chapter 12. Using commands . . .. 609Start and end a client command session . . .. 612

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

Process commands in batch mode . . . .. 612Process commands in interactive mode . . .. 613

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

Command name . . . . . . . . . .. 614Options . . . . . . . . . . . . .. 614

Options in interactive mode . . . . .. 614Parameters . . . . . . . . . . . .. 614File specification syntax . . . . . . . .. 615

Wildcard characters . . . . . . . . . .. 616Client commands reference . . . . . . . .. 617Archive . . . . . . . . . . . . . .. 617

Open file support . . . . . . . . . .. 619Archive FastBack . . . . . . . . . . .. 620Backup FastBack . . . . . . . . . . .. 623Backup Group . . . . . . . . . . . .. 626Backup Image . . . . . . . . . . . .. 628

Offline and online image backup . . . . .. 630Utilizing image backup to perform file systemincremental backup . . . . . . . . .. 631

Backup NAS . . . . . . . . . . . .. 632Backup Systemstate . . . . . . . . . .. 635Backup VAPP . . . . . . . . . . . .. 636Backup VM . . . . . . . . . . . . .. 642Cancel Process . . . . . . . . . . . .. 652Cancel Restore . . . . . . . . . . . .. 653Delete Access . . . . . . . . . . . .. 654Delete Archive . . . . . . . . . . . .. 654Delete Backup . . . . . . . . . . . .. 656Delete Filespace . . . . . . . . . . .. 660Delete Group . . . . . . . . . . . .. 661Expire . . . . . . . . . . . . . . .. 662Help . . . . . . . . . . . . . . .. 664Incremental . . . . . . . . . . . . .. 665

Open file support . . . . . . . . . .. 669Journal-based backup. . . . . . . . .. 670Backing up NTFS or ReFS volume mount points 671

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

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

Loop . . . . . . . . . . . . . . .. 673Macro . . . . . . . . . . . . . . .. 674Monitor Process . . . . . . . . . . .. 675Preview Archive . . . . . . . . . . .. 676Preview Backup . . . . . . . . . . .. 677Query Access . . . . . . . . . . . .. 678Query Adobjects . . . . . . . . . . .. 678Query Archive . . . . . . . . . . . .. 680Query Backup . . . . . . . . . . . .. 682

Query NAS file system images . . . . .. 685Query Backupset . . . . . . . . . . .. 686

Query Backupset without the backupsetnameparameter . . . . . . . . . . . .. 687

Query Filespace . . . . . . . . . . .. 689Query NAS file spaces . . . . . . . .. 691

Query Group . . . . . . . . . . . .. 691Query Image . . . . . . . . . . . .. 693

Query Inclexcl . . . . . . . . . . . .. 694Query Mgmtclass . . . . . . . . . . .. 696Query Node. . . . . . . . . . . . .. 697Query Options . . . . . . . . . . . .. 698Query Restore . . . . . . . . . . . .. 699Query Schedule . . . . . . . . . . .. 700Query Session . . . . . . . . . . . .. 700Query Systeminfo . . . . . . . . . .. 701Query Systemstate . . . . . . . . . .. 703Query VAPP . . . . . . . . . . . .. 704Query VM . . . . . . . . . . . . .. 708Restart Restore . . . . . . . . . . . .. 712Restore . . . . . . . . . . . . . .. 713

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

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

Restore Adobjects. . . . . . . . . . .. 721Restore Backupset . . . . . . . . . .. 722

Restore backup sets: considerations andrestrictions . . . . . . . . . . . .. 725Restore backup sets in a SAN environment .. 726Restore Backupset without the backupsetnameparameter . . . . . . . . . . . .. 727

Restore Group . . . . . . . . . . . .. 729Restore Image . . . . . . . . . . . .. 731Restore NAS . . . . . . . . . . . .. 734Restore Systemstate . . . . . . . . . .. 736Restore VAPP . . . . . . . . . . . .. 738Restore VM . . . . . . . . . . . . .. 741Retrieve . . . . . . . . . . . . . .. 749

Retrieve archives from file spaces that are notUnicode-enabled . . . . . . . . . .. 752Retrieve named streams . . . . . . . .. 752Retrieve sparse files . . . . . . . . .. 753

Schedule . . . . . . . . . . . . . .. 753Selective . . . . . . . . . . . . . .. 754

Open file support . . . . . . . . . .. 757Adaptive subfile backups . . . . . . .. 757Associate a local snapshot with a server filespace . . . . . . . . . . . . . .. 758

Set Access . . . . . . . . . . . . .. 758Set Event. . . . . . . . . . . . . .. 761Set Netappsvm . . . . . . . . . . .. 763Set Password . . . . . . . . . . . .. 764

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

Notices . . . . . . . . . . . . .. 773

Glossary . . . . . . . . . . . .. 777

Index . . . . . . . . . . . . . .. 779

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. File path and name limits . . . . . . .. 285. Client acceptor-managed services versus

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

directories . . . . . . . . . . . .. 918. Options for controlling processing using

include and exclude statements . . . . .. 929. Wildcard and other special characters . . .. 95

10. Specifying a drive specification usingwildcards . . . . . . . . . . . .. 96

11. Using wildcard characters with include andexclude patterns . . . . . . . . . .. 97

12. Options for controlling compression andencryption processing . . . . . . . .. 97

13. UNC name patterns and DOS patterns 10114. Required user security rights for Tivoli

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

Storage Manager GUI . . . . . . . .. 11516. Planning your backups . . . . . . .. 11917. Command line backup examples . . . .. 12518. Maximum file size . . . . . . . . .. 13319. Comparing incremental image backup

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

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

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

23. Client command line informational messages 17924. UNC examples . . . . . . . . . .. 18625. Command-line restore examples . . . .. 19126. Backup set GUI restore restrictions . . .. 20227. Backup set command-line restore restrictions 20328. Components for the restore command when

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

you restore files to a different computer. .. 21630. NAS options and commands . . . . .. 23231. Command-line archive examples . . . .. 23732. Command line examples of retrieving

archives . . . . . . . . . . . .. 24133. Sample classic query schedule output 25134. Sample enhanced query schedule output 25235. Client return codes and their meanings 26136. Default attribute values in the standard

management class . . . . . . . . .. 26537. TCP/IP options . . . . . . . . . .. 29238. Named Pipes communication option 29339. Shared memory communication options 29340. Backup and archive processing options 293

41. Restore and retrieve processing options 30242. Scheduling options. . . . . . . . .. 30543. Format and language options . . . . .. 30644. Command processing options . . . . .. 30745. Authorization options. . . . . . . .. 30746. Error processing options . . . . . . .. 30847. Transaction processing options . . . . .. 30848. Web client options . . . . . . . . .. 30949. Diagnostics options . . . . . . . .. 30950. Client command options . . . . . . .. 31151. Options that are valid on the initial command

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

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

distribute backups.. . . . . . . . .. 32154. Clusternode and clusterdisksonly

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

sources. . . . . . . . . . . . .. 36756. System services components and

corresponding keywords . . . . . . .. 39357. Other optional parameters . . . . . .. 42658. Incremental command: Related options 52159. Effects of server and client SSL settings on

success or failure of login attempts . . .. 53660. Commands . . . . . . . . . . .. 60961. Wildcard characters . . . . . . . .. 61762. Archive command: Related options . . .. 61863. Archive FastBack command: Related options 62164. Backup FastBack command: Related options 62465. Backup Group command: Related options 62766. Backup Image command: Related options 62967. Backup NAS command: Related options 63468. Backup VAPP command: Related options 63969. Delete Archive command: Related options 65570. Delete Backup command: Related options 65871. Delete Filespace command: Related options 66072. Delete Group command: Related options 66273. Expire command: Related options. . . .. 66374. Incremental command: Related options 66775. Query Adobjects command: Related options 67976. Query Archive command: Related options 68177. Query Backup command: Related options 68478. Query Backupset command: Related options 68779. Query Backupset command: Related options 68880. Query Filespace command: Related options 69081. Query Group command: Related options 69282. Query Image command: Related options 69483. Query Mgmtclass command: Related options 69784. Query Node command: Related options 69885. Query Options command: Related options 69886. Query Systeminfo command: Related options 70287. Query Systemstate command: Related options 70388. Query VAPP command: Related options 706

Copyright IBM Corp. 1993, 2015 xi

89. Query VM command: Related options forVMware virtual machine queries. . . . .. 708

90. Query VM command: Related options forHyper-V virtual machine queries. . . . .. 711

91. Restore command: Related options . . .. 71692. Restore Adobjects command: Related options 72193. Restore Backupset command: Related options 72494. Restore Group command: Related options 73095. Restore Image command: Related options 73296. Restore NAS command: Related options 735

97. Restore Systemstate command: Relatedoptions . . . . . . . . . . . .. 737

98. Restore VAPP command: Related options 74099. Restore VM command: Related options when

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

restoring Hyper-V virtual machines . . .. 747101. Retrieve command: Related options . . .. 750102. Schedule command: Related options . . .. 754103. Selective command: Related options . . .. 756

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.

Related concepts:Planning your backups (Windows) on page 119New for Tivoli Storage Manager Version 7.1.3 on page xviiChapter 1, Installing the Tivoli Storage Manager backup-archive clients, on page1

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 http://www.ibm.com/support/knowledgecenter.

Copyright IBM Corp. 1993, 2015 xiii

http://www.ibm.com/support/knowledgecenterhttp://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.

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 Space

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

v " quotation markv 'single quotation mark

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 Tivoli Storage Manager Version 7.1.3

IBM Tivoli Storage Manager backup-archive client Version 7.1.3 is updated toinclude information from APARs and new features.

New and changed 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.

The following features are new in V7.1.3:

Configure web-based file restore for Data Protection for VMwareThe set password command is updated. The new TYPE=DOMAIN parameterstores credentials for Windows domain controller logins in a Tivoli StorageManager for Virtual Environments Data Protection for VMware file restoreenvironment.

For more information, see Set Password on page 764.

Language packs are consolidatedIf you operate the backup-archive client in a language other than English,you no longer need to download and install separate language files. Thelanguage files are part of the client installation package and are installedautomatically.

For information about product installation, see Tivoli Storage ManagerWindows client installation overview on page 9.

Estimate compliance with license entitlementsFrom the Tivoli Storage Manager Operations Center, administrators canview front-end and back-end capacity usage to estimate compliance withlicense entitlements.

Important: The Tivoli Storage Manager client software needs to be at thelatest level for the Operations Center to present complete data.

Related information:About this publication on page xiii

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.Related concepts:New for Tivoli Storage Manager Version 7.1.3 on page xviiPlanning your backups (Windows) on page 119

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

Copyright IBM Corp. 1993, 2015 1

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

spaces 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 backupsof 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 is additional informationto consider before you use the new client software.

Be aware of the following information when you upgrade a backup-archive client:v The size of the buffer to record change notifications for a particular journal file

system (DirNotifyBufferSize) has changed. The default value is 16 KB.

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

v For a list of new and changed messages since the previous Tivoli StorageManager release, 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 use Tivoli Storage Manager servercommands to automatically deploy client upgrades. For information about howto manually set up automatic deployment of backup-archive clients, seehttp://www.ibm.com/support/docview.wss? uid=swg21673299.

v On a schedule definition. Schedules are defined on the server. Scheduledefinitions that deploy client software updates have an action=deploy statement.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 multiple

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

|||||||||

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

scheduler 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 deploymentfrom 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 clients disk. The lock file location isinstall_dir\..\IBM_ANR_WIN\mutext.txt.Related reference:Autodeploy on page 327

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 7

For current information about the client environment prerequisites for all of thesupported Tivoli Storage Manager client platforms, see technote 1243309(http://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,seetechnote 1197133 (http://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

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


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

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 the followingtypes of file systems:v GPFS

Restriction: The Tivoli Storage Manager Windows backup-archive client canback up 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/. If you do not alreadyhave 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, seethe product information at IBM Tivoli Storage Manager Fastback(http://www.ibm.com/support/knowledgecenter/SS9NU9/).

For information about integrating Tivoli Storage Manager and Tivoli StorageManager FastBack, see Integrating Tivoli Storage Manager FastBack and TivoliStorage Manager (http://www.ibm.com/support/knowledgecenter/SSGSG7_6.3.0/com.ibm.itsm.srv.fbint.doc_6.2.0/t_fbint.html).

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.

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:


http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.htmlftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/http://www.ibm.com/support/knowledgecenter/SS9NU9/http://www.ibm.com/support/knowledgecenter/SS9NU9/http://www.ibm.com/support/knowledgecenter/SSGSG7_6.3.0/com.ibm.itsm.srv.fbint.doc_6.2.0/t_fbint.htmlhttp://www.ibm.com/support/knowledgecenter/SSGSG7_6.3.0/com.ibm.itsm.srv.fbint.doc_6.2.0/t_fbint.htmlhttp://www.ibm.com/support/knowledgecenter/SSGSG7_6.3.0/com.ibm.itsm.srv.fbint.doc_6.2.0/t_fbint.html

Configuring the client to back up and archive Tivoli Storage Manager FastBackdata on page 66

Client configuration wizard for Tivoli Storage Manager FastBackThe Tivoli Storage Manager backup-archive client provides a wizard to configurethe 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 67

Tivoli Storage Manager Windows client installation overviewYou 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 theWindows backup-archive client are maintained on the web at http://www.ibm.com/support/docview.wss?uid=swg21197133Related concepts:Automatic backup-archive client deployment on page 3Related tasks:Creating and modifying the client options file on page 29Starting a web client session on page 112

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.v A manual installation or upgrade of the client is started.



v A client silent installation is started, even if the options to suppress rebootprompts, 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 proceduresThe 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 Windowsbackup-archive client for the first time. Thisprocedure presumes that the Windowscomputer that you are installing the clienton has never had a previous version of theclient installed on it before.

Upgrading the Windows client Describes how to upgrade an earlier versionof the Windows backup-archive client to thislatest version.

Reinstalling the Windows client Describes how to reinstall the Windowsbackup-archive client, if you uninstalled it.

Silent installation Describes how to install the Windowsbackup-archive client silently, without userinteraction during the installation procedure.

Repairing, modifying, or uninstalling theWindows client

Describes how to add or remove featuresfrom an installed backup-archive client(modify), replace damaged files or missingregistry keys (repair), or uninstall theWindows backup-archive 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.3, 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 compressed

installation 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.3release 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 to 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)


Option Description

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 and


Ctrl 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. To configure the default file systems for incremental backups, in the

Backup Type field, select Incremental. 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 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. To configure the default file systems for image backups, in the BackupType field, select Image. By default, Back up all local file systems isselected. If you do not want to back up all local file systems as the defaultaction during image backups, clear this option and individually select thefile systems to include. You can override the default selection when youinitiate 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 isreq

Documents

IBM Tivoli Storage Manager for Windows Backup-Archive ... · Upgrading the backup-ar chive client ... Chapter 2. Configure the T ivoli Storage ... Issuing a series of commands by