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.

that the workstation is not automatically restarted, use autodeploy=noreboot.The deployment will be cancelled if a restart is required. The current client isnot affected.v If a restart is required, the deployment manager initiates a restart for theclient computer <strong>and</strong> exits. However, it is possible that you cancel orinterrupt the restart. Since the deployment manager is already terminated,no message will be sent to the server to indicate the failure of the restart.The deployment result is still successful. It is your responsibility to restartthe computer so that the new client deployment completes.No Specifies that the client is not automatically deployed from the server.NORebootSpecifies that the deployment manager never automatically restarts the clientcomputer, even if a restart is required. If a restart is required, allowingautomatic deployment to many machines with the NOReboot parameter canresult in only a partial update for a large number of clients.To alleviate this problem, the deployment manager tries to detect if a restart isrequired. If a restart is required, the deployment manager cancels thedeployment before the new client installation. This guarantees that the clientcomputer still has a working backup-archive client, <strong>and</strong> the new clientdeployment can be rescheduled.There are rare cases where the deployment manager cannot detect the restart.For example, if client processes are started from a script. In these cases, thenew client installation will continue, but a manual restart of the clientcomputer is required.ExamplesOptions file:autodeploy noComm<strong>and</strong> line:Does not apply.Important: Use schedmode prompted in conjunction with the autodeploy option, toenable the scheduler to process the client deployment schedule immediately.Related concepts“Automatic client deployment (Windows)” on page 4AutofsrenameThe autofsrename option renames an existing file space that is notUnicode-enabled on the Tivoli Storage Manager server so that a Unicode-enabledfile space with the original name can be created for the current operation.When you specify autofsrename yes in your client options file, <strong>and</strong> the servervalue of autofsrename is set to client, Tivoli Storage Manager generates a uniquename by appending _OLD to the file space name you specify in the currentoperation. For example, Tivoli Storage Manager renames the file space\\your-node-name\h$ to \\your-node-name\h$_OLD. If the new file space name istoo long, the suffix replaces the last characters of the file space name, as follows:\\your-node-name_OLD310 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!