The NetBackup Enterprise Vault migrator communicates to NetBackup through the VxBSA module, and the VxBSA logs are the logs that you must collect from NetBackup. Each NetBackup backup takes place through the bpbkar process. The restore takes place through a tar process. Thus, it is important that you collect the logs for both these processes.
To collect the Enterprise Vault logs that were migrated to the NetBackup logs
Go to the NetBackup logs directory.
A logs directory resides under the NetBackup installed directory. For example, if NetBackup is installed under the directory, C:\Program Files\Veritas\NetBackup\, then the following logs directory also exists:
Create the required directories under the NetBackup logs folder.
You should refer to the following logs as your first point of reference when you investigate the details of any failure:
To enable the creation of these log files you must create the following directories under the NetBackup logs folder (if they do not already exist):
The migration can fail because of any failure in the workings of NetBackup. Therefore, even though the first point of investigation should start with the mentioned logs, it is safest to collect all of the logs by executing the command, mklogdir.bat.
Set the NetBackup logging level to the required level.
You should update the
logging level of the NetBackup client through which the migration
takes place. Ideally, you should set the logging level to the
highest level. You configure the client in the profile through
which the migration takes place (for example, EV_Default_Profile
).
You can update the logging level using the Client Properties dialog on either the NetBackup Administration Console or the Backup, Archive, and Restore user interface.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.