Archiving or backing up the Infrastructure Management Server

Before archiving or backing up the server, read the following guidelines and restrictions:

• You cannot change the partition name. The original partition name must be retained for proper operation of internal components.
• Do not change the IP address. If you change the IP address of the server, all remote agents must reinitialize on reconnecting, and you must change the IP address of the local agent to the new IP address after you restart the system. 
• For optimum safety and fault tolerance, send the archives to a different physical disk or to a tape drive. Minimally, send the archives to a disk partition other than the installation partition where the BMC TrueSight Infrastructure Management Server is located. 
• You do not have to shut down the BMC TrueSight Infrastructure Management Server to archive. If you use the database snapshot utility, the archive has the following components:
  • A snapshot of the database created by the pw database archive command
  • A tar of all the files and subdirectories in the installationDirectory/pw directory.
    However, when you perform the archive while the BMC TrueSight Infrastructure Management Server is running, you cannot use the tarred database files because the SAP SQL Anywhere database and the transaction log will be out of sync when they are added to the tar, and when the database files are restored from this tar, the database might not be able to resolve the discrepancy.
     If you shut down the BMC TrueSight Infrastructure Management Server before archiving begins, the tar of all the files and subdirectories in usr/pw by itself is sufficient (the database file and transaction log are in sync at the time of the shutdown).
• To save disk space, you can exclude the following database files from the tar archive:
  • installationDirectory/pw/sybase/pronto.log
  • installationDirectory/pw/sybase/storm_<hostname>.db
• In addition to restoring the files in the installationDirectory/pw directory, recovery also restores all the symbolic file links, startup and shutdown scripts, and crontab entries. The easiest way to address this is by running the server installation program on the recovery target host prior to recovery; the process takes care of all these items, with the possible exception of the crontab entries that you have customized.

To restore the BMC TrueSight Infrastructure Management Server

To restore the BMC TrueSight Infrastructure Management Server, perform the following tasks:

1. Ensure that the IP address of the new host is the same.
2. Restore the symbolic file links, the startup and shutdown scripts, and the crontab entries, either manually or by running the installation program.
   1. Restore the following symbolic file links:
      • installationDirectory/pw > installationDirectory/pw
        
      • /usr/pronto > installationDirectory/pw/pronto
      • /usr/bin/pw > installationDirectory/pw/pronto/bin/pw
   2. Restore the startup and shutdown scripts.
      You can identify startup and shutdown scripts by using the ls -al /etc/rc*/*| grep pronto command.
   3. Restore the crontab entries. 
      You can identify the BMC TrueSight Infrastructure Management Server crontab entries by using the crontab -l command and looking for all entries between the lines # begin_pronto and # end_pronto. By default, the crontab job ontains a pw database archive command for archiving the database on a weekly basis.
3. Run the following command from the command prompt: 
   tar xf /datadisk/archivedir/pronet.tar
4. Run the following command from the command prompt: 
   pw database restore /datadisk/archivedir