ibm tivoli storage manager for windows backup-archive clients: … · 2016. 6. 7. ·...

IBM Tivoli Storage Manager for WindowsBackup-Archive ClientsVersion 7.1.6

Installation and User's Guide

IBM

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

Seventh edition (June 2016)

This edition applies to version 7, release 1, modification 6 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, 2016.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

What's new for Version 7.1.6 . . . . . 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 . . . 5

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 . . . . . . . . . . . . 9Installing the backup-archive client from the DVDs . 9Windows backup-archive client installation overview 9

Windows client installation might require areboot . . . . . . . . . . . . . . . 10Installation procedures . . . . . . . . . 10

Installing the Windows client for the first time 11Upgrading the Windows client . . . . . . 15Reinstalling the Windows client . . . . . 19Silent installation . . . . . . . . . . 19Modifying, repairing, or uninstalling theWindows client . . . . . . . . . . . 23

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

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

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

Configuring the language for displaying the JavaGUI . . . . . . . . . . . . . . . . . 33Web client configuration overview. . . . . . . 33

Configuring the web client on Windows systems 34Configuring the scheduler . . . . . . . . . 36

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

Starting the client scheduler . . . . . . . . . 38Scheduling events using the GUI . . . . . . 39

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

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

Configuring the journal engine service . . . . 45JournalSettings stanza (Windows) . . . . . 47JournalExcludeList stanza . . . . . . . 49JournaledFileSystemSettings stanza . . . . 49Overriding stanzas . . . . . . . . . . 53

Client-side data deduplication . . . . . . . . 53Configuring the client for data deduplication . . 57Excluding files from data deduplication . . . . 59

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

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

Configuring the client for automated failover . . 63Determining the status of replicated client data 65Preventing automated client failover . . . . . 66Forcing the client to fail over . . . . . . . 67

Configuring the client to back up and archive TivoliStorage Manager FastBack data . . . . . . . . 67Configuring the backup-archive client to protectFastBack client data . . . . . . . . . . . 69Configuring the backup-archive client in a clusterserver environment . . . . . . . . . . . . 70

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

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

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

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

Protecting clustered-data ONTAP NetApp fileserver volumes . . . . . . . . . . . . 85

© Copyright IBM Corp. 1993, 2016 iii

|||

|||

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

Register your workstation with a server . . . . . 91Closed registration . . . . . . . . . . . 91Open registration . . . . . . . . . . . 91

Creating an include-exclude list . . . . . . . 92Include-exclude options . . . . . . . . . 93

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

Determine compression and encryptionprocessing . . . . . . . . . . . . . 100Preview include-exclude list files . . . . . . 101Include and exclude option processing . . . . 102Processing rules when using UNC names . . . 104

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

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

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

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

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

Starting a Java GUI session . . . . . . . . . 110Tivoli Storage Manager password. . . . . . 111Setup wizard . . . . . . . . . . . . 111

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

Specifying input strings that contain blank spacesor quotation marks . . . . . . . . . . . 114Starting a web client session . . . . . . . . 115

User privileges . . . . . . . . . . . . 115Start the client scheduler automatically . . . . . 116

Changing your password . . . . . . . . . 116Sorting file lists using the backup-archive clientGUI . . . . . . . . . . . . . . . . 117Displaying online help . . . . . . . . . . 119Ending a session . . . . . . . . . . . . 119Online forums . . . . . . . . . . . . . 119

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

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

LAN-free data movement . . . . . . . . 130LAN-free prerequisites . . . . . . . . 130LAN-free data movement options . . . . 131

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

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

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

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

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

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

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

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

Creating a client options file for AutomatedSystem Recovery . . . . . . . . . . . 151

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

Backing up the boot drive and system drive forAutomated System Recovery . . . . . . . 152

Image backup . . . . . . . . . . . . . 153Performing prerequisite tasks before creating animage backup . . . . . . . . . . . . 154Utilizing image backups to perform file systemincremental backups . . . . . . . . . . 155

Method 1: Using image backups with filesystem incremental backups . . . . . . 155Method 2: Using image backups withincremental-by-date image backups . . . . 156Comparing methods 1 and 2 . . . . . . 157

Performing an image backup using the GUI . . 157Performing an image backup using thecommand line . . . . . . . . . . . . 158

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

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

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

Preparing the environment for full backups ofVMware virtual machines . . . . . . . . 167Creating full backups for VMware virtualmachines . . . . . . . . . . . . . . 170Preparing the environment for file-level backupsof VMware virtual machines . . . . . . . 171Creating file-level backups for VMware virtualmachines . . . . . . . . . . . . . . 173Parallel backups of virtual machines. . . . . 174

Back up virtual machines on a Hyper-V system 178Hyper-V backup support limitations. . . . . 180

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

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

Examples: UNC names in domain lists . . . 188Examples: UNC name backup . . . . . . 189

Microsoft Dfs file protection methods . . . . 190

Chapter 5. Restoring your data . . . . 193Duplicate file names . . . . . . . . . . . 193Universal Naming Convention names restore. . . 194Active or inactive backup restore . . . . . . . 194Restoring files and directories . . . . . . . . 195

Restoring data by using the GUI . . . . . . 195

Examples for restoring data using the commandline. . . . . . . . . . . . . . . . 195

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

Restoring Windows system state . . . . . . . 199Restoring Automated System Recovery files . . . 201Restoring the operating system when the computeris working . . . . . . . . . . . . . . 201Recovering a computer when the Windows OS isnot working . . . . . . . . . . . . . . 202

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

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

Restoring an image using the GUI . . . . . 204Restoring an image using the command line . . 205

Restore data from a backup set . . . . . . . 206Restore backup sets: considerations andrestrictions . . . . . . . . . . . . . 208Backup set restore . . . . . . . . . . . 209Restoring backup sets using the GUI . . . . 209Backup set restores using the clientcommand-line interface . . . . . . . . . 211

Restore Net Appliance CIFS shares . . . . . . 211Restoring data from a VMware backup . . . . . 212

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

Full VM instant restore cleanup and repairscenarios . . . . . . . . . . . . . 217Recovering from non-standard errorconditions . . . . . . . . . . . . 219

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

Restore Windows individual Active Directoryobjects. . . . . . . . . . . . . . . . 224

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

Restoring or retrieving data during a failover. . . 228Authorizing another user to restore or retrieveyour files . . . . . . . . . . . . . . . 229Restoring or retrieving files from another clientnode . . . . . . . . . . . . . . . . 231Restoring or retrieving your files to anotherworkstation . . . . . . . . . . . . . . 232Deleting file spaces . . . . . . . . . . . 232Restoring data to a point in time . . . . . . . 233Restore NAS file systems . . . . . . . . . 235

Restoring NAS file systems using the web client 235

Contents v

Restoring NAS files and directories using theweb client . . . . . . . . . . . . . 236Options and commands to restore NAS filesystems from the command line . . . . . . 237

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

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

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

Archiving data with client node proxy . . . . 242Deleting archive data . . . . . . . . . . 244

Retrieve archives . . . . . . . . . . . . 244Retrieving archives with the GUI . . . . . . 245Retrieve archive copies by using the commandline. . . . . . . . . . . . . . . . 245

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

Evaluate schedule return codes in schedulescripts . . . . . . . . . . . . . . . 250Return codes from preschedulecmd andpostschedulecmd scripts . . . . . . . . . 251

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

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

Chapter 8. Client return codes . . . . 265

Chapter 9. Storage managementpolicies . . . . . . . . . . . . . . 267Policy domains and policy sets . . . . . . . 267Management classes and copy groups . . . . . 268Display information about management classesand copy groups . . . . . . . . . . . . 269

Copy group name attribute. . . . . . . . 269Copy type attribute . . . . . . . . . . 269Copy frequency attribute . . . . . . . . 270Versions data exists attribute . . . . . . . 270

Versions data deleted attribute . . . . . . 270Retain extra versions attribute . . . . . . . 270Retain only version attribute . . . . . . . 271Copy serialization attribute . . . . . . . . 271Copy mode parameter . . . . . . . . . 272Copy destination attribute . . . . . . . . 272Retain versions attribute. . . . . . . . . 272Deduplicate data attribute . . . . . . . . 273

Select a management class for files . . . . . . 273Assign a management class to files . . . . . . 273Override the management class for archived files 274Select a management class for directories . . . . 275Bind management classes to files . . . . . . . 275Rebind backup versions of files . . . . . . . 276Retention grace period . . . . . . . . . . 276Event-based policy retention protection. . . . . 277

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

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

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

Examples: Automating backups . . . . . 279Examples: Configuring the CAD to managean existing scheduler service . . . . . . 281Creating a new scheduler and associating aCAD to manage the scheduler. . . . . . 282

dsmcutil command . . . . . . . . . . . 283Dsmcutil commands: Required options andexamples . . . . . . . . . . . . . . 283Dsmcutil valid options . . . . . . . . . 290

Chapter 11. Processing options . . . 295Processing options overview . . . . . . . . 295Communication options . . . . . . . . . . 296

TCP/IP options . . . . . . . . . . . 296Named Pipes option . . . . . . . . . . 297Shared memory options . . . . . . . . . 297

Backup and archive processing options . . . . . 297Restore and retrieve processing options. . . . . 306Scheduling options . . . . . . . . . . . 309Format and language options . . . . . . . . 310Command processing options . . . . . . . . 311Authorization options . . . . . . . . . . 311Error processing options. . . . . . . . . . 312Transaction processing options . . . . . . . 312Web client options. . . . . . . . . . . . 313Diagnostics options . . . . . . . . . . . 313Using options with commands . . . . . . . 314

Entering options with a command . . . . . 314Initial command-line-only options . . . . . 319Client options that can be set by the TivoliStorage Manager server . . . . . . . . . 320

Client options reference . . . . . . . . . . 321Absolute . . . . . . . . . . . . . . 322Adlocation . . . . . . . . . . . . . 323Archmc . . . . . . . . . . . . . . . 323Asnodename . . . . . . . . . . . . . 324

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

Session settings and schedules for a proxyoperation . . . . . . . . . . . . . 326

Asrmode . . . . . . . . . . . . . . 327Auditlogging . . . . . . . . . . . . 328Auditlogname . . . . . . . . . . . . 330Autodeploy . . . . . . . . . . . . . 332Autofsrename . . . . . . . . . . . . 333Backmc . . . . . . . . . . . . . . . 335Backupsetname . . . . . . . . . . . . 336Basesnapshotname . . . . . . . . . . . 337Cadlistenonport . . . . . . . . . . . 338Casesensitiveaware . . . . . . . . . . 339Changingretries . . . . . . . . . . . 340Class . . . . . . . . . . . . . . . 341Clientview . . . . . . . . . . . . . 342Clusterdisksonly . . . . . . . . . . . 342Clusternode . . . . . . . . . . . . . 345Collocatebyfilespec . . . . . . . . . . 346Commmethod . . . . . . . . . . . . . 347Commrestartduration . . . . . . . . . . 348Commrestartinterval . . . . . . . . . . 349Compressalways . . . . . . . . . . . . 350Compression . . . . . . . . . . . . . 351Console . . . . . . . . . . . . . . 352Createnewbase . . . . . . . . . . . . 354Datacenter . . . . . . . . . . . . . 356Datastore . . . . . . . . . . . . . 356Dateformat . . . . . . . . . . . . . 356Dedupcachepath . . . . . . . . . . . . 359Dedupcachesize . . . . . . . . . . . . 359Deduplication . . . . . . . . . . . . 360Deletefiles . . . . . . . . . . . . . 361Description . . . . . . . . . . . . . 362Detail . . . . . . . . . . . . . . . 363Diffsnapshot . . . . . . . . . . . . 364Diffsnapshotname . . . . . . . . . . . 366Dirmc . . . . . . . . . . . . . . . 367Dirsonly . . . . . . . . . . . . . . 368Disablenqr . . . . . . . . . . . . . 368Diskbuffsize . . . . . . . . . . . . 369Diskcachelocation . . . . . . . . . . 370Domain . . . . . . . . . . . . . . . 371Domain.image . . . . . . . . . . . . 374Domain.nas . . . . . . . . . . . . . 375Domain.vcd . . . . . . . . . . . . . 376Domain.vmfile . . . . . . . . . . . . 378Domain.vmfull . . . . . . . . . . . . 381Enable8dot3namesupport . . . . . . . . . 386Enablearchiveretentionprotection . . . . . 388Enablededupcache . . . . . . . . . . . 389Enableinstrumentation . . . . . . . . . 390Enablelanfree . . . . . . . . . . . . 392Encryptiontype . . . . . . . . . . . . 393Encryptkey . . . . . . . . . . . . . 394Errorlogmax . . . . . . . . . . . . . 396Errorlogname . . . . . . . . . . . . 397Errorlogretention . . . . . . . . . . 398Exclude options . . . . . . . . . . . 400

Controlling compression processing . . . . 403Adaptive subfile backup processing . . . . 403Processing NAS file systems . . . . . . 404

Virtual machine exclude options . . . . . 404Fbbranch . . . . . . . . . . . . . . 406Fbclientname . . . . . . . . . . . . 407Fbpolicyname . . . . . . . . . . . . 409Fbreposlocation . . . . . . . . . . . 410Fbserver . . . . . . . . . . . . . . 411Fbvolumename . . . . . . . . . . . . 412Filelist . . . . . . . . . . . . . . 414Filename . . . . . . . . . . . . . . 417Filesonly . . . . . . . . . . . . . 418Forcefailover . . . . . . . . . . . . 419Fromdate . . . . . . . . . . . . . . 420Fromnode . . . . . . . . . . . . . . 420Fromtime . . . . . . . . . . . . . . 421Groupname . . . . . . . . . . . . . 422Guitreeviewafterbackup . . . . . . . . . 422Host . . . . . . . . . . . . . . . 423Httpport . . . . . . . . . . . . . . 423Hsmreparsetag . . . . . . . . . . . . 424Ieobjtype . . . . . . . . . . . . . 425Ifnewer . . . . . . . . . . . . . . 426Imagegapsize . . . . . . . . . . . . 427Imagetofile . . . . . . . . . . . . . 428Inactive . . . . . . . . . . . . . . 428Inclexcl . . . . . . . . . . . . . . 429

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

Compression, encryption, and adaptivesubfile backup processing . . . . . . . 435Processing NAS file systems . . . . . . 436Virtual machine include options . . . . . 437

Incrbydate . . . . . . . . . . . . . 445Incremental . . . . . . . . . . . . . 446Incrthreshold . . . . . . . . . . . . 446Instrlogmax . . . . . . . . . . . . . 448Instrlogname . . . . . . . . . . . . 449Journalpipe . . . . . . . . . . . . . 450Lanfreecommmethod . . . . . . . . . . 450Lanfreeshmport . . . . . . . . . . . . 452Lanfreetcpport . . . . . . . . . . . . 453Lanfreessl . . . . . . . . . . . . . 453Lanfreetcpserveraddress . . . . . . . . 454Language . . . . . . . . . . . . . . 455Latest . . . . . . . . . . . . . . . 456Localbackupset . . . . . . . . . . . . 456Managedservices . . . . . . . . . . . 457Maxcmdretries . . . . . . . . . . . . 459Mbobjrefreshthresh . . . . . . . . . . 460Mbpctrefreshthresh . . . . . . . . . . 461Memoryefficientbackup . . . . . . . . . 462Mode . . . . . . . . . . . . . . . 463Monitor . . . . . . . . . . . . . . 468Myprimaryserver . . . . . . . . . . . 468Myreplicationserver . . . . . . . . . . 469Namedpipename . . . . . . . . . . . . 471Nasnodename . . . . . . . . . . . . . 471Nodename . . . . . . . . . . . . . . 472Nojournal . . . . . . . . . . . . . 474Noprompt . . . . . . . . . . . . . . 474Nrtablepath . . . . . . . . . . . . . 475Numberformat . . . . . . . . . . . . 476

Contents vii

|||

||

||

||||

Optfile . . . . . . . . . . . . . . 478Password . . . . . . . . . . . . . . 478Passwordaccess . . . . . . . . . . . . 480Pick . . . . . . . . . . . . . . . 481Pitdate . . . . . . . . . . . . . . 482Pittime . . . . . . . . . . . . . . 483Postschedulecmd/Postnschedulecmd . . . . . 484Postsnapshotcmd . . . . . . . . . . . 486Preschedulecmd/Prenschedulecmd . . . . . 487Preservelastaccessdate . . . . . . . . . 489Preservepath . . . . . . . . . . . . 490Presnapshotcmd . . . . . . . . . . . . 492Queryschedperiod . . . . . . . . . . . 494Querysummary . . . . . . . . . . . . 495Quiet . . . . . . . . . . . . . . . 496Quotesareliteral . . . . . . . . . . . 497Replace . . . . . . . . . . . . . . 499Replserverguid . . . . . . . . . . . . 500Replservername . . . . . . . . . . . . 501Replsslport . . . . . . . . . . . . . 503Repltcpport . . . . . . . . . . . . . 504Repltcpserveraddress . . . . . . . . . 505Resetarchiveattribute . . . . . . . . . 507Resourceutilization . . . . . . . . . . 508

Regulating backup and archive sessions . . 509Regulating restore sessions . . . . . . . 510Multiple client session considerations . . . 510

Retryperiod . . . . . . . . . . . . . 511Revokeremoteaccess . . . . . . . . . . 512Runasservice . . . . . . . . . . . . 512Schedcmddisabled . . . . . . . . . . . 513Schedcmdexception . . . . . . . . . . 514Schedlogmax . . . . . . . . . . . . . 515Schedlogname . . . . . . . . . . . . 517Schedlogretention . . . . . . . . . . 518Schedmode . . . . . . . . . . . . . 519Schedrestretrdisabled . . . . . . . . . 521Scrolllines . . . . . . . . . . . . . 521Scrollprompt . . . . . . . . . . . . 522Sessioninitiation . . . . . . . . . . 523Shmport . . . . . . . . . . . . . . 525Showmembers . . . . . . . . . . . . . 526Skipmissingsyswfiles . . . . . . . . . 526Skipntpermissions . . . . . . . . . . 528Skipntsecuritycrc . . . . . . . . . . 528Snapdiff . . . . . . . . . . . . . . 529Snapdiffhttps . . . . . . . . . . . . 534Snapshotproviderfs . . . . . . . . . . 535Snapshotproviderimage . . . . . . . . . 536Snapshotroot . . . . . . . . . . . . 537Srvoptsetencryptiondisabled . . . . . . . 539Srvprepostscheddisabled . . . . . . . . 540Srvprepostsnapdisabled . . . . . . . . . 541Ssl . . . . . . . . . . . . . . . . 542Sslfipsmode . . . . . . . . . . . . . 543Sslrequired . . . . . . . . . . . . . 544Ssldisablelegacytls . . . . . . . . . . 546Stagingdirectory . . . . . . . . . . . 547Subdir . . . . . . . . . . . . . . . 548Subfilebackup . . . . . . . . . . . . 549Subfilecachepath . . . . . . . . . . . 550

Subfilecachesize . . . . . . . . . . . 551Systemstatebackupmethod . . . . . . . . 552Tapeprompt . . . . . . . . . . . . . 553Tcpadminport . . . . . . . . . . . . 554Tcpbuffsize . . . . . . . . . . . . . 555Tcpcadaddress . . . . . . . . . . . . 556Tcpclientaddress . . . . . . . . . . . 557Tcpclientport . . . . . . . . . . . . 557Tcpnodelay . . . . . . . . . . . . . 558Tcpport . . . . . . . . . . . . . . 559Tcpserveraddress . . . . . . . . . . . 560Tcpwindowsize . . . . . . . . . . . . 560Timeformat . . . . . . . . . . . . . 562Toc . . . . . . . . . . . . . . . . 563Todate . . . . . . . . . . . . . . . 564Totime . . . . . . . . . . . . . . . 565Txnbytelimit . . . . . . . . . . . . 566Type . . . . . . . . . . . . . . . 567Usedirectory . . . . . . . . . . . . 568Useexistingbase . . . . . . . . . . . 569Usereplicationfailover . . . . . . . . . 570V2archive . . . . . . . . . . . . . 570Vappmc . . . . . . . . . . . . . . . 571Vcdhost . . . . . . . . . . . . . . 572Vcdpw . . . . . . . . . . . . . . . 573Vcduser . . . . . . . . . . . . . . 573Verbose . . . . . . . . . . . . . . 574Verifyimage . . . . . . . . . . . . . 575Virtualfsname . . . . . . . . . . . . 575Virtualnodename . . . . . . . . . . . 576Vmautostartvm . . . . . . . . . . . . 577Vmbackdir . . . . . . . . . . . . . 578Vmbacknodelete . . . . . . . . . . . . 579Vmbackupmailboxhistory . . . . . . . . . 580Vmbackuptype . . . . . . . . . . . . 581Vmbackvcbtransport . . . . . . . . . . 582Vmchost . . . . . . . . . . . . . . 583Vmcpw . . . . . . . . . . . . . . . 584Vmctlmc . . . . . . . . . . . . . . 585Vmcuser . . . . . . . . . . . . . . 586Vmdatastorethreshold . . . . . . . . . 587Vmdefaultdvportgroup . . . . . . . . . 588Vmdefaultdvswitch . . . . . . . . . . 589Vmdefaultnetwork . . . . . . . . . . 590Vmdiskprovision . . . . . . . . . . . 591Vmenabletemplatebackups . . . . . . . . 591Vmexpireprotect . . . . . . . . . . . 593Vmiscsiadapter . . . . . . . . . . . . 594Vmiscsiserveraddress . . . . . . . . . 595Vmlimitperdatastore . . . . . . . . . . 596Vmlimitperhost . . . . . . . . . . . . 597Vmlist . . . . . . . . . . . . . . . 598Vmmaxparallel . . . . . . . . . . . . 598Vmmaxvirtualdisks . . . . . . . . . . 599Vmmc . . . . . . . . . . . . . . . 601Vmmountage . . . . . . . . . . . . . 601Vmnoprdmdisks . . . . . . . . . . . . 602Vmnovrdmdisks . . . . . . . . . . . . 603Vmpreferdagpassive . . . . . . . . . . 604Vmprocessvmwithindependent . . . . . . . 604Vmprocessvmwithprdm . . . . . . . . . . 606

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

||

||

Vmrestoretype . . . . . . . . . . . . 607Vmskipctlcompression . . . . . . . . . 609Vmskipmaxvirtualdisks . . . . . . . . . 610Vmskipmaxvmdks. . . . . . . . . . . 611Vmstoragetype . . . . . . . . . . . . 611Vmtagdatamover . . . . . . . . . . . . 612Vmtempdatastore . . . . . . . . . . . 615Vmverifyifaction . . . . . . . . . . . 615Vmverifyiflatest . . . . . . . . . . . 617Vmvstortransport . . . . . . . . . . . 618Vssaltstagingdir . . . . . . . . . . . 619Vssusesystemprovider . . . . . . . . . 620Vmtimeout . . . . . . . . . . . . . 621Webports . . . . . . . . . . . . . . 622Wildcardsareliteral . . . . . . . . . . 623

Chapter 12. Using commands . . . . 625Start and end a client command session . . . . 628

Process commands in batch mode . . . . . 628Process commands in interactive mode . . . . 629

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

Command name . . . . . . . . . . . 630Options . . . . . . . . . . . . . . 630

Options in interactive mode . . . . . . 630Parameters . . . . . . . . . . . . . 630File specification syntax . . . . . . . . . 631

Wildcard characters . . . . . . . . . . . 632Client commands reference . . . . . . . . . 633Archive . . . . . . . . . . . . . . . 633

Open file support . . . . . . . . . . . 635Archive FastBack . . . . . . . . . . . . 636Backup FastBack . . . . . . . . . . . . 639Backup Group . . . . . . . . . . . . . 642Backup Image . . . . . . . . . . . . . 644

Offline and online image backup . . . . . . 646Utilizing image backup to perform file systemincremental backup . . . . . . . . . . 647

Backup NAS . . . . . . . . . . . . . 648Backup Systemstate . . . . . . . . . . . 650Backup VAPP . . . . . . . . . . . . . 652Backup VM . . . . . . . . . . . . . . 658Cancel Process . . . . . . . . . . . . . 670Cancel Restore . . . . . . . . . . . . . 670Delete Access . . . . . . . . . . . . . 671Delete Archive . . . . . . . . . . . . . 672Delete Backup . . . . . . . . . . . . . 674Delete Filespace . . . . . . . . . . . . 677Delete Group . . . . . . . . . . . . . 678Expire . . . . . . . . . . . . . . . . 680Help . . . . . . . . . . . . . . . . 681Incremental . . . . . . . . . . . . . . 683

Open file support . . . . . . . . . . . 686Journal-based backup. . . . . . . . . . 687Backing up NTFS or ReFS volume mount points 688

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

Back up Microsoft Dfs root . . . . . . . . 689Incremental-by-Date . . . . . . . . . . 689Adaptive subfile backups . . . . . . . . 690

Associate a local snapshot with a server filespace . . . . . . . . . . . . . . . 690

Loop . . . . . . . . . . . . . . . . 690Macro . . . . . . . . . . . . . . . . 692Monitor Process . . . . . . . . . . . . 692Preview Archive . . . . . . . . . . . . 693Preview Backup . . . . . . . . . . . . 694Query Access . . . . . . . . . . . . . 695Query Adobjects . . . . . . . . . . . . 696Query Archive . . . . . . . . . . . . . 697Query Backup . . . . . . . . . . . . . 700

Query NAS file system images . . . . . . 703Query Backupset . . . . . . . . . . . . 703

Query Backupset without the backupsetnameparameter . . . . . . . . . . . . . 705

Query Filespace . . . . . . . . . . . . 706Query NAS file spaces . . . . . . . . . 708

Query Group . . . . . . . . . . . . . 709Query Image . . . . . . . . . . . . . 710Query Inclexcl . . . . . . . . . . . . . 712Query Mgmtclass . . . . . . . . . . . . 713Query Node. . . . . . . . . . . . . . 714Query Options . . . . . . . . . . . . . 715Query Restore . . . . . . . . . . . . . 716Query Schedule . . . . . . . . . . . . 717Query Session . . . . . . . . . . . . . 717Query Systeminfo . . . . . . . . . . . 718Query Systemstate . . . . . . . . . . . 720Query VAPP . . . . . . . . . . . . . 721Query VM . . . . . . . . . . . . . . 725Restart Restore . . . . . . . . . . . . . 729Restore . . . . . . . . . . . . . . . 730

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

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

Restore Adobjects. . . . . . . . . . . . 738Restore Backupset . . . . . . . . . . . 739

Restore backup sets: considerations andrestrictions . . . . . . . . . . . . . 742Restore backup sets in a SAN environment . . 743Restore Backupset without the backupsetnameparameter . . . . . . . . . . . . . 744

Restore Group . . . . . . . . . . . . . 746Restore Image . . . . . . . . . . . . . 748Restore NAS . . . . . . . . . . . . . 751Restore Systemstate . . . . . . . . . . . 753Restore VAPP . . . . . . . . . . . . . 755Restore VM . . . . . . . . . . . . . . 758Retrieve . . . . . . . . . . . . . . . 766

Retrieve archives from file spaces that are notUnicode-enabled . . . . . . . . . . . 769Retrieve named streams . . . . . . . . . 769Retrieve sparse files . . . . . . . . . . 770

Schedule . . . . . . . . . . . . . . . 770Selective . . . . . . . . . . . . . . . 771

Contents ix

||

Open file support . . . . . . . . . . . 774Adaptive subfile backups . . . . . . . . 774Associate a local snapshot with a server filespace . . . . . . . . . . . . . . . 775

Set Access . . . . . . . . . . . . . . 775Set Event. . . . . . . . . . . . . . . 778Set Netappsvm . . . . . . . . . . . . 780Set Password . . . . . . . . . . . . . 781Set Vmtags . . . . . . . . . . . . . . 787

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

Notices . . . . . . . . . . . . . . 793

Glossary . . . . . . . . . . . . . 797

Index . . . . . . . . . . . . . . . 799

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

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

directories . . . . . . . . . . . . . 948. Options for controlling processing using

include and exclude statements . . . . . . 959. Wildcard and other special characters . . . . 98

10. Specifying a drive specification usingwildcards . . . . . . . . . . . . . 99

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

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

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

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

backup-archive client GUI . . . . . . . 11816. Planning your backups . . . . . . . . 12117. Command line backup examples . . . . . 12718. Maximum file size . . . . . . . . . . 13519. Comparing incremental image backup

methods . . . . . . . . . . . . . 15720. NAS options and commands . . . . . . 16121. Backup and restore capabilities for VMware

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

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

23. Client command line informational messages 18224. UNC examples . . . . . . . . . . . 18925. Command-line restore examples . . . . . 19626. Backup set GUI restore restrictions . . . . 20727. Backup set command-line restore restrictions 20728. Components for the restore command when

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

you restore files to a different computer. . . 22130. NAS options and commands . . . . . . 23731. Command-line archive examples . . . . . 24132. Command line examples of retrieving

archives . . . . . . . . . . . . . 24633. Sample classic query schedule output 25534. Sample enhanced query schedule output 25635. Client return codes and their meanings 26536. Default attribute values in the standard

management class . . . . . . . . . . 26937. TCP/IP options . . . . . . . . . . . 29638. Named Pipes communication option 29739. Shared memory communication options 29740. Backup and archive processing options 297

41. Restore and retrieve processing options 30642. Scheduling options. . . . . . . . . . 30943. Format and language options . . . . . . 31044. Command processing options . . . . . . 31145. Authorization options . . . . . . . . . 31146. Error processing options . . . . . . . . 31247. Transaction processing options . . . . . . 31248. Web client options . . . . . . . . . . 31349. Diagnostics options . . . . . . . . . 31350. Client command options . . . . . . . . 31551. Options that are valid on the initial command

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

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

distribute backups.. . . . . . . . . . 32454. Clusternode and clusterdisksonly

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

sources. . . . . . . . . . . . . . 37456. System services components and

corresponding keywords . . . . . . . . 40257. Other optional parameters . . . . . . . 43458. Incremental command: Related options 53159. Effects of server and client SSL settings on

success or failure of login attempts . . . . 54560. Commands . . . . . . . . . . . . 62561. Wildcard characters . . . . . . . . . 63362. Archive command: Related options . . . . 63463. Archive FastBack command: Related options 63764. Backup FastBack command: Related options 64065. Backup Group command: Related options 64366. Backup Image command: Related options 64567. Backup NAS command: Related options 65068. Backup VAPP command: Related options 65469. Delete Archive command: Related options 67370. Delete Backup command: Related options 67671. Delete Filespace command: Related options 67872. Delete Group command: Related options 67973. Expire command: Related options. . . . . 68174. Incremental command: Related options 68475. Query Adobjects command: Related options 69676. Query Archive command: Related options 69877. Query Backup command: Related options 70178. Query Backupset command: Related options 70479. Query Backupset command: Related options 70680. Query Filespace command: Related options 70781. Query Group command: Related options 70982. Query Image command: Related options 71183. Query Mgmtclass command: Related options 71484. Query Node command: Related options 71585. Query Options command: Related options 71686. Query Systeminfo command: Related options 72087. Query Systemstate command: Related options 72088. Query VAPP command: Related options 723

© Copyright IBM Corp. 1993, 2016 xi

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

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

91. Restore command: Related options . . . . 73392. Restore Adobjects command: Related options 73893. Restore Backupset command: Related options 74194. Restore Group command: Related options 74795. Restore Image command: Related options 74996. Restore NAS command: Related options 752

97. Restore Systemstate command: Relatedoptions . . . . . . . . . . . . . 754

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

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

restoring Hyper-V virtual machines . . . . 765101. Retrieve command: Related options . . . . 767102. Schedule command: Related options . . . . 771103. Selective command: Related options . . . . 773

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 121“What's new for Version 7.1.6” 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 IBM Knowledge Center.

© Copyright IBM Corp. 1993, 2016 xiii

http://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

What's new for Version 7.1.6

IBM Tivoli Storage Manager Version 7.1.6 introduces new features and updates.

For a list of new features and updates in this release and previous Version 7releases, see Backup-archive client updates.

New and changed information in this product documentation is indicated by avertical bar (|) to the left of the change.Related information:“About this publication” on page xiii

© Copyright IBM Corp. 1993, 2016 xvii

http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.6/client/r_new_for_version.html

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 backup-archive client works in conjunction with the Tivoli Storage Managerserver. Contact your Tivoli Storage Manager server administrator to obtain backupor archive access to the server, or refer to the server publications to install andconfigure a Tivoli Storage Manager server.Related concepts:“What's new for Version 7.1.6” on page xvii“Planning your backups (Windows)” on page 121

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.6 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 in technote 1053218.

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:

© Copyright IBM Corp. 1993, 2016 1

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

– Ask your Tivoli Storage Manager administrator to rename the existing systemstate file spaces. Once the migration is complete and you have new backupsof the system state data, your administrator can delete the renamed filespaces. The file spaces to rename include one or more of the following:- 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.The client backs up all other directories and file spaces during the next fullincremental 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 client uses the non-Unicode filespace as the default file space for backup and restore operations.

Additional upgrade informationWhen you upgrade the backup-archive client, there is additional information toconsider 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.v For a list of new and changed messages since the previous Tivoli Storage

Manager release, see the client_message.chg file in the client package.

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

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

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


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 deploymentmanager and temporary files possibly left from the previous installation.

Sun 10/11/2009 10:17:10.53 WARNING: Still waiting for the result of querysystem 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 V6.2 andlater clients.

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 332

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 “Windows client environment requirements”v “NDMP support requirements (Extended Edition only)” on page 7

For current information about the client environment prerequisites for all of thesupported backup-archive client platforms, see technote 1243309.

Windows client environment requirementsThis section contains client environment information, backup-archive clientcomponents, and hardware and software requirements for the supported Windowsplatforms.



Windows client installable componentsThe backup-archive client is comprised of several installable components.

The installable components for the Windows backup-archive client are as follows:v Backup-archive command-line clientv Administrative clientv Backup-archive client graphical user interface, which uses Oracle Java™

technologyv 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 backup-archive client on Windows requires a minimum amount of disk spacefor installation and a supported operating system.

For software and hardware requirements for all supported versions of Windowsclients, including the most recent fix packs, seetechnote 1197133.

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 Windowsbackup-archive 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

IBM AIX®, HP-UX IA®,Linux, Oracle 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.

Table 2 on page 7 shows the supported and unsupported features on the variousWindows platforms.



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 Windows backup-archive client supports the following types of file systems:v GPFS™

Restriction: The Windows client can back up or restore files in a Windows-onlyGPFS cluster. If the GPFS cluster contains mixed nodes (some AIX, some Linux,and some Windows), you must use the AIX or Linux clients to protect data inthe 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 Edition


v Tape drive and tape library. For supported combinations, go to: productinformation

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

For information about integrating Tivoli Storage Manager and Tivoli StorageManager FastBack, see Integrating Tivoli Storage Manager FastBack and TivoliStorage Manager.

You can install the Tivoli Storage Manager client in one of the following ways:v Install the backup-archive 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 the backup-archive client on a workstation where the FastBack DisasterRecovery Hub is installed. In this case, the prerequisites are: the FastBackDisaster Recovery Hub setup, the FastBack shell, and the FastBack mount.

v Install the backup-archive client on a workstation where neither the FastBackserver or the FastBack Disaster Recovery Hub is installed. In this case, ensurethat 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 67


http://www.ibm.com/software/tivoli/products/storage-mgr/product-links.htmlhttp://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/SSGSG7_6.4.0/com.ibm.itsm.srv.fbint.doc/t_fbint.htmlhttp://www.ibm.com/support/knowledgecenter/SSGSG7_6.4.0/com.ibm.itsm.srv.fbint.doc/t_fbint.html

Client configuration wizard for Tivoli Storage Manager FastBackThe backup-archive client provides a wizard to configure the backup-archive clientfor 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 client configuration wizard for Tivoli Storage Manager FastBack on32-bit Windows systems that are supported by both Tivoli Storage Manager andFastBack. The configuration wizard must be installed on the same workstationwhere the FastBack server resides, or where a FastBack Disaster Recovery Hub isdeployed. You can use the client configuration wizard for Tivoli Storage ManagerFastBack with Tivoli Storage Manager FastBack Version 5.5.1 or later versions.Related concepts:“Configuring the backup-archive client to protect FastBack client data” on page 69

Installing the backup-archive client from the DVDsYou can install the backup-archive client and its components from Tivoli StorageManager DVDs.

About this task

To install the backup-archive client from a DVD, you change to the directory thatcontains the installation image for your client operating system and you install thebackup-archive client and its components.

The installation image for Windows backup-archive clients is in the setup directory.

Procedure1. Install the backup-archive clients by starting the installation program from the

appropriate installation image directory.2. Optional: Copy the installation images from the DVD to a server workstation

so that client workstations can mount the server volume and start theinstallation from the server copies.Copy all of the files that are in the DVD installation directory for the clientoperating systems and all of the subdirectories and files that are subordinate toit.For example, Windows users can use the xcopy command to copy the setupdirectory and its subdirectories from the Windows DVD to a remote disk. Inthis example, the H drive represents the DVD drive letter and the X driverepresents the remote disk: xcopy h:\setup\* x:\ /s. Substitute the driveletters that are appropriate for your environment.

Related tasks:“Windows backup-archive client installation overview”

Windows backup-archive client installation overviewYou can install the Tivoli Storage Manager Windows backup-archive client fromthe product DVD, or other installation media.


Before you begin

Before you begin a Windows client installation, ensure that the system that youwant to install the client on meets the client requirements. Then, determine thetype of installation that you need to perform, and follow the steps in theappropriate procedure.

For the hardware and software requirements for the Windows client, see technote1197133.Related concepts:“Automatic backup-archive client deployment” on page 3Related tasks:“Creating and modifying the client options file” on page 29“Starting a web client session” on page 115

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


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

Installation type Installation description

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 Windows backup-archive client for the firsttime.

Before you begin

If you have an earlier version of the Windows backup-archive client that is alreadyinstalled on a node and you want to upgrade it to Version 7.1.6, see “Upgradingthe Windows client” on page 15.

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.

Procedure1. 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 spinstall.exe file.Double-click the spinstall.exe file.


||||

Option Description

Install by using a compressed installationfile

1. The Tivoli Storage Manager V7.1 clientrelease 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. By default, the uncompressed files arestored in the current disk drive, in thedownload directory\TSMClient directory.If the installation program detects filesfrom another client installation attemptin this directory, you are prompted todetermine whether you want tooverwrite the old files. If you receive thisprompt, enter A to overwrite the existingfiles; this selection ensures that only thefiles from the current installation areused.

5. In the download directory\TSMClientdirectory, double-click the spinstall.exefile to start the client installationprogram.

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 backup-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 server administrator. If you are not sure what to select,accept the default setting (TCP/IP). If the default setting does not work whenthe client attempts to connect to the server, contact the server administrator todetermine 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

ibm tivoli storage manager for windows backup-archive clients: … · 2016. 6. 7. ·...

Documents