Sun Microsystems Virtual Tape Library - Manual (Page 245)

96267 • G Appendix C Troubleshooting 231
Case: Connection fails while expanding the VTL server node
1. Check the memory consumption on the console host.
2. If memory consumption is excessive, stop unnecessary processes, and retry.
3. If you can connect, stop here.
Avoid running memory‐intensive applications on this host when the console is in
use.
4. If you cannot connect or if memory consumption appears to be within normal
limits, contact Sun technical support.
Issue: Requested operations cannot be performed from the VTL console
Indications: The server exhibits symptoms of high CPU utilization, such as Server Busy or
RPC
Timeout messages.
Diagnostics: Determine whether high CPU utilization is normal.
1. Check the Event Log or syslog (/var/adm/messages) for CPU-intensive activity
on the server.
Backup jobs that backup to multiple virtual or physical devices in parallel, data
compression, and encryption all place heavy demands on the CPU.
2. If CPU-intensive processes are running on the server, stop here, and retry the
console later.
The VTL server is behaving normally.
3. If CPU-intensive processes are not running on the server, if the CPU is not
actually busy, or if the problem persists, contact Sun technical support.
Issue: VTL console operations are very slow
Indications: The VTL console is abnormally slow or unresponsive.
Diagnostics: Determine the reason.
Case: Low host system memory
1. Check memory utilization for all running processes on the host.
2. Stop unnecessary processes.
3. If no unnecessary processes are running, provide the host with more memory.