Date post: | 05-Apr-2018 |
Category: |
Documents |
Upload: | bupbechanh |
View: | 215 times |
Download: | 0 times |
of 190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
1/190
ibm.com/redbooks
Deploying the Tivoli Storage
Manager Clientin a Windows 2000Environment
Pat Randall
Javier Hernandez
Rod Macleod
Andrew Pearce
Using the TSM client support for
Windows 2000
Planning and implementing
backup scenarios
Restoring Windows 2000
objects
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
2/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
3/190
Deploying the Tivoli Storage Manager Client
in a Windows 2000 Environment
April 2001
SG24-6141-00
International Technical Support Organization
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
4/190
Copyright International Business Machines Corporation 2001. All rights reserved.
Note to U.S Government Users Documentation related to restricted rights Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.
First Edition (April 2001)
This edition applies to Tivoli Storage Manager V4.1.2 for use with the Microsoft Windows 2000
Operating System.
Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. 471F Building 80-E2650 Harry Road
San Jose, California 95120-6099
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the
information in any way it believes appropriate w ithout incurring any obligation to you.
Before using this information and the product it suppor ts, be sure to read the general information in
Appendix A, Special notices on page 157.
Take Note!
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
5/190
Copyright IBM Corp. 2001 iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
The team that wrote this Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1. Introducing TSM client support for Windows 2000 . . . . . . . 1
1.1 Types of Windows 2000 implementations . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1 Windows 2000 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.2 Windows 2000 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.3 Windows 2000 Advanced Server . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.4 Windows 2000 Datacenter Server. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Introduction to TSM 4.1.2 support for Windows 2000 . . . . . . . . . . . . . . 3
1.3 System State components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.2 System boot files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.3 Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.4 Event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3.5 COM+ Class DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.6 Certificate Services DB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.7 Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.8 System Volume (SYSVOL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.9 File Replication Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.10 Cluster DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 File System (NTFS) components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4.1 Encrypted File System (EFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.2 Reparse Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.3 Multiple Named Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.4 The Change Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4.5 Sparse file support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4.6 Distributed Link Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4.7 Directory Junctions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4.8 Volume Mount Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.5 Storage components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.5.1 Disk Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.5.2 Distributed File System (DFS) . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.3 Single Instance Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.4 Removable Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.5 Remote Storage Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
6/190
iv Deploying Tivoli Storage Manager for Windows 2000
1.5.6 Indexing service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client . . . . . . . . . 19
2.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 New features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2.1 System Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.2 SYSTEMOBJECT domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.3 System Objects managed as a group . . . . . . . . . . . . . . . . . . . . . 21
2.2.4 New commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.5 Support for mobile computer users enhanced. . . . . . . . . . . . . . . 24
2.2.6 ODBC driver not included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.7 InstallShield for Windows Installer used . . . . . . . . . . . . . . . . . . . 24
2.2.8 Registry backup now processes all hives . . . . . . . . . . . . . . . . . . 24
2.2.9 Event log backup now processes all logs . . . . . . . . . . . . . . . . . . 25
2.2.10 Restore to same location only. . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.11 Management class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 What has changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.1 System Objects require new backup. . . . . . . . . . . . . . . . . . . . . . 25
2.3.2 Changed commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.3 Local backup only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.4 One step backup and restore of System State . . . . . . . . . . . . . . 262.3.5 BACKUPREGISTRY option redundant . . . . . . . . . . . . . . . . . . . . 26
2.3.6 Restore without services active . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4 What has been fixed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.1 APAR list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.5 Advantages of TSM versus Microsoft NTbackup. . . . . . . . . . . . . . . . . 28
2.5.1 Using NTbackup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.5.2 Using Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3. Implementation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1 Tivoli Storage Manager Server code level . . . . . . . . . . . . . . . . . . . . . 31
3.2 Server registration modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3 Server storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.1 Database size calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.2 Recovery Log size calculation . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.3 Primary storage pool size calculation . . . . . . . . . . . . . . . . . . . . . 36
3.4 Network bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.5 Warnings about migration from a previous client level . . . . . . . . . . . . 37
3.6 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.7 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.8 User permissions for Windows 2000. . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.9 System information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
7/190
v
Chapter 4. Installation and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.1 Include-exclude list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.2 Tivoli Storage Manager 4.1.2 client install procedure . . . . . . . . . . . . . 45
4.2.1 Tivoli Storage Manager Client configuration wizards. . . . . . . . . . 51
4.3 ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4 Post install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5 Uninstalling the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.1 Remove services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.2 Remove code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.5.3 Remove temporary files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.5.4 Remove miscellaneous files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.6 Tips and hints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.6.1 Installation using Terminal Server. . . . . . . . . . . . . . . . . . . . . . . . 73
4.6.2 Renaming the Tivoli Storage Manager client node name . . . . . . 73
Chapter 5. Windows 2000 backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.1 Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.2 Permissions required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.2.1 Back up system objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.2.2 Back up regular files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.3 Scheduled backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.4 Client-controlled backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.4.1 GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.4.2 Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.4.3 Web client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.5 Backing up Windows 2000 Professional . . . . . . . . . . . . . . . . . . . . . . . 78
5.6 Backing up system objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.6.1 \ADSM.SYS contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.6.2 Individual system object component backup . . . . . . . . . . . . . . . . 80
5.6.3 Creating inactive versions of System Objects . . . . . . . . . . . . . . . 84
5.7 Backing up DFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.7.1 DFSBACKUPMNTPNT YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.7.2 DFSBACKUPMNTPNT NO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.8 Tips and hints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.8.1 Backup frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.8.2 Perform test restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.8.3 Windows 2000 user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.8.4 Transaction limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.8.5 MSINFO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.8.6 Tree view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 6. Windows 2000 restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.1 Permissions to restore Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . 91
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
8/190
vi Deploying Tivoli Storage Manager for Windows 2000
6.2 Restoring a Windows 2000 system. . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.2.1 Restore methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.2.2 The role of the System Object in the restore process . . . . . . . . . 93
6.2.3 Restoring a Windows 2000 Professional or member server . . . . 94
6.2.4 Restoring a Win 2000 domain controller (non-authoritatively) . . 102
6.3 Restoring Windows 2000 objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6.3.1 Restoring components from the TSM System Object . . . . . . . . 111
6.3.2 Distributed File System (DFS) . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.3.3 Disk quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466.3.4 Sparse files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
6.3.5 Junction points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
6.3.6 Removable Storage Management (RSM) . . . . . . . . . . . . . . . . . 148
6.3.7 Other Windows 2000 databases . . . . . . . . . . . . . . . . . . . . . . . . 150
6.4 Restoring user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
6.5.1 Restoring Windows 2000 Professional or member server . . . . . 154
6.5.2 Restoring a Domain Controller (non-authoritatively) . . . . . . . . . 155
Appendix A. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Appendix B. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
B.1 IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
B.2 IBM Redbooks collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
B.3 Tivoli publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
IBM Redbooks fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
9/190
Copyright IBM Corp. 2001 vii
Figures
1. System State in NTbackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. System Object in Tivoli Storage Manager Client . . . . . . . . . . . . . . . . . . . . . 6
3. Example of System Objects in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4. Example of a Query Systemobject command . . . . . . . . . . . . . . . . . . . . . . 21
5. Example of query inclexcl command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6. Example of show systemobject command. . . . . . . . . . . . . . . . . . . . . . . . . 24
7. Recommended include-exclude list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8. Select language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9. InstallSheild starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10. Choose destination folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
11. Select type of install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12. Custom setup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
13. Ready to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
14. InstallSheild complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
15. Start setup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
16. Choose type of install using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
17. Create a new dsm.opt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
18. Enter node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
19. Choose communication method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5620. Set TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
21. Modify domain and include-exclude list . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
22. Install a new Web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
23. Select options file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
24. Set Web client parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
25. Enter node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
26. Enter login account ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
27. Web client is done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
28. Install a new client scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
29. Enter scheduler name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
30. Choose scheduler options file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
31. Set log file names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6732. Enter node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
33. Select login account ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
34. Scheduler options done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
35. Client scheduler installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
36. Tivoli Storage Manager Client Service settings . . . . . . . . . . . . . . . . . . . . . 71
37. Example of System Objects in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
38. Example of a System Object Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
39. Query filespace command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
40. Example of a Query Systemobject command . . . . . . . . . . . . . . . . . . . . . . 82
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
10/190
viii Deploying Tivoli Storage Manager for Windows 2000
41. Example of Query Occupancy command . . . . . . . . . . . . . . . . . . . . . . . . . 82
42. GUI restore screen showing dates, times System Objects backed up . . . 83
43. a simple DFS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
44. Example of Query systemobject command . . . . . . . . . . . . . . . . . . . . . . . . 94
45. Restore options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
46. Successful Windows 2000 recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
47. Restore options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
48. Successful Windows 2000 recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
49. System Object Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11650. Example of authoritative restore command . . . . . . . . . . . . . . . . . . . . . . . 120
51. Restore System Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
52. Example of a Complete Sysvol Directory Structure . . . . . . . . . . . . . . . . . 122
53. Example of Active Directory Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
54. Example of authoritative restore command . . . . . . . . . . . . . . . . . . . . . . . 124
55. System Volume (sysvol) Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
56. Group policy object GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
57. System Volume Policy Folder s Identified by GUID. . . . . . . . . . . . . . . . . 127
58. Registry staging area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
59. Event Log Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
60. File level restore tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
61. DFS Link selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13562. Dialog box to specify objects destination. . . . . . . . . . . . . . . . . . . . . . . . . 136
63. File replace dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
64. Status report post restoration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
65. Not available share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
66. Not able to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
67. Selecting data to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
68. Nonexistent target directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
69. Restoring links directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
70. Restoring files from links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
71. Nonexistent pointed directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
72. Changing the IDLETIMEOUT parameter. . . . . . . . . . . . . . . . . . . . . . . . . 147
73. Selecting the RSM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14974. Reboot option after RSM restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
75. Restoring a user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
76. File replace dialog box for user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 153
77. File replace on reboot for user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 153
78. Reboot message to apply changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
11/190
Copyright IBM Corp. 2001 ix
Tables
1. Comparison of selected features in Windows 2000 implementations . . . . . 1
2. Tivoli Storage Manager client support for Windows 2000 . . . . . . . . . . . . . . 3
3. Windows 2000 event log file names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Server planning tasks checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5. Client planning task checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6. Typical disk space occupancy, Windows 2000 Systems (system data) . . 33
7. Sample client requirements worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8. Rules of thumb for selecting percentage of data changed. . . . . . . . . . . . . 35
9. Typical data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
10. Disk requirements for Tivoli Storage Manager Client . . . . . . . . . . . . . . . . 39
11. System Information sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12. Tivoli Storage Manager services settings . . . . . . . . . . . . . . . . . . . . . . . . . 71
13. Windows 2000 Restore Process Summary . . . . . . . . . . . . . . . . . . . . . . . . 94
14. Windows 2000 Domain Controller FSMO Roles . . . . . . . . . . . . . . . . . . . 103
15. Domain Controller Restore Process Summary . . . . . . . . . . . . . . . . . . . . 104
16. Active Directory Restore Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
17. Example scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
18. What is restored for each DFSBACKUPMNTPNT option . . . . . . . . . . . . 132
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
12/190
x Deploying Tivoli Storage Manager for Windows 2000
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
13/190
Copyright IBM Corp. 2001 xi
Preface
This IBM Redbook will help you use the Tivoli Storage Manager (TSM) client
at level 4.1.2 with Microsoft Windows 2000. It is intended as a supplement to
other TSM redbooks and documentation.
This book explains special considerations for using the TSM 4.1.2 client with
Windows 2000. We cover implementation planning, installation, and setup,
various backup considerations, and their associated restore methodologies.
This book is not intended to be a Windows 2000 primer or to cover TSM
server implementation.
Readers are expected to be familiar with MS Windows 2000 administration
concepts, functions, and features. Typically, they will be planning the
deployment of Windows 2000, or will have already deployed it.
We assume a basic understanding of TSM concepts and a good working
knowledge of previous TSM clients (GUI and command line interfaces).
The team that wrote this Redbook
This Redbook was produced by a team of specialists from around the world
working at the International Technical Support Organization San Jose Center.
Pat Randall is a Distributed Storage Software Specialist with the IBM
International Technical Support Organization, San Jose, California. He has
written 11 Redbooks on ADSM and Tivoli Storage Manager, teaches IBM
classes worldwide on all areas of distributed storage, and is a consultant in
disaster and business recovery. Before joining the ITSO in July 1996, Pat
worked in IBM UK's Business Recovery Services as a Solutions Architect.
Javier Hernandez is a Project Leader in Mexico with BYGPROY Tecnica en
Servicios S.A. de C.V, Veracruz, Ver. Mex. He has 3 years of experience inNetfinity Servers, Windows NT and Tivoli products. He holds a degree in
Computer Sciences from the Instituto Tecnologico de Veracruz. His areas of
expertise include Netfinity Server installation, performance and tuning,
Windows environments, Tivoli IT Director, and Tivoli Storage Manager.
Rod Macleod is a Senior System Programmer with TELUS Communications,
Inc. in Edmonton, Alberta, Canada. He has 20 years of experience in the
systems administration field and five years experience in ADSM/TSM. He
holds a degree in Computational Science from the University of
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
14/190
xii Deploying Tivoli Storage Manager for Windows 2000
Saskatchewan. His areas of expertise include OS/390, storage management,
and ADSM/TSM. He has co-authored one previous IBM Redbook.
Andrew Pearce is a Systems Technologist at Computer Sciences
Corporation in Wollongong, New South Wales, Australia. He has 7 years of
experience in the distributed systems field, working with Windows NT based
systems since 1994. He has spent the last year working on a Windows 2000
design project for one of Australias largest companies. His areas of expertise
include storage management and data recovery.
Thanks to the following people for their invaluable contributions to this project:
Jim Smith
Tivoli Systems
Mike Dile
Tivoli Systems
Don Moxley
Tivoli Systems
Comments welcome
Your comments are important to us!
We want our Redbooks to be as helpful as possible. Please send us your
comments about this or other Redbooks in one of the following ways:
Fax the evaluation form found in IBM Redbooks review on page 171 to
the fax number shown on the form.
Use the online evaluation form found at ibm.com/redbooks
Send your comments in an Internet note to [email protected]
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
15/190
Copyright IBM Corp. 2001 1
Chapter 1. Introducing TSM client support for Windows 2000
In this chapter we provide a brief overview for each of the Windows 2000
products. We introduce Windows 2000 features and enhancements and
discuss their support by the Tivoli Storage Manager 4.1.2 client.
1.1 Types of Windows 2000 implementations
Windows 2000 is divided into four implementations:
Professional
Server
Advanced Server
Datacenter Server
As shown in Table 1, each implementation is aimed at a specific market and
contains progressively more capability.
Table 1. Comparison of selected features in Windows 2000 implementations
Professional Server AdvancedServer
DatacenterServer
MaximumCPUssupported
2 4 8 32
Maximummemorysupported
4 GB 4 GB 8 GB 64 GB
Services likeActiveDirectory
No Yes Yes Yes
Clustering No No 2-node cluster 4-node cluster
Network LoadBalancing
No No Yes Yes
WinsockDirect
No No No Yes
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
16/190
2 Deploying Tivoli Storage Manager for Windows 2000
1.1.1 Windows 2000 Professional
Windows 2000 Professional is aimed at corporate desktops and business
mobile computing (laptops and notebooks). It provides the functions required
by desktop applications such as word processing and spreadsheets, and
network connectivity to the Internet, an intranet, or to cross-platform
applications. It provides a user interface similar to Windows 98 while
improving the speed of the operating system over Windows NT.
1.1.2 Windows 2000 Server
Windows 2000 Server is Microsofts entry-level server operating system. It is
targeted for file, print, intranet, and infrastructure servers. Windows 2000
Server can, but does not necessarily need to, run all of Microsofts server
services and features such as the Active Directory, with the exception of the
clustering services and features.
1.1.3 Windows 2000 Advanced Server
Windows 2000 Advanced Server is targeted to run e-commerce and
line-of-business applications while providing enhanced reliability, availability,
and scalability. It supports larger memory and more processors than Windows
2000 Server. Windows 2000 Advanced Server allows for clusteredconfigurations and network load balancing of IP t raffic.
1.1.4 Windows 2000 Datacenter Server
Windows 2000 Datacenter Server is Microsofts most powerful server
operating system providing the highest levels of availability and scalability.
Windows 2000 Datacenter Server is designed for applications like online
transaction processing, data warehouses and server consolidation. It
provides high speed SAN communications through the Winsock Direct facility.
Windows 2000 Datacenter Server has a new Process Control tool to manage
job objects of associated processes.
We did not test Windows 2000 Datacenter Server and it is not covered in
this redbook.
Note
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
17/190
Chapter 1. Introducing TSM client support for Windows 2000 3
1.2 Introduction to TSM 4.1.2 support for Windows 2000
The following section introduces the Windows 2000 components that require
special consideration when using the T ivoli Storage Manager 4.1.2 backup
client. More detailed information about specific backup and restore issues is
available in other sections of this book.
Table 2 provides a summary of the Windows 2000 components that are
supported by the Tivoli Storage Manager 4.1.2 client. An explanation abouteach component can be found following this table.
Table 2. Tivoli Storage Manager client support for Windows 2000
Windows 2000component
Explicit Support byv4.1.2 client
Comments
System State related
System boot files yes
Registry yes
Event Logs yes
COM+ database yes
Performance counters yes Included in system files
Certificate Servicesdatabase
yes
System Volume directory yes
Active Directory yes Non-authoritative restoresonly. Use NTDSUTIL forauthoritative restores.
File Replication service yes
Cluster database yes
Storage Related
Disk Quotas yes
Single Instance Store no
Removable StorageManagement database
yes
Remote Storage Servicedatabase
yes
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
18/190
4 Deploying Tivoli Storage Manager for Windows 2000
1.3 System State components
In this section, we introduce the Windows 2000 System State and follow this
with a discussion about some of the issues that affect the way Tivoli Storage
Manager is able to handle this important Windows 2000 feature. We also
discuss the individual System State components.
1.3.1 Introduction
Windows 2000 has several key components (represented as files anddatabases) that are logically grouped together to ensure the operating
system is backed up in a consistent state. Microsoft defines the collection of
these components as the System State. Figure 1 illustrates the logical
grouping of System State components in the Windows 2000 native backup
application, NTbackup.
Distributed File System yes
Indexing Service no
NTFS Related
NTFS Reparse Points yes
NTFS Directory Junctions yes
NTFS Volume MountPoints
yes
NTFS Spare Files yes
Terminal services db No
NTFS Change Journal No Not required. TivoliStorage Manager will backup changed data.
Encrypted File System yes
Distributed link trackingand object IDs
yes
Windows 2000component
Explicit Support byv4.1.2 client
Comments
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
19/190
Chapter 1. Introducing TSM client support for Windows 2000 5
Figure 1. System State in NTbackup
Rather than using Microsofts logical place holder (the System State), the
Tivoli Storage Manager client places individual components (such as Active
Directory and the registry) in the Tivoli Storage Manager System Object. Thisis shown in Figure 2. Other Windows 2000 features that are not part of the
Microsoft System State, such as the Removable Storage Management
database, are also included as components of the Tivoli Storage Manager
System Object.
The Tivoli Storage Manager client does notuse the concept of the System
State. Windows 2000 components which Microsoft has placed in the
System State, have been placed in the Tivoli Storage Manager client s
System Object.
It is very easy to become confused when the terms System State andSystem Object are used together. Therefore, System State will only be
used when the discussion is aimed at areas not specific to the Tivoli
Storage Manager client.
Note
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
20/190
6 Deploying Tivoli Storage Manager for Windows 2000
Figure 2. System Object in Tivoli Storage Manager Client
The TSM concept of System Object is meant to be a generic description of
any set of related files on any operating system. For example, System Object
might some day have a similar definition on a UNIX system.
1.3.1.1 Dependency issues
The Tivoli Storage Manager client has the ability to process the System
Object components either granularly (that is as isolated components) or as a
single entity. Unfortunately, the granular functionality cannot be fully exploited
in the current version of Windows 2000. This is because of dependencies that
exist at the operating system level between key Windows 2000 components.
Dependencies mainly exist between the distributed services running onWindows 2000 domain controllers making it inadvisable to backup or restore
one item in isolation. Examples of this are:
The Windows 2000 System Volume (SysVol) is a replicated data set
containing policies and scripts used by Active Directory. If the SysVol and
Active Directory are not synchronized, it is likely that one will contain cross
references to data that does not exist in the other.
The Active Directory publishes references to the Distributed File System
(DFS). If the Active Directory is backed up without considering DFS, it is
possible that a restored Active Directory could publish broken DFS links.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
21/190
Chapter 1. Introducing TSM client support for Windows 2000 7
The Windows 2000 registry contains housekeeping information on the
Active Directory such as when to perform database consistency checks or
a re-index operation.
Windows 2000 Professional and member server systems are also affected by
dependency issues. The most vivid example of this is the relationship
between the System Files and the Registry, with the latter making references
to files contained in the System Files component.
To ensure that the integrity of backups are maintained, the following rules
should be adopted for allWindows 2000 systems:
Always back up the entire System Object.
This is of par ticular importance on systems running Active Directory. Do
not create a backup policy which partially backups up the System Object
and expect the data to be restored in a consistent manner. For example,
adopting a policy of backing up the entire System Object each weekend
and just the Active Directory nightly is not recommended.
Do not restore an isolated component from the System Object unless you
are certain that it does not depend on another.
The Windows 2000 Event logs are an example of a System Object
component that can be safely restored in isolation
In order to meet the objectives required for a consistent Windows 2000
backup, the Tivoli Storage Manager Client will only perform a full backup of all
components in the System Object. For example, when backing up the System
Files component, allfiles that make up the System Files are backed up in
every job. An incremental backup is not performed.
An incremental backup is not currently supported by the Microsoft API.
To understand more about the dependencies that exist in Windows 2000,
please refer to Microsofts documentation on backup and restore. Two
suggested documents are:
Windows 2000 Server Distributed Systems Guide(part of the Windows
2000 Server resource kit)
Windows 2000 Server Disaster Recovery Guidelineswhitepaper at:
http://www.microsoft.com/TechNet/win2000/recovery.asp
Note
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
22/190
8 Deploying Tivoli Storage Manager for Windows 2000
1.3.1.2 Remote backup and restore
The backup of System State components must be processed locally by the
Tivoli Storage Manager client. System State components cannot be backed
up remotely using a mapped dr ive.
1.3.1.3 How System Object components are processed
The Tivoli Storage Manager client must use three different methods when
processing the System Object components. This is due to the way the
Windows 2000 backup APIs allow each component to be accessed. Allprocessing is done under-the-covers and does not require any intervention
from the Tivoli Storage Manager administrator.
Smaller system objects such as the registry, event logs and COM+
database are dumped to files in a staging folder called ADSM.SYS. From
here, Tivoli Storage Manager backs up system object data as standard
files. The process for restores is reversed. This behavior can be observed
in the dsmsched.log file on the client. It is impor tant that the staging file,
ADSM.SYS, is not excluded from processing. The statement INCLUDE
:\ADSM.SYS\...\* should be included as the last statement in the dsm.opt
file.
For the larger database components, for example, Active Directory andCertificate Services, Tivoli Storage Manager makes API calls to backup
directly from the database and transaction log files.
Components such as the Sysvol, FRS, system and boot files are
enumerated from the operating system and backed up as regular files.
1.3.2 System boot files
For Windows NT 4.0 and earlier, the system and boot files were backed up as
part of the file system just like data files. In Windows 2000, the system and
boot files are backed up as a single entity. These files consist of:
System partition boot files:
- boot.ini- bootsect.dos
- ntdetect.com
- ntdlr
- ntbootdd.sys
The System File Protection service catalog file
All files protected by System File Protection. These are files that have
been installed from the Windows 2000 installation CD-ROM with
extensions SYS, DLL, EXE, TTF, FON and OCX. For more information on
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
23/190
Chapter 1. Introducing TSM client support for Windows 2000 9
Windows 2000 System File Protection, see the Tivoli Storage Manager
v3.73 and v4.1 Technical Guide, SG24-6110.
Performance Counter Configuration files
- \system32\perf?00?.dat
- \system32\perf?00?.bak
1.3.3 Registry
The Windows 2000 Registry no longer allows individual Registry hives to be
selected for backed up. Instead, a full backup of the Registry will always be
performed. The Tivoli Storage Manager client uses information in the Registry
to identify the nonvolatile Registry hives which are candidates for backup.
Note that individual Registry hives can be activated using the REGREST
utility which is provided in the Windows 2000 Resource Kit.
1.3.4 Event logs
Like the Registry, the Windows 2000 event logs can no longer be selected for
individual backup. A full backup of all event logs is performed by Tivoli
Storage Manager using information from the Registry to identify the logs that
are to be backed up.
All Windows 2000 systems have the same three event logs as Windows NT:
Application log
Security log
System log
For Windows 2000 domain controllers, at least two additional logs are
created:
Directory service log
File replication service log
These are used by the Active Directory and File Replication Services,respectively. Additional services, for example DNS Server, also have
dedicated event logs. Windows 2000 stores active event logs in the folder
%systemroot%\system32\config.
Table 3 shows the file names of the core Windows 2000 event logs.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
24/190
10 Deploying Tivoli Storage Manager for Windows 2000
Table 3. Windows 2000 event log file names
1.3.5 COM+ Class DB
The Component Object Model (COM) is a binary standard for writing
component software. It is designed to promote software interoperability in a
distributed environment allowing two or more applications (or components) to
easily cooperate with one another, even if they were written by different vendors.
COM+ represents the next generation of COM, offering a Registry
independent database for storing component registration.
The Windows 2000 COM+ entity consists of two components:
Component binaries (DLLs and EXEs)
Component Services database
Tivoli Storage Manager is able to backup and restore the COM+ components
using two methods. The component binaries are backed up as a part of
normal file enumeration. The COM+ database is backed up and restored as
part of the System Object data.
1.3.6 Certificate Services DBWindows 2000 ships with a certificate server service that can be configured
to provide X.509 certificates for clients. The certificate database is the
repository for that information.
Tivoli Storage Manager is able to back up and restore the certificate database
as part of the System Object data. Only a full backup or restore of the
certificate server components is supported. The backup is comprised of the
database, logs and associated files. Incremental backups are not supported.
Event log File name
System SysEvent.Evt
Application AppEvent.Evt
Security SecEvent.Evt
Directory Services NTDS.Evt
IExplorer IExplore.evt
DNS server DNSEvent.evt
File Replication NtFrs.Evt
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
25/190
Chapter 1. Introducing TSM client support for Windows 2000 11
1.3.7 Active Directory
Active Directory is the directory service for Windows 2000 Server. It stores
information about objects on the network and makes this information easy for
administrators and users to find and use. The Active Directory directory
service uses a structured data store as the basis for a logical, hierarchical
organization of directory information.
Active Directory provides a single point of administration for all published
resources, including files, peripheral devices, host connections, databases,Web access, users, and other arbitrary objects and services. It provides a
single point for logging on to the network.
The Active Directory takes the form of a database that can only reside on
Windows 2000 domain controllers. The database file is called NTDS.DIT
(default location is %SystemRoot%\NTDS) and is based on the Jet format
(similar in many ways to the directory databases used in Microsoft
Exchange).
Tivoli Storage Manager performs a full backup of the Active Directory
database and its associated transaction log files. After the database and logs
are backed up, the logs are deleted.
The Active Directory cannot be restored onto an alternative system. It must
be restored to its original location.
1.3.8 System Volume (SYSVOL)
The Windows 2000 System Volume (SYSVOL) is a folder structure that exists
on all Windows 2000 domain controllers. It stores files (for example, logon
scripts) and some of the Group Policy objects for both the current domain as
well as the enterprise. Because of its close relationship with the Active
Directory, it is important that both components are kept synchronized
whenever a backup or restore occurs.
Tivoli Storage Manager backs up the SYSVOL by enumerating the contents
of the replicated directories and then processes them for backup and restore
as standard file data.
1.3.9 File Replication Service
Windows 2000 introduces full, two-way file replication for NTFS, replacing the
WIndows NT File Replication Service. File replication provides a mechanism
for duplicating any file system object and/or directory attribute to another
server.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
26/190
12 Deploying Tivoli Storage Manager for Windows 2000
The replication service stores data in both the directory services database
and a local Jet database.
The backup and restore of replicated data is controlled by the Windows 2000
File Replication Service (FRS). FRS is employed by Active Directory and
Distributed File System (DFS) to replicate critical files for performance and
availability.
Tivoli Storage Manager provides backup and restore of data under the controlof FRS. Tivoli Storage Manager obtains a list of directories from the FRS that
are replicated, and then backs up all files and directories under this list of
directories. FRS files are grouped as a System Object component and there
is no file level granularity available for backup or restore; only the FRS System
Object component can be restored.
1.3.10 Cluster DB
The cluster database component will only be present in the System Object if
the server is running as a cluster node. The cluster database contains
information about all physical and logical elements in a cluster. Tivoli Storage
Manager backs up this information using standard interfaces designed to
ensure restore consistency.
1.4 File System (NTFS) components
NTFS is a file system specially designed for Windows NT and Windows 2000.
NTFS manages databases, transaction processing, and objects to provide
data security, reliability and other features. It supports various features for the
POSIX subsystem and object-oriented applications by treating all files as
objects with user-defined and system-defined attributes.
Windows 2000 comes with an enhanced version of NTFS. This newest
version of NTFS provides greater performance, reliability, and functionality.
Also, some new features such as Active Directory directory service and thestorage features based on Reparse Points are only available on volumes
formatted with this new NTFS.
The new NTFS includes security features required for file servers and
personal computers in a corporate environment, data access control and
ownership privileges important for data integrity. This new version of NTFS,
commonly called NTFS 5, is supported by Tivoli Storage Manager Client.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
27/190
Chapter 1. Introducing TSM client support for Windows 2000 13
1.4.1 Encrypted File System (EFS)
File and directory-level encryption is included in the version of NTFS for
Windows 2000 to provide enhanced security in NTFS volumes. Encrypted
File System (EFS) provides security even when the storage media is
removed from a system running Windows 2000.
EFS uses Symmetric Key encryption and Public Key technology to provide
confidentiality for files and directories. It runs as an integrated system
service, which makes EFS difficult to attack, and is transparent to the userand to applications.
Tivoli Storage Manager Client supports EFS. In backups and restores, the
data remains in its own encrypted and secure format. T ivoli Storage Manager
does not decrypt data so it can only be restored in NTFS 5 partitions.
1.4.2 Reparse Points
Reparse Points are new file system objects in the version of NTFS included
with Windows 2000, They carry a specialized attribute containing
user-defined data and are used to extend functionality in the input/output
(I/O) subsystem.
One Reparse Point is allowed per file or directory. Remote Storage and NTFS
Directory Junction Points are based on Reparse Points. With Volume Mount
Points and Directory Junction Points the drive letter limit is exceeded.
Storage management applications need to be able to deal with this as user
defined properties for these files would otherwise be missed.
Tivoli Storage Manager Client supports Reparse Points. Depending on the
type of Reparse point found, the metadata representing the point, or the data
pointed to by the point, is backed up.
1.4.3 Multiple Named Data Streams
The new NTFS supports Multiple Named Data Streams (sequences of bits,bytes, or other small structurally uniform units), where the Stream name
identifies a new data attribute on the file. A Data Stream is a unique set of file
attributes. Streams have separate opportunistic locks, file locks, and sizes,
but common permissions.This feature enable you to manage data as a single
unit.
It is expected that applications will properly manage Data Streams attached
to files and directories. This means that basic functions applied to these
objects (such as copy, move or delete) are extended to the attached
subfiles or Named Data Streams.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
28/190
14 Deploying Tivoli Storage Manager for Windows 2000
Tivoli Storage Manager Client supports Multiple Named Data Streams backed
up or restored on NTFS 5 par titions. Files are restored normally within Named
Data Streams but Data Streams attached to directories always overwrite the
existing streams independently of the Client configuration. When these
objects are restored to other type of partitions (NTFS4, FAT, FAT32) the
Named Data Streams are not restored. Sparse Named Data Streams are not
supported.
1.4.4 The Change Journal
The Change Journal is a new feature in Windows 2000 that logs changes to
NTFS volumes, including additions, deletions, and modifications. The
Change Journal is on the volume as a sparse file.
The Change Journal may be a redundant feature for applications that support
incremental backup. In fact, for those applications, backing up the journal
could be space wasted. Tivoli Storage Manager Client does not support the
Change Journal.
1.4.5 Sparse file support
A sparse file is managed in a way that requires less disk space than wouldotherwise be need by allocating only meaningful or non-zero data. Sparse
support allows applications to create very large files without wasting disk
space for every byte.
Sparse files stored in Windows 2000 systems have a special attribute that
must be considered by storage management applications.
Depending on the option selected, the Tivoli Storage Manager Client sees the
sparse file as a normal file with the sparse information included, or as a truly
sparse file with the additional attribute. The file can be backed up or restored
correctly in NTFS 5 or non NTFS par titions.
You can use TSM file compression to compress out the sparseness of files.We cover this in section 6.3.4, Sparse files on page 146.
1.4.6 Distributed Link Tracking
Windows 2000 provides a Distributed Link-Tracking service that enables
applications to track link source objects that have been moved locally or
within a domain. Applications subscribed to this Link-Tracking service can
maintain the integrity of their references because the referenced objects can
be moved transparently. Link tracking stores a file's object identifier as part of
its tracking information.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
29/190
Chapter 1. Introducing TSM client support for Windows 2000 15
Link Tracking and Object IDs are stored as part of the Registry information.
This must be considered when applications are restored to ensure reliability.
Tivoli Storage Manager Client supports this feature as an addition to Registry
backup and System files.
1.4.7 Directory Junctions
An NTFS Directory Junction is an NTFS directory with a special type of
Reparse point associated with it. An NTFS Directory Junction can be mapped
to any local or remote target directory.
Tivoli Storage Manager Client treats each Directory Junction as a separate
file space and supports this feature in NTFS 5 formatted volumes.
1.4.8 Volume Mount Points
This new Windows 2000 feature represents storage volumes in a persistent
and robust manner allowing many disk volumes to be linked together in a tree
structure such as a DFS. You can only use a single drive letter pointing to the
root volume. This overcomes the 26 drive letter limit existing in previous
Windows versions. Frequently a volume point is placed in an empty directory,
in this case the directory name is used instead of the dr ive letter. Volume
points need NTFS 5 partitions because they are based on Reparse Points.
The Tivoli Storage Manager Client handles volume points in a similar way to
Directory Junctions by treating each volume point as a separate file space.
1.5 Storage components
Many changes have been made to the storage feature set in Windows 2000
in order to support growing storage requirements in large environments,
greater scalability requirements and support for emerging technology in the
storage market. To satisfy these needs, Windows 2000 includes an improved
NTFS file system and a list of new storage features and applications.
1.5.1 Disk Quotas
Windows 2000 supports disk quotas for volumes formatted as NTFS. You can
use disk quotas to monitor and limit disk-space use on a per-user or
per-volume basis. Disk quotas are stored in user profiles.
There are two scenarios that apply when a disk quota is exceeded:
1. The restore is being made by a user.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
30/190
16 Deploying Tivoli Storage Manager for Windows 2000
2. The restore is being made by an administrator but the data belongs to a
normal user.
In the first case the user can only restore as many files as its quota allows.
When the limit is reached a full disk message appears. In the second case
the ownership of files restored by an administrator reverts to the administrator
if the file owners quota is exceeded.
1.5.2 Distributed File System (DFS)The Microsoft Distributed File System is an integrated service in the Active
Directory that provides mapping, naming and hierarchical organization to
shared physical storage distributed along the Network. The DFS makes it
easier to administer shares and provides ways to balance access to
resources using file and share replication.
The Distributed File System is a server core component and it is expected
that storage applications include options to save either the metadata that
defines the tree structure and data which this structure points to.
Tivoli Storage Manager Client is able to backup and restore depending your
selections, the metadata that define the DFS volume (junction points) or thedata it points to (root directory and data in remote shares).
1.5.3 Single Instance Store
Windows 2000 systems can use this new service as an alternative to avoid
some applications such as Remote Install Service having to install many
different files with the same content. This service implements links with the
semantics of copies for files installed in Windows 2000 NTFS partitions. The
SIS service detects duplicated files and reports them for conversion into links.
There is no explicit support of this in TSM.
1.5.4 Removable Storage Manager
This is another new core feature in Windows 2000 Server to manage
removable storage media devices such as tapes, optical disks and libraries
(excepting floppies and other small storage devices).
Removable Storage Manager provides a set of Application Programming
Interfaces (APIs) that allow applications to catalog removable media
organized in storage pools which can control their access and share them
between applications.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
31/190
Chapter 1. Introducing TSM client support for Windows 2000 17
The Removable Storage Management service uses a database which stores
the devices configurations in an NTFS format.
The Tivoli Storage Manager Client uses API calls to backup and restore the
files comprising this database.
1.5.5 Remote Storage Service
Windows 2000 also includes a hierarchical storage management application
(not installed by default) that is able to migrate files from primary storage to
secondary storage depending on migration policies. This can optimize disk
space and cost of storage.
Remote Storage Service (RSS) uses a Jet database stored in the system
volume and the Microsoft Tape Format (MTF) to store information in the
secondary storage.
There are two common strategies to backup the RSS information:
1. The application can make a full backup of the database and the Reparse
Points included in it without backup of the Pr imary Data Streams, so the
Primary Data Streams depend on recovery from the RSS media.
2. The application can make a full backup of the database and the Reparse
Points included in it and all migrated Primary Data Streams.
Tivoli Storage Manager Client uses the first approach, so it is capable of
backup and restore of the RSS Database. It does not backup data managed
by Microsoft Remote Storage.
1.5.6 Indexing service
The Indexing service included in Windows 2000 (not NTFS 5 exclusive)
improves the user search capabilities analyzing many files in a few seconds.
It uses sparse files to store index data, the change log to update the index
and keeps track of information location still managed by the hierarchicalstorage application that comes with Windows 2000. The index service can
adversely impact the performance of the restore of a large number of small
files. Improved performance can be achieved by disabling the indexing
service during a large restore.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
32/190
18 Deploying Tivoli Storage Manager for Windows 2000
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
33/190
Copyright IBM Corp. 2001 19
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client
This chapter introduces the Tivoli Storage Manager 4.1.2 client. Some
background information is presented about what Microsoft has done in the
area of backups, and how Tivoli Storage Manager has adapted to these
initiatives. New features and functions introduced by this level of Tivoli
Storage Manager client is covered. It compares the Tivoli Storage Manager
tool to the Microsoft-supplied tool, NTbackup.
2.1 Background
Tivoli Storage Managers direction for backing up Windows 2000 is partly
determined by features and functions introduced in Windows 2000 by
Microsoft. As new features such as Active Directory are introduced, Tivoli
Storage Manager must develop a process to back up and restore these
features. Also, in many cases, Tivoli Storage Manager uses interfaces
published by Microsoft to access these features. This frees Tivoli Storage
Manager from having to create their own interfaces and, at the same time,
limits Tivoli Storage Manager to following requirements set by Microsoft.
In some cases, these Microsoft features or interfaces may not yet be
completely developed, completely implemented, or completely standardized
by Microsoft. In this case, Tivoli has the unenviable task of developing Tivoli
Storage Manager code and processes to handle what is stable and
developing a work-around for what is not. Sometimes the result is less than
elegant.
An example of this lack of clear direction is the different facilities Microsoft
provides to back up the various objects that make up the System Object.
Some components, primarily databases, can be backed up directly using
Microsoft APIs, but even here, the interfaces are not standard. For other
components, such as the Registry, Tivoli Storage Manager must internally
call Microsoft tools to export the Registry to a staging directory and back it upfrom there.
2.2 New features
The Tivoli Storage Manager 4.1.2. client was created (in part ) to support
functions introduced with Windows 2000. The features dealing with System
Objects require connection to a Tivoli Storage Manager 3.7.3 server or newer.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
34/190
20 Deploying Tivoli Storage Manager for Windows 2000
2.2.1 System Objects
Tivoli Storage Manager now displays all the System Objects in the graphical
user interface (GUI). An individual object can be selected for backup or
restore. See Figure 3 for an example of the System Objects in the GUI.
System Objects include:
Registry
COM+ database
Event logs
System and boot files
System volume (SYSVOL)
Removable Storage Management database
Active Directory
Certificate server database
Cluster database
Replicated file systems
Figure 3. Example of System Objects in the GUI
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
35/190
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client 21
2.2.2 SYSTEMOBJECT domain
The SYSTEMOBJECTkeyword is now a valid domain statement that specifies
the complete System Object. It is automatically included in the ALL-LOCAL
domain.
2.2.3 System Objects managed as a group
The System Object support uses the logical file grouping support in Tivoli
Storage Manager 3.7.3 servers and newer. This support allows all of theobjects in the System Object to be managed as a group.
2.2.4 New commands
2.2.4.1 BACKUP SYSTEMOBJECTS
This backup archive command line interface command backs up all valid
System Objects in Windows 2000 and the event logs and the Registry in
Windows NT.
2.2.4.2 QUERY of System Objects
A number of new commands are introduced in 4.1.2 to provide information
about the System Objects. The QUERY SYSTEMOBJECT command summarizes the
information for each backed up System Object. Individual query commands
display the same information but only for the individual object. Figure 4
displays an example of the information that is presented.
Figure 4. Example of a Query Systemobject command
tsm> query systemobjectSize Backup Date Mgmt Class A/I File---- ----------- ---------- --- ----
17,661 12/07/2000 10:55:37 DEFAULT A SYSTEM OBJECT\GOLD\COMPDB135,258 12/07/2000 10:55:56 DEFAULT A SYSTEM OBJECT\GOLD\EVENTLOG
231,108,288 12/07/2000 10:55:29 DEFAULT A SYSTEM OBJECT\GOLD\SYSFILES18,093 12/07/2000 10:55:50 DEFAULT A SYSTEM OBJECT\GOLD\SYSVOL
48,267,344 12/07/2000 10:55:54 DEFAULT A SYSTEM OBJECT\GOLD\NTDS10,006,668 12/07/2000 10:55:38 DEFAULT A SYSTEM OBJECT\GOLD\REGISTRY
117,074 12/07/2000 10:55:38 DEFAULT A SYSTEM OBJECT\GOLD\RSMtsm>
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
36/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
37/190
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client 23
Figure 5. Example of query inclexcl command
2.2.4.5 Undocumented Show SYSTEMOBJECT command
An undocumented command is available in the 4.1.2 version of the Backup
Archive Client command line interface. It appears to display whether a
System Object has ever been backed up in the life of this client node.
Note that the return codes listed can be used by TSM technical support to
help diagnose System Object backup and recovery problems.
The syntax of the command is Show Systemobject. An example of the
command and its output is shown in Figure 6.
Tivoli Storage ManagerCommand Line Backup Client Interface - Version 4, Release 1, Level 2.0(C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved.
tsm> query inclexclNode Name: AAXABKSession established with server BRAZIL: AIX-RS/6000
Server Version 4, Release 1, Level 1.0Server date/time: 12/05/2000 11:34:24 Last access: 12/05/2000 09:56:17
*** FILE INCLUDE/EXCLUDE ***Mode Function Pattern (match from top down) Source File---- --------- ------------------------------ -----------------Excl Directory #\RECYCLER dsm.optExcl Directory #\RECYCLED dsm.optExcl Directory #\...\TEMPORARY INTERNET FILES dsm.optExcl Directory #\SYSTEM VOLUME INFORMATION dsm.optExcl Directory #\...\NTDS dsm.optExcl Directory #\...\NTFRS\JET dsm.optIncl All #\ADSM.SYS\...\* dsm.optExcl All #\...\SYSTEM32\CONFIG\...\* dsm.optExcl All #\...\PAGEFILE.SYS dsm.optExcl All #\...\EA DATA. SF dsm.optExcl All #\WINNT\DEBUG\*.* dsm.optExcl All #\DOCUME~1\ADMINI~1.PAC\LOCALS~1\TEMP\...\* dsm.optExcl All #\WINNT\SCHEDLGU.TXT dsm.opt
Excl All #\HIBERFIL.SYS dsm.optExcl All #\WINNT\NETLOGON.CHG dsm.optExcl All #\WINNT\SYSTEM32\DTCLOG\MSDTC.LOG dsm.optExcl All #\DOCUMENTS\...\INDEX.DAT dsm.optExcl All #\WINNT\REGISTRATION\*.CLB\...\*.CRMLOG dsm.optExcl All #\WINNT\CSC\...\* dsm.optNo encryption include/exclude statements defined.tsm>
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
38/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
39/190
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client 25
2.2.9 Event log backup now processes all logs
Tivoli Storage Manager 4.1.2 now uses the values of the Registry key
HKLM\SYSTEM\CurrentControlSet\Services\Eventlog to determine which logs
need to be included in a backup of the logs.
2.2.10 Restore to same location only
Tivoli Storage Manager 4.1.2 cannot restore System Objects to locations
other than their original locations.
2.2.11 Management class
Tivoli Storage Manager assigns the default management class to System
Objects during backup. There is no way to change this management class.
2.3 What has changed
This section provides details about what has changed in the new Tivoli
Storage Manager 4.1.2 client.
2.3.1 System Objects require new backupBecause of the way System Objects are now being stored, a backup must be
performed from a Tivoli Storage Manager 4.1.2 client prior to attempting to
restore System Objects using the Tivoli Storage Manager 4.1.2 client.
2.3.2 Changed commands
A number of command options have changed in the Backup Archive client
command line interface to support the System Objects when running on a
Windows 2000 platform. In general, they remove the options to back up or
restore individual components inside a System Object such as the Security
Event log. The changed commands are:
BACKUP EVENTLOG BACKUP REGISTRY
RESTORE EVENTLOG
RESTORE REGISTRY
2.3.3 Local backup only
Tivoli Storage Manager can only back up and restore the System State or a
System Object on a local computer, not a remote computer. You can use the
Web client to restore system objects.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
40/190
26 Deploying Tivoli Storage Manager for Windows 2000
2.3.4 One step backup and restore of System State
The System Object is held in the SYSTEMOBJECT domain. This domain is
part of the ALL-LOCAL domain. Thus, the default for an incremental backup
includes the System State.
2.3.5 BACKUPREGISTRY option redundant
The Tivoli Storage Manager client option BACKUPREGISTRY is now redundant as
the Windows 2000 Registry is included in the System Objects. The SystemObjects make up the domain SYSTEMOBJECT which is included
automatically in the ALL_LOCAL domain. If the SYSTEMOBJECT domain is
not specified in the dsm.opt file for a Windows 2000 system, Tivoli Storage
Manager will honor the setting specified in the BACKUPREGISTRY option.
2.3.6 Restore without services active
Tivoli Storage Manager now restores the System State without the necessary
subcomponents having to be available. For example, Active Directory can be
restored to a vanilla system that does not already have Active Directory
available.
2.4 What has been fixed
The Client Acceptor service can now be set to start automatically.
2.4.1 APAR list
The PTFs for the following APARs have been incorporated into PTF IP22151 -
Version 4, Release 1, Level 2.0.
IC26935 - Tivoli Storage Manager cannot restore the Windows 2000
System State in Directory Services Restore Mode.
IC27670 - Win32 GUI backup of SYSTEMOBJECT and local filespace fails
with AN ERROR OCCURRED SAVING THE REGISTRY KEY. IC25968 - Incorrect trace file appends with tracemax option used.
IC26227 - Tivoli Storage Manager/NT client scheduler service brings up
Dr.Watson (core dump) if client node is not registered on the Tivoli
Storage Manager server.
IC26645 - CLC admin client command, HELP LABEL LIBV, does not work
correctly in a Japanese language environment.
IC26855 - Registry backup on Windows 95 or 98 fails with message
ANS4036E.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
41/190
Chapter 2. Introducing Tivoli Storage Manager 4.1.2 client 27
IC26949 - Message ANS1155E issued even if client is correctly configured
for cluster support.
IC26973 - When a file is skipped because it is changed, the Event Log
entry only says Changed. It needs to be more descriptive.
IC27088 - Client fails to observe exclude option if the option is specified in
both dsm.opt and client options set.
IC27199 - Tivoli Storage Manager admin command line NLS client is not
processing DO YOU WISH TO PROCEED Y/N response as expected.
IC27203 - Setup wizard for BA client not updating domain, ALL-LOCAL
and selected filespaces should be exclusive options.
IC27260 - When backing up file system that contains corrupted directories
the client terminates processing without appropriate message.
IC27264 - Windows client wizard 3.7.2.01 configures an invalid path for
the client scheduler service.
IC27315 - Tivoli Storage Manager client classic restore stops after 21
failures when data is unavailable on the server (ANS1314E).
IC27371 - Root object / not rebound after deletion of management class.
IC27382 - The httpport Registry setting is ignored by the Web client.
IC27409 - Schedule reports Scheduled event completed successfully in
spite of errors during backup.
IC27528 - If a directory is removed after the archival of the higher level
directory, the archive operation terminates with ANS4006E.
IC27728 - DSMC RESTORE SYSFILES does not restore all system files if
the backup was done with COMPRESSION=YES &
COMPRESSALWAYS=NO.
IC27750 - Unnecessary and misleading error messages are being written
to the dsmerror.log file.
IC27695 - API clients core dump if DIRMC is in dsm.sys file.
IC27852 - Windows does not parse the DOMAIN statement correctly,
when combining ALL-LOCAL with a dr ive.
IC27992 - Trace flag AUDIT crashes Tivoli Storage Manager Web GUI
and OS when prompted for offline media mount and choosing WAIT FOR
VOLUME TO BE MOUNTED
IC28337 - Too long command line arguments make Tivoli Storage
Manager client crash.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
42/190
28 Deploying Tivoli Storage Manager for Windows 2000
IC28340 - CLC 'Successful deletion' message not received when deleting
an archived file.
IC28454 - ENCRYPTKEY option in GUI displays SAVE ENCRYPTION
KEY PASSWORD LOCALLY even if Encryptkey prompt is specified in
DSM.OPT
IC28468 - Using ODBC in MS ACCESS to link a Tivoli Storage Manager
table containing > 100 entries fails with error 3146.
IC28492 - Client fails to send events to server.
IC28544 - Automatically adjust clock for daylight savings changes
causes incremental to do full backup.
IC28545 - ANS5016E Not enough memory for restore operation.
IC28565 - Wrong statistics at end of DSMC ARCHIVE.
IC28568 - APAR IC25107 Win32 RC = 193 Error not resolved if file
c:\program exists and DSMCUTIL install uses C:\Program Files.
2.5 Advantages of TSM versus Microsoft NTbackup
In this section, we contrast some of the functions of Tivoli Storage Managerwith NTbackup.
2.5.1 Using NTbackup
NTbackup is the tool supplied by Microsoft to perform backups of Windows
2000 systems. While it does back up and restore data and System Objects
(among other functions), it does have some limitations.
2.5.1.1 Local backup
NTBackup is limited to writing to locally attached devices. This reduces
backup and restore flexibility by requiring hardware to be directly attached to
the machine being backed up.
2.5.1.2 Policy management
NTbackup has no policy management for maintaining and expiring data.
These functions have to be managed manually outside of NTbackup by the
administrator.
2.5.2 Using Tivoli Storage Manager
Tivoli Storage Manager performs backups of Windows 2000 including the
System State and all the System Objects.
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
43/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
44/190
30 Deploying Tivoli Storage Manager for Windows 2000
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
45/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
46/190
32 Deploying Tivoli Storage Manager for Windows 2000
3.2 Server registration modes
Tivoli Storage Manager Server has a Registration setting for Client nodes and
it is necessary to perform different tasks depending on this setting value:
If the Registration option is Closed, the following tasks should be
accomplished prior to the Client installation:
- An administrator (System or Policy domain privilege) should define the
following on the Server: Node name
Initial password (optional)
Policy domain
Compress setting
Delete setting for backups and archives
If the Registration option is Open(default) the following tasks should be
accomplished during the Client Installation:
- The Client should give only the Contact Information, but if the
Authentication setting i s On(default is Off) a user-defined password
will also be required. Automatically, the following is defined during
installation:
Node name (same as machine name)
Password (Only if the Authentication setting on the Server is On)
Policy domain as STANDARD with STANDARD Policy set and
management class
Compress setting off(the user can change this option by modifying
the dsm.opt file)
Delete setting Onfor archive and Off for backup versions of files
Administrative user with Client Owner Privilege is defined
3.3 Server storage
Independently of the backup strategy (which should already be defined in
Tivoli Storage Manager Server) some guidelines must be considered to
modify the strategy (if it applies) and resize your Database, Recovery Log and
Storage pools:
The age of an Active Directory backup should not exceed the Active
Directory Tombstone Lifetime (this is the time period that deleted objects
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
47/190
Chapter 3. Implementation planning 33
remain in the Active Directory before the system permanently removes
them; the default is 60 days). If you try to restore Active Directory data
older than the Tombstone date, the restore APIs wil l reject data as out of
date. Backups must be done frequently.
To estimate the Database, Recovery Log and storage pools size needed to
store information about Windows 2000 systems, the following information
in Table 6 could be useful:
Table 6. Typical disk space occupancy, Windows 2000 Systems (system data)
In the following sections we provide some guidelines to size disk storage
volumes to allow you set up or modify your Tivoli Storage Manager Server
environment to support the Windows 2000 clients. If additional planinginformation is needed, it is recommended that you review Getting Started with
Tivoli Storage Manager: Implementation Guide, SG24-5416.
3.3.1 Database size calculation
First, it is recommended that you complete the fields in the worksheet as
shown in Table 7 with at least the information shown here (additional
information could be added).
Table 7. Sample client requirements worksheet
Windows 2000Professional
Windows 2000 Server Windows 2000 AdvancedServer
650 MB 1 GB 1 GB
Client 1 Client 2 Client 3
Client name John Mack Alice Reynolds Sarah Smith
Contactinformation
Servers Group Desktops Group Mobiles Group
Operating systems Windows 2000Professional
Windows 2000Server
Windows 2000Adv. Server
Number of filesbacked up
1000 2000 Not Available
Number of backedup GB
2 2 3
Additional space can be occupied by user data and applications.
Note
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
48/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
49/190
7/31/2019 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment Sg246141
50/190
36 Deploying Tivoli Storage Manager for Windows 2000
3.3.3 Primary storage pool size calculation
It is recommended that you use a primary storage pool as large as the total
amount of data backed up in an entire cycle. To estimate this pool size,
perform the following steps:
1. Using Table 7 on page 33, multiply the GB changed per backupby
(one minus the data reduction rateobtained fromTable 8) to obtain the
total bytes transferred for each client. Table 9 shows the typical data
compression rates.Table 9. Typical data compression
2. Add the total bytes transferred for all clients to obtain the total bytes
transferred per backup cycle.
3. Add 15 percent to the results obtained in the previous step to providetolerance.
For example, using the previous example we have:
1. 0.02 x (1- 0.66), 0.01 x (1 - 0.5), 0.3 x (1 - 0)
2. 0.0068 + 0.0050 + 0.3 = 0.3118
3. 0.3118 * 1.15 = 0.35857 GB Primary Storage Pool size
3.4 Network bandwidth
The network speed to back up clients should be enough to transport common
data and backup data. Generally, the backup should be done duringnonworking hours. We call this period the backup window. While it is possible
to split client backups to minimize network bandwidth, it makes the backup
administration more difficult. A normal a