HP 153636-001 - NeoServer - 150 Manuale di prevenzione degli errori - Pagina 6
Sfoglia online o scarica il pdf Manuale di prevenzione degli errori per Desktop HP 153636-001 - NeoServer - 150. HP 153636-001 - NeoServer - 150 12. Memory technology evolution: an overview of system memory technologies, 8th edition
Anche per HP 153636-001 - NeoServer - 150: Libro bianco tecnico (12 pagine), Aggiornamento del firmware (9 pagine), Panoramica (20 pagine)
Stampa la pagina
Using a Methodology
Following a set of procedures when using the server can help prevent problems, or
make troubleshooting easier if problems do occur.
•
Use uniform naming conventions for the servers, such as names that denote
server location. Uniform naming conventions help when trying to remember
often overlooked details that can hold the key to resolving a crisis.
•
Use unique IDs or names for the devices. You can reduce the risk of components
competing for the same resource if you have a list. Use the server setup utility to
check for conflicts.
•
Make a habit of using the HP tools, resources, software, and third-party product
resources to keep abreast of potential problems. You may be able to avoid
problems by noting the problems of others.
•
Have a reliable backup plan. Schedule backups based on the server needs. If data
is changed frequently, frequent backups are required. Maintain a library of
backups based on your information-restoring needs. Test the backups
periodically to be sure that the data is correctly stored.
•
Have a plan of action before the server fails, planning for failures of different
hardware parts.
•
Check hard disk space periodically. It is recommended that hard drives have a
minimum of 15 percent free space.
•
Scan for viruses weekly. Use the latest virus-scanning utilities available to be
sure that the data is not corrupted.
•
Keep historical data. You cannot know that the CPU utilization has increased
50 percent if you do not know what it was initially. If you have problems, you
can use the data to compare before and after scenarios. For example, you might
want to know about the user, bus, and power utilization rates.
•
Keep a trend analysis so that you will know what to expect during certain points
in time. For example, if the CPU utilization rate always increases by 50 percent
during certain hours, you will know that increase is normal for the server you are
tracking.
Error Prevention Guide
7