IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

Restore WASRoot UserThe restore was command specifies whether to restore the WebSphere ApplicationServer (WAS) Network Deployment Manager (contains setup, application files, andconfiguration information) or the Application Server from the Tivoli StorageManager server. The Application Server must be stopped for the restore to proceed.You can also restore the Network Deployment Manager, the Application Server,and their instances simultaneously in separate sessions.Use the wastype option to specify whether to restore the Network DeploymentManager (ND) or Application Server (APP) associated with the node name of theinstance of WAS that you want to restore. The default is ND. See “Wastype” onpage 390 for more information.WAS instance restore proceduresYou can use the following procedure if your entire WebSphere installation iscorrupted and it must be reinstalled, or you are installing WAS on a new machine:1. Install WAS on a machine with the same name and IP address as the machineon which the back up was performed. If you backed up a NetworkDeployment Manager on machine ebarton, the restore must also be performedon machine ebarton. Install the same type of WAS as the back up (either ND orAPP). When installing, choose the same node and cell names as the backup. Forexample, if you backed up an ND with a cell name of EdCell and node nameof EdNode then the new server must also use these names. Install to the samelocation in which the backup was performed. For example, if the backup wasperformed on an APP server installed at /home/WebSphere/App, the newserver must also be installed at /home/WebSphere/App. After installationensure that the server is stopped.Notes:a. You can use the washome option in your client user options file (dsm.opt)to specify an override base install path for the Application Server. See“Washome” on page 387 for more information.b. You can use the wasndhome option in your client user options file(dsm.opt) to specify an override base install path for the NetworkDeployment manager. See “Wasndhome” on page 388 for more information.2. Restore the WAS node.3. Start the server.4. If the server is an ND, you can now attach any remote nodes. The ND andremote nodes will then synchronize.Use the following procedure to restore to the same existing instance of a server.This procedure assumes that there is a preexisting WAS installation that is runningand has a backup stored on the Tivoli Storage Manager server:1. Stop the WAS server to be restored.2. Restore the correct WAS node (same wastype and node name as the server thatwas stopped) to the same location.3. Start the server.On an ND, the server will synchronize the restored data with the remote nodessince they are already connected.Chapter 10. Using commands 481