Managing Log Files

You can back up these files to another server using the secure shell SCP program.

Backing Up Log Files to a Remote Server

You can copy rotated logs to another server that is more suited for holding large amounts of log data using the following command line syntax:

save_rotated_log [[user@]host:]file [ -flush ] [ -now ]

Where:

-flushdeletes the current rotated logs -nowforces an immediate log rotation

The destination file is mandatory and must be the first argument. The order of the options (-flushand -now) does not matter; the system will perform the actions in the same order (save-flush-rotate) regardless of the options given.

If you supply user@host, the logs are transferred to a remote machine under the privileges of the specified user. If you do not supply user@, the system will assume that the current user is the remote one.

For remote destination, ensure that the remote machine is prepared to accept connections to ssh service on port 22. If only the file name is supplied, the system will copy the logs locally. You can include path names as part of the file name.

System Recovery Guidelines

In the event that the BladeManager goes down, the system will check the integrity of the file system during the restart. If a problem is found, then the system will attempt to repair any damage that may have occurred.

When performing a recovery procedure, if there is too much damage, you have the option to stop the booting process and take recovery actions through the serial console as follows:

1.Rebuild system partition

2.Rebuild database

3.Rebuild data log partition

The rest of the configuration process is done through the GUI/web interface.

AlterPath BladeManager Manual

5-19

Page 181
Image 181
Cyclades AlterPath BladeManager user manual Backing Up Log Files to a Remote Server, Where