![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/0/a5/0a5663ab-15e2-4e2c-926f-076e6f549524/0a5663ab-15e2-4e2c-926f-076e6f549524-bg6a.png)
74 SPARC Enterprise Mx000 Servers Administration Guide • November 2007
Archive Host Requirements
As the Service Processor keeps track of archive space on the archive host, you should
not store other files in these archive directories.
It is possible to set up the Service Processor so that it uses one of the domains in the
same system as an archive host. However, this configuration does not provide
optimal reliability and serviceability. Typically, a separate, remote server functions as
the archive host.
Log Archiving Errors
The log archiving system handles typical errors by retrying and recording errors in
the Event Log. Possible error causes include archive host downtime, network
outages, and misconfiguration of the Service Processor and/or the archive host. You
can use the showarchiving command to view the details of the last ten archiving
failures, including the first 1000 characters of output from any command that failed.
Using the snapshot Tool
Log data can also be collected and transferred from the Service Processor with the
snapshot command. The snapshot tool does not extend or replace any other
functionality, such as log archiving or logging of information using syslog. Refer to
the snapshot(8) man page for details on this tool.
Solaris OS Procedures for Log Archiving
▼ To Configure the Log Archive Host
1. Select a user account on the server that will be used as the archive host that the
Service Processor will use to log in.
2. Log in to the archive host and create an archive directory.
3. Set the permissions of the archive directory as desired. The Service Processor
log-in account must have read, write, and execute (rwx) permissions.