Your SlideShare is downloading. ×
Deployment guide series tivoli continuous data protection for files v3.1 sg247423
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Deployment guide series tivoli continuous data protection for files v3.1 sg247423

7,342

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
7,342
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Front coverDeployment Guide Series:Tivoli Continuous DataProtection for Files V3.1Deployment best practicesIntegration with TSM and NotesCase studies,troubleshooting , tips Vasfi Gucer Greg Bass Wolfgang Beuttler Marcia Kuboibm.com/redbooks
  • 2. International Technical Support OrganizationDeployment Guide Series: Tivoli Continuous DataProtection for Files V3.1August 2007 SG24-7423-00
  • 3. 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 ADPSchedule Contract with IBM Corp.
  • 4. 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiPart 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
  • 5. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Part 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 . . . . . . . . . . 151iv Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 6. 4.3.3 Small business with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2274.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Chapter 5. Troubleshooting, hints, and tips . . . . . . . . . . . . . . . . . . . . . . . 2555.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2865.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) . . . . 3435.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 . . . . . . . . . . . . . . . . . . . . . 3505.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 v
  • 7. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385vi Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 8. 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© Copyright IBM Corp. 2007. All rights reserved. vii
  • 9. 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 Express153viii Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 10. 4-33 Wizard to add computers and optionally deploy the backup client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544-34 Select option to add a computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554-35 Installation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564-36 Confirm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574-37 Stop Tivoli Storage Manager Express service . . . . . . . . . . . . . . . . . . . 1574-38 Start Tivoli Storage Manager Express in foreground mode . . . . . . . . . 1584-39 Configure node with delete permission . . . . . . . . . . . . . . . . . . . . . . . . . 1584-40 Shutdown Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . 1594-41 Start Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . . . . . 1594-42 Reset the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594-43 Windows credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604-44 New password information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604-45 General configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614-46 Files to protect in continuous protection . . . . . . . . . . . . . . . . . . . . . . . . 1624-47 Remote storage configuration for Tivoli Storage Manager Express . . . 1634-48 Node password on Tivoli Storage Manager Express server . . . . . . . . . 1644-49 Select applications, files, and frequency to back up to Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654-50 Create the include list for scheduled protection . . . . . . . . . . . . . . . . . . 1664-51 Filespace on Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . 1674-52 Small business with a file server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684-53 Map network drive and reconnect at logon . . . . . . . . . . . . . . . . . . . . . . 1694-54 Configure user name and password to access the file server . . . . . . . 1694-55 General configuration for this scenario . . . . . . . . . . . . . . . . . . . . . . . . . 1704-56 Files to protect in continuous backup . . . . . . . . . . . . . . . . . . . . . . . . . . 1714-57 Configure remote storage for continuous and scheduled protection. . . 1724-58 Configure directories, files, and frequency for schedule protection . . . 1734-59 Select files and directories for scheduled protection . . . . . . . . . . . . . . . 1744-60 Inform password for encrypted files . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744-61 Replicated files with encryption option on file server . . . . . . . . . . . . . . 1754-62 Computers and applications on Tivoli Storage Manager Express . . . . 1764-63 Excluded files on Tivoli Storage Manager Express client . . . . . . . . . . . 1774-64 Remove directory from dsm.opt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784-65 Files to backup on Tivoli Storage Manager Express. . . . . . . . . . . . . . . 1794-66 Example of enterprise environment with Tivoli Storage Manager centric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814-67 Lab environment (Tivoli Storage Manager centric) . . . . . . . . . . . . . . . . 1834-68 Add nodes to Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . 1854-69 General configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864-70 Files to protect in continuous protection . . . . . . . . . . . . . . . . . . . . . . . . 1874-71 Remote storage configuration to Tivoli Storage Manager . . . . . . . . . . . 1884-72 Node password on Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . 189 Figures ix
  • 11. 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 . . . . . . . . . . . . . . . . . . . 226x Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 12. 4-114 Enterprise and remote offices example. . . . . . . . . . . . . . . . . . . . . . . . 2274-115 Status page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2284-116 Welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2294-117 Files to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2304-118 Search BackupMe.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2314-119 Search status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2324-120 Select the file to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2324-121 Restore Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2334-122 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344-123 View report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344-124 Select remote storage to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2354-125 Tivoli Continuous Data Protection for Files searching files . . . . . . . . . 2364-126 Select file name and version of file to restore . . . . . . . . . . . . . . . . . . . 2364-127 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374-128 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2384-129 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2384-130 Check the restored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2394-131 Tivoli Continuous Data Protection for Files searching for files . . . . . . 2394-132 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404-133 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414-134 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424-135 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424-136 Check the restored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434-137 Tivoli Continuous Data Protection for Files Change Search Location window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434-138 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2444-139 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454-140 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2464-141 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2464-142 Select remote storage to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2474-143 Tivoli Continuous Data Protection for Files searching for files . . . . . . 2484-144 Select files to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2484-145 Versions of notes file log.nsf on file server . . . . . . . . . . . . . . . . . . . . . 2494-146 Select location to restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2494-147 Summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2504-148 Status page, view report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2504-149 The restored notes file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2514-150 Tivoli Storage Manager backup-archive client . . . . . . . . . . . . . . . . . . 2514-151 Restore Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2524-152 Select destination folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534-153 Report status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2545-1 Ready to Install the Program window . . . . . . . . . . . . . . . . . . . . . . . . . . . 2565-2 Out of Disk Space window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Figures xi
  • 13. 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) 296xii Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 14. 5-42 Modified settings in the Remote Backup page to save space on the remote target location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2975-43 Changed drive letter assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2985-44 Informational message that the network target cannot be reached . . . 2995-45 Event entry due to replication problem caused by changed drive letters (Event ID: 6069) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3005-46 Remote storage location inaccessible due to changed drive letter assignment (Status page). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3015-47 Shared network folder e$ on file server Izmir mapped to drive (W:) . . . 3035-48 Using the UNC name instead of the drive letter for the remote storage location (Remote Storage page). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3045-49 Using a WebDAV server as the remote storage destination . . . . . . . . . 3065-50 Tivoli Continuous Data Protection for Files needs a password (informational message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3075-51 Tivoli Continuous Data Protection for Files prompts for a password to access the WebDAV server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3075-52 Entering user name and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3085-53 The two passwords do not match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3085-54 WebDAV server not reachable because no Internet connection is available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3095-55 WebDAV server can be reached again (Internet connection established) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3095-56 Default (minimum) dsm.opt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3105-57 Using a Tivoli Storage Manager server as a remote backup location (Helsinki). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3135-58 Window explains target location (Helsinki) is not responding properly . 3145-59 Tivoli Continuous Data Protection for Files warning message . . . . . . . 3145-60 Event log entry due to unknown or incorrect ID (node name) entered . 3155-61 Entries in dsierror.log caused by unknown or incorrect ID (node name) entered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3155-62 Tivoli Continuous Data Protection for Files prompting for a password to access the Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . 3185-63 Informational entry in the event log (password information needed) . . 3195-64 Event log entry due to insufficient permission to delete backed up data3205-65 Error messages in dsierror.log due to insufficient permissions to delete backed up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3215-66 Event log entry when storing more versions of files as defined on remote storage location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3225-67 Tivoli Continuous Data Protection for Files unable to unlink the file (Event ID: 6086). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3235-68 FilePath ERROR entry (Event ID: 6000) in event log due to a permission problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3245-69 Entry in file purge_failed.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Figures xiii
  • 15. 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. . 377xiv Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 16. 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© Copyright IBM Corp. 2007. All rights reserved. xv
  • 17. xvi Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 18. 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© Copyright IBM Corp. 2007. All rights reserved. xvii
  • 19. xviii Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 20. NoticesThis 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. Consultyour 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 IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the usersresponsibility 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 licenseinquiries, 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimerof 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 madeto the information herein; these changes will be incorporated in new editions of the publication. IBM maymake improvements and/or changes in the product(s) and/or the program(s) described in this publication atany time without notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials 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 withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirmthe accuracy of performance, compatibility or any other claims related to non-IBM products. Questions onthe 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 themas 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 businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which thesample 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.© Copyright IBM Corp. 2007. All rights reserved. xix
  • 21. TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: Redbooks (logo) ® Lotus Notes® Redbooks® AIX® Lotus® System p™ Domino® Notes® Tivoli® IBM® Passport Advantage®The following terms are trademarks of other companies:Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporationand/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, othercountries, or both.Internet Explorer, Microsoft, Outlook, Windows Server, Windows Vista, Windows, Win32, and the Windowslogo 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 trademarksof 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 22. 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© Copyright IBM Corp. 2007. All rights reserved. xxi
  • 23. 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 USABecome 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.htmlxxii Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 24. 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
  • 25. xxiv Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 26. Part 1Part 1 Planning and architecture In this part we introduce the planning and architecture considerations for Tivoli Continuous Data Protection for Files V3.1.© Copyright IBM Corp. 2007. All rights reserved. 1
  • 27. 2 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 28. 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. Whats 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© Copyright IBM Corp. 2007. All rights reserved. 3
  • 29. “Value proposition of Tivoli Continuous Data Protection for Files” on page 144 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 30. 1.1 General overview of Tivoli Continuous DataProtection 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 5
  • 31. 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 Traditional backup Protection for Files solutions When to protect Continuous for highly Scheduled, full system important files, scheduled for others How to detect Journal-based on all file Journal-based on some file systems systems Where copies are stored Disk only, locally or Typically on tape remote; Tivoli Storage Manager Storage format Left “native”, online as files Wrapped into a proprietary format Management / Simplified per-client Client-server concept; administration administration only server component typically complexity 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 losses1.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.6 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 32. Although most companies have implemented solutions for protecting enterprisedata, data residing on workstations and notebooks is often underprotected—even though it amounts to 60 percent of all corporate data, accordingto some industry experts. This is particularly true where lost data cansignificantly 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. Today’s 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 helpalleviate clients concerns and provide simple, effective, and efficient dataprotection and integrity. Key client issues driving the requirements for continuousdata 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. Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 7
  • 33. 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. Recovery from a Recovery from tape disk image copy 2. Business and regulatory requirements for data continuity are increasing. Cost 3. Disk costs are declining, making replication technologies more cost effective. 4. Critical data assets found in remote Recovery Time Objective offices, mobile computers, and desktops are often not protected. Tivoli Continuous Data Protection for Files 5. Employee productivity declines with delivers faster recovery of file assets difficult recovery of data and recreation of lost assets. Figure 1-1 Why Tivoli Continuous Data Protection for Files is needed8 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 34. 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. Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 9
  • 35. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 36. 1.2 How Tivoli Continuous Data Protection for Filesworks 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. Tivoli Traditional Continuous Replication Data backups Protection for Files • To-disk duplication • Versioning of files • Lightning fast • Central administration • Real time for important files • Archiving (vaulting) • Tolerant of transient • Retention networks • Highly scalable • Multiple targets 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. Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 11
  • 37. 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 the12 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 38. 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 Protectionfor 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. Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 13
  • 39. – 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 DataProtection for Files For business units dependent on data availability and rapid data recovery, Tivoli Continuous Data Protection for Files provides uniquely efficient and effective14 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 40. data protection to ensure business continuity, employee productivity, and integrityof information assets.For storage managers and administrators responsible for protecting data whilecontaining cost, Tivoli Continuous Data Protection for Files simplifiesheterogeneous storage management and provides real options for an integrateddata 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 usageThe value proposition using Tivoli Continuous Data Protection for Files can besummarized 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) Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 15
  • 41. – 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 42. 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 server1.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 Chapter 1. Introduction to Tivoli Continuous Data Protection for Files 17
  • 43. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 44. 2 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© Copyright IBM Corp. 2007. All rights reserved. 19
  • 45. 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%System32Drivers. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 46. Mirroring: Kernel-based I/O mirroring: Inactive in the current product Replication: Notification of files that are replicatedThe kernel layer is based on a set of rules that set up the conditions under whichcertain activities, or actions, are performed. The rules and actions comepreconfigured to make the product act as designed. When Tivoli ContinuousData 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 Protectionfor 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
  • 47. See Figure 2-1 for an illustration of the relationship between the kernel layer and the daemon or driver. KERNEL FPQ: Critical Kernel injects commands; Audits accumulate in the component. mostly to kick-off replication kernel and are batch- Priority-based activities, but other dumped to daemon for queue. Both round- maintenance too. speed. Platform trip (synchronous) and one-way. Audit Options include Manipulation of “punt if full” or FPQ buffer live database “block if full.” IOCTL interface -Inject XML -Get Audit buffer -Get database, etc Agent has a thread that is always HTML listener in a “read()” to get next queue Replication command; Does a “write()” to Audit thread Service threads respond. (up to 10) Interactive FPA Main thread AGENT Figure 2-1 Agent-driver interaction2.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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 48. 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 eachreplication request at a given priority level, a file is opened and appended withthe specifics of the replication request. These files are in XML format. (See theReplication 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 threadThe main purpose of the audit thread is to wake up periodically and ask thekernel to dump its audit/log buffers. The audit buffers capture file change eventsthat are used by Tivoli Continuous Data Protection for Files for scheduledprotection and other activities. The daemon sleeps for a few seconds and thendrains any messages in the buffer (via an IOCTL request into the kernel). Thebuffer is formatted as a list of XML messages; each message indicates both thefile to add this message to, and the message. The message can be anythingdefined by the “action” and is typically in XML format. It includes variousexpanders (substitutions) for such things as filename, and so on. The following isan example of a message:<change vfs=”Unlink” src=”C:fpbuildchk.log” other=””size=”10697”app=”System”/>The ChangeJournal (sysprotect) rules/actions cause these audits to beaccumulated into a file called ChangeJournal.log in the installation directory. TheLocalPool rule causes audits to accumulate the locally versioned files into theLocalPool.log file.SysprotectWhen this thread is started, its job is to perform a scheduled protection byaddressing all of the files listed in the ChangeJournal.log file. This thread isstarted either on a periodic basis, or when the user selects Start ScheduledBackup Now from the Scheduled Protection window. When started, the threadwill 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 beenaltered (tabulation) and avoids issuing multiple audits for files that have beenrepeatedly altered. This hash has a 2,000 file limit and then it cycles. Sysprotectalso ignores the “vfs” mentioned in the log (see example message above) and Chapter 2. Product architecture, planning, and deployment 23
  • 49. 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 file’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 50. KERNEL FPQ AGENT Repl-1 Repl-1 Replication-1 Main thread thread thread thread Replication- Replication- Queued-Priority Active-Priority Rename Replication- Failed-Priority Replication-Log Figure 2-2 Replication threads2.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? Chapter 2. Product architecture, planning, and deployment 25
  • 51. 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 computer’s 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 user’s unique environment. The very best, but totally impractical, configuration would back up every version of every file and26 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 52. 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. Chapter 2. Product architecture, planning, and deployment 27
  • 53. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 54. 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 Scheduled Vaulting Protection Protection Recommended Recommended for Recommended for Recommended for for which files your most large dynamic files files that you don’t important files. Not like e-mail. want to be changed recommended for nor deleted. large dynamic files like e-mail. How protected Backup copies are Backup copies are Vaulted files and created on storage created on a folders cannot be area. storage area modified nor deleted. Frequency of File is backed up File is backed up No backups. backups whenever it is only at the saved. scheduled time, and only if it has been saved since the previous schedule. Backup copy Local or remote. Remote only. Not applicable. storage area Files protected Files selected in Files selected in Files selected in the Folders and the E-mail the Vault box of the Files box and the Protection page of Files to Protect Applications box of the Settings page of the the Files to Protect Notebook. Files Settings Notebook. page of the selected in the Settings Notebook. Folders and Files dialog of the Advanced page of the Settings Notebook. Chapter 2. Product architecture, planning, and deployment 29
  • 55. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 56. 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 Fileswith 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 user’s 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. Chapter 2. Product architecture, planning, and deployment 31
  • 57. 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 forTivoli 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 target’s 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 office32 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 58. 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 Filesloaded 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. Chapter 2. Product architecture, planning, and deployment 33
  • 59. 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 Filesinstallation 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 60. SoftwareThe 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 Server–Standard 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 followingbrowsers: Internet Explorer®, Version 6.0 and higher Mozilla Firefox 1.5.0.7 and higher Chapter 2. Product architecture, planning, and deployment 35
  • 61. 36 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 62. Part 2Part 2 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.© Copyright IBM Corp. 2007. All rights reserved. 37
  • 63. 38 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 64. 3 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 company’s 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© Copyright IBM Corp. 2007. All rights reserved. 39
  • 65. 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 window40 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 66. 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 prepared4. 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
  • 67. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 68. 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. Chapter 3. Installation and configuration 43
  • 69. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 70. Figure 3-6 Ready to Install window8. 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. Chapter 3. Installation and configuration 45
  • 71. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 72. 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. Chapter 3. Installation and configuration 47
  • 73. 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 Brings you back to the previous page Next Takes you forward to the next page Finish 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. Cancel 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 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 74. Figure 3-9 Welcome pageClick Next to get to the What is Critical page.What is Critical pageUse the What is Critical page (see Figure 3-10 on page 50) to specify the filesand folders that you want to protect. The specified files, folders, and applicationswill be continuously protected, which means Tivoli Continuous Data Protectionfor Files will create backup copies to a storage area as soon as the files arechanged. Chapter 3. Installation and configuration 49
  • 75. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 76. 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 boxThe Folders and Files dialog box gives a summary of the folders and files that arecontinuously protected. It contains either the names of protected files andfolders, or, in the case of an extensive list, the number of items being protectedwhich refer to the items in the list of folders and files. A single list item can specifymore than one file.To view all items in the list and modify the list, click the Details link. The Foldersand Files Settings dialog will display.Folder and Files Settings dialog boxIn the Folder and Files Settings dialog box (see Figure 3-11) you specify foldersand 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 orremove 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.Remove Select one or more list items, then click Remove to remove those items. Chapter 3. Installation and configuration 51
  • 77. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 78. Applications boxThe 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. TheApplications and Extensions box will display.Applications and Extensions boxIn the Applications and Extensions box (see Figure 3-13) you specify a list ofcritical applications to protect.Figure 3-13 Applications and Extensions boxThe Applications and Extensions box presents a list of applications and theirassociated file extensions. Applications that are checked will be continuouslyprotected. 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 adifferent 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. Chapter 3. Installation and configuration 53
  • 79. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 80. 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. Chapter 3. Installation and configuration 55
  • 81. 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 E-mail will not be protected. Hourly E-mail files will be backed up every hour, just after the hour. Daily If you choose this interval, choose the time for the backup. Weekly If you choose this interval, choose the day and time for the backup. Monthly 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 82. Figure 3-15 Remote Storage pageStoring files in a remote storage area will protect the files in case local copies arelost. Backups of continuously protected files and files protected on a scheduleare stored in the same remote area. Tivoli Continuous Data Protection for Files isvery tolerant of intermittently available networks. If remote storage area istemporarily available, Tivoli Continuous Data Protection for Files will queuebackup 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 fieldSpecify 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 Chapter 3. Installation and configuration 57
  • 83. 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=en58 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 84. Tivoli Continuous Data Protection for Files will create backup copies in asub-folder named RealTimeBackupcomputername. For example, if a computername is TestComputer, and the remote storage location is configured with thevalue remoteshare, backup copies will be stored inremoteshareRealTimeBackupTestComputer.If you log in to your computer with a user name and password that is also valid onyour remote storage location, Tivoli Continuous Data Protection for Files willauthenticate transparently into that network location. If you do not log in to yourcomputer with a user name and password that is also valid on your remotestorage location, you will need to log in to the network interactively using anotheraccount with regular privileges. You can log in interactively by using the Net Usecommand. 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 ServerSome Internet Service Providers (ISPs) provide Web-based DistributedAuthoring and Versioning (WebDAV). The WebDAV protocol provides thefunctionality to create, change, and move documents on a remote server. This isuseful for authoring the documents which a Web server serves, but can also beused for general Web-based file storage. If your ISP provides WebDAVfunctionality, Tivoli Continuous Data Protection for Files can store backups on aWeb-based server.In the Location: field. enter your WebDAV server location using the followingformat: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 ServerIn the Location: field, specify the Tivoli Storage Manager server location, usingthe following format: Chapter 3. Installation and configuration 59
  • 85. 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: Administrator’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 86. 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 pageUse the Initial Backup page (see Figure 3-16) to choose if you want to back up allyour files when you finish the wizard.Figure 3-16 Initial Backup pageWhen you first install Tivoli Continuous Data Protection for Files, we stronglyrecommend that you immediately back up all files that you configured forprotection. Without the initial backup, only files that change will be protected. Theinitial backup will protect all of the existing files that you designated for protection. Chapter 3. Installation and configuration 61
  • 87. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 88. Figure 3-17 Summary page with initial backupIt 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 pageAfter the Initial Configuration Wizard has completed, you will see the Status pageas shown in Figure 3-18 on page 64. Chapter 3. Installation and configuration 63
  • 89. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 90. Installation using command-line parameters Silent installation Push installation Pull installation (upgrade) Providing a configuration file3.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. Chapter 3. Installation and configuration 65
  • 91. Example for displaying all installation dialogs in German: TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /l”1031” 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 FilesTivoliCDP_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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 92. 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 suityour 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 /v”INSTALLDIR=C:newdir” is valid, while TivoliCDP_CDPForFiles_3.1.0.45_windows.exe /v “INSTALLDIR=C:newdir” is not. Quotation marks around an options 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 /v”INSTALLDIR=”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 /l”1031” /v”/l*v C:inst.logINSTALLDIR=C:newdir”This command will: Show all installation dialog boxes in German (/l”1031”) Log installation messages in file inst.log in the root of drive C: (/l*v C:inst.log) Chapter 3. Installation and configuration 67
  • 93. 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 FilesTivoliCDP_for_Files. If you want to install to another folder, use this option and specify the folder. REBOOT=ReallySuppress Suppress system reboot after installation. Example using specific options: 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 94. 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:WindowsSystem32 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 FilesTivoliCDP_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). Chapter 3. Installation and configuration 69
  • 95. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 96. Note: Separate the parameter and the value with a blank space, for example: /r “C:CDP 3.1 CodeTivoliCDP_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 FilesTivoliCDP_for_Files. If you want to install to another folder, use this option and specify the folder. The path corresponds to the remote computer. Chapter 3. Installation and configuration 71
  • 97. Example using specific options: fpPushInst.exe Cairo /user:administrator /pwd:cdp4admin /c:C:CDP_Filesfpa.txt /r “C:CDP 3.1 CodeTivoliCDP_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_Filesfpa.txt) Push the Tivoli Continuous Data Protection for Files installer file to the remote computer (/r “C:CDP 3.1 CodeTivoliCDP_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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 98. 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 andconfiguration files every 10 to 20 minutes. If the date of an installer file is morerecent than the file used for the current product level, Tivoli Continuous DataProtection for Files will adopt the new product level.When Tivoli Continuous Data Protection for Files detects a new installer file, amessage displays from the system tray indicating that a new version of thesoftware is being installed (see Figure 3-19).Figure 3-19 Message that a new version is being installedWhen the installation is complete, a message displays from the system trayindicating that the new software has been loaded, and you must reboot toresume data protection (see Figure 3-20).Figure 3-20 Message to reboot system after pull installationFrom the time that Tivoli Continuous Data Protection for Files pulls the upgradeuntil the computer is rebooted, Tivoli Continuous Data Protection for Files stopsprotecting your files. After the reboot, Tivoli Continuous Data Protection for Filescontinues protecting your files. Your protection settings are the same as in theprevious version of the product. Chapter 3. Installation and configuration 73
  • 99. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 100. 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. Chapter 3. Installation and configuration 75
  • 101. 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 Applies your new settings and returns to the Tivoli Continuous Data Protection for Files Status page Apply Applies your new settings but stays in the Settings Notebook Cancel 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 User’s 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 area76 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 102. Whether or not you want to store backup copies on local storage area, remote storage area, neither, or bothFigure 3-21 General pageBack up to: listChoose the location where your local backup copies will be stored. Local backupcopies will be stored in a folder on one of your local drives. The defaultconfiguration is the non-removable local drive which has the most free space.Tivoli Continuous Data Protection for Files will create backup copies in asub-folder named RealTimeBackup. For example, if the local storage area isconfigured as the C: drive, backup copies will be stored in C:RealTimeBackup. Chapter 3. Installation and configuration 77
  • 103. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 104. Local storage only Tivoli Continuous Data Protection for Files will create backup copies only on the local storage area.Remote storage only 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 pageUse 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 Chapter 3. Installation and configuration 79
  • 105. 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 protected80 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 106. refers to the items in the list of folders and files. A single list item can specifymore than one file.Figure 3-23 Folders and Files boxClick the Details link to view all items in the list and modify the list. The Folderand Files Settings dialog box will display.Folder and Files Settings dialog boxSpecify which folders and files to continuously protect by specifying those toinclude 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. Chapter 3. Installation and configuration 81
  • 107. The top of the list box has three menu buttons. Click the buttons to add and remove items from the list. Include Click Include to add files and folders that you want to continuously protect. The Select folders box will open. Exclude Click Exclude to add files and folders that you want to exclude from continuous and scheduled protection. The Select folders box will open. Remove Select a list item, then click Remove to remove that list item. 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. Type 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. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 108. Figure 3-25 Select folders box Note: Only your internal drives can be protected. Any external storage devices are considered remote storage devices.Applications boxThe Applications box (see Figure 3-26) gives a short list of the applications thatare protected.Figure 3-26 Applications boxTo see the complete list of the applications that are protected, click Details. TheApplications and Extensions box will display. Chapter 3. Installation and configuration 83
  • 109. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 110. Click OK in any of the views to update the list of protected files. Click Cancel toleave the box without changing the list of protected files.Vault boxThe Vault box (see Figure 3-28) displays a summary of vaulted folders.Figure 3-28 Vault boxTo change the folders that are protected, click Details. The Vault Settings boxdisplays.Vault Settings boxThe Vault Settings box (see Figure 3-29) displays a list of folders. All files in thesefolders and all sub-folders will be protected from being changed or deleted.Figure 3-29 Vault Settings boxVaulted 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 Click Vault to open a browser to choose the folder(s) to protect.Unvault Click Unvault to remove vault protection from the selected folder and all its files and sub-folders. Chapter 3. Installation and configuration 85
  • 111. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 112. 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 don’t 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 forFiles will continue to operate in the background without any significant impact onyour regular computing activities. Chapter 3. Installation and configuration 87
  • 113. 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. E-mail Protection page 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 backups88 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 114. Figure 3-31 E-mail Protection pageE-mail Application: listTivoli Continuous Data Protection for Files has predefined protection settings forthe following e-mail applications:Lotus Notes Associated suffixes: *.id and *.nsfMicrosoft Outlook Associated suffix: *.pstMicrosoft Outlook Express 5.5, 6 Associated suffixes: *.mbx and *.dbxIn 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 ofthem (Select Applications), all together (All), or Other if you are using anothere-mail application (see Figure 3-32 on page 90). Chapter 3. Installation and configuration 89
  • 115. 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 E-mail will not be protected. Hourly E-mail files will be backed up every hour, just after the hour. Daily If you choose this interval, choose the time for the backup.90 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 116. Weekly If you choose this interval, choose the day and time for the backup.Monthly If you choose this interval, choose the day of the month and time for the backup.Scheduled Backup Settings linkClick the Scheduled Backup Settings link to open the Folders and FilesSettings box (see Figure 3-34) for scheduled backup.Folder and Files Settings boxIn the Folder and Files Settings box you specify folders and files to back up onthe same schedule as e-mail files are backed up.Figure 3-34 Folder and Files Settings box (schedules)Start scheduled backup now check boxThe folders and files that you specify will be backed up on the same schedule asyour e-mail backups. If you want to force a backup now, check the Startscheduled backup now box and click the OK button. Chapter 3. Installation and configuration 91
  • 117. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 118. Figure 3-35 Scheduled backup reports tableThe scheduled backup reports table gives a summary of scheduled backups toremote storage areas for all computers who share a common centraladministration folder. To see the reports table, you must be connected to yourremote storage area.Each row identifies the reports associated with one Tivoli Continuous DataProtection for Files client and contains the following cells:Version The version of Tivoli Continuous Data Protection for FilesLast Backup The last completed scheduled backupFiles 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 Chapter 3. Installation and configuration 93
  • 119. 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. History 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. 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 area94 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 120. Figure 3-36 Remote Storage pageStoring files in a remote storage area will protect the files in case local copies arelost. Backups of continuously protected files and files protected on a scheduleare stored in the same remote area. Tivoli Continuous Data Protection for Files istolerant of intermittently available networks. If a remote storage area istemporarily available, Tivoli Continuous Data Protection for Files will queuebackup 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. Chapter 3. Installation and configuration 95
  • 121. 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 user’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 122. 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 lettingTivoli Continuous Data Protection for Files encrypt the files, you need to beaware that Tivoli Continuous Data Protection for Files does not support promptedencryption. So, if you specify a Tivoli Storage Manager server as your remotestorage area, you must configure non-prompted encryption in the Tivoli StorageManager API client dsm.opt options file. In the dsm.opt file, use the statement:encryptkey saveSee 3.4.1, “Installation and data directories” on page 108 to learn where thedsm.opt file can be found on your computer. For more information about settingencryption 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 User’s 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 buttonSet 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 againUse compression to save space on your remote storage location. Thecompression feature is not compatible with the encryption feature. You can use Chapter 3. Installation and configuration 97
  • 123. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 124. Use sub-file copy for files larger than: fieldIn the Use sub-file copy for files larger than: field, specify the file size thresholdfor using sub-file copy. For files larger than this size, only the changedinformation 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 pageUse 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) Chapter 3. Installation and configuration 99
  • 125. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 126. 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. Chapter 3. Installation and configuration 101
  • 127. 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 User’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 128. 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>BackupAdminReports.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>BackupAdminDownloads. 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 windowYou can open the Central Administration Settings window (see Figure 3-38 onpage 104) by clicking Central Administration from the menu of the TivoliContinuous 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. Chapter 3. Installation and configuration 103
  • 129. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 130. Publish this computer’s settings ... check boxWhen managing Tivoli Continuous Data Protection for Files on a group ofcomputers, it is customary to configure one computer as the template for allcomputers in the group. If you have configured other computers to share thecentral administration folder of this computer, they can be centrally managed bythis computer. Check this box to use this computer’s settings to configure theother computers. When you click the OK button, this computer’s configurationsettings file will be copied to the downloads sub-folder of the centraladministration folder that is shared by the group of computers (see Figure 3-39).All computers that share the central administration folder will adopt the TivoliContinuous Data Protection for Files configuration that you publish.Figure 3-39 Successfully published fpcommands.xml pop-up windowIf you publish this computer’s settings, your management of the group can befurther 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. Chapter 3. Installation and configuration 105
  • 131. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 132. Figure 3-40 Scheduled backup reports tableThe scheduled backup reports table gives a summary of scheduled backups toremote storage areas for all computers that share a common centraladministration folder. For more information on central administration folders, referto “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 DataProtection for Files client, and contains the following cells:Version The version of Tivoli Continuous Data Protection for Files.Last Backup The last completed scheduled backup. Chapter 3. Installation and configuration 107
  • 133. 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. 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. History 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.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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 134. 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 Data directory (fpa.txt, dsm.opt, log files, and so on.) a Windows XP, 2003 C:Program C:Documents and SettingsAll – new installation FilesTivoliCDP_for_Files UsersApplication DataTivoliCDP_for_Files Windows XP, 2003 C:Program C:Program – upgrade installation FilesTivoliCDP_for_Files FilesTivoliCDP_for_Files MS Vista C:Program C:ProgramDataTivoliCDP_for – new installation FilesTivoliCDP_for_Files _Files 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 SettingsAdministratorMy Documentstestfile.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. Chapter 3. Installation and configuration 109
  • 135. 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:dirfish.doc and C:fishtestfile.doc and C:fishfoodsomething. 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:FisHtestfile.doc but not C:dirfish.doc and not C:fishfoodsomething. Note: The pattern is not case-sensitive. Table 3-2 File and folder pattern matches This pattern ... ... matches these folders and files on your computer: myDir or C:myDir mYdiR or C:myDirContacts *myDir* or C:myDirContactscontacts.txt *mydir* C:ProjectsmyDir C:ProjectsmyDirmyThings C:ProjectsmyDirmyThingsthings.doc C:ProjectsmyDirmyThingsmyPhoto.jpg D:NotesmyDir *myDir C:myDir C:ProjectsmyDir D:NotesmyDir myDir* d:*mydir* D:NotesmyDir110 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 136. This pattern ... ... matches these folders and files on your computer: my best C:BooksMy Best.doc C:Photos.jpgMy Best Photo C:Photos.jpgMy Best PhotoBest.jpg F:ProjectsMy Best Project F:ProjectsMy Best ProjectDream.xls .jpg C:Photos.jpg C:Photos.jpgmyHouse.bmp C:Photos.jpgMy Best PhotoBest.jpg C:ProjectsmyDirmyThingsmyPhoto.jpg *.jpg C:Photos.jpg C:Photos.jpgMy Best PhotoBest.jpg C:ProjectsmyDirmyThingsmyPhoto.jpg E: or All files and folders on the E: drive. 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. Chapter 3. Installation and configuration 111
  • 137. 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 File is specified on Is file protected? Include list Exclude list No No No No Yes No Yes No Yes Yes 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 138. .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 folderwill not be protected. All other files in My Documents folder and its sub-folderswill be protected.For another example, using the same list above, if you choose an application inthe 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 youused instead temp (without the closing folder delimiter), this would have a verydifferent effect. Even though this might seem like a small change, it has apotentially large impact. All files which have temple, temptation, temperature,template, and other variations of temp*, would be excluded from protection. Chapter 3. Installation and configuration 113
  • 139. 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_VaultKeepSafeRetain 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. KeepSafeRetainForever 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. KeepSafeRetain 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 3years114 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 140. Retain_3yearsRetain-23DAYS_4minutesRetain 1000 daysKeepSafeRetainUntil DateSpecify 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 minuteThe following are valid examples:RetainUntil20190117153045RetainUntil 20200101RetainUntil20200101RetainUntil_20200101 Chapter 3. Installation and configuration 115
  • 141. 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 aC: Back up to How many versions to keep 20 Maximum space for backups 500 MB Continuous protection level 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 142. 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 TivoliCDP_for_Files Applications No applications Vault 0 folders Start an initial backup with the new settings left uncheckedE-mail Protection pageThe default values for your e-mail protection and your schedules are in Table 3-6on page 118. Chapter 3. Installation and configuration 117
  • 143. Table 3-6 E-mail Protection page default settings E-mail Protection page E-mail Application Select Application (nothing preselected) E-mail Application Data Folder (wildcards nothing predefined allowed) How often to protect your e-mail Never Scheduled Backup Settings 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 None Selected Location nothing predefined How many versions to keep 5 Maximum space for backups 40 GB Advanced Settings Encrypt backups not preselected Compress backups not preselected Use sub-file copy left unchecked Use sub-file copy for 50 MB files larger than 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 Enabled Performance Settings Do not locally back up files 10 GB larger than118 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 144. Advanced page Do not remotely back up files 1 GB larger than Maximum remote transfer rate 1 GbsScheduled Backup Settings nothing predefined Chapter 3. Installation and configuration 119
  • 145. 120 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 146. 4 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© Copyright IBM Corp. 2007. All rights reserved. 121
  • 147. 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 Local Disk Remote Disk WebDAV WebDAV (IIS Tivoli Storage Feature (external disk (Apache) 5.0/6.0) Manager / file server) Encryption Not supported Supported APAR opened APAR opened Supported Compression Not supported Supported APAR opened APAR opened Supported Vault Supported Not supported Not supported Not supported Not supported Sub-file copy Not supported Supported Supported Full backups Full backups Management N/A Supported Supported Supported Must specify area 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 Manager’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 148. 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 1 to local disk Amsterdam Active daemon identifyng the modified files Windows Vista User desktop 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
  • 149. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 150. Figure 4-3 Files to protect in a single user with local disk configurationFigure 4-3, shows which files we have selected to protect. We are only protectingthe Example Data directory.During the initial replication, Tivoli Continuous Data Protection for Files willcreate a directory called RealTimeBackup on the drive specified in General tabconfiguration. In our scenario the drive C: was specified. Chapter 4. Proof of concept scenarios 125
  • 151. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 152. Schedule protection to 11 12 1 remote storage 10 2 9 3 8 4 7 5 6 CDP 3 Continuous protection to 2 local disk 1 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 diskFigure 4-5 Single computer, with external storageThe 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 featureThis scenario is very similar to what we discussed previously, but with the addedexternal disk as the target storage area for our scheduled protection. Thefollowing screens will walk you through the configuration described above. Chapter 4. Proof of concept scenarios 127
  • 153. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 154. Figure 4-7 Selection of important files to continuously protect in a single user scenariowith external diskFigure 4-7 shows that the My Documents directory was added to our selectionof continuously protected files. Chapter 4. Proof of concept scenarios 129
  • 155. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 156. Figure 4-9 Configuring files for scheduled protectionFigure 4-9 shows how to configure files for scheduled protection. It is necessaryto 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 Settingslink. Include all extensions and directories that you want to protect with thescheduled 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. Chapter 4. Proof of concept scenarios 131
  • 157. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 158. Figure 4-11 Start an initial backupFigure 4-11 shows how to start an initial backup of files under either continuousor scheduled protection. We recommend that you use this option when you arenot using your computer. The first scan takes some time to run, depending on thesize of your files and network traffic.CompressionAnother way to save space on your remote location is to enable the filecompression feature within Tivoli Continuous Data Protection for Files. If youconfigure Tivoli Continuous Data Protection for Files to use compression, youmust 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. Chapter 4. Proof of concept scenarios 133
  • 159. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 160. Figure 4-13 Replicated directory and filesFigure 4-13 shows the replicated directory and files. The selected replicated filepresentation1 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., enablingcompression 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,806KB and the replicated file is 276,807 KB. At this point you are probably wonderingwhy Tivoli Continuous Data Protection for Files does not just back up the fileuncompressed when it realizes the compressed file is going to be bigger than thesource file. It is because the compression feature was added to save bandwidthon the LAN.By the time Tivoli Continuous Data Protection for Files realizes the file is gettingbigger while being compressed, most of the file has already been sent to thebackup directory. If you are sending the file to a backup server over the LAN, it is Chapter 4. Proof of concept scenarios 135
  • 161. 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 12 11 1 10 2 3 9 3 8 4 7 5 6 12 11 1 10 2 9 3 8 4 7 5 6 2 2 3 1 CDP 2 Paris Madrid Windows 2003 Windows XP HTTP Server 6.1 Mobile Computer 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 162. – Desktop computer– Intel Pentium 4 CPU 2.40 GHz– 512 MB memory– Microsoft Windows Server® 2003– IBM HTTP Server V6.1Madrid– 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 Chapter 4. Proof of concept scenarios 137
  • 163. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 164. Figure 4-16 Important files continuous protection in a single user with an ISP connectionFigure 4-16 shows that the ImportantFiles directory was added to the continuousprotection. Chapter 4. Proof of concept scenarios 139
  • 165. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 166. 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 Chapter 4. Proof of concept scenarios 141
  • 167. Figure 4-19 Configure the frequency and time to start the scheduled protection to an ISP provider142 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 168. Figure 4-20 Files for scheduled protectionFigure 4-20 shows the files configured for scheduled protection. Each hour TivoliContinuous Data Protection for Files will scan the directory ExampleData toverify whether any files have changed since the last backup. All files that havechanged since scheduled protection was configured will be replicated at thescheduled interval time.Figure 4-21 Activity report for changed filesAs an example, the files in Example Data directory docu1.doc, pres1.ppt, andsheet1.xls were modified. Figure 4-21 shows that all changed files werereplicated to both local and remote storage. Chapter 4. Proof of concept scenarios 143
  • 169. 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 file’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 170. 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 Chapter 4. Proof of concept scenarios 145
  • 171. 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: 12 11 1 10 2 9 3 8 4 7 5 6 LAN 12 12 12 12 11 1 11 1 11 1 11 1 10 2 10 2 10 2 10 2 9 3 9 3 9 3 9 3 8 4 8 4 8 4 8 4 7 5 7 5 7 5 7 5 6 6 6 6 2 2 2 2 CDP CDP CDP CDP 1 1 1 1 Cairo Dakar Amsterdam Madrid Windows 2003 Windows 2000 Windows Vista Windows XP Pentium 4 Pentium 4 Pentium 4 Intel Dual Core 1,5 GB memory 1,5 GB memory 1 GB memory 1 GB memory User desktop User desktop User desktop Mobile computer 3 DVD Disks External Berlin Drive Windows 2003 Pentium 4 1,5 GB memory File Server 1 Active daemon identifying the modified files: - Scheduled protection sends to journal list 2 At schedule time verifies the journal list and replicates the pending files to the file server 3 Backs up files on file server to the DVD Disks 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 = Daily146 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 172. Figure 4-25 General configuration without continuous protectionFigure 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 forFiles, you need to map a drive on each user’s computer to the target file server.The shared directory cdp_fileserver is already configured on Berlin server. SeeFigure 4-26 on page 148. Chapter 4. Proof of concept scenarios 147
  • 173. 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 server148 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 174. Figure 4-28 Configure remote storage for scheduled protectionFigure 4-28 shows the Remote Storage page configuration for this scenario.The configuration is: – Backup to: File Server (Berlin server) – Location: berlincdp_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) Chapter 4. Proof of concept scenarios 149
  • 175. 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 protection150 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 176. 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 doesn’t want to invest money in a file server as a target for backup copies, but the customer needs to back up the user’s 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: Chapter 4. Proof of concept scenarios 151
  • 177. 12 11 1 10 2 9 3 LAN 8 4 7 5 6 3 3 3 3 12 12 12 11 1 11 1 11 1 12 11 1 10 2 10 2 10 2 10 2 9 3 9 3 9 3 9 3 8 4 8 4 8 4 7 5 7 5 7 5 8 4 6 6 6 7 5 6 CDP CDP CDP CDP 1 2 1 2 1 2 1 2 Cairo Dakar Amsterdam Izmir Windows 2003 Windows 2000 Windows Vista Windows XP Pentium 4 Pentium 4 Pentium 4 Pentium 4 1,5 GB memory 1,5 GB memory 1 GB memory 512 GB memory User desktop User desktop User desktop User desktop 4 Tape Library Berlin Windows 2003 Pentium 4 1,5 GB memory Tivoli Storage Manager Express 1 Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list 2 Replicates the files in a local disk 3 At schedule time verifies the journal list and replicates the pending files to Tivoli Storage Manager Express 4 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 178. Tivoli Storage Manager Express configurationThe Tivoli Storage Manager Express server is installed and configured on theBerlin server. It is not necessary to install the backup/archive client, TivoliContinuous Data Protection for Files will use the API (application programinterface) to send files to Tivoli Storage Manager Express. The default dsm.opt islocated on the C:Documents and SettingsAll UsersApplicationDataTivoliCDP_for_Files directory.You must register the machines where Tivoli Continuous Data Protection for Filesresides 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 / cdp4admin3. Select the Computers and applications option as shown in Figure 4-32.Figure 4-32 Computers and applications option on Tivoli Storage Manager Express Chapter 4. Proof of concept scenarios 153
  • 179. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 180. 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 owner’s e-mail address: To send notification about schedule information Chapter 4. Proof of concept scenarios 155
  • 181. Figure 4-35 Installation settings 6. Confirm settings, and finish the task.156 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 182. Figure 4-36 Confirm settings7. 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 FilesTivoliTSMserver>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 service9. Start Tivoli Storage Manager Express in foreground mode, as follows. Chapter 4. Proof of concept scenarios 157
  • 183. C:Program FilesTivoliTSMserver>dsmserv ANR0900I Processing options file C:Program FilesTivoliTSMServer1 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 184. TSM:TSM-DEMO> halt ANR0991I Server shutdown complete.Figure 4-40 Shutdown Tivoli Storage Manager Express12.Start Tivoli Storage Manager Express service. C:Program FilesTivoliTSMserver>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 Express13.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 Chapter 4. Proof of concept scenarios 159
  • 185. 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, let’s configure Tivoli Continuous Data Protection for Files to work with Tivoli Storage Manager Express.160 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 186. Figure 4-45 General configurationFigure 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) Chapter 4. Proof of concept scenarios 161
  • 187. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 188. Figure 4-47 Remote storage configuration for Tivoli Storage Manager ExpressFigure 4-47 shows the configuration to send files to Tivoli Storage ManagerExpress: – 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 whenconnecting to Tivoli Storage Manager Express, see Figure 4-48 on page 164. Chapter 4. Proof of concept scenarios 163
  • 189. Figure 4-48 Node password on Tivoli Storage Manager Express server164 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 190. Figure 4-49 Select applications, files, and frequency to back up to Tivoli StorageManager Express Chapter 4. Proof of concept scenarios 165
  • 191. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 192. Figure 4-51 Filespace on Tivoli Storage Manager Express4.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: Chapter 4. Proof of concept scenarios 167
  • 193. 12 11 1 10 2 9 3 8 4 7 5 6 LAN 3 3 3 3 3 12 12 12 12 11 1 11 1 11 1 11 1 10 2 10 2 10 2 10 2 9 3 9 3 9 3 9 3 8 4 8 4 8 4 8 4 7 5 7 5 7 5 7 5 2 2 2 2 6 6 6 6 2 4 CDP CDP CDP CDP TSM Client 1 1 1 1 Tokyo Dakar Amsterdam Rome Athens 4 Windows 2003 Windows 2000 Windows Vista Windows XP Windows 2003 Pentium 4 Pentium 4 Pentium 4 Intel Dual Core Pentium 4 1,5 GB memory 1,5 GB memory 1 GB memory 1 GB memory 1,5 GB memory User desktop User desktop User desktop Mobile computer File Server Berlin Windows 2003 Pentium 4 1 GB memory TSM Server Express 1 Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list 2 Replicates the files in remote storage 3 At schedule time verifies the journal list and replicates the pending files to an ISP provider 4 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 user’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 194. Figure 4-53 Map network drive and reconnect at logonFigure 4-54 Configure user name and password to access the file server Chapter 4. Proof of concept scenarios 169
  • 195. 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 only170 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 196. 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 backupFigure 4-56 shows the files to protect continuously. In this scenario all machineshave this directory created which contains all files designated for continuousprotection. Chapter 4. Proof of concept scenarios 171
  • 197. 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: athenscdp_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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 198. – 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 Chapter 4. Proof of concept scenarios 173
  • 199. 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 user’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 200. It is critically important that the password be remembered and kept in a place thatis retrievable in the event of a machine or disk failure. If the password is lost, allencrypted data is completely unretrievable. The password is absolutely critical.You can then verify that the files are encrypted on the file server. SeeFigure 4-61.Figure 4-61 Replicated files with encryption option on file serverTivoli Continuous Data Protection for Files cannot protect backup copies thathave already been encrypted by another instance of Tivoli Continuous DataProtection for Files. This is an issue only if you send encrypted files to a fileserver with Tivoli Continuous Data Protection for Files, and then try to send thesefiles to another file server or to an ISP provider using a local copy of TivoliContinuous Data Protection for Files. If you configure Tivoli Continuous DataProtection for Files to encrypt the backup copies to a file server, you must not useTivoli Continuous Data Protection for Files to protect the encrypted backupcopies in that file server. You can use Tivoli Storage Manager or another backupsolution to protect the encrypted backup copies on that file server. Chapter 4. Proof of concept scenarios 175
  • 201. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 202. Figure 4-63 Excluded files on Tivoli Storage Manager Express clientYou need to edit the file C:Program Filestivolitsmbaclientdsm.opt to removethis exclusion. See Figure 4-64 on page 178. Chapter 4. Proof of concept scenarios 177
  • 203. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 204. Figure 4-65 Files to backup on Tivoli Storage Manager ExpressBackup policyThe number of backup versions on the file server will be controlled by TivoliContinuous Data Protection for Files, while Tivoli Storage Manager Express willcontrol the number of files that will be backed up from the file server.With Tivoli Storage Manager Express, you have a default backup policy whichretains files locally on disk for 14 days after the original backup. However, TivoliStorage Manager Express can be configured to use media copies to keepbackups for longer than the default 14 days allowing you to restore data after ithas been expired from the backup server’s 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. Chapter 4. Proof of concept scenarios 179
  • 205. 4.4 Tivoli Continuous Data Protection for Files in anenterprise 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 offices4.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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 206. Department A LAN CDP Mobile Computers TSM Department B CDP TSM . . . CDP Department Z TSM CDP TSM Tape LibraryFigure 4-66 Example of enterprise environment with Tivoli Storage Manager centricWhen you have a significant number of individual desktops loaded with TivoliContinuous Data Protection for Files it is not advisable to send backups directlyto Tivoli Storage Manager. Each file that needs to be replicated opens a newconnection on the server, so it is easy to imagine a scenario with anoverwhelmed Tivoli Storage Manager server. If you intend to send data fromTivoli Continuous Data Protection for Files to a Tivoli Storage Manager server,consider having different Tivoli Storage Manager server instances for your TivoliStorage Manager client backups and your Tivoli Continuous Data Protection forFiles 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. Chapter 4. Proof of concept scenarios 181
  • 207. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 208. Berlin Central Administration 12 11 1 10 2 9 3 LAN 8 4 7 5 6 3 3 3 3 12 12 12 11 1 11 1 11 1 12 10 2 10 2 10 2 11 1 10 2 9 3 9 3 9 3 9 3 8 4 8 4 8 4 7 5 7 5 7 5 8 4 6 6 6 7 5 6 CDP CDP CDP CDP 1 2 1 2 1 2 1 2 Bruge Dakar Amsterdam Izmir Windows 2003 Windows 2000 Windows Vista Windows XP 4 Pentium 4 Pentium 4 Pentium 4 Pentium 4 1,5 GB memory 1,5 GB memory 1 GB memory 512 GB memory User desktop User desktop User desktop User desktop Helsinki Tape Library Windows 2003 Dual Core 3 GB memory Tivoli Storage Manager 1 Active daemon identifying the modified files: - Continuous protection sends to replication thread - Scheduled protection sends to journal list 2 Replicates the files in a local disk 3 At schedule time verifies the journal list and replicates the pending files to Tivoli Storage Manager 4 Migrates files to tapesFigure 4-67 Lab environment (Tivoli Storage Manager centric)Before configuring Tivoli Continuous Data Protection for Files, it is necessary toproperly configure Tivoli Storage Manager.Tivoli Storage Manager configurationTivoli Storage Manager enables you to protect your organization’s data fromfailures and other errors by storing backup, archive, space management, andbare-metal restore data, as well as compliance and disaster recovery data in ahierarchy of offline storage. Because it is highly scalable, Tivoli Storage Managercan help protect computers running a variety of different operating systems, onhardware ranging from notebooks to a z/OS system and connected togetherthrough the Internet, wide area networks (WANs), local area networks (LANs), orstorage area networks (SANs). It uses Web based management, intelligent datamove-and-store techniques, and comprehensive policy based automation thatwork together to help increase data protection and potentially decrease time andadministration costs. Note: For more details on Tivoli Storage Manager go to http://www-306.ibm.com/software/tivoli/products/storage-mgr/. Chapter 4. Proof of concept scenarios 183
  • 209. 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 SettingsAll UsersApplication DataTivoliCDP_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 Administrator’s 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 210. 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: admin Enter your password: ***** 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 Platform Policy Domain Days Since Days Since Locked? Name Last Acce- Password ss Set ------------------------- -------- -------------- ---------- ---------- ------- AMSTERDAM (?) STANDARD <1 <1 No BRUGE (?) STANDARD <1 <1 No DAKAR (?) STANDARD <1 <1 No IZMIR (?) STANDARD <1 <1 NoFigure 4-68 Add nodes to Tivoli Storage Manager server Chapter 4. Proof of concept scenarios 185
  • 211. 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 General configuration Figure 4-69 shows the configuration for continuous protection in this scenario: – Backup to: C: (Local disk only)186 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 212. – 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 Files to protect in continuous protectionFigure 4-70 shows the files designated to protect continuously. Chapter 4. Proof of concept scenarios 187
  • 213. 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 214. Figure 4-72 Node password on Tivoli Storage ManagerFigure 4-73 Select applications, files, and frequency to back up to Tivoli StorageManager Server Chapter 4. Proof of concept scenarios 189
  • 215. Figure 4-74 Create the include list for scheduled protection 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 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 216. Figure 4-75 Advanced settingsFigure 4-75 shows the Advanced configuration for Tivoli Continuous DataProtection 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 GBCentralized AdministrationUse the Central Administration Settings window to identify administration foldersfor this computer and to manage the configuration settings on other computers.Select the option Central Administration on the Tivoli Continuous DataProtection for Files main panel, see Figure 4-76 on page 192. Chapter 4. Proof of concept scenarios 191
  • 217. 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 Central Result Remote location Administration storage location (Configured in Folders and Central remote storage Administration tab) Berlin Administrator Not applicable Not applicable Not applicable192 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 218. Computer Name Group Remote storage Central Result Remote location Administration storage location (Configured in Folders and Central remote storage Administration tab)Bruge Group TSM tsm:helsinki BerlinC$cdp_a BerlinC$cdp_a dmin dminDakar Group TSM tsm:helsinki BerlinC$cdp_a BerlinC$cdp_a dmin dminAmsterdam Group TSM tsm:helsinki BerlinC$cdp_a BerlinC$cdp_a dmin dminIzmir Group TSM tsm:helsinki BerlinC$cdp_a BerlinC$cdp_a dmin 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 BerlinC$cdp_admin$MACHINEBackupAdminReports. • 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 BerlinC$BackupAdminDownloads. – 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 Chapter 4. Proof of concept scenarios 193
  • 219. 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 configuration194 Deployment Guide Series: Tivoli Continuous Data Protection for Files V3.1
  • 220. Check the box Publish this computer’s settings as the configurationtemplate for other computers to use, see Figure 4-77 on page 194. When youclick the OK button, this computer’s configuration settings file will be copied tothe downloads sub-folder of the central administration folder that is shared by thegroup of computers. All computers that share the central administration folder willadopt the Tivoli Continuous Data Protection for Files sett