Ensure you have enough disk space in your archive directory to store the Log, Timestamp and Event files for each serviced system being archived. If disk space is limited, we recommend that you archive one system at a time, removing the archived files from the directory before continuing with the next system.
You cannot archive directly to a non-disk device. However, you can copy or move the files to a non-disk device, such as a magnetic tape, after archiving your data. If you choose to move them out of the archive directory, ensure that you keep the original filenames, otherwise the EXTRACT command, and the monitor interface REVIEW command will not operate correctly. The file names have the system and dates embedded in them and these are used to concatenate the data for review.
You cannot archive in the following situations:
If a user is connected to the console of a system that you want to archive. In this case, Console Manager generates an Archive aborted event, which includes the name of the user who is connected to the console.
If a user is reconfiguring.
In this case, Console Manager generates an Archive aborted event, indicating that a reconfigure is in progress.
If another archive operation is in progress.
If you do not want to keep your archived data, you can delete them as part of the archiving process.
The keyword ALL used as a system name archives all files.
The keyword CONSOLEMANAGER used as a system name archives the Console Manager log file. You must shut down Console Manager before you can archive the Console Manager log file.
You must also archive the files used to log Console Manager events as they grow continuously (see the section, Archiving Log Files, later in this chapter for instructions on how to do this).
You can archive the system log files while Console Manager is running. However, if you want to archive the Console Manager log files, you must shut down Console Manager first.
By default the archive directory CONSOLE$ARCHIVE resides on the same volume as the log files. You can redefine this logical name using the SYS$STARTUP:CONSOLE$PRIVATE_SETUP.COM procedure. If you wish to do this, copy the template file SYS$STARTUP:CONSOLE$PRIVATE_SETUP.TEMPLATE to SYS$STARTUP:CONSOLE$PRIVATE_SETUP.COM and edit it to reflect your individual requirements. The Console Manager startup checks to see if SYS$STARTUP:CONSOLE$PRIVATE_SETUP.COM exists and executes it automatically.
You can only archive files to a local directory on the Console Manager host system. That is, you cannot include a system name in the directory specification. For example, you cannot have SALT::CONSOLE$ARCHIVE:.
Automatic archiving is provided as a failsafe option. We recommend that you do not rely on this for archiving your log files, and manually archive at regular intervals; depending on the number of events being logged this could be daily or weekly.
To read data you have placed from the archive directory, follow the instructions in the section, Reading Archived Data, later in this section
For more archiving examples and information, see the HELP CONSOLE ARCHIVE command.
