12.07.2015 Views

Installation and User's Guide

Installation and User's Guide

Installation and User's Guide

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Volume Shadowcopy Service (VSS) is also supported for OFS <strong>and</strong> online imageoperations. You can enable VSS by setting the snapshotproviderfs <strong>and</strong>snapshotproviderimage options in the dsm.opt file. If you use VSS, you do notneed to install LVSA.Use the Setup wizard to select NONE, VSS, orLVSA for each of the OFS <strong>and</strong>online image functions. If LVSA is selected <strong>and</strong> it is not already installed on yoursystem, it is installed at this time.If you are migrating from a previous version of the Tivoli Storage Manager clientwhere you were using the LVSA for OFS or online image, <strong>and</strong> you decide duringthe installation to continue to use the LVSA, then you do not need to explicitly setthe snapshotproviderfs or snapshotproviderimage options. Since you do not needto set these options, it is easier to install the new client on a large number ofsystems, because the dsm.opt file will not need to be updated to continue to usethe OFS or online image functions.Automatic client deployment (Windows)The Tivoli Storage Manager server administrator can automatically deploy a clientto client workstations that already have the backup-archive installed.You can use the autodeploy option to conditionally enable automatic clientdeployment, if the deployment does not require a restart of the client workstation.Start the client deployment process as a post-schedule comm<strong>and</strong> of the scheduler.By default, the autodeploy option is enabled, <strong>and</strong> the client workstation is restartedif required. To use automatic deployment when you do not need to restart thesystem, add the autodeploy noreboot option.Important: For automatic client deployment to be operational, the followingconditions apply:v The client computer must have a minimum of 2 GB free disk space.v The Windows task scheduler service must be running.v The passwordaccess option must be set to generate.To store the password in the local Windows registry, the node must log on fromthe local workstation at least once, to provide the password.If the client automatic deployment process cannot find the node password in theregistry, these things occur:– The deployment process does not start.– A warning message is logged in the setup.log file.Here are some examples of the warning messages that are logged:Sun 10/11/2009 10:16:04.35 The deployclient.bat script is started.Sun 10/11/2009 10:16:04.37 deployclient.bat is removing the deploymentmanager <strong>and</strong> temporary files possibly left from the previous installation.Sun 10/11/2009 10:17:10.53 WARNING: Still waiting for the result of querysystem information.Ensure that "PASSWORDACCESS GENERATE" is set in the client options file<strong>and</strong> that a connection to the server can be made without being promptedfor a password.– The dsmc query systeminfo comm<strong>and</strong> is left running.– The deployment process cannot start, so no messages are sent to the server.vThe client is deployed from the server as a scheduled task. Therefore, the clientscheduler must be running.4 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: <strong>Installation</strong> <strong>and</strong> <strong>User's</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!