The Network Configuration Manager back up and restoration utilities gather all your critical application data to be stored in a preset backup location. This frees you from worrying about which data files within the Application server are important to back up, and which data files can be ignored.
Your network configuration data is stored essentially in three forms:
-
Relational database tables
-
XML data
-
Flat file data
All files needed for a successful backup of your Application server data are stored under [Product directory], and include:
[Product directory]/data [Product directory]/db
When a backup of your system takes place, the files in these directories are copied into a backup bundle, compressed, given a time-stamped name, and stored in a separate directory within your application environment, [Product directory]/data-image. By default, the data-image directory is on a filesystem local to the Application server.
When integrating the Network Configuration Manager backup process into your existing corporate backup, it is imperative that this backup data be stored off of the Application server (on a daily basis) to prevent an Application server hardware failure from corrupting both the application data and the backups.
There are several options to transfer your backup files onto a system other than the Network Configuration Manager Application server. The best option for your environment depends on your corporate IT backup, and your disaster recovery policy, but can include installing a third-party storage backup utility on the Network Configuration Manager Application server. Follow these steps:
-
Use the UNIX®® cron utility to rcp, scp, or ftp the backup file to a different server other than the Network Configuration Manager Application server.
-
Create an NFS mount point for the [Product directory]/data-image directory that resides on a remote server.
-
Copy the backup file to a removable storage device installed on the Network Configuration Manager Application server, such as tape or CD.
-
