Each service has its own log, but many of them have little value for troubleshooting. This is a simpler view of how the critical components relate to each other.
Simplified Component Relationships Diagram for Troubleshooting
Here is an abbreviated version of the comprehensive list of logs, showing the most useful ones for troubleshooting.
|
Service |
Log File Name |
What the Logs Include |
|
adhd |
adhd.log adhd.log-<date> adhd.log-<date>.bz2 |
Local and remote deduplication, replication and communications with remote systems. |
|
flasher |
flasher.log |
Creation of snapshots. |
|
omd |
omd.log |
Creation and deletion of VDisks before invoking the Flasher. |
|
psrv |
psrv.log.0 |
Communications with Tomcat, Actifio database, VMware, CLI, system health, scheduling GC. |
|
GUI/tomcat |
catalina.log.<Sequence> |
Communications with the Actifio Desktop and the Actifio Resource Center. The Sequence number increases as you go back in time. |
|
udppm |
udppm.log udppm.log-<Date> udppm.log-<Date>.bz2 |
Scheduling and operation of jobs. |
|
host/connector |
A variety of different logs depending upon the host, but always including UDSAgent.log. |
The Actifio Connector log includes information such as host OS version/patch revision, HBA make/model/type, firmware revision, CPU/Memory utilization, connector logs, RMAN, syslog, etc. |
Useful Actifio Logs for Troubleshooting
This is a topic that is near to my heart… Thank you!
Where are your contact details though?