Restoring IBM Information Server components [DataStage]

If you backed up the files, directories, and databases associated with IBM Information Server, you can restore these components to recover your data in the event of hardware failure or other disaster.

This task assumes that you are starting on a clean computer on which IBM Information Server has not been installed. It also assumes that the host name of the computer is identical to that of the computer on which the backup was performed and that all components are being restored in the exact same location that they originally were in.

 

To restore IBM Information Server components:

1.    Reinstall IBM Information Server. Select the same configuration as the prior installation. If you created an installer response file during the initial installation and have a copy of that file, you can pass that file to the installer from the command line using the following command: install.exe -options <response file>

2.    Disconnect all user sessions. Users should not be allowed to log in to the system at any point during the restore. Otherwise, it is possible that the restore may fail or users may lose data which will be overwritten when the metadata repository is restored.

3.    Stop IBM Information Server components:

a.    Stop the following services: ASB Agent, Logging Agent, DataStage Telnet Service, DSRPC Server, and DataStage Engine Resource Service.

§  Windows: Select Control Panel > Administration Tools > Services or stop the services from the command line using the following commands:

§  sc stop ASBagent

§  sc stop Logging Agent

§  sc stop dsrpc

§  sc stop dstelnet

§  sc stop DSEngine

§  UNIX: Run the following command to stop the ASBagent and the Logging Agent. This command is located in the /opt/IBM/InformationServer/ASBNode/bin directory.

§  ./NodeAgents.sh stop

You must include the "./" at the start of the command unless the directory in which the commands is located is defined in your PATH environment variable.

Stop the WebSphere DataStage services by running the bin/uv –admin –stop command from the WebSphere DataStage engine installation directory which is located, by default, in /opt/IBM/InformationServer/Server/DSEngine. You must run the command as the IBM Information Server administration user (or root) and have executed the dsenv profile.

b.    Stop WebSphere Application Server. Run the stopServer command from the command line. The stopServer command is located in the following directory by default:

§  Windows: C:\IBM\WebSphere\AppServer\bin

§  UNIX: /opt/IBM/InformationServer/WebSphere/AppServer/bin

4.    Restore the metadata repository using database management tools. See the vendor documentation for your database platform.

5.    If WebSphere Information Analyzer was installed, restore the analysis database used by WebSphere Information Analyzer. See the vendor documentation for your database platform.

6.    If WebSphere QualityStage was installed, restore the results database used for the WebSphere QualityStage Match Designer output. See the vendor documentation for your database platform.

7.    From the command line, use the restoreConfig command to restore the WebSphere Application Server profile. The restoreConfig command is located in the following directory by default:

o    Windows: C:\IBM\WebSphere\AppServer\bin

o    UNIX: /opt/IBM/InformationServer/WebSphere/AppServer/bin

8.    Replace the contents of the AppServer\profiles\default directory with the backed up copy.

In Windows, this directory is located by default in C:\IBM\InformationServer\AppServer\profiles\default\classes.

In UNIX, this directory is located by default in
/opt/IBM/InformationServer/AppServer/profiles/default/classes.

9.    Replace the contents of the installation directory and its subdirectories with the backed up copy. In Windows, this directory is located by default in C:\IBM\InformationServer. In UNIX, this directory is located by default in /opt/IBM/InformationServer.

10.  If needed, restore other files and software.

 .     Restore external files or libraries used by WebSphere DataStage jobs.

a.    Ensure that third party applications required by WebSphere MetaBrokers or bridges are reinstalled.

b.    Restore the environment variables and other settings, such as ODBC DNS.

11.  Restart WebSphere Application Server and other services.

 .     Start the WebSphere Application Server. Run the startServer command from the command line. The startServer command is located in the following directory by default:

§  Windows: C:\IBM\WebSphere\AppServer\bin

§  UNIX: /opt/IBM/InformationServer/WebSphere/AppServer/bin

a.    In Windows, select Control Panel > Administration Tools > Services and start the following services: ASB Agent, Logging Agent, DataStage Telnet Service, DSRPC Server, and DataStage Engine Resource Service. In Windows, you can also start the services from the command line using the following commands:

§  sc start ASBagent

§  sc start Logging Agent

§  sc start dsrpc

§  sc start dstelnet

§  sc start DSEngine

In UNIX, Run the following command to stop the ASBagent and the Logging Agent. This command is located in the /opt/IBM/InformationServer/ASBNode/bin directory.

§  ./NodeAgents.sh start

You must include the "./" at the start of the command unless the directory in which the command is located is defined in your PATH environment variable.

You can start the WebSphere DataStage services by running the bin/uv –admin –start command from the WebSphere DataStage engine installation directory which is located, by default, in /opt/IBM/InformationServer/Server/DSEngine. You must run the command as the IBM Information Server administration user (or root) and have executed the dsenv profile.

njoy the simplicity.......
Atul Singh