VERITAS NetBackup Guía para resolver problemas Pagina 175

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 322
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 174
Chapter 4, Status Codes and Messages 163
Status Codes
1. Examine the Backup Status and All Log Entries report for the appropriate time period
to determine the class or schedule that received the error.
2. Verify that the storage units drives are not down or waiting for media from a
previous operation that did not complete.
3. Verify that all the storage units do not have their Maximum concurrent jobs attribute
set to 0 (for disk storage units) and Maximum concurrent drives used for backup
attribute set to 0 (for Media Manager storage units).
4. Verify that the robot number and host name in the storage unit configuration matches
the Media Manager device configuration.
5. Determine if all storage units are set to On demand only for a class and schedule
combination that does not require a specific storage unit. If this is the case, either
specify a storage unit for the class and schedule combination or turn off On demand
only for a storage unit.
6. If the storage unit is on a UNIX NetBackup media server, it could indicate a problem
with bpcd. Check /etc/inetd.conf on the media server to verify that the bpcd
entry is ok.
If the storage unit is on a Windows NT/2000 NetBackup media server, verify that the
NetBackup Client service has been started on the Windows NT/2000 NetBackup
media server.
7. For detailed troubleshooting information, create a bpsched activity log directory on
the master server and retry the operation. Then, check the resulting activity log.
Status Code: 214
Message: regular bpsched is already running
Explanation: The NetBackup scheduler (bpsched) performs periodic checking of the
class and schedule configuration to determine if there are new backups due. Error 214
indicates that when a new instance of NetBackup starts, it finds that a scheduler process is
already checking the class and schedule configuration.
Recommended Action: Usually, no action is required for this condition. However, NEVER
kill bpsched before doing some checking. For example, bpsched could be calling bpdbm
(NetBackup Database Manager service on Windows NT/2000) to clean up and compress
the catalogs.
To determine what the running bpsched is currently doing, examine the bpsched
activity log on the master server. If necessary, enable bpsched activity logging by creating
a bpsched activity log directory on the master server and retrying the operation.
Vista de pagina 174
1 2 ... 170 171 172 173 174 175 176 177 178 179 180 ... 321 322

Comentarios a estos manuales

Sin comentarios