Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

to be protected from modification by using the /save_file/ function. The os_arch_post_l
script uses the merge_file function on files into which appropriate information is merged.
The files operated on by merge_file, and those that have a commented out save_file line
are those that are likely to be modified by Ignite-UX. Comments in this file explain any exceptions.
Because the list of files modified by Ignite-UX might change from release-to-release, it is best to
look at the os_arch_post_l script on the client to see which files are saved as is and which are
merged with information from the Ignite-UX configuration files.
How can I keep archives from being deleted by make_net_recovery when new
archives and configurations are created by subsequent invocations of
make_net_recovery?
You might want to prevent known good archives from being deleted from your client. The
make_net_recovery tool provides the -n option, which allows you to specify the number of
archives to save. To preserve the disk space, the oldest archives are removed as new archives are
created. The number of archives that are removed is based on the number of archives you specified
to be saved using the make_net_recovery -n. One way to ensure that known good archives
are saved is to specify the number of archives to save to be greater than the maximum number of
archives you plan to store on the client at any given time. This method has the potential to use a
great deal of disk space.
An alternative and better approach to saving known good archives is to rename the archive and
edit the configuration file to include the new archive name. The following procedure explains this
process in detail:
1. Login to the system where the archive is being stored; this system can be different from your
Ignite-UX server.
2. Rename the archive. The name of the archive to save can be anything unique, but it must be
outside the naming convention: yyyy-mm-dd,hr:min. For example:
# cd /var/opt/ignite/recovery/archives/system_name/
# mv old_archive_name saved_archive_name
# mv 1999-05-11,15:14 Recovery_Archive.0511.save
3. If the archive server is different from the Ignite-UX server, login to the Ignite-UX server.
4. Edit the following file to reference the new archive name:
#
/var/opt/ignite/clients/<client>/recovery/<old_archive>/archive_cfg
Change the archive_path variable inside the (source_type == "NET")
conditional to the name of the saved archive. For example:
(source_type == "NET") {
archive_path = "Recovery_Archive.0511.save"
}
else {
archive_path = "1"
}
5. Optionally, you can edit the <cfg> entry in the file /var/opt/ignite/clients/
<client>/CINDEX so that configuration is unique and descriptive when it is viewed using
the Ignite-UX GUI. For example, change:
cfg "1999-05-13,06:51 Recovery Archive" { description "Weekly
System Recovery Archive"
.
Frequently asked questions 45