Deployment Guide Series Tivoli Continuous Data Protection For Files V3.1 Sg247423

Front cover
Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
Deployment best practices Integration with TSM and Notes
Case studies, troubleshooting , tips
Vasfi Gucer Greg Bass Wolfgang Beuttler Marcia Kubo
ibm.com/redbooks
International Technical Support Organization Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1 August 2007
SG24-7423-00
Note: Before using this information and the product it supports, read the information in Notices on page xix.
First Edition (August 2007) This edition applies to IBM Tivoli Continuous Data Protection for Files Version 3, Release 1.
Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii Part 1. Planning and architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Introduction to Tivoli Continuous Data Protection for Files. . . 3 1.1 General overview of Tivoli Continuous Data Protection for Files . . . . . . . . 5 1.1.1 What is Tivoli Continuous Data Protection for Files? . . . . . . . . . . . . . 5 1.1.2 Why Tivoli Continuous Data Protection for Files is needed . . . . . . . . 6 1.1.3 Who should use Tivoli Continuous Data Protection for Files? . . . . . . 9 1.2 How Tivoli Continuous Data Protection for Files works. . . . . . . . . . . . . . . 11 1.3 Main features of Tivoli Continuous Data Protection for Files . . . . . . . . . . 13 1.4 Value proposition of Tivoli Continuous Data Protection for Files . . . . . . . 14 1.4.1 Benefits of using Tivoli Continuous Data Protection for Files . . . . . . 17 1.4.2 Unique differentiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chapter 2. Product architecture, planning, and deployment . . . . . . . . . . 19 2.1 Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1.1 Main components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1.2 Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1.3 Daemon architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.2 Planning for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.2.1 What are my critical files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.2.2 Where should I back my files up to? . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.2.3 How often do I need to back up different types of files? . . . . . . . . . . 26 2.2.4 Do I need e-mail and scheduled backups? . . . . . . . . . . . . . . . . . . . . 27 2.2.5 Do I need the Vault feature? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.2.6 Summary of protection methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Copyright IBM Corp. 2007. All rights reserved.
iii
2.3 Best practices and sizing considerations . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.3.1 Overall summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.3.2 Corporate scenario- Tivoli Continuous Data Protection for Files with Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.3 Corporate scenario- file server as remote storage target for Tivoli Continuous Data Protection for Files workstations . . . . . . . . . . . . . . 32 2.3.4 Corporate scenario- Tivoli Continuous Data Protection for Files loaded on file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3.5 Home user scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.4 Tivoli Continuous Data Protection for Files installation requirements . . . . 34 2.4.1 Basic installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.4.2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Part 2. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Chapter 3. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 39 3.1 Basic installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.1.1 Installing Tivoli Continuous Data Protection for Files . . . . . . . . . . . . 40 3.1.2 Configuration using the Initial Configuration Wizard . . . . . . . . . . . . . 48 3.2 Advanced installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 3.2.1 Installation using command-line parameters. . . . . . . . . . . . . . . . . . . 65 3.2.2 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.2.3 Push installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 3.2.4 Pull installation (upgrade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.2.5 Providing a configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 3.3 Advanced configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.3.1 Settings Notebook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 3.3.2 Central Administration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 3.4 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 3.4.1 Installation and data directories . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 3.4.2 Interpreting file and folder patterns . . . . . . . . . . . . . . . . . . . . . . . . . 109 3.4.3 Including and excluding files from protection . . . . . . . . . . . . . . . . . 111 3.4.4 Vault duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 3.4.5 Default protection settings (Settings Notebook) . . . . . . . . . . . . . . . 116 Chapter 4. Proof of concept scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 4.1 Product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 4.2 Single user environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 4.2.1 Single computer, local disk only . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 4.2.2 Single computer with external storage . . . . . . . . . . . . . . . . . . . . . . 126 4.2.3 Single computer with ISP connection . . . . . . . . . . . . . . . . . . . . . . . 136 4.3 Multiple computers in a home or small business. . . . . . . . . . . . . . . . . . . 145 4.3.1 Home network with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 4.3.2 Small business with Tivoli Storage Manager Express . . . . . . . . . . 151
iv
4.3.3 Small business with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 4.4 Tivoli Continuous Data Protection for Files in an enterprise environment180 4.4.1 Enterprise environment with Tivoli Storage Manager . . . . . . . . . . . 180 4.4.2 Enterprise with Tivoli Continuous Data Protection for Files loaded on file servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 4.4.3 Enterprise and remote offices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 4.5 Restore scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 4.5.1 Restore from local disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 4.5.2 Restore from remote storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 4.5.3 Restore from Tivoli Storage Manager or Tivoli Storage Manager Express to a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Chapter 5. Troubleshooting, hints, and tips . . . . . . . . . . . . . . . . . . . . . . . 255 5.1 Installation issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5.1.1 Disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5.1.2 Non-privileged users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 5.1.3 Port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 5.1.4 Push installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 5.1.5 Pull installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 5.2 Replication issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 5.2.1 Removable disk issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 5.2.2 File server issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 5.2.3 WebDAV issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 5.2.4 Tivoli Storage Manager issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 5.2.5 Transient conditions (remote storage location not reachable) . . . . 343 5.3 System operation and log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 5.3.1 Tivoli Continuous Data Protection for Files system operation files . 347 5.3.2 Tivoli Continuous Data Protection for Files logs . . . . . . . . . . . . . . . 348 5.3.3 Tivoli Storage Manager specific log files . . . . . . . . . . . . . . . . . . . . . 350 5.4 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 5.4.1 Before you start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 5.4.2 How to run a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 5.4.3 Tracing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Contents
Part 3. Planning for a client engagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Appendix A. Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Required skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Available resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Solution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Solution deployment tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Strategies for successful implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Appendix B. Sample Statement of Work for Tivoli Continuous Data Protection for Files deployment . . . . . . . . . . . . . . . . . . . . . 375 Building a protected environment for user workstations. . . . . . . . . . . . . . . . . 376 Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
vi
Figures
1-1 Why Tivoli Continuous Data Protection for Files is needed . . . . . . . . . . . . 8 1-2 Unique hybrid approach of Tivoli Continuous Data Protection for Files . . 11 1-3 General overview of Tivoli Continuous Data Protection for Files . . . . . . . 12 2-1 Agent-driver interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2-2 Replication threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3-1 Installation Setup Language window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3-2 InstallShield Wizard is being prepared . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3-3 Information window including the build number . . . . . . . . . . . . . . . . . . . . 42 3-4 Software License Agreement options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 3-5 Destination Folder window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3-6 Ready to Install window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3-7 Installation progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3-8 Installation completed window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3-9 Welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3-10 What is Critical page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3-11 Folder and Files Settings dialog box (critical files) . . . . . . . . . . . . . . . . . 51 3-12 Select folders dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3-13 Applications and Extensions box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3-14 E-mail Protection page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3-15 Remote Storage page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3-16 Initial Backup page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3-17 Summary page with initial backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 3-18 Status page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 3-19 Message that a new version is being installed . . . . . . . . . . . . . . . . . . . . 73 3-20 Message to reboot system after pull installation . . . . . . . . . . . . . . . . . . . 73 3-21 General page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 3-22 Files to Protect page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 3-23 Folders and Files box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 3-24 Folder and Files Settings dialog box (include/exclude). . . . . . . . . . . . . . 81 3-25 Select folders box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 3-26 Applications box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 3-27 Application Settings box (applications viewed by ranking) . . . . . . . . . . . 84 3-28 Vault box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 3-29 Vault Settings box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 3-30 Back up with new settings check box . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 3-31 E-mail Protection page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 3-32 E-mail Application: list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 3-33 E-mail Application Data Folder: text field . . . . . . . . . . . . . . . . . . . . . . . . 90
vii
3-34 Folder and Files Settings box (schedules) . . . . . . . . . . . . . . . . . . . . . . . 91 3-35 Scheduled backup reports table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 3-36 Remote Storage page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 3-37 Advanced page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 3-38 Central Administration Settings window . . . . . . . . . . . . . . . . . . . . . . . . 104 3-39 Successfully published fpcommands.xml pop-up window . . . . . . . . . . 105 3-40 Scheduled backup reports table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 3-41 Folder and Files Settings box (example include/exclude settings) . . . . 113 4-1 Single computer, local disk only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 4-2 General Configuration for a single user with local disk configuration . . . 124 4-3 Files to protect in a single user with local disk configuration. . . . . . . . . . 125 4-4 Continuous protection file directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 4-5 Single computer, with external storage . . . . . . . . . . . . . . . . . . . . . . . . . . 127 4-6 General configuration for a single user scenario with external disk . . . . 128 4-7 Selection of important files to continuously protect in a single user scenario with external disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 4-8 Configuring the remote storage for scheduled protection . . . . . . . . . . . . 130 4-9 Configuring files for scheduled protection . . . . . . . . . . . . . . . . . . . . . . . . 131 4-10 Configure the frequency and time to start the scheduled protection . . . 132 4-11 Start an initial backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 4-12 Original directory and files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 4-13 Replicated directory and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 4-14 Single computer, with ISP connection. . . . . . . . . . . . . . . . . . . . . . . . . . 136 4-15 Continuous protection for a single computer with ISP connection . . . . 138 4-16 Important files continuous protection in a single user with an ISP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 4-17 Remote storage with ISP configuration. . . . . . . . . . . . . . . . . . . . . . . . . 140 4-18 Username and password to access Web server. . . . . . . . . . . . . . . . . . 141 4-19 Configure the frequency and time to start the scheduled protection to an ISP provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 4-20 Files for scheduled protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 4-21 Activity report for changed files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 4-22 Activity report for changed file pres1.ppt. . . . . . . . . . . . . . . . . . . . . . . . 144 4-23 Sub-file functionality example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 4-24 Home network with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 4-25 General configuration without continuous protection . . . . . . . . . . . . . . 147 4-26 Map network drive in each computer . . . . . . . . . . . . . . . . . . . . . . . . . . 148 4-27 Configure user and password to access the file server . . . . . . . . . . . . 148 4-28 Configure remote storage for scheduled protection . . . . . . . . . . . . . . . 149 4-29 Configure schedule and select application for scheduled protection . . 150 4-30 Select files for scheduled protection . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 4-31 Small business without file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 4-32 Computers and applications option on Tivoli Storage Manager Express153
viii
4-33 Wizard to add computers and optionally deploy the backup client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 4-34 Select option to add a computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 4-35 Installation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 4-36 Confirm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 4-37 Stop Tivoli Storage Manager Express service . . . . . . . . . . . . . . . . . . . 157 4-38 Start Tivoli Storage Manager Express in foreground mode . . . . . . . . . 158 4-39 Configure node with delete permission . . . . . . . . . . . . . . . . . . . . . . . . . 158 4-40 Shutdown Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . 159 4-41 Start Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . . . . . 159 4-42 Reset the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 4-43 Windows credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 4-44 New password information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 4-45 General configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 4-46 Files to protect in continuous protection . . . . . . . . . . . . . . . . . . . . . . . . 162 4-47 Remote storage configuration for Tivoli Storage Manager Express . . . 163 4-48 Node password on Tivoli Storage Manager Express server . . . . . . . . . 164 4-49 Select applications, files, and frequency to back up to Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 4-50 Create the include list for scheduled protection . . . . . . . . . . . . . . . . . . 166 4-51 Filespace on Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . 167 4-52 Small business with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 4-53 Map network drive and reconnect at logon . . . . . . . . . . . . . . . . . . . . . . 169 4-54 Configure user name and password to access the file server . . . . . . . 169 4-55 General configuration for this scenario . . . . . . . . . . . . . . . . . . . . . . . . . 170 4-56 Files to protect in continuous backup . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4-57 Configure remote storage for continuous and scheduled protection. . . 172 4-58 Configure directories, files, and frequency for schedule protection . . . 173 4-59 Select files and directories for scheduled protection . . . . . . . . . . . . . . . 174 4-60 Inform password for encrypted files . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4-61 Replicated files with encryption option on file server . . . . . . . . . . . . . . 175 4-62 Computers and applications on Tivoli Storage Manager Express . . . . 176 4-63 Excluded files on Tivoli Storage Manager Express client . . . . . . . . . . . 177 4-64 Remove directory from dsm.opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 4-65 Files to backup on Tivoli Storage Manager Express. . . . . . . . . . . . . . . 179 4-66 Example of enterprise environment with Tivoli Storage Manager centric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 4-67 Lab environment (Tivoli Storage Manager centric) . . . . . . . . . . . . . . . . 183 4-68 Add nodes to Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . 185 4-69 General configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 4-70 Files to protect in continuous protection . . . . . . . . . . . . . . . . . . . . . . . . 187 4-71 Remote storage configuration to Tivoli Storage Manager . . . . . . . . . . . 188 4-72 Node password on Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . 189
Figures
ix
4-73 Select applications, files, and frequency to back up to Tivoli Storage Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 4-74 Create the include list for scheduled protection . . . . . . . . . . . . . . . . . . 190 4-75 Advanced settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 4-76 Initial Tivoli Continuous Data Protection for Files panel . . . . . . . . . . . . 192 4-77 Central administration configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 4-78 Publish settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 4-79 Rename fpcommands.xml to use push installation . . . . . . . . . . . . . . . . 195 4-80 Push installation on Bruge, Windows 2003 server . . . . . . . . . . . . . . . . 196 4-81 Warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 4-82 Scheduled backup reports table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 4-83 Expiration example on Tivoli Storage Manager Server . . . . . . . . . . . . . 199 4-84 Example of enterprise environment with Tivoli Storage Manager and file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 4-85 Lab environment (Tivoli Storage Manager and file server) . . . . . . . . . . 203 4-86 General configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 4-87 Files to protect in continuous protection . . . . . . . . . . . . . . . . . . . . . . . . 205 4-88 Remote storage configuration to file server Florence . . . . . . . . . . . . . . 206 4-89 Select applications, files, and frequency to back up to a file server . . . 207 4-90 Create the include list for scheduled protection . . . . . . . . . . . . . . . . . . 208 4-91 Advanced settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 4-92 Central administration configuration for group A. . . . . . . . . . . . . . . . . . 210 4-93 Publish settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 4-94 Remote storage configuration to file server Cairo . . . . . . . . . . . . . . . . . 211 4-95 Select applications, files and frequency to backup to file server Cairo . 212 4-96 Create the include list for scheduled protection . . . . . . . . . . . . . . . . . . 213 4-97 Advanced settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 4-98 Central administration configuration for group B. . . . . . . . . . . . . . . . . . 215 4-99 Publish settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 4-100 Central Management Report for Group B . . . . . . . . . . . . . . . . . . . . . . 218 4-101 Files to protect on file server Florence . . . . . . . . . . . . . . . . . . . . . . . . 219 4-102 Protected vaulting settings on file server Florence . . . . . . . . . . . . . . . 219 4-103 Files to protect on file server Cairo . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 4-104 Protected vaulting settings on file server Cairo. . . . . . . . . . . . . . . . . . 220 4-105 Message error when trying to delete vaulted files . . . . . . . . . . . . . . . . 221 4-106 Protect Lotus Notes 7, using scheduled continuous protection . . . . . 222 4-107 Password for Lotus Notes Database. . . . . . . . . . . . . . . . . . . . . . . . . . 222 4-108 Notes files on file server Cairo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 4-109 Backup policy on Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . 224 4-110 Register node on Tivoli Storage Manager server . . . . . . . . . . . . . . . . 225 4-111 Example of dsm.opt file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 4-112 Validate password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 4-113 Schedule backup on Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . 226
4-114 Enterprise and remote offices example. . . . . . . . . . . . . . . . . . . . . . . . 227 4-115 Status page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 4-116 Welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 4-117 Files to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 4-118 Search BackupMe.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 4-119 Search status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 4-120 Select the file to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 4-121 Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 4-122 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 4-123 View report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 4-124 Select remote storage to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 4-125 Tivoli Continuous Data Protection for Files searching files . . . . . . . . . 236 4-126 Select file name and version of file to restore . . . . . . . . . . . . . . . . . . . 236 4-127 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 4-128 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 4-129 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 4-130 Check the restored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 4-131 Tivoli Continuous Data Protection for Files searching for files . . . . . . 239 4-132 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 4-133 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 4-134 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 4-135 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 4-136 Check the restored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 4-137 Tivoli Continuous Data Protection for Files Change Search Location window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 4-138 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 4-139 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 4-140 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 4-141 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 4-142 Select remote storage to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 4-143 Tivoli Continuous Data Protection for Files searching for files . . . . . . 248 4-144 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 4-145 Versions of notes file log.nsf on file server . . . . . . . . . . . . . . . . . . . . . 249 4-146 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 4-147 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 4-148 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 4-149 The restored notes file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 4-150 Tivoli Storage Manager backup-archive client . . . . . . . . . . . . . . . . . . 251 4-151 Restore Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 4-152 Select destination folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 4-153 Report status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5-1 Ready to Install the Program window . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5-2 Out of Disk Space window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figures
xi
5-3 Custom Setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 5-4 Cancel installation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 5-5 InstallShield Wizard Completed window (canceled installation) . . . . . . . 259 5-6 Setup Type (of installation) window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 5-7 Destination Folder window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 5-8 Change Current Destination Folder window . . . . . . . . . . . . . . . . . . . . . . 262 5-9 Error message during non-privileged user installation . . . . . . . . . . . . . . 263 5-10 Port 9003 already being used by another program . . . . . . . . . . . . . . . . 265 5-11 Tivoli Continuous Data Protection for Files reporting a problem . . . . . . 266 5-12 Tivoli Continuous Data Protection for Files unable to start the Initial Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 5-13 Tivoli Continuous Data Protection for Files entries in the event log . . . 268 5-14 Error entry in the Windows system event log . . . . . . . . . . . . . . . . . . . . 269 5-15 Port number in the FpPort DWORD Value . . . . . . . . . . . . . . . . . . . . . . 270 5-16 Modifying the FpPort DWORD Value . . . . . . . . . . . . . . . . . . . . . . . . . . 271 5-17 Changing the port number to 9005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 5-18 New port number in the FpPort DWORD Value . . . . . . . . . . . . . . . . . . 272 5-19 Original start.html file with port 9003 . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 5-20 File start.html after editing (now using port 9005) . . . . . . . . . . . . . . . . . 274 5-21 Netstat -a output showing the usage of the new port 9005. . . . . . . . . . 276 5-22 HTML listener now successfully listening on port 9005 (Event Viewer) 277 5-23 Tivoli Continuous Data Protection for Files user interface using port 9005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 5-24 Shortcut in the quick launch area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 5-25 Push installation failing due to remote computer not being available . . 281 5-26 Check if remote system is available using the ping command . . . . . . . 282 5-27 Push installation failing due to wrong user name or wrong password . 283 5-28 Push installation failing due to wrong command syntax . . . . . . . . . . . . 284 5-29 Successful push installation of Tivoli Continuous Data Protection for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 5-30 Tivoli Continuous Data Protection for Files (pull) installation message 287 5-31 Event message due to installation of new software version . . . . . . . . . 288 5-32 FPcommand.bat file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 5-33 Options file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 5-34 Message to reboot the computer after the (pull) installation . . . . . . . . . 290 5-35 External USB disk named USB_Drive mapped as drive F:. . . . . . . . . . 292 5-36 Drive F: (USB_Drive) as remote backup target (external device) . . . . . 293 5-37 Disk full informational message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 5-38 Event log entry due to target backup device being full (Event ID: 6077)294 5-39 Remote storage location inaccessible due to disk / file system full (Status page) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 5-40 Tivoli Continuous Data Protection for Files experiencing a problem. . . 295 5-41 Event log entry due to disk / file system full condition (Event ID: 6000) 296
xii
5-42 Modified settings in the Remote Backup page to save space on the remote target location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 5-43 Changed drive letter assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 5-44 Informational message that the network target cannot be reached . . . 299 5-45 Event entry due to replication problem caused by changed drive letters (Event ID: 6069) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 5-46 Remote storage location inaccessible due to changed drive letter assignment (Status page). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 5-47 Shared network folder e$ on file server Izmir mapped to drive (W:) . . . 303 5-48 Using the UNC name instead of the drive letter for the remote storage location (Remote Storage page). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 5-49 Using a WebDAV server as the remote storage destination . . . . . . . . . 306 5-50 Tivoli Continuous Data Protection for Files needs a password (informational message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 5-51 Tivoli Continuous Data Protection for Files prompts for a password to access the WebDAV server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 5-52 Entering user name and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 5-53 The two passwords do not match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 5-54 WebDAV server not reachable because no Internet connection is available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 5-55 WebDAV server can be reached again (Internet connection established) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 5-56 Default (minimum) dsm.opt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 5-57 Using a Tivoli Storage Manager server as a remote backup location (Helsinki). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 5-58 Window explains target location (Helsinki) is not responding properly . 314 5-59 Tivoli Continuous Data Protection for Files warning message . . . . . . . 314 5-60 Event log entry due to unknown or incorrect ID (node name) entered . 315 5-61 Entries in dsierror.log caused by unknown or incorrect ID (node name) entered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 5-62 Tivoli Continuous Data Protection for Files prompting for a password to access the Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . 318 5-63 Informational entry in the event log (password information needed) . . 319 5-64 Event log entry due to insufficient permission to delete backed up data320 5-65 Error messages in dsierror.log due to insufficient permissions to delete backed up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 5-66 Event log entry when storing more versions of files as defined on remote storage location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 5-67 Tivoli Continuous Data Protection for Files unable to unlink the file (Event ID: 6086). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 5-68 FilePath ERROR entry (Event ID: 6000) in event log due to a permission problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 5-69 Entry in file purge_failed.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figures
xiii
5-70 File dsierror.log with error messages ANS1126E . . . . . . . . . . . . . . . . . 325 5-71 Target location (Helsinki) is not responding properly (window). . . . . . . 331 5-72 Entry in event log due to session being rejected from Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 5-73 ANS1355E message in dsierror.log file (session rejected) . . . . . . . . . . 332 5-74 Replication engine unable to copy the file (Event ID: 6086) . . . . . . . . . 333 5-75 Entry in file replication-failed.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 5-76 Informational message about the network target being not reachable . 336 5-77 TCP/IP connection error messages in file dsierror.log . . . . . . . . . . . . . 336 5-78 Event log entry caused by the network target being not available (Event ID: 6069). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 5-79 Entry in file replication-active.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 5-80 Entries in file replication-queue.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 5-81 Modified dsm.opt file containing an exclude statement for *.txt files . . . 340 5-82 Entry in event log due to file being excluded from backup (Event ID: 6000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 5-83 Replication engine unable to copy the file (Event ID: 6086) . . . . . . . . . 342 5-84 ANS1115W warning message in dsierror.log (excluded file) . . . . . . . . 343 5-85 Remote storage location not reachable (notification message) . . . . . . 344 5-86 Remote storage location inaccessible (Status page) . . . . . . . . . . . . . . 345 5-87 Remote storage location reachable again (notification message) . . . . 346 5-88 Remote storage location accessible again (Status page) . . . . . . . . . . . 346 5-89 FilePath agent in interactive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 5-90 Command to start a Tivoli Continuous Data Protection for Files trace . 354 5-91 Create file.doc to trigger an activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 5-92 DebugView capturing the trace output . . . . . . . . . . . . . . . . . . . . . . . . . 355 5-93 Command to stop the trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 5-94 Quitting the interactive mode of the FilePath agent . . . . . . . . . . . . . . . 355 5-95 Functionality overview of Tivoli Continuous Data Protection for Files. . 377
xiv
Tables
1-1 Comparison between Tivoli Continuous Data Protection for Files and traditional backup solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2-1 Summary of protection methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 3-1 Default installation and data directories . . . . . . . . . . . . . . . . . . . . . . . . . 109 3-2 File and folder pattern matches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 3-3 Interaction of inclusion and exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 3-4 General page default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 3-5 Files to Protect page default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3-6 E-mail Protection page default settings. . . . . . . . . . . . . . . . . . . . . . . . . . 118 3-7 Remote Storage page default settings . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3-8 Advanced page default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 4-1 Tivoli Continuous Data Protection V3.1 feature support matrix . . . . . . . 122 4-2 Central administration folder configurations for managing clients. . . . . . 192 4-3 Lifecycle file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 4-4 Characteristics of file on Tivoli Storage Manager . . . . . . . . . . . . . . . . . . 198 4-5 Central administration folder configurations for managing clients. . . . . . 216 5-1 Description of options used in dsm.opt . . . . . . . . . . . . . . . . . . . . . . . . . . 311 5-2 Some additional useful dsm.opt options . . . . . . . . . . . . . . . . . . . . . . . . . 312 5-3 Important system operation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 5-4 Installation log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 5-5 Replication logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 5-6 Scheduled protection logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 5-7 Local pool log file and \gendb\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 5-8 Tivoli Storage Manager API log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 5-9 Solution tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 5-10 Solution demonstration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 5-11 Skill adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 5-12 Major solution deployment tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 5-13 Technical requirement gathering sample examples . . . . . . . . . . . . . . . 366 5-14 Solution planning sub-tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 5-15 Solution implement sub-tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 5-16 Solution test sub-tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 5-17 Solution client training sub-tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 5-18 Engagement closing sub-tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
xv
xvi
Examples
5-1 Registering node florence without delete backup permission (register node) 316 5-2 Details of node florence without delete backup permission (query node) 317 5-3 Select command output displaying too much active versions of a file . . 326 5-4 Register node florence with backdelete=yes parameter (register node). 326 5-5 Update existing node florence with backdelete=yes parameter (update node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 5-6 Details of node florence with delete backup permission (query node) . . 327 5-7 Select command output displaying active and inactive versions of a file 328 5-8 Running expiration on the Tivoli Storage Manager server (expire inventory) 328 5-9 Select command output after running expiration (only active versions) . 329 5-10 Tivoli Storage Manager client sessions disabled on Tivoli Storage Manager server (query status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 5-11 Enable Tivoli Storage Manager client sessions again (enable sessions)334 5-12 Tivoli Storage Manager client sessions enabled on IBM Tivoli Storage Manager server (query status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 5-13 Tracing example (trace mask=fpl_meta). . . . . . . . . . . . . . . . . . . . . . . . 355
xvii
xviii
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
xix
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks (logo) AIX Domino IBM Lotus Notes Lotus Notes Passport Advantage Redbooks System p Tivoli
The following terms are trademarks of other companies: Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates. NetApp, and the Network Appliance logo are trademarks or registered trademarks of Network Appliance, Inc. in the U.S. and other countries. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Internet Explorer, Microsoft, Outlook, Windows Server, Windows Vista, Windows, Win32, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
xx
Preface
Tivoli Continuous Data Protection for Files is specifically targeted at user computers, such as mobile computers and workstations, as well as file servers. It provides continuous data protection of files, providing the highest level of protection possible, yet is simple to use and administer. This book presents a deployment guide for Tivoli Continuous Data Protection for Files Version 3.1. We cover planning, installing, and troubleshooting Tivoli Continuous Data Protection for Files for several use case scenarios. In addition, we provide some case studies, including integration with IBM Tivoli Storage Manager, that can be used as a proof of concept or demonstration of the product at a client environment. This book is geared for IT Specialists who will be working on Tivoli Continuous Data Protection for Files installations and proof of concepts.
The team that wrote this book

This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin Center. Vasfi Gucer is an IBM Certified Consultant IT Specialist working at the ITSO Austin Center. He worked with IBM Turkey for 10 years and has been with the ITSO since January 1999. He has more than 12 years of experience in systems management, networking hardware, and distributed platform software. He has worked on various Tivoli customer projects as a Systems Architect in Turkey and the United States. Vasfi is also a Certified Tivoli Consultant. Greg Bass is a Tivoli storage specialist in the Techline presales support organization based out of Austin, Texas. Greg has been supporting Tivoli storage products since 2000 when he was hired by the Tivoli Sales Infrastructure Group (SIG). Greg originally joined IBM in 1999 when he was brought to Austin to provide technical support for Lotus Notes and Domino servers. Greg has been in the technology realm for over 15 years. Prior to IBM, Greg worked in the San Francisco bay area for PC Computing magazine, Oracle and an Internet startup called Fabrik. Wolfgang Beuttler is an IBM Tivoli Storage Manager Support Specialist in Mainz, Germany. He works for the Tivoli Storage Manager front- and back-end support team and provides support to clients all over the world, including onsite
xxi
support. He has more than 14 years of experience in IT and eight years of experience with IBM and the Tivoli Storage Manager product portfolio, starting with ADSM Version 3.1. His areas of expertise include defect as well as non-defect problem determination of Tivoli Storage Manager products. Marcia Kubo is an IT Presales Support Specialist, in Brazil. She has eight years of experience in the IT field. She has been working for IBM since 2004. Her areas of expertise include IBM System p and AIX, IBM Storage and Data Protection solutions. She is an ITIL Certified, Tivoli Productivity Center V3.1 Certified, IBM Certified Deployment Professional: Tivoli Storage Manager V5.3, IBM Certified Storage Administrator: Tivoli Storage Manager V5, and an IBM Certified Advanced Technical Expert for AIX version V4. Thanks to the following people for their contributions to this project: Arzu Gucer, Bart Jacob International Technical Support Organization, Austin Center Terry Copeland, William Haselton, Linda Sandmann, Jennifer Shaw, Eric Schaefer, Chris Stakutis, Daniel Thompson, Erik Wilkinson IBM USA
Become a published author

Join us for a two- to six-week residency program! Help write a book dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will have the opportunity to team with IBM technical professionals, Business Partners, and Clients. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html
xxii
Comments welcome
Your comments are important to us! We want our books to be as helpful as possible. Send us your comments about this book or other IBM Redbooks in one of the following ways: Use the online Contact us review Redbooks form found at: ibm.com/redbooks Send your comments in an e-mail to: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xxiii
xxiv
Part 1
Part
Planning and architecture

In this part we introduce the planning and architecture considerations for Tivoli Continuous Data Protection for Files V3.1.
Chapter 1.
Introduction to Tivoli Continuous Data Protection for Files

The newest phase in the evolution of file backup is real time protection, and IBM Tivoli Continuous Data Protection for Files delivers a compelling solution offering a unique blend of continuous data protection and scheduled data protection in a single product. Tivoli Continuous Data Protection for Files is a solution for both file servers and user endpoints such as notebooks and workstations. Tivoli Continuous Data Protection for Files exploits the increasing availability of affordable disk storage by offering multiple disk-based target options for copies of your data. Instead of waiting for a scheduled interval, Tivoli Continuous Data Protection for Files backs up your files the moment they are saved, in real time. What's more, it does this effortlessly and transparently, in some cases eliminating the backup window. This chapter provides an introduction to Tivoli Continuous Data Protection for Files and discusses the following topics: Introduction to Tivoli Continuous Data Protection for Files on page 3 How Tivoli Continuous Data Protection for Files works on page 11 Main features of Tivoli Continuous Data Protection for Files on page 13
Value proposition of Tivoli Continuous Data Protection for Files on page 14
1.1 General overview of Tivoli Continuous Data Protection for Files

It is important to understand the evolution of data protection applications and the environments in which they operate in order to fully appreciate the Tivoli Continuous Data Protection for Files solution.
1.1.1 What is Tivoli Continuous Data Protection for Files?

Tivoli Continuous Data Protection for Files is a unique hybrid approach to file backup that combines replication with traditional backups. Tivoli Continuous Data Protection for Files is a real time, continuous data protection solution for mobile computers, workstations, and fileservers. Backups can go to one or more disk targets. Files are copied and saved in their native format. Tivoli Continuous Data Protection for Files is also highly tolerant of transient network connectivity. Easy-to-use wizards allow for simple configuration and file restoration. In addition, Tivoli Continuous Data Protection for Files is engineered specifically to support Lotus Notes and Microsoft Outlook mail clients. Tivoli Continuous Data Protection for Files will back up your most important files the moment they change instead of waiting for a scheduled backup. Non-critical files can be backed up on a scheduled basis. It works in the background, similar to a virus scanner, and is therefore completely transparent to the user. Since Tivoli Continuous Data Protection for Files has a single end-point architecture, there is no need for additional components such as a server component. It requires only a single installation on the system where the files to be protected are located. Tivoli Continuous Data Protection for Files keeps copies of your data in their native file format and does not modify or encode them in any way. This transparency allows for direct access to the copied files with our without the Tivoli Continuous Data Protection for Files GUI. In addition to providing multiple recovery points through file versioning, Tivoli Continuous Data Protection for Files provides additional redundancy by allowing multiple options for target destinations for your copied files: On local disk for protection, even when not connected to a network To a network file server or NAS device for remote machine protection To an IBM Tivoli Storage Manager (Tivoli Storage Manager) or IBM Tivoli Storage Manager Express (Tivoli Storage Manager Express) server To a Web-based device through http or https
Chapter 1. Introduction to Tivoli Continuous Data Protection for Files
Table 1-1 demonstrates the differences between Tivoli Continuous Data Protection for Files and traditional backup approaches.
Table 1-1 Comparison between Tivoli Continuous Data Protection for Files and traditional backup solutions Tivoli Continuous Data Protection for Files When to protect Continuous for highly important files, scheduled for others Journal-based on all file systems Disk only, locally or remote; Tivoli Storage Manager Left native, online as files Simplified per-client administration only Traditional backup solutions Scheduled, full system
How to detect Where copies are stored
Journal-based on some file systems Typically on tape
Storage format Management / administration complexity
Wrapped into a proprietary format Client-server concept; server component typically more expensive/complex
So overall, Tivoli Continuous Data Protection for Files provides simple, effective, and real time file protection for: Accidental file deletion File corruption Unwanted file alteration Disk crashes Other unforeseen losses
1.1.2 Why Tivoli Continuous Data Protection for Files is needed

Businesses today are increasingly concerned with protecting their data. Losing key business information can hamper productivity, delay projects, and divert resources and calls to the help desk. It can also harm organizations when they face regulatory scrutiny. In fact, many businesses today are legally required to use formal data protection. Data corruption is a regular concern, and companies need better recovery point capabilities. Often the most valuable files are those that the users are working with right now. In addition, companies need sophisticated policy-based data management that enables them to focus on data with the most business value.
Although most companies have implemented solutions for protecting enterprise data, data residing on workstations and notebooks is often under protectedeven though it amounts to 60 percent of all corporate data, according to some industry experts. This is particularly true where lost data can significantly impact productivity and viability. Additional facts to consider: In many companies, about 60-70% of corporate data resides on notebooks and workstations which are rarely, if ever, backed up. Almost half of small to medium sized businesses admit to having no formal data protection procedure. The loss of productivity due to data loss on user computers is a growing concern. Virus and data corruption on file servers is an increasing problem. Companies need better recovery point capabilities. Todays backup and recovery solutions are usually scheduled and tend to miss the most valuable data- what the user is working on right now. Mobile computer/desktop data protection is a growing problem: Corporate data centers are reluctant to take on mobile computer management. The business impact of lost data on mobile computers/desktops is increasing: Specific segments, such as law firms, medical practices, consulting, and so on, can have a very significant impact to productivity and liability. The aggregate impact to large corporations is significant.
With this in mind, Tivoli Continuous Data Protection for Files is designed to help alleviate clients' concerns and provide simple, effective, and efficient data protection and integrity. Key client issues driving the requirements for continuous data protection are: Critical information assets are being stored across the organization; they are no longer consolidated on just a few key servers. The complexity and expense associated with the replication of information assets across an organization. A shortage of skilled people resources, which demands that highly automated tools be deployed to help allow consistent practices across platforms, minimize human error, and improve the amount of storage a single storage administrator can handle. Meeting service-level objectives by providing continuous availability of data.
The integrity of data for governance and security requirements. Backups taken only on a scheduled basis allow too much productivity loss. For several years a major market trend has been the steady decline in the cost of disk storage (local hard drives, SAN disks, removable disks, NAS devices, and so on). This trend makes file protection using disk replication technologies more cost effective compared to traditional backup/recovery solutions, which primarily use tape as their storage repository. Tivoli Continuous Data Protection for Files leverages this development by utilizing a traditional backup and recovery solution while also employing data replication techniques. In the long term, this approach will lead to maximized efficiency and productivity in terms of both human and financial resources. For more information about the value proposition and the benefits of using Tivoli Continuous Data Protection for Files, refer to section 1.4, Value proposition of Tivoli Continuous Data Protection for Files on page 14.
Why is Tivoli Continuous Data Protection for Files needed?

1. Employee productivity declines when data assets are lost or difficult to recover. Business and regulatory requirements for data continuity are increasing. Disk costs are declining, making replication technologies more cost effective. Critical data assets found in remote offices, mobile computers, and desktops are often not protected. Employee productivity declines with difficult recovery of data and recreation of lost assets.
Cost
Recovery from a disk image
Recovery from tape copy
2.
3.
4.
Recovery Time Objective
5.
Tivoli Continuous Data Protection for Files delivers faster recovery of file assets
Figure 1-1 Why Tivoli Continuous Data Protection for Files is needed
1.1.3 Who should use Tivoli Continuous Data Protection for Files?
The concept and design of Tivoli Continuous Data Protection for Files makes it ideal to protect both home computing environments and workstations or large file servers in business critical environments. Generally speaking, Tivoli Continuous Data Protection for Files should be used by everyone who has the need to continuously protect files in real time. Ideal candidates for Tivoli Continuous Data Protection for Files are organizations with valuable data spread across multiple locations, departments, and file servers, or those whose IT infrastructure includes desktops and mobile computers which are not protected adequately or frequently. Tivoli Continuous Data Protection for Files might also be of interest for enterprise clients with large file servers already using traditional backup solutions like Tivoli Storage Manager or Veritas NetBackup. Due to the amount of data needed to be backed up, large file servers are often unable to meet their backup window. Data loss can also occur after the point of the last scheduled backup. Tivoli Continuous Data Protection for Files with its continuous backup methodology is therefore a perfect complement to traditional backup solutions. Overall, Tivoli Continuous Data Protection for Files could be the answer when: Clients are considering buying disks as an alternative to tape for simpler administration and configuration and faster recovery service levels. Clients view data as a major corporate asset. Clients are considering snapshot technologies. With Tivoli Continuous Data Protection for Files, there is no need to understand advanced IT concepts such as snapshots, mirrors, synchronous versus asynchronous and how to configure, maintain, and manage such elements. Clients are concerned about their ability to meet service and availability levels with a minimal to zero backup window. Skilled storage administrators are difficult to find and retain. Employee productivity suffers due to accidental data loss and recreating files from scratch. Organizations are considering a backup solution for remote offices Tivoli Continuous Data Protection for Files is ideal for remote office servers, because it will maintain a local backup of files and replicate data to centrally based servers while tolerating issues with network connectivity. System administrators need their computer systems to be online 24x7 with minimum CPU or network impact during data protection operations.
The organization is considering how to easily protect information assets found on individual desktops and mobile computers with minimum administration. The organization needs to protect critical files from alteration, deletion, viruses, and corruption.
10
1.2 How Tivoli Continuous Data Protection for Files works

Tivoli Continuous Data Protection for Files is a new backup paradigm using a unique hybrid approach by combining modern replication technologies with traditional backup methods. It does so by taking all the benefits from each technology and uniting them together into a completely new product: Tivoli Continuous Data Protection for Files.
Replication
To-disk duplication Lightning fast Real time for important files Tolerant of transient networks Multiple targets
Traditional backups
Versioning of files Central administration Archiving (vaulting) Retention Highly scalable
Tivoli Continuous Data Protection for Files
Figure 1-2 Unique hybrid approach of Tivoli Continuous Data Protection for Files
But how does it work? Figure 1-3 on page 12 gives a general overview on how Tivoli Continuous Data Protection for Files works.
11
Figure 1-3 General overview of Tivoli Continuous Data Protection for Files
Tivoli Continuous Data Protection for Files tracks the creation of new files or changes to existing files. If the file is included in your list of protected files or file types an immediate copy is made into a backup area (a separate directory tree) on the local disk. Tivoli Continuous Data Protection for Files can store multiple versions of each file subject to the local pool size which can be configured by the user. When the pool is full, the oldest copies (versions) are removed to make room for newer ones. The same file can also be sent to a remote storage area, such as a removable disk, file server, NAS device, and WebDAV server for remote protection. Another copy of the file can be sent to a Tivoli Storage Manager server or Tivoli Storage Manager Express server. Traditionally, Tivoli Storage Manager is a data protection product often used in larger business environments. Those clients might find Tivoli Continuous Data Protection for Files useful as a real time client solution for mobile computers and workstations, but they still want most of the protected data to be managed by a Tivoli Storage Manager server. Note: The Tivoli Continuous Data Protection for Filescode installs the Tivoli Storage Manager API automatically, so there is no need to install a separate API package. If scheduled protection is enabled, then files associated with scheduled protection will be queued for transmission to the remote target based on the
12
interval that has been selected within Tivoli Continuous Data Protection for Files (Hourly, Daily, Weekly, Monthly). When the interval expires, Tivoli Continuous Data Protection for Files will copy changed files to the remote target storage location. The types of protection offered by Tivoli Continuous Data Protection for Files (continuous or scheduled, local or remote) can be easily configured by the user in multiple combinations. This allows the user to protect their assets in a highly flexible manner. To summarize how Tivoli Continuous Data Protection for Files works, we have to differentiate between continuous and scheduled backup concepts: Files protected continuously: Specify multiple storage locations for continuously protected files. The target area(s) will capture a copy of the file each time it is saved. The local target area is auto-managed as a pool with a configurable size. There is an option to specify a remote file server for off-machine protection; it is still real time, but tolerant of transient networks. There is an option to specify a Tivoli Storage Manager server or Tivoli Storage Manager Express server for off-machine protection; it is still real time, but tolerant of transient networks. Files protected by scheduled backups (primarily mail files): Mail files are protected on a scheduled basis by being sent to the remote file server or Tivoli Storage Manager server. Change-journal eliminates having to take processor resources to scan the file system. Files are versioned on a remote file server, allowing for point-in-time restore. Remote versions are automatically managed to a configurable pool size.
1.3 Main features of Tivoli Continuous Data Protection for Files

At the time of this publication, the latest version of Tivoli Continuous Data Protection for Files was version 3.1. The main features of this version are: Completely automated continuous protection of important files When a file is saved: A copy is stored in a pool on local disk.
13
Another copy can be sent to a file server, NAS device, or WebDAV server, Tivoli Storage Manager, or Tivoli Storage Manager Express server Real time data protection High/low priority files options Tivoli Continuous Data Protection for Files allows user designated files to be backed up continuously as soon as they change. The user can also designate less important or constantly changing files to be saved on a scheduled basis (Hourly, Daily, Weekly, Monthly). File include/exclude options Tivoli Continuous Data Protection for Files offers the usage of include/exclude lists. By using them, the client can define precisely what type of files will be included for protection. They can also specify a list of files or directories that will be excluded by Tivoli Continuous Data Protection for Files and not backed up or vaulted. Tolerant of transient networks Versioning of files Archive retention Scalable Small foot print Tivoli Continuous Data Protection for Files can be installed in a few minutes on a system and will only use about 21 MB of disk space. Simplified management and central administration Due to its simplified management concept, Tivoli Continuous Data Protection for Files provides a central administration interface that allows the user to restore his own files quickly and easily. No server component required Maintains native file format Tivoli Continuous Data Protection for Files maintains files in their natural format and does not encode them in a proprietary format or modify them in any other way.
1.4 Value proposition of Tivoli Continuous Data Protection for Files

For business units dependent on data availability and rapid data recovery, Tivoli Continuous Data Protection for Files provides uniquely efficient and effective
14
data protection to ensure business continuity, employee productivity, and integrity of information assets. For storage managers and administrators responsible for protecting data while containing cost, Tivoli Continuous Data Protection for Files simplifies heterogeneous storage management and provides real options for an integrated data protection solution across all information assets. Tivoli Continuous Data Protection for Files: Provides easy to use data protection and integrity, requires little or no training to use Improves employee productivity by providing real time backups of data, so when a failure occurs, the recovery can be the latest version, not the last time a scheduled backup ran Improves IT productivity and labor resource utilization, because users can more easily recover files without IT involvement Improves network and bandwidth usage, because it is optimized to send data through network only when it is connected with no user or IT manual intervention required for optimizing the bandwidth usage The value proposition using Tivoli Continuous Data Protection for Files can be summarized as follows: Reduced or eliminated backup window Improved backup resource utilization Better return on investment (ROI) and total cost of ownership (TCO) Note: In finance, the return on investment (ROI)a is a calculation used to determine whether a proposed investment is wise, and how well it will repay the investor. It is calculated as the ratio of the amount gained (taken as positive), or lost (taken as negative), relative to the basis. Total cost of ownership (TCO)b is a financial estimate designed to help consumers and enterprise managers assess direct and indirect costs related to the purchase of any capital investment, such as (but not limited to) computer software or hardware.
a. Definition taken from article Return on investment, found at: http://en.wikipedia.org/wiki/Return_on_investment b. Definition taken from article Total cost of ownership, found at: http://en.wikipedia.org/wiki/Total_cost_of_ownership
Improved recovery point objective (RPO)
15
Reduced loss of data Improved productivity Note: The RPO is the degree of difference between the active online data and the disaster recovery copy of that data. An RPO of zero would mean that the primary copy and the disaster recovery copy are in exact synchronization. A failure would result in zero loss of data. Improved recovery time objective (RTO) User initiated restore, zero administration intervention Optional recovery from disk (local or remote) Note: The RTO is the amount of time after a failure that someone is willing to spend before a given application or group of data is back up and available. An RTO of zero means that failures should cause zero disruption.
16
1.4.1 Benefits of using Tivoli Continuous Data Protection for Files

Using Tivoli Continuous Data Protection for Files provides the following benefits: Simplified storage management can save IT staff and computer user time and labor Continuous data protection provides data integrity when viruses attack and corrupt systems Reduces or eliminates backup windows Optimizes integration to network and enterprise data protection solutions Optimizes bandwidth and network transfer of data Continuously protects multiple versions of files to allow clients a choice of recovery points Ability to write-protect data locally to prevent unwanted modification This has a variety of uses such as allowing a user to store final versions of documents to prevent unintentional changes. Ability to send data to heterogeneous backup devices: local file system (on local or SAN disk), file server, NAS, USB disk, HTTP server, or Tivoli Storage Manager server
1.4.2 Unique differentiators

The following unique differentiators of Tivoli Continuous Data Protection for Files have been identified: Fast time to deployment Tivoli Continuous Data Protection for Files can be installed, configured, and running in a few minutes. Ease of daily use No need to understand more IT-savvy concepts such as "snapshots" and how to maintain, configure, and manage such elements. Elimination or reduction of backup windows Backup target flexibility Tivoli Continuous Data Protection for Files allows the target of the backup to be any type of modern disk-based storage device such as: a local file system on local or Storage Area Network (SAN) disk, a USB (Universal Serial Bus) device, a File Server, a Network Attached Storage (NAS) device or a WebDAV enabled web server. If Tivoli Storage Manager is used as the remote storage destination, both disk and tape storage pools can be used. Easily integrates into traditional backup solutions
17
Tivoli Continuous Data Protection for Files integrates naturally with Tivoli Storage Manager and Tivoli Storage Manager Express as well as the backup target device, which can be backed up by any off the shelf data protection package. Effective backup for remote systems and traveling users Tivoli Continuous Data Protection for Files tolerates a missing remote target without generating error messages or shutting down the product. As soon as the remote target becomes visible again, Tivoli Continuous Data Protection for Files will resume its continuous or scheduled backups to the target. Effective backup for remote offices Tivoli Continuous Data Protection for Files is ideal for remote office servers, because it will locally version and protect high-importance files and migrates data back to corporate servers while tolerating network spottiness. Simple backup for department solutions Anyone, even with minimal technical skills, can add Tivoli Continuous Data Protection for Files to a department file server to provide real time file protection (even if just locally). User productivity With Tivoli Continuous Data Protection for Files, you can be assured that there is no loss of productivity due to re-creation of lost work. Other backup/recovery solutions offer near continuous protection: once an hour or once a day, which is not as effective as continuous data protection. Automating manual process to protect all corporate assets Users do not need to save to corporate systems for data protection and audit purposes; Tivoli Continuous Data Protection for Files automatically protects all changes to files (even when not connected to the corporate network). Protects critical files from alteration or deletion, viruses, and corruption Tivoli Continuous Data Protection for Files allows users to protect critical corporate assets in order to prevent deletion or alteration of active files from user error, device failure, or corruption.
18
Chapter 2.
Product architecture, planning, and deployment

This chapter discusses the architecture, planning considerations, and deployment of Tivoli Continuous Data Protection for Files and has the following sections: Product architecture on page 20 Planning for deployment on page 25 Best practices and sizing considerations on page 30 Tivoli Continuous Data Protection for Files installation requirements on page 34
19
2.1 Product architecture

Tivoli Continuous Data Protection for Files is a product that has just enough controls and options to allow for a wide range of different configurations. At its core, the program operates at the kernel level of the operating system, monitoring all file operations. It keeps track of all pertinent activities and performs other operations based on the configuration. Tivoli Continuous Data Protection for Files knows when you open files, when you save them, when you close them, and whether or not you have changed the file when you close or save them. When there is a change saved, this is noted and a new version of the file is replicated to one or more locations, either immediately or at a later time. The underlying technology was designed to be a general file system extension tool that can be presented to the user in a variety of different formats, for different purposes. The current product, Tivoli Continuous Data Protection for Files, mostly exploits the function of copy-on-close replication.
2.1.1 Main components

The main components of Tivoli Continuous Data Protection for Files are: Kernel fp.sys1: This is the driver that loads when the computer boots up. It is located in \%WINDIR%\System32\Drivers. User FilePathSrv.exe: This is the daemon, or process, that starts as a service (CDPforFilesSrv). If you are running in regular user mode, this service will stop until it has something to do. If you are running in service mode, the service will stay active. To run it from a command prompt, type filepathsrv -d. It is located in the Installation directory. fpa.exe: This is the command line interactive program that passes commands to the kernel. It can be used to set tracing levels. It is located in the Installation directory.
2.1.2 Capabilities
The kernel layer of the product performs a number of activities: Audit: Watches file activity, particularly noting files that are closed with new data Write Once Read Many (WORM): Prevents I/O or any alteration to files
1
The underlying technology of Tivoli Continuous Data Protection for Files is called FilePath. fp is shorthand for FilePath. Some internal components are called fp or use fp as a prefix.
20
Mirroring: Kernel-based I/O mirroring: Inactive in the current product Replication: Notification of files that are replicated The kernel layer is based on a set of rules that set up the conditions under which certain activities, or actions, are performed. The rules and actions come preconfigured to make the product act as designed. When Tivoli Continuous Data Protection for Files performs a basic local backup of a file that has changed, the kernel is obeying a chained set of rules and actions. A basic chain includes: Rule: When should the action occur? On Open, On Write or On Close.
Meta rules (optional): What conditions apply? For example, it does not fall under the exclusion list, and it matches *.ppt (or something from the inclusion list). Action: What to do if the rules are true? Trigger a replication, block I/O to this file (Vault action).
All of the basic rule action chains required for Tivoli Continuous Data Protection for Files to function properly are kept in XML format in the file fpa.txt. Important: Do not edit the fpa.txt file. First, you might change something in one of the rule action chains, which will cause the product to become unstable. Second, Tivoli Continuous Data Protection for Files updates the file from time to time, so you might lose some information by saving over necessary changes. The daemon, or process, handles the following activities: Executing the replication, or copy-on-close Driving the scheduled protection Displaying updated information in the GUI
Chapter 2. Product architecture, planning, and deployment
21
See Figure 2-1 for an illustration of the relationship between the kernel layer and the daemon or driver.
KERNEL
FPQ: Critical component. Priority-based queue. Both roundtrip (synchronous) and one-way. Options include punt if full or block if full. Kernel injects commands; mostly to kick-off replication activities, but other maintenance too. Audits accumulate in the kernel and are batchdumped to daemon for speed.
Platform
FPQ
Audit buffer
-Inject XML -Get Audit buffer -Get database, etc
Manipulation of live database
IOCTL interface
Agent has a thread that is always in a read() to get next queue command; Does a write() to respond.
HTML listener
Audit thread
Service Interactive FPA
Replication threads
(up to 10)
Main thread
AGENT
Figure 2-1 Agent-driver interaction
2.1.3 Daemon architecture

The daemon runs several threads to perform its various functions. They are: Queue thread Audit thread Sysprotect TSM thread HTML listener Replication thread(s)
Queue thread
When the kernel needs something done that can only be done in user mode, it creates a Queue entry, posts it, and usually waits for a response from the daemon. The main daemon thread is the queue reader, which loops in a read().
22
There are about six commands that the queue thread can be asked to perform, but the most important one in this product is Do a replication. For each replication request at a given priority level, a file is opened and appended with the specifics of the replication request. These files are in XML format. (See the Replication section of Figure 2-1 on page 22 for a description of these files.) These files are monitored by the replication threads that are described below.
Audit thread
The main purpose of the audit thread is to wake up periodically and ask the kernel to dump its audit/log buffers. The audit buffers capture file change events that are used by Tivoli Continuous Data Protection for Files for scheduled protection and other activities. The daemon sleeps for a few seconds and then drains any messages in the buffer (via an IOCTL request into the kernel). The buffer is formatted as a list of XML messages; each message indicates both the file to add this message to, and the message. The message can be anything defined by the action and is typically in XML format. It includes various expanders (substitutions) for such things as filename, and so on. The following is an example of a message:
<change vfs=Unlink src=C:\fp\buildchk.log other=size=10697 app=System/>
The ChangeJournal (sysprotect) rules/actions cause these audits to be accumulated into a file called ChangeJournal.log in the installation directory. The LocalPool rule causes audits to accumulate the locally versioned files into the LocalPool.log file.
Sysprotect
When this thread is started, its job is to perform a scheduled protection by addressing all of the files listed in the ChangeJournal.log file. This thread is started either on a periodic basis, or when the user selects Start Scheduled Backup Now from the Scheduled Protection window. When started, the thread will do the following: 1. Detect if the file ChangeJournal.log_1_inprocess exists and process that file. 2. Automatically rename ChangeJournal.log to ChangeJournal.log_1_inprocess so that audits can continue to accumulate. 3. Process the ChangeJournal.log_1_inprocess file and record each line to the ChangeJournal.log_2_last file. To minimize audit traffic, the kernel side keeps a hash of files that have been altered (tabulation) and avoids issuing multiple audits for files that have been repeatedly altered. This hash has a 2,000 file limit and then it cycles. Sysprotect also ignores the vfs mentioned in the log (see example message above) and
23
determines what to do based on the current version of a file. For example, if the source file is missing, presume that an unlink should be performed. The Sysprotect thread also performs the function of remote pool management. Every time a version is created on the remote target, an entry is made in the RemoteVersions.log file. The ServerPool metric is increased by the versioned files size, and this metric is compared against the ServerPoolQuota metric that was configured in the Remote Storage settings in the Configuration Notebook. If the metric indicates that the pool size is over the quota, the following actions are performed: 1. The RemoteVersions.log file is consumed, one line at a time, deleting the oldest files and removing the file name from the list. 2. This continues until the pool size is at least 20% under the threshold size. 3. The remainder of the RemoteVersions.log file replaces itself. 4. Files deleted are logged as unlinks in the Replication.log file. 5. Deletions that fail are logged to either: purge_failed.log: Generally when users have cleaned up the pool by deleting files themselves, in which case the pool size metric is decreased purge_struggled.log: Usually in the case of a network access type of error
TSM thread
The TSM thread starts when a Tivoli Storage Manager backup occurs for the real time processing activity.
HTML listener
The HTML listener thread processes requests from the browser. The browser displays the product GUI, which has information about configuration and settings and is also used by the user to change configuration settings.
Replication thread(s)
The replication threads manage the replication activity. They are file-centric, and they monitor the replication files. The queue thread places the list of files to be replicated in a replication-queued.N file, where N is the priority. The replication thread automatically renames this to a replication-active.N file and then processes the replications in priority order. If the replication encounters a permanent failure, the transaction gets logged in the replication-failed.N file. All other transactions are posted to the replication.log file. These threads are restartable and persistent, which makes them easy to trace for diagnosing problems. If the threads die, they will not stall the system. See Figure 2-2 on page 25 for a diagram of this process.
24
KERNEL FPQ AGENT

Main thread Repl-1 Repl-1 Replication-1 thread thread thread
ReplicationQueued-Priority Rename ReplicationActive-Priority
ReplicationFailed-Priority
Replication-Log
Figure 2-2 Replication threads
2.2 Planning for deployment

Although it is simple to install and configure Tivoli Continuous Data Protection for Files, it is worth taking a little time to consider how best to deploy the product to leverage it to the fullest. In this section, we will discuss general considerations as you install and configure the product. For a single machine installation, it is important to configure the product so that it is working most efficiently for you. Tivoli Continuous Data Protection for Files is a set it and forget it type of product. Once you have it set up, it will run in the background and you will be mostly unaware of it until you need to restore a critical file. To make sure that you can easily restore the correct version of a file at that critical point, you should take a little time up front to review your configuration. Before you begin, you should consider the following questions: What are my critical files? Where should I back my files up to? How often do I need to back up different types of files? Do I need e-mail and scheduled backups? Do I need the Vault feature?
25
2.2.1 What are my critical files?

By default, Tivoli Continuous Data Protection for Files will back up the contents of your \My Documents\ folder, along with a few other file types. If you typically save all of your critical documents under this directory path, then you will not need to add anything to the inclusion list. If, however, you save critical files in a different directory path, you should consider what type of files they are and where they get saved. Some programs select a different path by default, or you might have set up a different location for some files. In this case, you need to consider where those files get saved, what type of files they are, and what the file extension is. Depending on your situation, you will need to add either the directory path or the file extension to your inclusion list.
2.2.2 Where should I back my files up to?

The default location for backups created by Tivoli Continuous Data Protection for Files is a local disk on your computer. Tivoli Continuous Data Protection for Files will automatically select the drive with the largest free space as the target location. The primary use of this backup site is for you to have immediate access to recently saved versions of your files. If you save a version of a file but need to undo that save, or if you mistakenly delete an important file, you can easily restore a previously saved version of the file from your local backup. If you are working on a computer that is not connected to a network or any type of external storage, this will be your only backup location. If you have access to some sort of remote storage, you will probably want to consider one or more of the other backup options. These options include a local hard drive (local network or USB drive), a remote file server, a remote WebDav server, or a remote Tivoli Storage Manager or Tivoli Storage Manager Express server. We strongly recommend using the remote backup option if at all possible in case of hard drive failure or loss. You will need to know the fully qualified UNC path for your remote drive to configure it properly. Check with your network administrator if you do not know what to use. Tip: If you will be backing up several computers to a single network drive, you will not need to set up a separate folder for each user. Tivoli Continuous Data Protection for Files will create a unique folder for each computer with the computers network name at the top of the directory structure, directly underneath the RealTimeBackup folder.
2.2.3 How often do I need to back up different types of files?

This question is dependent on each users unique environment. The very best, but totally impractical, configuration would back up every version of every file and
26
keep them forever. Since this is not possible, you need to think about what best suits your needs. If you are going to implement either the remote continuous option or the scheduled backup option, you will need to consider both the size and timing of your backup.
Remote continuous
Although this backup option is labeled continuous, this is not always literally true. Tivoli Continuous Data Protection for Files makes note of all of your file saves, but if you are not currently connected to the network or if you are in between the time intervals you have set up for Tivoli Storage Manager backups, a list of file changes will be kept for backup at the next possible time. When you are selecting a time interval for Tivoli Storage Manager backups, keep in mind that the most recently saved version of a file will be sent when your Tivoli Storage Manager interval is due. So, if you set your Tivoli Storage Manager interval for 30 minutes, and you save a file 10 times in that interval, only the last version of the file will be sent to your Tivoli Storage Manager server. The number of versions of that file kept in Tivoli Storage Manager is configured in Tivoli Storage Manager. Although you do not explicitly set the time interval for continuous remote backups to a file server, you should keep in mind what percentage of time you are connected to the network. This will have an impact in the number of versions you select to keep on the remote target before they are eligible to be purged.
2.2.4 Do I need e-mail and scheduled backups?

Tivoli Continuous Data Protection for Files offers a more traditional form of backup that allows you designate files that will be backed up on a scheduled interval- hourly, daily, weekly, and monthly. Scheduled backups are ideal for large files or dynamic files that change constantly, such as e-mail. You can back up these files to either a remote file or Web server or to your preconfigured Tivoli Storage Manager server.
E-mail backup
You configure Tivoli Continuous Data Protection for Files to backup your e-mail application and its associated files via the E-mail Protection tab. Because e-mail files are typically large, they are not backed up continuously. They are only backed up on the schedule that you select. E-mail files are backed up only to remote storage. If the remote storage is not available at the scheduled backup time, Tivoli Continuous Data Protection for Files will queue the backup copies for later transmission. When the remote storage area becomes available, Tivoli Continuous Data Protection for Files will create the backup copies on the remote storage area.
27
Additional files to protect on a schedule

Large or frequently saved files can consume considerable computing or network resources when they are backed up. You can scheduled periodic backups of these files when the burden on computing or network resources will be least inconvenient. Files protected by schedule will be backed up even if they are open, but you can try to schedule the backup for a time when the file will be closed. The files you select for scheduled protection will be backed up only at the scheduled time and only if they change during the scheduled interval. This can yield fewer backup versions than continuously protected files. Fewer backup versions use less storage space, but offer fewer opportunities when you want to restore a file. We strongly recommend that you include scheduled backups covering a larger set of files than included with continuous backup for the following reasons: You might have missed some important file types in your inclusion list. You might install software that creates a new directory structure for saving files and therefore would not be caught by the inclusion list. There might be other files that get damaged or accidentally deleted that are important for the operation of various programs on your computer. Having these files backed up on some schedule may prevent you from having to reinstall software. Important: The scheduled protection option offered in Tivoli Continuous Data Protection for Files cannot be used for a complete system restore in the event of total hard drive failure. It does not take a complete snapshot of your machine that would include the system files that are required for a complete system restore.
2.2.5 Do I need the Vault feature?

In some cases, you might have files that need to be preserved in their exact format for a period of time. One way to do this is to write them to a CD-ROM. However, with the Vault feature in Tivoli Continuous Data Protection for Files, you can protect these files in the same manner. Once you Vault a file with Tivoli Continuous Data Protection for Files the file cannot be changed in any way. Vaulted files are available as read-only versions and cannot be altered or deleted. Some users might need this function for regulatory reasons. For example, if you are required to keep financial records in their original form for seven years, you can put these files in a directory covered under the Vault function. Tivoli Continuous Data Protection for Files will protect them from editing and deletion.
28
2.2.6 Summary of protection methods

The attributes of each type of protection are compared in the following table.
Table 2-1 Summary of protection methods Continuous Protection Recommended for which files Recommended for your most important files. Not recommended for large dynamic files like e-mail. Backup copies are created on storage area. File is backed up whenever it is saved. Scheduled Protection Recommended for large dynamic files like e-mail. Vaulting Recommended for files that you dont want to be changed nor deleted.
How protected
Backup copies are created on a storage area File is backed up only at the scheduled time, and only if it has been saved since the previous schedule. Remote only. Files selected in the E-mail Protection page of the Settings Notebook. Files selected in the Folders and Files dialog of the Advanced page of the Settings Notebook.
Vaulted files and folders cannot be modified nor deleted. No backups.
Frequency of backups
Backup copy storage area Files protected
Local or remote. Files selected in the Folders and Files box and the Applications box of the Files to Protect page of the Settings Notebook.
Not applicable. Files selected in the Vault box of the Files to Protect page of the Settings Notebook.
29
2.3 Best practices and sizing considerations

Tivoli Continuous Data Protection for Files is a simple product that has just enough controls and options to allow for a wide range of different configurations. The goal of this section is to outline what the creators of Tivoli Continuous Data Protection for Files believe are typical best practices configurations.
2.3.1 Overall summary

Here is our overall summary of how Tivoli Continuous Data Protection for Files should typically be configured: General tab. Set Continuous protection level: Local storage only with 2 GB cache. Include Microsoft Office files and other user-created content that is considered high-value. Note: enabling continuous protection to Remote storage (which includes file servers, Web servers, or a Tivoli Storage Manager server) could cause unnecessary network load. Consider an hourly scheduled backup if you want to keep files extremely current on remote targets. E-mail protection tab. This page allows for backup scheduling of e-mail and other file types. Configure a daily backup schedule with 10 GB cache (or approximately 1/6 to 1/10 the size of the source disks); 5 versions (and leave the other defaults as is). Use the Scheduled Backup Settings link to configure your include/exclude list for scheduled protection. Include a broader list of files than that defined with Continuous protection. For robust file protection consider using a wild card * (everything else), and a weekly schedule because these backups could be lengthy. Tivoli Continuous Data Protection for Files hallmark feature is the local-continuous protection which allows users to be 100% protected regardless of where they are and what their network connectivity is. This local/continuous feature should always be active. It is prudent, however, to adjust the exclusion list carefully. Be sure the Files to Protect list includes document types (or locations) that truly represent the critical work for users.
30
Important: The default size for the remote storage area is 40 GB. If you increase the number of backup versions to keep, consider increasing your storage area size. If you are unsure of how much space to allocate, you can monitor your space usage on the Status page and adjust the version and space settings accordingly. When the storage space becomes full, Tivoli Continuous Data Protection for Files deletes older backup copy versions of files that have several backup copy versions. After deleting the versioned backup copies, if more space is needed for new backup copies, Tivoli Continuous Data Protection for Files deletes the last remaining backup copies of enough files to make room for the newest backup copy. If you try to remotely back up a file which is larger than the space you have allocated for your remote storage area, Tivoli Continuous Data Protection for Files will purge all older versions of your files and might fail to back up the file. Make sure that the maximum space for your remote storage areas is greater than the maximum file size for remote backup in the Advanced page of the Settings Notebook. For example, if you decrease your maximum space for backups to 1 GB, you should decrease the maximum file size for remote backup from the default of 1 GB.
2.3.2 Corporate scenario- Tivoli Continuous Data Protection for Files with Tivoli Storage Manager
The best model for Tivoli Storage Manager with Tivoli Continuous Data Protection for Files is to have Tivoli Storage Manager backup a Tivoli Continuous Data Protection for Files target file server. Tivoli Storage Manager is a sophisticated backup and archive management system that can offer far greater control over versioning, long term retention, and hierarchical storage than Tivoli Continuous Data Protection for Files. We highly recommend that users consider backing up the Tivoli Continuous Data Protection for Files target file server using a traditional Tivoli Storage Manager environment. Using Tivoli Continuous Data Protection for Files for backups to a Tivoli Storage Manager server makes more sense on a file server than on a users workstation. A file server is typically a managed system in an IT shop (versus a user workstation whose uptime and network status are constantly in flux). As such, the connection to the Tivoli Storage Manager server is more dependable. Also, material on a corporate file server typically has a different level of retention and governance needs, so there is value in getting the data into Tivoli Storage Manager in a timely fashion. For such environments, Tivoli Continuous Data Protection for Files plus Tivoli Storage Manager is a valuable combination.
31
Is it necessary (or valuable) to have Tivoli Continuous Data Protection for Files push the data directly to Tivoli Storage Manager rather than simply having Tivoli Storage Manager run on a schedule? Yes, for two reasons. One reason is that Tivoli Continuous Data Protection for Files will never scan the file system looking for files to move because it has its journal list. This is particularly important for very large file systems. The second reason is that using Tivoli Continuous Data Protection for Files allows the administrator to have a separate include list. You might want to configure Tivoli Continuous Data Protection for Files to hourly back up some set of very important files, and let Tivoli Storage Manager back up the remaining system at night.
2.3.3 Corporate scenario- file server as remote storage target for Tivoli Continuous Data Protection for Files workstations
We believe that the typical corporate environment for Tivoli Continuous Data Protection for Files will often look something like this: 20 to 100 users sharing a common file server as their backup target with 50% of those users being highly mobile (notebook users). In this scenario, we recommend configuring the user workstations as discussed in 2.3.1, Overall summary on page 30. In addition we have three suggestions for the configuration of the remote file servers which function as your backup target: Disk pools with backup to tape: On your file server, pick a reasonable pool size per user (2-8 GB) with the intention of holding some number of days/months worth of material (rather than holding all material from a user). Then back that file server up using a traditional backup package (such as Tivoli Storage Manager or something similar) to tape. In this mode, the version count should be set to 1. The remote targets purpose is to allow for rapid restore of user data in the event of machine or disk failure of the workstation, but long term retrieval and retention will be the responsibility of your backup package. Disk pools with no backup: In this mode, the target file server is the long term backup device for all material. Configure the user space to be far more generous (perhaps 50% of their own system) and allow much higher version quantities (20). Since there is no other secondary backup element, more data needs to be present on this system to allow for longer historical recoveries. Disk pools daisy chained: In this mode, data passes through this backup file server and then re-replicates outwards (using Tivoli Continuous Data Protection for Files) to another concentration point (which would in turn be backed up using a traditional backup/tape configuration). This mode is well suited for remote offices where the backup target is essentially a local cache (provides better connection performance connection for the remote office
32
users) and essentially has all day to trickle the data back to a corporate location over a slower WAN link.
2.3.4 Corporate scenario- Tivoli Continuous Data Protection for Files loaded on file server
Tivoli Continuous Data Protection for Files runs just as well on file servers as it does on user endpoints (i.e. locally protecting data on file servers versus protecting data that resides on notebooks and workstations). The primary value of running Tivoli Continuous Data Protection for Files on a file server is that it allows each user to have multiple backup versions of their material locally available on the file server. In such an environment, the local cache for Tivoli Continuous Data Protection for Files should be generously sized (perhaps 25% of the size of the total file space). Should such a deployment use Tivoli Continuous Data Protection for Files to move data off of that file server and onto another backup target? Possibly. If the customer already has a backup strategy for that file server, perhaps nothing else needs to be done. Certainly, the administrator could exploit the fact that Tivoli Continuous Data Protection for Files is present and have this file server (and maybe several others) push their data to another collection point (a backup target) and then back up that target with a traditional mechanism or send data directly to a Tivoli Storage Manager server or Tivoli Storage Manager Express server.
2.3.5 Home user scenario

We recommend that typical home users configure their Tivoli Continuous Data Protection for Files per the 2.3.1, Overall summary on page 30, electing a generous local cache size (perhaps 20% of their disk capacity). Homeowner machines are possibly the most susceptible to damage and theft so it is of paramount importance to have an off-machine target configured in addition to the local repository internal to your machine. USB (or other removable) targets are a fine and affordable choice as this remote target. Additionally, continuous backups to a remote location makes the most sense when the remote target is a locally attached USB drive. This way you have continuous protection to a remote device without generating the corresponding network traffic. Users can also consider deploying an older computer on their home network as a backup target (configured as a file server in simple file serving mode) which relieves the user from having to remember to plug in a disk device. Attach a removable/USB device to that computer, if desired.
33
For additional redundancy consider deploying Tivoli Continuous Data Protection for Files on the backup target and have it push data outward, hopefully out of the house to an ISP target. In such a case, it might be necessary to shorten the include list to only critical file types.
2.4 Tivoli Continuous Data Protection for Files installation requirements

The following section contains information for installing and initially configuring Tivoli Continuous Data Protection for Files.
2.4.1 Basic installation

Basic installation includes a wizard-guided configuration and is suitable for installation on a single local computer. You can also upgrade and uninstall on a single computer.
2.4.2 System requirements

Tivoli Continuous Data Protection for Files requires a Windows server or workstation with specific hardware and software.
Hardware
Minimum hardware is an Intel Pentium III machine with the following specifications: 500 MHz CPU, 384 MB RAM Free disk space 21 MB for install footprint Additional space to store local backup copies Note: You must configure enough space to store at least one backup copy of every file that you protect. See 2.3, Best practices and sizing considerations on page 30. The hardware configuration must also support the Windows operating system, as specified by Microsoft Corporation.
34
Software
The following Windows operating systems are supported: 32-bit Windows 2000 Server, Advanced Server, SP2 and up (x86-32) 32-bit Windows XP Professional, SP1 and up (x86-32) 32-bit Windows 2003 ServerStandard Edition and Enterprise Edition (x86-32) 32-bit Windows Vista Ultimate and Business Edition (x86-32) The Continuous Data Protection for Files user interface supports the following browsers: Internet Explorer, Version 6.0 and higher Mozilla Firefox 1.5.0.7 and higher
35
36
Part 2
Part
Deployment
In this part we discuss deployment of Tivoli Continuous Data Protection for Files, including several case studies that show the features of the products.
37
38
Chapter 3.
Installation and configuration

In this chapter we describe how to install and customize Tivoli Continuous Data Protection for Files on a Windows (2003) system. The instructions given in this chapter are very detailed. By following them, you should be able to successfully install Tivoli Continuous Data Protection for Files and configure it, meeting your or your companys requirements. We also explain additional installation techniques like push installation to another computer and more advanced setup options. The chapter ends with a section about more general but important concepts you need to consider when implementing and maintaining Tivoli Continuous Data Protection for Files. The following topics are discussed in this chapter: Basic installation and configuration on page 40 Advanced installation options on page 64 Advanced configuration on page 75 Additional considerations on page 108
39
3.1 Basic installation and configuration

There are several ways to install Tivoli Continuous Data Protection for Files on a computer. For example interactively, silently, or using a push or pull installation. In this section we describe how to install Tivoli Continuous Data Protection for Files interactively on a single computer. For the other installation methods refer to 3.2, Advanced installation options on page 64. Important: Before installing Tivoli Continuous Data Protection for Files, you have to make sure that your computer meets the necessary hardware and software requirements of Tivoli Continuous Data Protection for Files. Refer to 2.4.2, System requirements on page 34.
3.1.1 Installing Tivoli Continuous Data Protection for Files

To install Tivoli Continuous Data Protection for Files, follow these steps: 1. Insert the product installation CD. Double-click on the Tivoli Continuous Data Protection for Files installer icon. Note: If you do not have the CD and have downloaded the software from the IBM Passport Advantage Web site, just double-click on the Tivoli Continuous Data Protection for Files executable file (ends with .exe) and you will be directed to the screens below. 2. The installer displays the language selection box as shown in Figure 3-1. Accept either the default language of English (United States) or choose your preferred language, and click OK.
Figure 3-1 Installation Setup Language window
40
Note: This selection only specifies the language for the Tivoli Continuous Data Protection for Files installation dialog boxes. The language of the Tivoli Continuous Data Protection for Files menus and messages depends on the language settings of the Internet Browser that you are using. 3. The InstallShield Wizard is prepared before the installation can continue (see Figure 3-2).
Figure 3-2 InstallShield Wizard is being prepared
4. The Tivoli Continuous Data Protection for Files information window displays including the build number, as shown in Figure 3-3 on page 42. Click Next to continue.
Chapter 3. Installation and configuration
41
Figure 3-3 Information window including the build number
5. The License Agreement window will be displayed (see Figure 3-4 on page 43). Read the license agreement carefully. Select the appropriate button if you accept the terms of the agreement, and click Next.
42
Figure 3-4 Software License Agreement options
Note: If you do not accept the license agreement and click Next, a window displays asking you if you really wish to decline the license agreement. If you click Yes, the InstallShield Wizard will be completed and the product will not be installed. Finally, you need to click Finish to exit the wizard. 6. The following window is the Destination Folder window (see Figure 3-5 on page 44). Here you can choose the location where Tivoli Continuous Data Protection for Files will be installed. You can change the default installation directory if you click the Change button and then choose an appropriate folder suiting your requirements, or you can just accept the default installation folder and click Next.
43
Figure 3-5 Destination Folder window
Note: We advise you to use the default Installation location. 7. The Ready to Install the Program window displays (see Figure 3-6 on page 45). Confirm that the information is correct and click Next, or click Back to make the necessary corrections.
44
Figure 3-6 Ready to Install window
8. Tivoli Continuous Data Protection for Files is installed on your computer. The progress of the installation is indicated by the progress bar in the installation window as shown in Figure 3-7 on page 46.
45
Figure 3-7 Installation progress window
Note: During installation, a command prompt window opens as the installer runs several scripts. Do not close or cancel this window. Let the installation run to the end. The installation can take up to several minutes depending on various variables, so in case the progress bar does not move forward for some time be patient and wait until the installation ends. 9. At the end of the installation, the InstallShield Wizard Completed box displays (see Figure 3-8 on page 47). Click Finish to end the InstallShield Wizard.
46
Figure 3-8 Installation completed window
Note: Depending on the installation type of Tivoli Continuous Data Protection for Files, you might have to reboot your computer. A reboot is not necessary When you install Tivoli Continuous Data Protection for Files for the first time on your computer A reboot is necessary When you re-install Tivoli Continuous Data Protection for Files or upgrade to Tivoli Continuous Data Protection for Files from a previous version If a product that uses the IBM Tivoli Storage Manager (Tivoli Storage Manager) API is installed and running on your computer such as the Tivoli Storage Manager Backup-Archive client If a reboot is necessary, a window will be displayed asking you to restart your system. Click Yes to reboot your computer at this time, or click No if you want to reboot at a later time.
47
After the installation is completed, the Initial Configuration Wizard starts automatically. For more details, refer to 3.1.2, Configuration using the Initial Configuration Wizard on page 48.
3.1.2 Configuration using the Initial Configuration Wizard

The Initial Configuration Wizard is new in Tivoli Continuous Data Protection for Files. It guides you through the initial setup of Tivoli Continuous Data Protection for Files. After you have finished the basic configuration settings, Tivoli Continuous Data Protection for Files will immediately be able to protect your files regarding your configuration settings. You can always change the protection settings of Tivoli Continuous Data Protection for Files at a later time as discussed in 3.3, Advanced configuration on page 75. Using the Initial Configuration Wizard, you can: Determine what files need continuous protection Determine where to store your backups Configure e-mail protection Make an initial backup (if desired) Navigation through the Initial Configuration Wizard and the actions you can perform are done using the buttons in the lower left hand corner: Back Next Finish Brings you back to the previous page Takes you forward to the next page Saves your settings (and runs the initial backup if chosen to do so). When finished, the Status page (Figure 3-18 on page 64) will be shown. Cancels the Initial Configuration Wizard and brings you straight to the Status page (Figure 3-18 on page 64) without changing the initial protection settings
Cancel
Note: Not all buttons can be clicked in every page of the Initial Configuration Wizard.
Welcome page
The Welcome page is the first screen of the Initial Configuration Wizard (see Figure 3-9 on page 49). It lists the steps to initially set your protection settings.
48
Figure 3-9 Welcome page
Click Next to get to the What is Critical page.
What is Critical page

Use the What is Critical page (see Figure 3-10 on page 50) to specify the files and folders that you want to protect. The specified files, folders, and applications will be continuously protected, which means Tivoli Continuous Data Protection for Files will create backup copies to a storage area as soon as the files are changed.
49
Figure 3-10 What is Critical page
When Tivoli Continuous Data Protection for Files is installed, it is preconfigured with a list of files and folders to continuously protect. Use this page to confirm that the initial protection settings are correct for your needs, or change the settings as appropriate. The protected files are listed by Folders and Files and by Applications. These lists are not exclusive of one another, but offer two views of what is protected: If you prefer viewing the file paths, names, and extensions that are protected, use the Folders and Files box. This option allows you to use a file tree to specify what to protect. If you prefer viewing the applications that are protected, use the Applications box. This option allows you to specify applications from a list. Files that are created by the listed applications are protected. The file extensions associated with the application will automatically be added to the Folders and Files list.
50
Note: E-mail applications are specified in the E-mail Protection page. Because these files are often very large, their protection settings are configured separately.
Folders and Files box

The Folders and Files dialog box gives a summary of the folders and files that are continuously protected. It contains either the names of protected files and folders, or, in the case of an extensive list, the number of items being protected which refer to the items in the list of folders and files. A single list item can specify more than one file. To view all items in the list and modify the list, click the Details link. The Folders and Files Settings dialog will display.
Folder and Files Settings dialog box

In the Folder and Files Settings dialog box (see Figure 3-11) you specify folders and files to protect by adding or removing items from the list.
Figure 3-11 Folder and Files Settings dialog box (critical files)
The top of the list box has two menu buttons. Click the buttons to include or remove items from the list. Include Click Include to add files and folders that you want to protect. The Select folders dialog (see Figure 3-12 on page 52) will open. Select one or more list items, then click Remove to remove those items.
Remove
51
Each row in the list has one column: Name Patterns in the Name column specify one or more files or folders. See 3.4.2, Interpreting file and folder patterns on page 109 to determine what files and folders will match a Name pattern with blanks or wildcards. When a folder is protected, all of its files and sub-folders are protected.
Select folders dialog box

The Select folders dialog box (see Figure 3-12) allows you to specify files and folders. You can browse to choose a folder, or type the name of a file or folder in the Folder name: text field. If you browse and choose a file or folder, you can modify its path in the Folder name: text field.
Figure 3-12 Select folders dialog box
Note: Only your internal drives can be protected. Any external storage devices are considered remote storage devices.
52
Applications box
The Applications box gives a short list of the applications that are protected. To see the complete list of the applications that are protected, click Details. The Applications and Extensions box will display.
Applications and Extensions box

In the Applications and Extensions box (see Figure 3-13) you specify a list of critical applications to protect.
Figure 3-13 Applications and Extensions box
The Applications and Extensions box presents a list of applications and their associated file extensions. Applications that are checked will be continuously protected. Note: The list of applications shown in the Applications and Extensions box could differ from one computer to another. Tivoli Continuous Data Protection for Files actually checks what applications have been installed on a computer when displaying this list. The list of applications has two views. Each views orders the applications in a different way. Click the menu item at the top of the box to change the view. View By Ranking The applications that have the greatest number of files on your computer are at the top of the list. The applications that have the fewest number files on your computer are at the bottom of the list.
53
View Alphabetically The applications are listed in alphabetical order. You can check and uncheck applications to suit your protection needs: If you check a box, all file extensions associated with that application will be added to the list of protected files. If you uncheck a box, all files with that extension will be removed from the list of protected files. Note that removing file extensions from the list of protected files does not mean adding those files to the list of files that are excluded from protection. Click OK in any of the views to update the list of protected files. Click Cancel to leave the dialog without changing the list of protected files. Important: You can add files to be protected in the Critical Settings dialog, but these applications will be protected only if the files are not excluded. Refer to 3.4.3, Including and excluding files from protection on page 111 for more information.
E-mail Protection page

In the E-mail Protection page (see Figure 3-14 on page 55) of the Initial Configuration Wizard you can select the e-mail application(s) that you want to protect as well as how often you want to protect your e-mail application(s).
54
Figure 3-14 E-mail Protection page
Important: When using e-mail protection, be aware of the following: Because e-mail files typically are very large and frequently change, they are not backed up continuously, but only on the schedule that you select. E-mail files are backed up only to remote storage. If the remote storage is not available at the scheduled backup time, Tivoli Continuous Data Protection for Files will queue the backup copies for later transmission. When the remote storage area becomes available, Tivoli Continuous Data Protection for Files will create the backup copies on the remote storage area. In case your E-mail files get changed multiple times when your remote storage area is temporarily unavailable, only the latest version of these files will be copied over to the remote storage location once it becomes available again.
55
E-mail Application: list

Select one of the popular e-mail applications in the list. If your application is not listed, select Other.
E-mail Application Data Folder: text field

If you choose your e-mail application from the E-mail Application: list, the default file type for that application will appear in this box, and you will not be able to update the file specification. You can update this field only if you select Other in the E-mail Application: list.
How often to protect your e-mail: list

You can schedule e-mail protection at one of several intervals: Never Hourly Daily Weekly Monthly E-mail will not be protected. E-mail files will be backed up every hour, just after the hour. If you choose this interval, choose the time for the backup. If you choose this interval, choose the day and time for the backup. If you choose this interval, choose the day of the month and time for the backup.
Remote Storage page

You can specify the remote storage for the backups of your protected files on the Remote Storage page (see Figure 3-15 on page 57).
56
Figure 3-15 Remote Storage page
Storing files in a remote storage area will protect the files in case local copies are lost. Backups of continuously protected files and files protected on a schedule are stored in the same remote area. Tivoli Continuous Data Protection for Files is very tolerant of intermittently available networks. If remote storage area is temporarily available, Tivoli Continuous Data Protection for Files will queue backup copies until the remote storage becomes available. Attention: If you change the same file multiple times when your remote storage area is temporarily unavailable, only the latest version of this file will be copied over to the remote storage location once it becomes available again.
Back up to: list and Location: text field

Specify the remote storage device where your backup copies will be stored. Specify the type of storage in the Back up to: list and the location of your storage
57
device in the Location: field. What you select from the Back up to: list affects what you enter in the Location: field. You can choose from the following remote backup locations: External Device or File Server WebDAV Server Tivoli Storage Manager or Tivoli Storage Manager Express Server Note: If you choose a WebDAV server or a Tivoli Storage Manager (Express) server as your remote backup destination, Tivoli Continuous Data Protection for Files will prompt you for a valid user name and password to authenticate the Tivoli Continuous Data Protection for Files client with the remote server. For more information refer to 4.2.3, Single computer with ISP connection on page 136.
External Device or File Server

You can specify a file server or removable disk to store the backup copies. The remote device can be another computer (such as a NAS or file server), a remote disk, or a removable disk. In the Location: field, it is recommended that you use Universal Naming Convention (UNC) specification for the file server instead of drive letters when you specify a remote storage area. Drive letters can change after rebooting and often do not reconnect automatically. Note: Using UNC, you can specify the file server either by its computer name or by its IP address. Click the Browse button to view a Browse for folder dialog box. Use this dialog box to navigate to the location for your remote storage area. If this dialog box becomes hidden behind other windows, click on the task bar to bring it to the front. Tip: If you choose a USB external device, you can select the drive letter. However, removable external device drive letters can change. Recommendations and detailed procedures for configuring USB drives as remote storage is described in technical note 1245761 Instructions on how to point Continuous Data Protection for Files to a USB device: http://www-1.ibm.com/support/docview.wss?rs=2339&context=SS3PE6&dc=D B520&q1=1245761&uid=swg21245761&loc=en_US&cs=utf-8&lang=en
58
Tivoli Continuous Data Protection for Files will create backup copies in a sub-folder named \RealTimeBackup\computername. For example, if a computer name is TestComputer, and the remote storage location is configured with the value \\remote\share, backup copies will be stored in \\remote\share\RealTimeBackup\TestComputer\. If you log in to your computer with a user name and password that is also valid on your remote storage location, Tivoli Continuous Data Protection for Files will authenticate transparently into that network location. If you do not log in to your computer with a user name and password that is also valid on your remote storage location, you will need to log in to the network interactively using another account with regular privileges. You can log in interactively by using the Net Use command. Tip: Some versions of Windows have a concept of simplified file sharing, which allows one computer to easily connect to another computer over the network. The resulting connection allows only limited file system capabilities and inhibits the creation of backup copies. Some information, such as access control lists or file streams, can be lost. We recommend that you disable simplified file sharing on the remote storage area.
WebDAV Server
Some Internet Service Providers (ISPs) provide Web-based Distributed Authoring and Versioning (WebDAV). The WebDAV protocol provides the functionality to create, change, and move documents on a remote server. This is useful for authoring the documents which a Web server serves, but can also be used for general Web-based file storage. If your ISP provides WebDAV functionality, Tivoli Continuous Data Protection for Files can store backups on a Web-based server. In the Location: field. enter your WebDAV server location using the following format: https://MyISP.com/MyAcct Note: When using WebDAV, Tivoli Continuous Data Protection for Files only supports the Basic Authentication method described in the HTTP 1.0 RFC. Because this authentication method sends the password as clear text over the network, we recommend that the Web server be configured to use secure sockets.
Tivoli Storage Manager or Tivoli Storage Manager Express Server

In the Location: field, specify the Tivoli Storage Manager server location, using the following format:
59
tsm://Host.com Note: You can use a dotted IP address instead of an IP name for the Tivoli Storage Manager server address. Before Tivoli Continuous Data Protection for Files can connect to the Tivoli Storage Manager server, you need to configure your Tivoli Storage Manager server first by registering your computer where Tivoli Continuous Data Protection for Files is installed as a Tivoli Storage Manager node. Tivoli Continuous Data Protection for Files will use the password assigned at registration to connect to the Tivoli Storage Manager server. For more information about registering a Tivoli Storage Manager node for your computer, see IBM Tivoli Storage Manager for Windows: Administrators Guide, SC32-0121. Important: In order to manage storage space, the Tivoli Storage Manager administrator must grant authority to the Tivoli Storage Manager client node to delete backup copies. For steps to assign authority to delete backup copies, see Node name defined but with wrong permission on page 316. To avoid problems when using Tivoli Storage Manager server, see 5.2.4, Tivoli Storage Manager issues on page 310. You can restore backup copies from Tivoli Storage Manager server only with the Tivoli Continuous Data Protection for Files GUI. You cannot use the Tivoli Storage Manager Backup-Archive client to restore backup copies created by Tivoli Continuous Data Protection for Files.
Maximum space for backups: field

Here you specify how much space to use for all backup copies on remote storage. The default size for the remote storage area is 40 GB. If you increase the number of backup versions to keep, consider increasing your storage area size. If you are unsure of how much space to allocate, you can monitor your space usage on the Status page and adjust the version and space settings accordingly. When the storage space becomes full, Tivoli Continuous Data Protection for Files deletes older backup copy versions of files that have several backup copy versions. After deleting the versioned backup copies, if more space is needed for new backup copies, Tivoli Continuous Data Protection for Files deletes the last remaining backup copies of enough files to make room for the newest backup copy.
60
Tip: If you try to remotely back up a file which is larger than the space you have allocated for your remote storage area, Tivoli Continuous Data Protection for Files will purge all older versions of your files and might fail to back up the file. Make sure that the maximum space for your remote storage area is greater than the maximum file size for remote backup in the Advanced page of the Settings Notebook. For example, if you decrease your maximum space for backups to 1 GB, you should decrease the maximum file size for remote backup from the default of 1 GB.
Initial Backup page

Use the Initial Backup page (see Figure 3-16) to choose if you want to back up all your files when you finish the wizard.
Figure 3-16 Initial Backup page
When you first install Tivoli Continuous Data Protection for Files, we strongly recommend that you immediately back up all files that you configured for protection. Without the initial backup, only files that change will be protected. The initial backup will protect all of the existing files that you designated for protection.
61
Note: The Yes, perform an initial backup of the system option is selected by default. The initial backup will scan all of your local drives, looking for files that you designated for protection. All files that meet your specifications will be backed up to local, remote, or both storage areas. Important: This process can take a long time and can slow down your computer. Start this initial backup when you will not be using your computer for other applications. If you choose not to back up by the installation wizard, you can force a complete backup at a later time. At that time, use the Files to Protect page of the Settings Notebook (see Files to Protect page on page 79).
Summary page
Use the Summary page (see Figure 3-17 on page 63) to view a summary of your configuration choices, and decide if you want to apply your configuration choices to Tivoli Continuous Data Protection for Files.
62
Figure 3-17 Summary page with initial backup
It displays the configuration you specified in the previous pages of the wizard. Choose Back to return to a previous page to modify your configuration choices. Choose Finish to apply your configuration choices. Tivoli Continuous Data Protection for Files will continue to run in the background and protect your files using the configuration choices you made. Choose Cancel to exit the wizard without applying your configuration choices. Tivoli Continuous Data Protection for Files will continue to run in the background and protect your files using the preconfigured settings.
Status page
After the Initial Configuration Wizard has completed, you will see the Status page as shown in Figure 3-18 on page 64.
63
Figure 3-18 Status page
The Status page is the entry to the Tivoli Continuous Data Protection for Files user interface. You can view a summary of how your files are being protected and link to other screens to view details and change protection settings. For more details see 3.3, Advanced configuration on page 75.
3.2 Advanced installation options

In addition to the interactive installation of Tivoli Continuous Data Protection for Files we have described in 3.1.1, Installing Tivoli Continuous Data Protection for Files on page 40, there are also some more advanced installation options available which we discuss in this section. We cover the following advanced installation techniques:
64
Installation using command-line parameters Silent installation Push installation Pull installation (upgrade) Providing a configuration file
3.2.1 Installation using command-line parameters

The installation process of Tivoli Continuous Data Protection for Files can be controlled by adding specific command-line parameters to the Tivoli Continuous Data Protection for Files installation executable. Note: The Tivoli Continuous Data Protection for Files installer is an executable file with a name like TivoliCDP_CDPForFiles_3.1.0.45_windows.exe. The installer name must include CDP and must be file type .exe. The version of the file name (3.1.0.45) can change from one version to the next. A special case of the installation using command-line parameters is the silent installation. See 3.2.2, Silent installation on page 68 for more details about this type of installation.
General syntax
The general syntax is: TivoliCDP_CDPForFiles_3.1.0.45_windows.exe [parameters]
Parameters
The parameters are: /s The /s command-line parameter hides the initialization dialog and causes the setup.exe to run silently. Note: The /s parameter alone does not force a completely silent installation. For more details about silent installation, refer to 3.2.2, Silent installation on page 68. /l Using the /l command-line parameter, you can specify what language to use during setup by using the appropriate decimal language identifier.
65
Example for displaying all installation dialogs in German: TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /l1031 Note: For more information about language identifiers see: http://helpnet.installshield.com/robo/projects/InstallShieldXHelp Lib/IHelpGlobLangIdentifiers.htm Not all language identifiers are currently supported by Tivoli Continuous Data Protection for Files. /v The /v command-line parameter enables you to pass parameters supported by the Windows Installer through setup.exe to the MSI package. Supported parameters are: /qn The /qn command-line parameter causes everything but setup.exe to be silent. Note: The /qn parameter alone does not force a completely silent installation. For more details about silent installation, refer to 3.2.2, Silent installation on page 68. /l*v path and file name The /l*v parameter enables verbose logging. A distinct log file name and location can be specified. Tivoli Continuous Data Protection for Files specific installation options INSTALLDIR=folder The default installation folder is C:\Program Files\Tivoli\CDP_for_Files. If you want to install to another folder, use this option and specify the folder. REBOOT=ReallySuppress Suppress system reboot after installation.
66
Important: This option is recommended when you are pushing an installation to a remote computer (see 3.2.3, Push installation on page 69), because rebooting after installation could be disruptive to users on the remote system. This option is not recommended for a local installation when a previous version of Tivoli Continuous Data Protection for Files exists. All parameters are optional and can be combined together in each way to suit your installation requirements and needs. Important: Command-line options that require a parameter must be specified with no space between the option and its parameter. Example: TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /vINSTALLDIR=C:\newdir is valid, while TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /v INSTALLDIR=C:\newdir is not. Quotation marks around an option's parameter are required only if the parameter contains spaces. If a path within a parameter contains spaces, you might need to use quotation marks within quotation marks, as in the following example: TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /vINSTALLDIR=\C:\new dir\ Note that the inner quotation marks need to be masked using a backslash (\) prior to the quotation mark.
Example using specific options:

TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /l1031 /v/l*v C:\inst.log INSTALLDIR=C:\newdir This command will: Show all installation dialog boxes in German (/l1031) Log installation messages in file inst.log in the root of drive C: (/l*v C:\inst.log)
67
Use the C:\newdir directory as the installation location instead of the default installation directory (INSTALLDIR=C:\newdir)
3.2.2 Silent installation

The silent installation can be considered a special case of the command-line installation (see 3.2.1, Installation using command-line parameters on page 65) using a specific combination of command-line parameters.
General silent installation syntax:

TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /s /v/qn [options]
Options
The following options are allowed: INSTALLDIR=folder The default installation folder is C:\Program Files\Tivoli\CDP_for_Files. If you want to install to another folder, use this option and specify the folder. REBOOT=ReallySuppress Suppress system reboot after installation.

TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /s /v/qn /l*v C:\inst.log INSTALLDIR=C:\newdir REBOOT=ReallySuppress This command will: Do a silent installation (/s /v/qn ...) Log installation messages in file inst.log in the root of drive C: (/l*v C:\inst.log) Use the C:\newdir directory as the installation location instead of the default installation directory (INSTALLDIR=C:\newdir) Suppress a reboot after installation (if this would have been necessary) A special case of silent installation is the push installation (see 3.2.3, Push installation on page 69), because this type of installation copies the necessary installer executable, and configuration file if specified, to a remote computer and starts a silent installation on that system. How push installation works is shown in the following section.
68
3.2.3 Push installation

There are several ways to push initial installation of Tivoli Continuous Data Protection for Files to other computers on your network. Use Microsoft Systems Management Server to install the IBM Tivoli Continuous Data Protection for Files.msi package. Refer to the Microsoft Systems Management Server documentation: http://www.microsoft.com/technet/sms/default.mspx Use IBM Tivoli Provisioning Manager Express for Software Distribution. Refer to IBM Tivoli Provisioning Manager Express for Software Distribution documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc =/com.ibm.itpmesd.doc/toc.xml Place the installer executable on a file server and ask the users to invoke the installer from there at their leisure. Use the Tivoli Continuous Data Protection for Files fpPushInst.exe executable. Using the fpPushInst.exe is discussed here.
fpPushInst.exe (Push Install Command)

The fpPushInst.exe executable pushes a local installer executable to another computer. To be more specific, it pushes the Tivoli Continuous Data Protection for Files installer executable to the \System32\ folder in the Windows installation directory of the remote computer. Note: Typically, the Windows installation directory is C:\Windows. In this case the folder where the Tivoli Continuous Data Protection for Files installer executable would be placed in is the C:\Windows\System32\ folder. The push install executable can be found at the root of the Tivoli Continuous Data Protection for Files installation folder, which is by default C:\Program Files\Tivoli\CDP_for_Files. The fpPushInst.exe executable can also copy a local configuration file fpa.txt to \System32\ in the Windows installation folder on the remote system and then start a service on the remote computer to invoke a silent installation using the specified configuration file fpa.txt (see 3.2.5, Providing a configuration file on page 74 for more information).
69
Note: Due to firewall and other system settings, the fpPushInst.exe executable will not work in some environments.
General push installation syntax

The general push installation syntax is: fpPushInst <\\computer> [/user:user] [/pwd:pwd|*] [/c:filename] /r <command/program [options]>
Parameters
The parameters are: computer The host name of the computer where you want to install Tivoli Continuous Data Protection for Files /user:user and /pwd:pwd An administrative user account and password on the remote computer /c:filename The path and file name of a Tivoli Continuous Data Protection for Files configuration file on the local computer (see 3.2.5, Providing a configuration file on page 74). The fpPushInst.exe executable copies the local configuration file to the \System32\ folder in the Windows installation folder of the remote computer. This parameter is optional. If not specified, the configuration of the remote Tivoli Continuous Data Protection for Files client will be the default configuration. Tip: The Tivoli Continuous Data Protection for Files installer looks for a configuration file named fpa.txt in the \System32\ folder in the Windows installation folder of the remote computer. Tivoli Continuous Data Protection for Files installer will not use a configuration file in that folder with any name other than fpa.txt. So, in most circumstances, the file you specify with this parameter should be named fpa.txt. /r The path and file name of the Tivoli Continuous Data Protection for Files installer file on the local computer. The installer file name must contain the string CDP and end with .exe. For example, a valid path and name is TivoliCDP_CDPForFiles_3.1.0.45_windows.exe.
70
Note: Separate the parameter and the value with a blank space, for example: /r C:\CDP 3.1 Code\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe Valid options are: /s The /s command-line parameter hides the initialization dialog and causes the setup.exe to run silently. /v The /v command-line parameter enables you to pass parameters supported by the Windows Installer through setup.exe to the MSI package. Supported parameters are: /qn The /qn command-line parameter causes everything but setup.exe to be silent. /l*v path and file name The /l*v parameter enables verbose logging. A distinct log file name and location can be specified. The options for a push installation are the following:
DONT_LAUNCH_FILEPATHSRV=1
This option is required for push installation. A pushed installation runs in the system context. It is not recommended that you launch Tivoli Continuous Data Protection for Files in the system context after installation. Running Tivoli Continuous Data Protection for Files in the system context can lead to failures when backing up files, or failures later when a user tries to restore files. Use this option to suppress launching Tivoli Continuous Data Protection for Files in the system context immediately after installation.
REBOOT=ReallySuppress
Suppress system reboot after installation. If users are logged on to the remote system, rebooting can be disruptive.
INSTALLDIR=folder
The default installation folder is C:\Program Files\Tivoli\CDP_for_Files. If you want to install to another folder, use this option and specify the folder. The path corresponds to the remote computer.
71

fpPushInst.exe \\Cairo /user:administrator /pwd:cdp4admin /c:C:\CDP_Files\fpa.txt /r C:\CDP 3.1 Code\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /s /v\/qn REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1\ Important: Note that you need to mask the quotation marks surrounding the options of the /v parameter as shown in the above example by using a backslash (\) prior the quotation mark. Do not use any unintentional spaces in the syntax for the /v parameter as this might cause the fpPushInst.exe command to fail. This command will: Use computer Cairo as the remote destination for the push installation (\\Cairo) Log into Cairo using user administrator and password cdp4admin (/user:administrator /pwd:cdp4admin) Push a configuration file named fpa.txt from local folder C:\CDP_Files to the \System32\ sub-folder of the Windows installation directory on Cairo and use these protection settings during (silent) installation (/c:C:\CDP_Files\fpa.txt) Push the Tivoli Continuous Data Protection for Files installer file to the remote computer (/r C:\CDP 3.1 Code\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe) Starting a service on the remote computer Cairo doing a silent installation (/s /v/qn ...) Not rebooting after installation (REBOOT=ReallySuppress) Not launching Tivoli Continuous Data Protection for Files in the system context immediately after installation (DONT_LAUNCH_FILEPATHSRV=1)
3.2.4 Pull installation (upgrade)

Once Tivoli Continuous Data Protection for Files is installed, you can silently upgrade the product by putting a new installer executable file in the downloads folder (see Administration folders on page 102) of the central administration area (see 3.3.2, Central Administration Settings on page 101). Tivoli Continuous Data Protection for Files will pull the new product code from there and install it silently on the local computer.
72
Note: The new installer file name must contain the uppercase string CDP and must end with .exe. For example, a typical name is TivoliCDP_CDPForFiles_3.1.0.45_windows.exe. Tivoli Continuous Data Protection for Files checks for new installer and configuration files every 10 to 20 minutes. If the date of an installer file is more recent than the file used for the current product level, Tivoli Continuous Data Protection for Files will adopt the new product level. When Tivoli Continuous Data Protection for Files detects a new installer file, a message displays from the system tray indicating that a new version of the software is being installed (see Figure 3-19).
Figure 3-19 Message that a new version is being installed
When the installation is complete, a message displays from the system tray indicating that the new software has been loaded, and you must reboot to resume data protection (see Figure 3-20).
Figure 3-20 Message to reboot system after pull installation
From the time that Tivoli Continuous Data Protection for Files pulls the upgrade until the computer is rebooted, Tivoli Continuous Data Protection for Files stops protecting your files. After the reboot, Tivoli Continuous Data Protection for Files continues protecting your files. Your protection settings are the same as in the previous version of the product.
73
Attention: Until you reboot, Tivoli Continuous Data Protection for Files will not back up any files. You will not lose any existing backup copies, but any changes you make will not be protected. If there is a long delay between install and reboot, consider forcing a backup of all protected files to protect any files that were changed during that time.
3.2.5 Providing a configuration file

When Tivoli Continuous Data Protection for Files is initially installed, the installer can get configuration data from a file named fpa.txt in the \System32\ sub-folder of the Windows installation directory (see Windows installation folder on page 75). If this file does not exist, the installer will install Tivoli Continuous Data Protection for Files with some default configuration settings and start the Initial Configuration Wizard at the end of the installation process for you to make the initial configuration. After the initial installation, Tivoli Continuous Data Protection for Files will pull future configuration settings from configuration files placed in a downloads folder in the central administration area (see 3.3.2, Central Administration Settings on page 101). New configurations will be adopted within 10 to 20 minutes after being placed in the downloads folder. Create a configuration file from an existing client: Configure Tivoli Continuous Data Protection for Files Use the Settings Notebook (see 3.3.1, Settings Notebook on page 76) to configure the client settings you want as the base configuration for other Tivoli Continuous Data Protection for Files clients. Publish the configuration Use the Publish this computers settings ... check box in the Central Administration page of the user interface. A configuration file called fpcommands.xml is created in the global downloads folder in the central administration area. Important: If you will use this file to change a configuration after an initial installation, do not rename the file. Tivoli Continuous Data Protection for Files only pulls configuration data from a file named fpcommands.xml. Depending on if you want to use the just published configuration settings when invoking the installer or use it after an initial installation, some further actions are necessary. These options are detailed here.
74
During initial installation

To use the published configuration settings when invoking the installer, rename the file to fpa.txt and place it in the \System32\ folder in the Windows installation folder of the system where Tivoli Continuous Data Protection for Files is getting installed.
After an initial installation

To use the published configuration settings after an initial installation, place the fpcommands.xml file in the downloads folder of the Tivoli Continuous Data Protection for Files client that is being updated. If you will use the configuration file for a push installation, do not configure a forced backup. Important: If you force a backup on a pushed installation, Tivoli Continuous Data Protection for Files will attempt to back up files in the system context. These backups can fail, and when a user later attempts to restore these files the restore can fail. To avoid a forced backup, do not check the Run Scan Now on other computers check box in the Central Administration Settings window.
Windows installation folder

Tivoli Continuous Data Protection for Files references the Windows installation folder during installation while it is looking for a file named fpa.txt in the \System32\ sub-folder of the Windows installation directory. Note: The Windows installation directory is also known by the environment variable %WINDIR% and as shared drive ADMIN$. Typically, the Windows installation directory is C:\Windows. If the fpa.txt file is present in the \System32\ sub-folder of the Windows installation directory, Tivoli Continuous Data Protection for Files will use these configurations settings (see 3.2.5, Providing a configuration file on page 74). If not, the Initial Configuration Wizard will be started for initial configuration of Tivoli Continuous Data Protection for Files (see 3.1.2, Configuration using the Initial Configuration Wizard on page 48).
3.3 Advanced configuration

When you install Tivoli Continuous Data Protection for Files for the first time, the Initial Configuration Wizard assists you with your initial protection settings.
75
In this section we describe how you can change your protection settings after an initial installation by using the Settings Notebook (see 3.3.1, Settings Notebook on page 76). We also give you an overview of how you can manage multiple Tivoli Continuous Data Protection for Files client systems using the central administration functionality of Tivoli Continuous Data Protection for Files (see 3.3.2, Central Administration Settings on page 101).
3.3.1 Settings Notebook

You can access the Settings Notebook by clicking Settings from the menu of the Tivoli Continuous Data Protection for Files Status page (see Figure 3-18 on page 64). The Settings Notebook consists of the following pages: General page (see General page on page 76) Files to Protect page (see Files to Protect page on page 79) E-mail Protection page (see E-mail Protection page on page 88) Remote Storage page (see Remote Storage page on page 94) Advanced page (see Advanced page on page 99) In the lower left hand corner of the Settings Notebook, you have the following action buttons to control the changes you have made in the Settings Notebook: OK Apply Cancel Applies your new settings and returns to the Tivoli Continuous Data Protection for Files Status page Applies your new settings but stays in the Settings Notebook Exits the Settings Notebook without applying your changes
For more details about the Settings Notebook and how to configure Tivoli Continuous Data Protection for Files in detail, refer to IBM Tivoli Continuous Data Protection for Files 3.1: Installation and Users Guide, GC32-1783.
General page
Use the General page (see Figure 3-21 on page 77) for these settings: Which drive to use for your local storage area How many versions of protected files to keep on local storage area The maximum size of your local storage area
76
Whether or not you want to store backup copies on local storage area, remote storage area, neither, or both
Figure 3-21 General page
Back up to: list

Choose the location where your local backup copies will be stored. Local backup copies will be stored in a folder on one of your local drives. The default configuration is the non-removable local drive which has the most free space. Tivoli Continuous Data Protection for Files will create backup copies in a sub-folder named \RealTimeBackup\. For example, if the local storage area is configured as the C:\ drive, backup copies will be stored in C:\RealTimeBackup\.
77
Note: The drive selected in the Back up to: list specifies the location where the backup copies are stored. The Back up to: list does not specify the files and folders to protect.
How many versions to keep: field

Tivoli Continuous Data Protection for Files can save more than one backup version of each file. When you restore a file, you can choose which version of the file you want to restore. When the configured number of versions is reached, older versions of a file are deleted. Keeping more versions requires more storage space, but allows you more choices when restoring a file.
Maximum space for backups: field

Specify how much space to use for all backup copies on local storage. When the storage area becomes full, older versions of files are deleted until the storage area is at about 80 percent of the configured maximum. If, after deleting all versioned backup copies, local storage space is still insufficient, Tivoli Continuous Data Protection for Files will delete the oldest non-versioned files. The default space for local backups is 500 MB. Important: No warning message displays when the maximum space is reached. During a forced backup of all protected files, Tivoli Continuous Data Protection for Files can use more space than you configured for local storage. The excessive space condition is only temporary. After the forced backup of all files is complete, the first time you change a protected file, Tivoli Continuous Data Protection for Files purges files from the local storage area, if necessary, to meet the space you configured. Tip: If you try to back up a file which is larger than the space you have allocated for your storage area, Tivoli Continuous Data Protection for Files will purge all older versions of your files and then will fail to back up the file. Make sure that the maximum space for your storage areas is greater than the file size limit in the Advanced page of the Settings Notebook.
Continuous protection level: list

Tivoli Continuous Data Protection for Files offers two levels of protection for your files: continuous protection and scheduled protection. Use this list to select which storage areas to use for continuously protected files. None No files will be continuously protected.
78
Local storage only Remote storage only
Tivoli Continuous Data Protection for Files will create backup copies only on the local storage area. Tivoli Continuous Data Protection for Files will create backup copies only on the remote storage area.
Local and remote storage Tivoli Continuous Data Protection for Files will create backup copies on both the local and remote storage areas. This provides the most protection for your files and is the default choice.
Files to Protect page

Use the Files to Protect page (see Figure 3-22 on page 80) for these settings: Which folders and files to continuously protect Which folders to vault Force a backup of all protected files when you change which files are continuously protected
79
Figure 3-22 Files to Protect page
The Files to Protect page is similar to the What is Critical page (see Figure 3-10 on page 50) of the Initial Configuration Wizard. On both pages you select the files and folders that you want to continuously protect, and you can specify the files to protect by Folders and Files and by Applications. In addition to the What is Critical page of the Initial Configuration Wizard, you can specify in the Files to Protect page those folders that you want to vault. You can also force an initial backup of all protected files when you add some files or folders for continuous protection.
Folders and Files box

The Folders and Files box (see Figure 3-23 on page 81) gives a summary of the folders and files that are continuously protected. The number of items protected
80
refers to the items in the list of folders and files. A single list item can specify more than one file.
Figure 3-23 Folders and Files box
Click the Details link to view all items in the list and modify the list. The Folder and Files Settings dialog box will display.
Folder and Files Settings dialog box

Specify which folders and files to continuously protect by specifying those to include and those to exclude (see Figure 3-24).
Figure 3-24 Folder and Files Settings dialog box (include/exclude)
Note: This Folders and Files Settings list is similar to the list displayed in the Initial Configuration Wizard. However, the Initial Configuration Wizard only allows file additions (all of type Include). The Initial Configuration Wizard is designed to get Tivoli Continuous Data Protection for Files started quickly and easily. Any Exclude patterns exclude files from protection as soon as Tivoli Continuous Data Protection for Files is installed, but they are hidden from view during installation. Although the predefined Exclude patterns are recommended for most users, the Exclude patterns are exposed in the Settings Notebook to allow advanced users more robust configuration options.
81
The top of the list box has three menu buttons. Click the buttons to add and remove items from the list. Include Exclude Click Include to add files and folders that you want to continuously protect. The Select folders box will open. Click Exclude to add files and folders that you want to exclude from continuous and scheduled protection. The Select folders box will open. Select a list item, then click Remove to remove that list item.
Remove
Each row in the list has two columns: Name Patterns in the Name column specify one or more files or folders. See 3.4.2, Interpreting file and folder patterns on page 109 to determine what files and folders will match a name pattern with blanks or wildcards. Values in the Type column indicate if the files and folders should be included or excluded from protection. Files and folders of type Exclude will be excluded from continuous and scheduled protection. Files of type Include will be protected.
Type
Important: When a folder is protected, all of its files and sub-folders are protected.
Exclude has precedence over Include, so any file or folder that matches an
Exclude pattern will not be protected, even if the same file or folder matches an Include pattern (see 3.4.3, Including and excluding files from protection on page 111).
Select folders box

The Select folders box (see Figure 3-25 on page 83) allows you to specify files and folders. You can browse to choose a folder, or type the name of a file or folder in the Folder name: text field. If you browse and choose a file or folder, you can modify its path in the Folder name: text field.
82
Figure 3-25 Select folders box
Note: Only your internal drives can be protected. Any external storage devices are considered remote storage devices.
Applications box
The Applications box (see Figure 3-26) gives a short list of the applications that are protected.
Figure 3-26 Applications box
To see the complete list of the applications that are protected, click Details. The Applications and Extensions box will display.
83
Application Settings box

The Applications and Extensions box (see Figure 3-27) has a list of applications and their associated file extensions. Applications that are checked will be continuously protected.
Figure 3-27 Application Settings box (applications viewed by ranking)
Note: The list of applications shown in the Applications and Extensions box can differ from one computer to another. Tivoli Continuous Data Protection for Files actually checks what applications have been installed on a computer when displaying this list. The list of applications has two views. Each view orders the applications in a different way. Click the menu item at the top of the box to change the view. View By Ranking The applications that have the greatest number of files on your computer are at the top of the list. The applications that have the fewest number of files on your computer are at the bottom of the list.
View Alphabetically The applications are listed in alphabetical order. You can check and uncheck applications to suit your protection needs: If you check a box, all file extensions associated with that application will be added to the list of protected files. If you uncheck a box, all files with that extension will be removed from the list of protected files. Note that removing file extensions from the list of protected files does not mean adding those files to the list of files that are excluded from protection.
84
Click OK in any of the views to update the list of protected files. Click Cancel to leave the box without changing the list of protected files.
Vault box
The Vault box (see Figure 3-28) displays a summary of vaulted folders.
Figure 3-28 Vault box
To change the folders that are protected, click Details. The Vault Settings box displays.
Vault Settings box

The Vault Settings box (see Figure 3-29) displays a list of folders. All files in these folders and all sub-folders will be protected from being changed or deleted.
Figure 3-29 Vault Settings box
Vaulted folders cannot be modified nor deleted. Files can be added to the folder, but the files in the folder cannot be changed nor deleted. Vault Unvault Click Vault to open a browser to choose the folder(s) to protect. Click Unvault to remove vault protection from the selected folder and all its files and sub-folders.
85
Important: Neither the Exclude nor Include items from other dialog boxes affect the list of vaulted folders. All folders in the Vault Settings box, and only the folders in the Vault Settings box, will be vaulted. Click the OK button to add your changes to the pending settings updates. Note: The configured settings will not be applied until you click the Settings Notebook OK or Apply button Click the Cancel button to exit the box without applying changes. For more information about how to specify a vaulting duration, see 3.4.4, Vault duration on page 114
Back up with new settings check box

Use the Back up with new settings check box (see Figure 3-30) to scan all drives and back up all files that are configured for protection.
Figure 3-30 Back up with new settings check box
If you changed the specifications for Folders and Files or Applications to include files that were not previously protected, we strongly recommend that you back up those files now. Check the box to scan and protect all files when you click the Settings Notebook OK or Apply button. Note: During a forced backup of all protected files, Tivoli Continuous Data Protection for Files can use more space than you configured for local storage. The excessive space condition is only temporary. After the forced backup of all files is complete, the first time you change a protected file, Tivoli Continuous Data Protection for Files purges files from the local storage area, if necessary, to meet the space you configured. A backup is not necessary to activate vault protection. If you changed Vault settings, the folders become vaulted when you click the Settings Notebook OK or Apply button. Changing the Vault settings does not require a forced backup.
86
Tip: Occasions in which you should consider backing up all files: When you first install Tivoli Continuous Data Protection for Files, we strongly recommend that you immediately back up all files that you configured for protection. Without the initial backup, only files that change will be protected. The initial backup will protect all of the existing files that you designated for protection. After the initial backup, the typical rate of file changes does not require that you again back up all files at once. If you change the specifications for Folders and Files or Applications to include files that were not previously protected, the new files need to be backed up. If you extend protection to new e-mail files or other files that are included in scheduled backups, the new files need to be backed up. Until you change these files, and without a forced backup, Tivoli Continuous Data Protection for Files will not back up these files. To protect these files, you must force a backup of all files. If you dont change your configuration but suddenly make a significant change to the files that are configured for protection, you should also force a backup of all files. Consider this if you add a new drive whose files are configured for protection. When you should not backup all files: When you push an installation of Tivoli Continuous Data Protection for Files to a remote computer and do not reboot. If you force a backup on a pushed installation without rebooting, Tivoli Continuous Data Protection for Files will attempt to back up files in the system context. These backups can fail, and when a logged on user later attempts to restore these files the restore can fail. If you are creating a configuration file for a push installation, do not check this box. After this scan and backup is complete, Tivoli Continuous Data Protection for Files will continue to operate in the background without any significant impact on your regular computing activities.
87
Important: A forced backup causes Tivoli Continuous Data Protection for Files to scan all local drives looking for files that you designated for protection This means that all files that meet the include, exclude, and size criteria will be copied to the local, remote, or both storage areas. The creation of backup copies could take several hours. It will also take significant processing resources. Plan the backup at a time when you do not need computing resources for other activities.

Use the E-mail Protection page (see Figure 3-31 on page 89) for these settings: What e-mail application, if any, to protect including the schedule frequency to protect your e-mail: Never Hourly Daily Weekly Monthly What files are backed up on a schedule, which tasks are run: Choose which files to back up on a schedule Start a backup of your scheduled files immediately View reports of your scheduled backups
88
Figure 3-31 E-mail Protection page
E-mail Application: list

Tivoli Continuous Data Protection for Files has predefined protection settings for the following e-mail applications: Lotus Notes Microsoft Outlook Associated suffixes: *.id and *.nsf Associated suffix: *.pst
Microsoft Outlook Express 5.5, 6 Associated suffixes: *.mbx and *.dbx In the E-mail Application list you can select one of the given e-mail applications (Lotus Notes, Microsoft Outlook, Microsoft Outlook Express 5.5, 6), none of them (Select Applications), all together (All), or Other if you are using another e-mail application (see Figure 3-32 on page 90).
89
Figure 3-32 E-mail Application: list
E-mail Application Data Folder: text field

If you choose your e-mail application from the E-mail Application list, the default file type for that application will display in the E-mail Application Data Folder box, and you will not be able to update the file specification. You can update this field only if you select Other in the E-mail Application list. In case you have selected Other, enter in the E-mail Application Data Folder text field the suffix(es) your e-mail application is using, for example *.mail (see Figure 3-33).
Figure 3-33 E-mail Application Data Folder: text field
Note: For backing up large e-mail application files which exceed the specified maximum file size threshold for sub-file copies (see Use sub-file copy for files larger than: field on page 99), Tivoli Continuous Data Protection for Files is using a bitmap backup mechanism, which means only the changed blocks of a file are sent to the remote backup target. The versioned bitmap backups of a file which have been backed up using the bitmap backup mechanism, have a -TPdelta file name suffix.
How often to protect your e-mail: list

You can schedule e-mail protection at one of several intervals: Never Hourly Daily E-mail will not be protected. E-mail files will be backed up every hour, just after the hour. If you choose this interval, choose the time for the backup.
90
Weekly Monthly
If you choose this interval, choose the day and time for the backup. If you choose this interval, choose the day of the month and time for the backup.
Scheduled Backup Settings link

Click the Scheduled Backup Settings link to open the Folders and Files Settings box (see Figure 3-34) for scheduled backup.
Folder and Files Settings box

In the Folder and Files Settings box you specify folders and files to back up on the same schedule as e-mail files are backed up.
Figure 3-34 Folder and Files Settings box (schedules)
Start scheduled backup now check box

The folders and files that you specify will be backed up on the same schedule as your e-mail backups. If you want to force a backup now, check the Start scheduled backup now box and click the OK button.
91
Note: Considerations for scheduled backups Files that are appropriate to protect on a schedule Large or frequently saved files can consume considerable computing or network resources when they are backed up. You can scheduled periodic backups of these files when the burden on computing or network resources will be least inconvenient. Some files are not often closed and saved, but should be backed up periodically. Files protected by schedule will be backed up even if they are open, but you can try to schedule the backup for a time when the file will be closed. The files you select for scheduled protection will be backed up only at the scheduled time and only if they change during the scheduled interval. This can yield fewer backup versions than continuously protected files. Fewer backup versions use less storage space, but offer fewer opportunities when you want to restore a file. Closing applications before a scheduled backup Tivoli Continuous Data Protection for Files backs up all files that have changed during the schedule interval, including files that are still open at the time of backup. The backup copies of files that are backed up while open can be corrupted. So, we recommend that you close applications before a scheduled backup. Tivoli Continuous Data Protection for Files offers an opportunity to close applications before a scheduled backup. At the beginning of a scheduled backup, Tivoli Continuous Data Protection for Files attempts to close all files that are listed in a text file called closeapps.txt in the installation directory. Each line in the file must be a program name, with name and extension, but no folder path. Tivoli Continuous Data Protection for Files sends a close command to each instance of every program named in the closeapps.txt file. Note that Tivoli Continuous Data Protection for Files will not send a start command to any of those programs when the scheduled backup is finished.
View Report link

Click the View Report link to open a table of scheduled backup reports for all computers that share a common central administration folder. For more information about central administration see 3.3.2, Central Administration Settings on page 101.
Scheduled backup reports table

Use the reports table (see Figure 3-35 on page 93) to monitor scheduled backups to remote storage areas.
92
Figure 3-35 Scheduled backup reports table
The scheduled backup reports table gives a summary of scheduled backups to remote storage areas for all computers who share a common central administration folder. To see the reports table, you must be connected to your remote storage area. Each row identifies the reports associated with one Tivoli Continuous Data Protection for Files client and contains the following cells: Version Last Backup Files The version of Tivoli Continuous Data Protection for Files The last completed scheduled backup A number indicating approximately how many files were successfully backed up at the last schedule. Due to the nature of the program and how the logging is done, this number is only an approximation. Click the number to
93
display a complete report of the scheduled backup. In addition to files backed up, the report shows administrative activities and failed backup attempts. Failures This column indicates how many errors there were during the backup. Click the number to display a report of the errors during scheduled backup. Click the link to display a list of the historical backup and failure logs. Once this list is displayed, you are able to click on logs to display more information. Only reports which had actual files backed up will show as active links.
History
Remote Storage page

Use the Remote Storage page (see Figure 3-36 on page 95) for these settings: Your remote storage area How many versions of protected files to keep on remote storage area The maximum size of your remote storage area Whether or not to encrypt, compress, or use sub-file copy for backup copies stored on remote storage area
94
Figure 3-36 Remote Storage page
Storing files in a remote storage area will protect the files in case local copies are lost. Backups of continuously protected files and files protected on a schedule are stored in the same remote area. Tivoli Continuous Data Protection for Files is tolerant of intermittently available networks. If a remote storage area is temporarily available, Tivoli Continuous Data Protection for Files will queue backup copies until the remote storage becomes available. Attention: If you change the same file multiple times when your remote storage area is temporarily unavailable, only the latest version of this file will be copied over to the remote storage location once it becomes available again.
95
Advanced Settings
You can specify the following advanced settings for your backups going to a remote storage location: Encrypt your backups Compress your backups Activate sub-file backups Note: Encryption and compression are mutually exclusive: you can specify either one or the other, but not both at the same time. Encryption and compression can both be combined with sub-file backups.
Encrypt backups button

Set encryption for remote backup copies. Tip: To enable encryption for your remote backup copies, press the Encrypt backups button. If you want to disable encryption, press this button again. The encryption feature provides extra security on your remote location. This can be useful if multiple users have access to the remote server location, and you need to ensure that each users data is protected from other users, or anyone else who has access to the remote server. When you click the button labeled Encrypt backups, at the next backup process Tivoli Continuous Data Protection for Files will display a box so that you can create a password for the encrypted files (see 4.3.3, Small business with a file server on page 167). This password will be required to view or access any files which are backed up by Tivoli Continuous Data Protection for Files. The encrypted password is kept either in the data directory (new installation) or in the installation directory (upgrade installation from Tivoli Continuous Data Protection for Files V2.x). If the files in this directory are lost, you will be prompted to enter a new password. Note: Once encryption has been enabled, the password is stored. If you disable encryption, then enable it again, you will not be prompted for a new password. General things to know about encryption: Files stored on the local storage area are not encrypted.
96
Files that are compressed using the compression option of Tivoli Continuous Data Protection for Files, cannot be encrypted, and the user interface will not allow you to configure both encryption and compression. Files that use sub-file copy can be encrypted. Important: The Tivoli Storage Manager API also has the ability to encrypt files when backing them up to a Tivoli Storage Manager server. This capability is transparent to the Tivoli Continuous Data Protection for Files client making it possible, but not recommended, to enable encryption with both applications. In case you want to use Tivoli Storage Manager API encryption instead of letting Tivoli Continuous Data Protection for Files encrypt the files, you need to be aware that Tivoli Continuous Data Protection for Files does not support prompted encryption. So, if you specify a Tivoli Storage Manager server as your remote storage area, you must configure non-prompted encryption in the Tivoli Storage Manager API client dsm.opt options file. In the dsm.opt file, use the statement: encryptkey save See 3.4.1, Installation and data directories on page 108 to learn where the dsm.opt file can be found on your computer. For more information about setting encryption options in the Tivoli Storage Manager dsm.opt file, refer to Chapter 9, Using processing options, in IBM Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and Users Guide, SC32-0146. Important: Tivoli Continuous Data Protection for Files cannot protect backup copies that it has encrypted. This is an issue only if you store backup copies on a file server and then protect the files on the file server. If you configure Tivoli Continuous Data Protection for Files to encrypt the backup copies to a file server, you must not use Tivoli Continuous Data Protection for Files to protect the encrypted backup copies on that file server. You can use Tivoli Storage Manager or another backup solution to protect the encrypted backup copies on that file server.
Compress backups button

Set compression for remote backup copies. Tip: To enable compression for your remote backup copies, click the Compress backups button. If you want to disable compression, click this button again Use compression to save space on your remote storage location. The compression feature is not compatible with the encryption feature. You can use
97
compression or encryption, but not both simultaneously. Files backed up using the compression function must be restored using Tivoli Continuous Data Protection for Files. Important: Tivoli Continuous Data Protection for Files is using a LZW compression algorithm. This can result in files actually getting larger in size when they are stored on the remote target location, if those files have already been stored locally in a compressed (or pseudo-compressed) format, such as ZIP, AVI, or MP3 files. If you enable both compression and sub-file copy, sub-file copy has precedence. This means that a file which has a size larger than the minimum for sub-file copy will not be compressed, since it is subject to sub-file copy activity. Only files smaller than the minimum size for sub-file copy will be compressed. Note: If a file has been compressed by Tivoli Continuous Data Protection for Files, an additional suffix .cdp will be added to the original name of the file name, for example the local file name compressed_file.txt will become compressed_file.txt.cdp on the remote storage location.
Use sub-file copy check box

Check the box to turn on sub-file copy for remote backup copies. Initially, an entire file is copied to the storage area. When sub-file copy is turned on, and when the file changes, only the changed information is copied to the storage area. The sub-file copies are saved as separate files on the remote storage. Attention: Currently Tivoli Continuous Data Protection for Files does not support sub-file backups to a Tivoli Storage Manager server and a Microsoft Internet Information Services (IIS) Server as the remote backup destination even though you can check the sub-file backup option. Sub-file copy can significantly reduce the amount of network traffic. However, sub-file copy consumes more processing resources on your computer. The default setting is to use sub-file copy for files larger than 50 MB. If you need to conserve more network resources, you can reduce the size setting so sub-file copy will be used on even smaller files. Note: The sub-file copies of a file which has been backed up using the sub-file backup option, have a -FPdelta file name suffix.
98
Use sub-file copy for files larger than: field

In the Use sub-file copy for files larger than: field, specify the file size threshold for using sub-file copy. For files larger than this size, only the changed information is copied to the storage area. Note: Activating sub-file copy and specifying the file size threshold for using sub-file copy does affect the way e-mail files will be backed up by Tivoli Continuous Data Protection for Files (see E-mail Application Data Folder: text field on page 90 for more information).
Advanced page
Use the Advanced page (see Figure 3-37 on page 100) for these settings: Whether to allow program messages to pop up Performance settings, including the following: Maximum size file to protect on local storage area Maximum size file to protect on remote storage area Maximum speed for transfer to remote storage area Contains a link to set your scheduled backups (see Figure 3-31 on page 89)
99
Figure 3-37 Advanced page
Allow program messages to pop up: list

For certain types of activities or notifications, Tivoli Continuous Data Protection for Files opens messages from the icon in the system tray. To prevent the messages from opening, select Disabled. Attention: If messaging is disabled, important program messages regarding the failure of Tivoli Continuous Data Protection for Files operations will be suppressed, which could lead to loss of data.
Performance Settings
In the Performance settings area you can specify how Tivoli Continuous Data Protection for Files handles large files (locally and remotely) and restrict the transfer rate when backing up to the remote storage destination:
100
Do not locally back up files larger than: field Limit the size of files that are backed up to your local storage area. If you try to back up a file which is larger than the space you have allocated for your storage area, Tivoli Continuous Data Protection for Files will purge all older versions of your files, and then will fail to back up the file. Make sure that the file size limit in this field and the size limit for files backed up to remote storage is less than the maximum space for your storage areas. Do not remotely back up files larger than: field Limit the size of files that are backed up to your remote storage area. Maximum remote transfer rate: field You can set a limit on the volume of data that Tivoli Continuous Data Protection for Files transfers to remote storage. Consider limiting the transfer rate if you need to ease the burden on your network.
3.3.2 Central Administration Settings

Tivoli Continuous Data Protection for Files has features that allow an administrator to manage the configuration of other Tivoli Continuous Data Protection for Files clients. You can manage the installed product level and configuration of other Tivoli Continuous Data Protection for Files clients and monitor their (schedule) activity reports. Note: The central management feature is only available with the PC Edition and Server Edition of Tivoli Continuous Data Protection for Files. The following tasks can be managed using central administration: Pulling of new product level (pull installation) and configuration settings Once Tivoli Continuous Data Protection for Files is installed, you can update the product level and configuration by putting the installer and configuration file in the appropriate downloads folder for the consuming clients (see 3.2.4, Pull installation (upgrade) on page 72). Central sharing of configuration data and monitoring of (schedule) activity reports You can configure the downloads and reports folders of the managed clients and the central administration folder of the managing client. You must configure each so that so that the managed clients consume the configuration and information exported by the managing client. The same configuration allows the managing client to view the activity reports of the managed clients. You can change the administration folder of the managing client to communicate with different groups of managed clients.
101
For the latter one, refer to the examples given in Chapter 7, Central Management Considerations, in IBM Tivoli Continuous Data Protection for Files 3.1: Installation and Users Guide, GC32-1783. Pushing an installation of Tivoli Continuous Data Protection for Files to other computers (push installation) Tivoli Continuous Data Protection for Files includes an executable that will push an installation of the product to other computers. You can also push a specific configuration file at the time of the installation (see 3.2.3, Push installation on page 69). Before we explain the concept of central administration and its settings, you need to understand what kind of administration folders Tivoli Continuous Data Protection for Files has and what they are needed for.
Administration folders
Tivoli Continuous Data Protection for Files uses special folders to manage configuration settings and product level. Tivoli Continuous Data Protection for Files clients pull configuration information and new product code from these folders. They also store their status reports in these folders and can push their own configuration information to these folders for other clients to consume. The folder for central administration is specified in the Central Administration Folder field in the Central Administration Settings window (see Figure 3-38 on page 104): If the Central Administration Folder: field is not configured, then the central administration folder defaults to the \RealTimeBackup\ folder in the remote storage area. If neither the Central Administration Folder: field nor a remote storage area is configured, then there is no central administration folder. Note: There is no central administration folder on Tivoli Storage Manager server remote storage. If you define a Tivoli Storage Manager server as your remote backup location and you want to use central administration folders, you must configure the Central Administration Folder: field in the Central Administration Settings window. The central administration folder contains two levels of administrative sub-folders: Group administrative sub-folders These folders apply to all computers that share this central administration folder.
102
Computer-specific sub-folders These folders apply to only one computer. In each level of administrative sub-folders, there are two folders: The Reports folder Tivoli Continuous Data Protection for Files stores status reports in the Reports folder. You can view the reports using the user interface of Tivoli Continuous Data Protection for Files. The full path is <central administration folder>\BackupAdmin\Reports\.
The Downloads folder When you put product upgrades or configuration files in this folder, Tivoli Continuous Data Protection for Files will automatically adopt the product upgrades or configuration. For more information about this process, see 3.2.4, Pull installation (upgrade) on page 72. The full path is <central administration folder>\BackupAdmin\Downloads\. Note: For pulling product upgrades or configuration files from the central administration area, the managed Tivoli Continuous Data Protection for Files clients must have read access to the administration folders.
Central Administration Settings window

You can open the Central Administration Settings window (see Figure 3-38 on page 104) by clicking Central Administration from the menu of the Tivoli Continuous Data Protection for Files Status page (see Figure 3-18 on page 64). The Central Administration Settings window allows you to: Identify administration folders for this computer. Manage the configuration settings on other computers.
103
Figure 3-38 Central Administration Settings window
Central Administration Folder: field

Type or browse for a folder that will be the central administration folder for this computer. The administrative tasks on the Central Administration Settings window are limited to only those computers that are centrally managed from this folder. Note: If you type the name of a folder that does not exist, Tivoli Continuous Data Protection for Files will create the folder. The central administration folder is used for several purposes. You can change the folder depending on your purpose (see Administration folders on page 102).
104
Publish this computers settings ... check box

When managing Tivoli Continuous Data Protection for Files on a group of computers, it is customary to configure one computer as the template for all computers in the group. If you have configured other computers to share the central administration folder of this computer, they can be centrally managed by this computer. Check this box to use this computers settings to configure the other computers. When you click the OK button, this computers configuration settings file will be copied to the downloads sub-folder of the central administration folder that is shared by the group of computers (see Figure 3-39). All computers that share the central administration folder will adopt the Tivoli Continuous Data Protection for Files configuration that you publish.
Figure 3-39 Successfully published fpcommands.xml pop-up window
If you publish this computers settings, your management of the group can be further extended: Lock the configuration of other computers check box Check this box to prevent any of the centrally managed computers from changing their settings. Note: If you will use the published configuration file to push installation to another computer, all Tivoli Continuous Data Protection for Files clients that share the central administration folder with the new client will be prevented from updating their configurations. Run Scan Now on other computers check box When you change a configuration to protect files and folders that were not previously protected, you should back up all files (see Back up with new settings check box on page 86 for considerations when backing up all files). Check this box to force the centrally managed computers to back up all protected files.
105
Note: Publishing to managed computers a configuration file with this setting can put a large burden on the network and the computing resources of the managed computers. If you will use the published configuration file to push installation to another computer, do not check this box. If you use this configuration setting in a push install, the push-installed Tivoli Continuous Data Protection for Files client will create backup copies in the system context. When you later run Tivoli Continuous Data Protection for Files in the user context, you can have problems restoring these files.
View Report link

Click the View Report link to display a table of scheduled backup reports for the computers that are centrally managed. A new browser window opens with the scheduled backup reports table (see Figure 3-40 on page 107).
Scheduled backup reports table

Use the reports table to monitor scheduled backups to remote storage areas.
106
The scheduled backup reports table gives a summary of scheduled backups to remote storage areas for all computers that share a common central administration folder. For more information on central administration folders, refer to Administration folders on page 102. Note: To see the reports table, you must be connected to your remote storage area. Each row identifies the reports associated with one Tivoli Continuous Data Protection for Files client, and contains the following cells: Version Last Backup The version of Tivoli Continuous Data Protection for Files. The last completed scheduled backup.
107
Files
This column indicates approximately how many files were successfully backed up at the last schedule. Due to the nature of the program and how the logging is done, this number is only an approximation. Click the number to display a complete report of the scheduled backup. In addition to files backed up, the report shows administrative activities and failed backup attempts. This column indicates how many errors there were during the backup. Click the number to display a report of the errors during scheduled backup. Click the link to display a list of the historical backup and failure logs. Once this list is displayed, you are able to click on logs to display more information. Only reports which had actual files backed up will show as active links.
Failures
History
3.4 Additional considerations

The following section lists several important concepts for consideration when implementing and maintaining Tivoli Continuous Data Protection for Files.
3.4.1 Installation and data directories

Depending on the operating system and type of installation - new versus upgrade installation - the path of the installation directory and the data directory might differ from one computer to another. The Tivoli Continuous Data Protection for Files program files will be installed in the installation directory you specify during your initial installation (see 3.1.1, Installing Tivoli Continuous Data Protection for Files on page 40). If you are upgrading an older version of Tivoli Continuous Data Protection for Files, the installation directory of this version will be used to place the program files of Tivoli Continuous Data Protection for Files. If you are installing Tivoli Continuous Data Protection for Files for the first time, the configuration file (fpa.txt), the Tivoli Storage Manager client options file (dsm.opt), the log files as well as some other important files will be stored in a special data directory. In case you are upgrading to Tivoli Continuous Data Protection for Files from a prior version, these files will be placed in the installation directory of the previous Tivoli Continuous Data Protection for Files version.
108
Table 3-1 shows an overview of the used directories depending on the operating system and type of installation.
Table 3-1 Default installation and data directories Installation directory Windows XP, 2003 new installation Windows XP, 2003 upgrade installation MS Vista new installation C:\Program Files\Tivoli\CDP_for_Files\ C:\Program Files\Tivoli\CDP_for_Files\ C:\Program Files\Tivoli\CDP_for_Files\ Data directory (fpa.txt, dsm.opt, log files, and so on.) C:\Documents and Settings\All Users\Application Data\Tivoli\CDP_for_Files\ C:\Program Files\Tivoli\CDP_for_Files\ C:\ProgramData\Tivoli\CDP_for _Files\
a
a. By default, the \Application Data\ is a hidden folder.
If you need to see the files in the data directory, this might not be possible at first, because this folder is hidden by the operating system by default. To allow hidden folders and files to be displayed by the operating system, follow these steps: 1. Select Start Run, type explorer, and click OK. This opens the Windows Explorer. 2. Click Tools, and select Folder Options... . 3. Click the View tab to show the current folder settings. 4. In the Advanced settings area click the Show hidden files and folders radio button. 5. Click OK to close the Folder Options window. 6. To exit the Windows Explorer, click File and select Close.
3.4.2 Interpreting file and folder patterns

Protection settings use patterns to specify what files and folders to protect. The files and folders that are protected depend on blanks before and after a pattern and asterisks in the pattern. You can enter the complete path of a file that you want to protect. For example, C:\Documents and Settings\Administrator\My Documents\testfile.doc. The complete path unambiguously matches a single file. But to specify all files this way would be time consuming. Use asterisks and blanks as wildcards in the pattern to specify several files.
109
Tip: An asterisk matches any number of characters in a file path. If there are no asterisks, then Tivoli Continuous Data Protection for Files will match any file whose fully expanded path name has that exact pattern anywhere in the path or filename. If there are no asterisks in the pattern, then blank spaces before and after the pattern are interpreted as asterisks. So, \myDocs\ and *\myDocs\* yield the same matches. If there are asterisks in the pattern, then blank spaces before or after the pattern match no characters. So, \myDir\, *\myDir\, and \myDir\* could yield three different matches (see examples in Table 3-2). As an example, assume a pattern fish. This pattern matches: C:\dir\fish.doc and C:\fish\testfile.doc and C:\fishfood\something. If the pattern has slashes around it (\fish\), it will match any object with \fish\ somewhere in the path. This pattern matches for example C:\FisH\testfile.doc but not C:\dir\fish.doc and not C:\fishfood\something. Note: The pattern is not case-sensitive.
Table 3-2 File and folder pattern matches This pattern ... \myDir\ or \mYdiR\ or *\myDir\* or *\mydir\* ... matches these folders and files on your computer: C:\myDir\ C:\myDir\Contacts\ C:\myDir\Contacts\contacts.txt C:\Projects\myDir\ C:\Projects\myDir\myThings\ C:\Projects\myDir\myThings\things.doc C:\Projects\myDir\myThings\myPhoto.jpg D:\Notes\myDir\ C:\myDir\ C:\Projects\myDir\ D:\Notes\myDir\
*\myDir\
\myDir\* d:*\mydir\* D:\Notes\myDir\
110
This pattern ... \my best
... matches these folders and files on your computer: C:\Books\My Best.doc C:\Photos.jpg\My Best Photo\ C:\Photos.jpg\My Best Photo\Best.jpg F:\Projects\My Best Project\ F:\Projects\My Best Project\Dream.xls C:\Photos.jpg\ C:\Photos.jpg\myHouse.bmp C:\Photos.jpg\My Best Photo\Best.jpg C:\Projects\myDir\myThings\myPhoto.jpg C:\Photos.jpg\ C:\Photos.jpg\My Best Photo\Best.jpg C:\Projects\myDir\myThings\myPhoto.jpg All files and folders on the E: drive.
.jpg
*.jpg
E:\ or E:\*
3.4.3 Including and excluding files from protection

Protected files are specified by including files and by excluding files.
Continuous and scheduled protection (not vaulted)

Tivoli Continuous Data Protection for Files keeps a list of files that are included for protection and a list of files that are explicitly excluded from protection. The list of included files is separated into those that are included for continuous protection and those that are included for scheduled protection. The list of excluded files applies to both continuous and scheduled protection. A file is on the include list if it is defined in the Folders and Files list by a pattern with type Include. Similarly, a file is on the exclude list if it is defined by a pattern with type Exclude. It is possible that a file can be on both the include list and the exclude list.
111
Attention: To avoid situations where you think you protect a file or folder but indeed you do not (or vice versa), be aware of how include and exclude lists work in Tivoli Continuous Data Protection for Files: If a file (or folder) is on the exclude list, it will not be protected, neither by continuous protection nor by scheduled protection. Even if the file (or folder) is also on an include list, it will not be protected. If a file is on an include list and not on the exclude list, it will be protected. If a file is not on an include list, it will not be protected. The table below (see Table 3-3) summarizes the interaction of inclusion and exclusion. The two left columns indicate if a file is included or excluded, and the right column indicates if the inclusion and exclusion yield protection for the file.
Table 3-3 Interaction of inclusion and exclusion File is specified on Include list No No Yes Yes File is specified on Exclude list No Yes No Yes Is file protected? No No Yes No
Note: Locations where files and folders can be added (and removed) from include and exclude list: You add items to the include list in several places where settings are configured. You add items to the exclude list in only one place: the Folder and Files Settings box of the Files to Protect page of the Settings Notebook.
112
Figure 3-41 Folder and Files Settings box (example include/exclude settings)
Note: Tivoli Continuous Data Protection for Files provides a default list of files and folders to be included and excluded. This list excludes from protection various Windows operating system files, the Program Files folder, and temporary files. These exclusions are recommended. For example, the list above includes only \My Documents\ and excludes only *.test. The result is that any files with .test file extension in \My Documents\ folder will not be protected. All other files in \My Documents\ folder and its sub-folders will be protected. For another example, using the same list above, if you choose an application in the Application Settings box that typically creates files with extension .test, those .test files will not be protected. Attention: Be very careful when excluding items. Because the patterns in your list can match more than one folder or file, be careful that you do not exclude some files by mistake. See 3.4.2, Interpreting file and folder patterns on page 109 for an explanation of how patterns match file and folder names. For example, consider a small variation to an excluded pattern: \Temp\. If you used instead \temp (without the closing folder delimiter), this would have a very different effect. Even though this might seem like a small change, it has a potentially large impact. All files which have \temple, \temptation\, \temperature\, \template\, and other variations of \temp*, would be excluded from protection.
113
Consider another example. You choose to exclude *.gif so you can avoid backing up files saved by your browser when you open different Web sites. This pattern will also exclude all .gif files in \My Pictures\ folder.
Vaulted folders
Vaulted folders, and the files in them, are not affected by the exclude list, nor by the lists of files that are specified for continuous or scheduled protection. All files that you select in the Vault settings box of the Files to protect page of the Settings Notebook will be vaulted.
3.4.4 Vault duration

You can specify the duration of vaulting by using special folder names. Files in these folders will be vaulted for a specific period of time and after that time the files will not be vaulted. To specify duration of vaulting, create a folder named \KeepSafe\ in any vaulted area. In the \KeepSafe\ folder, create folders that indicate the vaulting period. For example, C:\CDP_Vault\KeepSafe\Retain 3 years\. Any file created in that folder will be prevented from alteration or deletion for three years. After the expiration time, the file is no longer vaulted. There are three ways to indicate the vaulting period. Each way requires that you use a keyword in the folder name. \KeepSafe\RetainForever\ Files in this folder will be vaulted forever. Such material can never be moved to another folder with shorter vaulting duration. Material can be moved within the folder tree and to other folders of the same duration. \KeepSafe\Retain Duration\ Specify exact vaulting periods using English terminology. Duration is specified by a combination of the following time units: Years Days Hours Minutes Seconds Use one or more time units. Each time unit you use must be preceded by a number up to five digits long. You may include spaces, underlines, or dashes and mix case in the folder name. The following are valid examples: \Retain23days4hours\ \Retain 3years\
114
\Retain_3years\ \Retain-23DAYS_4minutes\ \Retain 1000 days\ \KeepSafe\RetainUntil Date\ Specify a date after which the vaulting will expire. The date must include year, month, and day in the following format: yyyymmddhhmmss. The hours, minutes, and seconds are optional. The default time is 00:00:00. Note: yyyy The year is specified using a 4 digit format, example: 2019 mm The month is specified using a 2 digit format, example: 01 for January dd The day is specified using a 2 digit format, example: 17 for the 17th day of the month Optional: hh The hour is specified using the 2 digit 24h format, example: 15 for 3am mm The minutes are specified using a 2 digit format, example: 30 for 30 minutes after the hour ss The seconds are specified using a 2 digit format, example: 45 for 45 seconds after the minute The following are valid examples: \RetainUntil20190117153045\ \RetainUntil 20200101\ \RetainUntil20200101\ \RetainUntil_20200101\
115
Note: You cannot create a \Retain... folder within a vaulted \Retain... folder. You cannot move material that is in one vaulted \Retain... folder to a vaulted \Retain... folder that has an earlier expiration date.
3.4.5 Default protection settings (Settings Notebook)

In case you have made some modifications to your Tivoli Continuous Data Protection for Files protection settings and want to revert back to the default settings, you need to know what those default settings are. This section lists the default Tivoli Continuous Data Protection for Files protection settings - separately outlined for each page of the Settings Notebook.
General page
In Table 3-4 you can see the default settings for the general protection settings of Tivoli Continuous Data Protection for Files.
Table 3-4 General page default settings General page Back up to How many versions to keep Maximum space for backups Continuous protection level
aC:\
20 500 MB Local and remote storage
a. Tivoli Continuous Data Protection for Files chooses by default the non-removable local drive which has the most free space. If you have more than one non-removable local drive in your computer, a drive name other than C: might be chosen.
Files to Protect page

Table 3-5 on page 117 shows the default values for the files you want to protect.
116
Table 3-5 Files to Protect page default settings Files to Protect page Folders and Files Include \My Documents\ *.doc *.xls *.ppt *.123 Exclude RealTimeBackup \Program Files \System32\ ~ *.tmp *.temp \Temp\ \Temporary \Windows\ \System Volume \tsmlvsacache \cache \Tivoli\CDP_for_Files\ Applications Vault Start an initial backup with the new settings No applications 0 folders left unchecked

The default values for your e-mail protection and your schedules are in Table 3-6 on page 118.
117
Table 3-6 E-mail Protection page default settings E-mail Protection page E-mail Application E-mail Application Data Folder (wildcards allowed) How often to protect your e-mail Scheduled Backup Settings Select Application (nothing preselected) nothing predefined Never nothing predefined
Remote Storage page

In Table 3-7 you can see the default remote storage settings of Tivoli Continuous Data Protection for Files
Table 3-7 Remote Storage page default settings Remote Storage page Back up to Location How many versions to keep Maximum space for backups Advanced Settings Encrypt backups Compress backups Use sub-file copy Use sub-file copy for files larger than None Selected nothing predefined 5 40 GB not preselected not preselected left unchecked 50 MB
Advanced page
Table 3-8 shows the default advanced protection settings of Tivoli Continuous Data Protection for Files.
Table 3-8 Advanced page default settings Advanced page Allow program messages to pop up Performance Settings Do not locally back up files larger than Enabled 10 GB
118
Advanced page Do not remotely back up files larger than Maximum remote transfer rate Scheduled Backup Settings 1 GB 1 Gbs nothing predefined
119
120
Chapter 4.
Proof of concept scenarios

In this chapter we cover several different usage scenarios for Tivoli Continuous Data Protection for Files. These scenarios attempt to provide you with an understanding of the various configurations and implementations possible with Tivoli Continuous Data Protection for Files. Use these scenarios as guidance for your planning and deployment strategy, and remember proper planning will help ensure successful implementation. This chapter covers the following: Product features on page 122 Single user environment on page 123 Multiple computers in a home or small business on page 145 Tivoli Continuous Data Protection for Files in an enterprise environment on page 180 Restore scenarios on page 228
121
4.1 Product features

The previous chapters have described various aspects of Tivoli Continuous Data Protection for Files functionality, however, not all functionality is supported in every usage scenario. Use the matrix below to determine what functionality is supported in an environmental context. Table 4-1 shows the Tivoli Continuous Data Protection for Files feature support matrix:
Table 4-1 Tivoli Continuous Data Protection V3.1 feature support matrix CDP Feature Encryption Compression Vault Sub-file copy Management area Local Disk Remote Disk (external disk / file server) Supported Supported Not supported Supported Supported WebDAV (Apache) APAR opened APAR opened Not supported Supported Supported WebDAV (IIS 5.0/6.0) APAR opened APAR opened Not supported Full backups Supported Tivoli Storage Manager Supported Supported Not supported Full backups Must specify
Not supported Not supported Supported Not supported N/A
Note: Compression and encryption features are mutually exclusive. It is not possible to use both together. The compression feature in Tivoli Continuous Data Protection for Files can not be used in conjunction with Tivoli Storage Manager compression. If the compression is enabled in Tivoli Storage Manager do not set this variable within Tivoli Continuous Data Protection for Files. If you have encryption enabled within Tivoli Storage Manager, note that Tivoli Continuous Data Protection for Files works only Tivoli Storage Managers AES128 encryption option. If you are using Tivoli Storage Manager as your remote backup target you need to specify a management area on a central Tivoli Continuous Data Protection for Files server if you wish to take advantage of Tivoli Continuous Data Protection for Files central management functions, such as backup reports and push installations.
122
4.2 Single user environment

Below we describe typical scenarios for home and mobile users. In this scenario we have three primary target locations for our copied data: Local disk only External storage (direct attached USB drive) Web server (in conjunction with a qualified ISP)
4.2.1 Single computer, local disk only

In this environment, we use Tivoli Continuous Data Protection for Files to backup our most important data to local disk.
CDP
Continuous protection to local disk
Amsterdam
Windows Vista User desktop
Active daemon identifyng the modified files Replicates the files in a local directory
Figure 4-1 Single computer, local disk only
In our lab environment we have a machine called Amsterdam. The environment has the following characteristics: Desktop computer Intel Pentium 4 CPU 2.40 GHz 512 MB memory Windows Microsoft Vista Ultimate 5 GB for backup files Continuous protection of the directory \Example Data\ The following screens will walk you through the configuration described above:
Chapter 4. Proof of concept scenarios
123
Figure 4-2 General Configuration for a single user with local disk configuration
Figure 4-2 shows which variables need to be configured when we have only the local disk and the C:\ drive partition available in this desktop. We are going to keep two versions of our protected files and the maximum space that we will use for backups will be 5 GB.
124
Figure 4-3 Files to protect in a single user with local disk configuration
Figure 4-3, shows which files we have selected to protect. We are only protecting the \Example Data\ directory. During the initial replication, Tivoli Continuous Data Protection for Files will create a directory called RealTimeBackup on the drive specified in General tab configuration. In our scenario the drive C:\ was specified.
125
Figure 4-4 Continuous protection file directory
Figure 4-4 shows the data that exists in C:\RealTimeBackup\ directory. Note that Tivoli Continuous Data Protection for Files mirrors our source directory tree inside the target \RealTimeBackup\ directory. Based on the specifications of our configuration you will see two versions of each file in our target directory.
4.2.2 Single computer with external storage

In this environment we have configured continuous data protection for backups of our most important files to a local drive and scheduled protection for backups of less important (or constantly changing) files to an external drive. In our lab environment we have the same machine from the above scenario, Amsterdam, and we added a direct attached USB drive as the target for our files under scheduled protection.
126
11 10 9 8 7
12
Schedule protection to remote storage

1 2 3 4 5
CDP
3 1 2
Continuous protection to local disk
USB Amsterdam
Windows Vista User desktop
Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list Replicates the files in a local directory At schedule time verifies the journal list and replicates the pending files in an external disk
Figure 4-5 Single computer, with external storage
The environment has the following characteristics: Desktop computer Intel Pentium 4 CPU 2.40 GHz 512 MB memory Windows Microsoft Vista Ultimate 5 GB local disk for continuously protected files 100 GB external (USB) disk for scheduled protection of files The directories \Example Data\ and \My Documents\ will be under continuous protection The directories \Example Data\ and all pdf and txt files will have the scheduled protection using the compression feature This scenario is very similar to what we discussed previously, but with the added external disk as the target storage area for our scheduled protection. The following screens will walk you through the configuration described above.
127
Figure 4-6 General configuration for a single user scenario with external disk
Figure 4-6 shows the necessary configuration for continuous protection of files. This is the same configuration that we have in section 4.2.1, Single computer, local disk only on page 123.
128
Figure 4-7 Selection of important files to continuously protect in a single user scenario with external disk
Figure 4-7 shows that the \My Documents\ directory was added to our selection of continuously protected files.
129
Figure 4-8 Configuring the remote storage for scheduled protection
Figure 4-8 shows the necessary configuration for the remote storage in this scenario. We intend to use 100 GB on the target device and to maintain two versions of each file. We enabled the Compress backups option to save space on the external disk. The directory E:\RealTimeBackup\ will be created on the external USB device. Note: When you configure your removable storage device make sure that you select it by using the Browse option next to the Location field on the Remote Storage page. There is currently an issue with the software that allows some removable devices to show up in the General backup list. You should not select the removable device from the General pick list.
130
Figure 4-9 Configuring files for scheduled protection
Figure 4-9 shows how to configure files for scheduled protection. It is necessary to configure a separate list of files to include in the scheduled protection settings. Select the E-mail Protection tab and then click the Schedule Backup Settings link. Include all extensions and directories that you want to protect with the scheduled option in the Folders and File Settings window (shown above). Note: Tivoli Continuous Data Protection for Files keeps a list of files that are included for protection and a list of files that are excluded from protection. The list of included files is separated into those that are included for continuous protection and those that are included for scheduled protection. The list of excluded files applies to both continuous and scheduled protection.
131
Figure 4-10 Configure the frequency and time to start the scheduled protection
Figure 4-10 shows that the scheduled backup will run daily, and the process will start at 07:00 PM. Note: The best time to configure scheduled protection is when the machine is not in use and all applications are closed. After the configuration is complete, you can start an initial backup by selecting the Start scheduled backup now check box. If you do not use this option, files changed under scheduled protection will be replicated when the next scheduled interval occurs.
132
Figure 4-11 Start an initial backup
Figure 4-11 shows how to start an initial backup of files under either continuous or scheduled protection. We recommend that you use this option when you are not using your computer. The first scan takes some time to run, depending on the size of your files and network traffic.
Compression
Another way to save space on your remote location is to enable the file compression feature within Tivoli Continuous Data Protection for Files. If you configure Tivoli Continuous Data Protection for Files to use compression, you must use it to restore compressed files. Note: If you intend to back up a significant number of files that have already been compressed or are of a compressed format, Tivoli Continuous Data Protection for Files compression might not be advisable.
133
After the initial scan, you can check to see if the files are compressed on the external storage device. The following pictures compare the original directory with the replicated directory:
Figure 4-12 Original directory and files
Figure 4-12 shows the original directory and files. The selected file presentation1.ppt is 739 KB in size. Compare this file with the replicated directory.
134
Figure 4-13 Replicated directory and files
Figure 4-13 shows the replicated directory and files. The selected replicated file presentation1 is 697 KB in size. As you can see, the file was compressed. For files that already have a compressed format, like avi, mp3, zip, etc., enabling compression might actually result in the files growing in size. This is illustrated with file avi1.avi in the screen above. The original file is 276,806 KB and the replicated file is 276,807 KB. At this point you are probably wondering why Tivoli Continuous Data Protection for Files does not just back up the file uncompressed when it realizes the compressed file is going to be bigger than the source file. It is because the compression feature was added to save bandwidth on the LAN. By the time Tivoli Continuous Data Protection for Files realizes the file is getting bigger while being compressed, most of the file has already been sent to the backup directory. If you are sending the file to a backup server over the LAN, it is
135
better for bandwidth to send the rest of the compressed file instead of restarting the backup and sending the entire file uncompressed.
4.2.3 Single computer with ISP connection

This scenario represents a user who has a single computer (a mobile computer) that has access to external storage through an ISP. For this user, all files are saved on local machines, and the remote storage on the ISP server is used primarily for occasional backups. The local backup repository still provides the primary method of protection. Note: If the storage space you have available through your ISP is limited, you might want to narrow the inclusion list for the schedule backup to save space. In our lab environment, we have two machines, one called paris and another called madrid. Paris is the WebDAV server and Madrid is the mobile computer with Tivoli Continuous Data Protection for Files installed.
Broadband
11 12 1 2 3 8 7 6 5 4
3
11 10 9 8 7 6 5 12 1 2 3 4
10 9
3 1
CDP
2 Paris
Windows 2003 HTTP Server 6.1
Windows XP Mobile Computer
Madrid
Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list Replicates the files in local and remote storage at the same time At schedule time verifies the journal list and replicates the pending files to an ISP provider
Figure 4-14 Single computer, with ISP connection
The environment has the following configuration: Paris:
136
Desktop computer Intel Pentium 4 CPU 2.40 GHz 512 MB memory Microsoft Windows Server 2003 IBM HTTP Server V6.1 Madrid Mobile computer Intel Pentium Dual Core 2.16 Ghz 1 GB memory Windows XP Service Pack 2 Continuous protection to local and remote drive Scheduled protection to Tivoli Storage Manager Important files for continuous protection ExampleData for scheduled protection 2 versions and 5 GB for continuous protection 5 versions and 10 GB for scheduled protection Sub-files for files greater than 3 MB
137
Figure 4-15 Continuous protection for a single computer with ISP connection
Figure 4-15 shows the configuration for continuous protection for a single computer with an ISP based storage repository. When any file in ImportantFiles directory has changed, it will replicate to local disk and to the ISP provider. Note: An internet connection to your remote storage device must be available for continuous replication of files that change. If a connection to the remote device is not available Tivoli Continuous Data Protection for Files will not be able to replicate copies of files as they change, and changed files are not cached for later transport. When the remote target becomes available Tivoli Continuous Data Protection for Files will transmit the current version of a protected file to the remote location. Versions of files that changed when the remote target was not available are no longer available to copy to the remote storage location, because these interim files are not cached by Tivoli Continuous Data Protection for Files.
138
Figure 4-16 Important files continuous protection in a single user with an ISP connection
Figure 4-16 shows that the ImportantFiles directory was added to the continuous protection.
139
Figure 4-17 Remote storage with ISP configuration
Figure 4-17 shows how to configure Tivoli Continuous Data Protection for Files when you have an ISP provider providing remote storage. In our lab environment we have a machine called Paris that has the HTTP Server V6.1 and the directory secure_backupvault with rights to receive the replicated files. All files that are bigger than 3 MB will use the sub-file copy feature that sends only the changed blocks of a file, as opposed to the entire file, to the remote storage location (reducing network traffic). After you apply your changes a window asking for user ID and password to access the Web server displays. See Figure 4-18 on page 141.
140
Figure 4-18 Username and password to access Web server
Note: There are various options on the market today for ISP-provided remote storage. Some service providers (e.g. Cable or DSL) will make disk space available (either as part of the base service or as a paid upgrade) for their users. Ideally the space provided is file server-type space which can be mounted by the operating system. If the target storage is web-server/ftp space, ask your service provider if they support WebDAV which allows Web servers to expose their storage space as file-server space. The ISP might offer a VPN (virtual private network) style connection or simply a SSL interface (and WebDAV can run over SSL transparently). As for securing the data on the back-end at the ISP, consult with your ISP provider to learn what they offer for on-disk security
141
Figure 4-19 Configure the frequency and time to start the scheduled protection to an ISP provider
142
Figure 4-20 Files for scheduled protection
Figure 4-20 shows the files configured for scheduled protection. Each hour Tivoli Continuous Data Protection for Files will scan the directory ExampleData to verify whether any files have changed since the last backup. All files that have changed since scheduled protection was configured will be replicated at the scheduled interval time.
Figure 4-21 Activity report for changed files
As an example, the files in Example Data directory docu1.doc, pres1.ppt, and sheet1.xls were modified. Figure 4-21 shows that all changed files were replicated to both local and remote storage.
143
Figure 4-22 Activity report for changed file pres1.ppt
To test how versioning in remote storage works, the file pres1.ppt was modified. This file was changed six times. Figure 4-22 shows that the last version was purged in the remote storage.
Sub-file copy and versioning

If you configure Tivoli Continuous Data Protection for Files to use sub-file copy, it will create files that contain each files delta information in your designated storage area. Those files have an FPdelta file name suffix. To test the sub-file copy functionality the file Sub-file example.txt was modified. This file is larger than 3 MB. Figure 4-23 on page 145 shows the replicated directory in our HTTP Server Paris. As you can see, we have the original file with 3,208 KB and a delta file with only the modified characters which is only 1 KB. Note that this feature is supported only with remote storage. To track versions of a file, Tivoli Continuous Data Protection for Files adds a version suffix to the file name of the backup copy. On remote storage, all backup copies contain a version suffix. When a file is deleted on your computer, Tivoli Continuous Data Protection for Files will add a version identifier to the file name of the most recent backup copy on the remote storage. The most recent backup copy of a file is the active backup copy. Older backup copies of that file are inactive backup copies. Tivoli Continuous Data Protection for Files will delete inactive backup copies of a file first if the storage space limit is reached.
144
A file that is protected by schedule could change several times during the schedule interval. Only the last version of the file prior to the end of the schedule will be backed up. A continuously protected file is backed up after every change.
Figure 4-23 Sub-file functionality example
To test how versioning in remote storage works, the file pres1.ppt was modified. This file was changed six times. Figure 4-22 on page 144 shows that the last version was purged in the remote storage.
4.3 Multiple computers in a home or small business

In this scenario there are multiple computers connected through a single network. You can have a supplemental file server or a backup application to protect the copied data. Tivoli Continuous Data Protection for Files will be configured in three different ways: Home network with a file server Small business without file server Small business with a file server
145
4.3.1 Home network with a file server

This scenario represents a small home environment, a single network with several computers. Typically this configuration will involve two to ten machines. Tivoli Continuous Data Protection for Files will replicate the data to a target file server. In this example the user will copy the replicated data to DVD. Only the scheduled protection will be used. See the lab environment illustrated below:
11 10 9 8 7
12
1 2 3 4 5
LAN
11 10 9 8 7
12
1 2 3 4 5 10 9 8
11
12
1 2 3 4 5 10 9 8
11
12
1 2 3 4 5 10 9 8
11
12
1 2 3 4 5
2
CDP CDP
2
CDP
CDP
1 1
Cairo
Windows 2003 Pentium 4 1,5 GB memory User desktop
Dakar
Amsterdam
Windows Vista Pentium 4 1 GB memory User desktop
Madrid
Windows XP Intel Dual Core 1 GB memory Mobile computer
External Drive
DVD Disks Berlin

Windows 2003 Pentium 4 1,5 GB memory File Server
Active daemon identifying the modified files: - Scheduled protection sends to journal list At schedule time verifies the journal list and replicates the pending files to the file server Backs up files on file server to the DVD Disks
2 3
Figure 4-24 Home network with a file server
The computers Cairo, Dakar, Amsterdam, and Madrid are configured to send the backup files to Berlin. Each computer needs to have appropriate access to the target file server to back up their files. Tivoli Continuous Data Protection for Files is installed on each machine. Below is the base configuration of Tivoli Continuous Data Protection for Files in this scenario: Scheduled protection to the file server 10 GB and 2 versions for scheduled protection ExampleData directory for scheduled protection Frequency for scheduled protection = Daily
146
Figure 4-25 General configuration without continuous protection
Figure 4-25 shows the configuration to disable continuous protection. The General page is configured with the following settings: Backup to: (leave default, not used in this scenario) How many versions to keep: (leave default, not used in this scenario) Maximum space for backups: (leave default, not used in this scenario) Continuous protection level: None (to disable continuous protection) Before configuring the remote storage in Tivoli Continuous Data Protection for Files, you need to map a drive on each users computer to the target file server. The shared directory cdp_fileserver is already configured on Berlin server. See Figure 4-26 on page 148.
147
Figure 4-26 Map network drive in each computer
We configured our file server to require a user name and password. See Figure 4-27.
Figure 4-27 Configure user and password to access the file server
148
Figure 4-28 Configure remote storage for scheduled protection
Figure 4-28 shows the Remote Storage page configuration for this scenario. The configuration is: Backup to: File Server (Berlin server) Location: \\berlin\cdp_fileserver How many versions to keep: 1 Maximum space for backup: 3 GB (the maximum space for backups for each machine needs to be enough to maintain at least one version for each file designated for scheduled protection)
149
Note: When the storage space becomes full, Tivoli Continuous Data Protection for Files deletes older backup copy versions of files that have several backup copy versions. After deleting the versioned backup copies, if more space is needed for new backup copies, Tivoli Continuous Data Protection for Files deletes the last remaining backup copies of enough files to make room for the newest backup copy. No warning message displays when the maximum space is reached.
Figure 4-29 Configure schedule and select application for scheduled protection
150
Figure 4-30 Select files for scheduled protection
Figure 4-29 on page 150 and Figure 4-30 show the frequency, directories, and files for schedule protection. In the E-mail protection tab, select Schedule backup settings, select Include, browse to select the directory, and click OK to save your changes. Each day after the scheduled backup has finished, you can back up the RealTimeBackup directory on the file server to DVD (or another media of your choice).
4.3.2 Small business with Tivoli Storage Manager Express

This scenario represents a small business environment of 10 to 25 desktop computers in a single network. The customer doesnt want to invest money in a file server as a target for backup copies, but the customer needs to back up the users data due to legal requirements. In this case, Tivoli Continuous Data Protection for Files is configured to send the continuous and scheduled backups directly to a Tivoli Storage Manager Express server. Note: IBM Tivoli Storage Manager Express is designed for small business environments with five to twenty servers. Typically, these businesses do not have the resources for a dedicated storage administrator, but nevertheless they must have reliable backups and restores. An illustration of our lab environment:
151
11 10
12
1 2 3
LAN
3
11 10 9 8 7 6 5 4 12 1 2 3 10 9 8 7 6 5 4 11 12 1 2 3
9 8 7 6 5 4
3
11 10 9 8 7 6 5 4 12 1 2
3
11 3 10 9 8 7 6 5 4 12 1 2
3
3
CDP
CDP
CDP
CDP
Cairo
Dakar
Amsterdam
Izmir
Windows XP Pentium 4 512 GB memory User desktop
Tape Library Berlin

Windows 2003 Pentium 4 1,5 GB memory Tivoli Storage Manager Express
Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list
2 3 4
Replicates the files in a local disk At schedule time verifies the journal list and replicates the pending files to Tivoli Storage Manager Express Saves files in tapes for long-term copies
Figure 4-31 Small business without file server
In this configuration, all computers have two lists of files to protect, one for continuous protection and another for scheduled protection. They are configured as follows: Continuous protection to local drive Scheduled protection to Tivoli Storage Manager Express 2 GB and 2 versions for continuous protection ImportantFiles directory for continuous protection ExampleData directory for scheduled protection 10 GB and 10 versions for scheduled protection Frequency for scheduled protection = Daily at 7 PM Before configuring Tivoli Continuous Data Protection for Files, it is necessary to configure Tivoli Storage Manager Express.
152
Tivoli Storage Manager Express configuration

The Tivoli Storage Manager Express server is installed and configured on the Berlin server. It is not necessary to install the backup/archive client, Tivoli Continuous Data Protection for Files will use the API (application program interface) to send files to Tivoli Storage Manager Express. The default dsm.opt is located on the C:\Documents and Settings\All Users\Application Data\Tivoli\CDP_for_Files\ directory. You must register the machines where Tivoli Continuous Data Protection for Files resides with the Tivoli Storage Manager Express server. On the Tivoli Storage Manager Express server Berlin, do the following: 1. On Tivoli Storage Manager Express server go to: Start Tivoli Storage Manager Backup Server Administration. 2. Input user name and password: Administrator / cdp4admin 3. Select the Computers and applications option as shown in Figure 4-32.
Figure 4-32 Computers and applications option on Tivoli Storage Manager Express
153
4. On left panel, Select Action Add Computers .... The following wizard displays:
Figure 4-33 Wizard to add computers and optionally deploy the backup client software
5. Select General and the option Add computer, but not deploy the client software, as shown in Figure 4-34 on page 155.
154
Figure 4-34 Select option to add a computer
To add a computer/node: Computer name: Node name of client where Tivoli Continuous Data Protection for Files is loaded Contact information: Administrator responsible for machine Web address for the backup client Web interface: The IP address for server and port number to access the node through Web Computer owners e-mail address: To send notification about schedule information
155
Figure 4-35 Installation settings
6. Confirm settings, and finish the task.
156
Figure 4-36 Confirm settings
7. Open an MS DOS prompt to configure backup delete permission on Tivoli Storage Manager Express. 8. Stop the Tivoli Storage Manager Express service, as shown below. C:\Program Files\Tivoli\TSM\server>net stop "TSM Express Backup Server" The TSM Express Backup Server service is stopping. The TSM Express Backup Server service was stopped successfully.
Figure 4-37 Stop Tivoli Storage Manager Express service
9. Start Tivoli Storage Manager Express in foreground mode, as follows.
157
C:\Program Files\Tivoli\TSM\server>dsmserv ANR0900I Processing options file C:\Program Files\Tivoli\TSM\Server1 \dsmserv.opt. ANR7800I DSMSERV generated at 02:27:45 on Mar 9 2006. Tivoli Storage Manager Express for Windows Version 5, Release 3, Level 7.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2006. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 100 megabytes. ANR0201I Database assigned capacity is 2000 megabytes. ANR0306I Recovery log volume mount in progress. ANR0285I Database page shadowing started using file dbpgshdw.bdt. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID,bb.b9.d8.b0.02.3a.11.dc.ac.9a.00.0c .29.eb.67.de, has initialized. ANR2100I Activity log process has started. ANR0993I Server initialization complete.
Figure 4-38 Start Tivoli Storage Manager Express in foreground mode
10.Configure delete permission. TSM:TSM-DEMO> update node dakar backdel=yes ANR2017I Administrator SERVER_CONSOLE issued command: UPDATE NODE dakar backdel=yes
Figure 4-39 Configure node with delete permission
11.Stop Tivoli Storage Manager Express in the foreground mode.
158
TSM:TSM-DEMO> halt ANR0991I Server shutdown complete.

Figure 4-40 Shutdown Tivoli Storage Manager Express
12.Start Tivoli Storage Manager Express service. C:\Program Files\Tivoli\TSM\server>net start "TSM Express Backup Server" he TSM Express Backup Server service is starting. he TSM Express Backup Server service was started successfully.
Figure 4-41 Start Tivoli Storage Manager Express
13.Log in on Tivoli Storage Manager Express again, select Computers and applications. Select the Dakar client node and reset the password, as shown in Figure 4-42.
Figure 4-42 Reset the password
159
Note: The first time that you connect the client node to the Tivoli Storage Manager Express server you need to reset the password. 14.Input the user name and password, as in Figure 4-43.
Figure 4-43 Windows credentials
15.Note the new password (Figure 4-44).
Figure 4-44 New password information
Tivoli Continuous Data Protection for Files and Tivoli Storage Manager Express
Now, lets configure Tivoli Continuous Data Protection for Files to work with Tivoli Storage Manager Express.
160
Figure 4-45 General configuration
Figure 4-45 shows the general configuration for this scenario: Backup to: C:\ (local disk only) How many versions to keep: 2 (two versions of each file with continuous protection) Maximum space for backups: 2 GB (maximum space allocated for continuous protection) Continuous protection level: Local storage only (continuous protection is enabled only for local disk)
161
Figure 4-46 Files to protect in continuous protection
Figure 4-46 shows the files selected for continuous protection. In this scenario, all machines have the ImportantFiles directory, and all files that require continuous protection should be located in this directory. To create your include list of files and directories, click the Details link next to Folders and Files. A new window, Folders and Files Settings, displays. Click Include and fill in the folder name or extensions to add to continuous protection.
162
Figure 4-47 Remote storage configuration for Tivoli Storage Manager Express
Figure 4-47 shows the configuration to send files to Tivoli Storage Manager Express: Backup to: Tivoli Storage Manager Location: tsm://berlin\ (hostname or IP address of the Tivoli Storage Manager Express Server) How many versions to keep: 10 different versions of each file Maximum space for backups: 10 GB (maximum space for backups on Tivoli Storage Manager Express Server) You will be prompted to input the user name and password for this node when connecting to Tivoli Storage Manager Express, see Figure 4-48 on page 164.
163
Figure 4-48 Node password on Tivoli Storage Manager Express server
164
Figure 4-49 Select applications, files, and frequency to back up to Tivoli Storage Manager Express
165
Figure 4-50 Create the include list for scheduled protection
Figure 4-49 on page 165 and Figure 4-50 show the frequency, directories, and files for schedule protection. All files that are being changed during the day in the ExampleData directory will be backed up to Tivoli Storage Manager Express every day at 7 PM.
Backup policy
Tivoli Continuous Data Protection for Files sends files to Tivoli Storage Manager Express with appended text which creates unique file names, even when the object is a new version of a file that has already been backed up. These newer versions of an existing file will be seen by Tivoli Storage Manager Express server as new files, will be categorized as active backup versions, and will never be marked as inactive. The backup policy is controlled and enforced by Tivoli Continuous Data Protection for Files. So, when a file is purged it will be marked on Tivoli Storage Manager Express as an expired object, allowing it to be removed from the Tivoli Storage Manager Express storage pool. Note that you cannot see each backup file in your Tivoli Storage Manager Express server; you can simply verify if a filespace called cdpfs exists. See Figure 4-51 on page 167.
166
Figure 4-51 Filespace on Tivoli Storage Manager Express
4.3.3 Small business with a file server

This scenario represents a small business environment (user desktops and application servers). Consider this scenario for 25 to 100 computers. In this case each client machine uses Tivoli Continuous Data Protection for Files to replicate data to a target file server. You can then back up the files from the file server to a backup server. For a small business, Tivoli Storage Manager Express is recommended. An illustration of our lab environment:
167
11 10 9 8 7
12
1 2 3 4 5
LAN
3
11 10 9 8 7 6 5 4 12 1 2 3 10 9 8 4 7 6 5 11 12 1 2 3 10 9 8 4 7 6 5
3
11 12 1 2
3
11 10 3 9 8 4 7 6 5 12 1 2
3
3
3 2 2 4
TSM Client
2
CDP
2
CDP
2
CDP
CDP
Tokyo
Dakar
Amsterdam
Rome
Athens
Windows 2003 Pentium 4 1,5 GB memory File Server
Berlin
Windows 2003 Pentium 4 1 GB memory TSM Server Express
2 3 4
Replicates the files in remote storage At schedule time verifies the journal list and replicates the pending files to an ISP provider At schedule time backs up the files to TSM Server Express
Figure 4-52 Small business with a file server
Our file server in this environment is Athens. The backup will be sent to the Tivoli Storage Manager Server Express, Berlin. The lab environment: Continuous and scheduled protection to file server 15 GB and 2 versions for each file ImportantFiles directory for continuous protection ExampleData directory for scheduled protection Frequency for scheduled protection = Daily Encryption Before configuring the Tivoli Continuous Data Protection for Files, it is necessary to configure the file server with the appropriate privileges and map the file server to each users computer. To reconnect to the file server each time that the machine is rebooted, use the option in Windows Explorer: Tools Map a network drive. See Figure 4-53 on page 169 and Figure 4-54 on page 169.
168
Figure 4-53 Map network drive and reconnect at logon
Figure 4-54 Configure user name and password to access the file server
169
Tivoli Continuous Data Protection for Files with a file server

Figure 4-55, shows the general configuration for desktop and mobile computers in this scenario.
Figure 4-55 General configuration for this scenario
The recommended configuration for each machine is: Backup to: (leave default, not applicable in this scenario) How many versions to keep: (leave default, not applicable in this scenario) Maximum space for backups: (leave default, not applicable in this scenario) Continuous protection level: Remote storage only
170
Note: When the continuous protection level is configured to remote storage only, you need to configure all parameters for continuous and scheduled protection in the Remote Storage tab.
Figure 4-56 Files to protect in continuous backup
Figure 4-56 shows the files to protect continuously. In this scenario all machines have this directory created which contains all files designated for continuous protection.
171
Figure 4-57 Configure remote storage for continuous and scheduled protection
Figure 4-57 shows the remote storage configuration for this scenario: Backup to: File Server (Athens) Location: \\athens\cdp_fileserver (mapped drive) How many versions to keep: 2 (two versions for files protected by both continuous and scheduled backups) Maximum space for backup: 15 GB (the maximum space for backup for each machine needs to be large enough to maintain at least one version for each file covered with both continuous and scheduled protection) Advanced setting: For security reasons encryption will be used. All machines in this environment are using the storage area for their replicated files.
172
Sub-file copy option: Send only the modified blocks when the file is greater than 3 MB.
Figure 4-58 Configure directories, files, and frequency for schedule protection
173
Figure 4-59 Select files and directories for scheduled protection
Figure 4-58 on page 173 and Figure 4-59 show the frequency, directories, and files for schedule protection.
Encryption
The encryption feature provides security on your remote storage location. This can be useful if multiple users have access to the remote server location, and you need to ensure that each users data is protected from others.
Figure 4-60 Inform password for encrypted files
When the first file is sent to the file server, you will be prompted for a password to enable encryption of the files, see Figure 4-60.
174
It is critically important that the password be remembered and kept in a place that is retrievable in the event of a machine or disk failure. If the password is lost, all encrypted data is completely unretrievable. The password is absolutely critical. You can then verify that the files are encrypted on the file server. See Figure 4-61.
Figure 4-61 Replicated files with encryption option on file server
Tivoli Continuous Data Protection for Files cannot protect backup copies that have already been encrypted by another instance of Tivoli Continuous Data Protection for Files. This is an issue only if you send encrypted files to a file server with Tivoli Continuous Data Protection for Files, and then try to send these files to another file server or to an ISP provider using a local copy of Tivoli Continuous Data Protection for Files. If you configure Tivoli Continuous Data Protection for Files to encrypt the backup copies to a file server, you must not use Tivoli Continuous Data Protection for Files to protect the encrypted backup copies in that file server. You can use Tivoli Storage Manager or another backup solution to protect the encrypted backup copies on that file server.
175
Backup the file server to a Tivoli Storage Manager Express

It is necessary to define your file server as a client node on to Tivoli Storage Manager Express. You can follow the same steps to add a node that are in section 4.3.2, Small business with Tivoli Storage Manager Express on page 151, to Tivoli Storage Manager Express.
Figure 4-62 Computers and applications on Tivoli Storage Manager Express
We have defined Athens as a client node to Tivoli Storage Manager Express to backup the RealTimeBackup directory. See Figure 4-62. By default this directory is excluded. See Figure 4-63 on page 177.
176
Figure 4-63 Excluded files on Tivoli Storage Manager Express client
You need to edit the file C:\Program Files\tivoli\tsm\baclient\dsm.opt to remove this exclusion. See Figure 4-64 on page 178.
177
Figure 4-64 Remove directory from dsm.opt
Now, it is possible to back up the replicated files from Tivoli Continuous Data Protection for Files to Tivoli Storage Manager Express. See Figure 4-65 on page 179.
178
Figure 4-65 Files to backup on Tivoli Storage Manager Express
Backup policy
The number of backup versions on the file server will be controlled by Tivoli Continuous Data Protection for Files, while Tivoli Storage Manager Express will control the number of files that will be backed up from the file server. With Tivoli Storage Manager Express, you have a default backup policy which retains files locally on disk for 14 days after the original backup. However, Tivoli Storage Manager Express can be configured to use media copies to keep backups for longer than the default 14 days allowing you to restore data after it has been expired from the backup servers disk storage. Note: Be sure to size Tivoli Storage Manager Express storage with enough disk space to accommodate 14 days of backups. You can extend the availability of your data by implementing media copies, which can also be sent offsite for additional recoverability.
179
4.4 Tivoli Continuous Data Protection for Files in an enterprise environment

The typical corporate environment for Tivoli Continuous Data Protection for Files can consist of up to a thousand user desktops. The planning and sizing considerations are critical in this type of configuration, so take the time to plan your deployment effectively. For enterprise environments we recommend that you use the push installation capabilities of Tivoli Continuous Data Protection for Files to deploy the same configuration on all computers. The typical scenarios for large environments discussed here are: Enterprise with Tivoli Storage Manager Enterprise with file servers Enterprise and branch offices
4.4.1 Enterprise environment with Tivoli Storage Manager

In this configuration, a user has Tivoli Continuous Data Protection for Files loaded on the local machine which sends data to network file servers. File servers are then backed up by Tivoli Storage Manager. See Figure 4-66 on page 181.
180
Department A LAN
CDP TSM
Mobile Computers Department B
CDP TSM
. . .
CDP
Department Z
TSM
CDP TSM
Tape Library
Figure 4-66 Example of enterprise environment with Tivoli Storage Manager centric
When you have a significant number of individual desktops loaded with Tivoli Continuous Data Protection for Files it is not advisable to send backups directly to Tivoli Storage Manager. Each file that needs to be replicated opens a new connection on the server, so it is easy to imagine a scenario with an overwhelmed Tivoli Storage Manager server. If you intend to send data from Tivoli Continuous Data Protection for Files to a Tivoli Storage Manager server, consider having different Tivoli Storage Manager server instances for your Tivoli Storage Manager client backups and your Tivoli Continuous Data Protection for Files backups. Important: The server is critical to the overall Tivoli Storage Manager infrastructure and design. Do a proper sizing of your Tivoli Storage Manager environment before your Tivoli Continuous Data Protection for Files installation and configuration. Use the rule of thumb to configure the size of your Tivoli Storage Manager database at 1 to 2% of the total amount of data in the environment. If you know the number of files to back up and the backup policy, you can multiply this number by 600 bytes.
181
The lab environment is configured as follows: Continuous protection to local drive Scheduled protection to Tivoli Storage Manager ImportantFiles directory covered by continuous protection ImportantFiles and ExampleData directories covered by scheduled protection Frequency for scheduled protection= Hourly 1 version and 5 GB for continuous protection 2 versions and 30 GB for scheduled protection Remote storage to Tivoli Storage Manager Server Push installation Central administration Do not replicate files greater than 200 MB local and 2 GB remote Tip: In our environment we implemented a user policy that all important files should be saved in the \ImportantFiles\ directory and other files that are candidates for backup in the \ExampleData\ directory. Creating a similar policy and configuration for your environment will ease storage administration. See the flow for this environment in Figure 4-67 on page 183.
182
Berlin Central Administration

11 10 12 1 2 3 8 7 6 5 4
LAN
3
11 10 9 8 7 6 5 4 12 1 2 3 10 9 8 7 6 5 4 11 12 1 2 3
3
11 10 9 8 7 6 5 4 12 1 2
3
11 3 10 9 8 7 6 5 4 12 1 2
3
3
CDP
CDP
CDP
CDP
Bruge
Dakar
Amsterdam
Izmir
Windows XP Pentium 4 512 GB memory User desktop
Helsinki
Windows 2003 Dual Core 3 GB memory Tivoli Storage Manager
Tape Library
2 3 4
Replicates the files in a local disk At schedule time verifies the journal list and replicates the pending files to Tivoli Storage Manager Migrates files to tapes
Figure 4-67 Lab environment (Tivoli Storage Manager centric)
Before configuring Tivoli Continuous Data Protection for Files, it is necessary to properly configure Tivoli Storage Manager.
Tivoli Storage Manager configuration

Tivoli Storage Manager enables you to protect your organizations data from failures and other errors by storing backup, archive, space management, and bare-metal restore data, as well as compliance and disaster recovery data in a hierarchy of offline storage. Because it is highly scalable, Tivoli Storage Manager can help protect computers running a variety of different operating systems, on hardware ranging from notebooks to a z/OS system and connected together through the Internet, wide area networks (WANs), local area networks (LANs), or storage area networks (SANs). It uses Web based management, intelligent data move-and-store techniques, and comprehensive policy based automation that work together to help increase data protection and potentially decrease time and administration costs. Note: For more details on Tivoli Storage Manager go to http://www-306.ibm.com/software/tivoli/products/storage-mgr/.
183
The Tivoli Storage Manager server is installed and configured on server Helsinki. On our clients it is not necessary to install the Tivoli Storage Manager backup/archive client, because Tivoli Continuous Data Protection for Files will use the Tivoli Storage Manager API (application program interface) to send files to Tivoli Storage Manager server. The default dsm.opt file is located in the C:\Documents and Settings\All Users\Application Data\Tivoli\CDP_for_Files\ directory. You can use the command line to configure each node on Tivoli Storage Manager Server. The password assigned at that time will be used by Tivoli Continuous Data Protection for Files to connect to Tivoli Storage Manager server. In order to properly manage storage space the Tivoli Storage Manager administrator must grant authority to the client node to delete backup copies. For more information about registering a Tivoli Storage Manager node, see IBM Tivoli Storage Manager for Windows Administrators Guide. See Web link http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp for more details. Follow these examples to add a client node to a Tivoli Storage Manager: Add nodes to Tivoli Storage Manager server:
184
IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 4, Level 0.2 (c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved. Enter your user id: Enter your password: admin *****
Session established with server ITSO_TSM: Windows Server Version 5, Release 4, Level 0.0 Server date/time: 05/09/2007 18:47:20 Last access: 05/09/2007 18:46:42
tsm: ITSO_TSM>register node bruge cdp4admin passexp=0 backdel=yes ANR2060I Node BRUGE registered in policy domain STANDARD. ANR2099I Administrative userid BRUGE defined for OWNER access to node BRUGE. tsm: ITSO_TSM>register node dakar cdp4admin passexp=0 backdel=yes ANR2060I Node DAKAR registered in policy domain STANDARD. ANR2099I Administrative userid DAKAR defined for OWNER access to node DAKAR. tsm: ITSO_TSM>register node Amsterdam cdp4admin passexp=0 backdel=yes ANR2060I Node Amsterdam registered in policy domain STANDARD. ANR2099I Administrative userid Amsterdam defined for OWNER access to node IZMIR. tsm: ITSO_TSM>register node izmir cdp4admin passexp=0 backdel=yes ANR2060I Node IZMIR registered in policy domain STANDARD. ANR2099I Administrative userid IZMIR defined for OWNER access to node IZMIR. tsm: ITSO_TSM>q node Node Name Days Since Days Since Locked? Last Acce- Password ss Set ------------------------- -------- -------------- ---------- ---------- ------AMSTERDAM BRUGE DAKAR IZMIR (?) (?) (?) (?) STANDARD STANDARD STANDARD STANDARD <1 <1 <1 <1 <1 <1 <1 <1 No No No No Platform Policy Domain Name
Figure 4-68 Add nodes to Tivoli Storage Manager server
185
Central management
Tivoli Continuous Data Protection for Files has features that allow an administrator to manage the configuration of other Tivoli Continuous Data Protection for Files clients. You can manage the installed product level and configuration of other Tivoli Continuous Data Protection for Files clients. The administrator can also monitor the activity reports of the other clients. To use the central management features, you must configure your Tivoli Continuous Data Protection for Files clients to work together. Select one machine on your network to use as a central management server. In our lab environment the server Berlin will play this role. It is necessary to install Tivoli Continuous Data Protection for Files on this server and do the initial configuration.
Figure 4-69 shows the configuration for continuous protection in this scenario: Backup to: C:\ (Local disk only)
186
How many versions to keep: 1 (Just one version for each file with continuous protection) Maximum space for backups: 5 GB (Maximum space for local continuous protection) Continuous protection level: Local storage only (continuous protection is enabled only for local disk).
Figure 4-70 shows the files designated to protect continuously.
187
Figure 4-71 Remote storage configuration to Tivoli Storage Manager
Figure 4-71 shows the remote settings configuration to send files to Tivoli Storage Manager: Backup to: Tivoli Storage Manager Location: tsm://helsinki (hostname or IP address of the Tivoli Storage Manager Server) How many versions to keep: 2 Maximum space for backups: 30 GB (maximum space for backups on Tivoli Storage Manager Server). You will be prompted for a Tivoli Storage Manager user name and password, see Figure 4-72 on page 189:
188
Figure 4-72 Node password on Tivoli Storage Manager
Figure 4-73 Select applications, files, and frequency to back up to Tivoli Storage Manager Server
189
Figure 4-73 on page 189 and Figure 4-74 show the frequency, directories, and files for scheduled protection. E-mail application: Select application (It will be configured on Schedule Backup Settings link) E-mail application data folder (wildcards allowed): Blank (It will be configured on Schedule Backup Settings link) How often to protect your e-mail: Hourly Select Schedule Backup Settings: Include the extensions or directories for scheduled protection Note: It is not necessary to use the encryption feature, because Tivoli Storage Manager implements a user name and password to protect files. Sub-file copy is not supported to send files directly to Tivoli Storage Manager.
190
Figure 4-75 Advanced settings
Figure 4-75 shows the Advanced configuration for Tivoli Continuous Data Protection for Files: Allow program messages to pop up: Disabled (disables messages when you are using centralized administration) Do not locally backup files larger than: 200 MB Do not remotely backup files larger than: 2 GB
Centralized Administration
Use the Central Administration Settings window to identify administration folders for this computer and to manage the configuration settings on other computers. Select the option Central Administration on the Tivoli Continuous Data Protection for Files main panel, see Figure 4-76 on page 192.
191
Figure 4-76 Initial Tivoli Continuous Data Protection for Files panel
The key to configuring your clients to be managed centrally is in defining the central administration folder(s). When managing Tivoli Continuous Data Protection for Files on a group of computers, it is customary to configure one computer as the template for all computers in the group. In our lab, the Berlin server was used as a template for the group. Tivoli Continuous Data Protection for Files clients with different configurations would need to point to different central administration folders (in our lab environment all clients have the same configuration and all point to the same central administration directory).
Table 4-2 Central administration folder configurations for managing clients Computer Name Group Remote storage location (Configured in remote storage tab) Not applicable Central Administration Folders Result Remote storage location and Central Administration Not applicable
Berlin
Administrator
Not applicable
192
Computer Name
Group
Remote storage location (Configured in remote storage tab) tsm:\\helsinki tsm:\\helsinki tsm:\\helsinki tsm:\\helsinki
Central Administration Folders
Result Remote storage location and Central Administration \\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin
Bruge Dakar Amsterdam Izmir
Group TSM Group TSM Group TSM Group TSM
\\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin \\Berlin\C$\cdp_a dmin
Tivoli Continuous Data Protection for Files uses special folders to manage configuration settings and product levels. Tivoli Continuous Data Protection for Files clients pull configuration options and new product code from these folders, and can push their configuration information to these folders for others clients to pull. The central administration folder is specified in the Central Administration Folder field. If not specified then the central administration folder defaults to the \RealTImeBackup\ folder in the remote storage area. The central administration folder contains two levels of administrative sub-folders. Group administrative sub-folder: These folders apply to all computers that share this central administration folder. In each level of administrative sub-folders, there are two folders: Reports Folder: Tivoli Continuous Data Protection for Files stores status reports in the Reports folder. The full path in our environment is \\Berlin\C$\cdp_admin\$MACHINE\BackupAdmin\Reports. Downloads Folder: When you put product upgrades or configuration files in this folder Tivoli Continuous Data Protection for Files will automatically pull the product upgrades or configuration. The full path in our environment is \\Berlin\C$\BackupAdmin\Downloads.
Computer-specific sub-folders: These folders apply to only one computer. There is no central administration folder on Tivoli Storage Manager server remote storage. If you use Tivoli Storage Manager server remote storage and you want to use central administration folders, you must configure the Central
193
Administration Folder: field in the Central Administration Settings window on the local machine. Type or browse for a folder that will be the central administration folder for the local computer. Note: Verify the default directory on the Central Administration server has the appropriate access rights.
Figure 4-77 Central administration configuration
194
Check the box Publish this computers settings as the configuration template for other computers to use, see Figure 4-77 on page 194. When you click the OK button, this computers configuration settings file will be copied to the downloads sub-folder of the central administration folder that is shared by the group of computers. All computers that share the central administration folder will adopt the Tivoli Continuous Data Protection for Files settings that you publish. Use the Lock the configuration of others computers option to prevent any of the centrally managed computers from changing their settings. Note: If you will use the published configuration file to push an installation to another computer, all Tivoli Continuous Data Protection for Files clients that share the central administration folder with the new client will be prevented from updating their configurations.
Note: If you will use the published configuration file to push installation to another computer, do not check the Run Scan Now box. If you do, all Tivoli Continuous Data Protection for Files clients that share the central administration folder with the new client will scan and backup all protected files. This can be a large burden on your network and the individual computers resources.
Figure 4-78 Publish settings
Figure 4-78 shows that the fpcommands.xml was created successfully. C:\cdp_admin\BackupAdmin\Downloads>copy fpcommands.xml fpa.txt 1 file(s) copied.
Figure 4-79 Rename fpcommands.xml to use push installation
To use published configuration settings when invoking the installer, rename the file to fpa.txt. See Figure 4-79.
195
Now, it is necessary to distribute the Tivoli Continuous Data Protection for Files software to other computers. C:\Program Files\Tivoli\CDP_for_Files>fpPushInst.exe \\Bruge /user:a dministrator /pwd:cdp4admin /c:C:\cdp_admin\BackupAdmin\Downloads\fp a.txt /r "C:\cdp_admin\BackupAdmin\Downloads\TivoliCDP_CDPForFiles_3 .1.0.45_windows.exe" /s /v\"/qn Reboot=ReallySupress DONT_LAUNCH_FIL EPATHSRV=1\" Connecting to remote service \\Bruge ... ADMIN$ connected IPC$ conn ected File C:\cdp_admin\BackupAdmin\Downloads\fpa.txt copied to \\Bruge\AD MIN$\System32\fpa.txt File C:\cdp_admin\BackupAdmin\Downloads\TivoliCDP_CDPForFiles_3.1.0. 45_windows.exe copied. Communication with remote established. Waiting remote command's response...
Remote command returned 0(0x0)

Figure 4-80 Push installation on Bruge, Windows 2003 server
Figure 4-80 shows the push installation. See 3.2.3, Push installation on page 69 for more details. Note: Push install is not supported on the Microsoft Vista operating system. In order to utilize your standard configuration, do a manual installation and configure the Central Administration Folder- for example \\Berlin\C$\cdp_admin. Use pull installation to utilize the same configuration from other managed client nodes. See 3.2.4, Pull installation (upgrade) on page 72 for more details. The user on this computer will not notice that the push installation is occurring. Tivoli Continuous Data Protection for Files will activate itself after the next reboot. In our scenario Dakar needs to have the same configuration of Berlin, our central management server. After rebooting the machine Dakar, the configuration is the same as that of the server Berlin. If you try to change the configuration you will get a warning message that the configuration is locked against changes, see Figure 4-81 on page 197.
196
Figure 4-81 Warning message
Centralized reporting
The scheduled backup reports table gives a summary of scheduled backups to remote storage areas for all computers who share a common central administration folder. To verify backups on our server Berlin we select Central Administration View Report.
Figure 4-82 shows the scheduled backup reports. Version: The version of Tivoli Continuous Data Protection for Files
197
Files: A number indicating approximately how many files were successfully backed up at the last schedule Failures: How many errors there were during the backup History: List of historical backup and failure logs
Backup policy
The existing backup policy configured on the Tivoli Storage Manager server will not be used in this configuration. Tivoli Continuous Data Protection for Files controls the number of files in the remote storage. Tivoli Storage Manager will be used as a storage repository and will not control versioning. For example, this scenario specifies that two versions shall be kept on Tivoli Storage Manager server. In the example below, the docu3.doc file had three different modifications creating two active versions and other remaining versions in an inactive state. See Table 4-3 and Table 4-4.
Table 4-3 Lifecycle file First Schedule docu3.doc (Active) Second Schedule docu3.doc (Active) docu3.doc-FP1178726854 .doc (Active) Third Schedule docu3.doc (Active) docu3.doc-FP1178727242 .doc (Active) docu3.doc-FP1178726854 .doc (Inactive)
Table 4-4 Characteristics of file on Tivoli Storage Manager File Name docu3.doc docu3.doc-FP1178726854 .doc docu3.doc-FP1178658964 .doc Active / Inactive Active Active Inactive Backup Date / Time 2007-05-09 14:58:27 2007-05-09 14:12:56 2007-05-09 14:06:34
198
tsm: ITSO_TSM>select ll_name,state,backup_date from backups where no de_name='DAKAR' and ll_name like 'docu3%' ANR2963W This SQL query may produce a very large result table, or ma y require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y LL_NAME -----------------docu3.doc docu3.doc-FP1178727242.doc docu3.doc-FP1178726854.doc STATE -----------------ACTIVE_VERSION ACTIVE_VERSION INACTIVE_VERSION BACKUP_DATE -----------------2007-05-09 14:58:27.000000 2007-05-09 14:12:56.000000 2007-05-09 14:06:34.000000
tsm: ITSO_TSM>expire inventory ANS8003I Process number 8 started. tsm: ITSO_TSM>select ll_name,state,backup_date from backups where no de_name='DAKAR' and ll_name like 'docu3%' ANR2963W This SQL query may produce a very large result table, or ma y require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y LL_NAME -----------------docu3.doc docu3.doc-FP1178727242.doc tsm: ITSO_TSM>
Figure 4-83 Expiration example on Tivoli Storage Manager Server
STATE -----------------ACTIVE_VERSION ACTIVE_VERSION
BACKUP_DATE -----------------2007-05-09 14:58:27.000000 2007-05-09 14:12:56.000000
Tivoli Continuous Data Protection for Files marks unwanted files as inactive. Expire inventory deletes unwanted backups from the Tivoli Storage Manager catalog and marks the backups on storage pools as expired. When the expire inventory process is executed on the Tivoli Storage Manager server the inactive versions will be removed from the Tivoli Storage Manager Database. See Figure 4-83.
199
4.4.2 Enterprise with Tivoli Continuous Data Protection for Files loaded on file servers
Tivoli Continuous Data Protection for Files is also designed to run well on the file server (protecting the data that resides on file servers versus protecting data on the end-point workstations). The main value of Tivoli Continuous Data Protection for Files on a file server is that it essentially allows each user to have continuous versioning of their files available locally and at a high speed. Note: We recommend that you back up the target file server using a traditional backup application such as Tivoli Storage Manager. As described in scenario 4.4.1, Enterprise environment with Tivoli Storage Manager on page 180, user workstations can be configured to send data directly to Tivoli Storage Manager, but it is not the preferred configuration for several reasons: An additional application/agent that needs to be deployed An additional application needs to be licensed Tivoli Storage Manager sub-file mechanisms are not as space/network-efficient as Tivoli Continuous Data Protection for Files The network restart capability is batch oriented (if the transmission of pending files to Tivoli Storage Manager fails, it will start over completely when connected again) A file server is constantly up while the users workstation might not be network connected at all times Note: When using a Tivoli Storage Manager server as your remote storage location, it is considered a best practice to position Tivoli Storage Manager and Tivoli Continuous Data Protection for Files on a file server rather than directly on users workstations.
200
Backup LAN
File Server A
File Server B
File Server Z
File Server Mobile Computers
Tape Library
TSM TSM TSM TSM
Corporate LAN Department A Department B Department Z
. . .
CDP
CDP
CDP
Mobile Computers
CDP
Figure 4-84 Example of enterprise environment with Tivoli Storage Manager and file server
The lab environment is configured as follows: Group A (desktop computers) Continuous protection to local drive Scheduled protection to file server A Continuous protection for ImportantFiles directory Scheduled protection for ImportantFiles and ExampleData directories Frequency for scheduled protection = Hourly 1 version and 5 GB for continuous protection 2 versions and 30 GB for scheduled protection Remote Storage to file server A (Florence) Sub-file copy from files greater than 3 MB (Notes sub-file backup) Push installation to install Tivoli Continuous Data Protection for Files client Central administration to manage clients
201
Do not replicate files greater than 200 MB local and 2 GB remote Maximum remote transfer rate 1Gbps Group B (mobile computers) Continuous protection to local drive Scheduled protection to file server B Continuous protection for ImportantFiles directory Scheduled protection for ImportantFiles and ExampleData directories Scheduled protection for e-mail Frequency for scheduled protection = Daily at 09:00 AM 1 version and 5 GB for continuous protection 2 versions and 30 GB for scheduled protection Remote Storage to file server B (Cairo) Sub-file copy from files greater than 3 MB (Notes sub-file backup) Push installation to install Tivoli Continuous Data Protection for Files client Central administration to manage clients Do not replicate files greater than 200 MB local and 2 GB remote Maximum remote transfer rate 100 MB File servers Vault for DoNotDeleteFiles directory This environment contains two different groups to manage. See the flow for this environment on Figure 4-85 on page 203.
202
11 10 9
12
1 2 3
Corporate LAN
11 10 9 8 7 6 5 4 12 1 2 3 10 9 8 7 6 5 4 11 12 1 2 3 10 9 8 7 6 5 4 11 12 1 2 3
8 7 6 5
11 10 9 8 7
12
1 2 3 4
CDP
CDP
CDP
CDP
3
5
TSM Client
Tokyo
Dakar
Amsterdam
Rome
Berlin
Windows 20003 Central Management
Florence
Windows 2003 Pentium 4 1,5 GB memory File Server A
Active daemon identifying the modified files: - Continuous protection sends to replication thread and replicates it locally - Scheduled protection sends to journal list Replicates the files in a remote storage At schedule time verifies the journal list and replicates the pending files to File Server At schedule time backs up the files to TSM Server
2 3 4
Backup LAN
Helsinki
Windows 2003 Pentium 4 1 GB memory TSM Server
11 10 9 8 7
12
1 2 3 4 10 9 8
11
12
1 2 3 4 10 9 8
11
12
1 2 3 4 10 9 8
11
12
1 2 3 4
CDP
3
5
CDP
3
5
CDP
3
5
CDP
3
5
Vienna
Windows XP Pentium 4 1,5 GB memory Mobile
Monaco
Montevideo
Windows XP Pentium 4 1 GB memory Mobile
Brasilia
Windows XP Intel Dual Core 1 GB memory Mobile
4
TSM Client
Windows XP Pentium 4 1,5 GB memory Mobile
Cairo
Windows 2003 Pentium 4 1,5 GB memory File Server B
Figure 4-85 Lab environment (Tivoli Storage Manager and file server)
Tivoli Continuous Data Protection for Files with file server

The main value of Tivoli Continuous Data Protection for Files on a file server is that it essentially allows each user to have continuous versions of their material available, at high speed, and it is possible to use a file server that already exists in your environment. Before configuring Tivoli Continuous Data Protection for Files, it is necessary to configure the file server with the appropriate privileges and map the file server to each users computer. To reconnect to the file server each time the machine is rebooted, use the option in Windows Explorer: Tools Map a network drive. See Figure 4-53 on page 169 and Figure 4-54 on page 169. Berlin is the Central Administration server in this scenario, and it will be used to manage groups A and B. Configuration for Group A:
203
Figure 4-86 shows the configuration for continuous protection in this scenario: Backup to: C:\ (local disk only) How many versions to keep: 1 (versions to cover with continuous protection) Maximum space for backups: 5 GB (maximum space for local continuous protection) Continuous protection level: Local storage only (continuous protection is enabled only for local disk)
204
Figure 4-87 shows the files to protect continuously in this scenario.
205
Figure 4-88 Remote storage configuration to file server Florence
Figure 4-88 shows the configuration to file server Florence. Backup to: File Server Location: \\florence\cdp_fileserver How many versions to keep: 2 Maximum space for backups: 30 GB (maximum space for local continuous protection) Advanced Settings: Encryption backups: Disable Compression backups: Disable
Sub-file copy: 3 MB (send only portions of each file greater than 3 MB)
206
Note: If you want additional security for your files on your file server enable the encryption option If you want to save space on your file server use the compression option
Figure 4-89 Select applications, files, and frequency to back up to a file server
207
Figure 4-89 on page 207 and Figure 4-90 show the frequency, directories, and files for scheduled protection. E-mail application: Select application (configured on Schedule Backup Settings link) E-mail application data folder (wildcards allowed): Blank (configured on Schedule Backup Settings link) How often to protect your e-mail: Hourly Schedule Backup Settings: ImportantData and ExampleData (include extensions and directories to scheduled protection)
208
Figure 4-91 shows the advanced configuration for Tivoli Continuous Data Protection for Files: Allow program messages to pop-up: Disabled (recommended for centralized administration) Do not locally backup files larger than: 200 MB (files greater than 200 MB will be skipped by Tivoli Continuous Data Protection for Files continuous protection) Do not remotely backup files larger than: 2 GB (files greater than 2 GB will skipped by Tivoli Continuous Data Protection for Files scheduled protection) Maximum remote transfer rate: 1 Gbs (maximum network throughput allowed)
209
Figure 4-92 Central administration configuration for group A
Figure 4-92 shows the Central Administration Settings for servers on Group A: Central Administration Folder: \\Berlin\C$\cdp_admin\groupA Publish this computers settings as the configuration template for others computers to use: Enable (create the fpcommands.xml file) Lock the configuration of others computers: Enable Run Scan Now on other computers: Disable
Click OK to publish settings, see Figure 4-93 on page 211.
210
Configuration for Group B: Some configuration options are the same as Group A so it is not necessary to change them: General configuration Files to protect in continuous protection
Figure 4-94 Remote storage configuration to file server Cairo
211
Figure 4-94 on page 211 shows the configuration to file server Cairo: Back up to: File Server Location: \\cairo\cdp_fileserver How many versions to keep: 2 (number of different versions of each file) Maximum space for backups: 30 GB (maximum space for local continuous protection) Advanced Settings: Encryption backups: Disable Compression backups: Disable Sub-file copy: 3 MB (send only portions of each file greater than 3 MB)
Figure 4-95 Select applications, files and frequency to backup to file server Cairo
212
Figure 4-95 on page 212 and Figure 4-96 show the frequency as well as directories and files for scheduled protection.
213
Figure 4-97 shows the advanced configuration for Tivoli Continuous Data Protection for Files.
214
Figure 4-98 Central administration configuration for group B
Figure 4-98 shows the Central Administration Settings for servers on Group A: Central Administration Folder: \\Berlin\C$\cdp_admin\groupB Publish this computers settings as the configuration template for others computers to use: Enable (create the fpcommands.xml file) Lock the configuration of others computers: Enable Run Scan Now on other computers: Disable
Click OK to publish settings, see Figure 4-99 on page 216:
215
Push Installation
Use the push installation option to distribute Tivoli Continuous Data Protection for Files to all computers. Note: You can also use software distribution applications to install Tivoli Continuous Data Protection for Files. Use push installation on the servers. For Windows Vista, you need to install Tivoli Continuous Data Protection for Files manually.
Central management
Two clients with different remote storage locations would have different default central administration folders. See Table 4-5.
Table 4-5 Central administration folder configurations for managing clients Computer Name Group Remote storage location (Configured in remote storage tab) Not applicable \\Florence\cdp_fil eserver \\Florence\cdp_fil eserver \\Florence\cdp_fil eserver \\Florence\cdp_fil eserver \\Cairo\cdp_files erver Central Administration Folders Result: Remote storage location and Central Administration Not applicable \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupB
Berlin Tokyo Dakar Amsterdam Rome Vienna
Administrator Group A Group A Group A Group A Group B
Not applicable \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupA \\Berlin\C$\cdp_ admin\GroupB
216
Computer Name
Group
Remote storage location (Configured in remote storage tab) \\Cairo\cdp_files erver \\Cairo\cdp_files erver \\Cairo\cdp_files erver
Central Administration Folders
Result: Remote storage location and Central Administration \\Berlin\C$\cdp_ admin\GroupB \\Berlin\C$\cdp_ admin\GroupB \\Berlin\C$\cdp_ admin\GroupB
Monaco Montevideo Brasilia
Group B Group B Group B
\\Berlin\C$\cdp_ admin\GroupB \\Berlin\C$\cdp_ admin\GroupB \\Berlin\C$\cdp_ admin\GroupB
When you manage group A, configure Berlins central administration folder to be the same as the central administration folder for group A. Follow these steps: 1. Open the Central Administration Settings window. 2. In the Central Administration Folder type \\Berlin\C$\cdp_admin\GroupA (or browse for this directory). 3. Click the OK button. The window will close. 4. Open the Central Administration Settings window again. 5. Click the View Report link. The remote storage reports table will open. When you manage group B, configure Berlins central administration folder to be the same as the central administration folder for group A. Follow these steps: 1. Open the Central Administration Settings window. 2. In the Central Administration Folder type \\Berlin\C$\cdp_admin\GroupB (or browse for this directory). 3. Click the OK button. The window will close. 4. Open the Central Administration Settings window again 5. Click the View Report link. The remote storage reports table will open. Figure 4-100 on page 218 shows the report for Group A.
217
Figure 4-100 Central Management Report for Group B
Vault
Vault folders, and the files in them, are not affected by the exclude list, nor by the list of files that are specified for continuous or scheduled protection. All files that you select in the Vault settings dialog will be vaulted. In our lab environment Tivoli Continuous Data Protection for Files is installed on the file server with just the vault option configured. No other tabs need to be configured. See Figure 4-101 on page 219, Figure 4-102 on page 219, Figure 4-103 on page 220 and Figure 4-104 on page 220.
218
Figure 4-101 Files to protect on file server Florence
Figure 4-102 Protected vaulting settings on file server Florence
219
Figure 4-103 Files to protect on file server Cairo
Figure 4-104 Protected vaulting settings on file server Cairo
220
If anyone tries to delete a file inside in this directory they will receive a message that this file is write-protected. See Figure 4-105.
Figure 4-105 Message error when trying to delete vaulted files
E-mail integration (Notes)

Tivoli Continuous Data Protection for Files has special support for files that are constantly open. The technique used by Tivoli Continuous Data Protection for Files is referred to as bitmapping a files I/O. When writes occur to database/file, Tivoli Continuous Data Protection for Files keeps a bit that identifies the region that is changing. This is a extremely low-overhead operation. At the time of replication, Tivoli Continuous Data Protection for Files can exploit that bitmap to know the regions to copy to the target. Because e-mail files typically are very large, they are not backed up continuously, but only on the schedule that you select. E-mail files are backed up only to remote storage. If the remote storage is not available at the scheduled backup time, Continuous Data Protection for Files will queue the backup copies for later transmission. When the remote storage area becomes available, Continuous Data Protection for Files will create the backup copies on the remote storage area. Note: If transmission is interrupted for any reason or the computer reboots or is shut down, Tivoli Continuous Data Protection for Files will resume at the block last transferred; it will not restart the entire transmission. In lab environment, Vienna, a Windows XP desktop user has Lotus Notes 7 installed and constantly in use. See Figure 4-106 on page 222.
221
Figure 4-106 Protect Lotus Notes 7, using scheduled continuous protection
The first time that you are using Tivoli Continuous Data Protection for Files with Notes you will be prompted for a Notes password. See Figure 4-107.
Figure 4-107 Password for Lotus Notes Database
This scenario has sub-file configured for files greater than 3 MB. Figure 4-108 on page 223 shows the replicated Notes files on file server Cairo.
222
Figure 4-108 Notes files on file server Cairo
Backup file server to Tivoli Storage Manager Server

Define your file server as a client node on Tivoli Storage Manager to back up the protected files from Tivoli Continuous Data Protection for Files.
Configure backup policy on Tivoli Storage Manager Server

Each file backed up by Tivoli Continuous Data Protection for Files has an appended suffix, so the file will be seen as unique to Tivoli Storage Manager and always active on Tivoli Storage Manager server and will never expire. Tivoli Storage Manager will delete these files when Tivoli Continuous Data Protection for Files purges them from the file server. In this scenario, the customer wants to retain the backed up files for 360 days. 1. From the Tivoli Storage Manager command line configure policy domain, policyset, management class and backup copy group:
223
tsm: ITSO_TSM>define domain pdfls description='Domain for File Server' ANR1500I Policy domain PDFLS defined. tsm: ITSO_TSM>define policyset pdfls psfls description='Policy Set for File Server' ANR1510I Policy set PSFLS defined in policy domain PDFLS. tsm: ITSO_TSM>define mgmtclass pdfls psfls mcfls description='Management Class Default for File Server' ANR1520I Management class MCFLS defined in policy domain PDFLS, set PSFLS.
tsm: ITSO_TSM>define copygroup pdfls psfls mcfls standard verexists=1 retextra=0 verdeleted=1 retonly=360 destination=di skpool ANR1530I Backup copy group STANDARD defined in policy domain PDFLS, set PSFLS, management class MCFLS. tsm: ITSO_TSM>assign defmgmtclass pdfls psfls mcfls ANR1538I Default management class set to MCFLS for policy domain PDFLS, set PSFLS. tsm: ITSO_TSM>activate policyset pdfls psfls ANR1554W DEFAULT Management class MCFLS in policy set PDFLS PSFLS does not have an ARCHIVE copygroup: files will not be archived by default if this set is activated. Do you wish to proceed? (Yes (Y)/No (N)) y ANR1554W DEFAULT Management class MCFLS in policy set PDFLS PSFLS does not have an ARCHIVE copygroup: files will not be archived by default if this set is activated. ANR1514I Policy set PSFLS activated in policy domain PDFLS.
Figure 4-109 Backup policy on Tivoli Storage Manager
2. From the Tivoli Storage Manager command line add nodes to Tivoli Storage Manager Server.
224
tsm: ITSO_TSM>register node florence cdp4admin domain=pdfls passex=0 ANR2060I Node FLORENCE registered in policy domain PDFLS. ANR2099I Administrative userid FLORENCE defined for OWNER access to node FLORENCE. tsm: ITSO_TSM>register node cairo cdp4admin domain=pdfls passex=0 ANR2060I Node CAIRO registered in policy domain PDFLS. ANR2099I Administrative userid CAIRO defined for OWNER access to node CAIRO.
Figure 4-110 Register node on Tivoli Storage Manager server
3. On the Tivoli Storage Manager client configure dsm.opt options (C:\Program Files\tivoli\tsm\client\ba\bin\dsm.opt).
Figure 4-111 Example of dsm.opt file
225
4. On the client node validate user name and password to access Tivoli Storage Manager. Go to Start All Programs Tivoli Storage Manager Backup-Archive GUI.
Figure 4-112 Validate password
5. Use Tivoli Storage Manager schedule or another scheduling tool to setup times to back up your file server tsm: ITSO_TSM>define schedule pdfls fs_incr_daily type=client description='Daily Backup Incremental' action=incremental starttime=22:00 duration=1 durunits=hours period=1 perunits=days dayofweek=any ANR2500I Schedule FS_INCR_DAILY defined in policy domain PDFLS. tsm: ITSO_TSM>define association pdfls fs_incr_daily cairo,florence ANR2510I Node CAIRO associated with schedule FS_INCR_DAILY in policy domain PDFLS. ANR2510I Node FLORENCE associated with schedule FS_INCR_DAILY in policy domain PDFLS.
Figure 4-113 Schedule backup on Tivoli Storage Manager
226
4.4.3 Enterprise and remote offices

A situation where you have small, remote offices with no local administrator is an ideal scenario to use Tivoli Continuous Data Protection for Files to replicate data to a centralized corporate file server. This is recommended when you have a few servers and the daily percentage of data change varies from 2 to 8%, otherwise the connection link might not be enough to support the replication of the remote data (based on the assumption your remote office has a limited network connection). Note: Properly size your network link when you intend to replicate data using a WAN.
Corporate Site
Remote Office A
Servers
Tape Library
Backup LAN
File Server A
File Server B
File Server Mobile Computers
File Server Remote Offces
Broadband
TSM TSM TSM TSM
Corporate LAN
Department A Department B
. . .
CDP
Departmen tB
CDP Mobile Computers
Remote Office B
Servers
Figure 4-114 Enterprise and remote offices example
To send the replicated files to a local file server follow the steps outlined in the sectionTivoli Continuous Data Protection for Files with file server on page 203. Remember to appropriately configure the Maximum remote transfer rate, on the Advanced tab.
227
4.5 Restore scenarios

If you have lost an important file (or set of files) Tivoli Continuous Data Protection for Files provides you with an easy way to restore your lost information. You can restore individual files, groups of files, and directory trees. You can restore them to their original location or to a new location. If a file has several backup versions, you can either restore the most recent version (the default setting) or select a different version. A wizard guides you to find the file, choose the right version, and choose the location to restore your file. To restore files, you need to click on the link Restore, on the file status page. See Figure 4-115.
Figure 4-115 Status page
The Welcome page lists the steps to restore your files. See Figure 4-116 on page 229.
228
Figure 4-116 Welcome page
Click the Next button to advance to the next page of the wizard, the page Files to restore displays, see Figure 4-117 on page 230, or click the Cancel button to exit the wizard without restoring any files.
229
Figure 4-117 Files to restore
4.5.1 Restore from local disk

In this scenario, the file BackupMe.txt will be restored on the Berlin server. 1. On the Files to Restore page, select the option Search, and type the name of the file to restore.
230
Figure 4-118 Search BackupMe.txt file
The search dialog has several fields. The fields are combined to narrow the search criteria. Leaving any field blank increases the chances of finding more files. Find files with all or part of this name: The option used in this example. When you know the name or part of the name of the file you want to restore. You can use an asterisk as a wildcard. Find files created by application check box: When you know the application that you want to restore. Check as many applications as you want. Find files from location type: Local (default option), remote storage or other (any folder you choose)
231
Figure 4-119 Search status
2. Select the file to restore and click Next.
Figure 4-120 Select the file to restore
232
Information on the file to restore: File Name: The name of the file to restore. Let your pointer hover over the file name to reveal the full path of the file. Version: The box lists the dates and times that this file was backed up. Note that this file has three different versions. Size: The size of the file
3. We will restore the file in the C:\RestoreFiles directory. Select the option to restore the file to the following location.
Figure 4-121 Restore Location
4. See the summary information and click Finish to restore the file.
233
Figure 4-122 Summary information
5. On the Status Page, View Report, you can check if the file was restored successfully:
Figure 4-123 View report
4.5.2 Restore from remote storage

It is possible to restore your files from the remote storage area that is currently configured.
234
Restore from external storage a compressed file

In this scenario, the file RestoreCompress.txt will be restored from an external device, on Amsterdam server. Remember that when you have a compressed file, it is mandatory to use Tivoli Continuous Data Protection for Files to restore, otherwise you cannot work with the file. In the Settings Notebook, select Restore Next (on Welcome Page) Search (on Files to Restore) Remote (on From location type, drill down option):
Figure 4-124 Select remote storage to restore
6. Click OK. Tivoli Continuous Data Protection for Files will search for the file:
235
Figure 4-125 Tivoli Continuous Data Protection for Files searching files
7. Select the file RestoreCompress.txt and click Next:
Figure 4-126 Select file name and version of file to restore
236
8. Select the option Restore data to the Following location, and select the path C:\RestoreFiles\ .
Figure 4-127 Select location to restore
9. On Summary information, verify that everything is correct and click Next.
237
10.On the Status Page, View Report, check if the file was restored successfully:
Figure 4-129 Status page, view report
11.The restored file does not have the extension .cdp anymore.
238
Figure 4-130 Check the restored file
Restore an encryption file from an ISP provider

In this scenario, the file RestoreEncryption.txt will be restored from an ISP provider to Madrid server. 1. In the Settings Notebook, select Restore Next (on Welcome Page) Search (on Files to Restore) Remote (on From location type, drill down option): 2. Click OK to search the file.
Figure 4-131 Tivoli Continuous Data Protection for Files searching for files
3. Select the file RestoreEncryption.txt and click Next.
239
Figure 4-132 Select files to restore
4. Select the option Restore data to Following location, and select the path C:\RestoreFiles\ .
240
5. In Summary information, verify that everything is correct and click Next.
241
6. In the Status Page, View Report, check if the file was restored successfully.
7. The restored file does not have the extension .cdp anymore.
242
Figure 4-136 Check the restored file
Restore an entire directory from a File Server

In this scenario, the directory ExampleData will be restored from a file server to the Dakar server. 1. In the Settings Notebook, select Restore Next (on Welcome Page) Folder View Change Search Location link Remote (on from Change source location (drill down option). Click OK. 2. Select the directory that you want to restore, click Update Table, and click OK.
Figure 4-137 Tivoli Continuous Data Protection for Files Change Search Location window
243
3. Select The following location and type in the path C:\RestoreDirectory\.
244
4. In Summary information, verify everything is correct and click Next.
245
5. Check status page to confirm the files were restored successfully.
Restore from File Server sub-file copy backup

In this scenario, the file log.nsf will be restored from the file server Vienna. In the Settings Notebook, select Restore Next (on Welcome Page) Search (on Files to Restore) Remote (on From location type, drill down option):
246
Figure 4-142 Select remote storage to restore
Click OK to search the files.
247
Figure 4-143 Tivoli Continuous Data Protection for Files searching for files
6. Select the file log.nsf and click Next.
248
This file has two different versions on the file server and one FPdelta file. If you choose the last version to restore, you will restore the last version and add the modifications that exist on delta file. See below.
Figure 4-145 Versions of notes file log.nsf on file server
7. Select the option Restore data to: The following location, and type in the path C:\RestoreNotes\.
8. In Summary information, verify everything is correct and click Next.
249
9. In Status Page, View Report, confirm that the file was restored successfully.
10.The restored file is shown below.
250
Figure 4-149 The restored notes file
4.5.3 Restore from Tivoli Storage Manager or Tivoli Storage Manager Express to a file server
The Tivoli Storage Manager client or Tivoli Storage Manager Express backup-client program allows you to restore files from the backup server to a file server. In this scenario the directory C:\ExampleData will be restored to the Dakar server on C:\RestoreFiles directory. 1. Start the Tivoli Storage Manager backup archive program: Start Programs Tivoli Storage Manager Backup-Archive GUI.
Figure 4-150 Tivoli Storage Manager backup-archive client
251
2. Select Restore Select File Level Select Directories or Files to Restore. Click Restore.
Figure 4-151 Restore Tab
3. Select The following Location and type the path to restore on C:\RestoreFiles. Choose the option Restore Complete Path. Click Restore.
252
Figure 4-152 Select destination folder
4. Check the Restore Report. If all files were restored successfully, click OK in the Restore Completed window.
253
Figure 4-153 Report status
254
Chapter 5.
Troubleshooting, hints, and tips

In this chapter, we discuss troubleshooting methods, hints, and tips for running Tivoli Continuous Data Protection for Files. We cover potential installation issues and replication problems using an external device, a Web-based Distributed Authoring and Versioning (WebDAV) server and an IBM Tivoli Storage Manager server. We provide information about the log files used by Tivoli Continuous Data Protection for Files and show how to trace the program. Note: While installing, configuring, and operating Tivoli Continuous Data Protection for Files, you might experience various issues. We cover common issues. It is not possible to cover all potential problems. If you face a problem that we have not described, follow the normal support procedure to contact your local IBM support personnel. This chapter helps you gather information that you can hand over to IBM support personnel for deeper problem analysis. In particular, we cover the following topics: Installation issues on page 256 Replication issues on page 291 System operation and log files on page 347 Tracing on page 351
255
5.1 Installation issues

This section contains information about some common problems that might arise during installation of Tivoli Continuous Data Protection for Files and explains how to solve and avoid these issues. For more information about the installation possibilities refer to 3.1, Basic installation and configuration on page 40 and 3.2, Advanced installation options on page 64.
5.1.1 Disk space

By default, Tivoli Continuous Data Protection for Files is installed in the directory C:\Program Files\Tivoli\CDP_for_Files. You can change the installation location to a different drive, path, or both, but this might lead to a problem if the new location does not have enough free disk space to install Tivoli Continuous Data Protection for Files. Figure 5-1 shows an example of a non-default installation location, where Tivoli Continuous Data Protection for Files is installed in the directory G:\Program Files\Tivoli\CDP_for_Files.
Figure 5-1 Ready to Install the Program window
Before Tivoli Continuous Data Protection for Files actually starts the installation process, it checks if the destination disk has enough free space for a complete installation.
256
If you click Next, and Tivoli Continuous Data Protection for Files encounters an out-of-space condition, you will see a warning window as shown in Figure 5-2.
Figure 5-2 Out of Disk Space window
Note: The disk with the out-of-space condition is highlighted (here the G: drive). Click OK to close the Out of Disk Space window. You will now see the Custom Setup window as shown in Figure 5-3 on page 258.
Chapter 5. Troubleshooting, hints, and tips
257
Figure 5-3 Custom Setup window
At this point you can: Remove files or folders from the destination drive to free up the needed space and continue the installation. Cancel this installation and start a new installation choosing a different installation destination. Choose a different installation location.
Removing files or folders

To delete files or folders from the designated installation location, you can use the Windows Explorer or the Windows command prompt. If you have freed up enough disk space for the Tivoli Continuous Data Protection for Files installation, click Next in the Custom Setup window (see Figure 5-3). You will see the Ready to Install the Program window (see Figure 5-1 on page 256). If you click Next, the installation process of Tivoli Continuous Data Protection for Files will start.
Cancelling the installation process

If you want to cancel this installation process, click Cancel in the Custom Setup window (see Figure 5-3). A window displays asking you if you really want to
258
cancel the installation of Tivoli Continuous Data Protection for Files (see Figure 5-4).
Figure 5-4 Cancel installation window
If you click Yes, the InstallShield Wizard Completed window (see Figure 5-5) displays informing you that the wizard was interrupted before Tivoli Continuous Data Protection for Files could be completely installed.
Figure 5-5 InstallShield Wizard Completed window (canceled installation)
Click Finish to exit the InstallShield Wizard. If you now run the installation again, make sure to specify an installation location with enough free disk space.
259
Choosing a different installation location

If you decide to install Tivoli Continuous Data Protection for Files to a different installation location, click Back in the Custom Setup window (see Figure 5-3 on page 258). You will see the Setup Type window as shown in Figure 5-6.
Figure 5-6 Setup Type (of installation) window
Select Complete as the installation type and click Next. The Ready to Install the Program window displays (see Figure 5-1 on page 256). Click Back, and you will see the Destination Folder window as shown in Figure 5-7 on page 261.
260
Figure 5-7 Destination Folder window
If you click Change..., you will be able to change the installation directory for Tivoli Continuous Data Protection for Files (see Figure 5-8 on page 262).
261
Figure 5-8 Change Current Destination Folder window
Here you can select a different installation destination with more disk space to finally complete the installation of Tivoli Continuous Data Protection for Files. Important: Be aware that you can only change the location where Tivoli Continuous Data Protection for Files installs its program files. You cannot change the location of the Tivoli Continuous Data Protection for Files data files. See 3.4.1, Installation and data directories on page 108 for more information about the installation directories. For the installation process of Tivoli Continuous Data Protection for Files to complete successfully, make sure that both installation locations, the program files installation directory and the data installation directory, have enough free disk space.
5.1.2 Non-privileged users

Tivoli Continuous Data Protection for Files works for all Windows users, even those users that have only limited privileges (non-privileged users).
262
Note: To configure Tivoli Continuous Data Protection for Files in a multi-user environment, refer to 4.4.1, Enterprise environment with Tivoli Storage Manager on page 180. However, to install Tivoli Continuous Data Protection for Files on a system, the user needs to have administrative rights. This is necessary because besides the program files, the user needs to install low-level driver components and perform updates to the Windows registry. To protect a system from unauthorized program installations, non-privileged users are usually not allowed to install programs into the program files directory. If a non-privileged user tries to install Tivoli Continuous Data Protection for Files anyway, an error window is displayed informing the user that the destination directory is not writable (see Figure 5-9).
Figure 5-9 Error message during non-privileged user installation
Tip: Ensure that you have the necessary administrative rights to install Tivoli Continuous Data Protection for Files or ask your system administrator to perform the program installation for you.
5.1.3 Port conflicts

To run Tivoli Continuous Data Protection for Files and manage it through its user interface, Tivoli Continuous Data Protection for Files service is listening by default on port 9003. Unfortunately, you cannot change this port prior or during the installation process. In case another application is already using port 9003, the Tivoli Continuous Data Protection for Files service will later fail binding to it. This section shows how you can change the default port in the Windows registry after the installation is finished, so Tivoli Continuous Data Protection for Files can operate again.
263
Important: If an application is already using port 9003 and cannot use a different port number, the installation of Tivoli Continuous Data Protection for Files will not fail. All necessary files will be copied to the system and the required entries will be made in the Windows registry.
Checking for potential port conflicts before the installation

To display all the current connections and listening ports, use the netstat -a command. To do so, perform the following steps: 1. Click Start Run, type cmd, and click OK. 2. In the command-line window that displays, enter the netstat -a command. Figure 5-10 on page 265 shows the output of a netstat -a command before the installation of Tivoli Continuous Data Protection for Files. A program is already listening on port 9003.
264
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>netstat -a Active Connections Proto TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP Local Address florence:echo florence:discard florence:daytime florence:qotd florence:chargen florence:nameserver florence:domain florence:http florence:epmap florence:microsoft-ds florence:1025 florence:1028 florence:1037 florence:1038 florence:1042 florence:1044 florence:1062 florence:1085 florence:1086 florence:1920 florence:2100 florence:3389 florence:3661 florence:5800 florence:5900 florence:6014 florence:6789 florence:8222 florence:8333 florence:9003 florence:9510 florence:9514 florence:9515 florence:10110 Foreign Address florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 State LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING
Figure 5-10 Port 9003 already being used by another program
265
In this example, the Tivoli Continuous Data Protection for Files service will not be able to bind successfully to port 9003 after the installation is completed.
Installing Tivoli Continuous Data Protection for Files

Refer to 3.1, Basic installation and configuration on page 40 and 3.2, Advanced installation options on page 64 for details about how to install Tivoli Continuous Data Protection for Files.
At the end of the installation process

When the service tries to start for the first time at the end of the Tivoli Continuous Data Protection for Files installation process, a notification message informs you that Tivoli Continuous Data Protection for Files is experiencing a problem (see Figure 5-11).
Figure 5-11 Tivoli Continuous Data Protection for Files reporting a problem
At the same time, Tivoli Continuous Data Protection for Files is launching a Web browser trying to start the Initial Configuration Wizard. This fails because it is trying to open the URL with the default port 9003 (see Figure 5-12 on page 267).
266
Figure 5-12 Tivoli Continuous Data Protection for Files unable to start the Initial Configuration Wizard
Windows system event log

If you refer to the system event log in the Event Viewer, as requested by Tivoli Continuous Data Protection for Files, the event log shows something similar to Figure 5-13 on page 268. Depending on the Windows operating system that you use, follow these steps to start the Event Viewer: Windows XP: Select Start Control Panel Administrative Tools Event Viewer System. Windows 2000 and 2003:
267
Select Start Settings Control Panel Administrative Tools Event Viewer System. Microsoft Vista: Select Start Control Panel System and Maintenance Administrative Tools Event Viewer Windows Logs System.
Figure 5-13 Tivoli Continuous Data Protection for Files entries in the event log
There are three log entries that belong to the Tivoli Continuous Data Protection for Files: Two informational log entries: Source: FilePath Event ID: 6033 Description: FilePath (host) driver loaded and ready Source: Tivoli CDP for Files Event ID: 6103 Description: Tivoli CDP for Files version 3.1.x.y is starting (kernel driver version is 3.1.x.y) Note: Instead of 3.1.x.y, you will see a real version number depending on the version of Tivoli Continuous Data Protection for Files you are running, for example 3.1.0.45. One error log entry:
268
Source: Tivoli CDP for Files Event ID: 6008 Description: During socket bind operation, failed; Reason: There are no more files. Figure 5-14 shows the complete properties of the error event log entry due to the Tivoli Continuous Data Protection for Files not being able to bind to the port. You can open this window by right-clicking Error log entry with Event ID 6008 and selecting Properties.
Figure 5-14 Error entry in the Windows system event log
Editing the Windows registry

To change the port number to a different unused port so that Tivoli Continuous Data Protection for Files can work properly, edit the Windows registry using the Registry Editor. We explain the steps to make the changes in the Windows registry in detail, because an incorrect handling of the Registry Editor can seriously harm the Windows systems stability and ability to function.
269
Attention: If you use the Registry Editor incorrectly, you could cause serious problems that could require you to reinstall your operating system. IBM cannot guarantee that you can solve the problems that result from using the Registry Editor incorrectly. Use the Registry Editor at your own risk. We recommend that you make a backup of the Windows registry before making any manual changes to it. This allows you to restore the Windows registry in case something goes wrong accidentally. Perform the following steps to make the necessary changes in the Windows registry: 1. To start the Registry Editor, select Start Run, type regedit, and click OK. 2. In the left frame, locate and select the branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FilePath srv Figure 5-15 shows that the port number (by default 9003) is stored in the DWORD Value named FpPort.
Figure 5-15 Port number in the FpPort DWORD Value
3. Right-click the FpPort DWORD Value, and select Modify (see Figure 5-16 on page 271).
270
Figure 5-16 Modifying the FpPort DWORD Value
4. Select Decimal, enter an unused port number (for example, 9005), and click OK (see Figure 5-17).
Figure 5-17 Changing the port number to 9005
Figure 5-18 on page 272 shows the new port number (9005) in the FpPort DWORD Value.
271
Figure 5-18 New port number in the FpPort DWORD Value
5. Click File and select Exit to close the Registry Editor. The changes you made are saved automatically.
Final steps
After changing the Windows registry, you have to perform some additional steps.
Modifying start.html and config.html

Tivoli Continuous Data Protection for Files places a small icon in the notification area of the taskbar in order to notify you about incidents or informational messages (for example see Figure 5-11 on page 266). Important: Usually if Tivoli Continuous Data Protection for Files is using its default port 9003, you can use the system tray icon to start the user interface of Tivoli Continuous Data Protection for Files by double-clicking it. This does not work when you have to change the port number to something other than 9003, because the default port (9003) is hard coded using this icon. If you want to start the Tivoli Continuous Data Protection for Files user interface by its program shortcut (Start (All) Programs Tivoli CDP for Files IBM Tivoli Continuous Data Protection for Files), this will not work anymore. Refer to Creating a shortcut in the quick launch area on page 277 for an easy way to launch the user interface of Tivoli Continuous Data Protection for Files again.
272
To get Tivoli Continuous Data Protection for Files to work, you need to change the port number of the URL in the files start.html and config.html to the same value that you entered in the Windows registry (in this case, 9005). Note: Usually, it is not necessary to make any manual changes to files like we do here with start.html (config.html). Follow the same steps as shown with start.html, with file config.html which you can find in the same directory as file start.html. To edit the start.html file, perform the following steps: 1. Click Start Run, type wordpad, and click OK. The WordPad editor opens. 2. Click File Open. 3. Change the type of files to be displayed from Rich Text Format (*.rtf) to All Documents (*.*) in the Files of type: list. 4. Use the navigation area to locate the file start.html in the C:\Program Files\Tivoli\CDP_for_Files\html\login directory (or wherever you have installed the Tivoli Continuous Data Protection for Files program files). 5. Select file start.html and click Open. The original start.html looks like Figure 5-19.
Figure 5-19 Original start.html file with port 9003
6. Change the port number from 9003 to 9005. The file start.html should now look like Figure 5-20 on page 274.
273
Figure 5-20 File start.html after editing (now using port 9005)
7. To save the changes, select File Save. 8. Exit WordPad by selecting File Exit.
Logging off / logging on or restarting the service

The last step to get the port conflict resolved depends on whether you are running Tivoli Continuous Data Protection for Files as a logged in application (which is the default) or whether you executed the FpForServers.js program so that Tivoli Continuous Data Protection for Files runs as a real Windows service. Running as a logged in application (default): If Tivoli Continuous Data Protection for Files is running as a logged in application, you have to log off and log on again. Running as a Windows service: In case Tivoli Continuous Data Protection for Files is running as a Windows service, you have to restart the service by performing the following steps: a. Windows 2000 and 2003: Select Start Settings Control Panel Administrative Tools Services. Windows XP: Select Start Control Panel Administrative Tools Services. Microsoft Vista: Select Start Control Panel System and Maintenance Administrative Tools Services. b. Right-click the CDPforFilesSrv service and select Restart.
274
Note: For more information about FpForServers.js and how to use Tivoli Continuous Data Protection for Files on a file server, refer to Run Continuous Data Protection for Files as a Service in Chapter 8, Protecting a Server in IBM Tivoli Continuous Data Protection for Files 3.1: Installation and Users Guide, GC32-1783.
Checking port usage

Finally, you need to check that everything is working as expected and that Tivoli Continuous Data Protection for Files is using the new port.
Using the netstat -a command

To check whether the new port (9005) is listened to, use the netstat -a command again. Figure 5-21 on page 276 shows the output of a netstat -a command after you have changed the port number.
275
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>netstat -a Active Connections Proto TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP Local Address florence:echo florence:discard florence:daytime florence:qotd florence:chargen florence:nameserver florence:domain florence:http florence:epmap florence:microsoft-ds florence:1025 florence:1028 florence:1037 florence:1038 florence:1042 florence:1044 florence:1062 florence:1085 florence:1086 florence:1920 florence:2100 florence:3389 florence:3661 florence:5800 florence:5900 florence:6014 florence:6789 florence:8222 florence:8333 florence:9003 florence:9005 florence:9510 florence:9514 florence:9515 Foreign Address florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 florence:0 State LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING LISTENING
Figure 5-21 Netstat -a output showing the usage of the new port 9005
276
Checking the Event Viewer

In the Event Viewer, you can also see that the HTML listener thread of Tivoli Continuous Data Protection for Files is now able to listen on port 9005 (see Figure 5-22).
Figure 5-22 HTML listener now successfully listening on port 9005 (Event Viewer)
Creating a shortcut in the quick launch area

As already mentioned earlier in this section, it is no longer possible to start the user interface of Tivoli Continuous Data Protection for Files using the icon in the Windows notification area nor by using the program shortcut of Tivoli Continuous Data Protection for Files. How can you start the Tivoli Continuous Data Protection for Files user interface to manage your protection settings? There are several ways, but an easy way is by creating a shortcut in the quick launch area of the Windows taskbar. Follow these steps to create a shortcut in the quick launch area:
277
1. Start your favorite Internet browser, for example Microsoft Internet Explorer or Mozilla Firefox. 2. Enter the following URL in the URL (location) area of your browser and press Enter: http://localhost:9005/G4/index.html You will see the Status page of Tivoli Continuous Data Protection for Files as shown in Figure 5-23.
Figure 5-23 Tivoli Continuous Data Protection for Files user interface using port 9005
3. To create the shortcut to this URL in the quick launch area, click the little icon at the beginning of the URL address in the URL (location) area and drag-and-drop it into the quick launch area. Figure 5-24 on page 279 shows the new shortcut to this URL in the quick launch area.
278
Figure 5-24 Shortcut in the quick launch area
If you double-click the icon in the quick launch bar, it will start the user interface of Tivoli Continuous Data Protection for Files using the appropriate URL (http://localhost:9005/G4/index.html).
5.1.4 Push installation

As described in 3.2.3, Push installation on page 69, you can use the fpPushInst.exe executable for pushing a local Tivoli Continuous Data Protection for Files installer executable to another computer. Tip: If you want to push the Tivoli Continuous Data Protection for Files installer executable to multiple computers at the same time, you can do so by creating a Windows batch file and specifying the fpPushInst.exe command syntax multiple times in this batch file. For more information about the creation of Windows batch files, see Microsoft Windows XP Batch file reference, found at: http://www.microsoft.com/resources/documentation/windows/xp/all/prod docs/en-us/batch.mspx?mfr=true This is an example of a correct syntax for pushing Tivoli Continuous Data Protection for Files to a remote computer: fpPushInst.exe \\Cairo /user:administrator /pwd:cdp4admin /c:C:\CDP_Files\fpa.txt /r C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /s /v\/qn /l*v C:\inst.log REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1\ Important: You need to mask the quotation marks surrounding the options of the /v parameter as shown in the above example by using a backslash (\) prior the quotation mark.
Do not use any unintentional spaces in the /v parameter syntax because this
might cause the fpPushInst.exe command to fail. This command will:
279
Use computer Cairo as the remote destination for the push installation (\\Cairo) Log into Cairo using user administrator and password cdp4admin (/user:administrator /pwd:cdp4admin) Push a configuration file named fpa.txt from local folder C:\CDP_Files to the \System32\ sub-folder of the Windows installation directory on Cairo and use these protection settings during (silent) installation (/c:C:\CDP_Files\fpa.txt) Push the Tivoli Continuous Data Protection for Files installer file to the remote computer (/r C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe") Starting a service on the remote computer Cairo doing a silent installation (/s /v/qn ...) Log installation messages in file inst.log in the root of drive C: (/l*v C:\inst.log) Note: The log file inst.log will not be created on the local Windows system; it will be created on the remote computer (Cairo). Not rebooting after installation (REBOOT=ReallySuppress) Not launching Tivoli Continuous Data Protection for Files in the system context immediately after installation (DONT_LAUNCH_FILEPATHSRV=1) We will use this example and modify it to demonstrate various issues you might see when using the push installation feature of Tivoli Continuous Data Protection for Files. In detail, we will discuss the following scenarios: Remote system not being available Wrong user name and/or password Wrong fpPushInst.exe command syntax Correct fpPushInst.exe command syntax
280
Note: The fpPushInst.exe executable can be found in the installation directory of Tivoli Continuous Data Protection for Files. By default this is the C:\Program Files\Tivoli\CDP_for_Files directory, but this can be wherever you have chosen to install Tivoli Continuous Data Protection for Files on your system. If you have not used the default installation location for Tivoli Continuous Data Protection for Files, use the following steps to change to this directory. 1. Select Start Run, type cmd, and click OK. A Windows command line window displays. 2. Change to the installation directory of Tivoli Continuous Data Protection for Files by entering cd \program files\tivoli\cdp_for_files. Now you can run the fpPushInst.exe commands as described in the following examples.
Remote system not being available

When you are trying to push the installation of Tivoli Continuous Data Protection for Files to a remote computer which is currently not available on the network, for example, if the user has shutdown the computer, the push installation will fail. This can easily happen if you are pushing Tivoli Continuous Data Protection for Files to multiple computers at the same time and did not check to see if they were all available on the network. Figure 5-25 shows the output of the failing fpPushInst.exe command in case the remote computer is unavailable on the network. C:\Program Files\Tivoli\CDP_for_Files>fpPushInst.exe \\Cairo /user:administrator /pwd:cdp4admin /c:C:\CDP_Files\fpa.txt /r "C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe" /s /v\"/qn /l*v C:\inst.log REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1\" Connecting to remote service \\Cairo ... Failed Couldn't connect to \\Cairo\ADMIN$ No network provider accepted the given network path.
C:\Program Files\Tivoli\CDP_for_Files>
Figure 5-25 Push installation failing due to remote computer not being available
281
Solution:
Make sure that the remote target system is available on the network. For example, see if you can reach the remote system using the ping command. To do so, follow these steps: 1. Select Start Run, type cmd, and click OK. A Windows command line window displays. 2. Enter ping followed by the target name or address (see Figure 5-26). Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>ping Cairo Pinging Cairo [9.3.5.56] with 32 bytes of data: Reply Reply Reply Reply from from from from 9.3.5.56: 9.3.5.56: 9.3.5.56: 9.3.5.56: bytes=32 bytes=32 bytes=32 bytes=32 time<1ms time<1ms time<1ms time<1ms TTL=128 TTL=128 TTL=128 TTL=128
Ping statistics for 9.3.5.56: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\Administrator>
Figure 5-26 Check if remote system is available using the ping command
If you get a reply from the target system, the remote computer is available on the network and a push installation to this computer should be possible if no further errors occur.
Wrong user name and/or password

If you specify an unknown (administrative) user name, a wrong password, or both, the fpPushInst.exe executable cannot connect successfully to the remote computer and therefore the push installation fails.
282
Important: Use an administrative user account to connect to the remote computer because this account will be used for the installation of Tivoli Continuous Data Protection for Files on the target system. Refer to 5.1.2, Non-privileged users on page 262 for more information about the potential issues when trying to install Tivoli Continuous Data Protection for Files as a non-privileged user. In Figure 5-27 you can see the failing message being reported by the Tivoli Continuous Data Protection for Files push installation executable as a result of using an unknown user name or a wrong password. C:\Program Files\Tivoli\CDP_for_Files>fpPushInst.exe \\Cairo /user:admin /pwd:cdptest /c:C:\CDP_Files\fpa.txt /r "C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe" /s /v\"/qn REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1\" Connecting to remote service \\Cairo ... Failed Couldn't connect to \\Cairo\ADMIN$ Logon failure: unknown user name or bad password.
C:\Program Files\Tivoli\CDP_for_Files>
Figure 5-27 Push installation failing due to wrong user name or wrong password
Solution:
Make sure to specify an administrative user account as the user name and a valid password for that account.
Wrong fpPushInst.exe command syntax

Even if the target computer is available on the network, and you are using a correct user name and password for the push installation of Tivoli Continuous Data Protection for Files, the installation still might fail. Most likely this is due to using a wrong fpPushInst.exe command syntax. For more information about the correct fpPushInst.exe command syntax and all available options refer to 3.2.3, Push installation on page 69.
283
Important: You need to mask the quotation marks surrounding the options of the /v parameter as shown in the above example by using a backslash (\) prior to the quotation mark.
Do not use any unintentional spaces in the syntax for the /v parameter
because this could cause the fpPushInst.exe command to fail. Figure 5-28 shows the output of the failing fpPushInst.exe command when a wrong syntax has been used. Note that in this example we did not mask the quotation marks surrounding the options of the /v parameter causing the push installation of Tivoli Continuous Data Protection for Files to fail. C:\Program Files\Tivoli\CDP_for_Files>fpPushInst.exe \\Cairo /user:administrator /pwd:cdp4admin /c:C:\CDP_Files\fpa.txt /r "C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe" /s /v"/qn /l*v C:\inst.log REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1" Connecting to remote service \\Cairo ... ADMIN$ connected IPC$ connected File C:\CDP_Files\fpa.txt copied to \\Cairo\ADMIN$\System32\fpa.txt File C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe copied. Communication with remote established. Waiting remote command's response...
Remote command returned 1203(0x4B3) C:\Program Files\Tivoli\CDP_for_Files>

Figure 5-28 Push installation failing due to wrong command syntax
As you can see, the fpPushInst.exe executable was able to connect successfully to the remote computer Cairo and could copy the Tivoli Continuous Data Protection for Files configuration file (fpa.txt) and the Tivoli Continuous Data Protection for Files installer executable to the \System32\ sub-folder of the Windows installation folder. What actually does fail is the installation process of Tivoli Continuous Data Protection for Files taking place on the remote computer (Cairo) due to the incorrect command syntax. The fpPushInst.exe command returns to the Windows command line with a remote return code different than 0 (here: 1203(0x4B3)).
284
Note: Although we have specified a log file to be written in the root of the C: drive (/l*v C:\inst.log), this log file is not getting written because the installation is failing too early in the installation process.
Solution:
Check the fpPushInst.exe command syntax for any unintentional spaces and for quotation marks surrounding the options of the /v parameter which have not been masked using a backslash (\) before the quotation mark. Correct the syntax if necessary and try the Tivoli Continuous Data Protection for Files push installation again.
Correct fpPushInst.exe command syntax

If everything is correct and the push installation of Tivoli Continuous Data Protection for Files succeeded, the fpPushInst.exe command returns to the Windows command line with a remote return code of 0(0x0) (see Figure 5-29). C:\Program Files\Tivoli\CDP_for_Files>fpPushInst.exe \\Cairo /user:administrator /pwd:cdp4admin /c:C:\CDP_Files\fpa.txt /r "C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe" /s /v\"/qn /l*v C:\inst.log REBOOT=ReallySuppress DONT_LAUNCH_FILEPATHSRV=1\" Connecting to remote service \\Cairo ... ADMIN$ connected IPC$ connected File C:\CDP_Files\fpa.txt copied to \\Cairo\ADMIN$\System32\fpa.txt File C:\CDP_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.exe copied. Communication with remote established. Waiting remote command's response...
Remote command returned 0(0x0) C:\Program Files\Tivoli\CDP_for_Files>

Figure 5-29 Successful push installation of Tivoli Continuous Data Protection for Files
285
Note: At this point there is no indication visible on the remote computer that Tivoli Continuous Data Protection for Files has been installed on this system using the push installation: no Tivoli Continuous Data Protection for Files icon is placed in the notification area nor any other message displayed informing the user about the Tivoli Continuous Data Protection for Files push installation. However, if you look at the installed programs (IBM Tivoli Continuous Data Protection for Files) or the Windows services (CDPforFilesSrv) you can see footprints of Tivoli Continuous Data Protection for Files on the remote computer. Be aware that the log file inst.log is created on the remote computer (Cairo) and not on your local system. Tivoli Continuous Data Protection for Files will start protecting the files on the remote computer (Cairo) the next time this system is rebooted.
5.1.5 Pull installation

In 3.2.4, Pull installation (upgrade) on page 72, we explained how to silently upgrade Tivoli Continuous Data Protection for Files once it is installed by placing a newer installer executable file in the downloads folder (see Administration folders on page 102) of the central administration area (see 3.3.2, Central Administration Settings on page 101). In this section we explain potential issues you might see when using the pull installation to upgrade one or more Tivoli Continuous Data Protection for Files clients to a newer version of the product. The following scenarios are discussed in this section: Upgrade to version 3.1 from a version below 2.2.1.22 Upgrade to version 3.1 from version 2.2.1.22 and higher
Upgrade to version 3.1 from a version below 2.2.1.22

If you are trying to upgrade to Tivoli Continuous Data Protection for Files V3.1 using pull installation, and you are currently running a Tivoli Continuous Data Protection for Files client below V2.2.1.22 on this computer, the pull installation will fail.
286
Important: A Tivoli Continuous Data Protection for Files client below V2.2.1.22 is not able to use pull installation to upgrade to a Tivoli Continuous Data Protection for Files V3.1 client. It will be able to pull the code of the Tivoli Continuous Data Protection for Files V3.1 client from the downloads folder of the central administration area, but the installation does not work. When your Tivoli Continuous Data Protection for Files client below V2.2.1.22 tries to install the upgrade to Tivoli Continuous Data Protection for Files V3.1, you will see following message in the notification area (see Figure 5-30):
Figure 5-30 Tivoli Continuous Data Protection for Files (pull) installation message
You will find the same message (A new version of the software is being installed.) as Event ID 6092 in the Event Viewer (see Figure 5-31 on page 288).
287
Figure 5-31 Event message due to installation of new software version
This installation does fail. You will see the following additional files in the installation directory of your Tivoli Continuous Data Protection for Files client: FPcommand.bat options TivoliCDP_CDPForFiles_3.1.0.45_windows.exe
FPcommand.bat file
The FPcommand.bat file (see Figure 5-32 on page 289) contains the command to install the Tivoli Continuous Data Protection for Files (V3.1) installer executable with some specific (Java-based) installation options as defined in the options file (see Figure 5-33 on page 289). This command does not work when a Tivoli Continuous Data Protection for Files V3.1 client is getting installed. This is because starting with Tivoli Continuous Data Protection for Files V3.1, a different installation/packaging method has been used; instead of the Java-based installation as used with Tivoli Continuous Data Protection for Files V.2.2 and below, now Tivoli Continuous Data Protection for Files V3.1 is using the Microsoft Windows Installer for the installation.
288
The given installation command tries to use the old Java-based installation syntax resulting in the command, and therefore the installation, to fail. set DSM_CDP=1 cd /d "C:\Program Files\Tivoli\CDP_for_Files\" "C:\Program Files\Tivoli\CDP_for_Files\TivoliCDP_CDPForFiles_3.1.0.45_windows.ex e" -silent -options "C:\Program Files\Tivoli\CDP_for_Files\options"
Figure 5-32 FPcommand.bat file
options file
The options file contains specific Java-based installation options (see Figure 5-33). -W bean9.selection=1 -G licenseAccepted=true
Figure 5-33 Options file
TivoliCDP_CDPForFiles_3.1.0.45_windows.exe file
This is the Tivoli Continuous Data Protection for Files V3.1 installer executable which was originally placed in the downloads folder of the central administration area and was pulled from there. Important: You will get no additional information messages indicating that the pull installation of Tivoli Continuous Data Protection for Files V3.1 has failed at this time.
Recommendation:
Upgrade to Tivoli Continuous Data Protection for Files V2.2.1.22 (or higher) first. You can upgrade by using pull installation if you place a higher versioned Tivoli Continuous Data Protection for Files V2.2 installer executable in the downloads folder. If Tivoli Continuous Data Protection for Files V2.2.1.22 (or higher) code has been pulled off the downloads folder and installed successfully, you can then place the Tivoli Continuous Data Protection for Files V3.1 installer executable in that downloads folder. This Tivoli Continuous Data Protection for Files V3.1 installer file will then be pulled from there and installed on your computer.
289
Summary:
If you are running a Tivoli Continuous Data Protection for Files client below V2.2.1.22, the order of upgrades to Tivoli Continuous Data Protection for Files V.3.1 needs to be: Tivoli Continuous Data Protection for Files below V2.2.1.22 Tivoli Continuous Data Protection for Files V2.2.1.22 or higher Tivoli Continuous Data Protection for Files V3.1.
Upgrade to version 3.1 from version 2.2.1.22 and higher

Upgrading from Tivoli Continuous Data Protection for Files V2.2.1.22 (or higher) to Tivoli Continuous Data Protection for Files V3.1 using a pull installation does not have the same issue that we discussed in the previous section (see Upgrade to version 3.1 from a version below 2.2.1.22 on page 286). Important: A Tivoli Continuous Data Protection for Files V2.2.1.22 (or higher) client is able to pull and install a Tivoli Continuous Data Protection for Files V3.1 installer file placed in the downloads folder of the central administration area. During the installation of the newer Tivoli Continuous Data Protection for Files (V3.1) client, you will see a message in the notification area informing you about the installation of the new software version (see Figure 5-30 on page 287). After the installation succeeds, you will be asked to reboot your computer to resume protection of your data using the new Tivoli Continuous Data Protection for Files client version (see Figure 5-34).
Figure 5-34 Message to reboot the computer after the (pull) installation
If you look in the installation directory of your Tivoli Continuous Data Protection for Files client, you will find following files: msipull.log TivoliCDP_CDPForFiles_3.1.0.45_windows.exe
290
msipull.log file
The msipull.log file is the installation log of the new Tivoli Continuous Data Protection for Files (V3.1) client as logged by the Microsoft Windows Installer. This file can be used as a first source for problem determination if any problems occur during pull installation.
TivoliCDP_CDPForFiles_3.1.0.45_windows.exe file
This is the Tivoli Continuous Data Protection for Files V3.1 installer executable which was originally placed in the downloads folder of the central administration area and was pulled from there.
5.2 Replication issues

This section covers some common (remote) replication issues. We discuss problems that could occur if you are using a removable disk (external device) as a remote target for saving your files. We also discuss issues you might experience when you are sending files to a remote file server, a Web-based Distributed Authoring and Versioning (WebDAV) server, and to a Tivoli Storage Manager server. Finally, transient (network) conditions are covered. In detail, the following topics are described in the section about using a removable (external USB) disk as a remote backup target: Removable disk / file system is full Problems with changing drive letter assignments We show you potential issues when you store files on a remote file server, because you have to consider using a Universal Naming Convention1 (UNC) name instead of a drive letter. The WebDAV section covers these common issues: Using wrong user name or password No Internet connection available (transient condition) In the section about IBM Tivoli Storage Manager issues, we discuss the following: No node name defined or wrong node name Node name defined but with wrong permission
1
For information about Universal Naming Convention (UNC), see Path (computing), found at: http://en.wikipedia.org/wiki/Path_%28computing%29#Universal_Naming_Convention
291
IBM Tivoli Storage Manager client sessions disabled IBM Tivoli Storage Manager server unavailable Conflicting include/exclude lists Transient conditions (the remote storage location is temporarily not reachable) are described in the last section.
5.2.1 Removable disk issues

Using a removable (external USB) disk is a very common and convenient method for protecting data when there is no file server available as a remote backup target. For example, if you are travelling around with your mobile computer, you do not want to miss having an alternative backup location other than your local backup area in case your internal disk gets corrupted, so that you can safely restore from the removable disk. In the following example, we are using an external USB disk named USB_Drive with assigned drive letter F as a remote backup location (see Figure 5-35 and Figure 5-36 on page 293).
Figure 5-35 External USB disk named USB_Drive mapped as drive F:
292
Figure 5-36 Drive F: (USB_Drive) as remote backup target (external device)
Disk / file system full

Due to the rising amount of data these days, an external USB drive might run out of disk/file space, even though the sizes of removable disks have dramatically increased in the last couple of years. If Tivoli Continuous Data Protection for Files is facing a problem replicating to the specified remote location due to a disk / file system full condition, it lets you know about this by issuing the notification message seen in Figure 5-37 on page 294.
293
Figure 5-37 Disk full informational message
The backup device full condition will also generate an informational message with Event ID: 6077 in the Windows system event log (see Figure 5-38).
Figure 5-38 Event log entry due to target backup device being full (Event ID: 6077)
Important: Tivoli Continuous Data Protection for Files keeps track of the changes you make to your files even when you see this message. It waits for some time and tries to replicate the changed files later, because this might be a temporary condition.
294
The Tivoli Continuous Data Protection for Files Status page indicates the current problem of your remote storage by turning the color of the Remote Storage icon from blue to yellow with a little exclamation mark (see Figure 5-39).
Figure 5-39 Remote storage location inaccessible due to disk / file system full (Status page)
Tivoli Continuous Data Protection for Files will wait for one minute and then tries replicating the changed file(s). If this fails again, an error message will be shown in the notification area (see Figure 5-40).
Figure 5-40 Tivoli Continuous Data Protection for Files experiencing a problem
295
The Windows system event log Event ID: 6000 is generated with more information about what process of Tivoli Continuous Data Protection for Files has a problem (see Figure 5-41).
Figure 5-41 Event log entry due to disk / file system full condition (Event ID: 6000)
Solution:
To avoid a disk / file system full condition, you can do either one or more of the following things: Free up some space on the removable disk or the remote file system.
296
Important: Do not delete any files or directories in the \RealTimeBackup\ folder, because this is the folder for Tivoli Continuous Data Protection for Files to store remote backup versions of your files. If you delete files there, for example using the Windows Explorer or the Windows command line, it is not known to Tivoli Continuous Data Protection for Files. Because Tivoli Continuous Data Protection for Files has no opportunity to re-sync its own gendb database inventory (see, Local pool log file and \gendb\ directory on page 350) with the real inventory on the remote target, Tivoli Continuous Data Protection for Files could get out-of-sync. For example, Tivoli Continuous Data Protection for Files could show you files for restore which are actually not available anymore (due to having been manually deleted on the remote storage location). If possible, free disk space outside of the \RealTimeBackup\ folder. On the Remote Storage page of the Settings Notebook, adjust the Remote Storage settings (see Figure 5-42): Decrease the number of versions per file being stored remotely. and/or Reduce the space being used for files on the remote location. and/or Activate compression of remote backups.
Figure 5-42 Modified settings in the Remote Backup page to save space on the remote target location
297
Changing drive letter assignments

One of the main features of the Windows operating systems in conjunction with USB (storage) devices is the plug-and-play functionality that automatically assigns a drive letter to a USB device as soon as it gets connected to the system. Usually, Windows keeps track of the already assigned drive letters (persistent drive letters) so that the same device gets the same drive letter assigned when it is plugged in the next time. However, under certain circumstances, this might not hold true, and a newly plugged-in USB device claims the same drive letter as another USB device that is currently offline. An example is shown in Figure 5-43: the USB disk (USB_Drive) had been offline when we plugged in a USB stick (USB_Stick). The USB stick claimed drive letter (F:) so the USB disk got the next available drive letter (G:) assigned when we plugged it in later. Note: We did not change the configuration of Tivoli Continuous Data Protection for Files, so drive (F:) is still defined as the remote backup location (see Figure 5-36 on page 293).
Figure 5-43 Changed drive letter assignments
298
Important: Tivoli Continuous Data Protection for Files does not replicate to the new remote location (F:) as long as there is no \RealTimeBackup\ folder on this device. This avoids unintentionally altering a device that is not meant to be a remote backup location, like a digital camera. Instead, Tivoli Continuous Data Protection for Files informs you that it cannot reach the target location by a notification message (see Figure 5-44).
Figure 5-44 Informational message that the network target cannot be reached
The replication engine of Tivoli Continuous Data Protection for Files creates an entry in the Windows system event log with Event ID: 6069 giving information about the error condition of the network (see Figure 5-45 on page 300).
299
Figure 5-45 Event entry due to replication problem caused by changed drive letters (Event ID: 6069)
The color of the Remote Storage icon on the Status page of Tivoli Continuous Data Protection for Files turns from blue to yellow with a little exclamation mark showing that it has problems with the remote storage location (see Figure 5-46 on page 301).
300
Figure 5-46 Remote storage location inaccessible due to changed drive letter assignment (Status page)
Solution:
In order to avoid unwanted changing of drive letters, you should consider manually assigning your removable disk a drive letter near the end of the alphabet, for example, X, Y or Z, because available drive letters are assigned automatically alphabetically. It is also a good idea to check the drive letter assignments each time you bring new USB devices online and correct them if necessary. To manually change the driver letter assignment for your external USB drive, follow these steps: 1. On the Windows desktop, right-click My Computer and then click Manage. 2. Under Computer Management, click Disk Management. In the right pane, you will see your drives listed.
301
3. Right-click the drive or device you want to change, and then click Change Drive Letter and Paths. 4. Click Change, click Assign the following drive letter, click the drive letter you want to assign, and then click OK. 5. Click the Yes button when the window displays asking you to confirm the change of the drive letter. Tip: Another way to prevent such an issue, is to create and assign a specific mount point to the external device (USB drive). For a detailed procedure refer to technical note 1245761 Instructions on how to point Continuous Data Protection for Files to a USB device, found at: http://www-1.ibm.com/support/docview.wss?rs=2339&context=SS3PE6&dc=D B520&q1=1245761&uid=swg21245761&loc=en_US&cs=utf-8&lang=en
5.2.2 File server issues

In this section, we discuss replication problems in case you have decided to protect your files by storing them on a remote network location (file server) for additional protection. Note: For avoiding general problems using a file server as a remote backup location: Log on to your machine with a user name and password that Tivoli Continuous Data Protection for Files can use to authenticate transparently into the network location you have specified. You can alternatively log into the network using another account with regular privileges interactively (for example, by using the Net Use command). Some versions of Windows have simplified file sharing, which allows one computer to network-attach to another with very little difficulty. The resulting connection allows only limited file system capabilities. If possible, disable simplified file sharing on the target system, because it limits how well Tivoli Continuous Data Protection for Files can produce an identical copy of your files. If simplified file sharing is not disabled, some information, such as access control lists or file streams, might not get copied correctly. Typical replication to a file server as the remote storage location problems are due to transient network conditions, that is, the file server is (temporarily) not reachable over the network. For more information about transient conditions refer to 5.2.5, Transient conditions (remote storage location not reachable) on page 343.
302
Universal Naming Convention (UNC) versus drive letters

To specify a remote backup location in the Tivoli Continuous Data Protection for Files user interface, you can either use the Universal Naming Convention (UNC) name of the file server or the drive letter you have it mapped to. In Figure 5-47, you can see that we connected to a shared network folder e$ on file server Izmir and have mapped it to drive letter (W:).
Figure 5-47 Shared network folder e$ on file server Izmir mapped to drive (W:)
Tip: Use the UNC naming specification of the file server instead of drive letters, since drive letters can change after rebooting and many times do not reconnect automatically. In our case, the recommended way to specify the file server is shown in Figure 5-48 on page 304 using the UNC name \\izmir\e$ instead of drive letter (W:).
303
Figure 5-48 Using the UNC name instead of the drive letter for the remote storage location (Remote Storage page)
5.2.3 WebDAV issues

Storing files on a Web-based Distributed Authoring and Versioning (WebDAV) server has become more popular in the last few years for sharing files (pictures, music and video files, etc.). Many Internet Service Providers (ISPs) offer their customers disk space on a WebDAV server as part of their contract. In this section, we show you some common problems when you use a WebDAV server on the Internet as a remote backup location for your files using Tivoli Continuous Data Protection for Files.
304
Using a WebDAV server as a remote backup location

From the Back up to: list on the Remote Storage page of the Settings Notebook you need to select Web Server (WebDAV) if you want to use a WebDAV server as the remote location for storing your files. You need to use the correct syntax as given by your ISP or administrator in the Location: field when specifying the URL address of your WebDAV server. If the IP address of your WebDAV server is for example webdav.server.net, you need to specify the following URL in the Location: field on the Remote Storage page: https://webdav.server.net Figure 5-49 on page 306 displays an example using a WebDAV server with webdav.server.net as the IP address. In this example we defined to keep five versions of a file on the WebDAV server using 5 GB as the maximum space.
305
Figure 5-49 Using a WebDAV server as the remote storage destination
Wrong user name and/or password

In addition to using the correct URL for your WebDAV server, you need to know and specify a valid user name and password for Tivoli Continuous Data Protection for Files to be able to communicate with the WebDAV server. Tivoli Continuous Data Protection for Files displays an informational message in the notification area that a password is needed for backing up files to the remote location (see Figure 5-50 on page 307).
306
Figure 5-50 Tivoli Continuous Data Protection for Files needs a password (informational message)
A new Web browser window opens prompting you to enter a user name and password to access the WebDAV server (see Figure 5-51).
Figure 5-51 Tivoli Continuous Data Protection for Files prompts for a password to access the WebDAV server
You need to enter the user name and password as given to you by your ISP or administrator (see Figure 5-52 on page 308).
307
Figure 5-52 Entering user name and password
The password needs to be entered twice to confirm its validity. If both passwords do not match, Tivoli Continuous Data Protection for Files opens a window informing you about this situation (see Figure 5-53).
Figure 5-53 The two passwords do not match
If both passwords are identical but wrong, or if the user name is not correct, Tivoli Continuous Data Protection for Files cannot successfully connect to the WebDAV server. If this happens, Tivoli Continuous Data Protection for Files keeps prompting you for the (correct) user name and password until you enter a correct user name and password (see Figure 5-51 on page 307). If you enter a correct user name and password, Tivoli Continuous Data Protection for Files creates a password file in the \pwd\ folder of the data directory with a similar name to the IP name of the WebDAV server (in our case the file name is webdavservernet.pwd). This file contains encrypted information to authenticate Tivoli Continuous Data Protection for Files with the WebDAV server.
308
No Internet connection available (transient condition)

For Tivoli Continuous Data Protection for Files to be able to store files on the WebDAV server, you need to have an active Internet connection. If Tivoli Continuous Data Protection for Files cannot access the WebDAV server because your Internet connection is not active or was dropped, it will display information that it cannot reach the remote network target (see Figure 5-54).
Figure 5-54 WebDAV server not reachable because no Internet connection is available
Because this might be a temporary condition, Tivoli Continuous Data Protection for Files will again try connecting to the WebDAV server to continue storing files there. Attention: Tivoli Continuous Data Protection for Files keeps track of the changes you make to your files even when you see this message. It waits for some time and tries to replicate the changed file(s) later, because this might be a temporary condition. If you change the same file multiple times when your Internet connection is temporarily unavailable, only the latest version of this file is copied over to the WebDAV server when the Internet connection becomes available again. There can be many reasons why your Internet connection is not available. If you are permanently unable to connect to the Internet, contact your ISP for further assistance. Once the Internet connection can be established again and the WebDAV server can be reached, you are notified about this event by Tivoli Continuous Data Protection for Files and replication continues (Figure 5-55).
Figure 5-55 WebDAV server can be reached again (Internet connection established)
309
For more information about transient conditions, refer to 5.2.5, Transient conditions (remote storage location not reachable) on page 343.
5.2.4 Tivoli Storage Manager issues

In this section, we discuss potential issues related to Tivoli Continuous Data Protection for Files in conjunction with a Tivoli Storage Manager server, respectively the Tivoli Storage Manager application programming interface (API). Note: In this section, we do not describe in detail how to configure the Tivoli Storage Manager API client with all its available options, nor do we discuss all the commands needed to maintain a Tivoli Storage Manager server. For more information about these topics, refer to Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and Users Guide, SC32-0146 and Tivoli Storage Manager for Windows: Administrators Guide, SC32-0121.
General information
In order to run properly, the Tivoli Storage Manager API client utilizes a client options file (dsm.opt). This file is installed automatically during the installation of Tivoli Continuous Data Protection for Files and is placed in the data directory used by Tivoli Continuous Data Protection for Files (see 3.4.1, Installation and data directories on page 108). Note: If there is already a Tivoli Storage Manager API available on your computer, maybe because you have a Tivoli Storage Manager Backup/Archive client installed, Tivoli Continuous Data Protection for Files will only install the Tivoli Storage Manager API files if the ones on the machine are older than the ones in the install package (merge module installation). Tivoli Continuous Data Protection for Files uses its own dsm.opt file in the data directory to communicate with a Tivoli Storage Manager server. A separately installed Tivoli Storage Manager client will have a separate options file (dsm.opt). Figure 5-56 displays the default (minimum) dsm.opt file as it is installed, created, and used by Tivoli Continuous Data Protection for Files. COMMMETHOD PASSWORDACCESS TCPip generate
Figure 5-56 Default (minimum) dsm.opt file
310
One of the most important purposes of the options file is to specify the communication protocol necessary to establish communications between the Tivoli Storage Manager API client and the Tivoli Storage Manager backup server. For example, to use the Transmission Control Protocol (TCP)/Internet Protocol (IP) communication protocol, the following needs to be stated in the dsm.opt file: COMMMethod TCPIP If your Tivoli Storage Manager server administrator decides that each client node needs to authenticate to the server when starting a session, you need to specify one of the following: If you want to be prompted for a password (PASSWORDAccess prompt) If the Tivoli Storage Manager API client automatically generates a new password for your client node each time it expires and stores the password encrypted in the Windows registry (PASSWORDAccess generate). This option is used in file dsm.opt used by Tivoli Continuous Data Protection for Files. Table 5-1 lists the minimum (default) options of the Tivoli Storage Manager API client options file as used by Tivoli Continuous Data Protection for Files and provides a short description of each of them and their used parameter value.
Table 5-1 Description of options used in dsm.opt Option Description Used value by Tivoli Continuous Data Protection for Files TCPip
COMMMethod
This option specifies the communication method you use to provide connectivity for client-server communication. This option specifies whether you want to generate your password automatically or set it as a user prompt. Your administrator can require a password for your client node by enabling the authentication feature. Ask your administrator if a password is required for your client node.
PASSWORDAccess
generate
By default, the Tivoli Storage Manager API uses the clients host name as the Tivoli Storage Manager node name when identifying itself to the Tivoli Storage Manager server. Sometimes it is a companys policy to use a specific naming convention for Tivoli Storage Manager node names that differ from the client host names. In this case, you must configure the Tivoli Storage Manager API to use
311
the appropriate node name when logging on to the Tivoli Storage Manager server. You can do so using the NODename option, for example: NODename cdp_florence The Tivoli Storage Manager server usually listens on port 1500 for incoming Tivoli Storage Manager client sessions. Because this can be changed by the Tivoli Storage Manager server administrator, you might need to specify a different port in the dsm.opt file to be used by the Tivoli Storage Manager API. To specify the TCP/IP port on which the Tivoli Storage Manager server listens for incoming client sessions, use the TCPPort option, for example: TCPPort 1510 Table 5-2 summarizes some additional dsm.opt options which are useful in case the Tivoli Storage Manager server administrator does not use the default Tivoli Storage Manager values.
Table 5-2 Some additional useful dsm.opt options Option NODename Description Use this option in your client options file dsm.opt to identify your workstation to the server. You can use different node names to identify multiple operating systems on your workstation. This option specifies a TCP/IP port address for a Tivoli Continuous Data Protection for Files server. You can obtain this address from your administrator. Default value (if not set) workstation (host) name
TCPPort
1500
Using a Tivoli Storage Manager server as a remote backup location

If you want to use a Tivoli Storage Manager server as the remote backup destination of your files, you need to select Tivoli Storage Manager from the Back up to: list in the Remote Storage page of the Settings Notebook. Be sure to use correct syntax in the Location: field by using either the dotted IP address or the IP name of the Tivoli Storage Manager server. Figure 5-57 on page 313 shows an example using the IP name of the Tivoli Storage Manager server named Helsinki. We specified in this example to keep two versions per file on the Tivoli Storage Manager server occupying a maximum space of 5 GB.
312
Figure 5-57 Using a Tivoli Storage Manager server as a remote backup location (Helsinki)
No node name defined or wrong node name

At the time you specify a Tivoli Storage Manager server IP address or name in the Location field and click OK or Apply on the Remote Storage page of the Settings Notebook, Tivoli Continuous Data Protection for Files tries to connect to the Tivoli Storage Manager server using the Tivoli Storage Manager API with the given options in the dsm.opt file and using the default values for options if they are not stated in dsm.opt. If you have not yet defined a Tivoli Storage Manager node name for the Tivoli Continuous Data Protection for Files client or you have defined a wrong node name, you will see a window display informing you that the target location you have specified (Helsinki) is not responding properly (see Figure 5-58 on page 314).
313
Figure 5-58 Window explains target location (Helsinki) is not responding properly
A Tivoli Continuous Data Protection for Files warning message displays in the notification area asking you to check the details in the Activity Report page of Tivoli Continuous Data Protection for Files, because the software is experiencing some problems (see Figure 5-59).
Figure 5-59 Tivoli Continuous Data Protection for Files warning message
This happens as Tivoli Continuous Data Protection for Files tries to connect to the Tivoli Storage Manager server using the clients host name, or the node name if it has been specified in the dsm.opt file, as the Tivoli Storage Manager node name and this fails if this node name does not exist on the Tivoli Storage Manager server. If you open the Windows system event log (see Windows system event log on page 267 for how to access the Windows system event log), you will see an event log entry (Event ID: 6000) explaining that the session has been rejected (ANS1353E) due to a wrong or in this case unknown ID (Tivoli Storage Manager node name) entered (see Figure 5-60 on page 315).
314
Figure 5-60 Event log entry due to unknown or incorrect ID (node name) entered
Note: Return code (RC) 53 is defined as DSM_RC_REJECT_ID_UNKNOWN, which translates to The node name you entered is not known by the server, or you are attempting to access a file migrated to a different node. For more information about Tivoli Storage Manager API return codes and their definitions, refer to Tivoli Storage Manager: Using the Application Program Interface, SC32-0147. The same error message (ANS1353E) is written into the error log file (dsierror.log) of the Tivoli Storage Manager API client which can be found in the data directory of Tivoli Continuous Data Protection for Files (see Figure 5-61). 05/10/2007 16:50:27 ANS1353E Session rejected: Unknown or incorrect ID entered 05/10/2007 16:50:27 ANS1353E Session rejected: Unknown or incorrect ID entered
Figure 5-61 Entries in dsierror.log caused by unknown or incorrect ID (node name) entered
315
Solution:
To solve this kind of error, you need to register the Tivoli Continuous Data Protection for Files clients host name as a Tivoli Storage Manager node name on the Tivoli Storage Manager server first, before the Tivoli Continuous Data Protection for Files client connects to the Tivoli Storage Manager server. If you have done so already, make sure you have used the correct node name and rename it on the Tivoli Storage Manager server if necessary. For more details on how to register or rename a node name on a Tivoli Storage Manager server, refer, for example, to IBM Tivoli Storage Manager for Windows: Administrators Reference, SC32-0127.
Node name defined but with wrong permission

Even if you have registered the Tivoli Continuous Data Protection for Files clients host name as a node name on the Tivoli Storage Manager server, there can still be some issues preventing Tivoli Continuous Data Protection for Files from working correctly together with a Tivoli Storage Manager server. One thing to keep in mind when you define the Tivoli Storage Manager client node, is to grant the authority to delete backup copies on the Tivoli Storage Manager server to that node. Important: If Tivoli Continuous Data Protection for Files does not have delete backup permission on the Tivoli Storage Manager server, it cannot successfully purge older files when the designated storage space is getting full or when the maximum number of versions per file defined to be stored on the remote storage location is exceeded. For demonstration purposes, we register node name florence - which is the host name of the computer hosting the Tivoli Continuous Data Protection for Files client - using password cdp4tsm without granting delete backup permission to that node (see Example 5-1).
Example 5-1 Registering node florence without delete backup permission (register node)
tsm: ITSO_TSM>register node florence cdp4tsm Session established with server ITSO_TSM: Windows Server Version 5, Release 4, Level 0.0 Server date/time: 05/10/2007 16:57:03 Last access: 05/10/2007 15:27:11 ANR2060I Node FLORENCE registered in policy domain STANDARD. ANR2099I Administrative userid FLORENCE defined for OWNER access to node FLORENCE.
316
Example 5-2 shows the details of node florence without delete backup permission (Backup Delete Allowed?: No).
Example 5-2 Details of node florence without delete backup permission (query node)
tsm: ITSO_TSM>query node florence f=d Node Name: Platform: Client OS Level: Client Version: Policy Domain Name: Last Access Date/Time: Days Since Last Access: Password Set Date/Time: Days Since Password Set: Invalid Sign-on Count: Locked?: Contact: Compression: Archive Delete Allowed?: Backup Delete Allowed?: Registration Date/Time: Registering Administrator: Last Communication Method Used: Bytes Received Last Session: Bytes Sent Last Session: Duration of Last Session: Pct. Idle Wait Last Session: Pct. Comm. Wait Last Session: Pct. Media Wait Last Session: Optionset: URL: Node Type: Password Expiration Period: Keep Mount Point?: Maximum Mount Points Allowed: Auto Filespace Rename : Validate Protocol: TCP/IP Name: TCP/IP Address: Globally Unique ID: Transaction Group Max: Data Write Path: Data Read Path: FLORENCE (?) (?) (?) STANDARD 05/10/2007 16:57:03 <1 05/10/2007 16:57:03 <1 0 No Client Yes No 05/10/2007 16:57:03 ADMIN 0 0 0.00 0.00 0.00 0.00
Client No 1 No No
0 ANY ANY
317
Session Initiation: ClientOrServer High-level Address: Low-level Address: Collocation Group Name: Proxynode Target: Proxynode Agent: Node Groups: Email Address: When Tivoli Continuous Data Protection for Files contacts the Tivoli Storage Manager server for the first time with a valid node name, Tivoli Continuous Data Protection for Files opens a new Web browser prompting you to enter the password to identify Tivoli Continuous Data Protection for Files to the Tivoli Storage Manager server (see Figure 5-62).
Figure 5-62 Tivoli Continuous Data Protection for Files prompting for a password to access the Tivoli Storage Manager server
318
In the Windows system event log - for how to access the Windows system event log refer to Windows system event log on page 267 - you see an event log entry (Event ID: 6091) generated due to the missing password which is needed to access the Tivoli Storage Manager server (see Figure 5-63).
Figure 5-63 Informational entry in the event log (password information needed)
After you have entered the same password you used when defining the node name on the Tivoli Storage Manager server (in our example cdp4tsm) and click OK, the Web browser window can be closed. Note: The password will be stored encrypted in a special file for that remote backup target in the \pwd\ folder in the data directory of Tivoli Continuous Data Protection for Files. A second entry in the Windows system event log is created after you have entered the password. At this time, Tivoli Continuous Data Protection for Files logs into the Tivoli Storage Manager server for the first time using the Tivoli Storage Manager API, checking if the node has sufficient permissions. As this is not true (Backup Delete Allowed?: No), a FilePath ERROR is logged with Event ID: 6000 in the Windows system event log (see Figure 5-64 on page 320).
319
Figure 5-64 Event log entry due to insufficient permission to delete backed up data
Note: Return code (RC) 27 is defined as DSM_RC_ABORT_NOT_AUTHORIZED, which translates to You cannot delete the file space data unless your Tivoli Continuous Data Protection for Files administrator has authorized your node to do so. Authorization permits you to delete backup data, archive data, or both. For more information about Tivoli Storage Manager API return codes and their definition, refer to Tivoli Storage Manager: Using the Application Program Interface, SC32-0147.
Figure 5-65 on page 321 displays the entries in the diserror.log (Tivoli Storage Manager API error log file).
320
05/10/2007 16:59:29 ANS1025E Session rejected: Authentication failure 05/10/2007 16:59:54 ANS1126E The file space cannot be deleted because this node does not have permission to delete archived or backed up data.
Figure 5-65 Error messages in dsierror.log due to insufficient permissions to delete backed up data
The first message (ANS1025E) is expected because at the very first contact of Tivoli Continuous Data Protection for Files with the Tivoli Storage Manager server there is no password for authentication available yet, leading to the session rejected error message. After you have entered the correct password when prompted to do so, this message does not display again. The second message (ANS1126E) is caused due to Tivoli Continuous Data Protection for Files (respectively its node name) lacking the authority to delete backup copies on the Tivoli Storage Manager server. Important: At this time, Tivoli Continuous Data Protection for Files stores files on the Tivoli Storage Manager server without any further error message indicating that the node does not have sufficient delete backup copies permissions - until your designated storage space is full or when the maximum number of versions per file defined to be stored on the remote storage location is exceeded. If this happens, Tivoli Continuous Data Protection for Files cannot successfully purge older files on the Tivoli Storage Manager server. A series of entries in the Windows system event log will be created when Tivoli Continuous Data Protection for Files tries to store more files on the remote backup location (Tivoli Storage Manager server) as defined in the Remote Storage page of the Settings Notebook. At first, for each file which is getting stored, two FilePath ERROR with Event ID: 6000 get reported in the Windows system event log (see Figure 5-66 on page 322).
321
Figure 5-66 Event log entry when storing more versions of files as defined on remote storage location
Also, Event ID: 6086 is created as the replication engine of Tivoli Continuous Data Protection for Files is not able to unlink the (old) versioned file (see Figure 5-67 on page 323).
322
Figure 5-67 Tivoli Continuous Data Protection for Files unable to unlink the file (Event ID: 6086)
The purge of older versioned files is not possible due to no authority to delete backup copies on the Tivoli Storage Manager server as reported by Event ID: 6000 in the Windows system event log (see Figure 5-68 on page 324).
323
Figure 5-68 FilePath ERROR entry (Event ID: 6000) in event log due to a permission problem
Due to Tivoli Continuous Data Protection for Files being unavailable to purge files on the Tivoli Storage Manager server, the file purge_failed.log is created, or a replication-status entry message is appended to that file if it already exists. For more information about the log files used by Tivoli Continuous Data Protection for Files, refer to 5.3.2, Tivoli Continuous Data Protection for Files logs on page 348. File purge_failed.log contains a replication-status message, that Tivoli Continuous Data Protection for Files failed (lastStatus="FAIL") to unlink (action="Unlink") file florence.txt-FP1178834646.txt ((src="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt-FP1178834646.txt") and (dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt-FP1178834646.txt")) on Tivoli Storage Manager server Helsinki (see Figure 5-69 on page 325).
324
<replication-status when="2007-05-10 17:05:01" lastStatus="FAIL" explanation="Purge" errValue="5079" errMnemonic="DSTEPERM" action="Unlink" src="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt-FP1178834646.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt-FP1178834646.txt" size="3" priority="5" time="1178834701" ID="589417085500000185"/>
Figure 5-69 Entry in file purge_failed.log
Each - unsuccessful - try to purge a file on the Tivoli Storage Manager server is causing error message ANS1126E to appear in the diserror.log (see Figure 5-70). 05/10/2007 17:05:01 ANS1126E The file space does not have permission to delete archived 05/10/2007 17:05:01 ANS1126E The file space does not have permission to delete archived cannot be or backed cannot be or backed deleted because this node up data. deleted because this node up data.
Figure 5-70 File dsierror.log with error messages ANS1126E
Important: Even if the defined maximum number of versions per file is exceeded, or the designated storage space is exhausted, Tivoli Continuous Data Protection for Files does still backup files to the Tivoli Storage Manager in case of missing delete backup authority. As Tivoli Continuous Data Protection for Files appends to each versioned file a unique file identifier, for instance florence.txt-FP11-78834646.txt, each version of the same file is treated as a different (new) file and therefore as an active object by the Tivoli Storage Manager server. This can lead to tremendous problems as the number of active objects can increase dramatically and - due to their active state - are not deleted by a Tivoli Storage Manager server expire inventory process. Also the storage on disk or tape pools used by the Tivoli Storage Manager server can grow rapidly in such a case. Example 5-3 on page 326 shows the output of a select command against the Tivoli Storage Manager server backups table. Note that we have originally defined only two versions (see Figure 5-57 on page 313) to be kept on the remote storage location, but the output of the select command shows seven active versions (six versioned and one un-versioned) of the file florence.txt.
325
Example 5-3 Select command output displaying too much active versions of a file
tsm: ITSO_TSM>select node_name,state,ll_name from backups where node_name='FLORENCE' and ll_name like '%florence%' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y NODE_NAME -----------------FLORENCE FLORENCE FLORENCE FLORENCE FLORENCE FLORENCE FLORENCE FLORENCE STATE -----------------ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION LL_NAME -----------------florence florence.txt florence.txt-FP1178834630.txt florence.txt-FP1178834646.txt florence.txt-FP1178834663.txt florence.txt-FP1178834698.txt florence.txt-FP1178834705.txt florence.txt-FP1178834711.txt
Solution:
To avoid such a situation, you need to either register the node name on the Tivoli Storage Manager server using the backdelete=yes parameter with the register node command (see Example 5-4) or, if the node has already been registered, use the update node command and specify the backdelete=yes parameter (see Example 5-5).
Example 5-4 Register node florence with backdelete=yes parameter (register node)
tsm: ITSO_TSM>register node florence cdp4tsm backdelete=yes ANR2060I Node FLORENCE registered in policy domain STANDARD. ANR2099I Administrative userid FLORENCE defined for OWNER access to node FLORENCE.
Example 5-5 Update existing node florence with backdelete=yes parameter (update node)
tsm: ITSO_TSM>update node florence backdelete=yes ANR2063I Node FLORENCE updated.
326
Example 5-6 shows the details of node florence with delete backup permission (Backup Delete Allowed?: Yes).
Example 5-6 Details of node florence with delete backup permission (query node)
tsm: ITSO_TSM>query node florence f=d Node Name: Platform: Client OS Level: Client Version: Policy Domain Name: Last Access Date/Time: Days Since Last Access: Password Set Date/Time: Days Since Password Set: Invalid Sign-on Count: Locked?: Contact: Compression: Archive Delete Allowed?: Backup Delete Allowed?: Registration Date/Time: Registering Administrator: Last Communication Method Used: Bytes Received Last Session: Bytes Sent Last Session: Duration of Last Session: Pct. Idle Wait Last Session: Pct. Comm. Wait Last Session: Pct. Media Wait Last Session: Optionset: URL: Node Type: Password Expiration Period: Keep Mount Point?: Maximum Mount Points Allowed: Auto Filespace Rename : Validate Protocol: TCP/IP Name: TCP/IP Address: Globally Unique ID: Transaction Group Max: Data Write Path: Data Read Path: FLORENCE (?) (?) (?) STANDARD 05/10/2007 17:16:43 <1 05/10/2007 17:16:43 <1 0 No Client Yes Yes 05/10/2007 17:16:43 ADMIN 0 0 0.00 0.00 0.00 0.00
Client No 1 No No
0 ANY ANY
327
Session Initiation: ClientOrServer High-level Address: Low-level Address: Collocation Group Name: Proxynode Target: Proxynode Agent: Node Groups: Email Address: If you have registered or updated a node using the required backdelete=yes parameter, Tivoli Continuous Data Protection for Files is able to successfully purge files on the Tivoli Storage Manager server. Example 5-7 shows the output of a select command run against the Tivoli Storage Manager server backups table displaying active and inactive versions of the file florence.txt. The formerly active versions of this file have been purged successfully by Tivoli Continuous Data Protection for Files now becoming an inactive version.
Example 5-7 Select command output displaying active and inactive versions of a file
tsm: ITSO_TSM>select node_name,state,ll_name from backups where node_name='FLORENCE' and ll_name like '%florence%' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y NODE_NAME -----------------FLORENCE FLORENCE FLORENCE FLORENCE FLORENCE STATE -----------------ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION INACTIVE_VERSION INACTIVE_VERSION LL_NAME -----------------florence florence.txt florence.txt-FP1178835759.txt florence.txt-FP1178835715.txt florence.txt-FP1178835740.txt
To eliminate inactive versions of files from the Tivoli Storage Manager server database, you need to run the expire inventory command (see Example 5-8).
Example 5-8 Running expiration on the Tivoli Storage Manager server (expire inventory)
tsm: ITSO_TSM>expire inventory
328
ANS8003I Process number 17 started. In Example 5-9 you can see, that the inactive versions have now been deleted from the Tivoli Storage Manager server database.
Example 5-9 Select command output after running expiration (only active versions)
tsm: ITSO_TSM>select node_name,state,ll_name from backups where node_name='FLORENCE' and ll_name like '%florence%' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y NODE_NAME -----------------FLORENCE FLORENCE FLORENCE STATE -----------------ACTIVE_VERSION ACTIVE_VERSION ACTIVE_VERSION LL_NAME -----------------florence florence.txt florence.txt-FP1178835759.txt
Tivoli Storage Manager client sessions disabled

There are many reasons, for example to perform maintenance on the Tivoli Storage Manager server, that a Tivoli Storage Manager server administrator does not want Tivoli Storage Manager client sessions to temporarily access the Tivoli Storage Manager server. He can prevent incoming Tivoli Storage Manager client sessions using the disable sessions client command on the Tivoli Storage Manager server. Example 5-10 displays the output from a query status command showing that the Tivoli Storage Manager server has been disabled for incoming Tivoli Storage Manager sessions (Availability: Enabled for Admin and Server sessions).
Example 5-10 Tivoli Storage Manager client sessions disabled on Tivoli Storage Manager server (query status)
tsm: ITSO_TSM>query status Storage Management Server for Windows - Version 5, Release 4, Level 0.0
Server Name: Server host name or IP address: Server TCP/IP port number: Crossdefine:
ITSO_TSM 9.3.5.52 1500 Off
329
Server Password Set: Server Installation Date/Time: Server Restart Date/Time: Authentication: Password Expiration Period: Invalid Sign-on Attempt Limit: Minimum Password Length: Registration: Subfile Backup: Availability: sessions
No 05/03/2007 20:05:21 05/10/2007 18:58:10 On 90 Day(s) 0 0 Closed No Enabled for Admin and Server
Accounting: On Activity Log Retention: 1 Day(s) Activity Log Number of Records: 1497 Activity Log Size: <1 M Activity Summary Retention Period: 30 Day(s) License Audit Period: 30 Day(s) Last License Audit: 05/15/2007 06:58:10 Server License Compliance: Valid Central Scheduler: Active Maximum Sessions: 25 Maximum Scheduled Sessions: 12 Event Record Retention Period: 10 Day(s) Client Action Duration: 5 Day(s) Schedule Randomization Percentage: 50 Query Schedule Period: 6 Hour(s) Maximum Command Retries: 10 Retry Period: 5 Minute(s) Scheduling Modes: Any Log Mode: Normal Database Backup Trigger: Not Defined BufPoolSize: 32,680 K Active Receivers: CONSOLE ACTLOG NTEVENTLOG Configuration manager?: Off Refresh interval: 60 Last refresh date/time: Context Messaging: Off Server-free Status: On Server-free Batch Size: 200 Table of Contents (TOC) Load Retention: 120 Minute(s) Machine Globally Unique ID: ec.10.51.80.64.1a.11.d9.b6.b1.00.11.09.9b.97.40 Archive Retention Protection: Off Encryption Strength: AES
330
Under this condition, Tivoli Continuous Data Protection for Files cannot successfully backup files to the Tivoli Storage Manager server using the Tivoli Storage Manager API as the incoming connection is rejected by the Tivoli Storage Manager server. As this is not transparent to Tivoli Continuous Data Protection for Files, it still tries to store files on the Tivoli Storage Manager if they were changed on the local system. If Tivoli Continuous Data Protection for Files wants to send a file to a Tivoli Storage Manager server with Tivoli Storage Manager client sessions being disabled, a window shows up informing you that the target location is not responding properly (see Figure 5-71).
Figure 5-71 Target location (Helsinki) is not responding properly (window)
The explanation why the remote backup target does not respond properly, can be found in the Windows system event log. An error Event ID: 6000 is generated because the session was rejected by the Tivoli Storage Manager server due to the disabled Tivoli Storage Manager client sessions (see Figure 5-72 on page 332).
331
Figure 5-72 Entry in event log due to session being rejected from Tivoli Storage Manager server
Note: Return code (RC) 55 is defined as DSM_RC_REJECT_SERVER_DISABLED, which translates to The server is in a disabled state and cannot be accessed for normal activity. For more information about Tivoli Storage Manager API return codes and their definition, refer to Tivoli Storage Manager: Using the Application Program Interface, SC32-0147. The same error message (ANS1355E) is also written into the error log file (dsierror.log) of Tivoli Storage Manager API client (see Figure 5-73). 05/10/2007 17:33:12 ANS1355E Session rejected: Server disabled
Figure 5-73 ANS1355E message in dsierror.log file (session rejected)
Along with the Event ID: 6000 message, a second event (Event ID: 6086) will be written into the Windows system event log (see Figure 5-74 on page 333).
332
Figure 5-74 Replication engine unable to copy the file (Event ID: 6086)
This error event has been caused, as the replication engine of Tivoli Continuous Data Protection for Files could not copy the locally changed file successfully to the Tivoli Storage Manager server. Replication problems and errors are written into specific log files used by Tivoli Continuous Data Protection for Files. See 5.3.2, Tivoli Continuous Data Protection for Files logs on page 348 for more information about the Tivoli Continuous Data Protection for Files logs. In this case, file replication-failed.5 is created, or - if it already exists - a new entry is appended to the replication-failed.5 file (see Figure 5-75 on page 334).
333
<replicate when="2007-05-10 17:33:12" lastStatus="FAIL" explanation="Unable to access the specified file" errValue="0" errMnemonic="SUCCESS" action="Copy" src="C:\Documents and Settings\Administrator\My Documents\florence.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt" size="2" priority="5" time="1178836392" ID="589417836500000315"/>
Figure 5-75 Entry in file replication-failed.5
It contains a replication entry, that the backup (action="Copy") of file florence.txt (src="C:\Documents and Settings\Administrator\My Documents\florence.txt") to Tivoli Storage Manager server Helsinki (dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt") was not possible (lastStatus="FAIL").
Solution:
For Tivoli Continuous Data Protection for Files to be able to backup files to the Tivoli Storage Manager server again, the Tivoli Storage Manager server administrator needs to allow Tivoli Storage Manager client sessions to access the Tivoli Storage Manager server. This can be done using the enable sessions client command (see Example 5-11).
Example 5-11 Enable Tivoli Storage Manager client sessions again (enable sessions)
tsm: ITSO_TSM>enable sessions client ANR2552I Server now enabled for Client access. The query status output when Tivoli Storage Manager clients sessions are enabled again can be seen in Example 5-12 (Availability: Enabled).
Example 5-12 Tivoli Storage Manager client sessions enabled on IBM Tivoli Storage Manager server (query status)
tsm: ITSO_TSM>query status Storage Management Server for Windows - Version 5, Release 4, Level 0.0
Server Name: Server host name or IP address: Server TCP/IP port number: Crossdefine: Server Password Set:
ITSO_TSM 9.3.5.52 1500 Off No
334
Server Installation Date/Time: 05/03/2007 20:05:21 Server Restart Date/Time: 05/10/2007 18:58:10 Authentication: On Password Expiration Period: 90 Day(s) Invalid Sign-on Attempt Limit: 0 Minimum Password Length: 0 Registration: Closed Subfile Backup: No Availability: Enabled Accounting: On Activity Log Retention: 1 Day(s) Activity Log Number of Records: 1500 Activity Log Size: <1 M Activity Summary Retention Period: 30 Day(s) License Audit Period: 30 Day(s) Last License Audit: 05/15/2007 06:58:10 Server License Compliance: Valid Central Scheduler: Active Maximum Sessions: 25 Maximum Scheduled Sessions: 12 Event Record Retention Period: 10 Day(s) Client Action Duration: 5 Day(s) Schedule Randomization Percentage: 50 Query Schedule Period: 6 Hour(s) Maximum Command Retries: 10 Retry Period: 5 Minute(s) Scheduling Modes: Any Log Mode: Normal Database Backup Trigger: Not Defined BufPoolSize: 32,680 K Active Receivers: CONSOLE ACTLOG NTEVENTLOG Configuration manager?: Off Refresh interval: 60 Last refresh date/time: Context Messaging: Off Server-free Status: On Server-free Batch Size: 200 Table of Contents (TOC) Load Retention: 120 Minute(s) Machine Globally Unique ID: ec.10.51.80.64.1a.11.d9.b6.b1.00.11.09.9b.97.40 Archive Retention Protection: Off Encryption Strength: AES
335
Tivoli Storage Manager server unavailable

It can happen, that the Tivoli Storage Manager cannot be reached at all by any Tivoli Storage Manager client, for example, if the Tivoli Storage Manager server had been shutdown completely. This condition is not transparent to Tivoli Continuous Data Protection for Files, so it tries sending files to the Tivoli Storage Manager server if they have been changed locally on the computer, using the Tivoli Storage Manager API. If the remote backup target cannot be reached at all, Tivoli Continuous Data Protection for Files informs you about this condition with a message in the notification area (see Figure 5-76).
Figure 5-76 Informational message about the network target being not reachable
Tivoli Continuous Data Protection for Files assumes, that this is only a transient condition (see 5.2.5, Transient conditions (remote storage location not reachable) on page 343 for more information) and re-tries to establish the connection to the remote backup target (Tivoli Storage Manager server Helsinki). File dsierror.log contains several TCP/IP error messages, that no connection to the Tivoli Storage Manager server could be established (see Figure 5-77). 05/10/2007 17:45:39 ANS5216E Could not establish a TCP/IP connection with address 'helsinki:1500'. The TCP/IP error is 'Unknown error' (errno = 10061). 05/10/2007 17:45:39 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 05/10/2007 17:45:39 ANS1017E Session rejected: TCP/IP connection failure 05/10/2007 17:45:49 ANS5216E Could not establish a TCP/IP connection with address 'helsinki:1500'. The TCP/IP error is 'Unknown error' (errno = 10061). 05/10/2007 17:45:49 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -50. 05/10/2007 17:45:49 ANS1017E Session rejected: TCP/IP connection failure
Figure 5-77 TCP/IP connection error messages in file dsierror.log
About every 10 seconds Tivoli Continuous Data Protection for Files tries to re-establish a connection with the remote storage location for continuous data protection.
336
The unavailability of the Tivoli Storage Manager server on the network is also causing an entry being generated in the Windows event log (Event ID: 6069) as the replication daemon detects that kind of network error condition (see Figure 5-78).
Figure 5-78 Event log entry caused by the network target being not available (Event ID: 6069)
As Tivoli Continuous Data Protection for Files is unable to replicate files being changed to the Tivoli Storage Manager server, it tracks the changed files in special replication log files. Refer to 5.3.2, Tivoli Continuous Data Protection for Files logs on page 348 for more information about the log files used by Tivoli Continuous Data Protection for Files. Here, the files replication-active.5 and replication-queue.5 get created. Usually these files are only available temporarily, but in case of the remote storage being unavailable these files will stay active until the remote backup destination can be accessed again (see Figure 5-79 on page 338 and Figure 5-80 on page 338).
337
<replicate when="2007-05-10 17:45:30" lastStatus="QUEUED" action="Copy" src="C:\Documents and Settings\Administrator\My Documents\florence.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt" size="13" priority="5" time="1178837130" ID="589418378000000235"/>
Figure 5-79 Entry in file replication-active.5
<replicate when="2007-05-10 17:45:39" lastStatus="QUEUED" action="Copy" src="C:\Documents and Settings\Administrator\My Documents\florence.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt" size="14" priority="5" time="1178837139" ID="589418378000000255"/> <replicate when="2007-05-10 17:45:53" lastStatus="QUEUED" action="Copy" src="C:\Documents and Settings\Administrator\My Documents\florence.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt" size="15" priority="5" time="1178837153" ID="589418378000000275"/> <replicate when="2007-05-10 17:46:30" lastStatus="QUEUED" action="Copy" src="C:\Documents and Settings\Administrator\My Documents\florence.txt" dst="tsm://helsinki\RealTimeBackup\florence\C\Documents and Settings\Administrator\My Documents\florence.txt" size="16" priority="5" time="1178837190" ID="589418378000000295"/>
Figure 5-80 Entries in file replication-queue.5
The main difference between those two files is, that the first change of a file will be tracked in file replication-active.5, as during the active replication process Tivoli Continuous Data Protection for Files detected that the remote backup location was not available and therefore could not replicate this file. All other changes of the same file - if it will be changed multiple times during the transient network condition - will be logged (queued) in file replication-queue.5 for replication at a later time once the remote storage location becomes available again.
338
Attention: Note that each replicate entry (lastStatus="QUEUED") in file replication-queue.5 refers to the same file name (src="C:\Documents and Settings\Administrator\My Documents\florence.txt"). Also be aware that Tivoli Continuous Data Protection for Files has no local cache to store different versions of the same file if it is changed repeatedly while the remote target is unavailable. So if you made changes to the same file multiple times when the Tivoli Storage Manager server was (temporarily) unavailable, only the latest version of this file will be copied over to the Tivoli Storage Manager server after it becomes available again.
Solution:
For Tivoli Continuous Data Protection for Files to be able to backup files to the Tivoli Storage Manager server, the Tivoli Storage Manager server needs to be started by the Tivoli Storage Manager server administrator. If the Tivoli Storage Manager server is up and running again, Tivoli Continuous Data Protection for Files will back up the files which have been changed while the Tivoli Storage Manager server was unavailable and will continue to store newly changed files on the Tivoli Storage Manager server.
Conflicting include/exclude lists

Both Tivoli Continuous Data Protection for Files and the Tivoli Storage Manager (API) manage files or directories for backup services based on include/exclude lists. This can lead to potential conflicts between Tivoli Continuous Data Protection for Files and the Tivoli Storage Manager API, for example, if a file is included in Tivoli Continuous Data Protection for Files for continuous protection but is excluded by the Tivoli Storage Manager API client from being stored on the Tivoli Storage Manager server. Note: For details about how to include files, directories, or both for protection, or how to exclude them from protection in Tivoli Continuous Data Protection for Files, refer to Files to Protect page on page 79. By design, the Tivoli Storage Manager (API) backs up any file that is not excluded. This can be done either in the Tivoli Storage Manager API client options file (dsm.opt) or on the Tivoli Storage Manager server (for multiple Tivoli Storage Manager clients together) using a client option set. We do not discuss the latter option here. For more information about defining a client option set,
339
refer to Chapter 5, Administrative Commands, in IBM Tivoli Storage Manager for Windows: Administrators Reference, SC32-0127. Important: The default Tivoli Storage Manager API options file dsm.opt (see Figure 5-56 on page 310) as used by Tivoli Continuous Data Protection for Files, does not contain any include/exclude statement, so all files will be backed up by the Tivoli Storage Manager API. We do recommend to specify files and folders to be backed up in the include/exclude list of Tivoli Continuous Data Protection for Files only, and not to use separate or additional include/exclude statements in the dsm.opt file of the Tivoli Storage Manager API. In this case, Tivoli Continuous Data Protection for Files controls which files will be backed up (or not) and no potential conflicts between different include/exclude lists will occur. You can add various include or exclude statements into the dsm.opt file. For full details about possible include/exclude statements and their syntax, refer to Chapter 2, Configuring Tivoli Storage Manager, in Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and Users Guide, SC32-0146. However, adding include/exclude statements into the dsm.opt might also lead to conflicts with the include/exclude list Tivoli Continuous Data Protection for Files is using. This is the reason why we do not recommend using include/exclude statements in the dsm.opt file for Tivoli Continuous Data Protection for Files implementations. As shown in our configuration example in Figure 3-22 on page 80, we defined all files in the \My Documents\ folder as files being protected continuously by Tivoli Continuous Data Protection for Files. Figure 5-81 shows the modified file dsm.opt we use in this example. Note that we added an exclude statement (Exclude "*:\...\*.txt"), which excludes all files with extension *.txt from being backed up by the Tivoli Storage Manager API. COMMMETHOD PASSWORDACCESS EXCLUDE TCPip generate *:\...\*.txt
Figure 5-81 Modified dsm.opt file containing an exclude statement for *.txt files
340
If we edit, for example, file florence.txt in the directory C:\Documents and Settings\Administrator\My Documents and save the changes, Tivoli Continuous Data Protection for Files tries to send the changed file to the Tivoli Storage Manager server using the Tivoli Storage Manager API. This fails, that is, the changed file florence.txt is not sent to the Tivoli Storage Manager server. The reason is we excluded all files ending with *.txt from being backed up by the Tivoli Storage Manager API according to the exclude statement in the dsm.opt file. In the Windows system event log you see an event log entry (Event ID: 6000) generated due to file florence.txt being excluded from backup (see Figure 5-82).
Figure 5-82 Entry in event log due to file being excluded from backup (Event ID: 6000)
Note: Return code (RC) 185 is defined as DSM_RC_TL_EXCLUDED, which translates to You cannot back up, archive, or migrate files that are excluded. For more information about Tivoli Storage Manager API return codes and their definition, refer to Tivoli Storage Manager: Using the Application Program Interface, SC32-0147.
341
Beside the Event ID: 6000 message, a second event (Event ID: 6086) will be written into the Windows system event log (see Figure 5-83).
Figure 5-83 Replication engine unable to copy the file (Event ID: 6086)
This error event has been caused, as the replication engine of Tivoli Continuous Data Protection for Files could not copy the locally changed file successfully to the Tivoli Storage Manager server. In the dsierror.log file a warning message (ANS1115W) will be reported, that a file had been excluded from backup due to the include/exclude list (Figure 5-84 on page 343). Note: The file name is missing in the ANS1115W warning message. You need to check the Windows system event log for error messages with the same timestamp as the ANS1115W message to see what file actually is excluded from backups and therefore causing this entry in the dsierror.log file.
342
05/15/2007 14:43:43 ANS1115W File '' excluded by Include/Exclude list

Figure 5-84 ANS1115W warning message in dsierror.log (excluded file)
Attention: Files excluded from backup by a Tivoli Storage Manager API include/exclude list will not be sent to the Tivoli Storage Manager server even if they are included for protection in Tivoli Continuous Data Protection for Files.
Solution:
In order to avoid such include/exclude conflicts between Tivoli Continuous Data Protection for Files and the Tivoli Storage Manager API, do not use any include/exclude statements in the dsm.opt file of the Tivoli Storage Manager API client. Instead, use Tivoli Continuous Data Protection for Files to specify which files and folders to protect (include) and which not (exclude) - even when using the Tivoli Storage Manager API to store files on a Tivoli Storage Manager server.
5.2.5 Transient conditions (remote storage location not reachable)

Replication problems due to transient conditions (remote storage location temporarily not reachable) can have a variety of different causes. The result is, that the remote location (external device, file server, Web server (WebDAV), or Tivoli Storage Manager server) cannot be accessed and therefore Tivoli Continuous Data Protection for Files fails replicating to this backup target. Several common issues are: The external disk is not plugged into your computer. Your own system is not connected to the network (for example, when you work from home and are not logged on to your companys network). The network has a problem (for example, a router/switch/hub is defective). The file-, WebDAV-, or Tivoli Storage Manager server is unavailable (for example, due to maintenance work). If the remote backup location is not reachable when Tivoli Continuous Data Protection for Files tries to replicate to it, you will see the notification message shown in Figure 5-85 on page 344.
343
Figure 5-85 Remote storage location not reachable (notification message)
Note: Even if you are using an external device (disk) as your remote storage location, you will see this notification message informing about the network target not being reachable in the case when you have an unconnected external device. At the same time, the Tivoli Continuous Data Protection for Files Status page shows the current inaccessibility of your remote storage by turning the color of the Remote Storage icon from blue to yellow with a little exclamation mark (see Figure 5-86 on page 345).
344
Figure 5-86 Remote storage location inaccessible (Status page)
Attention: Tivoli Continuous Data Protection for Files will keep track of the changes you make to your files even when you see this message. It will wait for some time and try to replicate the changed file(s) later again, as this might be only a temporary condition. If you change the same file multiple times when your remote storage area is temporarily unavailable, only the latest version of this file will be copied over to the remote storage location when it becomes available again. Once the remote storage location can be reached again, you will be notified about this event by Tivoli Continuous Data Protection for Files (see Figure 5-87 on page 346) and replication will continue.
345
Figure 5-87 Remote storage location reachable again (notification message)
Finally, the Remote Storage icon in the Status page of the Tivoli Continuous Data Protection for Files user interface turns back to blue again (see Figure 5-88).
Figure 5-88 Remote storage location accessible again (Status page)
346
5.3 System operation and log files

The following section provides some information about important system operation and log files used by Tivoli Continuous Data Protection for Files and the Tivoli Storage Manager application programming interface (API). An in-depth discussion about the log files and their structure will not take place here, as this is not necessary for the daily use of Tivoli Continuous Data Protection for Files. Anyhow, a general understanding of these log files might be of interest for deeper problem determination and troubleshooting. The log files are created, transparently to the user, in the data directory while the other system operation files - except for fpa.txt, which is in the data directory, too - can be found in the installation directory of Tivoli Continuous Data Protection for Files. Refer to 3.4.1, Installation and data directories on page 108 for more information about the directories used by Tivoli Continuous Data Protection for Files.
5.3.1 Tivoli Continuous Data Protection for Files system operation files
For Tivoli Continuous Data Protection for Files to function, there are several system operation files necessary. Table 5-3 displays the most important system operation files used by Tivoli Continuous Data Protection for Files.
Table 5-3 Important system operation files2 File name fp.sys Description File fp.sys is the driver which loads when the computer boots up. It is located in the \%WINDIR%\System32\Drivers directory. FilePathSrv.exe is the daemon, or process which starts as a service (name: CDPforFilesSrv). If you are running in regular user mode, this service will stop right away, until it has something to do. If you are running in service-mode, the service will stay active.
FilePathSrv.exe
The file fpa.txt is located in the data directory while all other system operating files will be found in the installation directory of Tivoli Continuous Data Protection for Files.
347
File name fpa.exe
Description File fpa.exe is the command line, interactive program which passes commands to the kernel. It can, for example, be used to set tracing levels or to change underlying Tivoli Continuous Data Protection for Files settings. The fpa.txt file is the database where main rules and some configuration information is stored.
fpa.txt
5.3.2 Tivoli Continuous Data Protection for Files logs

Tivoli Continuous Data Protection for Files uses various logs for reporting or tracking its activities. Those log files are explained in this section of the chapter. Note: You might not find all of the mentioned logs in your Tivoli Continuous Data Protection for Files data directory, as some of the log files are only used temporarily while others depend on how you have configured Tivoli Continuous Data Protection for Files.
Installation log file

In Table 5-4, you can see the log file being created during installation of Tivoli Continuous Data Protection for Files. It is helpful in case you have trouble getting Tivoli Continuous Data Protection for Files installed on your system.
Table 5-4 Installation log file Log file name fpinstall.log Description The file fpinstall.log contains the installation information fromTivoli Continuous Data Protection for Files.
348
Tip: If you have trouble installing Tivoli Continuous Data Protection for Files, it is recommended trying to install Tivoli Continuous Data Protection for Files using the verbose logging possibility (/l*v path and file name) of the Microsoft Windows Installer. This allows IBM support personnel to check the given log file too, for the reason of the installation failure. For more information about Tivoli Continuous Data Protection for Files installation using command-line parameters, refer to 3.2.1, Installation using command-line parameters on page 65.
Replication logs
The log files regarding the replication activities of Tivoli Continuous Data Protection for Files are explained in Table 5-5.
Table 5-5 Replication logs Log file name replication.log Description The log file replication.log contains the last replication transactions (limited in size to 1.3 MB). Queued replication transactions are written into file replication-queue.N. File replication-active.N contains the currently active replication transactions. Failed replication transactions are reported in log file replication-failed.N (not limited in size).
replication-queue.N (where N=0...9) replication-active.N (where N=0...9) replication-failed.N (where N=0...9)
E-mail and scheduled protection logs

Table 5-6 summarizes the various log files used when e-mail and/or scheduled protection has been enabled in the E-mail Protection page of the Settings Notebook in the Tivoli Continuous Data Protection for Files user interface.
Table 5-6 Scheduled protection logs Log file name ChangeJournal.log Description The file ChangeJournal.log does contain a list of all files pending for scheduled processing. Currently processed files are reported in file ChangeJournal.log_1_inprocess.
ChangeJournal.log_1_inprocess
349
Log file name ChangeJournal.log_2_last ChangeJournal.log_3_out ChangeJournal.log_LastSuccess
Description File ChangeJournal.log_2_last contains the last files being processed. ChangeJournal.log_3_out is empty. File ChangeJournal.log_LastSuccess contains the date and time of the last successful scheduled backup as seen in the E-mail Protection section of the My Files summary on the Tivoli Continuous Data Protection for Files Status page. File RemoteVersions.log holds an entry for each versioned file stored at the remote target. Files that appear unreachable during purge are reported in file purge_struggled.log if this looks like a temporary (restartable) condition. Files that appear unreachable during purge are reported in file purge_failed.log if this is a permanent (non-restartable) condition.
RemoteVersions.log
purge_struggled.log
purge_failed.log
Local pool log file and \gendb\ directory

The local pool log file and the directory \gendb\ are explained in Table 5-7.
Table 5-7 Local pool log file and \gendb\ Log file name LocalPool.log \gendb\ (directory) Description The file LocalPool.log is a list of all files in the local file pool (backup area). The directory \gendb\ and its subdirectories respectively hold version names with dates to facilitate pruning based on the retention settings.
5.3.3 Tivoli Storage Manager specific log files

For storing files on a Tivoli Storage Manager server as a remote backup location, Tivoli Continuous Data Protection for Files is using the Tivoli Storage Manager application programming interface (API). The Tivoli Storage Manager API has its
350
own specific log file for reporting (error) messages in conjunction with a Tivoli Storage Manager server. Table 5-8 shows the log file used by the Tivoli Storage Manager API and its description.
Table 5-8 Tivoli Storage Manager API log file3 Log file name dsierror.log Description File dsierror.log contains (error) messages which arise when backing up files to a Tivoli Storage Manager server.
5.4 Tracing
For problem determination, Tivoli Continuous Data Protection for Files has a built-in tracing functionality. In this section, we will show you the basics of how to capture a Tivoli Continuous Data Protection for Files trace and a short tracing example. Important: Tracing facilities are used by Tivoli Continuous Data Protection for Files product development and IBM support personnel for diagnosing and debugging problems and should only be used when requested by them. These facilities are subject to change without notice and might vary depending upon the version and release of the product.
5.4.1 Before you start

In order to view the Tivoli Continuous Data Protection for Files trace output, you need to have DebugView for Windows installed. DebugView is a program to display both Win32 and kernel-mode debug output. It can be downloaded from the following Web site: http://www.microsoft.com/technet/sysinternals/utilities/DebugView.mspx For installation instructions and usage of DebugView, refer to the same URL.
The dsierror.log file of the Tivoli Storage Manager API used by Tivoli Continuous Data Protection for Files is located in the data directory of Tivoli Continuous Data Protection for Files.
351
5.4.2 How to run a trace

Tracing will be started using the FilePath agent (fpa) executable fpa.exe found in the installation directory of Tivoli Continuous Data Protection for Files. The FilePath agent is a configuration/reporting tool and a daemon. It can be run with command-line parameters (as commands) that will get processed and then exits/returns or in an interactive mode where it awaits user-typed commands and responds after each one. In our example (see 5.4.3, Tracing example on page 353), we will use the FilePath agent interactively. Note: See Chapter 2, Product architecture, planning, and deployment on page 19 to get more information about the FilePath agent (fpa.exe).
Trace syntax:
TRACE [level=FINE/MEDIUM/COARSE] [program=programname] [device=FILE/SCREEN] mask=BASIC,ALL,SYS,HOOK,HOOK_IO,FPA,REPLQ,REPLT,REPLK,REPLD,LOG,EXEC,AU DIT,FPL,FPL_OPEN,FPL_WRITE,FPL_CLOSE,FPL_LIST,FPL_META,HTML,HTML_SET,HT ML_GET,HTML_RESTORE,DEBUG1,XML,FPQ,METRIC,ERR,HASH,IOCTL,PF,FILE,LRP,AN ALFS,ANALFS_XML,ANALFS_FILES,EXPUNGE,FNAME,WORM,CAS,TABULATION,MIRROR_M ETA,MIRROR_IO,MIRROR_IOLIST,MIRROR_SIZE,MIRROR_DRAINER
Parameters:
level Specifies the granularity of trace messages being reported. FINE Specifies that all messages are logged. Attention: This might create a huge amount of output depending on the trace mask(s) being used. MEDIUM Specifies that the most important messages are logged. COARSE Specifies that only a few messages are logged. program Specifies to filter a particular programs interaction. programname
352
Specifies the name of the particular program to monitor. device Specifies the system logging target. FILE Specifies the system error log file as the logging target. Important: The system error log (file) of Windows operating systems is the Windows event log. Using device=FILE on Windows is not recommended, as the trace output would be written into the Windows system event log and flood it with a lot of error messages. SCREEN Specifies the current terminal device of the active process as the logging target. mask Specifies the trace mask(s). In case multiple trace masks are used, this is a comma separated list of trace masks.
5.4.3 Tracing example

The following section demonstrates how to capture a Tivoli Continuous Data Protection for Files trace. The trace mask we are using (mask=fpl_meta) in this example is to show how Tivoli Continuous Data Protection for Files iterates through the exclude and include list to check if a file needs to be processed or not. Important: Before activating the Tivoli Continuous Data Protection for Files trace, you need to execute the DebugView program by double-clicking the DebugView program file (dbgview.exe). DebugView will immediately start capturing debug output. Use the following steps to start the FilePath agent (see also Figure 5-89 on page 354): 1. Select Start Run, type cmd, and click OK. A Windows command-line window displays. 2. Change to the installation directory of Tivoli Continuous Data Protection for Files by entering cd \program files\tivoli\cdp_for_files. 3. To run the FilePath agent in interactive mode, enter fpa.
353
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>cd "\program files\tivoli\cdp_for_files" C:\Program Files\Tivoli\CDP_for_Files>fpa fpa>
Figure 5-89 FilePath agent in interactive mode
The fpa> command prompt indicates that you are now using the FilePath agent interactively. Enter, on the fpa> command prompt, the trace command, as seen in Figure 5-90, to start the trace: fpa>trace level=fine device=screen program=cmd.exe mask=fpl_meta
Figure 5-90 Command to start a Tivoli Continuous Data Protection for Files trace
By specifying the trace command parameter program=cmd.exe, we are filtering the trace for Windows command-line (cmd.exe) activities only. This helps us reduce the information being captured in the trace though we are using the finest trace granularity (level=fine). Select Start Run, type cmd, and click OK to open a second Windows command-line window. To trigger an activity, create a file that is defined in your Tivoli Continuous Data Protection for Files configuration as a file for continuous data protection (see Figure 3-22 on page 80), for example, by running echo test >> c:\file.doc, as shown in Figure 5-91. Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>echo test >> c:\file.doc C:\Documents and Settings\Administrator>
Figure 5-91 Create file.doc to trigger an activity
Immediately after you have issued the command, the DebugView program is capturing the trace (debug) output, as you can see in Figure 5-92 on page 355.
354
Figure 5-92 DebugView capturing the trace output
To end tracing, enter a trace command with an empty trace mask (see Figure 5-93). fpa>trace mask=""
Figure 5-93 Command to stop the trace
By entering quit or exit on the fpa> command prompt, you can leave the FilePath agent again (see Figure 5-94). fpa>quit C:\Program Files\Tivoli\CDP_for_Files>
Figure 5-94 Quitting the interactive mode of the FilePath agent
Example 5-13 shows an excerpt from the complete trace created by creating the file named file.doc. You can see that the complete file name (C:\file.doc) is decomposed into its components: the directory (C:\), the base (file), and the extension (.doc). Afterwards, the file name is first matched against the exclude and then against the include list. As we defined files with extension doc for continuous data protection, the latter one is a hit (IsMetaHit Result:1 TRUE), and the action is executed: file.doc is processed for continuous data protection.
Example 5-13 Tracing example (trace mask=fpl_meta)
000000730.00080263FPL_META isAppropriateRuleTime rule:Group0 writable:1 meta.when OpenRW isDir:0 meta.select:Dirs&Files 000000740.00080829FPL_META isAppropriateRuleTime4 Result:1 TRUE 000000750.00081805FPL_META isMetaHit rule:Group0 dir:C:\ base:file ext:.doc
355
000000760.00083456 FPL_META isHit fullname:C:\file.doc matchList:RealTimeBackup|\Program Files|\System32\|~|*.tmp|*.temp|\Temp\|\Temporary|\Windows\|\System Volume|\tsmlvsacache|\cache|\Tivoli\CDP_for_Files\ match:Contains 000000770.00084565 FPL_META isHit full:[C:\file.doc] item:[RealTimeBackup] 000000780.00085615 FPL_META isHit full:[C:\file.doc] item:[\Program Files] 000000790.00086663 FPL_META isHit full:[C:\file.doc] item:[\System32\] 000000800.00087668 FPL_META isHit full:[C:\file.doc] item:[~] 000000810.00088680 FPL_META isHit full:[C:\file.doc] item:[*.tmp] 000000820.00089753 FPL_META isHit full:[C:\file.doc] item:[*.temp] 000000830.00090779 FPL_META isHit full:[C:\file.doc] item:[\Temp\] 000000840.00091815 FPL_META isHit full:[C:\file.doc] item:[\Temporary] 000000850.00092845 FPL_META isHit full:[C:\file.doc] item:[\Windows\] 000000860.00093892 FPL_META isHit full:[C:\file.doc] item:[\System Volume] 000000870.00094931 FPL_META isHit full:[C:\file.doc] item:[\tsmlvsacache] 000000880.00095948 FPL_META isHit full:[C:\file.doc] item:[\cache] 000000890.00097032 FPL_META isHit full:[C:\file.doc] item:[\Tivoli\CDP_for_Files\] 000000900.00097675 FPL_META isHit Result:0 FALSE 000000910.00098192FPL_META IsMetaHit Result:0 FALSE 000000920.00099113FPL_META isAppropriateRuleTime rule:ChangeJournal writable:1 meta.when OpenRW isDir:0 meta.select:Dirs&Files 000000930.00099677FPL_META isAppropriateRuleTime4 Result:1 TRUE 000000940.00100675FPL_META isMetaHit rule:ChangeJournal dir:C:\ base:file ext:.doc 000000950.00101682 FPL_META isHit fullname:C:\file.doc matchList: match:Contains 000000960.00102353 FPL_META isHit Result:0 FALSE 000000970.00102866FPL_META IsMetaHit Result:0 FALSE 000000980.00103770FPL_META isAppropriateRuleTime rule:Group1 writable:1 meta.when OpenRW isDir:0 meta.select:Dirs&Files 000000990.00104336FPL_META isAppropriateRuleTime4 Result:1 TRUE 000001000.00105311FPL_META isMetaHit rule:Group1 dir:C:\ base:file ext:.doc 000001010.00106493 FPL_META isHit fullname:C:\file.doc matchList:\My Documents\|*.doc|*.xls|*.ppt|*.123| match:Contains 000001020.00107569 FPL_META isHit full:[C:\file.doc] item:[\My Documents\] 000001030.00108586 FPL_META isHit full:[C:\file.doc] item:[*.doc] 000001040.00109232 FPL_META isHit Result:1 TRUE 000001050.00109752FPL_META IsMetaHit Result:1 TRUE
356
Part 3
Part
Planning for a client engagement

In this part we discuss service engagement planning for Tivoli Continuous Data Protection for Files in general. The target audience of this chapter is Business Partners and Solution Developers. Important: The time estimates in this section are not representative of all the possible implementation scenarios of a Tivoli Continuous Data Protection for Files based solution. Each environment is considered as unique and the time estimates regarded as general guidelines, not absolute numbers.
357
358
Appendix A.
Project planning
This appendix describes the necessary planning steps that can help you in the deployment for small, medium or large environments. The information in the section is not applicable to implementation of Tivoli Continuous Data Protection for Files on a single user computer. It is more geared to multi-computer and enterprise wide deployments. The following topics are discussed: Required skills on page 360 Solution description on page 361 Solution deployment tasks on page 365 Strategies for successful implementation on page 371 Summary on page 372
359
Required skills
To be able to successfully deploy a Tivoli Continuous Data Protection for Files solution requires considerable research and collaborative efforts between technicians, managers, consultants, administrators and users. The purpose of this section is to identify the skills needed and where to find available resources to help with Tivoli Continuous Data Protection for Files. You need to establish a team of people with a variety of skills, depending on the solution that you need to implement in order to design, develop and deploy a Tivoli Continuous Data Protection for Files solution: Windows operating system administration skills Administrate and configure Windows servers platform TCP/IP protocol networking skills File server configuration skills (If you have a file server in your environment) Administrate and configure a file server Set right permissions on a file server Connectivity and network skills Configure to establish communication between all machines involved in the solution Storage (external disks) skills Configure external drive, on a single-computer, on a file server or on a Tivoli Storage Manager Tivoli Storage Manager skills (If you intend to backup your file server) Ability to plan, install, configure, execute administrative tasks and perform problem determination on Tivoli Storage Manager and all optional components installed Note: It is important to identify all the applications and resources that exist in the client environment prior to defining the skills necessary for your deployment plan.
Available resources
The prerequisite skills listed in the previous table are those needed to customize or develop the solution. For each of these skills there are a variety of resources
360
available to help acquire the necessary skill level. The educational resources available for Tivoli Continuous Data Protection for Files: Tivoli Continuous Data Protection for Files online information: For more information about Tivoli Continuous Data Protection for Files see web page: http://www-306.ibm.com/software/tivoli/products/continuous-data-prot ection/ Online documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v12r1/index.jsp?to c=/com.ibm.itcdpf.doc/toc.xml IBM Redbooks: You can access practical and architectural information regarding IBM hardware and software on the IBM Redbooks Web site, including information about Tivoli Continuous Data Protection for Files concepts and architecture. See Web page: http://www.redbooks.ibm.com
Solution description
The deployment of any product is simplified when all relevant issues are considered and an action plan is completed prior to roll-out. It is important to invest time and effort to understand how Tivoli Continuous Data Protection for Files is going to be used and possible scenarios you can create that best fits your environment. The purpose of this section is to describe the groundwork and documentation required for a successful deployment.
Solution overview
The solution overview helps you to understand the solution concepts, business value and system architecture considerations. The following items need to be considered: Solution concepts and business value Solution architecture Recommended software, hardware and tools
Solution planning guide

The solution planning guide helps you to plan for the client engagement. The following items need to be considered:
Appendix A. Project planning
361
Skills required to implement the solution Spreadsheet of time estimates to plan for a services engagement Task descriptions Best practices
Implementation guide
The implementation guide is a technical guideline that helps you to set up the solution and learn all important techniques needed to implement a customized solution. The following items need to be considered: Implementation checklist Instructions, tips, installation best practices Customization information Use cases that can be used as part of a demonstration or education Sample code, data, script and configurations The key to achieve a successful Tivoli Continuous Data Protection for Files deployment depends on the adherence to a common road map, tailored to the client needs. You need to define the scope of the solution. The solution depends on, how many servers you want to protect and determining what will be your remote storage.Tivoli Continuous Data Protection for Files provides some facilities for remote deployment and report management, it is a real-time, continuous data protection solution for workstations and notebooks and is specially designed to work well even if the network connections are intermittent. Tivoli Continuous Data Protection for Files also provides continuous protection for file servers, reducing or eliminating backup windows and the amount of data potentially lost in a failure. There are several options for Tivoli Continuous Data Protection for Files solutions that can be presented to the client: Replicate data to a file server and backup to Tivoli Storage Manager or IBM Tivoli Storage Manager Express (depending on the size of your environment) Replicate data directly to a Tivoli Storage Manager or IBM Tivoli Storage Manager Express (depending on the size of your environment) Use Tivoli Continuous Data Protection for Files to backup remote office locations to a centralized server If you are an ISP provider, you can offer Tivoli Continuous Data Protection for Files as a service to replicate the important data across the internet.
362
It is important to work with clients to understand their needs and expectations. Once you have gathered this data, document the tasks, deliverables and associated costs in a Statement of Work. The Statement of Work acts as your contractual agreement with the client for the duration of the project. A detailed and well-defined Statement of Work is advantageous both to you and to your client. Implementors of a solution routinely rely on theirs skills and previous experience as a guide, but there are always some issues that might require some educated guesswork. You need to define the services engagement in your solution scope: Build an executive assessment The Executive Assessment is a service that can be offered to prospective clients as a billable service. This tool set helps you ask the right people the right questions; so that you get the information you need to propose the appropriate solution. The complete Executive Assessment process should take approximately 10 to 16 hours. See the tasks in Table 5-9
Table 5-9 Solution tasks Task An initial fact-finding meeting, asking questions and gathering data A review and analysis of competing solutions Preparation of a set of strategic recommendations Create a demonstration prototype A presentation of findings and close a contract Total Estimated time (hours) 3 2 1 3-9 1 10-16
This is a business-case assessment, not a technical assessment, so the audience should be business owners, line-of-business, marketing and sales managers, and finally, the IT manager. The business owner or line-of-business executive is likely to be the decision maker. Set up a demonstration system of proof of technology A demonstration system is typically set up in advance to show your clients the attributes of the solution. Tivoli Continuous Data Protection for Files is a very
363
simple tool to install and configure. You can do a simple demonstration to show how Tivoli Continuous Data Protection for Files will be used on the clients environment. You can create an environment on a virtualized machine. See Table 5-10.
Table 5-10 Solution demonstration tasks Task Set up Hardware Perform network configuration Install and configure Operating System Install and configure an e-mail application Install and configure Tivoli Continuous Data Protection for Files (continuous and scheduled protection) Demonstrated the functionality to the client Total: Estimated time (hours) 1-2 1 2-4 1-2 1-2
1-2 7-13
Analyze the solution tasks After the client has agreed to use the solution in their environment, you must determine the amount of effort necessary to implement it. These estimates would then be collected and written into a contract or Statement of Work. The suggested tasks will be discuss on next section Solution deployment tasks on page 365. The overall solution timing might be influenced by the amount of skill and experience that you or your team have with the solution, and also the access to resources facilitated by your client. The estimated time of implementation is typically based on the following: Knowledge of the Operating Systems. Knowledge of network configuration. Knowledge of file server configuration. Knowledge of Tivoli Storage Manager configuration. Depending on your skills and experience, the estimates presented might be too high or too low. Table 5-11 on page 365 illustrates one method of approximating more realistic time estimates for your efforts, based on whether you or your team are new to each skill area or could be considered experts. A novice represents someone who has completed training in the skill area but has no hands-on
364
experience. An expert represents someone who has completed training in the skill area and has also implemented Tivoli Continuous Data Protection for Files. You might use the percentages to adjust your time estimate.
Table 5-11 Skill adjustment Skill Experience of operating system Experience of network configuration Experience of file server configuration Experience of Tivoli Storage Manager configuration Novice increase by 25% 30% 40% 35% Expert reduce by 10% 10% 15% 20%
Create a statement of work A Statement of Work is a binding contractual agreement between you and your client that defines the service engagement that you must perform and the result that the client can expect from the engagement. The contract should leave nothing in unclear terms. A good overall understanding of the solution scope is a crucial prerequisite to successfully developing and implementing the solution. As a Solution Provider, you must understand what is involved in developing such a solution before you can discuss it with your client and size it for a cost estimate.
Solution deployment tasks

This section discusses the tasks necessary for solution deployment. It can be used to document the timing estimates for major deployment tasks. These tasks are broken down into sub-tasks in the later sections and discussed in more detail.
Table 5-12 Major solution deployment tasks Task Perform environmental analysis and plan tasks
365
Task Plan the solution Implement the solution Test the solution Customer training Close the engagement
Perform environmental analysis and plan tasks

To help gather these technical requirements, use the provided sample questions and make note of the issues that they raise, as demonstrated in Table 5-13.
Table 5-13 Technical requirement gathering sample examples Question What versions of the Windows operating system are in your environment? How many user desktops or mobile computers are deployed? How many GBs of data do you intend to replicate from each desktop? Will the files be replicated to a File Server or directly to a Tivoli Storage Manager Server? How many versions of each file? Do you need to support mobile users? Do they need a granular security model? Notes Check if all Windows versions that the client has are supported. The number of desktops or mobile computers is important to verify how many licenses will be needed. Helps to estimated external storage resources needed. Estimate the time to configure Tivoli Continuous Data Protection for Files to a file server or to a Tivoli Storage Manager server. Will help you determine the storage resources necessary Check the size of your WAN connection. Helps determine what security options might be needed.
Plan the solution

Planning the deployment of the Tivoli Continuous Data Protection for Files solution includes the subtasks listed below.
366
Table 5-14 Solution planning sub-tasks Task Gather detailed information about client environment Analyze client requirements Design the solution Develop implementation plan Develop a test plan Analyze client education needs Perform GAP analysis Estimated hours CDP, File Server and TSM 8-16 Estimated hours CDP and TSM 8-16
4-8 8-16 4-8 4-8 4-8 5-10
4-8 8-16 4-8 4-8 4-8 5-10
Gather detailed information about client requirements At the beginning of your engagement meet with your clients to understand their proposed objectives and gather their requirements. First determine the functional requirements. Functional requirements define the business functions that the Tivoli Continuous Data Protection for Files solution is going to provide. You determine the requirements by developing a good understanding of the business needs and what you hope to achieve. It is important to gather these requirements early in the process, and discover any challenges that might lie ahead while they can still be dealt with easily. Once you have determined the functional requirements, you can clarify the technical and system requirements. Obtaining the technical requirements involves spending time at the client site to determine and understand the clients hardware and software installation and infrastructure. A complete high-level inventory of the environment is created. Analyze client requirements In this stage information about client requirements are compiled and reviewed. Appropriate diagrams and charts are created in order to study how data copies will flow during replication and restores. Design the solution After the environment has been inventoried and described in sufficient detail and all requirements have been agreed to and documented, the detailed design of
367
the backup/recovery solution can be completed. The appropriate hardware to support the requirements is also chosen along with the right type and number of Tivoli Continuous Data Protection for Files nodes. It is important to design the solution to support the most demanding component. The solution design might require revisiting the requirements analysis phase due to unfavorable costs that arise trying to satisfy the clients initial recovery or data retention requirements. In such a situation the requirements could be lowered to balance requirements and costs. Develop implementation plan Implementing a Tivoli Continuous Data Protection for Files infrastructure successfully requires a fair amount of coordination and collaboration. Project planning and project management skills might be required to implement a detailed solution with minimal impact on regular production operations. Plans for procuring the actual hardware, software, services and supplies are developed as early in the process as possible. Develop a test plan A comprehensive test plan is developed to test the Tivoli Continuous Data Protection for Files implementation. The plan includes testing solution infrastructure (correct data-flow through network to a file server or a Tivoli Storage Manager server) configuration and data file retention. Analyze client education needs The support staff must be well trained in the details of Tivoli Continuous Data Protection for Files administration. Customer education plans must be created. Perform GAP analysis This task might involve performing a GAP analysis to give the client an estimate of the development effort required to set up the solution. As its core, the analysis seeks to determine what customizable components need to be extended, modified, or created. The number of complexity of customizable components drive the size of the project and the required resources.
Implement the solution

The implementation of the solution is performed using the tasks described in Table 5-15.
Table 5-15 Solution implement sub-tasks Task Hardware installation Estimated Time CDP, File Server and TSM Depends on environment Estimated time CDP and TSM Depends on environment
368
Task Tivoli Storage Manager installation and configuration File server configuration Installation and configuration on Tivoli Continuous Data Protection for Files
Estimated Time CDP, File Server and TSM 10-20
Estimated time CDP and TSM 12-24
8-12 8 - 10 (for 20 user workstations)
N/A 8 - 10 (for 20 user workstations)
Hardware installation Installation and configuration of hardware included in the solution is performed. This includes disk subsystems for file server, or a Tivoli Storage Manager server infrastructure, for example. Tivoli Storage Manager installation and configuration The efforts to install and configure Tivoli Storage Manager in this task, depends if the client wants to replicate the files directly to Tivoli Storage Manager, or if just the file servers will be backed up. The estimated hours corresponds to a basic server installation and configuration. File Server The efforts to configure a file server to replicate data and back it up to a Tivoli Storage Manager server. Tivoli Continuous Data Protection for Files installation After the infrastructure has been implemented the project proceeds to the more delicate work of installation and configuration of the product. Where large numbers of similar systems are encountered, a standard client installation might be tested and replicated or pushed to all clients using application deployment software, such as Tivoli Configuration Manager, or Microsoft Systems Management Server (SMS). Note: We do not provide details on installation for Microsoft SMS deployment. The clients who have SMS should refer to that products documentation for installation, configuration and use.
Test the solution

The tasks needed to test solution are listed in Table 5-16 on page 370.
369
Table 5-16 Solution test sub-tasks Task Perform replication / restore test plan Performance testing Estimated Time CDP, File Server and TSM 4-8 2-4 Estimated time CDP and TSM 2-4 2-4
Perform replication/restore test plan Solution infrastructure, Tivoli Continuous Data Protection for Files configuration and basic file replication and restore is tested and the results are noted for later documentation. Performance testing Various performance tests are carried out (backup/restore) speed across network).
Client training
The tasks needed to perform client training are listed in Table 5-17.
Table 5-17 Solution client training sub-tasks Task Customer training Estimated Time CDP, File Server and TSM 4-8 Estimated time CDP and TSM 4-8
We recommend that key system administrators are trained in the use of Tivoli Continuous Data Protection for Files. During the implementation you can offer hands-on training to your client.
Close the engagement

Closing the engagement is performed using tasks listed in the following table:
Table 5-18 Engagement closing sub-tasks Task Document solution Close the engagement Estimated Time CDP, File Server and TSM 16-20 4-8 Estimated time CDP and TSM 16-20 4-8
Document the solution
370
It is highly recommended to have your Tivoli Continuous Data Protection for Files environment documented with a list of all user desktops, application installation points and functionality flow charts. Close the engagement A final verification is made to ensure the implemented solution matches the initial client requirements. Documentation is handed over to the appropriate parties. When the technical work has been completed, and the education has been delivered, the engagement will need to be formally closed with the project sponsor. We suggest the following agenda items are covered during the meeting with the project sponsor: 1. Review of original business objectives 2. Summary of how solution meets defined objectives 3. Summary of services delivered 4. Summary of new capability 5. Other services or product identified during engagement 6. Thanks and closing
Strategies for successful implementation

Building and sustaining a storage management solution can challenge even the most successful organization. As mentioned earlier, have the right personnel on your deployment team, carefully plan out your deployment, and have commitment from the organization as a whole. In addition to these strategies, this section discusses other key considerations that can help you achieve a successful implementation of the Tivoli Continuous Data Protection for Files. Follow these strategies for a successful implementation:
Read the updated documentation

It is important to always check the online information about Tivoli Continuous Data Protection for Files because it is updated frequently. The README file that is shipped with the product contains the release notes and features included with the latest version.
Obtain commitment
Experts agree that a storage management initiative stands little chance of success unless upper level management takes ownership of the project. Project leaders can initiate the effort, but commitment from upper level management to get everyone behind it is an essential ingredient.
371
Verify technology integration issues

The infrastructure design and network will impact directly on Tivoli Continuous Data Protection for Files if you are sending replicated files to a remote storage, so all those aspects should be carefully examined and considered during your planning stage.
Clearly establish the scope of the project

Establish the scope of any knowledge management project early, and try to be realistic in what you can achieve and in ensuring that it truly provides business value.
Educate the client

It is widely accepted that a favorable corporate culture is a prerequisite for the successful implementation of knowledge management initiatives, so you have to focus not just on technology, but on culture and process as well. Sustainable knowledge management requires the introduction of a knowledge sharing culture organized around key skills, and a set of incentives to reuse knowledge to reinforce the skills required for the effective operation of the organization. You might not agree entirely with this point of view, but being aware of what is being written about knowledge management and considering how knowledge sharing and information reuse is currently practiced in your organization might reveal the type of culture you have to work with when you draw up your knowledge management program.
Involve, train, and inform your users

The benefits of deploying a knowledge management solution are likely to be lost on most users in your organization because there is no immediate result you can point to.
Obtain the right hardware

You will have a lot of problems if inadequate hardware resources have been allocated. System administrators should resist using second-hand hardware that does not meet the minimum system requirements.
Summary
For anyone who has deployed new technology into an enterprise, the concepts of careful planning and phasing a deployment through test and pilot environments will probably not be new. Much of the content of this chapter should therefore be a quick refresher.
372
However, when knowledge management technologies are involved, it is important to always consider the cultural and organizational impacts. Finding a clear and defined purpose for your deployment, and then ensuring that the organization truly understands the need to solve that problem, is crucial to ensuring the organizational commitment to any cultural changes required.
373
374
Appendix B.
Sample Statement of Work for Tivoli Continuous Data Protection for Files deployment
In this appendix, we provide a skeleton document that you can use to create your own customized Statement of Work. This is just a sample and should be customized based on the requirements of the client engagements.
375
Building a protected environment for user workstations

The content of the Statement of Work would include activities that provide: Continuous data protection Scheduled data protection Centralized reporting The Statement of Work to protect user workstations should consist of the following sections.
Executive summary
This service will build the infrastructure required to provide data protection for your computing environment. It will also supply working samples of key items that you will need to deploy a product solution. After this work has been completed, you will have the infrastructure necessary to successfully protect your user workstations.
Solution description
Businesses today cannot afford unprotected data. Losing key business information hampers productivity; creates application outages, delays projects, diverts resources and calls to the help desk, and harms businesses reputations with clients. And governments are increasingly requiring businesses to formally deploy data protection. Often times the most valuable files are what users are working on right now. Being able to roll back to a specific point in time is necessary, rather than just going back to last nights backup. Companies need sophisticated policy-based data management that enables them to focus on the data with the highest business value as well. Although most companies have implemented solutions for protecting the enterprise data, data residing in workstations, notebooks and file servers is notoriously under-protected even though it amounts to 60 to 70 percent of all corporate data, according to some industry experts. Tivoli Continuous Data Protection for Files (Figure 5-95 on page 377) provides a real-time, continuous data protection solution for file servers and users-endpoints. Instead of waiting for a scheduled interval, Tivoli Continuous Data Protection for Files backs up your most important files the moment they are saved, in real time. What's more, it does this effortlessly and transparently, in some cases eliminating the backup window. You can specify as many as three target backup/replication areas for high-priority files to help you capture every
376
save of a file when it occurs to help protect against corruption, file loss or system loss.
Figure 5-95 Functionality overview of Tivoli Continuous Data Protection for Files
The client will be provided with a complete Tivoli Continuous Data Protection for Files solution- including integrated with a file server and Tivoli Storage Managerto backup their user workstations. The provider guarantees the complete recoverability of the most critical files in case of hardware failure, user failure or hardware loss.
Assumptions
These are the assumptions that is made in this Statement of Work. Tivoli Continuous Data Protection for Files will be installed in all desktops and notebooks One server will be configured to be used for central administration of Tivoli Continuous Data Protection for Files All desktops and notebooks will be able to access the central administration server with the proper authority
Appendix B. Sample Statement of Work for Tivoli Continuous Data Protection for Files deployment
377
Tivoli Continuous Data Protection for Files will be configured to protect the following files and directories: My Documents Favorites D:\PersonalFiles pst files office files A secure file server will be established as a remote target for data replication The storage area on the file server should be sized to properly contain the replicated data The file server will be backed up to a Tivoli Storage Manager server The Tivoli Storage Manager Server infrastructure will be configured prior to the Tivoli Continuous Data Protection for Files installation The sizing of Tivoli Storage Manager database and storage pool should be sufficient to contain the replicated data backed up from the file server
Business partner responsibilities

This service will be provided according to the high standards of <name of Business Partner>, an IBM Certified Business Partner. We will provide: Skilled staff to undertake the defined activities Documentation of the completed solution Project management of these activities Note: Insert this section, only if you intend to work with a Business Partner. You are free to add additional responsibilities here that you will be taking on as part of this project.
Client responsibilities
Designate a representative who will be the focal point for all communication with IBM or Business Partner relative to this project and who will have the authority to act on the clients behalf in matters regarding this project. Designating operations personnel to work with IBM or Business Partner as appropriate. Provide all product data in a format as requested.
378
Provide all data and information required for implementation. Provide suitable workspace with internet and telephone access for the services specialists working on client premises. Provide user IDs, passwords, and IP addresses as required, enabling IBM or Business Partner to perform the service. Note: Add any technical client responsibilities that you need to assign in order to complete a successful delivery of your service.
Staffing estimates
The project will be performed with one Tivoli Continuous Data Protection for Files deployment specialist, who will be on site as required by the project schedule. We will also provide project management services, and will be onsite at the end of the project for its formal closure. The project is estimated to be performed within 5 working days (depending on the number of machines that you need to install). We expect that will need a single member of your staff working with us throughout this time, who will also perform any mediation role required between us and any other required technical resources within your computer operation.
Testing
The testing of the solution will be done with your existing infrastructure to replicate the data to a file server or Tivoli Storage Manager Server. Testing will be complete, when we have successfully: Replicate data to a file server or Tivoli Storage Manager Restored data from file server or Tivoli Storage Manager to the user workstation Generate reports Agree performance is acceptable
Deliverables
At the end of this engagement, you will have: Documentation of the deployed environment
Completion criteria
Completion criteria for this project are: The successful completion of all the tests
Appendix B. Sample Statement of Work for Tivoli Continuous Data Protection for Files deployment
379
The delivery of the solution documentation
380
Abbreviations and Acronyms

IBM IIS ISP ITSO LAN NAS RC ROI RPO RTO SAN SMS TCO TCP UNC USB WAN WebDAV WORM International Business Machines Corporation Internet Information Services Internet Service Provider International Technical Support Organization local area network network attached storage return code return on investment recovery point objective recovery time objective storage area network Systems Management Server total cost of ownership Transmission Control Protocol Universal Naming Convention Universal Serial Bus wide area network Web-based Distributed Authoring and Versioning Write Once Read Many
381
382
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.
Publications
These publications are also relevant as further information sources: Tivoli Continuous Data Protection for Files Version 3.1. Installation and Users Guide, GC32-1783 IBM Tivoli Storage Manager for Windows Administrators Guide V5.4, SC32-0121 IBM Tivoli Storage Manager: Using the Application Program Interface, SC32-0147 IBM Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and Users Guide, SC32-0146
Online resources
These Web sites are also relevant as further information sources: Tivoli Continuous Data Protection for Files online documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v12r1/index.jsp?to c=/com.ibm.itcdpf.doc/toc.xml Tivoli Provisioning Manager Express online documentation http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc =/com.ibm.itpmesd.doc/toc.xml
How to get IBM Redbooks

You can search for, view, or download IBM Redbooks, Redpapers, Technotes, draft publications and Additional materials, as well as order hardcopy IBM Redbooks, at this Web site:
383
ibm.com/redbooks
Help from IBM

IBM Support and downloads ibm.com/support IBM Global Services ibm.com/services
384
Index
A
action 21 Advanced page 118 AES128 encryption option 122 ANS1025E 321 ANS1115W 342 ANS1126E 321, 325 Apache 122 API (application program interface) 153 Applications box 53 Audit 20 automating manual process 18 ChangeJournal.log_LastSuccess 350 changing drive letter assignments 298 Checking port usage 275 client requirements 367 Close the engagement 370371 closeapps.txt 92 command-line installation 68 COMMMethod 311 Completion criteria 379 compliance data 183 compress backups 130 compressed_file.txt 98 compressed_file.txt.cdp 98 compression of remote backups 297 compression option 207 configurable pool size 13 Conflicting include/exclude lists 339 Continuous and scheduled protection 111 continuous data protection 20, 126 default location 26 Continuous protection level 161 Critical page 49
B
backdelete=yes parameter 328 backup copy group 223 Backup policy 198 backup windows 17 Backup-Archive client 60 Backup-target flexibility 17 bandwidth optimization 17 basic file replication 370 basic file restore 370 build number 4142 business continuity 15
D
Daemon architecture 22 data integrity 17 default dsm.opt file 310 Default protection settings 116 deliverables 379 direct attached USB drive 126 disable sessions client command 329 disaster-recovery data 183 disk full 293 Disk pools daisy chained 32 Disk pools with backup to tape 32 Disk pools with no backup 32 disk storage pools 17 document the solution 370 DONT_LAUNCH_FILEPATHSRV=1 72 dsierror.log 321, 342, 351 DSL service provider 141 dsm.opt 153, 184, 225, 340341 dsm.opt file 97
C
Cable service provider 141 Central Administration 191 central administration folder 101102, 193 computer-specific sub-folders 103 downloads folder 103 group administrative sub-folders 102 reports folder 103 Central Administration Folder field 102 Central Administration Settings 210 Central Administration Settings window 75, 217 central management 122, 216 Centralized reporting 197 ChangeJournal 23 ChangeJournal.log 23 ChangeJournal.log_2_last file 23
385
dsm.opt options 312 NODename 312 TCPPort 312 DSM_RC_REJECT_ID_UNKNOWN 315 DSM_RC_TL_EXCLUDED 341
hierarchical storage 31 HTML listener 24 HTTP Server V6.1 140
I
IBM Passport Advantage 40 IBM Passport Advantage Web site, 40 IBM Tivoli Continuous Data Protection for Files.msi 69 IBM Tivoli Provisioning Manager Express for Software Distribution 69 IBM Tivoli Storage Manager Express 12 implementation guide 362 implementation plan 368 Implementing the solution file Server 369 hardware installation 369 Tivoli Continuous Data Protection for Files installation 369 Tivoli Storage Manager installation and configuration 369 Improved backup resource utilization 15 improved productivity 16 inactive 199 include list 111 inclusion list 21, 26 increase data protection 183 Initial Backup page 61 Initial Configuration Wizard 48 inst.log 6768 installation silent 65 Installation directory 20, 23 InstallShield Wizard 46 InstallShield Wizard Completed dialog 46 interim files 138 Internet connection 138 Internet Explorer, Version 6.0 35 Internet Service Providers (ISPs) 59 ISP based storage repository 138 ISP provider 140 ISP-provided remote storage 141
E
education 368 eliminate inactive versions of files 328 E-mail application 27 E-mail files 27 E-mail Protection page 54, 117 encryption file 239 establish the scope 372 example.txt 144 exclude list 111 excluding files 111 exclusion list 21 executive assessment 363 Executive summary 376 expire inventory command 328 external disk 129 external USB device 130
F
file patterns 109 file server 2627 File server issues 302 file system full 293 FilePathSrv.exe 20 Files to Protect page 116 file-server space 141 firewall 70 first scan 133 folder patterns 109 Folders and Files box 51 fp.sys 20 fpa.exe 20 fpa.txt 21, 70, 75, 108, 195, 347 fpcommands.xml 7475, 195, 210 FPdelta file name suffix 144 fpPushInst.exe 69, 72 functional requirements 367
K H
heterogeneous backup devices 17 hidden folders 109 KeepSafe folder 114 kernel layer 21
386
L
list of excluded files 131 local area network (LAN) 183 local cache size 33 local pool size 12 locally attached USB drive 33 long-term retention 31
M
mail 27 Main components 20 management class 223 maximum number of versions 325 Maximum space for backups 60, 161 Meta rules 21 Microsoft Corporation 34 Microsoft Systems Management Server (SMS) 69, 369 Microsoft Vista Business Edition 35 Mirroring Kernel-based I/O mirroring 21 mobile computer 136137 Mozilla Firefox 1.5.0.7 35 multiple storage locations 13 multiple versions of files 17 mutually exclusive 122
Perform replication 370 performance testing 370 policy domain 223 policyset 223 primarily mail files 13 product identified during engagement 371 project sponsor 371 proof of concept scenarios 121 proof of technology 363 protected file 138 providing real-time backups 15 pull installation 72, 101 troubleshooting 286 purge of older versioned files 323 purge_failed.log 24, 324 purge_struggled.log 24 Push install Microsoft Vista operating system 196 Push Install Command 69 push installation 196 troubleshooting 279
Q
query status 334 query status command 329
R N
NAS device 12 native format 5 netstat -a 275 Network Attached Storage (NAS) 17 network file server (NAS) 5 network traffic 133 networking skills 360 newest backup copy 60 node name defined with wrong permission 316 NODename option 312 Notes sub-file backup 202 rapid data recovery 14 real-time data protection 14 RealTimeBackup 125 RealTimeBackup directory 126 RealTimeBackup folder 26 RealTimeBackup subfolder 77 RealTimeBackupcomputername 59 REBOOT=ReallySuppress 68 recovery options 17 recovery point objective (RPO) 15 recovery time objective (RTO) 16 Redbooks Web site 383 Contact us xxiii reduce network traffic 140 reduced loss of data 16 register node 185 register node command 326 Registry Editor 270 remaining backup copies 150 remote backup option 26
O
original business objectives 371
P
passwords do not match 308 pattern matches 110 Perform GAP analysis 368
Index
387
remote backup target 122 remote continuous 27 remote storage location 59, 95 Remote Storage page 56, 118 remote target 24, 27 remote WebDav server 26 RemoteVersions.log 24 Removable disk issues 292 replicate to local disk 138 replicated directory 134 replication 21 replication issues 291 replication.log 24 replication-active.N file 24 replication-failed.N file 24 replication-queued.N file 24 reports table 107 restore a previously saved version 26 restore scenarios 228 restore test plan 370 return on investment (ROI) 15
solution description 361 solution design 367 solution overview 361 solution planning guide 361 space management 183 SSL 141 staffing estimates 379 Start scheduled backup now check box 132 Statement of Work 363364 Status page 63, 103 storage area network (SAN) 17, 183 storage pools 199 Sub-file copy 144 Summary page 62 Sysprotect 23 System requirements 34
T
tape storage pools 17 target file server 31 target location is not responding properly 331 technical note 1245761 58 technical requirements 367 technology integration issues 372 test plan 368 Test the solution 369 testing 379 Tivoli Continuous Data Protection for Files 5, 17, 3334, 40, 43, 5960, 122, 131, 186, 196, 295, 308, 318319, 339, 351, 360361, 364, 371 advanced installation 64 architecture and components 20 available resources 360 backup policy 198 benefits 17 capabilities 20 Central Administration Settings window 102 central management 122, 186, 216 centralized reporting 197 compression 122 configuration 39 connect to Tivoli Storage Manager server 184 corporate scenario 32 Daemon architecture 22 audit thread 23 queue thread 22 sysprotect 23 Default protection settings
S
Sample Statement of Work 375 assumptions 377 business partner responsibilities 378 client responsibilities 378 completion criteria 379 deliverables 379 executive summary 376 solution description 376 staffing estimates 379 testing 379 Schedule Backup Settings 208 scheduled backups 13 scheduled interval time 143 scheduled protection 21, 209 scope of the solution 362 secure_backupvault 140 Select Schedule Backup Settings 190 ServerPool 24 ServerPoolQuota 24 several backup copy versions 150 silent installation 65, 68 simplified file sharing concept 59 simplified management 14 single user environment 123 small foot print 14
388
Advanced page 118 E-mail Protection page 117 Files to Protect page 116 General page 116 Remote Storage page 118 default protection settings 116 demonstration 364 deployment 19 encryption feature 122 general overview 5 hints and tips 255 home or small business scenario 145 Home user scenario 33 installation 39, 369 default language 40 Destination Folder window 43 fpPushInst.exe 69 information window 41 installation and data directories 108 License Agreement window 42 open command prompt window 46 providing a configuration file 74 pull installation 40 pull installation (upgrade) 72 Ready to Install the Program window 44 reboot 47 upgrade 72 installation requirements 34 Basic installation 34 hardware 34 software 35 supported operating systems 35 System requirements 34 installing 40 integration 17 interactive installation 40 interval selected 13 Daily 13 Hourly 13 Monthly 13 Weekly 13 main components 20 kernel 20 user 20 main features 13 Multiple computers 145 Home network with a file server 146 product capabilities 20 Audit 20
Mirroring Kernel-based I/O mirroring 21 Replication 21 Write Once Read Many (WORM) 20 product loaded on file server 33 README file 371 required skills 360 restore scenarios 228 Sales engagement analyze client requirements 367 available resources 360 building an executive assessment 363 client training 370 closing the engagement 370 create a statement of work 365 develop a test plan 368 develop an implementation plan 368 documenting the solution 370 implement the solution 368 overall solution timing 364 perform environmental analysis 366 perform GAP analysis 368 Performance testing 370 plan the solution 366 required skills 360 setting up a demonstration system 363 solution deployment tasks 365 solution description 361 solution tasks 363 successful implementation 371 Sample Statement of Work 375 server 312 Single user environment 123 Single computer with external storage 126 Single computer with ISP connection 136 Single computer, local disk only 123 sizing considerations 30 solution 360 solution description 361 support matrix 122 Tivoli Storage Manager Express integration 160 tracing 351 how to run 352 troubleshooting 255 unique differentiators 17 using patterns 109 valid node name 318 value proposition 14 Tivoli Continuous Data Protection for Files V2.x 96
Index
389
Tivoli Storage Manager 9, 1213, 27, 3031, 122, 316, 325, 333, 369, 379 API 184, 339 API client 311, 339 backup policy 224 Backup-Archive client 60 backups 27 client 225 client node 60 client sessions disabled 329 command line 224 database 181, 329 granting authority 60 restore from 251 server 14, 27, 339 server administrator 339 skills 360 troubleshooting 310 Tivoli Storage Manager Express 5, 18, 33, 251 integration 160 restore from 251 server 14 service 157 Tivoli Storage Manager node 60 total cost of ownership (TCO) 15 traditional backup application 200 traditional backup solutions 17 traditional Tivoli Storage Manager environment 31 training 370 transient conditions 343 transient networks 14 traveling users 18 TSM interval 27 TSM thread 24
V
value proposition 14 vault 218 vault box 85 vault duration 114 vault folders 218 Veritas NetBackup 9 versioning 144 virtualized machine 364 VPN (virtual private network) 141
W
Web server 140 Web-based Distributed Authoring and Versioning (WebDAV) 304, 343 what is it? 141 WebDAV issues 304 WebDAV over SSL 141 WebDAV server 12, 5859, 136, 308 WebDAV server location 59 Welcome page 48 wide area network (WAN) 183 wildcards 109 Windows 2000 Advanced Server 35 Windows 2000 Server 35 Windows 2003 Server 35 Windows Microsoft Vista Ultimate 123, 127 Windows system event log 319 Windows Vista Ultimate and Business Edition 35 Windows XP Professional 35 Write Once Read Many (WORM) 20 write-protect data 17 wrong node name 313 wrong user name 306
U
uncompressed 136 unique differentiators 17 Universal Naming Convention (UNC) 291, 303 unwanted files 199 update node command 326 usage scenarios 122 USB (Universal Serial Bus) 17 USB disk 298 USB external device 58 USB stick 298 user productivity 18
390
(0.5 spine) 0.475<->0.875 250 <-> 459 pages
Back cover
Deployment best practices Integration with the TSM and Notes Case studies, troubleshooting and much more
Tivoli Continuous Data Protection for Files is specifically targeted at user computers, such as mobile computers and workstations, as well as file servers. It provides continuous data protection of files, providing the highest level of protection possible, yet is simple to use and administer. This IBM Redbooks publication presents a deployment guide for Tivoli Continuous Data Protection for Files Version 3.1. We cover planning, installing, and troubleshooting of Tivoli Continuous Data Protection for Files for several use case scenarios. In addition, we provide some case studies, including integration with IBM Tivoli Storage Manager, that can be used as a proof of concept or demonstration of the product at a client environment. The target audience for this document is IT Specialists who will be working on Tivoli Continuous Data Protection for Files installations and proof of concepts.
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.
For more information: ibm.com/redbooks

SG24-7423-00 ISBN 0738489115

Deployment Guide Series Tivoli Continuous Data Protection For Files V3.1 Sg247423

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Deployment Guide Series Tivoli Continuous Data Protection For Files V3.1 Sg247423

Enviado por

Direitos autorais:

Formatos disponíveis

Front cover

Case studies, troubleshooting , tips

Vasfi Gucer Greg Bass Wolfgang Beuttler Marcia Kubo

Copyright IBM Corp. 2007. All rights reserved.

Copyright IBM Corp. 2007. All rights reserved.

Copyright IBM Corp. 2007. All rights reserved.

Copyright IBM Corp. 2007. All rights reserved.

Copyright IBM Corp. 2007. All rights reserved.

The team that wrote this book

Copyright IBM Corp. 2007. All rights reserved.

Become a published author

Planning and architecture

Copyright IBM Corp. 2007. All rights reserved.

Introduction to Tivoli Continuous Data Protection for Files

Copyright IBM Corp. 2007. All rights reserved.

Value proposition of Tivoli Continuous Data Protection for Files on page 14

1.1 General overview of Tivoli Continuous Data Protection for Files

1.1.1 What is Tivoli Continuous Data Protection for Files?

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

How to detect Where copies are stored

Journal-based on some file systems Typically on tape

Storage format Management / administration complexity

1.1.2 Why Tivoli Continuous Data Protection for Files is needed

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

Why is Tivoli Continuous Data Protection for Files needed?

Recovery from a disk image

Recovery from tape copy

Recovery Time Objective

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

1.2 How Tivoli Continuous Data Protection for Files works

Tivoli Continuous Data Protection for Files

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

1.3 Main features of Tivoli Continuous Data Protection for Files

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

1.4 Value proposition of Tivoli Continuous Data Protection for Files

Improved recovery point objective (RPO)

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

1.4.1 Benefits of using Tivoli Continuous Data Protection for Files

1.4.2 Unique differentiators

Chapter 1. Introduction to Tivoli Continuous Data Protection for Files

Product architecture, planning, and deployment

Copyright IBM Corp. 2007. All rights reserved.

2.1 Product architecture

2.1.1 Main components

Chapter 2. Product architecture, planning, and deployment

Manipulation of live database

Service Interactive FPA

Figure 2-1 Agent-driver interaction

2.1.3 Daemon architecture

Chapter 2. Product architecture, planning, and deployment

KERNEL FPQ AGENT

Figure 2-2 Replication threads

2.2 Planning for deployment

Chapter 2. Product architecture, planning, and deployment

2.2.1 What are my critical files?

2.2.2 Where should I back my files up to?

2.2.3 How often do I need to back up different types of files?

2.2.4 Do I need e-mail and scheduled backups?

Chapter 2. Product architecture, planning, and deployment

Additional files to protect on a schedule

2.2.5 Do I need the Vault feature?

2.2.6 Summary of protection methods