Symantec NetBackup status code 5016 to status code 5025

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 5016 to Status Code 5025 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 5016
Message: Failure in database connection
Explanation: The Indexing service has failed to connect to the database.
Recommended Action: Ensure that the NetBackup Relational Database (NBDB)
service is running.

NetBackup status code: 5017
Message: Database error occurred
Explanation: The Indexing service has detected a database error.
Recommended Action: Ensure that the NetBackup Relational Database (NBDB)
service is running.

NetBackup status code: 5018
Message: Duplicate record found
Explanation: The user submits an indexing request for a backup image that is
already in the indexing queue. The nbindexutil report shows that the backup ID
already exists in the indexing queue. A duplicate entry is not allowed.
Recommended Action: Remove the request.

NetBackup status code: 5019
Message: Data not found
Explanation: This code is unused.
Recommended Action: Not available.

NetBackup status code: 5020
Message: Indexing server value is not set
Explanation: This code is unused.
Recommended Action: Not available.

NetBackup status code: 5021
Message: Unsupported policy type for indexing
Explanation: User runs the nbindexutil command to request indexing for a
backup image that indexing does not support.
RecommendedAction: Ensure that the image that you submit for indexing uses
the supported policy type.

NetBackup status code: 5022
Message: Unknown error occurred
Explanation: This code is unused.
Recommended Action: Not available.

NetBackup status code: 5023
Message: Error in querying indexing schedule windows
Explanation: The PEM request for schedule windows fails. The internal policy
that is used for keeping indexing schedules may be corrupt.
Recommended Action: Check that the schedules are listed correctly by running
the nbpemreq -policies command.

NetBackup status code: 5024
Message: Unable to connect to Job Manager
Explanation: The Indexing service is unable to connect to the Job Manager service.
Recommended Action: To forcefully submit this indexing request, use the
nbindexutil -force option.

NetBackup status code: 5025
Message: indexing failed
Explanation: This code is a generic error code that is used to indicate that the
job fails because the indexing engine failed. The indexing software issues a new
job for the failed backup image.
Recommended Action: If the retry also fails, use the nbindexutil command to
submit the backup image again for indexing.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 5006 to status code 5015

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 5006 to Status Code 5015 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 5006
Message: Invalid machine name for indexing server
Explanation: The user tries to add a machine as an indexing server that has no
entry in the EMM.
Recommended Action: Run the nbemmcmd -listhosts command to determine
if the server name is listed. Names that are listed in nbemmcmd -listhosts are
the only valid server names to configure as Indexing servers.

NetBackup status code: 5007
Message: Invalid indexing server
Explanation: The user provides an invalid name of the indexing server when you
run the nbindexutil -indexserver command.
RecommendedAction: Verify the name of the configured indexing server in the
Host Properties of the NetBackup Administration Console.

NetBackup status code: 5008
Message: Unable to get Master Server key
Explanation: The Indexing service fails to get the information about the master
server.
Recommended Action: Not applicable.

NetBackup status code: 5009
Message: Invalid indexing state
Explanation: The Indexing service gets an invalid request to list the backup
images.
Recommended Action: Not applicable.

NetBackup status code: 5010
Message: Invalid date range
Explanation: The Indexing service tries to query the backup images from the
database for an invalid date range.
Recommended Action: Enter an appropriate date range.

NetBackup status code: 5011
Message: No images in sequence to process
Explanation: The Indexing service receives the empty request for processing.
Recommended Action: Not applicable.

NetBackup status code: 5012
Message: No such record found
Explanation: User runs the nbindexutil -remove operation to remove a backup
ID that is not present in the indexing queue. The nbindexutil report shows that
the Backup ID does not exist in the indexing queue.
Recommended Action: Make sure that you remove a backup ID that is present
in the indexing queue.

NetBackup status code: 5013
Message: Backup image is not indexed
Explanation: You use the nbindexutil -delete operation to delete a backup
image that is not indexed.
Recommended Action: Make sure that you delete only the backup images that are indexed.

NetBackup status code: 5014
Message: Failure in getting image header
Explanation: This error is internal for the Indexing service .
Recommended Action: Not applicable.

NetBackup status code: 5015
Message: Indexing is in progress for backup image
Explanation: User runs the nbindexutil -remove command to remove a backup
image from the indexing queue, but an indexing job for that image is already
running.
Recommended Action: Ensure that the indexing job is not running before you
submit a request to remove an image from the indexing queue.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2831 to status code 5005

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2831 to Status Code 5005 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2831
Message: Restore error
Explanation: An error caused the restore to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 4200
Message: Operation failed: Unable to acquire snapshot lock
Explanation: The snapshot is being accessed by another operation such as a
restore, browse, or copy to storage unit.
RecommendedAction: Retry the operation when the snapshot is not longer being
used by another operation.

NetBackup status code: 5000
Message: Indexing service internal failure
Explanation: This code is internal to the Indexing service .
Recommended Action: Not available.

NetBackup status code: 5001
Message: Unable to connect to Policy Execution Manager
Explanation: The Policy Execution Manager service is down. The NetBackup
Policy Execution Manager (nbpem) is required for indexing to work properly.
Recommended Action: Ensure that nbpem is running.

NetBackup status code: 5002
Message: Backup image is already indexed
Explanation: The user tries to submit an indexing request from nbindexutil for
a backup ID that is already indexed.
Recommended Action: To forcefully submit this indexing request, use the
nbindexutil -force option.

NetBackup status code: 5003
Message: Invalid arguments received
Explanation: The indexing engine returns invalidURLinformation to the Indexing
service . An appropriate message is logged in the nbim logs.
Recommended Action: Not applicable.

NetBackup status code: 5004
Message: Invalid backup image ID
Explanation: The nbim process tries to get client information for the backup ID
to be indexed. The appropriate message is logged in the nbim logs.
Recommended Action: Not available.

NetBackup status code: 5005
Message: Invalid database key
Explanation: This error occurs internally for the Indexing service when it tries
to fetch database records. An appropriate message is logged in the nbim logs.
Recommended Action: To forcefully submit this indexing request, use the
nbindexutil -force option.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2819 to status code 2830

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2819 to Status Code 2830 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2819
Message: Enterprise Vault policy restore error
Explanation: An error caused the restore of the Enterprise Vault data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar log for additional failure information. Also, check
the Enterprise Vault server event viewer (application and system) for errors
or clues.
¦ Connect to the server where the Enterprise Vault front-end runs. Launch the
restore by using the Backup, Archive, and Restore GUI.
¦ Verify that you launched the restore correctly.
See the NetBackup for Enterprise Vault Agent Server Administrator’s Guide.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2820
Message: NBU VMware policy restore error
Explanation: An error caused the restore of the VMware policy data to fail.
Recommended Action: Check the job details in the Activity Monitor and take
action as dictated by that information.

NetBackup status code: 2826
Message: Master server failed to connect to backup restore manager on media
server for restore
Explanation: A process on the master server cannot connect to a process on a
host on the network. This error occurs when the process tries to initiate
communication with the server that has the storage unit. This problem can occur
during a restore in either a single or a multiple server configuration.
RecommendedAction: Try the following possible solution in the order presented:
¦ From the master server, ping the master and all media servers by using the
host names in the storage unit configuration.
¦ From each of the media servers, ping the master server by using the name that
is specified in the NetBackup server list. On a UNIX or Linux server, this master
is the first SERVER entry in the bp.conf file. On a Windows server, the master
is designated on the Servers tab in the Master Server Properties dialog box.
¦ Check that all services are running on the media server.

NetBackup status code: 2828
Message: Restore failed because the MS-SQL-Server services are down
Explanation: The Microsoft SQL services are down on the system where the
NetBackup client and the NetBackup for Microsoft SQL agent are running. So the
NetBackup for Microsoft SQL agent cannot connect to the Microsoft SQL server.
RecommendedAction: Check that the Microsoft SQL instance service is running
and that NetBackup processes have permission to access to the Microsoft SQL instance service.

NetBackup status code: 2829
Message: Restore failed due to MS-SQL-Server database in use
Explanation: Microsoft SQL server database is busy with another operation and
cannot restore the requested database on the system where the NetBackup client
and the NetBackup for Microsoft SQL agent are running.
Recommended Action: After the database finishes its current operation, try to
restore the database. Or, the database administrator needs to check if the database
is busy and what operation it is performing.

NetBackup status code: 2830
Message: Restore failed due to an incorrect path in the MS-SQL-Server MOVE
script
Explanation: TheMOVEtemplate generated for database restore using Netbackup
forMSSQLagent GUI has incorrect path specified for database/log file for keyword
TO.
RecommendedAction: Check the MOVE script and correct the path specified for
the database log file for keyword TO.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2815 to status code 2818

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2815 to Status Code 2818 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2815
Message: AFS policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar log for additional failure information.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2816
Message: DataStore policy restore error
Explanation: An error caused the restore of the DataStore data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. If you run one PureDisk disaster recovery, check the output
from the /opt/pdinstall/DR_Restore_all.sh script on the PureDisk node.
Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check ownership and permission on the database instance that you restore.
¦ Check the NetBackup exten_client log for additional failure information.
¦ If you restore a Netezza appliance, collect the log files from
/nz/kit/log/restoresvf/*.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2817
Message: FlashBackup Windows policy restore error
Explanation: An error caused some or all of the files to fail.the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar log for additional failure information.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2818
Message: NBU Catalog policy restore error
Explanation: An error caused the restore of the NetBackup catalog to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
Ensure that NetBackup is at the same version and patch level as the machine
where the catalog image was created.
¦ Ensure that the path where you restore the catalog is same as when it was
backed up.
¦ Ensure that sufficient disk space exists on the target system where the restore
runs.
¦ Ensure that the current master server hostname matches the hostname of the
machine where the catalog image was created.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar, admin, bptm, and bpbr logs for additional failure
information.
¦ Correct the problems that you find and retry the restore.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2812 to status code 2814

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2812 to Status Code 2814 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2812
Message: DB2 policy restore error
Explanation: An error caused the restore of the DB2 data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission of the DB2 instance that you restore and the
directories where the files are restored.
¦ Check the NetBackup bpdb2 log for additional failure information.
¦ Ensure that the No.Restrictions file has been created on the master server
in case of restore.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2813
Message: NDMP policy restore error
Explanation: An error caused some or all of the files to fail.the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check if the destination NDMP host supports DAR. If not, disable DAR.
¦ Check the ndmpagent (Originator ID 134) log for additional failure information.
¦ Check the NetBackup bptm log for additional failure information.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2814
Message: FlashBackup policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar log for additional failure information.
¦ Enable and verify VxMS logs for additional failure information.
¦ For VMware restores, enable the bpvmutil logs.
¦ If you run a VMware restore, make sure that the user account specified in the
VMware credentials has full administration rights on the target vCenter and
the ESX server.
¦ Correct the problems that you find and retry the restore.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2810 to status code 2811

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2810 to Status Code 2811 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2810
Message: MS-Exchange policy restore error
Explanation: An error caused the restore of the Exchange data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission of the Exchange instance that you restore
and the directories where files are restored.
¦ Verify the following log files depending on the type of restore being performed.
All the log folders are located in the install_path\NetBackup\logs folder.
¦ beds – All restore operations.
¦ tar – All restore operations.
Restores with Granular Recovery Technology (GRT):
¦ nbfsd – This log appears on the client and the media server.
¦ ncf – This log uses unified logging and appears on the destination client
or proxy client.
¦ ncflbc – This log is for nblbc.exe. It appears on the destination client or
proxy client.
¦ ncfgre – This log is for nbgre.exe. It appears on the destination client or
proxy client.
Instant Recovery and Instant Recovery off-host:
¦ bpbkar – For off-host Instant Recovery restores, bpbkar logs on the alternate
client.
¦ bpfis – This log applies to Instant Recovery rollback restores. For off-host
Instant Recovery backups, bpfis logs exist on both the primary and the
alternate clients.
¦ bppfi – For off-host Instant Recovery restores, bppfi logs on both the
primary and the alternate clients.
¦ Check the Exchange Server event viewer for Application and System messages
related to the restore operation.
¦ Connect to the server where Exchange is running and launch the restore from
that server using the Backup, Archive, and Restore GUI.
¦ Verify that you launched the restore correctly.
See the NetBackup for Microsoft Exchange Server Administrator’s Guide.
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2811
Message: SAP policy restore error
Explanation: An error caused the restore of the SAP data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission of the SAP instance that you restore and the
directories where the files are restored.
¦ Ensure that the No.Restrictions file has been created on the master server
in case of alternate client restore.
¦ Check the following logs for additional failure information: backint, tar,
dbclient, bprestore, and user_ops.
¦ Correct the problems that you find and retry the restore.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2807 to status code 2809

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2807 to Status Code 2809 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2807
Message: SQL-BackTrack policy restore error
Explanation: An error caused the restore of the SQL-BackTrack data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored and
on the SQL-BackTrack instance that you are restoring.
¦ Check the NetBackup backtrack log for additional failure information.
¦ Ensure that the No.Restrictions file has been added on the master server in
case of alternate client restore.
¦ Correct the problems that you find and retry the restore.
More information is available for this status code.

NetBackup status code: 2808
Message: Windows File System policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check that you have selected the correct restore type on the Backup, Archive,
and Restore GUI.
¦ Check ownership and permission on directories where files are restored.
¦ Check that the destination directories or files exist. If so, select Overwrite
existing files option on the Backup, Archive, and Restore GUI.
¦ Check the following logs for additional failure information:
¦ Master server: bprd, nbjm
¦ Media server: bpbrm, bptm, bpdm
¦ Client: tar
¦ Correct the problems that you find and retry the restore.

NetBackup status code: 2809
Message: MS-SQL-Server policy restore error
Explanation: An error caused the restore of the SQL Server data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored and
on the SQL instance that you are restoring.
¦ Check ownership and permission on the SQL Server instance and on the
directories where files are restored.
¦ Check the following logs for additional failure information on the client side:
install_path\NetBackup\logs\dbclient
install_path\NetBackup\logs\bpbkar (Snapshot Client)
install_path\NetBackup\logs\bpfis (Snapshot Client)
install_path\NetBackup\logs\bppfi (instant recovery)
¦ Check the SQL server event viewers (application and system) for any errors
or messages related to the restore operation.
¦ Increase restore verbose levels.
See the NetBackup for Microsoft SQL Server Administrator’s Guide.
Review this guide to verify that you launched the restore correctly.
¦ Connect to the server where SQL is running and launch the restore from that
server using the Backup, Archive and Restore GUI.
¦ Correct the problems that you find and retry the restore.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 

Symantec NetBackup status code 2804 to status code 2806

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features.

Below are some of the NetBackup status error codes from Status Code 2804 to Status Code 2806 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 2804
Message: MS-SharePoint policy restore error
Explanation: An error caused the restore of the SharePoint data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Create the following log folders on the SQL Server, the front-end Web server,
the media server and the master server:
install_path\NetBackup\logs\tar
install_path\NetBackup\logs\bpresolver
install_path\NetBackup\logs\bpbrm (media server)
install_path\NetBackup\logs\bprd (master server)
If you use granular restore technology (GRT), the following log folders also
apply:
install_path\NetBackup\logs\ncf
install_path\NetBackup\logs\ncflbc
install_path\NetBackup\logs\ncfgre
install_path\NetBackup\logs\nbfsd
install_path\NetBackup\logs\spsv2ra
¦ Check all SharePoint server event viewers (application and system) for any
errors.
¦ Connect to the server where the SharePoint front-end server runs and launch
the restore using Backup, Archive and Restore GUI.
¦ Make sure the restore is being launched correctly.
See the NetBackup for Microsoft SharePoint Administrator’s Guide.
¦ Correct the problems that you find and retry the restore.
More information is available for this status code.

NetBackup status code: 2805
Message: MS-Windows policy restore error
Explanation: An error caused some or all of the files to fail the restore operation.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check that you have selected the correct restore type on the Backup, Archive,
and Restore GUI.
¦ Check ownership and permission on directories where files are restored.
¦ Check the following logs for additional failure information:
¦ Master server: bprd, nbjm
¦ Media server: bpbrm, bptm, bpdm
¦ Client: tar
¦ Correct the problems that you find and retry the restore.
More information is available for this status code.

NetBackup status code: 2806
Message: NetWare policy restore error
Explanation: An error caused the restore of the NetWare data to fail.
RecommendedAction: Try the following possible solutions in the order presented:
¦ Ensure that the client server list contains entries for the master server and
any media servers that can be used during a backup or restore.
¦ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
¦ Check ownership and permission on directories where files are restored.
¦ Check the NetBackup tar log for additional failure information. Also check the
following log files: bpcd, bpsrv, bprest, and user_ops.
¦ For target restores, ensure that you have create and write rights to the volume
where you are trying to restore. In the BP.INI file, ensure that the
Allow_Server_Write parameter is set to yes.
¦ If you launched a non-target restore from the NetBackup Administration
Console, ensure that the Allowserverdirected restores parameter is selected.
¦ Correct the problems that you find and retry the restore.
More information is available for this status code.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.

 
1 2 3 4 5