netbackup-insights/nbu_status_codes.json

{
    "0": {
        "code": 0,
        "desc": "The requested operation was successfully completed.",
        "first_action": "No action is needed, unless a database was backed up",
        "full_action": "No action is needed, unless a database was backed up\nthrough a database extension product (for example, NetBackup for Oracle or\nNetBackup for SQL Server). In those instances, code 0 means the backup script\n(that started the backup) ran without error. However, you must check other status\nas explained in the related NetBackup manual to see if the database was\nsuccessfully backed up."
    },
    "1": {
        "code": 1,
        "desc": "The requested operation was partially successful.",
        "first_action": "A file or a directory path is more than 1023 characters long.",
        "full_action": "Review the All Log Entries report and also the progress\nlog (if there is one).\nThe following are some of the problems that can appear under status code 1:\n■ A file or a directory path is more than 1023 characters long.\nFor NetBackup Snapshot Client, the maximum path name length is 1000\ncharacters for snapshot backups, not 1023. When the snapshot is created, a\nnew mount point is added to the beginning of the file path. If the new mount\npoint plus the original file path exceeds 1023 characters, the backup fails with\nstatus code 1. The progress log includes the entry\nERR-Skipping long dir path.\n■ You cannot open a file.\nThe file may have been locked for some reason.\n■ The following information applies only to UNIX systems:\nNetBackup cannot get the link name of a file.\n■ The following information applies only to UNIX systems:\nNetBackup cannot process a sparse file.\n■ A read error that was encountered in a file.\n■ File is of an unknown type, or may be hidden.\n■ The following information applies only to UNIX systems:\nThe lstat system call fails on a file that is eligible to be backed up. This error\nmay be a permission problem.\n■ The following information applies only to UNIX systems:\nA file cannot be locked that has mandatory locking enabled.\n■ A synthetic backup job may terminate with a status code 1 under the following\nconditions:\n■ No images were found to synthesize (status code = 607).\n■ TIR information has been pruned from component images (status code =\n136).\n■ Image format is unsupported (status code = 79).\nThe synthetic backup job logs the actual status code in the NetBackup error\nlog. Refer to the documentation for the corresponding NetBackup error code\nfor the corrective action to take.\n■ A BMR job may terminate with status code 1 in the following situation:\nYou save the BMR configuration and it returns an error even though the child\njobs completed successfully. For information, examine the Detailed Status tab\nof the Job Details dialog box, or the nbjm unified log (originator ID 117).\n■ A policy that contains multiple backup scripts starts a scheduled backup of a\nUNIX database extension client. If it fails with a status code 1, some of the\nbackup scripts returned a failure status.\n■ OnclientsusingWindowsOpenFileBackups(WOFB)tobackupopenoractive\nfiles, the following may occur:\nVolume snapshots were not enabled successfully for the backup.\nThe following logging messages should appear in the bpbkar32 logs if volume\nsnapshots were not successfully enabled.\nIfmultistreamedbackupjobsareenabled,logmessagessimilartothefollowing\nappear that indicate volume snapshots were not enabled for the multistreamed\nbackup job:\n11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:\nINF - Volume snapshots not enabled for: D:\\Directory1\nIfmultistreamedbackupswerenotenabled,logmessagessimilartothefollowing\nappear,whichindicatevolumesnapshotswerenotenabledforthenon-streamed\nbackup job:\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Attempting to\ncreate snapshots for D:\\Directory1\n1:59:41.229 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - CREATE request:\nC:\\Program Files\\VERITAS\\NetBackup\\bin\\bpfis create -fim VSP\n\"D:\\ Directory1\"\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot\ncreation, FIS_ID: 1058813981\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation\nEXIT STATUS 11: system call failed\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation\nwas not successful\n1:59:41.799 PM: [2076.2088] <4>\nV_Snapshot::V_Snapshot_CreateSnapshot: INF -\n===============================\nIn this case, examine the bpfis logs for error messages regarding snapshot\ncreation failures. More details are available on the bpfis logs.\nSee the NetBackup Snapshot Client Administrator’s Guide.\nIn the bpfis logs, the following messages may appear when snapshot creation\nfails for Windows Open File Backup:\nFirst message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS error 11; see\nfollowing messages:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method error\nwas reported\n04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:\nmethod: VSP, type: FIM, function: VSP_make\n04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method error\n3; see following message:\n04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:\nsnapshot creation failed: invalid argument(s).\nCause: VSP was not enabled because the VSP snapshot for the backup did\nnot meet the specified minimum time in the Busy File Wait VSP setting.\nEither increase the Busy File Timeout VSP setting (recommended setting: 300\nseconds or more) or submit the backup job when the volume has less activity.\nSecond message:\n04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:\n(null): There was an unexpected error while preparing the VSP\nsnapshot transaction. Dumping the parameter array to provide\nmore information: Error 112 from VSP_Prepare\nCause: VSP was not enabled for the backup because the client for the VSP\nSnapshot Cache files does not have enough free disk space.\nFree up disk space on the volumes being backed up.\nThird message:\nIf Microsoft Volume Shadow Copy Service (VSS) is used as the Windows Open\nFileBackupsnapshotproviderandsnapshotcreationfails,refertothefollowing:\nEvent Viewer’s Application and System Logs for error information.\n■ A snapshot error may have occurred. Also, you may have some clients that use\nthe Windows Open File Backup option to back up open or active files. In this\ncase, a log message in the bpbkar32 debug log appears, which indicates that\na snapshot error occurred.\nThe following is an example of a snapshot error:\n8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR -\nSnapshot Error while reading test.file\nSee the recommended actions under status code 156.\n■ The backup of Microsoft Exchange Server included multiple databases, but not\nall of the databases were backed up successfully. Review the job details for\nstatementsaboutthedatabasesthatwerenotbackedup.Inafulloradifferential\nbackup, the transaction logs are truncated for any databases that are backed\nup successfully. The transaction logs can be restored from the backup image\neven if backups of other databases fail. Warning: Any database for which the\nbackup has failed is unprotected by this backup.\n■ A granular-enabled backup of Microsoft Exchange Server successfully backed\nupthedatabases,butthesecondGRTphasetocapturemailbox-levelinformation\nfailed. Review the job details for the cause of the failure. In a full or a differential\nbackup, transaction logs are truncated for the databases that are backed up\nsuccessfully, regardless of whether the GRT phase succeeds. Any database\nthat is backed up successfully can be restored from the backup image even if\nthe GRT phase fails.\n■ DuringVMwarebackup,thevirtualmachinecannotbeunlockedtoallowstorage\nmigration.\nThe virtual machine can be restored from this backup. However, you may want\nto correct this problem before the next backup.\n■ During VMware backup, the virtual machine snapshot cannot be deleted or the\nvirtual machine's disks cannot be consolidated.\nThe virtual machine can be restored from this backup. However, you may want\nto correct this problem before the next backup.\n■ During VMware restore, the virtual machine cannot be imported into vCloud. In\ntheActivityMonitor,theDetailedStatustabofthejobdetailsincludesmessages\nfrom vCloud Director that indicate the reason for the error.\nThe restored virtual machine is present on the destination vCenter. However,\nyou must manually import it into vCloud.\nA NetApp NDMP accelerator backup may terminate with a status code 1 with the\nfollowing clock discrepancy warnings for the volumes:\n■ Clock discrepancy detected between NDMP filer and NetBackup\nMedia Server.\n■ If this is not expected, please perform a backup with Accelerator\nforced rescan enabled.\n■ In order to stop seeing these messages, please address\nclock discrepancy.\nOne of the following situations can cause the clock discrepancy issue:\n■ If the NetApp filer and NetBackup NDMP backup host have a time difference\nof more than one hour, a clock discrepancy warning is displayed. This warning\nis displayed for all of the volumes.\nCheck the time difference for the affected volumes and update as required. Or\nuse a media server that is in the same time zone as the filer.\nNote: An NTP server is the recommended method to ensure the correct time.\n■ If any SnapMirror (Data Protection) volume has a lag time of more than one\nhour, the warnings appear for that volume.\nUse the following command to determine if the volume is a Data Protection\nvolume and if the lag time is greater than one hour:\n■ For NetApp Clustered Data ONTAP (cDOT):\nsnapmirror show -fields lag-time\n■ For NetApp 7-mode:\nsnapmirror status\nIf Data Protection volumes are found on the filer, either:\n■ Browse to and select the volumes for backup in the Backup Selections for\nthe NetBackup policy.\n■ Use the VOLUME_EXCLUDE_LIST with the ALL_FILESYSTEMS directive\nto exclude the mirror volumes.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to detach the vmdk %s or the SCSI controller to which %s vmdk is\nattached from the destination VM %s during cleanup.\nManually detach the vmdk or the controller.\n■ Deletion of temporary VM %s failed with error %d.\nManually delete the specified VM.\n■ Failed to clean the staging location %s on destination VM %s.\nManually delete the staging location.\n■ Failed to attach the temporary vmdk %s to the destination VM %s with error\n%d.\nMakesurethatthetargetVMhasatleastoneParavirtualcontrollerwithavailable\nLUNs.\n■ Failed to upload the process rename file to the destination VM %s with error\n%d.\nMakesurethereissufficientspaceavailableintargetVM.ReviewthebpVMutil\nlog file on the target VM for additional information on this issue.\n■ Failed to restore the selected files and folders.\nReview the tar log to troubleshoot this issue.\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause is that the destination VM user credentials have insufficient permissions.\nIt is recommended destination VM user credentials have root or administrative\nprivileges.\nNetBackup did not find one or more SQL Server databases that were specified in\nthe intelligent group in the SQL Server policy. A message like the following is\nincluded in the error log.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: ERR -\nexit status: 5465 Could not find database objects during backup.\n08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: INF -\nPartial success status so switch status from <5465> to <1>\nPerform one of the following actions to resolve the issue:\n■ Review the intelligent group in the policy and adjust the query. If no action is\ntaken, any databases that NetBackup can’t find during a future backup are\nskipped and the Database state for these databases is changed to \"Deleted\".\n■ Ifyouwantcontinuedaccesstothedatabase,youcanuseNetBackuptorecover\nit."
    },
    "2": {
        "code": 2,
        "desc": "None of the requested files were backed up",
        "first_action": "The following information applies only to Lotus Notes:",
        "full_action": "Do the following, as appropriate:\n■ The following information applies only to Lotus Notes:\nThiserroroccurswhenarchivestyleloggingisnotenabledfortheLotusDomino\nserver on UNIX. It also occurs when another backup of the transaction logs is\nin progress.\n■ See the troubleshooting topic of the appropriate guide for a description of\ntroubleshooting tools:\n■ NetBackup for Microsoft SQL Server Administrator’s Guide\n■ NetBackup for Lotus Notes Administrator’s Guide\n■ NetBackup for Enterprise Vault Agent Administrator’s Guide"
    },
    "3": {
        "code": 3,
        "desc": "Valid archive image produced, but no files deleted due to non-fatal problems",
        "first_action": "Examine the progress log or status of the archive on the",
        "full_action": "Examine the progress log or status of the archive on the\nclient to determine if you need to retry the archive after you correct the problem. If\nthe problem is not serious and the files were backed up, you can manually delete\nthe files. To verify the files that were backed up, use the NetBackup client-user\ninterface in restore mode and browse the files in the archive.\nA possible cause for files not being deleted is that you do not have the necessary\npermissions. NetBackup cannot delete files unless you are the user that owns the\nfiles, a superuser on UNIX, or an administrator on Windows."
    },
    "4": {
        "code": 4,
        "desc": "Archive file removal failed",
        "first_action": "Verifythatyouhavepermissiontodeletethefilesandthat",
        "full_action": "Verifythatyouhavepermissiontodeletethefilesandthat\nthe read-only flag is not set for the files. On UNIX clients, verify that you have write\npermissiontothedirectoriesthatcontainthefiles.Sincethebackupwassuccessful,\nyou can delete the files that were backed up. (If you do not have the necessary\npermissions, have the system administrator delete the files.)"
    },
    "5": {
        "code": 5,
        "desc": "Restore failed completely.",
        "first_action": "If using Azure, contact your cloud provider to increase the threshold limit.",
        "full_action": "To correct this issue, try the following solutions as\nappropriate:\n■ If using Azure, contact your cloud provider to increase the threshold limit.\n■ If you try to restore a replicated copy of EC2, create a new key-pair in the\ndestination region. The new key-pair must be consistent with the key-pair in the\nsource region.\n■ Sourcesnapshotmustberetainedonthecloudprovideruntiltheimageexpiration\nduration is selected in the protection plan.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to upload recovery tool on destination VM %s with error %d.\nMake sure there is sufficient space or permissions available at the staging\nlocation.\n■ Failed to extract the recovery tool on the destination VM.\nConfirmthereissufficientspaceavailableatthestaginglocation%sinthetarget\nVM.\nWhen a granular restore fails, perform the following:\n■ For lvm and ldm disks granular restore, upgrade the Snapshot Manager to\nversion 10.0.\n■ Ensure that restore destination path is accessible with sufficient privileges and\ndisk space.\n■ The file wise restore error and warning report is available on source host\n(Windows or Linux) as follows:\n■ Windows host path:\nC:\\ProgramData\\Veritas\\CloudPoint\\restore\\<job-id>/\n■ Linux host path: /root/veritas/<job-id>/\nThese locations provide the details of the disk wise restored file status.\nFor example:\nD#.log -> Existing log file which shows higher level failure\nD#-Error.log ->This file is generated only when an error\n(at least one) is displayed during the copy process.\nThis file logs the Actual Exception / OS exception.\nD#-Warning.log -> This file is generated only when a warning message\n(at least one) is displayed during the restore task."
    },
    "6": {
        "code": 6,
        "desc": "User backup failed",
        "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Detach the disk from the target instance.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure path or ensure the CRL distribution point\nthat valid CRLs are present at the location. URL, from the respective host certificate, is\nCheckiftheCRLURLisaccessiblefromthe accessible from the Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate Contactyoursecurityadministratortoensure\nis revoked. Ensure that the certificates are that the server presents a valid certificate.\nnot revoked by certificate authority.\n■ If the certificate was revoked in error,\nreissue a certificate for the host.\n■ Ifthecertificatewasrevokedasintended,\nan attempted security breach may have\noccurred.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsure that the ECA_CRL_PATH is updated the ECA_CRL_PATH path.\nwith the latest CRL.\nYou can update the NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager's system\nvalid. time or provide a valid CRL.\nThe date of last update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe date of next update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe Azure or Azure Stack server certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid of it by checking the certificate to make sure\ncertificate. that the end date is valid.\nCheck if the Snapshot Manager's clock is in\nsync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nThe Azure or Azure stack servers certificate Check if the Snapshot Manager’s clock is in\nis not yet valid. sync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nTable 1-1 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nUnabletofindthepublicrootandintermediate Ensure that the certificate file is configured\ncertificates of the Azure Stack server. correctly at the ECA_TRUST_STORE_PATH\nlocated in the bp.conf file on the Snapshot\nManager.\nRerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support.\nFailed to load the Certificate Revocation List Ensure that the valid CRL file is configured\n(CRL)fromCRLcache.Ensurethatthevalid ontheSnapshotManagerforAzureorAzure\nCRL file is configured on the Snapshot Stack by the ECA_CRL_PATH.\nManager for Azure or Azure Stack by\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Ensure network connectivity between the\nserver.Ensurenetworkconnectivitybetween Snapshot Manager and the Azure or Azure\nSnapshot Manager and the Azure or Azure Stack server.\nStack server.\nCannot use the specified SSL cipher for Contact Cohesity Technical Support.\nAzure or Azure Stack server.\nOperation failed with cURL error: Rerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support."
    },
    "7": {
        "code": 7,
        "desc": "The archive failed to back up the requested files",
        "first_action": "Verify that you have read access to the files. Check the",
        "full_action": "Verify that you have read access to the files. Check the\nprogress log or the status on the client for messages on why the archive failed.\nCorrect problems and retry the archive.\nOn Windows clients, verify that the account used to start the NetBackup services\nhas read access to the files."
    },
    "8": {
        "code": 8,
        "desc": "Unable to determine the status of rbak",
        "first_action": "Check for a new core file to see if rbak quit abnormally.",
        "full_action": "Check for a new core file to see if rbak quit abnormally.\nCheck the ps output to see if rbak is hung. If so, cancel it and try again. Check the\nprogress log for any unusual messages from rbak."
    },
    "9": {
        "code": 9,
        "desc": "Anecessaryextensionpackageisnotinstalledornotconfiguredproperly",
        "first_action": "Verify that the required extension product is installed and",
        "full_action": "Verify that the required extension product is installed and\nconfigured."
    },
    "10": {
        "code": 10,
        "desc": "Allocation failed",
        "first_action": "Freeupmemorybyterminatinganyunneededprocesses",
        "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nthat consume memory. Add more swap space or physical memory."
    },
    "11": {
        "code": 11,
        "desc": "System call failed NetBackup status codes 101 NetBackup status codes",
        "first_action": "Check the All Log Entries and Problems reports to determine the system call",
        "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries and Problems reports to determine the system call\nthat failed and other information about the error.\n■ nbjm and nbproxy return status code 11 when an exception is processed, such\nas when nbproxy obtains policy or configuration information. Examine the nbjm\nunified log (originator ID 117) or the nbproxy legacy log for more detail on the\ncause of the error.\n■ A frequent cause is that the server’s file system is full. For example, you may\nsee a message similar to the following in the Problems report or bpdbm debug\nlog:\n06/27/95 01:04:00 romb romb db_FLISTsend failed: system call\nfailed (11)\n06/27/95 01:04:01 romb romb media manager terminated by parent\nprocess\n06/27/95 01:05:15 romb romb backup of client romb that exited with\nstatus 11 (system call failed)\nOn UNIX systems, run a df command on the /usr/openv/netbackup/db\ndirectory.\nIf the df command does not reveal the problem, check the bpdbm debug logs\nor do a grep for the message\nsystem call failed\nIn relevant files under the directory /usr/openv/netbackup/db/error/\nOnWindowssystems,verifythatthediskpartitionwhereNetBackupisinstalled\nhas enough room.\n■ Verify that the system is not running out of virtual memory. If virtual memory is\nthe problem, turn off unused applications or increase the amount of virtual\nmemory.\nToincreasevirtualmemoryonWindows,dothefollowingintheorderpresented:\n■ Display the Control Panel.\n■ Double-click System.\n■ On the Performance tab, set Virtual Memory to a higher value.\n■ The following information applies only to UNIX clients:\nCheck for a semaphore problem. This error may occur because the system\ndoes not have enough allocated semaphores. It is most commonly seen on\nSolaris servers when an RDBMS is also running.\nThe symptoms of the problem vary. In some cases, error messages in the\nNetBackuplogindicateabackupfailureduetoanerrorinsemaphoreoperation.\nAnother symptom is the inability of the NetBackup device manager daemon,\nltid, to acquire a needed semaphore.\nSystem requirements vary; thus, no definite recommendations can be made.\nOne customer running NetBackup and ORACLE on a Solaris server made the\nfollowing changes to the /etc/system file and then restarted the system (boot\n-r). The changes were adequate.\nset semsys:seminfo_semmni=300\nset semsys:seminfo_semmns=300\nset semsys:seminfo_semmsl=300\nset semsys:seminfo_semmnu=600\nSet these attributes to a value great enough to provide resources to all\napplications on your system.\n■ Examine other debug logs or the progress log or status on the client. Examine\nthe nbjm unified log (originator ID 117) for more detail on the cause of the error.\nIn case of NetApp storage, ensure that the following configurations are done in\nNetApp system manager:\n■ Enable Make snapshot (.snapshot) directory visible option.\n■ Disable Automatically delete older Snapshot copies."
    },
    "12": {
        "code": 12,
        "desc": "File open failed",
        "first_action": "If you want the path for the disk storage unit to reside in the root file system:",
        "full_action": "Do the following as appropriate:\n■ If you want the path for the disk storage unit to reside in the root file system:\nOpen the Change Storage Unit dialog box in the NetBackup Administration\nConsole and select the check box: This directory can exist on the root file\nsystem or system disk.\n■ If the specified path for the disk storage unit is not in the root file system or\nsystem device, verify that the path is in a mounted file system.\n■ If the specified path for the disk storage unit is in the root file system or system\ndevice but does not need to be there, use the Change Storage Unit dialog box\nto specify a different (non-root) path in a mounted file system.\n■ Check the NetBackup Problems report. Try to determine the file and why the\nerror occurred. A possible cause is a permission problem with the file. For\ndetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nthat returned this status code. Then, retry the operation and check the resulting\ndebug log.\n■ For NetBackup Lotus Notes, point-in-time restore jobs may fail with a status 12.\nThese jobs are initiated from the master server by using either the NetBackup\nAdministration Console or the Backup, Archive, and Restore interface. Their\nfailure is reported in the NetBackup tar log file. (For Windows, this file is located\nin the install_path\\NetBackup\\logs\\tar folder. For UNIX, it is located in the\n/usr/openv/netbackup/logs/tar folder.) If the install path of the NetBackup\nmaster server is different from the install path of the NetBackup client, the\nautomatic restore of Lotus transaction log extents during recovery of the Lotus\ndatabase fail. Note that the Activity Monitor shows a status 0 (successful). The\ntarlogontheclient,however,showssuccessfortherestorebutafailure(status\n12) for the Lotus database recovery.\nPerform the restore job from the Backup, Archive, and Restore interface on the\nNetBackup client.\n■ For NetBackup Snapshot Client, status code 12 may appear in the\n/usr/openv/netbackup/logs/bptm or bpdm log with the following:\ntpc_read_config failed: cannot open file\n/usr/openv/volmgr/database/3pc.conf\nThis status code may indicate that the policy is configured with either the\nNetBackup media server or the Third-party Copy Device as the off-host backup\nmethod, but the 3pc.conf file does not exist or is in the wrong location.\nInstructions are available on how to create the 3pc.conf file.\nSee the NetBackup Snapshot Client Administrator’s Guide.\n■ For a FlashBackup policy, if the CACHE= entry follows the source data entry,\nthe backup fails with status code 12. Messages such as the following appear in\nthe /usr/openv/netbackup/logs/bpbkar logs on the client:\n09:55:33.941 [6092] <16> bpfsmap: ERR - open_snapdisk: NetBackup\nsnapshot enable failed error 3\n09:55:33.942 [6092] <32> bpfsmap: FTL - bpfsmap: can't open\nsnapshot disk /dev/rdsk/c4t1d0s3 errno 0\n09:55:33.950 [6092] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 12: file open failed\n09:55:33.956 [6092] <4> bpbkar Exit: INF - EXIT STATUS 12: file\nopen failed\n09:55:33.957 [6092] <2> bpbkar Exit: INF - Close of stdout\ncomplete\nChangetheorderofthebackupselectionslistsothattheCACHEentryprecedes\nthe source data entry. (The source data entry specifies the raw partition that\ncontains the file system to be backed up.)"
    },
    "13": {
        "code": 13,
        "desc": "File read failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the problem",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the problem\noccurred.\n■ Check that network communication works properly.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ For a FlashBackup client, check the /var/adm/messages log for errors like the\nfollowing:\nMar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache\n/dev/rdsk/c0t2d0s3 full - all snaps using this cache are now\nunusable\nThis error indicates that the cache partition is not large enough. If possible,\nincrease the size of the cache partition. Or, if multiple backups use the same\ncache, reduce the number of concurrent backups. To reduce the number,\nreschedule some of them or reschedule the entire backup to a time when the\nfile system is less active.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ Ensure that the latest service packs for all products and components (SQL\nServer, Exchange, Notes, etc.) have been installed.\n■ Ensure that all the network hardware (NICs, hubs, switches, routers, etc.)\nthroughout the environment are set to full duplex, not half duplex.\n■ Check the following items regarding the NICs in your system:\n■ Upgrade to the latest NIC drivers throughout the system.\n■ Ensure that all NICs are set to full duplex, not half duplex.\nSee Troubleshooting network interface card performance in the NetBackup\nTroubleshooting Guide.\n■ Increase the timeout settings on the NIC.\n■ If NIC teaming is implemented, deactivate for testing purposes.\n■ Replace the NIC itself on the affected client or server.\n■ For NetBackup Snapshot Client, status code 13 may appear in the\n/usr/openv/netbackup/logs/bpbkar log.\nThe log can indicate the following:\n■ ThefilestobackupresideonanIDEdriveasopposedtoSCSI.Theoff-host\nbackup method was set to either NetBackup media server or Third-Party\nCopy Device. If you use off-host backup, the disk that contains the client\nfiles must be a SCSI or Fibre Channel device.\nIf the disk is an IDE drive, you may see the following in the /usr/openv/\nnetbackup/logs/bpfis log:\nget_disk_info: FTL - /var/tmp/caa026fEU disk_inquiry failed.\nErrno = 25: Inappropriate ioctl for device\nThefollowinglistingmayappearinthe/usr/openv/netbackup/logs/bpbkar\nlog:\nbpbkar: INF - Processing /var\nbpbkar: ERR - get_disk_info() failed, status 13\nbpbkar: ERR - tpc_get_disk_info() failed: err 13\nbpbkar: ERR - bpbkar FATAL exit status = 13: file read failed\nbpbkar: INF - EXIT STATUS 13: file read failed\n■ Thefilestobackupexistonafilesystemthatisnotmounted.Thefilesystem\nthat is specified as the snapshot source must be mounted. If the snapshot\nsource is not mounted but the mount point is present, NetBackup may try to\ntake a snapshot of the directory preceding the directory that was specified\nas the snapshot source.\n■ For the NetBackup media server method, you may need to increase the\nclient read timeout value. In some environments, NetBackup may require\nmore read time than the default value allows. If the client read timeout is\ninsufficient, the backup may fail and that causes this error.\nTo increase the client read timeout for all clients, in the NetBackup\nAdministration Console, go to Host Properties > Master Servers >\ndouble-click the master server, then go to Properties > Timeouts. Then,\nincrease the client read timeout.\n■ On Windows, refresh the Backup, Archive, and Restore client console and\nretry the restore. This action refreshes the file list that is displayed in the client\nconsole and passes the correct information about the selected files.\n■ To prevent timeouts in the VMware VDDK that cause simultaneous hotadd\nbackups from the same VMware backup host to fail, do one of the following:\n■ Reduce the number of hotadd backups that run simultaneously.\n■ Increase the client-read timeout on the media server as appropriate (15\nminutes or more):\nIn the NetBackup Administration Console, click NetBackup Management\n> Host Properties > Double-click on media server > Timeouts > Client\nread timeout."
    },
    "14": {
        "code": 14,
        "desc": "File write failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the problem",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the problem\noccurred.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ Make sure that the routers, bridges, and other network devices are all at \"full\"\nduplex.\nSee Troubleshooting network interface card performance in the NetBackup\nTroubleshooting Guide.\n■ Use a \"sniffer\" program to determine the number of packets being rejected or\nre-requested.\n■ On Windows systems, the client bpbkar log may contain a 10054 Connection\nReset Error (usually indicates a hardware error). Somewhere between the\nNetBackup client and server, the connection was reset. When NetBackup\nreceives this error, it cannot continue the backup. This error has been attributed\nto the following:\n■ A hiccup in the network.\n■ A bad network interface card on a NetBackup client.\n■ A bad network interface card on the NetBackup server.\n■ Faulty routers.\n■ Any other applications that interfere with NetBackup connections.\n■ The error occurs while you use the NetBackup Java interface: The application\nserver (bpjava processes) for the NetBackup Java interface probably ran out\nof disk space in the file system containing\n/usr/openv/netbackup/logs/user_ops.Theapplicationserverwritestemporary\nfiles into directories in the /user_ops directory. Try clearing up disk space in\nthe file system."
    },
    "15": {
        "code": 15,
        "desc": "File close failed",
        "first_action": "ChecktheNetBackupProblemsreportforcluesonwhere",
        "full_action": "ChecktheNetBackupProblemsreportforcluesonwhere\nand why the problem occurred. For detailed troubleshooting information, create a\ndebug log directory for the process that returned this status code. Then retry the\noperation and check the resulting debug log."
    },
    "16": {
        "code": 16,
        "desc": "Unimplemented feature NetBackup status codes 109 NetBackup status codes",
        "first_action": "Save all of the error information and contact Cohesity",
        "full_action": "Save all of the error information and contact Cohesity\nTechnical Support."
    },
    "17": {
        "code": 17,
        "desc": "Pipe open failed",
        "first_action": "Save all of the error information and contact Cohesity",
        "full_action": "Save all of the error information and contact Cohesity\nTechnical Support."
    },
    "18": {
        "code": 18,
        "desc": "Pipe close failed",
        "first_action": "Check the NetBackup Problems report for clues on why",
        "full_action": "Check the NetBackup Problems report for clues on why\nthe failure occurred. For detailed troubleshooting information, create a debug log\ndirectory for the process that returned this status code. Then retry the operation\nand check the resulting debug log."
    },
    "19": {
        "code": 19,
        "desc": "Getservbyname failed",
        "first_action": "Check the NetBackup Problems report for clues on why the failure occurred.",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on why the failure occurred.\n■ On a UNIX or Linux system, check that /etc/services and NIS services map\n(if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.\n■ On a Windows system, verify that the\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileshowsthecorrectentries\nfor the NetBackup Internet processes: bpcd, bpdbm, and bprd.\nEnsure that the following numbers match the settings in the services file: The\nNetBackup Client Service Port number and NetBackup Request Service Port\nnumber on the Network tab in the NetBackup Client Properties dialog box.\nTo display this dialog box, start the Backup, Archive, and Restore interface and\nclick NetBackup Client Properties on the File menu. The values on the\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nSee\"Verifyinghostnameandserviceentries\"intheNetBackupTroubleshooting\nGuide.\n■ Check the level of network activity. An overloaded network can cause this error.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log."
    },
    "20": {
        "code": 20,
        "desc": "Invalid command parameter",
        "first_action": "Review the NetBackup Problems report for clues.",
        "full_action": "Do the following, as appropriate:\n■ Review the NetBackup Problems report for clues.\n■ If the error occurs when you run a command on the command line, verify that\nthe parameters are valid.\n■ This status code may occur if nbjm passes parameters but does not have a\nrequired parameter. Review the nbjm unified logs (originator ID 117) for the list\nof parameters that were passed.\n■ The following information pertains to NetBackup Snapshot Client.\n■ If the following appears in the /usr/openv/netbackup/logs/bptm log as\nenabled on a third-party copy backup, multiplexing was enabled on a\nthird-party copy backup:\nbptm: cannot perform Third-Party-Copy for multiplexed backups\nsend_brm_msg: ERROR 20\nbptm: EXITING with status 20\nThe Third-party Copy Device off-host backup method is incompatible with\nmultiplexing (the writing of two or more concurrent backup jobs to the same\nstorage device). You must disable multiplexing for any third-party copy\nbackups. If multiplexing is enabled, the backup fails.\n■ The media server may not have the correct 3pc.conf file entry for the client\ndisk that is needed for the backup.\nThe following appears in the /usr/openv/netbackup/logs/bpbkar log:\n14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1\nEMC:SYMMETRIX:601092014000\n14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive\nchild started, pid = 15822\n14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:\n15822 killed\n14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1\n14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain\ndevice id string EMC:SYMMETRIX:601092014000\n14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit\nstatus = 227: no entity was found\n14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no\nentity was found\n14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout\ncomplete\nThis shows that a particular device cannot be found in the 3pc.conf file on\nthemediaserver(14:47:02.031 [15773] <16> bpmap_send_extend: ERR\n- can't obtain device id string EMC:SYMMETRIX:601092014000).\nThe problem is one of the following:\n■ The3pc.conffileonthemediaserverisoutdated.Recreatethe3pc.conf\nfile.\n■ The media server is not on the same Fibre Channel network as the\nthird-partycopydeviceandclientdisk.Asaresult,the3pc.conffiledoes\nnot have a correct entry for the client disk. Run the bptpcinfo command\nwith the -x client_name option; this option adds the client disk to the\n3pc.conf file. For each disk that is added to the file by means of\nbptpcinfo -x client_name, you may need to add the device’s World\nWide Name (WWN=).\nSee the NetBackup Snapshot Client Configuration online document.\nSee Snapshot Client Assistance in the NetBackup Snapshot Client\nAdministrator’s Guide.\n■ The HP VxFS snapshot mechanism requires a dedicated cache partition for\neach snapshot. A check is made in the mount table to make sure that the\ncache partition is not already in use. If the cache partition is already in use,\nstatus code 20 occurs.\nReviewthe/usr/openv/netbackup/logs/bpbkarlogforamessagesimilar\nto the following:\nbpfsmap: FTL - bpfsmap: snapshot cache already in use,\n/dev/arrayvg/vol4c\nbpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid\ncommand parameter\nbpbkar Exit: INF - EXIT STATUS 20: invalid command parameter\nIf the snapshot cache partition is already in use, do one of the following: Set\nup your policy schedules to run at different times or use different cache\npartitions for each backup.\nIf the Allow multiple data streams option is enabled, each stream must\nhave its own dedicated cache partition.\n■ Compare the NetBackup version level on the server to the version level on the\nclients by doing the following:\n■ On UNIX or Linux NetBackup servers and clients, review the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, review the\ninstall_path\\NetBackup\\version.txt file or the About NetBackup item\non the Help menu.\n■ On Microsoft Windows clients, review the About NetBackup item on the\nHelp menu.\n■ If a Java interface displays the error, tell them how to enable the debug print\nmanager in the Java startup file. Retry and compare the parameters that\nwere logged on the Java log with the parameters listed in the commands\nusage statement.\n■ FortheBackupMediaServeroptionforVMwarebackups,thestorageunitthat\nis specified in the policy must be unique to your media servers. If the storage\nunitisalsoavailableonanothermediaserver,thesnapshotjobcannotsucceed.\n■ If you protect NAS arrays using VSO FIM snapshot method, perform off-host\nbackup using an alternate client.\n■ ForBigDatapolicies,themediaserverandthebackuphostsmustusethesame\nNetBackup version.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocessthatreturnedthisstatuscode(iftheprocessuseslegacylogging).Then\nretry the operation and review the resulting log."
    },
    "21": {
        "code": 21,
        "desc": "Socket open failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the failure",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that returned this status code. Then,\nretry the operation and check the resulting debug logs.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed.\n■ TheNetBackupmediaservermaynothavetheServicesforNetworkFileSystem\n(NFS) installed. As a result, the media server cannot contact the Portmapper\nservice. The attempt to manually start the NFS services fails because the\nNetwork File System is not installed.\nInstall the Services for Network File System on the media server."
    },
    "22": {
        "code": 22,
        "desc": "Socket close failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the failure",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then, retry the operation and check the resulting debug logs.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed."
    },
    "23": {
        "code": 23,
        "desc": "Socket read failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the failure",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then, retry the operation and check the resulting debug logs.\n■ Corrupt binaries are one possible cause for this error.\nLoad a fresh bptm from the install media to try to resolve the problem.\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed.\n■ The NetBackup media server is an 8.0 or earlier version and you have disabled\ninsecure communication in NetBackup. If you want to continue with the host\nconnection, do one of the following:\n■ In the NetBackup Administration Console on the master server host,\nselect Security Management > Global Security > Enable insecure\ncommunication with the NetBackup 8.0 and earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncommand."
    },
    "24": {
        "code": 24,
        "desc": "Socket write failed",
        "first_action": "Check the NetBackup Problems report for clues on where and why the failure",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues on where and why the failure\noccurred. If you cannot determine the cause from the Problems report, create\ndebug log directories for the processes that could have returned this status\ncode. Then retry the operation and check the resulting debug logs.\n■ A possible cause is a high network load. For example, this problem occurs with\nCannot write to STDOUT when a Windows system that monitors network load\ndetects a high load. It then sends an ICMP packet to other systems to inform\nthem that the route they use is disconnected. The log messages were similar\nto the following:\n01/31/22 14:05:23 ruble crabtree.null.com from client\ncrabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No\nroute to host\n01/31/22 14:05:48 ruble crabtree.null.com successfully wrote\nbackup id crabtree.null.com_1643637900, copy 1, fragment 1,\n440864 Kbytes at 628.538 Kbytes/sec\n01/31/22 14:05:51 netbackup crabtree.null.com CLIENT\ncrabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT\nSTATUS 24 (socket write failed)\n■ The following information applies only to Sun Solaris:\nVerify that all operating system patches are installed.\nSee the Operating Notes section of the NetBackup Release Notes.\n■ The following information applies only to Windows systems:\nVerify that the recommended service packs are installed."
    },
    "25": {
        "code": 25,
        "desc": "Cannot connect on socket",
        "first_action": "Verifythatbpcompatd,vnetd,andPrivateBranchExchange(PBX)arerunning.",
        "full_action": "Do the following, as appropriate:\n■ Verifythatbpcompatd,vnetd,andPrivateBranchExchange(PBX)arerunning.\nInformation on how to start PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide.\n■ If necessary, stop and restart NetBackup.\n■ On UNIX systems, enter the following:\n/usr/openv/netbackup/bin/bp.kill_all\n/usr/openv/netbackup/bin/bp.start_all\n■ On Windows systems, enter the following:\ninstall_path\\NetBackup\\bin\\bpdown\ninstall_path\\NetBackup\\bin\\bpup\n■ The following information applies only to a UNIX or Linux NetBackup master\nserver:\nVerify that the bprd and the bpdbm processes are running. If these processes\nare not running, start them. On a Windows master server, verify that the\nNetBackup Request Manager and the NetBackup Database Manager services\nare running. If these services are not running, start them.\nIf these processes or services are running, examine the All Log Entries report\nfor the time of the failure to determine where the failure occurred.\nDo one of the following:\n■ Ifyoucannotviewthereportoryougetacannot connect on socketerror,\nverify again that the NetBackup Database Manager service or daemon is\nrunning. Then, create a debug log directory for bpdbm, retry the operation,\nand check the resulting debug log.\n■ If you view the report and do not find a problem-related entry, create the\ndebug log directories for the related processes that were running when the\nerror first appeared. (This process frequently is bpbrm.) Then, retry the\noperation and check the resulting debug logs.\n■ Verify that the server list specifies the correct master server.\n■ The following information applies only to Windows systems:\nThe master server is designated in the Server to use for backups and\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterface and click Specify NetBackup Machines and Policy Type on the\nFile menu.\n■ The following information applies only to UNIX and Linux systems:\nThe master server is the first SERVER entry in the bp.conf file.\n■ Check the Cohesity Technical Support website to ensure that all\nrecommended NetBackup patches are installed.\n■ If failure occurs when you run a user-directed backup from a client, make\nsure that a user-directed backup schedule exists at the master server.\n■ With NetBackup database extensions:\nMakesurethattheapplicabledatabaseproducthasthecorrectpermissions\nallowing NetBackup to write to the progress log on the client.\n■ The following information applies only to UNIX systems:\nIf bpdbm has quit when the shutdown script runs on a media server, carefully\nread the K77netbackup script. It contains details on how to prevent this\nproblem. The script is in /usr/openv/netbackup/bin/goodies.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ Check the services file.\n■ The following information applies only to UNIX systems:\nVerify that the /etc/services file (and NIS services if NIS is used) has\nentries for the NetBackup services: bpcd, bpdbm, and bprd.\nOnWindows,verifythatthe%SystemRoot%\\system32\\drivers\\etc\\services\nfile has the correct entries for bpcd, bpdbm, and bprd.\nAlso, verify that the following numbers match the settings in the services file:\nThe NetBackup Client Service Port and the NetBackup Request Service\nPort on the Network tab in the NetBackup Client Properties dialog box. To\ndisplay this dialog box, start the Backup, Archive, and Restore interface and\nclick NetBackup Client Properties on the File menu. The values on the\nNetworktabarewrittentotheservicesfilewhentheNetBackupClientservice\nstarts.\nSee Verifying host names and service entries in NetBackup in the NetBackup\nTroubleshooting Guide.\n■ On Sun Solaris, verify that all operating system patches are installed\nSee the Operating Notes section of the NetBackup Release Notes.\n■ On Windows, verify that the recommended service packs are installed.\n■ When the base NetBackup license key expires, daemons (such as bprd and\nbpdbm) terminate on the NetBackup server. If these daemons are not running,\nyou are likely to encounter status code 25 errors in the Administration console.\nInstall a valid base NetBackup license key, restart the daemons, and restart the\nconsole.\n■ For NetBackup Snapshot Client, the following applies: When many devices are\nconfigured on a media server, it may take a long time for the bptpcinfo\ncommand to generate the file 3pc. When the backup is run for the first time, the\nbackup may fail with status 25. Make sure that the\n/usr/openv/volmgr/database/3pc.conffileexists.Ifitdoes,rerunthebackup.\nIf the backup fails again, run the bptpcinfo manually to generate the file 3pc,\nthen try the backup again.\n■ In the Auto Image Replication (A.I.R.) scenario, the error can occur if insecure\ncommunication is disabled in NetBackup after the trust relationship between\nthe 8.1 and 8.0 master servers is established. If you want to continue with the\nhost connection, do one of the following:\n■ In the NetBackup Administration Console on the master server host,\nselect the Security Management > Global Security > Secure\nCommunication>EnableinsecurecommunicationwithNetBackup8.0\nand earlier hosts option.\n■ Specifythenbseccmd -setsecurityconfig -insecurecommunication on\ncommand.\n■ For RHV:\n■ Ensure that the RHV credentials are correct and the virtualization server is\naccessible.\n■ For VMware:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhethertheVMwarevirtualizationservers'(vCenter,ESX,ESXi)certificates\nand CRLs are added to the respective ECA configured trust store and the\nCRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only the PEM certificate format for file-based trust store & Windows trust\nstore are supported for virtualization servers. P7b or DER format file based\ntruststoreisnotsupported.Whenthisfeatureisenabled,thecertificateECA\nstore should either be Windows certificate store or file based PEM format\nstore.\n■ For Nutanix AHV:\n■ Ensure that the CA certificate is added to the NetBackup trust store. Refer\nto the Nutanix AHV Administrator’s Guide for more details."
    },
    "26": {
        "code": 26,
        "desc": "Client/server handshaking failed",
        "first_action": "Verify the PKI artifacts by running these commands:",
        "full_action": "Determine which activity encountered the handshake\nfailure by examining the All Log Entries report for the appropriate time period.\nDetermine the client and server that had the handshake failure.\nFordetailedtroubleshootinginformation,createadebuglogdirectoryfortheprocess\nthat returned this status code. Then retry the operation and review the resulting\ndebug log.\nIftheerrorhasoccurredduringthecertificateenrollmentprocess,verifythefollowing:\n■ Verify the PKI artifacts by running these commands:\n■ nbcertcmd -listAllCertificates [-jks] - Run on the master server to\ndisplay the web server certificate information from Java keystore.\n■ nbcertcmd -listCACertDetails -ECA - Run on the host to list the details\nof the CA certificates that are stored its trust store.\n■ Ensure that the issuers of the client and server certificates are available in each\nother’s trust stores."
    },
    "27": {
        "code": 27,
        "desc": "Child process killed by signal",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log."
    },
    "28": {
        "code": 28,
        "desc": "Failed trying to fork a process",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\ndebug log directories for the processes that think may have returned this status\ncode. Then, retry the operation and check the resulting debug logs."
    },
    "29": {
        "code": 29,
        "desc": "Failed trying to exec a command",
        "first_action": "Check the NetBackup All Log Entries report for clues on where and why the",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup All Log Entries report for clues on where and why the\nfailure occurred.\n■ Check the permissions on the command to be run.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log."
    },
    "30": {
        "code": 30,
        "desc": "Cannot get password information",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry the operation and check the resulting debug log."
    },
    "31": {
        "code": 31,
        "desc": "Could not set user ID for process",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log."
    },
    "32": {
        "code": 32,
        "desc": "Could not set group ID for process",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log."
    },
    "33": {
        "code": 33,
        "desc": "Failed while trying to send mail",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\na debug log directory for the process that you think may have returned this status\ncode. Then, retry the operation and check the resulting debug log."
    },
    "34": {
        "code": 34,
        "desc": "Failed waiting for child process",
        "first_action": "Check the NetBackup All Log Entries report for clues on",
        "full_action": "Check the NetBackup All Log Entries report for clues on\nwhereandwhythefailureoccurred.Fordetailedtroubleshootinginformation,create\nadebuglogfortheprocessthatyouthinkmayhavereturnedthisstatuscode.Then,\nretry the operation and check the resulting debug log."
    },
    "35": {
        "code": 35,
        "desc": "Cannot make required directory",
        "first_action": "Check the NetBackup All Log Entries report to determine which directory was",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup All Log Entries report to determine which directory was\nnotcreatedandwhyitwasnotcreated.Inparticular,checkforafulldiskpartition.\n■ Check the permissions on the parent directory. Verify that NetBackup services\narestartedwithaLogonasaccountthathaspermissiontocreatethedirectory.\n■ For detailed troubleshooting information, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log."
    },
    "36": {
        "code": 36,
        "desc": "Failed trying to allocate memory",
        "first_action": "Freeupmemorybyterminatinganyunneededprocesses",
        "full_action": "Freeupmemorybyterminatinganyunneededprocesses\nthat consume a lot of memory. Add more swap space or physical memory."
    },
    "37": {
        "code": 37,
        "desc": "Operation requested by an invalid server",
        "first_action": "The operating system where the files were backed up does not match the",
        "full_action": "ExaminetheNetBackupAllLogEntriesreportforthetime\nof this error to determine which system tried to connect to the master server.\nIf the server is a valid media server, verify that the storage unit for the media server\nisdefined.Also,verifythattheserverorWindowsNetBackupRemoteAdministration\nConsole has a server list entry on the master server.\nIf necessary, update the server list.\nOn a UNIX or Linux master server, add a SERVER = media_server_name to the\nbp.conf file. media_server_name is the host name of the media server. On a\nWindows master server, add the media server to the list on the Servers tab in the\nMaster Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nIf a server or NetBackup Remote Administration Console has more than one host\nname (Example: multiple network interfaces), verify that the master server has a\nserver list entry for each of them.\nIf you change the server list on a UNIX or Linux master server, do the following for\nthe changes to take effect: Stop and then restart the NetBackup Request Daemon\n(bprd) and NetBackup Database Manager Daemon (bpdbm). On Windows, stop\nand restart the NetBackup Request Manager and NetBackup Database Manager\nservices.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ The operating system where the files were backed up does not match the\noperating system where NetBackup attempted to restore the files.\nSelect a virtual machine for the restore that has the same operating system as\nthe backup virtual machine. Confirm that the operating system type that is\nspecifiedintargetVMpropertiesmatchestotheoperatingsystemthatisinstalled\nin the target VM."
    },
    "38": {
        "code": 38,
        "desc": "Could not get group information",
        "first_action": "Check the NetBackup Problems report for clues on why",
        "full_action": "Check the NetBackup Problems report for clues on why\nthe error occurred. For detailed troubleshooting information, create a debug log\ndirectory for the process that returned this status code. Then retry the operation\nand check the resulting debug log."
    },
    "39": {
        "code": 39,
        "desc": "Client name mismatch",
        "first_action": "Change one of the following so the two match: the",
        "full_action": "Change one of the following so the two match: the\nNetBackup client name setting on the client (see the applicable NetBackup users\nguide) or the one in the policy configuration on the server."
    },
    "40": {
        "code": 40,
        "desc": "Network connection broken",
        "first_action": "Try pinging the client from the server. If pinging is not possible, check for loose",
        "full_action": "Do the following, as appropriate:\n■ Try pinging the client from the server. If pinging is not possible, check for loose\nconnections or other network problems.\n■ Verify that the server list settings are correct on both the client and the server.\nIf the backup involves a media server, verify that these entries are correct on\nboth the master and the media server. For example, if a media server does not\nhave a server list entry for the master, it does not accept connections from the\nmaster.\n■ On Windows, the master server is designated on the Servers tab in the\nMaster Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in\nthe NetBackup Troubleshooting Guide.\n■ On UNIX and Linux systems, the master server is the first SERVER entry in\nthe bp.conf file.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ Status code 40 can also be due to denial of a mount request by the operator.\n■ Thisstatuscodemayoccurifnbjmwasunabletoconnecttobpbrmortobpmount.\nExamine the nbjm unified log (originator ID 117) or the bpbrm or the bpmount\nlegacy logs for more detail on the cause of the error."
    },
    "41": {
        "code": 41,
        "desc": "Network connection timed out NetBackup status codes 127 NetBackup status codes",
        "first_action": "If you backup to many files, use Host Properties on the NetBackup server to",
        "full_action": "Do the following, as appropriate:\n■ If you backup to many files, use Host Properties on the NetBackup server to\nchangeClientreadtimeouttoamuchhighervalue(forexample:4000).These\nsettings are on the Universal Settings tab in the Master Server Properties\ndialog box. The default for this time out is 300 seconds.\nAlso, set the File browse timeouton the Timeouts tab to a value greater than\n4000.\nThen retry the operation. The names of the files are logged on the debug log\nfile in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar\nprocesses them. The last file in the log is the file that causes problems.\n■ On UNIX, Linux, or Windows clients, check for the following problems with the\nbpbkar client process.\nOn Windows clients:The bpbkar client process is not hung. Due to the files and\ndirectoriesitscans,ithasnotrepliedtotheserverwithintheClientreadtimeout\nperiod. This error occurs during incremental backups when directories have\nthousands of unmodified files.\nFor this case, use Host Properties on the NetBackup server to change Client\nreadtimeout.ThissettingisontheUniversalSettingstabintheMasterServer\nProperties dialog box. The default for this time out is 300 seconds.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nYou can also monitor CPU utilization to determine if this condition exists.\nThe following information applies only to UNIX or Linux clients:\n■ Thebpbkarclientprocessishungonafilethathasamandatorylockingset.\nFor this case, add the following to the client’s bp.conf file:\nVERBOSE\nAs root on the client, run the following:\ntouch /usr/openv/netbackup/bpbkar_path_tr\n/usr/openv/netbackup/logs/bpbkar\nThen retry the operation. The names of the files are logged on the debug\nlogfileinthe/usr/openv/netbackup/logs/bpbkardirectorybeforebpbkar\nprocesses them. The last file in the log is the file that causes problems.\nNote: Also, use these procedures for other unknown bpbkar hangs.\nIf the problem is due to mandatory file locking, have NetBackup skip the\nlocked files. Set LOCKED_FILE_ACTION to SKIP in the\n/usr/openv/netbackup/bp.conf file on the client.\n■ The bpbkar client process is not hung. Due to the files and directories it\nscans, it has not replied to the server within CLIENT_READ_TIMEOUT or\nCLIENT_CONNECT_TIMEOUT. This error occurs during backups when\ndirectorieshavethousandsofunmodifiedfilesorduringrestoresofthesparse\nfiles that have thousands of holes. For this case, try to add or modify the\nCLIENT_READ_TIMEOUT value in the server’s\n/usr/openv/netbackup/bp.conf file. The default for\nCLIENT_READ_TIMEOUT is 300 seconds if it is not specified.\nUse your system’s ps command and monitor CPU utilization to help decide\nwhich of these conditions exist.\nWhen you finish the investigation of the problem, delete the\n/usr/openv/netbackup/logs/bpbkardirectory,sincethelogfilescanbecome\nquite large and are not deleted automatically. Also delete\n/usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log\nfiles than needed the next time you create directory\n/usr/openv/netbackup/logs/bpbkar.\n■ On Windows systems, try the following:\n■ Disable the following file:\ninstall_path\\VERITAS\\NetBackup\\bin\\tracker.exe\n■ Repair hard drive fragmentation. Try an application that is called Diskeeper\nLite, which is part of the Windows Resource Kit.\n■ Make sure that enough space is available in \\temp.\n■ If the server cannot connect to the client, create bpcd or bpbkar (UNIX, Linux,\nand Windows only) debug log directories on the client. Then retry the operation\nand check the resulting logs. If these logs do not provide a clue, create a bpbrm\ndebuglogontheserver.Thenretrytheoperationandchecktheresultingdebug\nlog.\nIf the bpbrm log has entries similar to the following, the problem is in the routing\nconfiguration on the server:\nbpbrm hookup_timeout: timed out waiting during the client hookup\nbpbrm Exit: client backup EXIT STATUS 41: network connection\ntimed out\nVerify that the client IP address is correct in the name service that is used. On\nUNIX clients, if both the NIS and the DNS files are used, verify that they match.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If you use an AIX token ring adapter and the routed daemon is running, the\ntime out occurs because the token ring adapter creates dynamic routes. It then\ncauses the routed daemon to crash.\n■ For a FlashBackup client, this error occurs if the file system being backed up is\nverylargeandhasaverylargenumberoffiles.Itcanalsooccurifalargenumber\nof concurrent data streams are active at the same time. To correct it, add\nCLIENT_READ_TIMEOUTtothe/usr/openv/netbackup/bp.conffileandset\nit to increase the time-out interval.\n■ Check the Cohesity Technical Support website to ensure that all recommended\nNetBackup patches are installed.\n■ Add the CLIENT_READ_TIMEOUT values to the master server, media server,\nandclientwhenaNetBackupdatabaseextensionproductisinstalled.Thevalues\nshould all be the same for each server. The value set is dependent on the size\nofthedatabasebeingbackedup.MoreinformationonCLIENT_READ_TIMEOUT\nis available.\nSee the NetBackup Administrator’s Guide, Volume II.\n■ Make sure that enhanced authentication is configured correctly. For example,\nthefollowingmayresultinstatuscode41:HostAisconfiguredtouseenhanced\nauthentication with host B, but host B is not configured to use enhanced\nauthentication with host A. In this case, connections from host B to host A are\nlikely to fail with status code 41. Connections from host A to B are likely to fail\nwith authentication errors (status code 160).\n■ If the Amazon S3 compliant cloud is not able to process the high number of\nrequests, perform one of the following:\n■ Configure the bandwidth throttling to reduce the number of requests. See\n\"NetBackup cloud storage server connection properties\" in the NetBackup\nCloud Administrator's Guide.\n■ Reduce the number of read/write buffers. See \"NetBackup cloud storage\nserverbandwidththrottlingproperties\"intheNetBackupCloudAdministrator's\nGuide.\n■ Ask your cloud vendor to increase the parallel requests limit.\n■ IfconnectionbetweenthemasterserverandaNATclientfailed,dothefollowing:\n■ Ensure that the subscriber service on the client is up and running.\n■ If the problem persists, restart the client services and ensure that the\nsubscriber service is connected with the NetBackup Messaging Broker (or\nnbmqbroker) service."
    },
    "42": {
        "code": 42,
        "desc": "Network read failed",
        "first_action": "Verify that both the client and the server are operational.",
        "full_action": "Do the following, as appropriate:\n■ Verify that both the client and the server are operational.\n■ Resolve any network communication problems.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Check the Problems report for clues."
    },
    "43": {
        "code": 43,
        "desc": "Unexpected message received",
        "first_action": "Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.",
        "full_action": "Do the following, as appropriate:\n■ Verifythatthecorrectversionofsoftwareisrunningontheclientandtheserver.\n■ To enable detailed debug logging, do the following:\n■ On the server, create a bpbrm debug log directory.\n■ On clients, create a bpcd debug log directory.\n■ Increase the amount of debug information to include in the logs.\nSee \"About logs\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and examine the logs.\nIf you use bpstart_notify scripts on UNIX, Linux, or Windows clients, verify\nthat messages are not written to stdout or stderr."
    },
    "44": {
        "code": 44,
        "desc": "Network write failed",
        "first_action": "Check the Problems report for information about the error.",
        "full_action": "Do the following, as appropriate:\n■ Check the Problems report for information about the error.\n■ Verify that the client and servers are operational and connected to the network.\n■ Create a debug log directory for the process that reported the problem and the\noperation. Examine the resulting debug log file for detailed troubleshooting\ninformation.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide."
    },
    "45": {
        "code": 45,
        "desc": "Request attempted on a non-reserved port",
        "first_action": "On UNIX NetBackup servers and clients, check the",
        "full_action": "Verify that the latest software is installed on the client and\nserver.\n■ On UNIX NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\netbackup\\version.txt file or the About NetBackup item on\nthe Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the Help\nmenu."
    },
    "46": {
        "code": 46,
        "desc": "Server not allowed access",
        "first_action": "If the server is a valid server but is not listed on the client, add its name to the",
        "full_action": "Do the following, as appropriate:\n■ If the server is a valid server but is not listed on the client, add its name to the\nclient’s server list:\n■ On Windows clients in the Specify NetBackup Machines and Policy Type\ndialogbox,dothefollowing:AddtheserverintheServertouseforbackups\nand restores drop-down list. To display this dialog box, start the Backup,\nArchive, and Restore interface on the client. Then click Specify NetBackup\nMachines and Policy Type on the File menu.\n■ On UNIX and Linux clients, add a SERVER entry in the bp.conf file.\nIf you continue to have problems, more information is available:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\nSee \"Verifying host names and services entries\" in the NetBackup\nTroubleshooting Guide.\n■ To make non-encrypted backups of the client, set CRYPT_OPTION on the client\nto allowed or denied.\nRefer to the NetBackup Security and Encryption Guide.\n■ If the NetBackup encryption evaluation license has expired on the server and\nyouwanttocontinueencryptingbackupsoftheclient,dothefollowing:Purchase\na permanent encryption license key and add it to the server. After you add the\npermanent encryption license key, check the attributes of the backup policy to\nmake sure that encryption is selected.\nTo check the validity of an evaluation license key, do the following:\nOn Windows, go to the Help menu on the NetBackup Administration window\non the NetBackup server and select License Keys. If the evaluation key is not\nlisted in the NetBackup License Keys window, the key has expired. Use this\nwindow to add the new permanent encryption key.\nOn UNIX, use the following command on the server:\n/usr/openv/netbackup/bin/admincmd/get_license_key\nSelect option f to list the active license keys and features. If the evaluation key\nis not listed, the key has expired. Use this command to add the new permanent\nencryption key.\n■ Be sure that all name resolution services (primary, load-balancing, and\nsecondary) are properly configured for consistent forward and reverse name\nresolution of NetBackup hosts.\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100029136\n■ If the error occurs during external certificate enrollment, do the following:\n■ Add the server name from where you want to enroll the external certificate\nfor a remote host in its SERVER configuration option."
    },
    "47": {
        "code": 47,
        "desc": "Host is unreachable",
        "first_action": "Verify that the name service (or services) used by the client are configured to",
        "full_action": "Do the following, as appropriate:\n■ Verify that the name service (or services) used by the client are configured to\nresolve the host names of the NetBackup server correctly.\n■ Verify that the name service (or services) used by the server are configured to\nresolve the host name of the NetBackup client correctly.\n■ Try to ping the client from the server and the server from the client.\n■ If you continue to have problems, do the following:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide."
    },
    "48": {
        "code": 48,
        "desc": "Client host name could not be found",
        "first_action": "The NetBackup policy configuration on the master server.",
        "full_action": "Verify that the client name is correct in the following:\n■ The NetBackup policy configuration on the master server.\n■ The General tab in the following dialog boxes: NetBackup Client Properties\nand Specify NetBackup Machines and Policy Type (on Microsoft Windows\nnon-target clients). To display these dialog boxes, start the Backup, Archive,\nandRestoreinterfaceontheclient.FortheGeneraltab,clickNetBackupClient\nProperties on the File menu; click Specify NetBackup Machines and Policy\nType on the File menu.\n■ The bp.conf file on UNIX and Linux clients.\n■ On clients and servers, verify that the name service is set up to resolve the\nNetBackup client names correctly.\nOn UNIX clients, verify that the client’s host name is in the /etc/hosts file or\nthe YP hosts file or NIS maps.\n■ The client name reflects a host where the NetBackup client is installed.\nNetBackupdoesnotcollectlogsfromanyagentlesshostswheretheNetBackup\nclient is not installed. For agentless hosts, the error log displays the following\nmessage: Failed to collect logs (EC: 48 - Client hostname could\nnot be found)."
    },
    "49": {
        "code": 49,
        "desc": "Client did not start",
        "first_action": "Make sure that software is installed on the client and it is the correct version. If",
        "full_action": "Do the following, as appropriate:\n■ Make sure that software is installed on the client and it is the correct version. If\nnecessary, reinstall the client software.\n■ Check for full file systems on the client.\n■ Enable detailed debug logging on the client by doing one of the following:\n■ Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug log\ndirectories.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On Windows clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\nRetry the operation and examine the resulting logs.\n■ On UNIX or Linux systems, use the UNIX sum command to check for corrupt\nbinaries."
    },
    "50": {
        "code": 50,
        "desc": "Client process aborted",
        "first_action": "Enable detailed debug logging.",
        "full_action": "Do the following, as appropriate:\n■ Enable detailed debug logging.\n■ Create a bpbkar debug log directory (UNIX, Linux, and Windows clients\nonly).\n■ Create a bpcd debug log directory.\n■ On UNIX clients, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or the log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\nRetry the operation and examine the resulting logs.\n■ Thiserrormayoccurifnbjmterminatedwhileabackupjobwasrunning.Examine\nthe unified logging files on the NetBackup server for nbjm (117) for more detail\non the error. All unified logging is written to /usr/openv/logs (UNIX) or\ninstall_path\\NetBackup\\logs (Windows).\n■ On UNIX clients, check for core files in the / directory.\n■ On UNIX clients, check the system log (/usr/adm/messages on Solaris) for\nsystem problems.\n■ This problem can sometimes be due to a corrupt binary.\nOn UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and\ntar binaries, which are located in /usr/openv/netbackup/bin on the client.\nReinstall them if they are not the same as in the client directory under\n/usr/openv/netbackup/client on the server.\nOn a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and\ntar32.exe files, which are located in the install_path\\NetBackup\\bin folder\non the client.\nReinstall the client if these files are as follows:\n■ Not the same size as on other Windows clients.\n■ Not at the same release level.\n■ Do not have the same NetBackup patches as other Windows clients.\n■ ReviewthefollowingwhenNetBackupisdeployedonaKubernetesdeployment:\n■ Check the number of pending pods. Post that to ensure that the issue\noccurred due to the node pool level max pods setting, and check if the\nworkflow runner or data mover pods are in pending state. Delete the node\npool and recreate the node pool with appropriate number to max pods using\nthe following formula:\n■ MAX pods per node = (RAM size * 2) + number of kube-system pods[10]\n+ No of nodes + 2\n■ Check the number of pending pods. Post that to ensure that there are sufficient\nnumberoffreeIPsareavailable.Theadministratorneedstoensurethatsufficient\nnumber of IPs are available."
    },
    "51": {
        "code": 51,
        "desc": "Timed out waiting for database information",
        "first_action": "Verify that the NetBackup Database Manager, bpdbm, is running.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the NetBackup Database Manager, bpdbm, is running.\n■ Verify that the file system that contains the NetBackup catalogs has enough\nspace.\n■ Create bpbrm and bpdbm debug log directories on the server and retry the\noperation.\n■ Look in the debug log files to find more information on the problem."
    },
    "52": {
        "code": 52,
        "desc": "Timed out waiting for media manager to mount volume",
        "first_action": "Verify that the requested volume is available and an appropriate drive is ready",
        "full_action": "Do the following, as appropriate:\n■ Verify that the requested volume is available and an appropriate drive is ready\nand in the UP state.\n■ If this error occurs during a read operation (restore, duplicate, verify), the drives\ncould be busy. Increase the timeout for the media mount that the NetBackup\nglobal attribute specifies, to allow more time to mount and position the media.\n■ Verify that the tape is not a cleaning tape that is configured as a regular volume.\n■ WhenanAutomatedCartridgeSystemcontrolstherobot,verifythattheACSLS\nsystem is up.\n■ If it is an initial installation, a procedure is available.\nSee\"Troubleshootingconfigurationproblems\"intheNetBackupTroubleshooting\nGuide.\n■ On Windows, check the Event Viewer Application log for the error messages\nthat indicate why the tape mount did not complete. On UNIX, check the system\nlog."
    },
    "53": {
        "code": 53,
        "desc": "Backup restore manager failed to read the file list",
        "first_action": "Create bpbrm debug log directories on the server.",
        "full_action": "Verify that the server software was installed correctly on\nall NetBackup servers. If that is not the problem, do the following:\n■ Create bpbrm debug log directories on the server.\n■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf\nfile. On a Windows NetBackup server, set the Global logging level option on\nthe Logging tab in the Master Server Properties dialog box.\nTo display this dialog box, refer to the following topic:\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\nIncreasetheunifiedlogginglevelsbyusingthevxlogcfgcommandasexplained\nin the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs for detailed\ntroubleshooting information."
    },
    "54": {
        "code": 54,
        "desc": "Timed out connecting to client",
        "first_action": "Perform the following procedure:",
        "full_action": "Do the following, as appropriate:\n■ Perform the following procedure:\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ OnUNIXclients,verifythatthe/usr/openv/netbackup/bin/bpcdbinaryexists\nand that it is the correct size.\n■ Check the /etc/inetd.conf file to make sure the bpcd path is correct in the\nfollowing entry:\nbpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd\n■ On the systems that include the following, make sure that the client name is in\nthe master’s /etc/hosts file: NetBackup master, media, and clients (with\nNetBackup database extension products installed on one or more clients).\n■ Completely uninstall the third-party software package on the client that causes\nthe failure. Or, contact the software manufacturer to investigate if other\nconfiguration options or workarounds are possible."
    },
    "55": {
        "code": 55,
        "desc": "Permission denied by client during rcmd",
        "first_action": "Add the server name to the /.rhosts file on the UNIX or",
        "full_action": "Add the server name to the /.rhosts file on the UNIX or\nLinux client."
    },
    "56": {
        "code": 56,
        "desc": "Client’s network is unreachable",
        "first_action": "Trytopingtheclientfromtheserver.ChecktheIPaddress",
        "full_action": "Trytopingtheclientfromtheserver.ChecktheIPaddress\nfor the client. If you still have problems, talk to your network administrator."
    },
    "57": {
        "code": 57,
        "desc": "Client connection refused",
        "first_action": "For Windows NetBackup servers:",
        "full_action": "Do the following, as appropriate:\n■ For Windows NetBackup servers:\n■ Make sure the NetBackup client software is installed.\n■ Verify that the bpcd and bprd port numbers in the\n%SystemRoot%\\system32\\drivers\\etc\\servicesfileontheservermatches\nthe setting on the client.\n■ Verify that the NetBackup Client Service Port number and NetBackup\nRequestServicePortnumberontheNetworktabintheNetBackupClient\nProperties dialog match the bpcd and bprd settings in the services file. To\ndisplay this dialog, start the Backup, Archive, and Restore interface on the\nserver and click NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Verify that the NetBackup client service is running.\n■ Use the following command to see if the master server returns correct\ninformation for the client:\ninstall_path\\VERITAS\\NetBackup\\bin\\bpclntcmd -pn\n■ On UNIX servers, do the following:\n■ Make sure the NetBackup client software is installed.\n■ Verify that the bpcd port number on the server (either NIS services map or\nin /etc/services) matches the number in the client’s services file.\n■ Additional help is available.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide."
    },
    "58": {
        "code": 58,
        "desc": "Can’t connect to client",
        "first_action": "Resolve network communication problems.",
        "full_action": "Resolve network communication problems.\nSee\"Resolvingnetworkcommunicationproblems\"intheNetBackupTroubleshooting\nGuide.\nWhen using Hadoop or HBase, verify that the application server port number is\nupdated correctly when using the tpconfig command."
    },
    "59": {
        "code": 59,
        "desc": "Access to the client was not allowed",
        "first_action": "If the server is a valid server, verify that it is in the server list on the client. If",
        "full_action": "Do the following, as appropriate:\n■ If the server is a valid server, verify that it is in the server list on the client. If\nnecessary add it as follows:\n■ On Windows clients: Add the server on the Server to use for backups and\nrestoresdrop-downintheSpecifyNetBackupMachinesandPolicyType\ndialogbox.Todisplaythisdialogbox,starttheBackup,Archive,andRestore\ninterfaceontheclient.ThenclickSpecifyNetBackupMachinesandPolicy\nType on the File menu.\n■ On UNIX clients: Add a SERVER entry in the bp.conf file.\nIf you change the server list on a UNIX or Linux master server, do the following\nfor the changes to take effect: Stop and then restart the NetBackup Request\nDaemon (bprd) and NetBackup Database Manager Daemon (bpdbm). On\nWindows, stop and restart the NetBackup Request Manager and NetBackup\nDatabase Manager services.\n■ On Windows clients, enable bpinetd debug logging as follows:\n■ Create a bpinetd debug log directory on the client.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Retry the backup and examine the resulting logs to determine the cause of\nthe failure.\n■ On all clients, enable bpcd debug logging as follows:\n■ Create a bpcd debug log directory on the client.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level as explained in the debug log\ntopics in Chapter 3.\n■ Retry the backup and examine the resulting logs to determine the cause of\nthe failure.\n■ Check the bpcd debug log to determine the server’s peer name and what\ncomparisons are made.\nThe bpcd process compares NetBackup server list entries to the peer name of\nthe server that tries the connection. It rejects the connection if the names are\ndifferent. If necessary, change the server list entry on the client to match the\npeer name.\n■ On Windows clients, check the following:\n■ Verify that NetBackup for Windows software was installed under a Windows\nadministrator account.\nIf NetBackup is under another type of account, reinstall it under an\nadministrator account. The installation completes successfully under a\nnon-administrator account except for the following: The NetBackup Client\nservice is not added to Windows and the NetBackup server cannot access\nthe client.\n■ Verify that the Windows TCP/IP service specifies the domain server that\nresolves names for the subnet that contains the NetBackup servers.\nUNIX, Linux, and Windows clients are frequently not on the same subnet\nand use different domain servers. When this condition exists, NetBackup\nserversandWindowsclientsmaybeabletopingoneanother,buttheserver\nstill cannot access the Windows client.\n■ The preceding items may not resolve this problem.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If NetBackup use multiple network interfaces with media servers, make sure\nthattheinterfacenamesappearintheclient’s/usr/openv/netbackup/bp.conf\nfile.\n■ For the Enterprise Vault Agent: See the Troubleshooting section of the\nNetBackup for Enterprise Vault Agent Administrator’s Guide.\n■ Be sure that all name resolution services (primary, load-balancing, and\nsecondary) are properly configured for consistent forward and reverse name\nresolution of NetBackup hosts.\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100029136"
    },
    "60": {
        "code": 60,
        "desc": "Client cannot read the mount table NetBackup status codes 144 NetBackup status codes",
        "first_action": "Run a df to see if the system can read the mount table.",
        "full_action": "Do the following, as appropriate:\n■ Run a df to see if the system can read the mount table.\n■ On an SCO system, code 60 can occur because the mount-point path name\nexceeds 31 characters (the maximum number on an SCOsystem). The bpbkar\ndebug log on the client shows a message similar to the following:\nbpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406\nTo eliminate these errors for future backups, create a mount point with a shorter\nname and symbolically link the long name to the short name.\n■ For detailed troubleshooting information, create a bpbkar debug log directory.\nThen retry the operation and check the resulting log."
    },
    "61": {
        "code": 61,
        "desc": "The vnetd proxy encountered an error",
        "first_action": "Verbose or debug output from the command.",
        "full_action": "Examineoneofthefollowingfora76xxcodethatprecedes\nthe status code 61, and then look up the explanation for that 76xx code:\n■ Verbose or debug output from the command.\n■ The Detailed Status of the Job Details in the NetBackup Administration\nConsole.\n■ The log file for the command or process that reported the status 61.\nFor more information, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945"
    },
    "63": {
        "code": 63,
        "desc": "Process was killed by a signal",
        "first_action": "Theusualcauseforthiserroristhatsomeoneintentionally",
        "full_action": "Theusualcauseforthiserroristhatsomeoneintentionally\nterminated a backup."
    },
    "64": {
        "code": 64,
        "desc": "Timed out waiting for the client backup to start",
        "first_action": "On all clients, enable bpcd debug logging as follows:",
        "full_action": "Do the following, as appropriate:\n■ On all clients, enable bpcd debug logging as follows:\n■ Create a bpcd debug log directory on the client.\n■ On a UNIX or Linux client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a UNIX, Linux, or Windows client, create the bpbkar debug log directory on\nthe client.\n■ On Windows clients, verify that the NetBackup Client service is running.\n■ On a UNIX or Linux client, use the ps command to check for a client process\nthat uses too much CPU time.\n■ Retry the backup and examine the debug logs for clues on the cause of the\nfailure."
    },
    "65": {
        "code": 65,
        "desc": "Clienttimedoutwaitingforthecontinuemessagefromthemediamanager",
        "first_action": "Create a bptm debug log directory on the server.",
        "full_action": "Verify that the requested volume is available and the\nrequired device is in an UP state.\n■ Create a bptm debug log directory on the server.\n■ On a UNIX or Linux NetBackup server, add the VERBOSE option to the bp.conf\nfile. On a Windows NetBackup server, set the Verbose logging level option\non the Logging tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ Retry the operation and check the bptm debug log file for information on the\ndrive, robot, and tape that causes the timeout.\n■ On a Windows NetBackup server (master or media): check the Event Viewer\nApplication log for the error messages that indicate why the tape mount did not\ncomplete."
    },
    "66": {
        "code": 66,
        "desc": "Client backup failed to receive the CONTINUE BACKUP message",
        "first_action": "Verify that the server did not crash.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ On UNIX, Linux, and Windows clients, enable bpbkar debug logging.\n■ Create a bpbkar debug log directory.\n■ On a UNIX or Linux client, add the VERBOSE option to the bp.conf file. On a\nWindowsclient,setVerboseontheTroubleShootingtabintheNetBackup\nClient Properties dialog box. To display this dialog box, start the Backup,\nArchive, and Restore interface on the client. Then select NetBackup Client\nProperties from the File menu.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Use the vxlogcfg command as described in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs."
    },
    "67": {
        "code": 67,
        "desc": "Client backup failed to read the file list",
        "first_action": "Verify that the server did not crash.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ Set up debug logging.\n■ On the server, create a bpbrm debug log directory.\n■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs."
    },
    "68": {
        "code": 68,
        "desc": "Client timed out waiting for the file list",
        "first_action": "Verify that the server did not crash.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the server did not crash.\n■ Set up debug logging.\n■ On the server, create a bpbrm debug log directory.\n■ On UNIX, Linux, and Windows clients, create a bpbkar debug log directory.\n■ On other PC clients, create a debug log directory for bpcd.\nIncrease the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs."
    },
    "69": {
        "code": 69,
        "desc": "Invalid filelist specification",
        "first_action": "VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in",
        "full_action": "Do the following, as appropriate:\n■ VMware Intelligent Policy: Check for duplication of the VM_name of the VMs in\nthe policy.\n■ Policy file list problem: Check the policy file list. If wildcards are used, verify that\nthe bracket characters ([ and ]) in the list match. If the file list contains UNC\n(UniversalNamingConvention)names,ensurethattheyareproperlyformatted.\nThis error can occur if nbjm is running and a SharePoint job rediscovery returns\na 0 or 1 and the policy file list is empty. Examine the nbjm unified log (originator\nID 117) for more detail on the cause of the error.\n■ Enterprise Vault Agent: For more information, please see the Troubleshooting\nsection of the NetBackup for Enterprise Vault Agent Administrator's Guide.\n■ NetBackup Snapshot Client: Remove the ALL_LOCAL_DRIVES entry from the file\nlist.\n■ For more information on the supported operating systems for backup hosts,\nrefer to the NetBackup Web UI RHV Administrator's Guide.\n■ For the errors that are related to Hypervisor policy and Nutanix AHV, refer to\nthe Nutanix AHV Administrator’s Guide."
    },
    "70": {
        "code": 70,
        "desc": "An entry in the filelist expanded to too many characters NetBackup status codes 149 NetBackup status codes",
        "first_action": "Change the wildcards in the file list to specify fewer files.",
        "full_action": "Change the wildcards in the file list to specify fewer files."
    },
    "71": {
        "code": 71,
        "desc": "None of the files in the file list exist",
        "first_action": "Verify that the correct file list is specified for this client.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the correct file list is specified for this client.\n■ On Windows clients, verify that the account used to start the NetBackup Client\nservice has read access to the files.\nIf you back up a network drive or a UNC (Universal Naming Convention) path,\ndo the following: Use the Services application in the Windows Control Panel to\nverifythattheNetBackupClientservicedoesnotstartunderthesystemaccount.\nThe System Account cannot access network drives.\nTo back up network drives or UNC paths: Change the NetBackup Client service\nstartup to log in as a user that has permission to access network drives.\n■ Check the All Log Entries report for clues.\n■ To set up debug logging, do one of the following:\n■ On UNIX, Linux, and Windows clients, create a debug log directory for\nbpbkar.\n■ On other PC clients, create a debug log directory for bpcd.\n■ Increase the amount of information that appears in the logs.\nSee\"Changingthelogginglevel on Windowsclients\"in theNetBackupLogging\nReference Guide.\n■ Retry the operation and check the resulting debug logs.\n■ For an NDMP policy type, verify that the credentials of the NDMP hosts have\nbeen added. If not, add them."
    },
    "72": {
        "code": 72,
        "desc": "The client type is incorrect in the configuration database",
        "first_action": "Verifythatthepolicytypeattributeforthepolicyiscorrect.",
        "full_action": "Verifythatthepolicytypeattributeforthepolicyiscorrect."
    },
    "73": {
        "code": 73,
        "desc": "Bpstart_notify failed",
        "first_action": "Check the bpstart_notify script on the client to see if",
        "full_action": "Check the bpstart_notify script on the client to see if\nit performs as expected."
    },
    "74": {
        "code": 74,
        "desc": "Client timed out waiting for bpstart_notify to complete",
        "first_action": "Try to speed up the bpstart_notify script or set the",
        "full_action": "Try to speed up the bpstart_notify script or set the\nBPSTART_TIMEOUT on the server to a value that is larger than the default. Set\nBPSTART_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server.\nOn a Windows NetBackup server, use Host Properties to set Backup Start Notify\nTimeout.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide."
    },
    "75": {
        "code": 75,
        "desc": "Client timed out waiting for bpend_notify to complete",
        "first_action": "Try to speed up the bpend_notify script or set",
        "full_action": "Try to speed up the bpend_notify script or set\nBPEND_TIMEOUT on the server to a value that is larger than the default. Set\nBPEND_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On\na Windows NetBackup server, use Host Properties to set Backup End Notify\nTimeout."
    },
    "76": {
        "code": 76,
        "desc": "Client timed out reading file",
        "first_action": "Make sure that the process that is to produce the data on",
        "full_action": "Make sure that the process that is to produce the data on\nthe named FIFO is started correctly. Add an entry to the\n/usr/openv/netbackup/bp.conffileontheservertosetCLIENT_READ_TIMEOUT\nto a larger value than the default."
    },
    "77": {
        "code": 77,
        "desc": "Execution of the specified system command returned a nonzero status",
        "first_action": "Verify that the command is specified correctly.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the command is specified correctly.\n■ For NetBackup Snapshot Client only, do the following:\nThe policy file list may contain the files that do not reside within a file system\nthat was designated as the snapshot source. To apply a snapshot method to\nthe backup of individual files, the snapshot source must be a file system. (It\ncannot be a raw partition or Volume Manager volume.) The files in the policy\nfile list must reside within that file system.\n■ Run the command manually to see if the wanted result is produced.\n■ For detailed troubleshooting information, set up debug logging as follows:\n■ On UNIX, Linux, and Windows clients, create a debug log directory for\nbpbkar.\n■ On other PC clients, create a debug log directory for bpcd.\n■ Increase the amount of information that appears in the logs.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Retry the operation and check the resulting debug log."
    },
    "78": {
        "code": 78,
        "desc": "Afs/dfs command failed",
        "first_action": "Check the NetBackup Problems Report for additional information on why the",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems Report for additional information on why the\ncommand failed.\n■ The bpbkar debug log shows the command that was run. Create a debug log\ndirectory for bpbkar. Retry the operation and retry the resulting debug log.\n■ Try running the vos command manually to duplicate the problem."
    },
    "79": {
        "code": 79,
        "desc": "Unsupported image format for the requested database query",
        "first_action": "Ensure that none of the images were encrypted.",
        "full_action": "Ensure that none of the images were encrypted."
    },
    "80": {
        "code": 80,
        "desc": "Media Manager device daemon (ltid) is not active",
        "first_action": "OnWindows,usetheActivityMonitorortheServicesapplicationintheWindows",
        "full_action": "Do the following, as appropriate:\n■ OnWindows,usetheActivityMonitorortheServicesapplicationintheWindows\nControl Panel to see if the NetBackup Device Manager service is running. If it\nis not running, start it. To enable verbose logging, place VERBOSE on a line by\nitself in the install_path\\Volmgr\\vm.conf file before you start the service.\n■ On UNIX, use vmps to see if ltid is running and if necessary start ltid in\nverbose mode with the following command:\n/usr/openv/volmgr/bin/ltid -v\nOr, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the\nvm.conf file if necessary.\n■ On UNIX, check the system logs to verify that ltid starts.\nNote: On UNIX systems, ltid, and on Windows systems, the NetBackup Device\nManager service, is used only if devices are attached to the system."
    },
    "81": {
        "code": 81,
        "desc": "Media Manager volume daemon (vmd) is not active",
        "first_action": "On UNIX, verify that the Media Manager device daemon (ltid) and the",
        "full_action": "Do the following, as appropriate:\n■ On UNIX, verify that the Media Manager device daemon (ltid) and the\nNetBackup Volume Manager (vmd) are running. Start them if necessary.\n■ On Windows, verify that both the NetBackup Device Manager service and the\nNetBackup Volume Manager service are running. Start them if necessary.\nNote: ltid or the NetBackup Device Manager service is used only if devices are\nattached to the system."
    },
    "82": {
        "code": 82,
        "desc": "Media manager killed by signal",
        "first_action": "This error should not occur in normal operation. If you",
        "full_action": "This error should not occur in normal operation. If you\nwant to terminate an active backup, use the NetBackup Activity Monitor.\nWhen you back up a DomainOS client, this error occurs after the server has not\nreceived anything on the socket for at least 300 seconds. It causes a client read\ntimeout and breaks the connection. The bpbkar debug log has an entry similar to\nthe following:\n13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET\nConnection reset by peer (UNIX/errno status)\nTo resolve the problem, increase the CLIENT_READ_TIMEOUT value. In this\ninstance, set the value to 900."
    },
    "83": {
        "code": 83,
        "desc": "Media open error",
        "first_action": "NetBackup Problems report",
        "full_action": "For additional information, check the following:\n■ NetBackup Problems report\n■ Event Viewer Application log (Windows)\n■ System log (UNIX)\n■ Typically, this status code indicates a drive configuration problem that allows\nmorethanoneprocessatatimetoopenthedevice.OnUNIX,theproblemmay\nbe due one or more of the following:\n■ Two (or more) devices were configured that are the same physical device\n(for different densities perhaps). Verify that none of the /dev files that were\nused for these devices have the same major or minor numbers.\n■ Links exist in the file system that allows users access to the drives.\n■ The configuration for the drives was modified (in the administrator interface\norvm.conf)andtheMediaManagerdevicedaemon,ltid,wasnotrestarted.\nVerify the configuration and then start ltid.\nOn Windows, the problem may be that the Media and Device Management\ndevice configuration was modified but the NetBackup Device Manager service\nwas not restarted. Verify the configuration and restart the NetBackup Device\nManager service.\n■ On Windows, make sure that the tapes are not write protected.\n■ For detailed troubleshooting information:\n■ Create a debug log directory for bpdm (if the device is disk) or bptm (if the\ndevice is tape).\n■ On UNIX, restartltid in the verbose mode by running the following:\n/usr/openv/volmgr/bin/ltid -v\nOr, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create\nthe vm.conf file if necessary.\n■ On Windows, to enable verbose logging, add VERBOSE on a line by itself in\nthe install_path\\Volmgr\\vm.conf file. Then, stop and restart the\nNetBackup Device Manager service.\n■ Retry the operation and check the resulting debug log files.\n■ On Windows systems, look at the\ninstall_path\\VERITAS\\NetBackup\\db\\media\\errors log for a drive that\nfrequently produces errors.\nOn UNIX systems, look at the /usr/openv/netbackup/db/media/errors\nlog(whichisalsoincludedinthe/usr/openv/netbackup/bin/support/nbsu\nscript output) for a drive that frequently produces errors."
    },
    "84": {
        "code": 84,
        "desc": "Media write error",
        "first_action": "For NetBackup Snapshot Client only:",
        "full_action": "Do the following, as appropriate:\n■ For NetBackup Snapshot Client only:\nIf the following message appears in the /usr/openv/netbackup/bptm log, and\nthe values for key, asc, and ascq are all zero (0x0) as shown in this example\nmessage:\ntape error occurred on extended copy command, key = 0x0, asc =\n0x0, ascq = 0x\nNetBackup Snapshot Client probably does not support your host-bus adapter\nanditsdriver.Thehost-busadaptersthataresupportedinthereleasearelisted\nin the NetBackup Release Notes.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ If NetBackup writes backups to a disk file, verify the following: The fragment\nsize that is configured for the disk storage unit is not greater than the maximum\nfile size that the operating system specifies.\n■ On Windows, make sure that the tapes are not write protected.\n■ If bpbackupdb was used to back up the NetBackup catalog to a disk path on a\nUNIX or Linux system, the image you try to write may be greater than the\nmaximum file size that is specified by that operating system. Tape files do not\nhave this limit. You may have to back up the catalog to tape.\n■ If the media is tape, check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (refer to the tpclean\ncommand for robotic drives).\n■ The wrong media type. Verify that the media matches the drive type you\nuse.\n■ Defective media. If it is defective, use the bpmedia command to set the\nvolume to the FROZEN state so it is not used for future backups.\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX the drive may be configured for fixed mode when it\nmust be variable mode.\nSee the NetBackup Device Configuration Guide for more information.\nThis configuration often results in the media being frozen with the message\ntoo many data blocks written, check tape and drive block size\nconfiguration\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ If you receive this error message when a GLACIER or LIFECYCLE backup job\nfails,theerrorisrelatedtotheAmazonlifecyclepolicyandoccursinthefollowing\nsituations:\n■ The Amazon lifecycle policy that NetBackup uses cannot be applied. The\nAmazon GLACIER or LIFECYCLE storage class is not supported for the\nregion to which the bucket belongs. Recreate the disk pool with the bucket\nin the supported region.\n■ A different Amazon lifecycle policy other than what NetBackup uses already\nexists. Remove the policy that is not used by NetBackup and rerun the job.\n■ TheerroroccurredwhilecreatingtheAmazonlifecyclepolicythatNetBackup\nuses to back up data to Amazon. Check the bptm logs for more details."
    },
    "85": {
        "code": 85,
        "desc": "Media read error",
        "first_action": "NetBackup Problems report to determine the device or media that caused the",
        "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX, the drive may be configured for fixed mode when it\nmust be variable mode. More information is available.\nSee the NetBackup Device Configuration Guide.\n■ Defective media. In this case, you may not be able to recover all the data\non the media. Use the bpmedia command to set the volume to the FROZEN\nstate so it is not used for future backups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ The wrong media type. Verify that the media matches the drive type you\nuse."
    },
    "86": {
        "code": 86,
        "desc": "Media position error",
        "first_action": "NetBackup Problems report to determine the device or media that caused the",
        "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Incorrect drive configuration. Verify the Media and Device Management and\nsystem configuration for the drive.\nFor example, on UNIX, the drive may be configured for fixed mode when it\nmust be variable mode.\nSee the NetBackup Device Configuration Guide for more information.\n■ Defective media. In this case, some data may be lost. Use the bpmedia\ncommand to set the volume to the FROZEN state so it is not used for future\nbackups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ The wrong media type. Verify that the media matches the drive type you\nuse."
    },
    "87": {
        "code": 87,
        "desc": "Media close error NetBackup status codes 159 NetBackup status codes",
        "first_action": "NetBackup Problems report to determine the device or media that caused the",
        "full_action": "For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused the\nerror\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ Check for the following:\n■ A defective or a dirty drive. Clean it or have it repaired (see the tpclean\ncommand for cleaning).\n■ Defective media. In this case, some data may be lost. Use the bpmedia\ncommand to set the volume to the FROZEN state so it is not used for future\nbackups.\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\nWhen Amazon AWS is used as cloud storage:\n■ Verify that you have SSL enabled for communication."
    },
    "88": {
        "code": 88,
        "desc": "OpenStorage WORM lock error.",
        "first_action": "Look at the OpenStorage storage server and ensure that",
        "full_action": "Look at the OpenStorage storage server and ensure that\nconfiguration of the storage device is consistent with NetBackup. Review the bptm\nand the bpdm logs for more detailed messages and OST error codes for more\ninformation about these failures."
    },
    "89": {
        "code": 89,
        "desc": "Problems encountered during setup of shared memory NetBackup status codes 160 NetBackup status codes",
        "first_action": "ForSolaris9,thedefaultshminfo_shmmaxvalueis8megabytes.Youcanplace",
        "full_action": "Checkforasharedmemoryproblem.Thiserrorcanoccur\nif the system cannot allocate enough shared memory. It usually occurs with\nmultiplexing, which increases the amount of shared memory that is required for the\noperation. An entry similar to the following may be seen in a NetBackup log or\nreport:\nsystem cannot allocate enough shared memory\nIf you see this type of message, refer to your platform vendor documentation for\ninstructions on how to increase shared memory on your system.\nFor older levels of Solaris, you may need to change one or more default System V\nSharedMemorysettingstopreventjobsfailingwiththememoryallocationmessage,\nas follows:\n■ ForSolaris9,thedefaultshminfo_shmmaxvalueis8megabytes.Youcanplace\nthe following line in your /etc/system file to increase this setting. A value of 32\nmegabytes has been used in this example. Your system may require a greater\nvalue under some circumstances such as a high value for the NetBackup\nmultiplexingparameter.AccordingtoSunMicrosystemsdocumentation,setting\nthisparametertoitsmaximumpossiblevaluehasnosideeffects.(Thisparameter\nis not applicable to Solaris 10).\nset shmsys:shminfo_shmmax=33554432\n■ For Solaris 9, the default shminfo_shmmni value is 100. You can place the\nfollowingline in your /etc/system file to increase this setting.The defaultvalue\nis usually sufficient for NetBackup. In some circumstances, such as installing a\nNetBackup media server on a large database server, this setting may need to\nbe increased. A value of 220 has been used in this example. (This parameter\nis not applicable to Solaris 10).\nset shmsys:shminfo_shmmni=220\nNote: If you modify any of these values in the /etc/system file, you must restart\nthe system with boot -r for the new settings to take effect.\nRefertoyourvendordocumentationfordetailedinstructionsonhowtomodifythese\nvalues. Note that these shminfo parameters are not applicable to Solaris 10."
    },
    "90": {
        "code": 90,
        "desc": "Media manager received no data for backup image",
        "first_action": "Check the All Log Entries report.",
        "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries report.\n■ For detailed debug information, create bpdm or bptm debug log directories on\nthe server. If the client is Windows, also create a bpbkar debug log directory\non the client. Retry the operation and check the resulting debug logs.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or media that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application log (Windows)\n■ Verify the Media and Device Management and system configuration for the\ndrive.\nFor example, on UNIX, the drive may not be set for variable mode in a case\nwhere NetBackup requires that mode.\nCheck the NetBackup Device Configuration Guide for drive configuration\ninformation.\n■ Verify that the Media and Device Management configuration for the backup\ndevice matches what is specified for the storage unit in the NetBackup policy.\n■ Verify that you use the correct media in the drive.\n■ For detailed debug information, create a bpdm or bptm debug log directory\n(whichever applies) on the server. If the client is Windows, also create a bpbkar\ndebug log directory on the client. Retry the operation and check the resulting\ndebug logs.\n■ If the error occurred during duplication or a Vault session that uses an Alternate\nRead Server to perform duplication, verify that the Alternate Read Server has\naccess to the source media."
    },
    "91": {
        "code": 91,
        "desc": "Fatal NB media database error",
        "first_action": "Check the All Log Entries report for more information.",
        "full_action": "Do the following, as appropriate:\n■ Check the All Log Entries report for more information.\n■ Check the NetBackup Media Lists report to see if the catalog is intact. If the\ncatalogisnotintact,youmaywanttoreloaditfromthelatestNetBackupcatalog\nbackup volume.\n■ Verify that the disk partition on which the catalog resides has enough space.\n■ If these actions do not explain the problem, check the NetBackup Problems\nreport.\n■ For detailed troubleshooting information, create a bptm debug log directory on\nthe server and retry the operation. Check the resulting debug log file.\n■ Contactcustomersupportandsendappropriateproblemanddebuglogsections."
    },
    "92": {
        "code": 92,
        "desc": "Media manager detected image that was not in tar format",
        "first_action": "Perform a bpverify of the affected image to determine if it is written correctly.",
        "full_action": "Do the following, as appropriate:\n■ Perform a bpverify of the affected image to determine if it is written correctly.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Verify the Media and Device Management and system configuration for the\ndrive.\nForexample,ifyoudonotconfigurethedriveforvariable-modeblocksizewrites\nonsomeUNIXsystems,thebackupimagesthatwritetothemediaproducethis\nerror when you attempt to restore the image.\nThe following sequence of events occurs:\n■ Backup succeeds.\n■ Verify succeeds.\n■ Restore fails.\nThe bptm debug log shows an error similar to the following:\n00:58:54 [2304] <16> write_data: write of 32768 bytes indicated\nonly 29696 bytes were written, errno = 0\nIn this case, configure the drive for variable-mode block sizes and suspend the\nmedia that writes on that device.\nSee the NetBackup Device Configuration Guide.\nThe images that were written to those media may be restorable (platform\ndependent),butsinglefilerestoresarealmostguaranteedtofail.Youcanexpire\nthese media and regenerate the backups. Or you can attempt to duplicate the\nimages on these media to another device and then expire the original copy.\n■ Thiserrorhasoccurredonre-labeledandvalue-added8-mmtapedriveswhere\nthe drive’s micro code incorrectly processes a forward space record SCSI\ncommand.\n■ If the problem is not one of those discussed, create a debug log directory for\neither bpdm or bptm and retry the operation. Check the resulting debug log file."
    },
    "93": {
        "code": 93,
        "desc": "Media manager found wrong tape in drive",
        "first_action": "Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompare",
        "full_action": "Do the following, as appropriate:\n■ Ifthevolumeisinarobotandtherobotsupportsbarcodes,performaCompare\nContents with Volume Configuration robot inventory (on Windows) or\nCompare robot contents with volume configuration robot inventory (UNIX).\nThe resulting report shows the media ID that was found and validates its slot\nnumberwithwhatisinthevolumeconfiguration.Then,eitherchangethephysical\nlocation in the robot or change the volume configuration to show the correct\nslot.\n■ If the volume was mounted on a nonrobotic drive, verify that the correct volume\nwas mounted and assigned."
    },
    "94": {
        "code": 94,
        "desc": "Cannot position to correct image",
        "first_action": "Try the restore on another drive if possible.",
        "full_action": "Do the following, as appropriate:\n■ Try the restore on another drive if possible.\n■ For additional information, check the following:\n■ NetBackup Problems report to determine the device or volume that caused\nthe error\n■ System and error logs for the system (UNIX)\n■ Event Viewer Application and System logs (Windows)\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log files."
    },
    "95": {
        "code": 95,
        "desc": "Media ID is not assigned to this host in the EMM database",
        "first_action": "Run a NetBackup Media List report to determine the valid",
        "full_action": "Run a NetBackup Media List report to determine the valid\nmedia IDs and their assigned hosts. Then, retry the command with a valid media\nID and assigned host."
    },
    "96": {
        "code": 96,
        "desc": "Unabletoallocatenewmediaforbackup,storageunithasnoneavailable",
        "first_action": "If the storage unit is a robot with empty slots, add more volumes (remember to",
        "full_action": "Check the NetBackup Problems report to determine the\nstorage unit that is out of media.\n■ If the storage unit is a robot with empty slots, add more volumes (remember to\nspecify the correct volume pool).\n■ If there are no empty slots, move some media to nonrobotic and then add\nnew volumes.\n■ If you have difficulty keeping track of your available volumes, try the\navailable_media script:\nOn UNIX, this script is in:\n/usr/openv/netbackup/bin/goodies/available_media\nOn Windows, the script is in:\ninstall_path\\NetBackup\\bin\\goodies\\available_media.cm\nd\nThis script lists all volumes in the volume configuration, and augments that\nlist with information on the volumes currently assigned to NetBackup.\n■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup\nneeds a new tape and none are available in the current volume pool, it does\nthe following: Moves a tape from the scratch pool into the volume pool that the\nbackup uses.\n■ If the storage unit and volume pool appear to have media, verify the following:\n■ Volume is not FROZEN or SUSPENDED.\nCheck for this condition by using the NetBackup Media List report. If the\nvolume is frozen or suspended, use the bpmedia command to unfreeze or\nunsuspend it (if that is wanted).\nSee \"Frozen media troubleshooting considerations\" in the NetBackup\nTroubleshooting Guide.\n■ Volume has not expired or exceeded its maximum number of mounts.\n■ The EMM database host name for the device is correct.\nIf you change the EMM database host name, stop and restart the following:\nThe Media Manager device daemon, ltid, (if the server is UNIX or Linux)\nor the NetBackup Device Manager service (if the server is a Windows\nsystem).\n■ The correct host is specified for the storage unit in the NetBackup\nconfiguration.\nThe host connection should be the server (master or media) with drives\nconnected to it.\n■ The Media and Device Management volume configuration has media in the\ncorrect volume pool. Unassigned or active media is available at the required\nretention level.\nUse the NetBackup Media List report to show the retention levels, volume\npools, and status (active and so on) for all volumes. Use the NetBackup\nMedia Summary report to check for active volumes at the correct retention\nlevels.\n■ The NetBackup bptm process is rejected when it requests media from the vmd\nprocess (UNIX) or the NetBackup Volume Manager service (Windows). The\ncause of this problem is that the process or service cannot determine the name\nof the host that makes the request.\nThis error can be due to an incorrect network configuration that involves the\nfollowing:\n■ Multiple network interfaces\n■ /etc/resolv.conf on those UNIX or Linux systems that use it\n■ Running DNS with reverse addressing not configured\n■ Create bptm and vmd debug log directories and retry the operation.\n■ Examine the bptm debug log to verify that bptm connects to the correct system.\nIf an error is logged, examine the vmd log.\nOn UNIX, the vmd log is:\n/usr/openv/volmgr/debug/daemon/log.xxxxxx\nOn Windows, the vmd log is:\ninstall_path\\Volmgr\\debug\\daemon\\xxxxxx.log\n■ If this storage unit is new and this attempt to use it is the first, stop and restart\nNetBackup on the master server.\nNote: The mds unified logging files (OID 143) usually show the NetBackup\nmedia selection process.\nMoretroubleshootinginformationinawizardformatisavailableforthisstatuscode."
    },
    "97": {
        "code": 97,
        "desc": "Requested media ID is in use, cannot process request",
        "first_action": "Retry the command when the volume is not in use. Use",
        "full_action": "Retry the command when the volume is not in use. Use\nthe Device Monitor to determine if the volume is in use."
    },
    "98": {
        "code": 98,
        "desc": "Error requesting media (tpreq)",
        "first_action": "Check the NetBackup Problems report to determine the reason for the failure.",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report to determine the reason for the failure.\nThe most common cause is that the NetBackup Device Manager service (on\nWindows)ortheMediaManagerdevicedaemon(ltid)(onUNIX)isnotrunning.\nStart it if necessary.\n■ If you duplicate backups or use Vault to duplicate backups, this error could\nindicate the following: The Alternate Read Server does not have access to the\ntape where the original backup resides."
    },
    "99": {
        "code": 99,
        "desc": "NDMP backup failure NetBackup status codes 168 NetBackup status codes",
        "first_action": "Check the NetBackup All Log Entries report for more information.",
        "full_action": "Do the following:\n■ Check the NetBackup All Log Entries report for more information.\n■ Try the following commands from another master server or media server:\n# tpautoconf -verify ndmp_filer\n# tpautoconf -probe ndmp_host\nOn the filer, verify that the NDMP service is running. The verification process\ndepends on the filer.\nFor NetApp, run ndmpd status to verify that the NDMP daemon is running. If\nnot, execute ndmpd on and re-run ndmpd status to verify.\n■ Change the NDMP wildcard to specify path names only. You cannot use a\nwildcardcharacterthatalsomatchesafilename.Forexample,anNDMPbackup\nselection is /vol/vol_archive_01/autoit*. This specification matches path\nname /vol/vol_archive_01/autoit_01/, bit it also matches file\nname/vol/vol_archive_01/autoit-v1-setup.exe."
    },
    "100": {
        "code": 100,
        "desc": "System error occurred while processing user command",
        "first_action": "Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as",
        "full_action": "Do the following, as appropriate:\n■ Enable debug logging for bparchive, bpbackup, bplist, or bprestore (as\nappropriate) by creating debug log directories for them.\nOn UNIX, if a nonroot user has problems, verify that the directory that was\ncreated has mode 666. Look for and correct any reported errors.\n■ Retry the operation and check the resulting logs.\nIf the logs do not reveal the problem, use the command-line version of the\ncommand and correct any problems that are reported on stderr."
    },
    "101": {
        "code": 101,
        "desc": "Failed opening mail pipe",
        "first_action": "Makesurethatmailisconfiguredontheclient.Fordetailed",
        "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting information, create a bpcd debug log directory and retry the\noperation. Check the resulting bpcd debug log."
    },
    "102": {
        "code": 102,
        "desc": "Failed closing mail pipe",
        "first_action": "Makesurethatmailisconfiguredontheclient.Fordetailed",
        "full_action": "Makesurethatmailisconfiguredontheclient.Fordetailed\ntroubleshooting information, create a bpcd debug log directory and retry the\noperation. Check the resulting bpcd debug log."
    },
    "103": {
        "code": 103,
        "desc": "Error occurred during initialization, check configuration file",
        "first_action": "Create the 3pc.conf file manually before running the first",
        "full_action": "Create the 3pc.conf file manually before running the first\nmultistreamdatamoverbackup.Usethefollowingcommandtocreatethe3pc.conf\nfile:\n# bptpcinfo -a\nThe 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf.\nMore information is available on the 3pc.conf file and how to create it.\nSee Configuring NetBackup for off-host data mover backups in the NetBackup\nSnapshot Client Configuration Guide."
    },
    "104": {
        "code": 104,
        "desc": "Invalid file pathname",
        "first_action": "None",
        "full_action": "None"
    },
    "105": {
        "code": 105,
        "desc": "File pathname exceeds the maximum length allowed",
        "first_action": "Shorten the current working directory path length.",
        "full_action": "Shorten the current working directory path length."
    },
    "106": {
        "code": 106,
        "desc": "Invalid file pathname found, cannot process request",
        "first_action": "Verify that the full path names are used and that they do not exceed the",
        "full_action": "Do one or more of the following:\n■ Verify that the full path names are used and that they do not exceed the\nmaximumpathlengthforthesystem.(OnUNIX,theystartwithaslashcharacter\n[ / ].)\n■ Verify that the files exist and that the permissions allow NetBackup to access\nthem.\n■ Some NDMP servers do not support directory-level expansion. Some NDMP\nfiler vendors do not have the APIs that are used to support wildcard characters\nlower than the volume level. For example, /fs1/dir* is not a supported backup\nselection specification on EMC filers."
    },
    "108": {
        "code": 108,
        "desc": "Action succeeded but auditing failed",
        "first_action": "Ensure that the nbaudit daemon (NetBackup Audit Manager) is running.",
        "full_action": "Do the following:\n■ Ensure that the nbaudit daemon (NetBackup Audit Manager) is running.\n■ Examine the logs responsible for the primary action and the nbaudit logs for\nmore details on the cause of the error. For example, check the bpdbm logs for\npolicy creation."
    },
    "109": {
        "code": 109,
        "desc": "Invalid date specified",
        "first_action": "Iftheerroroccurredonacommandline,examinethestandarderroroutputfrom",
        "full_action": "Do the following, as appropriate:\n■ Iftheerroroccurredonacommandline,examinethestandarderroroutputfrom\nthe command for an explanatory message.\n■ Refertotheformatforthedateoptionsintheusagestatementforthecommand.\nLook up the locale of the master server. Compare the date format of that locale\nwith the date format on the usage statement for the command.\n■ Check the NetBackup Problems report for clues.\n■ If the error appears in a Java interface, enable the debug print manager in the\nJava startup file. Retry and compare the parameters that are logged in the Java\nlog with the parameters listed in the command’s usage statement.\n■ If these actions do not reveal the problem, create a debug log directory for the\nprocess that returned this status code. Then retry the operation and check the\nresulting debug log.\n■ If the error appears in the web UI while performing a Microsoft SQL Server\nrestore, review the date provided. The date must be in ISO 8601 format."
    },
    "110": {
        "code": 110,
        "desc": "Cannot find the NetBackup configuration information",
        "first_action": "On Windows, reinstall NetBackup software on the client.",
        "full_action": "On Windows, reinstall NetBackup software on the client.\nOn UNIX, create a /usr/openv/netbackup/bp.conf file with at least the following\nlines:\nSERVER = server_name\nCLIENT_NAME = client_name"
    },
    "111": {
        "code": 111,
        "desc": "No entry was found in the server list",
        "first_action": "On a UNIX client, add the following line to the top of the",
        "full_action": "Do the following, as appropriate:\n■ On a UNIX client, add the following line to the top of the\n/usr/openv/netbackup/bp.conf file:\nSERVER = server_name\n■ On a Microsoft Windows client, add the server name on the Server to use for\nbackups and restores drop-down in the Specify NetBackup Machines and\nPolicy Type dialog box. To display this dialog box, start the Backup, Archive,\nand Restore interface on the client. Then click Specify NetBackup Machines\nand Policy Type on the File menu."
    },
    "112": {
        "code": 112,
        "desc": "Undefined error or there are no files specified in the policy backup selection.",
        "first_action": "Specify at least one file to be restored.",
        "full_action": "Do the following, as appropriate:\n■ Specify at least one file to be restored.\n■ This status code may occur if nbjm is running and a stream discovery fails to\nfind all stream files. Examine the nbjm unified log (originator ID 117) for more\ndetails on the cause of the error.\n■ Ensure that the correct backup selections are specified in the policy and they\nare in the correct format.\nThe supported backup selection are:\n■ For subscription: /Subscription IDif Subscription ID is\n1950a258-227b-4e31-a9cf-717495945fc2thenspecifythebackupselection\nas - / 1950a258-227b-4e31-a9cf-717495945fc2\n■ Forresourcegroup:/Subscription ID/Resource Groupif Subscription\nID is 1950a258-227b-4e31-a9cf-717495945fc2 and Resource Group\nname is TestRG, specify the backup selection as - /\n1950a258-227b-4e31-a9cf-717495945fc2/TestRG\n■ For VM Name: /Subscription ID/Resoutrce Group/VM Nameif\nSubscription ID is 1950a258-227b-4e31-a9cf-717495945fc2,Resource\nGroup name is TestRG, and the VM name is MyVM, specify the backup\nselection as - / 1950a258-227b-4e31-a9cf-717495945fc2/TestRG/MyVM\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Verify that the following setting is commented out from the sudoers list on\nCassandra nodes:\n#Defaults:!requiretty"
    },
    "114": {
        "code": 114,
        "desc": "Unimplemented error code",
        "first_action": "Examinethenbjmunifiedlog(originatorID117)fordetailed",
        "full_action": "Examinethenbjmunifiedlog(originatorID117)fordetailed\ninformation on the cause of the error."
    },
    "116": {
        "code": 116,
        "desc": "VxSS authentication failed",
        "first_action": "EnsurethattheVeritasProductAuthenticationServiceisinstalledandconfigured.",
        "full_action": "Do the following, as appropriate:\n■ EnsurethattheVeritasProductAuthenticationServiceisinstalledandconfigured.\nForcompleteinstallationinstructions,seetheNetBackupSecurityandEncryption\nGuide.\n■ Check that both parties have a valid certificate. Examine the expiry date that is\nlisted from a bpnbat -WhoAmI. For example:\nbpnbat -WhoAmI\nName: JDOG\nDomain: MYCOMPANY\nIssued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nExpiry Date: Sep 19 12:51:55 2009 GMT\nAuthentication method: Microsoft Windows\nOperation completed successfully.\nShows an expiry date of September 19th, 2009. After 12:51:55 GMT this\ncredential is no longer valid and a new credential is required.\n■ If you run from the NetBackup Administration Console, close and reopen the\nconsole. The console automatically obtains a credential for the currently logged\nin identity, if possible. By default, these certificates are valid for 24 hours. The\nfollowing is an example of how to extend the credential beyond 24 hours to 30\ndays (2592000 seconds):\nWindows: <install path>\\veritas\\netbackup\\sec\\at\\bin\\vssat\nsetexpiryintervals -p <plugin_name> -t <user> -e 2592000\nUNIX: usr/openv/netbackup/sec/at/bin/vssat setexpiryintervals -p\n<plugin_name> -t <user> -e 2592000\n■ Ensure that the certificates for both sides use the same broker or are children\nof the same root broker and that trusts are established between them.\nSee the NetBackup Security and Encryption Guide for more information on\nbroker hierarchies and how to establish trust relationships between brokers.\n■ Ensure that connectivity between the physical systems in question is possible.\nIf general sockets cannot connect between the computers (such as ping and\ntelnet), issues within the network unrelated to NetBackup can cause this\nproblem.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp"
    },
    "117": {
        "code": 117,
        "desc": "VxSS access denied Recommended Action: Do the following, as appropriate: ■ If you use the default groups, make certain that the user attempts to perform an operationappropriateforthatgroup.Forexample,amemberofNBU_Operators is unable to modify policy information, which is a permission reserved for administrator roles. ■ Ensure that the system has sufficient swap space and the following directories are not full: ■ /home/username ■ /usr/openv/netbackup/logs NetBackup status codes 176 NetBackup status codes ■ /tmp ■ If you use your own defined groups and permissions, first determine the object with which the operation is associated. Then, add the permissions relative to the action. For example, a user is required to up and down drives but currently does not have permission to do so. Verify that the user belongs to the correct authorization group. If necessary, verify that the group has Up and Down permissions on the Drive object within the Group Permission tab. If necessary, increase the verbosity level of NetBackup to locate what object and what permissions are required for the failing request. The pertinent lines in the debug logs look similar to the following: 17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info. Name: JMIZZLE Domain: MYCOMPANY Expiry: Sep 24 21:45:32 2003 GMT Issued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx AuthType: 1 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082: Function: VssAzAuthorize. Object NBU_RES_Drives 17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083: Function: VssAzAuthorize. Permissions Up 17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166: Function: VssAzAuthorize. 20 Permission denied. Inthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires the Up permission on the Drives object. To diagnose the problem, examine the groups to which the user belongs to ensure that the appropriate group includes the Up permission. (Up is a member of the Operate permission set for Drives.) ■ If you have performed disaster recovery and are now running catalog recovery using the Remote Administration Console, you need to restart the master server services. After the restart, if you do not log out from the Remote AdministrationConsoleandtrytoaccesstheSecurityManagementtab,you receive this error message and must log on again. Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.",
        "first_action": "If you use the default groups, make certain that the user attempts to perform an",
        "full_action": "Do the following, as appropriate:\n■ If you use the default groups, make certain that the user attempts to perform an\noperationappropriateforthatgroup.Forexample,amemberofNBU_Operators\nis unable to modify policy information, which is a permission reserved for\nadministrator roles.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/username\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ If you use your own defined groups and permissions, first determine the object\nwith which the operation is associated. Then, add the permissions relative to\nthe action. For example, a user is required to up and down drives but currently\ndoes not have permission to do so. Verify that the user belongs to the correct\nauthorization group.\nIf necessary, verify that the group has Up and Down permissions on the Drive\nobject within the Group Permission tab. If necessary, increase the verbosity\nlevel of NetBackup to locate what object and what permissions are required for\nthe failing request. The pertinent lines in the debug logs look similar to the\nfollowing:\n17:19:27.653 [904.872] <2> GetAzinfo: Peer Cred Info.\nName: JMIZZLE\nDomain: MYCOMPANY\nExpiry: Sep 24 21:45:32 2003 GMT\nIssued by: /CN=broker/OU=root@machine1.mycompany.com/O=vx\nAuthType: 1\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5082:\nFunction: VssAzAuthorize. Object\nNBU_RES_Drives\n17:19:37.077 [904.872] <2> VssAzAuthorize: vss_az.cpp.5083:\nFunction: VssAzAuthorize. Permissions Up\n17:19:40.171 [904.872] <2> VssAzAuthorize: vss_az.cpp.5166:\nFunction: VssAzAuthorize. 20 Permission denied.\nInthisexample,theuserJMIZZLEattemptstoperformanoperationthatrequires\nthe Up permission on the Drives object. To diagnose the problem, examine the\ngroups to which the user belongs to ensure that the appropriate group includes\nthe Up permission. (Up is a member of the Operate permission set for Drives.)\n■ If you have performed disaster recovery and are now running catalog recovery\nusing the Remote Administration Console, you need to restart the master\nserver services. After the restart, if you do not log out from the Remote\nAdministrationConsoleandtrytoaccesstheSecurityManagementtab,you\nreceive this error message and must log on again."
    },
    "118": {
        "code": 118,
        "desc": "VxSS authorization failed NetBackup status codes 177 NetBackup status codes",
        "first_action": "Ensure that the Cohesity Product Authorization Service or daemon is running.",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the Cohesity Product Authorization Service or daemon is running.\nSee the NetBackup Security and Encryption Guide for more information on\nauthentication and authorization daemons.\n■ Ensure that you are in communication with the correct master server. Within\nthe bp.conf files on the local server, verify that the entry\nAUTHORIZATION_SERVICESspecifiestheproperhostname(fullyqualified)ofthe\nauthorization service. For example, AUTHORIZATION_SERVICE =\nmachine2.mycompany.com 0 specifies that the server contacts machine2 to\nperform authorization checks. Also ensure that this entry matches that of the\nmaster server.\n■ Ensure that the system has sufficient swap space and the following directories\nare not full:\n■ /home/userName\n■ /usr/openv/netbackup/logs\n■ /tmp\n■ Ensure that the server that contacts the master has a valid certificate. The\ncomputer certificate can be examined as follows:\nFor UNIX:\n# bpnbat -WhoAmI -cf\n/usr/openv/var/vxss/credentials/machine3.mycompany.com\nFor Windows:\nBpnbat WhoAmI -cf \"c:\\Program\nFiles\\VERITAS\\NetBackup\\var\\vxss\\credentials\\machine3.my\ncompany.com\"\nBoth of which would return:\nName: machine3.mycompany.com\nDomain: NBU_Machines@machine2.mycompany.com\nIssued by: /CN=broker/OU=root@machine2.mycompany.com/O=vx\nExpiry Date: Sep 2 19:25:29 2004 GMT\nAuthentication method: Veritas Private Security\nOperation completed successfully.\nIf the expiry date was exceeded, use bpnbat -LoginMachine to obtain a new\ncredential for the computer.\nSeetheNetBackupCommandsReferenceGuideformoreinformationonbpnbat.\nTheserverthatattemptsthecheckisnotauthorizedtoexaminetheauthorization\ndatabase. Ensure that bpnbaz -ShowAuthorizers re-tuned the computer's\nidentity.Ensurethatthecomputerhasacomputercredentialunderthedirectory\nas follows:\nProgram Files\\VERITAS\\var\\vxss\\credentials (Windows)\n/usr/openv/var/vxss/credentials (UNIX)\nThis credential should have the full name of the computer as in the following\nexample: machine1.company.com.\n■ Checkthatthemaximumnumberofopensocketstotheauthorizationdatabase\nwas not exhausted. Use netstat to determine the number of sockets that are\nopened to port 4032 on the authorization server and that refer to the following\nconfigurations:\nWindows:\nHKLM\\SOFTWARE\\VERITAS\\Security\\Authorization\\Communication\\ClientMaxConnections\nUNIX: /etc/vx/vss/VRTSaz.conf entryClientMaxConnections\nIf the maximum number of open connections was reached, you may need to\nincreasethenumberofmaximumopenconnections.Anincreaseinthenumber\nofopenconnectionsincreasesthememoryfootprintoftheauthorizationservice\nordaemon.Notethatextremeincreasesinthemaximumnumberofconnections\ncan cause performance degradation."
    },
    "120": {
        "code": 120,
        "desc": "Cannot find configuration database record for requested NB database backup",
        "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.",
        "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ For detailed troubleshooting information, create admin and bpdbm debug log\ndirectories and retry the operation. Check the resulting debug logs.\n■ Contact customer support and send the appropriate problem and debug log\nsections that detail the error."
    },
    "121": {
        "code": 121,
        "desc": "No media is defined for the requested NB database backup",
        "first_action": "Add the media IDs to the catalog backup configuration.",
        "full_action": "Add the media IDs to the catalog backup configuration.\nVerify that the media IDs are in the NetBackup volume pool."
    },
    "122": {
        "code": 122,
        "desc": "Specified device path does not exist",
        "first_action": "Retry the command by using a valid device file name.",
        "full_action": "Retry the command by using a valid device file name."
    },
    "123": {
        "code": 123,
        "desc": "Specified disk path is not a directory",
        "first_action": "Specify a different disk path for the catalog backup or",
        "full_action": "Specify a different disk path for the catalog backup or\ndelete the file that already exists."
    },
    "124": {
        "code": 124,
        "desc": "NB database backup failed, a path was not found or is inaccessible",
        "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.",
        "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nThe following are some possible causes:\n■ The path does not exist.\n■ On a UNIX system, one of the paths contains a symbolic link.\n■ After you determine which path cannot be accessed, correct the path names in\nthe catalog backup configuration."
    },
    "125": {
        "code": 125,
        "desc": "A NetBackup catalog backup is in progress",
        "first_action": "Retry the operation after the catalog backup completes.",
        "full_action": "Retry the operation after the catalog backup completes."
    },
    "126": {
        "code": 126,
        "desc": "NB database backup header is too large, too many paths specified",
        "first_action": "Delete some of the paths from the catalog backup",
        "full_action": "Delete some of the paths from the catalog backup\nconfiguration."
    },
    "127": {
        "code": 127,
        "desc": "Specified media or path does not contain a valid NB database backup header",
        "first_action": "Validate that the correct media ID is used.",
        "full_action": "Validate that the correct media ID is used."
    },
    "128": {
        "code": 128,
        "desc": "NBdatabaserecoveryfailed,aprocesshasencounteredanexceptional condition",
        "first_action": "Fixtheproblemthatwasreportedintheerrormessageinthebprecoveroutput.",
        "full_action": "Do the following, as appropriate:\n■ Fixtheproblemthatwasreportedintheerrormessageinthebprecoveroutput.\n■ Identify which NetBackup services to shut down before a NetBackup database\nrecovery attempt:\nSee\"AboutrecoveringtheNetBackupcatalog\"intheNetBackupTroubleshooting\nGuide.\nThe NetBackup services should be shut down except for the NetBackup Client\nService, which must be running for the database recovery to succeed.\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\nThe following are some possible causes:\n■ A disk may be full.\n■ The NetBackup catalog tape may be corrupt."
    },
    "129": {
        "code": 129,
        "desc": "Disk storage unit is full",
        "first_action": "Either free sufficient space or add more space to the file system for this storage",
        "full_action": "Do the following, as appropriate:\n■ Either free sufficient space or add more space to the file system for this storage\nunit.\n■ Lower the high capacity mark for this disk storage unit. Configure the policies\nto access it through a storage unit group that provides alternative storage to\nuse when this storage unit fills up. Ideally, if an image exceeds the file system’s\nhighcapacitymark,italsocompletessuccessfully.Thisimageleavesthestorage\nunit in a full state (over the high capacity mark). The storage unit then is not\nassigned to other jobs until its capacity falls under its high capacity mark.\n■ If the Staging attribute is set on the disk storage unit that did not have enough\ncapacity, it may be unable to create free space. It cannot create space because\nthe backups that are staged to the disk are not relocated (eligible to be deleted\nfromthestagingstorageunit).Ensurethatstaging’srelocation(duplication)jobs\nsuccessfully copy enough images to provide sufficient free space for new\nbackups."
    },
    "130": {
        "code": 130,
        "desc": "System error occurred",
        "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.",
        "full_action": "Do the following, as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Check the system log for reported problems.\n■ For detailed troubleshooting information, create bpdbm, bptm, and bprd debug\nlog directories on the master server. Increase the unified logging level by using\nthe vxlogcfg command.\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ Retry the operation and check the resulting debug logs.\nIf the policy validation fails, it is due to one of following reasons:\n■ A certificate mismatch is present on the client. Remove the Snapshot Manager\nCA certificate from the following location and validate the policy again:\ninstall_location/var/global/cloudpoint/certificates\n■ The Snapshot Manager is not accessible.\n■ If the NetBackup APIs produce this error, examine the unified logs for\nnbwebservice on the master server. For details on the web services logs, see\nthe section on the NetBackup Web Services logging within the NetBackup\nLogging Reference Guide.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ Failed to stage recovery tool on path %s in destination VM %s with error code\n%d.\nMake sure that the staging location path that is used exists and the provided\ntarget VM credentials have root or admin privileges.\n■ Failed to get the staging location for destination VM %s with error %d.\nMake sure that there is TMP or TEMP environment path available in the target\nVM or provided target VM credentials has root or admin privileges.\n■ FailedtoretrievetheguestVM%soperatingsystem(OS)detailswitherrorcode\n%d.\nMake sure that latest VMware Tools are installed and running in the target VM."
    },
    "131": {
        "code": 131,
        "desc": "Client is not validated to use the server",
        "first_action": "Examine the NetBackup Problems report.",
        "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup Problems report.\n■ Createadebuglogdirectoryforbprdandretrytheoperation.Checktheresulting\ndebug log to determine the connection and the client names.\nDepending on the request type (restore, backup, and so on), you may need or\nwant to do the following:\n■ Change the client’s configured name.\n■ Modify the routing tables on the client.\n■ On the master server, set up an altnames directory and file for this client.\nSee the NetBackup Administrator’s Guide, Volume I.\nOr\n■ On a UNIX master server, create a soft link in the NetBackup image catalog.\n■ SeeVerifyinghostnamesandservicesentriesintheNetBackupTroubleshooting\nGuide."
    },
    "132": {
        "code": 132,
        "desc": "User is not validated to use the server from this client",
        "first_action": "None",
        "full_action": "None"
    },
    "133": {
        "code": 133,
        "desc": "Invalid request",
        "first_action": "If you suspect that the software versions are the problem, verify that all",
        "full_action": "Do the following, as appropriate:\n■ If you suspect that the software versions are the problem, verify that all\nNetBackup software is at the same version level.\n■ On UNIX NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non the Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the\nHelp menu.\n■ If the server denies list and restore requests, do one of the following:\n■ Go to the NetBackup Administration Console. In the left pane, expand\nNetBackupManagement>HostProperties>MasterServers.Intheright\npane, double-click the master server you want to modify. In the properties\ndialog box, in the left pane, select Client Attributesto access the Allow\nclient browse and Allow client restore options.\n■ Remove the DISALLOW_CLIENT_LIST_RESTORE and\nDISALLOW_CLIENT_RESTORE options from the bp.conf file on a UNIX\nNetBackup server or from the registry on a Windows NetBackup server.\nThen,stopandrestarttheNetBackupRequestDaemon(UNIX)orNetBackup\nRequest Manager service (Windows).\n■ For detailed troubleshooting information, create bpdbm, bprd, and admin debug\nlog directories. Retry the operation and check the resulting debug logs."
    },
    "134": {
        "code": 134,
        "desc": "Unable to process request because the server resources are busy",
        "first_action": "None",
        "full_action": "None\nThe 134 code is an informational message only and is not considered an error. It\ncan occur for a number of reasons in normal operation. The 134 status code can\noccur more frequently in an SSO environment. No action is necessary.\nAstatus134isnotloggedintheerrorlogs.A134statuscausesanewtrytoappear\nin the Activity Monitor. It does not increase the retry count that is associated with\nthe allowed number of retries."
    },
    "135": {
        "code": 135,
        "desc": "Client is not validated to perform the requested operation",
        "first_action": "Retry the operation as a root user (on UNIX) or as an",
        "full_action": "Retry the operation as a root user (on UNIX) or as an\nadministrator (on Windows) on the master server. Also see status code 131."
    },
    "136": {
        "code": 136,
        "desc": "Tir info was pruned from the image file",
        "first_action": "Reimport the TIR information into the catalog of each",
        "full_action": "Reimport the TIR information into the catalog of each\ncomponent image (from which the TIR information was pruned). Then rerun the\nsynthetic backup job. The TIR information can be imported into the image catalog\nbyinitiatingatrueimagerestoreofanyfilefromthatcomponentimage.Therestore\nprocess also restores the TIR information in the image catalog."
    },
    "140": {
        "code": 140,
        "desc": "User ID was not superuser",
        "first_action": "If appropriate, give the user or the process administrator",
        "full_action": "If appropriate, give the user or the process administrator\nprivileges (on Windows) or root privileges (on UNIX) and retry the operation."
    },
    "141": {
        "code": 141,
        "desc": "File path specified is not absolute",
        "first_action": "Correct the file specification and retry the command.",
        "full_action": "Correct the file specification and retry the command."
    },
    "142": {
        "code": 142,
        "desc": "File does not exist",
        "first_action": "InstalltheVxFSdynamiclibrariesontheNetBackupclient",
        "full_action": "InstalltheVxFSdynamiclibrariesontheNetBackupclient\nand try the backup again."
    },
    "143": {
        "code": 143,
        "desc": "Invalid command protocol",
        "first_action": "ExaminetheNetBackuperrorlogstodeterminethesystem",
        "full_action": "ExaminetheNetBackuperrorlogstodeterminethesystem\nthatwasthesourceofthedata.Onthatsystem,determinetheprocessthatinitiated\nthe request. If it was a NetBackup process, verify that the process or command is\ncompatible with the version of software on the server."
    },
    "144": {
        "code": 144,
        "desc": "Invalid command usage",
        "first_action": "Either correct the command or verify that all NetBackup",
        "full_action": "Either correct the command or verify that all NetBackup\nbinaries are at the same version level."
    },
    "145": {
        "code": 145,
        "desc": "Daemon is already running",
        "first_action": "Terminatethecurrentcopyoftheprocessandthenrestart",
        "full_action": "Terminatethecurrentcopyoftheprocessandthenrestart\nthe process."
    },
    "146": {
        "code": 146,
        "desc": "Cannot get a bound socket",
        "first_action": "Examine the NetBackup Problems and All Log Entries reports.",
        "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup Problems and All Log Entries reports.\n■ Create bprd and bpdbm debug log directories and retry the operation. Check\ntheresultinglogstoseethesystemerrormessagethatresultedfromtheattempt.\nIf another process has the port, use other system commands to determine the\nprocess.Basedonthisresearch,eitherchangetheportnumberinyourservices\nfile or map or terminate the process that acquired the port.\nOn UNIX, another possible cause for this error is the use of the kill command\nto terminate bprd or bpdbm. To stop bpdbm, use the\n/usr/openv/netbackup/bin/bpdbm -terminate command. Use of the kill\ncommand to stop these processes can leave them unable to bind to their\nassigned ports the next time they are started.\nTo identify a bprd or a bpdbm problem, look for lines similar to the following in\nthe debug log for the respective process:\n<16> getsockbound: bind() failed, Address already in use (114)\n<32> listen_loop: cannot get bound socket. errno = 114\n<4> terminate: termination begun...error code = 146\nSimilar entries can appear in the reports.\n■ If the problem persists longer than 10 minutes, it may be necessary to restart\nthe server."
    },
    "147": {
        "code": 147,
        "desc": "Required or specified copy was not found",
        "first_action": "Correct the request to specify a copy number that does",
        "full_action": "Correct the request to specify a copy number that does\nexist."
    },
    "148": {
        "code": 148,
        "desc": "Daemon fork failed",
        "first_action": "Restart the service at a later time and investigate the system problems that limit",
        "full_action": "Do the following, as appropriate:\n■ Restart the service at a later time and investigate the system problems that limit\nthe number of processes.\n■ On Windows systems, check the Event Viewer Application and System logs."
    },
    "149": {
        "code": 149,
        "desc": "Master server request failed",
        "first_action": "None",
        "full_action": "None"
    },
    "150": {
        "code": 150,
        "desc": "Termination requested by administrator",
        "first_action": "None",
        "full_action": "None"
    },
    "152": {
        "code": 152,
        "desc": "Required value not set",
        "first_action": "Verify that all software is at the same version level.",
        "full_action": "Do the following, as appropriate:\n■ Verify that all software is at the same version level.\n■ For detailed troubleshooting information, create bpdbm and admin debug log\ndirectories and retry the operation. Check the resulting debug logs."
    },
    "153": {
        "code": 153,
        "desc": "Server is not the master server",
        "first_action": "None",
        "full_action": "None"
    },
    "154": {
        "code": 154,
        "desc": "Storage unit characteristics mismatched to request",
        "first_action": "For a NetBackup Snapshot Client, the policy storage unit was set to",
        "full_action": "Verify that the characteristics of the selected storage unit\nare appropriate for the attempted backup.\n■ For a NetBackup Snapshot Client, the policy storage unit was set to\nAny_available and the off-host backup method was set to Third-Party Copy\nDeviceorNetBackupMediaServer.DonotchooseAny_available.Aparticular\nstorage unit must be specified when Third-Party Copy Device or NetBackup\nMedia Server is specified as the off-host backup method.\n■ For an NDMP policy type, verify the following:\n■ You have defined a storage unit of type NDMP.\n■ The NDMP host value matches the host name of the client. For example, if\nthe NDMP policy specifies toaster as the client, the configuration for the\nstorage unit must specify toaster as the NDMP host.\n■ The media server for the storage unit is running the correct version of\nNetBackup.\n■ For a policy type other than NDMP, verify that the policy specifies a media\nmanager or disk type storage unit."
    },
    "155": {
        "code": 155,
        "desc": "Disk is full",
        "first_action": "Free up space on the disks where NetBackup catalogs",
        "full_action": "Free up space on the disks where NetBackup catalogs\nreside or where the track log folder resides and retry the operation."
    },
    "156": {
        "code": 156,
        "desc": "Snapshot error encountered",
        "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the",
        "full_action": "Perform the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Ensure that the snapshot limit of the cloud provider is sufficient.\n■ Check the ncfnbcs logs.\n■ Select a different storage option for Oracle Copilot backup with instant access.\nFormoreinformation,reviewtheOracleCopilotwithinstantaccessanduniversal\nshare chapter in the NetBackup for Oracle Administrator’s Guide.\n■ Thesnapshotissuccessfulwhentheassetisdiscoveredinnextdiscoverycycle.\nOr, the user can manually initiate a discovery when a new asset is added.\n■ Restart the shadow copy service.\n■ Right click on the C drive and then select Configure Shadow Copies….\n■ Select C drive and click Settings.\n■ Click schedule and then OK.\n■ Select another drive and repeat the steps. If there are no other drives then\nclick OK.\n■ Refer to Configuring VSS to store shadow copies on the originating drive in\nthe NetBackup Snapshot Manager Install and Upgrade Guide.\n■ Unsubscribe the protection plan from the asset.\n■ To discover the asset, start a manual discovery or it would be discovered in the\nnext autodiscovery.\n■ If the Snapshot fails with the error asset hierarchy is incomplete, refer to\nthe following technical article:\n■ CloudPoint snapshot is failing with \"The host level snapshot of cannot be\nperformed as asset hierarchy is incomplete\" due to ebsnvme-id returning\n/dev/sda when it should just return sda for the boot disk.\n■ See “"
    },
    "157": {
        "code": 157,
        "desc": "Suspend requested by administrator",
        "first_action": "The administrator can resume the job from the last",
        "full_action": "The administrator can resume the job from the last\ncheckpoint from the Activity Monitor."
    },
    "158": {
        "code": 158,
        "desc": "Failed accessing daemon lock file",
        "first_action": "Examine the NetBackup error log to determine why the system call failed. Then",
        "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup error log to determine why the system call failed. Then\ncorrect the problem. It may be a permission problem.\n■ If the error log does not show the error, create a debug log directory for bprd\nor bpdbm (depending on which process encountered the error). Increase the\nunified logging level if nbpem, nbjm, or nbrb encountered the error. Use the\nvxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting debug log."
    },
    "159": {
        "code": 159,
        "desc": "Licensed use has been exceeded",
        "first_action": "To determine the cause of the error, examine the",
        "full_action": "To determine the cause of the error, examine the\nNetBackupAllLogEntriesreportforthecommandthatwasrun.SeealsotheActivity\nMonitor details for informative messages.\nIf the job fails on a SAN media server storage unit, ensure that only the local client\nis specified in the policy. If remote clients are specified in the policy, do one of the\nfollowing: remove them and place them in a policy that specifies a different storage\nunit or change the storage unit for that policy.\nIf you want to back up remote clients by using the SAN media server, you can\npurchase a regular NetBackup media server license."
    },
    "160": {
        "code": 160,
        "desc": "Authentication failed",
        "first_action": "Add back the names that were removed and retry the operation.",
        "full_action": "Do the following, as appropriate:\n■ Add back the names that were removed and retry the operation.\n■ Create the following debug log directories for the processes that are involved\nin authentication between NetBackup systems:\n■ Server: bprd, bpdbm, and bpcd.\n■ Client: bpbackup, bprestore, and bpbkar.\nRetry the operation and review the debug logs.\nThe following actions relate to Snapshot Manager:\n■ Ensure that the Snapshot Manager credentials are correct.\n■ Verify that the credentials that were entered while registering are valid.\n■ If the credentials and the Snapshot Manager port number are updated, ensure\nthat they are updated in NetBackup.\n■ Ensure that the Snapshot Manager credentials are correct.\n■ VerifythatthecredentialsthatwereenteredwhileregisteringSnapshotManager\nare valid.\n■ Verifythatthecredentialsthatwereenteredwhileconfiguringastorageprovider\nare valid.\n■ If the credentials and the Snapshot Manager port number are updated, ensure\nthat they are updated in NetBackup."
    },
    "161": {
        "code": 161,
        "desc": "Evaluation software has expired.",
        "first_action": "Obtain a licensed copy of NetBackup. For information on",
        "full_action": "Obtain a licensed copy of NetBackup. For information on\nlicensing, contact your NetBackup sales or partner representative."
    },
    "162": {
        "code": 162,
        "desc": "Incorrect server platform for license NetBackup status codes 197 NetBackup status codes",
        "first_action": "Ensure that you use a license key that is intended for the",
        "full_action": "Ensure that you use a license key that is intended for the\nplatform on which you plan to install."
    },
    "163": {
        "code": 163,
        "desc": "Media block size changed prior resume",
        "first_action": "Check the Activity Monitor job details for the job ID of the",
        "full_action": "Check the Activity Monitor job details for the job ID of the\nrestarted job."
    },
    "164": {
        "code": 164,
        "desc": "Unable to mount media because it is in a DOWN, or otherwise not available",
        "first_action": "If volume is in a DOWN drive, remove it and place it in its designated slot. Then,",
        "full_action": "Do the following, as appropriate:\n■ If volume is in a DOWN drive, remove it and place it in its designated slot. Then,\nretry the restore.\n■ If the volume is in the wrong slot, use a robot inventory option to reconcile the\ncontents of the robot with the volume configuration."
    },
    "165": {
        "code": 165,
        "desc": "NB image database contains no image fragments for requested backup id/copy number NetBackup status codes 198 NetBackup status codes",
        "first_action": "Check the NetBackup Problems report for additional",
        "full_action": "Check the NetBackup Problems report for additional\ninformationabouttheerror.Fordetailedtroubleshootinginformation,createadebug\nlog directory for either bpdm or bptm (whichever applies) and retry the operation.\nCheck the resulting debug log."
    },
    "166": {
        "code": 166,
        "desc": "Backups are not allowed to span media",
        "first_action": "None",
        "full_action": "None"
    },
    "167": {
        "code": 167,
        "desc": "Cannot find requested volume pool in EMM database",
        "first_action": "Verify the Media and Device Management volume",
        "full_action": "Verify the Media and Device Management volume\nconfiguration. Check the NetBackup Problems report for more information about\ntheerror.Fordetailedtroubleshootinginformation,createabptmdebuglogdirectory\nand retry the operation. Check the resulting debug log."
    },
    "168": {
        "code": 168,
        "desc": "Cannot overwrite media, data on it is protected NetBackup status codes 199 NetBackup status codes",
        "first_action": "Replace the volume with a new one or set the NetBackup",
        "full_action": "Replace the volume with a new one or set the NetBackup\nALLOW_MEDIA_OVERWRITE option to the appropriate value."
    },
    "169": {
        "code": 169,
        "desc": "Media ID is either expired or will exceed maximum mounts",
        "first_action": "If the volume was suspended, wait until it expires and",
        "full_action": "If the volume was suspended, wait until it expires and\nthen replace it. For NetBackup catalog backups, replace the media."
    },
    "170": {
        "code": 170,
        "desc": "Third party copy backup failure",
        "first_action": "If a non third-party copy device is listed in 3pc.conf file, correct it or remove",
        "full_action": "Do the following, as appropriate:\n■ If a non third-party copy device is listed in 3pc.conf file, correct it or remove\nthe non third-party copy device entry.\n■ If an incorrect LUN is specified in the 3pc.conf file or the device does not exist,\ncorrect the 3pc.conf file as appropriate.\n■ If an appropriate mover.conf file (with or without file name extension) cannot\nbe found, the /usr/openv/netbackup/logs/bptm log may show the following:\n09:51:04 [22281] <2> setup_mover_tpc: no\nmover.conf.vertex_std_tpc or mover.conf file exists, cannot\nperform TPC backup\n09:51:04 [22281] <16> bptm: unable to find or communicate with\nThird-Party-Copy mover for policy vertex_std_tpc\nMakesurethatanappropriatemover.conf fileexistsin/usr/openv/netbackup\non the media server. This file can be any of the following:\n■ mover.conf.policy_name file, where policy_name exactly matches the\nname of the policy.\n■ mover.conf.storage_unit_name,wherestorage_unit_nameexactlymatches\nthe name of the storage in the Backup Policy Management Policy\nattributes dialog box.\n■ mover.conf file (no extension) for the configurations that have only one\nthird-party copy device.\nNote that NetBackup looks for an appropriate mover.conf file in the order.\n■ If the SCSI pass-through path of the third-party copy device, as entered in the\nmover.conf file, does not exist, the bptm log may show the following:\n09:50:12 [22159] <16> setup_mover_tpc: open of passthru path\n/dev/sg/cXtXlX failed, No such file or directory\n09:50:12 [22159] <16> bptm: unable to find or communicate with\nThird-Party-Copy mover for policy vertex_std_tpc\nCorrecttheSCSIpass-throughpathofthethird-partycopydevicethatisentered\nin the mover.conf file.\n■ If the third-party copy device returned an error, you may see either of the\nfollowing messages in /usr/openv/netbackup/logs/bptm log:\ncannot process extended copy error due to truncated sense data,\nmay be HBA problem\ndisk error occurred on extended copy command, key = 0x0, asc =\n0x0, ascq = 0x0\n(where key, asc, and ascq are all zero)\nYour host-bus adapter (HBA) and its driver may need to be updated, or\nNetBackup Snapshot Client may not support them. The supported host-bus\nadapters are listed.\nSee the NetBackup Release Notes."
    },
    "171": {
        "code": 171,
        "desc": "Media ID must be 6 or less characters",
        "first_action": "Retry the command with a valid media ID.",
        "full_action": "Retry the command with a valid media ID."
    },
    "172": {
        "code": 172,
        "desc": "Cannotreadmediaheader,maynotbeNetBackupmediaoriscorrupted",
        "first_action": "If the volume is in a robot that supports bar codes, verify the robot contents by",
        "full_action": "Do the following, as appropriate:\n■ If the volume is in a robot that supports bar codes, verify the robot contents by\nusing a robot inventory option.\n■ If the volume was mounted on a nonrobotic drive, verify that the correct volume\nwas mounted and assigned.\n■ Check the NetBackup Problems report. If it shows a fatal read error, try the\noperation again with another drive, if possible.\n■ If your configuration has multiple servers or HBAs with access to your tape\nservices, make sure that the SCSI Reserve or Release is onfigured correctly.\n(Most likely, the tape services configuration is an SSO configuration.)\nFor more information on the storage server, please see the NetBackup\nAdministrator's Guide, Volume II."
    },
    "173": {
        "code": 173,
        "desc": "Cannot read backup header, media may be corrupted",
        "first_action": "Check the NetBackup Problems report for clues as to what caused the error.",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for clues as to what caused the error.\n■ Try the restore on another drive if possible.\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log."
    },
    "174": {
        "code": 174,
        "desc": "Media manager - system error occurred",
        "first_action": "Check the NetBackup Problems report to see if it shows the cause of the",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report to see if it shows the cause of the\nproblem. If you see a Problems report message similar to the following, save\nall logs and contact Cohesity Technical Support:\nattempted to write 32767 bytes, not a multiple of 512\n■ On UNIX, if this error occurs during a restore, the tape drive may be incorrectly\nconfigured. It may be configured to write in fixed-length mode when it should\nwrite in variable length mode.\nVerify your drive’s configuration by comparing it to what is recommended in the\nNetBackup Device Configuration Guide.\nIfyourconfigurationincorrectlyspecifiesfixed-lengthmode,changeittovariable\nlengthmodeandsuspendthemediathatwerewrittenonthatdevice.Theimages\nthat were written to those media may be restorable (platform dependent), but\nsingle file restores are likely to fail.\n■ If the problem occurs with a particular client only, verify that the client binaries\nare correct, especially for bpcd.\n■ If you can read or write any other images on this media, check the following\nreports for clues:\n■ Images on Media report\n■ Media Contents report\n■ Verify the following:\n■ The media, by using the NetBackup image verify option.\n■ That you used the correct media type for the device.\n■ Check the system or the console log for errors (on UNIX) or the Event Viewer\nApplication log (on Windows).\n■ For detailed debug information, create a debug log directory for either bptm or\nbpdm (whichever applies) and retry the operation. Check the resulting debug\nlog.\nOn UNIX, if the bptm debug log shows an error similar to the following, the tape\ndriveisconfiguredtowriteinfixed-lengthmoderatherthanvariablelengthmode.\n00:58:54 [2304] <16> write_data: write of 32768 bytes indicated\nonly 29696 bytes were written, errno = 0\nThe image being written encountered the end-of-media.\n■ If the backup was configured for an OpenStorage disk storage unit, the\nOpenStorage vendor's plug-in may not be installed on all media servers in the\nstorage unit's media server list. Either install the vendor plug-in on all of the\nmedia servers or remove from the list the servers that do not have the plug-in\ninstalled.\n■ On UNIX, if this error occurs during a restore, refresh the Backup, Archive,\nand Restore client console and retry the restore. This action refreshes the file\nlist displayed in the client console and passes the correct information about the\nselected files."
    },
    "175": {
        "code": 175,
        "desc": "Not all requested files were restored",
        "first_action": "Check the NetBackup Problems report and the status lot or the progress log on",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report and the status lot or the progress log on\nthe client for additional information about the error.\n■ For detailed troubleshooting information, create a debug log directory for either\nbptm or bpdm (whichever applies) and retry the operation. Check the resulting\ndebug log."
    },
    "176": {
        "code": 176,
        "desc": "Cannot perform specified media import operation",
        "first_action": "If the media ID is already active, duplicate all images on the original media ID",
        "full_action": "Check the NetBackup Problems report to find the exact\ncause of the failure and try the following:\n■ If the media ID is already active, duplicate all images on the original media ID\ntoanothervolume.Then,manuallyexpiretheoriginalmediaandredotheimport.\n■ If the media ID is not present in the volume configuration, add it.\n■ If you received a fatal bptm error, verify that the following are active: the\nNetBackupVolumeManager(vmd)onUNIXortheNetBackupVolumeManager\non Windows.\n■ If the entire image is not present, perform import phase 1 on the media IDs that\nhave the remainder of the image.\n■ If the barcode and media ID are a mismatch, use a barcode label that matches\ntherecordedmediaID.TapescanthenbemountedinadrivewithAVRDrunning\nso that the recorded media ID is displayed. Then, a barcode with that label\nneeds to be placed on the tape."
    },
    "177": {
        "code": 177,
        "desc": "Could not deassign media due to Media Manager error",
        "first_action": "Check the NetBackup Problems report for the cause of the problem.",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for the cause of the problem.\n■ Verify that the NetBackup Volume Manager (vmd) is active on UNIX or the\nNetBackup Volume Manager service is active on Windows.\n■ For detailed troubleshooting information, create a debug log directory for bptm\nand retry the operation. Check the resulting debug log."
    },
    "178": {
        "code": 178,
        "desc": "Media ID is not in NetBackup volume pool",
        "first_action": "Check the Media and Device Management volume",
        "full_action": "Check the Media and Device Management volume\nconfiguration to verify that the media IDs are present and in the NetBackup volume\npool."
    },
    "179": {
        "code": 179,
        "desc": "Density is incorrect for the media ID",
        "first_action": "CheckthevolumeconfigurationandtheNetBackupcatalog",
        "full_action": "CheckthevolumeconfigurationandtheNetBackupcatalog\nbackup configuration and correct any problems found."
    },
    "180": {
        "code": 180,
        "desc": "Tar was successful",
        "first_action": "None",
        "full_action": "None"
    },
    "181": {
        "code": 181,
        "desc": "Tar received an invalid argument",
        "first_action": "On a UNIX client:",
        "full_action": "Do the following, as appropriate:\n■ On a UNIX client:\n■ Ensure that the nbtar command in /usr/openv/netbackup/bin is the one\nprovided by NetBackup. If you are in doubt, reinstall it.\n■ Check /usr/openv/netbackup/bin/version on the client to verify that the\nclientisrunningthecorrectlevelsoftware.Ifthesoftwareisnotatthecorrect\nlevel,updatethesoftwareperthedirectionsintheNetBackupReleaseNotes.\n■ On a Windows client, create a tar debug log directory, retry the operation, and\ncheck the log."
    },
    "182": {
        "code": 182,
        "desc": "Tar received an invalid file name",
        "first_action": "Create a bpcd debug log directory on the client .",
        "full_action": "Do the following, as appropriate:\n■ Create a bpcd debug log directory on the client .\n■ On a Windows client, create a tar debug log directory.\n■ Increase the logging level on the client:\n■ On a UNIX client, add the VERBOSE option to the\n/usr/openv/netbackup/bp.conf file.\n■ On PC clients, increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Rerun the operation, check the resulting debug logs for the parameters that\nwere passed to tar and contact Cohesity Technical Support."
    },
    "183": {
        "code": 183,
        "desc": "Tar received an invalid archive",
        "first_action": "IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar",
        "full_action": "Do the following, as appropriate:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log directory on the client and rerun the operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart the client to see if it clears the problem.\n■ When you finish with your investigation of the problem, delete the\n/usr/openv/netbackup/logs/ tar directory on the client.\n■ If the problem is with a Microsoft Windows client, do the following in the order\npresented:\n■ Create a bpcd debug log directory on the client.\n■ On a Windows client, create a tar debug log directory.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ Rerun the operation and check the resulting debug logs.\n■ Restart the client to see if it clears the problem."
    },
    "184": {
        "code": 184,
        "desc": "Tar had an unexpected error",
        "first_action": "IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar",
        "full_action": "Do the following, as appropriate:\n■ IftheproblemiswithaUNIXclient,createa/usr/openv/netbackup/logs/tar\ndebug log directory on the client and rerun the operation.\n■ Checkthetardebuglogfileforanyerrormessagesthatexplaintheproblem.\n■ Restart the client to see if it clears the problem.\n■ When you finish your investigation of the problem, delete the\n/usr/openv/netbackup/logs/tar directory on the client.\n■ If the problem is with a Microsoft Windows client:\n■ Create a bpcd debug log directory on the client .\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a Windows client, create a tar debug log directory.\n■ Retry the operation and check the resulting debug logs.\n■ Restart the client to see if it clears the problem."
    },
    "185": {
        "code": 185,
        "desc": "Tar did not find all the files to be restored",
        "first_action": "If the problem is with a UNIX client:",
        "full_action": "Do the following, as appropriate:\n■ If the problem is with a UNIX client:\n■ Enable bpcd debug logging by creating the\n/usr/openv/netbackup/logs/bpcd directory on the client.\n■ Reruntheoperation,checktheresultingbpcdlogfilefortheparametersthat\nwere passed to nbtar, and contact Cohesity Technical Support.\n■ If the problem is with a Microsoft Windows client:\n■ Create a bpcd debug log directory on the client.\n■ Increase the debug or log level.\nSee \"Changing the logging level on Windows clients\" in the NetBackup\nLogging Reference Guide.\n■ On a Windows client, create a tar debug log directory.\n■ Retry the operation.\n■ Check the resulting debug logs for the parameters that were passed to tar\nand contact Cohesity Technical Support."
    },
    "186": {
        "code": 186,
        "desc": "Tar received no data",
        "first_action": "Retry the operation and check the status or the progress log on the client for",
        "full_action": "Do the following, as appropriate:\n■ Retry the operation and check the status or the progress log on the client for\nany error messages that reveal the problem.\n■ Verify that the tape is available and readable.\n■ Verify that the drive is in an UP state. Use the Device Monitor.\n■ For detailed troubleshooting information:\n■ Create a bptm debug log on the server.\n■ On a Windows client, create a tar debug log.\n■ Retry the operation and check the resulting debug logs."
    },
    "189": {
        "code": 189,
        "desc": "The server is not allowed to write to the client’s file systems",
        "first_action": "On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the",
        "full_action": "Performthefollowingtoperformrestoresorinstallsoftware\nfrom the server:\n■ On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the\n/usr/openv/netbackup/bp.conf file.\n■ On a Microsoft Windows client, select Allow server-directed restores on the\nGeneral tab in the NetBackup Client Properties dialog box. To display this\ndialog box, start the Backup, Archive, and Restore interface on the client and\nselect NetBackup Client Properties from the File menu."
    },
    "190": {
        "code": 190,
        "desc": "Found no images or media matching the selection criteria",
        "first_action": "Change the search criteria and retry.",
        "full_action": "Change the search criteria and retry."
    },
    "191": {
        "code": 191,
        "desc": "No images were successfully processed",
        "first_action": "Check the NetBackup Problems report for the cause of the error. To obtain",
        "full_action": "Do the following, as appropriate:\n■ Check the NetBackup Problems report for the cause of the error. To obtain\ndetailed troubleshooting information, create an admin debug log directory and\nretry the operation. Check the resulting debug log.\n■ If the backup or duplicate job failed for a policy configured with a retention level\ngreater than 25, you can either upgrade the media server to NetBackup 8.0 or\nlater or set the retention level between 0 and 25. Note that the retention period\nforlevel25isalwayssettoexpireimmediatelyandthisvaluecannotbechanged.\n■ Iftheerrorwasencounteredduringduplicationofbackups,checktheduplication\nprogress log to help determine the root cause of the problem.\n■ An Auto Image Replication job may cause this error. If the storage lifecycle\npolicy names or data classifications do not match the originating domain and\nthe target domain, the import job fails. Failed imports appear in the Problems\nreport when it is run on the target master server. The image is expired and\ndeleted during catalog cleanup. Note that the originating domain does not track\nfailed imports.\nMore information is available about troubleshooting this problem:\nFor more information on troubleshooting this problem, please see the About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ An automatic import job may cause this error. This job is an import job that\nshows a storage lifecycle policy name.\nMore information is available about troubleshooting this problem:\nFor more information on troubleshooting this problem, please see the About\nTroubleshootingAutoImageReplicationtopicoftheNetBackupTroubleshooting\nGuide.\n■ If a Vault job encountered the error responsible for the duplication, check the\nduplicate.log files in your sidxxx directories to determine the root cause:\nUNIX:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\n■ Reduce the maximum fragment size on the storage unit that writes to this file\nsystem. This value is typically less than 20 GB. But you may need to adjust the\nmaximum fragment size as necessary until the STS_EFILESYSTEM errors no\nlonger occur. The value is based on how much data that the storage unit writes\nto the image.\nTo change this value, in the NetBackup Administration Console, in the left\npane, expand NetBackup Management > Storage. Then in the right pane,\ndouble-click the storage unit for this file system. In the Change Storage Unit\ndialog box, change the value of the Maximum Fragment Size to 20480 MB (20\nGB) by checking the Reduce fragment size to checkbox and entering the new\nvalue.\n■ Increase the Allocation Unit Size by reconfiguring the file system. This usually\nrequires that you format the file system, so this action may not be a feasible for\nan existing file system. Consider this when you create a new file system for\nBasicDisk images or AdvancedDisk images. Because setting this value is\ndifferent on each OS file system, refer to the appropriate OS or file system\ndocumentation for instructions.\n■ Ensure that the Logical Storage Unit (LSU) name or the Domain Volume name\nhas less than 50 ASCII characters, including a hyphen (-) and an underscore\n(_), and that the name does not have a blank space."
    },
    "192": {
        "code": 192,
        "desc": "VxSS authentication is required but not available",
        "first_action": "Make sure that both systems are configured to use",
        "full_action": "Make sure that both systems are configured to use\nNetBackup Access Control VxSS authentication with each other. Or, make sure\nthat both systems are not configured to use VxSS with each other. The first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\nfor REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If\none is configured for PROHIBITED,the other must be configured for PROHIBITED\nor AUTOMATIC.\nSee the NetBackup Administrator’s Guide, Volume I, for the following information:\nhow to set the Access Control-related host properties, and how to configure a\nsystem to use Access Control."
    },
    "193": {
        "code": 193,
        "desc": "VxSS authentication is requested but not allowed",
        "first_action": "Make sure that both systems are configured to use",
        "full_action": "Make sure that both systems are configured to use\nNetBackup Access Control VxSS authentication with each other. Or, make sure\nthat both systems are not configured to use VxSS with each other. The first thing\ntocheckistheUseVxSSHostpropertiesvalueoneachsystem.Ifoneisconfigured\nfor REQUIRED, the other must be configured for REQUIRED or AUTOMATIC. If\none is configured for PROHIBITED,the other must be configured for PROHIBITED\nor AUTOMATIC.\nSee the NetBackup Administrator’s Guide, Volume I, for the following information:\nhow to set the Access Control-related host properties how to configure a system\nto use Access Control."
    },
    "194": {
        "code": 194,
        "desc": "The maximum number of jobs per client is set to 0",
        "first_action": "To enable backups and archives, change the Maximum",
        "full_action": "To enable backups and archives, change the Maximum\njobs per client value to the wanted nonzero setting. This attribute is on the Global\nNetBackup Attributes tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide."
    },
    "195": {
        "code": 195,
        "desc": "Client backup was not attempted",
        "first_action": "Retry the backup either immediately with a manual backup or allow the normal",
        "full_action": "Do the following, as appropriate:\n■ Retry the backup either immediately with a manual backup or allow the normal\nscheduler retries.\n■ For additional information, check the All Log Entries report. For detailed\ntroubleshooting information, increase the logging level for the diagnostic and\ndebug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nAfter the next backup try, check the logs."
    },
    "196": {
        "code": 196,
        "desc": "Client backup was not attempted because backup window closed",
        "first_action": "If possible, change the schedule to extend the backup window for this",
        "full_action": "Do the following, as appropriate:\n■ If possible, change the schedule to extend the backup window for this\ncombination of policy and schedule so it does not occur again.\n■ If the backup must be run, use the Manual Backup command on the Policy\nmenu in the Backup Policy Management window to perform the backup.\nManual backups ignore the backup window."
    },
    "197": {
        "code": 197,
        "desc": "The specified schedule does not exist in the specified policy",
        "first_action": "Check the client progress log (if available) to determine the policy and schedule",
        "full_action": "Do the following, as appropriate:\n■ Check the client progress log (if available) to determine the policy and schedule\nthat were specified.\n■ Check the configuration on the master server to determine if the schedule is\nvalid for the policy. If the schedule is not valid, either add the schedule to the\npolicy configuration or specify a valid schedule on the client."
    },
    "198": {
        "code": 198,
        "desc": "No active policies contain schedules of the requested type for this client NetBackup status codes 215 NetBackup status codes",
        "first_action": "If the client is in such a policy, check the general policy attributes to verify that",
        "full_action": "Determine if the client is in any policy that has a schedule\nof the appropriate type (either user backup or archive).\n■ If the client is in such a policy, check the general policy attributes to verify that\nthe policy is set to active.\n■ If the client is not in such a policy, do either of the following:\n■ Add a schedule of the appropriate type to an existing policy that has this\nclient.\n■ Create a new policy that has this client and a schedule of the appropriate\ntype."
    },
    "199": {
        "code": 199,
        "desc": "Operation not allowed during this time period",
        "first_action": "If possible, retry the operation when the backup window is open.",
        "full_action": "Determine the policies to which this client belongs that\nalso have a schedule of the appropriate type (either user backup or archive).\n■ If possible, retry the operation when the backup window is open.\n■ If the backup window is not open during appropriate time periods, adjust a\nbackup window for a schedule in one of the policies."
    },
    "200": {
        "code": 200,
        "desc": "The scheduler found that no backups are due. Or, the target hosts do not need to be upgraded.",
        "first_action": "Examine the NetBackup All Log Entries report for any messages in addition to",
        "full_action": "Usually, this message can be considered informational\nand does not indicate a problem. However, if you suspect a problem, do the\nfollowing:\n■ Examine the NetBackup All Log Entries report for any messages in addition to\nthe one that indicates the scheduler found nothing to do.\n■ Examine the policy configuration for all policies or the specific policy in question\nto determine if any of the reasons in the Explanation section apply.\n■ Toobtaindetailedtroubleshootinginformation,increasetheunifiedlogginglevel\nfor the diagnostic and debug logs.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs.\n■ For SQL Server policies that use intelligent groups, ensure that the credentials\nare valid for the SQL Server instances or databases that are included in the\npolicy.\nRefertotheNetBackupforMicrosoftSQLServerAdministrator’sGuideformore\ndetails on this error."
    },
    "201": {
        "code": 201,
        "desc": "Handshaking failed with server backup restore manager",
        "first_action": "Determinetheactivitythatencounteredthehandshakefailurebyexaminingthe",
        "full_action": "Do the following, as appropriate:\n■ Determinetheactivitythatencounteredthehandshakefailurebyexaminingthe\nNetBackup All Log Entries report for the appropriate time period. If there are\nmedia servers, determine if:\n■ The handshake failure was encountered between the master and a media\nserver.\nor\n■ Only the master server was involved.\n■ Ifnecessary,createthefollowingdebuglogdirectoriesandincreasethelogging\nlevel:\n■ bpcd on the NetBackup media host (can be either the master or a media\nserver).\n■ Iftheerrorwasencounteredduringabackupoperation,increasethelogging\nlevel for the diagnostic and debug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\n■ If the error was encountered during a restore operation, bprd on the master\nserver.\n■ If the error was encountered during a media list operation, admin in the\nNetBackup logs/admin directory on the master server.\n■ Status code 201 may occur if nbjm fails after it connects to bpbrm or bpmount\nbut before the policy file list is sent. Examine the nbjm unified log (originator ID\n117) or the bpbrm or the bpmount legacy logs for more detail on the cause of\nthe error.\n■ Retry the operation and examine the resulting debug logs for information on\nwhy the error occurred."
    },
    "202": {
        "code": 202,
        "desc": "Timed out connecting to server backup restore manager",
        "first_action": "Verify that the schedule specifies the correct storage unit.",
        "full_action": "Determine which activity encountered the connection\ntimeout failure by examining the All Log Entries report for the appropriate time\nperiod. If there are media servers, determine if the timeout occurred between the\nmaster and a media server or if only the master was involved.\n■ Verify that the schedule specifies the correct storage unit.\n■ Run the ping command from one host to another by using the following\ncombinations:\n■ From the master server, ping the master and all media servers by using the\nhost names that are found in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the host\nname that is specified in the NetBackup server list. On a UNIX or Linux\nserver,themasteristhefirstSERVERentryinthebp.conffile.OnaWindows\nserver, the master is designated on the Servers tab in the Master Server\nProperties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in\nthe NetBackup Troubleshooting Guide.\n■ Verify that the master server can communicate with bpcd on the host that has\nthe storage unit.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ If necessary, create debug log directories for the following processes and retry\nthe operation. Then, check the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, increase the logging level\nfor the diagnostic and debug logs for nbpem, nbjm, and nbrb.\nUse the vxlogcfg command as explained in the following procedure:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nAlso, check the bpcd legacy debug logs.\n■ If the error occurs during a restore operation, check the bprd debug logs."
    },
    "203": {
        "code": 203,
        "desc": "Server backup restore manager’s network is unreachable NetBackup status codes 219 NetBackup status codes",
        "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost",
        "full_action": "Determine which activity encountered this failure by\nexamining the All Log Entries report for the appropriate time frame. If there is more\nthan one NetBackup server (one or more media servers), determine the following:\nifthefailurewasbetweenthemasterandamediaserverorifonlythemasterserver\nwas involved. Run the ping command from one host to another by using the\nfollowing combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server host by using the host\nname that is specified in the NetBackup server list. On a UNIX or Linux server,\nthe master is the first SERVER entry in the bp.conf file. On a Windows server,\nthe master is designated on the Servers tab in the Master Server Properties\ndialog.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\nchecktheresultingdebuglogsonthemasterserver.Iftheerroroccurredduring\na restore, check the bprd debug logs."
    },
    "204": {
        "code": 204,
        "desc": "Connection refused by server backup restore manager",
        "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost",
        "full_action": "Runthepingcommandfromonehosttoanotherbyusing\nthe following combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nwas specified in the NetBackup server list. On a UNIX or Linux server, this\nmaster is the first SERVER entry in the bp.conf file. On a Windows server, the\nmasterisdesignatedontheServerstabintheMasterServerPropertiesdialog\nbox. The following topic shows how to access this dialog box:\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ On UNIX and Linux servers, verify that the bpcd entries in /etc/services or\nNIS on all the servers are identical. Verify that the media host listens on the\ncorrectportforconnectionstobpcd.Toverify,runoneofthefollowingcommands\n(depending on platform and operating system):\nnetstat -a | grep bpcd\nnetstat -a | grep 13782 (or the value that was specified during the install)\nrpcinfo -p | grep 13782 (or the value that was specified during the install)\nOn UNIX and Linux servers, it may be necessary to change the service number\nfor the following: bpcd in /etc/services and the NIS services map and send\nSIGHUP signals to the inetd processes on the clients.\n/bin/ps -ef | grep inetd\nkill -HUP the_inetd_pid\nor\n/bin/ps -aux | grep inetd\nkill -HUP the_inetd_pid\nNote: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to\ninetd.\n■ On Windows servers, do the following:\n■ Verify that the bpcd entries are correct in the following:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verify that the following numbers match the settings in the services file:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start the Backup, Archive, and Restore\ninterface and select NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Stop and restart the NetBackup services.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\ncheck the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, check the nbpem, nbjm, and\nnbrb logs by using the vxlogview command.\n■ If the error occurred during a restore operation, check the bprd debug logs."
    },
    "205": {
        "code": 205,
        "desc": "Cannot connect to server backup restore manager",
        "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost",
        "full_action": "Runthepingcommandfromonehosttoanotherbyusing\nthe following combinations:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nis specified in the NetBackup server list. On a UNIX or Linux server, this master\nis the first SERVER entry in the bp.conf file. On a Windows server, the master\nis designated on the Servers tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ On a UNIX or Linux server, verify that the bpcd entry in /etc/services or NIS\non all the servers are identical. Verify that the media host listens on the correct\nport for connections to bpcd. To verify, run one of the following commands\n(depending on platform and operating system):\nnetstat -a | grep bpcd\nnetstat -a | grep 13782 (or the value that is specified during the install)\nrpcinfo -p | grep 13782 (or the value that is specified during the install)\n■ On Windows servers, do the following:\n■ Verify that the bpcd entries are correct in the services file:\n%SystemRoot%\\system32\\drivers\\etc\\services\n■ Verify that the following numbers match the settings in the services file:\nNetBackupClientServicePortnumberandNetBackupRequestService\nPortnumberontheNetworktabintheNetBackupClientPropertiesdialog\nbox. To display this dialog box, start the Backup, Archive, and Restore\ninterface and select NetBackup Client Properties on the File menu.\nThe values on the Network tab are written to the services file when the\nNetBackup Client service starts.\n■ Stop and restart the NetBackup services.\n■ Perform the following procedures:\nSee \"Testing the media server and clients\" in the NetBackup Troubleshooting\nGuide.\nSee \"Resolving network communication problems\" in the NetBackup\nTroubleshooting Guide.\n■ Create a bpcd debug log directory on the server that has the storage unit and\nretry the operation. Then, check for additional information in the debug log."
    },
    "206": {
        "code": 206,
        "desc": "Access to server backup restore manager denied",
        "first_action": "Verify that the master server appears as a server in its own server list as well",
        "full_action": "Do the following, as appropriate:\n■ Verify that the master server appears as a server in its own server list as well\nas being listed on all media servers.\nIf you change the master server list, stop and restart the NetBackup Database\nManager (bpdbm) and NetBackup Request Daemon (bprd) to ensure that all\nappropriate NetBackup processes use the new server entry.\n■ Ifnecessary,createdebuglogdirectoriesforbprdandretrytheoperation.Then,\ncheck the resulting debug logs on the master server:\n■ If the error occurred during a backup operation, check the nbpem, nbjm, and\nnbrb logs by using the vxlogview command.\n■ If the error occurred during a restore operation, check the bprd debug logs."
    },
    "207": {
        "code": 207,
        "desc": "Error obtaining date of last backup for client",
        "first_action": "Verify that the NetBackup Database Manager, bpdbm, is running.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the NetBackup Database Manager, bpdbm, is running.\n■ ExaminetheAllLogEntriesreportfortheappropriatetimeframetogathermore\ninformation about the failure.\n■ For detailed troubleshooting information, create a bpdbm log directory on the\nmaster server. Increase the logging level for the diagnostic and debug logs for\nnbpem.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation, then check the resulting logs."
    },
    "209": {
        "code": 209,
        "desc": "Error creating or getting message queue",
        "first_action": "Create debug log directories on the master server and",
        "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also gather the output of the ipcs -a command to\nsee what system resources are currently in use."
    },
    "210": {
        "code": 210,
        "desc": "Error receiving information on message queue",
        "first_action": "Create debug log directories on the master server and",
        "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also gather the output of the ipcs -a command to\nsee what system resources are currently in use."
    },
    "212": {
        "code": 212,
        "desc": "Error sending information on message queue",
        "first_action": "Create debug log directories on the master server and",
        "full_action": "Create debug log directories on the master server and\nretry the operation. Then, determine the type of system failure by examining the\nlogs. Start with the bprd debug log.\nOn UNIX and Linux servers, also, gather the output of the ipcs -a command to\nsee what system resources are currently in use."
    },
    "213": {
        "code": 213,
        "desc": "No storage units available for use",
        "first_action": "Examine the Backup Status and All Log Entries report for the appropriate time",
        "full_action": "Do the following, as appropriate:\n■ Examine the Backup Status and All Log Entries report for the appropriate time\nperiod to determine the policy or schedule that received the error.\n■ Verify that the media server has not been deactivated for the storage unit or\nunits that are unavailable.\n■ Verify that the storage unit’s drives are not down.\n■ Verify the following attribute settings for all storage units:\n■ For disk storage units, the Maximum concurrent jobs is not set to 0\n■ For Media Manager storage units, the Maximum concurrent write drives\nis not set to 0\n■ Verify that the robot number and host name in the storage unit configuration\nmatches the Media and Device Management device configuration.\n■ Determine if all storage units are set to On demand only for a combined policy\nand schedule that does not require a specific storage unit. In this case, either\nspecify a storage unit for the policy and the schedule combination or turn off On\ndemand only for a storage unit.\n■ IfthestorageunitisonaUNIXorLinuxNetBackupmediaserver,itmayindicate\na problem with bpcd. Check /etc/inetd.conf on the media server to verify\nthat the bpcd entry is correct.\nIf the storage unit is on a Windows NetBackup media server, verify that the\nNetBackupClientservicewasstartedontheWindowsNetBackupmediaserver.\n■ For detailed troubleshooting information, increase the logging levels of nbrb\nand mds on the master server.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting debug logs."
    },
    "215": {
        "code": 215,
        "desc": "Failed reading global config database information",
        "first_action": "OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager",
        "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process is running. On a Windows master server, verify that the\nNetBackup Database Manager service is running.\n■ Try to view the global configuration settings by using the NetBackup\nadministrationinterface(onUNIXandLinuxsystems),orbyusingHostProperties\n(on Windows systems).\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\nand bpdbm on the master server and retry the operation. Check the resulting\ndebug logs for these processes. Also check the nbpem logs by using the\nvxlogview command."
    },
    "216": {
        "code": 216,
        "desc": "Failed reading retention database information",
        "first_action": "OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager",
        "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxmasterserver,verifythattheNetBackupDatabaseManager\n(bpdbm) process is running. On a Windows master server, verify that the\nNetBackup Database Manager service is running.\n■ For detailed troubleshooting information, create a debug log directory for bpdbm\non the master server.\nIncrease the logging level for nbpem by using the vxlogcfg command as\ndescribed in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs."
    },
    "217": {
        "code": 217,
        "desc": "Failed reading storage unit database information",
        "first_action": "OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)",
        "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess is running. On a Windows server, verify that the NetBackup Database\nManager service is running.\n■ TrytoviewthestorageunitconfigurationbyusingtheNetBackupadministration\ninterface.\n■ For detailed troubleshooting information, create debug logs for nbproxy and\nbpdbm on the master server and retry the operation. Check the resulting debug\nlogs. Also check the nbpem logs by using the vxlogview command.\nEnsure that the correct master server is specified for the connection."
    },
    "218": {
        "code": 218,
        "desc": "Failed reading policy database information",
        "first_action": "OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)",
        "full_action": "Do the following, as appropriate:\n■ OnaUNIXorLinuxserver,verifythattheNetBackupDatabaseManager(bpdbm)\nprocess is running. On a Windows server, verify that the NetBackup Database\nManager service is running.\n■ Try to view the policy configuration by using the NetBackup administration\ninterface.\n■ Fordetailedtroubleshootinginformation,createdebuglogdirectoriesfornbproxy\nand bpdbm on the master server and retry the operation. Check the resulting\ndebug logs. Also check the nbpem logs by using the vxlogview command.\nEnsure that the correct master server is specified for the connection."
    },
    "219": {
        "code": 219,
        "desc": "The required storage unit is unavailable",
        "first_action": "Verify that the schedule specifies the correct storage unit and the storage unit",
        "full_action": "Look in the Job Details window for the failed job.\n■ Verify that the schedule specifies the correct storage unit and the storage unit\nexists.\n■ Verifythatthefollowingdevicesarerunning:theMediaManagerdevicedaemon\n(ltid) (UNIX or Linux server) or the NetBackup Device Manager service\n(Windows server). Use bpps on UNIX and Linux and the Activity Monitor on\nWindows or the Services application in the Windows Control Panel.\n■ Verify the following attribute settings:\n■ For a disk storage unit, Maximum concurrent jobs is not set to 0.\n■ ForaMediaManagerstorageunit,theMaximumconcurrentdrivesattribute\nis not set to 0.\n■ If the storage unit is a tape, verify that at least one of the drives is in the UP\nstate. Use the Device Monitor.\n■ Verify that the robot number and host in the storage unit configuration match\nwhat is specified in the Media and Device Management device configuration.\n■ Verify that the master server can communicate with the bpcd process on the\nserver that has the storage unit.\n■ Verify that bpcd listens on the port for connections.\nOn a UNIX or Linux server where the storage unit is connected, if you run\nnetstat -a | grep bpcd,itshouldreturnsomethingsimilartothefollowing:\n*.bpcd *.* 0 0 0 0 LISTEN\nOn a Windows NetBackup server where the storage unit is connected, run\nnetstat -a to print several lines of output. If bpcd listens, one of those lines\nis similar to the following:\nTCP myhost:bpcd 0.0.0.0:0 LISTENING\n■ Check the nbrb and the mds logs by using the vxlogview command.\n■ If the cause of the problem is not obvious, perform some of the steps in the\nfollowing procedure:\nSee Resolving Network Communication Problems in the NetBackup\nTroubleshooting Guide."
    },
    "220": {
        "code": 220,
        "desc": "Database system error",
        "first_action": "Create a debug log directory for bpdbm. Increase the",
        "full_action": "Create a debug log directory for bpdbm. Increase the\nlogging level for the diagnostic and debug logs for nbemm.\nUse the vxlogcfg command as explained in the following topic:\nSee \"About unified logging\" in the NetBackup Logging Reference Guide.\nRetry the operation and check the resulting logs for information."
    },
    "221": {
        "code": 221,
        "desc": "Continue",
        "first_action": "Determine the cause of the status code that follows this",
        "full_action": "Determine the cause of the status code that follows this\none."
    },
    "222": {
        "code": 222,
        "desc": "Done",
        "first_action": "Determine the cause of the status code that follows this",
        "full_action": "Determine the cause of the status code that follows this\none."
    },
    "223": {
        "code": 223,
        "desc": "An invalid entry was encountered",
        "first_action": "Verify that all NetBackup software is at the same version",
        "full_action": "Verify that all NetBackup software is at the same version\nlevel and the command parameters are specified correctly. If neither of these is the\nproblem,obtaindetailedtroubleshootinginformationbycreatingabpdbmdebuglog\ndirectory. Then retry the operation. Check the resulting debug log."
    },
    "224": {
        "code": 224,
        "desc": "There was a conflicting specification",
        "first_action": "Verify that all NetBackup software is at the same version",
        "full_action": "Verify that all NetBackup software is at the same version\nlevel. If that is not the problem, obtain detailed troubleshooting information by\ncreating bpdbm and admin debug log directories. Then retry the operation. Check\nthe resulting debug logs."
    },
    "225": {
        "code": 225,
        "desc": "Text exceeded allowed length NetBackup status codes 231 NetBackup status codes",
        "first_action": "Verify that all NetBackup software is at the same version",
        "full_action": "Verify that all NetBackup software is at the same version\nlevel. If that is not the problem, create debug log directories for bpdbm and admin.\nThen, retry the operation and examine the resulting debug logs."
    },
    "226": {
        "code": 226,
        "desc": "The entity already exists",
        "first_action": "Correct your request and re-execute the command.",
        "full_action": "Correct your request and re-execute the command."
    },
    "227": {
        "code": 227,
        "desc": "No entity was found",
        "first_action": "Ensure that the appropriate plug-in is configured from the web UI.",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the appropriate plug-in is configured from the web UI.\n■ Ensure that the discovery of the asset is complete and the appropriate asset is\nvisible in the web UI."
    },
    "228": {
        "code": 228,
        "desc": "Unable to process request",
        "first_action": "Ifthisstatusinvolvesamediaserver,verifythatitsserverlistspecifiesthecorrect",
        "full_action": "Do the following, as appropriate:\n■ Ifthisstatusinvolvesamediaserver,verifythatitsserverlistspecifiesthecorrect\nmaster server. On a UNIX or Linux server, the master server is the first SERVER\nentry in the bp.conf file. On a Windows server, the master is designated on the\nServers tab in the Master Server Properties dialog box.\nSee \"Using the Host Properties window to access configuration settings\" in the\nNetBackup Troubleshooting Guide.\n■ For detailed troubleshooting information, create a bpdbm debug log directory\nand retry the operation. Then, check the resulting debug log."
    },
    "229": {
        "code": 229,
        "desc": "Events out of sequence - image inconsistency",
        "first_action": "Obtain detailed troubleshooting information by creating a",
        "full_action": "Obtain detailed troubleshooting information by creating a\ndebug log directory for bpdbm. Then, retry the operation, save the resulting debug\nlog, and contact Cohesity Technical Support."
    },
    "230": {
        "code": 230,
        "desc": "The specified policy does not exist in the configuration database",
        "first_action": "Correctyourparametersoroptionsandretrytheoperation.",
        "full_action": "Correctyourparametersoroptionsandretrytheoperation."
    },
    "231": {
        "code": 231,
        "desc": "Schedule windows overlap",
        "first_action": "Correct the schedule to eliminate the overlapping backup",
        "full_action": "Correct the schedule to eliminate the overlapping backup\nwindows."
    },
    "232": {
        "code": 232,
        "desc": "A protocol error has occurred",
        "first_action": "Create a debug log directory for bpdbm. Then, retry the",
        "full_action": "Create a debug log directory for bpdbm. Then, retry the\noperation, save the debug log, and contact Cohesity Technical Support."
    },
    "233": {
        "code": 233,
        "desc": "Premature eof encountered",
        "first_action": "During a restore, this status code means that tar (on the",
        "full_action": "During a restore, this status code means that tar (on the\nclient) received a stream of data that was not what it expected. If the restore is a\nnew configuration, verify that the tape drive is configured for variable mode.\nSee the NetBackup Device Configuration Guide.\nIf the communication failure is not due to an interrupt on a client system, save all\nerror information and contact Cohesity Technical Support."
    },
    "234": {
        "code": 234,
        "desc": "Communication interrupted",
        "first_action": "Save all of the error information and contact Cohesity",
        "full_action": "Save all of the error information and contact Cohesity\nTechnical Support."
    },
    "235": {
        "code": 235,
        "desc": "Inadequate buffer space",
        "first_action": "Verify that all NetBackup software is at the same version level. Update earlier",
        "full_action": "Do the following, as appropriate:\n■ Verify that all NetBackup software is at the same version level. Update earlier\nversions of NetBackup software.\n■ On UNIX and Linux, NetBackup servers and clients, check the\n/usr/openv/netbackup/bin/version file.\n■ On Windows NetBackup servers, check the\ninstall_path\\NetBackup\\version.txtfileortheAboutNetBackupitem\non the Help menu.\n■ On Microsoft Windows clients, check the About NetBackup item on the\nHelp menu.\n■ Iftheproblempersists,saveallerrorinformationandcontactCohesityTechnical\nSupport."
    },
    "236": {
        "code": 236,
        "desc": "The specified client does not exist in an active policy within the configuration database",
        "first_action": "Activate the required policy, correct the client name, or",
        "full_action": "Activate the required policy, correct the client name, or\nadd the client to a policy that meets your needs. After you make the correction,\nretry the operation."
    },
    "237": {
        "code": 237,
        "desc": "The specified schedule does not exist in an active policy in the configuration database NetBackup status codes 235 NetBackup status codes",
        "first_action": "Activate the required policy, correct the schedule name,",
        "full_action": "Activate the required policy, correct the schedule name,\nor create a schedule in a policy that meets your needs. After you make the\ncorrection, retry the operation."
    },
    "238": {
        "code": 238,
        "desc": "The database contains conflicting or erroneous entries",
        "first_action": "Obtain detailed troubleshooting information for bpdbm (on",
        "full_action": "Obtain detailed troubleshooting information for bpdbm (on\nUNIX and Linux) or the NetBackup Database Manager service (on Windows) by\ncreating a debug log directory for it. Then, retry the operation, save the resulting\ndebug log, and contact Cohesity Technical Support."
    },
    "239": {
        "code": 239,
        "desc": "The specified client does not exist in the specified policy",
        "first_action": "Correct the client name specification, specify a different",
        "full_action": "Correct the client name specification, specify a different\npolicy, or add the required client name to the policy. After you make the correction,\nretry the operation."
    },
    "240": {
        "code": 240,
        "desc": "No schedules of the correct type exist in this policy",
        "first_action": "Specify a different policy or create a schedule of the",
        "full_action": "Specify a different policy or create a schedule of the\nneeded type in the policy. After you make the correction, retry the operation."
    },
    "241": {
        "code": 241,
        "desc": "The specified schedule is the wrong type for this request",
        "first_action": "Specify only full or incremental schedules for manual",
        "full_action": "Specify only full or incremental schedules for manual\nbackups. If one does not exist in the policy, create one."
    },
    "242": {
        "code": 242,
        "desc": "Operation would cause an illegal duplication",
        "first_action": "Checktheerrorreportstodeterminethespecificduplication",
        "full_action": "Checktheerrorreportstodeterminethespecificduplication\nthat would occur. Correct the settings for the operation and retry it."
    },
    "243": {
        "code": 243,
        "desc": "The client is not in the configuration",
        "first_action": "Either correct the client name or add the client to the",
        "full_action": "Either correct the client name or add the client to the\nwanted policy."
    },
    "245": {
        "code": 245,
        "desc": "The specified policy is not of the correct client type",
        "first_action": "Retrytheoperationbyspecifyingapolicythatisthecorrect",
        "full_action": "Retrytheoperationbyspecifyingapolicythatisthecorrect\ntype for the client. If such a policy does not exist, create one."
    },
    "246": {
        "code": 246,
        "desc": "No active policies in the configuration database are of the correct client type",
        "first_action": "Createoractivateanappropriatepolicysotheuserbackup",
        "full_action": "Createoractivateanappropriatepolicysotheuserbackup\nrequest can be satisfied."
    },
    "247": {
        "code": 247,
        "desc": "The specified policy is not active",
        "first_action": "Activate the policy and retry the operation.",
        "full_action": "Activate the policy and retry the operation."
    },
    "248": {
        "code": 248,
        "desc": "There are no active policies in the configuration database",
        "first_action": "Activate the appropriate policy and retry the operation.",
        "full_action": "Activate the appropriate policy and retry the operation."
    },
    "249": {
        "code": 249,
        "desc": "The file list is incomplete",
        "first_action": "On the server, bptm, bpbrm, and bpdbm.",
        "full_action": "First,obtainadditionalinformationbycreatingdebuglogs.\nThen try to recreate the error. The debug logs to create are as follows:\n■ On the server, bptm, bpbrm, and bpdbm.\n■ On UNIX, Linux, and Windows clients, bpbkar.\n■ On other clients, bpcd."
    },
    "250": {
        "code": 250,
        "desc": "The image was not created with TIR information",
        "first_action": "Obtain detailed troubleshooting information by creating",
        "full_action": "Obtain detailed troubleshooting information by creating\ndebug logs for bptm or bpdbm on the server. Then, retry the operation and check\nthe resulting debug logs."
    },
    "251": {
        "code": 251,
        "desc": "The tir information is zero length",
        "first_action": "Check the policy file list and the exclude and include lists",
        "full_action": "Check the policy file list and the exclude and include lists\non the client to verify that the client has eligible files for backup. For example, this\nstatus code can appear if the exclude list on the client excludes all files.\nToobtaindetailedtroubleshootinginformation,createdebuglogsforbptmorbpdbm\non the server. Then, retry the operation and check the resulting debug logs."
    },
    "252": {
        "code": 252,
        "desc": "An extended error status has been encountered, check detailed status",
        "first_action": "To determine the actual error, examine the job details",
        "full_action": "To determine the actual error, examine the job details\ndisplay."
    },
    "253": {
        "code": 253,
        "desc": "The catalog image .f file has been archived",
        "first_action": "Refer to the catalog archiving help information to restore",
        "full_action": "Refer to the catalog archiving help information to restore\nthe archived catalog image .f files."
    },
    "254": {
        "code": 254,
        "desc": "Server name not found in the NetBackup configuration",
        "first_action": "Save all of the error information and contact Cohesity",
        "full_action": "Save all of the error information and contact Cohesity\nTechnical Support."
    },
    "256": {
        "code": 256,
        "desc": "Logic error encountered",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "257": {
        "code": 257,
        "desc": "Failed to get job data",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "258": {
        "code": 258,
        "desc": "Vault duplication was aborted by administrator request",
        "first_action": "Ensure that the abort request was intentional.",
        "full_action": "Ensure that the abort request was intentional."
    },
    "259": {
        "code": 259,
        "desc": "Vault configuration file not found",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "260": {
        "code": 260,
        "desc": "Failed to send signal",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "261": {
        "code": 261,
        "desc": "Vault internal error 261",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "262": {
        "code": 262,
        "desc": "Vault internal error 262",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "263": {
        "code": 263,
        "desc": "Session ID assignment failed",
        "first_action": "VerifythatthesessionIDthatisstoredinthesession.last",
        "full_action": "VerifythatthesessionIDthatisstoredinthesession.last\nfile is valid.\nUNIX and Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/session.last\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\session.last\nMake sure that the file system is not full and that no one has inadvertently edited\nthe session.last file. To correct the problem, store the highest session ID that\nwas assigned to a session for this Vault in the session.last file. If the problem\npersists, contact customer support and send the appropriate logs."
    },
    "265": {
        "code": 265,
        "desc": "Session ID file is empty or corrupt",
        "first_action": "Ensure that the session ID that is stored in the",
        "full_action": "Ensure that the session ID that is stored in the\nsession.last file is not corrupt. Make sure that the file system is not full and that\nno one has inadvertently edited the file. To correct the problem, store the highest\nsession ID that was assigned to a session for this Vault in the session.last file.\nIf the problem persists, contact customer support and send the appropriate logs."
    },
    "266": {
        "code": 266,
        "desc": "Cannot find robot, vault, or profile in the vault configuration",
        "first_action": "Rerunthecommandwiththecorrectprofile_nameortriplet",
        "full_action": "Rerunthecommandwiththecorrectprofile_nameortriplet\nrobot_name/vault_name/profile_name."
    },
    "267": {
        "code": 267,
        "desc": "Cannot find the local host name",
        "first_action": "Issuea hostnamecommandattheOScommandprompt.",
        "full_action": "Issuea hostnamecommandattheOScommandprompt.\nSeethehostname(orgethostbyname)manpageforanexplanationoftheconditions\nthat would cause it to fail.\nSee the OS System Administrator’s Guide for more information."
    },
    "268": {
        "code": 268,
        "desc": "The vault session directory is either missing or inaccessible",
        "first_action": "Make sure that you are running on the master server",
        "full_action": "Make sure that you are running on the master server\nwhere Vault is installed and configured. Also ensure that no one accidentally\nremoved the sessions directory or changed permission on the directory path so it\nis inaccessible to the Vault job."
    },
    "269": {
        "code": 269,
        "desc": "No vault session ID was found",
        "first_action": "EitherspecifyadifferentprofilefortheVaultjobsthatwere",
        "full_action": "EitherspecifyadifferentprofilefortheVaultjobsthatwere\nrun or exit vltopmenu and run a Vault job for the specific profile. Then rerun\nvltopmenu and select the profile."
    },
    "270": {
        "code": 270,
        "desc": "Unable to obtain process id, getpid failed",
        "first_action": "Look at the system log for any unusual system problems.",
        "full_action": "Look at the system log for any unusual system problems.\nWait a while and then try running the process again when system resources are\nfreed up."
    },
    "271": {
        "code": 271,
        "desc": "Vault XML version mismatch",
        "first_action": "Enable logging, start nbvault, and then examine the",
        "full_action": "Enable logging, start nbvault, and then examine the\nnbvault logs to determine the cause of the failure. If the upgrade process fails\nagain, contact your customer support representative.\nThe following are the locations of the nbvault logs:\nUNIX and Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault"
    },
    "272": {
        "code": 272,
        "desc": "Execution of a vault notify script failed",
        "first_action": "Ensurethatthenotifyscriptisexecutableandrunswithout",
        "full_action": "Ensurethatthenotifyscriptisexecutableandrunswithout\nerrors. You must debug the script by running it manually to eliminate coding errors."
    },
    "273": {
        "code": 273,
        "desc": "Invalid job id",
        "first_action": "Specify the job ID of the active Vault job that is currently",
        "full_action": "Specify the job ID of the active Vault job that is currently\nat the duplication step or operation."
    },
    "274": {
        "code": 274,
        "desc": "No profile was specified",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "275": {
        "code": 275,
        "desc": "A session is already running for this vault",
        "first_action": "Start the Vault session after the previous session has",
        "full_action": "Start the Vault session after the previous session has\ncompleted."
    },
    "276": {
        "code": 276,
        "desc": "Invalid session ID",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "277": {
        "code": 277,
        "desc": "Unable to print reports",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "278": {
        "code": 278,
        "desc": "Unable to collect pre eject information from the API",
        "first_action": "Ensure that all Media and Device Management daemons",
        "full_action": "Ensure that all Media and Device Management daemons\nare running or the robot is live and up."
    },
    "279": {
        "code": 279,
        "desc": "Eject process is complete",
        "first_action": "None",
        "full_action": "None"
    },
    "280": {
        "code": 280,
        "desc": "There are no volumes to eject",
        "first_action": "Ensurethatthemediatobeejectedarenotremovedfrom",
        "full_action": "Ensurethatthemediatobeejectedarenotremovedfrom\nthe library manually."
    },
    "281": {
        "code": 281,
        "desc": "Vault core error",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "282": {
        "code": 282,
        "desc": "Cannot connect to nbvault server",
        "first_action": "To determine the reason for failure, examine the logs for",
        "full_action": "To determine the reason for failure, examine the logs for\nthe service or services that are down and the operating system logs (EventLog on\nWindows).Restarttheserviceorservicesthataredownafterresolvingtheproblem.\nThe following are the locations of the nbvault logs:\nUNIX and Linux: /usr/openv/netbackup/logs/nbvault/\nWindows: install_path\\NetBackup\\logs\\nbvault"
    },
    "283": {
        "code": 283,
        "desc": "Error(s) occurred during vault report generation",
        "first_action": "Check logs for details of the failure.",
        "full_action": "Check logs for details of the failure."
    },
    "284": {
        "code": 284,
        "desc": "Error(s) occurred during vault report distribution",
        "first_action": "Check logs for details of the failure.",
        "full_action": "Check logs for details of the failure."
    },
    "285": {
        "code": 285,
        "desc": "Unable to locate vault directory",
        "first_action": "The Vault directory is created when the Vault package",
        "full_action": "The Vault directory is created when the Vault package\nis installed on the master server. Ensure that the Vault job or command is started\nas root on the master server. Ensure that the Vault directory was not removed\ninadvertently or made inaccessible to the root user."
    },
    "286": {
        "code": 286,
        "desc": "Vault internal error",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "287": {
        "code": 287,
        "desc": "Vault eject failed",
        "first_action": "Ensure that the Media and Device Management services",
        "full_action": "Ensure that the Media and Device Management services\nare running, the robot is up, and empty slots are available in the media access port\n(MAP)."
    },
    "288": {
        "code": 288,
        "desc": "Vault eject partially succeeded",
        "first_action": "Ensure that the media are not loaded in a drive and in",
        "full_action": "Ensure that the media are not loaded in a drive and in\nuse by other processes. Ensure that empty slots are available in the media access\nport (MAP)."
    },
    "289": {
        "code": 289,
        "desc": "Cannot consolidate reports of sessions from container and slot-based vaults",
        "first_action": "Change the report consolidation so that only reports for",
        "full_action": "Change the report consolidation so that only reports for\none type of vault operation are consolidated, either slots or containers."
    },
    "290": {
        "code": 290,
        "desc": "One or more errors detected during eject processing",
        "first_action": "Manually remove any media that are in the off-site Vault volume group but are",
        "full_action": "For detailed information, review the Vault debug log in\nthe following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nAfter the problem is identified and corrected, the media that were not ejected may\nneed to be ejected manually by means of vlteject or vltopmenu.\nThis error often indicates that the media were left in the off-site Vault volume group\nbut physically reside in the robot or the robotic MAP.\nTo solve this problem, do one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into the robotic volume group. Then rerun the Vault\nsessions that failed."
    },
    "291": {
        "code": 291,
        "desc": "Number of media has exceeded capacity of MAP; must perform manual eject using vltopmenu or vlteject",
        "first_action": "Usevltopmenutomanuallyejectthemediafortheselected",
        "full_action": "Usevltopmenutomanuallyejectthemediafortheselected\nprofile and session ID. The vltopmenu option lets you eject the selected media, a\nMAP-full (or less) at a time."
    },
    "292": {
        "code": 292,
        "desc": "Eject process failed to start",
        "first_action": "For detailed information about the problem, review the",
        "full_action": "For detailed information about the problem, review the\nVault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nUse the robtest utility to ensure that you can communicate with the Vault robotic\nlibrary. After the problem is resolved, rerun the Vault session, vlteject command,\nor vltopmenu command."
    },
    "293": {
        "code": 293,
        "desc": "Eject process has been aborted",
        "first_action": "Manually remove any media that are in the off-site Vault volume group but are",
        "full_action": "For detailed information about why the process was\ncanceled, review the Vault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux:\n/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:\ninstall_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nThis error often indicates that the media were left in the off-site Vault volume group\nbut physically reside in the robot or the robotic MAP.\nTo solve this problem, do one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robotic library.\n■ Inventorytheroboticlibrary.Aninventoryputsanymediathatwereintheoff-site\nVault volume group back into the robotic volume group. Then, rerun the Vault\nsessions that failed."
    },
    "294": {
        "code": 294,
        "desc": "Vault catalog backup failed",
        "first_action": "Review the Vault debug log in the following directory for",
        "full_action": "Review the Vault debug log in the following directory for\ndetailed information about why the process failed:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo find the actual problem that caused the catalog backup (bpbackupdb) to fail,\nreview the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nCorrect the problem and rerun the Vault job."
    },
    "295": {
        "code": 295,
        "desc": "Eject process could not obtain information about the robot",
        "first_action": "Fordetailedinformationaboutwhytheprocessfails,review",
        "full_action": "Fordetailedinformationaboutwhytheprocessfails,review\nthe Vault debug log in the following directory:\nUNIX and Linux: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nCorrect the error and rerun the Vault session, vlteject command, or vltopmenu\neject command."
    },
    "296": {
        "code": 296,
        "desc": "Process called but nothing to do",
        "first_action": "This error is an informative one and does not require any",
        "full_action": "This error is an informative one and does not require any\naction."
    },
    "297": {
        "code": 297,
        "desc": "All volumes are not available to eject",
        "first_action": "Remove or correct the defective media ID from the",
        "full_action": "Remove or correct the defective media ID from the\nvlt_ejectlist_notify script and rerun the Vault session. If the bad media ID is\nin the MAP or a drive or in transit, something is misconfigured."
    },
    "298": {
        "code": 298,
        "desc": "The library is not ready to eject volumes",
        "first_action": "Wait until the robotic library can support the eject action",
        "full_action": "Wait until the robotic library can support the eject action\nand rerun the Vault session, vlteject command, or vltopmenu command."
    },
    "299": {
        "code": 299,
        "desc": "There is no available MAP for ejecting",
        "first_action": "Wait until the robotic library’s MAP is available for use",
        "full_action": "Wait until the robotic library’s MAP is available for use\nand rerun the Vault session, vlteject command, or vltopmenu command."
    },
    "300": {
        "code": 300,
        "desc": "Vmchange eject verify not responding",
        "first_action": "Review the Vault debug log in the following directory for detailed information",
        "full_action": "Do the following, as appropriate:\n■ Review the Vault debug log in the following directory for detailed information\nabout why the process failed:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\n■ Alsoreviewthesummary.logineachofthesidxxxdirectoriesthathadproblems:\nUNIX:/usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows:install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nThis error often indicates that the media were left in the off-site Vault volume\ngroupbutphysicallyresideintherobotortheroboticMAP.Tosolvethisproblem,\ndo one of the following:\n■ Manually remove any media that are in the off-site Vault volume group but are\nstill in the robot.\n■ Inventory the robot. An inventory puts any media that were in the off-site Vault\nvolumegroupbackintotheroboticvolumegroup.Then,reruntheVaultsessions\nthat failed."
    },
    "301": {
        "code": 301,
        "desc": "Vmchange api_eject command failed",
        "first_action": "Review the Vault debug log in the following directory for",
        "full_action": "Review the Vault debug log in the following directory for\ndetailed information about why the process failed:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nWhen the problem is resolved, rerun the Vault session, vlteject command, or\nvltopmenu command."
    },
    "302": {
        "code": 302,
        "desc": "Errorencounteredtryingbackupofcatalog(multipletapecatalogbackup)",
        "first_action": "For the actual error that caused the failure, review the",
        "full_action": "For the actual error that caused the failure, review the\nVault debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nReview the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nIn addition, review the admin debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/admin\nWindows: install_path\\NetBackup\\logs\\admin\nCorrect the error and rerun the Vault session."
    },
    "303": {
        "code": 303,
        "desc": "Error encountered executing Media Manager command",
        "first_action": "For the actual error that caused the command to fail,",
        "full_action": "For the actual error that caused the command to fail,\nreview the Vault debug log in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where xxx is the session ID)\nTry running the command (with the same arguments as in the log file) to see the\nactualerror.EnsurethattheMediaandDeviceManagementdaemonsarerunning.\nAlso ensure that the robot is functional and you can communicate with it (for\nexample, inventory the robot through the GUI)."
    },
    "304": {
        "code": 304,
        "desc": "Specified profile not found",
        "first_action": "Rerun the Vault command with a profile name that is",
        "full_action": "Rerun the Vault command with a profile name that is\ndefined in the Vault configuration."
    },
    "305": {
        "code": 305,
        "desc": "Multiple profiles exist",
        "first_action": "Rerun the Vault command with the triplet",
        "full_action": "Rerun the Vault command with the triplet\nrobot_name/vault_name/profile_name. The triplet uniquely identifies the profile in\nyour Vault configuration."
    },
    "306": {
        "code": 306,
        "desc": "Vault duplication partially succeeded",
        "first_action": "Check the Vault logs in the vault directory and the",
        "full_action": "Check the Vault logs in the vault directory and the\nbpduplicate logs in the admin directory for the cause of the failure. These log\ndirectories are located at /usr/openv/netbackup/logs on UNIX and\ninstalled-dir\\NetBackup\\logs\\ on Windows."
    },
    "307": {
        "code": 307,
        "desc": "Eject process has already been run for the requested Vault session",
        "first_action": "Rerun vlteject for another session ID for which media",
        "full_action": "Rerun vlteject for another session ID for which media\nhas not been ejected."
    },
    "308": {
        "code": 308,
        "desc": "No images duplicated",
        "first_action": "For more information, review the Vault debug log in the",
        "full_action": "For more information, review the Vault debug log in the\nfollowing directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nAlso review the summary.log in each of the sidxxx directories that had problems:\nUNIX: /usr/openv/netbackup/vault/sessions/<vault_name/>sidxxx\nWindows: install_path\\NetBackup\\vault\\sessions\\vault_name\\sidxxx\n(where vault_name is the name of the vault, and xxx is the session ID)\nLook for the log entry that gives the total number of images processed. A common\ncause of failure is a lack of resources, such as no more media available in the\nspecified pools for duplication. Correct the problem and rerun the Vault job. Note\nthat the NetBackup scheduler retries a Vault job that terminates with this error.\nReview the admin debug log for duplicate entries and the bptm debug log."
    },
    "309": {
        "code": 309,
        "desc": "Report requested without eject being run",
        "first_action": "Rerun vlteject or vltopmenu to eject the media for the session before you",
        "full_action": "Perform one of these actions:\n■ Rerun vlteject or vltopmenu to eject the media for the session before you\ngenerate the reports.\n■ Reconfigure the profile to allow the eject step to be performed when the next\nVault session for this profile runs.\n■ Disable the report generation in the profile for the reports that require media to\nbe ejected."
    },
    "310": {
        "code": 310,
        "desc": "Updating of Media Manager database failed",
        "first_action": "To find the root cause of the error, review the Vault debug",
        "full_action": "To find the root cause of the error, review the Vault debug\nlogs in the following directory:\nUNIX: /usr/openv/netbackup/logs/vault\nWindows: install_path\\NetBackup\\logs\\vault\nTo fix the issue may involve making configuration changes."
    },
    "311": {
        "code": 311,
        "desc": "Iron Mountain Report is already created for this session",
        "first_action": "None. This report cannot be generated again.",
        "full_action": "None. This report cannot be generated again."
    },
    "312": {
        "code": 312,
        "desc": "Invalid container database entry",
        "first_action": "Togetthelinenumberofaninvalidrecordinthecontainer",
        "full_action": "Togetthelinenumberofaninvalidrecordinthecontainer\ndatabase, read the log file under the directory netbackup/logs/vault. Be aware\nthat a Vault log may not exist unless the directory netbackup/logs/vault existed\nbefore the error occurred. Open the container database file cntrDB and correct that\ninvalid entry. Note that this error occurs every time Vault reads this entry in cntrDB\nuntil either this invalid entry is deleted or it is corrected."
    },
    "313": {
        "code": 313,
        "desc": "Container does not exist in container database",
        "first_action": "Verifythatyouputsomemediaintothiscontainerbyusing",
        "full_action": "Verifythatyouputsomemediaintothiscontainerbyusing\nthe vltcontainers command. Verify that you did not delete it by using the\nvltcontainers -delete command."
    },
    "314": {
        "code": 314,
        "desc": "Container database truncate operation failed",
        "first_action": "Seethelogfileunderthedirectorynetbackup/logs/vault",
        "full_action": "Seethelogfileunderthedirectorynetbackup/logs/vault\nfor more details. Be aware that a log file is not created unless the\nnetbackup/logs/vault directory has already been created."
    },
    "315": {
        "code": 315,
        "desc": "Failed appending to container database",
        "first_action": "Read the relevant log file under the directory",
        "full_action": "Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created."
    },
    "316": {
        "code": 316,
        "desc": "Container_id is not unique in container database",
        "first_action": "Verify that you have specified the correct container ID.",
        "full_action": "Verify that you have specified the correct container ID."
    },
    "317": {
        "code": 317,
        "desc": "Container database close operation failed",
        "first_action": "Read the relevant log file under the directory",
        "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created."
    },
    "318": {
        "code": 318,
        "desc": "Container database lock operation failed",
        "first_action": "Read the relevant log file under the directory",
        "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file not created.\nIf some other Vault operation uses the container database and locks it, wait until\nthat operation completes and the container database is unlocked."
    },
    "319": {
        "code": 319,
        "desc": "Container database open operation failed",
        "first_action": "Read the relevant log file under the directory",
        "full_action": "Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created."
    },
    "320": {
        "code": 320,
        "desc": "The specified container is not empty",
        "first_action": "Inject all of the media that it contains into a robot.",
        "full_action": "Verify that you have specified the correct container ID.\nIf you still want to delete this container from the container database, first empty it\nby doing either of the following:\n■ Inject all of the media that it contains into a robot.\n■ Clear the Vault container ID fields for these media from the EMM database by\nusing vmchange -vlt cid with a value of -.\nTry to delete the container again."
    },
    "321": {
        "code": 321,
        "desc": "Container cannot hold any media from the specified robot",
        "first_action": "Verify that you specified the correct container ID and",
        "full_action": "Verify that you specified the correct container ID and\nmedia IDs. Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created."
    },
    "322": {
        "code": 322,
        "desc": "Cannot find vault in vault configuration file",
        "first_action": "Verify that you specified the correct Vault name. Read",
        "full_action": "Verify that you specified the correct Vault name. Read\nthe relevant log file under the directory netbackup/logs/vault for more details.\nBe aware that if this directory does not already exist, a log file is not created."
    },
    "323": {
        "code": 323,
        "desc": "Cannot find robot in vault configuration file NetBackup status codes 264 NetBackup status codes",
        "first_action": "Verify that you specified the correct robot number. Read",
        "full_action": "Verify that you specified the correct robot number. Read\nthe relevant log file under the directory netbackup/logs/vault for more details.\nBe aware that if this directory does not already exist, a log file is not created."
    },
    "324": {
        "code": 324,
        "desc": "Invalid data found in retention map file for duplication",
        "first_action": "Check the entries in the retention_mappings file.",
        "full_action": "Check the entries in the retention_mappings file."
    },
    "325": {
        "code": 325,
        "desc": "Unable to find policy/schedule for image using retention mapping",
        "first_action": "Verify whether or not the backup policy or the schedule",
        "full_action": "Verify whether or not the backup policy or the schedule\nthat created the image still exists. If either one or both do not exist, the image is\nnot duplicated through the Vault profile."
    },
    "326": {
        "code": 326,
        "desc": "Specified file contains no valid entry",
        "first_action": "Verifythateachentryin thespecifiedfiledoesnotexceed",
        "full_action": "Verifythateachentryin thespecifiedfiledoesnotexceed\nthe string size limit: six characters for media IDs and 16 characters for the numeric\nequivalent of barcodes. Correct the invalid entries in the specified file and try the\nsame operation again. Read the relevant log file under the directory\ninstall_path/netbackup/logs/vault for more details. Be aware that if this\ndirectory does not already exist, a log file is not created."
    },
    "327": {
        "code": 327,
        "desc": "No media ejected for the specified vault session",
        "first_action": "Verify that you have specified the correct combination of",
        "full_action": "Verify that you have specified the correct combination of\nVault name and session ID. Verify that the specified Vault session has ejected at\nleast one piece of media. Read the relevant log file under the directory\nnetbackup/logs/vault for more details. Be aware that if this directory does not\nalready exist, a log file is not created."
    },
    "328": {
        "code": 328,
        "desc": "Invalid container ID",
        "first_action": "Verify that the container ID does not contain any space",
        "full_action": "Verify that the container ID does not contain any space\ncharacters, and that the string size is a maximum of 29 characters long."
    },
    "329": {
        "code": 329,
        "desc": "Invalid recall status",
        "first_action": "Verify that the recall status is either 1 or 0.",
        "full_action": "Verify that the recall status is either 1 or 0."
    },
    "330": {
        "code": 330,
        "desc": "Invalid database host",
        "first_action": "VerifythattheEMMdatabasehostnamedoesnotcontain",
        "full_action": "VerifythattheEMMdatabasehostnamedoesnotcontain\nanyspacecharacters,andthatthestringsizeisamaximumof256characterslong."
    },
    "331": {
        "code": 331,
        "desc": "Invalid container description",
        "first_action": "Verify that the string size of the container description is a",
        "full_action": "Verify that the string size of the container description is a\nmaximum of 25 characters long."
    },
    "332": {
        "code": 332,
        "desc": "Error getting information from EMM database",
        "first_action": "OnUNIX,verifythattheNetBackupVolumeManagerdaemon(vmd)isrunning.",
        "full_action": "Do the following, as appropriate:\n■ OnUNIX,verifythattheNetBackupVolumeManagerdaemon(vmd)isrunning.\nOn Windows, verify that the NetBackup Volume Manager service is running.\n■ See the process-specific error log directory for more details.\nUNIX: /usr/openv/netbackup/logs/process_name\nWindows: install_path\\NetBackup\\logs\\process_name\nFor example, if you get this error while running a Vault command (such as\nvltcontainers or vltopmenu), look at the following logs to learn why:\n/usr/openv/netbackup/logs/vault\nNote: The log file cannot be created unless the appropriate log directory (for\nexample, /usr/openv/netbackup/logs/vault) is already created."
    },
    "333": {
        "code": 333,
        "desc": "Error getting information from media manager command line",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "334": {
        "code": 334,
        "desc": "Unable to receive response from robot; robot not ready.",
        "first_action": "Ensure that all Media and Device Management daemons",
        "full_action": "Ensure that all Media and Device Management daemons\nare running or the robot is live and up."
    },
    "335": {
        "code": 335,
        "desc": "Failure occurred while suspending media for eject",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "336": {
        "code": 336,
        "desc": "Failure occurred while updating session information",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "337": {
        "code": 337,
        "desc": "Failure occurred while updating the eject.mstr file",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "338": {
        "code": 338,
        "desc": "Vault eject timed out",
        "first_action": "Remove the media from the MAP if it is already full.",
        "full_action": "Do the following, as appropriate:\n■ Remove the media from the MAP if it is already full.\n■ Make sure that the MAP is closed properly."
    },
    "339": {
        "code": 339,
        "desc": "Vault configuration file format error",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "340": {
        "code": 340,
        "desc": "Vault configuration tag not found",
        "first_action": "If the Vault's operation is affected, contact customer",
        "full_action": "If the Vault's operation is affected, contact customer\nsupport and send the appropriate logs."
    },
    "341": {
        "code": 341,
        "desc": "Vault configuration serialization failed",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "342": {
        "code": 342,
        "desc": "Cannot modify - stale view",
        "first_action": "Check the latest attributes of the robot or vault or profile.",
        "full_action": "Check the latest attributes of the robot or vault or profile.\nTo check, refresh the view in the NetBackup Administration Console or retrieve\nthe attributes in the Vault Administration menu user interface again. Then retry\nthe operation."
    },
    "343": {
        "code": 343,
        "desc": "Robot already exists",
        "first_action": "Refresh the view in the NetBackup Administration",
        "full_action": "Refresh the view in the NetBackup Administration\nConsoleor retrievetheattributesin theVaultAdministrationmenu user interface\nagain to see the robot."
    },
    "344": {
        "code": 344,
        "desc": "Vault already exists",
        "first_action": "Choose a different name for the vault.",
        "full_action": "Choose a different name for the vault."
    },
    "345": {
        "code": 345,
        "desc": "Profile already exists",
        "first_action": "Choose a different name for the profile.",
        "full_action": "Choose a different name for the profile."
    },
    "346": {
        "code": 346,
        "desc": "Duplicate MAP",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "347": {
        "code": 347,
        "desc": "Vault configuration cache not initialized",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "348": {
        "code": 348,
        "desc": "Specified report does not exist",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs."
    },
    "349": {
        "code": 349,
        "desc": "Incorrect catalog backup policy",
        "first_action": "Verify that you specified a catalog backup policy for the",
        "full_action": "Verify that you specified a catalog backup policy for the\ncatalog backup in the Vault profile and that the policy is of type NBU-Catalog."
    },
    "350": {
        "code": 350,
        "desc": "Incorrect vault catalog backup schedule",
        "first_action": "VerifythatyouspecifiedaVaultCatalogBackupschedule",
        "full_action": "VerifythatyouspecifiedaVaultCatalogBackupschedule\nfor the catalog backup in the Vault profile. Also verify that the schedule is of type\nVault Catalog Backup."
    },
    "351": {
        "code": 351,
        "desc": "All configured vault steps failed",
        "first_action": "Forduplicationandcatalogbackupsteps,usetheActivity",
        "full_action": "Forduplicationandcatalogbackupsteps,usetheActivity\nMonitor to check the status of the respective jobs that Vault started. For Eject step\nstatus, check the Detailed Status tab of the Job Details dialog box for the Vault\njob."
    },
    "400": {
        "code": 400,
        "desc": "Server Group Type is Invalid",
        "first_action": "Select a valid server group type: MediaSharing, or AltServerRestore.",
        "full_action": "Do the following, as appropriate:\n■ Select a valid server group type: MediaSharing, or AltServerRestore.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the logs for nbemm (originator ID 111) which uses\nunified logging."
    },
    "401": {
        "code": 401,
        "desc": "Server Group Already Exists",
        "first_action": "Verify that the specified server group name is not in use.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified server group name is not in use.\n■ Create the server group by specifying a name that is not currently in use.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging."
    },
    "402": {
        "code": 402,
        "desc": "Server Group Already Exists with a different type",
        "first_action": "Verify that the specified server group name is not in use.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified server group name is not in use.\n■ Try to create the server group by specifying a name that is not currently in use.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging."
    },
    "403": {
        "code": 403,
        "desc": "Server Group Active State is not valid",
        "first_action": "Valid server group states are: ACTIVE and INACTIVE",
        "full_action": "Do the following, as appropriate:\n■ Valid server group states are: ACTIVE and INACTIVE\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator ID 111), which uses\nunified logging."
    },
    "404": {
        "code": 404,
        "desc": "Server Group does not exist",
        "first_action": "Verify that the specified media is correct.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified media is correct.\n■ Verify the media ownership.\n■ Verify that the server group exists.\n■ Verify that the server where the operation is performed is a member of the\nowning server group. If not, try the operation from a server that is a member of\nthe server group.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging."
    },
    "405": {
        "code": 405,
        "desc": "Member’s server type not compatible with Server Group",
        "first_action": "The Media Sharing server group can contain the following types of servers:",
        "full_action": "Do the following, as appropriate:\n■ The Media Sharing server group can contain the following types of servers:\nMaster, Media, NDMP, and cluster.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging."
    },
    "406": {
        "code": 406,
        "desc": "The computer specified is not a member of the server group specified",
        "first_action": "Verify that the specified media is correct.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified media is correct.\n■ Verify the media ownership.\n■ Verify that the server where the operation is performed is a member of the\nowning server group. If not, try the operation from a server that is a member of\nthe server group.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich use unified logging."
    },
    "407": {
        "code": 407,
        "desc": "Member’s NetBackup version not compatible with Server Group",
        "first_action": "EnsurethateachmemberserverhasavalidNetBackupversionforthespecified",
        "full_action": "Do the following, as appropriate:\n■ EnsurethateachmemberserverhasavalidNetBackupversionforthespecified\nserver group type.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformationcanbefoundinthelogfornbemm(originatorIDs111and143),which\nuses unified logging."
    },
    "408": {
        "code": 408,
        "desc": "Server Group is in use",
        "first_action": "Ensure that the server group is not the owner of any media by running",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the server group is not the owner of any media by running\nbpmedialist -owner group_name from the master server.\n■ For detailed troubleshooting information, create the admin debug log directory\nand retry the operation. Check the resulting debug logs. Additional debug\ninformation can be found in the log for nbemm (originator IDs 111 and 143),\nwhich uses unified logging."
    },
    "409": {
        "code": 409,
        "desc": "Member already exists in server group",
        "first_action": "Ensure that the server group member that you add does not already exist in the",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the server group member that you add does not already exist in the\ngroup.\n■"
    },
    "410": {
        "code": 410,
        "desc": "A backup host pool with this name already exists.",
        "first_action": "Use a unique name for the backup host pool.",
        "full_action": "Use a unique name for the backup host pool."
    },
    "411": {
        "code": 411,
        "desc": "The backup host pool group state is not active.",
        "first_action": "While creating a backup host pool, provide -grpstate",
        "full_action": "While creating a backup host pool, provide -grpstate\nACTIVE as the parameter value."
    },
    "412": {
        "code": 412,
        "desc": "The backup host pool does not exist.",
        "first_action": "Usethenbsvrgrp -listcommandtocheckifthebackup",
        "full_action": "Usethenbsvrgrp -listcommandtocheckifthebackup\nhost pool exists."
    },
    "413": {
        "code": 413,
        "desc": "The host entry in the backup host pool already exists.",
        "first_action": "The specified host is already a part of the backup host",
        "full_action": "The specified host is already a part of the backup host\npool. No user action is required."
    },
    "501": {
        "code": 501,
        "desc": "You are not authorized to use this application.",
        "first_action": "Check the auth.conf file on the host that is specified in",
        "full_action": "Check the auth.conf file on the host that is specified in\nthe NetBackup Java login dialog box for the proper authorization. If the auth.conf\nfile does not exist, it must be created with the proper entry for this user name. More\ndetails on the auth.conf file are available.\nSee NetBackup Administrator’s Guide, Volume I."
    },
    "502": {
        "code": 502,
        "desc": "Noauthorizationentryexistsintheauth.conffileforusernameusername. None of the NetBackup Java applications are available to you.",
        "first_action": "Check the auth.conf file on the computer (host name)",
        "full_action": "Check the auth.conf file on the computer (host name)\nspecified in the NetBackup Java logon dialog box for the proper authorization. If\nthefiledoesnotexist,createitwiththeproperentryforthisusername.Moredetails\non the auth.conf file are available.\nSee NetBackup Administrator’s Guide, Volume I."
    },
    "503": {
        "code": 503,
        "desc": "Invalid user name.",
        "first_action": "For UNIX hosts: the user name must be a valid user name in the passwd file on",
        "full_action": "Do the following, as appropriate:\n■ For UNIX hosts: the user name must be a valid user name in the passwd file on\nthe host that is specified in the logon dialog box.\n■ For Windows hosts: refer to the LogonUser function in the section titled\nClient/Server Access Control Functions of the Windows Platform Software\nDeveloper’s Kit to determine the required privileges."
    },
    "504": {
        "code": 504,
        "desc": "Incorrect password.",
        "first_action": "Enter the correct password.",
        "full_action": "Do the following, as appropriate:\n■ Enter the correct password.\n■ On Windows hosts: The exact error can be found in the bpjava-msvc log file.\nFormoredetails,refertotheLogonUserfunctioninthesectionClient/ServerAccess\nControl Functions of the Windows Platform Software Developer’s Kit."
    },
    "505": {
        "code": 505,
        "desc": "Cannot connect to the NetBackup Java authentication service on host on the configured port - (port_number). Check the log file for more details.",
        "first_action": "On UNIX, compare the bpjava-msvc entry in the /etc/services file with the",
        "full_action": "Do the following, as appropriate:\n■ On UNIX, compare the bpjava-msvc entry in the /etc/services file with the\nBPJAVA_PORT entry in the /usr/openv/java/nbj.conf file\nOn Windows, compare the bpjava-msvc entry in the\n%systemroot%\\system32\\drivers\\etc\\services file with the\ninstall_path\\java\\setconf.bat file (Windows). The entries must match.\n■ Ensure that no other application uses the port that is configured for the\nNetBackup Java interface."
    },
    "506": {
        "code": 506,
        "desc": "Cannot connect to the NetBackup Java user service on host on port port_number. If successfully logged in before, retry your last operation. Check the log file for more details.",
        "first_action": "Restart the NetBackup Java interface and log in again.",
        "full_action": "Do the following, as appropriate:\n■ Restart the NetBackup Java interface and log in again.\n■ If the problem persists, enable detailed debug logging.\n■ Restart the NetBackup Java interface and examine the logs."
    },
    "507": {
        "code": 507,
        "desc": "SocketconnectiontotheNetBackupJavauserservicehasbeenbroken. Retry your last operation. Check the log file for more details.",
        "first_action": "Retry the last operation.",
        "full_action": "Do the following, as appropriate:\n■ Retry the last operation.\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ Iftheproblemstillpersists,setthedebugloggingformediamanagertoahigher\nlevel.\n■ Restart the NetBackup Java interface and examine the logs.\nNote: You may have network or system problems unrelated to NetBackup."
    },
    "508": {
        "code": 508,
        "desc": "Cannot write file.",
        "first_action": "Retrievethespecificdetailsfromtheuserservicelogfiles.",
        "full_action": "Retrievethespecificdetailsfromtheuserservicelogfiles.\nSet the debug logging for media manager to a higher level."
    },
    "509": {
        "code": 509,
        "desc": "Cannot execute program.",
        "first_action": "If the problem persists, restart the NetBackup Java interface and try again.",
        "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting debug logging to a higher level\" in the NetBackup Logging\nReference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, you can retrieve the details from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files."
    },
    "510": {
        "code": 510,
        "desc": "File already exists: file_name",
        "first_action": "Removethefile,whichcanbeidentifiedintheuserservice",
        "full_action": "Removethefile,whichcanbeidentifiedintheuserservice\nlog files.\nSee \"Troubleshooting error messages in the NetBackup Administration Console\"\nin the NetBackup Logging Reference Guide."
    },
    "511": {
        "code": 511,
        "desc": "NetBackup Java application server interface error.",
        "first_action": "If the problem persists, restart the NetBackup Java interface and try again.",
        "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files."
    },
    "512": {
        "code": 512,
        "desc": "Internal error - a bad status packet was returned by NetBackup Java application server that did not contain an exit status code.",
        "first_action": "If the problem persists, restart the NetBackup Java interface and try again.",
        "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nThe error is probably the result of a system resource issue. When detailed debug\nlogging is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files."
    },
    "513": {
        "code": 513,
        "desc": "Bpjava-msvc: the client is not compatible with this server version (server_version).",
        "first_action": "Log in to a different NetBackup remote host.",
        "full_action": "Do the following, as appropriate:\n■ Log in to a different NetBackup remote host.\n■ Upgrade the NetBackup software on either of the following: the computer that\nis specified in the logon dialog box or the local host where you started the\nNetBackup Java interface."
    },
    "514": {
        "code": 514,
        "desc": "NetBackup Java: bpjava-msvc is not compatible with this application version (application_version). You may try logon to a different NetBackup host or exittheapplication.TheremoteNetBackuphosthastobeconfiguredwiththesame version of NetBackup as the host you started the application on.",
        "first_action": "Log in to a different NetBackup remote host.",
        "full_action": "Do the following, as appropriate:\n■ Log in to a different NetBackup remote host.\n■ Upgrade the NetBackup software on either of the following: the specified\ncomputer in the logon dialog box or the local host where you started the\nNetBackup Java interface."
    },
    "516": {
        "code": 516,
        "desc": "Couldnotrecognizeorinitializetherequestedlocale-(locale_NetBackup Java_was_started_in).",
        "first_action": "On the specified host in the NetBackup Java logon dialog",
        "full_action": "On the specified host in the NetBackup Java logon dialog\nbox, check the configuration file to ensure that a mapping is available for the\nindicated locale.\nFor information on locale configuration and mapping, refer to the NetBackup\nAdministrator's Guide, Volume II.\nIf there is a mapping, try to set the mapped locale on the host that was specified in\nthe NetBackupJava logon dialog box. This system may not be configuredproperly."
    },
    "517": {
        "code": 517,
        "desc": "Cannot connect to the NetBackup Java user service by VNETD on host on port configured_port_number. If successfully logged on beforehand, retry your last operation. Check the log file for more details.",
        "first_action": "On UNIX: Compare the VNETD entry in the /etc/services file with the",
        "full_action": "Do the following, as appropriate:\n■ On UNIX: Compare the VNETD entry in the /etc/services file with the\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare the VNETD entry with the VNETD_PORT entry in the\ninstall_path\\java\\setconf.bat file.\nThese entries must match.\n■ Ensure that no other application uses the port that is configured for VNETD."
    },
    "518": {
        "code": 518,
        "desc": "No ports available in range (port_number) through (port_number) per the NBJAVA_CLIENT_PORT_WINDOW configuration option. NetBackup status codes 286 NetBackup status codes",
        "first_action": "Restart the NetBackup Java interface and try again.",
        "full_action": "Do the following, as appropriate:\n■ Restart the NetBackup Java interface and try again.\n■ If the problem persists, increase the range of ports by changing the\nNBJAVA_CLIENT_PORT_WINDOWoptioninthe/usr/openv/java/nbj.conf\nfile (UNIX) or the install_path\\java\\setconf.bat file (Windows)."
    },
    "519": {
        "code": 519,
        "desc": "Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value: (option_value).",
        "first_action": "Correct the value in file /usr/openv/java/nbj.conf",
        "full_action": "Correct the value in file /usr/openv/java/nbj.conf\n(UNIX) or install_path\\java\\setconf.bat file (Windows)."
    },
    "520": {
        "code": 520,
        "desc": "Invalid value for NetBackup Java configuration option (option_name): (option_value).",
        "first_action": "Correct the value in file /usr/openv/java/nbj.conf",
        "full_action": "Correct the value in file /usr/openv/java/nbj.conf\n(UNIX) or install_path\\java\\setconf.bat file (Windows)."
    },
    "521": {
        "code": 521,
        "desc": "NetBackup Java Configuration file (file_name) does not exist.",
        "first_action": "Make sure that the configuration file the NetBackup Java",
        "full_action": "Make sure that the configuration file the NetBackup Java\ninterface exists and is properly formatted."
    },
    "522": {
        "code": 522,
        "desc": "NetBackup Java Configuration file (file_name) is not readable due to the following error: (message).",
        "first_action": "Correct the file as specified in the message.",
        "full_action": "Correct the file as specified in the message."
    },
    "523": {
        "code": 523,
        "desc": "NetBackup Java application server protocol error.",
        "first_action": "If the problem persists, restart the NetBackup Java interface and try again.",
        "full_action": "Do the following, as appropriate:\n■ If the problem persists, restart the NetBackup Java interface and try again.\n■ If the problem still persists, enable detailed debug logging as explained in the\nfollowing topic:\nSee \"Setting Media Manager debug logging to a higher level\" in the NetBackup\nLogging Reference Guide.\n■ Restart the NetBackup Java interface and examine the logs.\nNote: The error is probably the result of a system resource issue. When detailed\ndebug logging ID is enabled, the details can be retrieved from the bpjava-msvc,\nbpjava-susvc, or bpjava-usvc log files."
    },
    "525": {
        "code": 525,
        "desc": "CannotconnecttotheNetBackupJavaauthenticationservicebyVNETD on (host) on port (vnetd_configured_port_number). Check the log file for more details.",
        "first_action": "On UNIX: Compare the VNETD entry in the /etc/services file with the",
        "full_action": "Do the following, as appropriate:\n■ On UNIX: Compare the VNETD entry in the /etc/services file with the\nVNETD_PORT entry in /usr/openv/java/nbj.conf\nOn Windows: Compare the VNETD entry with the VNETD_PORT entry in the\ninstall_path\\java\\setconf.bat file.\nThese entries must match.\n■ Ensure that no other application uses the port that is configured for VNETD."
    },
    "526": {
        "code": 526,
        "desc": "Bpjava authentication service connection failed",
        "first_action": "If the target server is running an invalid version of NetBackup, the Java GUI",
        "full_action": "Do the following, as appropriate:\n■ If the target server is running an invalid version of NetBackup, the Java GUI\nattempts a further connection by the VNETD port 13724. No action is required.\n■ Check that the PBX service or daemon has been started on the server and that\nNetBackup services are running.\n■ Check iftheJava GUIproperties(java/nbj.conf) have been setup toconnect\nto a PBX port other than 1556."
    },
    "527": {
        "code": 527,
        "desc": "Bpjava user service connection if connection to pbx on port 1556 fails",
        "first_action": "Check that the PBX service or daemon has been started on the server and that",
        "full_action": "Do the following, as appropriate:\n■ Check that the PBX service or daemon has been started on the server and that\nNetBackup services are running.\n■ If the target server is running an invalid version of NetBackup, the Java GUI\nattempts a further connection by the VNETD port 13724. No action is required.\n■ CheckiftheJavaGUIproperties(java/nbj.conf)havebeenmodifiedtoattempt\na PBX port other than 1556."
    },
    "537": {
        "code": 537,
        "desc": "ConnectiontotheNetBackupdatabasewasnotsuccessful.Ensurethat the database service is running.",
        "first_action": "Start the NetBackup database service.",
        "full_action": "Start the NetBackup database service."
    },
    "538": {
        "code": 538,
        "desc": "Unable to login",
        "first_action": "Synchronize the time on both hosts or decrease the",
        "full_action": "Synchronize the time on both hosts or decrease the\ndifference in time to less than 24 hours."
    },
    "552": {
        "code": 552,
        "desc": "The Certificate Revocation List (CRL) could not be downloaded and, therefore,thecertificaterevocationstatuscouldnotbeverified.Formoreinformation, see the NetBackup logs.",
        "first_action": "For more information, see the bpjava logs.",
        "full_action": "For more information, see the bpjava logs."
    },
    "555": {
        "code": 555,
        "desc": "Unable to logon.",
        "first_action": "Use another authentication mechanism. For example,",
        "full_action": "Use another authentication mechanism. For example,\nauthenticate with either a user name and password or with the Windows Active\nDirectory logon credentials."
    },
    "600": {
        "code": 600,
        "desc": "An exception condition occurred",
        "first_action": "Contactcustomersupportandsendtheappropriatedebug",
        "full_action": "Contactcustomersupportandsendtheappropriatedebug\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "601": {
        "code": 601,
        "desc": "Unable to open listen socket",
        "first_action": "ChecktheOSerrorthatwasreportedintheerrormessage,",
        "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich bpsynth logged in the NetBackup error log. This error helps to diagnose the\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nRetry the synthetic backup job. If the problem persists, contact customer support\nand provide the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "602": {
        "code": 602,
        "desc": "Cannot set non-blocking mode on the listen socket",
        "first_action": "ChecktheOSerrorthatwasreportedintheerrormessage,",
        "full_action": "ChecktheOSerrorthatwasreportedintheerrormessage,\nwhich was logged in the NetBackup error log. The error helps to diagnose the\nproblem.EnsurethatthebpsynthbinarymatchestheinstalledNetBackupversion.\nIf the condition persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "603": {
        "code": 603,
        "desc": "Cannot register handler for accepting new connections",
        "first_action": "Ensure that the bpsynth binary matches the installed",
        "full_action": "Ensure that the bpsynth binary matches the installed\nNetBackup version. Retry the synthetic backup job. If the problem persists, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "604": {
        "code": 604,
        "desc": "No target storage unit specified for the new job",
        "first_action": "Retry the synthetic backup job. If the problem persists,",
        "full_action": "Retry the synthetic backup job. If the problem persists,\ncontact customer support and provide appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "605": {
        "code": 605,
        "desc": "Received error notification for the job",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "606": {
        "code": 606,
        "desc": "No robot on which the media can be read",
        "first_action": "Contact customer support and provide the appropriate",
        "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "607": {
        "code": 607,
        "desc": "No images were found to synthesize",
        "first_action": "Ensure that a synthetic full backup has one full image",
        "full_action": "Ensure that a synthetic full backup has one full image\n(real or synthetic) and one or more subsequent incremental images (differential or\ncumulative) to synthesize. For a cumulative synthetic backup, there must be two\nor more incremental (differential or cumulative) images to synthesize. Adjust your\nschedulessotheappropriatebackupjobscompletesuccessfullybeforethesynthetic\njob is run. The scheduler does not retry a synthetic backup job that fails with this\nerror code."
    },
    "608": {
        "code": 608,
        "desc": "Storage unit query failed",
        "first_action": "Verifythatthebpdbmprocessisrunningandthatnoerrors",
        "full_action": "Verifythatthebpdbmprocessisrunningandthatnoerrors\nwere logged to the NetBackup error log. Restart the bpdbm process (on UNIX), or\nthe NetBackup Database Manager Service (on Windows) and retry the synthetic\nbackup job. If the problem persists, contact customer support and send the\nappropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "609": {
        "code": 609,
        "desc": "Reader failed",
        "first_action": "SeetheNetBackuperrorlogfortheerrorsthatthebpsynth",
        "full_action": "SeetheNetBackuperrorlogfortheerrorsthatthebpsynth\nandbptmorbpdmreaderlogged.Theerrormessageshouldcontaintheactualerror\nthat the bptm or the bpdm reader reports.\nSee the NetBackup Troubleshooting Guide for information on the error that the\nbptm or the bpdm reader reports. The media may not be present or is defective or\nthe drive that was used for reading the media is defective. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "610": {
        "code": 610,
        "desc": "Endpoint terminated with an error",
        "first_action": "Review the errors in the NetBackup error log that the",
        "full_action": "Review the errors in the NetBackup error log that the\nfollowing processes logged: bpsynth and bptm or bpdm. Refer to the debug logs\nfor these processes for more information. The connection may have broken due to\nthefollowing:anerrorconditionthatthebptmorthebpdmprocessdetectsornetwork\nproblemsbetweenthemasterandthemediaserver.Checkthenetworkconnectivity\nbetweenthemasterandthemediaserver.Retrythejobandiftheproblempersists,\ncontact customer support, and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "611": {
        "code": 611,
        "desc": "No connection to reader",
        "first_action": "Thiserrorshouldnotoccur.Submitaproblemreportalong",
        "full_action": "Thiserrorshouldnotoccur.Submitaproblemreportalong\nwith the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "612": {
        "code": 612,
        "desc": "Cannot send extents to bpsynth",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "613": {
        "code": 613,
        "desc": "Cannot connect to read media server",
        "first_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster",
        "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\nserver and the specified media server. Examine the NetBackup error log for any\nerror messages that bpsynth logged. For more information, refer to the debug logs\nfor bpsynth on the master server and bpcd and bptm or bpdm on the media server.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "614": {
        "code": 614,
        "desc": "Cannot start reader on the media server",
        "first_action": "Examine the NetBackup error log for any errors that bpsynth logged. For more",
        "full_action": "Do the following, as appropriate:\n■ Examine the NetBackup error log for any errors that bpsynth logged. For more\ninformation, refer to the following debug logs: for bpsynth on the master server\nand for bpcd and bptm or bpdm on the media server. Ensure that the bptm or the\nbpdm binaries on the media server are executable and are not corrupt. Try\nrunning bptm or bpdm commands locally on the media server to ensure that the\nbinary is executable and not corrupt. For instance, you can run the following\ncommand\n/bp/bin/bptm -count -rn 0 -rt 8\nwhererobotnumberis0andtherobottypeis8.Therobottypethatcorresponds\nto the robot number can be taken from the command line that is logged in the\ndebug log for bptm. This command displays the counts for the up, shared, and\nassigned drives in the robot.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "615": {
        "code": 615,
        "desc": "Internal error 615",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "616": {
        "code": 616,
        "desc": "Internal error 616",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "617": {
        "code": 617,
        "desc": "No drives available to start the reader process",
        "first_action": "Ensure that sufficient drives are available before you",
        "full_action": "Ensure that sufficient drives are available before you\nrestart the job."
    },
    "618": {
        "code": 618,
        "desc": "Internal error 618",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "619": {
        "code": 619,
        "desc": "Internal error 619 NetBackup status codes 298 NetBackup status codes",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "620": {
        "code": 620,
        "desc": "Internal error 620",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "621": {
        "code": 621,
        "desc": "Unable to connect to bpcoord",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "622": {
        "code": 622,
        "desc": "Connection to the peer process does not exist",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "623": {
        "code": 623,
        "desc": "Execution of a command in a forked process failed",
        "first_action": "Retrythejobandiftheproblempersists,contactcustomer",
        "full_action": "Retrythejobandiftheproblempersists,contactcustomer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "624": {
        "code": 624,
        "desc": "Unabletosendastartcommandtoareaderorawriterprocessonmedia server",
        "first_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster",
        "full_action": "Ensurethatnetworkconnectivityexistsbetweenthemaster\nand the media server. Look for additional error messages in the NetBackup error\nlog. More detailed information is present in the debug logs for bpsynth (on master\nserver) and bptm or bpdm on the media server. If the problem persists, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "625": {
        "code": 625,
        "desc": "Data marshalling error",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "626": {
        "code": 626,
        "desc": "Data un-marshalling error",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "627": {
        "code": 627,
        "desc": "Unexpected message received from bpsynth",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "628": {
        "code": 628,
        "desc": "Insufficient data received",
        "first_action": "If this error causes the bpsynth binary to hang or",
        "full_action": "If this error causes the bpsynth binary to hang or\nmalfunction, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "629": {
        "code": 629,
        "desc": "No message was received from bptm",
        "first_action": "Look for additional error messages in the following logs:",
        "full_action": "Look for additional error messages in the following logs:\nthe NetBackup error log and the debug logs for bpsynth on the master server and\nbptm on the media server. A system condition (insufficient memory, file system full,\ninsufficient swap space) on the media server may prevent the bptm process from\nsending the response. Verify the network connectivity between the master and the\nmedia server. If no explanation is found for the failure and the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "630": {
        "code": 630,
        "desc": "Unexpected message was received from bptm",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "631": {
        "code": 631,
        "desc": "Received an error from bptm request to suspend media",
        "first_action": "Examine the bptm debug log for more information on the",
        "full_action": "Examine the bptm debug log for more information on the\nreasonforthesuspendfailure.Thebpsynthprocessignoresthiserrorandcontinues\nto process. It has the potential to fail later if the media with the images to be read\ngets assigned to another backup or restore job. If the synthetic backup job fails, fix\nthe condition that lead to the suspend failure and retry the job."
    },
    "632": {
        "code": 632,
        "desc": "Received an error from bptm request to un-suspend media",
        "first_action": "Look at the debug log for the bptm process on the media",
        "full_action": "Look at the debug log for the bptm process on the media\nserver for an explanation of the un-suspend failure and the media ID. Try to\nun-suspend the tape manually by using the bpmedia command."
    },
    "633": {
        "code": 633,
        "desc": "Unable to listen and register service by vnetd",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "634": {
        "code": 634,
        "desc": "No drives available to start the writer process",
        "first_action": "Ensure that the target storage unit that is configured for",
        "full_action": "Ensure that the target storage unit that is configured for\nthe synthetic backup schedule has an available drive to write the synthetic backup\nimage."
    },
    "635": {
        "code": 635,
        "desc": "Unable to register handle with the reactor",
        "first_action": "Examine NetBackup error log for any errors that were",
        "full_action": "Examine NetBackup error log for any errors that were\nlogged for the job. Refer to the debug logs for bpsynth for more information. Retry\nthe synthetic backup job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "636": {
        "code": 636,
        "desc": "Read from input socket failed",
        "first_action": "The bpsynth process encountered an error while reading",
        "full_action": "The bpsynth process encountered an error while reading\nfrom an input socket. The socket may be between bpsynth and bptm or bpdm.\nThe errno that was logged to the NetBackup error log indicates the reason for the\nfailure. For more information, refer to the following: the debug log for bpsynth (on\nthe master server) and for the bptm or the bpdm reader or writer processes (on the\nmedia server). Check the network connectivity between the master and the media\nserver. Rerun the synthetic backup job. If the problem persists, contact customer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "637": {
        "code": 637,
        "desc": "Write on output socket failed",
        "first_action": "The bpsynth process encountered an error while writing",
        "full_action": "The bpsynth process encountered an error while writing\nto an output socket. The socket is between bpsynth and bptm or bpdm.\nTheerrnothatloggedtotheNetBackuperrorlogindicatesthereasonforthefailure.\nFor more information, refer to the following: the debug log for bpsynth (on the\nmaster server) and for the bptm or the bpdm reader or writer process (on the media\nserver). Check the connectivity between the master and the media server. Retry\nthe synthetic backup job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "638": {
        "code": 638,
        "desc": "Invalid arguments specified",
        "first_action": "Help)forthecorrectargumentspecification.Ifthesyntheticbackupjobwasstarted",
        "full_action": "Refer to the bpsynth command line arguments (by using\n-help)forthecorrectargumentspecification.Ifthesyntheticbackupjobwasstarted\nmanually by the command line, correct the arguments to bpsynth and rerun the\njob. If the synthetic backup job was scheduled or started with the console, ensure\nthat the bpsynth and the nbjm binaries match the installed NetBackup version."
    },
    "639": {
        "code": 639,
        "desc": "Specified policy does not exist",
        "first_action": "The synthetic backup job was scheduled or started by using the NetBackup",
        "full_action": "If bpsynth is initiated with the command line, rerun the\ncommandforanexistingpolicy.Iftheproblempersistsafteryouverifythefollowing,\ncontact customer support and send the appropriate logs:\n■ The synthetic backup job was scheduled or started by using the NetBackup\nAdministration Console (manual start).\n■ The policy exists in the bppllist command configuration.\n■ Check the logs for nbjm, which uses unified logging (OID 117).\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "640": {
        "code": 640,
        "desc": "Specified schedule was not found",
        "first_action": "If the command line initiated bpsynth, do the following:",
        "full_action": "If the command line initiated bpsynth, do the following:\nrerun the command with the correct synthetic schedule label defined in the policy\nof the synthetic backup job to be run. If the synthetic backup job was scheduled or\nstarted with the NetBackup Administration Console, define a new schedule in\nthe policy and retry the job. If the problem persists, contact customer support and\nsend the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "641": {
        "code": 641,
        "desc": "Invalid media type specified in the storage unit",
        "first_action": "Ensure that the target storage unit that was configured",
        "full_action": "Ensure that the target storage unit that was configured\nfor synthetic backup is a disk, disk staging, or Media Manager type (not NDMP\ntype). Rerun synthetic backup with the appropriate storage unit."
    },
    "642": {
        "code": 642,
        "desc": "Duplicate backup images were found",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "643": {
        "code": 643,
        "desc": "Unexpected message received from bpcoord",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "644": {
        "code": 644,
        "desc": "Extent directive contained an unknown media ID",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "645": {
        "code": 645,
        "desc": "Unable to start the writer on the media server",
        "first_action": "ExaminetheNetBackuperrorlogforanymessagesthatbpsynthlogged.Formore",
        "full_action": "ExaminetheNetBackuperrorlogforanymessagesthatbpsynthlogged.Formore\ninformation, refer to the following: the debug logs for bpsynth on the master server\nand bpcd and bptm or bpdm on the media server. Ensure that the bptm or the bpdm\nbinaries on the media server are executable and are not corrupt. Try to run the\nbptm or the bpdm commands locally on the media server to ensure that the binary\nis executable and not corrupt. For instance, you can run the following command:\ninstall_path/netbackup/bin/bptm -count -rn 0 -rt 8\nwhere robot number is 0 and robot type is 8. The robot type that corresponds to\nthe robot number can be taken from the command line that is logged in the debug\nlog for bptm. This command displays the counts for the up, shared, and assigned\ndrives in the robot. In case the synthetic image is to be written to a disk storage\nunit, verify the bpdm binary by running the following command:\ninstall_path/netbackup/bin/bpdm\nIt should print the following:\nbpdm: media manager operation not specified\nRetry the synthetic backup job. If the problem persists, contact customer support\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "646": {
        "code": 646,
        "desc": "Unable to get the address of the local listen socket",
        "first_action": "Rerun the synthetic backup job. If the problem persists,",
        "full_action": "Rerun the synthetic backup job. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "647": {
        "code": 647,
        "desc": "Validation of synthetic image failed",
        "first_action": "This error may indicate a problem in the synthetic backup",
        "full_action": "This error may indicate a problem in the synthetic backup\nprocess. Examine the NetBackup error log for any messages that the following\nprocesses logged: bpsynth and bptm or bpdm. Look at the debug logs for these\nprocesses for additional information. If you cannot resolve the problem, contact\ncustomer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "648": {
        "code": 648,
        "desc": "Unable to send extent message to BPXM",
        "first_action": "This error indicates a communication problem between",
        "full_action": "This error indicates a communication problem between\nbpsynth and the bptm or the bpdm reader process on the media server. Ensure that\nthe media server is accessible and that the bptm or the bpdm process is running on\nthe media server. Examine the NetBackup error log for any errors that the following\nlogged: bpsynth (on the master server) and the bptm or the bpdm reader process\n(on the media server). Examine the debug logs for bpsynth and bptm or bpdm for\nadditional information. Rerun the synthetic backup job. If the problem persists,\ncontact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "649": {
        "code": 649,
        "desc": "Unexpected message received from BPXM",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "650": {
        "code": 650,
        "desc": "Unable to send extent message to bpcoord",
        "first_action": "Submit a problem report along with the appropriate logs.",
        "full_action": "Submit a problem report along with the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "651": {
        "code": 651,
        "desc": "Unable to issue the database query for policy",
        "first_action": "This error indicates a communication problem between",
        "full_action": "This error indicates a communication problem between\nbpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matches\nthe installed NetBackup version. Examine the NetBackup error log for any errors\nthat bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm\nfor additional information. Restart the bpdbm process (on UNIX) or the NetBackup\nDatabase Manager Service (on Windows) and rerun the synthetic backup job. If\nthe problem persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "652": {
        "code": 652,
        "desc": "Unable to issue the database query for policy information",
        "first_action": "This error indicates a communication problem between",
        "full_action": "This error indicates a communication problem between\nbpsynth and bpdbm. Ensure that bpdbm is running and the bpdbm binary matches\nthe installed NetBackup version. Examine the NetBackup error log for any errors\nthat bpdbm and bpsynth logged. Examine the debug logs for bpsynth and bpdbm\nfor additional information. Restart the bpdbm process (on UNIX) or the NetBackup\nDatabase Manager Service (on Windows) and rerun the synthetic backup job. If\nthe problem persists, contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "653": {
        "code": 653,
        "desc": "Unable to send a message to bpccord",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "654": {
        "code": 654,
        "desc": "Internal error 654",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "655": {
        "code": 655,
        "desc": "No target storage unit was specified by command line",
        "first_action": "Rerun bpsynth with the target storage unit specified by",
        "full_action": "Rerun bpsynth with the target storage unit specified by\nthe -S option."
    },
    "656": {
        "code": 656,
        "desc": "Unable to send start synth message to bpcoord",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "657": {
        "code": 657,
        "desc": "Unable to accept connection from the reader",
        "first_action": "Examine the NetBackup error log for any errors that",
        "full_action": "Examine the NetBackup error log for any errors that\nbpsynth and bptm or the bpdm reader process logged. The message that bpsynth\nlogged includes the error (errno) reported by the system call. Refer to the debug\nlogs for bpsynth on the master server and bptm or the bpdm process on the media\nservers for more information. Ensure that network connectivity exists between the\nmaster and the media servers. If the problem persists, contact customer support\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "658": {
        "code": 658,
        "desc": "Unable to accept connection from the writer",
        "first_action": "Examine the NetBackup error log for any errors that",
        "full_action": "Examine the NetBackup error log for any errors that\nbpsynthandthebptmorthebpdmwriterprocesslogged.Themessagethatbpsynth\nlogged includes the error (errno) reported by the system call. Also refer to the\ndebug logs for bpsynth on the master server and bptm or the bpdm process on the\nmediaserverformoreinformation.Ensurethatnetworkconnectivityexistsbetween\nthemasterandthemediaservers.Iftheproblempersists,contactcustomersupport\nand send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "659": {
        "code": 659,
        "desc": "Unable to send a message to the writer child process",
        "first_action": "Examine the NetBackup error log for any errors that",
        "full_action": "Examine the NetBackup error log for any errors that\nbpsynth and the bptm or the bpdm writer process logged. Refer to the following for\nmore information: the debug logs for bpsynth on the master server and the bptm\nor the bpdm process on the media server. Ensure that network connectivity exists\nbetweenthemasterandthemediaservers.Iftheproblempersists,contactcustomer\nsupport and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "660": {
        "code": 660,
        "desc": "A synthetic backup request for media resources failed",
        "first_action": "Create logs as explained in the following topic:",
        "full_action": "Create logs as explained in the following topic:\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide.\nRerun the job and send the logs to customer support."
    },
    "661": {
        "code": 661,
        "desc": "Unable to send exit message to the BPXM reader",
        "first_action": "Check the network connectivity between the master and",
        "full_action": "Check the network connectivity between the master and\nthe media server. Examine the NetBackup error log for any errors that bpsynth\nand bptm or the bpdm reader process logged. Examine the debug logs for bpsynth\non the master server and bptm or the bpdm reader process on the media servers\nformoredetailedinformation.Iftheproblempersists,contactcustomersupportand\nprovide the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "662": {
        "code": 662,
        "desc": "Unknown image referenced in the synth context message from BPXM",
        "first_action": "Contact customer support and provide the appropriate",
        "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "663": {
        "code": 663,
        "desc": "Image does not have a fragment map",
        "first_action": "Contact customer support and provide the appropriate",
        "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "664": {
        "code": 664,
        "desc": "Zero extents in the synthetic image, cannot proceed",
        "first_action": "Contact customer support and provide the appropriate",
        "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "665": {
        "code": 665,
        "desc": "Termination requested by bpcoord",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "667": {
        "code": 667,
        "desc": "Unable to open pipe between bpsynth and bpcoord",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "668": {
        "code": 668,
        "desc": "Pipe fgets call from bpcoord failed",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "669": {
        "code": 669,
        "desc": "Bpcoord startup validation failure",
        "first_action": "Contact customer support and send the appropriate logs.",
        "full_action": "Contact customer support and send the appropriate logs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "670": {
        "code": 670,
        "desc": "Send buffer is full",
        "first_action": "Contact customer support and provide the appropriate",
        "full_action": "Contact customer support and provide the appropriate\nlogs.\nA complete list of required logs and configuration information is available.\nSee \"Logs to accompany problem reports for synthetic backups\" in the NetBackup\nLogging Reference Guide."
    },
    "671": {
        "code": 671,
        "desc": "Query for list of component images failed",
        "first_action": "Run a non-synthetic backup (either a new full or new",
        "full_action": "Run a non-synthetic backup (either a new full or new\ncumulative), depending on the type of backup that failed."
    },
    "800": {
        "code": 800,
        "desc": "Resource request failed",
        "first_action": "Locate the EMM reason string, correct the problem, and",
        "full_action": "Locate the EMM reason string, correct the problem, and\nrerun the job.\nSome generic EMM reason strings (such as Disk volume is down) may require\ngenerating some reports to determine the cause of the failure. Generate the report\nby using either bperror or various log entry reports, such as Reports > Disk\nReports > Disk Logs in the NetBackup Administration Console."
    },
    "801": {
        "code": 801,
        "desc": "JM internal error",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "If the problem persists, submit a report with the following\nitems.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "802": {
        "code": 802,
        "desc": "JM internal protocol error",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "Ensure that the NetBackup software on the master and\nthe media server is from an official NetBackup release.\nIf the problem persists, submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "803": {
        "code": 803,
        "desc": "JM terminating",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "If nbjm was not terminated explicitly (by entering the\n/usr/openv/netbackup/bin/bp.kill_all command on UNIX or\ninstall_path\\NetBackup\\bin\\bpdown on Windows), submit a report with the\nfollowing items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm,\nand nbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "805": {
        "code": 805,
        "desc": "Invalid jobid",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "The requested operation may refer to a job that no longer exists or is not known to\nnbjm. Or the job ID is invalid (less than or equal to 0). Ensure that the command\nused to start the job did not specify a job ID already in use by another job.\nIf the problem persists, submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ Legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\nyou must create directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "806": {
        "code": 806,
        "desc": "This mpx group is unjoinable",
        "first_action": "If the failed job is scheduled and the retry count allows it,",
        "full_action": "If the failed job is scheduled and the retry count allows it,\nnbpem submits the job again. If the failed job was initiated manually, submit it again."
    },
    "807": {
        "code": 807,
        "desc": "Not externalized",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "811": {
        "code": 811,
        "desc": "Failed to communicate with resource requester",
        "first_action": "Verify the connectivity between the master and the media server.",
        "full_action": "Do the following, as appropriate:\n■ Verify the connectivity between the master and the media server.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformation on PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide."
    },
    "812": {
        "code": 812,
        "desc": "Failed to communicate with Resource Broker",
        "first_action": "Verify the connectivity between the master server and the EMM server.",
        "full_action": "Do the following, as appropriate:\n■ Verify the connectivity between the master server and the EMM server.\n■ VerifythePrivateBranchExchange(PBX)configurationandpermissions.More\ninformation on PBX is available.\nSee \"Resolving PBX problems\" in the NetBackup Troubleshooting Guide."
    },
    "813": {
        "code": 813,
        "desc": "Duplicate reference string specified",
        "first_action": "Choose a unique name that is not already in use.",
        "full_action": "Choose a unique name that is not already in use."
    },
    "818": {
        "code": 818,
        "desc": "Retention level mismatch",
        "first_action": "Contact Cohesity Technical Support and provide relevant",
        "full_action": "Contact Cohesity Technical Support and provide relevant\nsupporting materials."
    },
    "819": {
        "code": 819,
        "desc": "Unable to communicate with JM proxy",
        "first_action": "Restart the Job Manager. If the condition persists, please",
        "full_action": "Restart the Job Manager. If the condition persists, please\ncontact NetBackup Support and provide relevant supporting materials."
    },
    "823": {
        "code": 823,
        "desc": "No BRMComm to join",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "Submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "830": {
        "code": 830,
        "desc": "Drive(s) unavailable or down",
        "first_action": "Make sure that the drives and drive paths are up and correct for the media that",
        "full_action": "Do the following:\n■ Make sure that the drives and drive paths are up and correct for the media that\nyou configure.\n■ Verify that ltid is running on the required media server, and that the media\nserver is active for tape.\n■ Use the device monitor to startup the drives paths if they are down.\n■ If the drives are downed again, clean the drives."
    },
    "831": {
        "code": 831,
        "desc": "Image has been validated",
        "first_action": "No corrective action is required.",
        "full_action": "No corrective action is required."
    },
    "832": {
        "code": 832,
        "desc": "Failed to write discover data to a file",
        "first_action": "Make sure that the file system is not full.",
        "full_action": "Make sure that the file system is not full."
    },
    "833": {
        "code": 833,
        "desc": "Error parsing discovered XML data",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "Submit a report with the following items:\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacylogsareinsubdirectoriesunder/usr/openv/netbackup/logs/(UNIX)\nor install_path\\NetBackup\\logs\\ (Windows). If the directories do not exist,\ncreate directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "859": {
        "code": 859,
        "desc": "Exceededmaximumnumberofretries,unabletodeactivatedeployment host.",
        "first_action": "Retry the deployment job on the target host.",
        "full_action": "Retry the deployment job on the target host."
    },
    "860": {
        "code": 860,
        "desc": "Exceeded maximum number of retries, unable to activate deployment host.",
        "first_action": "Activate_host -h hostname to activate the host.",
        "full_action": "Wait until the host is active, or run vmoprcmd\n-activate_host -h hostname to activate the host."
    },
    "861": {
        "code": 861,
        "desc": "Theentryforexclude_file_listparameterinthejob paramfileisnot present.",
        "first_action": "Retry the backup job again. If the issue persists, update",
        "full_action": "Retry the backup job again. If the issue persists, update\nthe backup policy to reconfigure the exclude selections."
    },
    "900": {
        "code": 900,
        "desc": "Retry nbrb request later",
        "first_action": "For detailed information, examine the unified logging files on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs."
    },
    "901": {
        "code": 901,
        "desc": "RB internal error",
        "first_action": "For detailed information, examine the unified logging files on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs."
    },
    "902": {
        "code": 902,
        "desc": "RB invalid argument",
        "first_action": "For detailed information, examine the unified logging files on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs."
    },
    "903": {
        "code": 903,
        "desc": "RB communication error",
        "first_action": "For detailed information, examine the unified logging files on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level, by using Host Properties >\nMaster Server > Properties > Logging. Retry the operation and examine the\nnbrb logs."
    },
    "904": {
        "code": 904,
        "desc": "RB max reallocation tries exceeded",
        "first_action": "For detailed information, examine the unified logging files",
        "full_action": "For detailed information, examine the unified logging files\non the NetBackup server for the nbrb service (originator ID 118) and for nbemm\n(originator ID 111). All unified logging is written to /usr/openv/logs (UNIX) or\ninstall_path\\NetBackup\\logs (Windows). Also examine the legacy bptm log."
    },
    "905": {
        "code": 905,
        "desc": "RB media server mismatch",
        "first_action": "Configure the backup schedule with a storage unit or storage unit groups that",
        "full_action": "Do the following, as appropriate:\n■ Configure the backup schedule with a storage unit or storage unit groups that\ncan be run on the same media server.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)."
    },
    "906": {
        "code": 906,
        "desc": "RB operator denied mount request NetBackup status codes 329 NetBackup status codes",
        "first_action": "Determine the cause of the mount request denial and retry the job.",
        "full_action": "Do the following, as appropriate:\n■ Determine the cause of the mount request denial and retry the job.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)."
    },
    "907": {
        "code": 907,
        "desc": "RB user canceled resource request",
        "first_action": "Determine the action that resulted in cancelation of the resource request.",
        "full_action": "Do the following, as appropriate:\n■ Determine the action that resulted in cancelation of the resource request.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)."
    },
    "908": {
        "code": 908,
        "desc": "RB was reset",
        "first_action": "Determine the action that reset nbrb resources and the nbemm database.",
        "full_action": "Do the following, as appropriate:\n■ Determine the action that reset nbrb resources and the nbemm database.\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). All unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows)."
    },
    "912": {
        "code": 912,
        "desc": "RB disk volume mount failed",
        "first_action": "For detailed information, examine the unified logging files on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ For detailed information, examine the unified logging files on the NetBackup\nserver for the nbrb service (originator ID 118). Unified logging is written to\n/usr/openv/logs (UNIX) or install_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level: Host Properties > Master\nServer > Properties > Logging. Retry the operation and examine the nbrb\nlogs."
    },
    "914": {
        "code": 914,
        "desc": "RB media reservation not found",
        "first_action": "Examine the unified logging files on the NetBackup server for the nbrb service",
        "full_action": "Do the following, as appropriate:\n■ Examine the unified logging files on the NetBackup server for the nbrb service\n(originator ID 118). Unified logging is written to /usr/openv/logs (UNIX) or to\ninstall_path\\NetBackup\\logs (Windows).\n■ If necessary, set global logging to a higher level: Host Properties > Master\nServer > Properties > Logging. Retry the operation and examine the nbrb\nlogs."
    },
    "915": {
        "code": 915,
        "desc": "RB disk volume mount must retry NetBackup status codes 331 NetBackup status codes",
        "first_action": "Verifythatprocessesarenotinthediskvolumemountdirectories,whichprevents",
        "full_action": "Do the following, as appropriate:\n■ Verifythatprocessesarenotinthediskvolumemountdirectories,whichprevents\nthem from being unmounted. If the problem persists, restart NetBackup on the\nmedia server."
    },
    "916": {
        "code": 916,
        "desc": "Resource request timed out",
        "first_action": "Distributethescheduledjobstarttimesoverawiderperiod",
        "full_action": "Distributethescheduledjobstarttimesoverawiderperiod\nof time."
    },
    "917": {
        "code": 917,
        "desc": "RB multiplexing group not found",
        "first_action": "Restart nbjm and nbrb. If the problem persists, write a",
        "full_action": "Restart nbjm and nbrb. If the problem persists, write a\nproblem report with the appropriate logs including the nbjm and nbrb logs."
    },
    "918": {
        "code": 918,
        "desc": "RB does not have a multiplexing group that uses this media ID or drive name NetBackup status codes 332 NetBackup status codes",
        "first_action": "The nbrbutil command may cause this error. Rerun the",
        "full_action": "The nbrbutil command may cause this error. Rerun the\ncommand with an allocated media ID or drive. Also, this error may be internal. If\nthe problem persists, write a problem report with the appropriate logs including\nnbjm and nbrb."
    },
    "925": {
        "code": 925,
        "desc": "Backup host pool name is not provided in the Resource Broker request.",
        "first_action": "Ensure that the backup host pool is configured in the",
        "full_action": "Ensure that the backup host pool is configured in the\nbackup policy."
    },
    "927": {
        "code": 927,
        "desc": "No backup host from configured backup host pool is available for job execution.",
        "first_action": "Ensure all NetBackup services are up and running on",
        "full_action": "Ensure all NetBackup services are up and running on\nbackup host. If the services are already running, then the backup host is running\natfullcapacityfordynamicstreaming.Youmustwaitfortheactivejobstocomplete."
    },
    "928": {
        "code": 928,
        "desc": "The NetBackup version of the backup hosts and the configured backup host pool must be of the same version.",
        "first_action": "Ensure that all backup hosts in a backup host pool are",
        "full_action": "Ensure that all backup hosts in a backup host pool are\nthe same NetBackup version."
    },
    "930": {
        "code": 930,
        "desc": "No supported media server available, in the All_Media_Server_Pool, as backup host to run the job.",
        "first_action": "Volume backup from snapshot using multiple backup hosts: NetBackup 10.4",
        "full_action": "Confirm that you have a Windows media server if you\nback up the NAS shares with the SMB protocol. Confirm that you have a Linux\nmedia server if you back up the NAS shares with the NFS protocol.\nRecommended Action: For Windows media servers, you must log on to the\nNetBackup Client Service and NetBackup legacy network service services as a\ndomain user.\nRecommended Action: Ensure that the NetBackup media server version is equal\nto or higher than the minimum required version, based on these parameters of the\nNAS data protection policy:\n■ Volume backup from snapshot using multiple backup hosts: NetBackup 10.4\n■ VCT enabled index from snapshot: NetBackup 10.3\n■ VCT enabled backup from snapshot: NetBackup 10.2\n■ All other scenarios: NetBackup 10.1.1"
    },
    "1000": {
        "code": 1000,
        "desc": "Client is offline",
        "first_action": "Wait until the client is brought online or manually bring",
        "full_action": "Wait until the client is brought online or manually bring\nthe client online by using the GUI or the bpclient command before you submit the\nmanual job."
    },
    "1001": {
        "code": 1001,
        "desc": "Discovery document error NetBackup status codes 334 NetBackup status codes",
        "first_action": "UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm",
        "full_action": "Submit a report with the following items.\n■ UnifiedloggingfilesontheNetBackupserverfornbpem(originatorID116),nbjm\n(117), nbrb (118), and PBX (103). All unified logging is written to\n/usr/openv/logs (UNIX and Linux) or install_path\\NetBackup\\logs\n(Windows).\n■ The following legacy logs:\n■ On the NetBackup master server for bpbrm, bpjobd, bpcompatd, bpdbm, and\nnbproxy\n■ On the media server for bpcd, bpbrm, and bptm or bpdm\n■ On the client for bpcd and bpbkar\nLegacy logs are in subdirectories under /usr/openv/netbackup/logs/ (UNIX\nand Linux) or install_path\\NetBackup\\logs\\ (Windows). If the directories\ndo not exist, create directories for each of these processes and rerun the job.\n■ Contents of /usr/openv/db/jobs/trylogs (UNIX and Linux) or\ninstall_path\\NetBackup\\db\\jobs\\trylogs (Windows).\n■ bpdbjobs output: run bpdbjobs to obtain the state and status of all jobs."
    },
    "1002": {
        "code": 1002,
        "desc": "Discovery detected a failed client",
        "first_action": "See the job details log for more specific information.",
        "full_action": "See the job details log for more specific information."
    },
    "1004": {
        "code": 1004,
        "desc": "Failed to get the Snapshot Manager name.",
        "first_action": "CheckiftheNetBackupWebManagementConsole(nbwmc)",
        "full_action": "CheckiftheNetBackupWebManagementConsole(nbwmc)\nservice is up and running. Then stop and restart the service if necessary."
    },
    "1005": {
        "code": 1005,
        "desc": "Missing one or more of the required policy values for unix_eca_cert_path, unix_eca_trust_store_path, or unix_eca_private_key_path.",
        "first_action": "Reset policy fields unix_eca_crl_path,",
        "full_action": "Reset policy fields unix_eca_crl_path,\nunix_eca_crl_check_level,andunix_eca_key_passphrasefileifyouonlyhave\nwindows clients. Otherwise, set required fields unix_eca_cert_path,\nunix_eca_trust_store_path, and unix_eca_private_key_path."
    },
    "1006": {
        "code": 1006,
        "desc": "Missingoneormoreoftherequiredpolicyvaluesforwin_eca_cert_path, win_eca_trust_store_path, or win_eca_private_key_path.",
        "first_action": "Reset policy fields win_eca_crl_path,",
        "full_action": "Reset policy fields win_eca_crl_path,\nwin_eca_crl_check_level, and win_eca_key_passphrasefile if you only have\nUNIX clients. Otherwise, set required fields win_eca_cert_path,\nwin_eca_trust_store_path, and win_eca_private_key_path."
    },
    "1007": {
        "code": 1007,
        "desc": "Cannot specify policy values for win_eca_cert_path, win_eca_trust_store_path, win_eca_private_key_path, and win_eca_key_passphrasefile when the policy value win_eca_cert_store is specified.",
        "first_action": "Set the required policy field win_eca_crl_check_level",
        "full_action": "Set the required policy field win_eca_crl_check_level\nand reset policy fields win_eca_cert_path, win_eca_trust_store_path,\nwin_eca_private_key_path, and win_eca_key_passphrasefile or reset the\npolicy field win_eca_cert_store."
    },
    "1008": {
        "code": 1008,
        "desc": "Missing required field unix_eca_crl_path.",
        "first_action": "Set the policy field unix_eca_crl_path or change",
        "full_action": "Set the policy field unix_eca_crl_path or change\nunix_eca_crl_check_level to either use_cdp or disabled."
    },
    "1009": {
        "code": 1009,
        "desc": "Missing required field win_eca_crl_path.",
        "first_action": "Set the policy field win_eca_crl_path or change",
        "full_action": "Set the policy field win_eca_crl_path or change\nwin_eca_crl_check_level to either use_cdp or disabled."
    },
    "1010": {
        "code": 1010,
        "desc": "Field unix_eca_crl_check_level must be use_path if field unix_eca_crl_path is specified.",
        "first_action": "Set the policy field unix_eca_crl_check_level to",
        "full_action": "Set the policy field unix_eca_crl_check_level to\nuse_path or reset the policy field unix_eca_crl_path."
    },
    "1011": {
        "code": 1011,
        "desc": "Field win_eca_crl_check_level must be use_path if field win_eca_crl_path is specified.",
        "first_action": "Setthepolicyfieldwin_eca_crl_check_leveltouse_path",
        "full_action": "Setthepolicyfieldwin_eca_crl_check_leveltouse_path\nor reset the policy field win_eca_crl_path."
    },
    "1012": {
        "code": 1012,
        "desc": "Missing required field win_eca_crl_check_level.",
        "first_action": "Set the policy field win_eca_crl_check_level and also",
        "full_action": "Set the policy field win_eca_crl_check_level and also\nset the policy field win_eca_crl_path if win_eca_crl_check_level is use_path."
    },
    "1013": {
        "code": 1013,
        "desc": "Invalid deployment_cert_source value, file must be specified.",
        "first_action": "Changedeployment_cert_sourcevaluefromcert_store",
        "full_action": "Changedeployment_cert_sourcevaluefromcert_store\nto file."
    },
    "1014": {
        "code": 1014,
        "desc": "Invaliddeployment_cert_sourcevalue,cert_storemustbespecified.",
        "first_action": "Change the deployment_cert_source value from file",
        "full_action": "Change the deployment_cert_source value from file\nto cert_store."
    },
    "1019": {
        "code": 1019,
        "desc": "Failed to get Snapshot Manager capability.",
        "first_action": "Ensure that the NetBackup service - nbemm is up and running.",
        "full_action": "Perform the following, as appropriate:\n■ Ensure that the NetBackup service - nbemm is up and running.\n■ Perform a refresh configuration operation of the Snapshot Manager using the\ntpconfig command to reset capability parameters in EMM."
    },
    "1020": {
        "code": 1020,
        "desc": "Failed to get the last backup snapshot ID.",
        "first_action": "Ensure that the last reference snapshot image exists",
        "full_action": "Ensure that the last reference snapshot image exists\nbefore you retry a VCT-based incremental backup."
    },
    "1021": {
        "code": 1021,
        "desc": "The maintenance version that is specified is not the same base version as installed version.",
        "first_action": "If package the name is maint.nbclient_8.2.3.2 then change to",
        "full_action": "Change package name to match the base version.\nFor example:\n■ If package the name is maint.nbclient_8.2.3.2 then change to\nmaint.nbclient.8.2.2.2 which matches the base release version 8.2.2 of\nthe installed package maint.nbclient.8.2.2.1."
    },
    "1022": {
        "code": 1022,
        "desc": "The maintenance version that is specified cannot be older than installed version, or no update required.",
        "first_action": "Ifinstalledpackageismaint.nbclient_8.3.0.5thenanynewmaint.nbclient",
        "full_action": "Change the maint.client or maint.nbserver package\nnames version to be the same or newer than the installed package version. For\nexample:\nFor example:\n■ Ifinstalledpackageismaint.nbclient_8.3.0.5thenanynewmaint.nbclient\npackage names version must be 8.3.0.[5-9]."
    },
    "1023": {
        "code": 1023,
        "desc": "Invalid package name specified.",
        "first_action": "8.2.1.",
        "full_action": "Change package name to match the format required\n<name>_<version>. Where the <version> Is a valid a NetBackup release like\n8.2.1.\nThe format of the package name must be one of the following:\n■ nbclient_<version>\n■ nbserver_<version>\n■ nbeeb_<version>\n■ nbeeb.client_<version>\n■ nbeeb.server_<version>\n■ maint.nbclient_<version>\n■ maint.nbserver_<version>"
    },
    "1024": {
        "code": 1024,
        "desc": "The BigData policy cannot be used to protect Nutanix AHV VMs using a backup host with NetBackup version 8.3 or later.",
        "first_action": "Migrate the policy by editing the existing BigData policy",
        "full_action": "Migrate the policy by editing the existing BigData policy\nand selecting the policy type as Hypervisor. Refer to the Migrating BigData policy\nto Hypervisor policy topic in the NetBackup for Nutanix Acropolis Hypervisor (AHV)\nAdministrator’s Guide."
    },
    "1026": {
        "code": 1026,
        "desc": "Cannot start the backup job, as another backup for the same asset, using the same policy is already running.",
        "first_action": "Wait for the current backup to finish before you initiate a",
        "full_action": "Wait for the current backup to finish before you initiate a\nnew backup for the same asset, with the same policy."
    },
    "1057": {
        "code": 1057,
        "desc": "A data corruption has been detected.",
        "first_action": "Search storaged.log on the server for the affected",
        "full_action": "Search storaged.log on the server for the affected\nbackups and contact Cohesity Technical Support."
    },
    "1058": {
        "code": 1058,
        "desc": "A data inconsistency has been detected and corrected automatically.",
        "first_action": "Search the storaged.log file on the pertinent media",
        "full_action": "Search the storaged.log file on the pertinent media\nserver. Contact support to investigate the root cause if the problem persists."
    },
    "1227": {
        "code": 1227,
        "desc": "Key group does not have an active key.",
        "first_action": "Run the following to verify that the key record is in an active state: nbkmscmd",
        "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nCheck whether required keys are present in Key Management Service (KMS) by\nrunning the following commands:\n■ Run the following to verify that the key record is in an active state: nbkmscmd\n-listkeys -name <kms name> -keyGroupName <key_group_name>\n■ Run the following to create a new key if key is not present in a group: nbkmscmd\n-createKey -name <configuration name> -KeyName <name of the key\nto be created> -keyGroupName < key group name>\n■ Runthefollowingtoactivatethekeyifanyofthekeyrecordsarenotinanactive\nstate in a group: nbkmsutil -modifykey -keyname <key_name> -kgname\n<key_group_name> -activate\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue."
    },
    "1229": {
        "code": 1229,
        "desc": "Key group was not found.",
        "first_action": "Run the following to verify whether the group is present in the KMS server:",
        "full_action": "See the errorDetails in the JSON output for additional\ndetails.\n■ Run the following to verify whether the group is present in the KMS server:\nnbkmscmd -listkeys -name <kms name> -keyGroupName <key_group_name>\n■ Run the following to create a key group in the KMS server: nbkmscmd\n-createKey -name <configuration name> -KeyName <name of the key\nto be created> -keyGroupName <name of the key group associated\nwith the key>\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue."
    },
    "1260": {
        "code": 1260,
        "desc": "Key record was not found.",
        "first_action": "1. GetconfiguredKMSinformationbyrunning:nbkmscmd -listKMSConfig -name",
        "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nCheck whether required keys are present in Key Management Service (KMS) by\nrunning the following commands:\n1. GetconfiguredKMSinformationbyrunning:nbkmscmd -listKMSConfig -name\n<kms_configuration_name>\n■ IftheEnabled for BackupoptionissettofalsefortheexistingKMSserver\nthen set it to true state by running: nbkmscmd -updateKMSConfig\n■ If the KMS configuration is not present for the KMS server then add a new\nKMS configuration with the Enabled for Backup option by running:\nnbkmscmd -configureKMS\nVerifythatthedesiredkeygroupsarepresentintheKMSserverwhereEnabled\nFor Backup is set to true.\n2. Get list of keys by running: nbkmscmd -listKeys -name\n<kms_configuration_name>\n3. If the key is not present then run nbkmscmd -createKey -name\n<configuration name> -KeyName <name of the key to be created>\n-keyGroupName <name of the key group associated with the key> to\nadd the key record to the KMS server.\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue."
    },
    "1288": {
        "code": 1288,
        "desc": "Failed to retrieve the Key Management Service (KMS) details.",
        "first_action": "1. Run the nbkmscmd -listKMSConfig -name <kms_configuration_name>",
        "full_action": "See the errorDetails in JSON output for additional\ndetails.\nThis error can occur due to NetBackup Key Management Service (KMS) is not\nrunning or the NetBackup Key Management Service (KMS) is not configured.\nVerify if the NetBackup Key Management Service (KMS) is running and configured\nby running the following:\n1. Run the nbkmscmd -listKMSConfig -name <kms_configuration_name>\ncommand to verify if the nbkms service is configured.\n2. If the nbkms service is not configured then run the nbkmscmd -configureKMS\nto configure the NetBackup KMS service.\n3. Runthenbkmscmd -discoverNBkmscommandifthenbkmscmd -configureKMS\ncommand recommends running this command.\n4. Verify that the nbkms service is configured by running the nbkmscmd\n-listKMSConfig -name <kms_configuration_name> command.\n5. Verify that the nbkms service is up and in a running state by executing the\nnbkmscmd -validateKMSConfig -name <kms_ configuration_name>\ncommand.\nIf the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnical Support website offers additional information to help you troubleshoot\nthis issue."
    },
    "1289": {
        "code": 1289,
        "desc": "Failed to create the Key Management Service (KMS) configuration.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "1290": {
        "code": 1290,
        "desc": "Failed to update the KMS configuration.",
        "first_action": "Provide at least one attribute.",
        "full_action": "When you update the KMS configuration, ensure the\nfollowing:\n■ Provide at least one attribute.\n■ To update the NetBackup KMS configuration, ensure that the KMIP attributes\nare not provided."
    },
    "1291": {
        "code": 1291,
        "desc": "TheNetBackupKeyManagementService(NBKMS)isalreadyconfigured, but not registered.",
        "first_action": "RunthenbkmscmdcommandtodiscoverNetBackupKMS.",
        "full_action": "RunthenbkmscmdcommandtodiscoverNetBackupKMS.\nFor more information on the nbkmscmd command, see the NetBackup Commands\nReference Guide."
    },
    "1292": {
        "code": 1292,
        "desc": "TheNetBackupKeyManagementService(NBKMS)cannotberegistered because it is not configured.",
        "first_action": "Run the nbkmscmd command to configure NetBackup",
        "full_action": "Run the nbkmscmd command to configure NetBackup\nKMS. This step automatically registers NetBackup KMS. For more information on\nthe nbkmscmd command, see the NetBackup Commands Reference Guide."
    },
    "1293": {
        "code": 1293,
        "desc": "The JSON string cannot be processed.",
        "first_action": "See the errorDetails in the response JSON output for",
        "full_action": "See the errorDetails in the response JSON output for\nadditional details. A retry of the same operation should resolve the issue. For more\ndetails, review the nbkmiputil and nbwebservice logs. If the issue persists, visit\nthe Cohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue."
    },
    "1294": {
        "code": 1294,
        "desc": "Time-out has occurred sending the JSON string to the NetBackup key management utility.",
        "first_action": "See the errorDetails in the JSON output for additional",
        "full_action": "See the errorDetails in the JSON output for additional\ndetails.\nVerify the KMS server name and the port number in the KMS configuration using\nthe nbkmscmd -listKMSConfig command. If everything seems to proper in the\nKMS configuration, run the nbkmscmd -validateKMSConfig -name <KMS\nConfiguration Name> command.\nA retry of the same operation can resolve the issue. For more details, review the\nnbkmiputil and nbwebservice logs. If the issue persists, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue."
    },
    "1295": {
        "code": 1295,
        "desc": "The JSON string cannot be read from the NetBackup key management utility as the utility is executed.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails.Aretryofthesameoperationcanresolvetheissue.Formoredetails,review\nthe nbkmiputil and nbwebservice logs. If the issue persists, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue."
    },
    "1296": {
        "code": 1296,
        "desc": "The KMS configuration cannot be validated.",
        "first_action": "Ensure that the nbkms service is up and running.",
        "full_action": "Ensure that the nbkms service is up and running."
    },
    "1297": {
        "code": 1297,
        "desc": "The KMS key cannot be created.",
        "first_action": "EnsurethattherequiredKMSkeyattributesareprovided.",
        "full_action": "EnsurethattherequiredKMSkeyattributesareprovided."
    },
    "1298": {
        "code": 1298,
        "desc": "Cannot communicate with one or more key management servers.",
        "first_action": "Run the nbkmscmd -validateKMSConfig -name <KMS",
        "full_action": "Run the nbkmscmd -validateKMSConfig -name <KMS\nConfiguration Name> command to retrieve and review the error details. You can\nuse the nbkmscmd -listKMSConfig command to see the configured KMS server\nand the <KMS Configuration Name>."
    },
    "1299": {
        "code": 1299,
        "desc": "The KMS configuration pre-check failed.",
        "first_action": "You need to specify either credId or pkiAttributes. Do not specify both at",
        "full_action": "Verify the following as needed:\n■ You need to specify either credId or pkiAttributes. Do not specify both at\nthe same time.\n■ Verify that you have one of the following mandatory fields: credId or\npkiAttributes.\n■ Verify that the mandatory field kmsServerAttributes is not blank.\n■ Review the certificate. The certificate is mandatory and it cannot be blank.\n■ Review the CA Certificate. The CA Certificate is mandatory and it cannot be\nblank.\n■ Review the private key. The private key is mandatory and it cannot be blank.\n■ Verify that NBKMS is not used. The operation is not supported for that KMS type."
    },
    "1304": {
        "code": 1304,
        "desc": "Failed to update key in KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1305": {
        "code": 1305,
        "desc": "Failed to update key group in KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1306": {
        "code": 1306,
        "desc": "Failed to delete key in KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1307": {
        "code": 1307,
        "desc": "Failed to delete key group in KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1308": {
        "code": 1308,
        "desc": "Failed to create key group in KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1309": {
        "code": 1309,
        "desc": "Failed to modify Host Master Key.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1310": {
        "code": 1310,
        "desc": "Failed to modify Key Protection Key.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1311": {
        "code": 1311,
        "desc": "Failed to recover key from KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation runs with the REST API, the request payload may be invalid.\nReview the API documentation for the correct request payload.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1312": {
        "code": 1312,
        "desc": "Failed to fetch key group from KMS.",
        "first_action": "Confirm that the NetBackup KMS is configured.",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the NetBackup KMS is configured.\n■ If the operation continues to fail, contact Cohesity Technical Support."
    },
    "1401": {
        "code": 1401,
        "desc": "Invalid arguments received",
        "first_action": "Ensure that all the required parameters are passed with",
        "full_action": "Ensure that all the required parameters are passed with\nthe correct values."
    },
    "1402": {
        "code": 1402,
        "desc": "Hold ID or Hold name argument is invalid",
        "first_action": "Checkthe-holdidand-holdnameoptionsforvalidvalues.",
        "full_action": "Checkthe-holdidand-holdnameoptionsforvalidvalues."
    },
    "1403": {
        "code": 1403,
        "desc": "Backup ID argument is invalid",
        "first_action": "Check the -backupid option for a valid value.",
        "full_action": "Check the -backupid option for a valid value."
    },
    "1405": {
        "code": 1405,
        "desc": "No images are found.",
        "first_action": "Check that the -backupid option is for a valid image.",
        "full_action": "Check that the -backupid option is for a valid image."
    },
    "1407": {
        "code": 1407,
        "desc": "Invalid hold state",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "1408": {
        "code": 1408,
        "desc": "Database error",
        "first_action": "Make sure that the Hold database and the DBM services",
        "full_action": "Make sure that the Hold database and the DBM services\nare running."
    },
    "1409": {
        "code": 1409,
        "desc": "Unable to connect to database",
        "first_action": "Make sure that the Hold database and the DBM services",
        "full_action": "Make sure that the Hold database and the DBM services\nare running."
    },
    "1410": {
        "code": 1410,
        "desc": "No data found",
        "first_action": "Make sure that all the required parameters are passed",
        "full_action": "Make sure that all the required parameters are passed\nwith their correct values."
    },
    "1411": {
        "code": 1411,
        "desc": "Catalog error",
        "first_action": "Check that the image copy on which the hold operation",
        "full_action": "Check that the image copy on which the hold operation\nis applied is valid and not expired."
    },
    "1412": {
        "code": 1412,
        "desc": "Hold record is being updated",
        "first_action": "Retry the operation at a later time or restart the nbim",
        "full_action": "Retry the operation at a later time or restart the nbim\nservice."
    },
    "1413": {
        "code": 1413,
        "desc": "Requested hold is not found",
        "first_action": "Check the -holdname and -holdid options. You can use",
        "full_action": "Check the -holdname and -holdid options. You can use\nnbholdutil -list command."
    },
    "1414": {
        "code": 1414,
        "desc": "Duplicate hold found",
        "first_action": "Try a different name.",
        "full_action": "Try a different name."
    },
    "1415": {
        "code": 1415,
        "desc": "Duplicate image found",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1416": {
        "code": 1416,
        "desc": "Partially failed due to duplicate image",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1417": {
        "code": 1417,
        "desc": "Partially failed due to unhold image",
        "first_action": "Make sure that you provide the correct backup ID and",
        "full_action": "Make sure that you provide the correct backup ID and\nthat it is present in the current hold."
    },
    "1418": {
        "code": 1418,
        "desc": "Requested image is not found",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1419": {
        "code": 1419,
        "desc": "Partially failed due to invalid image copy",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1420": {
        "code": 1420,
        "desc": "Cannot expire on hold image copy.",
        "first_action": "Remove all holds from this backup image. Or remove",
        "full_action": "Remove all holds from this backup image. Or remove\nholds from all images on this backup ID to expire the backup image."
    },
    "1421": {
        "code": 1421,
        "desc": "Active holds cannot be changed",
        "first_action": "Restart the NBIM service",
        "full_action": "Restart the NBIM service"
    },
    "1422": {
        "code": 1422,
        "desc": "Cannot deassign media on hold",
        "first_action": "Lift the holds on the image copies that are backed up on",
        "full_action": "Lift the holds on the image copies that are backed up on\nthe media being de-assigned."
    },
    "1423": {
        "code": 1423,
        "desc": "Unable to retrieve hold status of the image copies",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1425": {
        "code": 1425,
        "desc": "Requested hold is not found",
        "first_action": "Use the nbholdutil -list to list all holds. Check that",
        "full_action": "Use the nbholdutil -list to list all holds. Check that\nthe specified -holdname and -holdid options are valid."
    },
    "1426": {
        "code": 1426,
        "desc": "Retired holds cannot be changed",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "1500": {
        "code": 1500,
        "desc": "Storage unit does not exist or cannot be used where specified",
        "first_action": "VerifythatthespecifiedstorageunitorstorageunitgroupexistsintheNetBackup",
        "full_action": "Do the following, as appropriate:\n■ VerifythatthespecifiedstorageunitorstorageunitgroupexistsintheNetBackup\ndatabase.\n■ Verify that the specified storage unit is not of type BasicDisk or Staging,\nbecause storage lifecycle policies do not support them.\n■ Verify that the storage unit is not specified for snapshot destinations in storage\nlifecyclepolicy.Snapshotdestinationsdonotrequireastorageunitinthestorage\nlifecycle policy."
    },
    "1501": {
        "code": 1501,
        "desc": "Source operation cannot be used where specified",
        "first_action": "Verify that the specified source refers to a valid destination in the list of",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified source refers to a valid destination in the list of\ndestinations in storage lifecycle policy.\n■ Verify that the Backup or Snapshot destination type does not have any source\nspecified. If you use nbstl to configure storage lifecycle policy, use value zero\n(0) as the source for a backup or a snapshot destination type.\n■ Verify that the destination that refers to the specified source is not a Snapshot\ndestinationtype.NetBackupcannotduplicateabackupimagethatusessnapshot\ncopy as a source.\n■ Verify that the specified source does not refer to the destination itself for which\nthe source is mentioned.\n■ Verify that the specified list of destinations in a storage lifecycle has a circular\ndependency for the source.\n■ For cloud snapshot replication, the source must be snapshot operation."
    },
    "1502": {
        "code": 1502,
        "desc": "Retention type cannot be used where specified",
        "first_action": "Verify that the retention type that you specify in the storage lifecycle policy is",
        "full_action": "Do the following, as appropriate:\n■ Verify that the retention type that you specify in the storage lifecycle policy is\neither of Fixed, Staged capacity managed, or Expire after duplication.\n■ Verify that the Expire after duplication retention type is used for a destination\nonly if it is specified as a source to other destinations in storage lifecycle policy.\n■ Verify that the Staged capacity managed retention type is used in storage\nlifecyclepolicyonlyforthediskdestinationsthatsupportCapacitymanagement\ncapabilities.\n■ Verify that the Snapshot destination type in storage lifecycle policy uses Fixed\nretention type only.\n■ For cloud snapshot replication only, fixed retention type is supported."
    },
    "1503": {
        "code": 1503,
        "desc": "Volume pool does not exist or cannot be used where specified",
        "first_action": "Verify that the specified volume pool exists in NetBackup database.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified volume pool exists in NetBackup database.\n■ Verify that the volume pool is not specified for the Backup destination type in\nstorage lifecycle policy.\n■ Verify that the volume pool is not specified for the Snapshot destination type\nin storage lifecycle policy.\n■ Verify that the volume pool is not specified for the Duplication destination type\nthat uses disk storage units in storage lifecycle policy."
    },
    "1504": {
        "code": 1504,
        "desc": "Server group does not exist or cannot be used where specified",
        "first_action": "Verify that the specified media server group exists in NetBackup database.",
        "full_action": "Do the following, as appropriate:\n■ Verify that the specified media server group exists in NetBackup database.\n■ Verify that the media server group is not specified for Backup destination types\nin storage lifecycle policy.\n■ Verify that the server group is not specified for Snapshot destination types in\nstorage lifecycle policy.\n■ Verify that the media server group is not specified for Duplication destination\ntypes that use disk storage unit in storage lifecycle policy."
    },
    "1505": {
        "code": 1505,
        "desc": "Alternate read server does not exist or cannot be used where specified",
        "first_action": "VerifythatthespecifiedalternatereadserverexistsintheNetBackupdatabase.",
        "full_action": "Do the following, as appropriate:\n■ VerifythatthespecifiedalternatereadserverexistsintheNetBackupdatabase.\n■ VerifythatthealternatereadserverisnotspecifiedforBackupdestinationtypes\nin storage lifecycle policy.\n■ Verify that the alternate read server is not specified for Snapshot destination\ntypes in storage lifecycle policy."
    },
    "1506": {
        "code": 1506,
        "desc": "Data classification does not exist",
        "first_action": "Verify that the specified data classification exists in the",
        "full_action": "Verify that the specified data classification exists in the\nNetBackup database."
    },
    "1507": {
        "code": 1507,
        "desc": "Invalid deferred operation flag",
        "first_action": "Ifyouusedthenbstl -defopcommand,makesurethatthespecifiedargument",
        "full_action": "Do the following:\n■ Ifyouusedthenbstl -defopcommand,makesurethatthespecifiedargument\nis one of the following: f, F, t, or T.\nFor more information on the nbstl command, see the NetBackup Commands\nReference Guide.\n■ Make sure that the flag is not set for the primary SLP operations: Backup,\nsnapshot, and import.\n■ Make sure that the source copy has fixed retention.\n■ Refer to the detailed log messages for more details."
    },
    "1508": {
        "code": 1508,
        "desc": "Storage lifecycle policy exceeds maximum copies",
        "first_action": "Verify that the number of destinations that you specify in",
        "full_action": "Verify that the number of destinations that you specify in\nthe storage lifecycle policy does not exceed 10."
    },
    "1509": {
        "code": 1509,
        "desc": "Storage lifecycle policy exceeds maximum backup operations",
        "first_action": "4.)",
        "full_action": "Verify that the number of Backup type destinations that\nyou specify in the storage lifecycle policy is less than or equal to 4. (The default\nvalue of the maximum number of allowed simultaneous copies parameter is\n4.)"
    },
    "1510": {
        "code": 1510,
        "desc": "Storage lifecycle policy cannot have more than one snapshot operation",
        "first_action": "Verify that the storage lifecycle policy is not configured",
        "full_action": "Verify that the storage lifecycle policy is not configured\nwith more than one “Snapshot” type of destinations."
    },
    "1511": {
        "code": 1511,
        "desc": "Storagelifecyclepolicymusthaveatleastonefixedretentionorsnapshot rotation operation",
        "first_action": "Verify that the specified storage lifecycle policy has at",
        "full_action": "Verify that the specified storage lifecycle policy has at\nleast one destination that is configured with a Fixed retention type."
    },
    "1512": {
        "code": 1512,
        "desc": "Storagelifecyclepolicymusthaveatleastonebackup,import,orsnapshot operation",
        "first_action": "Verify that the storage lifecycle policy has at least one",
        "full_action": "Verify that the storage lifecycle policy has at least one\nBackup type of destination."
    },
    "1513": {
        "code": 1513,
        "desc": "Invalid priority",
        "first_action": "Verify that the duplication priority that you specify in the",
        "full_action": "Verify that the duplication priority that you specify in the\nstorage lifecycle policy is in the range of 0 to 99999."
    },
    "1514": {
        "code": 1514,
        "desc": "Invalid operation type",
        "first_action": "Verify that the destination type that you specify on each destination in storage",
        "full_action": "Do the following, as appropriate:\n■ Verify that the destination type that you specify on each destination in storage\nlifecycle policy is either Backup, Duplication, or Snapshot.\n■ If you are use the nbstl command to configure storage lifecycle policy, the\nfollowing are the valid values for the destination type: 0 indicates Backup, 1\nindicates Duplication, and 2 indicates Snapshot."
    },
    "1515": {
        "code": 1515,
        "desc": "Multiplexing value is not valid or cannot be used where specified NetBackup status codes 363 NetBackup status codes",
        "first_action": "If you use the nbstl command to configure storage lifecycle policy, then verify",
        "full_action": "Do the following, as appropriate:\n■ If you use the nbstl command to configure storage lifecycle policy, then verify\nthat the valid values are used to indicate the preserve multiplexing flag for each\ndestination.Thevalue“T”or“t”indicatestrue(Preservemultiplexing).Thevalue\n“F” or “f” indicates false (do not preserve multiplexing).\n■ Verify that destinations of type Backup are not configured to preserve\nmultiplexing.\n■ Verify that destinations of type Snapshot are not configured to preserve\nmultiplexing.\n■ VerifythatdestinationsoftypeDuplicationthatare usingdisk storageunitsare\nnot configured to preserve multiplexing."
    },
    "1516": {
        "code": 1516,
        "desc": "All storage units or groups must be on the same media server",
        "first_action": "Verify that all the destinations of type Backup are",
        "full_action": "Verify that all the destinations of type Backup are\naccessible by at least one common media server."
    },
    "1517": {
        "code": 1517,
        "desc": "Invalid retention level",
        "first_action": "Verify that the retention level that you specify on each",
        "full_action": "Verify that the retention level that you specify on each\ndestination in storage lifecycle policy is in the range of 0 to 100."
    },
    "1518": {
        "code": 1518,
        "desc": "Backup image is not supported by storage lifecycle policy",
        "first_action": "Verify that if a NetBackup policy is configured to perform snapshot backups and",
        "full_action": "Do the following, as appropriate:\n■ Verify that if a NetBackup policy is configured to perform snapshot backups and\nusesstoragelifecyclepolicyasitsstoragedestination,thenthespecifiedstorage\nlifecycle policy must be configured with a snapshot destination. Otherwise,\nbackupimagesthatarecreatedbythoseNetBackuppoliciesarenotprocessed\nfurther by storage lifecycle policy for any lifecycle operations.\n■ Verify that NetBackup policies that use the storage lifecycle policy as a storage\ndestination are not configured to perform “snapshots-only” operations. They\nmustcreatebackupsinadditiontosnapshots.TheStoragelifecyclepolicyeven\nthoughconfiguredwithasnapshotdestination,performslifecycleoperationson\nsuch images only if they have at least one backup copy."
    },
    "1519": {
        "code": 1519,
        "desc": "Images are in process",
        "first_action": "Wait until the image processing is done, then retry the",
        "full_action": "Wait until the image processing is done, then retry the\noperation. Or, terminate the SLP processing for the needed images."
    },
    "1521": {
        "code": 1521,
        "desc": "Database not available",
        "first_action": "Make sure that the database service is running.",
        "full_action": "Do one of the following:\n■ Make sure that the database service is running.\n■ Make sure that the disk is not full."
    },
    "1522": {
        "code": 1522,
        "desc": "Error executing database query",
        "first_action": "Examinethelogfilesforthenbstservprocessororiginator",
        "full_action": "Examinethelogfilesforthenbstservprocessororiginator\nID 369 for more information."
    },
    "1523": {
        "code": 1523,
        "desc": "Invalid fragment",
        "first_action": "Check the NetBackup Problems Report for details.",
        "full_action": "Check the NetBackup Problems Report for details."
    },
    "1524": {
        "code": 1524,
        "desc": "Duplicate image record",
        "first_action": "Check the NetBackup Problems Report for details.",
        "full_action": "Do one of the following:\n■ Check the NetBackup Problems Report for details.\n■ Delete the duplicate image from storage because NetBackup cannot do it."
    },
    "1525": {
        "code": 1525,
        "desc": "Invalid lsu",
        "first_action": "Configure the LSU as a valid disk volume in a valid disk pool, and create a valid",
        "full_action": "Do one of the following:\n■ Configure the LSU as a valid disk volume in a valid disk pool, and create a valid\nstorage unit for it. Associate this storage unit with an import storage lifecycle\npolicy.\n■ Reconfigure the replication on your storage devices to use a replication target\ndisk volume (LSU) that NetBackup recognizes."
    },
    "1526": {
        "code": 1526,
        "desc": "Storage lifecycle policy exceeds maximum import operations",
        "first_action": "Configurethestoragelifecyclepolicywithonlyoneimport",
        "full_action": "Configurethestoragelifecyclepolicywithonlyoneimport\ndestination."
    },
    "1527": {
        "code": 1527,
        "desc": "Storagelifecyclepolicycanhaveonlyoneofbackup,import,andsnapshot operations",
        "first_action": "Configurethestoragelifecyclepolicywithonlyoneimport",
        "full_action": "Configurethestoragelifecyclepolicywithonlyoneimport\ndestination and additional destinations of type duplication only."
    },
    "1528": {
        "code": 1528,
        "desc": "The source copy for an Auto Image Replication is not capable of replication",
        "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectSLPdestination",
        "full_action": "Do one of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectSLPdestination\nindex number for the source copy.\n■ Use the appropriate indentation to indicate the correct source storage lifecycle\npolicy destination in the GUI.\n■ Ensure that the source uses a storage unit that is capable of replication. The\nstorageunitisspecifiedbytheSLPdestinationindexontheCLIorbyindentation\nin the GUI. That is, check the properties of the disk volumes within the disk pool\nthat the storage unit specifies.\n■ After you set a replication target, you must refresh the disk pool. In the\nNetBackup Administration Console, in the left pane, expand Media and\nDevice Management Devices > Disk Pools. In the right pane, select the disk\npoolthatyouwanttoupdate.IntheChangeDiskPooldialogbox,clickRefresh\nto configure the replication settings for the disk pool."
    },
    "1529": {
        "code": 1529,
        "desc": "ThesourcecopyforAutoImageReplicationmustspecifyastorageunit",
        "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle",
        "full_action": "Do one or more of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number for the source copy.\n■ Ensure that you use the appropriate indentation to indicate the correct source\nstorage lifecycle policy destination in the GUI.\n■ Ensure that the source that is specified by either the storage lifecycle policy\ndestination index on the CLI or by indentation in the GUI uses a storage unit\n(notastorageunitgroup,storagelifecyclepolicyorAnyAvailable)thatiscapable\nof replication. That is, check the properties of the disk volumes within the disk\npool that the storage unit specifies.\n■ Ensurethatyouarenotusingastorageunitgroupforreplication.Forthesource\ncopy, select a storage unit that is not in a storage unit group. For the target, do\nnot select a storage unit group."
    },
    "1530": {
        "code": 1530,
        "desc": "Only one Auto Image Replication allowed per copy",
        "first_action": "Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle",
        "full_action": "Do one of the following:\n■ Ifyouusethecommandline,ensurethatyouspecifythecorrectstoragelifecycle\npolicy destination index number for the source copy.\n■ Ensure that you use the appropriate indentation to indicate the correct source\nstorage lifecycle policy destination in the GUI.\n■ Ensure that the source that is specified by either the storage lifecycle policy\ndestination index on the CLI or by indentation in the GUI does not have more\nthan one Auto Image Replication destination specifying it as its source copy."
    },
    "1531": {
        "code": 1531,
        "desc": "Animportstoragelifecyclepolicyrequiresonecopywithremoteretention type",
        "first_action": "Change one of the destinations in the storage lifecycle policy to use the remote",
        "full_action": "Add a destination to the storage lifecycle policy that uses\nthe remote retention type.\nDo one of the following:\n■ Change one of the destinations in the storage lifecycle policy to use the remote\nretention type. If the storage lifecycle policy has only one destination that is an\nimport destination, then it must be a remote retention type.\n■ Addadestinationtothestoragelifecyclepolicywhichusestheremoteretention\ntype."
    },
    "1532": {
        "code": 1532,
        "desc": "Import failed because the imported image specifies an SLP name which does not exist",
        "first_action": "Verifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured",
        "full_action": "Do one of the following:\n■ Verifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\nanAutoImageReplicationmatchesthestoragelifecyclepolicyinthedestination\ndomain where you configured the import. The match is case-sensitive.\n■ Add a storage lifecycle policy with an import destination using the same name\nas your storage lifecycle policy in the source domain."
    },
    "1533": {
        "code": 1533,
        "desc": "Import failed because the imported image data class is different than the SLP data class",
        "first_action": "Changethedataclassificationofthestoragelifecyclepolicyinthesourcedomain",
        "full_action": "Do one of the following:\n■ Changethedataclassificationofthestoragelifecyclepolicyinthesourcedomain\nwhere you configured an Auto Image Replication to match the following: the\ndata classification in the destination domain where you have configured the\nimport. The match is case-sensitive.\nVerifythatthestoragelifecyclepolicyinthesourcedomainwhereyouconfigured\nan Auto Image Replication matches the following: the storage lifecycle policy in\nthe destination domain where you configured the import. The match is\ncase-sensitive.\n■ Change the data classification of the storage lifecycle policy in the destination\ndomainwhereyouconfiguredanAutoImageReplicationtomatchthefollowing:\nthe data classification in the source domain where you have configured the\nimport. The match is case-sensitive."
    },
    "1534": {
        "code": 1534,
        "desc": "Import failed because the imported image specifies an SLP name with no import operation",
        "first_action": "Useadifferentstoragelifecyclepolicynameinthesource",
        "full_action": "Useadifferentstoragelifecyclepolicynameinthesource\ndomain where you configured an Auto Image Replication. This name must match\na storage lifecycle policy name with an import destination in the destination domain\nwhere you have configured the import. The match is case-sensitive."
    },
    "1535": {
        "code": 1535,
        "desc": "Import failed because the imported image backup ID conflicts with an existing image",
        "first_action": "Delete the duplicate image from storage because",
        "full_action": "Delete the duplicate image from storage because\nNetBackup cannot delete it. Use the following command:\n# bpimage -deletecopy # -backupid backupid\nwhere # is the copy number of the image that you want to delete."
    },
    "1536": {
        "code": 1536,
        "desc": "The storage unit or storage unit group cannot be deleted because an SLP references it",
        "first_action": "Run the following command to display all versions of each SLP:",
        "full_action": "Use the nbstl command to view and change the older\nSLP versions. Do the following in the order listed:\n■ Run the following command to display all versions of each SLP:\n# nbstl -L -all_versions\n■ Determine the name and version of each SLP that references the storage unit\nor storage unit group.\n■ Run the following command to replace the storage unit (group) to be deleted\nwith the name of a different storage unit.\n# nbstl <SLP_name> -modify_version <version_number>...\nFor more information on storage lifecycle policy versions, see the NetBackup\nAdministrator’s Guide, Volume I."
    },
    "1537": {
        "code": 1537,
        "desc": "Backuppolicyandstoragelifecyclepolicyhaveconflictingconfigurations",
        "first_action": "In the NetBackup Administration Console, locate the",
        "full_action": "In the NetBackup Administration Console, locate the\nChange Storage Lifecycle Policy dialog for the SLP in question. Then run the\nValidation Report to display the specific conflicts that pertain to the SLP. Correct\nthose conflicts."
    },
    "1538": {
        "code": 1538,
        "desc": "Data classification in the SLP conflicts with backup policy",
        "first_action": "Change the policy to reference an SLP with a matching data classification",
        "full_action": "Do one of the following:\n■ Change the policy to reference an SLP with a matching data classification\n■ Change the data classification in either the backup policy or the SLP so that\nthey match."
    },
    "1539": {
        "code": 1539,
        "desc": "Backuppolicygeneratessnapshotsbutstoragelifecyclepolicydoesnot handle them",
        "first_action": "Change the backup policy to use an SLP that provides snapshot support.",
        "full_action": "Do one of the following:\n■ Change the backup policy to use an SLP that provides snapshot support.\n■ Change the backup policy so it does not generate snapshots.\n■ Change the SLP to include a snapshot operation."
    },
    "1540": {
        "code": 1540,
        "desc": "SLP expects snapshots but backup policy does not create them with SLP management enabled",
        "first_action": "Find and expire the existing snapshot which is no longer",
        "full_action": "Find and expire the existing snapshot which is no longer\nneeded."
    },
    "1541": {
        "code": 1541,
        "desc": "Snapshotcreationfailed.Themaximumsnapshotlimitforthepolicyhas been exceeded and no existing snapshots are eligible for expiration.",
        "first_action": "Do not try to expire a snapshot copy that is still pending",
        "full_action": "Do not try to expire a snapshot copy that is still pending\nor has not reached its retention period. Check the maximum snapshot limit setting\nin your Backup Policy>Attributes>Snapshot Options."
    },
    "1542": {
        "code": 1542,
        "desc": "An existing snapshot is no longer valid or cannot be mounted for subsequent operations",
        "first_action": "Run a new backup job to generate a new snapshot.",
        "full_action": "Run a new backup job to generate a new snapshot."
    },
    "1543": {
        "code": 1543,
        "desc": "Policy type is not compatible with SLP operations",
        "first_action": "Choose a different SLP that is compatible with the policy",
        "full_action": "Choose a different SLP that is compatible with the policy\ntype."
    },
    "1545": {
        "code": 1545,
        "desc": "Schedule type is not compatible with SLP operations",
        "first_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule",
        "full_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule\ntype."
    },
    "1546": {
        "code": 1546,
        "desc": "Capacity managed retention type is not compatible with SLP operations",
        "first_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule",
        "full_action": "ChooseadifferentSLPthatiscompatiblewiththeschedule\ntype."
    },
    "1547": {
        "code": 1547,
        "desc": "Expire after copy retention requires a dependent copy",
        "first_action": "No operations can be performed on this snapshot. Expire",
        "full_action": "No operations can be performed on this snapshot. Expire\nit from the catalog."
    },
    "1548": {
        "code": 1548,
        "desc": "Retention type is not compatible with snapshot operation",
        "first_action": "Choose a different retention type.",
        "full_action": "Do one of the following:\n■ Choose a different retention type.\n■ If the backup policy is configured for Replication Director, open the backup\npolicy. In the Attributes tab, click Options to display the Replication Director\noptions. If the values for the Maximum Snapshots do not include Managed\nby SLP Retention, select 0 (zero) instead. A value of 0 indicates the Managed\nby SLP Retention selection.\n■ For cloud snapshot replication only, fixed retention type is supported."
    },
    "1549": {
        "code": 1549,
        "desc": "TIR information selection is not compatible with SLP operations",
        "first_action": "Remove the TIR information selection from the backup policy.",
        "full_action": "Do one of the following:\n■ Remove the TIR information selection from the backup policy.\n■ Choose a different SLP to use with the backup policy."
    },
    "1552": {
        "code": 1552,
        "desc": "The source and target storage units are not valid replication partners.",
        "first_action": "Run the following command to get a list of matching target storage units or",
        "full_action": "Do one of the following:\n■ Run the following command to get a list of matching target storage units or\ngroups for the given source storage unit or group:\n# nbdevquery -listreptargets -stunit source_stu_or_group\n■ Rerun the nbstl command with the target storage unit or group from the list\nthat the nbdevquery command displays.\n■ Run the bpstsinfo -li command and check the output for the storage server\nname. The name that you use to create the storage server must match this\nname.\n■ Ensure that NetBackup is configured after the storage server configuration is\ncomplete. If not, use the Change Disk Pool dialog of the NetBackup\nAdministration Console or the nbdevconfig -updatedp command to refresh\neach disk pool of the storage server."
    },
    "1553": {
        "code": 1553,
        "desc": "Checkpoints are not allowed with SLP operations",
        "first_action": "Remove the checkpoint restart selection from the backup policy.",
        "full_action": "Do one of the following:\n■ Remove the checkpoint restart selection from the backup policy.\n■ Choose a different SLP to use with the backup policy."
    },
    "1554": {
        "code": 1554,
        "desc": "Storage unit snapshot capability is not compatible with operation characteristics",
        "first_action": "Chooseastorageunitthatsupportsthecorrectcapabilities.",
        "full_action": "Chooseastorageunitthatsupportsthecorrectcapabilities."
    },
    "1556": {
        "code": 1556,
        "desc": "The SLP deletion failed because a backup policy refers to it.",
        "first_action": "Change the backup policies to use other SLPs or storage",
        "full_action": "Change the backup policies to use other SLPs or storage\nunits. Then try again to delete the SLP."
    },
    "1557": {
        "code": 1557,
        "desc": "Must specify mirror retention when target storage unit is mirror capable.",
        "first_action": "If you used a nbstl command to configure the storage",
        "full_action": "If you used a nbstl command to configure the storage\nlifecycle policy, rerun the command after the following: Specify the mirror retention\ntype for the replication operation corresponding to the storage unit that is\nmirror-capable.Usethebpstulist -Ucommandtoviewthestorageunitproperties.\nIf the error occurs when you configure the storage lifecycle policy by using the GUI,\nsubmit a problem report and provide the appropriate logs."
    },
    "1558": {
        "code": 1558,
        "desc": "Mirror retention is not allowed when target storage unit is not mirror capable.",
        "first_action": "U command to view the storage unit properties. If the error occurs when you",
        "full_action": "If you used a nbstl command to configure the storage\nlifecycle policy, rerun the command after you do the following: Specify the\nappropriate retention type (other than mirror retention) for the replication operation\ncorresponding to the storage unit that is non-mirror capable. Use the bpstulist\n-U command to view the storage unit properties. If the error occurs when you\nconfigurethestoragelifecyclepolicybyusingtheGUI,submitaproblemreportand\nprovide the appropriate logs."
    },
    "1559": {
        "code": 1559,
        "desc": "SLP referenced in policy or schedule not found",
        "first_action": "Check the spelling of the SLP used in the policy. The SLP",
        "full_action": "Check the spelling of the SLP used in the policy. The SLP\ndisplayed in the NetBackup Administration Console or the nbstl command can\nbe used to list the SLPs that have been defined. Select one of the defined SLPs to\nuse in the backup policy or create one with the desired name."
    },
    "1560": {
        "code": 1560,
        "desc": "Fixed or rotation retention required without a replication operation",
        "first_action": "Add an operation with the required retention or change",
        "full_action": "Add an operation with the required retention or change\nthe retention of an existing operation."
    },
    "1561": {
        "code": 1561,
        "desc": "Policy using NDMP conflicts with multiple Backup From Snapshot operations in storage lifecycle policy",
        "first_action": "Change the policy type or data mover type so that it is not NDMP.",
        "full_action": "Do one of the following:\n■ Change the policy type or data mover type so that it is not NDMP.\n■ Use a different SLP that does not contain multiple Backup From Snapshot\noperations."
    },
    "1562": {
        "code": 1562,
        "desc": "Backup schedule generates snapshots but storage lifecycle policy does not handle them",
        "first_action": "Select an SLP that begins with a Snapshot operation so",
        "full_action": "Select an SLP that begins with a Snapshot operation so\nthat it can process the snapshot generated by the backup policy and schedule."
    },
    "1563": {
        "code": 1563,
        "desc": "SLP expects snapshots but backup schedule does not create them",
        "first_action": "Select an SLP that does not begin with a Snapshot",
        "full_action": "Select an SLP that does not begin with a Snapshot\noperation."
    },
    "1564": {
        "code": 1564,
        "desc": "Storage lifecycle policy contains errors",
        "first_action": "Check the other errors that are displayed.",
        "full_action": "Check the other errors that are displayed."
    },
    "1565": {
        "code": 1565,
        "desc": "PolicysnapshotmethodisnotcompatiblewithSLPsnapshotoperations NetBackup status codes 380 NetBackup status codes",
        "first_action": "Use a different SLP that does not contain unsupported",
        "full_action": "Use a different SLP that does not contain unsupported\noperations."
    },
    "1566": {
        "code": 1566,
        "desc": "Storage unit required for snapshot operation when no other operation present",
        "first_action": "Add a storage unit to the Snapshot operation.",
        "full_action": "Add a storage unit to the Snapshot operation."
    },
    "1567": {
        "code": 1567,
        "desc": "Only one NDMP backup of a snapshot per backup ID is allowed",
        "first_action": "Modify the SLP so that it contains only one Backup From Snapshot operation.",
        "full_action": "Do one of the following:\n■ Modify the SLP so that it contains only one Backup From Snapshot operation.\n■ Modify the backup policy so that it uses a different SLP."
    },
    "1568": {
        "code": 1568,
        "desc": "OnlyoneIndexFromSnapshotoperationisallowedperstoragelifecycle policy",
        "first_action": "Change the backup policies to use other SLPs or storage",
        "full_action": "Change the backup policies to use other SLPs or storage\nunits. Then try again to delete the SLP."
    },
    "1569": {
        "code": 1569,
        "desc": "Snapshot storage unit is not configured for primary snapshots. It cannot be used in snapshot operation.",
        "first_action": "Select a different storage unit that is snapshot-capable to use in the Snapshot",
        "full_action": "Do one of the following:\n■ Select a different storage unit that is snapshot-capable to use in the Snapshot\noperation.\n■ Change the configuration of the desired storage unit so that it supports primary\nsnapshot operations."
    },
    "1570": {
        "code": 1570,
        "desc": "Policy type does not support Index from Snapshot",
        "first_action": "Select a different SLP that does not contain an Index",
        "full_action": "Select a different SLP that does not contain an Index\nfrom Snapshot operation"
    },
    "1571": {
        "code": 1571,
        "desc": "Data mover type specified in policy does not support Index from Snapshot",
        "first_action": "Select a different SLP that does not contain an Index",
        "full_action": "Select a different SLP that does not contain an Index\nfrom Snapshot operation."
    },
    "1572": {
        "code": 1572,
        "desc": "Storage unit must be specified for this operation",
        "first_action": "Add a storage unit to the SLP operation.",
        "full_action": "Add a storage unit to the SLP operation."
    },
    "1573": {
        "code": 1573,
        "desc": "Backup image cannot be expired because its SLP processing is not yet complete",
        "first_action": "Wait until SLP processing for that image is complete, then retry the expiration",
        "full_action": "Do one of the following:\n■ Wait until SLP processing for that image is complete, then retry the expiration\noperation.\n■ Use the nbstlutil -cancel command to cancel further processing on the\nrelevant image. Then retry the expiration operation.\n■ Add the -force_not_complete option to the bpexpdate command to force\nexpiration even if the image-copy is not SLP complete."
    },
    "1574": {
        "code": 1574,
        "desc": "Data Classification name cannot be 'Any' while creating new data classification",
        "first_action": "Use a different name and try again.",
        "full_action": "Use a different name and try again."
    },
    "1575": {
        "code": 1575,
        "desc": "Data Classification auto creation failed",
        "first_action": "Manually create the data classification on the master",
        "full_action": "Manually create the data classification on the master\nserver with the same name as that of the image being imported."
    },
    "1576": {
        "code": 1576,
        "desc": "Topology validation failed",
        "first_action": "Check that the media servers that are associated with the storage servers are",
        "full_action": "Do the following:\n■ Check that the media servers that are associated with the storage servers are\nrunning.\n■ Check the connectivity between the media server (or client) and the storage\nserver (NetApp OnCommand server).\n■ Check the detailed messages supplied with this error to determine the\nvendor-specific errors."
    },
    "1577": {
        "code": 1577,
        "desc": "StorageunitintheSLPdoesnotmatchtheacceleratorattributeinpolicy",
        "first_action": "SelectadifferentstorageunitfortheSLPthatdoessupport",
        "full_action": "SelectadifferentstorageunitfortheSLPthatdoessupport\nthe accelerator backup operation."
    },
    "1578": {
        "code": 1578,
        "desc": "Invalid window close options",
        "first_action": "If you used the nbstl -wcopt command, make sure that",
        "full_action": "If you used the nbstl -wcopt command, make sure that\nthe specified argument is either SFN or SHN.\nFormoreinformationonthenbstlcommand,pleaseseetheNetBackupCommands\nReference Guide."
    },
    "1579": {
        "code": 1579,
        "desc": "One or more images were not processed because the window closed",
        "first_action": "This behavior is expected and no action is necessary.",
        "full_action": "This behavior is expected and no action is necessary.\nProcessing resumes when the next window opens."
    },
    "1580": {
        "code": 1580,
        "desc": "VMware policy with PFI enabled requires an SLP",
        "first_action": "Use the VMware policy without Replication Director, or",
        "full_action": "Use the VMware policy without Replication Director, or\nprovide an SLP that has at least a Snapshot operation."
    },
    "1581": {
        "code": 1581,
        "desc": "Non-application consistent VMware policy is not compatible with snapdupe operations",
        "first_action": "Enable Application Consistency, or remove the Backup",
        "full_action": "Enable Application Consistency, or remove the Backup\nfrom Snapshot operation from the SLP definition."
    },
    "1582": {
        "code": 1582,
        "desc": "Application consistent VMware policy requires VM quiesce",
        "first_action": "DisableApplicationConsistencyorenablevirtualmachine",
        "full_action": "DisableApplicationConsistencyorenablevirtualmachine\nquiesce."
    },
    "1583": {
        "code": 1583,
        "desc": "VMware policy with PFI enabled requires VIP auto discovery",
        "first_action": "Enable automatic discovery of virtual machines.",
        "full_action": "Enable automatic discovery of virtual machines."
    },
    "1584": {
        "code": 1584,
        "desc": "VMwarepolicywith'PersistentFrozenImage'enabledrequiresschedule type of Full Backup",
        "first_action": "Useafullscheduleandremoveallincrementalschedules.",
        "full_action": "Useafullscheduleandremoveallincrementalschedules."
    },
    "1585": {
        "code": 1585,
        "desc": "Backup image cannot be expired because not all dependent copies are expired",
        "first_action": "Waitforthedependentimagestobeeligibleforexpiration",
        "full_action": "Waitforthedependentimagestobeeligibleforexpiration\nwhen their SLP state transitions into IMAGE_COMPLETE state. Also, you can\ncancel the SLP operations on the dependent images."
    },
    "1586": {
        "code": 1586,
        "desc": "SLP operation was canceled",
        "first_action": "No action is required.",
        "full_action": "No action is required."
    },
    "1587": {
        "code": 1587,
        "desc": "Storage lifecycle policy cannot have both target and untarget replication to remote master",
        "first_action": "Do not mix the targeted and untargeted replication",
        "full_action": "Do not mix the targeted and untargeted replication\noperation to a remote master."
    },
    "1588": {
        "code": 1588,
        "desc": "Target master server is already used in one of the replications to remote master NetBackup status codes 387 NetBackup status codes",
        "first_action": "Define all targeted replication operations with distinct",
        "full_action": "Define all targeted replication operations with distinct\ntarget master server."
    },
    "1589": {
        "code": 1589,
        "desc": "Cannot connect to specified target master server",
        "first_action": "Check that all services on source domain and target",
        "full_action": "Check that all services on source domain and target\ndomain are running."
    },
    "1590": {
        "code": 1590,
        "desc": "Cannot find specified target import SLP",
        "first_action": "Enter a valid name of the target domain SLP with the",
        "full_action": "Enter a valid name of the target domain SLP with the\nimport operation, in the targeted replication operation of the source domain’s SLP."
    },
    "1591": {
        "code": 1591,
        "desc": "No import SLP(s) found with compatible replication target device.",
        "first_action": "Correct one or more of the possible problems.",
        "full_action": "Correct one or more of the possible problems."
    },
    "1592": {
        "code": 1592,
        "desc": "Trusted master servers are being referred by one or more Storage Lifecycle Policies (SLPs) on the source or target domain. NetBackup status codes 388 NetBackup status codes",
        "first_action": "Delete or change the SLPs so they do not refer to domain",
        "full_action": "Delete or change the SLPs so they do not refer to domain\nB, then try to delete domain B from domain A again."
    },
    "1593": {
        "code": 1593,
        "desc": "Replication Director for VMware policy requires mapped backups",
        "first_action": "Enable mapping.",
        "full_action": "Enable mapping."
    },
    "1594": {
        "code": 1594,
        "desc": "Failed to determine disk media ID",
        "first_action": "Recheck the storage server, disk pool, and storage unit",
        "full_action": "Recheck the storage server, disk pool, and storage unit\nconfigurations."
    },
    "1596": {
        "code": 1596,
        "desc": "Select a storage lifecycle policy that has no snapshot operation as a policy’s Storage Destination NetBackup status codes 389 NetBackup status codes",
        "first_action": "Select a storage lifecycle policy that has no snapshot",
        "full_action": "Select a storage lifecycle policy that has no snapshot\noperation as the policy storage destination."
    },
    "1597": {
        "code": 1597,
        "desc": "Replication Director for Oracle policy requires an SLP",
        "first_action": "Configure an SLP with a Snapshot as the first operation",
        "full_action": "Configure an SLP with a Snapshot as the first operation\nandReplicationasasubsequentoperation.SpecifythisSLPastheOverridepolicy\nstorage selection on the Full schedule."
    },
    "1598": {
        "code": 1598,
        "desc": "Oracle policy with PFI and FI enabled requires an SLP",
        "first_action": "Configure an SLP with a Snapshot as the first operation.",
        "full_action": "Configure an SLP with a Snapshot as the first operation.\nSpecify this SLP as the Override policy storage selection on the Full schedule."
    },
    "1599": {
        "code": 1599,
        "desc": "Application schedule storage selection cannot be a snapshot SLP",
        "first_action": "Specify a non-SLP storage (basic disk, tape, advanced",
        "full_action": "Specify a non-SLP storage (basic disk, tape, advanced\ndisk,etc.)oranSLPwithBackupasthefirstoperationforanOverridepolicystorage\nselection on the Application schedule"
    },
    "1600": {
        "code": 1600,
        "desc": "ThePolicystorageisasnapshotSLPandtheApplicationscheduledoes not override the policy storage selection. Snapshot SLP storage is not allowed on an Application schedule.",
        "first_action": "Specify a non-SLP storage (basic disk, tape, advanced",
        "full_action": "Specify a non-SLP storage (basic disk, tape, advanced\ndisk, etc.) or an SLP with Backup as the first operation for the Policy storage or as\nthe Override policy storage selection on the Application schedule."
    },
    "1601": {
        "code": 1601,
        "desc": "Full schedule requires a snapshot SLP",
        "first_action": "Configure an SLP with a Snapshot as the first operation.",
        "full_action": "Configure an SLP with a Snapshot as the first operation.\nSpecify this SLP as the Override policy storage selection on the Full schedule."
    },
    "1602": {
        "code": 1602,
        "desc": "The Policy storage is not a snapshot SLP and the Full schedule does not override the policy storage selection. Snapshot SLP storage is required on the Full schedule.",
        "first_action": "SpecifyeitheranSLPwithaSnapshotasthefirstoperation",
        "full_action": "SpecifyeitheranSLPwithaSnapshotasthefirstoperation\nfor the Policy storage or as the Override policy storage selection on the Full\nschedule."
    },
    "1603": {
        "code": 1603,
        "desc": "Failed to save target SLP volume information",
        "first_action": "Take action as dictated by the EMM logs.",
        "full_action": "Take action as dictated by the EMM logs."
    },
    "1604": {
        "code": 1604,
        "desc": "No import SLP(s) found with compatible data class.",
        "first_action": "No specific recommended action found in the manual.",
        "full_action": ""
    },
    "1608": {
        "code": 1608,
        "desc": "Theregionassetthatisusedasacloudsnapshotreplicationdestination does not exist. Enter a valid region asset.",
        "first_action": "VerifytheregionassetIDandperformtheoperationagain.",
        "full_action": "VerifytheregionassetIDandperformtheoperationagain."
    },
    "1609": {
        "code": 1609,
        "desc": "The region asset is already used as a cloud snapshot replication destination. Provide a different region asset. NetBackup status codes 392 NetBackup status codes",
        "first_action": "Use multiple schedules or use a different region asset.",
        "full_action": "Use multiple schedules or use a different region asset."
    },
    "1610": {
        "code": 1610,
        "desc": "TheprovidedregionassetsassociatewithadifferentSnapshotManagers. The provided region assets must associate with the same Snapshot Manager.",
        "first_action": "Ensure that specified region assets associate with the",
        "full_action": "Ensure that specified region assets associate with the\nsame Snapshot Manager. Update the cloud provider plug-in configuration details\naccordingly."
    },
    "1611": {
        "code": 1611,
        "desc": "The assets that are subscribed to the protection plan belong to different Snapshot Managers. Subscribed assets must belong to the same Snapshot Manager.",
        "first_action": "FortheassetsthatareassociatedwithdifferentSnapshot",
        "full_action": "FortheassetsthatareassociatedwithdifferentSnapshot\nManagers, create different protection plans."
    },
    "1612": {
        "code": 1612,
        "desc": "Some of the selected assets belong to a Snapshot Manager other than the Snapshot Manager of the snapshot replication destination region asset. The assets must belong to the same Snapshot Manager.",
        "first_action": "Ensure that the region assets associate with the same",
        "full_action": "Ensure that the region assets associate with the same\nSnapshot Manager. Update the cloud provider plug-in configuration details\naccordingly."
    },
    "1613": {
        "code": 1613,
        "desc": "For some of the selected assets, the source region is same as the cloud snapshot replication destination region. The source region and the cloud snapshot replication destination region must be different.",
        "first_action": "The source region and the cloud snapshot replication",
        "full_action": "The source region and the cloud snapshot replication\ndestination region must be different."
    },
    "1614": {
        "code": 1614,
        "desc": "Cloud snapshot replication is supported only for Amazon cloud assets.",
        "first_action": "Skip the assets that do not belong to Amazon cloud",
        "full_action": "Skip the assets that do not belong to Amazon cloud\nprovider."
    },
    "1615": {
        "code": 1615,
        "desc": "Cloud snapshot replication is not supported for the asset type region.",
        "first_action": "Skip the asset with type region.",
        "full_action": "Skip the asset with type region."
    },
    "1616": {
        "code": 1616,
        "desc": "Checkpoints are only allowed for the Backup from Snapshot storage lifecycle policy operation. NetBackup status codes 394 NetBackup status codes",
        "first_action": "UpdatethebackuppolicytouseBackupfromSnapshot",
        "full_action": "UpdatethebackuppolicytouseBackupfromSnapshot\nstorage lifecycle operation before checkpoint functionality is enabled."
    },
    "1617": {
        "code": 1617,
        "desc": "Cloud snapshot indexing is not supported for the specified asset.",
        "first_action": "Ensure that the Snapshot Manager is deployed in the same region as the",
        "full_action": "Perform the following, as appropriate:\n■ Ensure that the Snapshot Manager is deployed in the same region as the\nspecified asset.\n■ Review the Snapshot Manager supported versions for indexing."
    },
    "1618": {
        "code": 1618,
        "desc": "This retention period is incompatible with WORM storage expiration duration. The lock minimum and maximum duration can be found in disk pool properties.Anupdatetodiskpoolpropertiesmaybeneededifconfigurationchanges have been made to the underlying storage.",
        "first_action": "The following procedure may be necessary once you are",
        "full_action": "The following procedure may be necessary once you are\nsure that the retention level matches the range the underlying the storage volume\nallows. This procedure only applies if the NetBackup Administration Console is in\nuse to create the policy.\nTo adjust the retention level\n1 Save the policy schedule with the desired retention level, but with storage\nselected as any available.\n2 Edit the policy again, and now select the desired storage unit in the policy\nattributes."
    },
    "1630": {
        "code": 1630,
        "desc": "WhileconfiguringaNetBackuppolicywiththeCohesitysnapshotoption (VSO) FIM, you must select an SLP as Policy storage destination.",
        "first_action": "Select Policy storage as storage lifecycle policy. If you",
        "full_action": "Select Policy storage as storage lifecycle policy. If you\nselectSTUasthePolicystorageoption,selectOverridepolicystorageselection\nwith the SLP option."
    },
    "1633": {
        "code": 1633,
        "desc": "Invalid media server is provided in the API request.",
        "first_action": "Provide a valid NetBackup media server name.",
        "full_action": "Provide a valid NetBackup media server name."
    },
    "1634": {
        "code": 1634,
        "desc": "Unable to process the EMM request.",
        "first_action": "Check whether the EMM service is up and running.",
        "full_action": "Perform the following as appropriate:\n■ Check whether the EMM service is up and running.\n■ To diagnose the issue, review the EMM server logs for issues and troubleshoot\nas necessary."
    },
    "1635": {
        "code": 1635,
        "desc": "Unable to connect with the EMM server.",
        "first_action": "Troubleshoot any EMM server connection failure issues.",
        "full_action": "Troubleshoot any EMM server connection failure issues."
    },
    "1636": {
        "code": 1636,
        "desc": "Backup time range filter is not supported in the API request.",
        "first_action": "ChangetheAPIrequestsothatitdoesnotusethebackup",
        "full_action": "ChangetheAPIrequestsothatitdoesnotusethebackup\ntime range filter (greater than and lesser than)."
    },
    "1637": {
        "code": 1637,
        "desc": "Duplicate filters are not supported in the API request.",
        "first_action": "You cannot use the same filter twice in the API request.",
        "full_action": "You cannot use the same filter twice in the API request.\nReview the API request and remove any of the same filters that are used twice."
    },
    "1641": {
        "code": 1641,
        "desc": "TrueimagerestoreissupportedonlyforSLPswithbackupfromsnapshot.",
        "first_action": "Configure a policy using an SLP which has backup from",
        "full_action": "Configure a policy using an SLP which has backup from\nsnapshot and select the True image restore option."
    },
    "1642": {
        "code": 1642,
        "desc": "For ISM on-premises replication, the client or alternate client configured in the policy is not supported.",
        "first_action": "Update the policy by selecting the client or the alternate",
        "full_action": "Update the policy by selecting the client or the alternate\nclient to version NetBackup 10.5 or higher."
    },
    "1643": {
        "code": 1643,
        "desc": "Accelerator option is not supported for SLPs with index from snapshot.",
        "first_action": "Clear the Use Accelerator option in the policy",
        "full_action": "Clear the Use Accelerator option in the policy\nconfiguration."
    },
    "1800": {
        "code": 1800,
        "desc": "Invalid client list",
        "first_action": "Specifyonlyoneclientinthepolicy,orremovethedirective",
        "full_action": "Specifyonlyoneclientinthepolicy,orremovethedirective\nfrom the backup selection that does not support multiple client.\nSee the Troubleshooting section of the NetBackup for Enterprise Vault Agent\nAdministrator’s Guide."
    },
    "1915": {
        "code": 1915,
        "desc": "Cannot delete instance group that contains instances (delete or move instances first)",
        "first_action": "First delete the instances individually by selecting them",
        "full_action": "First delete the instances individually by selecting them\nunder the instances node in the NetBackup Administration Console or by using\nthe command. After all the instances in the group have been deleted, try again to\ndelete the group."
    },
    "1916": {
        "code": 1916,
        "desc": "Database error, cannot access the instance repository",
        "first_action": "Make sure that all NetBackup services are started and",
        "full_action": "Make sure that all NetBackup services are started and\nthat nbdb installed correctly."
    },
    "1917": {
        "code": 1917,
        "desc": "Cannot add instance group, this group name is already in use",
        "first_action": "Type a different group name in the appropriate field, and",
        "full_action": "Type a different group name in the appropriate field, and\ntry to add the group again."
    },
    "1918": {
        "code": 1918,
        "desc": "Cannot find a group by this name",
        "first_action": "Refresh the view (F5 key).",
        "full_action": "Refresh the view (F5 key)."
    },
    "1919": {
        "code": 1919,
        "desc": "Another process modified this instance, database, or instance group.",
        "first_action": "When the Oracle APIs are used, if the If-Match header value does not match",
        "full_action": "Refresh the view (F5 key) in the NetBackup\nAdministration Console.\nDo the following as appropriate:\n■ When the Oracle APIs are used, if the If-Match header value does not match\nthe returned ETag value for the object you attempt to modify. Retrieve the latest\nversion of the object’s ETag and attempt your operation again."
    },
    "1920": {
        "code": 1920,
        "desc": "An instance with this name and client already exists",
        "first_action": "CLI:Usenboracmd list instancesornbsqlcmd list instancestoviewthe",
        "full_action": "Do one of the following:\n■ CLI:Usenboracmd list instancesornbsqlcmd list instancestoviewthe\ninstances that already exist.\n■ GUI: Refresh the view (F5 key)."
    },
    "1921": {
        "code": 1921,
        "desc": "The specified instance or database cannot be found.",
        "first_action": "CLI: Make sure that the instance or the database name is spelled correctly. If",
        "full_action": "Do one of the following:\n■ CLI: Make sure that the instance or the database name is spelled correctly. If\nworking with a RAC database, the database unique name is case-sensitive.\nOn Windows, the instance name is not case-sensitive. On UNIX, the instance\nname is case-sensitive.\n■ GUI: Refresh the view (F5 key)."
    },
    "1924": {
        "code": 1924,
        "desc": "Domain is a required field for Windows instances",
        "first_action": "Specify a domain in the domain field, then try to register",
        "full_action": "Specify a domain in the domain field, then try to register\nthe instance again."
    },
    "1925": {
        "code": 1925,
        "desc": "The requested operation(s) failed",
        "first_action": "Recheckthecommandlinearguments.Iftheerrorpersists,",
        "full_action": "Recheckthecommandlinearguments.Iftheerrorpersists,\ncheck the debug logs for clues or contact Cohesity Technical Support."
    },
    "1926": {
        "code": 1926,
        "desc": "The entry specified already exists",
        "first_action": "TheDBAhasalreadybeenadded,sonoactionisneeded.",
        "full_action": "TheDBAhasalreadybeenadded,sonoactionisneeded."
    },
    "1927": {
        "code": 1927,
        "desc": "The entry specified does not exist",
        "first_action": "The entry has already been deleted, so no action is likely",
        "full_action": "The entry has already been deleted, so no action is likely\nneeded."
    },
    "1928": {
        "code": 1928,
        "desc": "The credentials for 1 or more instances could not be verified NetBackup status codes 402 NetBackup status codes",
        "first_action": "Make sure that the client is running at least this version",
        "full_action": "Make sure that the client is running at least this version\nof NetBackup, and is configured to use the correct master server. Make sure that\nyoucorrectlyenteredtheusername,password,andauxiliaryfieldssuchasdomain\n(Windows) or TNS (Oracle or RMAN)."
    },
    "1932": {
        "code": 1932,
        "desc": "Aninstance,database,orinstancegroupcannotbedeletedorrenamed when it is included in a policy.",
        "first_action": "Remove the instance, database, or instance group from",
        "full_action": "Remove the instance, database, or instance group from\nall policies. Once the instance, database, or instance group is removed from all\npolicies you can retry the deletion or the modification process."
    },
    "1933": {
        "code": 1933,
        "desc": "Cannot change instance or database state without credentials.",
        "first_action": "Verify that the database is registered before you attempt",
        "full_action": "Verify that the database is registered before you attempt\nto change the database state."
    },
    "1946": {
        "code": 1946,
        "desc": "The current version of NetBackup on the client is incorrect for the validation of the requested credential type. NetBackup status codes 403 NetBackup status codes",
        "first_action": "Upgrade the NetBackup client to the current version of",
        "full_action": "Upgrade the NetBackup client to the current version of\nNetBackup."
    },
    "1952": {
        "code": 1952,
        "desc": "An availability group cannot be deleted when it is included in a policy. First remove the availability group from all policies.",
        "first_action": "Remove the availability group from the policies in which",
        "full_action": "Remove the availability group from the policies in which\nit is included. Then try again to delete the availability group."
    },
    "1953": {
        "code": 1953,
        "desc": "Unable to delete the asset because metadata for it exists. Expire any backup images that contain the asset and try again.",
        "first_action": "Expire any backup images that contain the asset and try",
        "full_action": "Expire any backup images that contain the asset and try\nthe operation again."
    },
    "1954": {
        "code": 1954,
        "desc": "Moving an instance to a different RAC cluster is not allowed.",
        "first_action": "The instance must be delete and added into a different",
        "full_action": "The instance must be delete and added into a different\nRAC cluster."
    },
    "1955": {
        "code": 1955,
        "desc": "Registering a RAC instance is not allowed.",
        "first_action": "Credentials must be provided for all nodes of the RAC",
        "full_action": "Credentials must be provided for all nodes of the RAC\ncluster at the database level. If you need to back up a node in the RAC cluster as\na single instance you must delete the instance. After you delete that instance you\nmust add it as a single instance and add the single instance to the backup policy."
    },
    "1956": {
        "code": 1956,
        "desc": "A registered, single instance cannot be moved to a RAC cluster.",
        "first_action": "To add an existing instance to an existing RAC cluster",
        "full_action": "To add an existing instance to an existing RAC cluster\nyou must delete that instance and then add it into the RAC cluster."
    },
    "1957": {
        "code": 1957,
        "desc": "Unable to register a RAC cluster as it does not contain any RAC instances.",
        "first_action": "Add at least one RAC instance to your RAC cluster within",
        "full_action": "Add at least one RAC instance to your RAC cluster within\nNetBackup."
    },
    "1958": {
        "code": 1958,
        "desc": "Oracle Wallet credentials cannot be used with Oracle or OS credentials. NetBackup status codes 405 NetBackup status codes",
        "first_action": "Oracle Wallet",
        "full_action": "Retry the operation by reevaluating what types of\ncredentials are allowed to be used with that operation.\nExamples of valid credential usages for single instances and instance groups:\n■ Oracle Wallet\n■ Oracle Wallet and RMAN\n■ OS\n■ OS and RMAN\n■ OS and Oracle\n■ OS, Oracle, and RMAN\n■ Oracle\n■ Oracle and RMAN\nExamples of valid credential usages for Oracle RAC:\n■ Wallet\n■ Oracle Wallet and RMAN\n■ Oracle\n■ Oracle and RMAN"
    },
    "1960": {
        "code": 1960,
        "desc": "Addition of an Oracle alias did not succeed.",
        "first_action": "Ensure that the provided parameters correspond to an",
        "full_action": "Ensure that the provided parameters correspond to an\neligible Oracle instance and alias.\nFile system mount path."
    },
    "1961": {
        "code": 1961,
        "desc": "Deletion of an Oracle alias did not succeed. NetBackup status codes 406 NetBackup status codes",
        "first_action": "Ensure that the provided parameters correspond to an",
        "full_action": "Ensure that the provided parameters correspond to an\neligible Oracle instance and alias. Confirm that the alias exists in NetBackup for\nthe instance."
    },
    "1962": {
        "code": 1962,
        "desc": "RMAN catalog credentials that are stored in an Oracle Wallet cannot be used with Oracle or OS credentials.",
        "first_action": "Review the existing credential configuration and make",
        "full_action": "Review the existing credential configuration and make\nsure that the configuration you try to switch to or try to add to, is supported."
    },
    "1967": {
        "code": 1967,
        "desc": "Addition of an Oracle Data Guard did not succeed.",
        "first_action": "Review the nbars debug log for additional information.",
        "full_action": "Review the nbars debug log for additional information."
    },
    "1968": {
        "code": 1968,
        "desc": "Deletion of an Oracle Data Guard did not succeed.",
        "first_action": "Review the nbars debug log for additional information.",
        "full_action": "Review the nbars debug log for additional information."
    },
    "1969": {
        "code": 1969,
        "desc": "The specified Oracle Data Guard cannot be found.",
        "first_action": "Verify that the Oracle Data Guard has been entered into",
        "full_action": "Verify that the Oracle Data Guard has been entered into\nthe NetBackup database. Review the bprd and the nbars debug logs for additional\ninformation."
    },
    "1970": {
        "code": 1970,
        "desc": "Update of an Oracle Data Guard configuration did not succeed.",
        "first_action": "To troubleshoot the Oracle Data Guard configuration update",
        "full_action": "Perform the following procedure:\nTo troubleshoot the Oracle Data Guard configuration update\n1 Verify that the Oracle Data Guard exists in the NetBackup database.\n2 Verify that the Oracle instance or the RAC database exists in the NetBackup\ndatabase.\n3 Review the nbars debug log for additional information."
    },
    "1974": {
        "code": 1974,
        "desc": "Clone may fail without a valid set of redo logs.",
        "first_action": "Review the Oracle cloning chapter in the NetBackup for",
        "full_action": "Review the Oracle cloning chapter in the NetBackup for\nOracle Administrator's Guide for more information.\nThe following example RMAN steps may resolve the issue after a clone:\nSQL> alter database drop standby logfile group 1;\nDatabase altered.\nSQL> alter database drop standby logfile group 2;\nDatabase altered.\nSQL> alter database drop standby logfile group 3;\nDatabase altered.\nSQL> ALTER DATABASE ADD LOGFILE group 1 ('c:\\clone\\REDO01.LOG') size 5M;\nDatabase altered.\nSQL> ALTER DATABASE ADD LOGFILE group 2 ('c:\\clone\\REDO02.LOG') size 5M;\nDatabase altered.\nSQL> alter database activate standby database;\nDatabase altered.\nSQL> alter database open;\nDatabase altered.\nSQL>"
    },
    "2000": {
        "code": 2000,
        "desc": "Unabletoallocatenewmediaforbackup,storageunithasnoneavailable.",
        "first_action": "Check the NetBackup Problems report to determine the storage unit that is out",
        "full_action": "Try the following:\n■ Check the NetBackup Problems report to determine the storage unit that is out\nof media.\n■ If the storage unit is a robot with empty slots, add more volumes and specify\nthecorrectvolumepool.Ifnoemptyslotsexist,movesomemediatonon-robotic\nand add new volumes. If you have difficulty keeping track of your available\nvolumes, try the available_media script located in the following directory:\nOn UNIX: /usr/openv/netbackup/bin/goodies/available_media\nOnWindows:install_path\\NetBackup\\bin\\goodies\\available_media.cmd\nThis script lists all volumes in the volume configuration, and information on the\nvolumes currently assigned to NetBackup.\n■ Set up a scratch volume pool as a reserve of unassigned tapes. If NetBackup\nneeds a new tape and none are available in the current volume pool, it moves\na tape from the scratch pool into the volume pool that the backup uses.\n■ If the storage unit and volume pool appear to have media, verify the following:\n■ Use the NetBackup Media List report to check if the volume is FROZEN or\nSUSPENDED.If so, use the bpmedia command to unfreeze it or unsuspend\nit, if so desired.\n■ The volume has not expired or exceeded its maximum number of mounts.\n■ The EMM database host name for the device is correct. If you change the\nEMM database host name, stop and restart the Media Manager device\ndaemon(ltidforaUNIXserver)ortheNetBackupDeviceManagerservice\n(Windows server).\n■ The correct host is specified for the storage unit in the NetBackup\nconfiguration. The host connection must be the server (master or media)\nwith drives connected to it.\n■ The Media and Device Management volume configuration has media in the\ncorrect volume pool. Unassigned or active media is available at the required\nretention level. Use the NetBackup Media List report to show the retention\nlevels, volume pools, and status for all volumes. Use the NetBackup Media\nSummary report to check for active volumes at the correct retention levels.\n■ Create the bptm debug log directory, and set the MDS VxUL logging (OID 143)\nto debug level 2. Then retry the operation.\n■ If this storage unit is new and this attempt to use it is the first, stop and restart\nNetBackup on the master server. The MDS unified logging files (OID 143) at\ndebug level 2 usually show the NetBackup media selection process."
    },
    "2001": {
        "code": 2001,
        "desc": "No drives are available for this job NetBackup status codes 410 NetBackup status codes",
        "first_action": "Verify that the required drives and robots are configured and up.",
        "full_action": "Try the following:\n■ Verify that the required drives and robots are configured and up.\n■ Verify that ltid is active and a drive path exists that is configured on the drive\nfor the media server that the storage unit requires.\n■ If the job requires an NDMP drive path, verify that one exists."
    },
    "2002": {
        "code": 2002,
        "desc": "Invalid STU identifier type",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2003": {
        "code": 2003,
        "desc": "Drive is not allocated.",
        "first_action": "The MDS unified logging files (OID 143) from the master server at debug level",
        "full_action": "ThiserrorisinternaltotheMDScomponentofNetBackup.\nCheck the following logs:\n■ The MDS unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2004": {
        "code": 2004,
        "desc": "Drive is already allocated",
        "first_action": "A drive may have been reset while it was allocated for a",
        "full_action": "A drive may have been reset while it was allocated for a\njob. Wait for the jobs that use the drive to complete."
    },
    "2005": {
        "code": 2005,
        "desc": "MDS has received an invalid message from a media server.",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\n■ The bptm legacy log from the media server, with VERBOSE=5."
    },
    "2006": {
        "code": 2006,
        "desc": "NDMP credentials are not defined in EMM.",
        "first_action": "If the job uses an NDMP device, verify that the media",
        "full_action": "If the job uses an NDMP device, verify that the media\nserver has NDMP credentials that are configured for the filer."
    },
    "2007": {
        "code": 2007,
        "desc": "Storage unit is not compatible with requesting job",
        "first_action": "Catalog backups are directed to shared disk storage units.",
        "full_action": "A job tries to run on a media server that is running an\nolder version of NetBackup. The job may require a feature that is not available on\nthe media server being requested. Verify that the storage unit type and the media\nserver that the policy and storage unit call out support the feature.\nThis error can occur when the policy being run is not compatible with the storage\nunits requested by the policy:\n■ Catalog backups are directed to shared disk storage units.\n■ Multiplexed jobs are directed to storage units that do not have the multiplex\nfeature configured.\n■ NDMP backup policies are directed to non-NDMP storage units."
    },
    "2008": {
        "code": 2008,
        "desc": "All compatible drive paths are down",
        "first_action": "Verify that ltid is running on the required media server,",
        "full_action": "Verify that ltid is running on the required media server,\nand that the media server is active for tape. Using a device monitor, bring up the\ndrive paths if they are down. If the drives are downed again, clean the drives."
    },
    "2009": {
        "code": 2009,
        "desc": "All compatible drive paths are down but media is available",
        "first_action": "Verify that ltid is running on the required media server,",
        "full_action": "Verify that ltid is running on the required media server,\nand that the media server is active for tape. Using a device monitor, bring up the\ndrive paths if they are down. If the drives are downed again, clean the drives."
    },
    "2010": {
        "code": 2010,
        "desc": "Job type is invalid",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2011": {
        "code": 2011,
        "desc": "The media server reported a system error",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2012": {
        "code": 2012,
        "desc": "Media has conflicts in EMM",
        "first_action": "The media is marked as having conflicts. The upgrade",
        "full_action": "The media is marked as having conflicts. The upgrade\nfrom NetBackup 5.x has found multiple volume databases where two tapes in\ndifferent volume databases have the same media ID. This error is internal. If the\nproblem persists, please call NetBackup support for resolution."
    },
    "2013": {
        "code": 2013,
        "desc": "Error record insert failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2014": {
        "code": 2014,
        "desc": "Media is not assigned",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Verify that the job requested the desired media. For\nexample,ifyouwanttolistcontentsofthemedia,makesurethatyouhavespecified\nthe correct media ID.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2015": {
        "code": 2015,
        "desc": "Media is expired",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Make sure that non-expired media is available for the job.\nCheck the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2016": {
        "code": 2016,
        "desc": "Media is assigned to another server",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Check the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2017": {
        "code": 2017,
        "desc": "Media needs to be unmounted from a drive",
        "first_action": "Identifythemediathatis requestedby thejobthatreturns",
        "full_action": "Identifythemediathatis requestedby thejobthatreturns\nthis error. If it is used by another job, wait for that job to complete."
    },
    "2018": {
        "code": 2018,
        "desc": "Number of cleanings is invalid",
        "first_action": "OntheChangeMediascreen,setthenumberofcleanings",
        "full_action": "OntheChangeMediascreen,setthenumberofcleanings\nremaining for the cleaning media to a number greater than or equal to zero (0)."
    },
    "2019": {
        "code": 2019,
        "desc": "Media is in a drive that is not configured on local system",
        "first_action": "If drive paths are down, identify the media server that is",
        "full_action": "If drive paths are down, identify the media server that is\nconfigured for use by the storage unit, and bring up the drive path to that media\nserver."
    },
    "2020": {
        "code": 2020,
        "desc": "Robotic library is down on server",
        "first_action": "Verify that the media server that is required for this",
        "full_action": "Verify that the media server that is required for this\nallocation is running, and verify that ltid is up on that media server."
    },
    "2021": {
        "code": 2021,
        "desc": "Allocation record insert failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2022": {
        "code": 2022,
        "desc": "Allocation status record insert failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2023": {
        "code": 2023,
        "desc": "Allocation identifier is not known to EMM",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2024": {
        "code": 2024,
        "desc": "Allocation request update failed NetBackup status codes 418 NetBackup status codes",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2025": {
        "code": 2025,
        "desc": "Allocation request delete failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2026": {
        "code": 2026,
        "desc": "Allocation status request delete failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2027": {
        "code": 2027,
        "desc": "Media server is not active",
        "first_action": "Verify that the media server that is required for this allocation is running.",
        "full_action": "Do one or more of the following:\n■ Verify that the media server that is required for this allocation is running.\n■ If this is a tape job, verify that ltid is running on the media server. If a media\nserver has gone offline and returned online, a delay of several minutes may\noccur before a job can use that media server.\n■ Use the vmoprcmd command to show the state of the media server. If the job is\ntrying to access a disk storage unit, verify that the nbrmms process is running\non the media server. If the job is trying to access a tape storage unit, verify that\nltid is running on the media server."
    },
    "2028": {
        "code": 2028,
        "desc": "Media is reserved",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "If multiple duplication jobs attempt to use the same tape\nmedia for read, each job reserves the media. NetBackup should allow more than\none job to get a reservation for the tape media.\nThis error is internal. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2029": {
        "code": 2029,
        "desc": "EMM database is inconsistent NetBackup status codes 420 NetBackup status codes",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\nRun thenbrbutil -resetallcommand togettheNetBackupallocationdatabase\nbackintoaconsistentstate.Notethatthiscommandcancelsalljobsincludingthose\nthat are currently running."
    },
    "2030": {
        "code": 2030,
        "desc": "Insufficient disk space or high water mark would be exceeded",
        "first_action": "If there are images on the disk that can be expired, expire them, and run",
        "full_action": "Try the following possible solutions:\n■ If there are images on the disk that can be expired, expire them, and run\nnbdelete to delete the images from disk.\n■ It may be that NetBackup creates disk images more quickly than they expire. If\nso, modifications to policies may be necessary to change the rate of image\ncreation and expiration for the disk.\n■ It may be helpful to lower the high water mark and low water mark for the disk\ngroup."
    },
    "2031": {
        "code": 2031,
        "desc": "Media is not defined in EMM",
        "first_action": "Amediavolumethatisrequiredforarestorejobhasbeen",
        "full_action": "Amediavolumethatisrequiredforarestorejobhasbeen\ndeleted from the EMM database. If the media is available, use bpimport to import\nit."
    },
    "2032": {
        "code": 2032,
        "desc": "Media is in use according to EMM",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. Check the following logs to help\nidentify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2033": {
        "code": 2033,
        "desc": "Media has been misplaced",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Verify that the media that is required by the job is in the\nproper robotic slot as shown by vmquery.\nIf the error persists, the following logs may be useful in understanding the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3.\n■ The verbose bptm logs on the media server(s) that access this media."
    },
    "2034": {
        "code": 2034,
        "desc": "Retry the allocation request later",
        "first_action": "This error should never appear as a job return status. In",
        "full_action": "This error should never appear as a job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldqueuebecauseresources\nare busy."
    },
    "2035": {
        "code": 2035,
        "desc": "Request needs to pend",
        "first_action": "This error should never appear as a job return status. In",
        "full_action": "This error should never appear as a job return status. In\nthemdsandnbrb vxullogs,itindicatesthatajobshouldpostarequestforoperator\nintervention to the NetBackup device monitor."
    },
    "2036": {
        "code": 2036,
        "desc": "Drive is in a robotic library that is up",
        "first_action": "A request for non-robotic media may have caused a",
        "full_action": "A request for non-robotic media may have caused a\npending request in the device monitor, and the operator has assigned the request\nto a drive that is not a standalone drive. This error is not fatal. The request will pend\nagain in the NetBackup device monitor. Assign the pending mount to a standalone\ndrive or to a drive that is in AVR mode (non-robotic)."
    },
    "2037": {
        "code": 2037,
        "desc": "Drive is not ready",
        "first_action": "Thiserrormayoccurwhenarequestfornon-roboticmedia",
        "full_action": "Thiserrormayoccurwhenarequestfornon-roboticmedia\nhadcausedapendingrequestinthedevicemonitor,andtheoperatorhasassigned\nthe request to a drive that is not in a ready state. This error is not a fatal error. The\nrequest will pend again in the NetBackup device monitor. Verify that required tape\nis in the drive it is assigned to, and that the drive ready light has come on. It may\ntake some time for the drive to become ready after the tape has been inserted. If\nthe drive never goes to a ready state after a tape has been inserted, there may be\na problem with the drive."
    },
    "2038": {
        "code": 2038,
        "desc": "Media loaded in drive is not write-enabled",
        "first_action": "This is not a fatal error. The request will pend again in the",
        "full_action": "This is not a fatal error. The request will pend again in the\nNetBackup device monitor. If you are sure that it is OK to write on this tape, verify\nthat the required tape has its write enable switch set to allow write."
    },
    "2039": {
        "code": 2039,
        "desc": "SCSI reservation conflict detected",
        "first_action": "This error should never occur at job resource allocation",
        "full_action": "This error should never occur at job resource allocation\ntime, but may occur during i/o for a tape job. The verbose bptm logs on the media\nserver may be useful in understanding the problem."
    },
    "2040": {
        "code": 2040,
        "desc": "Maximum job count has been reached for the storage unit",
        "first_action": "Target a different storage unit with one of the copies, or",
        "full_action": "Target a different storage unit with one of the copies, or\nincrease the maximum job count for the storage unit."
    },
    "2041": {
        "code": 2041,
        "desc": "Storage unit is down",
        "first_action": "Run the bperror -disk command to indicate why the",
        "full_action": "Run the bperror -disk command to indicate why the\ndisk is considered down."
    },
    "2042": {
        "code": 2042,
        "desc": "Density mismatch detected",
        "first_action": "Restore the jobs request tape media by media ID density.",
        "full_action": "Restore the jobs request tape media by media ID density.\nIf the requested density does not match the configured density for the media, it\ncannot be allocated."
    },
    "2043": {
        "code": 2043,
        "desc": "Requested slot is empty",
        "first_action": "The robot may need to be inventoried.",
        "full_action": "The robot may need to be inventoried."
    },
    "2044": {
        "code": 2044,
        "desc": "Media is assigned to another application",
        "first_action": "Verifythatthemediathatisrequiredforthejobisassigned",
        "full_action": "Verifythatthemediathatisrequiredforthejobisassigned\nto NetBackup."
    },
    "2045": {
        "code": 2045,
        "desc": "Storage unit is disabled since max job count is less than 1",
        "first_action": "Increasethemaximumjobcount(ormaximumconcurrent",
        "full_action": "Increasethemaximumjobcount(ormaximumconcurrent\ndrive count) to a value greater than 0."
    },
    "2046": {
        "code": 2046,
        "desc": "Media is unmountable",
        "first_action": "Clean the drives in the media's robot. Determine if any of",
        "full_action": "Clean the drives in the media's robot. Determine if any of\nthe media is bad."
    },
    "2047": {
        "code": 2047,
        "desc": "Media is write protected",
        "first_action": "Make sure that media in the scratch pool is not write",
        "full_action": "Make sure that media in the scratch pool is not write\nprotected."
    },
    "2048": {
        "code": 2048,
        "desc": "Media is in use by the ACS robotic library",
        "first_action": "Makesurethattherequiredmediaisnotinusebyanother",
        "full_action": "Makesurethattherequiredmediaisnotinusebyanother\napplication."
    },
    "2049": {
        "code": 2049,
        "desc": "Media not found in the ACS robotic library",
        "first_action": "Make sure thattherequiredmediais availablein theACS",
        "full_action": "Make sure thattherequiredmediais availablein theACS\nrobot.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide."
    },
    "2050": {
        "code": 2050,
        "desc": "ACS media has an unreadable external label",
        "first_action": "Correct the barcode label problem for this media.",
        "full_action": "Correct the barcode label problem for this media.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide."
    },
    "2051": {
        "code": 2051,
        "desc": "ACS media is not in the drive's domain",
        "first_action": "Verify that the robot that contains the required media is",
        "full_action": "Verify that the robot that contains the required media is\naccessible to a NetBackup media server.\nFor more information, refer to the section on configuring ACSLS robots in the\nNetBackup Device Configuration Guide."
    },
    "2052": {
        "code": 2052,
        "desc": "An ACS Library Storage Module (LSM) is offline",
        "first_action": "Bring the ACS LSM online.",
        "full_action": "Bring the ACS LSM online.\nFormoreinformation,seethesectiononconfiguringACSLSrobotsintheNetBackup\nDevice Configuration Guide."
    },
    "2053": {
        "code": 2053,
        "desc": "Media is in an inaccessible drive",
        "first_action": "Locatethemediaandcorrecttheproblemthathascaused",
        "full_action": "Locatethemediaandcorrecttheproblemthathascaused\nthe drive or drive path to be down."
    },
    "2054": {
        "code": 2054,
        "desc": "Media is in a drive that is currently in a DOWN state",
        "first_action": "Locatethemediaandcorrecttheproblemthathascaused",
        "full_action": "Locatethemediaandcorrecttheproblemthathascaused\nthe drive or drive path to be down."
    },
    "2055": {
        "code": 2055,
        "desc": "ACS physical drive is not available",
        "first_action": "Locate and install an ACS drive.",
        "full_action": "Locate and install an ACS drive."
    },
    "2056": {
        "code": 2056,
        "desc": "The file name used for the mount request already exists",
        "first_action": "Specifyadifferentfilenamefortpreq,orrunthetpunmount",
        "full_action": "Specifyadifferentfilenamefortpreq,orrunthetpunmount\ncommand for the media which has been loaded using tpreq with the conflicting file\nname."
    },
    "2057": {
        "code": 2057,
        "desc": "The scan host of the drive is not active",
        "first_action": "If the problem persists, restart the NetBackup media",
        "full_action": "If the problem persists, restart the NetBackup media\nservers that have paths to this drive."
    },
    "2058": {
        "code": 2058,
        "desc": "LTID needs to be restarted on media servers before the device can be used",
        "first_action": "When the media server is not in a busy state, stop and",
        "full_action": "When the media server is not in a busy state, stop and\nrestart ltid on that media server."
    },
    "2059": {
        "code": 2059,
        "desc": "The robotic library is not available",
        "first_action": "Verify that the robot that the jobs require is properly",
        "full_action": "Verify that the robot that the jobs require is properly\nconfigured. If the error persists, the following logs may be useful in understanding\ntheproblem:Themdsunifiedloggingfiles(OID143)fromthemasterserveratdebug\nlevel 2."
    },
    "2060": {
        "code": 2060,
        "desc": "Media needs to be rewound or unmounted from a drive",
        "first_action": "Not applicable.",
        "full_action": "Not applicable."
    },
    "2061": {
        "code": 2061,
        "desc": "The host is not an active node of a cluster",
        "first_action": "Restart the failed job.",
        "full_action": "Restart the failed job."
    },
    "2062": {
        "code": 2062,
        "desc": "Throttled job count has been reached for the storage unit",
        "first_action": "Not available",
        "full_action": "Not available"
    },
    "2063": {
        "code": 2063,
        "desc": "Server is not licensed for the Remote Client Option NetBackup status codes 430 NetBackup status codes",
        "first_action": "Backup this client on a media server that is licensed to",
        "full_action": "Backup this client on a media server that is licensed to\ndo so. Verify that the media server has connectivity to the master server when\nadding its licenses."
    },
    "2064": {
        "code": 2064,
        "desc": "Job history indicates that no media is available",
        "first_action": "Make sure that media is available for the storage unit. If",
        "full_action": "Make sure that media is available for the storage unit. If\nnecessary, upgrade the software on the media server. Add media if necessary. If\nmedia is available, wait 12 hours until the storage unit can be used again. To make\nthe storage unit immediately usable, run the following command on the master\nserver to release the hold:\nnbrbutil -releaseAllocHolds"
    },
    "2065": {
        "code": 2065,
        "desc": "Job history indicates that no drive is available",
        "first_action": "Upgrade the media server software. Make sure all of the",
        "full_action": "Upgrade the media server software. Make sure all of the\ndrives in the storage unit are up and available for use. Clean all drives that need\ncleaning."
    },
    "2066": {
        "code": 2066,
        "desc": "Disk pool not found",
        "first_action": "Verify that the storage unit that this job uses is configured",
        "full_action": "Verify that the storage unit that this job uses is configured\nfor use with a properly configured disk pool."
    },
    "2067": {
        "code": 2067,
        "desc": "Disk volume not found",
        "first_action": "Verifythatthedisk storagethatthisjob uses is configured",
        "full_action": "Verifythatthedisk storagethatthisjob uses is configured\nfor use with a disk pool that has volumes configured. For a read job, verify that the\nvolume that is required for reading exists in the nbemm database."
    },
    "2068": {
        "code": 2068,
        "desc": "Disk volume mount point not found",
        "first_action": "Verify that the configuration is correct for the disk group",
        "full_action": "Verify that the configuration is correct for the disk group\nand for the disk volumes in the disk group."
    },
    "2069": {
        "code": 2069,
        "desc": "Disk volume mount point record insert failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2070": {
        "code": 2070,
        "desc": "The specified mount path will not fit in the allocated space",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2071": {
        "code": 2071,
        "desc": "Unable to find any storage servers for the request",
        "first_action": "Verify that the storage servers serving the disk group that",
        "full_action": "Verify that the storage servers serving the disk group that\nthe job requires are configured and enabled. Verify that they are in an UP state."
    },
    "2072": {
        "code": 2072,
        "desc": "Invalid operation on static mount point",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2073": {
        "code": 2073,
        "desc": "Disk pool is down",
        "first_action": "Run the bperror -disk command to determine why the",
        "full_action": "Run the bperror -disk command to determine why the\ndiskpoolwasputintoaDOWNstate.Correcttheproblem,andusethenbdevconfig\ncommand to return the disk pool to an UP state."
    },
    "2074": {
        "code": 2074,
        "desc": "Disk volume is down",
        "first_action": "You may be able to see why the disk volume was put into",
        "full_action": "You may be able to see why the disk volume was put into\na DOWN state by runningbperror -disk. Correct the problem, and use\nnbdevconfig to return the disk volume to an UP state."
    },
    "2075": {
        "code": 2075,
        "desc": "Fibre Transport resources are not available",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Configure the job to switch to LAN transport if Fibre\nTransport is not available. Verify that the job type being run is compatible with Fibre\nTransport. Using nbdevquery, verify that the Disk Pool being requested is enabled\nfor use with Fibre Transport. Verify that there are Fibre Transport connections that\nareupbetweentheclientandmediaserverrequiredforthejob.Checkthefollowing\nlogs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2076": {
        "code": 2076,
        "desc": "DSM returned an unexpected error",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2078": {
        "code": 2078,
        "desc": "Themaximumnumberofmountsforthediskvolumehavebeenexceeded",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, please call\nNetBackup support for resolution. Check the following logs to help identify the\nproblem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2079": {
        "code": 2079,
        "desc": "DSM has detected that an invalid file system is mounted on the volume",
        "first_action": "Verify that the disk volumes and their associated mount",
        "full_action": "Verify that the disk volumes and their associated mount\npoints that NetBackup uses are not used by other applications."
    },
    "2080": {
        "code": 2080,
        "desc": "Disk volume has no max writers count",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Verify proper disk configuration by using nbdevquery.\nThis error is internal. If the problem persists, please call NetBackup support for\nresolution. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2081": {
        "code": 2081,
        "desc": "Disk volume has no max readers count",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "Verify the proper disk configuration by using nbdevquery.\nThis error is internal. If the problem persists, please call NetBackup support for\nresolution. Check the following logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2082": {
        "code": 2082,
        "desc": "The drive needs to be marked as available",
        "first_action": "ReleaseMDS command to release the allocation for the drive so it can be used.",
        "full_action": "Run the nbrbutil -dump command on the master server\nto show allocations for this job. If the problem persists, run the nbrbutil\n-releaseMDS command to release the allocation for the drive so it can be used."
    },
    "2083": {
        "code": 2083,
        "desc": "The media affinity group is not defined in EMM",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, check the\nfollowing logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2084": {
        "code": 2084,
        "desc": "Media affinity group record insert failed",
        "first_action": "The mds unified logging files (OID 143) from the master server at debug level",
        "full_action": "This error is internal. If the problem persists, check the\nfollowing logs to help identify the problem:\n■ The mds unified logging files (OID 143) from the master server at debug level\n2.\n■ The nbrb unified logging files (OID 118) from the master server at debug level\n3."
    },
    "2085": {
        "code": 2085,
        "desc": "Disk volume is not available",
        "first_action": "Ensure that the disk group has disk volumes configured.",
        "full_action": "Ensure that the disk group has disk volumes configured.\nA multiple copy job cannot target two copies for the same disk volume."
    },
    "2086": {
        "code": 2086,
        "desc": "Disk volume cannot be used for more than one copy in the same job",
        "first_action": "Use the nbdevquery -listdv command to verify thatthe",
        "full_action": "Use the nbdevquery -listdv command to verify thatthe\nexpected disk volume is configured. For a multiple copy job, ensure that unique\neligible disk volumes exist for each copy. A multiple copy job cannot target two\ncopies for the same disk volume."
    },
    "2087": {
        "code": 2087,
        "desc": "Media allocation would exceed maximum partially full media limit",
        "first_action": "This error may occur with a multiple copy job or a",
        "full_action": "This error may occur with a multiple copy job or a\nduplicationjob.Iftheproblempersists,youmayneedtoincreasemaximumpartially\nfull media setting on the disk pool."
    },
    "2088": {
        "code": 2088,
        "desc": "Cleaning media is not available",
        "first_action": "Add a cleaning volume to the robot containing the drive.",
        "full_action": "Add a cleaning volume to the robot containing the drive."
    },
    "2089": {
        "code": 2089,
        "desc": "FT client is not running",
        "first_action": "Verify that the Private Branch Exchange (PBX) service is installed and running.",
        "full_action": "Do one or more of the following:\n■ Verify that the Private Branch Exchange (PBX) service is installed and running.\nRun the bpps -x command to ensure that pbx_exchange is listed in the\nprocesses that are running.\n■ Verify that the client is configured as a SAN Client. Run the bpclntcmd\n-sanclient command to return the current state of the SAN Client. A response\nof 0 (zero) indicates that SAN Client is not configured. Rerun the command as\nbpclntcmd -sanclient 1.\n■ Verify that the client is not also a media server, master server, or EMM server.\nThe SAN Client process runs only on a NetBackup client.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server.\n■ Verify that no server entries for the SAN Client exist on the NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nClient. If the master server has the SAN Client listed also as a server, it may\nshutdown the SAN Client.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverreboots,\nbut does not automatically restart after you run the bpclntcmd command. To\nstart the SAN Client service, run the client startup script or use the Service\nManager in Windows.\nFormoreinformation,seetheTroubleshootingchapteroftheNetBackupSANClient\nand Fibre Transport Guide."
    },
    "2090": {
        "code": 2090,
        "desc": "FT client has no devices configured NetBackup status codes 439 NetBackup status codes",
        "first_action": "Verify that Fibre Transport devices are installed on the",
        "full_action": "Verify that Fibre Transport devices are installed on the\nclient.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide."
    },
    "2091": {
        "code": 2091,
        "desc": "FT client devices are offline",
        "first_action": "Verify that the Private Branch Exchange (PBX) service is installed and running.",
        "full_action": "Do one or more of the following:\n■ Verify that the Private Branch Exchange (PBX) service is installed and running.\nRun the bpps -x command to ensure that pbx_exchange is listed in the\nprocesses that are running.\n■ Verify that the client is configured as a SAN Client. Run the bpclntcmd\n-sanclient command to return the current state of the SAN Client. A response\nof 0 (zero) indicates that SAN Client is not configured. Rerun the command as\nbpclntcmd -sanclient 1.\n■ Verify that the client is not also a media server, master server, or EMM server.\nThe SAN Client process runs only on a NetBackup client.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server.\n■ Verify that no server entries for the SAN Client exist on the NetBackup master\nserver.RemoveanySERVER=clientnameentryinthemasterserverfortheSAN\nClient. If the master server has the SAN Client also listed as a server, it may\nshutdown the SAN Client.\n■ RestarttheSANClientservice.TheSANClientrestartswhentheserverrestarts,\nbut does not automatically restart after you run the bpclntcmd command. To\nstart the SAN Client service, run the client startup script or use the Service\nManager in Windows.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide."
    },
    "2092": {
        "code": 2092,
        "desc": "FT server devices for client are offline",
        "first_action": "Verify that marked QLogic Target ports exist in the server. The nbftsrvr and",
        "full_action": "Do one of the following:\n■ Verify that marked QLogic Target ports exist in the server. The nbftsrvr and\nnbfdrv64 processes exit if the system has no ports available for Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature that requires a key called \"SAN\nClient\" on the master server. The Fibre Transport server performs a license\ncheck during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require that you reboot the media server after you install\nFibre Transport to load the Fibre Transport drivers on the marked target ports.\nIn addition, reboot the Linux servers if you choose to not unload the existing\nQLogic drivers during the installation of Fibre Transport.\nFor further information, see the Troubleshooting chapter of the NetBackup SAN\nClient and Fibre Transport Guide."
    },
    "2093": {
        "code": 2093,
        "desc": "No FT servers for this client are running",
        "first_action": "Verify that marked QLogic Target ports exist in the server. The nbftsrvr and",
        "full_action": "Do one of the following:\n■ Verify that marked QLogic Target ports exist in the server. The nbftsrvr and\nnbfdrv64 processes exit if the system has no ports available for Target Mode\nuse.\n■ VerifythatavalidlicensefortheSANClientfeatureresidesonthemasterserver.\nSAN Client is a separately licensed feature which requires a key called \"SAN\nClient\" on the master server. The Fibre Transport server performs a license\ncheck during startup.\n■ DetermineifarebootisrequiredfortheinstallationoftheFibreTransportserver.\nSolaris installations require that you reboot the media server after you install\nFibre Transport to load the Fibre Transport drivers on the marked target ports.\nIn addition, reboot the Linux servers if you choose to not unload the existing\nQLogic drivers during the installation of Fibre Transport.\nFor further information, see the NetBackup SAN Client and Fibre Transport\nTroubleshooting Guide."
    },
    "2094": {
        "code": 2094,
        "desc": "STU cannot run Lifecycle backups",
        "first_action": "Run the nbdevquery -listdp command to check the",
        "full_action": "Run the nbdevquery -listdp command to check the\nconfiguration of the disk pool. If the Lifecycle attribute is not enabled for the disk\npool, run the nbdevconfig -changedp -setattribute command to enable it."
    },
    "2095": {
        "code": 2095,
        "desc": "STU cannot run VMware backup",
        "first_action": "To run a VMware backup, the media server must run a",
        "full_action": "To run a VMware backup, the media server must run a\nvalid version of NetBackup. Verify that a valid version of NetBackup is running or\nconfigure the backup for a media server that runs a valid version of NetBackup."
    },
    "2096": {
        "code": 2096,
        "desc": "NDMP operation does not support multiple inline copies",
        "first_action": "NetBackupcannotmakemultiplecopiesofNDMPpolicies.",
        "full_action": "NetBackupcannotmakemultiplecopiesofNDMPpolicies.\nConfigure the backup for a single storage unit destination."
    },
    "2097": {
        "code": 2097,
        "desc": "Storage unit group does not exist in EMM configuration",
        "first_action": "Reconfigure the policy to use a storage unit or storage",
        "full_action": "Reconfigure the policy to use a storage unit or storage\nunit group that exists in the configuration."
    },
    "2098": {
        "code": 2098,
        "desc": "Media pool is not eligible for this job",
        "first_action": "Change the configured media pool for the job to use a",
        "full_action": "Change the configured media pool for the job to use a\npoolthatisconfigured,orcreatetherequiredmediapool.Makesurethatthemedia\npool you have configured for the job is not a scratch pool."
    },
    "2099": {
        "code": 2099,
        "desc": "Required drive or drive path is not configured",
        "first_action": "Run the vmoprcmd command to verify the drive",
        "full_action": "Run the vmoprcmd command to verify the drive\nconfiguration. Configure the drives that are necessary for the media type that is\nused."
    },
    "2100": {
        "code": 2100,
        "desc": "Maximum number of mounts has been exceeded for tape media",
        "first_action": "Increase the maximum allowed mounts for the media.",
        "full_action": "Increase the maximum allowed mounts for the media.\nYoumayneedtoretirethismediaifithasexceededthemaximumnumberofmounts\nyou have configured."
    },
    "2101": {
        "code": 2101,
        "desc": "Media server not found in EMM database",
        "first_action": "For a restore from tape, you can use the Force Media Server Restore option to",
        "full_action": "Do the following as appropriate:\n■ For a restore from tape, you can use the Force Media Server Restore option to\nforce NetBackup to replace the missing media server with a new media server.\n■ For optimized duplication, ensure that the media server in common has\ncredentials for both storage servers. More information about OpenStorage\noptimized duplication is available.\nSee the NetBackup OpenStorage Solutions Guide for Disk."
    },
    "2102": {
        "code": 2102,
        "desc": "Storage unit does not support spanning",
        "first_action": "Some disk types do not support spanning. Run the",
        "full_action": "Some disk types do not support spanning. Run the\nnbdevconfig -listdg command to determine if a disk group supports spanning.\nIf this error persists, ensure that enough space is available on your disk storage\nunits for the new jobs that are running."
    },
    "2103": {
        "code": 2103,
        "desc": "Media server mismatch",
        "first_action": "All copies of a multiple copy job must run on the same",
        "full_action": "All copies of a multiple copy job must run on the same\nmediaserver.Configurethestorageunitsthathavedrivepathsordiskaccessfrom\na common media server."
    },
    "2104": {
        "code": 2104,
        "desc": "Storage units are not available",
        "first_action": "Verify that all criteria in met for the policy with the storage",
        "full_action": "Verify that all criteria in met for the policy with the storage\nunits that are configured."
    },
    "2105": {
        "code": 2105,
        "desc": "Storage unit requested for replication job is not replication capable",
        "first_action": "Make sure that replication jobs include status configured",
        "full_action": "Make sure that replication jobs include status configured\nfor replication enabled disks in their storage unit specifiers."
    },
    "2106": {
        "code": 2106,
        "desc": "Disk storage server is down NetBackup status codes 445 NetBackup status codes",
        "first_action": "TheNetBackupCloudStoreServiceisrunningonthemasterandmediaservers.",
        "full_action": "Verify that all media servers that are configured for the\nstorageservercancommunicatewiththestorageserver.Thebpstsinfocommand\nqueries the storage server periodically, so you can use the bpstsinfo log set to\nverbosity level 5 on the media server.\nIftheerrorisrelatedtoacloudstoragebackupfailure,youshouldverifythefollowing\ninformation:\n■ TheNetBackupCloudStoreServiceisrunningonthemasterandmediaservers.\nSee the NetBackup CloudStore Service Container startup and shutdown\ntroubleshooting section in the NetBackup Cloud Administrator's Guide for\ninformation on how to start the service.\n■ TheNetBackupcertificatesarestale/unavailableontheconfiguredmediaserver,\nwhich can cause the storage server to go down. Ensure that you deploy all of\nthe required certificates on that media server to keep the storage server up. For\nmore information, see the NetBackup Security Encryption Guide.\n■ The Enable insecure communication with 8.0 and earlier hosts option on\nthe NetBackup master server is selected if the media server is version 8.0 or\nearlier. The option is available in the NetBackup Administration Console on\nthe Security Management > Global Security Settings > Secure\nCommunication tab."
    },
    "2107": {
        "code": 2107,
        "desc": "Requested media server does not have credentials or is not configured for the storage server",
        "first_action": "Optimized duplication requires a media server with",
        "full_action": "Optimized duplication requires a media server with\ncredentials for both the read side and write side storage servers. Add the needed\ncredentials or limit the media servers that the write side storage unit calls out to\nthose that are credentialed for the read media."
    },
    "2108": {
        "code": 2108,
        "desc": "RequestedNDMPmachinedoesnothavecredentialsorisnotconfigured in NetBackup",
        "first_action": "Jobs for NDMP policies require that the NDMP host that",
        "full_action": "Jobs for NDMP policies require that the NDMP host that\nis specified as the client in the policy be configured in NetBackup. The credentials\nthat are defined for any server must access the NDMP host.\nVerify that the required NDMP host is configured. If the configured NDMP host is\nafullyqualifiednameandtheNDMPhostnameinthepolicyisnot,runthefollowing\ncommand to add an alias to the NDMP host:\n# nbemmcmd -machinealias -addalias -alias string -machinename string"
    },
    "2109": {
        "code": 2109,
        "desc": "Requested Fibre Transport client machine was not found in NetBackup configuration",
        "first_action": "Fibre Transport backup and restore operations require",
        "full_action": "Fibre Transport backup and restore operations require\neachFibreTransportclienttobeconfiguredinNetBackup.Verifythattheclientthat\nis requested for the job is configured as a Fibre Transport client."
    },
    "2110": {
        "code": 2110,
        "desc": "Requested machine is not configured in NetBackup",
        "first_action": "The policy that you use to run the job may indicate which",
        "full_action": "The policy that you use to run the job may indicate which\nserver the job requires. If not, find the server that the job looks for by setting the\nMDS VxUL logging (OID 143) to debug level 2 and retry the job. The MDS log\nusually indicates which host name caused the problem."
    },
    "2111": {
        "code": 2111,
        "desc": "AllstorageunitsareconfiguredwithOnDemandOnlyandarenoteligible for jobs requesting ANY storage unit",
        "first_action": "Change the policy to use a specific storage unit instead",
        "full_action": "Change the policy to use a specific storage unit instead\nof any available storage unit, or configure at least one storage unit without the On\nDemand Only setting."
    },
    "2112": {
        "code": 2112,
        "desc": "NetBackup media server version is too low for the operation",
        "first_action": "Point the storage unit to a media server with a newer",
        "full_action": "Point the storage unit to a media server with a newer\nversion of software."
    },
    "2113": {
        "code": 2113,
        "desc": "Invalid or no disk array credentials are added for vserver",
        "first_action": "UndertheDiskArrayHostscredentialssection,addadmin",
        "full_action": "UndertheDiskArrayHostscredentialssection,addadmin\ncredentials of NetApp Storage Virtual Machine's interface that has management\naccess enabled. Ensure that the right Storage Virtual Machine's interface name is\nentered that holds the snapshot/replica to be indexed. Ensure that the Storage\nVirtual Machine (SVM) user account with the ONTAPi application is in the unlocked\nstate.\nSee the NetBackup Replication Director Solutions Guide for more information."
    },
    "2114": {
        "code": 2114,
        "desc": "Media server is not recognized.",
        "first_action": "Add authorization for the media server on the master server and restart the",
        "full_action": "This error does not necessarily mean that a configuration\nchange is required. However, repeated instances of this error indicate that a\nconfiguration change should be considered to maintain good master server\nperformance.\nPerform the following as appropriate:\n■ Add authorization for the media server on the master server and restart the\nNetBackup services on the media server.\n■ Add media server to the PBX BLOCK_SERVER_SERVICE list on the master server.\nThe services that should be blocked are EMM and NBREM.\nFormoreinformationaboutblockingincomingconnections,refertothefollowing\narticle on the Cohesity Technical Support website:\nhttps://www.veritas.com/content/support/en_US/article.100048495\n■ Uninstall media server software.\n■ Shut down the media server.\nWarning: In a NetBackup DNAT environment, the identified IP address and host\nname may point to a gateway and not the media server. Verify the host information\nbefore attempting additional steps to resolve the problem."
    },
    "2205": {
        "code": 2205,
        "desc": "Snapshot replication is not supported for the specified details.",
        "first_action": "You must change the protection plan configuration to fix",
        "full_action": "You must change the protection plan configuration to fix\nthese issues. NetBackup does not retry the replication job."
    },
    "2206": {
        "code": 2206,
        "desc": "SnapshotManagerfailedtoretrievenetworksecuritygroupsagainstthe specified plug-in instance.",
        "first_action": "You must select a valid subnetId from one of the regions",
        "full_action": "You must select a valid subnetId from one of the regions\nthat are mentioned in the cloud provider configuration."
    },
    "2213": {
        "code": 2213,
        "desc": "Failed to delete configured plug-in instance in Snapshot Manager.",
        "first_action": "If a plug-in delete is needed, then delete all active",
        "full_action": "If a plug-in delete is needed, then delete all active\nsnapshots and attempt to delete the plug-in again. If you need to delete the plug-in\nwithoutclearingasnapshot,youcanpasstheX-NetBackup-Force-Plugin-Delete\nheader as TRUE. The snapshots remain in the cloud so you must remove those\nmanually."
    },
    "2228": {
        "code": 2228,
        "desc": "Security Group or Subnet configuration cannot be provided when you retain the network configuration for cloud VM restore.",
        "first_action": "Retain either the original network configuration or specify",
        "full_action": "Retain either the original network configuration or specify\na destination subnet or security group."
    },
    "2229": {
        "code": 2229,
        "desc": "Cannotretainnetworkconfigurationwhilerestoringacrosscloudservice providers.",
        "first_action": "Through API, delete the retainNetworkConfig flag or",
        "full_action": "Through API, delete the retainNetworkConfig flag or\nset it to False in the recovery or pre-recovery payload. Through the UI, deselect\nthe Restore network configuration option."
    },
    "2230": {
        "code": 2230,
        "desc": "Failed to create snapshot due to a missing asset.",
        "first_action": "Unsubscribe the asset from the protection plan.",
        "full_action": "Unsubscribe the asset from the protection plan."
    },
    "2231": {
        "code": 2231,
        "desc": "Not enough free space on host.",
        "first_action": "CreatesomespaceonthehostwhereNetBackupprimary",
        "full_action": "CreatesomespaceonthehostwhereNetBackupprimary\nserver is installed."
    },
    "2232": {
        "code": 2232,
        "desc": "File already exists.",
        "first_action": "Determine if the file being uploaded is a duplicate file.",
        "full_action": "Perform the following as appropriate:\n■ Determine if the file being uploaded is a duplicate file.\n■ Change the name of the file you want to upload."
    },
    "2233": {
        "code": 2233,
        "desc": "Failed to upload telemetry file.",
        "first_action": "Correct any errors that you find in the nbwebservice logs",
        "full_action": "Correct any errors that you find in the nbwebservice logs\nthat occurred when you attempted to create or to upload the telemetry file."
    },
    "2250": {
        "code": 2250,
        "desc": "TherequesthastimedoutwhileNetBackupretrievedtheerrorlogresults page.",
        "first_action": "Narrow the date range, then run the query again. If you",
        "full_action": "Narrow the date range, then run the query again. If you\nuse the APIs, you can also change the page size."
    },
    "2251": {
        "code": 2251,
        "desc": "The cursor value is invalid. NetBackup status codes 452 NetBackup status codes",
        "first_action": "Review the previous API response and use the correct",
        "full_action": "Review the previous API response and use the correct\nvalue for the page[after] value. If the request contains an invalid value, in the\nerror log locate the pagination meta tag in the response. The value of \"next\" is\nthe value that you want to use for page[after].\n\"meta\": {\n\"pagination\":\n{ \"next\": \"28002872c601fd648f3154e58532558e429c9632035c3bf042a6accdd77d8356\", \"limit\": 5 }\n}"
    },
    "2252": {
        "code": 2252,
        "desc": "The number of simultaneous error log requests has been exceeded.",
        "first_action": "Wait until one or more active requests for error logs are",
        "full_action": "Wait until one or more active requests for error logs are\ncomplete. Then try to run the new error log request again."
    },
    "2300": {
        "code": 2300,
        "desc": "The vmRecoveryDestination field must be specified in the recovery request. NetBackup status codes 453 NetBackup status codes",
        "first_action": "Verify that the vmRecoveryDestination field is specified",
        "full_action": "Verify that the vmRecoveryDestination field is specified\nand that it is not empty."
    },
    "2301": {
        "code": 2301,
        "desc": "The alternateLocationDirectory field must not be blank.",
        "first_action": "The alternateLocationDirectory field is optional. If",
        "full_action": "The alternateLocationDirectory field is optional. If\nthis field is included, you must specify a directory value for the\nalternateLocationDirectory field that is not empty."
    },
    "2302": {
        "code": 2302,
        "desc": "The instanceUuid field must not be blank.",
        "first_action": "Verify the instanceUuid field of the pre-recovery check",
        "full_action": "Verify the instanceUuid field of the pre-recovery check\nrequestis specifiedand notempty.TheinstanceUuidfieldoftherecovery request\nis optional. If the field is included, you must specify a value that is not empty."
    },
    "2303": {
        "code": 2303,
        "desc": "The stagingLocation field must not be blank.",
        "first_action": "The stagingLocation field is optional. If this field is",
        "full_action": "The stagingLocation field is optional. If this field is\nincluded, you must specify a path value that is not empty."
    },
    "2304": {
        "code": 2304,
        "desc": "The datastore field must not be blank.",
        "first_action": "Verify the datastore field of the pre-recovery check",
        "full_action": "Verify the datastore field of the pre-recovery check\nrequest is specified and not empty. The datastore field of the recovery request is\noptional. If that field is included, you must specify a value that is not empty."
    },
    "2305": {
        "code": 2305,
        "desc": "Invalid virtual machine user name or password.",
        "first_action": "Verify that the vmUsername and vmPassword fields are",
        "full_action": "Verify that the vmUsername and vmPassword fields are\nspecified and that they are not empty."
    },
    "2306": {
        "code": 2306,
        "desc": "The vmFiles field must not be blank.",
        "first_action": "Verify that the vmFiles field is specified and that it is not",
        "full_action": "Verify that the vmFiles field is specified and that it is not\nempty."
    },
    "2307": {
        "code": 2307,
        "desc": "The source field of virtual machine files must not be blank.",
        "first_action": "Verify that the file source field is specified and that it is",
        "full_action": "Verify that the file source field is specified and that it is\nnot empty."
    },
    "2308": {
        "code": 2308,
        "desc": "The destination field of virtual machine files must not be blank.",
        "first_action": "The destination field is optional. If this field is included,",
        "full_action": "The destination field is optional. If this field is included,\nyou must specify a destination path value that is not empty."
    },
    "2309": {
        "code": 2309,
        "desc": "Failed to create the agentless recovery restore specification.",
        "first_action": "The JSON request syntax is invalid.",
        "full_action": "The JSON request syntax is invalid."
    },
    "2310": {
        "code": 2310,
        "desc": "The size field must not be blank.",
        "first_action": "Verify that the size field is specified and that it is not",
        "full_action": "Verify that the size field is specified and that it is not\nempty."
    },
    "2311": {
        "code": 2311,
        "desc": "Failed to add guest virtual machine credentials.",
        "first_action": "Verify the NetBackup services are running on the master",
        "full_action": "Verify the NetBackup services are running on the master\nserver."
    },
    "2312": {
        "code": 2312,
        "desc": "The alternateLocationDirectory must begin with a /.",
        "first_action": "You must specify a forward slash (/) at the beginning of",
        "full_action": "You must specify a forward slash (/) at the beginning of\nthe alternateLocationDirectory path."
    },
    "2313": {
        "code": 2313,
        "desc": "The source path of virtual machine files must begin with /.",
        "first_action": "You must specify a forward slash (/) at the beginning of",
        "full_action": "You must specify a forward slash (/) at the beginning of\nthe file source path."
    },
    "2314": {
        "code": 2314,
        "desc": "The destination path of virtual machine files must begin with /.",
        "first_action": "You must specify a forward slash (/) at the beginning of",
        "full_action": "You must specify a forward slash (/) at the beginning of\nthe file destination path."
    },
    "2317": {
        "code": 2317,
        "desc": "Failed to remove guest virtual machine credentials.",
        "first_action": "Manually remove the credentials from the guest virtual",
        "full_action": "Manually remove the credentials from the guest virtual\nmachine."
    },
    "2318": {
        "code": 2318,
        "desc": "The appendString field must not be blank.",
        "first_action": "TheappendStringfieldisoptional.Ifthisfieldisincluded,",
        "full_action": "TheappendStringfieldisoptional.Ifthisfieldisincluded,\nyou must specify a string value for the appendString field that is not empty."
    },
    "2319": {
        "code": 2319,
        "desc": "Append string to file names is not supported for directories.",
        "first_action": "TheappendStringfieldisonlysupportedforfiles.Remove",
        "full_action": "TheappendStringfieldisonlysupportedforfiles.Remove\nany directories that are specified in the list of entries to be restored."
    },
    "2320": {
        "code": 2320,
        "desc": "Flatten directory structures is not supported for directories.",
        "first_action": "TheflattenDirectoryStructurefieldisonlysupported",
        "full_action": "TheflattenDirectoryStructurefieldisonlysupported\nforfiles.Removeanydirectoriesthatarespecifiedinthelistofentriestoberestored."
    },
    "2322": {
        "code": 2322,
        "desc": "Failed to create the staging location path.",
        "first_action": "The staging location defaults to /usr/openv/var/stagingloc or",
        "full_action": "Use the default staging location path or ensure that the\nuser-configured staging location path is valid.\nStaging location setup information:\n■ The staging location defaults to /usr/openv/var/stagingloc or\nVERITAS\\NetBackup\\var\\stagingloc.Thislocationisusedtostagefilesduring\nRestricted Restore Mode restore.\n■ You can override the path using the bp.conf parameter\nAGENTLESS_RHOST_STAGING_PATH = \"path\" configured on the recovery host.\nIfthepathdoesnotexistontherecoveryhost,NetBackupautomaticallycreates\nit with appropriate permissions."
    },
    "2323": {
        "code": 2323,
        "desc": "The staging location exists but ACLs and or permission bits set to on are insecure.",
        "first_action": "OnWindows:TheACLsdefinedmustbeexplicitandshouldnotrelyoninherited",
        "full_action": "Ensure that the staging location path is secure.\n■ OnWindows:TheACLsdefinedmustbeexplicitandshouldnotrelyoninherited\npermissions from the parent folder.\n■ On UNIX: Accessible only to the owner or the group. Permission bits for other\nshould look like 07?0 or drxw???---."
    },
    "2324": {
        "code": 2324,
        "desc": "Failed to remove the staging location and any files that are left on the recovery host.",
        "first_action": "Remove any files and folders from the staging location",
        "full_action": "Remove any files and folders from the staging location\nfolder that were left behind. Review the logs to determine why NetBackup failed to\ndelete the folder. Ensure no other process and or user blocks NetBackup from\nremoving this folder."
    },
    "2325": {
        "code": 2325,
        "desc": "SpecifiedrecoveryhostneedstobeatNetBackupversion9.0orgreater to support Restricted Restore Mode restores.",
        "first_action": "Select a recovery host that is NetBackup 9.0 or newer.",
        "full_action": "Select a recovery host that is NetBackup 9.0 or newer."
    },
    "2326": {
        "code": 2326,
        "desc": "Failed to update the recovery state file.",
        "first_action": "Review logs to determine why NetBackup did not read or",
        "full_action": "Review logs to determine why NetBackup did not read or\nwrite to the recovery state file."
    },
    "2328": {
        "code": 2328,
        "desc": "The communicationType field cannot be empty.",
        "first_action": "The communicationType field is mandatory. The value",
        "full_action": "The communicationType field is mandatory. The value\nmust be either set to SSH or WMI."
    },
    "2329": {
        "code": 2329,
        "desc": "The targetHost field is either empty or the name is invalid",
        "first_action": "The targetHost field is mandatory. Provide a valid host",
        "full_action": "The targetHost field is mandatory. Provide a valid host\nname or an IP address of the target host."
    },
    "2330": {
        "code": 2330,
        "desc": "The sshFingerprint field cannot be empty.",
        "first_action": "The sshFingerprint field is mandatory. Provide an SSH",
        "full_action": "The sshFingerprint field is mandatory. Provide an SSH\nkey fingerprint of the target host."
    },
    "2331": {
        "code": 2331,
        "desc": "The specified recovery host must be at NetBackup version 9.1 or later to support agentless restores.",
        "first_action": "VerifytheNetBackupversiononrecoveryhost.Theversion",
        "full_action": "VerifytheNetBackupversiononrecoveryhost.Theversion\nshould be 9.1 or later."
    },
    "2334": {
        "code": 2334,
        "desc": "Recovery host staging location does not exist.",
        "first_action": "Windows:",
        "full_action": "Verify that the default staging location path or the\nuser-configured staging location path for the recovery host is valid.\nNetBackup uses the following locations on the recovery host as default staging\nlocations:\n■ Windows:\ninstallpath\\Veritas\\NetBackup\\var\\tmp\\staging\\\n■ UNIX\n/usr/openv/var/tmp/staging/\nVerify that the staging location path that is used exists. For the user-configured\nstaginglocation,checkifavalidpathontherecoveryhostisspecifiedinthebp.conf\nparameter AGENTLESS_RHOST_STAGING_PATH = \\\"path\\\"."
    },
    "2335": {
        "code": 2335,
        "desc": "A tar image was not found at the staging location on the recovery host.",
        "first_action": "The tar image was not found at the recovery host staging",
        "full_action": "The tar image was not found at the recovery host staging\nlocation.Retrytheoperationandiftheissuepersists,visitsupport.veritas.com.The\nCohesityTechnicalSupportsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue."
    },
    "2336": {
        "code": 2336,
        "desc": "Internal error has caused failure of recovery validation.",
        "first_action": "Save the bpVMutil logs on the recovery host and contact",
        "full_action": "Save the bpVMutil logs on the recovery host and contact\nCohesity Technical Support."
    },
    "2337": {
        "code": 2337,
        "desc": "Not enough space available on recovery host.",
        "first_action": "Verify that there is sufficient free space available on the",
        "full_action": "Verify that there is sufficient free space available on the\nrecovery host staging location by comparing it to the total size of files or folders\nselected.Or,selectadifferentrecoveryhostwithsufficientfreespaceforperforming\nan agentless restore."
    },
    "2339": {
        "code": 2339,
        "desc": "Not enough space available on target host.",
        "first_action": "Ifnotexplicitlyprovided,NetBackupusestheuser’shome",
        "full_action": "Ifnotexplicitlyprovided,NetBackupusestheuser’shome\ndirectoryasadefaultstaginglocationontargethost.Verifythatsufficientfreespace\nis available on the target host or select a different staging location on same target\nhost with sufficient free space."
    },
    "2340": {
        "code": 2340,
        "desc": "Tar is not present on the target host.",
        "first_action": "Thetarutilityisnotpresentonthetargethost.Thesystem",
        "full_action": "Thetarutilityisnotpresentonthetargethost.Thesystem\ntar utility is required to be present on target host with UNIX operating system for\nperforming an agentless restore on it using NetBackup. Retry the operation after\ndeploying the tar utility."
    },
    "2341": {
        "code": 2341,
        "desc": "The user does not have required permission on the target host staging location.",
        "first_action": "Verify that the user has sufficient permissions to access",
        "full_action": "Verify that the user has sufficient permissions to access\nthe location and the target host staging location exists."
    },
    "2342": {
        "code": 2342,
        "desc": "The user does not have root or administrator privileges. To restore files and folders, provide user with root or administrator privileges.",
        "first_action": "The provided credentials do not have the required",
        "full_action": "The provided credentials do not have the required\npermissions on the target host for agentless files or folders restore. For Windows,\nyou must use the credential which is part of the local administrator group on the\ntarget host. For the UNIX target host, use the credential which is the root or the\nsudo account with ALL permissions."
    },
    "2343": {
        "code": 2343,
        "desc": "The administrator share of the target host is not accessible from the recovery host.",
        "first_action": "Firewall exceptions are set up correctly",
        "full_action": "Thiserrorisusuallyseenwhenthetargethostforagentless\nrestore has a Windows OS. Verify that the following items are set up correctly on\ntarget host:\n■ Firewall exceptions are set up correctly\n■ File and printer sharing is enabled.\n■ GPO/SoftwareRestrictionPolicyoranantivirussoftwaredoesnotblockaccess.\n■ The target host is accessible with valid credentials."
    },
    "2344": {
        "code": 2344,
        "desc": "The provided credentials are for a local administrator user.",
        "first_action": "For agentless restore in a User Account Control (UAC)",
        "full_action": "For agentless restore in a User Account Control (UAC)\nenvironment, you must provide the credentials of a domain user. The domain user\nmust be part of the local administrator group on the Windows target host."
    },
    "2345": {
        "code": 2345,
        "desc": "Agentless restore is not possible.",
        "first_action": "Agentless files or folders restore has failed due to an",
        "full_action": "Agentless files or folders restore has failed due to an\nunexpected reason. Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "2346": {
        "code": 2346,
        "desc": "Operating systems do not match. Ensure that the operating system of recovery host matches with the backed-up VM operating system.",
        "first_action": "Use an alternate recovery host that has same operating",
        "full_action": "Use an alternate recovery host that has same operating\nsystem as the backed-up VM."
    },
    "2347": {
        "code": 2347,
        "desc": "Failed to retrieve the backup image operating system.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "2348": {
        "code": 2348,
        "desc": "Recovery host operating system is not compatible with the provided communication mode.",
        "first_action": "The recovery host OS type and the communication type",
        "full_action": "The recovery host OS type and the communication type\nmust be compatible. If the recovery host is a UNIX OS, communication type should\nbe SSH. If the recovery host is a Windows OS, the communication type should be\nWMI."
    },
    "2349": {
        "code": 2349,
        "desc": "Target host SSH private key is invalid.",
        "first_action": "IftheauthenticationtypeisSSH_KEY,verifythatthesshKey",
        "full_action": "IftheauthenticationtypeisSSH_KEY,verifythatthesshKey\nfield is specified and not empty."
    },
    "2351": {
        "code": 2351,
        "desc": "Invalid input was received for configuring the service operation.",
        "first_action": "MakesurethattheinputJSONpassedtotheAPIiscorrect",
        "full_action": "MakesurethattheinputJSONpassedtotheAPIiscorrect\nas per the API specification. Review the nbwebservice logs for more information."
    },
    "2352": {
        "code": 2352,
        "desc": "Failed to generate response for the specified service operation.",
        "first_action": "Review the bpVMutil logs for more information.",
        "full_action": "Review the bpVMutil logs for more information."
    },
    "2353": {
        "code": 2353,
        "desc": "System call execution fails for the service operation.",
        "first_action": "Review the bpVMutil logs and retry the operation.",
        "full_action": "Review the bpVMutil logs and retry the operation."
    },
    "2354": {
        "code": 2354,
        "desc": "Unknown error has occurred while the service operation request was processed.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "2355": {
        "code": 2355,
        "desc": "Failed to start nbcctd for the specified host.",
        "first_action": "Review the bpVMutil logs for any errors and retry the",
        "full_action": "Review the bpVMutil logs for any errors and retry the\noperation."
    },
    "2356": {
        "code": 2356,
        "desc": "The specified directory path does not exist.",
        "first_action": "Ensure that the staging directory path that is specified in",
        "full_action": "Ensure that the staging directory path that is specified in\nthe CDP gateway configuration request exists on the CDP gateway."
    },
    "2357": {
        "code": 2357,
        "desc": "SQLite database error occurred.",
        "first_action": "CheckthestagingareafilesystemIO.Also,trytominimize",
        "full_action": "CheckthestagingareafilesystemIO.Also,trytominimize\nthe number parallel CDP operations, if any."
    },
    "2358": {
        "code": 2358,
        "desc": "The specified staging size validation failed.",
        "first_action": "Depending on what was specified in the API, you need",
        "full_action": "Depending on what was specified in the API, you need\ntoincreasethesizeofthestagingdirectory.Thesizeofthestagingdirectoryshould\nnot be less than 100 GB."
    },
    "2359": {
        "code": 2359,
        "desc": "Failed to register the specified virtual machine to the backup host.",
        "first_action": "The nbwebservice log on the master server.",
        "full_action": "Refer to the following logs for more details:\n■ The nbwebservice log on the master server.\n■ The bpVMutil log and the nbcctd log on the CDP gateway"
    },
    "2360": {
        "code": 2360,
        "desc": "Service configuration pre-checks are not met.",
        "first_action": "Increase the staging database size to more than 100 GB.",
        "full_action": "Perform the following as appropriate:\n■ Increase the staging database size to more than 100 GB.\n■ Increase memory to more than 4 GB."
    },
    "2361": {
        "code": 2361,
        "desc": "Failed to configure the specified backup host.",
        "first_action": "Check if all of the NetBackup processes are running.",
        "full_action": "Perform the following as appropriate:\n■ Check if all of the NetBackup processes are running.\n■ Check if the specified CDP gateway is correct and reachable."
    },
    "2362": {
        "code": 2362,
        "desc": "Failed to retrieve the service configuration.",
        "first_action": "Verifythatthe/usr/openv/netbackup/nbcct/nbcct.conf",
        "full_action": "Verifythatthe/usr/openv/netbackup/nbcct/nbcct.conf\nfile exists and is accessible by the nbcctd service."
    },
    "2363": {
        "code": 2363,
        "desc": "Failed to remove the service configuration.",
        "first_action": "Review the reason why the unlinking of the file failed.",
        "full_action": "Perform the following as appropriate:\n■ Review the reason why the unlinking of the file failed.\n■ The NBCCTD service is running, stop the service."
    },
    "2364": {
        "code": 2364,
        "desc": "Failed to stop the service.",
        "first_action": "Check the state of nbcctd process.",
        "full_action": "Perform the following:\n■ Check the state of nbcctd process.\n■ Stop the nbcctd service manually."
    },
    "2365": {
        "code": 2365,
        "desc": "Watermarks validation failed.",
        "first_action": "1. Check the specified value for low watermark and the high watermark.",
        "full_action": "Perform the following:\n1. Check the specified value for low watermark and the high watermark.\n2. Specify the values in the given range.\n■ Low watermark - (0-99)\n■ High watermark - (1-100)\n■ Verify that the low watermark value should be less than high watermark\nvalue."
    },
    "2367": {
        "code": 2367,
        "desc": "The specified host already has an active configuration.",
        "first_action": "Remove the currently configured CDP gateway and",
        "full_action": "Remove the currently configured CDP gateway and\nconfigure a new gateway."
    },
    "2368": {
        "code": 2368,
        "desc": "The host of this VM is not in a running state.",
        "first_action": "Turn on the VM and put it into a running state manually.",
        "full_action": "Turn on the VM and put it into a running state manually."
    },
    "2369": {
        "code": 2369,
        "desc": "Failed to unregister the specified VM from the backup host.",
        "first_action": "Refer to the bpVMutil and nbcctd logs on the CDP",
        "full_action": "Refer to the bpVMutil and nbcctd logs on the CDP\ngateway for more details."
    },
    "2370": {
        "code": 2370,
        "desc": "Another CDP enabled backup is running for this VM.",
        "first_action": "Scheduledormanuallytriggeredjobssucceedifthereare",
        "full_action": "Scheduledormanuallytriggeredjobssucceedifthereare\nno concurrent jobs running for same VM. If jobs keep failing, review the backup\nschedule and remove concurrent jobs for this VM."
    },
    "2372": {
        "code": 2372,
        "desc": "You can update CDP policy only with the same VM.",
        "first_action": "Specify the correct instance in the UUID in the policy",
        "full_action": "Specify the correct instance in the UUID in the policy\nupdate request."
    },
    "2373": {
        "code": 2373,
        "desc": "The staging directory is not empty.",
        "first_action": "Verify that the staging directory path that is specified in",
        "full_action": "Verify that the staging directory path that is specified in\nCDP configuration request is empty."
    },
    "2374": {
        "code": 2374,
        "desc": "NetBackup Accelerator must be enabled for CDP policies.",
        "first_action": "Enable the Accelerator option for the policy.",
        "full_action": "Enable the Accelerator option for the policy."
    },
    "2375": {
        "code": 2375,
        "desc": "Intelligent policy is not supported for CDP policies.",
        "first_action": "Change the VMware policy to not include CDP.",
        "full_action": "Change the VMware policy to not include CDP."
    },
    "2376": {
        "code": 2376,
        "desc": "You cannot select multiple VMs for backup in CDP policies.",
        "first_action": "Specify a single VM in the CDP policy creation request.",
        "full_action": "Specify a single VM in the CDP policy creation request."
    },
    "2377": {
        "code": 2377,
        "desc": "The VM is already subscribed to another policy.",
        "first_action": "UnsubscribetheVMfromthecurrentCDPprotectionplan",
        "full_action": "UnsubscribetheVMfromthecurrentCDPprotectionplan\nand retry the operation."
    },
    "2378": {
        "code": 2378,
        "desc": "Failed to remove the specified CDP host configuration.",
        "first_action": "Unsubscribe the CDP gateway from all the protection",
        "full_action": "Unsubscribe the CDP gateway from all the protection\nplans which use the CDP gateway and retry the operation."
    },
    "2379": {
        "code": 2379,
        "desc": "Failed to start the CDP gateway service because the memory size validation failed.",
        "first_action": "Increase the size of CDP host memory to greater than 4",
        "full_action": "Increase the size of CDP host memory to greater than 4\nGB."
    },
    "2380": {
        "code": 2380,
        "desc": "Failed to start the CDP gateway service.",
        "first_action": "Review the CCT_POOL_SIZE_QUOTA_PERCENTAGE value in",
        "full_action": "Review the CCT_POOL_SIZE_QUOTA_PERCENTAGE value in\nthe nbcct.conf file and increase the CCT_POOL_SIZE_QUOTA_PERCENTAGE to more\nthan 1 GB."
    },
    "2381": {
        "code": 2381,
        "desc": "Only full backup schedule is supported for CDP policies.",
        "first_action": "Removeanynon-fullbackupschedulesfrompolicycreation",
        "full_action": "Removeanynon-fullbackupschedulesfrompolicycreation\npayload and retry the operation."
    },
    "2382": {
        "code": 2382,
        "desc": "Insufficient space available on the staging path for the CDP gateway. NetBackup status codes 474 NetBackup status codes",
        "first_action": "Increase the size of the staging directory to minimum of",
        "full_action": "Increase the size of the staging directory to minimum of\n100 GB."
    },
    "2383": {
        "code": 2383,
        "desc": "NBCCTD is down for the specified host.",
        "first_action": "Ensure that the NBCCTD service is running on the CDP",
        "full_action": "Ensure that the NBCCTD service is running on the CDP\ngateway."
    },
    "2384": {
        "code": 2384,
        "desc": "Storage path does not have a supported file system.",
        "first_action": "Change the staging path to a non-root file system with a",
        "full_action": "Change the staging path to a non-root file system with a\nsupported file system type (XFS, EXT3, EXT4, NFS, VxFS)."
    },
    "2385": {
        "code": 2385,
        "desc": "Providedpathistotherootfilesystem.ProvideaCDPstagingareapath on non-root file system.",
        "first_action": "Changethestagingdirectorypathtoanon-rootfilesystem.",
        "full_action": "Changethestagingdirectorypathtoanon-rootfilesystem."
    },
    "2386": {
        "code": 2386,
        "desc": "No mount point found for the provided staging area path.",
        "first_action": "Change the staging path to a non-root file system with a",
        "full_action": "Change the staging path to a non-root file system with a\nvalid mount point."
    },
    "2387": {
        "code": 2387,
        "desc": "Cannot update accelerator forced rescan property, for the CDP policy.",
        "first_action": "Updating the accelerator forced rescan attribute for schedules in CDP policy is",
        "full_action": "Perform the following as appropriate:\n■ Updating the accelerator forced rescan attribute for schedules in CDP policy is\nnot allowed.\n■ Delete the current schedules using update (PUT) API, and create new schedule\nwith the accelerator forced rescan attribute value that you want to set."
    },
    "2388": {
        "code": 2388,
        "desc": "Only one accelerator force rescan schedule is supported for continuous data protection policies.",
        "first_action": "Remove any extra acceleratorForcedRescan enabled",
        "full_action": "Remove any extra acceleratorForcedRescan enabled\nschedules."
    },
    "2389": {
        "code": 2389,
        "desc": "Onlyoneacceleratorforcerescanschedule,andatleastonefullbackup schedule with no accelerator force rescan, are required for CDP policies.",
        "first_action": "Remove any extra acceleratorForcedRescan enabled schedules.",
        "full_action": "Perform the following as appropriate:\n■ Remove any extra acceleratorForcedRescan enabled schedules.\n■ Add at least one regular, full backup schedule in a CDP policy."
    },
    "2390": {
        "code": 2390,
        "desc": "Invalid backup host.",
        "first_action": "Specify a correct or a reachable backup host.",
        "full_action": "Specify a correct or a reachable backup host."
    },
    "2391": {
        "code": 2391,
        "desc": "Cannot subscribe the VM. No space available in the staging area.",
        "first_action": "Subscribe the VM to another gateway.",
        "full_action": "Subscribe the VM to another gateway."
    },
    "2392": {
        "code": 2392,
        "desc": "Cannot subscribe the VM. Insufficient memory available.",
        "first_action": "Subscribe the VM to another gateway.",
        "full_action": "Subscribe the VM to another gateway."
    },
    "2393": {
        "code": 2393,
        "desc": "The nbcctd service user on the CDP host does not have sufficient permissions to the staging directory.",
        "first_action": "The nbcctd user must have sufficient permissions to be",
        "full_action": "The nbcctd user must have sufficient permissions to be\nable to access the staging directory."
    },
    "2395": {
        "code": 2395,
        "desc": "VM quota size in GB validation has failed for CDP configuration.",
        "first_action": "You must enter a value of the VM quota size (in GB) that",
        "full_action": "You must enter a value of the VM quota size (in GB) that\nis within 10 GB to 1024 GB."
    },
    "2396": {
        "code": 2396,
        "desc": "VMquotareservepercentagevalidationhasfailedforCDPconfiguration.",
        "first_action": "You must enter a value for the VM quota reserve",
        "full_action": "You must enter a value for the VM quota reserve\npercentage that is within the limits of 25 to 50."
    },
    "2397": {
        "code": 2397,
        "desc": "Max full-sync validation has failed for CDP configuration.",
        "first_action": "You must enter a value for the max full-sync that is within",
        "full_action": "You must enter a value for the max full-sync that is within\nthe limits of 2 to 25."
    },
    "2398": {
        "code": 2398,
        "desc": "VMquotasizeinGBvalidationhasfailedforCDPconfigurationbecause the VM quota size in GB must be less than staging space.",
        "first_action": "You must enter a value for the VM quota size in GB that",
        "full_action": "You must enter a value for the VM quota size in GB that\nis less than the staging area size."
    },
    "2399": {
        "code": 2399,
        "desc": "CDP service configuration was successful but failed to add CDP host configured entry in the bp.conf file on the CDP gateway.",
        "first_action": "Verify that the bp.conf file is present at install_path/openv/netbackup",
        "full_action": "Perform the following as appropriate:\n■ Verify that the bp.conf file is present at install_path/openv/netbackup\nlocation and the service user has permission to modify.\n■ You can also add theCCT_IS_HOST_CONFIGURED=YESentry manually and try the\nconfiguration operation again."
    },
    "2400": {
        "code": 2400,
        "desc": "CDP configuration migration is not complete. First start the CDP service manually and complete the migration.",
        "first_action": "First, start the CDP service manually and then complete",
        "full_action": "First, start the CDP service manually and then complete\nthe migration (upgrade). Next, try the configuration update operation, if necessary."
    },
    "2401": {
        "code": 2401,
        "desc": "Cannot connect to the back-end services on the primary server or the CDP gateway.",
        "first_action": "Start the services on the CDP gateway and the primary",
        "full_action": "Start the services on the CDP gateway and the primary\nserver using bp.start_all. Also, verify that there is network connectivity between\nthe primary server and the CDP gateway."
    },
    "2402": {
        "code": 2402,
        "desc": "Cannot perform the requested CDP operation because an internal error occurred.",
        "first_action": "Review the nbwebservice, bprd, bpVMutil, and the",
        "full_action": "Review the nbwebservice, bprd, bpVMutil, and the\nnbcctd logs for more information. Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "2450": {
        "code": 2450,
        "desc": "Target host operating system is not supported for the agentless files or folders restore.",
        "first_action": "SUSE Linux Enterprise Server, Microsoft Windows, and",
        "full_action": "SUSE Linux Enterprise Server, Microsoft Windows, and\nRed Hat Enterprise Linux (RHEL) are supported platforms. Refer to the NetBackup\nClient Compatibility List for the supported platforms for agentless restore."
    },
    "2451": {
        "code": 2451,
        "desc": "Invalid target host user name or password.",
        "first_action": "Verify that the user name and password fields, in the",
        "full_action": "Verify that the user name and password fields, in the\nauthenticationdetailsoftherecoveryandpre-recoverycheckrequest,arespecified\nand are not empty."
    },
    "2504": {
        "code": 2504,
        "desc": "Direct expiration of a mirror copy is not allowed",
        "first_action": "None",
        "full_action": "None"
    },
    "2505": {
        "code": 2505,
        "desc": "Unable to connect to the database",
        "first_action": "In this case, the semmni value was insufficient at 128. By",
        "full_action": "In this case, the semmni value was insufficient at 128. By\nincreasingthisvalueto1024,theODBCconnectionwassuccessfulandNetBackup\nthenransuccessfully.Althoughthiscouldaffectotherplatforms,thiserrorhasbeen\nseen in multiple RedHat Enterprise Linux (RHEL) environments, usually when the\nRHELsystemistheNetBackupmasterserver.AnysupportedversionofNetBackup\ncould be affected by this environmental issue. See the Recommended NetBackup\nUNIX / Linux semaphore tuning values (Linux/Solaris/HP-UX/AIX) article at the\nfollowing location for general recommendations and refer to the platform vendor\nsupport for additional details:\nhttps://www.veritas.com/support/en_US/article.100023842"
    },
    "2517": {
        "code": 2517,
        "desc": "Backup set identifier may only contain a-z, A-Z, 0-9 and .-+_",
        "first_action": "Removetheinvalidcharacterfromthebackupsetidentifier.",
        "full_action": "Removetheinvalidcharacterfromthebackupsetidentifier.\nThis value is specified in the Attributes tab of the GUI Policy utility."
    },
    "2521": {
        "code": 2521,
        "desc": "Datafile copy tag may only contain a-z, A-Z, 0-9 and .-+_",
        "first_action": "Remove the invalid character from the Datafile copy tag.",
        "full_action": "Remove the invalid character from the Datafile copy tag.\nThis value is specified in the Oracle tab of the GUI Policy utility."
    },
    "2522": {
        "code": 2522,
        "desc": "Oracle policy cannot include a pluggable database with a FRA backup.",
        "first_action": "ChecktheOracleIntelligentPolicy.IfthepolicyhasProtect",
        "full_action": "ChecktheOracleIntelligentPolicy.IfthepolicyhasProtect\nInstances and Databases selected and includes pluggable databases, then the\nbackup selection cannot be Fast Recovery Area (FRA). You can either select a\ndifferent backup selection or select the Oracle 12c instance and Fast Recovery\nArea (FRA)."
    },
    "2523": {
        "code": 2523,
        "desc": "Failed to add client to NetBackup configuration.",
        "first_action": "Save the nbemm and bpdbm logs and contact Cohesity",
        "full_action": "Save the nbemm and bpdbm logs and contact Cohesity\nTechnical Support."
    },
    "2524": {
        "code": 2524,
        "desc": "Catalogbackupfailedbecausethepassphraseforthedisasterrecovery package is not set.",
        "first_action": "In the NetBackup Administration Console, expand Security Management",
        "full_action": "To set the passphrase for the disaster recovery package,\ndo one of the following:\n■ In the NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use the nbseccmd -drpkgpassphrase command."
    },
    "2525": {
        "code": 2525,
        "desc": "The passphrase for the disaster recovery package is not set. You must set it for the catalog backups to be successful.",
        "first_action": "In the NetBackup Administration Console, expand Security Management",
        "full_action": "To set the passphrase for the disaster recovery package,\ndo one of the following:\n■ In the NetBackup Administration Console, expand Security Management\n>GlobalSecuritySettings.OntheDisasterRecoverytab,setthepassphrase.\n■ Use the nbseccmd -drpkgpassphrase command."
    },
    "2526": {
        "code": 2526,
        "desc": "The master server certificate cannot be backed up from Windows certificate store during catalog backup.",
        "first_action": "The private key of the master server’s certificate file is marked as exportable",
        "full_action": "Ensure the following to resolve the issue:\n■ The private key of the master server’s certificate file is marked as exportable\nwhile you store it in the Windows certificate store.\n■ The certificate is available as a file in the file system and the ECA_CERT_PATH,\nECA_TRUST_STORE_PATH,andECA_PRIVATE_KEY_PATHconfigurationoptionsare\nset to appropriate values. For more information on the NetBackup configuration\noptions, refer to the NetBackup Administrator’s Guide, Volume I."
    },
    "2527": {
        "code": 2527,
        "desc": "Changes are not allowed for a template that a protection plan manages.",
        "first_action": "Use the NetBackup web UI to update or delete protection",
        "full_action": "Use the NetBackup web UI to update or delete protection\nplan."
    },
    "2528": {
        "code": 2528,
        "desc": "Changes are not allowed for an SLP that a protection plan manages.",
        "first_action": "Use the NetBackup web UI to update or delete protection",
        "full_action": "Use the NetBackup web UI to update or delete protection\nplan."
    },
    "2531": {
        "code": 2531,
        "desc": "Thedisasterrecoverypackagewassuccessfullycreated.However,one or more users who have permissions to the identity files from the package do not exist on the system.",
        "first_action": "Identify whether the Access Control Lists (ACL) of these",
        "full_action": "Identify whether the Access Control Lists (ACL) of these\nnon-existing users are required or not. Review and compare the ACLs of the same\nidentity file on a host where NetBackup is freshly installed. If these users do not\nneed to have permission to the identity files, delete the ACLs of the associated\nidentity files.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnical Support site offers additional information to help you troubleshoot this\nissue."
    },
    "2532": {
        "code": 2532,
        "desc": "Schedule copies have storage units from different media servers.",
        "first_action": "If you use multiple copies for a schedule, make sure that",
        "full_action": "If you use multiple copies for a schedule, make sure that\nthe storage units that are assigned to each schedule are from same media server."
    },
    "2607": {
        "code": 2607,
        "desc": "Server information is not available.",
        "first_action": "Ensure that the MySQL installation is present, and the",
        "full_action": "Ensure that the MySQL installation is present, and the\nservices are up.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs log\nfrom the NetBackup client host."
    },
    "2610": {
        "code": 2610,
        "desc": "MySQL library path is not present in Backup Selection as well as environment variables.",
        "first_action": "Set the LIB_MYSQL_CLIENT Path in the Environment",
        "full_action": "Set the LIB_MYSQL_CLIENT Path in the Environment\nVariables and the Path Variable for Windows and Linux, respectively. Also, ensure\nthe symbolic link for the MySQL client library is correctly created in the same\nLIB_MYSQL_CLIENT directory.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host."
    },
    "2611": {
        "code": 2611,
        "desc": "Database name was not found for the MySQL backup dump.",
        "first_action": "Ensure that the protection plan is properly attached with",
        "full_action": "Ensure that the protection plan is properly attached with\nthe databases to be backed up.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host."
    },
    "2612": {
        "code": 2612,
        "desc": "Invalid library path was given for MySQL backup.",
        "first_action": "Set the LIB_MYSQL_CLIENT Path in the Environment",
        "full_action": "Set the LIB_MYSQL_CLIENT Path in the Environment\nVariables and Path Variable for Windows and Linux, respectively. Also, ensure the\nsymbolic link for the MySQL client library is correctly created in the same\nLIB_MYSQL_CLIENT directory.\nIf you need to contact Cohesity Technical Support, you must have the ncfnbcs and\nbphdb logs from the NetBackup client host."
    },
    "2613": {
        "code": 2613,
        "desc": "Unable to obtain MySQL credentials.",
        "first_action": "Ensure that the specific database credentials are correct.",
        "full_action": "Ensure that the specific database credentials are correct.\nIf you need to contact Cohesity Technical Support, you must have the bphdb log\nfrom the NetBackup client host."
    },
    "2800": {
        "code": 2800,
        "desc": "Standard policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages about why\nthe restore failed. Also, check the All Log Entries report on the server.\n■ Check the following logs for additional failure information:\n■ NetBackup tar log\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Make sure that the required media server is available for the restore, or use the\nMedia host override option.\n■ Verify that the media that is required for the restore is present and that the robot\nhas been inventoried.\n■ Verify that no network issues exist between the media server and the client.\n■ Select the original path that is listed in the Backup Selections tab."
    },
    "2801": {
        "code": 2801,
        "desc": "Oracle policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the Oracle instance that you restore.\n■ Check the NetBackup dbclient and user_ops logs for additional failure\ninformation.\n■ If restoring to an alternate client using RMAN, more information is available in\nthe following technical article:\nhttps://www.veritas.com/support/en_US/article.100022605\nCheck that the Oracle user on the client can successfully communicate with the\nmaster server by using the bpclntcmd -pn command.\n■ Check that the Oracle user on the client can see the backup images on the\nmaster by using the bplist command.\n■ On UNIX and Linux hosts, check that the oracle user has sufficient permissions\nto read /etc/services, /etc/nsswitch.conf, and\n/usr/openv/netbackup/bp.conf.\n■ Ensure thatthe Oracle databaseis linked correctly, according to the NetBackup\nforOracleAdministrator'sGuide(forexample,$ORACLE_HOME/lib/libobk.so).\nMore information is available in the following technical article:\nhttps://www.veritas.com/support/en_US/article.100021454\n■ Correct the problems that you find and retry the restore."
    },
    "2802": {
        "code": 2802,
        "desc": "Informix-On-BAR policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the Informix instance that you restore.\n■ Check the NetBackup infxbsa and user_ops logs from the client, and the bprd\nlog from the master server for additional failure information.\n■ Check the Informix BAR_ACT_LOG, BAR_DEBUG_LOG, and MSGPATH logs\nfor additional failure information.\n■ For large database restores, you may need to increase the client read timeout\nvalue.\n■ If you are restoring to an alternate client, review the checklist in the following\narticle:\nhttps://www.veritas.com/support/en_US/article.100010442\n■ Correct the problems that you find and retry the restore."
    },
    "2803": {
        "code": 2803,
        "desc": "Sybase policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on the Sybase instance that you restore and\non the directories where files are restored.\n■ Check the NetBackup sybackup log for additional failure information.\n■ Create the following log folders, then retry the restore:\nOn the client:\n/usr/openv/netbackup/logs/bphdb\n/usr/openv/netbackup/logs/bprestore\n/usr/openv/netbackup/logs/tar\n/usr/openv/netbackup/logs/sybackup\nOn the media server:\n/usr/openv/netbackup/logs/bptm\n/usr/openv/netbackup/logs/bpbrm\nOn the master server:\n/usr/openv/netbackup/logs/bprd\n■ Correct the problems that you find and retry the restore.\nTo set the debug level on UNIX and Linux clients, enter the following line in the\nbp.conf file:\nVERBOSE = 5\nFor a Sybase alternate client restore, the user ID (UID) of the restoring Sybase\nbackup server must match the UID of the Sybase backup server from the source\nhost.\nFor an alternate client restore, authorize the alternate client to access images for\nthe original client.\nVerify that the alternate client can browse the backup images for the original client:\n# /usr/openv/netbackup/bin/bplist -C <origClient> -t 7 -l -R /\n# install_path\\netbackup\\bin\\bplist -t 7 -l -R /\nOn the alternate client, use the bpclntcmd command to test connectivity and name\nresolution. The command should display the name of the master server on the first\nline. The second line must contain the IP address of the network interface that the\nalternate client used when communicating with the master server. The first word\non the second line is the name of the alternate client as resolved on the master\nserver from the IP address. The second word on the second line may be 'NULL' if\nthealternateclientisnotbeingbackedup.Otherwise,itisthenameofthealternate\nclient (or an alias) which is defined in a backup policy on the master server.\n# /usr/openv/netbackup/bin/bpclntcmd -pn\nMakesurethatCLIENT_READ_TIMEOUTonthealternateclientandmediaserver\nis set large enough to allow the tapes to be read, the data transferred, and the\ndatabase instance to write the data to disk.\nSee the following technical article for information about the steps for a Sybase\nalternative client restore operation:\nhttps://www.veritas.com/support/en_US/article.100016002"
    },
    "2804": {
        "code": 2804,
        "desc": "MS-SharePoint policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Create the following log folders on the SQL Server, the front-end web server,\nthe media server, and the master server:\ninstall_path\\NetBackup\\logs\\tar\ninstall_path\\NetBackup\\logs\\bpresolver\ninstall_path\\NetBackup\\logs\\bpbrm (media server)\ninstall_path\\NetBackup\\logs\\bprd (master server)\nIf you use granular restore technology (GRT), the following log folders also\napply:\ninstall_path\\NetBackup\\logs\\ncf\ninstall_path\\NetBackup\\logs\\ncflbc\ninstall_path\\NetBackup\\logs\\ncfgre\ninstall_path\\NetBackup\\logs\\nbfsd\ninstall_path\\NetBackup\\logs\\spsv2ra\n■ Check all SharePoint server Event Viewers (application and system) for any\nerrors.\n■ Connect to the server where the SharePoint front-end server runs and launch\nthe restore using Backup, Archive, and Restore GUI.\n■ Make sure that the restore is being launched correctly.\nSee the NetBackup for Microsoft SharePoint Administrator’s Guide.\n■ Correct the problems that you find and retry the restore.\n■ If you need to restore a VMware job, you must ensure that the media server is\nadded to the additional server list. To access this list in the NetBackup\nAdministration Console, expand Host Properties > Master Server.\nDouble-click the name of the server to view the properties. Select the Servers\ntab to display the server list. In the Servers properties dialog box, select the\nAdditional Servers tab and add the media server to the server list."
    },
    "2805": {
        "code": 2805,
        "desc": "MS-Windows policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check that you have selected the correct restore type on the Backup, Archive,\nand Restore GUI.\n■ Check ownership and permission on directories where files are restored.\n■ Check the following logs for additional failure information:\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Correct the problems that you find and retry the restore."
    },
    "2806": {
        "code": 2806,
        "desc": "NetWare policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information. Also check the\nfollowing log files: bpcd, bpsrv, bprest, and user_ops.\n■ For target restores, ensure that you have create and write rights to the volume\nthat you are trying to restore. In the BP.INI file, ensure that the\nAllow_Server_Write parameter is set to yes.\n■ If you launched a non-target restore from the NetBackup Administration\nConsole,ensurethattheAllowserverdirectedrestoresparameterisselected.\n■ Correct the problems that you find and retry the restore."
    },
    "2807": {
        "code": 2807,
        "desc": "SQL-BackTrack policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored and on\nthe SQL-BackTrack instance that you are restoring.\n■ Check the NetBackup backtrack log for additional failure information.\n■ Correct the problems that you find and retry the restore."
    },
    "2808": {
        "code": 2808,
        "desc": "Windows File System policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check that you have selected the correct restore type on the Backup, Archive,\nand Restore GUI.\n■ Check ownership and permission on directories where files are restored.\n■ Check that the destination directories or files exist. If so, select the Overwrite\nexisting files option on the Backup, Archive, and Restore GUI.\n■ Check the following logs for additional failure information:\n■ Master server: bprd, nbjm\n■ Media server: bpbrm, bptm, bpdm\n■ Client: tar\n■ Correct the problems that you find and retry the restore."
    },
    "2809": {
        "code": 2809,
        "desc": "MS-SQL-Server policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored and on\nthe SQL instance that you are restoring.\n■ Check ownership and permission on the SQL Server instance and on the\ndirectories where files are restored.\n■ Check the following logs for additional failure information on the client side:\ninstall_path\\NetBackup\\logs\\dbclient\ninstall_path\\NetBackup\\logs\\bpbkar (Snapshot Client)\ninstall_path\\NetBackup\\logs\\bpfis (Snapshot Client)\ninstall_path\\NetBackup\\logs\\bppfi (instant recovery)\n■ Check the SQL server Event Viewers (application and system) for any errors\nor messages that are related to the restore operation.\n■ Increase restore verbose levels.\nSee the NetBackup for SQL Server Administrator’s Guide.\nReview this guide to verify that you launched the restore correctly.\n■ Connect to the server where SQL is running and launch the restore from that\nserver using the Backup, Archive, and Restore GUI.\n■ Correct the problems that you find and retry the restore."
    },
    "2810": {
        "code": 2810,
        "desc": "MS-Exchange policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the Exchange instance that you restore\nand the directories where files are restored.\n■ Verify the following log files depending on the type of restore being performed.\nAll the log folders are located in the install_path\\NetBackup\\logs folder.\n■ beds - All restore operations.\n■ tar - All restore operations.\nRestores with Granular Recovery Technology (GRT):\n■ nbfsd - This log appears on the client and the media server.\n■ ncf - This log uses unified logging and appears on the destination client or\nproxy client.\n■ ncflbc - This log is for nblbc.exe. It appears on the destination client or\nproxy client.\n■ ncfgre - This log is for nbgre.exe. It appears on the destination client or\nproxy client.\nInstant Recovery and Instant Recovery off-host:\n■ bpbkar-Foroff-hostInstantRecoveryrestores,bpbkarlogsonthealternate\nclient.\n■ bpfis - This log applies to Instant Recovery rollback restores. For off-host\nInstant Recovery backups, bpfis logs exist on both the primary and the\nalternate clients.\n■ bppfi-Foroff-hostInstantRecoveryrestores,bppfilogsonboththeprimary\nand the alternate clients.\n■ ChecktheExchangeServerEventViewerforApplicationandSystemmessages\nthat are related to the restore operation.\n■ Connect to the server where Exchange is running and launch the restore from\nthat server using the Backup, Archive, and Restore GUI.\n■ Verify that you launched the restore correctly.\nSee the NetBackup for Microsoft Exchange Server Administrator’s Guide.\n■ Correct the problems that you find and retry the restore."
    },
    "2811": {
        "code": 2811,
        "desc": "SAP policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the SAP instance that you restore and the\ndirectories where the files are restored.\n■ Check the following logs for additional failure information: backint, tar,\ndbclient, bprestore, and user_ops.\n■ Correct the problems that you find and retry the restore."
    },
    "2812": {
        "code": 2812,
        "desc": "DB2 policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission of the DB2 instance that you restore and the\ndirectories where the files are restored.\n■ Check the NetBackup bpdb2 log for additional failure information.\n■ Ensure that you configured the clients to allow redirected restores. See the\nNetBackup for DB2 Administrator’s Guide for details.\n■ Correct the problems that you find and retry the restore."
    },
    "2813": {
        "code": 2813,
        "desc": "NDMP policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check the ownership and permission on directories where files are restored.\n■ Verify that the destination NDMP host supports DAR. If not, disable DAR.\n■ Check the ndmpagent (Originator ID 134) log for additional failure information.\n■ Check the NetBackup bptm log for additional failure information.\n■ Check that the Force rollback even if it destroy snapshots option of the\npoint-in-time rollback restore is set (checked) or not set (unchecked).\nFormoreinformationonrollbackrestore,pleaseseetheNetBackupReplication\nDirector Solutions Guide.\n■ Correct the problems that you find and retry the restore."
    },
    "2814": {
        "code": 2814,
        "desc": "FlashBackup policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Enable and verify VxMS logs for additional failure information.\n■ For VMware restores, enable the bpvmutil logs.\n■ If you run a VMware restore, make sure that the user account that is specified\nin the VMware credentials has full administration rights on the target vCenter\nand the ESX server.\n■ Correct the problems that you find and retry the restore."
    },
    "2815": {
        "code": 2815,
        "desc": "AFS policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Correct the problems that you find and retry the restore."
    },
    "2816": {
        "code": 2816,
        "desc": "DataStore policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. If you run one PureDisk disaster recovery, check the output from\nthe /opt/pdinstall/DR_Restore_all.sh script on the PureDisk node. Also,\ncheck the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check ownership and permission on the database instance that you restore.\n■ Check the NetBackup exten_client log for additional failure information.\n■ If you restore a Netezza appliance, collect the log files from\n/nz/kit/log/restoresvf/*.\n■ Correct the problems that you find and retry the restore."
    },
    "2817": {
        "code": 2817,
        "desc": "FlashBackup Windows policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information.\n■ Correct the problems that you find and retry the restore."
    },
    "2818": {
        "code": 2818,
        "desc": "NetBackup Catalog policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Ensure that NetBackup is at the same version and patch level as the computer\nwhere the catalog image was created.\n■ Ensure that the path where you restore the catalog is same as when it was\nbacked up.\n■ Ensure that sufficient disk space exists on the target system where the restore\nruns.\n■ Ensure that the current master server host name matches the host name of the\ncomputer where the catalog image was created.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar, admin, bptm, and bpbrm logs for additional failure\ninformation.\n■ Correct the problems that you find and retry the restore."
    },
    "2819": {
        "code": 2819,
        "desc": "Enterprise Vault policy restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Check the NetBackup tar log for additional failure information. Also, check the\nEnterprise Vault server Event Viewer (application and system) for errors or\nclues.\n■ Connect to the server where the Enterprise Vault front-end runs. Launch the\nrestore by using the Backup, Archive, and Restore GUI.\n■ Verify that you launched the restore correctly.\nSee the NetBackup for Enterprise Vault Agent Server Administrator’s Guide.\n■ Correct the problems that you find and retry the restore."
    },
    "2820": {
        "code": 2820,
        "desc": "NetBackup VMware policy restore error",
        "first_action": "Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or",
        "full_action": "Review the following lists for solutions to this error.\nCheck the job details in the Activity Monitor and take action as dictated by that\ninformation, as follows:\n■ Ensure that an .ISO file that is presented to a virtual machine as a virtual CD or\nDVD during backup is available on the destination host.\n■ For a successful hotadd restore, ensure that the two virtual machines are in the\nsame VMware data center.\n■ Select a different transport mode and retry the restore.\n■ You cannot restore restore a file that has a path name longer than 1023\ncharacters.\n■ If possible, restore the VM to a VMware server that supports the VM's hardware\nversion.\n■ In Backup, Archive, and Restore, change the restored virtual disk to Thick\nProvision Lazy Zeroed or Thin Provisioning.\nWhen a VMware agentless restore is performed, the restore can cause one of the\nfollowing issues:\n■ FailedtoidentifythenewlyattacheddeviceondestinationVM%s.Onepossible\ncause is that the destination VM user credentials have insufficient permissions.\nIt is recommended target VM user credentials with root or administrative\nprivileges.\n■ Failed to attach the temporary vmdk %s to the destination VM %s with error\n%d.\nMakesurethatthetargetVMhasatleastoneparavirtualcontrollerwithavailable\nLUNs.\n■ Failed to upload the process rename file to the destination VM %s with error\n%d.\nMake sure there is sufficient space available in target VM.\n■ Failed to restore the selected files and folders.\nReview the tar log to troubleshoot this issue."
    },
    "2821": {
        "code": 2821,
        "desc": "Hyper-V policy restore error",
        "first_action": "Update the NIC drivers and firmware if necessary.",
        "full_action": "Try the following:\n■ Update the NIC drivers and firmware if necessary.\n■ Ensure that the network hardware between the media server and the client\noperates properly.\n■ Add NetBackup processes and directories to the Antivirus Exclusion List since\nantivirus applications may close the established socket.\n■ Increase TCP resiliency on the Windows hosts (master servers, media servers,\nand clients) by setting the TcpMaxDataRetransmissions registry key to a value\nof 10. The default value is 5.\nMore information is available from Microsoft about the\nTcpMaxDataRetransmissions registry key:\nhttp://msdn.microsoft.com/en-us/library/aa915651.aspx"
    },
    "2822": {
        "code": 2822,
        "desc": "Hypervisor policy restore error.",
        "first_action": "Review the job details from the Activity Monitor for issue details. Refer to the",
        "full_action": "Pleasereview thefollowinginformationforyour particular\nworkload.\n■ Review the job details from the Activity Monitor for issue details. Refer to the\nbpVMutil logs for more information. If the issue persists, visit the Cohesity\nTechnical Support website. The Cohesity Technical Support website offers\nadditional information to help you troubleshoot this issue.\n■ Ensure that there is enough space available on the destination storage domain\nto restore the disks. The disk creation can take some time to complete.\n■ Verify that the entries in the rename file are in the correct format.\n■ Refer to the bpVMutil logs for more information. If the issue persists, visit the\nCohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue.\nRHV:\n■ VerifytheRHV_CREATEDISK_TIMEOUTconfigurationentryandupdateitifrequired.\n■ VerifythatthetargetstoragedomaintypeissupportedforrestoresbyNetBackup.\n■ Refer to the bpVMutil logs for more information. If the issue persists, visit the\nCohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue.\n■ RefertotheRHVdocumentationforthesupportedVMdisplaynamecharacters\nand length.\nNutanix AHV:\n■ Refer to the Nutanix AHV documentation for the supported VM display name\ncharacters and length."
    },
    "2824": {
        "code": 2824,
        "desc": "Cloud policy restore error.",
        "first_action": "For VM-based deployment, if no external",
        "full_action": "The following tables list the nbcs level error messages\nwhich are displayed in Job Details on the Activity Monitor and the action you\nneed to take to fix the issue.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset\nMessage Recommended action\nDiskResource group <RG>doesnotexist. The resource group in the disk destination\npathdoesnotexist.Selecttheresourcegroup\nwhich is present in the cloud.\nDisk subscription ID <> must be the Ensure that the given subscription ID as part\nsame as the host subscription ID. of the disk destination path, match with\nsubscription ID from VM destination path.\nVM with name <> already exists. Retrytheoperationafterchangingthedisplay\nname.\nVM display name <> is unsupported. Ensure that the VM name is compliant with\nthe cloud provider’s naming convention.\nDestinationPath <>: is not configured The provided subscription is not configured\nfor selected config. inthegivendestinationconfiguration.Provide\na subscription that exists in the configured\ncloud provider.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset (continued)\nMessage Recommended action\nSubnet <id> does not exist. Thedestinationnetworkthatisselecteddoes\nnot exist in the selected subscription. Select\na network which is present on the cloud.\nEnsure that discovery has run after the\ncreation of a new subnet.\nDestination Resource group <RG> does The resource group in the VM destination\nnot exist. path does not exist. Select a resource group\nwhich is present on the cloud.\nRegion <> is not configured. Ensure that the selected region is part of the\ndestination configuration.\nFailed to find sqlpackage client utility on a Installtherequiredsqlpackageutilityonthe\ngiven host. media server.\nConfigure and mount Universal Share ■ For VM-based deployment if an external\nAccelerator failed. disk is attached to the NetBackup\nSnapshot Manager host and mounted as\n/datamover_storage then ensure at\nleast 500GB of disk space is available.\n■ For VM-based deployment, if no external\ndisk is attached to the NetBackup\nSnapshot Manager host or if it is not\nmountedas/datamover_storage:then\nensure that the root partition has at least\n500GB of disk space available.\nFailed to get export path and vpfs server. ■ InCloudScaledeploymentensurethatall\nMSDP pods have at least 500GB of disk\nspace available.\n■ In VM-based deployment ensure that the\nstorage server should have at least\n500GB of disk space available at the\nconfigured storage path.\nThe following are only applicable for Azure Stack restore from backup.\nRestore failed due to the staging location not correctly specified. Verify that the\n/cloudpoint/azurestack.conf has a correct entry for the staging location.\nTable 1-2 Restore failed as the pre-requisites for restore operation were\nnot satisfied for the asset (continued)\nMessage Recommended action\nFailed to get a staging location for the Ensure that staging location details (for\nsubscription: {id}. example:storageaccountandcontainer)are\nadded in the file\n/cloudpoint/azurestack.conf for the\nselected target subscription.\nThe storage account:<account Ensurethatthestorageaccountispresentin\nname>, does not exist. the target subscription.\nThe container: {container name}, Ensure that the storage account container is\ndoes not exist in the storage account: present in the storage account.\n{account name}.\nTable 1-3 Failed to perform a recovery operation for the asset\nMessage Recommended action\nFailed to create an asset <disk/host>. One of the probable reasons can be that the\nquota limit has exceeded. Check if the\nrequired resource limit is available.\nAsset <> not found. Ensure that the asset is present in the cloud\nand it is discovered.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you CopythelatestCRLintotheECA_CRL_PATH\nhaveconfiguredtheECA_CRL_PATH,ensure path or ensure the CRL distribution point\nthat valid CRLs are present at the location. URL, from the respective host certificate, is\nCheckiftheCRLURLisaccessiblefromthe accessible from the Snapshot Manager.\nSnapshot Manager.\nTheAzureorAzureStackservers’certificate The certificate of the server has been\nis revoked. Ensure that the certificates are revoked. Contact your security administrator\nnot revoked by certificate authority. for assistance.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsure that the ECA_CRL_PATH is updated the ECA_CRL_PATH path.\nwith the latest CRL.\nYou can update the NetBackup CRL cache\nmanuallybyusingthefollowingcommandon\nSnapshot Manager:\ndocker exec -i flexsnap-certauth bash -c\n'/usr/openv/pdde/pdopensource\n/nbcertcmdtool/nbcertcmdtool -atLibPath\n/usr/openv/pdde/pdopensource/nbcertcmdtool\n-updateCRLCache'\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager’s system\nvalid. time or provide a valid CRL.\nThe date of the last update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe date of the next update of the certificate ChecktheCRLusingtheopensslcommand\nrevocation list (CRL) is not in a valid format. or contact your Security Administrator.\nThe Azure or Azure Stack server certificate Reviewthecertificateandensurethevalidity\nisexpired.Ensurethattheserverhasavalid of it by checking the certificate to make sure\ncertificate. that the end date is valid.\nCheck if the Snapshot Manager’s clock is in\nsync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nThe Azure or Azure stack servers certificate Check if the Snapshot Manager’s clock is in\nis not yet valid. sync with the specified server. Correct the\ntime on the host, if necessary, and rerun the\noperation. If the problem continues, save all\nof the error log information and contact\nCohesity Technical Support.\nTable 1-4 RestorefailedduetoSSLcertificateissuesorconnectivityissues\nbetween Snapshot Manager and Azure or Azure Stack\n(continued)\nMessage Recommended action\nUnabletofindthepublicrootandintermediate Ensure that the certificate file is configured\ncertificates of the Azure Stack server. correctly at the ECA_TRUST_STORE_PATH\nlocated in the bp.conf file on the Snapshot\nManager.\nRerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support.\nFailed to load the Certificate Revocation List Ensure that the valid CRL file is configured\n(CRL) from the CRL cache. Ensure that the ontheSnapshotManagerforAzureorAzure\nvalid CRL file is configured on the Snapshot Stack by the ECA_CRL_PATH.\nManager for Azure or Azure Stack by\nECA_CRL_PATH.\nFailedtoconnecttotheAzureorAzureStack Ensure network connectivity between the\nserver.Ensurenetworkconnectivitybetween Snapshot Manager and the Azure or Azure\nSnapshot Manager and the Azure or Azure Stack server.\nStack server.\nCannot use the specified SSL cipher for Contact Cohesity Technical Support.\nAzure or Azure Stack server.\nOperation failed with cURL error: Rerun the operation. If the problem persists,\nsave all of the error log information and\ncontact Cohesity Technical Support."
    },
    "2826": {
        "code": 2826,
        "desc": "Master server failed to connect to backup restore manager on media server for restore",
        "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost",
        "full_action": "Try the following possible solution in the order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ From each of the media servers, ping the master server by using the name that\nis specified in the NetBackup server list. On a UNIX or Linux server, this master\nis the first SERVER entry in the bp.conf file. On a Windows server, the master\nis designated on the Servers tab in the Master Server Properties dialog box.\n■ Check that all of the services are running on the media server."
    },
    "2827": {
        "code": 2827,
        "desc": "Client failed to connect to the media server for restore",
        "first_action": "Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost",
        "full_action": "Try the following possible solution in the order presented:\n■ Fromthemasterserver,pingthemasterandallmediaserversbyusingthehost\nnames in the storage unit configuration.\n■ Check that all services are running on the media server."
    },
    "2828": {
        "code": 2828,
        "desc": "Restore failed because the MS-SQL-Server services are down",
        "first_action": "Check that the SQL Server instance service is running",
        "full_action": "Check that the SQL Server instance service is running\nandthatNetBackupprocesseshavepermissiontoaccesstheSQLServerinstance\nservice."
    },
    "2829": {
        "code": 2829,
        "desc": "Restore failed due to MS-SQL-Server database in use NetBackup status codes 510 NetBackup status codes",
        "first_action": "After the database finishes its current operation, try to",
        "full_action": "After the database finishes its current operation, try to\nrestorethedatabase.Or,thedatabaseadministratorneedstocheckifthedatabase\nis busy and what operation it is performing."
    },
    "2830": {
        "code": 2830,
        "desc": "Restore failed due to an incorrect path in the MS-SQL-Server MOVE script",
        "first_action": "Check the MOVE script and correct the path that was",
        "full_action": "Check the MOVE script and correct the path that was\nspecified for the database log file for the keyword TO."
    },
    "2831": {
        "code": 2831,
        "desc": "Restore error",
        "first_action": "Ensure that the client server list contains entries for the master server and any",
        "full_action": "Trythefollowingpossiblesolutionsintheorderpresented:\n■ Ensure that the client server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Correct the problems that you find and retry the restore."
    },
    "2832": {
        "code": 2832,
        "desc": "Restore failed due to rename file format error NetBackup status codes 511 NetBackup status codes",
        "first_action": "If you want to execute the nbrestorevm command and",
        "full_action": "If you want to execute the nbrestorevm command and\nmanuallyentertherenamefile,verifythatthefilecomplieswiththeformatspecified\nin the NetBackup Commands Reference Guide. For additional information, check\nthe job details in the Activity Monitor and the bprd log on the master server."
    },
    "2833": {
        "code": 2833,
        "desc": "Restore failed due to partition restore error",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2834": {
        "code": 2834,
        "desc": "Restore failed due to failure to read change block bitmap",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2835": {
        "code": 2835,
        "desc": "Restore failed due to corrupt image",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2836": {
        "code": 2836,
        "desc": "Restore failed because the bitmap size read from the image header differs from the expected size.",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2837": {
        "code": 2837,
        "desc": "Restore failed due to invalid metadata",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2838": {
        "code": 2838,
        "desc": "Restore failed because no raw partitions were found",
        "first_action": "Verifythatthebackupimagecontainsalistofrawpartitions.",
        "full_action": "Verifythatthebackupimagecontainsalistofrawpartitions.\nThiserrormayindicatethatthebackupimageisdefective.Foradditionalinformation,\ncheck the job details in the Activity Monitor, the bprd log on the master server, and\nthe bptm log on the media server."
    },
    "2839": {
        "code": 2839,
        "desc": "Restore failed due to invalid raw partition ID",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2840": {
        "code": 2840,
        "desc": "Restore failed due to out of sequence raw partitions",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2841": {
        "code": 2841,
        "desc": "Restore failed due to failure to read the header from the backup image",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2842": {
        "code": 2842,
        "desc": "Restore failed due to failure to read the VMware bitmap",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2843": {
        "code": 2843,
        "desc": "Restore failed due to failure to start VxMS",
        "first_action": "Verify that the media server and the recovery host",
        "full_action": "Verify that the media server and the recovery host\nenvironment has adequate memory and correct file permissions. For additional\ninformation, check the job details in the Activity Monitor and the bprd log on the\nmaster server."
    },
    "2844": {
        "code": 2844,
        "desc": "Restore failed due to failure to read the FIID file",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2845": {
        "code": 2845,
        "desc": "Restore failed due to failure to retrieve the bitmap",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2846": {
        "code": 2846,
        "desc": "Restore failed due to failure to retrieve the fsmap",
        "first_action": "Ifanotherbackupcopyexists,makethatimagetheprimary",
        "full_action": "Ifanotherbackupcopyexists,makethatimagetheprimary\ncopy and attempt to restore from it. For additional information, check the job details\nin the Activity Monitor, the bprd log on the master server, and the bptm log on the\nmedia server."
    },
    "2847": {
        "code": 2847,
        "desc": "Restore failed due to failure to start the bptm writer",
        "first_action": "Verify that the media server and the recovery host",
        "full_action": "Verify that the media server and the recovery host\nenvironment has adequate memory and correct file permissions. For additional\ninformation, check the job details in the Activity Monitor and the bprd log on the\nmaster server."
    },
    "2848": {
        "code": 2848,
        "desc": "Restore failed due to failure to create the virtual machine",
        "first_action": "Check that the VMware server has sufficient permissions.",
        "full_action": "Do the following:\n■ Check that the VMware server has sufficient permissions.\n■ Increase the space available for the datastore.\n■ Resolve any configuration incompatibilities."
    },
    "2849": {
        "code": 2849,
        "desc": "Restore failed due to failure to delete the virtual machine snapshot",
        "first_action": "Check that the VMware server has sufficient permissions to delete a virtual",
        "full_action": "Do the following:\n■ Check that the VMware server has sufficient permissions to delete a virtual\nmachine snapshot.\n■ Increase the space available for the datastore.\n■ Error or task cancellation on the VMware server.\nFor additional information, check the job details in the Activity Monitor, the bprd log\non the master server, and the bptm log on the media server."
    },
    "2850": {
        "code": 2850,
        "desc": "Restore error",
        "first_action": "Ensure that the client-server list contains entries for the master server and any",
        "full_action": "Thisstatuscodecanappearformultipleworkloads.Please\nreview the following information for your particular workload.\nFor general troubleshooting, try the following possible solutions in the order\npresented:\n■ Ensure that the client-server list contains entries for the master server and any\nmedia servers that can be used during a backup or restore.\n■ Examine the status or the progress log on the client for messages on why the\nrestore failed. Also, check the All Log Entries report on the server.\n■ Check ownership and permission on directories where files are restored.\n■ Correct the problems that you find and retry the restore.\nIn the case of Hadoop and HBase:\n■ Thiserrorisencounteredwhenanimportofanimageisusedtocreateacatalog\nentry and then afterwards a restore is triggered. To troubleshoot this error, refer\nto the following procedure:\nTo troubleshoot the restore failure:\n1 Create a rename file with the ALT_APPLICATION_SERVER as the application\nserver name. Provide the primary name node only (instead of alternate name\nnode). Ensure that the credentials for primary name node are already present.\n2 Perform the restore using the bprestore command.\nIn the case of Azure Stack and OpenStack:\n■ If the error occurs for an AIR restore scenario, restore the catalog before you\nrestore the AIR images.\nIn the case of Hadoop with Kerberos:\n■ ThisissuearisesiftheHDFSownerdoesnotsetownershipforfilesanddirectories\nor if there are issues with Kerberos configuration. Before restoring, ensure the\nfollowing:\n■ Ensure that the HDFS owner user is used for Kerberos backup.\n■ Ensure that with the current Kerberos user, it is possible to set the\nowners/ACLSmanuallyusingHDFScommands,suchaschownandsetfacl."
    },
    "2864": {
        "code": 2864,
        "desc": "The disaster recovery package could not be imported.",
        "first_action": "Ensure that you are using the disaster recovery package",
        "full_action": "Ensure that you are using the disaster recovery package\nthat was emailed to you or a copy of the same package."
    },
    "2865": {
        "code": 2865,
        "desc": "The database table could not be loaded.",
        "first_action": "On UNIX: /usr/openv/db/bin/nbdb_ping",
        "full_action": "Ensure that the NetBackup database is accessible while\nthe NetBackup database process is running. Use the following command to check\nif the database is accessible:\n■ On UNIX: /usr/openv/db/bin/nbdb_ping\n■ On Windows: install_path\\NetBackup\\bin\\nbdb_ping"
    },
    "2866": {
        "code": 2866,
        "desc": "The specified passphrase is incorrect.",
        "first_action": "Ensure that the specified passphrase is the same as the",
        "full_action": "Ensure that the specified passphrase is the same as the\nonethatyousetatthetimeofthecatalogbackupthatisassociatedwiththisdisaster\nrecovery package."
    },
    "2869": {
        "code": 2869,
        "desc": "The identity package is corrupt. NetBackup status codes 519 NetBackup status codes",
        "first_action": "Use a different DR identity package or use the steps that",
        "full_action": "Use a different DR identity package or use the steps that\nare available in the following article:\nhttps://www.veritas.com/support/en_US/article.000125933"
    },
    "2870": {
        "code": 2870,
        "desc": "The master server certificate cannot be imported from the DR package to Windows certificate store.",
        "first_action": "PFX file path for the alternate directory import :",
        "full_action": "Try to restore the disaster recovery (DR) package to an\nalternate directory location and manually import the PFX files into the Windows\ncertificate store. You can manually import the files by double-clicking the PFX files\nin the following locations:\n■ PFX file path for the alternate directory import :\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\*.pfx\n■ File path of the PFX file’s password:\n■ alternate_directory\\directory_name\\usr\\openv\\netbackup\\tmp\\tempWinCredStore\\pfxPwdFile.txt"
    },
    "2877": {
        "code": 2877,
        "desc": "Hypervisor pre-restore operation failed.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "2880": {
        "code": 2880,
        "desc": "The recovery host in the restore specification does not support in-place virtual machine disk restores. NetBackup status codes 520 NetBackup status codes",
        "first_action": "To perform an in-place disk restore, specify a recovery",
        "full_action": "To perform an in-place disk restore, specify a recovery\nhost with NetBackup version 8.3 or later."
    },
    "2881": {
        "code": 2881,
        "desc": "Failed to query the data specific to disaster recovery package.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "2882": {
        "code": 2882,
        "desc": "Thespecifieddisasterrecoverypackageisbeingrestoredonahostwith a name that is different from the one where the package was created.",
        "first_action": "Ensurethatthehostnamesmatchincaseofbothbackup",
        "full_action": "Ensurethatthehostnamesmatchincaseofbothbackup\nand restore of the disaster recovery package."
    },
    "2883": {
        "code": 2883,
        "desc": "One or more users who have permissions to the identity files that need to be backed up as part of the DR package do not exist on the system.",
        "first_action": "Either map the non-existing users to the appropriate users on the host or skip",
        "full_action": "Perform the following as appropriate:\n■ Either map the non-existing users to the appropriate users on the host or skip\nthem while retrying.\n■ If you install NetBackup in a disaster recovery mode, set the DR_PKG_MAPUSER\nenvironment variable with the mapping.\n■ Use the -mapuser option to provide the mapping or skipping the ACLs of user.\nRefer to the NetBackup Commands Reference Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support site\noffers additional information to help you troubleshoot this issue."
    },
    "2887": {
        "code": 2887,
        "desc": "Import of VM to vApp failed.",
        "first_action": "Ensure that the maximum number of VMs has not been exceeded.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the maximum number of VMs has not been exceeded.\n■ Ensure that there is enough allocated storage."
    },
    "2888": {
        "code": 2888,
        "desc": "VM has been left at vCenter after import failure.",
        "first_action": "The VM needs to be deleted or imported manually.",
        "full_action": "Perform the following as appropriate:\n■ The VM needs to be deleted or imported manually.\n■ Ensure that the maximum number of VMs has not been exceeded.\n■ Ensure that there is enough allocated storage.\n■ NetBackup can automatically delete a VM on import failure. To enable this\noption, set DELETE_VM_ON_IMPORT_FAILURE = 1 in the bp.conf file or in the\nregistry on the master server."
    },
    "2889": {
        "code": 2889,
        "desc": "Kubernetes pre-restore operation failed.",
        "first_action": "Check if the data mover image is properly set in the data mover ConfigMap and",
        "full_action": "Perform the following as appropriate:\n■ Check if the data mover image is properly set in the data mover ConfigMap and\nthe user have access to pull the image from the repository.\n■ Ensure that the storage classes have the required NetBackup labels.\n■ Ensure that there are enough resources on the cluster for spawning pods.\n■ Check NetBackup Kubernetes operator logs to know more details about the\nerror."
    },
    "2890": {
        "code": 2890,
        "desc": "Kubernetes restore data operation failed.",
        "first_action": "Ensure that the data mover is running properly.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the data mover is running properly.\n■ Ensure that the media server is reachable from the data mover pod.\n■ Ensure that the host aliases are present in the data mover ConfigMap if short\nnames are in use.\n■ Ensure that the backupservercert is configured in a correct manner on the\nKubernetes operator cluster."
    },
    "2891": {
        "code": 2891,
        "desc": "Kubernetes post-restore operation failed.",
        "first_action": "To restore a PVC to the original namespace, ensure that the PVC is not present",
        "full_action": "Perform the following as appropriate:\n■ To restore a PVC to the original namespace, ensure that the PVC is not present\nin the original namespace before you start a restore operation.\n■ Review the NetBackup Kubernetes operator logs to get more details about the\nerror."
    },
    "2892": {
        "code": 2892,
        "desc": "Kubernetes restore from backup operation failed.",
        "first_action": "Ensure that the namespace has the NetBackup supported resources.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the namespace has the NetBackup supported resources.\n■ Check Kubernetes operator logs for more details about the error."
    },
    "2893": {
        "code": 2893,
        "desc": "NetBackup FIPS mode is enabled and the specified disaster recovery package was created on a host where FIPS mode was disabled.",
        "first_action": "If you import a disaster recovery package from a system",
        "full_action": "If you import a disaster recovery package from a system\nwhere FIPS was disabled, then disable FIPS on the current NetBackup system.\nThen you can try to import the disaster recovery package.\nFor more information about disabling FIPS in NetBackup, refer to the NetBackup\nSecurity and Encryption Guide."
    },
    "2894": {
        "code": 2894,
        "desc": "Failed to create the instant access mount for cloud backup image.",
        "first_action": "Reduce the number of instant access mounts and retry",
        "full_action": "Reduce the number of instant access mounts and retry\nthe operation."
    },
    "2897": {
        "code": 2897,
        "desc": "Instant access mount point already exists.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on the master server."
    },
    "3000": {
        "code": 3000,
        "desc": "TousetheAllowdynamicmulti-streamingoption,theVSOFIMshould be selected in snapshot options.",
        "first_action": "Update the policy configuration to select the VSO as",
        "full_action": "Update the policy configuration to select the VSO as\nsnapshot method."
    },
    "3002": {
        "code": 3002,
        "desc": "Clienttimed-outwaitingfor filesystem crawler to populatethe filelist in the shared memory.",
        "first_action": "Ensure network connectivity between the backup host",
        "full_action": "Ensure network connectivity between the backup host\nand volume is consistent. Resume or restart the policy backup."
    },
    "3003": {
        "code": 3003,
        "desc": "The file system crawler process timed-out waiting for streams to attach with shared memory. NetBackup status codes 525 NetBackup status codes",
        "first_action": "Ensure that network connectivity of the backup host is",
        "full_action": "Ensure that network connectivity of the backup host is\nconsistent."
    },
    "3004": {
        "code": 3004,
        "desc": "Theoff-hostbackupfortheNAS-Data-Protectionpolicywasnotselected.",
        "first_action": "Configure the policy to enable the off-host backup and",
        "full_action": "Configure the policy to enable the off-host backup and\nselect a backup host pool."
    },
    "3005": {
        "code": 3005,
        "desc": "InstantRecoverysnapshotonlyoptionisnotsupportedifthecheckpoint option is selected.",
        "first_action": "Change the policy type to Storage Lifecycle Policies.",
        "full_action": "Change the policy type to Storage Lifecycle Policies."
    },
    "3006": {
        "code": 3006,
        "desc": "For NAS-Data-Protection policy, the policy storage must be Storage Lifecycle Policies or select the Override policy storage selection option while schedules are configured.",
        "first_action": "Change the policy type to Storage Lifecycle Policies.",
        "full_action": "Change the policy type to Storage Lifecycle Policies."
    },
    "3007": {
        "code": 3007,
        "desc": "For NAS-Data-Protection policy, the destination client cannot be used to restore.",
        "first_action": "SelectasourceclientasaNASarrayheadanddestination",
        "full_action": "SelectasourceclientasaNASarrayheadanddestination\nclient as backup host to mount the volume or the share."
    },
    "3008": {
        "code": 3008,
        "desc": "Failed to get required value from MediaDescription.",
        "first_action": "Ensure that connectivity to master server is consistent to",
        "full_action": "Ensure that connectivity to master server is consistent to\navoid partial retrieval of image data."
    },
    "3009": {
        "code": 3009,
        "desc": "For NAS-Data-Protection policy, the value of the Maximum jobs per policyattributemustbegreaterthantheMaximumnumberofstreamspervolume attribute",
        "first_action": "Update the values of Maximum jobs per policy in the",
        "full_action": "Update the values of Maximum jobs per policy in the\nhost properties to accommodate selected streams."
    },
    "3010": {
        "code": 3010,
        "desc": "For NAS-Data-Protection policy, the off-host backup and use backup host pool options must be selected.",
        "first_action": "Configure the policy to enable off-host backup and then",
        "full_action": "Configure the policy to enable off-host backup and then\nselect the backup host pool."
    },
    "3011": {
        "code": 3011,
        "desc": "For NAS-Data-Protection policy, a backup host pool name must be configured in the policy.",
        "first_action": "Configure the NAS-Data-Protection policy to enable",
        "full_action": "Configure the NAS-Data-Protection policy to enable\noff-host backup and select the backup host pool."
    },
    "3012": {
        "code": 3012,
        "desc": "Failed to get local host name.",
        "first_action": "Ensure all NetBackup services are up and running on the",
        "full_action": "Ensure all NetBackup services are up and running on the\nbackup host."
    },
    "3013": {
        "code": 3013,
        "desc": "The SnapshotonlySLPis not supportedfor the NAS-Data-Protection policy.",
        "first_action": "Configure the Backup From Snapshot to existing SLP",
        "full_action": "Configure the Backup From Snapshot to existing SLP\nas a second operation."
    },
    "3014": {
        "code": 3014,
        "desc": "Failed to generate vendor change tracking information.",
        "first_action": "Retry the operation. If the issue persists, review the",
        "full_action": "Retry the operation. If the issue persists, review the\nflexsnap logs."
    },
    "3016": {
        "code": 3016,
        "desc": "Failed to fetch the vendor change tracking task details.",
        "first_action": "Ensure that the Snapshot Manager services are up and",
        "full_action": "Ensure that the Snapshot Manager services are up and\nrunning."
    },
    "3017": {
        "code": 3017,
        "desc": "Failed to get snapshot diff.",
        "first_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap",
        "full_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap\nlogs."
    },
    "3018": {
        "code": 3018,
        "desc": "Snapshot does not support diff capability.",
        "first_action": "Clear the Enable vendor change tracking for",
        "full_action": "Clear the Enable vendor change tracking for\nincremental backups check box in the policy configuration."
    },
    "3019": {
        "code": 3019,
        "desc": "Base snapshot ID is unknown to get diff.",
        "first_action": "Update the policy schedule to create full backup first and then create an",
        "full_action": "Perform the following, as appropriate:\n■ Update the policy schedule to create full backup first and then create an\nincremental backup.\n■ When a new NAS volume is added or discovered in the NAS-Data-Protection\npolicy, perform a backup using the full schedule.\n■ Adjustthesnapshotcopyretentionsettingtoensurethatthesnapshotisavailable\nwhen an incremental backup starts."
    },
    "3021": {
        "code": 3021,
        "desc": "Failed to get all snapshot diffs.",
        "first_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap",
        "full_action": "Retrytheoperation.Iftheissuepersists,refertoflexsnap\nlogs."
    },
    "3022": {
        "code": 3022,
        "desc": "Failed to parse the response of the create vendor change tracking information.",
        "first_action": "Refer the NetBackup Compatibility List to verify that the",
        "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported."
    },
    "3023": {
        "code": 3023,
        "desc": "Failed to parse the response of the get vendor change tracking information. NetBackup status codes 530 NetBackup status codes",
        "first_action": "Refer the NetBackup Compatibility List to verify that the",
        "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported."
    },
    "3024": {
        "code": 3024,
        "desc": "Failed to parse the response of get all snapshot diffs.",
        "first_action": "Refer the NetBackup Compatibility List to verify that the",
        "full_action": "Refer the NetBackup Compatibility List to verify that the\ninstalled version of Snapshot Manager is supported."
    },
    "3025": {
        "code": 3025,
        "desc": "Failed to find the existing diff for given snapshots.",
        "first_action": "Update the policy schedule to create a full backup first.",
        "full_action": "Update the policy schedule to create a full backup first."
    },
    "3026": {
        "code": 3026,
        "desc": "For the NAS-Data-Protection policy, the snapshot method argument max_snapshots is not supported.",
        "first_action": "Configure the snapshot arguments and add the",
        "full_action": "Configure the snapshot arguments and add the\nconfigurations again to the policy."
    },
    "3027": {
        "code": 3027,
        "desc": "For the NAS-Data-Protection policy, the Maximum snapshot limit retention option is not supported in SLP.",
        "first_action": "Configure time-based retention or expire after copy",
        "full_action": "Configure time-based retention or expire after copy\nretention in the SLP."
    },
    "3028": {
        "code": 3028,
        "desc": "For the NAS-Data-Protection policy, if the Enable vendor change tracking for incremental backup option is enabled, the Expire after copy option retention is not supported.",
        "first_action": "Update the SLP to set time-based retention.",
        "full_action": "Update the SLP to set time-based retention."
    },
    "3030": {
        "code": 3030,
        "desc": "Failedtocreateacheckpointdirectoryfordynamicdatastreambackups.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3031": {
        "code": 3031,
        "desc": "Failed to create a checkpoint file for saving the shared memory state.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3032": {
        "code": 3032,
        "desc": "Failed to save shared memory state in checkpoint file.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3033": {
        "code": 3033,
        "desc": "Failedtorenametemporarycheckpointfile.Resumeoperationforcurrent job might not be able to use checkpoint information.",
        "first_action": "Ensure that connectivity to backup host is consistent and",
        "full_action": "Ensure that connectivity to backup host is consistent and\nNetBackup services are up and running."
    },
    "3034": {
        "code": 3034,
        "desc": "Failed to access checkpoint directory. Resume operation for the current job commences from the start.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3035": {
        "code": 3035,
        "desc": "Failedtoreaddatafromcheckpointfile.Resumeoperationforthecurrent job commences from the start.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3036": {
        "code": 3036,
        "desc": "Failed to fetch the checkpoint file for reading the shared memory state from master server.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3037": {
        "code": 3037,
        "desc": "Failedtopushcheckpointfiletostoresharedmemorystatefiletomaster server.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3041": {
        "code": 3041,
        "desc": "Failed to get shared memory identifier.",
        "first_action": "Ensurethatenoughmemoryisavailabletocreateashared",
        "full_action": "Ensurethatenoughmemoryisavailabletocreateashared\nmemory on the backup host."
    },
    "3042": {
        "code": 3042,
        "desc": "Failed to attach with shared memory identifier.",
        "first_action": "Retry the backup operation.",
        "full_action": "Retry the backup operation."
    },
    "3043": {
        "code": 3043,
        "desc": "Failedtocreatesharedmemoryconfigurationdirectoryfordynamicdata stream backups.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3044": {
        "code": 3044,
        "desc": "Failed to open shared memory configuration file.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3045": {
        "code": 3045,
        "desc": "Failed to save shared memory information in configuration file.",
        "first_action": "Ensure that connectivity to the backup host is consistent",
        "full_action": "Ensure that connectivity to the backup host is consistent\nand NetBackup services are up and running."
    },
    "3047": {
        "code": 3047,
        "desc": "For NAS-Data-Protection policy, storage unit disk type should be AdvancedDisk or PureDisk.",
        "first_action": "Ensure that the destination storage in storage lifecycle",
        "full_action": "Ensure that the destination storage in storage lifecycle\npolicy is AdvancedDisk, PureDisk, or a storage unit group of these disk types."
    },
    "3049": {
        "code": 3049,
        "desc": "Vendor change tracking enabled backups are not supported for NetApp storage array.",
        "first_action": "Ensure the Vendor Change Tracking (VCT) check box is cleared in the policy or",
        "full_action": "Perform the following as appropriate:\nEnsure the Vendor Change Tracking (VCT) check box is cleared in the policy or\nthat the backup from snapshot operation is removed from SLP when you perform\na backup of NetApp array volume."
    },
    "3050": {
        "code": 3050,
        "desc": "The vendor change tracking enabled index from a snapshot job has failed to synthesize the catalog.",
        "first_action": "Disable VCT in the policy and run the index from snapshot job with full schedule.",
        "full_action": "Perform the following as appropriate:\nDisable VCT in the policy and run the index from snapshot job with full schedule."
    },
    "3052": {
        "code": 3052,
        "desc": "Unable to retrieve the NetBackup version for the host.",
        "first_action": "Ensure that you have selected the correct destination",
        "full_action": "Ensure that you have selected the correct destination\nserver and the primary server services are up and running."
    },
    "3053": {
        "code": 3053,
        "desc": "ThemounthostmustbeatNetBackupversion10.5orgreatertosupport Parallel Restore using Snapshot Copy.",
        "first_action": "Use a single stream to restore the data from the snapshot or the replica copy.",
        "full_action": "Perform the following as appropriate:\n■ Use a single stream to restore the data from the snapshot or the replica copy.\n■ To perform a restore with parallel streams, upgrade the existing mount host to\nNetBackup version 10.5 or higher. Your mount host is the backup host that you\nuse to perform the snapshot operation."
    },
    "3054": {
        "code": 3054,
        "desc": "The destination client must be at NetBackup version 10.5 or greater to support Parallel Restore using Snapshot Copy.",
        "first_action": "Use a single stream to restore the data from the snapshot or the replica copy.",
        "full_action": "Perform the following as appropriate:\n■ Use a single stream to restore the data from the snapshot or the replica copy.\n■ To perform a restore with parallel streams, upgrade the existing destination\nclient to NetBackup version 10.5 or higher."
    },
    "3200": {
        "code": 3200,
        "desc": "A file was skipped because it was in the process of being backed up.",
        "first_action": "Ensure that the backup file is not in use and is ready for",
        "full_action": "Ensure that the backup file is not in use and is ready for\nbackup. Also, you can verify that the file is in the process of being backed up."
    },
    "3201": {
        "code": 3201,
        "desc": "Cassandra version is not supported.",
        "first_action": "Verify if NetBackup supports the installed Cassandra",
        "full_action": "Verify if NetBackup supports the installed Cassandra\nversion by reviewing the following:\nNetBackup Compatibility List for all Versions"
    },
    "3202": {
        "code": 3202,
        "desc": "The OS platform version is not supported.",
        "first_action": "Verify if NetBackup supports the OS platform versions for",
        "full_action": "Verify if NetBackup supports the OS platform versions for\nthe Cassandra clusters by reviewing the following:\nNetBackup Compatibility List for all Versions"
    },
    "3203": {
        "code": 3203,
        "desc": "The CBR node hash in the tpconfig command and Cassandra configuration does not match.",
        "first_action": "Verify that the CBR node hash in both the Cassandra",
        "full_action": "Verify that the CBR node hash in both the Cassandra\nconfiguration file and the tpconfig command match."
    },
    "3204": {
        "code": 3204,
        "desc": "Data Staging Server node parameters are not specified.",
        "first_action": "Verify that the Data Staging Server node entries are",
        "full_action": "Verify that the Data Staging Server node entries are\navailable in the Cassandra configuration file."
    },
    "3205": {
        "code": 3205,
        "desc": "The username of the Data Staging Server node is not specified for the Secure Shell connection.",
        "first_action": "Verify that the username of the Data Staging Server node",
        "full_action": "Verify that the username of the Data Staging Server node\nis specified in the tpconfig command."
    },
    "3206": {
        "code": 3206,
        "desc": "DataStagingServernodepasswordisnotspecifiedfortheSecureShell connection.",
        "first_action": "Verify if the password of the Data Staging Server node is",
        "full_action": "Verify if the password of the Data Staging Server node is\nspecified in the tpconfig command."
    },
    "3207": {
        "code": 3207,
        "desc": "Data folder is not specified in the configuration for Data Staging Server node. NetBackup status codes 539 NetBackup status codes",
        "first_action": "Ensure that the Cassandra Data folder is specified in the",
        "full_action": "Ensure that the Cassandra Data folder is specified in the\nCassandra configuration file for the Data Staging Server node."
    },
    "3208": {
        "code": 3208,
        "desc": "Data Staging Server node keyhashes are not specified.",
        "first_action": "Verify that the Data Staging Server node keyhashes are",
        "full_action": "Verify that the Data Staging Server node keyhashes are\nspecified in the Cassandra configuration file."
    },
    "3209": {
        "code": 3209,
        "desc": "TheusernameofDataStagingServerCassandraclusterisnotspecified.",
        "first_action": "Verify that the username of the Data Staging Server",
        "full_action": "Verify that the username of the Data Staging Server\nCassandra cluster is specified in the tpconfig command."
    },
    "3210": {
        "code": 3210,
        "desc": "DataStagingServerpasswordfortheCassandraclusterisnotspecified.",
        "first_action": "Verify that the password of the Data Staging Server for",
        "full_action": "Verify that the password of the Data Staging Server for\nthe Cassandra cluster is mentioned in tpconfig command."
    },
    "3211": {
        "code": 3211,
        "desc": "Cassandra cluster name of Data Staging Server node is not specified.",
        "first_action": "VerifythattheCassandraclusternameoftheDataStaging",
        "full_action": "VerifythattheCassandraclusternameoftheDataStaging\nServer node is specified in the tpconfig command."
    },
    "3212": {
        "code": 3212,
        "desc": "Snapshot name is not specified.",
        "first_action": "Review the nbaapidiscv log or the nbaapireq_handler",
        "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details."
    },
    "3213": {
        "code": 3213,
        "desc": "Backup type is not specified.",
        "first_action": "Review the nbaapidiscv log or the nbaapireq_handler",
        "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details."
    },
    "3214": {
        "code": 3214,
        "desc": "Backup file name is not specified.",
        "first_action": "Review the nbaapidiscv log or the nbaapireq_handler",
        "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details."
    },
    "3215": {
        "code": 3215,
        "desc": "Controller ID is not specified.",
        "first_action": "Review the nbaapidiscv log or the nbaapireq_handler",
        "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details."
    },
    "3216": {
        "code": 3216,
        "desc": "Controller ID of the claim command did not match with controller ID of the upload done command.",
        "first_action": "Review the nbaapidiscv log or the nbaapireq_handler",
        "full_action": "Review the nbaapidiscv log or the nbaapireq_handler\nlog for more details."
    },
    "3217": {
        "code": 3217,
        "desc": "CBR node is not specified in configuration settings.",
        "first_action": "Verify that the CBR node is specified in the Cassandra",
        "full_action": "Verify that the CBR node is specified in the Cassandra\nconfiguration file."
    },
    "3218": {
        "code": 3218,
        "desc": "Failed to create the directory.",
        "first_action": "VerifyallnodesinboththeDatastagingserverCassandra",
        "full_action": "VerifyallnodesinboththeDatastagingserverCassandra\ncluster and Production Cassandra cluster are reachable. Also, verify that the user\nhas the correct access permissions to create the directories that are specified in\nthe Cassandra configuration file.\nReview the nbaapidiscv log or the nbaapireq_handler log for more details."
    },
    "3219": {
        "code": 3219,
        "desc": "Error occurred when the file was copied.",
        "first_action": "Verify that the user has proper access permissions for",
        "full_action": "Verify that the user has proper access permissions for\nboth the file and the destination path. Review the nbaapidiscv log or\nnbaapireq_handler log for more details."
    },
    "3220": {
        "code": 3220,
        "desc": "Failed to delete the data directory.",
        "first_action": "Verifyiftheuserhascorrectaccesspermissionstodelete",
        "full_action": "Verifyiftheuserhascorrectaccesspermissionstodelete\nthedatadirectory.Reviewthenbaapidiscvlogornbaapireq_handlerlogformore\ndetails."
    },
    "3221": {
        "code": 3221,
        "desc": "ProductionCassandraclusterpasswordisnotspecifiedinthecommand.",
        "first_action": "Verify that the Production Cassandra cluster password is",
        "full_action": "Verify that the Production Cassandra cluster password is\nspecified in the tpconfig command."
    },
    "3222": {
        "code": 3222,
        "desc": "ProductionCassandraclusterusernameisnotspecifiedinthecommand. NetBackup status codes 543 NetBackup status codes",
        "first_action": "Verify if the Production Cassandra cluster username is",
        "full_action": "Verify if the Production Cassandra cluster username is\nspecified in the tpconfig command."
    },
    "3223": {
        "code": 3223,
        "desc": "Security mode is not specified.",
        "first_action": "Verify that a valid Security mode is specified in the",
        "full_action": "Verify that a valid Security mode is specified in the\nCassandra configuration file."
    },
    "3224": {
        "code": 3224,
        "desc": "Unable to open the progress file to read.",
        "first_action": "Verify that the user access permissions are correct for",
        "full_action": "Verify that the user access permissions are correct for\nthe progress file. Refer to the nbaapidiscv log or the nbaapireq_handler log for\nmore details."
    },
    "3225": {
        "code": 3225,
        "desc": "No data was found to copy.",
        "first_action": "Verify that a valid path is specified for the Data Staging",
        "full_action": "Verify that a valid path is specified for the Data Staging\nServer in the Cassandra configuration file."
    },
    "3232": {
        "code": 3232,
        "desc": "Data directory storage of Data Staging Server does not have enough storage.",
        "first_action": "Verify that the data directory of the Data Staging Server has enough storage",
        "full_action": "Perform the following as appropriate:\n■ Verify that the data directory of the Data Staging Server has enough storage\nspace and does not contain any contents of previous jobs.\n■ Verify that the Cassandra data directory of the Data Staging Server does not\ncontain contents of previous jobs.\n■ Ensure that the ScriptHome directory of the Data Staging Server has enough\nstorage space to perform the restore operation.\n■ Verify that the ScriptHome directory, which is specified in the Cassandra\nconfiguration file, is present on Data Staging Server. If the file is not present,\ncreate the ScriptHome directory on Data Staging Server and retry the restore\noperation."
    },
    "3234": {
        "code": 3234,
        "desc": "Parse error.",
        "first_action": "Verify that all the parameters and attributes that are",
        "full_action": "Verify that all the parameters and attributes that are\nmentioned in cassandra.conf are correct."
    },
    "3235": {
        "code": 3235,
        "desc": "Down node’s threshold value exceeds permissible limit.",
        "first_action": "Turnuptheproductionnodesorincreasethedownnodes",
        "full_action": "Turnuptheproductionnodesorincreasethedownnodes\nthreshold value to match the percentage of nodes that are down."
    },
    "3236": {
        "code": 3236,
        "desc": "JSON format is not valid.",
        "first_action": "Verify that all the parameters and attributes that are contained in the",
        "full_action": "Perform the following as appropriate:\n■ Verify that all the parameters and attributes that are contained in the\ncassandra.conf file are correct.\n■ Verify that the cassandra.conf file format is in a valid JSON format."
    },
    "3245": {
        "code": 3245,
        "desc": "Failed to get Production Cassandra cluster IP addresses.",
        "first_action": "Fortheprovidedclustername,verifythattheclusternodes",
        "full_action": "Fortheprovidedclustername,verifythattheclusternodes\nare up and running."
    },
    "3246": {
        "code": 3246,
        "desc": "An exception has occurred during Production Cassandra cluster validation.",
        "first_action": "For the provided cluster name, verify that the cluster nodes are up and running.",
        "full_action": "Perform the following as appropriate:\n■ For the provided cluster name, verify that the cluster nodes are up and running.\n■ Verify that the nodes are accessible from the CBR nodes.\n■ Verify that the production cluster has a supported Cassandra version.\n■ VerifythattheproductionclusternodesaredeployedonasupportedOSplatform."
    },
    "3251": {
        "code": 3251,
        "desc": "ProductionCassandraclusternamedidnotmatchwiththeconfiguration settings.",
        "first_action": "Verify that the Cassandra cluster name that is in the",
        "full_action": "Verify that the Cassandra cluster name that is in the\ncassandra.yaml file is correct on the production node."
    },
    "3252": {
        "code": 3252,
        "desc": "Failed to run Cassandra Query Language Shell command.",
        "first_action": "Verify the Cassandra Username and Password that are provided in the",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password that are provided in the\napplication configuration file for the specified Cassandra cluster and its\nassociated entries are correct.\n■ Verify the Cassandra node status. All nodes on the data staging server and the\nproduction cluster should be up and running.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3253": {
        "code": 3253,
        "desc": "No valid nodes were found for restore.",
        "first_action": "Verify that the production cluster node or nodes are up",
        "full_action": "Verify that the production cluster node or nodes are up\nand running."
    },
    "3254": {
        "code": 3254,
        "desc": "Failed to start Cassandra service.",
        "first_action": "Verify that the Cassandra cluster node status is up and in a normal state.",
        "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster node status is up and in a normal state.\n■ Verify that the node Username or Password details in the cassandra.yaml file\nare correct.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3255": {
        "code": 3255,
        "desc": "Failed to stop Cassandra service.",
        "first_action": "Verify that the Cassandra cluster node status is up and in a normal state.",
        "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster node status is up and in a normal state.\n■ Verify that the node Username or Password details in the cassandra.yaml file\nare correct.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3256": {
        "code": 3256,
        "desc": "Failed to start Cassandra server.",
        "first_action": "Verify that the nodes in the Cassandra cluster are up and",
        "full_action": "Verify that the nodes in the Cassandra cluster are up and\nin a normal state. Also, verify that the firewall settings on the cluster nodes are\ncorrect. Port 7000/9042 should be open."
    },
    "3257": {
        "code": 3257,
        "desc": "Failed to stop Cassandra server.",
        "first_action": "Verify that the nodes in the Cassandra cluster are up and",
        "full_action": "Verify that the nodes in the Cassandra cluster are up and\nin a normal state. Also, verify that the firewall settings on the cluster nodes are\ncorrect. Port 7000/9042 should be open."
    },
    "3258": {
        "code": 3258,
        "desc": "Failed to set Cassandra yaml file on Data Staging server cluster.",
        "first_action": "Verify if the data staging server node or nodes are up and",
        "full_action": "Verify if the data staging server node or nodes are up and\nrunning."
    },
    "3259": {
        "code": 3259,
        "desc": "An exception has occurred while Cassandra schema was fetched.",
        "first_action": "Verify that the Cassandra Username and Password on the production cluster",
        "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra Username and Password on the production cluster\nare correct.\n■ Verify that the cluster node where the schema resides from is up and running.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3260": {
        "code": 3260,
        "desc": "Unable to fetch database schema.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3261": {
        "code": 3261,
        "desc": "Failed to run Cassandra Query Language query on the cluster.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3262": {
        "code": 3262,
        "desc": "No table schema found.",
        "first_action": "Verify that no column family or table is identified as part",
        "full_action": "Verify that no column family or table is identified as part\nof the keyspace."
    },
    "3263": {
        "code": 3263,
        "desc": "Failed to create keyspaces.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3264": {
        "code": 3264,
        "desc": "Failed to create tables.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3265": {
        "code": 3265,
        "desc": "Failed to alter tables.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3266": {
        "code": 3266,
        "desc": "Cassandra Query Language command is empty.",
        "first_action": "Reviewthenbaapidiscvorthenbaapireq_handlerlogs",
        "full_action": "Reviewthenbaapidiscvorthenbaapireq_handlerlogs\nfor more detail about the failure."
    },
    "3267": {
        "code": 3267,
        "desc": "Failed to drop keyspaces. NetBackup status codes 553 NetBackup status codes",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3268": {
        "code": 3268,
        "desc": "Unable to fetch the datacenter from the Cassandra cluster.",
        "first_action": "Verify that the correct data center entry is in the cassandra.conf in the",
        "full_action": "Perform the following as appropriate:\n■ Verify that the correct data center entry is in the cassandra.conf in the\nproduction cluster.\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3269": {
        "code": 3269,
        "desc": "An exception has occurred when an attempt was made to fetch the datacenter.",
        "first_action": "Review the Detailed status in the Activity monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity monitor.\n■ Review the nbaapidiscv log or the nbaapireq_handler log for more detail."
    },
    "3270": {
        "code": 3270,
        "desc": "Unable to fetch the datacenter for a node.",
        "first_action": "Verify that the datacenter settings in the application",
        "full_action": "Verify that the datacenter settings in the application\nconfiguration file for the specified Cassandra cluster and its associated entries are\ncorrect.Also,verifythatthefirewallsettingsontheclusternodesarecorrectbecause\nport 7000/9042 should be open."
    },
    "3271": {
        "code": 3271,
        "desc": "Failed to set up backup Cassandra cluster.",
        "first_action": "Verify the Cassandra Username and Password on the production cluster are",
        "full_action": "Perform the following as appropriate:\n■ Verify the Cassandra Username and Password on the production cluster are\ncorrect.\n■ Verify that the node status of Cassandra cluster is up and in a normal state.\n■ Verify that the firewall settings on the cluster nodes are correct. Port 7000/9042\nshould be open."
    },
    "3272": {
        "code": 3272,
        "desc": "No keyspace found for Cassandra cluster backup.",
        "first_action": "Use cqlsh to access the production node and verify that",
        "full_action": "Use cqlsh to access the production node and verify that\none non-empty keyspace is present in the cluster."
    },
    "3273": {
        "code": 3273,
        "desc": "Job cleanup time-out is not valid.",
        "first_action": "An integer",
        "full_action": "Verify that the value of the jobCleanupTimeoutSec in\ncassandra.conf file is:\n■ An integer\n■ Greater than zero"
    },
    "3274": {
        "code": 3274,
        "desc": "Failed to prepare backup.",
        "first_action": "Review the Detailed status in the Activity Monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv log or the nbaapireq_handler log for more detail."
    },
    "3275": {
        "code": 3275,
        "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection consists of full backup images from multiple image groups.",
        "first_action": "Verifythattheimagegroupthatisprovidedinthebprestorecommandiscorrect.",
        "full_action": "Perform the following as appropriate:\n■ Verifythattheimagegroupthatisprovidedinthebprestorecommandiscorrect.\n■ Verifythatthestartandtheendtimethatisprovidedinthebprestorecommand\nis correct."
    },
    "3276": {
        "code": 3276,
        "desc": "BigDatabackupimagegroupvalidationhasfailedasthespecifiedimage selection does not contain all backup images from the image group. NetBackup status codes 557 NetBackup status codes",
        "first_action": "Verify that an image group is provided to the bprestore command and verify",
        "full_action": "Perform the following as appropriate:\n■ Verify that an image group is provided to the bprestore command and verify\nthat it is the correct image group.\n■ Review the start and the end time that the bprestore command returns and\nverify that they are correct."
    },
    "3277": {
        "code": 3277,
        "desc": "Failed to delete stale database schema.",
        "first_action": "Clear the contents in the data directory of the DSS nodes",
        "full_action": "Clear the contents in the data directory of the DSS nodes\nand try to run the job again."
    },
    "3280": {
        "code": 3280,
        "desc": "Data Staging Server nodes do not have enough space.",
        "first_action": "Verify that the Data Staging Server node has sufficient",
        "full_action": "Verify that the Data Staging Server node has sufficient\nspace."
    },
    "3281": {
        "code": 3281,
        "desc": "Failed to disassemble the Data Staging Server cluster.",
        "first_action": "1. Stop the Cassandra service on all DSS nodes.",
        "full_action": "Perform the following procedure:\n1. Stop the Cassandra service on all DSS nodes.\n2. Change the seed node IP address in the Cassandra yaml file of all DSS nodes\nto their respective IP addresses.\n3. Start the Cassandra service on all DSS nodes.\n4. Retry the job."
    },
    "3282": {
        "code": 3282,
        "desc": "Failed to get the backup status.",
        "first_action": "Review the Detailed status in the Activity Monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapireq_handler logs for more details."
    },
    "3283": {
        "code": 3283,
        "desc": "Failed to set the incremental backup flag.",
        "first_action": "Verify that the Cassandra yaml path that is specified in",
        "full_action": "Verify that the Cassandra yaml path that is specified in\nthe Cassandra configuration file is valid and has proper permissions.\nReview the nbaapireq_handler logs for more details."
    },
    "3284": {
        "code": 3284,
        "desc": "Failed to flush the nodetool buffer. NetBackup status codes 559 NetBackup status codes",
        "first_action": "Verify that the nodetool works properly.",
        "full_action": "Perform the following as appropriate:\n■ Verify that the nodetool works properly.\n■ Verify if Cassandra services are active and CQLSH is running.\n■ Check if the incremental_backup parameter in the Cassandra yaml file is set\nto true.\n■ Check nbaapireq_handler logs for more details."
    },
    "3286": {
        "code": 3286,
        "desc": "An error has occurred during Backup Prepare due to invalid input.",
        "first_action": "Verify the configuration in the Cassandra configuration",
        "full_action": "Verify the configuration in the Cassandra configuration\nfile for the specified Cassandra cluster and its associated entries are correct."
    },
    "3287": {
        "code": 3287,
        "desc": "The keyspace or the column family already exists on the Production Cassandra cluster.",
        "first_action": "Verify if the overwrite parameter is set to true in the",
        "full_action": "Verify if the overwrite parameter is set to true in the\nrenamedfile.Ifitissettofalse,thenmakesurethatyouhavedeletedthekeyspace\nand or column family before the restore job."
    },
    "3288": {
        "code": 3288,
        "desc": "Minimum RAM required is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the dssMinRam parameter is mentioned in the",
        "full_action": "Verify that the dssMinRam parameter is mentioned in the\nCassandra configuration file."
    },
    "3289": {
        "code": 3289,
        "desc": "Minimum Storage per backup node is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the dssMinStoragePerBkupNode parameter is",
        "full_action": "Verify that the dssMinStoragePerBkupNode parameter is\nmentioned in the Cassandra configuration file."
    },
    "3290": {
        "code": 3290,
        "desc": "Cassandra yaml file path is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the Cassandra yaml path is specified in the",
        "full_action": "Verify that the Cassandra yaml path is specified in the\nCassandra configuration file and that the file path is correct."
    },
    "3291": {
        "code": 3291,
        "desc": "The concurrent_compactors parameter is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the concurrent_compactors parameter is",
        "full_action": "Verify that the concurrent_compactors parameter is\nspecified and it must be non-empty in the Cassandra configuration file."
    },
    "3292": {
        "code": 3292,
        "desc": "Memory size of the sstableloaderMemsize parameter is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the sstableloaderMemsize parameter is",
        "full_action": "Verify that the sstableloaderMemsize parameter is\nspecified and it must be non-empty in the Cassandra configuration file."
    },
    "3293": {
        "code": 3293,
        "desc": "Concurrent transfers parameter is not specified for Data Staging Server cluster.",
        "first_action": "Verifythattheconcurrenttransfersparameteris specified",
        "full_action": "Verifythattheconcurrenttransfersparameteris specified\nand it must be non-empty in the Cassandra configuration file."
    },
    "3294": {
        "code": 3294,
        "desc": "Script home is not specified for the Data Staging Server cluster.",
        "first_action": "Verify if a valid script home path is specified in the",
        "full_action": "Verify if a valid script home path is specified in the\nCassandra configuration file."
    },
    "3295": {
        "code": 3295,
        "desc": "A working directory path is not specified for the Cassandra backup and restore node.",
        "first_action": "Verify if a working directory path is specified in the",
        "full_action": "Verify if a working directory path is specified in the\nCassandra configuration file."
    },
    "3296": {
        "code": 3296,
        "desc": "The dssDist path is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that a valid dssDist path is specified in the",
        "full_action": "Verify that a valid dssDist path is specified in the\nCassandra configuration file."
    },
    "3297": {
        "code": 3297,
        "desc": "The cph parameter is not specified for the Data Staging Server cluster.",
        "first_action": "Verify that the cph parameter is mentioned in the",
        "full_action": "Verify that the cph parameter is mentioned in the\nCassandra configuration file."
    },
    "3298": {
        "code": 3298,
        "desc": "Backup has failed.",
        "first_action": "Review the Detailed status in the Activity Monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail."
    },
    "3299": {
        "code": 3299,
        "desc": "Backup has failed after retrying.",
        "first_action": "Review the Detailed status in the Activity Monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail."
    },
    "3300": {
        "code": 3300,
        "desc": "An exception has occurred during backup task execution.",
        "first_action": "Review the Detailed status in the Activity Monitor.",
        "full_action": "Perform the following as appropriate:\n■ Review the Detailed status in the Activity Monitor.\n■ Review the nbaapidiscv or nbaapireq_handler logs for more detail."
    },
    "3301": {
        "code": 3301,
        "desc": "Finalize status is not specified for backup task.",
        "first_action": "Verify the parameters for backup_finalize.",
        "full_action": "Perform the following as appropriate:\n■ Verify the parameters for backup_finalize.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail."
    },
    "3304": {
        "code": 3304,
        "desc": "An exception has occurred during restore prepare.",
        "first_action": "Verify that you use valid combinations of selection file and rename file from the",
        "full_action": "Perform the following as appropriate:\n■ Verify that you use valid combinations of selection file and rename file from the\nRestore Combinations.\n■ Reviewthenbcbrlogsinnbaapireq_handlerformoredetailabouttheschema\nfailures."
    },
    "3306": {
        "code": 3306,
        "desc": "Failed to get the file status.",
        "first_action": "Verify the permissions of the workingDir path on DSS node are correct.",
        "full_action": "Perform the following as appropriate:\n■ Verify the permissions of the workingDir path on DSS node are correct.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail."
    },
    "3307": {
        "code": 3307,
        "desc": "Failed to create upload done file.",
        "first_action": "Verify that the workingDir path exists on the CBR and if",
        "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information."
    },
    "3308": {
        "code": 3308,
        "desc": "Failed to create upload failed file.",
        "first_action": "Verify that the workingDir path exists on the CBR and if",
        "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information."
    },
    "3309": {
        "code": 3309,
        "desc": "Target file is not ready.",
        "first_action": "Verify that the backup job has completed. Review the",
        "full_action": "Verify that the backup job has completed. Review the\nnbaapidiscv logs or nbaapireq_handler logs for more details about the issue."
    },
    "3310": {
        "code": 3310,
        "desc": "Failed to lock the file.",
        "first_action": "Verify that the workingDir path exists on the CBR and if",
        "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information."
    },
    "3311": {
        "code": 3311,
        "desc": "File is already locked.",
        "first_action": "Verify that the workingDir path exists on the CBR and if",
        "full_action": "Verify that the workingDir path exists on the CBR and if\nthe path does exist, does it have the correct information."
    },
    "3312": {
        "code": 3312,
        "desc": "Persisted task list is empty.",
        "first_action": "Verify whether new data was present on the Cassandra",
        "full_action": "Verify whether new data was present on the Cassandra\nCluster for the incremental backup."
    },
    "3313": {
        "code": 3313,
        "desc": "Job status is invalid.",
        "first_action": "Deletion of the workingDir and scriptHome on all DSS Node and Production",
        "full_action": "Check the cleanup process for backup or restore for DSS\nand Production nodes. Review the nbaapidiscv logs or nbaapireq_handler logs\nfor more detail.\nFor successful cleanup, verify that the following items completed successfully:\n■ Deletion of the workingDir and scriptHome on all DSS Node and Production\nNode.\n■ Deletion of the lock files on all DSS Node and Production Node.\n■ The Cassandra services were started or stopped on all DSS nodes and\nProduction Node.\n■ The data directories on only the DSS node were deleted.\n■ Disassembled the DSS cluster by replacing the seed node with the respective\nIP.\n■ Deletion of the backup and the snapshots directories within the data directory\npath on the Production Node."
    },
    "3314": {
        "code": 3314,
        "desc": "An exception was encountered during performing finalize.",
        "first_action": "Deletion of the workingDir and scriptHome on all DSS Node and Production",
        "full_action": "Verify that the cleanup has succeeded.\nFor successful cleanup, verify that the following items completed successfully:\n■ Deletion of the workingDir and scriptHome on all DSS Node and Production\nNode.\n■ Deletion of the lock files on all DSS Node and Production Node.\n■ The Cassandra services were started or stopped on all DSS nodes and\nProduction Node.\n■ The data directories on only the DSS node were deleted.\n■ Disassembled the DSS cluster by replacing the seed node with the respective\nIP.\n■ Deletion of the backup and the snapshots directories within the data directory\npath on the Production Node."
    },
    "3315": {
        "code": 3315,
        "desc": "The requested file is already claimed.",
        "first_action": "Verifythatthefilethatiscontainedinthefilepathisclaimed",
        "full_action": "Verifythatthefilethatiscontainedinthefilepathisclaimed\nin the backup."
    },
    "3316": {
        "code": 3316,
        "desc": "Failed to truncate the column family.",
        "first_action": "Perform the truncate operation on DSS. Review the",
        "full_action": "Perform the truncate operation on DSS. Review the\nnbaapidiscv logs or nbaapireq_handler logs for more detail."
    },
    "3317": {
        "code": 3317,
        "desc": "The specified hosts are not found in the Datacenter or Cluster.",
        "first_action": "Verify that the specified production nodes are present in",
        "full_action": "Verify that the specified production nodes are present in\ndatacenter. Verify that the credentials or configurations are correct."
    },
    "3318": {
        "code": 3318,
        "desc": "Invalid value for the nodeDownThresholdPercentage parameter.",
        "first_action": "Verify that the value of nodeDownThresholdPercentage",
        "full_action": "Verify that the value of nodeDownThresholdPercentage\nin Cassandra configuration file is a value that it is greater than 0 or less than 100."
    },
    "3319": {
        "code": 3319,
        "desc": "Thebackuphasfailedasoneofthetaskshasfailedtostartinthebackup.",
        "first_action": "Review the nbaapidiscv logs or nbaapireq_handler logs for more detail.",
        "full_action": "Perform the following as appropriate:\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail.\n■ EnsurethattheSStableloaderutilityworks betweentheproductionnodes and\nthe data staging servers."
    },
    "3321": {
        "code": 3321,
        "desc": "Specified download directory path does not exist.",
        "first_action": "Verify that the data directory path doesn’t exist on the",
        "full_action": "Verify that the data directory path doesn’t exist on the\nProduction Nodes."
    },
    "3322": {
        "code": 3322,
        "desc": "Specified download directory is empty.",
        "first_action": "Verify that the contents of the data directory path doesn't",
        "full_action": "Verify that the contents of the data directory path doesn't\nexist on the Production Nodes."
    },
    "3323": {
        "code": 3323,
        "desc": "Failed to transfer the Sorted Strings Table. NetBackup status codes 569 NetBackup status codes",
        "first_action": "Verify that the directories named backups and snapshots exist on the Data",
        "full_action": "Perform the following as appropriate:\n■ Verify that the directories named backups and snapshots exist on the Data\nStaging Server or the Production Nodes.\n■ Review the nbaapidiscv logs or nbaapireq_handler logs for more detail."
    },
    "3324": {
        "code": 3324,
        "desc": "Parallel transfer task has failed.",
        "first_action": "Review the nbaapidiscv or nbaapireq_handler logs for",
        "full_action": "Review the nbaapidiscv or nbaapireq_handler logs for\nmore details."
    },
    "3325": {
        "code": 3325,
        "desc": "Backup Optimize task has failed.",
        "first_action": "Review the nbaapidiscv or nbaapireq_handler logs for",
        "full_action": "Review the nbaapidiscv or nbaapireq_handler logs for\nmore details."
    },
    "3326": {
        "code": 3326,
        "desc": "Backup Transfer task has failed.",
        "first_action": "Verify that the Cassandra cluster nodes are up and accessible.",
        "full_action": "Perform the following as appropriate:\n■ Verify that the Cassandra cluster nodes are up and accessible.\n■ Verify that the user accounts specified are correct and have access privileges\non the Cassandra cluster nodes."
    },
    "3327": {
        "code": 3327,
        "desc": "An error has occurred during backup in production data transfer due to invalid command parameters.",
        "first_action": "Verify that the settings in the application configuration file",
        "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct."
    },
    "3328": {
        "code": 3328,
        "desc": "Anerrorhasoccurredduringtherestoreinthedatatransferduetoinvalid command parameters.",
        "first_action": "Verify that the settings in the application configuration file",
        "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct."
    },
    "3329": {
        "code": 3329,
        "desc": "An error has occurred during the backup in the optimize task due to invalid command parameters.",
        "first_action": "Verify that the settings in the application configuration file",
        "full_action": "Verify that the settings in the application configuration file\nfor the specified Cassandra cluster and its associated entries are correct."
    },
    "3330": {
        "code": 3330,
        "desc": "An active job is currently running for this Cassandra cluster.",
        "first_action": "Ensure that no other parallel operation is running on the Data staging servers",
        "full_action": "Perform the following as appropriate:\n■ Ensure that no other parallel operation is running on the Data staging servers\nor Cassandra cluster nodes.\n■ Retry the job after waiting for the current job to finish.\n■ If there are no jobs running in parallel create a setting in cassandra.conf file\nunder the settings key as follows:\n\"jobCleanupTimeoutSec\": 0\nRetry the job.\nRemove this setting once the jobs start running again. The default time-out is\n8 hours."
    },
    "3331": {
        "code": 3331,
        "desc": "One or more of the input parameters or arguments for restore is invalid.",
        "first_action": "ChecktherestoreSelectionsandalternateRecoveryOptionsfiles.Thefiles",
        "full_action": "Perform the following as appropriate:\n■ ChecktherestoreSelectionsandalternateRecoveryOptionsfiles.Thefiles\nmust contain valid keyspace and alternate column family names.\n■ If an alternate column family or keyspace specified, make sure that they\nare specified as part of the restore selection or the restoreSelections is for\nthe full cluster.\nThe following table contains non-supported restore combinations and the solution\nfor the issue.\nTable 1-5 Non-supported combinations\nError Details Scenario Solution\nKeyspace and its Restoringbothkeyspace Specifyeitherthekeyspace’snewName\ncolumn family cannot be and its column family orthecolumnfamily’snewNameinthe\nrenamed together. with new names. alternateRecoveryOptions.\nNo selection should be When performing a full Remove selectionCriteria from\ngiven when ALL recovery and restoreSelections.\nKEYSPACES is keyspaces are\nrecovered. selected.\nMissing or blank Performing a selective Add the keyspace in the\nkeyspace in selection recovery and selecting selectionCriteria to identify the\ncolumn family without columnFamilies that belong to the\nspecifyingitskeyspace. corresponding keyspace.\nKeyspace cannot be Performing a selective Add the same keyspace in the\nrenamed if it is not recovery and there is a selectionCriteria that is also\nselected in GRANULAR missingkeyspacename specified in\nrecovery. in alternateRecoveryOptions.\nrestoreSelections.\nMissingkeyspaceorthe Renaming a column Add the keyspace in\nkeyspacenameisblank family without alternateRecoveryOptions to\nfor the corresponding specifyingitskeyspace. identify which columnFamilies\ncolumn family being belong to which corresponding\nrenamed. keyspace.\nThe following table contains input validation errors and the solution for the issue.\nTable 1-6 Basic input validation errors\nError Details Scenario Solution\nMissing or blank The Add a valid keyspace value in\nkeyspace in selection. restoreSelections selectionCriteria.\ncontains an invalid\nkeyspace name.\nBlank column family The Add a valid column family value in\nin selection. restoreSelections selectionCriteria.\ncontains an invalid\ncolumn family name.\nTable 1-6 Basic input validation errors (continued)\nError Details Scenario Solution\nMissingkeyspaceorthe The Add a valid keyspace name value in\nkeyspacenameisblank alternateRecoveryOptions alternateRecoveryOptions.\nin the renaming. contains an invalid\nkeyspace name.\nMissingorblankcolumn The Add a valid column family name\nfamily name in the alternateRecoveryOptions value in\nrenaming. contains an invalid alternateRecoveryOptions.\ncolumn family name.\nThe strategy name The AddSIMPLEorNETWORKasvaluesin\nmust be either SIMPLE alternateRecoveryOptions thestrategy nameforthereplication\nor NETWORK. contains an invalid strategy that is required for the\nstrategy name value. respective keyspace in\nalternateRecoveryOptions.\nMissing the strategy The AddSIMPLEorNETWORKasvaluesin\nname and it must be alternateRecoveryOptions strategy name for the replication\neither SIMPLE or does not contain a strategy that is required for the\nNETWORK. strategy name value. respective keyspace in\nalternateRecoveryOptions."
    },
    "3332": {
        "code": 3332,
        "desc": "BackupfailedduetoaninvalidqueryintheCassandraQueryLanguage shell command.",
        "first_action": "Ensure that the Cassandra version and configuration on",
        "full_action": "Ensure that the Cassandra version and configuration on\nthe data staging servers match that of the Cassandra production nodes."
    },
    "3333": {
        "code": 3333,
        "desc": "Restore has failed.",
        "first_action": "Verify that the selections in the restoreSelections and",
        "full_action": "Verify that the selections in the restoreSelections and\nthe alternateRestoreOptions, as mentioned in the Cassandra documentation,\nare correct. Review the restore prerequisites."
    },
    "3335": {
        "code": 3335,
        "desc": "Column family must be selected when you rename the file.",
        "first_action": "Select the name of the column family in the",
        "full_action": "Select the name of the column family in the\nrestoreSelections if you want to rename the column family. Refer to the restore\nprerequisites in the Cassandra documentation."
    },
    "3336": {
        "code": 3336,
        "desc": "Keyspace cannot be changed when column family is selected.",
        "first_action": "If you want to rename a keyspace, don’t select a granular",
        "full_action": "If you want to rename a keyspace, don’t select a granular\nrestore of a column family. Select the keyspace to rename and restore the whole\nkeyspace."
    },
    "3337": {
        "code": 3337,
        "desc": "Strategy cannot be changed when column family is selected.",
        "first_action": "If you want to change the strategy you should only select",
        "full_action": "If you want to change the strategy you should only select\nthe keyspace to be restored and not an individual column family in that keyspace.\nSelect the keyspace as a whole to be restored if you want to change the strategy."
    },
    "3340": {
        "code": 3340,
        "desc": "Verbose is not specified. NetBackup status codes 575 NetBackup status codes",
        "first_action": "Youmustspecifyaverbosesettinginthecassandra.conf",
        "full_action": "Youmustspecifyaverbosesettinginthecassandra.conf\nfile."
    },
    "3341": {
        "code": 3341,
        "desc": "Maximum log size is not specified.",
        "first_action": "You must specify a maximum log size in the settings in",
        "full_action": "You must specify a maximum log size in the settings in\nthe cassandra.conf file."
    },
    "3342": {
        "code": 3342,
        "desc": "Failed to clean up Production Cassandra cluster.",
        "first_action": "You must manually clear the folder that is specified in",
        "full_action": "You must manually clear the folder that is specified in\nsettings on the Cassandra cluster nodes."
    },
    "3346": {
        "code": 3346,
        "desc": "Optional threshold is not specified.",
        "first_action": "You must set the optional threshold value to a max of 32",
        "full_action": "You must set the optional threshold value to a max of 32\nin the cassandra.conf file."
    },
    "3361": {
        "code": 3361,
        "desc": "MongoDB Ops Manager recovery failed.",
        "first_action": "Collect and review the logs that are shown for additional",
        "full_action": "Collect and review the logs that are shown for additional\ninformation: bprd, tar, and nbaapireq_handler. If the problem persists, collect\nthe logs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/."
    },
    "3362": {
        "code": 3362,
        "desc": "The missing MongoDB oplogs are required for recovery.",
        "first_action": "Selectanothersetofbackupandincrementalimagesand",
        "full_action": "Selectanothersetofbackupandincrementalimagesand\nretry the recovery operation."
    },
    "3363": {
        "code": 3363,
        "desc": "Either the cluster or one of its nodes is down.",
        "first_action": "Make sure that the cluster and all the nodes of the cluster",
        "full_action": "Make sure that the cluster and all the nodes of the cluster\nare in an Active state in MongoDB Ops."
    },
    "3364": {
        "code": 3364,
        "desc": "The selected cluster is not a third party managed cluster.",
        "first_action": "Ensure that the target MongoDB Cluster is Third party",
        "full_action": "Ensure that the target MongoDB Cluster is Third party\nmanaged in MongoDB Ops Manager and retry the recovery operation."
    },
    "3365": {
        "code": 3365,
        "desc": "Failed to mark the snapshot as FINISHED.",
        "first_action": "Collect and review the logs that are shown for additional",
        "full_action": "Collect and review the logs that are shown for additional\ninformation: bpbrm, nbaapidiscv, and bpbkar. If the problem persists, collect the\nlogs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/."
    },
    "3366": {
        "code": 3366,
        "desc": "Failed to mark the snapshot as FAILED.",
        "first_action": "Collect and review the logs that are shown for additional",
        "full_action": "Collect and review the logs that are shown for additional\ninformation: bpbrm, nbaapidiscv, and bpbkar. If the problem persists, collect the\nlogs that are indicated and contact Cohesity Technical Support.\nThelogsarefoundat:Windows:install_path\\NetBackup\\logs\\UNIXandLinux:\n/usr/openv/netbackup/logs/."
    },
    "3367": {
        "code": 3367,
        "desc": "NetBackup found a gap in the MongoDB oplogs.",
        "first_action": "Startafullbackupandconfirmthattheoplogsaredumped",
        "full_action": "Startafullbackupandconfirmthattheoplogsaredumped\nat the oplog location."
    },
    "3600": {
        "code": 3600,
        "desc": "Cannot perform the COSP operation.",
        "first_action": "/usr/openv/netbackup/logs/bpbkar",
        "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp"
    },
    "3601": {
        "code": 3601,
        "desc": "Cannot complete the cloud operation.",
        "first_action": "Ensure that the backup host or recovery host has connectivity to the cloud",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the backup host or recovery host has connectivity to the cloud\nendpoint.\n■ Ensure that the COSP account has valid credentials.\n■ Ensure that the bucket or container exists and the provided credentials have\nthe required permissions to access them.\nYoucanvalidateusinganycloudproviderCLIorcURLcommandstovalidateREST\nAPI for cloud operation works from the backup or the recovery host."
    },
    "3602": {
        "code": 3602,
        "desc": "Cannot run the operation because of insufficient permissions.",
        "first_action": "Use the credentials that have all the proper permissions",
        "full_action": "Use the credentials that have all the proper permissions\nto perform a backup and restore operation."
    },
    "3603": {
        "code": 3603,
        "desc": "Cannot find the object in the specified container or bucket.",
        "first_action": "During policy configuration, provide the object that exists",
        "full_action": "During policy configuration, provide the object that exists\nin the selected bucket or container."
    },
    "3605": {
        "code": 3605,
        "desc": "Failed to connect to NetBackup COSP process.",
        "first_action": "Make sure that the nbcosp process is running using bpps",
        "full_action": "Make sure that the nbcosp process is running using bpps\ncommand.\nYou can manually start the nbcosp process by using the following:\n/usr/openv/pdde/pdcr/bin/nbcosp start"
    },
    "3606": {
        "code": 3606,
        "desc": "Invalid backup selection format was used to specify the value.",
        "first_action": "Make sure that the backup selection format for specifying",
        "full_action": "Make sure that the backup selection format for specifying\nvalues is followed and correct. Values are specified within single quotes in the\nbackup selection."
    },
    "3607": {
        "code": 3607,
        "desc": "Invalid backup selection format.",
        "first_action": "Verify that the backup selection format is correct.",
        "full_action": "Verify that the backup selection format is correct."
    },
    "3608": {
        "code": 3608,
        "desc": "Invalid filter query type or backup selection format.",
        "first_action": "Verify that the backup selection format is correct.",
        "full_action": "Verify that the backup selection format is correct."
    },
    "3609": {
        "code": 3609,
        "desc": "Cannot process response from the COSP process.",
        "first_action": "/usr/openv/netbackup/logs/bpbkar",
        "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp"
    },
    "3612": {
        "code": 3612,
        "desc": "Bucket or container does not exist.",
        "first_action": "Only add an existing container or bucket from the policy",
        "full_action": "Only add an existing container or bucket from the policy\nconfiguration."
    },
    "3613": {
        "code": 3613,
        "desc": "ACLs are not enabled in the bucket and the restore does not attempt to set ACLs for the object or blob.",
        "first_action": "You must enable ACLs for the selected provider.",
        "full_action": "You must enable ACLs for the selected provider."
    },
    "3614": {
        "code": 3614,
        "desc": "Cannot set ACL on the object.",
        "first_action": "Verify that the ACL on the bucket is enabled.",
        "full_action": "Verify that the ACL on the bucket is enabled."
    },
    "3615": {
        "code": 3615,
        "desc": "Cannot confirm upload to the object or blob.",
        "first_action": "/usr/openv/netbackup/logs/bpbkar",
        "full_action": "Check that the metadata is valid and supported by the\ncloud provider. Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp"
    },
    "3616": {
        "code": 3616,
        "desc": "Failed to fetch metadata for the blob.",
        "first_action": "/usr/openv/netbackup/logs/bpbkar",
        "full_action": "Review the following COSP logs for more details:\nFor backup operations:\n■ /usr/openv/netbackup/logs/bpbkar\n■ /usr/openv/netbackup/logs/nbcosp\nFor restore operations:\n■ /usr/openv/netbackup/logs/tar\n■ /usr/openv/netbackup/logs/bptm\n■ /usr/openv/netbackup/logs/nbcosp"
    },
    "3617": {
        "code": 3617,
        "desc": "Empty metadata received.",
        "first_action": "Minimum required metadata fields should be backed up.",
        "full_action": "Minimum required metadata fields should be backed up.\nFor example: Stats"
    },
    "3618": {
        "code": 3618,
        "desc": "An error occurs during ACL fetch for object.",
        "first_action": "Review the appropriate logs. Also, check if an ACL is",
        "full_action": "Review the appropriate logs. Also, check if an ACL is\nenabled on the bucket."
    },
    "3619": {
        "code": 3619,
        "desc": "Cannot restore empty ACLs of the object or blob.",
        "first_action": "Check if the ACL is backed up and if not, then this issue",
        "full_action": "Check if the ACL is backed up and if not, then this issue\nisexpectedbehavior.NeedtoenabletheACLonthebucketandthenrunabackup."
    },
    "3620": {
        "code": 3620,
        "desc": "Provider does not support tag on objects.",
        "first_action": "Remove the tags and retry the operation.",
        "full_action": "Remove the tags and retry the operation."
    },
    "3621": {
        "code": 3621,
        "desc": "Cannot back up the object or blob due to inconsistent data.",
        "first_action": "In the Activity monitor, note all the inconsistent objects",
        "full_action": "In the Activity monitor, note all the inconsistent objects\nfrom the backup. Determine which processes modified these objects during the\nbackup. Take appropriate steps to prevent this issue in future backups. Perform a\nfull backup. Confirm that the inconsistent objects are successfully backed up."
    },
    "3633": {
        "code": 3633,
        "desc": "Cannot retrieve the shared memory identifier.",
        "first_action": "Ensure that there is enough storage space.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is enough storage space.\n■ Restart the computer to clear any shared memory which is not in use.\n■ See the ncfnbcs logs for more information."
    },
    "3634": {
        "code": 3634,
        "desc": "Cannot attach the shared memory identifier.",
        "first_action": "Provide the necessary access rights to the NetBackup user.",
        "full_action": "Perform the following as appropriate:\n■ Provide the necessary access rights to the NetBackup user.\n■ See the ncfnbcs logs for more information."
    },
    "3635": {
        "code": 3635,
        "desc": "Cannot create the shared memory configuration directory for dynamic data stream backups.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/.\n■ See the ncfnbcs logs for more information."
    },
    "3636": {
        "code": 3636,
        "desc": "Cannot open the shared memory configuration file.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/shm/.\n■ See the ncfnbcs logs for more information."
    },
    "3637": {
        "code": 3637,
        "desc": "Cannot save the shared memory information in the configuration file.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/shm/parent_job_stream_number.\n■ See the ncfnbcs logs for more information."
    },
    "3638": {
        "code": 3638,
        "desc": "The crawler timed out waiting for the streams to attach.",
        "first_action": "Confirm that the Maximum number of concurrent jobs",
        "full_action": "Confirm that the Maximum number of concurrent jobs\nparameter in the policy configuration has a value greater than 1. Review the status\nofthesharedmemoryandconfirmthereisenoughsharedmemoryfortheoperation\nto run. Then retry the backup."
    },
    "3639": {
        "code": 3639,
        "desc": "Cannotcreateobjectpropertydirectoryfordynamicdatastreambackups.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/nbcosp/\n■ See the ncfnbcs logs for more information."
    },
    "3640": {
        "code": 3640,
        "desc": "Cannot open the object property configuration file.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has the permissions to create files and folders in the\nlocation: install_path/db/config/nbcosp/parent_job\n■ See the ncfnbcs logs for more information."
    },
    "3641": {
        "code": 3641,
        "desc": "Cannot save the object property information in the configuration file.",
        "first_action": "Ensure that there is adequate storage space or number of nodes.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that there is adequate storage space or number of nodes.\n■ Ensure that NetBackup has write permissions for files in the location:\ninstall_path/db/config/nbcosp/parent_job/stream_number/batch_number/filename.\n■ See the ncfnbcs logs for more information."
    },
    "3642": {
        "code": 3642,
        "desc": "Cannot list the objects.",
        "first_action": "Ensure that the nbcosp daemon is running.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the nbcosp daemon is running.\n■ Ensure that the bucket or container exists.\n■ See the nbcosp and ncfnbcs logs for more information."
    },
    "3643": {
        "code": 3643,
        "desc": "Failed to start backup operation.",
        "first_action": "Confirm that the nbcosp service is active. Review the",
        "full_action": "Confirm that the nbcosp service is active. Review the\nmessages in the Activity monitor and take corrective action as necessary. Then\nretry the backup."
    },
    "3644": {
        "code": 3644,
        "desc": "The staging path that is provided in the policy is invalid. NetBackup status codes 588 NetBackup status codes",
        "first_action": "Specify a valid path in the policy and retry the backup.",
        "full_action": "Specify a valid path in the policy and retry the backup."
    },
    "3645": {
        "code": 3645,
        "desc": "Failed to create or insert into database.",
        "first_action": "Verifythatthetemporarydatabaseexistsatthetemporary",
        "full_action": "Verifythatthetemporarydatabaseexistsatthetemporary\nstaging location. Confirm that the NetBackup service user has the required read\nand write permissions for that database. Then retry the operation."
    },
    "3646": {
        "code": 3646,
        "desc": "Cannot create the staging location directory.",
        "first_action": "ConfirmthattheNetBackupserviceuserhasthenecessary",
        "full_action": "ConfirmthattheNetBackupserviceuserhasthenecessary\nread and write permissions to create directories at the temporary staging location.\nRetry the backup."
    },
    "3647": {
        "code": 3647,
        "desc": "Failed to download object.",
        "first_action": "Review the Activity monitor for details about the reason",
        "full_action": "Review the Activity monitor for details about the reason\nfor the failure and take appropriate corrective action. Then retry the backup. If the\nreason for the failure is an API call, retry the backup."
    },
    "3648": {
        "code": 3648,
        "desc": "File is not found in the staging area.",
        "first_action": "Review the Activity monitor for details about the failure",
        "full_action": "Review the Activity monitor for details about the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "3649": {
        "code": 3649,
        "desc": "Failed to interpret the response from the cloud API.",
        "first_action": "ReviewtheActivitymonitorforthereasonforfailureand",
        "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective action. Then retry the backup."
    },
    "3650": {
        "code": 3650,
        "desc": "Themultifactorauthenticationstatetokenisinvalidorexpiredornouser exists or is associated with the specified token.",
        "first_action": "Re-authenticate with the username and password to receive new state token.",
        "full_action": "Perform the following as appropriate:\nRe-authenticate with the username and password to receive new state token."
    },
    "3651": {
        "code": 3651,
        "desc": "The authorization header is not present, the token is invalid, or you do not have permission for this action.",
        "first_action": "EnsurethatmultifactorauthenticationwebAPIsarecalledwithrequiredauthorization",
        "full_action": "Perform the following as appropriate:\nEnsurethatmultifactorauthenticationwebAPIsarecalledwithrequiredauthorization\nheader."
    },
    "3652": {
        "code": 3652,
        "desc": "Failed to validate the one-time password.",
        "first_action": "Enter new one-time password.",
        "full_action": "Perform the following as appropriate:\nEnter new one-time password."
    },
    "3653": {
        "code": 3653,
        "desc": "The multifactor authentication request cannot be processed.",
        "first_action": "Reconfigure the multifactor authentication so that a new state token is generated.",
        "full_action": "Perform the following as appropriate:\nReconfigure the multifactor authentication so that a new state token is generated."
    },
    "3654": {
        "code": 3654,
        "desc": "Failed to configure multifactor authentication.",
        "first_action": "Determine if the user account has already registered multifactor authentication or",
        "full_action": "Perform the following as appropriate:\nDetermine if the user account has already registered multifactor authentication or\nif the input secret key is valid. The secret key is shared secret between the\nauthenticator application and NetBackup. It is shown in the form of QR code on\nscreen."
    },
    "3655": {
        "code": 3655,
        "desc": "You do not have permissions to perform the operation.",
        "first_action": "Set the correct RBAC permissions on the user account that allows the user to reset",
        "full_action": "Perform the following as appropriate:\nSet the correct RBAC permissions on the user account that allows the user to reset\nother users. Refer to the NetBackup API documentation for more details about\nRBAC permissions."
    },
    "3656": {
        "code": 3656,
        "desc": "Your user account is not registered for multifactor authentication.",
        "first_action": "This error is only seen in the case of direct web API execution. If you see this error",
        "full_action": "Perform the following as appropriate:\nThis error is only seen in the case of direct web API execution. If you see this error\nin regular operation, Cohesity recommends that you review the multifactor\nauthentication status of that user account."
    },
    "3657": {
        "code": 3657,
        "desc": "Failedtocheckwhethermultifactorauthenticationisenabledfortheuser account or not.",
        "first_action": "Review the bpjava-msvc log file on the primary server for more details.",
        "full_action": "Perform the following as appropriate:\nReview the bpjava-msvc log file on the primary server for more details."
    },
    "3658": {
        "code": 3658,
        "desc": "Multifactor authentication is enforced in the domain, however your user account is not configured for multifactor authentication.",
        "first_action": "Configure multifactor authentication for a given user account and then try user",
        "full_action": "Perform the following as appropriate:\nConfigure multifactor authentication for a given user account and then try user\nauthentication."
    },
    "3660": {
        "code": 3660,
        "desc": "Pagination filter string is not in the correct format.",
        "first_action": "Provide OData filter in the correct format when you invoke the NetBackup web API",
        "full_action": "Perform the following as appropriate:\nProvide OData filter in the correct format when you invoke the NetBackup web API\nto list multifactor authentication configured users."
    },
    "3661": {
        "code": 3661,
        "desc": "The specified operation is not allowed on this NetBackup solution.",
        "first_action": "RefertothecorrectNetBackupsolutionguidetoconfiguremultifactorauthentication,",
        "full_action": "Perform the following as appropriate:\nRefertothecorrectNetBackupsolutionguidetoconfiguremultifactorauthentication,\nsuch as the NetBackup Flex Scale documentation set."
    },
    "3662": {
        "code": 3662,
        "desc": "Failed to validate the one-time password during configuration of multifactor authentication.",
        "first_action": "Make the clocks correct as per the current time at the primary server or at the",
        "full_action": "Perform the following as appropriate:\nMake the clocks correct as per the current time at the primary server or at the\nhandheld smart device where authenticator application is running."
    },
    "3675": {
        "code": 3675,
        "desc": "The multifactor authentication request ID does not exist.",
        "first_action": "Specify the valid multifactor authentication request ID in",
        "full_action": "Specify the valid multifactor authentication request ID in\nthe API."
    },
    "3676": {
        "code": 3676,
        "desc": "The configuration cannot be changed using this host.",
        "first_action": "Use the NetBackup web UI to perform the operation.",
        "full_action": "Use the NetBackup web UI to perform the operation."
    },
    "3677": {
        "code": 3677,
        "desc": "The multifactor authentication request has timed out.",
        "first_action": "Ensure that you enter the one-time password within 180",
        "full_action": "Ensure that you enter the one-time password within 180\nseconds during multifactor authentication."
    },
    "3678": {
        "code": 3678,
        "desc": "The multifactor authentication request is not valid.",
        "first_action": "Use the same JWT token for both the API calls.",
        "full_action": "Use the same JWT token for both the API calls."
    },
    "3700": {
        "code": 3700,
        "desc": "Failed to configure the Hardware Security Module in NetBackup or to update the existing configuration in NetBackup.",
        "first_action": "Ensure that all input parameters are valid when configuring HSM.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right HSM token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation."
    },
    "3701": {
        "code": 3701,
        "desc": "TherequestedHardwareSecurityModuleoperationcannotbeperformed.",
        "first_action": "Ensure that all input parameters are valid when configuring HSM.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation."
    },
    "3702": {
        "code": 3702,
        "desc": "Failed to find the PKCS library on the specified path.",
        "first_action": "Confirm that the path information is correct and that the",
        "full_action": "Confirm that the path information is correct and that the\nservice user has the required access permissions to the PKCS#11 library."
    },
    "3703": {
        "code": 3703,
        "desc": "The Hardware Security Module logon failed.",
        "first_action": "Provide the correct pin or token label. Ensure that the",
        "full_action": "Provide the correct pin or token label. Ensure that the\nservice user has appropriate permission to access HSM token object. Refer to the\nNetBackup Security and Encryption Guide for more details."
    },
    "3704": {
        "code": 3704,
        "desc": "The specified key does not exist in the Hardware Security Module.",
        "first_action": "ReviewtheavailablekeysintheHardwareSecurityModule",
        "full_action": "ReviewtheavailablekeysintheHardwareSecurityModule\nand use the correct one."
    },
    "3705": {
        "code": 3705,
        "desc": "The desired cryptographic operation failed.",
        "first_action": "Ensure that all input parameters are valid when configuring HSM.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that all input parameters are valid when configuring HSM.\n■ ConfirmthattheserviceuserhasaccesstothetokendirectoryandthePKCS#11\nlibrary.\n■ Confirm HSM is installed, the key is created, and you can log on to HSM.\n■ Ensure that the correct PKCS#11 library is in use, the HSM key is valid, and\nthe right token is in use.\n■ Verify that the configuration uses supported key algorithms.\n■ Review the logs at install_path/netbackup/logs/nbhsmcmd for debug\ninformation."
    },
    "3706": {
        "code": 3706,
        "desc": "Failed to retrieve the Hardware Security Module configuration in NetBackup.",
        "first_action": "Ensure that the Hardware Security Module is configured.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the Hardware Security Module is configured.\n■ Reviewthelogsatinstall_path/netbackup/logs/nbhsmcmdforfurtherdebug\ninformation."
    },
    "3707": {
        "code": 3707,
        "desc": "Hardware Security Module is not configured in NetBackup.",
        "first_action": "Configure the Hardware Security Module and retry the",
        "full_action": "Configure the Hardware Security Module and retry the\ndesired operation."
    },
    "3708": {
        "code": 3708,
        "desc": "The specified PKCS library path is invalid.",
        "first_action": "Review the location of the PKCS library and provide the",
        "full_action": "Review the location of the PKCS library and provide the\ncorrect PKCS library path."
    },
    "3709": {
        "code": 3709,
        "desc": "The specified token label of the Hardware Security Module is invalid.",
        "first_action": "Review the token label of the Hardware Security Module",
        "full_action": "Review the token label of the Hardware Security Module\nand provide the valid HSM token label."
    },
    "3710": {
        "code": 3710,
        "desc": "The specified key identifier is invalid.",
        "first_action": "Enter a valid and a unique HSM key identifier.",
        "full_action": "Enter a valid and a unique HSM key identifier."
    },
    "3711": {
        "code": 3711,
        "desc": "The specified key label of the Hardware Security Module is invalid. NetBackup status codes 598 NetBackup status codes",
        "first_action": "Enter a valid HSM key label.",
        "full_action": "Enter a valid HSM key label."
    },
    "3712": {
        "code": 3712,
        "desc": "The specified key algorithm is invalid.",
        "first_action": "Provideasupportedkeyalgorithm.RefertotheNetBackup",
        "full_action": "Provideasupportedkeyalgorithm.RefertotheNetBackup\nSecurity Encryption Guide for more details."
    },
    "3713": {
        "code": 3713,
        "desc": "The specified key identifier already exists.",
        "first_action": "Provide a unique identifier for the HSM key.",
        "full_action": "Provide a unique identifier for the HSM key."
    },
    "3800": {
        "code": 3800,
        "desc": "Cannot retrieve the operation type.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3801": {
        "code": 3801,
        "desc": "Cannot complete the requested operation.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3802": {
        "code": 3802,
        "desc": "Cannot run the command.",
        "first_action": "Check that the utility which is used in the requested",
        "full_action": "Check that the utility which is used in the requested\noperation is installed or not.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on the\nmedia server."
    },
    "3803": {
        "code": 3803,
        "desc": "Cannot test the connection to the database.",
        "first_action": "Ensure that the required credentials for the database are valid.",
        "full_action": "If the connection between the media server and the\ndatabase fails, perform the following:\n■ Ensure that the required credentials for the database are valid.\n■ Verify that the media server is able to reach the database.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on the\nmedia server."
    },
    "3804": {
        "code": 3804,
        "desc": "Cannot parse the argument.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3805": {
        "code": 3805,
        "desc": "Out of memory.",
        "first_action": "Review the memory usage and configuration of the",
        "full_action": "Review the memory usage and configuration of the\ndatabase server and then retry the operation with increased memory.\nFor detailed troubleshooting information, refer to the dbagentsutil logs on media\nserver."
    },
    "3806": {
        "code": 3806,
        "desc": "Cannot complete pre-backup operation, the database does not exist.",
        "first_action": "Verify that the database exists. Perform the discovery",
        "full_action": "Verify that the database exists. Perform the discovery\nagain and retry the requested operation."
    },
    "3807": {
        "code": 3807,
        "desc": "Cannot complete the post-backup operation.",
        "first_action": "Reviewthelogsandcheckwhichresourcesarenotcleaned",
        "full_action": "Reviewthelogsandcheckwhichresourcesarenotcleaned\nup in the post backup operation."
    },
    "3808": {
        "code": 3808,
        "desc": "Cannot check if the database exists.",
        "first_action": "Ensure that the database is present before the requested",
        "full_action": "Ensure that the database is present before the requested\noperation is performed."
    },
    "3809": {
        "code": 3809,
        "desc": "Cannot run the backup command.",
        "first_action": "Review the logs for verification of the command and its",
        "full_action": "Review the logs for verification of the command and its\nattributes."
    },
    "3810": {
        "code": 3810,
        "desc": "Cannot find the backup file at the specified location.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3811": {
        "code": 3811,
        "desc": "Cannot perform the PIT restore.",
        "first_action": "Ensure that the cloud storage is available to perform the PIT restore operation.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the cloud storage is available to perform the PIT restore operation.\n■ Refer to the dbagentsutil logs for the exact cause of failures."
    },
    "3812": {
        "code": 3812,
        "desc": "Cannot perform pre-restore operation, database already exists.",
        "first_action": "Ensurethatthedatabasenameisuniqueandnotpresent",
        "full_action": "Ensurethatthedatabasenameisuniqueandnotpresent\nalready."
    },
    "3813": {
        "code": 3813,
        "desc": "Cannot run the restore command.",
        "first_action": "Check the dbagentsutil logs for verification of the",
        "full_action": "Check the dbagentsutil logs for verification of the\ncommand and its attributes."
    },
    "3814": {
        "code": 3814,
        "desc": "Cannot create empty database.",
        "first_action": "Ensure that the database with the new name does not exist.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the database with the new name does not exist.\n■ Ensure there are enough permissions to create the new databases.\n■ Ensurethatthereisenoughstoragespaceavailabletocreatethenewdatabase."
    },
    "3815": {
        "code": 3815,
        "desc": "Cannot complete the post-restore operation. NetBackup status codes 603 NetBackup status codes",
        "first_action": "Reviewthelogstocheckwhichresourcesarenotcleaned",
        "full_action": "Reviewthelogstocheckwhichresourcesarenotcleaned\nup in the post-restore operation."
    },
    "3816": {
        "code": 3816,
        "desc": "Cannot retrieve the list of databases.",
        "first_action": "Ensure there are enough permissions to retrieve the list of all databases for the",
        "full_action": "Perform the following as appropriate:\n■ Ensure there are enough permissions to retrieve the list of all databases for the\ndatabase server.\n■ Review the logs for more information."
    },
    "3817": {
        "code": 3817,
        "desc": "Cannot complete the pre-backup operation.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3818": {
        "code": 3818,
        "desc": "Cannot complete the pre-restore operation.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3819": {
        "code": 3819,
        "desc": "Cannot complete the restore operation.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3820": {
        "code": 3820,
        "desc": "Internal server error.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "3821": {
        "code": 3821,
        "desc": "Cannot complete the credential validate operation.",
        "first_action": "Ensure that server credentials are correct.",
        "full_action": "Ensure that server credentials are correct."
    },
    "3822": {
        "code": 3822,
        "desc": "Cannot delete the database.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3823": {
        "code": 3823,
        "desc": "The cloud provider type not supported.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting dbagentsutil logs on the media server."
    },
    "3824": {
        "code": 3824,
        "desc": "Failed to fetch credentials from CMS.",
        "first_action": "Ensurethatthecorrectcredentialsareaddedandverified",
        "full_action": "Ensurethatthecorrectcredentialsareaddedandverified\nfor the required asset before the requested operation begins."
    },
    "3825": {
        "code": 3825,
        "desc": "Cannot perform the operation because no matching database agent found.",
        "first_action": "Thedbutiliy(InternalCall)foundaninvalidagent.Retry",
        "full_action": "Thedbutiliy(InternalCall)foundaninvalidagent.Retry\nthe operation with a supported configuration."
    },
    "3826": {
        "code": 3826,
        "desc": "Cannot perform the requested operation because the associated credentials were not found.",
        "first_action": "Ensurethatthecorrectcredentialsareaddedandverified.",
        "full_action": "Ensurethatthecorrectcredentialsareaddedandverified."
    },
    "3827": {
        "code": 3827,
        "desc": "Cannot perform the restore due to an invalid database name.",
        "first_action": "Enter a database name using supported characters that",
        "full_action": "Enter a database name using supported characters that\nthe cloud provider supports."
    },
    "3828": {
        "code": 3828,
        "desc": "Unable to reach the database server host.",
        "first_action": "Check the network connectivity or firewall rules to ensure",
        "full_action": "Check the network connectivity or firewall rules to ensure\nthere is a connection to the database server from the NetBackup media server that\nis used during backup and restore operations."
    },
    "3829": {
        "code": 3829,
        "desc": "Cannot perform the requested operation because the native client utility does not exist on the provided host.",
        "first_action": "Ensure that the DBPaaS Native Client utility package is",
        "full_action": "Ensure that the DBPaaS Native Client utility package is\ninstalled on the media server."
    },
    "3830": {
        "code": 3830,
        "desc": "NetBackupWindowsprimaryserverdoesnotsupportbackupandrestore of databases with multi-byte or non-English characters in their name.",
        "first_action": "You can use a primary server running on a Linux platform",
        "full_action": "You can use a primary server running on a Linux platform\nto run the backup of the AWS RDS instance that has multi-byte or non-English\ncharacters in the display name."
    },
    "3831": {
        "code": 3831,
        "desc": "Cannot create instant access for DBPaaS.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server."
    },
    "3832": {
        "code": 3832,
        "desc": "Cannot retrieve details of DBPaaS instant access.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server."
    },
    "3883": {
        "code": 3883,
        "desc": "Cannot delete the DBPaaS instant access export path.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server."
    },
    "3834": {
        "code": 3834,
        "desc": "Failed to fetch cloud plug-in credentials from Snapshot Manager. NetBackup status codes 608 NetBackup status codes",
        "first_action": "Verify that the Snapshot Manager is up and running",
        "full_action": "Verify that the Snapshot Manager is up and running\nbecause this error occurs when NetBackup attempts to retrieve the cloud plug-in\ncredentials from Snapshot manager."
    },
    "3835": {
        "code": 3835,
        "desc": "Failed to unmount instant access path.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting nbtar logs on media server."
    },
    "3836": {
        "code": 3836,
        "desc": "Cannot retrieve all the DBPaaS instant access mounts.",
        "first_action": "For detailed troubleshooting information, create a debug",
        "full_action": "For detailed troubleshooting information, create a debug\nlogdirectoryfortheprocessthatreturnedthisstatuscode.Thenretrytheoperation\nand check the resulting bprd logs on master server."
    },
    "3837": {
        "code": 3837,
        "desc": "Failed to get Azure Managed Identity Access token.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "3838": {
        "code": 3838,
        "desc": "Failed to check if database user has the super privilege.",
        "first_action": "Review the dbagents logs for the check superuser",
        "full_action": "Review the dbagents logs for the check superuser\ncommand and its attributes."
    },
    "3839": {
        "code": 3839,
        "desc": "The database user does not have super privilege.",
        "first_action": "The database user must have the super privilege.",
        "full_action": "The database user must have the super privilege."
    },
    "3840": {
        "code": 3840,
        "desc": "Failed to create the temporary restore file.",
        "first_action": "Retry the restore job.",
        "full_action": "Retry the restore job."
    },
    "3841": {
        "code": 3841,
        "desc": "Cannot complete the universal share operation.",
        "first_action": "Reviewthevpfslogsatthestoragepathofthedatamover",
        "full_action": "Reviewthevpfslogsatthestoragepathofthedatamover\ncontainer."
    },
    "3842": {
        "code": 3842,
        "desc": "The requested backup type for the corresponding DBPaaS asset is unsupported. NetBackup status codes 610 NetBackup status codes",
        "first_action": "VerifythatthebackuptypeforthecorrespondingDBPaaS",
        "full_action": "VerifythatthebackuptypeforthecorrespondingDBPaaS\nasset is supported and if not you must correct the backup type."
    },
    "3843": {
        "code": 3843,
        "desc": "Failed to enable CDC.",
        "first_action": "Verify that the DBPaaS asset user has access to enable",
        "full_action": "Verify that the DBPaaS asset user has access to enable\nCDC and if not, the user needs access enabled to CDC for the DBPaaS asset."
    },
    "3844": {
        "code": 3844,
        "desc": "Failed to disable CDC.",
        "first_action": "Verify that the DBPaaS asset user has access to disable",
        "full_action": "Verify that the DBPaaS asset user has access to disable\nCDC and if not, the user needs access to disable CDC for the DBPaaS asset."
    },
    "3845": {
        "code": 3845,
        "desc": "The database server does not support Azure Managed Identity.",
        "first_action": "Try the operation with database credentials.",
        "full_action": "Try the operation with database credentials."
    },
    "3846": {
        "code": 3846,
        "desc": "Cannot enable version 2 of the variable length deduplication algorithm.",
        "first_action": "-imageId <ushare-id> --segment vldv2 --sw_min 16 --sw_max 32",
        "full_action": "Manually run the vpfs_actions command on storage\nserver to enable vldv2 per the following example:\n/usr/openv/pdde/vpfs/bin/vpfs_actions -a tune\n--imageId <ushare-id> --segment vldv2 --sw_min 16 --sw_max 32"
    },
    "3847": {
        "code": 3847,
        "desc": "Cannot create the S3 bucket because you do not have the required permissions.",
        "first_action": "Add the permission createbucket to the user that needs",
        "full_action": "Add the permission createbucket to the user that needs\nto create the S3 bucket."
    },
    "3849": {
        "code": 3849,
        "desc": "Cannot retrieve GCP Service object.",
        "first_action": "Associate the appropriate permissions to the service",
        "full_action": "Associate the appropriate permissions to the service\naccount that is used."
    },
    "3851": {
        "code": 3851,
        "desc": "Cannot complete the operation, another operation was already in progress.",
        "first_action": "Wait for the current job to complete and rerun the first job.",
        "full_action": "Wait for the current job to complete and rerun the first job."
    },
    "3852": {
        "code": 3852,
        "desc": "Cannot clean up the DBPaaS instant access staging path.",
        "first_action": "EnsurethatavalidAWSElasticfilesystemismountedonthecorrespondingstaging",
        "full_action": "Perform the following as appropriate:\nEnsurethatavalidAWSElasticfilesystemismountedonthecorrespondingstaging\npath."
    },
    "3854": {
        "code": 3854,
        "desc": "Cannot perform the requested operation as the native client utility does not have the required permissions to run.",
        "first_action": "Assign executable permissions to the service user on the",
        "full_action": "Assign executable permissions to the service user on the\nmediaserverforallthird-partyutilitiesthatareusedforcredentialvalidation,backup,\nand restore."
    },
    "3900": {
        "code": 3900,
        "desc": "The page offset is invalid.",
        "first_action": "Review the parameters from the External Credential",
        "full_action": "Review the parameters from the External Credential\nManagement System provider and retry the operation."
    },
    "3901": {
        "code": 3901,
        "desc": "The External Credential Management System provider details were not found with the supplied configuration name. NetBackup status codes 613 NetBackup status codes",
        "first_action": "Create a configuration with the supplied configuration",
        "full_action": "Create a configuration with the supplied configuration\nname through the NetBackup web UI in the Credential management."
    },
    "3902": {
        "code": 3902,
        "desc": "The credential name does not exist.",
        "first_action": "Create the required External Credential Management",
        "full_action": "Create the required External Credential Management\nSystem server credentials before you configure or update the External Credential\nManagement System server. If you get this error when the external credentials are\ncreated, retry the operation."
    },
    "3903": {
        "code": 3903,
        "desc": "The External Credential Management System provider type is invalid.",
        "first_action": "The only supported provider type is CyberArk.",
        "full_action": "The only supported provider type is CyberArk."
    },
    "3904": {
        "code": 3904,
        "desc": "Connection to the External Credential Management System server fails using the provided credential name or port number.",
        "first_action": "Verifyifthehostname,port,certificates,orcredentialsare",
        "full_action": "Verifyifthehostname,port,certificates,orcredentialsare\nvalidsothattheconnectionwiththeExternalCredentialManagementSystemserver\ncan be established."
    },
    "3905": {
        "code": 3905,
        "desc": "Invalid credential response was received from the external credential management system server.",
        "first_action": "Ensurethatthecredentialsthatwere createdin CyberArk",
        "full_action": "Ensurethatthecredentialsthatwere createdin CyberArk\nmaptothesupportedworkloadinNetBackup.Forexample,theMSSQLcredentials\nin CyberArk must only be used with Microsoft SQL assets in NetBackup."
    },
    "3906": {
        "code": 3906,
        "desc": "DeletingtheselectedNamedcredentialisnotpossibleasitisassociated with the Configuration name of the External Credential Management System server. Delete the associated entry first.",
        "first_action": "The External Credential Management System server",
        "full_action": "The External Credential Management System server\nconfiguration must be deleted first to delete a named credential."
    },
    "3907": {
        "code": 3907,
        "desc": "Deleting the selected External Credential Management System server isnotpossibleasitisassociatedwiththeNamedcredentials.Deletetheassociated entry first.",
        "first_action": "To delete an External Credential Management System",
        "full_action": "To delete an External Credential Management System\nserver, you must first delete the Named credentials which use the External\nCredential Management System server."
    },
    "3908": {
        "code": 3908,
        "desc": "The agent details of the External Credential Management System are not found.",
        "first_action": "Create new external credentials with the provided name",
        "full_action": "Create new external credentials with the provided name\nor review the ID of the credentials you want to delete."
    },
    "3909": {
        "code": 3909,
        "desc": "TherequesttoupdatetheinformationofExternalCredentialManagement System provider is invalid.",
        "first_action": "ConfigName",
        "full_action": "Ensure that the following fields are set with valid values:\n■ configName\n■ ecmsHostName\n■ credentialName"
    },
    "3910": {
        "code": 3910,
        "desc": "Application ID is not defined.",
        "first_action": "Ensure that the Application ID exists on the CyberArk",
        "full_action": "Ensure that the Application ID exists on the CyberArk\nserver.\nNote: Application ID - Specifies the unique ID of the application issuing the\npassword request."
    },
    "3911": {
        "code": 3911,
        "desc": "Object or Safe name is not defined.",
        "first_action": "EnsurethatObjectorSafeexistsontheCyberArkserver.",
        "full_action": "EnsurethatObjectorSafeexistsontheCyberArkserver.\nNote: Object - Specifies the name of the password object to retrieve.\nSafe - Specifies the name of the safe where the password is stored."
    },
    "3912": {
        "code": 3912,
        "desc": "The Common Name or Subject Alternative Name of the certificate does not contain the host name of the server or the certificate is invalid.",
        "first_action": "You must ensure that the certificate that is deployed on",
        "full_action": "You must ensure that the certificate that is deployed on\ntheECMSserverhasaCommonNameoraSubjectAlternativeNamethatmatches\nthe host name."
    },
    "3913": {
        "code": 3913,
        "desc": "The credential type is invalid.",
        "first_action": "Make sure that the category of the credentials that are",
        "full_action": "Make sure that the category of the credentials that are\nused when the EMCS server is configured, are the credentials for CyberArk."
    },
    "4000": {
        "code": 4000,
        "desc": "Storage web server login failed.",
        "first_action": "Verify that the NBU Deduplication Storage Server's",
        "full_action": "Verify that the NBU Deduplication Storage Server's\ncredentials(storedintheNetBackupdatabase)arecurrentandvalidforthespecified\nstorage server. These credentials are those that are accessed from the Java GUI."
    },
    "4001": {
        "code": 4001,
        "desc": "Failed to create the instant access mount.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4002": {
        "code": 4002,
        "desc": "Failed to fetch the instant access mount list.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4003": {
        "code": 4003,
        "desc": "Failed to fetch the instant access mount details.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4004": {
        "code": 4004,
        "desc": "Failed to create an instant access virtual machine (VM).",
        "first_action": "Verify that the network configuration is correct and the NFS port is opened in",
        "full_action": "Do the following, as appropriate:\n■ Verify that the network configuration is correct and the NFS port is opened in\nthe firewall settings. If IPv6 is enabled in the ESXi host, also verify the IPv6\nconnectivity between the ESXi host and the storage server.\n■ Verify that the VM name does not conflict with any existing VM in the ESXi\nhost/cluster.\n■ Check the VMWare user privileges to ensure that the user is allowed to create\nthe VM on the vCenter/ESXi host."
    },
    "4005": {
        "code": 4005,
        "desc": "A backup image from an unsupported policy type was specified. Only PureDisk is supported.",
        "first_action": "TheInstantAccessfeatureisonlysupportedontheMSDP",
        "full_action": "TheInstantAccessfeatureisonlysupportedontheMSDP\nstorage server, so ensure that the correct storage server is selected in the policy."
    },
    "4006": {
        "code": 4006,
        "desc": "A backup image from an unsupported policy type was specified. Only the VMware policy type is supported.",
        "first_action": "The Instant Access feature is only supported on the",
        "full_action": "The Instant Access feature is only supported on the\nVMware workload, so ensure that the correct policy type is selected."
    },
    "4007": {
        "code": 4007,
        "desc": "Failed to fetch the storage server name.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4008": {
        "code": 4008,
        "desc": "Unexpected response from the storage web server.",
        "first_action": "Check the storage web service logs on the appliance for",
        "full_action": "Check the storage web service logs on the appliance for\nthe specific reason of the failure."
    },
    "4011": {
        "code": 4011,
        "desc": "Failed to restore a single file to the specified virtual machine (VM).",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4012": {
        "code": 4012,
        "desc": "Failed to list instant access mount directory.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4013": {
        "code": 4013,
        "desc": "Failed to delete the instant access mount.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4014": {
        "code": 4014,
        "desc": "Invalid instant access mount ID.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4015": {
        "code": 4015,
        "desc": "Instant access mount is not yet ready. Try again later.",
        "first_action": "A VM that is being created cannot be deleted. Wait a few",
        "full_action": "A VM that is being created cannot be deleted. Wait a few\nminutes for the VM creation process to complete and then try again."
    },
    "4016": {
        "code": 4016,
        "desc": "Failed to get the download URL from the instant access mount.",
        "first_action": "Ensure that the download file exists; a file that does not exist cannot be",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the download file exists; a file that does not exist cannot be\ndownloaded.\n■ Verify that the download user has enough access permission to download the\nfile.\n■ Verify that the network connection between the browser and the media server\nis working."
    },
    "4017": {
        "code": 4017,
        "desc": "Failed to get RSA public keys from the storage web server.",
        "first_action": "Ensure that your server is running properly.",
        "full_action": "Do the following, as appropriate:\n■ Ensure that your server is running properly.\n■ Ensure that your certificate is valid.\n■ Ensure that there is not a host name mismatch in the certificate.\nIf the public key is still unavailable, please check the web server logs."
    },
    "4019": {
        "code": 4019,
        "desc": "Failed to fetch the storage server credentials.",
        "first_action": "VerifythattheNetBackupWebManagementConsolecan",
        "full_action": "VerifythattheNetBackupWebManagementConsolecan\nread the storage server credentials."
    },
    "4020": {
        "code": 4020,
        "desc": "Failed to fetch VMware server credentials",
        "first_action": "VerifythattheNetBackupWebManagementConsolecan",
        "full_action": "VerifythattheNetBackupWebManagementConsolecan\nread the VMware server credentials."
    },
    "4021": {
        "code": 4021,
        "desc": "Invalid file path specified.",
        "first_action": "Check that the download file exists; a file cannot be downloaded if it does not",
        "full_action": "Do the following, as appropriate:\n■ Check that the download file exists; a file cannot be downloaded if it does not\nexist.\n■ Verify that the download user has enough access permission to download the\nfile."
    },
    "4022": {
        "code": 4022,
        "desc": "Invalid virtual machine (VM) username/password.",
        "first_action": "Specify a username and a password.",
        "full_action": "Specify a username and a password."
    },
    "4023": {
        "code": 4023,
        "desc": "Oneoftherequiredparameters(BIOSUUID,instanceUUID,VMname) is invalid.",
        "first_action": "Specify the required parameters (BIOS UUID, instance",
        "full_action": "Specify the required parameters (BIOS UUID, instance\nUUID, and VM name)."
    },
    "4024": {
        "code": 4024,
        "desc": "Invalid virtual machine (VM) name specified.",
        "first_action": "When you create a VM, you must specify a name that is",
        "full_action": "When you create a VM, you must specify a name that is\nnot blank and that is not longer than 80 characters."
    },
    "4025": {
        "code": 4025,
        "desc": "Failed to fetch image details.",
        "first_action": "Check the NetBackup web service logs for the specific",
        "full_action": "Check the NetBackup web service logs for the specific\ncause of the failure."
    },
    "4026": {
        "code": 4026,
        "desc": "Backup image does not support instant access.",
        "first_action": "Back up the image to supported storage: Media Server",
        "full_action": "Back up the image to supported storage: Media Server\nDeduplication Pool (MSDP)."
    },
    "4027": {
        "code": 4027,
        "desc": "Failed to create the instant access mount.",
        "first_action": "Reduce the number of instant access mounts and try the",
        "full_action": "Reduce the number of instant access mounts and try the\noperation again."
    },
    "4028": {
        "code": 4028,
        "desc": "Failed to reload Media Server Deduplication Pool metadata.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4029": {
        "code": 4029,
        "desc": "Failed to get images from Amazon S3.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4030": {
        "code": 4030,
        "desc": "Internal API call failed.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4031": {
        "code": 4031,
        "desc": "Internal API call to the catalog failed.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4032": {
        "code": 4032,
        "desc": "Failed to get version from the Storage Platform Web Service (SPWS). Ensure that NGINX is running and configured correctly on the selected MSDP storage server.",
        "first_action": "FortheNetBackupAppliance,reviewtheNetBackupWeb",
        "full_action": "FortheNetBackupAppliance,reviewtheNetBackupWeb\nService logs for the specific cause of the failure. For a NetBackup build-your-own\nstorage server, please verify that NGINX is installed and running. Depending on\nworkload, refer to NetBackup for VMware Administrator’s Guide or the NetBackup\nforMicrosoftSQLServerAdministrator’sGuidefordetailedinstructionaboutInstant\nAccess."
    },
    "4033": {
        "code": 4033,
        "desc": "Verification of the JSON Web Token signature failed.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4034": {
        "code": 4034,
        "desc": "Failed to create a NetBackup job for the instant access operation.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4035": {
        "code": 4035,
        "desc": "Failed to update the NetBackup job for the instant access operation.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4036": {
        "code": 4036,
        "desc": "Failed to fetch the NetBackup instant access job details. NetBackup status codes 626 NetBackup status codes",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4037": {
        "code": 4037,
        "desc": "Failed to delete an instant access virtual machine (VM).",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4038": {
        "code": 4038,
        "desc": "Failed to get the instant access folder attributes.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4039": {
        "code": 4039,
        "desc": "The required parameter path is invalid.",
        "first_action": "Correct the path parameter and try the operation again.",
        "full_action": "Correct the path parameter and try the operation again."
    },
    "4040": {
        "code": 4040,
        "desc": "The storage server has an earlier version of NetBackup.",
        "first_action": "UpgradethestorageservertothelatestNetBackupversion.",
        "full_action": "UpgradethestorageservertothelatestNetBackupversion."
    },
    "4041": {
        "code": 4041,
        "desc": "Failed to create the universal share.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4042": {
        "code": 4042,
        "desc": "Failed to fetch the instant access universal share details.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4043": {
        "code": 4043,
        "desc": "Failed to fetch the instant access universal share list.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4044": {
        "code": 4044,
        "desc": "Failed to delete the instant access universal share.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4045": {
        "code": 4045,
        "desc": "Universal share capability is not supported.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4046": {
        "code": 4046,
        "desc": "Failed to fetch asset information.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4047": {
        "code": 4047,
        "desc": "Failed to ping Storage Platform Web Service.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4048": {
        "code": 4048,
        "desc": "Failed to create the instant sync VM.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4049": {
        "code": 4049,
        "desc": "Failed to fetch instant sync VM details.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4050": {
        "code": 4050,
        "desc": "Failed to configure instant access.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "4200": {
        "code": 4200,
        "desc": "Operation failed: Unable to acquire snapshot lock",
        "first_action": "Retry the operation when the snapshot is no longer used",
        "full_action": "Retry the operation when the snapshot is no longer used\nby another operation."
    },
    "4201": {
        "code": 4201,
        "desc": "Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries",
        "first_action": "Therequiredcorrectstoragearraycredentialforthesnapshotmethod(wherever",
        "full_action": "Verify the following:\n■ Therequiredcorrectstoragearraycredentialforthesnapshotmethod(wherever\napplicable) is configured in NetBackup.\n■ The required software for the snapshot method is configured correctly on the\nclient.\n■ You can choose the snapshot method to protect the entries of the backup\nselection (for example, file system).\n■ The entries that are specified in the backup selection are compatible with the\nsnapshot method configured in the policy.\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout configuring a snapshot method."
    },
    "4202": {
        "code": 4202,
        "desc": "Invalid or incompatible storage unit configured",
        "first_action": "The storage destination that is used for the policy is compatible. For example,",
        "full_action": "Verify the following:\n■ The storage destination that is used for the policy is compatible. For example,\nthe snapshot method OST_FIM operates only on an SLP configured as storage\ndestination.\n■ The configuration parameter that was provided for the snapshot method is\ncorrect. For example, verify that the snapshot resources are correct and the\nconfiguration parameters for the configured snapshot method are correct.\n■ You can choose the snapshot method to protect the entries of the backup\nselection (for example, file system).\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout configuring a snapshot method."
    },
    "4203": {
        "code": 4203,
        "desc": "Invalid or unsupported backup selection filelist",
        "first_action": "The entries that are given in the backup selection can be protected by the",
        "full_action": "Verify the following:\n■ The entries that are given in the backup selection can be protected by the\nsnapshot method. For example, a file system that was created on top of an HP\nEVA disk cannot be protected using the snapshot method for IBM.\n■ The volume is mounted on the specified path for NAS volumes (NFS mount\npoints or CIFS share)."
    },
    "4204": {
        "code": 4204,
        "desc": "Incompatible client found",
        "first_action": "Youhaveloggedintotheclientwiththesamedomain-userastheoneregistered",
        "full_action": "Verify the following:\n■ Youhaveloggedintotheclientwiththesamedomain-userastheoneregistered\nwith the NetBackup client service.\n■ The primary client and target or remote client are compatible."
    },
    "4205": {
        "code": 4205,
        "desc": "Incorrect or no credentials found",
        "first_action": "If you created an NDMP policy or configured an NAS Data Mover, check that",
        "full_action": "Verify the following:\n■ If you created an NDMP policy or configured an NAS Data Mover, check that\nthe NDMP host is configured with the correct credentials.\n■ The disk array host or storage server credentials are correct.\n■ Thethirdpartysoftwareorsupportingsoftwarethatisrequiredbytheconfigured\nsnapshot method is installed on the client.\nSee the NetBackup Snapshot Client Administration Guide for more information\nabout snapshot methods."
    },
    "4206": {
        "code": 4206,
        "desc": "Authentication error occurred. NetBackup Client Service is running as Local System, this is likely incorrect. NetBackup status codes 632 NetBackup status codes",
        "first_action": "Update the NetBackup Client Service in the Windows",
        "full_action": "Update the NetBackup Client Service in the Windows\nservices to use the proper credentials that allow access to the storage server."
    },
    "4207": {
        "code": 4207,
        "desc": "Could not fetch snapshot metadata or state files",
        "first_action": "The NetBackup client can communicate with the NetBackup master.",
        "full_action": "Verify the following:\n■ The NetBackup client can communicate with the NetBackup master.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\nUNIX: /usr/openv/netbackup/online_util/fi_cntl"
    },
    "4208": {
        "code": 4208,
        "desc": "Could not send snapshot metadata or statefiles",
        "first_action": "The NetBackup client can communicate with the NetBackup master.",
        "full_action": "Verify the following:\n■ The NetBackup client can communicate with the NetBackup master.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\<client>\nUNIX: /usr/openv/netbackup/db/snapshot/<client>"
    },
    "4209": {
        "code": 4209,
        "desc": "Snapshot metadata or statefiles cannot be created",
        "first_action": "The logs contain a failure that precedes this error which restricts the creation",
        "full_action": "Verify the following:\n■ The logs contain a failure that precedes this error which restricts the creation\nof metadata content.\n■ The state file location on the NetBackup client has write permission. The typical\nlocation of the NetBackup state file on the NetBackup client is as follows:\nWindows: C:\\Program Files\\Veritas\\NetBackup\\db\\snapshot\\<client>\nUNIX: /usr/openv/netbackup/db/snapshot/<client>"
    },
    "4210": {
        "code": 4210,
        "desc": "Incorrect or no content found in snapshot metadata",
        "first_action": "Windows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\",
        "full_action": "Verify that the specified state file is present on the host.\nThe NetBackup state file is normally located in the following NetBackup client\ndirectory:\n■ Windows: C:\\Program Files\\Veritas\\NetBackup\\online_util\\fi_cntl\\\n■ UNIX: /usr/openv/netbackup/online_util/fi_cntl\nContact Cohesity NetBackup support for assistance."
    },
    "4211": {
        "code": 4211,
        "desc": "Snapshot not accessible or invalid snapshot",
        "first_action": "The connection between the NetBackup client and the storage management",
        "full_action": "Verify the following:\n■ The connection between the NetBackup client and the storage management\nhost-array is intact.\n■ The host-specific permission is enabled on the storage array.\n■ The snapshot exists on the storage array or filer.\n■ The snapshot target device is not mapped to multiple HBAs. If it is, unmap one\nof the HBAs and continue. Support of multiple paths for a device that requires\nthe multi-path software."
    },
    "4212": {
        "code": 4212,
        "desc": "Recreation of snapshot failed",
        "first_action": "Verify that the restore flow of operations has succeeded.",
        "full_action": "Verify that the restore flow of operations has succeeded."
    },
    "4213": {
        "code": 4213,
        "desc": "Snapshot import failed",
        "first_action": "The snapshot device is accessible on the client.",
        "full_action": "Verify the following:\n■ The snapshot device is accessible on the client.\n■ The client has all the required software for building the snapshot I/O stack. This\nshould be equivalent to the I/O stack of the primary client whose entity was\nrequired to be protected.\n■ The communication between the NetBackup client and the master server is\nintact.\n■ The copy-back restore target device is not mapped to multiple HBAs. If it is,\nunmap one of the HBAs and continue. Support of multiple paths for a device\nrequires the multi-path software.\n■ Make sure that the iSCSI session is established between the node and the\ntarget."
    },
    "4214": {
        "code": 4214,
        "desc": "Snapshot mount failed",
        "first_action": "You can use the required file system type to mount the given snapshot.",
        "full_action": "Verify the following:\n■ You can use the required file system type to mount the given snapshot.\n■ The required permission exists on the client to enable snapshots for reading\nand traversing."
    },
    "4215": {
        "code": 4215,
        "desc": "Snapshot deletion failed",
        "first_action": "Ensure that the appropriate plug-in is configured in the web UI with the",
        "full_action": "Verify the following:\n■ Ensure that the appropriate plug-in is configured in the web UI with the\nappropriate credentials. If the credentials are changed, ensure that they are\nupdated from the web UI.\n■ Ensure that the snapshot limit of the cloud provider is sufficient."
    },
    "4216": {
        "code": 4216,
        "desc": "Snapshot cleanup failed",
        "first_action": "Verify that you have enabled the permission to delete the",
        "full_action": "Verify that you have enabled the permission to delete the\nfiles."
    },
    "4217": {
        "code": 4217,
        "desc": "Snapshot restore failed",
        "first_action": "The snapshot exists.",
        "full_action": "Verify the following:\n■ The snapshot exists.\n■ You have enough permission to overwrite or create files in the restore directory\nor folder.\n■ The communication between NetBackup and the storage array-filer is intact."
    },
    "4218": {
        "code": 4218,
        "desc": "Snapshot deport failed",
        "first_action": "The snapshot exists.",
        "full_action": "Verify the following:\n■ The snapshot exists.\n■ The communication between NetBackup and the storage array-filer is intact.\n■ TherequiredcredentialsforthestorageserverhavebeensuppliedinNetBackup.\n■ Any required software and license for the third-party software are configured."
    },
    "4219": {
        "code": 4219,
        "desc": "Commandoperationfailed:Third-partycommandorAPIexecutionfailed",
        "first_action": "From the NetBackup logs, identify the failing command or API.",
        "full_action": "Do the following:\n■ From the NetBackup logs, identify the failing command or API.\n■ Ensure that you have the required permission to execute these commands.\n■ If possible, execute the command manually to gather more details about the\nfailure.\n■ Check your configuration to determine the cause of the failing command or the\nAPI."
    },
    "4220": {
        "code": 4220,
        "desc": "Command operation failed: System command or API execution failed",
        "first_action": "From the NetBackup logs, identify the failing command or API.",
        "full_action": "Verify the following:\n■ From the NetBackup logs, identify the failing command or API.\n■ Take corrective actions based on the error that is reported as a result of the\ncommand execution.\n■ Ensure that you have the required permission to execute these commands.\n■ If possible, execute the command manually to gather more details about the\nfailure."
    },
    "4221": {
        "code": 4221,
        "desc": "Found an invalid or unsupported configuration",
        "first_action": "From the NetBackup logs, identify the failing entity and its error.",
        "full_action": "Verify the following:\n■ From the NetBackup logs, identify the failing entity and its error.\n■ Check the support matrix to determine the correct setup for the configuration."
    },
    "4222": {
        "code": 4222,
        "desc": "Operation failed: Unable to acquire policy lock to take snapshot",
        "first_action": "Nomanualinterventionisrequired.TheNetBackupPolicy",
        "full_action": "Nomanualinterventionisrequired.TheNetBackupPolicy\nExecution Manager (NBPEM) retries the job based on the Job retry delay setting\non the master server. To view or set this property, go to Host Properties>Master\nServer>Global Parameters. Contact NetBackup Support if you continue to get\nthis error and you have ensured that no overlapping snapshot jobs are in progress."
    },
    "4223": {
        "code": 4223,
        "desc": "Operation not completed",
        "first_action": "Make sure that Storage vMotion is completed and that",
        "full_action": "Make sure that Storage vMotion is completed and that\nyou move the VM from NetBackup storage to the production datastore."
    },
    "4224": {
        "code": 4224,
        "desc": "STS Internal Error",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "4225": {
        "code": 4225,
        "desc": "Unauthorized operation attempted by client or media on storage server",
        "first_action": "Valid storage server credentials are configured.",
        "full_action": "Verify the following:\n■ Valid storage server credentials are configured.\n■ The client has the required privileges per the vendor specification. Please refer\nto the NetBackup Replication Director Solutions Guide for more details."
    },
    "4226": {
        "code": 4226,
        "desc": "Communication failure occurred with storage server.",
        "first_action": "Ensure that the correct Snapshot Manager is registered with the correct port",
        "full_action": "Verify the following:\n■ Ensure that the correct Snapshot Manager is registered with the correct port\nnumber.\n■ If the Snapshot Manager host name or port number is changed, ensure that it\nis updated in NetBackup.\n■ Ensure that the Snapshot Manager host name is accessible from the media\nserver. To verify, try to log on to the Snapshot Manager host from the browser\nof the media server.\n■ VerifyifthemediaserverorSnapshotManagercertificatesareinvalidormissing.\nThe certificates are not generated if the Snapshot Manager was configured to\nskip certificate generation by adding the following entry in\n/cloudpoint/flexsnap.conf file: [client_registration]\nskip_certificate_generation = yes\nPerform the following to generate the certificates:\n■ Ensure that the primary server hostname is accessible from the Snapshot\nManager. To verify, try to log on to the Snapshot Manager and telnet to the\nprimary server using ports 1556 and 443.\n■ If you use private names for installing certificates and communicating with\nNetBackup, which have to be resolved using /etc/hosts, perform the\nfollowing:\n■ Add entries similar to /etc/hosts file in the\n/cloudpoint/openv/etc/hosts file.\n■ EnsurethatyouusethesameprivatenameduringtheSnapshotManager\ninstallation as well as the Snapshot Manager registration.\n■ Remove the following entry from /cloudpoint/flexsnap.conf file:\n[client_registration] skip_certificate_generation = yes\n■ Re-register Snapshot Manager in the Cloud workload, using the Edit option\navailable in the Snapshot Manager tab in the web UI."
    },
    "4227": {
        "code": 4227,
        "desc": "STS Plug-in error occurred",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "4228": {
        "code": 4228,
        "desc": "Storage server or plug-in version mismatch",
        "first_action": "Verify that the client and the media server support the",
        "full_action": "Verify that the client and the media server support the\nversion of the storage server."
    },
    "4229": {
        "code": 4229,
        "desc": "Insufficient resources or capabilities found by storage server",
        "first_action": "The storage server recognizes the identified device from the backup selection.",
        "full_action": "Verify the following:\n■ The storage server recognizes the identified device from the backup selection.\n■ The required features are enabled on the storage.\n■ The required feature licenses are applied on the storage.\n■ ThestorageserverhassufficientavailablestoragespaceforNetBackuptriggered\nsnapshots."
    },
    "4230": {
        "code": 4230,
        "desc": "Invalid storage topology or storage server configuration error",
        "first_action": "Verify that the storage is correctly configured per the vendor specification.",
        "full_action": "Do the following:\n■ Verify that the storage is correctly configured per the vendor specification.\n■ Verify that the underlying storage supports the topology that is specified in the\nstorage lifecycle policy."
    },
    "4231": {
        "code": 4231,
        "desc": "STS Unexpected Error",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "4232": {
        "code": 4232,
        "desc": "Invalid Discovery Query URI",
        "first_action": "Examine the URI using the policy editor for syntax errors.",
        "full_action": "Examine the URI using the policy editor for syntax errors."
    },
    "4233": {
        "code": 4233,
        "desc": "BIOS UUID client reference not allowed for vCloud NetBackup status codes 642 NetBackup status codes",
        "first_action": "Select another form of client reference for the policy,",
        "full_action": "Select another form of client reference for the policy,\npossibly instance UUID."
    },
    "4234": {
        "code": 4234,
        "desc": "VMware server login failure",
        "first_action": "Correct the credentials that are configured for the",
        "full_action": "Correct the credentials that are configured for the\ndesignated server."
    },
    "4235": {
        "code": 4235,
        "desc": "VCloud keyword used when vCloud not enabled",
        "first_action": "Configure a vCloud director credential, or remove any",
        "full_action": "Configure a vCloud director credential, or remove any\nvCloud related keywords from the policy query."
    },
    "4236": {
        "code": 4236,
        "desc": "VCloud policy includes multiple organizations",
        "first_action": "Correct the policy query to select only VMs from a single",
        "full_action": "Correct the policy query to select only VMs from a single\norganization, or change the policy to enable VMs from multiple organizations."
    },
    "4237": {
        "code": 4237,
        "desc": "Client does not meet policy requirements",
        "first_action": "ModifytheVMtomeettherequirementsfortheconfigured",
        "full_action": "ModifytheVMtomeettherequirementsfortheconfigured\nclient reference, or change the policy to use a different client reference."
    },
    "4238": {
        "code": 4238,
        "desc": "No server credentials configured for policy",
        "first_action": "Verify that the appropriate server credentials have been",
        "full_action": "Verify that the appropriate server credentials have been\nentered for the type of discovery policy."
    },
    "4239": {
        "code": 4239,
        "desc": "Unable to find the virtual machine",
        "first_action": "The virtual machine identifier configured for the policy and the name (display",
        "full_action": "Verify the following:\n■ The virtual machine identifier configured for the policy and the name (display\nname, host name, UUID) entered for the virtual machine on the policy agree.\n■ You can view the virtual machine in the VMware user interface."
    },
    "4240": {
        "code": 4240,
        "desc": "Operation not supported",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "4241": {
        "code": 4241,
        "desc": "Block-level incremental backups are not supported for this device",
        "first_action": "Upgrade the virtual machine hardware to version 7 or",
        "full_action": "Upgrade the virtual machine hardware to version 7 or\nhigher (see the appropriate VMware documentation)."
    },
    "4243": {
        "code": 4243,
        "desc": "Unable to connect to the VirtualCenter server",
        "first_action": "If there are too many VM snapshot jobs, limit the VM jobs",
        "full_action": "If there are too many VM snapshot jobs, limit the VM jobs\nusing the VMware Resource Limit to limit the concurrent jobs."
    },
    "4245": {
        "code": 4245,
        "desc": "Invalid pathname for backup selection",
        "first_action": "The IP address cannot be used in the pathname.",
        "full_action": "The IP address cannot be used in the pathname."
    },
    "4246": {
        "code": 4246,
        "desc": "The requested operation was partially successful.",
        "first_action": "Create a separate policy for each client",
        "full_action": "Do the following:\n■ Create a separate policy for each client\n■ Specify the correct volume name for the Vserver\n■ Specify a volume name and not a directory within a volume"
    },
    "4248": {
        "code": 4248,
        "desc": "Index from snapshot operation failed with an internal error",
        "first_action": "ChecktheNetBackupadministrationlogsformoredetails.",
        "full_action": "ChecktheNetBackupadministrationlogsformoredetails.\nEnsurethatthereisenoughspaceonthemediaservertocreatetheindexdatabase."
    },
    "4249": {
        "code": 4249,
        "desc": "Index from snapshot operation failed, catalog already exists NetBackup status codes 646 NetBackup status codes",
        "first_action": "Check that there is no existing catalog for the specified",
        "full_action": "Check that there is no existing catalog for the specified\nsource image. Check the NetBackup administration logs for more details."
    },
    "4250": {
        "code": 4250,
        "desc": "Index from snapshot operation failed, unable to find child image or file information",
        "first_action": "ChecktheNetBackupadministrationlogsformoredetails.",
        "full_action": "ChecktheNetBackupadministrationlogsformoredetails."
    },
    "4251": {
        "code": 4251,
        "desc": "Indexfromsnapshotoperationfailed.Failedtowriteintoindexdatabase.",
        "first_action": "Typically, the index database is created under",
        "full_action": "Typically, the index database is created under\nNB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be\noverridden by SNAPDIFF_DB_PATH in the NetBackup configuration file. Ensure\nthatthereisenoughspaceonthemediaservertocreatetheindexdatabase.Check\nthe NetBackup administration logs for more details."
    },
    "4252": {
        "code": 4252,
        "desc": "Index from snapshot operation failed. Entry does not belong to any of the backup selection entries.",
        "first_action": "ChecktheNetBackupadministrationlogsformoredetails.",
        "full_action": "ChecktheNetBackupadministrationlogsformoredetails."
    },
    "4253": {
        "code": 4253,
        "desc": "Index from snapshot operation failed. SLP version mismatch for current and previous backup image.",
        "first_action": "ChecktheNetBackupadministrationlogsformoredetails.",
        "full_action": "ChecktheNetBackupadministrationlogsformoredetails."
    },
    "4254": {
        "code": 4254,
        "desc": "Invalid or no path found to create index database",
        "first_action": "Typically, the index database is created under",
        "full_action": "Typically, the index database is created under\nNB_INSTALL_DIR/tmp; for example, /usr/openv/netbackup/tmp. It can be\noverriddenbyaddingSNAPDIFF_DB_PATHintheNetBackupconfiguration.Check\nif the defined path exists."
    },
    "4255": {
        "code": 4255,
        "desc": "Index from snapshot using SnapDiff is disabled by the user",
        "first_action": "Set to 0; do not perform the index from snapshot operation by using SnapDiff.",
        "full_action": "To enable the index from snapshot by using SnapDiff,\nchange the value of the NetBackup configuration key USE_SNAPDIFF by using\nthe bpsetconfig CLI. The possible values of the key are as follows:\n■ Set to 0; do not perform the index from snapshot operation by using SnapDiff.\n■ Set to 1; the index from snapshot by using SnapDiff is enabled only for the\nincremental schedule.\n■ Set to 2; the index from snapshot by using SnapDiff is enabled for all schedule\ntypes."
    },
    "4256": {
        "code": 4256,
        "desc": "Index from snapshot is not supported for the file system associated with backup selection",
        "first_action": "Currently, the index from the snapshot operation using",
        "full_action": "Currently, the index from the snapshot operation using\nSnapDiff is supported for NFS, CIFS file systems. It is also supported when the\npolicy type is NDMP. Change the policy with the backup selection entries that have\na file system that is supported for the index from snapshot operations by using\nSnapDiff."
    },
    "4257": {
        "code": 4257,
        "desc": "Index from snapshot is not supported for the storage server",
        "first_action": "PleasecheckthattheindexfromsnapshotusingSnapDiff",
        "full_action": "PleasecheckthattheindexfromsnapshotusingSnapDiff\nis supported for the storage server. If it is not, then change the SLP with the STU\nassociated with the storage server having support for index from snapshot using\nSnapDiff."
    },
    "4258": {
        "code": 4258,
        "desc": "Transient error encountered while taking Hyper-V VM snapshot",
        "first_action": "Check the event log for Hyper-V VMMS (Log Name:",
        "full_action": "Check the event log for Hyper-V VMMS (Log Name:\nMicrosoft-Windows-Hyper-V-VMMS/Admin) for more information."
    },
    "4259": {
        "code": 4259,
        "desc": "Failed to find VirtualCenter host name in VMware Lookup Service",
        "first_action": "Use the system name as configured in the Platform",
        "full_action": "Use the system name as configured in the Platform\nServices Controller as the NetBackup virtual machine server name."
    },
    "4260": {
        "code": 4260,
        "desc": "Encountered SSO login failure",
        "first_action": "Ensure that the credentials that you entered for the",
        "full_action": "Ensure that the credentials that you entered for the\nNetBackup virtual machine server are authorized for Single Sign-On."
    },
    "4261": {
        "code": 4261,
        "desc": "Encountered VMware Internal Server Error",
        "first_action": "Refer to the details that are given in the error message",
        "full_action": "Refer to the details that are given in the error message\nand the related VMware Knowledge Base article. Check the NetBackup VxUL logs\n(libvcloudsuite).\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2124204"
    },
    "4262": {
        "code": 4262,
        "desc": "Encountered VMware vCloud Suite API failure",
        "first_action": "Refer to the VMware vCenter Server 6.0 Deployment",
        "full_action": "Refer to the VMware vCenter Server 6.0 Deployment\nGuide and the related VMware Knowledge Base article.\nRelated VMware Knowledge Base article: http://kb.vmware.com/kb/2106283"
    },
    "4263": {
        "code": 4263,
        "desc": "Encountered VMware SOAP API failure",
        "first_action": "Refer to the details that are given in the error message",
        "full_action": "Refer to the details that are given in the error message\nand the related VMware Knowledge Base article. Check the NetBackup VxUL logs\n(libvcloudsuite).\nVMware Knowledge Base article: http://kb.vmware.com/kb/2125193"
    },
    "4264": {
        "code": 4264,
        "desc": "Encountered unexpected error while processing TagView XML",
        "first_action": "If the error is from a test query, try the operation again. If",
        "full_action": "If the error is from a test query, try the operation again. If\nthe parent (Discovery) job fails, try the job again with a Reuse VMware selection\nquery results value of 0 in the failing policy clients tab to regenerate the XML file."
    },
    "4265": {
        "code": 4265,
        "desc": "Encountered a VMware Virtual Machine Server that does not support Tags NetBackup status codes 651 NetBackup status codes",
        "first_action": "RefertotheNetBackupforVMwareAdministrator'sGuide.",
        "full_action": "RefertotheNetBackupforVMwareAdministrator'sGuide."
    },
    "4266": {
        "code": 4266,
        "desc": "Encountered a VMware Virtual Machine Server that does not offer Tag APIs",
        "first_action": "RefertotheNetBackupforVMwareAdministrator'sGuide.",
        "full_action": "RefertotheNetBackupforVMwareAdministrator'sGuide."
    },
    "4267": {
        "code": 4267,
        "desc": "Failed to initialize Java Runtime Environment",
        "first_action": "InstalltheversionoftheNetBackupRemoteAdministration",
        "full_action": "InstalltheversionoftheNetBackupRemoteAdministration\nConsole that corresponds to the NetBackup Client installation. The version of the\nNetBackup Remote Administration Console must match the NetBackup Client\nversion."
    },
    "4268": {
        "code": 4268,
        "desc": "Failed to retrieve resource pool information",
        "first_action": "Check the resource pool path. If it is incorrect, specify the",
        "full_action": "Check the resource pool path. If it is incorrect, specify the\ncorrect resource pool path that exists in destination vCenter server."
    },
    "4269": {
        "code": 4269,
        "desc": "Found multiple virtual machines with same identity",
        "first_action": "Select a different display name for restore or rename the",
        "full_action": "Select a different display name for restore or rename the\nvirtualmachinesinthedestinationresourcepoolorvApp.Onlyonevirtualmachine\nwith the same display name can exist in the resource pool or vApp."
    },
    "4270": {
        "code": 4270,
        "desc": "A snapshot of the virtual machine exists and the policy option specifies aborting the backup",
        "first_action": "Either remove the snapshot and restart the backup job or",
        "full_action": "Either remove the snapshot and restart the backup job or\nmodify the policy to ignore or remove existing snapshots. NetBackup removes\nexisting snapshots only if NetBackup created them."
    },
    "4271": {
        "code": 4271,
        "desc": "Maximum virtual machine snapshots exceeded",
        "first_action": "Remove the virtual machine's snapshots and restart the",
        "full_action": "Remove the virtual machine's snapshots and restart the\nbackup job."
    },
    "4272": {
        "code": 4272,
        "desc": "Maximum delta files exceeded NetBackup status codes 653 NetBackup status codes",
        "first_action": "Consolidate the virtual machine’s disks and restart the",
        "full_action": "Consolidate the virtual machine’s disks and restart the\nbackup job."
    },
    "4273": {
        "code": 4273,
        "desc": "Unable to lock the backup or restore host for virtual machine snapshot operations",
        "first_action": "Restart the backup job when no other virtual machine",
        "full_action": "Restart the backup job when no other virtual machine\nsnapshotoperationsareinprocess.IfNetBackupcannotacquirethelockfrequently,\nadjust the NetBackup job configuration as necessary to allow the virtual machine\nsnapshots to run at different times or to run on different hosts. Alternatively,\nreconfigure NetBackup so that the snapshot serialization is not required."
    },
    "4274": {
        "code": 4274,
        "desc": "Failed to remove virtual machine snapshot",
        "first_action": "Delete the virtual machine snapshot manually.",
        "full_action": "Delete the virtual machine snapshot manually."
    },
    "4275": {
        "code": 4275,
        "desc": "Unable to consolidate Virtual Machine Disks",
        "first_action": "Consolidate the virtual machine’s disks manually and",
        "full_action": "Consolidate the virtual machine’s disks manually and\nrestart the job."
    },
    "4276": {
        "code": 4276,
        "desc": "Unable to retrieve Virtual Machine Disk information",
        "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional",
        "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that cause the\nfailure and restart the job."
    },
    "4277": {
        "code": 4277,
        "desc": "Virtual machine path contains unsupported characters",
        "first_action": "Renamethevirtualmachineand/orfolderpathtoonethat",
        "full_action": "Renamethevirtualmachineand/orfolderpathtoonethat\ncontains only supported characters."
    },
    "4278": {
        "code": 4278,
        "desc": "Unable to retrieve virtual machine information",
        "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional",
        "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that cause the\nfailure and restart the job."
    },
    "4279": {
        "code": 4279,
        "desc": "Unable to retrieve virtual machine vCloud information",
        "first_action": "Reviewthejobdetailsandthebpfislogforanyadditional",
        "full_action": "Reviewthejobdetailsandthebpfislogforanyadditional\ninformation that is related to the error. Correct the underlying issues that caused\nthe failure and restart the job."
    },
    "4280": {
        "code": 4280,
        "desc": "Virtual machine contains independent and Raw Device Mapping disks only",
        "first_action": "Remove the virtual machine from the backup policy",
        "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks."
    },
    "4281": {
        "code": 4281,
        "desc": "Virtual machine contains independent disks only",
        "first_action": "Remove the virtual machine from the backup policy",
        "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks."
    },
    "4282": {
        "code": 4282,
        "desc": "Virtual machine contains Raw Device Mapping disks only",
        "first_action": "Remove the virtual machine from the backup policy",
        "full_action": "Remove the virtual machine from the backup policy\nselection or modify the virtual machine to include additional disks."
    },
    "4283": {
        "code": 4283,
        "desc": "Error detected while processing disk identifiers",
        "first_action": "Modify the virtual machine so that none of the UUIDs for",
        "full_action": "Modify the virtual machine so that none of the UUIDs for\nits disks duplicate the UUID for any other virtual machine."
    },
    "4287": {
        "code": 4287,
        "desc": "ANetBackupsnapshotofthevirtualmachineexistsandthepolicyoption specifies aborting the backup",
        "first_action": "Manually remove the orphaned snapshot.",
        "full_action": "Do the following, as appropriate:\n■ Manually remove the orphaned snapshot.\nFor VMware, you can use the VMware vSphere interface to remove virtual\nmachine snapshots. For Hyper-V, you can use nbhypervtool.exe to remove\nNetBackupsnapshotsthatwerecreatedwiththeWMIbackupmethod.Formore\ninformationonnbhypervtool.exe,refertotheNetBackupCommandsReference\nGuide.\n■ Reduce the likelihood of orphaned snapshots by changing the resource limits\nto reduce the load on the appropriate VMware or Hyper-V resource. The\nResource Limit dialog is in the NetBackup Administration Console under\nHost Properties > Master Servers. The NetBackup guides for VMware and\nHyper-V describe the available settings.\n■ Change the NetBackup policy schedules to avoid simultaneous backups of the\nvirtual machine.\n■ ForVMwareonly:ChangetheNetBackuppolicy’sExistingsnapshothandling\nparameter to a different option (such as Continue Backup).\n■ For RHV only: Refer to the following article for steps to unlock the disk:\nhttps://access.redhat.com/solutions/396753. Then manually remove the older\nsnapshots from the RHV manager.\n■ For Nutanix AHV, refer to the Nutanix AHV Administrator’s Guide to remove the\nVM snapshots."
    },
    "4290": {
        "code": 4290,
        "desc": "Failed to create virtual machine snapshot. Virtual machine is busy performing another operation.",
        "first_action": "Retry the snapshot job after the virtual machine has",
        "full_action": "Retry the snapshot job after the virtual machine has\ncompleted the conflicting operation."
    },
    "4292": {
        "code": 4292,
        "desc": "Unabletoactivatechangeblocktrackingincurrentstateofvirtualmachine",
        "first_action": "Delete or consolidate the snapshots on virtual machines",
        "full_action": "Delete or consolidate the snapshots on virtual machines\non vSphere version 6.5 and above so that NetBackup can enable change block\ntracking."
    },
    "4293": {
        "code": 4293,
        "desc": "Invalid credentials or an access violation",
        "first_action": "Verify that there are valid credentials configured for the",
        "full_action": "Verify that there are valid credentials configured for the\nhost/server that is being accessed and that the user has valid privileges to make\nthe request."
    },
    "4294": {
        "code": 4294,
        "desc": "The virtual machine is disconnected",
        "first_action": "Ensure that the ESXi host is powered on and the vCenter",
        "full_action": "Ensure that the ESXi host is powered on and the vCenter\nServer agent (vpxa) is running."
    },
    "4295": {
        "code": 4295,
        "desc": "VM retrieval failed.",
        "first_action": "EnsurethattheRHVmanagercredentialsarecorrectand",
        "full_action": "EnsurethattheRHVmanagercredentialsarecorrectand\nthe RHV manager is accessible from the backup host."
    },
    "4296": {
        "code": 4296,
        "desc": "No server credentials configured.",
        "first_action": "Add the RHV virtualization server credentials.",
        "full_action": "Add the RHV virtualization server credentials."
    },
    "4297": {
        "code": 4297,
        "desc": "Unable to obtain RHV server credentials.",
        "first_action": "Ensure that the RHV manager is accessible from the",
        "full_action": "Ensure that the RHV manager is accessible from the\nbackuphostandthebackuphostisaddedtotheRHVAccessHostsfromNetBackup\nAdministration Console."
    },
    "4298": {
        "code": 4298,
        "desc": "Unable to obtain RHV manager version.",
        "first_action": "Check the RHV versions that NetBackup supports for VM",
        "full_action": "Check the RHV versions that NetBackup supports for VM\nbackup or restore. If the RHV version has changed, you might see this failure if the\nresponse body of some RHV APIs has changed. Ensure that the RHV manager\nname has 95 or fewer characters. Refer to the logs for more information."
    },
    "4299": {
        "code": 4299,
        "desc": "Unable to get topology view tree.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4301": {
        "code": 4301,
        "desc": "Single file restore is not supported for this policy type.",
        "first_action": "Disablethesinglefilerestoreoptioninthepolicyandrerun",
        "full_action": "Disablethesinglefilerestoreoptioninthepolicyandrerun\nthe backup."
    },
    "4302": {
        "code": 4302,
        "desc": "The VM is unavailable on the current host. If the VM is a highly available VM, it may have moved to another host.",
        "first_action": "When SCVMM is used to manage a VM, dynamic",
        "full_action": "When SCVMM is used to manage a VM, dynamic\noptimization can trigger more frequent migration. If there are too frequent retries\nhappening, configure VM optimization actions correctly to manage VM migrations.\nAfter you have configured VM optimization actions, retry the operation."
    },
    "4307": {
        "code": 4307,
        "desc": "Authentication error. NetBackup legacy network service is running as local system.",
        "first_action": "Log on to the NetBackup legacy network service as the",
        "full_action": "Log on to the NetBackup legacy network service as the\ndomain user and try again."
    },
    "4308": {
        "code": 4308,
        "desc": "Authentication error. The service user for NetBackup client service and NetBackup legacy network service, must be the same. NetBackup status codes 661 NetBackup status codes",
        "first_action": "Log on to the NetBackup client service and NetBackup",
        "full_action": "Log on to the NetBackup client service and NetBackup\nlegacy network service as the domain user and try again."
    },
    "4309": {
        "code": 4309,
        "desc": "Authentication error. Unable to retrieve the user for the service.",
        "first_action": "RestartalloftheNetBackupservicesandtrytheoperation",
        "full_action": "RestartalloftheNetBackupservicesandtrytheoperation\nagain."
    },
    "4310": {
        "code": 4310,
        "desc": "Cannot retrieve snapshot information.",
        "first_action": "WhileasnapshotwastakenforSANdevice,someinternal",
        "full_action": "WhileasnapshotwastakenforSANdevice,someinternal\nissuesoccurred.NetBackupcannotcorrectlystorethesnapshot-relatedinformation.\nCheck the bpfis logs and retry the operation."
    },
    "4311": {
        "code": 4311,
        "desc": "Thedevicelistbasedontherestoreselectiondoesnotmatchthedevice’s consistencygroup or groups thatwere foundon thestoragearray. Rollback restore may affect data on consistency group devices.",
        "first_action": "Log on to the storage array and correct the inconsistency in the consistency",
        "full_action": "Perform the following as appropriate:\n■ Log on to the storage array and correct the inconsistency in the consistency\ngroup.\n■ To go ahead with the restore process, use the option Force rollback even if it\ndestroys the consistency group’s state on the storage array available in\nBackup, Archive, and Restore GUI or use -force_group_rollback option with\nbprestore command. Refer to the NetBackup Commands Reference Guide to\nget more information about this rollback option."
    },
    "4312": {
        "code": 4312,
        "desc": "The job did not complete because the /etc/fstab file contains an entry of a backup selection in the UUID or LABEL form.",
        "first_action": "When you use the configuration that is detailed in the",
        "full_action": "When you use the configuration that is detailed in the\nExplanation, of the /etc/fstab file on the primary host, you must use an alternate\nclient as backup host in the policy."
    },
    "4313": {
        "code": 4313,
        "desc": "The rollback restore did not complete because the /etc/fstab file contains an entry of backup selection in UUID or LABEL form.",
        "first_action": "When you use the configuration that is detailed in the",
        "full_action": "When you use the configuration that is detailed in the\nExplanation, of the /etc/fstab file on the primary host, you must temporarily\nremove the policy backup selection entry from the /etc/fstab file. After removal\noftheentry,retrytherollbackrestoreagain.Whentherollbackrestoreissuccessful,\nyou can add the entries back to the /etc/fstab file."
    },
    "4315": {
        "code": 4315,
        "desc": "Cannot replicate the on-premises snapshot.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "4500": {
        "code": 4500,
        "desc": "The number of images to be imported is more than the limit.",
        "first_action": "Reduce the number of images to import to 64 or fewer.",
        "full_action": "Reduce the number of images to import to 64 or fewer."
    },
    "4501": {
        "code": 4501,
        "desc": "Incorrect media ID is used while importing the image.",
        "first_action": "Use the correct media ID while importing the image. Use",
        "full_action": "Use the correct media ID while importing the image. Use\nthe bpmedialist command to get the information."
    },
    "4502": {
        "code": 4502,
        "desc": "Invalid information about the master or the media server. NetBackup status codes 664 NetBackup status codes",
        "first_action": "Use the correct host name during the image import.",
        "full_action": "Use the correct host name during the image import."
    },
    "4503": {
        "code": 4503,
        "desc": "Current active job count exceeds active job count limitation.",
        "first_action": "Wait for the import job to finish before any new import",
        "full_action": "Wait for the import job to finish before any new import\njobs are initiated."
    },
    "4504": {
        "code": 4504,
        "desc": "The number of images to import is zero.",
        "first_action": "Increase the number of images to import.",
        "full_action": "Increase the number of images to import."
    },
    "4505": {
        "code": 4505,
        "desc": "Input client name is inconsistent with client name in backup ID.",
        "first_action": "Verify that you used the correct client name and backup",
        "full_action": "Verify that you used the correct client name and backup\nID when you imported or recovered images."
    },
    "4506": {
        "code": 4506,
        "desc": "Failed to get images from cloud storage.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4507": {
        "code": 4507,
        "desc": "Failed to reload MSDP metadata.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4508": {
        "code": 4508,
        "desc": "Failed to get AMI IDs from AWS.",
        "first_action": "Verify your network connection to Amazon Web Service.",
        "full_action": "Verify your network connection to Amazon Web Service.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "4509": {
        "code": 4509,
        "desc": "Failed to get DR in cloud status.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4510": {
        "code": 4510,
        "desc": "Cloud DR LSU name is not specified.",
        "first_action": "Specify the LSU name for the cloud DR in the request of",
        "full_action": "Specify the LSU name for the cloud DR in the request of\nthe RESTful API."
    },
    "4511": {
        "code": 4511,
        "desc": "Specified cloud DR LSU name does not exist.",
        "first_action": "Use the correct LSU name in the request of RESTful API.",
        "full_action": "Use the correct LSU name in the request of RESTful API."
    },
    "4512": {
        "code": 4512,
        "desc": "No cloud DR LSU is present.",
        "first_action": "Configure a cloud DR LSU in the NetBackup server.",
        "full_action": "Configure a cloud DR LSU in the NetBackup server."
    },
    "4513": {
        "code": 4513,
        "desc": "Input LSU name must be a string.",
        "first_action": "Set the LSU name to the correct JSON formatted string",
        "full_action": "Set the LSU name to the correct JSON formatted string\nin the POST body of the RESTful API."
    },
    "4514": {
        "code": 4514,
        "desc": "Failed to get storage servers.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4515": {
        "code": 4515,
        "desc": "Storage server name is not specified.",
        "first_action": "Specify the storage server name for the cloud DR in the",
        "full_action": "Specify the storage server name for the cloud DR in the\nrequest of the RESTful API."
    },
    "4516": {
        "code": 4516,
        "desc": "Specified storage server name does not exist.",
        "first_action": "Use the correct storage server name in the request of the",
        "full_action": "Use the correct storage server name in the request of the\nRESTful API."
    },
    "4517": {
        "code": 4517,
        "desc": "No storage server is present.",
        "first_action": "Configure a storage server in NetBackup.",
        "full_action": "Configure a storage server in NetBackup."
    },
    "4518": {
        "code": 4518,
        "desc": "Input storage server name must be a string.",
        "first_action": "SetthestorageservernametothecorrectJSONformatted",
        "full_action": "SetthestorageservernametothecorrectJSONformatted\nstring in the POST body of the RESTful API."
    },
    "4519": {
        "code": 4519,
        "desc": "Failed to get active import job count.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4520": {
        "code": 4520,
        "desc": "This operation is not supported on current cloud provider.",
        "first_action": "Review your request and confirm that it is supported on",
        "full_action": "Review your request and confirm that it is supported on\nthe cloud provider."
    },
    "4521": {
        "code": 4521,
        "desc": "This operation is not supported on requested workload.",
        "first_action": "Review that the requested workload is supported on the",
        "full_action": "Review that the requested workload is supported on the\nRESTful API."
    },
    "4604": {
        "code": 4604,
        "desc": "You do not have the required permissions to delete the license key.",
        "first_action": "Verify that you have sufficient permissions for the delete",
        "full_action": "Verify that you have sufficient permissions for the delete\nlicensefileoperation.Verifythatthelicensefilehassufficientpermissionsfordelete\noperation."
    },
    "4605": {
        "code": 4605,
        "desc": "The license key cannot be deleted.",
        "first_action": "Review the OS-based error and take appropriate action.",
        "full_action": "Review the OS-based error and take appropriate action."
    },
    "4606": {
        "code": 4606,
        "desc": "The specified entitlement ID does not exist.",
        "first_action": "Verify that the ID specified is correct.",
        "full_action": "Verify that the ID specified is correct."
    },
    "4607": {
        "code": 4607,
        "desc": "ThespecifiedoperationontheNetBackupentitlementcannotbecarried out.",
        "first_action": "Check the error details mentioned in RESTful API response and perform",
        "full_action": "Perform the following as appropriate:\n■ Check the error details mentioned in RESTful API response and perform\nnecessary corrective action.\n■ Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website site offers additional information to help\nyou troubleshoot this issue."
    },
    "4608": {
        "code": 4608,
        "desc": "License with the specified entitlement ID already exists in NetBackup.",
        "first_action": "Delete the existing license if it is necessary to add it to",
        "full_action": "Delete the existing license if it is necessary to add it to\nNetBackup again. No action is needed when the addition of the license is not\nnecessary."
    },
    "4609": {
        "code": 4609,
        "desc": "The specified license file is corrupted.",
        "first_action": "You must use the license file that is downloaded from the",
        "full_action": "You must use the license file that is downloaded from the\nCohesity licensing portal and add it to the NetBackup software."
    },
    "4610": {
        "code": 4610,
        "desc": "The entitlements do not exist in NetBackup.",
        "first_action": "Verify that you have at least one license in NetBackup.",
        "full_action": "Verify that you have at least one license in NetBackup."
    },
    "4611": {
        "code": 4611,
        "desc": "Cannot add new license when an existing license of a different edition is present.",
        "first_action": "Makesurethatlicensesofdifferenteditionsarenotadded",
        "full_action": "Makesurethatlicensesofdifferenteditionsarenotadded\nat the same time. Make sure that the perpetual license cannot be added on to the\nsubscription license."
    },
    "4612": {
        "code": 4612,
        "desc": "The expired license cannot be added.",
        "first_action": "Make sure that the license is not expired and renew the license before you add a",
        "full_action": "Perform the following as appropriate:\nMake sure that the license is not expired and renew the license before you add a\nnew license."
    },
    "4700": {
        "code": 4700,
        "desc": "Unable to attach restored disks to target VM.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4701": {
        "code": 4701,
        "desc": "Unable to get virtual machine configuration for VM. NetBackup status codes 672 NetBackup status codes",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "4702": {
        "code": 4702,
        "desc": "Delete of existing VM failed with error.",
        "first_action": "Ensure that the VM is turned off. If possible, try to delete",
        "full_action": "Ensure that the VM is turned off. If possible, try to delete\nthe VM manually and then run the restore operation. Refer to the bpVMutil logs\nfor more information and contact Cohesity Technical Support if required."
    },
    "4703": {
        "code": 4703,
        "desc": "Virtual machine creation failed, cannot proceed with restore.",
        "first_action": "Ensure that enough resources are available on the RHV,",
        "full_action": "Ensure that enough resources are available on the RHV,\nVMware, or Nutanix AHV server for the creation of the VM. Refer to the bpVMutil\nlogs for more information and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "4704": {
        "code": 4704,
        "desc": "Failed to create virtual machine with specified disks.",
        "first_action": "Ensure that enough resources are available on the RHV",
        "full_action": "Ensure that enough resources are available on the RHV\nserver for creation of the disks. Refer to the bpVMutil logs for more information\nand contact Cohesity Technical Support if required."
    },
    "4705": {
        "code": 4705,
        "desc": "Unable to retrieve virtual disk configuration.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4706": {
        "code": 4706,
        "desc": "Incorrect virtual disk configuration retrieved.",
        "first_action": "Ensure that the disks that are specified in the rename file",
        "full_action": "Ensure that the disks that are specified in the rename file\nfollow the correct syntax as per specification. Refer to the bpVMutil logs for more\ninformation and contact Cohesity Technical Support if required."
    },
    "4707": {
        "code": 4707,
        "desc": "Unable to attach restored networks to target VM.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions that",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4708": {
        "code": 4708,
        "desc": "Unable to attach restored tags to target VM.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions that",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4709": {
        "code": 4709,
        "desc": "Unable to set high availability option on target VM.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions that",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4710": {
        "code": 4710,
        "desc": "Failed to get VM Tags Information.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions that",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackupsupportsforVMbackup or restore.RefertothebpVMutil logs formore\ninformation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4711": {
        "code": 4711,
        "desc": "CURLencounteredanerror.Insufficientmemoryorinadequateresources available to complete the job.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4712": {
        "code": 4712,
        "desc": "Resource name is empty.",
        "first_action": "Enter the appropriate VM display name. Refer to the",
        "full_action": "Enter the appropriate VM display name. Refer to the\nbpVMutil logs for more information and contact Cohesity Technical Support if\nrequired."
    },
    "4713": {
        "code": 4713,
        "desc": "Resource name contains unsupported characters.",
        "first_action": "Use supported characters in the VM display name. Refer",
        "full_action": "Use supported characters in the VM display name. Refer\nto the bpVMutil logs for more information and contact Cohesity Technical Support\nif required."
    },
    "4714": {
        "code": 4714,
        "desc": "Resource name length exceeds supported maximum length.",
        "first_action": "Ensure that the length of the VM display name is within",
        "full_action": "Ensure that the length of the VM display name is within\nthe supported length. Refer to the bpVMutil logs for more information and contact\nCohesity Technical Support if required."
    },
    "4715": {
        "code": 4715,
        "desc": "Pre-recovery check failure.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4716": {
        "code": 4716,
        "desc": "Unsupported hypervisor type.",
        "first_action": "Refer to the bpVMutil logs for more information. If the",
        "full_action": "Refer to the bpVMutil logs for more information. If the\nproblem persists, contact Cohesity Technical Support."
    },
    "4718": {
        "code": 4718,
        "desc": "Invalid API request parameter.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4719": {
        "code": 4719,
        "desc": "Unable to read and understand virtual disk metadata.",
        "first_action": "Check the disk types that are attached to VM and make",
        "full_action": "Check the disk types that are attached to VM and make\nsurethatNetBackupsupportsthediskformat.Verifythatthedisksthatareattached\nto VMs are properly visible inside the VM."
    },
    "4720": {
        "code": 4720,
        "desc": "Encrypted Virtual Disk is not supported.",
        "first_action": "Verify the list of options that NetBackup supports for",
        "full_action": "Verify the list of options that NetBackup supports for\nbacking up the RHV, VMware, or Nutanix AHV VMs."
    },
    "4721": {
        "code": 4721,
        "desc": "Compressed Virtual Disk is not supported.",
        "first_action": "Verify the list of options that NetBackup supports for",
        "full_action": "Verify the list of options that NetBackup supports for\nbacking up the RHV, VMware, or Nutanix AHV VMs."
    },
    "4722": {
        "code": 4722,
        "desc": "Failed to read from Virtual Disk.",
        "first_action": "Retry the backup operation. Refer to the vxms logs for",
        "full_action": "Retry the backup operation. Refer to the vxms logs for\nmore information about the error."
    },
    "4723": {
        "code": 4723,
        "desc": "Failed to write into Virtual Disk.",
        "first_action": "Retry the restore operation. Refer to the vxms logs for",
        "full_action": "Retry the restore operation. Refer to the vxms logs for\nmore information about the error."
    },
    "4724": {
        "code": 4724,
        "desc": "Invalid Disk Transfer Info.",
        "first_action": "Refer to the vxms logs for more information about this",
        "full_action": "Refer to the vxms logs for more information about this\nerror and if the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4725": {
        "code": 4725,
        "desc": "An internal error occurred.",
        "first_action": "Retry the operation. Refer to the vxms or vfms logs for",
        "full_action": "Retry the operation. Refer to the vxms or vfms logs for\nmore information."
    },
    "4726": {
        "code": 4726,
        "desc": "Failed to create snapshot of the specified VM.",
        "first_action": "Make sure that the VM is unlocked before the backup",
        "full_action": "Make sure that the VM is unlocked before the backup\nstarts. Try to create temporary user snapshot to make sure that there is no issue\nwiththeRHVplatform.RefertothevxmslogsorcontactCohesityTechnicalSupport\nif required.\nBefore a CDP backup job runs, make sure that there is no issue with the nbcctd\nservice. Review the job details in the activity monitor or the bpfis and nbcctd logs\non CDP gateway for more details."
    },
    "4727": {
        "code": 4727,
        "desc": "Failed to fetch VM snapshot information.",
        "first_action": "Check the virtualization server events or logs for more",
        "full_action": "Check the virtualization server events or logs for more\ninformation about this error."
    },
    "4728": {
        "code": 4728,
        "desc": "Failed to open the specified disk.",
        "first_action": "If it is the backup operation, check if the VM disks are",
        "full_action": "If it is the backup operation, check if the VM disks are\nunlocked before the backup starts. Follow the RHV, VMware, or Nutanix AHV\ndocumentation to unlock the disk or VMs if required and retry the backup. If it is the\nrestoreoperation,refertothevxmslogsformoreinformationandiftheissuepersists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue."
    },
    "4729": {
        "code": 4729,
        "desc": "Failed to read the specified disk.",
        "first_action": "Refer to the vxms logs for more information about this",
        "full_action": "Refer to the vxms logs for more information about this\nerror and if the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "4730": {
        "code": 4730,
        "desc": "Failed to close the specified disk.",
        "first_action": "Check the virtualization server events or logs for more",
        "full_action": "Check the virtualization server events or logs for more\ninformation about this error."
    },
    "4731": {
        "code": 4731,
        "desc": "Received invalid response.",
        "first_action": "Check the RHV versions that NetBackup supports for",
        "full_action": "Check the RHV versions that NetBackup supports for\nbackupandrestore.Refertothelogsformoreinformationandthenretrythebackup\nor restore operation."
    },
    "4732": {
        "code": 4732,
        "desc": "Error in parsing the HTTP response.",
        "first_action": "Check the RHV, VMware, or Nutanix AHV versions that",
        "full_action": "Check the RHV, VMware, or Nutanix AHV versions that\nNetBackup supports for VM backup and restore. If the version has changed, you\nmight see this failure if the response body of some APIs has changed. Refer to the\nlogs for more information and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "4733": {
        "code": 4733,
        "desc": "Operation failed due to locked status of VM.",
        "first_action": "Retry the backup operation. Make sure that the VM",
        "full_action": "Retry the backup operation. Make sure that the VM\nsnapshot creation operation happens properly on the RHV server. Try creating a\nVMsnapshotmanuallyfromtheRHVmanagementconsole.Ifthesnapshotcreation\noperationisunresponsive,contactRHVsupport.Ifthesnapshotiscreatedproperly,\nretry the backup operation."
    },
    "4734": {
        "code": 4734,
        "desc": "Failed to update catalog metadata of VM.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "4735": {
        "code": 4735,
        "desc": "Failed to read storage details of VM.",
        "first_action": "Retry the backup operation.",
        "full_action": "Retry the backup operation."
    },
    "4736": {
        "code": 4736,
        "desc": "Failed to set power state of VM.",
        "first_action": "Try to turn on the VM manually. Refer to the bpVMutil",
        "full_action": "Try to turn on the VM manually. Refer to the bpVMutil\nlogs for more information and contact Cohesity Technical Support if required."
    },
    "4737": {
        "code": 4737,
        "desc": "Cannot create VM, VM already exists.",
        "first_action": "UseadifferentVMname,deletetheexistingVM,orcreate",
        "full_action": "UseadifferentVMname,deletetheexistingVM,orcreate\nthe VM on an alternate hypervisor. Refer to the bpVMutil logs for more information\nand contact Cohesity Technical Support if required."
    },
    "4739": {
        "code": 4739,
        "desc": "No disks are attached to the specified VM.",
        "first_action": "When you protect a VM, ensure that the VM has at least",
        "full_action": "When you protect a VM, ensure that the VM has at least\none disk attached."
    },
    "4740": {
        "code": 4740,
        "desc": "Failed to parse catalog entry.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "4741": {
        "code": 4741,
        "desc": "Access forbidden.",
        "first_action": "Make sure that the credentials of the virtualization server",
        "full_action": "Make sure that the credentials of the virtualization server\ndonotchangeduringthebackuporrestore.Ifthecredentialshavechanged,modify\n(or delete and again add) the virtualization server credentials in NetBackup."
    },
    "4743": {
        "code": 4743,
        "desc": "Invalid HTTP method.",
        "first_action": "Refertothevxmslogsformoreinformation.Iftheproblem",
        "full_action": "Refertothevxmslogsformoreinformation.Iftheproblem\npersists, contact Cohesity Technical Support."
    },
    "4744": {
        "code": 4744,
        "desc": "Failed to make HTTP request.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "4745": {
        "code": 4745,
        "desc": "FailedtogetthesignedtickettodownloadthediskfromtheRHVserver. The disk might be in locked state.",
        "first_action": "Ensure that the disk of the VM being backed up is not in",
        "full_action": "Ensure that the disk of the VM being backed up is not in\nlocked state. If it is locked, refer to the RHV documentation to unlock it and then\nretry the backup operation."
    },
    "4746": {
        "code": 4746,
        "desc": "Encountered unaligned page table entry in the Qcow2 disk. Repair the disk and retry the operation.",
        "first_action": "An unexpected alignment of page table entry in Qcow2",
        "full_action": "An unexpected alignment of page table entry in Qcow2\ndisk is observed. Ensure that the VM is up and running with the disk attached, and\nall the VM disks are properly accessible from the VM."
    },
    "4747": {
        "code": 4747,
        "desc": "Storage domain type is undefined. Disk creation failed",
        "first_action": "Check the list storage domain types that NetBackup",
        "full_action": "Check the list storage domain types that NetBackup\nsupports for restoring the RHV VMs."
    },
    "4748": {
        "code": 4748,
        "desc": "Unable to retrieve the VM. NetBackup status codes 684 NetBackup status codes",
        "first_action": "Ensurethatthevirtualizationservercredentialsarecorrect,",
        "full_action": "Ensurethatthevirtualizationservercredentialsarecorrect,\nand the virtualization server is accessible from the backup host. Refer to the\nbpVMutil logs for more information and contact Cohesity Technical Support if\nrequired."
    },
    "4749": {
        "code": 4749,
        "desc": "No server credentials configured.",
        "first_action": "Add the virtualization server credentials to NetBackup.",
        "full_action": "Add the virtualization server credentials to NetBackup."
    },
    "4750": {
        "code": 4750,
        "desc": "Unable to obtain server credentials.",
        "first_action": "Ensurethatthevirtualizationservercredentialsareadded",
        "full_action": "Ensurethatthevirtualizationservercredentialsareadded\nin the Virtual Machine Servers dialog box from the NetBackup Administration\nConsole."
    },
    "4751": {
        "code": 4751,
        "desc": "Failed to delete the snapshot of the specified VM.",
        "first_action": "On the virtualization server, manually delete the VM",
        "full_action": "On the virtualization server, manually delete the VM\nsnapshotthatNetBackupcreated.Ensurethatnobackupjobisrunningforbacking\nup the VM."
    },
    "4755": {
        "code": 4755,
        "desc": "Unable to obtain server version.",
        "first_action": "Ensure that the provided host details (host name, IP, and",
        "full_action": "Ensure that the provided host details (host name, IP, and\nport number) are correct. Also ensure that the host is active and running."
    },
    "4769": {
        "code": 4769,
        "desc": "Unable to retrieve the list of containers.",
        "first_action": "Ensure that you have entered the correct credentials of",
        "full_action": "Ensure that you have entered the correct credentials of\nthe virtualization server and that the server is available and accessible."
    },
    "4770": {
        "code": 4770,
        "desc": "Enter a valid primary VM identifier, NetBackup uses this VM identifier to select and backup virtual machines.",
        "first_action": "Before you begin a backup operation, enter the primary",
        "full_action": "Before you begin a backup operation, enter the primary\nVM identifier to select and back up the VMs."
    },
    "4771": {
        "code": 4771,
        "desc": "Failed to start IOTAPPING for the virtual machine on the VM server.",
        "first_action": "Review the bpVMutil logs on the CDP gateway and the",
        "full_action": "Review the bpVMutil logs on the CDP gateway and the\nCIM service logs on the ESX host for more details."
    },
    "4772": {
        "code": 4772,
        "desc": "Invalid request was received to start IOTAPPING for the virtual machine on the VM server.",
        "first_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.",
        "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview the bpVMutil logs on the CDP gateway for more details."
    },
    "4773": {
        "code": 4773,
        "desc": "Failed to retrieve the virtual machine host information.",
        "first_action": "Verify that there are no issues with the vCenter and the",
        "full_action": "Verify that there are no issues with the vCenter and the\nESX host. Review the bpVMutil logs on the CDP gateway for more details."
    },
    "4774": {
        "code": 4774,
        "desc": "Failed to interact or operate with the VM server services.",
        "first_action": "VerifythattherearenoissueswiththeCIMservicerunning",
        "full_action": "VerifythattherearenoissueswiththeCIMservicerunning\non the ESX. Review the bpVMutil logs on the CDP gateway for more details."
    },
    "4775": {
        "code": 4775,
        "desc": "Invalid request was received to stop IOTAPPING for the virtual machine on the VM server.",
        "first_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.",
        "full_action": "VerifythattheinputJSONreceivedbybpVMutiliscorrect.\nReview bpVMutil logs on the CDP gateway for more details."
    },
    "4776": {
        "code": 4776,
        "desc": "Failed to stop IOTAPPING for the virtual machine on the VM server.",
        "first_action": "Review the bpVMutil logs on the CDP gateway and the",
        "full_action": "Review the bpVMutil logs on the CDP gateway and the\nCIM service logs on the ESX host for more details."
    },
    "4777": {
        "code": 4777,
        "desc": "Storage policy is not detached from one or more virtual disks of virtual machine.",
        "first_action": "Detach the storage policy for all the disks of the VM and",
        "full_action": "Detach the storage policy for all the disks of the VM and\nretry the operation."
    },
    "4778": {
        "code": 4778,
        "desc": "Power state of specified virtual machine to be registered for IO tapping is not on.",
        "first_action": "Turn on the VM to be protected and retry the operation.",
        "full_action": "Turn on the VM to be protected and retry the operation."
    },
    "4779": {
        "code": 4779,
        "desc": "Unsupported ESXi version.",
        "first_action": "Use ESXi version 6.7 or higher with CDP feature.",
        "full_action": "Use ESXi version 6.7 or higher with CDP feature."
    },
    "4780": {
        "code": 4780,
        "desc": "Failed to retrieve or parse the version of Cohesity IO filter.",
        "first_action": "Restart the CIM server service on the ESXi server and",
        "full_action": "Restart the CIM server service on the ESXi server and\nretry the VM subscription to the CDP protection plan. You can find the CIM server\nservice of the ESXi server inConfigure > Services section of the ESXi."
    },
    "4781": {
        "code": 4781,
        "desc": "Unsupported Veritas IO filter version.",
        "first_action": "Install or upgrade VAIO VIB to a version of 4.0 or higher.",
        "full_action": "Install or upgrade VAIO VIB to a version of 4.0 or higher."
    },
    "4782": {
        "code": 4782,
        "desc": "Storage policy is not attached to one or more virtual disks of virtual machine to be registered for IOTAPPING.",
        "first_action": "Attach the storage policy to all the disks of the VM and",
        "full_action": "Attach the storage policy to all the disks of the VM and\nretry."
    },
    "4783": {
        "code": 4783,
        "desc": "The operation was canceled because another operation is in progress for the Cohesity IO filter. NetBackup status codes 689 NetBackup status codes",
        "first_action": "Subscribe or unsubscribe the VMs in batches of five or",
        "full_action": "Subscribe or unsubscribe the VMs in batches of five or\nless."
    },
    "4784": {
        "code": 4784,
        "desc": "Virtual machine is already registered for IO tapping to some gateway.",
        "first_action": "Another CDP gateway protects this VM. You may need",
        "full_action": "Another CDP gateway protects this VM. You may need\ntounsubscribetheVMfromtheoldergatewayandsubscribetoanewCDPgateway."
    },
    "4785": {
        "code": 4785,
        "desc": "ISCSI initiator on the backup or the recovery host is either not running or unable to connect and or authenticate.",
        "first_action": "Ensure that the iSCSI initiator service is installed and",
        "full_action": "Ensure that the iSCSI initiator service is installed and\nrunning and or enabled on the backup or the recovery host. For more information\nabout the iSCSI initiator service installation and enablement on Windows or UNIX\nplatforms, refer to the NetBackup Web UI AHV Administrator’s Guide."
    },
    "4786": {
        "code": 4786,
        "desc": "External data service IP for iSCSI is not set on the AHV cluster.",
        "first_action": "AsrecommendedbyNutanix,thedataservicesIPaddress",
        "full_action": "AsrecommendedbyNutanix,thedataservicesIPaddress\nmust be set for the iSCSI data transfer. To configure: Logon to Nutanix AHV cluster\nPrism console > Settings > Cluster Details > Set iSCSI Data Services IP."
    },
    "4787": {
        "code": 4787,
        "desc": "Unable to retrieve the list of Nutanix AHV hosts.",
        "first_action": "Ensure that the provided credentials of the virtualization",
        "full_action": "Ensure that the provided credentials of the virtualization\nserver are correct and that the server is available and accessible."
    },
    "4788": {
        "code": 4788,
        "desc": "Unable to verify data integrity.",
        "first_action": "IncreasetheCDP_DATA_CHECKSUM_VERIFICATION_TIMEOUT",
        "full_action": "IncreasetheCDP_DATA_CHECKSUM_VERIFICATION_TIMEOUT\nvalue in the bp.conf file on the CDP host."
    },
    "4789": {
        "code": 4789,
        "desc": "Invalid Hypervisor type.",
        "first_action": "The media server that is associated with the STU must",
        "full_action": "The media server that is associated with the STU must\nhave NetBackup version 9.1 or higher."
    },
    "4790": {
        "code": 4790,
        "desc": "The trial backup operation is not supported for the NetBackup version of the remote host. NetBackup status codes 691 NetBackup status codes",
        "first_action": "Torunthetrialbackup,verifythatthemediaserver’slatest",
        "full_action": "Torunthetrialbackup,verifythatthemediaserver’slatest\nversion is 10.0 or newer. If the media server's version is older than 10.0, you must\nupgrade that media server."
    },
    "4793": {
        "code": 4793,
        "desc": "Network interface restore is supported only for original restore location. Select the remove network interface and try again.",
        "first_action": "The Network interface restore option is not supported",
        "full_action": "The Network interface restore option is not supported\nforanalternaterestorescenario.SelecttheRemovenetworkinterfaceoptionand\ninitiate restore again."
    },
    "4794": {
        "code": 4794,
        "desc": "Unable to retrieve the cluster details.",
        "first_action": "Ensure that the backup host can communicate with the",
        "full_action": "Ensure that the backup host can communicate with the\nNetBackup primary server."
    },
    "4795": {
        "code": 4795,
        "desc": "Unable to find the Prism Central for the AHV cluster.",
        "first_action": "EnsurethatthecorrectPrismCentralisconfiguredforthe",
        "full_action": "EnsurethatthecorrectPrismCentralisconfiguredforthe\nAHV cluster."
    },
    "4900": {
        "code": 4900,
        "desc": "The NetBackup UI Compatibility Service is not running.",
        "first_action": "Contact your NetBackup administrator for assistance.",
        "full_action": "Contact your NetBackup administrator for assistance."
    },
    "5100": {
        "code": 5100,
        "desc": "Unable to create the robot inventory file.",
        "first_action": "If the file is not created, confirm that you have enough space available on the",
        "full_action": "Perform the following as appropriate:\n■ If the file is not created, confirm that you have enough space available on the\nsystem.\n■ If NetBackup failed to correctly set permissions on the file, it could be due to\nincorrect file permissions. Ensure that you have the necessary permission to\naccess the folder or the file. Select the file or folder, right-click, and select\nProperties. Then, select the Security tab and confirm that your user account\nhas the necessary permissions.\n■ If NetBackup failed to write the contents to the file enable the write privileges\non the file."
    },
    "5400": {
        "code": 5400,
        "desc": "Backup error - None of the request objects were found in the database",
        "first_action": "Check the backup selection list. Add the objects that are",
        "full_action": "Check the backup selection list. Add the objects that are\npart of the database or remove the database instance from the policy."
    },
    "5401": {
        "code": 5401,
        "desc": "Backup error - FRA (Fast Recovery Area) was requested, but it was not found in the database",
        "first_action": "AddanFRAareatothedatabaseorremovethedatabase",
        "full_action": "AddanFRAareatothedatabaseorremovethedatabase\ninstance from the policy."
    },
    "5402": {
        "code": 5402,
        "desc": "OS Authentication error - Could not connect to the database. Please check the OS credentials",
        "first_action": "Confirmthatthecredentialsareproperlyset.OnWindows,",
        "full_action": "Confirmthatthecredentialsareproperlyset.OnWindows,\nyou may need to replace a process level token. First, select Start>Control\nPanel>AdministrativeTools>LocalSecurityPolicy.Then,expandLocalPolicies\nintheleftpane,clickUserRightsAssignment,anddouble-clickReplaceaprocess\nlevel token in the right pane. Add the user you want to run the client policies as.\nRestart the server for this right to take effect."
    },
    "5403": {
        "code": 5403,
        "desc": "Oracle Authentication error - Could not connect to the database. Please check the Oracle credentials",
        "first_action": "Confirm that the credentials are properly set.",
        "full_action": "Confirm that the credentials are properly set."
    },
    "5404": {
        "code": 5404,
        "desc": "ASM validation error - PROXY backup is not supported for ASM",
        "first_action": "Move the database to non-ASM storage or remove the",
        "full_action": "Move the database to non-ASM storage or remove the\ndatabase instance from the policy."
    },
    "5405": {
        "code": 5405,
        "desc": "Recovery Catalog Authentication error - Could not connect to the Recovery Catalog. Please check the Recovery Catalog credentials. NetBackup status codes 695 NetBackup status codes",
        "first_action": "ConfirmthattheRecoveryCatalogcredentialsareproperly",
        "full_action": "ConfirmthattheRecoveryCatalogcredentialsareproperly\nset."
    },
    "5406": {
        "code": 5406,
        "desc": "Archivelogonlybackuprequested,butdatabaseisnotinARCHIVELOG Mode",
        "first_action": "Confirm that the database archive log mode is properly",
        "full_action": "Confirm that the database archive log mode is properly\nset to either ARCHIVELOG or MANUAL."
    },
    "5407": {
        "code": 5407,
        "desc": "Databaseisinthewrongstate(mustbeOPEN)fortherequestedaction.",
        "first_action": "Confirm that the database mode is set to OPEN. Possible Oracle commands",
        "full_action": "Perform the following as appropriate:\n■ Confirm that the database mode is set to OPEN. Possible Oracle commands\nstartup, startup opens read only, or startup open.\n■ Open the target container database in read-write mode before initiating a PDB\nclone."
    },
    "5408": {
        "code": 5408,
        "desc": "OS Authentication error - Could not find credentials. If this instance is part of an instance group, make sure that the group has the credentials that match this OS Type NetBackup status codes 696 NetBackup status codes",
        "first_action": "If the instance is on a UNIX client, make sure that its",
        "full_action": "If the instance is on a UNIX client, make sure that its\ninstance group contains UNIX credentials. If the instance is on a Windows client,\nmake sure that its instance group contains Windows credentials."
    },
    "5409": {
        "code": 5409,
        "desc": "Cloning is NOT supported for this client platform",
        "first_action": "Refer to the NetBackup Release Notes or the NetBackup",
        "full_action": "Refer to the NetBackup Release Notes or the NetBackup\nMaster Compatibility List for the supported platforms for the cloning feature at the\nfollowing URL:\nhttp://www.netbackup.com/compatibility"
    },
    "5410": {
        "code": 5410,
        "desc": "Oracle Intelligent Policy is NOT supported for this client platform",
        "first_action": "Refer to the NetBackup Release Notes or the NetBackup",
        "full_action": "Refer to the NetBackup Release Notes or the NetBackup\nMasterCompatibilityListforthesupportedplatformsforthisfeatureatthefollowing\nURL:\nhttp://www.netbackup.com/compatibility"
    },
    "5411": {
        "code": 5411,
        "desc": "Cannot do a hot backup of a database in NOARCHIVELOG mode",
        "first_action": "Confirm that the database archive log mode is properly",
        "full_action": "Confirm that the database archive log mode is properly\nset to ARCHIVELOG or change to an offline (cold) database backup."
    },
    "5412": {
        "code": 5412,
        "desc": "Database is in the wrong state (must be OPEN or MOUNTED) for an Archive Log Backup",
        "first_action": "Put the database in an OPEN or MOUNTED state and",
        "full_action": "Put the database in an OPEN or MOUNTED state and\nretry the backup."
    },
    "5413": {
        "code": 5413,
        "desc": "Database is in the wrong state (must be OPEN or MOUNTED) for an FRA backup",
        "first_action": "Put the database in an OPEN or MOUNTED state and",
        "full_action": "Put the database in an OPEN or MOUNTED state and\nretry the backup."
    },
    "5414": {
        "code": 5414,
        "desc": "The requested operation is not supported with this client version",
        "first_action": "Upgrade the NetBackup Client service to enable this",
        "full_action": "Upgrade the NetBackup Client service to enable this\noperation."
    },
    "5415": {
        "code": 5415,
        "desc": "Cannot shut down read-only standby database",
        "first_action": "Do not select the cold database backup option on the",
        "full_action": "Do not select the cold database backup option on the\nOracle tab of the policy."
    },
    "5416": {
        "code": 5416,
        "desc": "Oracle cannot resolve the TNS connection identifier",
        "first_action": "The correct TNS identifier.",
        "full_action": "Verify the following:\n■ The correct TNS identifier.\n■ The correctly configured tnsnames.ora file.\n■ The correct path for the TNS_ADMIN environment variable."
    },
    "5417": {
        "code": 5417,
        "desc": "An error has occurred checking if the NFS server is an appliance.",
        "first_action": "Verify that the database backup share is exported from a",
        "full_action": "Verify that the database backup share is exported from a\nNetBackup appliance."
    },
    "5418": {
        "code": 5418,
        "desc": "The NFS server is not an appliance.",
        "first_action": "Verify that the database backup share is exported from a",
        "full_action": "Verify that the database backup share is exported from a\nNetBackup appliance."
    },
    "5419": {
        "code": 5419,
        "desc": "The database backup share directory is not available on the appliance.",
        "first_action": "Verify that the database backup share directory exists on",
        "full_action": "Verify that the database backup share directory exists on\nthe NetBackup appliance."
    },
    "5420": {
        "code": 5420,
        "desc": "Whole Database - Datafile Copy Share selection is not supported for this client platform.",
        "first_action": "Back up the database using a different method.",
        "full_action": "Back up the database using a different method."
    },
    "5421": {
        "code": 5421,
        "desc": "None of the requested pluggable databases were found.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of the pluggable databases\nthat are specified in the Oracle Intelligent Policy are correct and in the requested\ndatabase. Update the list of pluggable databases in policy. If the pluggable\ndatabases were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete."
    },
    "5422": {
        "code": 5422,
        "desc": "Partial success - one or more of the requested pluggable databases were not found.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of pluggable databases that\nare specified in the Oracle Intelligent Policy are correct and in the requested\ndatabase. Update the list of pluggable databases in policy. If the pluggable\ndatabases were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete."
    },
    "5423": {
        "code": 5423,
        "desc": "Noneoftherequestedtablespaceswerefoundintherequestedpluggable databases.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate the lists, where applicable, in policy. If the pluggable databases or\ntablespaces were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete."
    },
    "5424": {
        "code": 5424,
        "desc": "Partial success - one or more of the requested pluggable databases did not contain any of the requested tablespaces.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivitymonitorformoreinformation.Confirmthelistoftablespacesthatarespecified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdate the lists, where applicable, in policy. If the pluggable databases or\ntablespaces were specified using the command line, please confirm their spelling.\nRetry the backup once the updates are complete."
    },
    "5425": {
        "code": 5425,
        "desc": "None of the requested data files were found in the requested pluggable databases.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of data files that are specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nwere specified using the command line, please confirm their spelling. Retry the\nbackup once the updates are complete."
    },
    "5426": {
        "code": 5426,
        "desc": "Partial success - one or more of the requested pluggable databases did not contain any of the requested data files.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information. Confirm the list of data files that are specified\nintheOracleIntelligentPolicyarecorrectandintherequestedpluggabledatabases.\nUpdatethelists,whereapplicable,inpolicy.Ifthepluggabledatabasesordatafiles\nwere specified using the command line, please confirm their spelling. Retry the\nbackup once the updates are complete."
    },
    "5427": {
        "code": 5427,
        "desc": "Partial success - more than one error was encountered, please refer to the Detailed Status tab in the Job Details and review logs for more information.",
        "first_action": "Check the detailed status of the associated jobs in the",
        "full_action": "Check the detailed status of the associated jobs in the\nactivity monitor for more information on the errors. Depending on the errors, make\nthe appropriate changes to the policy. Retry the backup once the updates are\ncomplete."
    },
    "5428": {
        "code": 5428,
        "desc": "No database backup shares were found.",
        "first_action": "Configuretheappliancedatabasebackupshareandthen",
        "full_action": "Configuretheappliancedatabasebackupshareandthen\nbackup the files to the share using the database vendor’s tools. NetBackup does\nnot retry this job after failure."
    },
    "5429": {
        "code": 5429,
        "desc": "No new files or files that are related to the instance or database were found in the database backup share.",
        "first_action": "Makesurethatabackupisonthedatabasebackupshare",
        "full_action": "Makesurethatabackupisonthedatabasebackupshare\nbefore the policy is executed. If the policy contained an incremental schedule, then\nverify that the database backup share contained new files. NetBackup does not\nretry this job after failure."
    },
    "5430": {
        "code": 5430,
        "desc": "Database must be in ARCHIVELOG mode to perform a cold backup of a pluggable database.",
        "first_action": "ChangethedatabasetoARCHIVELOGmodeorchangethe",
        "full_action": "ChangethedatabasetoARCHIVELOGmodeorchangethe\nbackup request from a cold backup to a hot backup. Retry the backup once the\nupdates are complete."
    },
    "5431": {
        "code": 5431,
        "desc": "The requested operation did not get a response from the NetBackup appliance.",
        "first_action": "On Windows: Add a registry DWORD entry that is called APPLIANCE_TIMEOUT with",
        "full_action": "Thedefaulttimeoutis setto60 seconds.Configurea new\ntimeout on the NetBackup master server. After the timeout is configured on the\nmaster server, confirm the NetBackup appliance is active and retry the operation.\n■ On Windows: Add a registry DWORD entry that is called APPLIANCE_TIMEOUT with\na value in seconds at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\n■ On UNIX: Change the APPLIANCE_TIMEOUT setting in the bp.conf file"
    },
    "5432": {
        "code": 5432,
        "desc": "The requested NetBackup appliance operation is unsuccessful.",
        "first_action": "Review the NetBackup appliance error message log, the",
        "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help."
    },
    "5433": {
        "code": 5433,
        "desc": "The NetBackup request did not complete due to a NetBackup appliance communication issue.",
        "first_action": "Review the NetBackup appliance error message log, the",
        "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help."
    },
    "5434": {
        "code": 5434,
        "desc": "Cannot validate the identity of the NetBackup appliance.",
        "first_action": "Review the NetBackup appliance error message log, the",
        "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help."
    },
    "5435": {
        "code": 5435,
        "desc": "Recoverypointoperations(-create,-delete,or-list)mustbeinitiated from a master server.",
        "first_action": "Create, -delete, or -list command options from the master server. The",
        "full_action": "Contact the NetBackup administrator to run the nborair\n-create, -delete, or -list command options from the master server. The\nNetBackup administrator must have root user (UNIX) or administrator (Windows)\naccess on the master server."
    },
    "5436": {
        "code": 5436,
        "desc": "No recovery point was found.",
        "first_action": "Confirm there is a recovery point created. If there is no",
        "full_action": "Confirm there is a recovery point created. If there is no\nrecovery point, create a recovery point and retry the operation."
    },
    "5437": {
        "code": 5437,
        "desc": "Partial success - recovery points from one or more database shares were not found.",
        "first_action": "Review the NetBackup debug logs (bprd, nboarir) for",
        "full_action": "Review the NetBackup debug logs (bprd, nboarir) for\nmore details about the error. Also, review the NetBackup appliance debug logs for\nfurther details."
    },
    "5438": {
        "code": 5438,
        "desc": "The requested export path information is not found.",
        "first_action": "List all recovery points and see if the requested export",
        "full_action": "List all recovery points and see if the requested export\npath /recovery point is available. Review the NetBackup debug logs (bprd,\nnboarir) for more details about the error. Also, review the NetBackup appliance\ndebug logs for further details."
    },
    "5439": {
        "code": 5439,
        "desc": "Validation unsuccessful. The recovery point was not created from the specified backup ID.",
        "first_action": "Confirm that you requested the correct mount path. Also,",
        "full_action": "Confirm that you requested the correct mount path. Also,\nconfirm that you have requested the correct backup ID in the create recovery point\nprocess. Check with the NetBackup administrator for the correct backup ID in the\ncreaterecoverypointprocessandsystemadministratorforthecorrectexportmount\npath."
    },
    "5440": {
        "code": 5440,
        "desc": "Required environment variable is not set.",
        "first_action": "You need to set the required environment variable",
        "full_action": "You need to set the required environment variable\nORACLE_HOME with the appropriate value and perform the validate operation again.\nReview the NetBackup debug logs (nborair) for more information."
    },
    "5441": {
        "code": 5441,
        "desc": "Attempt to open Oracle direct NFS file was unsuccessful.",
        "first_action": "When NetBackup performs the validate operation on",
        "full_action": "When NetBackup performs the validate operation on\nWindows, we get the mount path that is associated with the set export path from\nOracle direct NFS file. Confirm that the correct value is set in the environment\nvariable ORACLE_HOME. Review the NetBackup debug logs (nborair) for more\ninformation."
    },
    "5442": {
        "code": 5442,
        "desc": "Attempt to retrieve the device information from the NFS mount path was unsuccessful.",
        "first_action": "Confirm that the provided mount path is correct and that",
        "full_action": "Confirm that the provided mount path is correct and that\nthe path is rightly mounted (UNIX) or Oracle direct NFS file (Windows) has the\ncorrect entries. Review the NetBackup debug logs (nborair) for more information."
    },
    "5443": {
        "code": 5443,
        "desc": "Backup ID cannot be used for Oracle instant recovery.",
        "first_action": "Use the nborair command with -list_images option to",
        "full_action": "Use the nborair command with -list_images option to\nview which images should be used for instant recovery and specify a different\nbackup ID."
    },
    "5444": {
        "code": 5444,
        "desc": "The NetBackup appliance credentials retrieval was unsuccessful.",
        "first_action": "Review the NetBackup appliance error message log, the",
        "full_action": "Review the NetBackup appliance error message log, the\nNetBackup Appliance Troubleshooting Guide, or contact the NetBackup appliance\nadministrator for help."
    },
    "5445": {
        "code": 5445,
        "desc": "Oracle instant recovery share cannot be used for backup operations.",
        "first_action": "A Copilot instant recovery share cannot be used in a",
        "full_action": "A Copilot instant recovery share cannot be used in a\nbackup policy."
    },
    "5446": {
        "code": 5446,
        "desc": "Partial success - backup of one or more of the requested shares unsuccessful.",
        "first_action": "Review the detailed status of the backup job and the",
        "full_action": "Review the detailed status of the backup job and the\nbpdbsbora debug logs."
    },
    "5447": {
        "code": 5447,
        "desc": "Could not resolve appliance host name from IP address.",
        "first_action": "Update the NetBackup server list or media server list to",
        "full_action": "Update the NetBackup server list or media server list to\nuse the appliance host name."
    },
    "5448": {
        "code": 5448,
        "desc": "Could not match the appliance to a server in the client’s server list.",
        "first_action": "Add the appliance host name to the client’s server list.",
        "full_action": "Add the appliance host name to the client’s server list."
    },
    "5449": {
        "code": 5449,
        "desc": "The script is not approved for execution. NetBackup status codes 709 NetBackup status codes",
        "first_action": "Move the script to the default location or add the path as",
        "full_action": "Move the script to the default location or add the path as\nan authorized location using the nbsetconfig or bpsetconfig command. The\ndefault location for UNIX is: /usr/openv/netbackup/ext/db_ext. The default\nlocation for Windows is: install_path\\netbackup\\dbext."
    },
    "5450": {
        "code": 5450,
        "desc": "No scripts or paths are approved for execution on this client.",
        "first_action": "Consult the client administrator for information as to why",
        "full_action": "Consult the client administrator for information as to why\nnone was set on this client."
    },
    "5451": {
        "code": 5451,
        "desc": "The script is stored in a remote location.",
        "first_action": "Movethescripttoalocalauthorizedlocationforexecution.",
        "full_action": "Movethescripttoalocalauthorizedlocationforexecution."
    },
    "5452": {
        "code": 5452,
        "desc": "The script cannot be accessed for execution.",
        "first_action": "Confirm that the script and its location are on the local",
        "full_action": "Confirm that the script and its location are on the local\nsystemandNetBackupcanaccessthescript.ForWindowsclients,besuretoverify\nthat the user running the NetBackup client service has read and execute\npermissions for the script."
    },
    "5453": {
        "code": 5453,
        "desc": "The discovered Database ID or Database Unique Name did not match the ID or Name that was expected or provided.",
        "first_action": "Confirm that the registered RAC database has all the",
        "full_action": "Confirm that the registered RAC database has all the\ncorrectinformation.Reviewthescanname,servicename,port,DBID,uniquename,\nand anything else that was provided. Retry the operation."
    },
    "5454": {
        "code": 5454,
        "desc": "The client is not part of the specified RAC cluster.",
        "first_action": "Run the command from a client that is part of the RAC",
        "full_action": "Run the command from a client that is part of the RAC\ncluster."
    },
    "5455": {
        "code": 5455,
        "desc": "The Oracle backup did not start.",
        "first_action": "Check that your database and the file system are in a",
        "full_action": "Check that your database and the file system are in a\nnormal state. Confirm that there are no memory constraints, locked files, rogue\nprocesses, or any other issues that can prevent a backup. Review error logs if\npossible.Oncethesystemisverifiedfunctional,retrytheOraclebackup.Iftheissue\npersists, visit the Cohesity Technical Support website. The Cohesity Technical\nSupport website offers additional information to help you troubleshoot this issue"
    },
    "5456": {
        "code": 5456,
        "desc": "No Oracle RAC instance connections. NetBackup status codes 711 NetBackup status codes",
        "first_action": "Verify that one or more Oracle RAC instances are up and running and can be",
        "full_action": "Retry the backup after you verify the following:\n■ Verify that one or more Oracle RAC instances are up and running and can be\nconnected to.\n■ Verify the credentials that are used to connect to the Oracle RAC instance are\ncorrect in NetBackup."
    },
    "5457": {
        "code": 5457,
        "desc": "Database must not contain any data files that are in backup mode.",
        "first_action": "NetBackup fails any jobs where Oracle data files are",
        "full_action": "NetBackup fails any jobs where Oracle data files are\ndetected to be in backup mode. Take the affected data file out of backup mode and\nre-run the backup."
    },
    "5458": {
        "code": 5458,
        "desc": "The collection and backup of metadata was unsuccessful.",
        "first_action": "Examine the bpdbsbora and dbclient logs on the client",
        "full_action": "Examine the bpdbsbora and dbclient logs on the client\n(Oracle server) to determine the cause of the failure."
    },
    "5459": {
        "code": 5459,
        "desc": "Oracle and DB2 templates are not supported.",
        "first_action": "Oracle backups:",
        "full_action": "You must convert the template into an Oracle Intelligent\nPolicy (OIP), scripts for Oracle, or scripts for DB2 in the following ways:\nOracle templates:\n■ Oracle backups:\n■ Convert the policy and template into an Oracle Intelligent Policy (OIP) using\ntheNetBackupAdministrationConsoleortheNetBackupwebUI.Thisoption\nis the one that is recommended.\n■ Convert the template into an RMAN backup script. Replace the template in\nthe policy with this new backup script.\n■ Oracle restores:\n■ Convert the template into an RMAN restore script.\nDB2 templates:\n■ DB2 backup\n■ ConvertthebackuptemplateintoaDB2backupscript.Replacethetemplate\nin the policy with this new backup script.\n■ DB2 restores:\n■ Convert the template into a DB2 restore script."
    },
    "5461": {
        "code": 5461,
        "desc": "No data file copies were found on the NFS share.",
        "first_action": "An RMAN crosscheck must be performed.",
        "full_action": "An RMAN crosscheck must be performed."
    },
    "5462": {
        "code": 5462,
        "desc": "The Oracle clone operation was unsuccessful.",
        "first_action": "Review the job details to see what failed. You can also",
        "full_action": "Review the job details to see what failed. You can also\nreview the bphdb, bpdbsbora, and dbclient logs on the client (Oracle server) and\nNBARS (NetBackup primary server) for more details."
    },
    "5464": {
        "code": 5464,
        "desc": "Data corruption was detected in the database during backup.",
        "first_action": "Review the database for corruption.",
        "full_action": "Perform the following as appropriate:\n■ Review the database for corruption.\nIf corruption is confirmed, restore the database from the most recent backup\nyou know is good.\n■ Validate the backup integrity before you restore the databases.\n■ Investigatetherootcauseofthecorruptionandimplementpreventivemeasures\nlike regular backups and integrity checks."
    },
    "5500": {
        "code": 5500,
        "desc": "Target destination was not provided to recover the object.",
        "first_action": "Add cloudObjectStoreRecoveryDestination in the",
        "full_action": "Add cloudObjectStoreRecoveryDestination in the\nrecovery API. For more information, go to the SORT website\n(https://sort.veritas.com/), and under Supported Products select NetBackup.\nThen search for NetBackup Recovery API."
    },
    "5501": {
        "code": 5501,
        "desc": "Bucket name must be specified.",
        "first_action": "AddthetargetbucketnameintherecoveryAPI.Formore",
        "full_action": "AddthetargetbucketnameintherecoveryAPI.Formore\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5502": {
        "code": 5502,
        "desc": "Provider name must be specified.",
        "first_action": "Add the provider name in the recovery API. For more",
        "full_action": "Add the provider name in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5503": {
        "code": 5503,
        "desc": "Cloud object store account must be specified.",
        "first_action": "Add the cloud object store account name in the recovery",
        "full_action": "Add the cloud object store account name in the recovery\nAPI. For more information, go to the SORT website (https://sort.veritas.com/), and\nunder Supported Products select NetBackup. Then search for NetBackup\nRecovery API."
    },
    "5504": {
        "code": 5504,
        "desc": "Object/Blobs type must be specified.",
        "first_action": "Add valid Object/Blobs type in the recovery API. For",
        "full_action": "Add valid Object/Blobs type in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5505": {
        "code": 5505,
        "desc": "Recovery type must be specified as part of recovery request.",
        "first_action": "Add a valid recovery type in the recovery API. For more",
        "full_action": "Add a valid recovery type in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5506": {
        "code": 5506,
        "desc": "Recovery Object/Blobs must be specified.",
        "first_action": "Add recovery Object/Blobs if includeAll is false. For",
        "full_action": "Add recovery Object/Blobs if includeAll is false. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5507": {
        "code": 5507,
        "desc": "Recovery Object/Blobs source not provided. NetBackup status codes 716 NetBackup status codes",
        "first_action": "Add the Object/Blobs source in the recovery API. For",
        "full_action": "Add the Object/Blobs source in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5508": {
        "code": 5508,
        "desc": "No destination details provided as part of recovery request.",
        "first_action": "Add the recovery destination details in the recovery API.",
        "full_action": "Add the recovery destination details in the recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5509": {
        "code": 5509,
        "desc": "Specified recovery type is not valid.",
        "first_action": "Add a valid recovery type in the recovery API. For more",
        "full_action": "Add a valid recovery type in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5510": {
        "code": 5510,
        "desc": "Specified provider is not valid.",
        "first_action": "Add a valid provider name in the recovery API. For more",
        "full_action": "Add a valid provider name in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5511": {
        "code": 5511,
        "desc": "The specified Object/Blobs value is invalid.",
        "first_action": "Add a valid Object/Blobs value in the recovery API. For",
        "full_action": "Add a valid Object/Blobs value in the recovery API. For\nmore information, go to the SORT website (https://sort.veritas.com/), and under\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5512": {
        "code": 5512,
        "desc": "Cannot retrieve any objects with the specified prefix.",
        "first_action": "AddavalidprefixintherecoveryAPI.Formoreinformation,",
        "full_action": "AddavalidprefixintherecoveryAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search for NetBackup Recovery API."
    },
    "5513": {
        "code": 5513,
        "desc": "Invalid destination bucket name provided.",
        "first_action": "Add a valid bucket in the recovery API. For more",
        "full_action": "Add a valid bucket in the recovery API. For more\ninformation,gototheSORTwebsite(https://sort.veritas.com/),andunderSupported\nProducts select NetBackup. Then search for NetBackup Recovery API."
    },
    "5514": {
        "code": 5514,
        "desc": "Specified destination object/Prefix name is not valid. NetBackup status codes 718 NetBackup status codes",
        "first_action": "Add a valid object/Prefix name in the recovery API.",
        "full_action": "Add a valid object/Prefix name in the recovery API.\nFormoreinformation,gototheSORTwebsite(https://sort.veritas.com/),andunder\nSupported Products select NetBackup. Then search for NetBackup Recovery\nAPI."
    },
    "5517": {
        "code": 5517,
        "desc": "Either the NetBackup version or the operating system of the recovery host does not meet the minimum requirements.",
        "first_action": "Review the operating system and version of the NetBackup media server.",
        "full_action": "Perform the following as appropriate:\n■ Review the operating system and version of the NetBackup media server.\n■ If the media server is RHEL, you must use NetBackup version 10.1 or later.\n■ If the media server is SUSE, you must use NetBackup version is 11.0.0.1\nor later.\n■ If the configuration does not meet these requirements, either upgrade the\nNetBackup media server or migrate the media server to a supported operating\nsystem.\n■ After you make the required changes, reconfigure the Cloud object store\ncredentials and retry the operation."
    },
    "5532": {
        "code": 5532,
        "desc": "Cannot retrieve storage unit information.",
        "first_action": "Ensure that the storage unit is up and running.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the storage unit is up and running.\n■ Restart the media server on which the storage unit is configured."
    },
    "5533": {
        "code": 5533,
        "desc": "The storage unit ANY is not supported for Cloud object store dynamic multistreaming.",
        "first_action": "Select a specific Policy storage option. Do not select the",
        "full_action": "Select a specific Policy storage option. Do not select the\noption ANY."
    },
    "5534": {
        "code": 5534,
        "desc": "Cannot complete the backup because of an invalid input.",
        "first_action": "ReviewtheActivitymonitorforthereasonforfailureand",
        "full_action": "ReviewtheActivitymonitorforthereasonforfailureand\ntake appropriate corrective action. Then retry the backup."
    },
    "5535": {
        "code": 5535,
        "desc": "Failed to stop backup operation.",
        "first_action": "Review the Activity monitor for the cause of the failure.",
        "full_action": "Review the Activity monitor for the cause of the failure.\nConfirm that the backup image was created and is recoverable. NetBackup\nautomatically cleans the stale data. If the backup image was created and is\nrecoverable, no further action is required."
    },
    "5536": {
        "code": 5536,
        "desc": "Failed to open the SQLite database.",
        "first_action": "Confirm that the temporary database is accessible and",
        "full_action": "Confirm that the temporary database is accessible and\nthat the NetBackup user has the necessary permissions. Then retry the backup."
    },
    "5537": {
        "code": 5537,
        "desc": "Incorrectreadorwritepermissionsarespecifiedforthedownloadstaging path.",
        "first_action": "Confirm that the NetBackup user has the correct",
        "full_action": "Confirm that the NetBackup user has the correct\npermissions to read and write the retry the backup."
    },
    "5538": {
        "code": 5538,
        "desc": "Incorrect ownership is specified for the download staging path.",
        "first_action": "Provide the correct ownership to the NetBackup user for",
        "full_action": "Provide the correct ownership to the NetBackup user for\nthe temporary staging area. The NetBackup user must have read, write, and run\npermissions to the specified folder. Then retry the backup."
    },
    "5540": {
        "code": 5540,
        "desc": "Backup performance is slowed as the staging space nears capacity.",
        "first_action": "Increase the amount of storage space available at the",
        "full_action": "Increase the amount of storage space available at the\nstaging location."
    },
    "5541": {
        "code": 5541,
        "desc": "Insufficient space at the specified staging location.",
        "first_action": "Confirm that the staging location has sufficient space and",
        "full_action": "Confirm that the staging location has sufficient space and\nthen retry the operation."
    },
    "5542": {
        "code": 5542,
        "desc": "The heartbeat listening service has timed out.",
        "first_action": "Review the Activity monitor for the causes of the failure",
        "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "5543": {
        "code": 5543,
        "desc": "The Cloud object store backup encountered an internal error.",
        "first_action": "Review the Activity monitor for the causes of the failure",
        "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "5544": {
        "code": 5544,
        "desc": "Backup failed as error occurred while fetching latest log object.",
        "first_action": "Review the Activity monitor for the causes of the failure",
        "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "5545": {
        "code": 5545,
        "desc": "Backup failed as NetBackup cannot parse records from the log object.",
        "first_action": "Review the Activity monitor for the causes of the failure",
        "full_action": "Review the Activity monitor for the causes of the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "5546": {
        "code": 5546,
        "desc": "Cannot retrieve the bucket logging information from the source bucket.",
        "first_action": "Review the configurations for the causes of the failure",
        "full_action": "Review the configurations for the causes of the failure\nand take appropriate corrective action. Then retry the backup."
    },
    "5547": {
        "code": 5547,
        "desc": "Backup failed due to an invalid marker, or error(s) in reading, writing, or extracting marker data.",
        "first_action": "Ensure that bucket logging is enabled, confirm that the",
        "full_action": "Ensure that bucket logging is enabled, confirm that the\npolicy is properly set on the target bucket, and retry the backup."
    },
    "5548": {
        "code": 5548,
        "desc": "An error occurred while fetching cloud object properties. NetBackup status codes 723 NetBackup status codes",
        "first_action": "Check the configuration, resolve the issue, and retry the",
        "full_action": "Check the configuration, resolve the issue, and retry the\nbackup."
    },
    "5549": {
        "code": 5549,
        "desc": "Cannot validate bucket logging information.",
        "first_action": "Each source bucket must have a unique prefix. The prefix cannot be empty.",
        "full_action": "Check the configuration and retry the backup operation.\nConfigurations should be like:\n■ Each source bucket must have a unique prefix. The prefix cannot be empty.\n■ The LoggingType attribute must be Journal.\n■ Set the TargetObjectKeyFormat attribute as PartitionedPrefix.\n■ Set the PartitionDateSource attribute as EventTime."
    },
    "5576": {
        "code": 5576,
        "desc": "The maximum number of concurrent jobs specified for a storage unit, must be greater than or equal to the number of streams specified in the policy.",
        "first_action": "Increase the concurrent jobs setting for the storage unit",
        "full_action": "Increase the concurrent jobs setting for the storage unit\nto match the number of streams specified in the policy."
    },
    "5577": {
        "code": 5577,
        "desc": "Cannot parse the specified field or object.",
        "first_action": "Check the Activity monitor for the exact reason for the",
        "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup."
    },
    "5578": {
        "code": 5578,
        "desc": "CannotretrievetheimageinfofromNetBackupdatabaseforthespecified field or object.",
        "first_action": "Check the Activity monitor for the exact reason for",
        "full_action": "Check the Activity monitor for the exact reason for\nmissing data. Resolve the issue, then retry the backup."
    },
    "5579": {
        "code": 5579,
        "desc": "Fallingbacktoobjectlistingforchangedetection,notconsideringobject change tracking for this bucket, specified in the policy.",
        "first_action": "Thereisnoworkaroundforthisissue.Forallthesereasons,",
        "full_action": "Thereisnoworkaroundforthisissue.Forallthesereasons,\nNetBackup uses object listing for change detection. NetBackup will revert to object\nchange tracking for the subsequent backups."
    },
    "5580": {
        "code": 5580,
        "desc": "The specified failover strategy for the storage unit group is incompatible with the Cloud object store policy, with dynamic multistreaming.",
        "first_action": "UseacompatiblestorageunitgroupwiththeCloudobject",
        "full_action": "UseacompatiblestorageunitgroupwiththeCloudobject\nstore policy.\nTo change storage unit selection\n1 In the NetBackup UI, on the left click Storage, and then click Storage units.\nClick the Storage unit group tab.\n2 Click Add to add a new storage unit, or edit an existing one.\n3 UnderStorageunitselectionoptions,selectanyoftheseoptionsasrequired:\nPrioritized, Round Robin, or Media Server Load Balancing.\nRetry the backup."
    },
    "5581": {
        "code": 5581,
        "desc": "Cannot parse the failed object file.",
        "first_action": "Check the Activity monitor for the exact reason for the",
        "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup."
    },
    "5582": {
        "code": 5582,
        "desc": "Cannot retrieve image handle.",
        "first_action": "Check the Activity monitor for the exact reason for the",
        "full_action": "Check the Activity monitor for the exact reason for the\nfailure. Resolve the issue, then retry the backup."
    },
    "5626": {
        "code": 5626,
        "desc": "After you upgrade both the source and the target master server, you must update the trust relationship on both of the servers. After you update the trust relationship, you can make configuration changes related to the trusted master servers.",
        "first_action": "Domainname domain_name -username username -fpfile filename",
        "full_action": "Run one of the following commands on both the source\nand the target master server.\nRun the following command if you are using user credentials; you are prompted to\nprovide the password:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -username username -fpfile filename\nRun the following command if you are using an authorization token; you are\nprompted to provide the token:\nnbseccmd -setuptrustedmaster -update -masterserver\nmaster_server_name -remotemasterserver remote_master_server\n-domainname domain_name -fpfile filename\nRun the following command if you are using the answer file:\nnbseccmd -setuptrustedmaster -update -info answer_file\nFormoreinformationaboutthenbseccmdcommand,seetheNetBackupCommands\nReference Guide."
    },
    "5631": {
        "code": 5631,
        "desc": "The source master server uses a NetBackup CA-signed certificate and the target master server uses an external CA-signed certificate. Configure an external certificate on the source master server, which should be compatible with the target master server. NetBackup status codes 727 NetBackup status codes",
        "first_action": "Ensure that you have configured an external certificate",
        "full_action": "Ensure that you have configured an external certificate\non the source master server that is compatible with the target master server."
    },
    "5761": {
        "code": 5761,
        "desc": "Failed to initialize Windows Socket library",
        "first_action": "None",
        "full_action": "None"
    },
    "5762": {
        "code": 5762,
        "desc": "Peer is not a NetBackup Master or Media Server",
        "first_action": "Verify that the requesting NetBackup server is indeed the",
        "full_action": "Verify that the requesting NetBackup server is indeed the\nmaster server as recognized by the NetBackup host returning this status code."
    },
    "5763": {
        "code": 5763,
        "desc": "Encountered error during socket communication",
        "first_action": "If NetBackup is otherwise functioning correctly, this error",
        "full_action": "If NetBackup is otherwise functioning correctly, this error\nrequires Cohesity Technical Support assistance."
    },
    "5764": {
        "code": 5764,
        "desc": "Command specified for execution is invalid or not allowed",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5765": {
        "code": 5765,
        "desc": "Failed to execute specified command (CreateProcess or exec)",
        "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,",
        "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support."
    },
    "5766": {
        "code": 5766,
        "desc": "Failed to execute specified command (fork)",
        "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,",
        "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support."
    },
    "5767": {
        "code": 5767,
        "desc": "Failed to get exit code of child process",
        "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact",
        "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support."
    },
    "5768": {
        "code": 5768,
        "desc": "Failed to read complete output of executed command",
        "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,",
        "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support."
    },
    "5769": {
        "code": 5769,
        "desc": "Failed to reap exit code of child process",
        "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact",
        "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support."
    },
    "5770": {
        "code": 5770,
        "desc": "Failed to get cluster configuration",
        "first_action": "None",
        "full_action": "None"
    },
    "5771": {
        "code": 5771,
        "desc": "Failed to write output received from remote command",
        "first_action": "Ifthiserrorisnottheresultofmanualintervention,contact",
        "full_action": "Ifthiserrorisnottheresultofmanualintervention,contact\nCohesity Technical Support."
    },
    "5772": {
        "code": 5772,
        "desc": "Failed to read unified logging configuration file",
        "first_action": "Check the existence and the format of the VxUL",
        "full_action": "Check the existence and the format of the VxUL\nconfigurationfilethatwasmentionedalongwiththeerrormessageonthespecified\nNetBackup host."
    },
    "5773": {
        "code": 5773,
        "desc": "Failed to get virtual name of primary server",
        "first_action": "None",
        "full_action": "None"
    },
    "5774": {
        "code": 5774,
        "desc": "Specified logs are not valid",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5775": {
        "code": 5775,
        "desc": "Invalid option specified",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5776": {
        "code": 5776,
        "desc": "Failed to spawn new process",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5777": {
        "code": 5777,
        "desc": "Failed to create staging directory on primary server",
        "first_action": "Verify that the specified path already exists. If not, try to",
        "full_action": "Verify that the specified path already exists. If not, try to\ncreate it manually."
    },
    "5778": {
        "code": 5778,
        "desc": "Failed to read Logging Assistant database",
        "first_action": "CheckpermissionsoftheLoggingAssistantdatabasefile:",
        "full_action": "CheckpermissionsoftheLoggingAssistantdatabasefile:\nUNIX: /usr/openv/var/global/logasst.db\nWindows: <Install Path>\\Veritas\\NetBackup\\var\\global\\logasst.db"
    },
    "5779": {
        "code": 5779,
        "desc": "Failed to lock Logging Assistant database",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5780": {
        "code": 5780,
        "desc": "Failed to set non-inherit flag on database file handle",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5781": {
        "code": 5781,
        "desc": "Failed to prepare to save Logging Assistant database",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5782": {
        "code": 5782,
        "desc": "Failed to start to write Logging Assistant database",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5783": {
        "code": 5783,
        "desc": "Failed to save Logging Assistant database",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5784": {
        "code": 5784,
        "desc": "Failed to access or write the readme or progress file",
        "first_action": "Please check the specified path.",
        "full_action": "Please check the specified path."
    },
    "5786": {
        "code": 5786,
        "desc": "Logging Assistant record does not exist",
        "first_action": "Refresh the Logging Assistant GUI, then check if the",
        "full_action": "Refresh the Logging Assistant GUI, then check if the\nrecord has been deleted."
    },
    "5787": {
        "code": 5787,
        "desc": "Logging Assistant record already exists",
        "first_action": "None",
        "full_action": "None"
    },
    "5788": {
        "code": 5788,
        "desc": "Debug logging has not been set up for Logging Assistant record",
        "first_action": "Refresh the Logging Assistant GUI view and retry.",
        "full_action": "Refresh the Logging Assistant GUI view and retry."
    },
    "5789": {
        "code": 5789,
        "desc": "Failed to interpret bpdbjobs output for job detail",
        "first_action": "Manually select the debug logging to set up. Contact",
        "full_action": "Manually select the debug logging to set up. Contact\nCohesity Technical Support to investigate the Job Analysis failure."
    },
    "5790": {
        "code": 5790,
        "desc": "Failed to fetch PureDisk configuration setting from Windows registry",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5794": {
        "code": 5794,
        "desc": "Failed to calculate debug logs size for preview",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5796": {
        "code": 5796,
        "desc": "LoggingAssistantagentencounteredfailurewritingonsockettoprimary server",
        "first_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,",
        "full_action": "RetrytheLoggingAssistantaction.Iftheproblempersists,\ncontact Cohesity Technical Support."
    },
    "5798": {
        "code": 5798,
        "desc": "Failed to list disk volumes on primary server using bpmount",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish free space information and initiate the\nintended action such as log collection."
    },
    "5799": {
        "code": 5799,
        "desc": "Failed to get disk space information of volumes or mount points",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport.\nYou may still be able to manually establish free space information and initiate the\nintended action such as log collection."
    },
    "5800": {
        "code": 5800,
        "desc": "Failed to execute bpdbjobs to fetch job details",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "5801": {
        "code": 5801,
        "desc": "Failed to fetch job details. Check if job exists.",
        "first_action": "IfthespecifiedjobIDdoesexist,contactCohesityTechnical",
        "full_action": "IfthespecifiedjobIDdoesexist,contactCohesityTechnical\nSupport."
    },
    "5803": {
        "code": 5803,
        "desc": "Failed to modify PureDisk configuration file",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5804": {
        "code": 5804,
        "desc": "Failed to modify Java GUI configuration file (Debug.properties)",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5805": {
        "code": 5805,
        "desc": "RemotehostNetBackupversionnotsupportedbytheLoggingAssistant",
        "first_action": "None",
        "full_action": "None"
    },
    "5806": {
        "code": 5806,
        "desc": "Unexpected contents of PureDisk configuration file (pdregistry.cfg)",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5807": {
        "code": 5807,
        "desc": "Failed to copy nbcplogs/nbsu output file from remote host",
        "first_action": "Check that the connection from the master server to bpcd",
        "full_action": "Check that the connection from the master server to bpcd\ncan be set up by using bptestbpcd."
    },
    "5808": {
        "code": 5808,
        "desc": "Failed to load PBX configuration to change log level NetBackup status codes 737 NetBackup status codes",
        "first_action": "Check the existence and format of the PBX configuration",
        "full_action": "Check the existence and format of the PBX configuration\nfile and the error message on the specified NetBackup host."
    },
    "5809": {
        "code": 5809,
        "desc": "Invalid PBX Debug Log Level specified",
        "first_action": "Set the PBX logging level to an appropriate value.",
        "full_action": "Set the PBX logging level to an appropriate value."
    },
    "5811": {
        "code": 5811,
        "desc": "Temporary directory to use for logs collection does not exist",
        "first_action": "Check the directory permissions on the NetBackup host.",
        "full_action": "Check the directory permissions on the NetBackup host.\nAlso verify that the parent directory of the specified temporary directory exists."
    },
    "5812": {
        "code": 5812,
        "desc": "Nbcplogs exited with error",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5813": {
        "code": 5813,
        "desc": "Nbcplogs did not collect any logs",
        "first_action": "Check that the debug logs on the host are available to",
        "full_action": "Check that the debug logs on the host are available to\ncollect. If the debug logs relevant to the Logging Assistant record exist on the host,\ncontact Cohesity Technical Support."
    },
    "5814": {
        "code": 5814,
        "desc": "Nbsu exited with error",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "5815": {
        "code": 5815,
        "desc": "No activity for the Logging Assistant record is in progress",
        "first_action": "Refresh the Logging Assistant GUI and retry.",
        "full_action": "Refresh the Logging Assistant GUI and retry."
    },
    "5816": {
        "code": 5816,
        "desc": "Collect debug logs operation canceled",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "5817": {
        "code": 5817,
        "desc": "Collect nbsu operation canceled.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "5819": {
        "code": 5819,
        "desc": "Cancel operation requested",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "5820": {
        "code": 5820,
        "desc": "Not a valid Logging Assistant temporary directory for clean-up",
        "first_action": "Enter a valid Logging Assistant temporary directory and",
        "full_action": "Enter a valid Logging Assistant temporary directory and\nretry the operation. If the issue persists, visit support.veritas.com. The Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue."
    },
    "5821": {
        "code": 5821,
        "desc": "Failed to get policy details",
        "first_action": "Iftheassociatedpolicydoesexist,pleasecontactCohesity",
        "full_action": "Iftheassociatedpolicydoesexist,pleasecontactCohesity\nTechnical Support."
    },
    "5902": {
        "code": 5902,
        "desc": "Fingerprint of the certificate could not be generated.",
        "first_action": "Run the nbcertcmd -getCACertificate command and",
        "full_action": "Run the nbcertcmd -getCACertificate command and\ntry to generate the CA certificate again."
    },
    "5903": {
        "code": 5903,
        "desc": "CA certificate could not be verified.",
        "first_action": "The NetBackup host must trust the CA. Check if the CA",
        "full_action": "The NetBackup host must trust the CA. Check if the CA\ncertificate was added to the trust store with the nbcertcmd -listCACertDetails\ncommand.Runthenbcertcmd -getCACertificatecommandtoaddthecertificate\nto the trust store.\nIf the trust store has multiple certificates with the same (generic) name, contact\nCohesity Technical Support."
    },
    "5904": {
        "code": 5904,
        "desc": "Internal error.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5905": {
        "code": 5905,
        "desc": "The host ID is not valid. NetBackup status codes 741 NetBackup status codes",
        "first_action": "ListCertDetails command. If the specified NetBackup host is part of multiple",
        "full_action": "Check the specified host ID using the nbcertcmd\n-listCertDetails command. If the specified NetBackup host is part of multiple\nNetBackup domains, ensure that you are providing the correct host ID that\ncorresponds to the specified NetBackup domain."
    },
    "5906": {
        "code": 5906,
        "desc": "The token is not valid.",
        "first_action": "Redo the action. If the problem continues, save all of the",
        "full_action": "Redo the action. If the problem continues, save all of the\nerror log information and contact Cohesity Technical Support."
    },
    "5907": {
        "code": 5907,
        "desc": "Unknown resource requested.",
        "first_action": "Verify the certificate details that you provided. Details can",
        "full_action": "Verify the certificate details that you provided. Details can\ninclude a serial number, host ID, or host name."
    },
    "5908": {
        "code": 5908,
        "desc": "Unknown error occurred.",
        "first_action": "Save the error log information for the nbcert log and",
        "full_action": "Save the error log information for the nbcert log and\ncontact Cohesity Technical Support."
    },
    "5909": {
        "code": 5909,
        "desc": "Token does not exist for this token value.",
        "first_action": "Provide the correct token value and rerun the operation.",
        "full_action": "Provide the correct token value and rerun the operation."
    },
    "5910": {
        "code": 5910,
        "desc": "Host name is not specified.",
        "first_action": "Rerun the operation. If the problem continues, save all of",
        "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5913": {
        "code": 5913,
        "desc": "A token with this name already exists.",
        "first_action": "Provide a new name and then recreate the token.",
        "full_action": "Provide a new name and then recreate the token."
    },
    "5914": {
        "code": 5914,
        "desc": "The security service is not available.",
        "first_action": "Check the network connectivity of the host on which you",
        "full_action": "Check the network connectivity of the host on which you\nare performing the operation. Contact the NetBackup administrator to correct the\nstatus of the NetBackup web service."
    },
    "5915": {
        "code": 5915,
        "desc": "Request timed out.",
        "first_action": "Check the network connectivity of the host on which you",
        "full_action": "Check the network connectivity of the host on which you\nare performing the operation. Contact the NetBackup administrator to correct the\nstatus of the NetBackup web service."
    },
    "5916": {
        "code": 5916,
        "desc": "Token name is not specified.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5917": {
        "code": 5917,
        "desc": "The reissue token cannot have the usage count greater than one.",
        "first_action": "Amulti-usetokencannotbeassociatedwiththehost.The",
        "full_action": "Amulti-usetokencannotbeassociatedwiththehost.The\nre-issue token cannot be a multi-use token. Take appropriate action and generate\nthe required token."
    },
    "5918": {
        "code": 5918,
        "desc": "The maximum usage count for the token should be provided within the valid range, which is from 1 to 99999.",
        "first_action": "Select a valid usage count.",
        "full_action": "Select a valid usage count."
    },
    "5919": {
        "code": 5919,
        "desc": "Validity period specified for this token is not valid. The maximum validity period that you can specify is 999 days.",
        "first_action": "Select a valid period.",
        "full_action": "Select a valid period."
    },
    "5920": {
        "code": 5920,
        "desc": "The specified token is associated with a different host name.",
        "first_action": "Verify that you are using the correct token. If the specified",
        "full_action": "Verify that you are using the correct token. If the specified\nNetBackup host is associated with multiple NetBackup domains, ensure that you\nare using the token that corresponds to the appropriate NetBackup domain."
    },
    "5921": {
        "code": 5921,
        "desc": "The specified token is associated with a different host ID.",
        "first_action": "Verify that you are using the correct token.",
        "full_action": "Verify that you are using the correct token."
    },
    "5922": {
        "code": 5922,
        "desc": "The reissue token cannot be associated with the host name.",
        "first_action": "Use either the host ID or the host name and try to",
        "full_action": "Use either the host ID or the host name and try to\nregenerate the token."
    },
    "5925": {
        "code": 5925,
        "desc": "The required data is missing.",
        "first_action": "Ensure that all of the required inputs provided are correct",
        "full_action": "Ensure that all of the required inputs provided are correct\nandretrytheoperation.Iftheproblemcontinues,savealloftheerrorloginformation\nand contact Cohesity Technical Support."
    },
    "5926": {
        "code": 5926,
        "desc": "Certificate signing request is not valid.",
        "first_action": "Regeneratethecertificaterequestfile,reruntheoperation,",
        "full_action": "Regeneratethecertificaterequestfile,reruntheoperation,\nand ensure that the data has not changed in transit."
    },
    "5927": {
        "code": 5927,
        "desc": "The specified file could not be opened.",
        "first_action": "Use a valid file name and try to open the file or check",
        "full_action": "Use a valid file name and try to open the file or check\npermissions."
    },
    "5929": {
        "code": 5929,
        "desc": "The certificate is not in the Active state, so it cannot be renewed.",
        "first_action": "Send the certificate re-issue request after performing",
        "full_action": "Send the certificate re-issue request after performing\ncorrective actions. If you want to use the same credential (key pair), then the new\ncertificate can be generated using the re-issue token. You can use the following\ncommand:\nnbcertcmd -getCertificate\nIfyouplantochangecredentials,seetheNetBackupSecurityandEncryptionGuide\nfor workflow details."
    },
    "5930": {
        "code": 5930,
        "desc": "The request could not be authorized.",
        "first_action": "Logintype WEB command to get a web authentication token.",
        "full_action": "Useare-issuetokenwiththenbcertcmd -getCertificate\ncommand. If the user has not been authenticated, use the bpnbat -login\n-logintype WEB command to get a web authentication token."
    },
    "5931": {
        "code": 5931,
        "desc": "The host ID is empty.",
        "first_action": "Resend the request. If the problem continues, save all of",
        "full_action": "Resend the request. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5932": {
        "code": 5932,
        "desc": "Token usage count is not set.",
        "first_action": "Generate a token with valid parameters. The allowable",
        "full_action": "Generate a token with valid parameters. The allowable\ncount is from 1 to 99, 999."
    },
    "5933": {
        "code": 5933,
        "desc": "The maximum token usage limit has been reached.",
        "first_action": "Create a new token.",
        "full_action": "Create a new token."
    },
    "5934": {
        "code": 5934,
        "desc": "The token has expired.",
        "first_action": "Create a new token.",
        "full_action": "Create a new token."
    },
    "5936": {
        "code": 5936,
        "desc": "The specified token name is not in a valid format.",
        "first_action": "Specify a valid token name. The valid characters are A-Z,",
        "full_action": "Specify a valid token name. The valid characters are A-Z,\na-z, 0-9, and _."
    },
    "5938": {
        "code": 5938,
        "desc": "The revocation reason code is not valid.",
        "first_action": "Specify a valid reason code and then try to revoke the",
        "full_action": "Specify a valid reason code and then try to revoke the\ncertificate."
    },
    "5939": {
        "code": 5939,
        "desc": "This revocation reason code is not supported by the server.",
        "first_action": "Specify a valid reason code and then try to revoke the",
        "full_action": "Specify a valid reason code and then try to revoke the\ncertificate."
    },
    "5940": {
        "code": 5940,
        "desc": "Reissue token is mandatory; please provide a reissue token.",
        "first_action": "Generate a reissue token for the required host and then",
        "full_action": "Generate a reissue token for the required host and then\nrequest a certificate reissue. Use the following command (or the NetBackup\nAdministration Console) to generate the reissue token:\nnbcertcmd -createToken -name name_of_token -reissue\n[-host host_name | -hostId host_id]"
    },
    "5941": {
        "code": 5941,
        "desc": "The host ID is not associated with any host.",
        "first_action": "VerifythatthespecifiedhostIDcorrespondstothespecified",
        "full_action": "VerifythatthespecifiedhostIDcorrespondstothespecified\nmaster server. Use the nbcertcmd -listCertDetails command on the specified\nNetBackup host to find the host ID that corresponds to the specified master server."
    },
    "5942": {
        "code": 5942,
        "desc": "Certificate could not be read from the local certificate store.",
        "first_action": "The external certificate that is specified in bp.conf/registry against",
        "full_action": "Checkifyouhaveadministratorprivilegesonthespecified\nNetBackup host. If you have the required privileges, use the -force option with the\nnbcertcmd -getCertificate command to regenerate the existing certificate. You\nmay have to supply a token with this command, depending on the certificate\ndeployment security levels specified on the master server.\nIf external CA signed certificate is used for communication, it may be lost or\ncorrupted. Try the following:\n■ The external certificate that is specified in bp.conf/registry against\nECA_CERT_PATH key may be lost or corrupted. Make sure that the provided\ncertificate path is in the correct format. Review the value that is set for the\nECA_CERT_PATH configuration option, check if it has the required access\npermissions, and it is accessible."
    },
    "5943": {
        "code": 5943,
        "desc": "Lock cannot be acquired on the file for writing.",
        "first_action": "Rerun the operation. If the problem continues, save all of",
        "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5944": {
        "code": 5944,
        "desc": "The host alias list has multiple host names. NetBackup status codes 750 NetBackup status codes",
        "first_action": "Specifyasinglehostnameinthecertificatesigningrequest",
        "full_action": "Specifyasinglehostnameinthecertificatesigningrequest\nand resend the request to the master server."
    },
    "5945": {
        "code": 5945,
        "desc": "Host alias is not specified.",
        "first_action": "Specify a host name in the certificate signing request and",
        "full_action": "Specify a host name in the certificate signing request and\nresend the request to the master server."
    },
    "5946": {
        "code": 5946,
        "desc": "Token is mandatory; please provide a token.",
        "first_action": "Generate an authorization token and then run the",
        "full_action": "Generate an authorization token and then run the\nnbcertcmd -getCertificate command to request a certificate."
    },
    "5947": {
        "code": 5947,
        "desc": "The host is not registered with the server.",
        "first_action": "Specifythecorrecthostnameor use a validauthorization",
        "full_action": "Specifythecorrecthostnameor use a validauthorization\ntoken and rerun the operation."
    },
    "5948": {
        "code": 5948,
        "desc": "Certificate could not be written to the local certificate store. NetBackup status codes 751 NetBackup status codes",
        "first_action": "Check if you have administrator privileges on the given",
        "full_action": "Check if you have administrator privileges on the given\nNetBackup host. If you have the required privileges, redo the action. If the problem\ncontinues, save all of the error log information and contact Cohesity Technical\nSupport."
    },
    "5949": {
        "code": 5949,
        "desc": "Certificate does not exist.",
        "first_action": "Ensure that the appropriate certificate is deployed. See",
        "full_action": "Ensure that the appropriate certificate is deployed. See\nthe NetBackup Security and Encryption Guide for details on how to deploy\ncertificates."
    },
    "5950": {
        "code": 5950,
        "desc": "Certificate already exists.",
        "first_action": "Usethenbcertcmd -getCertificate -forcecommand",
        "full_action": "Usethenbcertcmd -getCertificate -forcecommand\nto overwrite the existing certificate, if required."
    },
    "5953": {
        "code": 5953,
        "desc": "The certificate deployment level is not valid.",
        "first_action": "Select a certificate deployment level between 0 - 2 and",
        "full_action": "Select a certificate deployment level between 0 - 2 and\nrerun the command to set the certificate deployment level. For more information\noncertificatedeploymentlevels,seetheNetBackupSecurityandEncryptionGuide."
    },
    "5954": {
        "code": 5954,
        "desc": "Thehostnamecouldnotberesolvedtotherequestinghost'sIPaddress.",
        "first_action": "Verify and correct your network configurations so that the",
        "full_action": "Verify and correct your network configurations so that the\nmaster server can resolve the host name to the peer IP address. Alternatively, you\ncan use an authorization token to deploy the certificate."
    },
    "5955": {
        "code": 5955,
        "desc": "The host name is not known to the primary server.",
        "first_action": "Ensure that the host entry exists on one of the following",
        "full_action": "Ensure that the host entry exists on one of the following\nlocations: the server configuration list, the EMM database, at least 1 catalog image\n(not more than 6 months old), the clients listed in policies, or the client DB entry.\nAlternatively, you can use an authorization token to deploy the certificate."
    },
    "5956": {
        "code": 5956,
        "desc": "The existing certificate deployment level on the primary server does not allow this operation.",
        "first_action": "GetCertificate option.",
        "full_action": "If you see this error message while you are retrieving the\nhost ID-based certificate, ensure that you use a valid authorization token with the\n-getCertificate option."
    },
    "5957": {
        "code": 5957,
        "desc": "The primary server is unable to connect to the CA.",
        "first_action": "Check the status of the NetBackup AT broker on the",
        "full_action": "Check the status of the NetBackup AT broker on the\nprimary server. Restart the service, if required."
    },
    "5958": {
        "code": 5958,
        "desc": "The primary server is unable to access the CA certificate.",
        "first_action": "Ensure that the web service user has the required",
        "full_action": "Ensure that the web service user has the required\npermissions to read the CA certificate on the primary server."
    },
    "5959": {
        "code": 5959,
        "desc": "The NetBackup AT credentials of the web service user are not valid.",
        "first_action": "Stop the web service on the master server, run the",
        "full_action": "Stop the web service on the master server, run the\nnbcertconfig -u -user webservice_usercommand,andrestartthewebservice."
    },
    "5960": {
        "code": 5960,
        "desc": "NetBackupATconfigurationontheprimaryservercouldnotbeinitialized.",
        "first_action": "Ensure that the web service user has the required",
        "full_action": "Ensure that the web service user has the required\npermissions to access the certificate store on the primary server."
    },
    "5962": {
        "code": 5962,
        "desc": "The host name does not match the existing name in the certificate.",
        "first_action": "1. The NetBackup host administrator should ask the NetBackup administrator to",
        "full_action": "If the NetBackup host administrator wants to get the\ncertificate for the given host with the new name, then perform the following steps:\n1. The NetBackup host administrator should ask the NetBackup administrator to\nrevoke the certificate of the host by using the -host host_name | -hostId\nhost_idoptions.TheNetBackupadministratorcanusethefollowingcommand:\nnbcertcmd -revokeCertificate -reasonCode value\n-host old_host_name | -hostId host_id\n2. The NetBackup host administrator should ask the NetBackup administrator to\ngenerate a reissue token for a specific host. The NetBackup administrator can\nuse the following command:\nnbcertcmd -createToken -name token_name -reissue\n-host old_host_name | -hostId host_id\n3. AftertheNetBackuphostadministratorreceivesthereissuetoken,thefollowing\ncommand can be used (specify the received token when prompted):\nnbcertcmd -getCertificate -token -force"
    },
    "5963": {
        "code": 5963,
        "desc": "Entity does not exist.",
        "first_action": "Checkthattheargumentvaluessuppliedinthecommand",
        "full_action": "Checkthattheargumentvaluessuppliedinthecommand\nare correct."
    },
    "5964": {
        "code": 5964,
        "desc": "Data conversion error.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5965": {
        "code": 5965,
        "desc": "The host ID associated with this reissue token is assigned to another host. Before you can reuse the host ID for this host, revoke the existing certificate associated with the host ID and map this host name to the host ID.",
        "first_action": "The user must revoke the current certificate with the",
        "full_action": "The user must revoke the current certificate with the\nexisting host name and then use the reissue token to request a certificate using\nthe new host name."
    },
    "5966": {
        "code": 5966,
        "desc": "The host has an active certificate. You need to revoke the certificate before you can disassociate the host from its host ID.",
        "first_action": "The user must revoke the certificate for this host and only",
        "full_action": "The user must revoke the certificate for this host and only\nthen mark it as decoupled from the associated host ID."
    },
    "5967": {
        "code": 5967,
        "desc": "The file already exists. NetBackup status codes 756 NetBackup status codes",
        "first_action": "The user can rename/move/delete the existing file or",
        "full_action": "The user can rename/move/delete the existing file or\nsubmit a new file name."
    },
    "5968": {
        "code": 5968,
        "desc": "The host information could not be retrieved while creating the certificate signing request.",
        "first_action": "Retry the current operation.",
        "full_action": "Try the following possible solutions:\n■ Retry the current operation.\n■ Retry the current operation by restarting the system.\n■ If the problem persists, contact Cohesity Technical Support."
    },
    "5969": {
        "code": 5969,
        "desc": "ResponsefromtheNetBackupWebManagementConsoleservicecould not be parsed.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5970": {
        "code": 5970,
        "desc": "The server time could not be fetched.",
        "first_action": "Rerun the operation. If the problem continues, save all of",
        "full_action": "Rerun the operation. If the problem continues, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5971": {
        "code": 5971,
        "desc": "The token contains characters that are not supported.",
        "first_action": "Checkthetokenvaluepassedinthetokenfileandensure",
        "full_action": "Checkthetokenvaluepassedinthetokenfileandensure\nthat it contains valid characters (A-Z, a-z, and 0-9). Ensure that the file encoding\nformat is ANSI."
    },
    "5972": {
        "code": 5972,
        "desc": "The certificate could not be revoked. It was already revoked or expired.",
        "first_action": "Specify the active certificate and then try to revoke the",
        "full_action": "Specify the active certificate and then try to revoke the\ncertificate."
    },
    "5973": {
        "code": 5973,
        "desc": "The token type is not valid.",
        "first_action": "0 - Default token",
        "full_action": "Specify one of the following token types:\n■ 0 - Default token\n■ 1 - Reissue token\nIf you have not provided the token type, the default token type (0) is automatically\nselected."
    },
    "5974": {
        "code": 5974,
        "desc": "The specified token requires a host ID.",
        "first_action": "Provide a host ID of the host for which you want to create",
        "full_action": "Provide a host ID of the host for which you want to create\na token."
    },
    "5976": {
        "code": 5976,
        "desc": "The passphrase must contain a minimum of 8 and a maximum of 20 characters.",
        "first_action": "Specifyapassphrasewithaminimumof8andamaximum",
        "full_action": "Specifyapassphrasewithaminimumof8andamaximum\nof 20 characters."
    },
    "5977": {
        "code": 5977,
        "desc": "The existing passphrase and the new passphrase must be different.",
        "first_action": "Specify a passphrase that is different than the existing",
        "full_action": "Specify a passphrase that is different than the existing\none."
    },
    "5978": {
        "code": 5978,
        "desc": "Failed to refresh the certificate revocation list (CRL) and security level.",
        "first_action": "Failed to save the CRL on the disk",
        "full_action": "Failed to fetch the CRL via the HTTP request\n■ Failed to save the CRL on the disk\n■ Failed to fetch the security level via the HTTP request\n■ Failedtoupdatethecertmapinfo.jsonwithCRLandsecuritylevelinformation\n■ Failed to get the CRL because a client in the DMZ could not connect to the\nHTTP tunnel on the media server\nRecommended Action: Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On the media server, examine the pbx (OID 103), nbpxytnl (OID 490), and\nnbpxyhelper (OID 486) logs. pbx is logged to the following directories:\nWindows: install_path\\VxPBX\\log\nUNIX: /opt/VRTSpbx/log\n■ Ensure that the following are online:\n■ NetBackup Master server\n■ NetBackup Web Management Console service (nbwmc)\n■ NetBackup relational database (NBDB)\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd."
    },
    "5979": {
        "code": 5979,
        "desc": "The certificate revocation list (CRL) in the certificate is invalid.",
        "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.",
        "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\nUse these logs to help troubleshoot issues that appear in the web services.\n■ On the master server, examine the unified logs for nbwebservice (OIDs 466\nand 484).\n■ Restart the services on the master server. Then, retry the following command\nfor the host to fetch the CRL:\n./nbcertcmd -getCrl"
    },
    "5980": {
        "code": 5980,
        "desc": "The security level in the certificate is invalid.",
        "first_action": "On the master server, examine the unified logs on the NetBackup server for",
        "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Run the following command for the host to fetch the CRL and the security level:\n./nbcertcmd -getCrl"
    },
    "5982": {
        "code": 5982,
        "desc": "The certificate revocation list (CRL) is unavailable.",
        "first_action": "Retry the command or operation.",
        "full_action": "Do the following, as appropriate:\nFor Scenario 1, do the following:\n■ Retry the command or operation.\n■ Verify that nbatd is running on the master server, then retry the operation.\n■ Restart the services on the master server, then retry the operation.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (all OIDs).\n■ On the master server and on the host where the error occurred, examine the\nunified logs for nbatd (OID 18).\nFor Scenario 2, do the following:\n■ Run the following command for the master server and then retry the operation:\n./nbcertcmd -getCrl -server master server name\n■ On all hosts that are involved in the communication, examine the unified logs\nfor nbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ (Scenario 3) NetBackup is not configured with correct CRL path or certificate\ndoes not contain a valid CDP.\n■ If the ECA_CRL_PATH setting is specified in the NetBackup configuration file,\nensure the following:\n■ The ECA_CRL_PATH has the correct CRL directory path.\n■ The CRL directory contains CRLs for all required certificate issuers (as\nper ECA_CRL_CHECK setting).\n■ The CRL is in PEM or DER format.\n■ The CRL is not expired.\n■ The CRL last update date is not a future date.\n■ If the CDP is used, do the following when appropriate:\n■ Make sure that the certificate has at least one CDP (with HTTP/HTTPS\nprotocol) that points to a CRL that includes revocation information for all\nreasons.\n■ CDP URL is accessible.\n■ (Scenario 4) The host does not have a CRL cached in NetBackup CRL cache.\n■ If ECA_CRL_PATH setting is specified in the NetBackup configuration file, run\nthe following command on all hosts that are involved in the communication\nand retry the operation:\n./nbcertcmd -updateCRLCache\n■ If bpclntcmd is running, terminate it (bpclntcmd -terminate) and retry the\noperation.\n■ Set VERBOSE and ENABLE_NBCURL_VERBOSE (0|1).\n■ Examine the logs for bpclntcmd.\n■ On all hosts that are involved in the communication, examine the unified\nlogs for nbpxyhelper (OID 486).\n■ Onthehostwheretheerroroccurred,examinethelegacylogsfornbcertcmd."
    },
    "5983": {
        "code": 5983,
        "desc": "The host certificate is revoked.",
        "first_action": "Onthehostwheretheerroroccurred,examinethelegacylogsontheNetBackup",
        "full_action": "Do the following, as appropriate:\n■ Onthehostwheretheerroroccurred,examinethelegacylogsontheNetBackup\nserver for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ If the certificate was revoked in error, reissue a certificate for the host.\n■ If the certificate was revoked as intended, an attempted security breach may\nhave occurred.\n■ Contact your Security Administrator.\n■ To reissue a certificate for the host, see the NetBackup Security and Encryption\nGuide."
    },
    "5986": {
        "code": 5986,
        "desc": "Certificaterequestforhostwasrejectedasthehostcouldnotbevalidated as a primary server.",
        "first_action": "Ensure that you do not send the master server-specific",
        "full_action": "Ensure that you do not send the master server-specific\nparameters when you deploy the certificate on a non-master server host."
    },
    "5987": {
        "code": 5987,
        "desc": "CouldnotfetchthehostIDoftheNetBackupprimaryserver.Theprimary server may not have the certificate.",
        "first_action": "NBSL is running on the master server",
        "full_action": "Ensure that the following occurs:\n■ NBSL is running on the master server\n■ IfNBSLisrunningonthemasterserver,ensurethatthehostID-basedcertificate\nis deployed on the master server\n■ If the host ID-based certificate is deployed and if you still see this error, refer to\nthe Resolving the master server host name change issue procedure..\nResolving the master server host name change issue\nThiserrormayoccurifthemasterserverhostnameischangedfromaFullyQualified\nDomain Name (FQDN) to a short name (or vice versa) in any of the following\nscenarios:\n■ NetBackup installation after a disaster\n■ Manual update in the NetBackup configuration file (bp.conf file on the UNIX or\nWindows registry).\nIn the following example, NetBackup is installed on a master server with a short\nname and the catalog backup is run. After a disaster, NetBackup is installed on the\nmaster server in a disaster recovery mode, but this time with FQDN. However, the\nidentity of the master server (or disaster recovery package) is restored with the\nshort name. This can cause failure when reissuing the client certificates,\nautomatically renewing the client certificates and deploying new certificates on\nclients.\nTo resolve this issue, use the following steps:\n1. Log on to the master server.\n2. Run following command:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -ping\nWindows:\nInstall_path\\NetBackup\\bin\\nbcertcmd -ping\n■ If the command is executed successfully, proceed to next step.\n■ If it fails with the exist status code 8509 (The specified server name was\nnot found in the web service certificate), then carry out the steps that are\nprovided in the following technote:\nhttps://www.veritas.com/support/en_US/article.100034092\nProceed to the next step.\n3. StopandstarttheNetBackupWebManagementConsoleserviceonthemaster\nserver. Use following the NetBackup command:\nUNIX:\n/usr/openv/netbackup/bin/nbwmc -terminate\n/usr/openv/netbackup/bin/nbwmc -start\nWindows:\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -stop -srvname \"NetBackup\nWeb Management Console\"\ninstall_path\\NetBackup\\wmc\\bin\\nbwmc.exe -start -srvname\n\"NetBackup Web Management Console\"\n4. Perform the user login on the master server. Use the following command:\ninstall_path/netbackup/bin/bpnbat -login -loginType WEB\nFor example:\ninstall_path\\netbackup\\bin\\bpnbat -login -loginType WEB\nAuthentication Broker [abc.example.com is default]:\nAuthentication port [0 is default]:\nAuthentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap) [WINDOWS is default]:\nDomain [abc.example.com is default]:\nLogin Name [administrator is default]:\nPassword:\nOperation completed successfully.\n5. Note the value of the key Client_Name for the master server. For a clustered\nmaster server, note the value of the key Cluster_Name This can be found at\nthe following locations:\nUNIX:/usr/openv/netbackup/bp.conf\nWindows:HKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Config\nThis value can either be the FQDN or the short name. For example,\nabc.example.com.\n6. Note the host ID of the master server. You can obtain its value by using the\nfollowing command:\ninstall_path/netbackup/bin/nbcertcmd -listCertDetails\nFor a clustered master setup, use the following command:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails -cluster\nThis command may return multiple records (if only one record is returned,\nselect the host ID provided in that record).\n■ If the host name obtained in step 5 is FQDN, then pick the record where\nthe “Issued By” entry matches its short name.\n■ If the host name obtained in step 5 is a short name, then pick the record\nwhere the “Issued By” entry matches its FQDN.\nFor example:\ninstall_path\\netbackup\\bin\\nbcertcmd -listCertDetails\nMaster Server : abc\nHost ID : xxxxxx-4201-4c6a-xxxx-xxxxx\nIssued By : /CN=broker/OU=root@abc/O=vx\nSerial Number : 0x62e108c90000000c\nExpiry Date : Aug 21 08:42:54 2018 GMT\nSHA1 Fingerprint : 50:89:AE:66:12:9A:29:4A:66:E9:DB:71:37:\nC7:EA:94:8C:C6:0C:A0\nMaster Server : xyz\nHost ID : yyyyyy-4785-4252-yyyy-yyyyy\nIssued By : /CN=broker/OU=root@xyz.master1.com/O=vx\nSerial Number : 0x6ede87a70000000a\nExpiry Date : Aug 21 09:52:13 2018 GMT\nSHA1 Fingerprint : FE:08:C2:09:AC:5D:82:57:7A:96:5C:C1:4A:\nE6:EC:CA:CC:99:09:D2\nOperation completed successfully.\nHere, 2 records are returned. For the first record, the issuer name provided in\nthe “Issued By” field matches the short name of the client_name obtained in\nstep 5. Select the host ID that appears in the first record.\n7. Add a host ID-to-host name mapping. Map the host ID of the master server\nthat you have obtained in step 6 to the host name that you have obtained in\nstep 5.\nUse the following command:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -a -i host_ID -hm\nhost_name\nFor example:\ninstall_path/netbackup/bin/admincmd/nbhostmgmt -a -i\nxxxxxx-4201-4c6a-xxxx-xxxxx -hm abc.example.com\nabc.example.com is successfully mapped to xxxxxx-4201-4c6a-xxxx-xxxxx.\nYou can also add this host ID-to-host name mapping using the NetBackup\nAdministrationConsole.UsetheSecurityManagement>HostManagement\n> Hosts tab.\n8. RenewthehostID-basedcertificateofthemasterserverbyusingthefollowing\ncommand:\ninstall_path/netbackup/bin/nbcertcmd -renewCertificate\nFor a clustered master server, use the following command:\ninstall_path\\netbackup\\bin\\nbcertcmd -renewCertificate -cluster\n9. Continuewiththecertificatedeploymentonaclient(thiscanbeeitherareissue\ncertificate, the automatic renewal of a certificate, or a new certificate\ndeployment)."
    },
    "5988": {
        "code": 5988,
        "desc": "The host name is not part of the host ID-to-host name mapping list.",
        "first_action": "Map the host name to the associated host ID. In the",
        "full_action": "Map the host name to the associated host ID. In the\nNetBackup Administration Console, use the Security Management > Host\nManagement > Hosts tab or the nbhostmgmt command to add mappings."
    },
    "5989": {
        "code": 5989,
        "desc": "The reissue token is mandatory as a certificate was already issued to this host. Revoke the existing certificate if it is active and map this host name to the associated host ID. NetBackup status codes 767 NetBackup status codes",
        "first_action": "If the host has an active certificate, revoke it.",
        "full_action": "To deploy a certificate using this new name, you need to\nprovide a reissue token for the existing host ID. For successful re-installation using\nthe new host name, ensure the following:\n■ If the host has an active certificate, revoke it.\n■ The host names are mapped to the associated host ID. In the NetBackup\nAdministrationConsole,usetheSecurityManagement>HostManagement\n> Hosts tab or the nbhostmgmt command to add mappings.\n■ The client name for the host matches the primary host name associated with\nthe issued host ID.\nNote: If you want to deploy a certificate on a host with a host name that matches\nan existing host ID-to-host name mapping of another host, you must either delete\nthe existing host ID-to-host name mapping and retry the operation or add a new\nhost in the host database.\nFor more information on how to add a host, see the NetBackup Security and\nEncryption Guide."
    },
    "5990": {
        "code": 5990,
        "desc": "The specified host ID-to-host name mapping is shared by multiple hosts and the auto reissue certificate parameter is set for two or more hosts.",
        "first_action": "Inthecaseofsharedmapping,ensurethattheautoreissue",
        "full_action": "Inthecaseofsharedmapping,ensurethattheautoreissue\ncertificate parameter is set only for the required host. You can reset the parameter\nfor other hosts by running the following command:\nnbhostmgmt -allowautoReissueCert -autoReissue 0\nAlternatively, you can use the NetBackup Administration Console."
    },
    "5991": {
        "code": 5991,
        "desc": "The specified host either does not exist or the auto reissue certificate parameter is not set for the host.",
        "first_action": "Ensure that the specified host exists and that the auto",
        "full_action": "Ensure that the specified host exists and that the auto\nreissue certificate parameter is set for the host. If the host to be recovered does\nnotexist,initiatethePreparetoRestoreworkflowagainforthehost.To settheauto\nreissue certificate parameter for the host, run the following command:\nnbhostmgmt -allowautoReissueCert -autoReissue 1\nAlternatively, you can use the NetBackup Administration Console."
    },
    "5992": {
        "code": 5992,
        "desc": "The certificate request has failed as the host information cannot be updated.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "5993": {
        "code": 5993,
        "desc": "The certificate is not valid for this host.",
        "first_action": "Verify that the certificate is issued for the same host and",
        "full_action": "Verify that the certificate is issued for the same host and\nretry the operation. If the problem persists, contact Cohesity Technical Support."
    },
    "5994": {
        "code": 5994,
        "desc": "The specified fingerprint does not match the CA certificate’s fingerprint.",
        "first_action": "Ensurethatyouhavespecifiedtheappropriatefingerprint",
        "full_action": "Ensurethatyouhavespecifiedtheappropriatefingerprint\nand retry the operation. If the problem persists, remove the CA certificate from the\nlocal trust store by using the nbcertcmd -removeCACertificate command and\nretry the operation."
    },
    "5995": {
        "code": 5995,
        "desc": "The certificate enrollment failed. The host ID that is associated with the certificate to be enrolled is assigned to another host.",
        "first_action": "Provide the certificate that is already enrolled for or issued to the host.",
        "full_action": "Do one of the following:\n■ Provide the certificate that is already enrolled for or issued to the host.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Do the following:\n■ Run the nbcertcmd -deleteECACertEntry command to delete the\nassociation of the existing host with the certificate.\n■ Run the nbcertcmd -createECACertEntry command to associate the\ncertificate with the existing host. For more information on the commands,\nrefer to the NetBackup Commands Reference Guide."
    },
    "5996": {
        "code": 5996,
        "desc": "The certificate enrollment failed. The request does not contain the certificate or the certificate is corrupted. NetBackup status codes 770 NetBackup status codes",
        "first_action": "Ensurethattheprovidedcertificateis valid.Iftheproblem",
        "full_action": "Ensurethattheprovidedcertificateis valid.Iftheproblem\npersists contact Cohesity Technical Support."
    },
    "5997": {
        "code": 5997,
        "desc": "The host certificate cannot be registered. The certificate must contain the Client Authentication and Server Authentication attributes in the Extended Key Usage field.",
        "first_action": "Run the following command:",
        "full_action": "Ensure that the third-party certificate that you want to\nregister contains the Client Authentication and the Server Authentication attributes\nin the Extended Key Usage field. Do the following, as appropriate:\n■ Run the following command:\nopenssl x509 -in certificatepath -text -noout -purpose\n■ If the certificate contains both the Client Authentication and the Server\nAuthentication attributes, the following output is displayed:\nCertificate purposes:\nSSL client: Yes\nSSL server: Yes\nTry to register the third-party certificate again.\n■ Ifoneorbothoftheattributesaremissing,contactyoursecurityadministrator\nto resolve the issue."
    },
    "5998": {
        "code": 5998,
        "desc": "The certificate is not enrolled with this primary server.",
        "first_action": "Enroll the host certificate with the primary server by using",
        "full_action": "Enroll the host certificate with the primary server by using\nthe nbcertcmd -enrollcertificate command."
    },
    "5999": {
        "code": 5999,
        "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase is not provided.",
        "first_action": "Ensure that the passphrase file path is specified for the",
        "full_action": "Ensure that the passphrase file path is specified for the\nECA_KEY_PASSPHRASEFILE configuration option. For more information on the\nNetBackup configuration options, refer to the NetBackup Administrator’s Guide,\nVolume I."
    },
    "6000": {
        "code": 6000,
        "desc": "The provided path is not allowed.",
        "first_action": "It is recommended using the NetBackup default paths for",
        "full_action": "It is recommended using the NetBackup default paths for\nprogress logs or rename file options; for example, use the user_ops folder. If you\ncannotusetheNetBackupdefaultpathinyoursetup,youshouldaddcustompaths\ntotheNetBackupconfiguration.Formoreinformationonhowtoaddacustompath,\nseetheBPCD_ALLOWED_PATHoptionforNetBackupserversandclientssection\nin the NetBackup Administrator’s Guide, Volume I."
    },
    "6071": {
        "code": 6071,
        "desc": "Credentials of the Cohesity Alta View are not valid.",
        "first_action": "Theregistrationtokenhasexpired.Usershoulddownload",
        "full_action": "Theregistrationtokenhasexpired.Usershoulddownload\nthe registration file again from Cohesity Alta View and re-register."
    },
    "6072": {
        "code": 6072,
        "desc": "An internal server error has occurred attempting to connect to the Cohesity Alta View.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "6073": {
        "code": 6073,
        "desc": "Failed to connect to the Cohesity Alta View.",
        "first_action": "Cohesity Alta View should be reachable from the domain",
        "full_action": "Cohesity Alta View should be reachable from the domain\nwheretheNetBackupprimaryserverisinstalledonport443.Confirmthatyouhave\nconnectivity and retry."
    },
    "6074": {
        "code": 6074,
        "desc": "FailedtoestablishapersistentconnectionbetweenthecurrentNetBackup primary server and the Cohesity Alta View platform.",
        "first_action": "Delete the domain from the Cohesity Alta View UI and",
        "full_action": "Delete the domain from the Cohesity Alta View UI and\nretry the registration process."
    },
    "6075": {
        "code": 6075,
        "desc": "Failed to configure the current NetBackup primary server with the Cohesity Alta View platform. NetBackup status codes 773 NetBackup status codes",
        "first_action": "An internal server error occurs when the SSL Handshake was performed with",
        "full_action": "Failed to establish connection with Cohesity Alta View\nserver. Review the following list for possible reasons the failure occurred:\n■ An internal server error occurs when the SSL Handshake was performed with\nthe Cohesity Alta View platform.\n■ The Cohesity Alta View server is not reachable.\n■ The proxy server is not reachable.\nRetry the operation."
    },
    "6078": {
        "code": 6078,
        "desc": "Unable to configure Cohesity Alta View, as it is already configured.",
        "first_action": "The primary server is already registered with a Cohesity",
        "full_action": "The primary server is already registered with a Cohesity\nAlta View server. Try to unregister the primary server from Cohesity Alta View and\nthen retry registration."
    },
    "6079": {
        "code": 6079,
        "desc": "Proxy server does not exist.",
        "first_action": "Retry the registration with Cohesity Alta View. Review the",
        "full_action": "Retry the registration with Cohesity Alta View. Review the\nNetBackup Web Service logs for the specific cause of the failure."
    },
    "6080": {
        "code": 6080,
        "desc": "Failed to delete the WebSocket connection.",
        "first_action": "You must clean up the Cohesity Alta View configuration",
        "full_action": "You must clean up the Cohesity Alta View configuration\nfilemanually.UsetheDELETECohesityAltaViewServerAPI.Formoreinformation,\ngototheSORTwebsite(https://sort.veritas.com/),andunderSupportedProducts\nselect NetBackup. Then search for NetBackup Alta View API."
    },
    "6082": {
        "code": 6082,
        "desc": "Failed to get the data collection status for Cohesity Alta View.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "6083": {
        "code": 6083,
        "desc": "Failed to update the data collection status for Cohesity Alta View.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "6084": {
        "code": 6084,
        "desc": "Failed to get the server information for the NetBackup primary server.",
        "first_action": "Review the NetBackup Web Service logs for the specific",
        "full_action": "Review the NetBackup Web Service logs for the specific\ncause of the failure."
    },
    "6085": {
        "code": 6085,
        "desc": "The proxy server is not reachable. The proxy server details that are configured are not valid.",
        "first_action": "Verify that the proxy server is reachable on the network",
        "full_action": "Verify that the proxy server is reachable on the network\nand verify the proxy server details that are configured for Alta View server\ncommunication are correct."
    },
    "6100": {
        "code": 6100,
        "desc": "Failed to forward connection socket to the Private Branch Exchange.",
        "first_action": "Check the Private Branch Exchange or the subscriber",
        "full_action": "Check the Private Branch Exchange or the subscriber\nprocess logs for more information. Retry the operation after some time."
    },
    "6101": {
        "code": 6101,
        "desc": "An internal error has occurred during the subscriber process.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "6102": {
        "code": 6102,
        "desc": "A socket that connects the subscriber and the message queue broker processes is closed.",
        "first_action": "Check the subscriber logs.",
        "full_action": "Do the following:\n■ Check the subscriber logs.\n■ Ensure that the message queue broker process is running on the server."
    },
    "6103": {
        "code": 6103,
        "desc": "A socket that connects the publisher and the message queue broker processes is closed.",
        "first_action": "See the process logs that publish messages to message",
        "full_action": "See the process logs that publish messages to message\nqueue broker for more logs. Also ensure that message queue broker on the master\nserver is running."
    },
    "6104": {
        "code": 6104,
        "desc": "The publisher process cannot publish messages to the message queue broker.",
        "first_action": "Check the subscriber process logs of the remote client for more details.",
        "full_action": "Do the following:\n■ Check the subscriber process logs of the remote client for more details.\n■ Check that remote client is up and running.\n■ Check that subscriber service on remote client is running.\n■ Check that subscriber service has valid certificate to communicate with master."
    },
    "6105": {
        "code": 6105,
        "desc": "The publisher and or subscriber process does not receive an acknowledgment for the published message.",
        "first_action": "Ensure that the subscriber is connected to the message",
        "full_action": "Ensure that the subscriber is connected to the message\nqueue broker."
    },
    "6106": {
        "code": 6106,
        "desc": "Failed to build a message that is to be published in a JSON format.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "6107": {
        "code": 6107,
        "desc": "Failed to parse the JSON message that the message queue broker has sent.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "6108": {
        "code": 6108,
        "desc": "The message type of the message queue broker is not supported.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "6109": {
        "code": 6109,
        "desc": "Message queue broker details in the JSON response are not valid.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "6405": {
        "code": 6405,
        "desc": "Specified path does not exist on the local disk.",
        "first_action": "Specify a staging location on the target host that is on its",
        "full_action": "Specify a staging location on the target host that is on its\nlocal disk."
    },
    "6172": {
        "code": 6172,
        "desc": "Your sign in attempt was denied by the administrator.",
        "first_action": "ContacttheNetBackupadministratortoresolvethisissue.",
        "full_action": "ContacttheNetBackupadministratortoresolvethisissue."
    },
    "6173": {
        "code": 6173,
        "desc": "The ticket for your sign in request has expired.",
        "first_action": "Determine if the approver exists in the system. If they do,",
        "full_action": "Determine if the approver exists in the system. If they do,\nsign in again to generate a new multiperson authorization ticket. If the NetBackup\nadministrator approves your request, you can log on successfully."
    },
    "6174": {
        "code": 6174,
        "desc": "Sign-in request was denied for security reasons.",
        "first_action": "If you receive this message when trying to complete a",
        "full_action": "If you receive this message when trying to complete a\ntrust primary operation, you can use the nbseccmd to complete the operation. See\nthe NetBackup Commands Reference Guide for more information."
    },
    "6175": {
        "code": 6175,
        "desc": "The sign in request failed.",
        "first_action": "Review the NetBackup Web Services logs for errors and",
        "full_action": "Review the NetBackup Web Services logs for errors and\nretry the log on."
    },
    "6176": {
        "code": 6176,
        "desc": "Failed to cancel the sign in request.",
        "first_action": "You can ignore this error message.",
        "full_action": "You can ignore this error message."
    },
    "6406": {
        "code": 6406,
        "desc": "WMI connection to the target host is failed.",
        "first_action": "ToconnectwithWMIandDCOMservice,usermusthavetherequiredpermission",
        "full_action": "The failed connection can be due to the following list:\n■ ToconnectwithWMIandDCOMservice,usermusthavetherequiredpermission\nto connect with the remote WMI service.\n■ Firewall exceptions are set up to allow WMI traffic through the firewall.\n■ GPO/Software restriction policy or an antivirus software blocks access.\n■ Ensure that target host is accessible. Validate the given target host credentials.\n■ Ensure that the target host trust relationship with domain is intact. If you\ncommunicate across domains, two-way trust relationship between different\ndomains exists."
    },
    "6416": {
        "code": 6416,
        "desc": "Unable to find the specified file on the remote server.",
        "first_action": "Verifythatthespecifiedstaginglocationonthetargethost",
        "full_action": "Verifythatthespecifiedstaginglocationonthetargethost\nexists or specify another valid staging location."
    },
    "6423": {
        "code": 6423,
        "desc": "File exists with same name as the directory.",
        "first_action": "On the remote host, check if a file already exists with the",
        "full_action": "On the remote host, check if a file already exists with the\nsame name and path as the staging location. If the file exists, rename or remove\nthat file, or specify an alternate staging location."
    },
    "6430": {
        "code": 6430,
        "desc": "Failed to validate administrative privileges for the user.",
        "first_action": "The provided credentials do not have the required",
        "full_action": "The provided credentials do not have the required\npermissions on the target host for agentless files or folders restore. For a Windows\ntarget host, you must use the credentials that are part of the local administrator\ngrouponthetargethost.ForaUNIXtargethost,usethecredentialsthatarearoot\nor sudo account with ALL permissions."
    },
    "6431": {
        "code": 6431,
        "desc": "Failed to connect a network resource using windows API.",
        "first_action": "Firewall exceptions are set up correctly.",
        "full_action": "Asapartofagentlessfilesandfoldersrestoresoperation,\nthe SMB Admin share is created from the recovery host on the target host with the\ncredentials provided by user. This error is seen when the target host for agentless\nrestore has a Windows OS and the administrator share of the target host is not\naccessible from the recovery host. Verify the following items on the target host:\n■ Firewall exceptions are set up correctly.\n■ File and printer sharing is enabled.\n■ GPO/Software restriction policy or an antivirus software does not block access.\n■ Target host is accessible with valid credentials."
    },
    "6435": {
        "code": 6435,
        "desc": "Unable to retrieve user's home directory on the target host. Specify the custom staging location.",
        "first_action": "The user's default staging location, which is the home",
        "full_action": "The user's default staging location, which is the home\ndirectory, can't be retrieved on the target host. Retry the operation with a valid\nstaging location."
    },
    "6437": {
        "code": 6437,
        "desc": "Failed to establish SSH session with host.",
        "first_action": "Verify that aes256-ctr is the supported cipher used for communication. Verify",
        "full_action": "Retry the operation after verification of all the following\ncriteria are satisfied:\n■ Verify that aes256-ctr is the supported cipher used for communication. Verify\nthat both the recovery host and the target host support this cipher.\n■ Verify at least one of the following HMAC protocols are supported on both\nrecovery host and target host: hmac-sha2-256, hmac-sha2-512.\n■ Verify that the method that is used for generating the host key is one of the\nfollowing:\n■ ECDSA_SHA2_NISTP256\n■ ECDSA_SHA2_NISTP384\n■ ECDSA_SHA2_NISTP521\n■ SSH_RSA\n■ SSH_DSS"
    },
    "6438": {
        "code": 6438,
        "desc": "Failed to verify SSH key fingerprint of host.",
        "first_action": "Verify the SSH key fingerprint of the target host and retry",
        "full_action": "Verify the SSH key fingerprint of the target host and retry\nthe operation."
    },
    "6440": {
        "code": 6440,
        "desc": "Failed to authenticate the host with provided user name or password.",
        "first_action": "Verify the user name and password of the target host and",
        "full_action": "Verify the user name and password of the target host and\nretry the operation."
    },
    "6441": {
        "code": 6441,
        "desc": "Failed to authenticate the host with specified SSH key.",
        "first_action": "VerifytheSSHprivatekeyandthekeypassphraseifused",
        "full_action": "VerifytheSSHprivatekeyandthekeypassphraseifused\nto generate the SSH private key of the target host and retry. Ensure that the\ncorresponding public key is present in the authorized_keys file in /root/.ssh\nfolder at the target host."
    },
    "6459": {
        "code": 6459,
        "desc": "Matching SSH key fingerprint host key method was not found on target host.",
        "first_action": "ThesupportedhostkeymethodofthespecifiedSSHkeyfingerprintisavailable",
        "full_action": "Ensure that either:\n■ ThesupportedhostkeymethodofthespecifiedSSHkeyfingerprintisavailable\non target host.\n■ ProvideSSHfingerprintofthehostkeymethodthatisconfiguredontargethost."
    },
    "6530": {
        "code": 6530,
        "desc": "Unable to start SharePoint web service on server",
        "first_action": "The SharePoint GRT web service,",
        "full_action": "The SharePoint GRT web service,\nVeritas.NetBackup.SPServiceHost.exe,isdeployedbydefaultontheNetBackup\nclients and starts only during the restores of SharePoint 2016 backups. After the\nrestore is completed, the web service is stopped.\nVerify that SharePoint 2016 has been installed correctly on the front-end server.\nYou can also try to manually start the service,\nVeritas.NetBackup.SPServiceHost.exe, from the command line. Verify that the\nservice starts during the restore and stops after the restore is completed."
    },
    "6531": {
        "code": 6531,
        "desc": "Validation of operating system user/password failed for client",
        "first_action": "Configure the SharePoint credentials on all of the nodes",
        "full_action": "Configure the SharePoint credentials on all of the nodes\nthat are used to browse, backup, or restore.\nSee\"ConfiguringthelogonaccountfortheNetBackupClientServiceforNetBackup\nfor SharePoint\" in the NetBackup for Microsoft SharePoint Server Administrator’s\nGuide."
    },
    "6600": {
        "code": 6600,
        "desc": "The BigData policy job failed. Check and verify that you have entered validcredentialsandprovidedcorrectentriesfortheapplicationserverorthebackup hosts.",
        "first_action": "Check and verify that you have entered the valid",
        "full_action": "Check and verify that you have entered the valid\ncredentials, provided correct entries for the application server or the backup hosts,\nand resolved any network connectivity issues."
    },
    "6601": {
        "code": 6601,
        "desc": "One or more of the input parameters or arguments are invalid.",
        "first_action": "Check and verify that you have entered valid credentials",
        "full_action": "Check and verify that you have entered valid credentials\nandprovidedthecorrectentriesfortheapplicationserverorthebackuphost.Ensure\nthat the BigData framework libraries are correctly installed on the computer."
    },
    "6602": {
        "code": 6602,
        "desc": "Insufficient memory or inadequate resources available to complete the job.",
        "first_action": "Ensure that sufficient memory is allocated and adequate",
        "full_action": "Ensure that sufficient memory is allocated and adequate\nresources are available to the system."
    },
    "6603": {
        "code": 6603,
        "desc": "Cannot complete the operation. Access to the server is denied due to a lack of system permissions.",
        "first_action": "Check to see if the user has the required permissions to",
        "full_action": "Check to see if the user has the required permissions to\naccesstheapplicationserverandtocompleteabackuporrestoreoperation.Ensure\nthat you have added the backup host to the relevant access lists."
    },
    "6604": {
        "code": 6604,
        "desc": "Failed to complete the operation. The number of open objects on the server has reached its limit.",
        "first_action": "Increase the limit of open objects. To increase the limit of",
        "full_action": "Increase the limit of open objects. To increase the limit of\nopen objects, see the appropriate plug-in support guide. Alternatively, you can\ncheck the open file settings on the backup host. For example, ulimit -n on UNIX\nsystems."
    },
    "6605": {
        "code": 6605,
        "desc": "Unable to process the request because the server resources are busy.",
        "first_action": "Retry the operation.",
        "full_action": "Retry the operation."
    },
    "6606": {
        "code": 6606,
        "desc": "Failed to complete the operation. The object already exists.",
        "first_action": "Ifoneormorevirtualmachinesexistwiththesamename,youcaneitherrename",
        "full_action": "Do the following, as appropriate:\n■ Ifoneormorevirtualmachinesexistwiththesamename,youcaneitherrename\nor delete one of the virtual machines.\n■ Check the NetBackup logs (bpbkar logs or nbappdiscv logs) for more\ninformation.\n■ In addition, you may want to remove the relevant state file."
    },
    "6607": {
        "code": 6607,
        "desc": "The version of NetBackup does not match the version of the BigData framework libraries. NetBackup status codes 787 NetBackup status codes",
        "first_action": "EnsurethatNetBackupandtheBigDataframeworklibraries",
        "full_action": "EnsurethatNetBackupandtheBigDataframeworklibraries\nare correctly installed."
    },
    "6608": {
        "code": 6608,
        "desc": "The version of NetBackup does not match the version of the plug-in libraries.",
        "first_action": "Ensure that NetBackup and the relevant plug-in libraries",
        "full_action": "Ensure that NetBackup and the relevant plug-in libraries\nare correctly installed."
    },
    "6609": {
        "code": 6609,
        "desc": "The NetBackup plug-in cannot complete the operation because the object is invalid.",
        "first_action": "Check and verify that you have entered the correct entries for the application",
        "full_action": "Do the following, as appropriate:\n■ Check and verify that you have entered the correct entries for the application\nserver or the backup hosts.\n■ Ensure that you have installed the correct plug-in to successfully complete the\noperation."
    },
    "6610": {
        "code": 6610,
        "desc": "An internal error occurred in the NetBackup processes.",
        "first_action": "Check the NetBackup debug logs for more information.",
        "full_action": "Check the NetBackup debug logs for more information."
    },
    "6612": {
        "code": 6612,
        "desc": "Unable to process the request because the server resources are either busy or unavailable. Retry the operation.",
        "first_action": "Retry the operation.",
        "full_action": "Retry the operation."
    },
    "6614": {
        "code": 6614,
        "desc": "Failed to complete the operation.",
        "first_action": "Retry the operation after the system is up and running.",
        "full_action": "Retry the operation after the system is up and running."
    },
    "6616": {
        "code": 6616,
        "desc": "The operation type is currently not supported.",
        "first_action": "Ensure the plug-in supports the type of backups or",
        "full_action": "Ensure the plug-in supports the type of backups or\noperations that you are trying to complete."
    },
    "6617": {
        "code": 6617,
        "desc": "A system call failed. NetBackup status codes 789 NetBackup status codes",
        "first_action": "Check the system logs or the operating system logs for",
        "full_action": "Check the system logs or the operating system logs for\nmore details."
    },
    "6618": {
        "code": 6618,
        "desc": "NetBackup cannot find the file to complete the operation.",
        "first_action": "Verify the location of the file. Check if the file was deleted",
        "full_action": "Verify the location of the file. Check if the file was deleted\nduring the backup job. Ensure that the file has the required access permissions."
    },
    "6619": {
        "code": 6619,
        "desc": "An error occurred because of a network connectivity issue.",
        "first_action": "To resolve the network connectivity issues, check the",
        "full_action": "To resolve the network connectivity issues, check the\nsystem logs and try again."
    },
    "6620": {
        "code": 6620,
        "desc": "The server has exceeded its connection limit.",
        "first_action": "Increase the limit of open objects. To increase the limit of",
        "full_action": "Increase the limit of open objects. To increase the limit of\nopen objects, see the appropriate plug-in support guide. Alternatively, you can\ncheck the open file settings on the backup host. For example, ulimit -n on UNIX\nsystems."
    },
    "6621": {
        "code": 6621,
        "desc": "An error occurred because the network protocol is not supported.",
        "first_action": "Verify and resolve any network connectivity issues. To",
        "full_action": "Verify and resolve any network connectivity issues. To\nresolve the network connectivity issues, check the system logs and try again."
    },
    "6622": {
        "code": 6622,
        "desc": "An internal error has occurred in the NetBackup process.",
        "first_action": "In the case of an OpenStack workload, update the image service name to",
        "full_action": "Review the NetBackup logs for more details.\n■ In the case of an OpenStack workload, update the image service name to\nglance. Run the following command in the OpenStack console:\nopenstack service set --name glance name or ID of image service\n■ In the case of a Hadoop workload, verify the hadoop.conf JSON file format is\nvalid."
    },
    "6623": {
        "code": 6623,
        "desc": "Failedtoconnecttotheapplicationserverorthebackuphost.Theserver is either shut down or not reachable.",
        "first_action": "Verifyandresolveanynetworkconnectivityissues.Ensure",
        "full_action": "Verifyandresolveanynetworkconnectivityissues.Ensure\nthat the application server and the backup host are up and running."
    },
    "6625": {
        "code": 6625,
        "desc": "The backup host is either unauthorized to complete the operation or it is unable to establish a connection with the application server.",
        "first_action": "The backup host has the required permissions.",
        "full_action": "Ensure the following:\n■ The backup host has the required permissions.\n■ Thefirewallissuebetweenthebackuphostandtheapplicationserverisresolved.\n■ The backup host is added to the relevant access lists."
    },
    "6626": {
        "code": 6626,
        "desc": "The server name is invalid.",
        "first_action": "Ensure that you have provided the correct name for the",
        "full_action": "Ensure that you have provided the correct name for the\napplication server."
    },
    "6628": {
        "code": 6628,
        "desc": "UnabletoestablishanetworkconnectionduetoanerrorwiththeDomain Name Service (DNS).",
        "first_action": "VerifyandresolveanynetworkconnectivityissuesorDNS",
        "full_action": "VerifyandresolveanynetworkconnectivityissuesorDNS\nissues. To resolve the network connectivity issues, check the system logs and try\nagain."
    },
    "6629": {
        "code": 6629,
        "desc": "Unable to complete the operation. Failed to authorize the user or the server.",
        "first_action": "Ensure that the user has the required permissions and",
        "full_action": "Ensure that the user has the required permissions and\nthattheserver(applicationserverorabackuphost)isaddedtotherelevantaccess\nlists."
    },
    "6630": {
        "code": 6630,
        "desc": "Unable to process the request because the server resources are either busy or unavailable. Retry the operation.",
        "first_action": "Ensure that a single job is resorting a particular file or an",
        "full_action": "Ensure that a single job is resorting a particular file or an\nobject."
    },
    "6631": {
        "code": 6631,
        "desc": "There is insufficient storage available to the system.",
        "first_action": "Ensure that sufficient storage is available to the system.",
        "full_action": "Ensure that sufficient storage is available to the system."
    },
    "6633": {
        "code": 6633,
        "desc": "Unable to complete the operation. Access to the object is denied due to a lack of system permissions.",
        "first_action": "Ensure that you have read and write access to the file or",
        "full_action": "Ensure that you have read and write access to the file or\nthe object."
    },
    "6634": {
        "code": 6634,
        "desc": "Unable to find the file or the object.",
        "first_action": "Check if the file or the object is available at the specified",
        "full_action": "Check if the file or the object is available at the specified\nlocation. Provide valid entries to complete the operation."
    },
    "6635": {
        "code": 6635,
        "desc": "The version of the server does not support the requested operation.",
        "first_action": "Ensurethattheversionoftheserversupportstheoperation",
        "full_action": "Ensurethattheversionoftheserversupportstheoperation\nthat you have requested."
    },
    "6640": {
        "code": 6640,
        "desc": "The version of the NetBackup process does not match with the version of the BigData framework libraries.",
        "first_action": "Ensure that NetBackup and its framework libraries are",
        "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed."
    },
    "6641": {
        "code": 6641,
        "desc": "The relevant libraries are either unavailable or inaccessible.",
        "first_action": "Ensure that NetBackup and its framework libraries are",
        "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed and granted relevant access permissions."
    },
    "6642": {
        "code": 6642,
        "desc": "The relevant libraries are either unavailable or the plug-in does not support the requested operation.",
        "first_action": "Toresolvethisissue,checktheNetBackuplogsformissing",
        "full_action": "Toresolvethisissue,checktheNetBackuplogsformissing\nsymbols."
    },
    "6643": {
        "code": 6643,
        "desc": "An internal error occurred in the NetBackup processes.",
        "first_action": "Check the NetBackup logs for more information.",
        "full_action": "Check the NetBackup logs for more information."
    },
    "6644": {
        "code": 6644,
        "desc": "An internal error occurred in the NetBackup processes.",
        "first_action": "Check the system logs or the operating system logs for",
        "full_action": "Check the system logs or the operating system logs for\nmore information."
    },
    "6646": {
        "code": 6646,
        "desc": "Unable to communicate with the server. NetBackup status codes 795 NetBackup status codes",
        "first_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided",
        "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\nthe correct entries (such as the host name and port number) for the application\nserver or the backup host."
    },
    "6647": {
        "code": 6647,
        "desc": "Unable to create or access a directory or a path.",
        "first_action": "Ensure that the application server lets the backup host",
        "full_action": "Ensure that the application server lets the backup host\naccess its files or directories to complete the operations."
    },
    "6649": {
        "code": 6649,
        "desc": "The relevant libraries are either unavailable or inaccessible.",
        "first_action": "Ensure that NetBackup and its framework libraries are",
        "full_action": "Ensure that NetBackup and its framework libraries are\ncorrectly installed and have relevant access permissions."
    },
    "6650": {
        "code": 6650,
        "desc": "The relevant libraries are either unavailable or the plug-in does not support the requested operation.",
        "first_action": "To resolve the issue, check the NetBackup logs for a",
        "full_action": "To resolve the issue, check the NetBackup logs for a\nmissing symbol."
    },
    "6652": {
        "code": 6652,
        "desc": "Failed to complete the operation. The version of the plug-in might not support the requested operation.",
        "first_action": "Ensure that the plug-in version supports the operation",
        "full_action": "Ensure that the plug-in version supports the operation\nthat you have requested."
    },
    "6653": {
        "code": 6653,
        "desc": "The selected schedule type is currently not supported.",
        "first_action": "WhenyoucreateaBigDatapolicy,ensurethattheplug-in",
        "full_action": "WhenyoucreateaBigDatapolicy,ensurethattheplug-in\nsupports the selected schedule type."
    },
    "6654": {
        "code": 6654,
        "desc": "Unable to retrieve the credentials for the server.",
        "first_action": "Hadoop: When setting the Application_Type parameter, you cannot use any",
        "full_action": "Ensurethatyouhaveenteredvalidcredentialsandprovided\ncorrect entries for the application server or the backup host.\nCreating a BigData policy:\n■ Hadoop: When setting the Application_Type parameter, you cannot use any\nuppercase letters. Example of correct form:\nApplication_Type=hadoop"
    },
    "6655": {
        "code": 6655,
        "desc": "The virtual machine does not exist.",
        "first_action": "Enter a valid name for the virtual machine. The virtual",
        "full_action": "Enter a valid name for the virtual machine. The virtual\nmachine display name is case sensitive and it does not allow spaces and certain\nspecial characters."
    },
    "6656": {
        "code": 6656,
        "desc": "Invalid credentials. Verify and enter the correct credentials.",
        "first_action": "Verify and re-enter the valid credentials for the workload.",
        "full_action": "Verify and re-enter the valid credentials for the workload."
    },
    "6657": {
        "code": 6657,
        "desc": "The server you are trying to connect is not responding.",
        "first_action": "Verify that the application server is up and running and",
        "full_action": "Verify that the application server is up and running and\ntry reconnecting with the server."
    },
    "6658": {
        "code": 6658,
        "desc": "The backup failed. The snapshot could not be created.",
        "first_action": "Refer to the errors listed in the nbaapidiscv log on the",
        "full_action": "Refer to the errors listed in the nbaapidiscv log on the\nbackup host and troubleshoot the issues"
    },
    "6659": {
        "code": 6659,
        "desc": "The backup failed. The workload file could not be created.",
        "first_action": "Refer to the errors listed in the nbaapidiscv log on the",
        "full_action": "Refer to the errors listed in the nbaapidiscv log on the\nbackup host and troubleshoot the issues."
    },
    "6661": {
        "code": 6661,
        "desc": "Unable to find the configuration parameter.",
        "first_action": "Verify the content of the azurestack configurations in the credential file that",
        "full_action": "Perform the following, as appropriate:\n■ Verify the content of the azurestack configurations in the credential file that\nwasspecifiedwiththetpconfig application_server_confcommandoption.\nBased on the missing configuration parameter, modify the configuration that is\nspecified in the credential file and update the tpconfig entry on the master\nserver.\n■ Verify the content of the Cassandra production cluster and the DSS cluster\ndetails in the cassandra.conf configuration file."
    },
    "6662": {
        "code": 6662,
        "desc": "Unable to find the configuration file.",
        "first_action": "1. Verify that the /usr/openv/var/global directory is whitelisted on the master",
        "full_action": "Do the following, as appropriate:\n1. Verify that the /usr/openv/var/global directory is whitelisted on the master\nserver. Run the bpgetconfig command.\n2. Verify that the application_server_name.conf credential file is in the\n/usr/openv/var/global directory on the master server.\n3. If the credential file is not in the /usr/openv/var/global directory on the\nmasterserver,createa.jsoncredentialfilewiththeazurestackconfigurations\nwith any file name (for example, azurestackserver.conf) at any location on\nthe master server.\n4. Add this file name with the tpconfig add command. Verify that the file is in\nthe /usr/openv/var/global directory with filename\napplication_server_name.conf after adding tpconfig entry."
    },
    "6663": {
        "code": 6663,
        "desc": "Failed to establish a Secure Shell connection with the remote server.",
        "first_action": "Verify that you entered the valid credentials for the",
        "full_action": "Verify that you entered the valid credentials for the\napplication server."
    },
    "6664": {
        "code": 6664,
        "desc": "Unable to load JSON object.",
        "first_action": "Verify that the production host user password is correct.",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue.\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Verify that the production host user password is correct.\n■ Verify that the DSS host user password is correct."
    },
    "6665": {
        "code": 6665,
        "desc": "There was an error constructing the URL.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "6666": {
        "code": 6666,
        "desc": "The MongoDB processes are not running on the host.",
        "first_action": "To backup or recover the MongoDB databases, ensure",
        "full_action": "To backup or recover the MongoDB databases, ensure\nthat the MongoDB cluster is running."
    },
    "6667": {
        "code": 6667,
        "desc": "The mongod process is not running on the host.",
        "first_action": "To recover the MongoDB databases, ensure that the",
        "full_action": "To recover the MongoDB databases, ensure that the\nmongod process is running."
    },
    "6668": {
        "code": 6668,
        "desc": "The mongos process is not running on the host.",
        "first_action": "To recover the MongoDB databases, ensure that the",
        "full_action": "To recover the MongoDB databases, ensure that the\nmongos process is running."
    },
    "6669": {
        "code": 6669,
        "desc": "Unable to capture the topology of the MongoDB cluster.",
        "first_action": "Ensure that the correct MongoDB credentials are used or",
        "full_action": "Ensure that the correct MongoDB credentials are used or\nthe MongoDB cluster is running. Ensure that the MongoDB shards are connected\nto the config server."
    },
    "6670": {
        "code": 6670,
        "desc": "Unable to capture balancer state.",
        "first_action": "Ensure that the correct MongoDB credentials are used or",
        "full_action": "Ensure that the correct MongoDB credentials are used or\nthe MongoDB cluster is running. Ensure that the MongoDB shards are connected\nto the config server."
    },
    "6671": {
        "code": 6671,
        "desc": "Unable to find database.",
        "first_action": "Ensure that the MongoDB cluster is running and admin",
        "full_action": "Ensure that the MongoDB cluster is running and admin\ndatabase is accessible."
    },
    "6672": {
        "code": 6672,
        "desc": "Failed to shutdown database server. NetBackup status codes 802 NetBackup status codes",
        "first_action": "Ensure that the MongoDB cluster is running and admin",
        "full_action": "Ensure that the MongoDB cluster is running and admin\ndatabase is accessible. Ensure that the correct MongoDB credentials are used."
    },
    "6673": {
        "code": 6673,
        "desc": "Failed to perform pre-recovery operation.",
        "first_action": "To recover the MongoDB databases, ensure that the",
        "full_action": "To recover the MongoDB databases, ensure that the\nMongoDBclusterisrunning.EnsurethattheMongoDBclusterisrunningandadmin\ndatabase is accessible. Ensure that the correct MongoDB credentials are used.\nFor more information, refer to the mdbserver logs."
    },
    "6674": {
        "code": 6674,
        "desc": "Failed to clean the data paths.",
        "first_action": "EnsurethatthedatapaththatisusedforrunningMongoDB",
        "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocesses is correct. For more information, refer to the mdbserver logs."
    },
    "6675": {
        "code": 6675,
        "desc": "Data path does not exist.",
        "first_action": "EnsurethatthedatapaththatisusedforrunningMongoDB",
        "full_action": "EnsurethatthedatapaththatisusedforrunningMongoDB\nprocesses is correct. For more information, refer to the mdbserver logs."
    },
    "6676": {
        "code": 6676,
        "desc": "UnabletocompletetheoperationbecausetheMongoDBprocessesare running on the server.",
        "first_action": "Ensure that the MongoDB processes are not spawned",
        "full_action": "Ensure that the MongoDB processes are not spawned\nbefore the MongoDB cluster recovery is complete."
    },
    "6677": {
        "code": 6677,
        "desc": "Unable to add a shard to the MongoDB cluster.",
        "first_action": "Ensure that the mongos process is running on the config",
        "full_action": "Ensure that the mongos process is running on the config\nserver. Ensure that the correct MongoDB credentials are used."
    },
    "6678": {
        "code": 6678,
        "desc": "Failed to initiate the shard.",
        "first_action": "Ensure that the mongod process is running on the config",
        "full_action": "Ensure that the mongod process is running on the config\nserver. Ensure that the correct MongoDB credentials are used."
    },
    "6679": {
        "code": 6679,
        "desc": "Failed to perform post-recovery operation.",
        "first_action": "Formoreinformationabouttheerror,refertotheCohesity",
        "full_action": "Formoreinformationabouttheerror,refertotheCohesity\nmdbserver logs or MongoDB logs. If the issue persists, visit support.veritas.com.\nThe Cohesity Support site offers additional information to help you troubleshoot\nthis issue."
    },
    "6680": {
        "code": 6680,
        "desc": "Unable to recover the MongoDB cluster.",
        "first_action": "For more information, refer to the mdbserver logs.",
        "full_action": "For more information, refer to the mdbserver logs."
    },
    "6681": {
        "code": 6681,
        "desc": "Multiple objects with same name found.",
        "first_action": "Ensure that the instance display names are unique and",
        "full_action": "Ensure that the instance display names are unique and\nreconfigure the policy."
    },
    "6682": {
        "code": 6682,
        "desc": "Host not found.",
        "first_action": "Verify the instance name or ID and reconfigure the policy.",
        "full_action": "Verify the instance name or ID and reconfigure the policy."
    },
    "6683": {
        "code": 6683,
        "desc": "Failed to create instance snapshot.",
        "first_action": "Verify the OpenStack logs and also ensure that instance",
        "full_action": "Verify the OpenStack logs and also ensure that instance\nsnapshot can be created."
    },
    "6684": {
        "code": 6684,
        "desc": "Failed to create volume snapshot.",
        "first_action": "Verify the OpenStack logs and also ensure that volume",
        "full_action": "Verify the OpenStack logs and also ensure that volume\nsnapshot can be created."
    },
    "6685": {
        "code": 6685,
        "desc": "Volume creation is in an invalid state.",
        "first_action": "Verify the OpenStack logs.",
        "full_action": "Verify the OpenStack logs."
    },
    "6686": {
        "code": 6686,
        "desc": "Failed to retrieve volume details.",
        "first_action": "Verify the OpenStack logs.",
        "full_action": "Verify the OpenStack logs."
    },
    "6687": {
        "code": 6687,
        "desc": "Volume snapshot creation is in an invalid state.",
        "first_action": "Verify the OpenStack logs.",
        "full_action": "Verify the OpenStack logs."
    },
    "6688": {
        "code": 6688,
        "desc": "Failed to retrieve volume snapshot details.",
        "first_action": "Verify the OpenStack logs.",
        "full_action": "Verify the OpenStack logs."
    },
    "6689": {
        "code": 6689,
        "desc": "MongoDBtopologyhaschangedsincethelastbackup.Youmustcreate a full backup.",
        "first_action": "Run a full backup if the topology has changed. Following",
        "full_action": "Run a full backup if the topology has changed. Following\na successful full backup, an incremental backup should be possible."
    },
    "6690": {
        "code": 6690,
        "desc": "The MongoDB rename file is either missing or invalid.",
        "first_action": "Reviewthesyntaxoftheentriesintherenamefile.Incase",
        "full_action": "Reviewthesyntaxoftheentriesintherenamefile.Incase\nof recovery to the alternate application server, make sure that the alternate\napplication server is specified in change entry in format as\nALT_APPLICATION_SERVER=Host:Port.Also,verifythatasingleinstancehost:port\nis not redirected to multiple host:port."
    },
    "6691": {
        "code": 6691,
        "desc": "Unable to create MongoDB restore specification file.",
        "first_action": "Make sure that the backup host (Destination client) is",
        "full_action": "Make sure that the backup host (Destination client) is\nreachable by the NetBackup master server."
    },
    "6692": {
        "code": 6692,
        "desc": "Unable to read and process the MongoDB restore specification file.",
        "first_action": "Ensure that the NetBackup backup host (Destination",
        "full_action": "Ensure that the NetBackup backup host (Destination\nclient) has the proper access permissions."
    },
    "6693": {
        "code": 6693,
        "desc": "Unable to read and process the MongoDB configuration file.",
        "first_action": "Ensure that the NetBackup backup host (Destination",
        "full_action": "Ensure that the NetBackup backup host (Destination\nclient) has the proper access permissions."
    },
    "6694": {
        "code": 6694,
        "desc": "Backup of MongoDB is supported only on Logical Volume Management based volumes.",
        "first_action": "Ensure to mount the database directory on a logical",
        "full_action": "Ensure to mount the database directory on a logical\nvolume."
    },
    "6695": {
        "code": 6695,
        "desc": "Backup of MongoDB on VxFS volumes is not supported.",
        "first_action": "Ensure to mount the database directory on a logical",
        "full_action": "Ensure to mount the database directory on a logical\nvolume."
    },
    "6696": {
        "code": 6696,
        "desc": "SimultaneousbackupoperationsonsameordifferentMongoDBinstances onamachinearenotsupported.Rescheduletheoperationstorunatdifferenttimes.",
        "first_action": "Reschedulethebackupofmultipleinstancesonthesame",
        "full_action": "Reschedulethebackupofmultipleinstancesonthesame\nmachine to run at different times."
    },
    "6697": {
        "code": 6697,
        "desc": "Maximum number of supported volumes has been reached.",
        "first_action": "The maximum number of attached volumes that are",
        "full_action": "The maximum number of attached volumes that are\nsupported is 32."
    },
    "6698": {
        "code": 6698,
        "desc": "Maximum number of supported security groups exceeded. NetBackup status codes 809 NetBackup status codes",
        "first_action": "Themaximumnumberofsecuritygroupsthataresupported",
        "full_action": "Themaximumnumberofsecuritygroupsthataresupported\nis 32. Adjust the number of security groups and retry the operation."
    },
    "6699": {
        "code": 6699,
        "desc": "Maximum number of supported attached volumes exceeded.",
        "first_action": "Themaximumnumberofextendedattachedvolumesthat",
        "full_action": "Themaximumnumberofextendedattachedvolumesthat\naresupportedis32.Adjustthenumberofattachedvolumesandretrytheoperation."
    },
    "6700": {
        "code": 6700,
        "desc": "Maximum number of supported network interfaces reached.",
        "first_action": "The maximum number of network interfaces that are",
        "full_action": "The maximum number of network interfaces that are\nsupported is 100. Adjust the number of network interfaces and retry the operation."
    },
    "6701": {
        "code": 6701,
        "desc": "Unable to open the device.",
        "first_action": "Verifythatyourstoragesystemisingoodstate.Alsoverify",
        "full_action": "Verifythatyourstoragesystemisingoodstate.Alsoverify\nyour backup host and instance to be backed up are on the same Hypervisor."
    },
    "6702": {
        "code": 6702,
        "desc": "Unable to obtain the authentication token.",
        "first_action": "Thetokenisgeneratedusingacombinationofusername,",
        "full_action": "Thetokenisgeneratedusingacombinationofusername,\nuser password, user domain name, project name, and project domain name. Verify\nthat these values are correctly mentioned in creds file."
    },
    "6703": {
        "code": 6703,
        "desc": "Backup of an instance with flavor disk size 0 and booting from image is not supported.",
        "first_action": "Verify that NetBackup does not attempt to back up an",
        "full_action": "Verify that NetBackup does not attempt to back up an\ninstance booting from an image and using a flavor with disk size 0."
    },
    "6704": {
        "code": 6704,
        "desc": "Restoring multiple MongoDB nodes on one replica set is invalid.",
        "first_action": "Only one node can be restored in a replica set. Select",
        "full_action": "Only one node can be restored in a replica set. Select\nredirect restore and edit the path to point to one node from the replica set. If your\nbackup was done from different nodes due to role changes, select all nodes to be\nrestored to one node on the destination cluster. This operation should be done by\nselecting the alternate restore option in the restore workflow. Use the alternate\nrestore option in the restore workflow."
    },
    "6705": {
        "code": 6705,
        "desc": "Restoring MongoDB data on an arbiter node is invalid.",
        "first_action": "Select another node in the destination MongoDB cluster",
        "full_action": "Select another node in the destination MongoDB cluster\nthat is not an arbiter in the destination MongoDB cluster."
    },
    "6706": {
        "code": 6706,
        "desc": "Adiscoveredshardwasfoundindrainstate,cannotproceedwithbackup.",
        "first_action": "Retry the backup operation when the shard is out of the",
        "full_action": "Retry the backup operation when the shard is out of the\ndrain state. Refer to the MongoDB Administrator’s Guide to change the state of the\nshard."
    },
    "6707": {
        "code": 6707,
        "desc": "An unsupported MongoDB storage engine is detected.",
        "first_action": "Change the storage engine to Wired Tiger and resubmit",
        "full_action": "Change the storage engine to Wired Tiger and resubmit\nyouroperation.RefertoMongoDBdocumentationforchangingthestorageengine."
    },
    "6708": {
        "code": 6708,
        "desc": "Unable to parse command output.",
        "first_action": "Refer to the mdbserver logs to get more details of the",
        "full_action": "Refer to the mdbserver logs to get more details of the\ncommand status and its failure. Retry the operation and if the issue persists, visit\nthe Cohesity Technical Support website. The Cohesity Technical Support website\noffers additional information to help you troubleshoot this issue."
    },
    "6709": {
        "code": 6709,
        "desc": "Unable to run the command.",
        "first_action": "Refer to the mdbserver logs to find the error code and refer to the MongoDB",
        "full_action": "Multipleworkloadscanshowthiserror.Reviewthefollowing\ninformation for your specific workload.\nWhen performing a backup or restore of a MongoDB, review the following:\n■ Refer to the mdbserver logs to find the error code and refer to the MongoDB\nAdministrator’s Guide for the reason of the failure based on the error code. If\nrunning an incremental backup on MongoDB version 4.4 or later, then ensure\nto have the mongodump utility installed. After installation, retry the operation and\nif the issue persists, visit the Cohesity Technical Support website. The Cohesity\nTechnicalSupportwebsiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue.\n■ Whencertificate-basedauthenticationisenabled,differentialincrementalbackups\nmayfail.Refertothemdbserverlogstofindtheerrorcodeandcommanddetails.\nIf the mdbserver logs indicate a mongodump command failure, try running the\nmongodump command manually on the MongoDB host and check the error. If\nthe mongodump command fails with X509 certificate-related connection errors,\nyou must fix these errors by updating the MongoDB server certificates with the\nsubjectAltName property as per the MongoDB documentation. Then retry the\ndifferential incremental backup.\nWhen performing a backup or restore of a Cassandra database, perform the\nfollowing as appropriate:\n■ Check SSH sessions for production nodes. The CBR node should be able to\nuse SSH to connect to the production nodes.\n■ Ensure that the CBR node is running and reachable.\n■ Verify that nbcbr process is running. If the process is not running, manually\nclearthefolderthatisspecifiedintheCassandraconfigurationfileonCassandra\ncluster nodes and retry the backup operation again."
    },
    "6710": {
        "code": 6710,
        "desc": "Pre-check for recovery has failed as WiredTiger log files are present at the database path.",
        "first_action": "Select the overwrite option in the restore workflow and",
        "full_action": "Select the overwrite option in the restore workflow and\nretry the operation."
    },
    "6711": {
        "code": 6711,
        "desc": "Unable to backup MongoDB configuration file.",
        "first_action": "Review the access control for the MongoDB configuration file. Allow the host",
        "full_action": "Review the mdbserver logs for more details.\nTry the following as appropriate:\n■ Review the access control for the MongoDB configuration file. Allow the host\nuserthatisspecifiedinthetpconfigforthisnode,alltherightsthatarerequired\nto read the MongoDB configuration file.\n■ Review the access control rights to the snapshot directory that is specified in\ntpconfig. Allow the host user that is specified in the tpconfig for this node,\nthe rights to write to the snapshot mount directory.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6712": {
        "code": 6712,
        "desc": "Unable to find operation log for previous backup.",
        "first_action": "Changethescheduletypetofullandretrythebackupand",
        "full_action": "Changethescheduletypetofullandretrythebackupand\nverify that it completes with no issues. Schedule an incremental backup after the\nfull backup."
    },
    "6713": {
        "code": 6713,
        "desc": "Operation log roll-over detected.",
        "first_action": "Change the schedule type to full and retry the backup.",
        "full_action": "Change the schedule type to full and retry the backup.\nSchedule an incremental backup after the full backup. Increase the frequency of\nincremental backups or increase the size of the operation logs such that operation\nlogs do not roll over before the next incremental. This step must be done based on\nthe average number of operations that are done on MongoDB and the recovery\npoint objective for your data. Refer to MongoDB Administrator’s Guide to change\nthe operation log size."
    },
    "6714": {
        "code": 6714,
        "desc": "Error while collection was iterated.",
        "first_action": "Refer to mdbserver logs to get details of the error. Run a",
        "full_action": "Refer to mdbserver logs to get details of the error. Run a\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup."
    },
    "6715": {
        "code": 6715,
        "desc": "Operation log verification error.",
        "first_action": "Refer to mdbserver logs to get details of the error. Run a",
        "full_action": "Refer to mdbserver logs to get details of the error. Run a\nfullbackupandafterthefullbackupissuccessful,scheduleanincrementalbackup."
    },
    "6716": {
        "code": 6716,
        "desc": "Failed I/O operation on operation log store info file.",
        "first_action": "Review the nbaapireq_handler logs and the mdbserver",
        "full_action": "Review the nbaapireq_handler logs and the mdbserver\nlogs to troubleshoot the issue. If the failure is for deleting operation logs, manually\ndelete these to bring up the MongoDB instance to get it running. If the failure is in\nfinding the operation log path, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "6717": {
        "code": 6717,
        "desc": "Invaliddeletepathwaspassedforrestoredoperationlogfiles.Operation log files have not been deleted.",
        "first_action": "Refer to mdbserver logs for more details. If the issue",
        "full_action": "Refer to mdbserver logs for more details. If the issue\npersists, visit the Cohesity Technical Support website. The Cohesity Technical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "6718": {
        "code": 6718,
        "desc": "Unable to replay operation logs.",
        "first_action": "4.4orlater,thenensuretohavethemongorestoreutilityinstalled.Afterinstallation,",
        "full_action": "If running an incremental recovery on MongoDB version\n4.4orlater,thenensuretohavethemongorestoreutilityinstalled.Afterinstallation,\nmanually apply the operation log. Refer to the operation logs restored from\nmdbserver logs and restore these manually. Refer to MongoDB Administrator’s\nGuide for the mongorestore command parameters."
    },
    "6719": {
        "code": 6719,
        "desc": "Unable to revoke NetBackup replay operation logs role from user.",
        "first_action": "Review the mdbserver logs for details.",
        "full_action": "Review the mdbserver logs for details.\nRun the following command to manually revoke the NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])"
    },
    "6720": {
        "code": 6720,
        "desc": "Unable to drop NetBackup replay operation logs role.",
        "first_action": "Review the mdbserver logs for details.",
        "full_action": "Review the mdbserver logs for details.\nRun the following command to manually drop the role for the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')"
    },
    "6721": {
        "code": 6721,
        "desc": "Unabletoreplayoperationlogs.Also,failedtorevokeNetBackupreplay operation logs role and drop NetBackup replay operation logs role.",
        "first_action": "RunthefollowingcommandtomanuallyrevoketheNetBackupreplayoperations",
        "full_action": "Review the mdbserver logs for details.\nPerform the following:\n■ RunthefollowingcommandtomanuallyrevoketheNetBackupreplayoperations\nlogs role for the user:\n\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])\".\n■ Run the following command to manually drop the role of the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')"
    },
    "6722": {
        "code": 6722,
        "desc": "Unable to replay the operation logs. Also, failed to revoke NetBackup replay operation logs role.",
        "first_action": "Manually apply the operation log. Refer to the operation",
        "full_action": "Manually apply the operation log. Refer to the operation\nlogs restored from mdbserver logs and restore these manually. Refer to MongoDB\nAdministrator’s Guide for the mongorestore command parameters.\nRun the following command to manually revoke the NetBackup replay operations\nlogsroleontheuser:\"db.getSiblingDB('admin').revokeRolesFromUser('{user\ninfo}',[{'role':'netbackup-replayoplogs', 'db':'admin'}])"
    },
    "6723": {
        "code": 6723,
        "desc": "Unable to replay operation logs. Also, failed to drop NetBackup replay operation logs role. NetBackup status codes 818 NetBackup status codes",
        "first_action": "Manually apply the operation log. Refer to the operation",
        "full_action": "Manually apply the operation log. Refer to the operation\nlogs restored from mdbserver logs and restore these manually. Refer to MongoDB\nAdministrator’s Guide for the mongorestore command parameters.\nRun the following command to manually drop the role on the administrator user:\n\"db.getSiblingDB('admin').dropRole('netbackup-replayoplogs')"
    },
    "6724": {
        "code": 6724,
        "desc": "Restore node count is invalid.",
        "first_action": "Only one node can be restored in a replica set. If your",
        "full_action": "Only one node can be restored in a replica set. If your\nbackup was done from different nodes due to role changes, select all the nodes to\nberestoredtoonesinglenodeonthedestinationMongoDBcluster.Usethealternate\nrestore option in the restore workflow."
    },
    "6725": {
        "code": 6725,
        "desc": "Unable to find information about the MongoDB replica set.",
        "first_action": "Refer to mdbserver logs for more details. Retry the",
        "full_action": "Refer to mdbserver logs for more details. Retry the\noperation and if the issue persists, visit the Cohesity Technical Support website.\nThe Cohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "6726": {
        "code": 6726,
        "desc": "Either the backup host that is selected as the destination client is invalid or inaccessible, or the required plug-in is not found on the client.",
        "first_action": "Makesurethatthecorrectbackuphosthasbeenselected",
        "full_action": "Makesurethatthecorrectbackuphosthasbeenselected\nas the destination. Also, make sure that the MongoDB plug-in is installed on the\nbackup host and retry the operation."
    },
    "6727": {
        "code": 6727,
        "desc": "Failed to transfer a file to the remote host.",
        "first_action": "Review the connectivity between the NetBackup client",
        "full_action": "Review the connectivity between the NetBackup client\nand the MongoDB nodes. Refer to the nbapidiscv and nbaapire_handler logs\nfor more details."
    },
    "6728": {
        "code": 6728,
        "desc": "Invalid backup host was used in the policy.",
        "first_action": "Updatethepolicytospecifythecorrectbackuphost.Verify",
        "full_action": "Updatethepolicytospecifythecorrectbackuphost.Verify\nthat the appropriate plug-in is installed on the backup host and retry the backup\noperation."
    },
    "6729": {
        "code": 6729,
        "desc": "Unable to download the thin client from the package repository.",
        "first_action": "Ensure that you have added the MongoDB_tc package on",
        "full_action": "Ensure that you have added the MongoDB_tc package on\nthe NetBackup master server. Refer to the MongoDB Administrator’s Guide to add\nthe thin client using the nbrepo --add command. Add the thin client package for\ntherelevantMongoDBnodeoperatingsystemoraddthethinclientsforbothRHEL\nand SUSE on your master. Then retry the operation."
    },
    "6730": {
        "code": 6730,
        "desc": "The selected schedule type is currently not supported for the sharded cluster that has Feature Compatibility Version 4.2 or later.",
        "first_action": "If you run an incremental on Sharded MongoDB cluster",
        "full_action": "If you run an incremental on Sharded MongoDB cluster\nwithversion4.2,refertotheMongoDBAdministrator’sGuidetochangetheFeature\nCompatibility Version of MongoDB to 4.0. Retry the operation with a full backup\nfollowed by incremental backup. If you do not want to change the Feature\nCompatibility Version, change the schedule type to only do full backups of this\nMongoDB instance. Incremental backups are not supported for a Sharded cluster\nwith MongoDB version 4.4 or later."
    },
    "6731": {
        "code": 6731,
        "desc": "All the required parameters for authentication type certificate-based are not provided.",
        "first_action": "Ensure that you have provided all authentication details",
        "full_action": "Ensure that you have provided all authentication details\nin tpconfig for your MongoDB cluster and that you provide all the required\nparameters. Refer to the NetBackup for MongoDB Administrator’s Guide for more\ninformation on required parameters."
    },
    "6732": {
        "code": 6732,
        "desc": "Ensure that you provide all the required parameters.",
        "first_action": "Ensure that you have provided all authentication details",
        "full_action": "Ensure that you have provided all authentication details\nin tpconfig for your MongoDB cluster. Refer to the NetBackup MongoDB\nAdministrator’s Guide for more information on required parameters."
    },
    "6733": {
        "code": 6733,
        "desc": "NetBackup does not support protection of the given MongoDB cluster version.",
        "first_action": "Refer to NetBackup Enterprise Server and Server OS",
        "full_action": "Refer to NetBackup Enterprise Server and Server OS\nSoftware Compatibility List for your NetBackup client version to find out supported\nMongoDB version."
    },
    "6734": {
        "code": 6734,
        "desc": "Unable to obtain the MongoDB version.",
        "first_action": "Ensure that the MongoDB cluster is up and running and",
        "full_action": "Ensure that the MongoDB cluster is up and running and\nretry the operation."
    },
    "6735": {
        "code": 6735,
        "desc": "Unable to obtain the Feature Compatibility Version.",
        "first_action": "Ensure that the MongoDB cluster is up and running and",
        "full_action": "Ensure that the MongoDB cluster is up and running and\nretry the operation."
    },
    "6736": {
        "code": 6736,
        "desc": "The source and the target cluster must have the same communication mode for certificate-based authentication. NetBackup status codes 822 NetBackup status codes",
        "first_action": "Change the restore cluster authentication type to match",
        "full_action": "Change the restore cluster authentication type to match\nwith the backup cluster authentication type and retry the restore."
    },
    "6737": {
        "code": 6737,
        "desc": "Unable to stop the balancer on the MongoDB cluster.",
        "first_action": "Refer to mdbserver logs for more details. Refer to Mongo",
        "full_action": "Refer to mdbserver logs for more details. Refer to Mongo\nlogs for more details about the failure. Retry the operation and if the issue persists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue."
    },
    "6738": {
        "code": 6738,
        "desc": "Unable to start the balancer on the MongoDB cluster.",
        "first_action": "Refer to mdbserver logs for more details. Refer to Mongo",
        "full_action": "Refer to mdbserver logs for more details. Refer to Mongo\nlogs for more details about the failure. Retry the operation and if the issue persists,\nvisit the Cohesity Technical Support website. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue."
    },
    "6739": {
        "code": 6739,
        "desc": "The cluster is created using the externally sourced configuration file values. NetBackup currently does not support this MongoDB configuration.",
        "first_action": "NetBackup doesn't support the externally sourced",
        "full_action": "NetBackup doesn't support the externally sourced\nconfiguration files. Please change the MongoDB configuration to use local\nconfiguration files and retry the operation."
    },
    "6740": {
        "code": 6740,
        "desc": "Either the MongoDB Version or the Feature Compatibility Version of the MongoDB cluster has changed.",
        "first_action": "Runafullbackupandthenanincrementalbackupshould",
        "full_action": "Runafullbackupandthenanincrementalbackupshould\nwork."
    },
    "6741": {
        "code": 6741,
        "desc": "The quota is exceeded for volumes.",
        "first_action": "EnsurethattheOpenStackvolumequotais largeenough",
        "full_action": "EnsurethattheOpenStackvolumequotais largeenough\nto accommodate the creation of new volumes that are required during backup and\nor restore operations."
    },
    "6742": {
        "code": 6742,
        "desc": "The quota is exceeded for instances.",
        "first_action": "EnsurethattheOpenStackinstancequotaislargeenough",
        "full_action": "EnsurethattheOpenStackinstancequotaislargeenough\nto accommodate the creation of new instance that is required during restore\noperation."
    },
    "6743": {
        "code": 6743,
        "desc": "Failed to get the instance name. NetBackup status codes 824 NetBackup status codes",
        "first_action": "For the backup to succeed, ensure that the OpenStack",
        "full_action": "For the backup to succeed, ensure that the OpenStack\ninstance is present in the tenant or the instance name is not blank."
    },
    "6744": {
        "code": 6744,
        "desc": "The host name on the backup host is empty.",
        "first_action": "Verify that the host name is properly configured for the",
        "full_action": "Verify that the host name is properly configured for the\nbackup host and make sure the /tmp folder of the backup host is mounted with\nexecution permissions."
    },
    "6745": {
        "code": 6745,
        "desc": "Failed to connect to MongoDB instance.",
        "first_action": "Verify that there is connectivity to the MongoDB instance.",
        "full_action": "Perform the following as appropriate:\n■ Verify that there is connectivity to the MongoDB instance.\n■ If the MongoDB instance target destination or ALT_APPLICATION_SERVER is an\narbiter, change it to a non-arbiter MongoDB instance."
    },
    "6746": {
        "code": 6746,
        "desc": "Connection cannot be established because the backup host failed to resolve the application server. NetBackup status codes 825 NetBackup status codes",
        "first_action": "Ensure that you have entered the correct host name of the application server.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that you have entered the correct host name of the application server.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom the backup host."
    },
    "6747": {
        "code": 6747,
        "desc": "Thebackuphostcannotestablishaconnectiontotheapplicationserver.",
        "first_action": "Ensure that you have provided the correct host name for the application server.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that you have provided the correct host name for the application server.\n■ Trytopingthebackuphostfromtheapplicationserverandtheapplicationserver\nfrom the backup host.\n■ Ensure that the port is updated correctly using tpconfig or hadoop.conf."
    },
    "6748": {
        "code": 6748,
        "desc": "A problem has occurred with the SSL or the TLS communication.",
        "first_action": "Ensure that the certificates that are provided for the SSL",
        "full_action": "Ensure that the certificates that are provided for the SSL\nor the TLS communication have the correct file format, path, and permissions."
    },
    "6749": {
        "code": 6749,
        "desc": "Failed in SSL or TLS communication due to an invalid client certificate.",
        "first_action": "Ensure that the certificate is accessible and that the",
        "full_action": "Ensure that the certificate is accessible and that the\nspecified path is correct."
    },
    "6750": {
        "code": 6750,
        "desc": "Failed to verify the application server.",
        "first_action": "Ensure that the certificates that are provided for the SSL",
        "full_action": "Ensure that the certificates that are provided for the SSL\northeTLScommunicationhavethecorrectfileformat,path,andpermissions.Also,\nverify that the certificate is not revoked."
    },
    "6751": {
        "code": 6751,
        "desc": "Failed to read the SSL CA certificate.",
        "first_action": "Ensure that the certificates and the CRL files are in the",
        "full_action": "Ensure that the certificates and the CRL files are in the\ncorrect format and that the trust store file and the CRL files are not corrupted."
    },
    "6752": {
        "code": 6752,
        "desc": "An unknown Certificate Authority issued the certificate.",
        "first_action": "Obtain the CA certificate for the required server and rerun the operation.",
        "full_action": "Perform the following as appropriate:\n■ Obtain the CA certificate for the required server and rerun the operation.\n■ Retry the operation and save all the error log information. If the issue persists,\nvisit support.veritas.com. The Cohesity Technical Support website offers\nadditional information to help you troubleshoot this issue."
    },
    "6753": {
        "code": 6753,
        "desc": "Ensure that the application server clock and the backup host clocks are synchronized.",
        "first_action": "Checkifthebackuphost’sclockisinsyncwiththespecified",
        "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\napplicationserver.Ifnecessary,correctthetimeontheapplicationserverandrerun\nthe operation and save all error log information. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "6754": {
        "code": 6754,
        "desc": "The security certificate has expired.",
        "first_action": "Checkifthebackuphost’sclockisinsyncwiththespecified",
        "full_action": "Checkifthebackuphost’sclockisinsyncwiththespecified\nApplication Server. If necessary, correct the time on the Application host and rerun\nthe operation and save all error log information. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "6755": {
        "code": 6755,
        "desc": "The certificate revocation list (CRL) is unavailable.",
        "first_action": "The ECA_CRL_PATH has the correct certificate revocation list (CRL) directory",
        "full_action": "If the ECA_CRL_PATH setting is specified in the bp.conf\nconfiguration file, ensure the following:\n■ The ECA_CRL_PATH has the correct certificate revocation list (CRL) directory\npath.\n■ The CRL directory contains CRLs for all required certificate issuers.\n■ The CRL is in PEM format.\n■ The CRL has not expired.\n■ The CRL last update date is not a future date."
    },
    "6756": {
        "code": 6756,
        "desc": "The certificate revocation list (CRL) has expired.",
        "first_action": "Provide the CRL that has not expired.",
        "full_action": "Provide the CRL that has not expired."
    },
    "6757": {
        "code": 6757,
        "desc": "The security certificate is revoked.",
        "first_action": "Ensurethatthecertificatethatisprovidedfortheapplication",
        "full_action": "Ensurethatthecertificatethatisprovidedfortheapplication\nserver is not revoked. Also, if the certificate is not revoked and you still see this\nerror, check if the certificate revocation list (CRL) is updated in the CRL cache."
    },
    "6758": {
        "code": 6758,
        "desc": "Unable to decrypt the certificate revocation list (CRL) signature.",
        "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity",
        "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue."
    },
    "6759": {
        "code": 6759,
        "desc": "Certificate revocation list (CRL) signature failure.",
        "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity",
        "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue."
    },
    "6760": {
        "code": 6760,
        "desc": "The certificate revocation list (CRL) is not yet valid.",
        "first_action": "Check your system time or provide a valid CRL.",
        "full_action": "Check your system time or provide a valid CRL."
    },
    "6761": {
        "code": 6761,
        "desc": "The certificate revocation list (CRL) last update date is not in a valid format.",
        "first_action": "Check the CRL using the OpenSSL command or contact",
        "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator."
    },
    "6762": {
        "code": 6762,
        "desc": "The certificate revocation list (CRL) next update date is not in a valid format.",
        "first_action": "Check the CRL using the OpenSSL command or contact",
        "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator."
    },
    "6763": {
        "code": 6763,
        "desc": "Unable to retrieve the certificate revocation list (CRL) issuer certificate.",
        "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity",
        "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue."
    },
    "6764": {
        "code": 6764,
        "desc": "Key usage does not include certificate revocation list (CRL) signing.",
        "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity",
        "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support site offers additional information to help you\ntroubleshoot this issue."
    },
    "6765": {
        "code": 6765,
        "desc": "Critical certificate revocation list (CRL) contains invalid file extensions.",
        "first_action": "Check the CRL using the OpenSSL command or contact",
        "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator."
    },
    "6766": {
        "code": 6766,
        "desc": "The certificate revocation list (CRL) scope is different, it must cover all revocation reasons.",
        "first_action": "Check the CRL using the OpenSSL command or contact",
        "full_action": "Check the CRL using the OpenSSL command or contact\nyour Security Administrator."
    },
    "6767": {
        "code": 6767,
        "desc": "Certificate revocation list (CRL) path validation error.",
        "first_action": "Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity",
        "full_action": "UsetheOpenSSLverifycommandtocheckthecertificate\nwith the CRL.\nPerform the following as appropriate:\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ Iftheverificationissuccessfulbuttheproblempersists,visitsupport.veritas.com.\nThe Cohesity Technical Support website offers additional information to help\nyou troubleshoot this issue."
    },
    "6768": {
        "code": 6768,
        "desc": "Failed to verify the application server certificate.",
        "first_action": "Retrytheoperationandiftheissuepersists,saveallerror",
        "full_action": "Retrytheoperationandiftheissuepersists,saveallerror\nlog information and visit support.veritas.com. The Cohesity Technical Support\nwebsite offers additional information to help you troubleshoot this issue."
    },
    "6772": {
        "code": 6772,
        "desc": "An unsupported protocol was used to communicate with the application server.",
        "first_action": "ECA_TRUST_STORE_PATH",
        "full_action": "Check the protocol that is used for communication with\nthe application server. If the application server uses HTTP, ensure that the port is\nupdated correctly using tpconfig or hadoop.conf.\nUpdate the following files in the bp.conf file:\n■ ECA_TRUST_STORE_PATH\n■ ECA_CRL_PATH\n■ HADOOP_SECURE_CONNECT_ENABLED\n■ HADOOP_CRL_CHECK"
    },
    "6773": {
        "code": 6773,
        "desc": "Unable to retrieve the issuer certificate.",
        "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,",
        "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct."
    },
    "6774": {
        "code": 6774,
        "desc": "A self-signed certificate cannot be found in the list of trusted certificates.",
        "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,",
        "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct. Check if the host certificate contents are part of the\ncertificate that is provided as ECA_TRUST_STORE_PATH."
    },
    "6775": {
        "code": 6775,
        "desc": "Unable to verify the first certificate.",
        "first_action": "Ensurethatthecertificatesfileformats,paths,permissions,",
        "full_action": "Ensurethatthecertificatesfileformats,paths,permissions,\nand passwords are correct."
    },
    "6776": {
        "code": 6776,
        "desc": "CannotlocatetherequiredVxUpdatepackagefortheNetBackupversion of the backup host and the operating system of the MongoDB host.",
        "first_action": "Ensure that you have added the required VxUpdate",
        "full_action": "Ensure that you have added the required VxUpdate\npackage for the MongoDB thin client on the NetBackup master server. Refer to the\nMongoDB Administrator’s Guide to add the thin client using the nbrepo --add\ncommand. Add the thin client package corresponding to the NetBackup version of\nthe backup host and the operating system of the MongoDB host. Then, retry the\noperation."
    },
    "6777": {
        "code": 6777,
        "desc": "Partialsuccess-failedtoparseaccessURIformanageddisksnapshot.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess"
    },
    "6778": {
        "code": 6778,
        "desc": "Partial success - disk snapshot export failed.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about granting access, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/grantaccess"
    },
    "6779": {
        "code": 6779,
        "desc": "Partial success - the disk snapshot cancel export failed.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about revoking access to a disk, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/disks/revokeaccess"
    },
    "6780": {
        "code": 6780,
        "desc": "Partial success - failed to delete the managed disk snapshot.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about deleting snapshots, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/compute/snapshots/delete"
    },
    "6781": {
        "code": 6781,
        "desc": "Partial success - invalid access URI returned when disk snapshot was exported.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody."
    },
    "6782": {
        "code": 6782,
        "desc": "Partial success - the open object for disk operation failed.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody."
    },
    "6783": {
        "code": 6783,
        "desc": "Partial success - Failed to obtain the disk snapshot blob.",
        "first_action": "Raise the verbose log level to 5 in the bp.conf file on the backup host and",
        "full_action": "Thiscodeisdisplayedduetoabackupjobthatwaspartially\nsuccessful.\nPerform the following as appropriate:\n■ Raise the verbose log level to 5 in the bp.conf file on the backup host and\nmedia server and retry the operation. Review the nbaapidiscv and bpbkar\nlogs.\n■ Add CURL_VERBOSE = true into /usr/openv/var/global/azurestack.conf\nandretrytheoperation.ReviewthefailedRESTAPIrequestandresponsebody.\nFor more information about the Get Blob operation, refer to:\nhttps://docs.microsoft.com/en-us/rest/api/storageservices/get-blob"
    },
    "6784": {
        "code": 6784,
        "desc": "The asynchronous operation returned an unknown failure.",
        "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the",
        "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations"
    },
    "6785": {
        "code": 6785,
        "desc": "The asynchronous operation is in progress.",
        "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the",
        "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations"
    },
    "6786": {
        "code": 6786,
        "desc": "The asynchronous operation failed.",
        "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the",
        "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations"
    },
    "6787": {
        "code": 6787,
        "desc": "The asynchronous operation was canceled.",
        "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the",
        "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations"
    },
    "6788": {
        "code": 6788,
        "desc": "The asynchronous operation returned an unknown error.",
        "first_action": "Azure-AsyncOperation - The URL for checking the ongoing status of the",
        "full_action": "If an asynchronous operation fails or returns a canceled\nerror as part if the HTTP response, then the backup operation retries.\nYou can monitor the status of the asynchronous operation in two different ways.\nYou can determine the correct approach to help you correct the issue by examining\nthe header values that are returned from your original request. Primarily, look for:\n■ Azure-AsyncOperation - The URL for checking the ongoing status of the\noperation. If your operation returns this value, use it to track the status of the\noperation.\n■ Retry-After - The number of seconds to wait before the status of the\nasynchronous operation is checked.\nFor more information about asynchronous operations, refer to:\nhttps://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations"
    },
    "6789": {
        "code": 6789,
        "desc": "The configuration is invalid for the specified resource.",
        "first_action": "Perform a restore to the original location using the Restore everything to it",
        "full_action": "Review the tar log file for the exact error message and as\nper the restore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that the configuration during the backup operation of the VM that is\nspecified in the error message is available on Azure Stack.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ Specify the valid storage account type value in the managed disk rename\nentry. This step is required only in managed disk VM restores.\n■ Specify the disk resource group name that is configured in the subscription\nID on Azure Stack where you want to restore. Add this information in the\nmanaged disk rename entry. This step is required only in managed disk VM\nrestores.\n■ Specify the correct value of the subscription ID that is configured on Azure\nStack where you want to restore for subscription ID rename entry.\n■ For the RgName rename entry, specify the resource group name that is\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\n■ For the Nsg rename entry, specify the network security group that is\nconfiguredforthesubscriptionIDonAzureStackwhereyouwanttorestore.\nIf the resource group for the network security group is different from the VM\nresource group, it needs to be specified in the Nsg rename entry as:\nNsg=<ResourceGroup_Name>/<NetworkSecurityGroup_Name>\n■ For the Vnet rename entry, specify the virtual network that is configured for\nthesubscriptionIDonAzureStackwhereyouwanttorestore.Iftheresource\ngroup for Vnet is different from the VM resource group, it needs to be\nspecified in the Vnet rename entry as:\nVnet=<ResourceGroup_Name>/<virtual_network_Name>"
    },
    "6791": {
        "code": 6791,
        "desc": "Failed to create the disk.",
        "first_action": "WhenperformingarestoreusingtheRestoreeverything",
        "full_action": "WhenperformingarestoreusingtheRestoreeverything\nto a different location (maintaining existing structure) option, review the HTTP\nresponse or log message in the tar log file."
    },
    "6792": {
        "code": 6792,
        "desc": "Unable to find a storage account. NetBackup status codes 842 NetBackup status codes",
        "first_action": "Perform a restore to the original location using the Restore everything to it",
        "full_action": "Review the tar log file for the exact error message for the\nrestore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that the storage account that is specified during the backup of the VM\nis available during the restore of respective unmanaged and managed VM\nrestore.\n■ If you restore a managed disk VM, you need to specify the staging storage\naccount exists in the original restore location on the azurestack in the\nazurestack.conf file.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ For managed disk VM restores, specify the configured staging storage\naccountinthesubscriptionIDwhereyouwanttemporaryVHDtobecreated\non Azure Stack. Use either the rename file or the azurestack.conf file.\n■ For unmanaged disk VM restores, specify the configured storage account\nin the subscription ID where you want to restore on Azure Stack. Use the\nrename file for VHD blob rename entry.\n■ VerifythattheHTTPoptionisenabledonthestorageaccountthatisspecified\nfor the managed and unmanaged VM restores."
    },
    "6793": {
        "code": 6793,
        "desc": "Failed to recover the VM.",
        "first_action": "Reviewthetarlogfilefortheexacterrormessage.Review",
        "full_action": "Reviewthetarlogfilefortheexacterrormessage.Review\nthe HTTP response message, in the tar log file, for exact error reason."
    },
    "6794": {
        "code": 6794,
        "desc": "Failed to create the resource.",
        "first_action": "Perform a restore to the original location using the Restore everything to it",
        "full_action": "Review the tar log file for the exact error message for the\nrestore location.\nTry one of the following as appropriate:\n■ Perform a restore to the original location using the Restore everything to it\noriginal location option.\n■ Verify that all the configured resources that are specified during the backup\nof the VM are available during the restore operation.\n■ Verify that operation quota is sufficient on the Azure Stack. The quota must\nbe sufficient to create a public IP address if the public IP address option is\nselected at restore time.\n■ PerformanalternatelocationrestoreusingtheRestoreeverythingtoadifferent\nlocation (maintaining existing structure) option.\n■ In the Vnet rename entry, specify the virtual network that is configured for\nthe subscription ID on Azure Stack where you want to restore.\n■ IntheNsgrenameentry,specifythenetworksecuritygroupthatisconfigured\nfor the subscription ID on Azure Stack where you want to restore.\n■ In the subnet rename entry, specify the subnet that is configured for the\nsubscription ID on Azure Stack where you want to restore."
    },
    "6795": {
        "code": 6795,
        "desc": "An invalid backup selection is specified in the policy. NetBackup status codes 844 NetBackup status codes",
        "first_action": "Create a policy using an intelligent group with supported",
        "full_action": "Create a policy using an intelligent group with supported\nassets or manually adding supported assets in the policy."
    },
    "6797": {
        "code": 6797,
        "desc": "Unable to find the resource.",
        "first_action": "Perform an alternate location restore using the Restore",
        "full_action": "Perform an alternate location restore using the Restore\neverything to a different location (maintaining existing structure) option.\nAfter you perform the restore, review the tar log file for the exact error message.\nVerify that the virtual network, network security group, or the subnet is configured\non Azure Stack for the target subscription ID location for the restore operation."
    },
    "6798": {
        "code": 6798,
        "desc": "Unable to find an available port on MongoDB host for the thin client.",
        "first_action": "Verify that the port range that is specified in the mongodb.conf file or tpconfig",
        "full_action": "Perform the following as appropriate:\n■ Verify that the port range that is specified in the mongodb.conf file or tpconfig\nglobal settings is available on the MongoDB host. The port range is set using\nthe mdbserver_port and mdbserver_port_range settings.\n■ Increase the port number range by adjusting the setting to a higher value for\nmdbserver_port_range if you have:\n■ Parallel NetBackup backup or restore operations running on this host.\n■ Multiple MongoDB instances running on this host."
    },
    "6800": {
        "code": 6800,
        "desc": "NewNetBackupCAofthegivenkeysizecannotbesetupformigration.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6801": {
        "code": 6801,
        "desc": "TheNetBackupCAthatisnewlysetupformigrationcannotbeactivated.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6802": {
        "code": 6802,
        "desc": "The migration of NetBackup CA cannot be completed.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6803": {
        "code": 6803,
        "desc": "NetBackup CA with the given fingerprint cannot be decommissioned. NetBackup status codes 846 NetBackup status codes",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6804": {
        "code": 6804,
        "desc": "The key size is not valid. In non-FIPS mode, NetBackup supports 2048, 3072, 4096, and 8192 bits for key size. In FIPS mode, NetBackup supports only 2048 and 3072 bits for key size.",
        "first_action": "In non-FIPS mode, use 2048, 3072, 4096, and 8192 bits for key size.",
        "full_action": "UseoneofthefollowingkeysizesthatNetBackupsupports:\n■ In non-FIPS mode, use 2048, 3072, 4096, and 8192 bits for key size.\n■ In FIPS mode, use only 2048 bits and 3072 bits for key size."
    },
    "6805": {
        "code": 6805,
        "desc": "The migration of NetBackup CA is not initiated.",
        "first_action": "Perform this operation when NetBackup CA migration is",
        "full_action": "Perform this operation when NetBackup CA migration is\nin progress and is in an appropriate phase. Refer to the NetBackup Security and\nEncryption Guide to learn more about CA migration phases."
    },
    "6806": {
        "code": 6806,
        "desc": "NetBackup CA with the given fingerprint does not exist.",
        "first_action": "Use RESTful API GET",
        "full_action": "Use RESTful API GET\n/security/certificate-authoritiesorusethenbseccmd -nbcalistcommand\nto get a list of all certificate authorities that NetBackup supports and to view their\nfingerprints."
    },
    "6807": {
        "code": 6807,
        "desc": "NetBackup CA with the given fingerprint cannot be decommissioned. A NetBackup CA should be in ABANDONED state to be decommissioned.",
        "first_action": "UseRESTful GET /security/certificate-authorities",
        "full_action": "UseRESTful GET /security/certificate-authorities\norusethenbseccmd -nbcalistcommandtogetalistofCertificateauthoritiesthat\nNetBackup supports and view the certificate authorities that are in the ABANDONED\nstate."
    },
    "6808": {
        "code": 6808,
        "desc": "The trust version does not exist.",
        "first_action": "Access the /security/trust-versions API to view the",
        "full_action": "Access the /security/trust-versions API to view the\ntrust versions from the database. Ensure that the trust version of the certificate\nexists."
    },
    "6809": {
        "code": 6809,
        "desc": "NetBackup CA with the given certificate does not exist.",
        "first_action": "Reason <reason> command to synchronize the NetBackup database and",
        "full_action": "Run the nbseccmd -nbcaMigrate -syncMigrationDB\n-reason <reason> command to synchronize the NetBackup database and\nNetBackup security services. If the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "6810": {
        "code": 6810,
        "desc": "The NetBackup CA migration summary cannot be retrieved.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6811": {
        "code": 6811,
        "desc": "The NetBackup CA migration is initiated; however, the CA migration status is incorrect. The expected CA migration status: INITIATED.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "6812": {
        "code": 6812,
        "desc": "Failed to retrieve the list of hosts that do not have the required CA certificates in their trust stores.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6813": {
        "code": 6813,
        "desc": "The activation phase of the NetBackup CA migration is to be started. The CA migration status should be INITIATED.",
        "first_action": "Ensure that the NetBackup CA migration status is",
        "full_action": "Ensure that the NetBackup CA migration status is\nINITIATED before the NetBackup CA is activated."
    },
    "6814": {
        "code": 6814,
        "desc": "TheactivationphaseoftheNetBackupCAmigrationiscomplete,however theCAmigrationstatusisincorrect.TheexpectedCAmigrationstatus:ACTIVATED.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "6815": {
        "code": 6815,
        "desc": "The completion phase of the NetBackup CA migration is started so the CA migration status should be ACTIVATED.",
        "first_action": "Ensure that the current NetBackup CA migration status",
        "full_action": "Ensure that the current NetBackup CA migration status\nis ACTIVATED before the NetBackup CA migration is completed."
    },
    "6816": {
        "code": 6816,
        "desc": "The NetBackup CA migration is complete, however the CA migration status is incorrect. The expected CA migration status: NO_MIGRATION. NetBackup status codes 850 NetBackup status codes",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "6817": {
        "code": 6817,
        "desc": "One or more hosts do not have the required CA certificates in their trust stores. Communication with these hosts may break. Rerun the command with the -force option to skip this validation.",
        "first_action": "Ensure that the NetBackup CAs are present in the trust stores of all hosts in the",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup CAs are present in the trust stores of all hosts in the\ndomain before activating the NetBackup CA migration. The trust is established\nautomatically for a NetBackup 8.2.1 or later host and can be verified using the\nRESTful API GET\n/security/certificate-authorities/hosts-pending-trust-propagation\northenbseccmd -nbcamigrate -hostspendingtrustpropagationcommand.\nVerify the trust propagation for NetBackup 8.2 or earlier hosts manually. The\nlistofCAsthatshouldbepresentinthetruststoreofthehostcanbelistedusing\nthe RESTful API GET /security/cacert.\n■ If you want to skip the validation, rerun the command with the -force option."
    },
    "6818": {
        "code": 6818,
        "desc": "Activating the newly set up NetBackup CA is successful, but NetBackup cannot retrieve the CA migration summary.",
        "first_action": "Run the nbseccmd -nbcaMigrate -summary command",
        "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigrationstatusisACTIVATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "6819": {
        "code": 6819,
        "desc": "The CA migration database cannot be updated with the current NetBackup CA certificate details.",
        "first_action": "Ensure that all NetBackup services are up and retry after",
        "full_action": "Ensure that all NetBackup services are up and retry after\nsome time. If the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "6820": {
        "code": 6820,
        "desc": "Failed to retrieve the list of hosts that require certificate renewal.",
        "first_action": "Ensure that all NetBackup services are up and retry the",
        "full_action": "Ensure that all NetBackup services are up and retry the\noperationaftersometime.Iftheissuepersists,visittheCohesityTechnicalSupport\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "6821": {
        "code": 6821,
        "desc": "One or more hosts have pending certificate renewals with the new CA. Communication with these hosts may break. Rerun the command with the -force option to skip this validation.",
        "first_action": "Ensure that all NetBackup hosts in the domain have their certificates signed by",
        "full_action": "Do the following, as appropriate:\n■ Ensure that all NetBackup hosts in the domain have their certificates signed by\nthe active NetBackup CA and can be verified using the RESTful API GET\n/config/hosts-pending-renewal or the nbseccmd -nbcamigrate\n-hostspendingrenewal command. Verify the certificates for NetBackup 8.2 or\nearlier hosts manually.\n■ If you want to skip the validation, rerun the command with the -force option."
    },
    "6822": {
        "code": 6822,
        "desc": "NewNetBackupCAmigrationcannotbeinitiatedbecausethemigration is currently activated.",
        "first_action": "Complete the current NetBackup CA migration and then",
        "full_action": "Complete the current NetBackup CA migration and then\ninitiate a new one."
    },
    "6823": {
        "code": 6823,
        "desc": "The NetBackup CA migration summary cannot be retrieved after the completion of migration.",
        "first_action": "Run the nbseccmd -nbcaMigrate -summary command",
        "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigration status is NO_MIGRATION. If you see different status, visit the Cohesity\nTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffersadditional\ninformation to help you troubleshoot this issue."
    },
    "6824": {
        "code": 6824,
        "desc": "TheNetBackupCAmigrationsummarycannotberetrievedafterinitiating the migration.",
        "first_action": "Run the nbseccmd -nbcaMigrate -summary command",
        "full_action": "Run the nbseccmd -nbcaMigrate -summary command\nto view the CA migration summary after some time. The expected NetBackup CA\nmigrationstatusisINITIATED.Ifyouseedifferentstatus,visittheCohesityTechnical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "6831": {
        "code": 6831,
        "desc": "None of the credential IDs map with the given credential name or ID.",
        "first_action": "Configure a credential with provided credential name or",
        "full_action": "Configure a credential with provided credential name or\nuse already configured credential ID or name."
    },
    "6832": {
        "code": 6832,
        "desc": "Multiple credential IDs map with the given credential name or ID.",
        "first_action": "Configure a credential with unique credential name and",
        "full_action": "Configure a credential with unique credential name and\nuse this credential for further operations."
    },
    "6833": {
        "code": 6833,
        "desc": "One or more credential configuration checks failed.",
        "first_action": "The certificate path is valid.",
        "full_action": "Ensure that the following pre-checks succeed for the\ncredential configuration or the update operation to succeed.\nThese checks are performed while the credential configuration operation is\nattempted:\n■ The certificate path is valid.\n■ The trust store path is valid.\n■ The private key path is valid.\n■ The certificates in certificate chain are readable.\n■ The certificates in trust store are readable.\n■ The private key is readable.\n■ The Common Name field is not empty.\n■ The certificate is not expired.\n■ The certificate is currently valid.\n■ The private key matches the certificate.\n■ The CRL directory consists of CRL files - This check is optional. It is performed\nif the ECA_CRL_PATH is configured with the path for the CRL directory.\n■ The CRL check level is valid - This check is optional. It is performed if the\nECA_CRL_PATH is configured with the path for the CRL directory and the CRL\ncheck level is anything but Disable.\n■ TheCRLpathisvalid-Thischeckisoptional.ItisperformediftheECA_CRL_PATH\nis configured with the path for the CRL directory and the CRL check level is\nanything but Disable."
    },
    "6882": {
        "code": 6882,
        "desc": "Deletion of a NetBackup Certificate Authority certificate is not allowed.",
        "first_action": "Ensure that the ECA certificate is enrolled on the host",
        "full_action": "Ensure that the ECA certificate is enrolled on the host\nbefore you attempt to delete the NBCA certificate. Verify that the domain is in pure\nECA mode before you attempt to delete the NBCA certificate of the primary server."
    },
    "7100": {
        "code": 7100,
        "desc": "The manifest file is not in the input data. Ensure that the manifest file is available.",
        "first_action": "Make sure that the manifest file is present in the input",
        "full_action": "Make sure that the manifest file is present in the input\ndata."
    },
    "7101": {
        "code": 7101,
        "desc": "Multiple manifest files exist in input data. Ensure that only one manifest file exists in the input data.",
        "first_action": "Remove the multiple manifest files in the input data.",
        "full_action": "Remove the multiple manifest files in the input data."
    },
    "7102": {
        "code": 7102,
        "desc": "The manifest file format is incorrect. Change the format and try again.",
        "first_action": "Check the manifest file format and correct if required as",
        "full_action": "Check the manifest file format and correct if required as\nper Sheltered Harbor specification."
    },
    "7103": {
        "code": 7103,
        "desc": "Account data files are not available. Ensure that the files are available.",
        "first_action": "Ensure that the account data files are present in the input",
        "full_action": "Ensure that the account data files are present in the input\ndata."
    },
    "7104": {
        "code": 7104,
        "desc": "Hash files are not present. Ensure that the files are available.",
        "first_action": "Ensure that the hash files are present in the input data.",
        "full_action": "Ensure that the hash files are present in the input data."
    },
    "7105": {
        "code": 7105,
        "desc": "Input data integrity validation has failed. Ensure that the data is correct.",
        "first_action": "Ensure that the input files are correct in the input data.",
        "full_action": "Ensure that the input files are correct in the input data."
    },
    "7106": {
        "code": 7106,
        "desc": "The file name format does not follow the proper naming convention. Correct the file name format and try again.",
        "first_action": "Make sure that provided input files are correct as per",
        "full_action": "Make sure that provided input files are correct as per\nSheltered Harbor specification."
    },
    "7107": {
        "code": 7107,
        "desc": "Invalid zip file. Try the operation again.",
        "first_action": "Makesurethattheprovidedinputdataisincorrectformat.",
        "full_action": "Makesurethattheprovidedinputdataisincorrectformat."
    },
    "7108": {
        "code": 7108,
        "desc": "The directory path that is specified for data restoration contains files or folders. Remove the existing contents from the directory path and try again.",
        "first_action": "Remove or move the files and or folder present in the",
        "full_action": "Remove or move the files and or folder present in the\ndirectory that was provided at the time of the restoration of data as the restored\ndata storage path. Retry the restore operation."
    },
    "7109": {
        "code": 7109,
        "desc": "Input data path does not exist. Provide the correct path and try again.",
        "first_action": "Ensure that the provided input path exists at the time of",
        "full_action": "Ensure that the provided input path exists at the time of\nbackup."
    },
    "7110": {
        "code": 7110,
        "desc": "The specified directory path is not valid.",
        "first_action": "Provide a valid pathname.",
        "full_action": "Provide a valid pathname."
    },
    "7112": {
        "code": 7112,
        "desc": "A call to the nbcryptocmd utility has timed out. Check the log file for more information.",
        "first_action": "By default, the time-out for the nbcryptocmd utility is 30",
        "full_action": "By default, the time-out for the nbcryptocmd utility is 30\nminutes. If you want to increase the time-out, contact the NetBackup administrator."
    },
    "7113": {
        "code": 7113,
        "desc": "The license validation failed.",
        "first_action": "Make sure that the given license parameter is correct as",
        "full_action": "Make sure that the given license parameter is correct as\nper Sheltered Harbor specification."
    },
    "7114": {
        "code": 7114,
        "desc": "The license has expired.",
        "first_action": "Get a new license from Sheltered Harbor and update the",
        "full_action": "Get a new license from Sheltered Harbor and update the\nlicense file with the new license parameters provided by Sheltered Harbor."
    },
    "7115": {
        "code": 7115,
        "desc": "The extension of the specified file is not supported. The file should have .json extension.",
        "first_action": "Provide a valid JSON file with the .json extension.",
        "full_action": "Provide a valid JSON file with the .json extension."
    },
    "7116": {
        "code": 7116,
        "desc": "Failed to create the transfer storage path. Check the log file for more information.",
        "first_action": "Ensure that the provided transfer storage path exists. Or,",
        "full_action": "Ensure that the provided transfer storage path exists. Or,\nverify that permissions are correct and create the transfer storage path."
    },
    "7117": {
        "code": 7117,
        "desc": "File does not exist. Check the log file for more information.",
        "first_action": "Ensure that the provided file exists at the given location.",
        "full_action": "Ensure that the provided file exists at the given location.\nCheck the nbshvault log for more information about the file."
    },
    "7118": {
        "code": 7118,
        "desc": "The JSON format is invalid. Enter the correct format and try again.",
        "first_action": "Make sure that JSON file format is correct.",
        "full_action": "Make sure that JSON file format is correct."
    },
    "7119": {
        "code": 7119,
        "desc": "The cryptographic material file format is incorrect. Contact your NetBackup administrator for assistance.",
        "first_action": "Make sure that cryptographic material file is in the correct",
        "full_action": "Make sure that cryptographic material file is in the correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator."
    },
    "7120": {
        "code": 7120,
        "desc": "The secure envelope file format is incorrect. Contact your NetBackup administrator for assistance.",
        "first_action": "Make sure that the secure envelope file is in the correct",
        "full_action": "Make sure that the secure envelope file is in the correct\nformatperShelteredHarborspecifications.Formoredetails,contacttheNetBackup\nadministrator for assistance."
    },
    "7121": {
        "code": 7121,
        "desc": "Database tables do not exist. Ensure that all the tables are available.",
        "first_action": "Contact the NetBackup administrator for more details.",
        "full_action": "Contact the NetBackup administrator for more details."
    },
    "7122": {
        "code": 7122,
        "desc": "Database error occurred. Check the log file for more information.",
        "first_action": "Contact the NetBackup administrator for more details.",
        "full_action": "Contact the NetBackup administrator for more details."
    },
    "7123": {
        "code": 7123,
        "desc": "The Sheltered Harbor compliance solution is not configured. Configure the solution using the --configure option. NetBackup status codes 861 NetBackup status codes",
        "first_action": "-configure option.",
        "full_action": "You need to configure the compliance solution using the\n--configure option."
    },
    "7125": {
        "code": 7125,
        "desc": "The platform is not supported.",
        "first_action": "Make sure to run the nbshvault utility on the NetBackup",
        "full_action": "Make sure to run the nbshvault utility on the NetBackup\nserver platforms."
    },
    "7126": {
        "code": 7126,
        "desc": "Data vaulting of the image in isolated recovery environment (IRE) is still in progress. Retry at a later time.",
        "first_action": "Retrythedatavaultingafterthecurrentoperationfinishes",
        "full_action": "Retrythedatavaultingafterthecurrentoperationfinishes\nusing the --attest option."
    },
    "7127": {
        "code": 7127,
        "desc": "The NetBackup version in the file path is not valid. Ensure that the NetBackup installation was successful.",
        "first_action": "Verify that NetBackup is installed properly. For more",
        "full_action": "Verify that NetBackup is installed properly. For more\ndetails, contact your NetBackup Administrator."
    },
    "7128": {
        "code": 7128,
        "desc": "ThebackupimageIDismissing.Checkthelogfileformoreinformation.",
        "first_action": "Retry the operation. If the issue persists, contact the",
        "full_action": "Retry the operation. If the issue persists, contact the\nNetBackup administrator."
    },
    "7129": {
        "code": 7129,
        "desc": "The institution ID does not match the manifest file data. Use the correct institution ID and try again.",
        "first_action": "You need to use the correct institution ID and try again.",
        "full_action": "You need to use the correct institution ID and try again."
    },
    "7130": {
        "code": 7130,
        "desc": "You are using an earlier version of NetBackup. Upgrade to the latest version.",
        "first_action": "You must run a NetBackup version that is 10.1 or higher.",
        "full_action": "You must run a NetBackup version that is 10.1 or higher."
    },
    "7131": {
        "code": 7131,
        "desc": "RegistrationresponseJSONisnotintheproperformat.Enterthecorrect format and try again.",
        "first_action": "Retry the Sheltered Harbor backup workflow. If the issue",
        "full_action": "Retry the Sheltered Harbor backup workflow. If the issue\npersists, contact the NetBackup administrator."
    },
    "7132": {
        "code": 7132,
        "desc": "Secure envelope was not found. Ensure that the secure envelope is available.",
        "first_action": "Ifthesecureenvelopeisnotfoundinthetransferstorage,",
        "full_action": "Ifthesecureenvelopeisnotfoundinthetransferstorage,\nyou can recheck the input data and run the backup operation again."
    },
    "7133": {
        "code": 7133,
        "desc": "Parameter is not in the secure envelope. Ensure that the parameter is available.",
        "first_action": "If the secure envelope JSON file parameter is not in the",
        "full_action": "If the secure envelope JSON file parameter is not in the\ntransfer storage path, you can recheck the file parameters and run the backup\noperation again."
    },
    "7134": {
        "code": 7134,
        "desc": "AttestationresponseJSONnotinproperformat.Enterthecorrectformat and try again.",
        "first_action": "Ensure that the solution is registered and the Ethereum",
        "full_action": "Ensure that the solution is registered and the Ethereum\nprivate key is created in proper format."
    },
    "7135": {
        "code": 7135,
        "desc": "The JSON input data does not match the respective JSON schema. Enter the correct format.",
        "first_action": "Make sure that the given JSON file format is correct as",
        "full_action": "Make sure that the given JSON file format is correct as\nper the JSON schema. You have to correct the JSON file format if the format is\nincorrect. Check the nbshvault log file for more information."
    },
    "7136": {
        "code": 7136,
        "desc": "Registration message posting of financial institution failed. Check the log file for more information.",
        "first_action": "Verify that Sheltered Harbor registration API is reachable",
        "full_action": "Verify that Sheltered Harbor registration API is reachable\nfrom the NetBackup client where nbshvault is running."
    },
    "7137": {
        "code": 7137,
        "desc": "Attestationmessagepostingfailed.Checkthelogfileformoreinformation.",
        "first_action": "VerifythattheShelteredHarborattestationAPIisreachable",
        "full_action": "VerifythattheShelteredHarborattestationAPIisreachable\nfrom the NetBackup client where nbshvault is running."
    },
    "7138": {
        "code": 7138,
        "desc": "No pending attestation found.",
        "first_action": "Retry the operation and if the issue persists, contact the",
        "full_action": "Retry the operation and if the issue persists, contact the\nNetBackup administrator."
    },
    "7139": {
        "code": 7139,
        "desc": "Failed to read key file. Ensure that the key file is available.",
        "first_action": "Verify that you have read access permissions to the",
        "full_action": "Verify that you have read access permissions to the\nvar/nbshvault/cert file where the Ethereum private key is created."
    },
    "7140": {
        "code": 7140,
        "desc": "Key file does not exist. Ensure that the key file is available.",
        "first_action": "Make sure that the Ether private key such as",
        "full_action": "Make sure that the Ether private key such as\n<Institution_ID_keys > JSON file is available in the var/nbshvault/cert/\ndirectory. If the institute is not registered, register it using the --register option."
    },
    "7141": {
        "code": 7141,
        "desc": "Private key does not exist. Ensure that the private key is available.",
        "first_action": "Verify that ether_pri_key is present in the",
        "full_action": "Verify that ether_pri_key is present in the\nvar/nbshvault/cert/<institution ID_keys>.json file."
    },
    "7142": {
        "code": 7142,
        "desc": "Recovery storage path does not exist. Provide the correct recovery storage path. NetBackup status codes 866 NetBackup status codes",
        "first_action": "Makesurethattheprovidedrecoverystoragepathexists.",
        "full_action": "Makesurethattheprovidedrecoverystoragepathexists."
    },
    "7143": {
        "code": 7143,
        "desc": "Failed to create restored data storage path. Check the log file for more information.",
        "first_action": "Verifythattherestoreddatastoragepathexistsandcheck",
        "full_action": "Verifythattherestoreddatastoragepathexistsandcheck\nif you have create permissions access."
    },
    "7144": {
        "code": 7144,
        "desc": "Archivevolumeisnotpresent.Ensurethatthearchivevolumeisavailable.",
        "first_action": "Verify that the archive volume exists.",
        "full_action": "Verify that the archive volume exists."
    },
    "7146": {
        "code": 7146,
        "desc": "Failed to extract compressed volume. Check the log file for more information.",
        "first_action": "Verifythattheencryptedcompressedvolumesarerestored",
        "full_action": "Verifythattheencryptedcompressedvolumesarerestored\ncorrectly. Restore the data again and then retry the operation."
    },
    "7147": {
        "code": 7147,
        "desc": "The exit code is not valid. Check the log file for more information.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "7148": {
        "code": 7148,
        "desc": "Unabletoaccessrestoreddatastoragepath.Checkthelogfileformore information.",
        "first_action": "Verify that you have the read and write access to the",
        "full_action": "Verify that you have the read and write access to the\nrestored data storage path."
    },
    "7149": {
        "code": 7149,
        "desc": "The -path option is not present in the --generate-template. Provide the correct path using the -path option.",
        "first_action": "Make sure to use --generate-template -path <path>",
        "full_action": "Make sure to use --generate-template -path <path>\noption to generate templates."
    },
    "7151": {
        "code": 7151,
        "desc": "The NetBackup configuration file cannot be read. Check the log file for more information.",
        "first_action": "Make sure that you have read and write access to the",
        "full_action": "Make sure that you have read and write access to the\nvar/nbshvault/config folder."
    },
    "7152": {
        "code": 7152,
        "desc": "Failed to generate the template. Check the log file for more information.",
        "first_action": "Make sure that you have the read and write access to the",
        "full_action": "Make sure that you have the read and write access to the\npath provided with --path option."
    },
    "7153": {
        "code": 7153,
        "desc": "Unknown error.",
        "first_action": "You need to review the nbshvault logs to see a detailed",
        "full_action": "You need to review the nbshvault logs to see a detailed\nerror message. For more information, contact the NetBackup administrator."
    },
    "7154": {
        "code": 7154,
        "desc": "FailedtoreadtheinstallationdirectoryfromtheNetBackupconfiguration file. For more details, contact your NetBackup Administrator.",
        "first_action": "For more details, contact the NetBackup administrator.",
        "full_action": "For more details, contact the NetBackup administrator."
    },
    "7155": {
        "code": 7155,
        "desc": "NoKMSisenabledduringtheShelteredHarborcomplianceconfiguration. NetBackup status codes 869 NetBackup status codes",
        "first_action": "IfKMSconfigurationisnotenabled,usethe--configure",
        "full_action": "IfKMSconfigurationisnotenabled,usethe--configure\noption to update the Sheltered Harbor compliance configuration."
    },
    "7156": {
        "code": 7156,
        "desc": "Archive generation has timed out.",
        "first_action": "By default, the archive generation time out is 30 minutes.",
        "full_action": "By default, the archive generation time out is 30 minutes.\nTo increase the time-out, change the archive_generation time-out option in the\nconfigure.json file and use this file to configure the solution."
    },
    "7157": {
        "code": 7157,
        "desc": "Archive repository backup has timed out.",
        "first_action": "By default, the archive repository time-out is 30 minutes.",
        "full_action": "By default, the archive repository time-out is 30 minutes.\nTo increase the time-out, change the archive_repository time-out option in the\nconfigure.json file and use this file to configure the solution."
    },
    "7158": {
        "code": 7158,
        "desc": "Vaulting attestation has timed out.",
        "first_action": "By default, the vaulting attestation time-out is 30 minutes.",
        "full_action": "By default, the vaulting attestation time-out is 30 minutes.\nTo increase the time-out, change the vaulting_attestation time-out in the\nconfigure.json file and use this file to configure the solution."
    },
    "7159": {
        "code": 7159,
        "desc": "Daily backup workflow process has timed out.",
        "first_action": "By default, the daily backup workflow process time out is",
        "full_action": "By default, the daily backup workflow process time out is\n120minutes.Toincreasethetime-out,changethedaily_backup_processtime-out\nin the configure.json file and use this file to configure the solution."
    },
    "7160": {
        "code": 7160,
        "desc": "Restore workflow process has timed out.",
        "first_action": "By default, the restore workflow process time-out is 120",
        "full_action": "By default, the restore workflow process time-out is 120\nminutes. To increase the time-out, change the restore_process time-out in the\nconfigure.json file and use this file to configure the solution."
    },
    "7161": {
        "code": 7161,
        "desc": "Air gap image replication has timed out.",
        "first_action": "By default, the restore workflow process time-out is 30",
        "full_action": "By default, the restore workflow process time-out is 30\nminutes. To increase the time-out, change the air_gap_timeout time-out in the\nconfigure.json file and use this file to configure the solution."
    },
    "7162": {
        "code": 7162,
        "desc": "The attestation private key size is not correct.",
        "first_action": "The attestation private key size is expected to be 256-bit.",
        "full_action": "The attestation private key size is expected to be 256-bit.\nIf the institution ID is already registered with Sheltered Harbor, import the private\nkey that was used at the time of registration using the --import-key option and\nretry."
    },
    "7163": {
        "code": 7163,
        "desc": "The institution ID is incorrect.",
        "first_action": "You need to use the 10-digit institution ID provided by",
        "full_action": "You need to use the 10-digit institution ID provided by\nSheltered Harbor."
    },
    "7164": {
        "code": 7164,
        "desc": "The registration key is incorrect. Ensure that the correct registration key is provided.",
        "first_action": "You need to use the valid registration key provided by",
        "full_action": "You need to use the valid registration key provided by\nSheltered Harbor."
    },
    "7165": {
        "code": 7165,
        "desc": "An internal error occurred. Check the nbcryptocmd logs.",
        "first_action": "Review the nbcryptocmd logs to diagnose the problem.",
        "full_action": "Review the nbcryptocmd logs to diagnose the problem."
    },
    "7166": {
        "code": 7166,
        "desc": "The authentication fails during connection to the cloud KMS.",
        "first_action": "Review the cloud KMS configuration parameters of",
        "full_action": "Review the cloud KMS configuration parameters of\nnbshvault and verify if they are correct."
    },
    "7167": {
        "code": 7167,
        "desc": "The cloud KMS operation failed. Check the nbcryptocmd logs.",
        "first_action": "Review the nbcryptocmd logs to diagnose the problem.",
        "full_action": "Review the nbcryptocmd logs to diagnose the problem."
    },
    "7168": {
        "code": 7168,
        "desc": "Another instance of the same operation is in progress. Retry at a later time.",
        "first_action": "You must wait until the first running process completes",
        "full_action": "You must wait until the first running process completes\nand then retry the operation."
    },
    "7200": {
        "code": 7200,
        "desc": "Execution of nbinstallagent in the remote host failed.",
        "first_action": "On Windows:",
        "full_action": "Review the media server admin log at the following\nlocations:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\admin\\root*.log\n■ On UNIX and Linux:\n/usr/openv/netbackup/logs/admin/root*.log"
    },
    "7201": {
        "code": 7201,
        "desc": "The file name is not provided.",
        "first_action": "On Windows:",
        "full_action": "Review the Job Manager log at the following locations to\nensure that the file_name option is not empty:\n■ On Windows:\ninstall_path\\NetBackup\\logs\\nbjm\n■ On UNIX and Linux:\n/usr/openv/logs/nbjm"
    },
    "7202": {
        "code": 7202,
        "desc": "Unable to retrieve NetBackup version from the remote host.",
        "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost",
        "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server."
    },
    "7203": {
        "code": 7203,
        "desc": "Unable to retrieve platform information from the remote host.",
        "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost",
        "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server."
    },
    "7204": {
        "code": 7204,
        "desc": "Remote host name not specified.",
        "first_action": "Review the Job Manager log at the following locations to",
        "full_action": "Review the Job Manager log at the following locations to\nensure that the hostname option is not empty:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX and Linux: /usr/openv/logs/nbjm"
    },
    "7205": {
        "code": 7205,
        "desc": "Unable to retrieve NetBackup install directory from the remote host.",
        "first_action": "Ensurethatthebpcdserviceisrunningintheremotehost",
        "full_action": "Ensurethatthebpcdserviceisrunningintheremotehost\nand it has connectivity to the media server. Ensure that NetBackup is properly\ninstalled.Confirmthatrecentbackupsransuccessfully.Runatestbackup.Confirm\nthat the version of NetBackup being upgraded is supported. For more information,\nplease see the NetBackup Upgrade Guide."
    },
    "7206": {
        "code": 7206,
        "desc": "Failed to transfer a file to the remote host.",
        "first_action": "Ensurethatthebpcdserviceisrunningintheremotehostandithasconnectivity",
        "full_action": "Perform the following as appropriate:\n■ Ensurethatthebpcdserviceisrunningintheremotehostandithasconnectivity\nto the media server.\n■ Ensure that NetBackup is properly installed.\n■ Confirm that recent backups ran successfully.\n■ Run a test backup.\n■ Confirm that the version of NetBackup being upgraded is supported.\n■ Verify that the transfer file exists and has the proper permissions.\n■ Identify the file being transferred by reviewing the admin logs on the server\nand the nbinstallagent logs on the target host.\n■ Confirm that the file exists in its expected location and that the source and\nthe destination locations have appropriate permissions."
    },
    "7207": {
        "code": 7207,
        "desc": "Unable to receive the data from the client.",
        "first_action": "Review the media server admin log as well as the client",
        "full_action": "Review the media server admin log as well as the client\nnbinstallagent log at the following locations:\nOn Windows: install_path\\NetBackup\\logs\\admin\\root*.log.\nOn UNIX: /usr/openv/netbackup/logs/admin/root*.log\nOn Windows: install_path\\NetBackup\\logs\\nbinstallagent\nOn UNIX: /usr/openv/netbackup/logs/nbinstallagent\nValidate connectivity between the target host and the staging host. Note that the\nstaging host may be the master server or a media server that is named in the\ndeployment operation.\nTo configure the amount of time VxUpdate waits for processes to finish before\nreporting 7207 as the job status, you can define the TIMEOUT_SECONDS option. The\nfollowingvaluescanbedefinedintheNetBackupconfigurationonthemasterserver:\nVXUPDATE_CLIENT_READ_TIMEOUT_SECONDS This value controls how long precheck\noperations and client upgrade operations\nare allowed to take, in seconds. The\ndefault value is 1800 (30 minutes). It can\nbe decreased to as little as 600 (10\nminutes)orincreasedtoasmuchas3600\n(60 minutes).\nVXUPDATE_SERVER_READ_TIMEOUT_SECONDS This value controls how long server\nupgrade operations are allowed to take,\nin seconds. The default value is 2700 (45\nminutes). It can be decreased to as little\nas 600 (10 minutes) or increased to as\nmuch as 5400 (90 minutes).\nFor details on how the bpsetconfig command can be used to add values to the\nNetBackup configuration of a master server, see the NetBackup Commands\nReference Guide."
    },
    "7208": {
        "code": 7208,
        "desc": "A required file cannot be opened.",
        "first_action": "NetBackup tmp",
        "full_action": "Verify that the user that is running the nbmtrans media\nserver process has permission to read the files in the NetBackup directories. Users\nmust have read permissions to the following directories:\n■ NetBackup tmp\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX and Linux: /usr/openv/tmp\n■ NetBackup bin\nOn Windows: install_path\\NetBackup\\bin\nOn UNIX and Linux: /usr/openv/netbackup/bin\n■ NetBackup repo\nOn Windows: install_path\\NetBackup\\var\\global\\repo\nOn UNIX and Linux: /usr/openv/var/global/repo"
    },
    "7209": {
        "code": 7209,
        "desc": "The deployment package was not found or was invalid in the cache media server.",
        "first_action": "Ensure that the package exists in the package repository",
        "full_action": "Ensure that the package exists in the package repository\non the master server. As part of the error handling process, VxUpdate attempts to\nremove the invalid or the corrupted package and replace it with the valid package."
    },
    "7210": {
        "code": 7210,
        "desc": "Unable to write to the specified file.",
        "first_action": "Ensure that the directory has the correct permission.",
        "full_action": "Ensure that the directory has the correct permission.\nNetBackup requires write and execute permissions for the target file."
    },
    "7211": {
        "code": 7211,
        "desc": "Failed to convert NetBackup version string.",
        "first_action": "The version string that is returned from the remote host",
        "full_action": "The version string that is returned from the remote host\nwas not properly formatted. Please connect to the remote host and verify that\nNetBackup is installed properly."
    },
    "7212": {
        "code": 7212,
        "desc": "The nbinstallagent command has executed with an empty argument.",
        "first_action": "Review the Job Manager log at the following locations to",
        "full_action": "Review the Job Manager log at the following locations to\nensure that execute_nbinstallagent has the correct arguments:\nOn Windows: install_path\\NetBackup\\logs\\nbjm\nOn UNIX: /usr/openv/logs/nbjm"
    },
    "7213": {
        "code": 7213,
        "desc": "Unable to identify remote host platform.",
        "first_action": "Win_x64",
        "full_action": "Ensure that the remote host has a supported version of\nNetBackup.\nFrom a NetBackup master or media server, run\n<install_path>/netbackup/bin/adminincmd/bptestbpcd -client <target\nhost name> -verbose. Review the PLATFORM key that this command returns. This\ntarget host cannot be upgraded if the PLATFORM key value is not in the following list:\n■ win_x64\n■ linuxR_x86_2.6.18\n■ linuxR_x86_2.6.32\n■ linuxR_x86_3.10.0\n■ linuxR_x86_4.18.0\n■ linuxS_x86_2.6.16\n■ linuxS_x86_3.0.76\n■ linuxS_x86_4.4.73\n■ plinuxR_3.10.0\n■ plinuxR_4.18.0\n■ plinuxS_4.4.21\n■ plinuxS_5.3.18\n■ zlinuxR_2.6.18\n■ zlinuxR_2.6.32\n■ zlinuxR_3.10.0\n■ zlinuxR_4.18.0\n■ zlinuxS_3.0.76\n■ zlinuxS_4.4.\n■ zlinuxS_5.3.18\n■ rs6000_71\n■ solaris10\n■ solaris_x86_10_64"
    },
    "7214": {
        "code": 7214,
        "desc": "Failed to copy the specified file.",
        "first_action": "Read permissions on the source file.",
        "full_action": "Confirm that the directory has the correct permissions.\nNetBackup requires the following permissions:\n■ Read permissions on the source file.\n■ Read and execute permissions on the source directory.\n■ Execute and write permissions on the target directory.\nConfirm that there is enough available disk space at the file copy destination.\nFor more information, see the nbrepo log on the master server and the admin log\non the staging server at the following locations:\nOn Windows: install_path\\NetBackup\\logs.\nOn UNIX: /usr/openv/netbackup/logs"
    },
    "7215": {
        "code": 7215,
        "desc": "Failed to stat VxUpdate package",
        "first_action": "Confirm that the package has originated from a Cohesity",
        "full_action": "Confirm that the package has originated from a Cohesity\nsourceandhasnotbeenalteredorcorrupted.Reviewthenbrepologonthemaster\nserver for more information."
    },
    "7216": {
        "code": 7216,
        "desc": "The package name does not comply with VxUpdate package name standard.",
        "first_action": "Confirm that the package name has not been modified.",
        "full_action": "Confirm that the package name has not been modified.\nView the nbrepo log for details."
    },
    "7217": {
        "code": 7217,
        "desc": "The package repository location does not exist.",
        "first_action": "Confirmthattherepositorydirectoryexistsatthefollowing",
        "full_action": "Confirmthattherepositorydirectoryexistsatthefollowing\nlocations:\nOn Windows: install_path\\var\\global\\repo\nOn UNIX: /usr/openv/var/global/repo"
    },
    "7218": {
        "code": 7218,
        "desc": "The package already exists in the repository.",
        "first_action": "Confirm that the package that you want to add has not",
        "full_action": "Confirm that the package that you want to add has not\nalready been added. To replace this package, first delete it using the nbrepo -d\ncommand."
    },
    "7219": {
        "code": 7219,
        "desc": "Invalid package ID",
        "first_action": "The package ID must be a positive integer. Confirm that",
        "full_action": "The package ID must be a positive integer. Confirm that\nthe package ID is correct by using the nbrepo -l command."
    },
    "7220": {
        "code": 7220,
        "desc": "The deployment package was not found in the package repository.",
        "first_action": "Use the nbrepo -l command to list the packages that",
        "full_action": "Use the nbrepo -l command to list the packages that\nare currently in the repository."
    },
    "7221": {
        "code": 7221,
        "desc": "The package delete operation was canceled.",
        "first_action": "To delete a package, the user must confirm the delete.",
        "full_action": "To delete a package, the user must confirm the delete."
    },
    "7222": {
        "code": 7222,
        "desc": "The package was not found.",
        "first_action": "Required VxUpdate package was not found on the master server.",
        "full_action": "Confirm that the package exists in the repository. Confirm\nthat the package being installed has not been modified from its original form.\nWhen a VMware or Nutanix AHV agentless restore is performed, the restore can\ncause one of the following issues:\n■ Required VxUpdate package was not found on the master server.\nProvision VxUpdate packages for all platforms for which you have virtual\nmachines where you want to perform agentless recovery. Review the bpVMutil\nlog for additional assistance with this error message.\nReview the following if the failure is during a deployment or a MongoDB job:\n■ For a deployment job, review the nbrepo, admin, and nbinstallagent logs for\nadditional assistance with this error message.\n■ For MongoDB jobs, review the mongoDB logs for additional assistance with this\nerror message."
    },
    "7223": {
        "code": 7223,
        "desc": "The requested operation is not supported.",
        "first_action": "See the NetBackup Upgrade Guide for information about",
        "full_action": "See the NetBackup Upgrade Guide for information about\nthe supported operations and platforms for VxUpdate."
    },
    "7224": {
        "code": 7224,
        "desc": "Could not create a required file or directory.",
        "first_action": "On Windows:",
        "full_action": "The specific file and path are reported in the\nnbinstallagent log file on the target host or the admin log on the staging host.\nThenbinstallagentbinaryrequirestheabilitytocreatetemporaryfilesandfolders\nin both the NetBackup tmp and NetBackup bin directories.\nThe nbmtrans binary requires the ability to create files in the NetBackup repo\ndirectory.\nSee the following locations:\n■ On Windows:\ninstall_path\\NetBackup\\Temp\ninstall_path\\NetBackup\\bin\ninstall_path\\NetBackup\\var\\global\\repo\n■ On UNIX:\n/usr/openv/tmp\n/usr/openv/netbackup/bin\n/usr/openv/var/global/repo\nVerify that the user executing the nbinstallagent and nbmtrans commands has\npermissiontocreatefilesandfoldersinthesedirectories.Verifythatthereissufficient\ndisk space in these directories."
    },
    "7225": {
        "code": 7225,
        "desc": "A specified file or directory was not found.",
        "first_action": "Confirmthatthefileexistsinthelocationspecified.Confirm",
        "full_action": "Confirmthatthefileexistsinthelocationspecified.Confirm\nthatthepackagebeinginstalledhasnotbeenmodifiedfromitsoriginalform.Confirm\nthat the NetBackup installation folder has not been corrupted.\nReview the nbinstallagent, nbrepo, and admin log files for information about the\nproblematic files and their expected locations."
    },
    "7226": {
        "code": 7226,
        "desc": "A supporting command failed.",
        "first_action": "Nbcheck.exe (the NetBackup preinstall environment checker)",
        "full_action": "The nbinstallagent binary runs many commands as\npart of supporting various operations, including the following:\n■ nbcheck.exe (the NetBackup preinstall environment checker)\n■ The NetBackup EEB installer\n■ NetBackup’s versioninfo command in the goodies folder\n■ UNIX native packaging commands - rpm, installp, pkgadd, and swinstall.\n■ setup.exe - the NetBackup Windows setup utility\n■ gunzip - the UNIX tar uncompression utility\nThe nbinstallagent logic reports the specific command that failed to execute.\nThisspecificerrorindicatesthatthecommanditselfcannotbeexecutedsuccessfully,\nwhich can be different than the command executing successfully but returning an\nerror.Possiblecausesincludepermissionsissuesandfilesorfoldersunexpectedly\nabsent from the remote host. Review the nbinstallagent log file on the target\nhost."
    },
    "7227": {
        "code": 7227,
        "desc": "Cannot open nbinstallagent log file.",
        "first_action": "Verify that the user executing the nbinstallagent binary",
        "full_action": "Verify that the user executing the nbinstallagent binary\nhas permission to write to NetBackup's log folder. Verify that there is sufficient disk\nspace on the system."
    },
    "7228": {
        "code": 7228,
        "desc": "Installation of the target package was unsuccessful.",
        "first_action": "Review the installation log for the target package.",
        "full_action": "Review the installation log for the target package.\nWhen you install NetBackup packages for UNIX, the installation log is located at\n/usr/openv/tmp.\nWhen you install NetBackup packages for Windows, the installation log is located\nat %ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs.\nFor additional information on installing EEBs as well as logs from the EEB\ninstallation, see the related article:\nhttps://www.veritas.com/support/en_US/article.100019405"
    },
    "7229": {
        "code": 7229,
        "desc": "Couldnotcopynbinstallagenttodestinationpathaspartofself-update process.",
        "first_action": "Verify that the user executing nbinstallagent has",
        "full_action": "Verify that the user executing nbinstallagent has\npermission to write to the NetBackup directories. Verify that there is sufficient disk\nspace on the system."
    },
    "7230": {
        "code": 7230,
        "desc": "Could not execute nbinstallagent from new path.",
        "first_action": "Verify that the user executing the nbinstallagent binary",
        "full_action": "Verify that the user executing the nbinstallagent binary\nhas permission to execute files within the NetBackup directories."
    },
    "7231": {
        "code": 7231,
        "desc": "Could not open a required registry key.",
        "first_action": "Verifythattheuserexecutingthebinaryhasadministrative",
        "full_action": "Verifythattheuserexecutingthebinaryhasadministrative\nprivileges. Verify that NetBackup’s registry information at\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup is not corrupt or missing."
    },
    "7232": {
        "code": 7232,
        "desc": "Could not query registry value.",
        "first_action": "Verify that the user executing the nbinstallagent and",
        "full_action": "Verify that the user executing the nbinstallagent and\nnbhostdbcmdbinarieshasadministrativeprivileges.VerifythatNetBackup’sregistry\ninformationatHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackupisnotcorrupt\nor missing."
    },
    "7233": {
        "code": 7233,
        "desc": "Could not resolve the path to a NetBackup directory.",
        "first_action": "Verify that the user executing the nbinstallagent binary",
        "full_action": "Verify that the user executing the nbinstallagent binary\nhasreadprivilegesontheNetBackupapplicationfolders.VerifythattheNetBackup\napplication folder is not corrupt or missing."
    },
    "7234": {
        "code": 7234,
        "desc": "Could not remove the nbinstallagent binary’s configuration file.",
        "first_action": "Windows:",
        "full_action": "Verify that the user executing the nbinstallagent binary\nhas write privileges on NetBackup’s application folders. The nbinstallagent\nconfiguration information resides in NetBackup’s tmp directory and is named\nnbinstallagent_conffile.\nLocation of tmp directory:\n■ Windows:\ninstall_path\\NetBackup\\Temp\n■ UNIX:\n/usr/openv/tmp"
    },
    "7235": {
        "code": 7235,
        "desc": "Failed to open or extract a package.",
        "first_action": "The specific file that cannot be operated on is reported in",
        "full_action": "The specific file that cannot be operated on is reported in\nthe nbinstallagent or nbrepo log file. Confirm that the package exists in the\nrequired location. Confirm that the package being installed has not been modified\nfrom its original form. Verify that the user executing the nbinstallagent binary\nhasreadandwritepermissionsforNetBackup'sapplicationfolders.Verifythatthere\nis sufficient disk space on the system."
    },
    "7236": {
        "code": 7236,
        "desc": "The package signature is invalid.",
        "first_action": "Confirm that the package has come from a legitimate",
        "full_action": "Confirm that the package has come from a legitimate\nCohesity source and has not been altered or manipulated."
    },
    "7237": {
        "code": 7237,
        "desc": "The public key was not found at the expected location.",
        "first_action": "The default location for the public key is at the following",
        "full_action": "The default location for the public key is at the following\nlocations:\nOn Windows: install_path\\NetBackup\\var\\VxUpdate\\pubkey.pem\nOn UNIX and Linux: /usr/openv/var/global/vxupdate/pubkey.pem\nThis file is included with the NetBackup Client and the NetBackup server 8.1.2 and\nlater packages. Verify that the user executing the nbinstallagent, nbrepo, and\nbpvmutil binaries have read privileges for NetBackup’s application folders. Verify\nthat NetBackup’s application folders are not corrupt or missing."
    },
    "7238": {
        "code": 7238,
        "desc": "Windows socket initialization was unsuccessful.",
        "first_action": "This error is a sign of a socket or networking issue on the",
        "full_action": "This error is a sign of a socket or networking issue on the\nremotehost.Formoreinformation,seetheMSDNdocumentationforWSAStartup()\nat the following location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup"
    },
    "7239": {
        "code": 7239,
        "desc": "Exceeded time-out waiting for Windows socket initialization.",
        "first_action": "Thenbinstallagentbinarywaitsamaximumof2minutes",
        "full_action": "Thenbinstallagentbinarywaitsamaximumof2minutes\nfor the socket initialization to complete. This error is from a socket or networking\nissue on the remote host. For more information, see the MSDN documentation for\nWSAStartup() at the following location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup"
    },
    "7240": {
        "code": 7240,
        "desc": "The Winsock version is unsupported.",
        "first_action": "This error is from a socket or networking issue on the",
        "full_action": "This error is from a socket or networking issue on the\nremotehost.ItmaybeasymptomofattemptingtouseVxUpdateonanunsupported\nversion of Windows. For more information, see the MSDN documentation for\nWSAStartup() and, specifically, the WSAVERNOTSUPPORTED return code at the\nfollowing location:\nhttps://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-wsastartup"
    },
    "7241": {
        "code": 7241,
        "desc": "Could not initialize socket.",
        "first_action": "This error can happen if an operating system function to",
        "full_action": "This error can happen if an operating system function to\naccess or change the settings for the standard output socket is unsuccessful. The\nnbinstallagent log file reports the specific operating system call that failed, along\nwith an OS-specific error code."
    },
    "7242": {
        "code": 7242,
        "desc": "Failed to add package to the repository.",
        "first_action": "Review the nbwebservice log for related messages and",
        "full_action": "Review the nbwebservice log for related messages and\nadditional details. Confirm the package (.sja file) is not corrupted and came from\na legitimate source. Confirm that a user with appropriate privileges performed the\nVxUpdate operation. Confirm there is adequate disk space on the drive or volume\nwhere the NetBackup application folder resides."
    },
    "7243": {
        "code": 7243,
        "desc": "Temporary files cannot be removed from the system.",
        "first_action": "Thenbinstallagentbinaryattemptstocleanupthetemp",
        "full_action": "Thenbinstallagentbinaryattemptstocleanupthetemp\nfiles at the beginning and the end of its execution. Verify that the user executing\nnbinstallagenthasreadandwritepermissionsforNetBackup'sapplicationfolders.\nVerify that other system processes do not maintain handles to NetBackup files.\nOn Windows: install_path\\NetBackup\\Temp\nOn UNIX and Linux: /usr/openv/tmp"
    },
    "7245": {
        "code": 7245,
        "desc": "An unsupported self-update operation was attempted.",
        "first_action": "Verify that the NetBackup application folder is in a clean",
        "full_action": "Verify that the NetBackup application folder is in a clean\nstate. If the nbinstallagent cannot clean up temporary files as part of previous\noperations, the failure to remove leftover temporary files may be responsible for\nthis error."
    },
    "7246": {
        "code": 7246,
        "desc": "An unsupported registry query was attempted.",
        "first_action": "This error can happen if a NetBackup registry value was",
        "full_action": "This error can happen if a NetBackup registry value was\nmodified from its original type to another type. For example, if a user changed\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\INSTALLDIR\nfromaREG_SZtype(string)toREG_DWORD(integer).ConfirmthatNetBackup'sregistry\nhas not been altered or corrupted."
    },
    "7247": {
        "code": 7247,
        "desc": "Could not open a pipe to capture command output.",
        "first_action": "Verify that the user executing the nbinstallagent or",
        "full_action": "Verify that the user executing the nbinstallagent or\nnbhostdbcmd binaries has administrative privileges."
    },
    "7248": {
        "code": 7248,
        "desc": "The NetBackup command to retrieve version information is not present.",
        "first_action": "The default location for the versioninfo command is at",
        "full_action": "The default location for the versioninfo command is at\nthe following locations:\nOn Windows: install_path\\NetBackup\\bin\\goodies\\versioninfo.exe\nOn UNIX: /usr/openv/netbackup/bin/goodies/support/versioninfo\nConfirm that NetBackup’s application folder has not been altered or corrupted."
    },
    "7249": {
        "code": 7249,
        "desc": "Could not open process for reading.",
        "first_action": "The nbinstallagent found a NetBackup process to be",
        "full_action": "The nbinstallagent found a NetBackup process to be\nrunning, but cannot open it for further processing. Verify that the user executing\nthe nbinstallagent binary has administrative privileges. Verify that the existing\nNetBackup processes are running under the expected user accounts."
    },
    "7250": {
        "code": 7250,
        "desc": "Process status cannot be determined.",
        "first_action": "Verify that the user executing the nbinstallagent or",
        "full_action": "Verify that the user executing the nbinstallagent or\nnbhostdbcmd binaries have administrative privileges. Verify that the existing\nNetBackup processes are running under the expected user accounts. Review the\nnbinstallagent and nbhostdbcmd log files to determine what command was run\nand its output."
    },
    "7251": {
        "code": 7251,
        "desc": "Process cannot be stopped.",
        "first_action": "A particular NetBackup process cannot be terminated.",
        "full_action": "A particular NetBackup process cannot be terminated.\nThe nbinstallagent log file reports the specific process. Verify that the user\nexecuting the nbinstallagent binary has administrative privileges. Verify that the\nexisting NetBackup processes are running under the expected user accounts."
    },
    "7252": {
        "code": 7252,
        "desc": "The attempt to extract a package was unsuccessful.",
        "first_action": "Theissuecanoccurinbothnbinstallagentandnbrepo.",
        "full_action": "Theissuecanoccurinbothnbinstallagentandnbrepo.\nReview the associated log files for the name of the problematic file and other\ninformation.VerifythattheuserhaswritepermissionsfortheNetBackupapplication\nfoldersonthemasterserverandtargethost.Verifythatthereissufficientdiskspace\non the master server and target."
    },
    "7253": {
        "code": 7253,
        "desc": "The package is empty.",
        "first_action": "Confirm that the package originated from a Cohesity",
        "full_action": "Confirm that the package originated from a Cohesity\nsource and has not been altered or corrupted."
    },
    "7254": {
        "code": 7254,
        "desc": "Data in process was formatted incorrectly.",
        "first_action": "The prechecker uses this size as part of its disk space",
        "full_action": "The prechecker uses this size as part of its disk space\nreview. This particular status code indicates that the content of the package_sizes\nfile is in an unexpected format. Confirm that the prechecker package originated\nfrom a Cohesity source and has not been altered or corrupted."
    },
    "7255": {
        "code": 7255,
        "desc": "A supporting command’s output was in an unexpected format.",
        "first_action": "Review the nbinstallagent logs to determine which",
        "full_action": "Review the nbinstallagent logs to determine which\ncommand produced the unexpected output."
    },
    "7256": {
        "code": 7256,
        "desc": "Could not get the current working directory path.",
        "first_action": "Collectthenbinstallagentlogsatthefollowinglocations",
        "full_action": "Collectthenbinstallagentlogsatthefollowinglocations\nfor the remote host:\nOn Windows: install_path\\NetBackup\\logs\nOn UNIX and Linux: /usr/openv/netbackup/logs\nSave all logs and contact Cohesity Technical Support."
    },
    "7258": {
        "code": 7258,
        "desc": "Could not determine the state of security certificates on the local host.",
        "first_action": "Review the nbinstallagent log for a copy of the exact",
        "full_action": "Review the nbinstallagent log for a copy of the exact\ncommand line executed, its return status, and its output. Consult the NetBackup\nCommand Reference Guide for information on the specific error."
    },
    "7259": {
        "code": 7259,
        "desc": "The deployment policy's external CA certificate configuration specifications are invalid for this host.",
        "first_action": "For Windows, the nbcertcmdtool logs are located in the normal install log",
        "full_action": "For more details about this error, examine the\nnbcertcmdtoollogs.Thenbinstallagentlogreportsthenbcertcmdtoolcommand\nline arguments and output.\n■ For Windows, the nbcertcmdtool logs are located in the normal install log\nlocation (which defaults to\n%ALLUSERSPROFILE%\\Veritas\\NetBackup\\InstallLogs). A separate file is\ncreated for each command run and the files you want to review are prefixed\nwith ExternalCertificateOp.\n■ For UNIX, these are in /usr/openv/tmp/ and the name is prefixed with\ninstall_commands. The PID is appended and for example, a file name can be\n/usr/openv/tmp/install_commands.47832\nFor more information, see the NetBackup API Reference Guide.\nReview the external CA certificate values that are defined in the deployment policy\n(or the nbinstallcmd command line) to ensure that they apply to the target host.\nReview the nbinstallagent log for a record of the NetBackup command that is\nexecuted to resolve the external CA certificate. Review the NetBackup Security\nand Encryption Guide for more information on how to configure a NetBackup\nenvironment for use with external CA certificates."
    },
    "7260": {
        "code": 7260,
        "desc": "CouldnotparsetheJSONstringtoretrievetheexternalcertificatevalues.",
        "first_action": "Review the admin log on the media server (or master",
        "full_action": "Review the admin log on the media server (or master\nserver if a media server was not used) for additional information. In the JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\nand non-English characters. Review NetBackup documentation for details on\nsupported characters in policy values."
    },
    "7261": {
        "code": 7261,
        "desc": "Could not load the JSON string.",
        "first_action": "Review the admin log on the media server (or master",
        "full_action": "Review the admin log on the media server (or master\nserver if a media server was not used) for additional information. In the JSON\nreferencedthere,lookforcommonoffenders-pathswithspaces,excessivequotes,\nand non-English characters. Review NetBackup documentation for details on\nsupported characters in policy values."
    },
    "7262": {
        "code": 7262,
        "desc": "Could not determine the CA certificate type that is configured on the master server.",
        "first_action": "Confirm that the master server and client communicate",
        "full_action": "Confirm that the master server and client communicate\nsuccessfully. Review the nbinstallagent log for a copy of the exact command\nline executed, its return status, and its output. Consult the NetBackup Commands\nReference Guide for information on the specific error."
    },
    "7263": {
        "code": 7263,
        "desc": "There is insufficient disk space available to complete the operation.",
        "first_action": "Free up space on the disk where the NetBackup package",
        "full_action": "Free up space on the disk where the NetBackup package\nrepository is located and retry the operation."
    },
    "7264": {
        "code": 7264,
        "desc": "Package release version is not supported.",
        "first_action": "Confirm that you have downloaded the appropriate",
        "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment."
    },
    "7265": {
        "code": 7265,
        "desc": "Package type is invalid.",
        "first_action": "Confirm that you have downloaded the appropriate",
        "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment."
    },
    "7266": {
        "code": 7266,
        "desc": "Package operating system is not supported.",
        "first_action": "Confirm that you have downloaded the appropriate",
        "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment."
    },
    "7267": {
        "code": 7267,
        "desc": "Package EEB version is not supported.",
        "first_action": "Confirm that you have downloaded the appropriate",
        "full_action": "Confirm that you have downloaded the appropriate\nVxUpdate SJA package for your environment."
    },
    "7268": {
        "code": 7268,
        "desc": "EEB install is not supported. NetBackup status codes 897 NetBackup status codes",
        "first_action": "You cannot install server EEB on a client system. Verify",
        "full_action": "You cannot install server EEB on a client system. Verify\nthat the target host is a client and the type of EEB being installed is a client EEB.\nFor more information, review the EEB documentation for proper installation."
    },
    "7269": {
        "code": 7269,
        "desc": "Found active NetBackup jobs on the target host.",
        "first_action": "Review the activity monitor to determine which jobs are",
        "full_action": "Review the activity monitor to determine which jobs are\nrunning on the target media server. Wait until the jobs are complete on the target\nmedia server and run the VxUpdate job again."
    },
    "7270": {
        "code": 7270,
        "desc": "There are no existing security certificates on the host.",
        "first_action": "In the deployment job, supply ECA values instead of",
        "full_action": "In the deployment job, supply ECA values instead of\nselecting the Use existing certificates when possible option."
    },
    "7271": {
        "code": 7271,
        "desc": "The initialization of the nbcertcmdtool utility failed.",
        "first_action": "Validate that the VxUpdate packages are not corrupted.",
        "full_action": "Validate that the VxUpdate packages are not corrupted.\nReview the target host’s NetBackup temp directory for remnants of older\nnbcertcmdtool files."
    },
    "7272": {
        "code": 7272,
        "desc": "The preinstallation checks failed.",
        "first_action": "Review the nbinstallagent logs to determine if there",
        "full_action": "Review the nbinstallagent logs to determine if there\nwas a problem executing nbcheck. If not, review the output from nbcheck to\ndetermine which check has failed. Note that only critical checks can cause the\ninstallation to fail. Correct the condition that the preinstall checker displays and\nre-run the job."
    },
    "7273": {
        "code": 7273,
        "desc": "The existing security configuration is invalid.",
        "first_action": "Verifythatthemasterserverisintheexpectedmode.The",
        "full_action": "Verifythatthemasterserverisintheexpectedmode.The\ncommand<install_path>/netbackup/bin/nbcertcmd -getSecConfig -caUsage\ndisplays the mode."
    },
    "7275": {
        "code": 7275,
        "desc": "The native Package Manager command failed.",
        "first_action": "Review the nbinstallagent logs to determine if the",
        "full_action": "Review the nbinstallagent logs to determine if the\nproblem was with adding or removing the package."
    },
    "7276": {
        "code": 7276,
        "desc": "The NetBackup processes cannot be started.",
        "first_action": "Log onto the target host and start processes manually",
        "full_action": "Log onto the target host and start processes manually\nusing bp.start_all (UNIX) or bpup (Windows)."
    },
    "7277": {
        "code": 7277,
        "desc": "The NetBackup configuration on the host is invalid or corrupt.",
        "first_action": "If the target host is windows inspect the",
        "full_action": "If the target host is windows inspect the\nSOFTWARE\\Veritas\\NetBackup\\CurrentVersion\\Install Type key.\nIfthetargethostisUNIX,runbpclntcmd -is_server <target host>todetermine\nif it is a client or a server. If it is a server, run bpclntcmd -is_master_server\n<target host> to determine if the target host is a master or a media server."
    },
    "7278": {
        "code": 7278,
        "desc": "Failed to get the NetBackup install status from the remote host.",
        "first_action": "Reviewtheinstallationlogsonthetargethosttodetermine",
        "full_action": "Reviewtheinstallationlogsonthetargethosttodetermine\nif the upgrade was successful. If it was not, review the nbinstallagent logs to\ndetermine what caused the failure."
    },
    "7279": {
        "code": 7279,
        "desc": "The host type and package type do not match.",
        "first_action": "Specify a different package which is compatible with the host’s type.",
        "full_action": "To fix the issue, try one of the following as applicable:\n■ Specify a different package which is compatible with the host’s type.\n■ Change the specified host to a type compatible with the package."
    },
    "7281": {
        "code": 7281,
        "desc": "The command-line length is too long.",
        "first_action": "In most cases, this message is due to larger SERVER and",
        "full_action": "In most cases, this message is due to larger SERVER and\nMEDIA_SERVER lists, and the internal commands that require specification of those\nserversonthecommandline.Considerfilteringortrimmingserverlistsforthetarget\nhosts in the bp.conf file (or Windows registry) and running the process with smaller\ngroups of SERVER and MEDIA_SERVER lists."
    },
    "7282": {
        "code": 7282,
        "desc": "Could not query the system for the state of existing installed packages.",
        "first_action": "Refertoplatform-specificPackageManagerdocumentation.",
        "full_action": "Refertoplatform-specificPackageManagerdocumentation.\nConfirm that the native packaging system is in a healthy state on all target hosts."
    },
    "7283": {
        "code": 7283,
        "desc": "Could not parse the deployment option.",
        "first_action": "Verify that NetBackup passes the deployment options",
        "full_action": "Verify that NetBackup passes the deployment options\ncorrectly: NetBackup Job Manager (nbjm) to NetBackup media server transport\n(nbmtrans). Review any manually entered deployment options to determine if they\nare syntactically correct. Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7284": {
        "code": 7284,
        "desc": "One or more package file paths were not accepted.",
        "first_action": "Verify that the file paths exist and have an sja extension.",
        "full_action": "Verify that the file paths exist and have an sja extension."
    },
    "7285": {
        "code": 7285,
        "desc": "Could not find a value for javagui_jre field in the conf file.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7286": {
        "code": 7286,
        "desc": "Could not extract and verify the nbjavajre package successfully.",
        "first_action": "Confirm that the package has come from a legitimate",
        "full_action": "Confirm that the package has come from a legitimate\nsource and has not been altered or manipulated. Confirm that there is sufficient\ndisk space to extract the package on the target host. Retry the operation and if the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "7287": {
        "code": 7287,
        "desc": "Incorrect javagui_jre value that is specified in the conf file. The valid values are include, exclude, or match.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7288": {
        "code": 7288,
        "desc": "Could not query registry info.",
        "first_action": "Verify the registry key",
        "full_action": "Verify the registry key\nSOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall exists and is not\ncorrupted."
    },
    "7289": {
        "code": 7289,
        "desc": "The installed NetBackup packages list exceeds the maximum allowed characters.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7290": {
        "code": 7290,
        "desc": "TheVxUpdateplatformnameexceedsthemaximumallowedcharacters.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7291": {
        "code": 7291,
        "desc": "The definition for the VxUpdate platform is not valid.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7292": {
        "code": 7292,
        "desc": "The definition for the VxUpdate platform is not found.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7293": {
        "code": 7293,
        "desc": "The package is invalid for hosts at this version level.",
        "first_action": "Retry the operation using a maintenance release that is",
        "full_action": "Retry the operation using a maintenance release that is\ncompatible with the version of NetBackup on the target host. You need to use a\nNetBackup maintenance release version that is on the same release line."
    },
    "7294": {
        "code": 7294,
        "desc": "The destination release’s agent process did not execute as expected. ConfirmthatthedestinationNetBackupreleaseleveliscompatiblewiththeplatform and OS level of this host.",
        "first_action": "Review the NetBackup Software Compatibility List to",
        "full_action": "Review the NetBackup Software Compatibility List to\nconfirm that the target host meets operating system and platform requirements.\nConfirm that the operating system and its libraries are installed correctly."
    },
    "7295": {
        "code": 7295,
        "desc": "This host is unable to communicate with the master server following the upgrade.",
        "first_action": "ReviewtheNetBackupSecurityand EncryptionGuidefor",
        "full_action": "ReviewtheNetBackupSecurityand EncryptionGuidefor\ndetailsonhowtoconfiguresecurecommunicationinthelatestNetBackupreleases.\nSome security modes can be configured using VxUpdate. Other security modes\nrequire action outside of VxUpdate.\nIn cases where you want to force VxUpdate to proceed with the upgrade anyway,\nuse bpsetconfig or other utilities to add the\nIGNORE_VXUPDATE_PREUPGRADE_COMMUNICATION_CHECK value to the NetBackup\nconfiguration of the target host. Set this value to 1. The next VxUpdate operation\nreports the post-upgrade communication concern, but proceeds with the upgrade.\nUsing this method is not without risk and may cause multiple issues with your\ninstallation."
    },
    "7296": {
        "code": 7296,
        "desc": "Could not take the host offline.",
        "first_action": "IfNetBackupiscurrentlyactiveonthetargetmediaserver",
        "full_action": "IfNetBackupiscurrentlyactiveonthetargetmediaserver\n(Example: a backup or restore is running), it's recommended to wait for that activity\nto finish before VxUpdate is attempted.\nIncaseswhereimmediateinterventionisneeded,relyonNetBackupprocessutilities\nto report and potentially stop or suspend NetBackup processes. Review the\nNetBackup Commands Reference Guide sections for bp.kill_all, bpdown, bpps,\nnbstop, and vmoprcmd."
    },
    "7297": {
        "code": 7297,
        "desc": "Failed to delete the deployment package file.",
        "first_action": "Verifythattheuserexecutingthenbrepobinaryhasdelete",
        "full_action": "Verifythattheuserexecutingthenbrepobinaryhasdelete\nprivileges. Verify that the file is not in use or has a lock on it."
    },
    "7298": {
        "code": 7298,
        "desc": "The specified file exists, but some NetBackup processes cannot access it.",
        "first_action": "Move the file to a location that NetBackup core processes are permitted to work",
        "full_action": "Perform one of the following as appropriate:\n■ Move the file to a location that NetBackup core processes are permitted to work\nwith, such as /usr/openv/tmp or <INSTALLDIR>\\NetBackup\\Temp.\n■ Use the system chmod command on UNIX platforms, or the nbserviceusercmd\ncommand on Windows, to modify permissions on the target file and or folder so\nthat NetBackup core processes have access.\n■ Change the NetBackup daemons and services to run under a user account that\nhas permissions to access the target file and or folder. Remember that there\nare security implications when performing this operation."
    },
    "7299": {
        "code": 7299,
        "desc": "The library libnsl.so.1 is not present on the target host.",
        "first_action": "Installthelibnsl.so.1libraryonthetargethostandthen",
        "full_action": "Installthelibnsl.so.1libraryonthetargethostandthen\nrerun the VxUpdate operation."
    },
    "7300": {
        "code": 7300,
        "desc": "Uninstall of the target package was unsuccessful.",
        "first_action": "Verify that you have used the correct target package for",
        "full_action": "Verify that you have used the correct target package for\nthis uninstall. Use the uninstall package that corresponds to the successful install\npackage you used."
    },
    "7301": {
        "code": 7301,
        "desc": "The Windows host does not have the required Visual C++ run-time libraries installed.",
        "first_action": "Install Visual C++ run-time libraries 14.36.32532 or later",
        "full_action": "Install Visual C++ run-time libraries 14.36.32532 or later\non the Windows computer and retry the operation. For more information on Visual\nC++ run-time libraries, search Microsoft's website for Redistributing Visual C++\nFiles."
    },
    "7302": {
        "code": 7302,
        "desc": "A transfer request is already in progress for a package file.",
        "first_action": "Wait for the existing package transfer to complete and",
        "full_action": "Wait for the existing package transfer to complete and\nthen retry the newer package transfer."
    },
    "7303": {
        "code": 7303,
        "desc": "Failed to move the specified file.",
        "first_action": "Review the related log messages to identify the source",
        "full_action": "Review the related log messages to identify the source\nand the destination file paths. Confirm that permissions are correct for those\ndirectories. Confirm a user with appropriate privileges attempts the VxUpdate\noperation."
    },
    "7304": {
        "code": 7304,
        "desc": "Uploaded file name does not match the package name in database. NetBackup status codes 908 NetBackup status codes",
        "first_action": "Confirmthepackage(.sjafile)isnotcorruptedandcame",
        "full_action": "Confirmthepackage(.sjafile)isnotcorruptedandcame\nfrom a legitimate source."
    },
    "7305": {
        "code": 7305,
        "desc": "The transfer was started but became inactive or was abandoned before completion.",
        "first_action": "Knownissuesthatcauseofthiserrorinclude:connectivity",
        "full_action": "Knownissuesthatcauseofthiserrorinclude:connectivity\nissues between the source host and the primary server, failure of network services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nthat connectivity is healthy between the source host and the primary server. Retry\nthe transfer."
    },
    "7306": {
        "code": 7306,
        "desc": "Package file has failed to upload.",
        "first_action": "Known issues that cause this error include: connectivity",
        "full_action": "Known issues that cause this error include: connectivity\nissues between the source host and the primary server, failure of network services\nonthesourcehost,andfailureofNetBackupservicesontheprimaryserver.Confirm\nthat connectivity is healthy between the source host and the primary server. Retry\nthe transfer."
    },
    "7307": {
        "code": 7307,
        "desc": "Cannot delete package while package add operation is running.",
        "first_action": "Wait until the package add attempt is complete and retry",
        "full_action": "Wait until the package add attempt is complete and retry\nthe delete operation."
    },
    "7400": {
        "code": 7400,
        "desc": "Storage server with the same name and type already exists.",
        "first_action": "Use a different storage server name. Contact Cohesity",
        "full_action": "Use a different storage server name. Contact Cohesity\nTechnical Support for additional troubleshooting."
    },
    "7401": {
        "code": 7401,
        "desc": "Failed to create storage server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7402": {
        "code": 7402,
        "desc": "Failed to get storage server properties.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7403": {
        "code": 7403,
        "desc": "Failed to update storage server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7404": {
        "code": 7404,
        "desc": "Failed to delete storage server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7405": {
        "code": 7405,
        "desc": "Failed to remove the storage server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7406": {
        "code": 7406,
        "desc": "Requested data has the following invalid or missing fields.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7407": {
        "code": 7407,
        "desc": "Disk pool with the same name already exists.",
        "first_action": "Useadifferentdiskpoolname.Ifissuestillpersistscontact",
        "full_action": "Useadifferentdiskpoolname.Ifissuestillpersistscontact\nCohesity Technical Support."
    },
    "7408": {
        "code": 7408,
        "desc": "Failed to get disk pool.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7409": {
        "code": 7409,
        "desc": "Failed to update disk pool.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7410": {
        "code": 7410,
        "desc": "Failed to delete disk pool.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7411": {
        "code": 7411,
        "desc": "Storage unit with the same name already exists.",
        "first_action": "Tryadifferentstorageunitname.Iftheissueisstillpersists,",
        "full_action": "Tryadifferentstorageunitname.Iftheissueisstillpersists,\ncontact Cohesity Technical Support."
    },
    "7412": {
        "code": 7412,
        "desc": "Failed to create storage unit.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7413": {
        "code": 7413,
        "desc": "Failed to get storage unit.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7414": {
        "code": 7414,
        "desc": "Failed to update storage unit. NetBackup status codes 913 NetBackup status codes",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7415": {
        "code": 7415,
        "desc": "Failed to delete storage unit.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7416": {
        "code": 7416,
        "desc": "Service method unimplemented.",
        "first_action": "Check the API documentation for the supported method.",
        "full_action": "Check the API documentation for the supported method.\nIf the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7417": {
        "code": 7417,
        "desc": "Storage API Management feature is disabled.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7418": {
        "code": 7418,
        "desc": "Access denied on target storage server. NetBackup status codes 914 NetBackup status codes",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7419": {
        "code": 7419,
        "desc": "Failed to add replication target to the storage server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7420": {
        "code": 7420,
        "desc": "Replication relationship already exists.",
        "first_action": "Check the input that is specified for errors. If the issue",
        "full_action": "Check the input that is specified for errors. If the issue\npersists, contact Cohesity Technical Support for additional troubleshooting."
    },
    "7421": {
        "code": 7421,
        "desc": "Failed to get storage server configuration properties.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7422": {
        "code": 7422,
        "desc": "Failed to create disk pool.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7423": {
        "code": 7423,
        "desc": "Failed to create disk volume.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7424": {
        "code": 7424,
        "desc": "Failed to get disk volume.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7425": {
        "code": 7425,
        "desc": "Failed to get replication targets.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. If the issue persists, contact Cohesity Technical Support for additional\ntroubleshooting."
    },
    "7426": {
        "code": 7426,
        "desc": "Failed to get the replication relationship details.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "7427": {
        "code": 7427,
        "desc": "Failed to create universal share.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7428": {
        "code": 7428,
        "desc": "Failed to update universal share.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7429": {
        "code": 7429,
        "desc": "Failed to fetch the universal share details. NetBackup status codes 917 NetBackup status codes",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7430": {
        "code": 7430,
        "desc": "Failed to delete universal share.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7431": {
        "code": 7431,
        "desc": "Failed to fetch the universal share list.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "7432": {
        "code": 7432,
        "desc": "Failed to add replication target on disk volume.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "7433": {
        "code": 7433,
        "desc": "Failed to delete replication target on disk volume.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "7434": {
        "code": 7434,
        "desc": "Failed to get replication target details of disk volume.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "7435": {
        "code": 7435,
        "desc": "Failed to update disk volume details.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "7436": {
        "code": 7436,
        "desc": "Failed to list cloud buckets.",
        "first_action": "Select a different option and retry the operation. If the",
        "full_action": "Select a different option and retry the operation. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "7437": {
        "code": 7437,
        "desc": "Failed to create a cloud bucket.",
        "first_action": "Select a different option and retry the operation. If the",
        "full_action": "Select a different option and retry the operation. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "7450": {
        "code": 7450,
        "desc": "The databaseName field must be specified.",
        "first_action": "If the databaseName field is specified, verify that it is not",
        "full_action": "If the databaseName field is specified, verify that it is not\nan empty string. Specify a database name in the databaseName field."
    },
    "7451": {
        "code": 7451,
        "desc": "The instanceName field must be specified.",
        "first_action": "If the instanceName field is specified, verify that it is not",
        "full_action": "If the instanceName field is specified, verify that it is not\nan empty string. Specify an instance name in the instanceName field."
    },
    "7452": {
        "code": 7452,
        "desc": "The consistencyCheck field must be specified.",
        "first_action": "If the consistencyCheck field is specified, verify that it is",
        "full_action": "If the consistencyCheck field is specified, verify that it is\nnot an empty string. Specify an instance name in the consistencyCheck field."
    },
    "7453": {
        "code": 7453,
        "desc": "The consistencyCheck field must be one of these values: NONE,FULLINCLUDINGINDICES, FULLEXCLUDINGINDICES, CHECKCATALOG, or PHYSICALCHECKONLY.",
        "first_action": "If the consistencyCheck field is provided, verify that it is",
        "full_action": "If the consistencyCheck field is provided, verify that it is\na valid value. Valid consistencyCheck values are: NONE,FULLINCLUDINGINDICES,\nFULLEXCLUDINGINDICES, CHECKCATALOG, or PHYSICALCHECKONLY. Specify a valid\nvalue in the consistencyCheck field."
    },
    "7454": {
        "code": 7454,
        "desc": "The maxTransferSize field must be specified.",
        "first_action": "If the maxTransferSize field is provided, verify that it is",
        "full_action": "If the maxTransferSize field is provided, verify that it is\nnot an empty string. Valid transfer sizes are: 64K, 128K, 256K, 1M, 2M, or 4M.\nSpecify a valid transfer size in the maxTransferSize field."
    },
    "7455": {
        "code": 7455,
        "desc": "The maxTransferSize field must be one of these values: 64K, 128K, 256K, 1M, 2M, or 4M.",
        "first_action": "If the maxTransferSize field is provided, verify that it is",
        "full_action": "If the maxTransferSize field is provided, verify that it is\na valid value. Valid transfer sizes are: 64K, 128K, 256K, 1M, 2M, or 4M. Specify a\nvalid transfer size in the maxTransferSize field."
    },
    "7456": {
        "code": 7456,
        "desc": "The numBuffs field must be between 1 to 32.",
        "first_action": "If the numBuffs field is provided, verify that it is not an",
        "full_action": "If the numBuffs field is provided, verify that it is not an\nempty string. Specify a valid number of buffers in the numBuffs field. Valid values\nare in the range of 1 to 32."
    },
    "7457": {
        "code": 7457,
        "desc": "The recoveredState field must be specified.",
        "first_action": "IftherecoveredStatefieldisprovided,verifythatitisnot",
        "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\nan empty string. Specify a valid recovered state in the recoveredState field. Valid\nrecovered states are: Recovered, NotRecovered, or Standby."
    },
    "7458": {
        "code": 7458,
        "desc": "The recoveredState field must be one of these values: Recovered, NotRecovered, or Standby.",
        "first_action": "IftherecoveredStatefieldisprovided,verifythatitisnot",
        "full_action": "IftherecoveredStatefieldisprovided,verifythatitisnot\nan empty string. Specify a valid recovered state in the recoveredState field. Valid\nrecovered states are: Recovered, NotRecovered, or Standby."
    },
    "7459": {
        "code": 7459,
        "desc": "The traceLevel field must be specified.",
        "first_action": "If the traceLevel field is provided, verify that it is not an",
        "full_action": "If the traceLevel field is provided, verify that it is not an\nempty string. Specify a valid trace level in the traceLevel field. Valid trace levels\nare: Minimum, Medium, or Maximum."
    },
    "7460": {
        "code": 7460,
        "desc": "The traceLevel field must be one of these values: Minimum, Medium, or Maximum.",
        "first_action": "If the traceLevel field is provided, verify that it is a valid",
        "full_action": "If the traceLevel field is provided, verify that it is a valid\nvalue. Valid trace levels are: Minimum, Medium, or Maximum. Specify a valid trace\nlevel in the traceLevel field."
    },
    "7461": {
        "code": 7461,
        "desc": "Exactly one option in trxLogRecoveryOptions must be specified.",
        "first_action": "Verify that only one of the options is provided. Specify",
        "full_action": "Verify that only one of the options is provided. Specify\nonlyoneofthetransactionlogrecoveryoptions.Thefollowingisanexamplesubset\nof recovery options: toPointInTime, toTrxLogMark, toTrxLogMarkButAfter,\nbeforeTrxLogMark, and beforeTrxLogMarkButAfter."
    },
    "7462": {
        "code": 7462,
        "desc": "The toPointInTime field must be specified.",
        "first_action": "If the inPointInTime field is specified, verify that it is not",
        "full_action": "If the inPointInTime field is specified, verify that it is not\nan empty string. Specify a time in the toPointInTime field."
    },
    "7463": {
        "code": 7463,
        "desc": "The toTrxLogMark field must be specified.",
        "first_action": "If the toTrxLogMark field is specified, verify that it is not",
        "full_action": "If the toTrxLogMark field is specified, verify that it is not\nan empty string. Specify a log mark in the toTrxLogMark field."
    },
    "7464": {
        "code": 7464,
        "desc": "The toTrxLogMarkButAfter field must be specified.",
        "first_action": "IfthetoTrxLogMarkButAfterfieldisspecified,verifythat",
        "full_action": "IfthetoTrxLogMarkButAfterfieldisspecified,verifythat\nitisnotanemptystring.SpecifyatimeandalogmarkinthetoTrxLogMarkButAfter\nfield."
    },
    "7465": {
        "code": 7465,
        "desc": "The beforeTrxLogMark field must be specified. NetBackup status codes 924 NetBackup status codes",
        "first_action": "If the beforeTrxLogMark field is specified, verify that it is",
        "full_action": "If the beforeTrxLogMark field is specified, verify that it is\nnot an empty string. Specify a log mark in the beforeTrxLogMark field."
    },
    "7466": {
        "code": 7466,
        "desc": "The beforeTrxLogMarkButAfter field must be specified.",
        "first_action": "IfthebeforeTrxLogMarkButAfterfieldisspecified,verify",
        "full_action": "IfthebeforeTrxLogMarkButAfterfieldisspecified,verify\nthat it is not an empty string. Specify a time and a log mark in the\nbeforeTrxLogMarkButAfter field."
    },
    "7467": {
        "code": 7467,
        "desc": "The standbyPath field must be specified.",
        "first_action": "Verify that the standbyPath field has been included and",
        "full_action": "Verify that the standbyPath field has been included and\nthat it is not an empty string. Specify a fully qualified path in the standbyPath field."
    },
    "7468": {
        "code": 7468,
        "desc": "The standbyPath field must be a valid file.",
        "first_action": "Verify that the standbyPath field has been provided and",
        "full_action": "Verify that the standbyPath field has been provided and\nthat it is not an empty string. Specify a fully qualified path in the standbyPath field."
    },
    "7469": {
        "code": 7469,
        "desc": "The trxLogRecoveryOptions can't be specified.",
        "first_action": "If the trxLogRecoveryOptions option is provided, verify",
        "full_action": "If the trxLogRecoveryOptions option is provided, verify\nthat there is a transaction log backup ID associated with it."
    },
    "7472": {
        "code": 7472,
        "desc": "Could not start database recovery.",
        "first_action": "Try restarting services for the EMM server.",
        "full_action": "Try the following as appropriate:\n■ Try restarting services for the EMM server.\n■ Review the recovery options that were provided for Microsoft SQL Server and\ncorrect any issues."
    },
    "7473": {
        "code": 7473,
        "desc": "Failed to authenticate instance credentials on the target server.",
        "first_action": "Verify the credentials that were used on the target server.",
        "full_action": "Verify the credentials that were used on the target server.\nCorrect any issues and retry the recovery."
    },
    "7476": {
        "code": 7476,
        "desc": "Failed to get active disk pools details. NetBackup status codes 926 NetBackup status codes",
        "first_action": "Review the NetBackup Troubleshooting Guide for additional information about",
        "full_action": "Perform the following as appropriate:\n■ Review the NetBackup Troubleshooting Guide for additional information about\nthe error.\n■ Increase the logging level and retry the operation.\n■ Collect the web service logs from the time of the error and contact Cohesity\nTechnical Support. The web service logs are located in either\n/usr/openv/netbackup/logs/nbwebservice or\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice."
    },
    "7477": {
        "code": 7477,
        "desc": "Failed to get active and encrypted disk pools details.",
        "first_action": "Review the NetBackup Troubleshooting Guide for additional information about",
        "full_action": "Perform the following as appropriate:\n■ Review the NetBackup Troubleshooting Guide for additional information about\nthe error.\n■ Increase the logging level and retry the operation.\n■ Collect the web service logs from the time of the error and contact Cohesity\nTechnical Support. The web service logs are located in either\n/usr/openv/netbackup/logs/nbwebservice or\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservice."
    },
    "7600": {
        "code": 7600,
        "desc": "An unknown internal error occurred.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7601": {
        "code": 7601,
        "desc": "Failed to register service with PBX.",
        "first_action": "Verify that the pbx_exchange service is running. If not, start the service.",
        "full_action": "Do the following:\n■ Verify that the pbx_exchange service is running. If not, start the service.\n■ If the problem persists, contact Cohesity Technical Support."
    },
    "7603": {
        "code": 7603,
        "desc": "Failed to initialize PBX.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7604": {
        "code": 7604,
        "desc": "Failed to register PBX acceptor with the reactor.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7607": {
        "code": 7607,
        "desc": "Failed to set socket to non-blocking mode.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7609": {
        "code": 7609,
        "desc": "Failed to perform a reactor event handler operation.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7610": {
        "code": 7610,
        "desc": "Failed to parse the specified object.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7611": {
        "code": 7611,
        "desc": "A connection protocol error occurred.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7612": {
        "code": 7612,
        "desc": "An unexpected protocol event occurred.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7613": {
        "code": 7613,
        "desc": "A lookup failed for host. NetBackup status codes 929 NetBackup status codes",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7614": {
        "code": 7614,
        "desc": "No valid source-target bindings exist for host.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7617": {
        "code": 7617,
        "desc": "A JSON conversion error occurred.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7618": {
        "code": 7618,
        "desc": "Failed to find JSON key.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7619": {
        "code": 7619,
        "desc": "The specified state machine is still active.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7622": {
        "code": 7622,
        "desc": "Input I/O is required.",
        "first_action": "Under normal circumstances this message may appear",
        "full_action": "Under normal circumstances this message may appear\nin the logs of the vnetd proxy. No user action is required. If a problem persists,\ncontact Cohesity Technical Support."
    },
    "7623": {
        "code": 7623,
        "desc": "Output I/O is required.",
        "first_action": "Under normal circumstances this message may appear",
        "full_action": "Under normal circumstances this message may appear\nin the logs of the NetBackup process. No user action is required. If a problem\npersists, contact Cohesity Technical Support."
    },
    "7624": {
        "code": 7624,
        "desc": "A SSL socket accept failed.",
        "first_action": "A missing, expired, or revoked host certificate on the local or the remote host.",
        "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate on the local or the remote host.\nIn case of the NetBackup CA, verify that the hosts have a valid host ID-based\ncertificate. In case of an external CA, verify that the external certificate and\nkeystore paths are correctly set in the external certificate configuration file. If\nthe host is configured to use an encrypted keystore, ensure that the correct\npassphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in the NetBackup Security and Encryption Guide.\n■ If you use the NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nthat the cipher strings are compatible between the hosts.\nIf the problem persists, contact Cohesity Technical Support."
    },
    "7625": {
        "code": 7625,
        "desc": "A SSL socket connect failed.",
        "first_action": "A missing, expired, or revoked host certificate on the local or the remote host.",
        "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate on the local or the remote host.\nIn case of the NetBackup CA, verify that the hosts have a valid host ID-based\ncertificate. In case of an external CA, verify that the external certificate and\nkeystore paths are correctly set in the external certificate configuration file. If\nthe host is configured to use an encrypted keystore, ensure that the correct\npassphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessiveclockskewoneitherthelocalortheremotehost.Seetheinformation\nabout clock skew in the NetBackup Security and Encryption Guide.\n■ If you use the NetBackup SECURE_PROXY_CIPHER_LIST configuration option on\neitherthelocalortheremotehost,thecipherstringentriesmaybeinvalid.Verify\nthat the cipher strings are compatible between the hosts.\nIf the problem persists, contact Cohesity Technical Support."
    },
    "7627": {
        "code": 7627,
        "desc": "SSL initialization failed.",
        "first_action": "A missing, expired, or revoked host certificate. In case of the NetBackup CA,",
        "full_action": "Examine the details of the error message to determine\nwhy the SSL handshake failed. Possible causes of this error may be as follows:\n■ A missing, expired, or revoked host certificate. In case of the NetBackup CA,\nverifythatthehostshaveavalidhostID-basedcertificate.Incaseofanexternal\nCA, verify that the external certificate and keystore paths are correctly set in the\nexternalcertificateconfigurationfile.Ifthehostisconfiguredtouseanencrypted\nkeystore, ensure that the correct passphrase for the certificate’s private key is\nspecified for the ECA_KEY_PASSPHRASEFILE configuration option.\n■ Excessive clock skew on the host. See the information about clock skew in the\nNetBackup Security and Encryption Guide.\n■ IfyouusetheNetBackupSECURE_PROXY_CIPHER_LISTconfigurationoption,the\ncipher string entries may be invalid. Verify that the cipher strings are permitted\nOpenSSL strings.\n■ For VMware:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhethertheVMwarevirtualizationserver’s(vCenter,ESX,ESXi)certificates\nand CRLs are added to the respective ECA configured trust store and the\nCRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only PEM certificate format for file-based trust store & Windows trust store\nare supported for virtualization servers. P7b or DER format file based trust\nstore is not supported. When this feature is enabled, the certificate ECA\nstore should either be Windows certificate store or file based PEM format\nstore.\nIf the problem persists, contact Cohesity Technical Support."
    },
    "7628": {
        "code": 7628,
        "desc": "VxSS initialization failed. NetBackup status codes 933 NetBackup status codes",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7631": {
        "code": 7631,
        "desc": "Certificate path lookup failed.",
        "first_action": "In case of the NetBackup CA, verify that the hosts have",
        "full_action": "In case of the NetBackup CA, verify that the hosts have\na valid host ID-based certificate. In case of an external CA, verify that the hosts\nhave a valid external CA-signed certificate."
    },
    "7632": {
        "code": 7632,
        "desc": "A protocol sanity verification failed.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7633": {
        "code": 7633,
        "desc": "The state machine was terminated before completion.",
        "first_action": "Under normal circumstances this message may be seen",
        "full_action": "Under normal circumstances this message may be seen\nin the logs of the vnetd proxy. No user action is required. If the problem persists,\ncontact Cohesity Technical Support."
    },
    "7634": {
        "code": 7634,
        "desc": "Failed to set up a UNIX Domain Socket listener for user. NetBackup status codes 934 NetBackup status codes",
        "first_action": "Examine the status message for additional details. It may",
        "full_action": "Examine the status message for additional details. It may\nbe that the process does not have the permissions to create the required files or\nthe disk volume may be full. Examine the state and the contents of (Linux) or\n(Windows)."
    },
    "7635": {
        "code": 7635,
        "desc": "Failed to create a local acceptor.",
        "first_action": "Examine the status message for additional details. There",
        "full_action": "Examine the status message for additional details. There\nmaybealistenportconflict,orapermissionorfreespaceproblemwiththeproxy.d\ndirectory or its contents. The directory is located in or ."
    },
    "7636": {
        "code": 7636,
        "desc": "Failed to import socket from remote process.",
        "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause",
        "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nroot causes, review the nbpxyhelper logs or contact Cohesity Technical Support."
    },
    "7637": {
        "code": 7637,
        "desc": "Failed to export socket to remote process.",
        "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause",
        "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfiledescriptorsareunavailabletemporarily.Therefore,retrytheoperation.Forother\nroot causes, review the nbpxyhelper logs or contact Cohesity Technical Support."
    },
    "7638": {
        "code": 7638,
        "desc": "Failed to create a socket pair.",
        "first_action": "Thisfailureislikelyatransientproblem,perhapsbecause",
        "full_action": "Thisfailureislikelyatransientproblem,perhapsbecause\nfile descriptors or TCP ports are unavailable temporarily. Therefore, retry the\noperation. For other root causes, review the nbpxyhelper logs or contact Cohesity\nTechnical Support."
    },
    "7639": {
        "code": 7639,
        "desc": "Failed to create a peer name mapping.",
        "first_action": "Examine the status message for additional details. It may",
        "full_action": "Examine the status message for additional details. It may\nbe that the process does not have the permissions to create the required files or\nthe disk volume may be full. Examine the state and the contents of (Linux) or\n(Windows)."
    },
    "7640": {
        "code": 7640,
        "desc": "The peer closed the connection.",
        "first_action": "Under normal circumstances this message may be seen",
        "full_action": "Under normal circumstances this message may be seen\nin the vnetd proxy logs. No user action is required. If a problem persists, contact\nCohesity Technical Support.\nFor more information, review this technical article:\nhttps://www.veritas.com/support/en_US/article.100039945"
    },
    "7641": {
        "code": 7641,
        "desc": "Failed to find a common CA Root for secure handshake.",
        "first_action": "Recommended Action: Missing, expired, or revoked host certificate on the",
        "full_action": "Examine the error message for the details of which CA\nRoots each NetBackup process advertised. The following are possible causes of\nthis error:\n■ Recommended Action: Missing, expired, or revoked host certificate on the\nlocalortheremotehost.IncaseoftheNetBackupCA,verifythatthehostshave\navalidhostID-basedcertificate.IncaseofanexternalCA,verifythattheexternal\ncertificate and keystore paths are correctly set in the external certificate\nconfiguration file. If the host is configured to use an encrypted keystore, ensure\nthat the correct passphrase for the certificate's private key is specified for the\nECA_KEY_PASSPHRASEFILE configuration option.\n■ Recommended Action: The hosts are not members of the same NetBackup\ndomain.IncaseoftheNetBackupCA,ensurethatbothhostshavehostID-based\ncertificates issued by the required master server. In case of an external CA,\nensure that both hosts have the external certificates that are enrolled with the\nrequired master server."
    },
    "7642": {
        "code": 7642,
        "desc": "Failed to verify Java GUI session token.",
        "first_action": "1. Verify the authorization of the user who launched the NetBackup",
        "full_action": "Do the following:\n1. Verify the authorization of the user who launched the NetBackup\nAdministration Console.\nSee “About authorizing NetBackup users” in the NetBackup Administrator's\nGuide, Volume I.\n2. Close the NetBackup Administration Console.\n3. Launch a new instance of the NetBackup AdministrationConsole and open\nthe Activity Monitor.\nIf the problem persists, contact Cohesity Technical Support."
    },
    "7643": {
        "code": 7643,
        "desc": "Connection cannot be established because the host validation cannot be performed.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7645": {
        "code": 7645,
        "desc": "Could not get name from certificate information.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7647": {
        "code": 7647,
        "desc": "Proxy peer does not conform to proxy protocol.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "7648": {
        "code": 7648,
        "desc": "Connection cannot be established because the host validation failed.",
        "first_action": "Ensure that the NetBackup master server name and the",
        "full_action": "Ensure that the NetBackup master server name and the\nhost name are configured correctly."
    },
    "7649": {
        "code": 7649,
        "desc": "Data retrieved from the cache is not in a valid format.",
        "first_action": "Deletethepeerhost'scacheentryandretrytheoperation.",
        "full_action": "Deletethepeerhost'scacheentryandretrytheoperation.\nUse bpclntcmd -clear_host_cache. If the problem continues, contact Cohesity\nTechnical Support."
    },
    "7650": {
        "code": 7650,
        "desc": "Data that is retrieved from the server is not in a valid format.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7651": {
        "code": 7651,
        "desc": "Could not process audit reason.",
        "first_action": "Encode the X-NetBackup-Audit-Reason HTTP header",
        "full_action": "Encode the X-NetBackup-Audit-Reason HTTP header\nusing the appropriate UTF-8 strings to represent the non-ASCII characters, then\nresubmit the HTTP web service request."
    },
    "7652": {
        "code": 7652,
        "desc": "Secure communication proxy is not available for use.",
        "first_action": "Number 0",
        "full_action": "Determineifthevnetdprocessanditsproxiesarerunning.\nOn Windows, you can use the Task Manager Processes tab (you must show the\nCommand Line column). On UNIX and Linux, you can use the NetBackup bpps\ncommand, as follows:\n$ bpps\n…output shortened…\nroot 13577 1 0 Aug27 ? 00:00:04 /usr/openv/netbackup/bin/vnetd -standalone\nroot 13606 1 0 Aug27 ? 00:01:55 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy\n-number 0\nroot 13608 1 0 Aug27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy\n-number 0\nDepending on which vnetd process or proxy is running, try the following:\n■ If the vnetd process (-standalone) is not running, start it.\n■ If the vnetd process is running, examine the vnetd debug log to confirm that it\ntries to start the proxy processes.\n■ If the vnetd process does try to start the proxy processes, examine the\nnbpxyhelper debug log to determine why the proxy process does not listen for\nconnections.\nIf the problem persists, contact Cohesity Technical Support."
    },
    "7653": {
        "code": 7653,
        "desc": "The Peer Certificate is revoked Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.",
        "first_action": "If the certificate was revoked in error, reissue a certificate for the host.",
        "full_action": "Do the following, as appropriate:\n■ If the certificate was revoked in error, reissue a certificate for the host.\n■ If the certificate was revoked as intended, an attempted security breach may\nhave occurred.\n■ Contact your security administrator."
    },
    "7654": {
        "code": 7654,
        "desc": "The Certificate Revocation List is invalid Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.",
        "first_action": "On the host that has the invalid CRL, run the following",
        "full_action": "On the host that has the invalid CRL, run the following\ncommand as an administrator to get a fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL"
    },
    "7655": {
        "code": 7655,
        "desc": "Certificate Revocation List is signed incorrectly Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.",
        "first_action": "The CRL may have been replaced. On the host that has",
        "full_action": "The CRL may have been replaced. On the host that has\nthe incorrectly signed CRL, run the following command as an administrator to get\na fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL"
    },
    "7656": {
        "code": 7656,
        "desc": "Certificate Revocation List is out of date Note: This error may also be thrown while logging on to the NetBackup Administration Console with a different error message and you will not be able to log in.",
        "first_action": "On the host that has the invalid CRL, run the following",
        "full_action": "On the host that has the invalid CRL, run the following\ncommand as an administrator to get a fresh CRL:\nUNIX:\n/usr/openv/netbackup/bin/nbcertcmd -getCRL\nWindows:\ninstall_path\\Veritas\\NetBackup\\bin\\nbcertcmd -getCRL"
    },
    "7657": {
        "code": 7657,
        "desc": "Cannot identify service type of acceptor",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7658": {
        "code": 7658,
        "desc": "Connection cannot be established because the host validation cannot be performed on the target host.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "7659": {
        "code": 7659,
        "desc": "Connection cannot be established because the host validation failed on the target host.",
        "first_action": "Ensure that the NetBackup master server name and other host names are",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup master server name and other host names are\ncorrectly configured on the remote host.\n■ Ensure that the pending mapping requests for this host are approved, or, in the\nNetBackup Administration Console, select the Security Management >\nGlobal Security Settings > Secure Communication > Automatically map\nNetBackup host ID to host names option.\n■ If you have recently installed or upgraded NetBackup, ensure that the security\ncertificates are correctly deployed on all hosts."
    },
    "7660": {
        "code": 7660,
        "desc": "The peer proxy cannot find usable certificates for the certificate protocol",
        "first_action": "Verify that certificates have been successfully deployed",
        "full_action": "Verify that certificates have been successfully deployed\non the proxy peer host. If the problem occurs after certificates have been deployed\nsuccessfully, save all the error log information and contact Cohesity Technical\nSupport for assistance."
    },
    "7662": {
        "code": 7662,
        "desc": "Theexternalcertificatecannotbeautomaticallyenrolled.Thepeerhost’s external certificate must be already enrolled.",
        "first_action": "1. Check the enrollment status on communicating hosts using the nbcertcmd",
        "full_action": "Do the following:\n1. Check the enrollment status on communicating hosts using the nbcertcmd\n-listEnrollmentStatus command. If both hosts are not enrolled, manually\nenroll one of the hosts, preferably the NetBackup server, using the nbcertcmd\n-enrollCertificate command.\n2. If the problem persists, contact Cohesity Technical Support."
    },
    "7663": {
        "code": 7663,
        "desc": "The matching master server name is not available in the NetBackup configuration file, which is required for the automatic enrollment of the external certificate.",
        "first_action": "1. EnsurethatthemasterservernameisaddedasaserverentryintheNetBackup",
        "full_action": "Do the following:\n1. EnsurethatthemasterservernameisaddedasaserverentryintheNetBackup\nconfiguration file of the respective host.\n2. If the server entry is present, check the subjectAltName extension of the\nNetBackup’s web server external certificate. Then, update the NetBackup\nconfiguration file with the correct server name entry.\n3. If NetBackup configuration has correct server entry, but subjectAltName\nextension does not have the required host name, contact your Security\nAdministrator. You need to get an external certificate with the correct\nsubjetAltName extension.\n4. If the problem persists, contact Cohesity Technical Support."
    },
    "7720": {
        "code": 7720,
        "desc": "External certificate is not configured for the NetBackup host, therefore it cannot be removed.",
        "first_action": "Ensure that the external certificate is configured before",
        "full_action": "Ensure that the external certificate is configured before\nyou perform this operation."
    },
    "7721": {
        "code": 7721,
        "desc": "ExternalcertificateisnotconfiguredfortheNetBackupwebUI,therefore it cannot be removed.",
        "first_action": "Ensure that the external certificate is configured before",
        "full_action": "Ensure that the external certificate is configured before\nyou perform this operation."
    },
    "7722": {
        "code": 7722,
        "desc": "NetBackup host communication fails if you remove the given certificate.",
        "first_action": "Ensure that either a NetBackup certificate or an external",
        "full_action": "Ensure that either a NetBackup certificate or an external\ncertificate is present for host communication."
    },
    "7723": {
        "code": 7723,
        "desc": "Communication with the NetBackup web UI fails if you remove the certificate. NetBackup status codes 945 NetBackup status codes",
        "first_action": "Ensure that either a NetBackup certificate or an external",
        "full_action": "Ensure that either a NetBackup certificate or an external\ncertificate for the web UI is present for communication."
    },
    "7724": {
        "code": 7724,
        "desc": "The certificate cannot be removed.",
        "first_action": "From the /usr/openv/wmc/webserver/logs/ or the",
        "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log."
    },
    "7725": {
        "code": 7725,
        "desc": "List of certificates cannot be retrieved.",
        "first_action": "From the /usr/openv/wmc/webserver/logs/ or the",
        "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log."
    },
    "7726": {
        "code": 7726,
        "desc": "The certificate ID is not valid.",
        "first_action": "1. Configure or delete a NetBackup certificate.",
        "full_action": "You must specify a valid certificate ID when you perform\nany of the listed actions:\n1. Configure or delete a NetBackup certificate.\n2. Configure or delete an external certificate for a NetBackup host.\n3. Configure or delete an external certificate for the NetBackup web UI."
    },
    "7727": {
        "code": 7727,
        "desc": "TheNetBackupCA-issuedcertificatescannotbedeletedusingNetBackup APIs.",
        "first_action": "Use the configureWebServerCerts -removeNBCert",
        "full_action": "Use the configureWebServerCerts -removeNBCert\ncommand to delete the certificates."
    },
    "7728": {
        "code": 7728,
        "desc": "The input file of ECA configuration is not valid.",
        "first_action": "Ensure that the input file is in the required format. Review",
        "full_action": "Ensure that the input file is in the required format. Review\nthe permissions on the NetBackup Install\nDirectory/var/global/wsl/credentials folder. If the problem persists, save all\nthe error logs, and contact Cohesity Technical Support."
    },
    "7729": {
        "code": 7729,
        "desc": "The specified CRL check level value is not valid.",
        "first_action": "Specify one of the CRL check levels shown: CHAIN, LEAF,",
        "full_action": "Specify one of the CRL check levels shown: CHAIN, LEAF,\nor DISABLE."
    },
    "7730": {
        "code": 7730,
        "desc": "The private key cannot be added.",
        "first_action": "Ensurethattheexternalcertificateparameters(certificate",
        "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, and trust store) are in the correct format. If the problem persists,\nsave all the error logs, and contact Cohesity Technical Support."
    },
    "7731": {
        "code": 7731,
        "desc": "The trust bundle cannot be added.",
        "first_action": "Ensurethattheexternalcertificateparameters(certificate",
        "full_action": "Ensurethattheexternalcertificateparameters(certificate\nchain, private key, and trust store) are in the correct format. If the problem persists,\nsave all the error logs, and contact Cohesity Technical Support."
    },
    "7732": {
        "code": 7732,
        "desc": "TheNetBackupCA-issuedcertificatescannotbeaddedusingNetBackup APIs.",
        "first_action": "UsetheconfigureWebServerCerts -addNBCertcommand",
        "full_action": "UsetheconfigureWebServerCerts -addNBCertcommand\nto configure the certificates."
    },
    "7733": {
        "code": 7733,
        "desc": "External certificate of the NetBackup web UI cannot be removed.",
        "first_action": "From the /usr/openv/wmc/webserver/logs/ or the",
        "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log."
    },
    "7734": {
        "code": 7734,
        "desc": "External certificate of the NetBackup host cannot be removed. NetBackup status codes 949 NetBackup status codes",
        "first_action": "From the /usr/openv/wmc/webserver/logs/ or the",
        "full_action": "Based on your operating system, collect the logs that are\nshown from the time of the error and contact Cohesity Technical Support.\n■ From the /usr/openv/wmc/webserver/logs/ or the\ninstall_path\\Veritas\\NetBackup\\wmc\\webserver\\logs\\ directory, collect\nthe configureWebServerCerts.log.\n■ From the /usr/openv/netbackup/logs/nbwebservice or the\ninstall_path\\Veritas\\NetBackup\\logs\\nbwebservicedirectory,collectthe\n*.log.\n■ From the /usr/openv/netbackup/bin/admincmd or the\ninstall_path\\Veritas\\NetBackup\\bin\\admincmd directory, use the\nnbauditreport command to collect the audit records.\n■ From the /usr/openv/netbackup/logs/nblibcurlcmd or the\ninstall_path\\Veritas\\NetBackup\\logs\\nblibcurlcmddirectory,collectthe\n*.log."
    },
    "7750": {
        "code": 7750,
        "desc": "The dashboard security status request or the data that is sent is not valid.",
        "first_action": "Retry the operation with valid request and data.",
        "full_action": "Retry the operation with valid request and data."
    },
    "7751": {
        "code": 7751,
        "desc": "The security status request cannot be processed.",
        "first_action": "Review the NetBackup troubleshooting guide for additional information about",
        "full_action": "Perform the following as appropriate:\n■ Review the NetBackup troubleshooting guide for additional information about\nthe error.\n■ Increasethelogginglevelandretrytheoperation.Iftheproblempersists,contact\nCohesity Technical Support."
    },
    "7752": {
        "code": 7752,
        "desc": "The Alta View user should perform the operation.",
        "first_action": "Perform the operation from Alta View.",
        "full_action": "Perform the operation from Alta View."
    },
    "7800": {
        "code": 7800,
        "desc": "Unable to display the details for all identity providers.",
        "first_action": "Retry the operation or check the database connection.",
        "full_action": "Retry the operation or check the database connection."
    },
    "7801": {
        "code": 7801,
        "desc": "Unable to display the details for the identity provider with the specified name.",
        "first_action": "Retry the operation or check the database connection.",
        "full_action": "Retry the operation or check the database connection."
    },
    "7802": {
        "code": 7802,
        "desc": "Failed to add the identity provider.",
        "first_action": "Retry the operation or check the database connection.",
        "full_action": "Retry the operation or check the database connection."
    },
    "7803": {
        "code": 7803,
        "desc": "The IDP configuration contains invalid arguments or details.",
        "first_action": "Reviewallargumentvaluesandverifythattheyarecorrect.",
        "full_action": "Reviewallargumentvaluesandverifythattheyarecorrect.\nRetry the operation."
    },
    "7804": {
        "code": 7804,
        "desc": "Failed to delete the configuration for the identity provider.",
        "first_action": "Retry the operation or check the database connection.",
        "full_action": "Retry the operation or check the database connection."
    },
    "7805": {
        "code": 7805,
        "desc": "Failed to update the details for the configured identity provider with the specified name.",
        "first_action": "Retry the operation or check the database connection.",
        "full_action": "Retry the operation or check the database connection."
    },
    "7806": {
        "code": 7806,
        "desc": "An IDP configuration with the specified name already exists. NetBackup status codes 952 NetBackup status codes",
        "first_action": "Verify the IDP configuration name that you used and add",
        "full_action": "Verify the IDP configuration name that you used and add\nIDP configuration with a different name."
    },
    "7807": {
        "code": 7807,
        "desc": "An IDP configuration with the specified name does not exist.",
        "first_action": "Provide the correct IDP configuration name or an existing",
        "full_action": "Provide the correct IDP configuration name or an existing\nIDP configuration name."
    },
    "7808": {
        "code": 7808,
        "desc": "An empty or a null name was specified.",
        "first_action": "Provide the non-empty or non-null name. Retry the",
        "full_action": "Provide the non-empty or non-null name. Retry the\noperation."
    },
    "7809": {
        "code": 7809,
        "desc": "An invalid IDP configuration name was specified. The name can only contain the following characters: a-z, A-Z, 0-9, -, _.",
        "first_action": "Provide a name with characters from this category: a-z,",
        "full_action": "Provide a name with characters from this category: a-z,\nA-Z, 0-9, -, _"
    },
    "7810": {
        "code": 7810,
        "desc": "Failed to get service provider metadata.",
        "first_action": "Review the metadata file and provide the correct IDP metadata content.",
        "full_action": "Perform the following as appropriate:\n■ Review the metadata file and provide the correct IDP metadata content.\n■ Generate the Java keystore."
    },
    "7811": {
        "code": 7811,
        "desc": "An attempt was made to enable a new or an existing IDP configuration when there is already an IDP configuration that is enabled.",
        "first_action": "Disable the enabled IDP and then retry the required",
        "full_action": "Disable the enabled IDP and then retry the required\noperation."
    },
    "7812": {
        "code": 7812,
        "desc": "At least one IDP configuration must be enabled.",
        "first_action": "Review your IDP configuration and enable at least one of",
        "full_action": "Review your IDP configuration and enable at least one of\nthe configurations."
    },
    "7813": {
        "code": 7813,
        "desc": "Theenablefieldorthemetadatafieldisnotpresentintheupdateidentity providerpayload.Oneofthefieldsisrequiredtoupdatethedetailsfortheconfigured identity provider with the specified name. NetBackup status codes 954 NetBackup status codes",
        "first_action": "Provide values for either the -e (enable) field or the -mxp",
        "full_action": "Provide values for either the -e (enable) field or the -mxp\n(metadata) field using the CLI or either the enable or the idpMetadata fields in an\nupdate API payload."
    },
    "7814": {
        "code": 7814,
        "desc": "The specified file does not have expected format.",
        "first_action": "Verify that the metadata file is in the correct .xml format.",
        "full_action": "Verify that the metadata file is in the correct .xml format.\nRetry the operation and if the issue persists, visit the Cohesity Technical Support\nwebsite. The Cohesity Technical Support website offers additional information to\nhelp you troubleshoot this issue."
    },
    "7815": {
        "code": 7815,
        "desc": "Failed to redirect to the IDP server.",
        "first_action": "Review the metadata file and provide the correct IDP metadata content.",
        "full_action": "Perform the following as appropriate:\n■ Review the metadata file and provide the correct IDP metadata content.\n■ Generate the Java keystore."
    },
    "7850": {
        "code": 7850,
        "desc": "Unable to create mount due to an error in Instant Access.",
        "first_action": "Verify that the BYO for Instant Access is done and that",
        "full_action": "Verify that the BYO for Instant Access is done and that\nInstant Access properly functions. Refer to the NetBackup Administrator’s Guide,\nVolume I for more details."
    },
    "7851": {
        "code": 7851,
        "desc": "Unable to check status of the mount due to an error in Instant Access.",
        "first_action": "Verify that the BYO for Instant Access is done and that",
        "full_action": "Verify that the BYO for Instant Access is done and that\nInstant Access properly functions. Refer to the NetBackup Administrator’s Guide,\nVolume I for more details."
    },
    "7852": {
        "code": 7852,
        "desc": "Workload is not supported for malware detection.",
        "first_action": "Only standard and Windows workloads are supported for",
        "full_action": "Only standard and Windows workloads are supported for\nmalware detection."
    },
    "7853": {
        "code": 7853,
        "desc": "Unable to get details of the image from the catalog.",
        "first_action": "Verify that the backup image exists in catalog and that it",
        "full_action": "Verify that the backup image exists in catalog and that it\nis not be expired."
    },
    "7854": {
        "code": 7854,
        "desc": "Specified scan host pool is invalid.",
        "first_action": "You must provide a valid scan host pool.",
        "full_action": "You must provide a valid scan host pool."
    },
    "7855": {
        "code": 7855,
        "desc": "Unable to create a worklist.",
        "first_action": "VerifythattheNetBackupservices are up.Alsoverifythat",
        "full_action": "VerifythattheNetBackupservices are up.Alsoverifythat\nthe database is available."
    },
    "7856": {
        "code": 7856,
        "desc": "Invalid backupId.",
        "first_action": "If a backup image host pool scan is already in progress.",
        "full_action": "Review the following as appropriate:\n■ If a backup image host pool scan is already in progress.\n■ IfthebackupimagehasanInstantAccesscapablecopy.RefertotheNetBackup\nAdministrator’s Guide, Volume I for more details.\n■ The media server should have Linux and a NetBackup version 9.1.2 or newer."
    },
    "7857": {
        "code": 7857,
        "desc": "Scan host pool is not provided in the request.",
        "first_action": "You must provide a valid scan host pool.",
        "full_action": "You must provide a valid scan host pool."
    },
    "7858": {
        "code": 7858,
        "desc": "Malware tool is not specified in the request.",
        "first_action": "You must provide a valid malware tool.",
        "full_action": "You must provide a valid malware tool."
    },
    "7859": {
        "code": 7859,
        "desc": "Scan host name is not specified in the request.",
        "first_action": "You must provide a unique scan host name.",
        "full_action": "You must provide a unique scan host name."
    },
    "7860": {
        "code": 7860,
        "desc": "Scan host pool name is not specified in the request.",
        "first_action": "You must provide a unique scan host pool name when a",
        "full_action": "You must provide a unique scan host pool name when a\nnew one is created."
    },
    "7861": {
        "code": 7861,
        "desc": "Share type is not specified in the request.",
        "first_action": "You must provide a valid share type.",
        "full_action": "You must provide a valid share type."
    },
    "7862": {
        "code": 7862,
        "desc": "Specified malware tool is invalid.",
        "first_action": "You must provide a valid malware tool.",
        "full_action": "You must provide a valid malware tool."
    },
    "7863": {
        "code": 7863,
        "desc": "Specified scan host is invalid.",
        "first_action": "You must provide a valid scan host ID.",
        "full_action": "You must provide a valid scan host ID."
    },
    "7864": {
        "code": 7864,
        "desc": "The scan host cannot be created because the scan host name already exists in the database.",
        "first_action": "You must provide a unique scan host name.",
        "full_action": "You must provide a unique scan host name."
    },
    "7865": {
        "code": 7865,
        "desc": "Thescanhostpoolcannotbecreatedbecausethescanhostpoolname already exists in the database.",
        "first_action": "You must provide a unique scan host pool name.",
        "full_action": "You must provide a unique scan host pool name."
    },
    "7866": {
        "code": 7866,
        "desc": "The specified malware tool does not exist.",
        "first_action": "You must provide a valid malware tool ID from the",
        "full_action": "You must provide a valid malware tool ID from the\nsupported malware tool list."
    },
    "7867": {
        "code": 7867,
        "desc": "The malware tool cannot be created because the malware tool name already exists in the database.",
        "first_action": "The malware tool name must be unique.",
        "full_action": "The malware tool name must be unique."
    },
    "7868": {
        "code": 7868,
        "desc": "The specified scan host does not exist.",
        "first_action": "You must provide a valid scan host.",
        "full_action": "You must provide a valid scan host."
    },
    "7869": {
        "code": 7869,
        "desc": "The specified scan host pool does not exist.",
        "first_action": "You must provide a valid scan host pool.",
        "full_action": "You must provide a valid scan host pool."
    },
    "7870": {
        "code": 7870,
        "desc": "The specified scan result does not exist.",
        "first_action": "The scan result should exist in the system. Retry the",
        "full_action": "The scan result should exist in the system. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue."
    },
    "7871": {
        "code": 7871,
        "desc": "Invalid scan result request.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "7872": {
        "code": 7872,
        "desc": "No scan host was found for the specified scan host pool.",
        "first_action": "You must associate a scan host with a scan host pool.",
        "full_action": "You must associate a scan host with a scan host pool."
    },
    "7873": {
        "code": 7873,
        "desc": "Unable to delete the mount due to an error in Instant Access.",
        "first_action": "Verify that Instant Access works and has a backup image",
        "full_action": "Verify that Instant Access works and has a backup image\nmounted. Refer to the NetBackup Administrator’s Guide, Volume I for more details."
    },
    "7874": {
        "code": 7874,
        "desc": "Unable to update the backup image by catalog client.",
        "first_action": "Verify that the backup image exists in catalog and that",
        "full_action": "Verify that the backup image exists in catalog and that\nimage is not expired."
    },
    "7875": {
        "code": 7875,
        "desc": "Invalid worklistId.",
        "first_action": "Verify that a valid worklistId is tagged in the request.",
        "full_action": "Verify that a valid worklistId is tagged in the request."
    },
    "7876": {
        "code": 7876,
        "desc": "Invalid scan host credentials.",
        "first_action": "If the scan host pool has an SMB share, then verify that",
        "full_action": "If the scan host pool has an SMB share, then verify that\nthe Active Directory details are provided in the credentials that are associated with\nthe scan host."
    },
    "7877": {
        "code": 7877,
        "desc": "Invalid media server in image catalog.",
        "first_action": "Upgrade the media server to version 9.1.2 or newer.",
        "full_action": "Perform the following as appropriate:\n■ Upgrade the media server to version 9.1.2 or newer.\n■ Check if the media server OS is Linux.\n■ Check if the supported media server is available and has connectivity to the\nmasterserver.RefertotheNetBackupAdministrator’sGuide,VolumeIformore\ndetails."
    },
    "7878": {
        "code": 7878,
        "desc": "Unable to initiate the scan on media server.",
        "first_action": "A scan cannot be initialized on the media server. Verify",
        "full_action": "A scan cannot be initialized on the media server. Verify\nthat the media server is up and that there are no connection issues."
    },
    "7879": {
        "code": 7879,
        "desc": "No active scan host was found in the selected scan host pool.",
        "first_action": "You must activate the scan host that is associated with",
        "full_action": "You must activate the scan host that is associated with\nthe scan host pool."
    },
    "7880": {
        "code": 7880,
        "desc": "Unable to assign permissions on scan host credentials.",
        "first_action": "Verify if the supported media server is available and then",
        "full_action": "Verify if the supported media server is available and then\nreinitiate scan."
    },
    "7881": {
        "code": 7881,
        "desc": "The specified scan host pool and scan host mapping does not exist.",
        "first_action": "You must provide a valid scan host and scan host pool",
        "full_action": "You must provide a valid scan host and scan host pool\nID."
    },
    "7882": {
        "code": 7882,
        "desc": "Specified media server is not supported.",
        "first_action": "Upgrade the media server to a version that is supported.",
        "full_action": "Upgrade the media server to a version that is supported."
    },
    "7883": {
        "code": 7883,
        "desc": "Specified media server is not available.",
        "first_action": "Verify that the supported media server is available and",
        "full_action": "Verify that the supported media server is available and\nthen reinitiate scan."
    },
    "7884": {
        "code": 7884,
        "desc": "Storage server does not exist.",
        "first_action": "Verify that storage server is available or that it exists.",
        "full_action": "Verify that storage server is available or that it exists."
    },
    "7885": {
        "code": 7885,
        "desc": "Scan result data limit exceeds.",
        "first_action": "There are too many infected files that cannot be exported",
        "full_action": "There are too many infected files that cannot be exported\nto one file (limit is 200 MB). Review the detailed infected file list in the scan logs."
    },
    "7886": {
        "code": 7886,
        "desc": "Invalid scan result ID.",
        "first_action": "Verify that the scan job cancellation was from an invalid",
        "full_action": "Verify that the scan job cancellation was from an invalid\nscan result ID. Retry the operation."
    },
    "7887": {
        "code": 7887,
        "desc": "Specified X-Trigger-Method header is invalid.",
        "first_action": "PleaseenteravalidheaderthatcontainseitherAUTOMATIC",
        "full_action": "PleaseenteravalidheaderthatcontainseitherAUTOMATIC\nor MANUAL. If no value is entered, the default value is MANUAL is used."
    },
    "7888": {
        "code": 7888,
        "desc": "Large number of infected files.",
        "first_action": "Because the results cannot be exported or viewed, you",
        "full_action": "Because the results cannot be exported or viewed, you\nmust review the scan logs to view a detailed list of the infected files for the selected\nscan result."
    },
    "7889": {
        "code": 7889,
        "desc": "Too many infected files in the selected time range.",
        "first_action": "Select the Allow recovery of files impacted by malware option which can be",
        "full_action": "Review the scan logs to view the infected files list for the\nbackup images in the selected date range. Update the date range or recovery files\nand folders selection to reduce the number of infected files. Retry the operation.\nYou can also perform one of the following:\n■ Select the Allow recovery of files impacted by malware option which can be\nused to recover selective clean files.\n■ Skip that backup image from recovery."
    },
    "7890": {
        "code": 7890,
        "desc": "Unable to delete the scan host pool.",
        "first_action": "Review the scan results page to identify the scan jobs",
        "full_action": "Review the scan results page to identify the scan jobs\nthat are using the scan hosts associated with this scan host pool to scan backup\nimages. Wait for the scan jobs to finish and try again."
    },
    "7891": {
        "code": 7891,
        "desc": "Unable to delete the scan host.",
        "first_action": "Review the scan results page to identify the scan jobs",
        "full_action": "Review the scan results page to identify the scan jobs\nthat are using the selected scan host to scan backup images. Wait for the scan\njobs to finish and try again."
    },
    "7892": {
        "code": 7892,
        "desc": "Unable to remove the scan host from a scan host pool.",
        "first_action": "Review the scan results page to identify the scan jobs",
        "full_action": "Review the scan results page to identify the scan jobs\nthat are using the selected scan host to scan backup images. Wait for the scan job\nto finish and try to remove the scan host from the scan host pool again."
    },
    "7893": {
        "code": 7893,
        "desc": "No scan process was found for the specified scan result.",
        "first_action": "Review the scan result ID to get the correct scan process",
        "full_action": "Review the scan result ID to get the correct scan process\ninformation."
    },
    "7894": {
        "code": 7894,
        "desc": "Failed to cancel malware scan job.",
        "first_action": "Verify that you have the correct scan result ID and retry",
        "full_action": "Verify that you have the correct scan result ID and retry\nthe cancel operation with the correct scan result ID."
    },
    "7895": {
        "code": 7895,
        "desc": "The number of parallel scans should be in the range from 1 to 10.",
        "first_action": "Youmustenteravalidnumberofparallelscans.Thevalid",
        "full_action": "Youmustenteravalidnumberofparallelscans.Thevalid\nrange of parallel scans is 1 to 10."
    },
    "7896": {
        "code": 7896,
        "desc": "The requested scan host is mapped with an existing scan pool.",
        "first_action": "Remove the selected scan host from all associated scan",
        "full_action": "Remove the selected scan host from all associated scan\nhost pools and try to delete again."
    },
    "7897": {
        "code": 7897,
        "desc": "The requested scan host is associated with an existing scan result.",
        "first_action": "To clean up the scan results, adjust the cleanup period",
        "full_action": "To clean up the scan results, adjust the cleanup period\nand try to delete scan host again. Refer to the NetBackup Administrator’s Guide,\nVolume I for more information."
    },
    "7898": {
        "code": 7898,
        "desc": "Error in the processing scan and the recover request.",
        "first_action": "Review the job details in the Activity Monitor for an error",
        "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job."
    },
    "7899": {
        "code": 7899,
        "desc": "The requested recovery options are invalid.",
        "first_action": "Youmustverifytherecoveryrequestandtryagain.Review",
        "full_action": "Youmustverifytherecoveryrequestandtryagain.Review\nthe webservice logs for more details."
    },
    "7900": {
        "code": 7900,
        "desc": "Unable to initiate recovery request.",
        "first_action": "You must verify the recovery request and retry. Review",
        "full_action": "You must verify the recovery request and retry. Review\nthe webservice logs for more details."
    },
    "7901": {
        "code": 7901,
        "desc": "The specified malware job does not exist.",
        "first_action": "You must verify the recovery request and retry. Review",
        "full_action": "You must verify the recovery request and retry. Review\nthe webservice logs for more details."
    },
    "7902": {
        "code": 7902,
        "desc": "Failed to cancel malware job because the job is completed.",
        "first_action": "Completed malware jobs cannot be canceled.",
        "full_action": "Completed malware jobs cannot be canceled."
    },
    "7903": {
        "code": 7903,
        "desc": "Unable to create a scan and a recovery job.",
        "first_action": "Review the webservice logs and try again.",
        "full_action": "Review the webservice logs and try again."
    },
    "7905": {
        "code": 7905,
        "desc": "Unable to create a malware job.",
        "first_action": "Review the webservice logs and try again.",
        "full_action": "Review the webservice logs and try again."
    },
    "7907": {
        "code": 7907,
        "desc": "Too many backup images for scan and recover in selected date range.",
        "first_action": "Change the start or the end date of backup images that",
        "full_action": "Change the start or the end date of backup images that\nyou selected for recovery."
    },
    "7910": {
        "code": 7910,
        "desc": "Not able to complete scan job.",
        "first_action": "Review the job details in the Activity Monitor for an error",
        "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job."
    },
    "7911": {
        "code": 7911,
        "desc": "Workload is not supported for malware test scan. NetBackup status codes 970 NetBackup status codes",
        "first_action": "SelectbackupimageofStandardpolicytypefortestscan.",
        "full_action": "SelectbackupimageofStandardpolicytypefortestscan."
    },
    "7912": {
        "code": 7912,
        "desc": "Provided backup copy is not Instant Access capable.",
        "first_action": "Select a backup image or copy which is instant access",
        "full_action": "Select a backup image or copy which is instant access\ncapable. For example, backup image on MSDP storage."
    },
    "7913": {
        "code": 7913,
        "desc": "Not able to initiate scan on given scan host.",
        "first_action": "Review the job details in the Activity Monitor for an error",
        "full_action": "Review the job details in the Activity Monitor for an error\nand retry the job."
    },
    "7914": {
        "code": 7914,
        "desc": "Unable to delete scan result.",
        "first_action": "RefreshthewebUIanddetermineifthescanresultexists",
        "full_action": "RefreshthewebUIanddetermineifthescanresultexists\nin a failed or a canceled state."
    },
    "7915": {
        "code": 7915,
        "desc": "Too many scan results to cancel.",
        "first_action": "Reduce the number of scan results to cancel to 20 or",
        "full_action": "Reduce the number of scan results to cancel to 20 or\nfewer."
    },
    "8000": {
        "code": 8000,
        "desc": "User does not have permission(s) to perform the requested operation.",
        "first_action": "To perform the requested operation, you must be a root",
        "full_action": "To perform the requested operation, you must be a root\nuser, administrator, or have the appropriate privileges through Role-Based Access\nControl (RBAC). Contact the NetBackup system administrator."
    },
    "8001": {
        "code": 8001,
        "desc": "The JSON Web Token is expired",
        "first_action": "The user must log on again.",
        "full_action": "The user must log on again."
    },
    "8002": {
        "code": 8002,
        "desc": "JWT Token is invalid",
        "first_action": "The user must log on again.",
        "full_action": "The user must log on again."
    },
    "8009": {
        "code": 8009,
        "desc": "Specified permission not present in JSON Web Token",
        "first_action": "The user should contact the NetBackup security",
        "full_action": "The user should contact the NetBackup security\nadministrator to request RBAC permissions for the NetBackup web user interface."
    },
    "8016": {
        "code": 8016,
        "desc": "Cannot delete a role based access control resource that is configured in an access rule.",
        "first_action": "Before you can delete a role or an object group, you must",
        "full_action": "Before you can delete a role or an object group, you must\nremove it from all of the associated access rules."
    },
    "8018": {
        "code": 8018,
        "desc": "Identity cannot be empty. Enter a valid user or group.",
        "first_action": "The API expects a non-empty input value in order to",
        "full_action": "The API expects a non-empty input value in order to\nidentify and validate a user or group. Ensure that the identity input value is not\nempty."
    },
    "8019": {
        "code": 8019,
        "desc": "Invalid identity format. When specifying a domain, use either the User Principal Name (UPN) format or the Down-Level Logon Name format.",
        "first_action": "Username@DOMAIN",
        "full_action": "TheAPIrequiresthattheinputvaluebeinaspecificformat\nin order to identify and validate a user or group. Ensure that the identity input value\nis in one of the following formats:\n■ username@DOMAIN\n■ DOMAIN\\username\n■ groupname@DOMAIN\n■ DOMAIN\\groupname\n■ username\n■ groupname"
    },
    "8021": {
        "code": 8021,
        "desc": "Unable to validate the user or group.",
        "first_action": "Use the vssat addldapdomain command to configure",
        "full_action": "Use the vssat addldapdomain command to configure\nthe LDAP domain. For more information, refer to the NetBackup Commands\nReference Guide."
    },
    "8051": {
        "code": 8051,
        "desc": "FULL recovery backup not found.",
        "first_action": "You must start or schedule a full backup first and then an",
        "full_action": "You must start or schedule a full backup first and then an\nincremental backup can be run or scheduled. After this incremental backup, the\nimage can be recovered."
    },
    "8053": {
        "code": 8053,
        "desc": "Asset type for recovery object does not match with scenario type.",
        "first_action": "Set the value of assetType to INSTANCE in the payload.",
        "full_action": "Set the value of assetType to INSTANCE in the payload."
    },
    "8054": {
        "code": 8054,
        "desc": "Unknown host server.",
        "first_action": "Verifythatthetargethostis a valid NetBackupclienthost.",
        "full_action": "Verifythatthetargethostis a valid NetBackupclienthost."
    },
    "8055": {
        "code": 8055,
        "desc": "Error while renaming file.",
        "first_action": "Verify that the path that is provided doesn't contain any",
        "full_action": "Verify that the path that is provided doesn't contain any\nnon-ASCII characters.\nIf you need to contact Cohesity Technical Support, you must have the tar log from\nthe recovery host."
    },
    "8056": {
        "code": 8056,
        "desc": "Database name is invalid input for instance recovery.",
        "first_action": "Remove the database name from payload.",
        "full_action": "Remove the database name from payload."
    },
    "8100": {
        "code": 8100,
        "desc": "The vCloud organization name cannot be blank.",
        "first_action": "Verify that the vCloud organization name is added. Retry",
        "full_action": "Verify that the vCloud organization name is added. Retry\nthe operation and if the issue persists, visit support.veritas.com. The Cohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue."
    },
    "8101": {
        "code": 8101,
        "desc": "The vCloud organization virtual datacenter name cannot be blank.",
        "first_action": "VerifythatthevCloudorganizationvirtualdatacentername",
        "full_action": "VerifythatthevCloudorganizationvirtualdatacentername\nis added. Retry the operation and if the issue persists, visit support.veritas.com.\nThe Cohesity Technical Support website site offers additional information to help\nyou troubleshoot this issue."
    },
    "8102": {
        "code": 8102,
        "desc": "The vCloud vApp name cannot be blank.",
        "first_action": "Verify that the vCloud vApp name is added. Retry the",
        "full_action": "Verify that the vCloud vApp name is added. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue."
    },
    "8103": {
        "code": 8103,
        "desc": "The vCloud catalog name cannot be blank.",
        "first_action": "Verify that the vCloud catalog name is added. Retry the",
        "full_action": "Verify that the vCloud catalog name is added. Retry the\noperationandiftheissuepersists,visitsupport.veritas.com.TheCohesityTechnical\nSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshootthisissue."
    },
    "8104": {
        "code": 8104,
        "desc": "The vCloud catalog vApp template name cannot be blank.",
        "first_action": "Verify that the vCloud catalog vApp template name is",
        "full_action": "Verify that the vCloud catalog vApp template name is\nadded. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website site offers additional information to help you\ntroubleshoot this issue."
    },
    "8105": {
        "code": 8105,
        "desc": "Specify a valid value for the recovery failure strategy.",
        "first_action": "Provide the valid values of recovery failure strategy type",
        "full_action": "Provide the valid values of recovery failure strategy type\nas Fail Fast, Proceed Ahead, or Retry."
    },
    "8106": {
        "code": 8106,
        "desc": "Specify a valid value for the retry count.",
        "first_action": "Provide a valid retry count when the Retry strategy type",
        "full_action": "Provide a valid retry count when the Retry strategy type\nis selected. The valid Retry count range is 2 to 5."
    },
    "8107": {
        "code": 8107,
        "desc": "The recovery failure strategy feature is disabled on the Kubernetes workload.",
        "first_action": "Enable the feature toggle for AIR, duplication, and the",
        "full_action": "Enable the feature toggle for AIR, duplication, and the\nrestore failure strategy."
    },
    "8200": {
        "code": 8200,
        "desc": "KMIP internal error.",
        "first_action": "Reviewthenbkmiputillegacylogstohelpfindthecause",
        "full_action": "Reviewthenbkmiputillegacylogstohelpfindthecause\nof the issue. If the issue persists, visit the Cohesity Technical Support website. The\nCohesity Technical Support website offers additional information to help you\ntroubleshoot this issue."
    },
    "8201": {
        "code": 8201,
        "desc": "Failed to connect to the external KMS server.",
        "first_action": "The external KMS server name or the IP address might",
        "full_action": "The external KMS server name or the IP address might\nbe wrong. Check the network connectivity between the master server and the\nexternal KMS server."
    },
    "8203": {
        "code": 8203,
        "desc": "Failed to initialize SSL context to connect to the external KMS server.",
        "first_action": "Check for any mismatch between private key and",
        "full_action": "Check for any mismatch between private key and\ncertificate. Check for any out of memory error."
    },
    "8204": {
        "code": 8204,
        "desc": "Failed to establish SSL connection with the external KMS server.",
        "first_action": "Review the credentials (private key, certificate, CA",
        "full_action": "Review the credentials (private key, certificate, CA\ncertificate, passphrase for private key) that are used to connect to EKMS server."
    },
    "8205": {
        "code": 8205,
        "desc": "FailedtoestablishSSLconnectionwiththeexternalKMSserverbecause the connection times out.",
        "first_action": "Increase the connection time-out value.",
        "full_action": "Increase the connection time-out value."
    },
    "8207": {
        "code": 8207,
        "desc": "The KMIP request to external KMS server failed.",
        "first_action": "Check the connection with the server.",
        "full_action": "Try one of the following as appropriate:\n■ Check the connection with the server.\n■ Check the operation by running the nbkmiputil command."
    },
    "8208": {
        "code": 8208,
        "desc": "The KMIP request to external KMS server has timed out.",
        "first_action": "Increase the request time-out value. Check the server",
        "full_action": "Increase the request time-out value. Check the server\nresponse using EKMS CLI or any other network tool."
    },
    "8209": {
        "code": 8209,
        "desc": "The KMIP item cannot be found.",
        "first_action": "Check whether the KMIP item is present on the EKMS",
        "full_action": "Check whether the KMIP item is present on the EKMS\nserver using EKMS CLI or any other network tool."
    },
    "8211": {
        "code": 8211,
        "desc": "SSL verification failed due to host name mismatch.",
        "first_action": "Check that the connecting host name exists in the KMS",
        "full_action": "Check that the connecting host name exists in the KMS\nserver certificate SAN or CN field. If the host name does not exist, fix the server\ncertificate or bypass the peer host validation by setting the EKMS_VERIFY_HOST=0\nflag in the bp.conf file."
    },
    "8212": {
        "code": 8212,
        "desc": "SSL verification failed due to IP address mismatch.",
        "first_action": "Check that the connecting host name IP address exists",
        "full_action": "Check that the connecting host name IP address exists\nin the KMS server certificate SAN or CN field. If the host name IP address does not\nexist, fix the server certificate or bypass the peer host validation by setting the\nEKMS_VERIFY_HOST=0 flag in the bp.conf file."
    },
    "8216": {
        "code": 8216,
        "desc": "The KMIP version is not supported.",
        "first_action": "The KMIP server and the client are mismatched in the",
        "full_action": "The KMIP server and the client are mismatched in the\nKMIP protocol version. Refer to the Cohesity Software Compatibility List or the\nNetBackup Security and Encryption Guide for supported KMIP versions."
    },
    "8217": {
        "code": 8217,
        "desc": "Error was encountered at external KMS server while the operation was performed.",
        "first_action": "Perform the same operation through EKMS CLI or any",
        "full_action": "Perform the same operation through EKMS CLI or any\nother network tool."
    },
    "8220": {
        "code": 8220,
        "desc": "The permission is denied.",
        "first_action": "Review user permissions at the EKMS server whose",
        "full_action": "Review user permissions at the EKMS server whose\ncertificate is used to connect to EKMS server."
    },
    "8221": {
        "code": 8221,
        "desc": "The KMIP object is archived.",
        "first_action": "The KMIP object must be recovered from the archive",
        "full_action": "The KMIP object must be recovered from the archive\nbefore the operation is performed using the EKMS server tool."
    },
    "8224": {
        "code": 8224,
        "desc": "NetBackup does not support any of the KMIP versions that the external KMS server supports.",
        "first_action": "Check if the external KMS server supports any of the",
        "full_action": "Check if the external KMS server supports any of the\nNetBackup supported KMIP versions and change the external KMS server setting\nto use it."
    },
    "8226": {
        "code": 8226,
        "desc": "The KMIP operation is not attempted.",
        "first_action": "Debug or troubleshoot the pre-requisite operation and",
        "full_action": "Debug or troubleshoot the pre-requisite operation and\nthen try again."
    },
    "8227": {
        "code": 8227,
        "desc": "No NetBackup keys are found.",
        "first_action": "Check the EKMS server whether any key is defined with",
        "full_action": "Check the EKMS server whether any key is defined with\ncustomattributex-application=NetBackuptoqualifyasNetBackup(casesensitive)\nkey. Review user permissions and verify that the user has the permission to locate\nkeys as per their privileges."
    },
    "8228": {
        "code": 8228,
        "desc": "Failed to perform CRL check.",
        "first_action": "Verify that the CRL and the EKMS server certificates are from the same CA.",
        "full_action": "Check for following things as appropriate:\n■ Verify that the CRL and the EKMS server certificates are from the same CA.\n■ Verify that the ECA_CRL_PATH is set in the NetBackup configuration. If the path\nexists, confirm that is has EKMS server certificate CRLs.\n■ If ECA_CRL_PATH is not set, verify that the EKMS server certificate has CDP\ndefined.\n■ If the CDP is defined, verify that the CDP server is reachable.\n■ If CDP server is reachable, then verify that the downloader vnetd service is up\nand running.\n■ IfCRLchecklevelisnotdefinedatthetimeofKMSconfigurationthenthedefault\nCRL check level is LEAF."
    },
    "8229": {
        "code": 8229,
        "desc": "The external KMS server certificate is revoked.",
        "first_action": "Use the unrevoked certificate for the EKMS server or the",
        "full_action": "Use the unrevoked certificate for the EKMS server or the\nCRL check can be disabled."
    },
    "8234": {
        "code": 8234,
        "desc": "Failed to set certificate in the SSL context.",
        "first_action": "Use a PEM encoded certificate.",
        "full_action": "Use a PEM encoded certificate."
    },
    "8235": {
        "code": 8235,
        "desc": "Failed to set CA certificates in the SSL context.",
        "first_action": "Use PEM encoded CA certificates.",
        "full_action": "Use PEM encoded CA certificates."
    },
    "8236": {
        "code": 8236,
        "desc": "Failed to set private key in the SSL context.",
        "first_action": "Use a PEM encoded private key. Verify the key matches",
        "full_action": "Use a PEM encoded private key. Verify the key matches\nwith the provided certificate by using the openssl utility."
    },
    "8237": {
        "code": 8237,
        "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable for encryption.",
        "first_action": "Set the Cryptographic Usage mask of the key for encryption.",
        "full_action": "Perform the following as appropriate:\n■ Set the Cryptographic Usage mask of the key for encryption.\n■ Correct the Process Start date.\n■ Correct the Protect Stop date.\n■ Check if the time and or date does not match between the NetBackup master\nserver and the external KMS server. If they do not match, correct the time and\nor date."
    },
    "8238": {
        "code": 8238,
        "desc": "ThekeysthatwereretrievedfromtheexternalKMSserverarenotusable for decryption.",
        "first_action": "Set the Cryptographic Usage mask of the key for decryption.",
        "full_action": "Perform the following as appropriate:\n■ Set the Cryptographic Usage mask of the key for decryption.\n■ Correct the Process Start date.\n■ Check if the time and or date does not match between the NetBackup master\nserver and the external KMS server. If they do not match, correct the time and\nor date.\n■ SettheflagEKMS_DISABLE_KEY_USAGE_CHECK=1inbp.conftobypasskeyusage\ncheck."
    },
    "8240": {
        "code": 8240,
        "desc": "The KMIP object already exists.",
        "first_action": "The KMIP object must be provided with a unique name",
        "full_action": "The KMIP object must be provided with a unique name\nwhen the object is created."
    },
    "8250": {
        "code": 8250,
        "desc": "Cannot create the NetBackup job.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8251": {
        "code": 8251,
        "desc": "Failed to update NetBackup job.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8252": {
        "code": 8252,
        "desc": "Unsupported policy type.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8253": {
        "code": 8253,
        "desc": "Cannot restore the requested resource.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8300": {
        "code": 8300,
        "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it cannot be enabled as the client or the backup host version is older than 9.1.",
        "first_action": "Upgrade the NetBackup client or the backup host to a version that supports",
        "full_action": "Perform the following as appropriate:\n■ Upgrade the NetBackup client or the backup host to a version that supports\ndata-in-transit encryption.\n■ Contact your security administrator and change the data-in-transit encryption\nglobal setting to PREFERRED_ON or PREFERRED_OFF.\nNote that the data-in-transit encryption is disabled during communication with\nhosts running a version older than 9.1.\nFor more information, refer to theConfiguring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8301": {
        "code": 8301,
        "desc": "Theglobaldata-in-transitencryptionisenforcedintheNetBackupdomain, but it cannot be enabled as the media server version is older than 9.1.",
        "first_action": "Upgrade the NetBackup media server to a version that supports data-in-transit",
        "full_action": "Perform one of the following as appropriate:\n■ Upgrade the NetBackup media server to a version that supports data-in-transit\nencryption.\n■ Changetheconfigurationtoselectthemediaserverwhichsupportsdata-in-transit\nencryption for performing the NetBackup operations.\n■ Contact your security administrator and change the data-in-transit encryption\nglobal setting to PREFERRED_ON or PREFERRED_OFF.\nNotethatdata-in-transitencryptionisdisabledduringcommunicationwithhosts\nhaving a version older than 9.1.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8302": {
        "code": 8302,
        "desc": "The data-in-transit encryption attribute of the backup image cannot be updated.",
        "first_action": "1. Ensure that the bpdbm service is running on the primary server and there is",
        "full_action": "Perform the following:\n1. Ensure that the bpdbm service is running on the primary server and there is\nconnectivity between the media server and the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server bpbrm logs available to help troubleshoot the issue."
    },
    "8303": {
        "code": 8303,
        "desc": "The data-in-transit encryption attribute of the job cannot be updated.",
        "first_action": "1. Ensure that the bpjobd service is running on the primary server and there is",
        "full_action": "Perform the following:\n1. Ensure that the bpjobd service is running on the primary server and there is\nconnectivity between the media server and the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server and the primary server logs available to help\ntroubleshoot the issue."
    },
    "8304": {
        "code": 8304,
        "desc": "The global data-in-transit encryption setting cannot be fetched.",
        "first_action": "1. Ensure that the bpcd service is running on the primary server.",
        "full_action": "Perform the following:\n1. Ensure that the bpcd service is running on the primary server.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the following primary server logs available to help troubleshoot the\nissue:\n■ nbwebservice\n■ nbjm\n■ bprd\n■ bpcd"
    },
    "8305": {
        "code": 8305,
        "desc": "The data-in-transit encryption setting of the client cannot be fetched. NetBackup status codes 989 NetBackup status codes",
        "first_action": "1. Ensure bpcd service is running on the client.",
        "full_action": "Perform the following:\n1. Ensure bpcd service is running on the client.\n2. Retry the operation and if the issue persists, visit support.veritas.com. The\nCohesity Technical Support website offers additional information to help you\ntroubleshootthisissue.IfyoudocontactCohesityTechnicalSupport,youneed\nto have the media server bpbrm and the client bpcd logs available to help\ntroubleshoot the issue."
    },
    "8306": {
        "code": 8306,
        "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, therefore NetBackup tries to encrypt the data but the media server version is older than 9.1.",
        "first_action": "1. UpgradetheNetBackupmediaservertoaversionthatsupportsdata-in-transit",
        "full_action": "Perform one of the following as appropriate:\n1. UpgradetheNetBackupmediaservertoaversionthatsupportsdata-in-transit\nencryption.\n2. Change the configuration to select the media server which supports\ndata-in-transit encryption for performing NetBackup operations.\n3. Change the data-in-transit encryption (DTE) mode of the given backup image\nto Off using the following command:\nbpimage -update -image_dtemode Off -id <backup_id>\n4. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in the NetBackup\nconfiguration file of the primary server or the media server.\nFor option 3 and option 4, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8307": {
        "code": 8307,
        "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but the DTE setting is disabled on the client or the backup host.",
        "first_action": "If data-in-transit is to be enforced for a client or a backup host, then enable",
        "full_action": "Perform one of the following as appropriate:\n■ If data-in-transit is to be enforced for a client or a backup host, then enable\ndata-in-transit encryption for that client or a backup host. Enable encryption by\nsetting the DTE_CLIENT_MODE option in the bp.conf configuration file to On.\n■ If data-in-transit encryption is to be off for a particular client or a backup host,\nperform the following:\n■ Set the data-in-transit encryption of the domain to PREFERRED_ON.\nFor option 2, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8308": {
        "code": 8308,
        "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, therefore NetBackup tries to encrypt the data but the client version is older than 9.1.",
        "first_action": "1. Upgrade the NetBackup client to a version that supports data-in-transit",
        "full_action": "Perform one of the following as appropriate:\n1. Upgrade the NetBackup client to a version that supports data-in-transit\nencryption.\n2. Change the data-in-transit encryption (DTE) mode of the given backup image\nto Off using the following command:\nbpimage -update -image_dtemode Off -id <backup_id>\n3. Set DTE_IGNORE_IMAGE_MODE = WHERE_UNSUPPORTED in the NetBackup\nconfiguration file of the primary server.\nFor option 2 and option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8310": {
        "code": 8310,
        "desc": "The data-in-transit encryption (DTE) setting is enabled on the client, but is disabled on the media server.",
        "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports",
        "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operation.\n2. The media server that handles the given operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver <media_server_name>\n3. If the media server that handles the NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ The global DTE mode should be either PREFERRED_OFF or PREFERRED_ON.\n■ The DTE client mode setting needs to be either OFF or AUTOMATIC.\nFor option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8311": {
        "code": 8311,
        "desc": "Theglobaldata-in-transitencryption(DTE)isenforcedintheNetBackup domain, but the DTE setting is disabled on the media server.",
        "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports",
        "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operation.\n2. The media server that handles the secondary operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on -mediaserver <media_server_name>\n3. If the media server that handles the NetBackup operation needs to have\ndata-in-transitencryptiondisabled,ensurethatthefollowingconfigurationsare\nset:\n■ The global DTE mode should be either PREFERRED_OFF or PREFERRED_ON.\n■ The DTE client mode setting needs to be either OFF or AUTOMATIC.\nFor option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8312": {
        "code": 8312,
        "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, but the DTE setting is disabled on the media server. NetBackup status codes 993 NetBackup status codes",
        "first_action": "1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports",
        "full_action": "Perform one of the following as appropriate:\n1. ChangetheNetBackupconfigurationtoselectthemediaserverwhichsupports\ndata-in-transit encryption for performing the NetBackup operations.\n2. The media server that handles the secondary operation needs to have the\ndata-in-transitencryptionsettingenabled.ChangethemediaserverDTEsetting\nof the given media server to on using the following command:\nnbseccmd -setsecurityconfig -dtemediamode on\n-mediaserver <media_server_name>\n3. If the media server that handles the backup needs to have data-in-transit\nencryption disabled, change the data-in-transit encryption (DTE) mode of the\nbackup image to Off using the following command:\nbpimage -update -image_dtemode Off -id <backup_id>\nNote: This option is not applicable for import phase 1.\n4. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in the NetBackup configuration file of\nthe primary server or media server (for import phase 1).\nFor option 3 and option 4, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8313": {
        "code": 8313,
        "desc": "The data-in-transit encryption (DTE) mode of the backup image is set to On, but the DTE setting is disabled on the client.",
        "first_action": "1. If data-in-transit is to be enforced for the client, then enable data-in-transit",
        "full_action": "Perform one of the following as appropriate:\n1. If data-in-transit is to be enforced for the client, then enable data-in-transit\nencryptionforthatclientbysettingtheDTE_CLIENT_MODEoptioninthebp.conf\nconfiguration file to On.\n2. If data-in-transit is to be off for the particular client then change the\ndata-in-transit encryption (DTE) mode of the backup image to Off using the\nfollowing command:\nbpimage -update -image_dtemode Off -id <backup_id>\n3. Set DTE_IGNORE_IMAGE_MODE = ALWAYS in the NetBackup configuration file of\nthe primary server.\nFor option 2 and option 3, DTE is disabled while the job is performed.\nFor more information, refer to the Configuring data-in-transit encryption section in\nthe NetBackup Security and Encryption Guide."
    },
    "8314": {
        "code": 8314,
        "desc": "The media is not yet ready for the backup operation.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8315": {
        "code": 8315,
        "desc": "The media server has not completed the backup operation.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8316": {
        "code": 8316,
        "desc": "Failed to retrieve the pre-shared key which is required for TLS communication.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8350": {
        "code": 8350,
        "desc": "The backup job failed. The protection plan is configured to fail partially successful backups.",
        "first_action": "Reviewthejob detailstosee theresourcesthatfail.Ifyou",
        "full_action": "Reviewthejob detailstosee theresourcesthatfail.Ifyou\nwant to retain a backup with the failed resources, consider disabling this feature.\nIn the Backup options tab, while configuring a protection plan, clear the option:\nFail a backup job, if any of the resources fail to get protected"
    },
    "8351": {
        "code": 8351,
        "desc": "Kubernetes Operator Service is down.",
        "first_action": "To verify the status of the deployment, run the",
        "full_action": "To verify the status of the deployment, run the\ncommand:helm list -n <namespace in which you have deployed the K8s\nNB operator>\nMake sure that the Kubernetes NetBackup operator is deployed in the cluster."
    },
    "8352": {
        "code": 8352,
        "desc": "The asset group doesn’t have valid clusters.",
        "first_action": "To run the backup, select an asset group with a valid",
        "full_action": "To run the backup, select an asset group with a valid\ncluster or a cluster that is not deleted."
    },
    "8401": {
        "code": 8401,
        "desc": "Error in creating the service <service-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and ensure that it meets the expected\nprerequisites.RefertotheNetBackupDeploymentonAzureKubernetesCluster\n(AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\n■ kubectl delete -f <environment.yaml> and recreate it again kubectl\napply -f <environment.yaml>\nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain."
    },
    "8402": {
        "code": 8402,
        "desc": "Error in fetching the service <service-name> from the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>. NetBackup status codes 997 NetBackup status codes",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if the service is created in the given namespace using the following\ncommand:\nkubectl get service <service-name> -n <namespace>\n■ Check the Kubernetes documentation for service\ndetails:https://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8403": {
        "code": 8403,
        "desc": "Error in creating the service <service-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name> because the service is already available in the namespace with an unexpected label.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the service using the following command:\nkubectl delete service <service-name> -n <namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Refer to the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8404": {
        "code": 8404,
        "desc": "Error in creating the service <service-name> in the namespace <namespace>forthePrimaryServer <PrimaryServer-name>becausetheservice is already available in the namespace with an unexpected selector.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<operator-namespace>\n■ Delete the service using the following command:\nkubectl delete service <service-name> -n <namespace>\nThe NetBackup operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8405": {
        "code": 8405,
        "desc": "Error in creating the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\n■ kubectl delete -f <environment.yaml> and recreate it again kubectl\napply -f <environment.yaml>\nThe NetBackup environment and its resources are deleted and recreated\nagain."
    },
    "8406": {
        "code": 8406,
        "desc": "Error in fetching the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\n“”.\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if ConfigMap is available in given namespace using the following\ncommand:\nkubectl get configmap <configmap-name> -n <namespace>\n■ Check the Kubernetes documentation for ConfigMap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/"
    },
    "8407": {
        "code": 8407,
        "desc": "Error in creating the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name> because the ConfigMap is already present in the namespace.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the existing ConfigMap with the same name in the namespace."
    },
    "8408": {
        "code": 8408,
        "desc": "ErrorincreatingPVC <PVC-name>inthenamespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check if storageClassName and PVC storage capacity are correct in the CR\nYAML. If PVC is already available in the namespace with the same name, use\ncommand kubectl get pvc <pvc-name> -n <namespace> to verify storage\ncapacity. The storage capacity must be greater than or equal to the storage\ncapacity that is mentioned in the CR spec.\n■ Check if the storageClassName provided in CR is available in the cluster using\nfollowing command:\nkubectl get storageclass\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/"
    },
    "8409": {
        "code": 8409,
        "desc": "Error in fetching the PVC <PVC-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check if the PVC is available in namespace using the following command:\nkubectl get pvc <pvc-name> -n <namespace>\nIfthePVCisnotavailable,applytheenvironmentYAMLagainusingthefollowing\ncommand:\nkubectl apply -f <environment.yaml>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/"
    },
    "8410": {
        "code": 8410,
        "desc": "ErrorinupdatingPVC <PVC-name>inthenamespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ EnsurethenewPVCstoragecapacitythatismentionedintheCRisgreaterthan\ncurrent storage capacity. You cannot shrink the capacity. In this case, update\ntheCRYAMLwithcorrectsizeandapplytheCRYAMLagainusingthefollowing\ncommand:\nkubectl apply -f <environment.yaml>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details:\nhttps://kubernetes.io/docs/concepts/storage/persistent-volumes/"
    },
    "8411": {
        "code": 8411,
        "desc": "Error in creating the StatefulSet <sts-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command: “",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command: “\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ Check if the required secrets are present in the namespace."
    },
    "8412": {
        "code": 8412,
        "desc": "Error in fetching the StatefulSet <sts-name> from the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you can\ndelete the environment CR using the following command:\nkubectl delete -f <environment.yaml>andrecreateitagainkubectl apply\n-f <environment.yaml>\nTheNetBackupenvironmentanditsresourcesaredeletedandrecreatedagain."
    },
    "8413": {
        "code": 8413,
        "desc": "Error in creating the StatefulSet <sts-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name> because the StatefulSet is already available in the namespace with an unexpected label.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset <statefulset-name> -n <namespace>\nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8414": {
        "code": 8414,
        "desc": "Error in creating the StatefulSet <sts-name> in the namespace <namespace-name> for the PrimaryServer <PrimaryServer-name> because the StatefulSet is already available in the namespace with an unexpected selector.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<operator-namespace>\n■ Delete the existing statefulset using the following command: “.\nkubectl delete statefulset <statefulset-name> -n <namespace>\nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8415": {
        "code": 8415,
        "desc": "Error in creating the service <service-name> in the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If the issue still doesn’t resolve, perform the following steps:\n■ Edit the environment CR and decrement the media server replicas. Change\nthereplicacountinthemediasectionwiththelastsuccessfulcountforwhich\nthe load balancer service was created for the media replicas. Then, apply\nthe changes using the following command:\nkubectl apply -f <environment.yaml>\n■ For example: The media replica count is set to three and services are\nsuccessfully created for only two media servers replicas. However, there\nisanerrorincreatingserviceforthethirdmediaserver.Youmustchange\nthe replica count to two.\n■ If there is an error in creating service for the first media replica, change\nthe replica count to 0.\n■ Verify if the media replica services are decremented as per provided replica\ncount using the following command:\nkubectl get service <service-name> -n <namespace>\n■ Edit the environment CR and increment media replica count back to the\noriginal count and apply the changes. Verify if the service is now created for\nrespective media server."
    },
    "8416": {
        "code": 8416,
        "desc": "Error in fetching the service <service-name> from the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if service is available in given namespace using the following command:\nkubectl get service <service-name> -n <namespace>\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8417": {
        "code": 8417,
        "desc": "Service <service-name> already available in the namespace <namespace> for the MediaServer <MediaServer-name> with unexpected labels.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the service using the following command:\nkubectl delete service <service-name> -n <namespace>\nThe operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8418": {
        "code": 8418,
        "desc": "Service <service-name> already available in the namespace <namespace>fortheMediaServer <MediaServer-name>withunexpectedselectors.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the service using the following command:\nkubectl delete service <service-name> -n <namespace>\nThe operator recreates the service.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/"
    },
    "8419": {
        "code": 8419,
        "desc": "Error in creating the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for service details:\nhttps://kubernetes.io/docs/concepts/services-networking/service/\n■ If you deploy NetBackup on Azure Kubernetes Cluster for the first time, you\ncan delete the media CR by removing the mediaServers section in the\nenvironment CR YAML. You need to save the mediaServer data to reuse it\nin next step.\n■ Recreate the MediaServer CR again by updating the environment.yaml\nwiththemediaServerssectionthatwasdeletedearlierandapplythechanges\nusing the following command:\nkubectl apply -f <environment.yaml>\nThe NetBackup environment and its resources are deleted and recreated\nagain."
    },
    "8420": {
        "code": 8420,
        "desc": "Error in fetching the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if configmap is available in the given namespace using the following\ncommand:\nkubectl get configmap <configmap-name> -n <namespace>\n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/"
    },
    "8421": {
        "code": 8421,
        "desc": "Error in updating the ConfigMap <ConfigMap-name> in the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/"
    },
    "8422": {
        "code": 8422,
        "desc": "ConfigMap <ConfigMap-name> is already available in the namespace <namespace-name> for the MediaServer <MediaServer -name> with unexpected labels.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check the Kubernetes documentation for configmap details:\nhttps://kubernetes.io/docs/concepts/configuration/configmap/"
    },
    "8423": {
        "code": 8423,
        "desc": "Error in creating the StatefulSet <sts-name> in the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster configuration and verify that it meets the expected\nprerequisites for NetBackup deployment. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8424": {
        "code": 8424,
        "desc": "Error in fetching the StatefulSet <sts-name> from the namespace <namespace-name> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check your cluster for issues and verify that the configuration is correct. Verify\nthat it meets the expected prerequisites for NetBackup deployment. Refer to\ntheNetBackupDeploymentonAzureKubernetesCluster(AKS)Administrator’s\nGuide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/\n■ If the setup is a fresh deployment and the backup and the recovery jobs are not\nconfigured:\n■ You may delete the CR by removing mediaServers section in\nenvironment.yaml (user needs to save the mediaServer data to reuse it in\nnext step) and apply the changes using the following command:\nkubectl apply -f <environment.yaml>\n■ Recreate the MediaServer CR again by updating the environment.yaml\nwiththeMediaServersectionthatwasdeletedearlierandapplythechanges\nusing the following command:\nkubectl apply -f <environment.yaml>\nThe NetBackup environment and its resources are deleted and recreated\nagain."
    },
    "8425": {
        "code": 8425,
        "desc": "Error in updating the StatefulSet <sts-name> from the namespace <namespace-name> for the MediaServer <MediaServer -name>. NetBackup status codes 1011 NetBackup status codes",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check if the replica count in the media server section in environment CR is\ngreater than the previously used replica count.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8426": {
        "code": 8426,
        "desc": "StatefulSet <Statefulset-name>alreadyavailableinthenamespace <namespace> for the MediaServer <MediaServer> with unexpected labels.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset <statefulset-name> -n <namespace>\nThe operator recreates the statefulset.\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8427": {
        "code": 8427,
        "desc": "StatefulSet <Statefilset-name>alreadyavailableinthenamespace <namespace> for the MediaServer <MediaServer> with unexpected selectors. NetBackup status codes 1012 NetBackup status codes",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the existing statefulset using the following command:\nkubectl delete statefulset <statefulset-name> -n <namespace>\n■ Check the Kubernetes documentation for statefulset details:\nhttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/"
    },
    "8428": {
        "code": 8428,
        "desc": "Failed to get an instance of the Primary service.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Checkiftheprimaryloadbalancerserviceisavailableingivennamespaceusing\nthe following command:\nkubectl get service <service-name> -n <namespace>\n■ Check your cluster verify that the configuration is correct. Verify that it meets\nthe expected prerequisites for NetBackup deployment. Refer to the NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide."
    },
    "8429": {
        "code": 8429,
        "desc": "Failed to get the load balancer service details of the primary server.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ There might be an issue in fetching the service. Verify that RBAC permissions\nare correct. Refer to the NetBackup Deployment on Azure Kubernetes Cluster\n(AKS) Administrator’s Guide."
    },
    "8430": {
        "code": 8430,
        "desc": "Failed to connect to the primary server because the primary server may not have started.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Ensurethattheclusternetworkisconfiguredcorrectly.Theloadbalancerservice\nmay not be routing requests to the pod correctly.\n■ Check the PrimaryServer pod is in the ready state (1/1)."
    },
    "8431": {
        "code": 8431,
        "desc": "Failed to get primary server’s authentication secret <secret-name> in the namespace <namespace>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check that the respective secret is available in the namespace where the\nPrimaryServer CR is deployed using the following command:\nkubectl get secret <secret-name> -n <namespace>"
    },
    "8432": {
        "code": 8432,
        "desc": "Failed to get the CA certificate fingerprint or token from the primary server.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ The PrimaryServer credentials may have expired. Wait for the next reconciler\nloop (wait time for 5 min added).\n■ Look for the primary server pod and check the ready state (1/1) of the\nPrimaryServer pod using the following command:\nkubectl get pod -n <namespace>\nIf primary pod is not in ready state, check the health probe events using the\nfollowing command:\nkubectl describe <primary-pod-name> -n\n<netbackup-environment-namespace>\n■ For more information that is related to health probes, refer to the NetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide."
    },
    "8433": {
        "code": 8433,
        "desc": "Error in updating the bp.conf of the primary server in the namespace <namespace> for the MediaServer <MediaServer -name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Ensurethattheprimaryservercredentialsthatareinthesecretarenotexpired."
    },
    "8434": {
        "code": 8434,
        "desc": "Only one IP can be provided in the iplist of the Custom Resource for a primary server.",
        "first_action": "In the networkLoadBalancer of the primary section of the environment CR",
        "full_action": "Perform the following as appropriate:\n■ In the networkLoadBalancer of the primary section of the environment CR\nYAML, the number of entries that are mentioned in the ipList must be equal\nto 1.\nIf not, edit the environment CR with either of following items and ensure that\nthe number of entries in ipList of the primary section must be equal to 1.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n<netbackup-environment-name> -n <environmentCR-namespace>\n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f <environment.yaml>"
    },
    "8435": {
        "code": 8435,
        "desc": "NumberofIPsprovidedinipListofCustomResourcemustnotbeless than the replica count.",
        "first_action": "Verify the number of IP addresses that are mentioned in the ipList provided",
        "full_action": "Perform the following as appropriate:\n■ Verify the number of IP addresses that are mentioned in the ipList provided\nin the networkLoadBalancer of the media section in the environment CR. The\nnumber must be greater than or equal to the media replica count that is\nmentioned in same section.\nIf not, edit the environment CR and ensure that the number of entries in the\nipList of the mediaServers section is greater than or equal to media replica\ncount. Edit the environment CR with either of the following items:\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n<netbackup-environment-name> -n <environmentCR-namespace>\n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f <environment.yaml>"
    },
    "8436": {
        "code": 8436,
        "desc": "ResourceNamePrefix in spec of custom resource of the media server must not contain the string primary.",
        "first_action": "Ensure that the resourceNamePrefix in the mediaServers section of the",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the resourceNamePrefix in the mediaServers section of the\nenvironment CR does not have the primary substring.\nIf it does contain the primary substring, edit the environment CR with either of\nfollowing steps and update the resourceNamePrefix in the mediaServers\nsection.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n<netbackup-environment-name> -n <environmentCR-namespace>\n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f <environment.yaml>"
    },
    "8437": {
        "code": 8437,
        "desc": "ResourceNamePrefix in spec of custom resource of the primary server must not contain the string media.",
        "first_action": "Ensure that the resourceNamePrefix in primary section of environment CR",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the resourceNamePrefix in primary section of environment CR\ndoes not have the media substring.\nIf not, edit the environment CR with either of following items and update the\nresourceNamePrefix in the primary section.\n■ Edit the environment CR using following command and save:\nkubectl edit environments.netbackup.veritas.com\n<netbackup-environment-name> -n <environmentCR-namespace>\n■ Edit the environment CR YAML and apply the change using following\ncommand:\nkubectl apply -f <environment.yaml>"
    },
    "8438": {
        "code": 8438,
        "desc": "External IP is not assigned to service <service-name>.",
        "first_action": "Check the service events for a detailed message using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the service events for a detailed message using the following command:\nkubectl describe <service-name> -n <namespace>\n■ TheresourcePrefixNameprovidedfortheprimaryandormediaserverssection\nin environment CR YAML must be unique. If it is not unique, update the\nrespective section in the YAML, delete the environment CR, and apply it again.\n■ Verify the provided IP address and hostname FQDN are already created. Also,\nverify that they correctly used if mentioned in the ipList under the\nnetworkLoadBalancer in the primary and the media servers section in the\nenvironment CR YAML. For more details refer to the load balancer service\nsection in the NetBackup Deployment on Azure Kubernetes Cluster (AKS)\nAdministrator’s Guide.\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide."
    },
    "8439": {
        "code": 8439,
        "desc": "Error in creating the Job <Config-check-job-Name> in the namespace <namespace> for the <Primary/Media Server> <Primary/Media Server Name>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ VerifythattheRBACpermissionsfortheJobarecorrect.RefertotheNetBackup\nDeployment on Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If this issue happens with a fresh deployment, perform the following:\n■ If the issue is the primaryServer CR, perform the following:\nDelete the environment CR using the command: kubectl delete -f\n<environment.yaml>\nRedeploy the environment again using the command: kubectl apply -f\n<environment.yaml>\n■ If the issue is the mediaServer CR, delete the CR by removing the\nmediaServers section in environment.yaml. Save the mediaServers data\nsomewheresothatitcanbeusedatthetimeofredeployment.Applychanges\nusing the command: kubectl apply -f <environment.yaml>\nAfter deleting the mediaServer, update the environment.yaml with the\nmediaServers data that was deleted earlier. Redeploy it again using the\ncommand: kubectl apply -f <environment.yaml>"
    },
    "8440": {
        "code": 8440,
        "desc": "Config-checker failed, or the configuration requirements were not met. NetBackup status codes 1019 NetBackup status codes",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Iftheconfigurationchecksfailed,fixthecheckswithavalidresolution.Forother\nConfig-checkerdetails,refertotheNetBackupDeploymentonAzureKubernetes\nCluster (AKS) Administrator’s Guide."
    },
    "8441": {
        "code": 8441,
        "desc": "Failed to get Config-checker logs.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ ChecktheConfig-checkerpodlogsformoredetailedmessageusingthefollowing\ncommand:\nkubectl logs <config-checker-pod-name> -n <operator-namespace>"
    },
    "8442": {
        "code": 8442,
        "desc": "Config-checker exceeded the time-out limit.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Ensure that the nodes are available to schedule the pod in the cluster with\nrespective labels.\n■ Check events of the config-checker pod using the following command:\nkubectl describe <config-checker-pod-name> -n <operator-namespace>"
    },
    "8443": {
        "code": 8443,
        "desc": "Incorrect username or password in the secret <secret-name> in namespace <namespace>.",
        "first_action": "Ensure that the username and password that is defined",
        "full_action": "Ensure that the username and password that is defined\nin the secret and used in the PrimaryServer CR are same as the secret used in\nthe MediaServer CR."
    },
    "8444": {
        "code": 8444,
        "desc": "Error in creating the role <custom role> in the namespace <namespace>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for role documentation: Using RBAC\nAuthorization | Kubernetes"
    },
    "8445": {
        "code": 8445,
        "desc": "Error in retrieving the role <custom role> in the namespace <namespace>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check if role is available in given namespace using the following command:\nkubectl get role <role-name> -n <namespace>\n■ Check the Kubernetes documentation for role documentation: Using RBAC\nAuthorization | Kubernetes"
    },
    "8446": {
        "code": 8446,
        "desc": "Invalid format for static IP address <IP-address> provided in custom resource specification.",
        "first_action": "Ensure that the format of IP addresses specified in the primaryServers or",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the format of IP addresses specified in the primaryServers or\nmediaServers section in environment CR are valid.\n■ If the format of the IP addresses is not correct, edit the environment CR with\neither of following steps and update the IP address format in the respective\nsections.\n■ Edit environment CR using the following command and save:\nkubectl edit environments.netbackup.veritas.com\n<netbackup-environment-name> -n <environmentCR-namespace>\n■ EdittheenvironmentCRYAMLandapplythechangeusingthefollowing\ncommand:\nkubectl apply -f <environment.yaml>"
    },
    "8453": {
        "code": 8453,
        "desc": "Error in creating the job <Migration-job-Name> in the namespace <namespace> for the <Primary> <Primary>.",
        "first_action": "Review the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Review the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator\n-n<netbackup-operator-namespace>\n■ VerifythattheRBACpermissionsforthejobarecorrect.RefertotheNetBackup\nDeployment for Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ If the issue is with the primary server CR, perform the following:\n■ Delete the environment CR using the command: kubectl delete -f\n<environment.yaml>\n■ Redeploy the environment again using the command: kubectl apply -f\n<environment.yaml>\n■ If this issue occurs during data migration, perform the following:\n■ Check the migration pod logs for details using the following command:\nkubectl logs <catalog-or-log-migration-job-name> -n\n<netbackup-environment-namespace>\n■ If the NetBackup operator pod has one of the following messages:\nError while getting PVC for renaming.\nError while deleting old PVC.\nError while patching old PVC.\nError while renaming logs PVC.\nError while renaming catalog PVC.\nPerform the following steps:\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc <azure-disk- or-files-pvc-name>\n-n <netbackup-environment-namespace>\n■ Delete the old Azure disk or files PVC, and rename the new Azure files\nPVC to the old Azure disk or files PVC name as follows:\nkubectl delete pvc <azure-disk-or-files-pvc-name>\n-n <netbackup-environment-namespace>\nkubectl patch pv <saved_volume_name> --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: <old_pvc_name>\nnamespace: <old_pvc_namespace>\nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: <saved_volume_name>\nstorageClassName: <saved_storage_class_name>\nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 <STS name> -n\n<netbackup-environment-namespace>orreapplytheenvironment.yaml\nfile."
    },
    "8454": {
        "code": 8454,
        "desc": "Migration failed or the configuration requirements were not met.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Delete the new PVC with the Azure files created during failed data migration\nusing the following command:\nkubectl delete pvc <pvc_name> -n <netbackup-environment-namespace>\nReapply the environment.yaml file to reinitiate the data migration. For other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide."
    },
    "8455": {
        "code": 8455,
        "desc": "Failed to get migration logs.",
        "first_action": "Review the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Review the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Review the migration pod logs for more detailed message using the following\ncommand:\nkubectl logs <migration-pod-name> -n <operator-namespace>"
    },
    "8456": {
        "code": 8456,
        "desc": "Migration exceeded the time-out limit. NetBackup status codes 1025 NetBackup status codes",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Ensure that the nodes are available to schedule the pod in the cluster with\nrespective labels.\n■ Review the events of the migration pod using the following command:\nkubectl describe <migration-pod-name> -n <operator-namespace>\n■ Delete the new PVC with the Azure files that the failed data migration creates\nusing the following command:\nkubectl delete pvc <pvc_name> -n <netbackup-environment-namespace>\nReapply the environment.yaml file to reinitiate the data migration. For other\nmigrationdetails,refertotheNetBackupDeploymentforAzureKubernetesCluster\n(AKS) Administrator’s Guide."
    },
    "8459": {
        "code": 8459,
        "desc": "MigrationStatus: Transfer Failed.",
        "first_action": "Check the migration pod logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the migration pod logs for details using the following command:\nkubectl logs <catalog-or-log-migration-job-name> -n\n<netbackup-environment-namespace>\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc <azure-disk- or-files-pvc-name>\n-n <netbackup-environment-namespace>\n■ Delete the old Azure disk or files PVC, and rename the new Azure files PVC to\nthe old Azure disk or files PVC name as follows:\nkubectl delete pvc <azure-disk-or-files-pvc-name>\n-n <netbackup-environment-namespace>\nkubectl patch pv <saved_volume_name> --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: <old_pvc_name>\nnamespace: <old_pvc_namespace>\nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: <saved_volume_name>\nstorageClassName: <saved_storage_class_name>\nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 <STS name> -n\n<netbackup-environment-namespace> or reapply the environment.yaml file."
    },
    "8460": {
        "code": 8460,
        "desc": "MigrationStatus: Verification Failed",
        "first_action": "Check the migration pod logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the migration pod logs for details using the following command:\nkubectl logs <catalog-or-log-migration-job-name> -n\n<netbackup-environment-namespace>\n■ Manually copy or ignore the files or continue with the next steps.\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc <azure-disk- or-files-pvc-name>\n-n <netbackup-environment-namespace>\n■ Delete the old Azure disk or files PVC, and rename the new Azure files PVC to\nthe old Azure disk or files PVC name as follows:\nkubectl delete pvc <azure-disk-or-files-pvc-name>\n-n <netbackup-environment-namespace>\nkubectl patch pv <saved_volume_name> --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: <old_pvc_name>\nnamespace: <old_pvc_namespace>\nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: <saved_volume_name>\nstorageClassName: <saved_storage_class_name>\nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 <STS name> -n\n<netbackup-environment-namespace> or reapply the environment.yaml file."
    },
    "8469": {
        "code": 8469,
        "desc": "Error in renaming the PVC <old-pvc-name> to <new-pvc-name> in the namespace <netbackup-environment-namespace>.",
        "first_action": "Check the NetBackup operator logs for details using the following command:",
        "full_action": "Perform the following as appropriate:\n■ Check the NetBackup operator logs for details using the following command:\nkubectl logs <netbackup-operator-pod-name> netbackup-operator -n\n<netbackup-operator-namespace>\n■ Check if the storageClassName provided in CR is available in the cluster using\nfollowing command:\nkubectl get storageclass\n■ Verify that RBAC permissions are correct. Refer to the NetBackup Deployment\non Azure Kubernetes Cluster (AKS) Administrator’s Guide.\n■ Check the Kubernetes documentation for PVC details.\n■ Manually rename using the following steps:\n■ Save the PVC’s volume name and storage class as follows:\nkubectl describe pvc <azure-disk- or-files-pvc-name>\n-n < netbackup-environment-namespace >\n■ Delete the old Azure disk or files PVC:\nkubectl delete pvc <azure-disk-or-files-pvc-name>\n-n <netbackup-environment-namespace>\nkubectl patch pv <saved_volume_name> --type json\n-p '[{\"op\": \"remove\", \"path\": \"/spec/claimRef\"}]'\n■ Ensure that the PV is available after completing the previous steps.\n■ Create a new Azure files PVC with the old PV as follows:\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\nname: <old_pvc_name>\nnamespace: <old_pvc_namespace>\nspec:\naccessModes:\n- ReadWriteMany\nvolumeName: <saved_volume_name>\nstorageClassName: <saved_storage_class_name>\nresources:\nrequests:\nstorage: 100Gi #previous files size\n■ Enable the probes /opt/veritas/vxapp-manage/nb-health enable.\n■ Set replica count to 1 or reapply environment.yaml file as follows:\nkubectl scale --replicas=1 <STS name> -n\n<netbackup-environment-namespace> or reapply the environment.yaml\nfile."
    },
    "8500": {
        "code": 8500,
        "desc": "Connection with the web service was not established",
        "first_action": "Check that the NetBackup Web Management Console is",
        "full_action": "Check that the NetBackup Web Management Console is\nup and running. If it is not running, start it with the nbwmc -start command."
    },
    "8503": {
        "code": 8503,
        "desc": "CURL has returned an unknown error.",
        "first_action": "For more information about this error code, review the",
        "full_action": "For more information about this error code, review the\nfollowingtechnicalarticle:https://www.veritas.com/support/en_US/article.100034053"
    },
    "8504": {
        "code": 8504,
        "desc": "ThewebservicecertificateisissuedbyanunknownCertificateAuthority.",
        "first_action": "Fetch the CA certificate for the required server and rerun the operation.",
        "full_action": "Do one of the following:\n■ Fetch the CA certificate for the required server and rerun the operation.\n■ Ensure that the master server is enabled to use a NetBackup CA-signed\ncertificate or an external CA-signed certificate, whichever is applicable.\nIf the problem continues, save all of the error log information and contact Cohesity\nTechnical Support."
    },
    "8505": {
        "code": 8505,
        "desc": "Ensurethatthehostclockandthemasterserverclockaresynchronized.",
        "first_action": "Check if the host’s clock is in sync with the specified",
        "full_action": "Check if the host’s clock is in sync with the specified\nserver. Correct the time on the host, if necessary, and rerun the operation. If the\nproblem continues, save all of the error log information and contact Cohesity\nTechnical Support."
    },
    "8506": {
        "code": 8506,
        "desc": "The certificate has expired.",
        "first_action": "Checkifthehost'sclockisinsyncwiththespecifiedserver.",
        "full_action": "Checkifthehost'sclockisinsyncwiththespecifiedserver.\nCorrect the time on the host, if necessary, and rerun the operation. If the problem\ncontinues, save all of the error log information and contact Cohesity Technical\nSupport."
    },
    "8507": {
        "code": 8507,
        "desc": "The certificate could not be verified.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "8508": {
        "code": 8508,
        "desc": "List of trusted Certificate Authorities cannot be fetched. NetBackup status codes 1031 NetBackup status codes",
        "first_action": "Use the nbcertcmd -listCACertDetails command to verify that the CA",
        "full_action": "Do the following, as appropriate:\n■ Use the nbcertcmd -listCACertDetails command to verify that the CA\ncertificate is added to the trust store. Run the nbcertcmd -getCACertificate\n-server master_server_name command to add the required certificate to the\ntrust store.\n■ For RHV:\n■ When the VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED option is\nenabled, you must verify the placement of the certificates and CRLs. Verify\nwhether the RHV virtualization server’s certificates and CRLs are added to\nthe respective ECA configured trust store and the CRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and\nthe trust store file and the CRL files are not corrupted.\n■ Only PEM certificate format for file-based trust store & Windows trust store\nare supported for virtualization servers. P7b or DER format file based trust\nstore is not supported. When this feature is enabled, the certificate ECA\nstore should either be Windows certificate store or file based PEM format\nstore."
    },
    "8509": {
        "code": 8509,
        "desc": "The specified server name was not found in the web service certificate.",
        "first_action": "Rerun the operation using one of the names listed in the",
        "full_action": "Rerun the operation using one of the names listed in the\nserver’s certificate."
    },
    "8510": {
        "code": 8510,
        "desc": "Web server certificate verification failed. NetBackup status codes 1032 NetBackup status codes",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "8511": {
        "code": 8511,
        "desc": "Failed to load the local certificate or the keystore.",
        "first_action": "Ensurethatthecertificateandthekeystoreareaccessible",
        "full_action": "Ensurethatthecertificateandthekeystoreareaccessible\nand that their paths are correct."
    },
    "8512": {
        "code": 8512,
        "desc": "Failed to retrieve the certificate information.",
        "first_action": "Ensure that the specified certificate trust store file is in",
        "full_action": "Ensure that the specified certificate trust store file is in\nthe correct format and the required host certificates are present in the file."
    },
    "8516": {
        "code": 8516,
        "desc": "SSL handshake error has occurred.",
        "first_action": "Ensure that the cipher that is configured on the remote",
        "full_action": "Ensure that the cipher that is configured on the remote\nhost is present in the cipher list on the host. Also ensure that the remote host\nsupports the TLS version being used."
    },
    "8517": {
        "code": 8517,
        "desc": "The specified SSL cipher cannot be used.",
        "first_action": "Ensurethatthecipherthatisconfiguredonthevirtualization",
        "full_action": "Ensurethatthecipherthatisconfiguredonthevirtualization\nserver is present in the cipher list on the host. Also ensure that the specified cipher\nlist is in the correct format."
    },
    "8604": {
        "code": 8604,
        "desc": "Unable to validate the certificate for host.",
        "first_action": "WhentheVIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLEDoptionisenabled,",
        "full_action": "Do the following, as appropriate:\nFor RHV:\n■ WhentheVIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLEDoptionisenabled,\nyou must verify the placement of the certificates and CRLs. Verify whether the\nRHV virtualization server’s certificates and CRLs are added to the respective\nECA configured trust store and the CRL path.\n■ Ensure that the certificates and the CRL files are in the correct format and the\ntrust store file and the CRL files are not corrupted.\n■ Only the PEM certificate format for a file-based trust store and Windows trust\nstore is supported for virtualization servers. P7b or DER format file-based trust\nstore is not supported. When this feature is enabled, the certificate ECA store\nshould either be Windows certificate store or file-based PEM format store.\nFor Sheltered Harbor solution:\n■ Verify that the correct CA certificate file is provided in the Sheltered Harbor\nsolution configuration. You can verify the configuration of the Sheltered Harbor\nsolution using the following command:\nOn UNIX:\n/usr/openv/netbackup/bin/nbshvault --show-config\nOn Windows:\ninstall_path\\NetBackup\\bin\\nbshvault --show-config"
    },
    "8611": {
        "code": 8611,
        "desc": "Failed to open the connection to the remote object that is referred to by the URI.",
        "first_action": "Verify if the host name or the port is valid so that the",
        "full_action": "Verify if the host name or the port is valid so that the\nconnection with the server can be established. Also, make sure if the server is\nreachable."
    },
    "8617": {
        "code": 8617,
        "desc": "The connection continues because insecure communication with hosts is allowed.",
        "first_action": "8.0, so it can communicate securely.",
        "full_action": "UpgradethehosttoaNetBackupversionthatislaterthan\n8.0, so it can communicate securely."
    },
    "8618": {
        "code": 8618,
        "desc": "The connection is dropped because the host ID-to-host name mapping is not approved.",
        "first_action": "The NetBackup administrator must approve all relevant",
        "full_action": "The NetBackup administrator must approve all relevant\nhost ID-to-host name mappings for the given host."
    },
    "8619": {
        "code": 8619,
        "desc": "The connection continues as the host ID-to-host name mapping is automatically approved.",
        "first_action": "No action is required.",
        "full_action": "No action is required."
    },
    "8620": {
        "code": 8620,
        "desc": "The connection is dropped because insecure communication with hosts is not allowed.",
        "first_action": "8.0, so it can communicate securely.",
        "full_action": "UpgradethehosttoaNetBackupversionthatislaterthan\n8.0, so it can communicate securely."
    },
    "8621": {
        "code": 8621,
        "desc": "The connection is dropped because the host appears to be NetBackup 8.0 or earlier.",
        "first_action": "Verify that the peer host was upgraded and then",
        "full_action": "Verify that the peer host was upgraded and then\ndowngraded to a back-level release. If this is the case, then the NetBackup\nadministrator can mark the given host as insecure.\nIf this is not the case, then another host is trying to spoof the peer host. You can\nuse the network tools to find out which host it is and take corrective action."
    },
    "8622": {
        "code": 8622,
        "desc": "TheconnectionisdroppedbecauseaconflictinthehostID-to-hostname mapping is detected.",
        "first_action": "If there are multiple host IDs in your environment that are",
        "full_action": "If there are multiple host IDs in your environment that are\nassociated with the same host name, the NetBackup administrator should verify\nand approve the mapping.\nIf an unknown host tries to spoof the peer host, you can use the available network\ntools to find out which host it is and take corrective action."
    },
    "8623": {
        "code": 8623,
        "desc": "Failed to determine the connection type of the host.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "8625": {
        "code": 8625,
        "desc": "Server is unavailable to process the request. Please try later.",
        "first_action": "Ensure that the NetBackup services are up and running correctly.",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the NetBackup services are up and running correctly.\n■ If the relevant NetBackup services are up and you still receive this error code,\nthenthewebserverisunderaheavyload.Retrytheoperationinafewseconds."
    },
    "8629": {
        "code": 8629,
        "desc": "The NetBackup deduplication web server's SSL certificate hash entry was not found in the NetBackup configuration database.",
        "first_action": "Follow the troubleshooting steps to install the SSL",
        "full_action": "Follow the troubleshooting steps to install the SSL\ncertificates on the NetBackup master server for the NetBackup appliances."
    },
    "8630": {
        "code": 8630,
        "desc": "The NetBackup deduplication web server's SSL certificate record was not found in the NetBackup configuration database.",
        "first_action": "Follow the troubleshooting steps to install the SSL",
        "full_action": "Follow the troubleshooting steps to install the SSL\ncertificates on the NetBackup master server for the NetBackup appliances."
    },
    "8631": {
        "code": 8631,
        "desc": "The current host ID-to-host name mapping conflicts with the NetBackup deduplication web server's host name in the NetBackup configuration database. Please update the NetBackup deduplication web server's SSL certificate record.",
        "first_action": "The current NetBackup host ID-to-hostname mapping is returning a different",
        "full_action": "Do the following, as appropriate:\n■ The current NetBackup host ID-to-hostname mapping is returning a different\nhost name from the host name that is stored in the NetBackup database record\nfortheMSDPSSLcertificates.UpdatetheNetBackupdeduplicationwebserver's\nSSL certificate record.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster server for the NetBackup appliances."
    },
    "8632": {
        "code": 8632,
        "desc": "TheNetBackupdeduplicationwebserver'sSSLcertificatewasnotfound in the trust store for the NetBackup deduplication servers.",
        "first_action": "There is a NetBackup database record for the MSDP SSL certificate, but the",
        "full_action": "Do the following, as appropriate:\n■ There is a NetBackup database record for the MSDP SSL certificate, but the\ncertificate was not found in the trust store. Ensure that there is a certificate in\nthe trust store.\n■ FollowthetroubleshootingstepstoinstalltheSSLcertificatesontheNetBackup\nmaster server for the NetBackup appliances."
    },
    "8633": {
        "code": 8633,
        "desc": "The provided SSL certificate hash did not match the SSL certificate presented by the NetBackup deduplication web server.",
        "first_action": "Verify that the provided SHA-512 SSL certificate hash is",
        "full_action": "Verify that the provided SHA-512 SSL certificate hash is\nfor the certificate that is presented by the web server (nginx) on the NetBackup\nappliance host. This host is known to the master server by the given host ID."
    },
    "8634": {
        "code": 8634,
        "desc": "Duplicate key name.",
        "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore",
        "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey"
    },
    "8635": {
        "code": 8635,
        "desc": "Error storing the key in the keystore.",
        "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore",
        "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey"
    },
    "8636": {
        "code": 8636,
        "desc": "Error loading the keystore.",
        "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore",
        "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey"
    },
    "8638": {
        "code": 8638,
        "desc": "Error working with the encryption cipher.",
        "first_action": "Ensure that the NetBackup Java Runtime Environment",
        "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action."
    },
    "8639": {
        "code": 8639,
        "desc": "Encryption key error.",
        "first_action": "Ensure that the NetBackup Java Runtime Environment",
        "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action."
    },
    "8640": {
        "code": 8640,
        "desc": "Encryption error working with key tag.",
        "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore",
        "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey"
    },
    "8641": {
        "code": 8641,
        "desc": "Encryption manager error.",
        "first_action": "Ensure that the NetBackup Java Runtime Environment",
        "full_action": "Ensure that the NetBackup Java Runtime Environment\n(JRE) security providers are installed. Then, restart the NetBackup Web\nManagement Console (nbwmc or nbwmc.exe) and retry the action."
    },
    "8642": {
        "code": 8642,
        "desc": "Encryption error working with keystore.",
        "first_action": "UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore",
        "full_action": "Verify the ownership and the permissions of the files\n.credential_keystore and credjkskey. If necessary, allow read permission for\nthe user account nbwebsvc. Then, retry the action.\nThe path to .credential_keystore is:\n■ UNIX: /usr/openv/var/global/wsl/credentials/.credential_keystore\n■ Windows:\ninstall_path\\NetBackup\\var\\global\\wsl\\credentials\\.credential_keystore\nThe path to credjskey (the file that holds the password to the credential keystore)\nis:\n■ UNIX: /usr/openv/var/global/credjkskey\n■ Windows: install_path\\NetBackup\\var\\global\\credjkskey"
    },
    "8656": {
        "code": 8656,
        "desc": "The SAML certificate already exists.",
        "first_action": "If you want to re-generate the SAML certificates and",
        "full_action": "If you want to re-generate the SAML certificates and\nkeystore, send the -f option with the nbidpcmd CLI command to forcefully\nre-generate the certificate and keystore."
    },
    "8657": {
        "code": 8657,
        "desc": "The SAML keystore cannot be generated.",
        "first_action": "ForNetBackupissuedSAMLcertificateandkeystore,deleteanyexistingSAML",
        "full_action": "Perform the following actions as appropriate:\n■ ForNetBackupissuedSAMLcertificateandkeystore,deleteanyexistingSAML\ncertificates or keystore and re-generate them.\n■ For external CA issued SAML keystore configuration, review the following as\nappropriate:\n■ IfyouwanttoreusetheNetBackupECAconfiguration,verifythatthemaster\nserverisECAconfiguredandtheECAkeystoreandpasskeyfilesarepresent\nin the following paths:\n■ Windows:\nECA credentials directory path:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\nECA keystore path: install_path\\var\n\\global\\wsl\\credentials\\externalcacreds\\nbwebservice.bcfks\nECA keystore passkey path:\ninstall_path\\var\\global\\wsl\\credentials\\externalcacreds\\jkskey\n■ UNIX:\nECA credentials directory path:\nusr/openv/var/global/wsl/credentials/externalcacreds\nECA keystore path:\nusr/openv/var/global/wsl/credentials/externalcacreds/nbwebservice.bcfks\nECA keystore passkey path:\nusr/openv/var/global/wsl/credentials/externalcacreds/jkskey\n■ IftheexternalCAissuedcertificateandprivatekeyfilesareprovided,verifythat\nthe provided paths are correct and the provided files are in PEM format. Verify\nthat the files are not corrupted."
    },
    "8658": {
        "code": 8658,
        "desc": "The SAML keystore cannot be deleted.",
        "first_action": "NetBackup issued SAML certificate and keystore files:",
        "full_action": "Ensure that user has the required permission to delete\nthe SAML certificate and keystore files present in the following paths:\n■ NetBackup issued SAML certificate and keystore files:\n■ Windows:\nSAML credentials directory path:\ninstall_path\\var\\global\\vxss\\samlcreds\nSAML keystore path:\ninstall_path\\var\\global\\wsl\\credentials\\nbwebsaml.bcfks\nSAML keystore passkey path: install_path\\var\\global\\samljkskey\n■ UNIX:\nSAMLcredentialsdirectorypath:usr/openv/var/global/vxss/samlcreds\nSAML keystore path:\nusr/openv/var/global/wsl/credentials/nbwebsaml.bcfks\nSAML keystore passkey path: usr/openv/var/global/samljkskey\n■ External CA issued SAML keystore:\n■ Windows:\nSAML credentials directory path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\nSAML keystore path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\nbwebsaml.bcfks\nSAML keystore passkey path:\ninstall_path\\var\\global\\wsl\\credentials\\samlecacreds\\jkskey\n■ UNIX:\nSAML credentials directory path:\nusr/openv/var/global/wsl/credentials/samlecacreds\nSAML keystore path:\nusr/openv/var/global/wsl/credentials/samlecacreds/nbwebsaml.bcfks\nSAML keystore passkey path:\nusr/openv/var/global/wsl/credentials/samlecacreds/jkskey"
    },
    "8676": {
        "code": 8676,
        "desc": "The access code is not appropriate.",
        "first_action": "Ensure that you used the appropriate access code and",
        "full_action": "Ensure that you used the appropriate access code and\napproval workflow."
    },
    "8677": {
        "code": 8677,
        "desc": "The access code is expired.",
        "first_action": "Run the bpnbat -login -loginType webUI command",
        "full_action": "Run the bpnbat -login -loginType webUI command\nto receive the new access code."
    },
    "8678": {
        "code": 8678,
        "desc": "The access code request is declined.",
        "first_action": "Contact your Security Administrator.",
        "full_action": "Contact your Security Administrator."
    },
    "8679": {
        "code": 8679,
        "desc": "The access code request is already approved.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "8680": {
        "code": 8680,
        "desc": "The access code request has approval pending.",
        "first_action": "Contact the Security Administrator to verify the access",
        "full_action": "Contact the Security Administrator to verify the access\ncode."
    },
    "8700": {
        "code": 8700,
        "desc": "The host database web service is unavailable due to an internal error.",
        "first_action": "Examine the NetBackup error logs for additional error",
        "full_action": "Examine the NetBackup error logs for additional error\nmessages. Additionally, you can refer to the debug logs for this web service (on\nthe master server) to determine the cause of the error.\nAlternatively, contact Cohesity Technical Support and send the appropriate logs.\nA complete list of required logs and configuration information is available."
    },
    "8701": {
        "code": 8701,
        "desc": "The host does not exist.",
        "first_action": "Thehostthatyouaretryingtoaccessmaynotbeaknown",
        "full_action": "Thehostthatyouaretryingtoaccessmaynotbeaknown\nNetBackup host. Starting with NetBackup 8.0, a host is added automatically when\nit communicates with a NetBackup 8.0 master server.\nAlternatively, contact Cohesity Technical Support and send the appropriate logs.\nA complete list of required logs and configuration information is available."
    },
    "8702": {
        "code": 8702,
        "desc": "The host cannot be created because the host name already exists in the host database. NetBackup status codes 1047 NetBackup status codes",
        "first_action": "Toresolveissuesthatarerelatedtodifferenthostshaving",
        "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\nthe same name or alias, verify the network host name mapping."
    },
    "8703": {
        "code": 8703,
        "desc": "The host cannot be created because the host ID-to-host name mapping already exists in the host database.",
        "first_action": "Toresolveissuesthatarerelatedtodifferenthostshaving",
        "full_action": "Toresolveissuesthatarerelatedtodifferenthostshaving\nthe same name or alias, verify the network host name mapping."
    },
    "8704": {
        "code": 8704,
        "desc": "A conflict occurred while updating the host database. Kindly retry the operation.",
        "first_action": "Iftheproblemcontinues,savealloftheerrorloginformation",
        "full_action": "Iftheproblemcontinues,savealloftheerrorloginformation\nand contact Cohesity Technical Support. A complete list of required logs and\nconfiguration information is available."
    },
    "8705": {
        "code": 8705,
        "desc": "The specified host is not a NetBackup client host and therefore it cannot be decommissioned.",
        "first_action": "Use the information in the technical note that is shown to",
        "full_action": "Use the information in the technical note that is shown to\ndetermine the cause of the error and the appropriate actions to resolve it:\nhttps://www.veritas.com/content/support/en_US/article.100073398"
    },
    "8706": {
        "code": 8706,
        "desc": "The required field is missing from the input request.",
        "first_action": "Enter a valid value for the mandatory fields and try again.",
        "full_action": "Enter a valid value for the mandatory fields and try again."
    },
    "8707": {
        "code": 8707,
        "desc": "The web service cannot update the host ID.",
        "first_action": "Remove the host ID from the input request to complete",
        "full_action": "Remove the host ID from the input request to complete\nthe remaining operations."
    },
    "8708": {
        "code": 8708,
        "desc": "Constraint violations are detected for the given attributes in the input request",
        "first_action": "Enter a valid input for the input parameter and try again.",
        "full_action": "Enter a valid input for the input parameter and try again."
    },
    "8709": {
        "code": 8709,
        "desc": "The destination file or directory already exists.",
        "first_action": "No action required.",
        "full_action": "No action required."
    },
    "8710": {
        "code": 8710,
        "desc": "The file cannot be uploaded because of insufficient disk space on the host.",
        "first_action": "To resolve the issue, create space on the master server",
        "full_action": "To resolve the issue, create space on the master server\nfor var/global paths."
    },
    "8711": {
        "code": 8711,
        "desc": "The folder where the telemetry data needs to be uploaded does not exist.",
        "first_action": "Contact Cohesity Technical Support and send the",
        "full_action": "Contact Cohesity Technical Support and send the\nappropriate logs. A complete list of required logs and configuration information is\navailable."
    },
    "8712": {
        "code": 8712,
        "desc": "Failed to upload the file. NetBackup status codes 1050 NetBackup status codes",
        "first_action": "Contact Cohesity Technical Support and send the",
        "full_action": "Contact Cohesity Technical Support and send the\nappropriate logs. A complete list of required logs and configuration information is\navailable."
    },
    "8713": {
        "code": 8713,
        "desc": "Failed to upload the file. The input file cannot be empty.",
        "first_action": "Verify that the input file for telemetry is correct.",
        "full_action": "Verify that the input file for telemetry is correct."
    },
    "8714": {
        "code": 8714,
        "desc": "The mapping cannot be marked as unshared because it is already shared.",
        "first_action": "Delete the shared mapping entry.",
        "full_action": "Delete the shared mapping entry."
    },
    "8715": {
        "code": 8715,
        "desc": "Aconflictinthemappingisdetected.Thehostnameisalreadymapped with a different host.",
        "first_action": "Mark the conflicting mapping as shared to be able to approve it.",
        "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark the conflicting mapping as shared to be able to approve it.\n■ Delete the conflicting mapping."
    },
    "8716": {
        "code": 8716,
        "desc": "The mapping cannot be added because it is empty.",
        "first_action": "Provide a valid host ID-to-host name mapping.",
        "full_action": "Provide a valid host ID-to-host name mapping."
    },
    "8717": {
        "code": 8717,
        "desc": "The operation failed as one of the input parameters is invalid.",
        "first_action": "Provide a valid input parameter. For more information,",
        "full_action": "Provide a valid input parameter. For more information,\nsee the NetBackup logs."
    },
    "8718": {
        "code": 8718,
        "desc": "The mapping cannot be deleted as this is the primary host name for the host ID.",
        "first_action": "Do not delete the primary host name that is mapped with",
        "full_action": "Do not delete the primary host name that is mapped with\nthe host ID."
    },
    "8719": {
        "code": 8719,
        "desc": "The conflicting mapping cannot be approved because it is not a shared mapping.",
        "first_action": "Mark the conflicting mapping as shared to be able to approve it.",
        "full_action": "Dooneofthefollowingtoresolvetheconflictingmapping:\n■ Mark the conflicting mapping as shared to be able to approve it.\n■ Delete the conflicting mapping."
    },
    "8720": {
        "code": 8720,
        "desc": "The host ID does not exist.",
        "first_action": "ListCertDetails command. If the specified NetBackup host is part of multiple",
        "full_action": "Check the specified host ID by using the nbcertcmd\n-listCertDetails command. If the specified NetBackup host is part of multiple\nNetBackup domains, ensure that you provide the correct host ID that corresponds\nto the specified NetBackup domain."
    },
    "8722": {
        "code": 8722,
        "desc": "The specified name exceeds the maximum allowed length of 1024 characters. Enter a valid name for host ID-to-host name mapping.",
        "first_action": "Ensure that the mapping that you have entered does not",
        "full_action": "Ensure that the mapping that you have entered does not\nexceed 1024 characters."
    },
    "8723": {
        "code": 8723,
        "desc": "The specified comment exceeds the maximum allowed length.",
        "first_action": "Ensurethatthecommentthatyouprovidedoesnotexceed",
        "full_action": "Ensurethatthecommentthatyouprovidedoesnotexceed\n2048 bytes."
    },
    "8724": {
        "code": 8724,
        "desc": "The host ID-to-host name mapping cannot be configured as a shared mapping because it is associated with a single host. NetBackup status codes 1053 NetBackup status codes",
        "first_action": "Ensure that the host ID-to-host name mapping that you",
        "full_action": "Ensure that the host ID-to-host name mapping that you\nwant to add is not configured as shared because the mapping is associated with a\nsingle host."
    },
    "8725": {
        "code": 8725,
        "desc": "The host ID should not be provided in the request along with the subject name.",
        "first_action": "DonotprovidethehostIDwhenyouperformanoperation",
        "full_action": "DonotprovidethehostIDwhenyouperformanoperation\nthat uses a certificate that is issued by an external CA."
    },
    "8727": {
        "code": 8727,
        "desc": "External CA certificates cannot be used for host communication.",
        "first_action": "Use the certificate that is issued by the NetBackup CA for your host.",
        "full_action": "Do one of the following:\n■ Use the certificate that is issued by the NetBackup CA for your host.\n■ Change the setting on the master server to enable the use of certificates that\nare issued by an external CA."
    },
    "8728": {
        "code": 8728,
        "desc": "The certificate operation failed because the NetBackup CA certificates cannot be used for host communication in the domain.",
        "first_action": "Use the certificate that is issued by the external CA for your host.",
        "full_action": "Do one of the following:\n■ Use the certificate that is issued by the external CA for your host.\n■ Change the configuration on the master server to enable the use of NetBackup\ncertificates."
    },
    "8729": {
        "code": 8729,
        "desc": "No external certificates with the specified subject are available.",
        "first_action": "Retrieve the subject name either using the NetBackup",
        "full_action": "Retrieve the subject name either using the NetBackup\nwebUI(externalcertificatelistview)orthenbhostmgmtcommand.Usethatsubject\nname to perform the delete or the reset operation."
    },
    "8730": {
        "code": 8730,
        "desc": "External certificate with the specified subject is already available.",
        "first_action": "Use the nbcertcmd -deleteECACertEntry command to delete the existing",
        "full_action": "If the subject name is associated with a different host, try\none of the following actions:\n■ Use the nbcertcmd -deleteECACertEntry command to delete the existing\nentry from the database.\n■ Use a different subject name."
    },
    "8731": {
        "code": 8731,
        "desc": "The subject name of the certificate is not in the valid format.",
        "first_action": "If you want to provide the subject name using the OpenSSL or the vxsslcmd",
        "full_action": "Do one of the following:\n■ If you want to provide the subject name using the OpenSSL or the vxsslcmd\nAPI, ensure that it is in the RFC 2253 format. Use the following command:\n■ Install_Path/goodies/vxsslcmd x509 -noout -in input certificate\nfile -subject -nameopt RFC2253 or openssl x509 -noout -in input\ncertificate file -subject -nameopt RFC2253\n■ RetrievethesubjectnameeitherusingtheNetBackupwebUI(externalcertificate\nlist view) or the nbhostmgmt command."
    },
    "8732": {
        "code": 8732,
        "desc": "An entry for the specified subject name that is associated with a host ID already exists in the NetBackup database.",
        "first_action": "Update the existing subject name to host ID association using the",
        "full_action": "Do one of the following:\n■ Update the existing subject name to host ID association using the\nnetbackup/security/external-certificates API.\n■ Delete the existing subject name to host ID entry from the database using the\nnbcertcmd -deleteECACertEntrycommand(orthroughtheAPI).Thencreate\na new entry using the createECACertEntry command.\n■ Use a new subject name."
    },
    "8733": {
        "code": 8733,
        "desc": "An entry for the specified host ID associated with the subject name already exists in the NetBackup database.",
        "first_action": "Update the existing subject name to host ID association using the",
        "full_action": "Do one of the following:\n■ Update the existing subject name to host ID association using the\nnetbackup/security/external-certificates API.\n■ RetrievetheconfiguredsubjectnameforthespecifiedhostID.Deletetheexisting\nsubject name to host ID entry from the database using the nbcertcmd\n-deleteECACertEntrycommand(orthroughtheAPI).Thencreateanewentry\nusing the createECACertEntry command."
    },
    "8739": {
        "code": 8739,
        "desc": "ThehostID-to-hostnamemappingcannotbeadded.Automaticmapping is disabled for NAT clients.",
        "first_action": "AddtherequiredhostID-to-hostnamemappingusingthe",
        "full_action": "AddtherequiredhostID-to-hostnamemappingusingthe\nNetBackup web UI or NetBackup Administration Console. Alternatively, use the\nnbhostmgmt command to add the required name mapping."
    },
    "8740": {
        "code": 8740,
        "desc": "Failed to fetch the master server information.",
        "first_action": "The appropriate license key is used.",
        "full_action": "Ensure the following:\n■ The appropriate license key is used.\n■ The NBSL service is up and running."
    },
    "8743": {
        "code": 8743,
        "desc": "The specified host is already decommissioned.",
        "first_action": "This request is invalid. The host was already",
        "full_action": "This request is invalid. The host was already\ndecommissioned and cannot be decommissioned again."
    },
    "8744": {
        "code": 8744,
        "desc": "Primary servers cannot be decommissioned. NetBackup status codes 1057 NetBackup status codes",
        "first_action": "This request is invalid. The specified host is a primary",
        "full_action": "This request is invalid. The specified host is a primary\nserver and primary servers cannot be decommissioned."
    },
    "8745": {
        "code": 8745,
        "desc": "The specified host is an unknown server.",
        "first_action": "This request is invalid. The specified host is not known to",
        "full_action": "This request is invalid. The specified host is not known to\nNetBackup and cannot be decommissioned."
    },
    "8747": {
        "code": 8747,
        "desc": "Protected hosts cannot be decommissioned.",
        "first_action": "Removethehostfromtheassociatedpoliciesorprotection",
        "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans.Determineifthehostispartofanybackuphostpoolthatisusedinthepolicy\nor the protection plan. If it is present, remove the given host from the backup host\npool and then decommission the host. Alternatively, use the force option to\ndecommission the host."
    },
    "8748": {
        "code": 8748,
        "desc": "OneormoreimagesforthespecifiedhostexistintheNetBackupcatalog.",
        "first_action": "Remove the images present for given host. You can use",
        "full_action": "Remove the images present for given host. You can use\nthe force option to ignore this failure."
    },
    "8749": {
        "code": 8749,
        "desc": "Policies, protection plans, or images are associated with the specified host.",
        "first_action": "Removethehostfromtheassociatedpoliciesorprotection",
        "full_action": "Removethehostfromtheassociatedpoliciesorprotection\nplans,andexpireanyassociatedimages,thendecommissionthehost.Alternatively,\nuse the force option to decommission the host.\nRemove the host from the associated policies or protection plans. Determine if the\ngiven host is part of any backup host pool that is used in the policy or the protection\nplan. If it is present, remove the host from the backup host pool and then\ndecommissionthehost.Expireanyassociatedimagesandthendecommissionthe\nhost. Alternatively, use the force option to decommission the host."
    },
    "8753": {
        "code": 8753,
        "desc": "The certificate enrollment failed. The host name should be part of the certificate.",
        "first_action": "Ensure that the host name is part of the subject name of the certificate.",
        "full_action": "Do one of the following:\n■ Ensure that the host name is part of the subject name of the certificate.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackupdatabase.Usethenbcertcmd -createECACertEntryandnbcertcmd\n-deleteECACertEntry commands. For more information on the commands,\nrefer to the NetBackup Commands Reference Guide."
    },
    "8754": {
        "code": 8754,
        "desc": "The certificate enrollment failed. The host name should be a primary name.",
        "first_action": "Use the primary name of the host during certificate enrollment.",
        "full_action": "Do one of the following:\n■ Use the primary name of the host during certificate enrollment.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Use the nbcertcmd -deleteECACertEntry then the\nnbcertcmd -createECACertEntry commands. For more information on the\ncommands, refer to the NetBackup Commands Reference Guide."
    },
    "8755": {
        "code": 8755,
        "desc": "The certificate enrollment failed. The host name should be part of the certificate and it should be a primary name.",
        "first_action": "Use the primary name of the host during certificate enrollment and ensure that",
        "full_action": "Do one of the following:\n■ Use the primary name of the host during certificate enrollment and ensure that\nthe host name is part of the subject alternate name of the certificate.\n■ Add or update (delete and then add) the subject name of the certificate in the\nNetBackup database. Use the nbcertcmd -deleteECACertEntry then the\nnbcertcmd -createECACertEntry commands. For more information on the\ncommands, refer to the NetBackup Commands Reference Guide."
    },
    "8756": {
        "code": 8756,
        "desc": "The certificate enrollment failed. The host name is already enrolled with a certificate with a different subject name.",
        "first_action": "1. Runthenbcertcmd -deleteECACertEntrycommandtodeletetheassociation",
        "full_action": "Add or update (delete and then add) the subject name of\nthe certificate in the NetBackup database. Do the following:\n1. Runthenbcertcmd -deleteECACertEntrycommandtodeletetheassociation\nof the existing host with the certificate.\n2. Run the nbcertcmd -createECACertEntry command to associate the new\ncertificate with the existing host.\nFor more information on the commands, refer to the NetBackup Commands\nReference Guide."
    },
    "8757": {
        "code": 8757,
        "desc": "Failed to retrieve the Certificate Authority usage information of the NetBackup web server.",
        "first_action": "Try retrieving the Certificate Authority usage information",
        "full_action": "Try retrieving the Certificate Authority usage information\nof the web server again."
    },
    "8759": {
        "code": 8759,
        "desc": "The certificate to be used for enrollment is not yet valid.",
        "first_action": "VerifythetimethatisspecifiedforthenotBeforeparameter",
        "full_action": "VerifythetimethatisspecifiedforthenotBeforeparameter\ninthecertificate.Ifthetimeisinthefuture,tryenrollingadifferentexternalcertificate\nthat is valid."
    },
    "8760": {
        "code": 8760,
        "desc": "The certificate to be used for enrollment is expired.",
        "first_action": "VerifythetimethatisspecifiedforthenotAfterparameter",
        "full_action": "VerifythetimethatisspecifiedforthenotAfterparameter\nin the certificate. If the time is in the past, try enrolling a different external certificate\nthat is valid."
    },
    "8761": {
        "code": 8761,
        "desc": "The certificate enrollment failed. The certificate is revoked.",
        "first_action": "Contact your security administrator to get a new external",
        "full_action": "Contact your security administrator to get a new external\ncertificate that is valid. Try enrolling the new external certificate."
    },
    "8762": {
        "code": 8762,
        "desc": "Theprivatekeyoftheexternalcertificateisencrypted,butthepassphrase is blank.",
        "first_action": "Ensure that the passphrase is defined on the first line of",
        "full_action": "Ensure that the passphrase is defined on the first line of\nthe ECA_KEY_PASSPHRASEFILE configuration option."
    },
    "8763": {
        "code": 8763,
        "desc": "Thecertificateenrollmentfailed.Anotherhostwiththesameshortname exists in the NetBackup database.",
        "first_action": "Provide the correct CLIENT_NAME of the host. Use the nbhostmgmt -list",
        "full_action": "Try one of the following actions:\n■ Provide the correct CLIENT_NAME of the host. Use the nbhostmgmt -list\ncommand to get the client name and retry the operation.\n■ If the host for which an external certificate is to be enrolled and the host that is\navailableonthemasterserveraredifferentthenusethenbhostmgmt -addhost\ncommand."
    },
    "8764": {
        "code": 8764,
        "desc": "The certificate or the certificate path is not valid.",
        "first_action": "Ensure that the certificate and the certificate file path are",
        "full_action": "Ensure that the certificate and the certificate file path are\nvalid."
    },
    "8765": {
        "code": 8765,
        "desc": "The host does not have any security certificate configured with respect to this master server.",
        "first_action": "Run the following command: nbcertcmd - getCertificate",
        "full_action": "Carry out the following steps:\n1 Generate and deploy a NetBackup certificate (or a host ID-based certificate).\n■ Run the following command: nbcertcmd - getCertificate\n2 Enroll an external certificate.\n■ Run the following command: nbcertcmd - enrollCertificate\nFor more details on the certificate deployment and enrollment process, refer to the\nNetBackup Security and Encryption Guide.\nFor more details on the commands, refer to the NetBackup Commands Guide."
    },
    "8766": {
        "code": 8766,
        "desc": "The certificate enrollment failed. The common name (CN) is not present in the certificate.",
        "first_action": "Add the common name of the host in the certificate.",
        "full_action": "Do one of the following:\n■ Add the common name of the host in the certificate.\n■ Add the host name in the certificate’s subject alternative name.\n■ Carry out the following steps in the given order:\n■ Addthehostinthehostdatabaseusingthenbhostmgmt -addhostcommand.\n■ AddthesubjectalternativenameofthecertificateintheNetBackupdatabase\nusing the nbcertcmd -createECACertEntry command."
    },
    "8767": {
        "code": 8767,
        "desc": "Thecertificateenrollmentfailed.Theissuerinthecertificateandtheone that you have provided do not match.",
        "first_action": "Ensurethatyouprovidethecorrectcertificateissuername.",
        "full_action": "Ensurethatyouprovidethecorrectcertificateissuername."
    },
    "8768": {
        "code": 8768,
        "desc": "The specified certificate store does not exist on the local machine.",
        "first_action": "The certificate store name is specified correctly.",
        "full_action": "Ensure the following:\n■ The certificate store name is specified correctly.\n■ The specified certificate store is part of the HKEY_LOCAL_MACHINE certificate\nstore."
    },
    "8769": {
        "code": 8769,
        "desc": "Certificate path is invalid. If your store name, issuer, or subject contains any special characters, ensure that they are included in double quotes.",
        "first_action": "1. Ensurethatthecertificatestorenameorcertificatesubjectnamearenotempty.",
        "full_action": "Perform the following steps:\n1. Ensurethatthecertificatestorenameorcertificatesubjectnamearenotempty.\n2. If the certificate issuer name is blank, ensure that your certificate path looks\nlike the following: <store name>\\\\<subject>.\n3. If the store name, issuer name, or subject name contains special characters,\nuse double quotes to specify these parameters."
    },
    "8770": {
        "code": 8770,
        "desc": "The certificate cannot be found at the specified path.",
        "first_action": "Ensure that the specified certificate path is correct and",
        "full_action": "Ensure that the specified certificate path is correct and\nthe certificate is present at the given path."
    },
    "8771": {
        "code": 8771,
        "desc": "The certificate with the given subject name cannot be found.",
        "first_action": "1. Ensure that the certificate subject name is specified correctly.",
        "full_action": "Perform the following steps:\n1. Ensure that the certificate subject name is specified correctly.\n2. Ensure that the certificate store contains the specified certificate.\n3. If the host name is used as the subject name, ensure that the subject name is\nmentioned as $hostname."
    },
    "8772": {
        "code": 8772,
        "desc": "The Windows certificate store cannot be opened.",
        "first_action": "The certificate store name is specified correctly.",
        "full_action": "Ensure the following:\n■ The certificate store name is specified correctly.\n■ The specified certificate store is part of the Local Machine certificate store."
    },
    "8773": {
        "code": 8773,
        "desc": "The certificate is not valid as the certificate validity period starts in the future.",
        "first_action": "Reviewthecertificatedate.Useacertificatethatiscurrently",
        "full_action": "Reviewthecertificatedate.Useacertificatethatiscurrently\nvalid."
    },
    "8774": {
        "code": 8774,
        "desc": "The Windows certificate store cannot be closed.",
        "first_action": "Wait for a few minutes and try enrolling the certificate",
        "full_action": "Wait for a few minutes and try enrolling the certificate\nagain."
    },
    "8775": {
        "code": 8775,
        "desc": "The host name cannot be retrieved. NetBackup status codes 1066 NetBackup status codes",
        "first_action": "Verifythatthehostnameissetandthenretrytheoperation.",
        "full_action": "Verifythatthehostnameissetandthenretrytheoperation."
    },
    "8776": {
        "code": 8776,
        "desc": "NetBackup does not support the algorithm used, see logs for more information regarding the algorithm.",
        "first_action": "Use a certificate that is encrypted using an algorithm that",
        "full_action": "Use a certificate that is encrypted using an algorithm that\nNetBackup supports. Refer to the NetBackup Security and Encryption Guide."
    },
    "8777": {
        "code": 8777,
        "desc": "The certificate cannot be enrolled because of an unknown error.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "8778": {
        "code": 8778,
        "desc": "Failed to get the specified certificate from Windows certificate store.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "8779": {
        "code": 8779,
        "desc": "ECA health check failed.",
        "first_action": "Causes:",
        "full_action": "Each failed validation is associated with a validation ID.\nFor each failure, there may be a specific reason and you can carry out certain\ntroubleshootingsteps.ReviewthefollowinglistofvalidationsfortheecaHealthCheck\ncommand.\nValidation ID: USER_INPUT_CERT_PATH_VALIDATION\n■ Causes:\n■ The certificate path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the certificate path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_CERTIFICATES_VALIDATION\n■ Causes:\n■ Error in reading the certificate file.\n■ Recommended actions:\n■ Ensure that the certificate file contains a certificate.\n■ Ensure that the certificate file format is one that NetBackup supports. The\nsupported certificate formats are PEM, P7BPEM, P7BDER.\nValidation ID: USER_INPUT_PRIVATE_KEY_PATH_VALIDATION\n■ Causes:\n■ The private key path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the private key path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_PRIVATE_KEY_READ_VALIDATION\n■ Causes:\n■ Error in reading the private key: File read failed.\n■ Error in reading the private key: The private key of the external certificate is\nencrypted, but the passphrase is not provided.\n■ Error in reading the private key: The private key of the external certificate is\nencrypted, but the passphrase is blank.\n■ Recommended actions:\n■ Ensure that the private key format or key algorithms format is one of those\nsupported by NetBackup. The supported key formats are PEM and DER.\n■ If the private key is encrypted, ensure that the ECA_KEY_PASSPHRASEFILE or\n-passphraseFile with its value as passphrase file path location is given.\n■ If the private key is encrypted and the passphrase file is given, ensure that\nthe passphrase file is not empty and the passphrase in it is correct.\nValidation ID: USER_INPUT_TRUST_STORE_PATH_VALIDATION\n■ Causes:\n■ The trust store path is empty.\n■ The file at the specified path filename cannot be accessed.\n■ Recommended actions:\n■ Ensure that the trust store path is not blank.\n■ Ensure that the file has the Read permissions for the corresponding user.\nValidation ID: USER_INPUT_TRUST_STORE_VALIDATION\n■ Causes:\n■ Error in reading the trust store path.\n■ Recommended actions:\n■ Ensure that the trust store certificate file contains a trusted certificate.\n■ Ensure that the certificate file format is one that NetBackup supports. The\nsupported certificate formats are PEM, P7BPEM, P7BDER.\nValidation ID: CERTIFICATES_KEYS_ACCESS_VALIDATION\n■ Causes:\n■ Windows:NetBackupservicesarenotabletoreadthecertificate,truststore,\nor private key.\n■ UNIX: NetBackup service user is not able to read the certificate, trust store,\nor private key.\n■ Recommended actions:\n■ Windows:\n■ EnsurethattheLocalServiceisnotdeniedaccesstothecertificate,trust\nstore, or private key.\n■ Ensure that the NetBackup services have access to the certificate, trust\nstore, or private key.\n■ Run the icacls command to ensure the NetBackup services or Local\nService have read permissions. Example:\nicacls <file>\n...\n<file> NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note only applicable to Windows systems.\nThis check is not applicable for group members if the Local Service and\nor NetBackup service are members of a group that is given the\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX:\n■ Ensure that the NetBackup service user has access to the certificates,\nthe private key, and the passphrase file.\nValidation ID: LEAF_CERTIFICATE_ENHANCED_KEY_USAGE_VALIDATION\n■ Causes:\n■ The required extended key usages are not available in the given certificate.\n■ Recommended actions:\n■ Execute the following command:\n■ For Windows:\n■ install_path\\bin\\goodies\\vxsslcmd.exe x509 -text -in\nend_entity_certificate\n■ For UNIX:\n■ install_path/bin/goodies/vxsslcmdx509-text-inend_entity_certificate\n■ If the certificate has a X509v3 Key Usage extension present, it must include\nthe following key usage purposes:\n■ Forthewebservercertificate:AtleastoneoftheDigitalSignatureorKey\nEncipherment should be present.\n■ For a NetBackup host certificate: Digital Signature purpose should be\npresent. Key Encipherment may or may not be present.\n■ For a certificate that is used for both web server and NetBackup host:\nDigital Signature purpose should be present. Key Encipherment may or\nmay not be present.\n■ The certificate may have other key usage purposes listed in addition to\nthe purposes specified here. These additional purposes are ignored.\n■ The X509v3 Key Usage extension may be either critical or non-critical.\n■ A certificate without a X509v3 Key Usage extension is also usable with\nNetBackup.\n■ If the certificate has a X509v3 Extended Key Usage extension present, it\nmust include the following key usage purposes:\n■ For the web server certificate: TLS Web Server Authentication.\n■ For a NetBackup host certificate: TLS Web Server Authentication and\nTLS Web Client Authentication.\n■ For a certificate that is used for both web server and NetBackup host:\nTLS Web Server Authentication and TLS Web Client Authentication.\n■ The certificate may have other key usage purposes listed in addition to\nthe purposes specified here. These additional purposes are ignored.\n■ The X509v3 Extended Key Usage extension may be either critical or\nnon-critical.\n■ AcertificatewithoutaX509v3ExtendedKeyUsageextensionisalsousable\nwith NetBackup.\n■ If the certificate doesn’t meet the requirements that are listed in this\nRecommend actions section, contact your certificate provider to obtain a\nnew certificate.\nValidation ID: CERTIFICATE_SUBJECT_DN_LENGTH_VALIDATION\n■ Causes:\n■ The subject name contains more than 255 characters\n■ Recommended actions:\n■ A subject name with a length greater that 255 characters is not supported.\nContact your external certificate provider.\nValidation ID: CERTIFICATE_SAN_HOSTNAME_VALIDATION\n■ Causes:\n■ The Subject Alternative Name field in the certificate is not empty and the\nhostname is not present in the field.\n■ Recommended actions:\n■ If the certificate Subject Alternative Name is non-empty, ensure that it has\nhost name present in it.\n■ To view Subject Alternative Name run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 SubjectAlternativeName: DNS:host FQDN DNS:host name\nValidation ID: PRIVATE_KEY_VALIDATION\n■ Causes:\n■ The private key does not match the certificate.\n■ Recommended actions:\n■ Ensure that the certificate and its corresponding private key are given.\nValidation ID: CERTIFICATE_SUBJECT_DN_ASCII_VALIDATION\n■ Causes:\n■ A non-ASCII character was found in the Subject: subject name of the\ncertificate.\n■ Recommended actions:\n■ A certificate subject with characters other than ascii 7-bit characters is not\nsupported. Contact your external certificate provider.\nValidation ID: CERTIFICATE_CHAIN_VALIDATION_AGAINST_TRUST_STORE\n■ Causes:\n■ Certificatechainverificationcanfailduetomanyreasons.Theonlycommon\nsentence that is displayed is The certificate chain verification\nfailed. The rest of the error is displayed with whatever openssl returns.\n■ Recommended actions:\n■ Ensure that certificate with given subject name is present in the provided\ntrust store.\n■ Review the openssl error and rectify per the error text.\nValidation ID: CERTIFICATE_CN_EMPTINESS_VALIDATION\n■ Causes:\n■ The Common Name field in the certificate is empty.\n■ Recommended actions:\n■ Ensure that certificate common name is not empty. Contact your external\ncertificate provider.\n■ Run the following command to verify:\n■ vxsslcmd x509 -subject -in certificate_file\n■ Verify that the value of CN in the subject is not empty.\nValidation ID: CERTIFICATES_ORDER\n■ Causes:\n■ The signature of the certificate subject name cannot be verified with the\npublic key of the current certificate subject name.\n■ Recommended actions:\n■ If you use a PEM-formatted certificate, ensure that in the certificate file, the\nleaf certificate is present first followed by its issuer, followed by the issuer\nof the leaf’s issuer and so on.\nValidation ID: CERTIFICATE_CHAIN_EXPIRY_VALIDATION\n■ Causes:\n■ The certificate with the subject subject name is expired.\n■ Recommended actions:\n■ Renew your certificate or use a certificate that is currently valid.\n■ To ensure, run the following command:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate is not valid\nnotAfter=date after which certificate is not valid\nValidation ID: CERTIFICATE_CHAIN_CURRENT_ACTIVE_VALIDATION\n■ Causes:\n■ The certificate with the subject subject name is not yet active.\n■ Recommended actions:\n■ Use a certificate that is currently valid.\n■ To ensure, run the following command:\n■ vxsslcmd x509 -dates -in certificate_file\nOutput:\nnotBefore=date before which certificate is not valid\nnotAfter=date after which certificate is not valid\nValidation ID: WINDOWS_CERTIFICATE_STORE_PRIVATE_KEY_VALIDATION\n■ Severity: Fail or Warn\n■ Causes:\n■ A warning is given when MANAGE_WIN_CERT_STORE_PRIVATE_KEY is set to\nDisabled in the NetBackup configuration and the NetBackup services are\npermitted to access the private key.\n■ The check fails when MANAGE_WIN_CERT_STORE_PRIVATE_KEY is set to\nDisabled in the NetBackup configuration and the NetBackup services are\nnot permitted to access the private key.\n■ The check fails when the Cryptographic Service Provider (CSP) or Key\nStorage Provider (KSP) do not support the security descriptors.\n■ Recommended actions:\n■ SetMANAGE_WIN_CERT_STORE_PRIVATE_KEYtoAutomaticsothatNetBackup\nprivileged services can update the read permissions for private key for\nNetBackup non-privileged services.\n■ If the validation fails, give NetBackup services permissions to access the\nprivate key. You can run the command: nbcertcmd\n-setwincertprivkeypermissions -force\n■ If the validation returns a warning, ensure that the NetBackup services have\nreadpermissionstoaccesstheprivatekey.Thepermissionsareresetduring\ncertain operations like certificate renewal or disaster recovery.\n■ If the validation fails because the Cryptographic Service Provider (CSP) or\nKey Storage Provider (KSP) do not support the security descriptors, then\nuse a provider that supports the security descriptors.\nRefer to the section Limitations of Windows Certificate Store support when\nNetBackup services are running in Local Service account context in the\nNetBackup Security and Encryption Guide for more details.\nValidation ID: USER_INPUT_WIN_CERT_PATH_VALIDATION\n■ Causes:\n■ The certificate with the given subject name cannot be found.\n■ Recommended actions:\n■ EnsurethattheWindowscertificatestorecertificatepathisprovidedcorrectly\nand the certificate exists in the given certificate store. Refer to the External\nCAsupportinNetBackupfromtheNetBackupSecurityandEncryptionGuide.\nValidation ID: CERTIFICATE_SAN_CN_HOSTNAME_VALIDATION\n■ Causes:\n■ The Subject Alternative Name field in the certificate is empty and the host\nname hostname is not present in the Common Name field.\n■ Recommended actions:\n■ IfthecertificateSubjectAlternativeNameisempty,ensurethattheCommon\nName field has a host name present in it.\n■ To view the Subject Alternative Name, run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\n■ To view Common Name, run the following command:\n■ vxsslcmd x509 -text -in end_entity_certificate_file\n■ X509v3 Subject Alternative Name: DNS: host FQDN DNS:host name\nValidation ID: USER_INPUT_WIN_CERT_VALIDATION\n■ Causes:\n■ Cannot open the provided certificate store.\n■ Issuer of the certificate is not found.\n■ Certificate with the provided subject is not found.\n■ The host name of the computer cannot be fetched. [Used with special\nkeyword $hostname]\n■ Certificate is not valid yet.\n■ Certificate is expired.\n■ Private key is not found for the certificate.\n■ The required purposes (Client Authentication & Server Authentication) are\nnot present in the certificate.\n■ Recommendedactions:(ThefollowingactionsshouldbeperformedinWindows\ncertificate store)\n■ Ensure that certificate path is in correct format:\nstore-name\\issuer-name\\subject\n■ Checkthecertificate’sValid fromfield.Thevalue(date)shouldbeincurrent\ndate range.\n■ Check the certificate’s Valid to field. The value (date) should be in current\ndate range.\n■ Ensure that the private key is present that corresponds to the end entity\ncertificate.\n■ EnsurethattheEnhanced Key UsagefieldcontainsServer Authentication\n(1.3.6.1.5.5.7.3.1)andClient Authentication (1.3.6.1.5.5.7.3.2).\nAll purpose is also accepted.\nValidation ID: USER_INPUT_CRL_PATH_VALIDATION\n■ Causes:\n■ The CRL path is not accessible.\n■ The CRL path is empty.\n■ The CRL path contains only 0-KB files.\n■ Recommended actions:\n■ Ensure that the CRL path is correct and not empty.\nValidation ID: USER_INPUT_CRL_PATH_CONTAINS_CRLS\n■ Causes:\n■ The CRL path does not contain any CRL files.\n■ Recommended actions:\n■ Ensure that the CRL path is correct and not empty.\nValidation ID: CRL_FILES_ACCESS_VALIDATION\n■ Causes:\n■ Windows: NetBackup services are not able to read the CRL files.\n■ UNIX: NetBackup service user is not able to read the CRL files.\n■ Recommended actions:\n■ Windows:\n■ Ensure that the Local Service is not denied access to the CRL files.\n■ Ensure that the NetBackup services have access to the CRL files.\n■ Run the icacls command to ensure the NetBackup services or Local\nService have read permission. Example:\nicacls <file>\n...\n<file> NT SERVICE\\NetBackup Audit Manager:(R)\n...\nNote: This note only applicable to Windows systems.\nThis check is not applicable for group members if the Local Service and\nor NetBackup service are members of a group that is given the\npermissionsdenyandorallow.Thevalidationcheckdoesnotdetecttheir\npermissions.\n■ UNIX: Ensure that the service user has access to the CRL files.\nValidation ID: CRL_CDP_URL_VALIDATION\n■ Causes:\n■ The CRL Distribution Point in the certificate does not contain valid URLs.\nNetBackup supports only HTTP or HTTPS URLs.\n■ Recommended actions:\n■ Ensure that the CRL Distribution Point contains valid URLs.\nValidation ID: ALL_CRLS_READABLE\n■ Causes:\n■ CRL files available are not readable or invalid CRLs.\n■ Recommended actions:\n■ Ensure that valid CRLs are available in the CRL path."
    },
    "8787": {
        "code": 8787,
        "desc": "ThespecifiedprivatekeyoftheexternalcertificateisnotFIPS-compliant.",
        "first_action": "Ensure that the private key for the external certificate is",
        "full_action": "Ensure that the private key for the external certificate is\ngenerated using FIPS-compliant algorithms."
    },
    "8788": {
        "code": 8788,
        "desc": "The Cryptographic Service Provider or key storage provider does not support security descriptors.",
        "first_action": "Use a Cryptographic Service Provider or key storage",
        "full_action": "Use a Cryptographic Service Provider or key storage\nprovider that supports security descriptors. Alternatively, use the Local System or\nan administrator account to run the NetBackup non-privileged services.\nFor more information about changing the service user, see the NetBackup Security\nand Encryption Guide."
    },
    "8789": {
        "code": 8789,
        "desc": "Failed to acquire private key corresponding to certificate in Windows certificate store.",
        "first_action": "1. Use a certificate that has a private key that is associated with it.",
        "full_action": "Perform the following:\n1. Use a certificate that has a private key that is associated with it.\n2. Check if the user has permissions to read the private key."
    },
    "8790": {
        "code": 8790,
        "desc": "Failed to update security descriptor of private key corresponding to certificate in Windows certificate store.",
        "first_action": "1. Checkiftheuserhaspermissionstomodifythesecuritydescriptoroftheprivate",
        "full_action": "Perform the following:\n1. Checkiftheuserhaspermissionstomodifythesecuritydescriptoroftheprivate\nkey.\n2. Check if the Cryptographic Service Provider or key storage provider supports\nsecurity descriptors. Use a provider that supports security descriptors or the\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nFor more information about changing the service user, see the NetBackup\nSecurity and Encryption Guide."
    },
    "8791": {
        "code": 8791,
        "desc": "Failed to read the security descriptor of private key corresponding to certificate in Windows certificate store.",
        "first_action": "1. Check if the user reading the security descriptor of the private key has",
        "full_action": "Perform the following:\n1. Check if the user reading the security descriptor of the private key has\npermissions to read it.\n2. Check if the Cryptographic Service Provider or key storage provider supports\nsecurity descriptors. Use a provider that supports security descriptors or the\nLocalSystemoranadministratoraccounttoruntheNetBackupnon-privileged\nservices.\nFor more information about changing the service user, see the NetBackup\nSecurity and Encryption Guide."
    },
    "8792": {
        "code": 8792,
        "desc": "FailedtosettheattributesoftheprivatekeyorcertificateinsideWindows certificate store.",
        "first_action": "1. Check if the certificate is valid.",
        "full_action": "Perform the following:\n1. Check if the certificate is valid.\n2. Check if the user has permissions to write the attributes of private key."
    },
    "8793": {
        "code": 8793,
        "desc": "Failed to read the attributes from the private key or certificate inside Windows certificate store.",
        "first_action": "1. Check if the certificate is valid.",
        "full_action": "Perform the following:\n1. Check if the certificate is valid.\n2. Check if the user has permissions to read the attributes of private key."
    },
    "8794": {
        "code": 8794,
        "desc": "NetBackup is not enabled to manage the private key corresponding to certificate in the Windows certificate store. Check NetBackup configuration.",
        "first_action": "Change the value of the",
        "full_action": "Change the value of the\nMANAGE_WIN_CERT_STORE_PRIVATE_KEY in the NetBackup configuration to\nAutomatic."
    },
    "8798": {
        "code": 8798,
        "desc": "The certificate of the host cannot be validated because FIPS mode is enabled.",
        "first_action": "Providerclass and -providerpath are needed as the trust store is a BCFKS",
        "full_action": "To overcome this problem, a temporary FIPS-compliant\ntrust store has been introduced in NetBackup 10.0 which is located at:\ninstall_path/var/global/wsl/credentials/cacerts.bcfks\nWhen a NetBackup primary server is running in FIPS mode, administrators now\nneed to ensure that this trust store has the remote entity’s CA certificate already\navailable in it. This check must be done before the APIs are called to fetch the CA\ncertificate of remote entity. NetBackup Web Services API workflows use this trust\nstore to verify the identity of the remote entity NetBackup communicates with.\nContact your NetBackup Administrator to populate the trust store with the target\nserver’s CA certificate for validating the server’s authenticity.\nNote: The following steps need to be performed on the NetBackup primary server\nwhich is configured to run in FIPS mode.\nThe keytool command that is available on the primary server, can be used to\nimport the CA certificates into the trust store\ninstall_path/var/global/wsl/credentials/cacerts.bcfks. The options\n-providerclass and -providerpath are needed as the trust store is a BCFKS\nformat trust store, the only fully FIPS-compliant store format.\nThe remote entity’s CA certificate must be available in a file in a PEM encoded\nformat. The CA certificate must be copied over to the NetBackup primary server\nrunning in FIPS mode.\nThe steps to export the remote entity’s CA certificate into a PEM format file can\nvary. One of the ways to get the information is by using the following keytool\ncommands. The NetBackup administrator needs to refer to the documentation of\ntheproduct/sub-systemNetBackupisintendedtobeintegrated.Forexample,while\nadding VRP server in NetBackup, steps to get the VRP server’s CA certificate in a\nPEM format will be available in VRP documentation.\nUse the following keytool commands to import the CA certificate into\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file <CA certificate file (PEM encoded) path>\n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass <password from the install_path\\var\\global\\jkskey file>\n-alias <alias name of the trusted certificate entry to be added>\nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file <CA certificate file (PEM encoded) path>\n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass <password from the /usr/openv/var/global/jkskey file>\n-alias <alias name of the trusted certificate entry to be added>\nNetBackupdoesn’tneedtheseCAcertificatesafterthebootstrappingcallsaredone\n(subsequentAPIcallsmakeuseofadifferenttruststorethathastheseCAcertificate\nentries populated). Cohesity recommends that entries are cleaned up once the\nremote entity is configured in NetBackup. To delete an entry from the temporary\nkeystore:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file <CA certificate file (PEM encoded) path>\n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass <password from the install_path\\var\\global\\jkskey file>\n-delete -alias <alias of the entry to be deleted>\nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-keystore /usr/openv/var/global/wsl/credentials/cacerts.bcfks\n-storepass <password from the /usr/openv/var/global/jkskey file> -delete\n-alias <alias of the entry to be deleted>\nPerform the following procedure to configure a trusted primary server.\nTo configure a trusted primary server\n1 Perform the following on the destination primary server:\nExport the CA certificate from a BCFKS format trust store using the keytool\ncommand:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-exportcert -alias <alias of the cert to be exported>\n-keystore <BCFKS format trust store> -storepass <store password> -rfc\n-file <destination PEM file in which this CA certificate will be exported>\nExample:\nWindows:\ninstall_path\\jre\\bin\\keytool\n-providerpath install_path\\wmc\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-file <file name of the CA cert PEM>\n-keystore install_path\\var\\global\\wsl\\credentials\\nbwebservice.bcfks\n-storepass <password from install_path\\var\\global\\jkskey>\nUNIX:\n/usr/openv/java/jre/bin/keytool -providerpath /usr/openv/wmc/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-storetype BCFKS -export -alias nbwmc -rfc\n-file /usr/openv/var/global /wsl/credentials/nbwmc.pem\n-keystore /usr/openv/var/global/wsl/credentials/nbwebservice.bcfks\n-storepass <password from /usr/openv/var/global/jkskey>\n2 Copy the PEM file that is created as part of the step 1 command run, from the\ndestination primary server to source primary server.\n3 On the source primary server, import the CA certificate from the PEM file to\ninstall_path/var/global/wsl/credentials/cacerts.bcfks:\nWindows:\ninstall_path\\java\\jre\\bin\\keytool -storetype BCFKS\n-providerpath install_path\\wmc\\webserver\\lib\\ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file <CA certificate file (PEM encoded) path>\n-keystore install_path\\var\\global\\wsl\\credentials\\cacerts.bcfks\n-storepass <password from the install_path\\var\\global\\jkskey file>\n-alias <alias name of the trusted certificate entry to be added>\nUNIX:\n/usr/openv/java/jre/bin/keytool -storetype BCFKS\n-providerpath /usr/openv/wmc/webserver/lib/ccj.jar\n-providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider\n-importcert -trustcacerts -file <CA certificate file (PEM encoded) path>\n-keystore install_path/var/global/wsl/credentials/cacerts.bcfks\n-storepass <password from the /usr/openv/var/global/jkskey file>\n-alias <alias name of the trusted certificate entry to be added>\n4 (Conditional)ToimporttheCAcertificateofsourceprimaryservertodestination\nprimary server, you must follow steps 1, 2, and 3. For step 1, the destination\nprimaryserverbecomessourceandsourcebecomesdestination.Thischange\nensures that both primary servers have each other’s CA certificate available\nat install_path/var/global/wsl/credentials/cacerts.bcfks.\nIf the remote entity has a JKS formatted keystore, the following command can\nbe used to export the CA certificate in PEM format.\nExporting a CA certificate from a JKS format trust store using the keytool\ncommand:\n/usr/openv/java/jre/bin/keytool -exportcert\n-alias <alias of the cert to be exported>\n-keystore <trust store path>\n-storepass <store password> -rfc\n-file <destination PEM file in which this CA certificate will be exported>"
    },
    "8799": {
        "code": 8799,
        "desc": "The validation of the certificate signing algorithm failed.",
        "first_action": "Contact your Certificate Authority to generate and issue",
        "full_action": "Contact your Certificate Authority to generate and issue\na certificate that is signed using non-deprecated algorithm."
    },
    "8800": {
        "code": 8800,
        "desc": "Communication with EMM failed.",
        "first_action": "Ensure that the nbemm service is running.",
        "full_action": "Do the following, as appropriate:\n■ Ensure that the nbemm service is running.\n■ Restart nbemm or the NetBackup Web Management Console (nbwmc) and retry\nthe request.\n■ ExaminetheunifiedloggingfilesontheNetBackupmasterserverforthenbemmm\n(OID 111) service and the NetBackup web services. Unified logging is written\nto /usr/openv/logs (UNIX) or to install_path\\NetBackup\\logs (Windows).\nSee the NetBackup Troubleshooting Guide and the NetBackup Logging\nReference Guide for details on troubleshooting the web services and on their\nlogs.\n■ If the problem persists, contact Cohesity Technical Support."
    },
    "8813": {
        "code": 8813,
        "desc": "Policy attributes must be specified using the property named 'policy'.",
        "first_action": "Please specify the policy attributes, including any",
        "full_action": "Please specify the policy attributes, including any\nschedules, clients, and backup selections within the ‘policy’ property in the JSON\npayload. See the NetBackup REST API documentation for details about the Policy\nAPI JSON schema."
    },
    "8814": {
        "code": 8814,
        "desc": "Please enter a valid Hyper-V machine name.",
        "first_action": "EnsurethattheNetBackupclientisinstalledontheHyper-V",
        "full_action": "EnsurethattheNetBackupclientisinstalledontheHyper-V\nserver and that the NetBackup master server can communicate with it."
    },
    "8816": {
        "code": 8816,
        "desc": "The ID in the URL does not match the ID in the body.",
        "first_action": "Ensure that the ID in the request URL matches the ID in",
        "full_action": "Ensure that the ID in the request URL matches the ID in\nthe request body."
    },
    "8817": {
        "code": 8817,
        "desc": "The credential name that you provided already exists.",
        "first_action": "Enteradifferentvalidcredentialnameintherequestbody.",
        "full_action": "Enteradifferentvalidcredentialnameintherequestbody.\nDo not leave any spaces between characters. The name must not exceed 256\ncharacters."
    },
    "8818": {
        "code": 8818,
        "desc": "Invalid policy name.",
        "first_action": "See the NetBackup Administrator’s Guide Volume I for details on the naming",
        "full_action": "Enter a valid name for the policy according to the naming\nrules. Use only alphabetic (ASCII A-Z and a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), or period (.) characters. Do not use a minus (-) or period (.) as the\nfirst or last character. Do not leave any spaces between characters.\nFor more information on policy names:\n■ See the NetBackup Administrator’s Guide Volume I for details on the naming\nconventions.\n■ You may also refer to the Article: 100016372 in the Support Knowledge Base\nfor more information about policy naming."
    },
    "8819": {
        "code": 8819,
        "desc": "Invalid schedule name.",
        "first_action": "Enter a valid name for the policy according to the naming",
        "full_action": "Enter a valid name for the policy according to the naming\nrules. Use only alphabetic (ASCII A-Z and a-z), numeric (0-9), plus (+), minus (-),\nunderscore(_), or period (.) characters. Do not use a minus (-) or period (.) as the\nfirst or last character. Do not leave any spaces between characters.\nSee the NetBackup Administrator’s Guide Volume I for details on the naming\nconventions."
    },
    "8820": {
        "code": 8820,
        "desc": "Failed to retrieve details of all the media servers.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8821": {
        "code": 8821,
        "desc": "Failed to retrieve the details of the specified media server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8822": {
        "code": 8822,
        "desc": "Failed to add the trusted master server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8823": {
        "code": 8823,
        "desc": "Failed to update the trusted master server.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8824": {
        "code": 8824,
        "desc": "Failed to retrieve the trusted master server details.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8825": {
        "code": 8825,
        "desc": "Failed to retrieve the remote primary server details.",
        "first_action": "See the errorDetails in JSON output for additional",
        "full_action": "See the errorDetails in JSON output for additional\ndetails. Retry the operation and if the issue persists, visit the Cohesity Technical\nSupport website. The Cohesity Technical Support website offers additional\ninformation to help you troubleshoot this issue."
    },
    "8836": {
        "code": 8836,
        "desc": "Failed to update the details of the specified media server.",
        "first_action": "The media server is known to master server.",
        "full_action": "Verify the following:\n■ The media server is known to master server.\n■ The media server is reachable from master server."
    },
    "8837": {
        "code": 8837,
        "desc": "The specified media server does not support this DTE configuration.",
        "first_action": "The media server is known to the master server.",
        "full_action": "Verify the following:\n■ The media server is known to the master server.\n■ The media server is on NetBackup 10.0 release or newer.\n■ The media server is reachable from the master server."
    },
    "8842": {
        "code": 8842,
        "desc": "Failed to save the proxy server details.",
        "first_action": "1 Call the POST API",
        "full_action": "Perform the following steps:\n1 Call the POST API\n(https://{NetbackupUrl}/netbackup/config/proxy-servers) to create\nthe proxy server.\n2 Create the API with proper syntax to validate the request but use some invalid\ndata which shows an error during run time.\n3 Verify that the error is shown in the API response."
    },
    "8900": {
        "code": 8900,
        "desc": "The host name that was provided must be associated with a single host ID.",
        "first_action": "Ensure that the host name that you want to add or delete",
        "full_action": "Ensure that the host name that you want to add or delete\nfor mapping is associated with a single host ID."
    },
    "8901": {
        "code": 8901,
        "desc": "The mapping name that was provided does not exist.",
        "first_action": "Provide a valid mapping name and try again.",
        "full_action": "Provide a valid mapping name and try again."
    },
    "8902": {
        "code": 8902,
        "desc": "Mappings for the specified host do not exist.",
        "first_action": "Provide a valid host name and try again.",
        "full_action": "Provide a valid host name and try again."
    },
    "8903": {
        "code": 8903,
        "desc": "The host name does not exist in the host ID to host name mapping list.",
        "first_action": "Use host name that is present in host ID to host name",
        "full_action": "Use host name that is present in host ID to host name\nmapping list. Alternatively, add the given host name to the mapping list with the\nnbhostmgmt -add command."
    },
    "8904": {
        "code": 8904,
        "desc": "The host database operations are blocked when disaster recovery is in progress.",
        "first_action": "Manually reset the environment variable",
        "full_action": "Manually reset the environment variable\nNB_DR_IN_PROGRESS to 0."
    },
    "8951": {
        "code": 8951,
        "desc": "The NetBackup API version is invalid.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8952": {
        "code": 8952,
        "desc": "A response cannot be generated in the media type specified by the request accept header.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8953": {
        "code": 8953,
        "desc": "The content type specified by the request content-type header is not supported by the requested resource for the requested method.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8954": {
        "code": 8954,
        "desc": "The filter criteria is invalid.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8955": {
        "code": 8955,
        "desc": "An invalid API request is encountered.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8956": {
        "code": 8956,
        "desc": "Multiple authorization headers are not allowed.",
        "first_action": "Remove the extra authorization headers and try again.",
        "full_action": "Remove the extra authorization headers and try again."
    },
    "8957": {
        "code": 8957,
        "desc": "The HTTP method is not supported.",
        "first_action": "For more details about this error, examine the webserver",
        "full_action": "For more details about this error, examine the webserver\nand nbwebservice logs. For more information, see the NetBackup API Reference\nGuide."
    },
    "8958": {
        "code": 8958,
        "desc": "A database system error occurred.",
        "first_action": "If you used the recovery point API to call Microsoft SQL",
        "full_action": "If you used the recovery point API to call Microsoft SQL\nsource files, review all API inputs and try again. If the problem persists, contact the\nCohesity Technical Support. For more information, see the NetBackup API\nReference Guide."
    },
    "8959": {
        "code": 8959,
        "desc": "Multiple audit reason headers are not allowed.",
        "first_action": "Choose one audit reason header and remove the other",
        "full_action": "Choose one audit reason header and remove the other\nheaders."
    },
    "8960": {
        "code": 8960,
        "desc": "The X-NetBackup-Audit-Reason header is not properly URL-encoded.",
        "first_action": "Ensurethattheauditreasonisproperlypercentencoded.",
        "full_action": "Ensurethattheauditreasonisproperlypercentencoded.\nOnly ISO-8859-1 characters are allowed."
    },
    "8962": {
        "code": 8962,
        "desc": "Requested operation failed.",
        "first_action": "Formoredetailsaboutthiserror,examinethewebserver",
        "full_action": "Formoredetailsaboutthiserror,examinethewebserver\nand nbwebservice logs. If the problem persists, contact the Cohesity Technical\nSupport. For more information, see the NetBackup API Reference Guide."
    },
    "8963": {
        "code": 8963,
        "desc": "The host name that you have specified to connect to the NetBackup web server is not present in the NetBackup web server certificate.",
        "first_action": "If you want to access the NetBackup Web Management",
        "full_action": "If you want to access the NetBackup Web Management\nConsole functionality using additional host names and or IP addresses (other than\nthe ones present in server certificate), refer to the following procedure.\nNote:Thissettingisonlyforamasterserver.Theallowedlist.propertiesneeds\nto have all the additional names (host names, IP addresses) of the master server\nthat would be used to connect from the clients. Examples of clients are the\nNetBackup Administration Console, web UI, any rest client, or other NetBackup\nclients.\nAccessing the NetBackup Web Management Console functionality using\nadditional host names and or IP addresses\n1 Create a file VAR_GLOBAL/wsl/config/allowedlist.properties.\nExample:\nWindows:\n<install_path>\\NetBackup\\var\\global\\wsl\\config\\allowedlist.properties\nUNIX: /usr/openv/var/global/wsl/config/allowedlist.properties\n2 Ensure that the web service account user has read permissions on this file.\nExample: On UNIX systems chmod a+r\n/usr/openv/var/global/wsl/config/allowedlist.propertiesisoneway\nto ensure required permissions on this file.\n3 Add required additional valid host.headers and x.forwarded.host.headers\nheader values.\n4 Save the file.\n5 Restart the NetBackup Web Management Console service.\nOnaWindowssystem,theNetBackup Web Management Consoleservicecan\nbe restarted from the Windows Service Control Manager.\nOn UNIX systems /usr/openv/netbackup/bin/nbwmc stop &&\n/usr/openv/netbackup/bin/nbwmc start.\nThe following is an example of an allowedlist.properties file looks like:\n#Sample Properties File#\n#Properties file to allow additional valid HOST and X-FORWARDED-HOST header values\n#Fri Apr 23 16:14:42 CDT 2021\nhost.headers=master_server_additional_name_1,master_server_additional_name_2,\nmaster_server_additional_ip_1,master_server_additional_ip_2\nx.forwarded.host.headers=master_server_additional_name_1,\nmaster_server_additional_name_2 ,master_server_additional_ip_1,\nmaster_server_additional_ip_2\nThe key host.headers has comma-separated string values of the host names and\nIP addresses which need to be considered valid for the HOST request header.\nThe key x.forwarded.host.headers has comma-separated string values of the\nhost names and IP addresses which need to be considered valid for the\nX-FORWARDED-HOST header."
    },
    "9032": {
        "code": 9032,
        "desc": "Could not connect to the virtual machine.",
        "first_action": "VerifyifthevirtualmachineisuportheSnapshotManager",
        "full_action": "VerifyifthevirtualmachineisuportheSnapshotManager\ncan communicate with the virtual machine. Review the Snapshot Manager logs."
    },
    "9050": {
        "code": 9050,
        "desc": "No matching report found.",
        "first_action": "Check if the report ID is in the GET /netbackup/reports",
        "full_action": "Check if the report ID is in the GET /netbackup/reports\nresponse."
    },
    "9051": {
        "code": 9051,
        "desc": "Invalid filter specified in the request.",
        "first_action": "Check if the filter string that was passed through the",
        "full_action": "Check if the filter string that was passed through the\nrequest body is valid."
    },
    "9052": {
        "code": 9052,
        "desc": "Invalid report request.",
        "first_action": "Check that the request body is valid.",
        "full_action": "Check that the request body is valid."
    },
    "9053": {
        "code": 9053,
        "desc": "Invalid job report type found.",
        "first_action": "CheckifthereporttypeisintheGET /netbackup/reports",
        "full_action": "CheckifthereporttypeisintheGET /netbackup/reports\nresponse."
    },
    "9101": {
        "code": 9101,
        "desc": "Failed to lock the file.",
        "first_action": "Examine the logs for the operation you tried to perform.",
        "full_action": "Do the following, as appropriate:\n■ Examine the logs for the operation you tried to perform.\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)."
    },
    "9102": {
        "code": 9102,
        "desc": "Failed to unlock the file.",
        "first_action": "Examine the logs for the operation you tried to perform.",
        "full_action": "Do the following, as appropriate:\n■ Examine the logs for the operation you tried to perform.\n■ Examine legacy logs on the NetBackup server for nbcertcmd."
    },
    "9103": {
        "code": 9103,
        "desc": "Unexpected response from the web service. NetBackup status codes 1099 NetBackup status codes",
        "first_action": "Upgrade the back-level master server.",
        "full_action": "Do the following, as appropriate:\n■ Upgrade the back-level master server.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (all OIDs).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)."
    },
    "9104": {
        "code": 9104,
        "desc": "The certificate verification failed.",
        "first_action": "Verify the PKI artifacts using the OpenSSL command.",
        "full_action": "Verify the PKI artifacts using the OpenSSL command."
    },
    "9108": {
        "code": 9108,
        "desc": "Failed to connect to the vnetd service.",
        "first_action": "1. Ensure that the vnetd process is running on the NetBackup host.",
        "full_action": "Do the following:\n1. Ensure that the vnetd process is running on the NetBackup host.\n2. If the problem persists, contact Cohesity Technical Support."
    },
    "9126": {
        "code": 9126,
        "desc": "The remote server’s certificate is not valid or doesn’t exist.",
        "first_action": "Review the nbcs/bpfis/bppfi level error messages that are displayed in Job",
        "full_action": "Perform the following as appropriate:\nThe table that is shown lists the issue and the associated action that is required to\nfix the issue:\n■ Review the nbcs/bpfis/bppfi level error messages that are displayed in Job\ndetails on the Activity monitor. For more details, review the component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\nand plug-in configuration. For more details, review the component logs.\nTable 1-7 Operation failed due to SSL certificate issues or connectivity\nissues.\nMessage Recommended action\nUnable to retrieve the certificate CRL. If you Copy the latest CRL into the\nhave configured the ECA_CRL_PATH, ECA_CRL_PATHpathorensurethattheCRL\nensure that valid CRLs are present at the distribution point URL from the respective\nlocation. Confirm that the CRL URL is host certificate is accessible from the\naccessible from the Snapshot Manager. Snapshot Manager.\nThecertificaterevocationlist(CRL)isexpired. Ensure that the latest CRL’s are uploaded at\nEnsurethattheECA_CRL_PATHisupdated the ECA_CRL_PATH path.\nwith the latest CRL.\nThe Snapshot Manager CRL cache can be\nupdated manually by using the following\ncommand on Snapshot Manager host:\nflexsnap_configure renew --token\ntoken\nThecertificaterevocationlist(CRL)isnotyet Review your Snapshot Manager’s system\nvalid. time or provide a valid CRL.\nThe date of last update of the certificate Review the CRL using the OpenSSL\nrevocation list (CRL) is not in a valid format. command or contact your Security\nAdministrator.\nThe date of next update of the certificate Review the CRL using the OpenSSL\nrevocation list (CRL) is not in a valid format. command or contact your Security\nAdministrator.\nTable 1-7 Operation failed due to SSL certificate issues or connectivity\nissues. (continued)\nMessage Recommended action\nThe operation has failed with a cURL error. Perform the operation again. If the problem\npersists, save all of the error log information\nand contact Cohesity Technical Support.\nThe certificate is revoked. Determine if any of the certificates in the\nchain have been revoked or contact your\nSecurity Administrator.\nTo renew Snapshot Manager certificate, run\nthe following command on the Snapshot\nManager host:\nFor NBCA: flexsnap_configure renew\n--hostnames FQDN --token token\n--force\nFor ECA: flexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nFor more details, refer to status code 9318.\nThe certificate has expired. (Not applicable for NBCA) Review the\nexpiration of the certificates or contact your\nSecurity Administrator.\nFor ECA, renew the Snapshot Manager\ncertificate manually on Snapshot Manager\nhost using the following command.\nflexsnap_configure renew\n--hostnames FQDN --ca ca_file_path\n--key key_file_path --chain\nchain_file_path\nFor NBCA, Snapshot Manager certificates\nareautomaticallyrenewedwithinlast90days\nof the expiration period.\nFor more details, refer to status code 8506.\nOther NetBackup error codes or messages can also be referred to for more\ninformation of SSL certificate or connectivity issues between primary server and\nSnapshotManager.Resolvenetworkissuesifany,withnetstatorasimilarnetwork\ndiagnosis tool. The status of certificates that are issued for Snapshot Manager can\nbeverifiedusingflexsnap_configure serverinfoandhealthofcontainersrunning\ncan be verified using flexsnap_configure status."
    },
    "9128": {
        "code": 9128,
        "desc": "Failed to obtain the backup ID from the track log file.",
        "first_action": "1. Rename the appropriate track journal folder on client:",
        "full_action": "To address the issue, perform the following:\n1. Rename the appropriate track journal folder on client:\ninstall_path\\Veritas\\NetBackup\n\\track\\<media_server>\\<storage_server>\\<client>\\<policy>\n2. Perform a new full backup."
    },
    "9129": {
        "code": 9129,
        "desc": "The private key file cannot be loaded.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "9130": {
        "code": 9130,
        "desc": "The private key file cannot be validated.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "9131": {
        "code": 9131,
        "desc": "The SSL handshake failed.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support site offers additional\ninformation to help you troubleshoot this issue."
    },
    "9132": {
        "code": 9132,
        "desc": "Cannot connect to the host because the NetBackup services are not running on the host.",
        "first_action": "PBX services",
        "full_action": "Verify that the following services are up and are running\non the host:\n■ PBX services\n■ NetBackup services\nIf you continue to have problems, see Resolving network communication problems\nin the NetBackup Troubleshooting Guide."
    },
    "9134": {
        "code": 9134,
        "desc": "Failed to retrieve the passphrase.",
        "first_action": "Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect",
        "full_action": "Perform the following as appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If the file is present but lacks the proper permissions, adjust the\npermissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9135": {
        "code": 9135,
        "desc": "TheNetBackupclientusesaweakcipherforencryption,ortheencryption is of the legacy type.",
        "first_action": "Use STANDARD kind of encryption method with strong ciphers like AES.",
        "full_action": "Perform the following as appropriate:\nUse STANDARD kind of encryption method with strong ciphers like AES."
    },
    "9136": {
        "code": 9136,
        "desc": "Rotation of the passphrase key failed.",
        "first_action": "Verify that the passphrase key file exists at the keystore location and has the",
        "full_action": "Perform the following as appropriate:\n■ Verify that the passphrase key file exists at the keystore location and has the\ncorrectpermissions.Ifthefileispresentbutlackstheproperpermissions,adjust\nthe permissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9139": {
        "code": 9139,
        "desc": "Backup files already present in keystore.",
        "first_action": "Remove the backup files in the keystore folder that have the _bkup suffix and",
        "full_action": "Perform the following as appropriate:\n■ Remove the backup files in the keystore folder that have the _bkup suffix and\nretry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice logs\nand contact Cohesity Technical Support."
    },
    "9140": {
        "code": 9140,
        "desc": "Directory is empty.",
        "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs",
        "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support."
    },
    "9141": {
        "code": 9141,
        "desc": "Keystore is in inconsistent state. NetBackup status codes 1106 NetBackup status codes",
        "first_action": "Verify that the private key, passphrase, and passphrase key files exist at the",
        "full_action": "Perform the following as appropriate:\n■ Verify that the private key, passphrase, and passphrase key files exist at the\nkeystorelocationandhavethecorrectserviceuserpermissions.Ifthefilesare\npresent but lack the proper permissions, adjust the permissions manually and\nretry the operation.\n■ If backup files are present clean-up the backup files with the _bkup suffix and\nretry the operation.\n■ For any other case:\n■ If the issue persists, remove all files from the keystore directory, including\nany hidden files. Depending on your configuration, the keystore directory\nis install_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystore\ndirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ Iftheissuepersists,collectthenbcert,nbpxyhelper,andnbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9142": {
        "code": 9142,
        "desc": "File does not exist.",
        "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs",
        "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support."
    },
    "9143": {
        "code": 9143,
        "desc": "Rotation of the passphrase failed.",
        "first_action": "Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect",
        "full_action": "Perform the following as appropriate:\n■ Verifythatthepassphrasefileexistsatthekeystorelocationandhasthecorrect\npermissions. If the file is present but lacks the proper permissions, adjust the\npermissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9144": {
        "code": 9144,
        "desc": "Rotation of the passphrase and the subsequent restore failed.",
        "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs",
        "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support."
    },
    "9145": {
        "code": 9145,
        "desc": "The given tag does not exist in the passphrase key file.",
        "first_action": "If the issue persists, remove all files from the keystore directory, including any",
        "full_action": "Perform the following as appropriate:\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9146": {
        "code": 9146,
        "desc": "The passphrase key file does not have any contents.",
        "first_action": "If the issue persists, remove all files from the keystore directory, including any",
        "full_action": "Perform the following as appropriate:\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9147": {
        "code": 9147,
        "desc": "Failed to create encryption tag.",
        "first_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,",
        "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, and nbwebservice logs and contact Cohesity Technical Support."
    },
    "9148": {
        "code": 9148,
        "desc": "Failed to create encryption key.",
        "first_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,",
        "full_action": "Retrytheoperation.Iftheissuepersists,collectthenbcert,\nnbpxyhelper, and nbwebservice logs and contact Cohesity Technical Support."
    },
    "9149": {
        "code": 9149,
        "desc": "Failed to create passphrase key file.",
        "first_action": "Verify that the passphrase key file or directory exists at the keystore location",
        "full_action": "Perform the following as appropriate:\n■ Verify that the passphrase key file or directory exists at the keystore location\nand has the correct permissions. If the file is present but lacks the proper\npermissions, adjust the permissions manually and retry the operation.\n■ If the issue persists, remove all files from the keystore directory, including any\nhidden files. Depending on your configuration, the keystore directory is\ninstall_dir/var/vxss/credentials/keystore,\ninstall_dir/var/global/vxss/credentials/keystore,\ninstall_path\\NetBackup\\var\\vxss\\credentials\\keystore, or\ninstall_path\\NetBackup\\var\\global\\vxss\\credentials\\keystoredirectory.\n■ Perform nbcertcmd -getCertificate with reissueToken option for all\nservers with which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice\nlogs and contact Cohesity Technical Support."
    },
    "9150": {
        "code": 9150,
        "desc": "Failed to rotate passphrase due to the incorrect encryption state of the keystore.",
        "first_action": "Performnbcertcmd -getCertificatewithreissueTokenoptionforallservers",
        "full_action": "Perform the following as appropriate:\n■ Performnbcertcmd -getCertificatewithreissueTokenoptionforallservers\nwith which the host is registered and retry the operation.\n■ If the issue persists, collect the nbcert, nbpxyhelper, and nbwebservice logs\nand contact Cohesity Technical Support."
    },
    "9151": {
        "code": 9151,
        "desc": "An internal error occurred.",
        "first_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs",
        "full_action": "Collectthenbcert,nbpxyhelper,andnbwebservicelogs\nand contact Cohesity Technical Support."
    },
    "9152": {
        "code": 9152,
        "desc": "The user does not have permission to access the keystore directory.",
        "first_action": "Verify the file or the folder permissions.",
        "full_action": "Perform the following as appropriate:\n■ Verify the file or the folder permissions.\n■ Grant the service user read, write, and access permissions if necessary.\n■ Retry the operation."
    },
    "9201": {
        "code": 9201,
        "desc": "The service user cannot switch the context to another user.",
        "first_action": "Update or remove the logon details from catalog backup",
        "full_action": "Update or remove the logon details from catalog backup\npolicy."
    },
    "9202": {
        "code": 9202,
        "desc": "The service user account does not have the write permissions on the specified path.",
        "first_action": "Windows:",
        "full_action": "Verify that the service account has write access on the\nuser path that is specified.\nFor example: If the service user account does not have write permissions on the\ndisaster recovery package path specified in the catalog backup policy, the catalog\nbackup fails with this error.\nThe catalog recovery also fails with this error if the service user account does not\nhave write access to the DR path and its contents.\nRun the following commands so that service user account has write access on the\ndisaster recovery path:\n■ Windows:\nICACLS \"<DR_Path>\" /grant:r\n\"*S-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012:(OI)(CI)F\"\nIn this command example,\nS-1-5-80-623693008-3165178162-2673590941-1612452212-3346329012 is\nService SID of NetBackup Database Manager service (bpdbm).\n■ UNIX:\nchown -R <service_user_name> <DR_Path>\nAfter the chown command is run, verify that the service user can write to the\nspecified path using the su command.\nsu <service_user_name> -c \"touch <DR_path>/test.txt\""
    },
    "9250": {
        "code": 9250,
        "desc": "Host IDs of the target and the source hosts do not match.",
        "first_action": "Make sure the reissue token that is generated for the same host is used for the",
        "full_action": "Perform the following as appropriate:\nFor NBCA:\n■ Make sure the reissue token that is generated for the same host is used for the\nfetching certificate.\n■ If the reissue token is correct, then delete the particular entry that caused the\nissue and fetch the certificates from that primary server again.\n■ RefertothesectionAboutreissuinghostID-basedcertificatesintheNetBackup\nSecurity and Encryption Guide for more details.\nFor ECA:\n■ This problem may be reported if the certificate used for enrollment is already\nenrolledwithsomeotherhost.Verifythatthecertificatethatisusedforenrollment\nis associated with the current host. Find and delete the particular entry that\ncaused the issue and enroll the certificate again.\n■ Refer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nRetrytheoperationandiftheissuepersists,visitsupport.veritas.com.TheCohesity\nTechnicalSupportwebsitesiteoffersadditionalinformationtohelpyoutroubleshoot\nthis issue."
    },
    "9251": {
        "code": 9251,
        "desc": "Host IDs of the target and the source master servers do not match.",
        "first_action": "Manually delete the entry for the primary host ID causing",
        "full_action": "Manually delete the entry for the primary host ID causing\nthe issue and perform the operation again.\nRefer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue."
    },
    "9252": {
        "code": 9252,
        "desc": "Either the source host ID or the target host ID is null.",
        "first_action": "Manually delete the entry that has a null host ID causing",
        "full_action": "Manually delete the entry that has a null host ID causing\nthe issue and perform the operation again.\nRefer to the section About external CA support in NetBackup in the NetBackup\nSecurity and Encryption Guide for more details.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue."
    },
    "9253": {
        "code": 9253,
        "desc": "Removing JSON array failed.",
        "first_action": "Check the write file permission. If the issue persists, visit",
        "full_action": "Check the write file permission. If the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "9270": {
        "code": 9270,
        "desc": "Failed to retrieve credentials for SpanFS server.",
        "first_action": "Review the nbemm logs from the primary server and the",
        "full_action": "Review the nbemm logs from the primary server and the\nbptm logs from the media server for errors. Search the Cohesity Technical Support\nwebsite to determine the source of those errors. For additional assistance, collect\nthe nbemm and bptm logs and contact Cohesity Technical Support."
    },
    "9271": {
        "code": 9271,
        "desc": "Failed to retrieve trusted certificate for SpanFS server.",
        "first_action": "Storage_server cluster_FQDN -stype SpanFS -media_server",
        "full_action": "If the automatic trust certificate retrieval fails, configure\nor update the SpanFS server manually, using REST API or tpconfig command.\nTo configure or update the SpanFS server, SpanFS CA certificate is required.\nRefer to article to retrieve the SpanFS CA certificate:\nUsing REST API\nTo configure SpanFS server, use the POST API\n'/netbackup/storage/storage-server' endpoint.\nTo update SpanFS server credentials, use the PATCH API\n'/netbackup/storage/storage-server' endpoint.\nUsing tpconfig CLI\nTo configure SpanFS server\n1 Create a storage server of type SpanFS using the fully qualified domain name\n(FQDN) of the cluster.\n/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests\n-storage_server cluster_FQDN -stype SpanFS -media_server\nmedia_server\n2 Add credentials for the SpanFS server.\n/usr/openv/volmgr/bin/tpconfig -add -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [-password password] [-st\nstorage_type] [-ca_file_path SpanFS_CA_certificate_path]\nTo update SpanFS server credentials\n◆ /usr/openv/volmgr/bin/tpconfig -update -storage_server server_name\n-stype SpanFS -sts_user_id user_ID [ password password] [\n-ca_file_path SpanFS_CA_certificate_path]"
    },
    "9300": {
        "code": 9300,
        "desc": "Failed to encode the certificate revocation list (CRL).",
        "first_action": "On the master server, examine the unified logs on the NetBackup server for",
        "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Ensure that you use the NetBackup SSL libraries.\n■ Contact Cohesity Technical Support."
    },
    "9301": {
        "code": 9301,
        "desc": "Failed to decode the certificate revocation list (CRL).",
        "first_action": "On the master server, examine the unified logs on the NetBackup server for",
        "full_action": "Do the following, as appropriate:\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ On all hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486).\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ Run the following command to get a new CRL for the corresponding domain:\n./nbcertcmd -getCrl [-server master server name]"
    },
    "9302": {
        "code": 9302,
        "desc": "Attempted to replace the certificate revocation list (CRL) with an older version. NetBackup status codes 1117 NetBackup status codes",
        "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.",
        "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On all of the hosts involved in the communication, examine the unified logs for\nnbpxyhelper (OID 486)."
    },
    "9303": {
        "code": 9303,
        "desc": "The web service request to fetch the certificate revocation list (CRL) failed.",
        "first_action": "On the host where the error occurred, examine the legacy logs for nbcertcmd.",
        "full_action": "Do the following, as appropriate:\n■ On the host where the error occurred, examine the legacy logs for nbcertcmd.\n■ On the master server, examine the unified logs on the NetBackup server for\nnbwebservice (OID 466 and 484).\n■ Ensure the following:\n■ The master server is online.\n■ The web service (nbwmc) is online."
    },
    "9304": {
        "code": 9304,
        "desc": "The HTTP request is not complete; it should be checked again later.",
        "first_action": "Examine the legacy logs for nbcertcmd and the unified",
        "full_action": "Examine the legacy logs for nbcertcmd and the unified\nlogs on the NetBackup server for nbwebservice (OID 466 and 484)."
    },
    "9305": {
        "code": 9305,
        "desc": "An attempt to refresh the certificate revocation list (CRL) and security level was partially successful.",
        "first_action": "Examine the legacy logs for nbcertcmd.",
        "full_action": "Do the following, as appropriate:\n■ Examine the legacy logs for nbcertcmd.\n■ Ensure that the HTTP request to fetch the CRL and the security level was\nsuccessful.OntheNetBackupserver,examinetheunifiedlogsfornbwebservice\n(OID 466 and 484) for HTTP request failures."
    },
    "9306": {
        "code": 9306,
        "desc": "The HTTP request for fetching the security level failed.",
        "first_action": "Examine the legacy logs for nbcertcmd and the unified logs on the NetBackup",
        "full_action": "Do the following, as appropriate:\n■ Examine the legacy logs for nbcertcmd and the unified logs on the NetBackup\nserver for nbwebservice (OID 466 and 484).\n■ Ensure the following:\n■ The master server is online.\n■ The web service (nbwmc) is online."
    },
    "9307": {
        "code": 9307,
        "desc": "The HTTP request to fetch the CRL failed. The reason for the failure is unknown.",
        "first_action": "Examine the legacy logs on the NetBackup host for",
        "full_action": "Examine the legacy logs on the NetBackup host for\nnbcertcmd."
    },
    "9308": {
        "code": 9308,
        "desc": "Failed to read the certificate revocation list (CRL).",
        "first_action": "If NetBackup CA-signed certificate is used for communication: On all the hosts",
        "full_action": "Do the following, as appropriate:\n■ If NetBackup CA-signed certificate is used for communication: On all the hosts\nthatareinvolvedinthecommunication,examinetheunifiedlogsfornbpxyhelper\n(OID 486).\n■ Examine the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\nFor a clustered master server:\n/usr/openv/var/global/vxss/crl\n■ For a Windows server, verify in the certmapinfo.json files that the crlPath\nvalues point to a valid path for the CRL:\ninstall_path\\NetBackup\\var\\vxss\\certmapinfo.json\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\certmapinfo.json\n■ ForaUNIXserver,verifyinthecertmapinfo.jsonfilesthatthecrlPathvalues\npoint to a valid path for the CRL:\n/usr/openv/var/vxss/certmapinfo.json\nFor a clustered master server:\n/usr/openv/var/global/vxss/certmapinfo.json\n■ Run the following command for the master server:\n./nbcertcmd -getCRL -server master_server_name\nIf external CA-signed certificate is used for communication:\n■ On all hosts that are involved in the communication, examine the unified logs\nfor nbpxyhelper (OID 486).\n■ Examine the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\n■ Verify if above directory contains all the required valid CRLs (as per\nECA_CRL_CHECK setting)."
    },
    "9309": {
        "code": 9309,
        "desc": "Failed to write the certificate revocation list (CRL).",
        "first_action": "Examine the unified logs on the NetBackup server for nbwebservice (OID 466",
        "full_action": "Do the following, as appropriate:\n■ Examine the unified logs on the NetBackup server for nbwebservice (OID 466\nand 484) and the legacy logs for nbcertcmd.\n■ For a Windows server, verify that the following directories exist:\ninstall_path\\NetBackup\\var\\vxss\\crl\nFor a clustered master server:\ninstall_path\\NetBackup\\var\\global\\vxss\\crl\n■ For a UNIX server, verify that the following directories exist:\n/usr/openv/var/vxss/crl\nFor a clustered master server:\n/usr/openv/var/global/vxss/crl"
    },
    "9310": {
        "code": 9310,
        "desc": "The CRL for the specified issuer cannot be found in the CRL cache.",
        "first_action": "Provide the SHA-1 hash of the correct CRL issuer that",
        "full_action": "Provide the SHA-1 hash of the correct CRL issuer that\nyou want to clean up from the CRL cache. The path for the CRL cache is:\n/usr/openv/var/vxss/crl."
    },
    "9311": {
        "code": 9311,
        "desc": "Failed to clean up the CRL for the specified issuer from the CRL cache.",
        "first_action": "Another process may have locked the CRL file. Retry the",
        "full_action": "Another process may have locked the CRL file. Retry the\noperation."
    },
    "9312": {
        "code": 9312,
        "desc": "Failed to clean up the expired CRLs from the CRL cache.",
        "first_action": "Another process may have locked the CRL files. Retry",
        "full_action": "Another process may have locked the CRL files. Retry\nthe operation."
    },
    "9313": {
        "code": 9313,
        "desc": "Failed to clean up some of the expired CRLs from the CRL cache.",
        "first_action": "Another process may have locked the CRL files. Retry",
        "full_action": "Another process may have locked the CRL files. Retry\nthe operation."
    },
    "9314": {
        "code": 9314,
        "desc": "The CRL is expired.",
        "first_action": "Provide the CRLs that are not expired.",
        "full_action": "Provide the CRLs that are not expired."
    },
    "9315": {
        "code": 9315,
        "desc": "Failed to update some of the CRLs in the CRL cache.",
        "first_action": "CRLs are not expired.",
        "full_action": "Ensure the following:\n■ CRLs are not expired.\n■ CRLs use a valid format.\n■ CRLs are updated then the cached copy."
    },
    "9316": {
        "code": 9316,
        "desc": "Failed to update the CRLs in the CRL cache.",
        "first_action": "CRLs are not expired.",
        "full_action": "Ensure the following:\n■ CRLs are not expired.\n■ CRLs use a valid format.\n■ CRLs are updated then the cached copy."
    },
    "9317": {
        "code": 9317,
        "desc": "The CRL check is disabled.",
        "first_action": "Ensure that the ECA_CRL_CHECK configuration option is",
        "full_action": "Ensure that the ECA_CRL_CHECK configuration option is\nset to LEAF or CHAIN."
    },
    "9318": {
        "code": 9318,
        "desc": "The certificate is revoked.",
        "first_action": "If the certificate is not revoked and you still see this error,",
        "full_action": "If the certificate is not revoked and you still see this error,\ncheck if the CRL is updated in the CRL cache. If the problem persists, contact your\nsecurity administrator."
    },
    "9319": {
        "code": 9319,
        "desc": "The certificate is not revoked.",
        "first_action": "Ifthecertificateis revokedand you stillsee thismessage,",
        "full_action": "Ifthecertificateis revokedand you stillsee thismessage,\ncheck if the CRL is updated in the CRL cache. If the problem persists, contact your\nsecurity administrator."
    },
    "9324": {
        "code": 9324,
        "desc": "The CRL cache cannot be updated. The ECA_CRL_PATH configuration option is not set to a valid CRL directory path.",
        "first_action": "Specify the correct directory path for the ECA_CRL_PATH",
        "full_action": "Specify the correct directory path for the ECA_CRL_PATH\nconfiguration option."
    },
    "9325": {
        "code": 9325,
        "desc": "The CRL cache cannot be updated. CRLs are not available in the directory that is set for the ECA_CRL_PATH configuration option.",
        "first_action": "SpecifyavalidCRLdirectorypaththatcontainsvalidCRL",
        "full_action": "SpecifyavalidCRLdirectorypaththatcontainsvalidCRL\nfiles for the ECA_CRL_PATH configuration option."
    },
    "9326": {
        "code": 9326,
        "desc": "The CRL is delta CRL.",
        "first_action": "NetBackup does not support delta CRLs. You should",
        "full_action": "NetBackup does not support delta CRLs. You should\nspecify a full CRL for the ECA_CRL_PATH or for the CDP."
    },
    "9327": {
        "code": 9327,
        "desc": "Unable to retrieve CRL for the certificate.",
        "first_action": "Check if the CRL exists in the CRL cache for the certificate issuer based on the",
        "full_action": "Perform the following:\n■ Check if the CRL exists in the CRL cache for the certificate issuer based on the\nECA_CRL_CHECK configuration option (CHAIN or LEAF). If the CRL does not exist\nin the cache, do the following:\n■ If the ECA_CRL_PATH configuration option is configured, run the nbcertcmd\n-updatecrlcache command.\n■ If CDP is enabled, check the bpclntcmd crldownloader logs.\nRefertoSee“"
    },
    "9328": {
        "code": 9328,
        "desc": "Unable to decrypt the CRL signature.",
        "first_action": "For file-based certificates:",
        "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support."
    },
    "9329": {
        "code": 9329,
        "desc": "CRL signature failure.",
        "first_action": "For file-based certificates:",
        "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support."
    },
    "9330": {
        "code": 9330,
        "desc": "The CRL is not yet valid.",
        "first_action": "Check your system time or provide a valid CRL.",
        "full_action": "Check your system time or provide a valid CRL."
    },
    "9331": {
        "code": 9331,
        "desc": "The CRL last update date is not in a valid format.",
        "first_action": "Check the CRL using the openssl command or contact",
        "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator."
    },
    "9332": {
        "code": 9332,
        "desc": "The CRL next update date is not in a valid format.",
        "first_action": "Check the CRL using the openssl command or contact",
        "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator."
    },
    "9333": {
        "code": 9333,
        "desc": "Unable to retrieve the CRL issuer certificate.",
        "first_action": "For file-based certificates:",
        "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support."
    },
    "9334": {
        "code": 9334,
        "desc": "Key usage does not include CRL signing.",
        "first_action": "For file-based certificates:",
        "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support."
    },
    "9335": {
        "code": 9335,
        "desc": "Critical CRL extension is not valid.",
        "first_action": "Check the CRL using the openssl command or contact",
        "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator."
    },
    "9336": {
        "code": 9336,
        "desc": "The CRL scope is different, it should cover all revocation reasons.",
        "first_action": "Check the CRL using the openssl command or contact",
        "full_action": "Check the CRL using the openssl command or contact\nyour Security Administrator."
    },
    "9337": {
        "code": 9337,
        "desc": "CRL path validation error.",
        "first_action": "For file-based certificates:",
        "full_action": "Perform the following:\n■ For file-based certificates:\n■ Usetheopenssl verifycommandtocheckthecertificateagainsttheCRL.\n■ For Windows certificate store:\n■ Exportthecertificateandruntheopenssl verifyorthecertUtilcommand.\n■ Iftheverificationfails,refertotheOpenSSLdocumentsorcontactyourSecurity\nAdministrator.\n■ If the verification is successful but the problem persists, contact Cohesity\nNetBackup support."
    },
    "9338": {
        "code": 9338,
        "desc": "The CRL on the server is expired.",
        "first_action": "Provide a valid CRL for the issuer of the client certificate.",
        "full_action": "Provide a valid CRL for the issuer of the client certificate."
    },
    "9339": {
        "code": 9339,
        "desc": "The CRL is not available on the server.",
        "first_action": "Provide a valid CRL for the issuer of the client certificate",
        "full_action": "Provide a valid CRL for the issuer of the client certificate\non the server host."
    },
    "9340": {
        "code": 9340,
        "desc": "CRL server internal error.",
        "first_action": "Check the CRL configuration on the server or refer to the",
        "full_action": "Check the CRL configuration on the server or refer to the\nAbout certificate revocation lists for external CA section in the NetBackup Security\nand Encryption Guide."
    },
    "9350": {
        "code": 9350,
        "desc": "The API key is not valid.",
        "first_action": "Use a valid API key to access NetBackup APIs.",
        "full_action": "Use a valid API key to access NetBackup APIs."
    },
    "9351": {
        "code": 9351,
        "desc": "The API key cannot be generated.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "9352": {
        "code": 9352,
        "desc": "An unexpected API key error occurred.",
        "first_action": "Contact Cohesity Technical Support for assistance.",
        "full_action": "Contact Cohesity Technical Support for assistance."
    },
    "9353": {
        "code": 9353,
        "desc": "An API key for the given user already exists.",
        "first_action": "Delete the existing API key for the user and recreate an",
        "full_action": "Delete the existing API key for the user and recreate an\nAPI key."
    },
    "9354": {
        "code": 9354,
        "desc": "The specified API key does not exist.",
        "first_action": "The specified API key is not deleted.",
        "full_action": "Ensure the following:\n■ The specified API key is not deleted.\n■ The specified API key tag is correct."
    },
    "9355": {
        "code": 9355,
        "desc": "The API key has expired.",
        "first_action": "Delete the expired API key.",
        "full_action": "Perform the following actions:\n■ Delete the expired API key.\n■ Create a new API key for the given user."
    },
    "9356": {
        "code": 9356,
        "desc": "The API key tag in the URL should match the ID from the payload.",
        "first_action": "Provide the API key tag that is same as the ID in the",
        "full_action": "Provide the API key tag that is same as the ID in the\npayload."
    },
    "9357": {
        "code": 9357,
        "desc": "TheAPIkeyexpirationdatemustnotbelaterthan9999-12-31 23:59:59 +00:00.",
        "first_action": "Provide a valid expiration date for the API key.",
        "full_action": "Provide a valid expiration date for the API key."
    },
    "9380": {
        "code": 9380,
        "desc": "Themultipersonauthorizationrequestorthedatathatissentisnotvalid.",
        "first_action": "Retry the operation with valid request and data.",
        "full_action": "Perform the following as appropriate:\nRetry the operation with valid request and data."
    },
    "9381": {
        "code": 9381,
        "desc": "The multiperson authorization request cannot be processed.",
        "first_action": "ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.",
        "full_action": "Perform the following as appropriate:\n■ ChecktheNetBackupProblemsreportforadditionalinformationabouttheerror.\n■ Increase the logging level. Retry the operation and check the resulting debug\nlogs."
    },
    "9382": {
        "code": 9382,
        "desc": "The operation has failed because it is configured for multiperson authorization.",
        "first_action": "Perform the operation using NetBackup web UI.",
        "full_action": "Perform the following as appropriate:\n■ Perform the operation using NetBackup web UI.\n■ Usethenbcmdruncommand.SeetheNetBackupCommandsReferenceGuide\nfor more information about the nbcmdrun command.\n■ Contact the NetBackup Security Administrator to exempt from multiperson\nauthorization."
    },
    "9383": {
        "code": 9383,
        "desc": "The date is not within the allowed range that is between 01/01/1970 and the current date. NetBackup status codes 1133 NetBackup status codes",
        "first_action": "Specify a valid date that is between 01/01/1970 and the current date.",
        "full_action": "Perform the following as appropriate:\nSpecify a valid date that is between 01/01/1970 and the current date."
    },
    "9384": {
        "code": 9384,
        "desc": "The multiperson authorization ticket with the given ID cannot be found.",
        "first_action": "Specify a valid ticket ID.",
        "full_action": "Perform the following as appropriate:\nSpecify a valid ticket ID."
    },
    "9385": {
        "code": 9385,
        "desc": "The current state of the multiperson authorization ticket is not valid.",
        "first_action": "Check the current state of the multiperson ticket and take corrective actions before",
        "full_action": "Perform the following as appropriate:\nCheck the current state of the multiperson ticket and take corrective actions before\nyou invoke the operation."
    },
    "9386": {
        "code": 9386,
        "desc": "Youdonothavethepermissionstoupdatethemultipersonauthorization ticket.",
        "first_action": "Contact the NetBackup Administrator for the required permissions.",
        "full_action": "Perform the following as appropriate:\nContact the NetBackup Administrator for the required permissions."
    },
    "9387": {
        "code": 9387,
        "desc": "A multiperson authorization ticket is created for the given operation.",
        "first_action": "Use the NetBackup web UI to verify whether the associated multiperson",
        "full_action": "Perform the following as appropriate:\n■ Use the NetBackup web UI to verify whether the associated multiperson\nauthorization ticket is approved or not. Contact your NetBackup administrator\northeNetBackupmultipersonauthorizationapprovertogetyourticketapproved.\n■ To prevent ticket generation for the associated user, contact the NetBackup\nSecurity Administrator to exempt the user from the multiperson authorization\nprocess."
    },
    "9388": {
        "code": 9388,
        "desc": "The maximum limit of the images to be expired is reached.",
        "first_action": "Split the bidfile into multiple files such that each file",
        "full_action": "Split the bidfile into multiple files such that each file\ndoes not contain more than 30000 entries."
    },
    "9389": {
        "code": 9389,
        "desc": "The operation has failed because there is a pending ticket for the same entity.",
        "first_action": "Make sure that the current request is resolved before you",
        "full_action": "Make sure that the current request is resolved before you\nrequest another operation on the same entity."
    },
    "9391": {
        "code": 9391,
        "desc": "You do not have the permissions to view the multiperson authorization ticket.",
        "first_action": "Make sure that the requester has appropriate RBAC",
        "full_action": "Make sure that the requester has appropriate RBAC\npermissions to fetch the multiperson authorization ticket information which was\ncreated on the behalf of action of other user."
    },
    "9392": {
        "code": 9392,
        "desc": "The authorization data that is associated with this multiperson authorization ticket cannot be verified.",
        "first_action": "Perform the required operation again so that a new",
        "full_action": "Perform the required operation again so that a new\nmultiperson authorization ticket is created with valid authorization data."
    },
    "9400": {
        "code": 9400,
        "desc": "The OData json is malformed.",
        "first_action": "PleasesubmitabugreportwiththeappropriateNetBackup",
        "full_action": "PleasesubmitabugreportwiththeappropriateNetBackup\nlogs, including the logs for the process where the error was encountered and the\nweb service logs."
    },
    "9401": {
        "code": 9401,
        "desc": "The OData filter criteria is invalid.",
        "first_action": "Use a valid OData filter.",
        "full_action": "Use a valid OData filter."
    },
    "9402": {
        "code": 9402,
        "desc": "An OData operator is not supported.",
        "first_action": "Use a valid OData operator in the OData filter. For OData",
        "full_action": "Use a valid OData operator in the OData filter. For OData\nsupport details, see the following article:\nhttp://www.veritas.com/docs/100043320"
    },
    "9403": {
        "code": 9403,
        "desc": "An OData entity data model (EDM) type is not supported.",
        "first_action": "Use a supported OData entity model (EDM) type in the",
        "full_action": "Use a supported OData entity model (EDM) type in the\nOData filter. See the following article:\nhttp://www.veritas.com/docs/100043320"
    },
    "9404": {
        "code": 9404,
        "desc": "An operand for an OData operator or method is invalid.",
        "first_action": "Use a valid operand in the OData filter.",
        "full_action": "Use a valid operand in the OData filter."
    },
    "9405": {
        "code": 9405,
        "desc": "An OData method is not supported.",
        "first_action": "Use a supported method in the OData filter. See the",
        "full_action": "Use a supported method in the OData filter. See the\nfollowing article:\nhttp://www.veritas.com/docs/100043320"
    },
    "9480": {
        "code": 9480,
        "desc": "The user profile with the given ID cannot be found.",
        "first_action": "Make sure the correct ID is specified when you use the",
        "full_action": "Make sure the correct ID is specified when you use the\nRESTful API."
    },
    "9481": {
        "code": 9481,
        "desc": "The user profile request cannot be processed.",
        "first_action": "CollectthewebservicelogsandcontactCohesityTechnical",
        "full_action": "CollectthewebservicelogsandcontactCohesityTechnical\nSupport."
    },
    "9482": {
        "code": 9482,
        "desc": "The user does not have permission to access the user profile with specified ID.",
        "first_action": "Make sure that the requester has the necessary RBAC",
        "full_action": "Make sure that the requester has the necessary RBAC\npermissions to fetch the user profile information of other users."
    },
    "9483": {
        "code": 9483,
        "desc": "The user does not have permission to update the user profile with specified ID.",
        "first_action": "Make sure that the requester has the necessary RBAC",
        "full_action": "Make sure that the requester has the necessary RBAC\npermissions to update the user profile information of other users."
    },
    "9484": {
        "code": 9484,
        "desc": "TheuserprofileIDspecifiedinrequestURLandpayloaddoesnotmatch.",
        "first_action": "Specify the same ID in the request URL and body when",
        "full_action": "Specify the same ID in the request URL and body when\nyou use the API to update the profile of a user with the specified ID."
    },
    "9490": {
        "code": 9490,
        "desc": "Failed to list the AD or the LDAP servers.",
        "first_action": "Retry the operation and review the logs in the following",
        "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "9491": {
        "code": 9491,
        "desc": "Failed to add the AD or the LDAP server.",
        "first_action": "Retry the operation and review the logs in the following",
        "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "9492": {
        "code": 9492,
        "desc": "Failed to delete the AD or the LDAP server.",
        "first_action": "Retry the operation and review the logs in the following",
        "full_action": "Retry the operation and review the logs in the following\ndirectory for more details.\nOn Windows: install_path\\NetBackup\\logs\\nbatd\nOn UNIX: /usr/openv/logs/nbatd\nFor more information, refer to the NetBackup Security and Encryption Guide. If the\nissuepersists,visittheCohesityTechnicalSupportwebsite.TheCohesityTechnical\nSupport website offers additional information to help you troubleshoot this issue."
    },
    "9509": {
        "code": 9509,
        "desc": "Failed to create email body using the template.",
        "first_action": "CollectthewebservicelogsandcontactCohesityTechnical",
        "full_action": "CollectthewebservicelogsandcontactCohesityTechnical\nSupport."
    },
    "9550": {
        "code": 9550,
        "desc": "Retry attempts were exhausted for NetBackup OpenStack VM.",
        "first_action": "Ensure the proper connectivity between the NetBackup host and NBOSVM",
        "full_action": "Perform the following as appropriate:\n■ Ensure the proper connectivity between the NetBackup host and NBOSVM\nserver.\n■ Ensure that the required ports on NBOSVM are open and accessible to the\nNetBackup hosts.\n■ Ensure that the NBOSVM server is registered properly with NetBackup."
    },
    "9551": {
        "code": 9551,
        "desc": "An internal server error has occurred during NetBackup OpenStack VM operation.",
        "first_action": "See the detailed error message on the NetBackup activity monitor.",
        "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ Check the status of the following services on all NBOSVM nodes:\n■ nbosjm-policies\n■ nbosjm-api\n■ nbosjm-scheduler\n■ nbosjm-cron\n■ See the nbosjm logs for more information."
    },
    "9552": {
        "code": 9552,
        "desc": "NetBackup OpenStack VM authentication failed.",
        "first_action": "Ensure that the NBOSVM server is registered properly with NetBackup.",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the NBOSVM server is registered properly with NetBackup.\n■ See the detailed error message on the NetBackup activity monitor.\n■ See the nbosjm logs for more information."
    },
    "9553": {
        "code": 9553,
        "desc": "NetBackup OpenStack VM backup API failed.",
        "first_action": "See the detailed error message on the NetBackup activity monitor.",
        "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ EnsurethatthesufficientdiskspaceisavailableonthetargetMSDPserverand\nuniversal share host."
    },
    "9554": {
        "code": 9554,
        "desc": "Invalid snapshot metadata.",
        "first_action": "See the nbosjm logs for more information.",
        "full_action": "Perform the following as appropriate:\nSee the nbosjm logs for more information."
    },
    "9555": {
        "code": 9555,
        "desc": "Failed to generate the NetBackup state file.",
        "first_action": "See the detailed error message on the NetBackup activity monitor.",
        "full_action": "Perform the following as appropriate:\n■ See the detailed error message on the NetBackup activity monitor.\n■ See the ncfnbcs logs for more information."
    },
    "9556": {
        "code": 9556,
        "desc": "Failed to fetch the snapshot ID.",
        "first_action": "See the ncfnbcs logs for more information.",
        "full_action": "Perform the following as appropriate:\nSee the ncfnbcs logs for more information."
    },
    "9600": {
        "code": 9600,
        "desc": "Unable to delete Asset group",
        "first_action": "Removetheassetgroupfromanyprotectionplantowhich",
        "full_action": "Removetheassetgroupfromanyprotectionplantowhich\nit belongs. Then, retry to delete the asset group."
    },
    "9616": {
        "code": 9616,
        "desc": "The migration process is in progress. The provided data may be inconsistent and incomplete. NetBackup status codes 1143 NetBackup status codes",
        "first_action": "The migration process may take some time. Wait for",
        "full_action": "The migration process may take some time. Wait for\nmigration to complete, then try the action again."
    },
    "9700": {
        "code": 9700,
        "desc": "Unable to create subscription. The asset is covered by the same protection plan.",
        "first_action": "Subscribe the same asset to different protection plan.",
        "full_action": "Subscribe the same asset to different protection plan.\nEnsure that the asset ID specified is correct or verify that the protection plan ID is\ncorrect."
    },
    "9701": {
        "code": 9701,
        "desc": "Cannot complete the operation because the protection plan currently protects an asset.",
        "first_action": "Unsubscribe all the assets that are subscribed to this",
        "full_action": "Unsubscribe all the assets that are subscribed to this\nprotection plan and try again. Also, ensure that the asset ID specified is correct or\nverify that the protection plan ID is correct."
    },
    "9702": {
        "code": 9702,
        "desc": "Thescheduleretentionissmallerthanorequaltotheschedulefrequency. This schedule issue may cause some data to be unprotected.",
        "first_action": "Edittheschedulesin theprotectionplantohaveretention",
        "full_action": "Edittheschedulesin theprotectionplantohaveretention\ngreater than the frequency. Then, retry creating the protection plan."
    },
    "9703": {
        "code": 9703,
        "desc": "The schedule must have a backup window and no overlap is allowed.",
        "first_action": "Ensure that each schedule has the same backup window",
        "full_action": "Ensure that each schedule has the same backup window\nand make corrections if there are any overlaps. Then, retry the protection plan\ncreation."
    },
    "9704": {
        "code": 9704,
        "desc": "The duplication retention period must be greater than the schedule frequency.",
        "first_action": "Edittheschedulewithduplicationtohaveretentiongreater",
        "full_action": "Edittheschedulewithduplicationtohaveretentiongreater\nthan the schedule frequency. Then, retry creating the protection plan."
    },
    "9705": {
        "code": 9705,
        "desc": "The PATCH request can only be used to update the description or the storage details of the protection plan.",
        "first_action": "Ensure that the PATCH request only has an update of the",
        "full_action": "Ensure that the PATCH request only has an update of the\ndescription or the storage details."
    },
    "9706": {
        "code": 9706,
        "desc": "A protection plan already exists with the same name. NetBackup status codes 1145 NetBackup status codes",
        "first_action": "The name of the protection plan should be unique and",
        "full_action": "The name of the protection plan should be unique and\ncannot be repeated. Retry the operation using a different name for the protection\nplan."
    },
    "9708": {
        "code": 9708,
        "desc": "A schedule must specify a backup storage and a duplication storage option. Replication must have a target master server and a target SLP. All storage options must be the same for all schedules.",
        "first_action": "Ensure consistency between all of the schedules with",
        "full_action": "Ensure consistency between all of the schedules with\nrespect to the storage options."
    },
    "9709": {
        "code": 9709,
        "desc": "Protection plan for snapshot storage must not have any duplication, replication, or storage options.",
        "first_action": "Create a protection plan without duplication, replication,",
        "full_action": "Create a protection plan without duplication, replication,\nand storage options for snapshot storage."
    },
    "9710": {
        "code": 9710,
        "desc": "Tape is not a supported storage option in a protection plan.",
        "first_action": "Create a protection plan with a supported storage type.",
        "full_action": "Create a protection plan with a supported storage type."
    },
    "9711": {
        "code": 9711,
        "desc": "Basic disk is not supported as part of SLP configuration.",
        "first_action": "Create a protection plan with a supported storage type.",
        "full_action": "Create a protection plan with a supported storage type."
    },
    "9712": {
        "code": 9712,
        "desc": "The update or create process did not complete. Invalid workload type.",
        "first_action": "Set the correct workload type and try to update or create",
        "full_action": "Set the correct workload type and try to update or create\nthe protection plan again."
    },
    "9713": {
        "code": 9713,
        "desc": "Unable to create subscription. Schedule list is missing.",
        "first_action": "Ensure that the protection plan is created with schedules.",
        "full_action": "Ensure that the protection plan is created with schedules."
    },
    "9714": {
        "code": 9714,
        "desc": "Unable to create subscription. Asset validation failed.",
        "first_action": "Ensure that the group or the asset that was subscribed",
        "full_action": "Ensure that the group or the asset that was subscribed\nto that protection plan exists. Verify the proper permissions for the asset or the\ngroup."
    },
    "9715": {
        "code": 9715,
        "desc": "Could not find asset or asset group details for the given ID.",
        "first_action": "Provide a valid asset or asset group ID and retry the",
        "full_action": "Provide a valid asset or asset group ID and retry the\noperation."
    },
    "9716": {
        "code": 9716,
        "desc": "Unable to create subscription. Cloud Asset provider generated ID is invalid.",
        "first_action": "Provide a valid cloud asset and retry the operation.",
        "full_action": "Provide a valid cloud asset and retry the operation."
    },
    "9717": {
        "code": 9717,
        "desc": "Unable to create subscription. No instance UUID found for the asset.",
        "first_action": "Provide a valid instance UUID for the asset and retry the",
        "full_action": "Provide a valid instance UUID for the asset and retry the\nprocess."
    },
    "9718": {
        "code": 9718,
        "desc": "Unable to create subscription. Invalid selection type specified.",
        "first_action": "Rerun the operation. If the problem persists, save all of",
        "full_action": "Rerun the operation. If the problem persists, save all of\nthe error log information and contact Cohesity Technical Support."
    },
    "9719": {
        "code": 9719,
        "desc": "The replication retention period must be greater than the schedule frequency.",
        "first_action": "Edittheschedulewithreplicationtohaveretentiongreater",
        "full_action": "Edittheschedulewithreplicationtohaveretentiongreater\nthan schedule frequency. Then, retry creating the protection plan."
    },
    "9720": {
        "code": 9720,
        "desc": "Cannot add or delete a schedule protection plan. Also, each schedule must specify storage attributes.",
        "first_action": "Verify whether valid storage units are included for each",
        "full_action": "Verify whether valid storage units are included for each\nof the selected operations (backup, replication, LTR). Adjust the protection plan\nstorage options to include valid options for backup, replication, and LTR."
    },
    "9722": {
        "code": 9722,
        "desc": "ID must be same in the request URL and the body.",
        "first_action": "Verify that you use the same protection ID in URL and",
        "full_action": "Verify that you use the same protection ID in URL and\nthe body."
    },
    "9723": {
        "code": 9723,
        "desc": "Cannot subscribe VMware asset to snapshot storage protection plan or cloud asset to non-snapshot storage protection plan.",
        "first_action": "Subscribe VMware asset to a non-snapshot storage",
        "full_action": "Subscribe VMware asset to a non-snapshot storage\nprotection plan or subscribe a cloud asset to a snapshot storage (cloud) protection\nplan."
    },
    "9724": {
        "code": 9724,
        "desc": "Unable to find the protection plan for the given ID.",
        "first_action": "ReviewtheprotectionplanIDandprovideavalidprotection",
        "full_action": "ReviewtheprotectionplanIDandprovideavalidprotection\nplan ID."
    },
    "9725": {
        "code": 9725,
        "desc": "The protection plan does not support the SLP operation that the policy uses.",
        "first_action": "Use supported SLP operation in policy.",
        "full_action": "Use supported SLP operation in policy."
    },
    "9726": {
        "code": 9726,
        "desc": "The protection plan does not support multiple copies within a schedule.",
        "first_action": "Use single copy in policy schedule.",
        "full_action": "Use single copy in policy schedule."
    },
    "9731": {
        "code": 9731,
        "desc": "Unable to find subscription for given ID.",
        "first_action": "Specify a valid protection plan ID.",
        "full_action": "Specify a valid protection plan ID."
    },
    "9732": {
        "code": 9732,
        "desc": "The cloud snapshot replication retention period must be greater than the schedule frequency.",
        "first_action": "Adjust the cloud snapshot replication retention period or",
        "full_action": "Adjust the cloud snapshot replication retention period or\nadjust the frequency in the schedule."
    },
    "9733": {
        "code": 9733,
        "desc": "Multi-target cloud snapshot replication is not supported.",
        "first_action": "Use the same replication target that is set for cloud",
        "full_action": "Use the same replication target that is set for cloud\nreplication."
    },
    "9734": {
        "code": 9734,
        "desc": "The cloud replication is not compatible with specified workload type.",
        "first_action": "Set cloud as workload type.",
        "full_action": "Set cloud as workload type."
    },
    "9735": {
        "code": 9735,
        "desc": "The assets must be the same workload type to add them to an existing protection plan.",
        "first_action": "Subscribe the asset or the asset group to a protection",
        "full_action": "Subscribe the asset or the asset group to a protection\nplan with the matching workload type."
    },
    "9736": {
        "code": 9736,
        "desc": "Frequency must be specified for frequency-based schedules and includeDatesmustbespecifiedforcalendar-basedschedules.Thesefieldscannot be specified simultaneously.",
        "first_action": "SpecifyexactlyoneoffrequencySecondsorincludeDates",
        "full_action": "SpecifyexactlyoneoffrequencySecondsorincludeDates\nattribute when you create or modify a protection plan or subscription."
    },
    "9737": {
        "code": 9737,
        "desc": "Schedule type must be specified for calendar-based schedules.",
        "first_action": "Specify the schedule type (appropriate for the workload)",
        "full_action": "Specify the schedule type (appropriate for the workload)\nfor the calendar-based schedule."
    },
    "9738": {
        "code": 9738,
        "desc": "Subscription edit is not allowed for Cloud workload type.",
        "first_action": "Set the allowSubscriptionEdit attribute to false for a",
        "full_action": "Set the allowSubscriptionEdit attribute to false for a\nprotection plan with workloadTypeCloud."
    },
    "9739": {
        "code": 9739,
        "desc": "PUT protection plan or subscription must provide the same inputs as POST. Both schedules and policy attributes must be supplied.",
        "first_action": "Supply all required fields for PUT",
        "full_action": "Supply all required fields for PUT\n/servicecatalog/slos/{sloId}/subscriptions/{subId} or PUT\n/servicecatalog/slos/{sloId}. The schedules and policyDefinition are\nrequired fields."
    },
    "9740": {
        "code": 9740,
        "desc": "The upgrade of this protection plan to NetBackup 8.2 or later produced a failure.",
        "first_action": "Creatingor deletinga subscriptiondoesnotwork untilthe",
        "full_action": "Creatingor deletinga subscriptiondoesnotwork untilthe\nprotection plan has been converted from an 8.2.1 protection plan. Normally, this\nconversion happens automatically. Wait for a few minutes, then retry the operation.\nIf the conversion is not successful, the process can be triggered immediately by\nretrieving the details of the protection plan by modifying the URL. Modify the URL\nin the NetBackup web UI to:\nhttps://<master_server>:1556/webui/protection-plans/{sloId}\nIf the failure is due to an intermittent problem when NetBackup policies or storage\nlifecycle policies (SLPs) are created, a retry may succeed.\nOtherwise,theoldprotectionplanmaybeunusable.Inthiscase,existingsubscribed\nasset protection is still active and backup jobs still run. Consider creating a new\nprotection plan and migrating the subscriptions to this new protection plan. The\ndefinition of the old ProtectionPlan is persisted in the NetBackup database.\nContact Cohesity Technical Support for assistance in retrieving the old protection\nplan definition."
    },
    "9741": {
        "code": 9741,
        "desc": "The protection plan updates partially succeeded.",
        "first_action": "Verify with backup administrator to ensure that the jobs",
        "full_action": "Verify with backup administrator to ensure that the jobs\n(created by SLPs) write to the correct storage unit. Run GET PP API to get the\ncorrect state. Retry the update operation with correct storage information."
    },
    "9743": {
        "code": 9743,
        "desc": "Multiple transaction log schedules found.",
        "first_action": "Retry the operation and if the issue persists, visit the",
        "full_action": "Retry the operation and if the issue persists, visit the\nCohesityTechnicalSupportwebsite.TheCohesityTechnicalSupportwebsiteoffers\nadditional information to help you troubleshoot this issue."
    },
    "9744": {
        "code": 9744,
        "desc": "The subscription contains one or more configuration entries that have not been delegated to this user.",
        "first_action": "Based on the contents of the error payload, identify the",
        "full_action": "Based on the contents of the error payload, identify the\nconfigurationentriesthathavenotbeendelegatedtothesubscribinguser.Remove\nthose entries from the subscription payload, and retry the request. If the subscriber\ncannot use the protection plan without changes, they may request delegation of\nadditional subscription customization capabilities on that protection plan. If none of\nthe delegation rules contain the necessary attributes, an administrator with the\nCREATE operation on the PROTECTION_PLAN namespace must create a protection\nplan with appropriate protection customizations."
    },
    "9745": {
        "code": 9745,
        "desc": "A subscription cannot delete inherited protection plan schedules.",
        "first_action": "Whenattemptingtocustomizescheduling,ensurethatall",
        "full_action": "Whenattemptingtocustomizescheduling,ensurethatall\nof the schedules from the protection plan are represented in the schedule payload.\nIf not attempting to customize schedules, do not include the schedule section of\nthe payload. If the subscriber cannot use the schedules that are inherited from the\nprotectionplan,anadministratorwiththeCREATEoperationonthePROTECTION_PLAN\nnamespace must create a protection plan with appropriate schedules."
    },
    "9746": {
        "code": 9746,
        "desc": "A subscription cannot add schedules.",
        "first_action": "Ifthesubscribercannotusetheschedulesthatareinherited",
        "full_action": "Ifthesubscribercannotusetheschedulesthatareinherited\nfrom the protection plan, an administrator with the CREATE operation on the\nPROTECTION_PLAN namespace must create a protection plan with appropriate\nschedules."
    },
    "9747": {
        "code": 9747,
        "desc": "At least one subscription schedule does not supply the scheduleName field that is required to identify the protection plan schedule being edited.",
        "first_action": "Review the subscription schedule payload, and ensure",
        "full_action": "Review the subscription schedule payload, and ensure\nthat all scheduleName fields are populated with the name of the schedule to which\nthe edit applies."
    },
    "9748": {
        "code": 9748,
        "desc": "CannotsubscribeorbackupMicrosoftSQLServeravailabilitygroupwith the protection plan because of incorrect policy options.",
        "first_action": "Select the Availability database backup preference",
        "full_action": "Select the Availability database backup preference\noption in the protection plan. In combination with that option, you can select the\nProtect primary replica option or the Protect preferred replica option."
    },
    "9749": {
        "code": 9749,
        "desc": "Cannot subscribe or backup Microsoft SQL Server availability group database with the protection plan because of incorrect policy options.",
        "first_action": "Clear the selection of the Availability database backup preference option.",
        "full_action": "Intheprotectionplan,performoneofthefollowingoptions:\n■ Clear the selection of the Availability database backup preference option.\n■ Select the Availability database backup preference option and the Protect\nprimary replica option for the protection plan.\n■ Select the Availability database backup preference option and the Protect\npreferred replica option for the protection plan."
    },
    "9751": {
        "code": 9751,
        "desc": "The update or create process did not complete due to an invalid cloud provider type.",
        "first_action": "Set the correct cloud provider type and try to update or",
        "full_action": "Set the correct cloud provider type and try to update or\ncreate the protection plan again."
    },
    "9752": {
        "code": 9752,
        "desc": "The cloud assets must be the same cloud provider type to add them to an existing protection plan.",
        "first_action": "Subscribe the asset or the asset group to a protection",
        "full_action": "Subscribe the asset or the asset group to a protection\nplan with the matching cloud provider type."
    },
    "9760": {
        "code": 9760,
        "desc": "A protection plan that has enabled the disk exclusion option can only be applied to the cloud VM type assets.",
        "first_action": "Make sure that you apply a protection plan with disk",
        "full_action": "Make sure that you apply a protection plan with disk\nexclusion option to the VM (host type) assets only."
    },
    "9764": {
        "code": 9764,
        "desc": "Backup from snapshot operation is supported on the NetBackup media server 10.0 and later versions.",
        "first_action": "10.0, you must upgrade that media server.",
        "full_action": "To run the backup from snapshot, verify that the media\nserver’s latest version is 10.0 or newer. If the media server's version is older than\n10.0, you must upgrade that media server."
    },
    "9765": {
        "code": 9765,
        "desc": "YoucansubscribeorbackuponlycloudPaaSassetsusingaprotection plan with primary backup operation.",
        "first_action": "Subscribe a PaaS protection plan only to PaaS assets.",
        "full_action": "Subscribe a PaaS protection plan only to PaaS assets."
    },
    "9766": {
        "code": 9766,
        "desc": "Protection plan with backup storage is not supported with provided operations like replication, backup from snapshot, and cloud index.",
        "first_action": "Create a protection plan with a backup storage unit or",
        "full_action": "Create a protection plan with a backup storage unit or\nwith duplication enabled."
    },
    "9767": {
        "code": 9767,
        "desc": "Schedules having no backup storage unit does not support provided policy attributes.",
        "first_action": "A protection plan with a staging storage path PaaS",
        "full_action": "A protection plan with a staging storage path PaaS\nprotection flag must have backup storage configured in the schedule."
    },
    "9768": {
        "code": 9768,
        "desc": "Schedules having backup storage units must have PaaS protection enabled with an explicit staging storage path.",
        "first_action": "Create a PaaS protection enabled protection plan by",
        "full_action": "Create a PaaS protection enabled protection plan by\nspecifying a staging storage path and PaaS protection flag along with backup\nstorage in the schedule."
    },
    "9769": {
        "code": 9769,
        "desc": "MSDP instant access enabled storage is the only supported storage option for a protection plan.",
        "first_action": "Provide an MSDP storage with instant access enabled in",
        "full_action": "Provide an MSDP storage with instant access enabled in\nthe protection plan."
    },
    "9770": {
        "code": 9770,
        "desc": "Associate credentials with the asset or the parent asset to subscribe it to a PaaS protection plan.",
        "first_action": "AddcredentialstotheassetoritsparentusingCredential",
        "full_action": "AddcredentialstotheassetoritsparentusingCredential\nmanagement option."
    },
    "9771": {
        "code": 9771,
        "desc": "Cannot subscribe the PaaS assets with multi-byte characters in the displaynamestotheprotectionplanbecausetheyarenotsupportedontheprimary servers running Windows.",
        "first_action": "ThePaaSassetswithmulti-byteornon-Englishcharacters",
        "full_action": "ThePaaSassetswithmulti-byteornon-Englishcharacters\nin the display name must be backed up and restored using a Linux primary server."
    },
    "9773": {
        "code": 9773,
        "desc": "Thestorageserverversionisnotsupported.Minimumsupportedversion is 10.1.",
        "first_action": "Select a storage server with NetBackup version 10.1 or",
        "full_action": "Select a storage server with NetBackup version 10.1 or\nlater."
    },
    "9778": {
        "code": 9778,
        "desc": "Cannot subscribe the PaaS asset to the protection plan that supports differential incremental backup.",
        "first_action": "Verify that the DBPaaS asset supports differential",
        "full_action": "Verify that the DBPaaS asset supports differential\nincremental backup. If the DBPaaS asset does not, you must create a protection\nplan that does not have a differential incremental schedule type. Then subscribe\nthe asset to the new protection plan."
    },
    "9781": {
        "code": 9781,
        "desc": "InvalidpolicyattributeswereprovidedfortheOpenStackprotectionplan.",
        "first_action": "Configure the OpenStack protection plan with valid policy attributes.",
        "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with valid policy attributes."
    },
    "9783": {
        "code": 9783,
        "desc": "Schedules that have the backup storage units configured are not supported for the OpenStack protection plan.",
        "first_action": "ConfiguretheOpenStackprotectionplanwiththeschedulesthatdonothavebackup",
        "full_action": "Perform the following as appropriate:\nConfiguretheOpenStackprotectionplanwiththeschedulesthatdonothavebackup\nstorage units."
    },
    "9784": {
        "code": 9784,
        "desc": "Schedules that have the storage units configured must have the staging storage path and mount path.",
        "first_action": "OpenStackprotectionplanisconfiguredwiththeschedulesthathavestorageunits",
        "full_action": "Perform the following as appropriate:\nOpenStackprotectionplanisconfiguredwiththeschedulesthathavestorageunits\nconfigured but do not have the staging storage path or mount path."
    },
    "9785": {
        "code": 9785,
        "desc": "OpenStack protection is not supported for universal share with SMB protocol.",
        "first_action": "Configure the OpenStack protection plan with the supported universal share only.",
        "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with the supported universal share only."
    },
    "9786": {
        "code": 9786,
        "desc": "Theprovidedstagingpathisnotmountedontheselectedbackupstorage.",
        "first_action": "Ensure that the staging path that was provided to create the OpenStack",
        "full_action": "Perform the following as appropriate:\n■ Ensure that the staging path that was provided to create the OpenStack\nprotection plan gets mounted on the selected backup storage.\n■ Ensure that the backup storage is mentioned in the universal share host list.\n■ Ensure that the backup storage has the required permissions to access and\nmount the staging path on itself."
    },
    "9787": {
        "code": 9787,
        "desc": "The provided mount path does not match with the staging storage path.",
        "first_action": "Configure the OpenStack protection plan with the valid mount path and staging",
        "full_action": "Perform the following as appropriate:\nConfigure the OpenStack protection plan with the valid mount path and staging\nstorage path."
    },
    "9788": {
        "code": 9788,
        "desc": "Unsupported storage server version for OpenStack.",
        "first_action": "Ensure that the storage server version is 11.1.0.2 or later.",
        "full_action": "Perform the following as appropriate:\nEnsure that the storage server version is 11.1.0.2 or later."
    },
    "9789": {
        "code": 9789,
        "desc": "Cannot subscribe the PaaS asset to the protection plan that supports Archive redo logs backup.",
        "first_action": "To subscribe the asset to the protection plan, remove the",
        "full_action": "To subscribe the asset to the protection plan, remove the\narchive redo logs schedule from the protection plan."
    },
    "9794": {
        "code": 9794,
        "desc": "Cannot subscribe the selected PaaS assets to this protection plan, as the assets are already subscribed to a protection plan with an incremental backup schedule.",
        "first_action": "Remove the asset from previously subscribed protection",
        "full_action": "Remove the asset from previously subscribed protection\nplans with incremental backup schedules."
    },
    "9795": {
        "code": 9795,
        "desc": "Cannot subscribe to this protection plan as this plan cannot protect archive log backup type with a frequency of less than 24 hours.",
        "first_action": "Create a protection plan with the archive log backup type",
        "full_action": "Create a protection plan with the archive log backup type\nwith a backup frequency of less than 24 hours."
    },
    "9796": {
        "code": 9796,
        "desc": "Cannot subscribe the PaaS asset to the protection plan as the plan supports differential incremental and archive redo logs backup.",
        "first_action": "Create a protection plan with a full backup schedule.",
        "full_action": "Create a protection plan with a full backup schedule."
    },
    "9800": {
        "code": 9800,
        "desc": "Snapshot Manager is not configured.",
        "first_action": "Configure the Snapshot Manager from the NetBackup",
        "full_action": "Configure the Snapshot Manager from the NetBackup\nAdministration Console or use the tpconfig CLI.\nIf the Snapshot Manager is already configured, ensure that the registration entry\nis in the NetBackup database. Use the NetBackup Administration Console or\nrun the tpconfig utility."
    },
    "9801": {
        "code": 9801,
        "desc": "Snapshot Manager login failed.",
        "first_action": "Update the credentials and port number in NetBackup.",
        "full_action": "Dependingonthecause,performonethefollowingtasks:\n■ Update the credentials and port number in NetBackup.\n■ Ensure that the Snapshot Manager is up and reachable on the network from\nthe NetBackup master server.\nTo verify, log on to the Snapshot Manager host from the master server browser."
    },
    "9802": {
        "code": 9802,
        "desc": "Failed to retrieve the supported plug-in list from the Snapshot Manager.",
        "first_action": "Verify if the connection with the Snapshot Manager is up.",
        "full_action": "Verify if the connection with the Snapshot Manager is up."
    },
    "9803": {
        "code": 9803,
        "desc": "Failed to retrieve the NetBackup supported plug-in list.",
        "first_action": "Verify the connection with the master server.",
        "full_action": "Verify the connection with the master server."
    },
    "9804": {
        "code": 9804,
        "desc": "The plug-in is not configured for the cloud provider.",
        "first_action": "Configure the required plug-in with NetBackup.",
        "full_action": "Configure the required plug-in with NetBackup."
    },
    "9805": {
        "code": 9805,
        "desc": "The specified configuration instance was not found.",
        "first_action": "Specify the correct instance ID.",
        "full_action": "Specify the correct instance ID."
    },
    "9806": {
        "code": 9806,
        "desc": "A configuration instance with the same configuration details already exists.",
        "first_action": "Either use the same configuration instance or create a",
        "full_action": "Either use the same configuration instance or create a\nnew configuration instance with different details."
    },
    "9807": {
        "code": 9807,
        "desc": "Internal server error.",
        "first_action": "Verify Snapshot Manager logs.",
        "full_action": "Verify Snapshot Manager logs."
    },
    "9808": {
        "code": 9808,
        "desc": "The plug-in type is not supported.",
        "first_action": "Verify that the plug-in is on the NetBackup supported",
        "full_action": "Verify that the plug-in is on the NetBackup supported\nplug-ins list. You can find more information about supported plug-ins on Cohesity\nServices and Operations Readiness Tools (SORT) ."
    },
    "9809": {
        "code": 9809,
        "desc": "Plugin instance name already exists.",
        "first_action": "Specify a different identifier.",
        "full_action": "Specify a different identifier."
    },
    "9810": {
        "code": 9810,
        "desc": "Failed to configure the plug-in instance in Snapshot Manager.",
        "first_action": "See the nbemm logs on the NetBackup master server.",
        "full_action": "See the nbemm logs on the NetBackup master server."
    },
    "9811": {
        "code": 9811,
        "desc": "Failed to register the plug-in instance in NetBackup.",
        "first_action": "Ensure that the CloudPoint_plugin.conf accessible",
        "full_action": "Ensure that the CloudPoint_plugin.conf accessible\nand retry the operation."
    },
    "9812": {
        "code": 9812,
        "desc": "Failedtoretrievetheconfiguredplug-ininstancefromSnapshotManager.",
        "first_action": "Update the Snapshot Manager using the existing",
        "full_action": "Update the Snapshot Manager using the existing\ncredentials."
    },
    "9813": {
        "code": 9813,
        "desc": "Failed to retrieve the configured plug-in instance from NetBackup.",
        "first_action": "Retry the operation again.",
        "full_action": "Retry the operation again."
    },
    "9814": {
        "code": 9814,
        "desc": "The instance type for the specified configured plug-in does not match with the instance type entry in NetBackup.",
        "first_action": "Verifytheinstancetypeentryandupdatetheplug-inagain.",
        "full_action": "Verifytheinstancetypeentryandupdatetheplug-inagain."
    },
    "9815": {
        "code": 9815,
        "desc": "Failed to modify the configured plug-in instance in Snapshot Manager.",
        "first_action": "Verify the Snapshot Manager logs.",
        "full_action": "Verify the Snapshot Manager logs."
    },
    "9816": {
        "code": 9816,
        "desc": "Failedtoretrievetheconfiguredplug-ininstancefromSnapshotManager.",
        "first_action": "Ensure that the Snapshot Manager is up or verify the",
        "full_action": "Ensure that the Snapshot Manager is up or verify the\nSnapshot Manager logs."
    },
    "9818": {
        "code": 9818,
        "desc": "SnapshotManageronwhichthespecifiedplug-ininstancewasconfigured is not available.",
        "first_action": "Ensure that the Snapshot Manager that hosts the plug-in",
        "full_action": "Ensure that the Snapshot Manager that hosts the plug-in\ninstance is registered in NetBackup."
    },
    "9819": {
        "code": 9819,
        "desc": "A Snapshot Manager on which plug-in instances with specified plug-in type are configured is not available.",
        "first_action": "EnsurethatalloftheSnapshotManagersthatcontainthe",
        "full_action": "EnsurethatalloftheSnapshotManagersthatcontainthe\nplug-in instances are registered in NetBackup."
    },
    "9820": {
        "code": 9820,
        "desc": "Failed to disable the plug-in instance.",
        "first_action": "Verify if the CloudPoint_plugin.conf is updated.",
        "full_action": "Verify if the CloudPoint_plugin.conf is updated."
    },
    "9821": {
        "code": 9821,
        "desc": "Specified plug-in instance does not exist on the Snapshot Manager.",
        "first_action": "Retry the operation and save all of the error information.",
        "full_action": "Retry the operation and save all of the error information.\nIf the issue persists, visit support.veritas.com. The Cohesity Technical Support\nwebsite site offers additional information to help you troubleshoot this issue."
    },
    "9822": {
        "code": 9822,
        "desc": "Plug-in instance already exists in the Snapshot Manager. NetBackup status codes 1169 NetBackup status codes",
        "first_action": "Change the configuration attributes. For example, if it is",
        "full_action": "Change the configuration attributes. For example, if it is\nan Amazon AWS plug-in configuration, ensure that the specified region is not\nincluded in any of the existing AWS plug-in configurations that have the same\naccess key. If a region is already specified in a plug-in, its assets are already\nprotected."
    },
    "9823": {
        "code": 9823,
        "desc": "Plug-in authentication failed. Credentials are invalid.",
        "first_action": "Verify that the credentials are correct and perform the",
        "full_action": "Verify that the credentials are correct and perform the\noperation again.\nEnsure that you enable the preferred regions for the account that is linked to the\nSnapshot Manager instance that is deployed on AWS."
    },
    "9830": {
        "code": 9830,
        "desc": "Operation not supported. The associated Snapshot Manager is on an older version.",
        "first_action": "Upgrade the Snapshot Manager server to a supported",
        "full_action": "Upgrade the Snapshot Manager server to a supported\nversion equal to the NetBackup primary server version."
    },
    "9833": {
        "code": 9833,
        "desc": "NetBackup cannot connect to the virtual machine.",
        "first_action": "ReviewtheNetBackupnbwebserviceandthenbemmlogs.",
        "full_action": "ReviewtheNetBackupnbwebserviceandthenbemmlogs."
    },
    "9834": {
        "code": 9834,
        "desc": "The specified asset is not found in the Snapshot Manager database.",
        "first_action": "To verify the deleted assets, refer to the last discovered",
        "full_action": "To verify the deleted assets, refer to the last discovered\ntime."
    },
    "9835": {
        "code": 9835,
        "desc": "Application configuration operation failed.",
        "first_action": "Review the NetBackup nbwebservice and nbemm logs.",
        "full_action": "Review the NetBackup nbwebservice and nbemm logs."
    },
    "9836": {
        "code": 9836,
        "desc": "Application already configured on the Snapshot Manager.",
        "first_action": "Skip the operation.",
        "full_action": "Skip the operation."
    },
    "9837": {
        "code": 9837,
        "desc": "Configure application operation has failed from NetBackup.",
        "first_action": "Review the NetBackup nbwebservice and nbemm logs.",
        "full_action": "Review the NetBackup nbwebservice and nbemm logs."
    },
    "9838": {
        "code": 9838,
        "desc": "The specified operation is not supported with the current Snapshot Manager license in use.",
        "first_action": "Apply a license with the appropriate privileges.",
        "full_action": "Apply a license with the appropriate privileges."
    },
    "9839": {
        "code": 9839,
        "desc": "The origiasset is deleted. Only snapshot of the asset is available.",
        "first_action": "Recover the asset from the snapshot.",
        "full_action": "Recover the asset from the snapshot."
    },
    "9841": {
        "code": 9841,
        "desc": "The Snapshot Manager host name does not match with the associated Snapshot Manager.",
        "first_action": "Verify if the Snapshot Manager host name is configured",
        "full_action": "Verify if the Snapshot Manager host name is configured\ncorrectly."
    },
    "9842": {
        "code": 9842,
        "desc": "The virtual machine is already connected.",
        "first_action": "Thevirtualmachineisalreadyconnected,youcanproceed",
        "full_action": "Thevirtualmachineisalreadyconnected,youcanproceed\nwith application configuration."
    },
    "9843": {
        "code": 9843,
        "desc": "Unable to retrieve virtual machine details.",
        "first_action": "Refer to the Snapshot Manager logs.",
        "full_action": "Refer to the Snapshot Manager logs."
    },
    "9844": {
        "code": 9844,
        "desc": "Unable to retrieve the application details.",
        "first_action": "Refer to the Snapshot Manager logs.",
        "full_action": "Refer to the Snapshot Manager logs."
    },
    "9845": {
        "code": 9845,
        "desc": "Failed to deploy the snapshot agent on the Windows host.",
        "first_action": "DeploytheWindowshostmanually.RefertotheSnapshot",
        "full_action": "DeploytheWindowshostmanually.RefertotheSnapshot\nManager documentation in the NetBackup Snapshot Client Administrator’s Guide."
    },
    "9846": {
        "code": 9846,
        "desc": "Failed to update the asset information in the database.",
        "first_action": "Restart the nbwebservice and retry the operation.",
        "full_action": "Restart the nbwebservice and retry the operation."
    },
    "9847": {
        "code": 9847,
        "desc": "Failed to retrieve cloud asset type. NetBackup status codes 1173 NetBackup status codes",
        "first_action": "Retry the operation.",
        "full_action": "Retry the operation."
    },
    "9848": {
        "code": 9848,
        "desc": "Invalid Cloud asset type.",
        "first_action": "Verify the ncfnbcs logs.",
        "full_action": "Verify the ncfnbcs logs."
    },
    "9849": {
        "code": 9849,
        "desc": "Invalid virtual machine credentials.",
        "first_action": "Verify the virtual machine credentials and provide correct",
        "full_action": "Verify the virtual machine credentials and provide correct\ncredentials."
    },
    "9850": {
        "code": 9850,
        "desc": "The specified application is not supported with the host’s operating system.",
        "first_action": "Review the Snapshot Manager host’s operating system",
        "full_action": "Review the Snapshot Manager host’s operating system\nand compare it to the NetBackup Compatibility List."
    },
    "9851": {
        "code": 9851,
        "desc": "For plug-ins configured directly with NetBackup, the original instance name and specified plug-in ID must be same.",
        "first_action": "IftheIDisdifferent,youcanupdatealltheotherparameters",
        "full_action": "IftheIDisdifferent,youcanupdatealltheotherparameters\napart from the ID. NetBackup does not support updates to the ID."
    },
    "9853": {
        "code": 9853,
        "desc": "Invalid copy type.",
        "first_action": "Iftheproblempersists,contactCohesityTechnicalSupport.",
        "full_action": "Iftheproblempersists,contactCohesityTechnicalSupport."
    },
    "9854": {
        "code": 9854,
        "desc": "Cloud snapshot replication failed.",
        "first_action": "If you try to replicate a copy of an EC2 instance, create a new key-pair in the",
        "full_action": "Perform the following as appropriate:\n■ If you try to replicate a copy of an EC2 instance, create a new key-pair in the\ndestination region. The new key-pair must be consistent with the key-pair in the\nsource region.\n■ Refer to the ncfnbcs logs on the media server for more information."
    },
    "9855": {
        "code": 9855,
        "desc": "Snapshot export failed.",
        "first_action": "Refertothebpfis logson theclientor thealternateclient",
        "full_action": "Refertothebpfis logson theclientor thealternateclient\nfor more information.\nFor cloud backups, review the NCFNBCS logs on the media server for relevant\ninformation."
    },
    "9856": {
        "code": 9856,
        "desc": "Failed to parse JSON response from Snapshot Manager.",
        "first_action": "Manually clean up the operation-specific copy from the",
        "full_action": "Manually clean up the operation-specific copy from the\ncloud."
    },
    "9857": {
        "code": 9857,
        "desc": "Failed to start indexing of snapshot.",
        "first_action": "Refer to the ncfnbcs logs on the media server and the",
        "full_action": "Refer to the ncfnbcs logs on the media server and the\nSnapshot Manager logs."
    },
    "9858": {
        "code": 9858,
        "desc": "Failed to add NetBackup Snapshot Manager.",
        "first_action": "Review your network connectivity with Snapshot Manager.",
        "full_action": "Try one of the following as appropriate:\n■ Review your network connectivity with Snapshot Manager.\n■ Resolve any network issues with netstat or similar network diagnosis tool."
    },
    "9859": {
        "code": 9859,
        "desc": "Failed to retrieve the Mount Path.",
        "first_action": "Retry the snapshot operation again. If it still fails, refer to",
        "full_action": "Retry the snapshot operation again. If it still fails, refer to\nthe Snapshot Manager logs."
    },
    "9860": {
        "code": 9860,
        "desc": "Invalid Cloud FS Mount Path.",
        "first_action": "Review the mounted file system path on the target host",
        "full_action": "Review the mounted file system path on the target host\nand try to launch the snapshot operation again. If it still fails, refer to the Snapshot\nManager logs."
    },
    "9861": {
        "code": 9861,
        "desc": "Snapshot Manager is already added to a NetBackup master server.",
        "first_action": "Deploy and add a new Snapshot Manager.",
        "full_action": "Deploy and add a new Snapshot Manager."
    },
    "9862": {
        "code": 9862,
        "desc": "Failed to get CA certificate for Snapshot Manager.",
        "first_action": "Check your network connectivity with the Snapshot Manager.",
        "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager.\n■ Resolve any network issues with netstat or similar network diagnosis tool."
    },
    "9863": {
        "code": 9863,
        "desc": "Failed to save CA certificate for Snapshot Manager.",
        "first_action": "Confirm the correct permissions for the NetBackup certificate store",
        "full_action": "Try one of the following as appropriate:\n■ Confirm the correct permissions for the NetBackup certificate store\n(/usr/openv/var/global/cloudpoint).\n■ Check the format of Snapshot Manager certificate using the\n/config/snapshot-mgmt-servers-cacerts/{snapshotMgmtServer}/ports/{port}\nAPI.\n■ Only pem format is supported.\n■ Add or modify the Snapshot Manager configuration using the tpconfig\ncommand. Run the tpconfig command as a root user. This action re-assigns\nthe ownership of the root certificate path or the certificate file to the NetBackup\nservice user."
    },
    "9865": {
        "code": 9865,
        "desc": "NetBackup media server platform should be either Red Hat Enterprise Linux, SUSE Linux Enterprise Server, or Microsoft Windows to be associated with a Snapshot Manager.",
        "first_action": "Use SUSE Linux Enterprise Server, Microsoft Windows,",
        "full_action": "Use SUSE Linux Enterprise Server, Microsoft Windows,\nandRHELplatformonly,toassociatethemediaserverwiththeSnapshotManager."
    },
    "9866": {
        "code": 9866,
        "desc": "The NetBackup host certificate that is provided to Snapshot Manager is not valid or does not exist.",
        "first_action": "Review the nbcs/bpfis/bppfi level error messages that are displayed in Job",
        "full_action": "Try one of the following as appropriate:\n■ Review the nbcs/bpfis/bppfi level error messages that are displayed in Job\ndetails on the Activity monitor. For more details, review the component logs.\n■ Reviewthenbwebservice/nbemmlevelerrormessagefortheSnapshotManager\nand plug-in configuration. For more details, review the component logs.\n■ Review the NetBackup error codes or messages appearing in the previously\nspecified logs. These logs can provide additional insight into the actual SSL\ncertificate issue or connectivity issues between primary server and Snapshot\nManager."
    },
    "9867": {
        "code": 9867,
        "desc": "The ECA_TRUST_STORE_PATH option is not configured, or the certificate path is not accessible or doesn’t exist. NetBackup status codes 1179 NetBackup status codes",
        "first_action": "Check if the ECA_TRUST_STORE_PATH is configured correctly.",
        "full_action": "Try one of the following as appropriate:\n■ Check if the ECA_TRUST_STORE_PATH is configured correctly.\n■ Review all access rights of certificate path are correct."
    },
    "9868": {
        "code": 9868,
        "desc": "Failed to get API version for Snapshot Manager.",
        "first_action": "Check your network connectivity with the Snapshot Manager and review the",
        "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager and review the\nSnapshot Manager credentials you used to connect.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ Update the Snapshot Manager credentials using the Edit Server option."
    },
    "9869": {
        "code": 9869,
        "desc": "Failed to get Deployment Summary for Snapshot Manager.",
        "first_action": "Check your network connectivity with the Snapshot Manager, NetBackup, and",
        "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with the Snapshot Manager, NetBackup, and\ncloud provider.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ ReviewandupdatetheSnapshotManagercredentialsusingEditServeroption.\n■ Review and update the cloud provider credentials or secret key."
    },
    "9870": {
        "code": 9870,
        "desc": "Failed to get version for Snapshot Manager.",
        "first_action": "Check your network connectivity with Snapshot Manager and NetBackup.",
        "full_action": "Try one of the following as appropriate:\n■ Check your network connectivity with Snapshot Manager and NetBackup.\n■ Resolve any network issues with netstat or similar network diagnosis tool.\n■ ReviewandupdateSnapshotManagercredentialsusingtheEditServeroption."
    },
    "9871": {
        "code": 9871,
        "desc": "Operationnotsupported.ThespecifiedmediaservermustbeNetBackup version 8.3 or later.",
        "first_action": "Select a media server of NetBackup version 8.3 or later",
        "full_action": "Select a media server of NetBackup version 8.3 or later\nto associate with Snapshot Manager."
    },
    "9872": {
        "code": 9872,
        "desc": "Unable to retrieve the Snapshot Manager on-host agent token details.",
        "first_action": "Refer to the nbwebservice and Snapshot Manager log",
        "full_action": "Refer to the nbwebservice and Snapshot Manager log\nand ensure that all Snapshot Manager services are running."
    },
    "9873": {
        "code": 9873,
        "desc": "The Snapshot Manager is disabled.",
        "first_action": "Check for any underlying maintenance issues that are",
        "full_action": "Check for any underlying maintenance issues that are\nrelated to the disabled Snapshot Manager. If there are any maintenance issues,\nyou must resolve these issues.\nIf there are no maintenance issues, perform the following:\n1 Log on to NetBackup web UI.\n2 On the left, click Cloud and then select the Snapshot Manager tab.\n3 Select the appropriate Snapshot Manager.\n4 In the Actions menu on the right, click the Enable option.\n5 Verifythatthediscoveryprocessistriggeredandthatitcompletessuccessfully.\n6 After the Snapshot Manager is enabled, run the operation again."
    },
    "9874": {
        "code": 9874,
        "desc": "Thissnapshotisnotindexed.GRToperationsonnon-indexedsnapshots are not supported.",
        "first_action": "Select a recovery point that is indexed and retry the",
        "full_action": "Select a recovery point that is indexed and retry the\noperation."
    },
    "9876": {
        "code": 9876,
        "desc": "Failed to disconnect VM from Snapshot Manager.",
        "first_action": "Refer to the nbwebservice and Snapshot Manager logs.",
        "full_action": "Refer to the nbwebservice and Snapshot Manager logs.\nEnsure that all the Snapshot Manager services are running."
    },
    "9877": {
        "code": 9877,
        "desc": "Failed to remove application from the Snapshot Manager.",
        "first_action": "Refer to the nbwebservice and Snapshot Manager logs.",
        "full_action": "Refer to the nbwebservice and Snapshot Manager logs.\nEnsure that all the Snapshot Manager services are running."
    },
    "9878": {
        "code": 9878,
        "desc": "The Unconfigure application API failed due to a discovery was not performed after the application API was configured.",
        "first_action": "Manually start the discovery on the Snapshot Manager",
        "full_action": "Manually start the discovery on the Snapshot Manager\nor wait for the scheduled discovery operation to complete."
    },
    "9879": {
        "code": 9879,
        "desc": "Failed to unconfigure the application as it has active snapshots.",
        "first_action": "Refer to the nbwebservice and Snapshot Manager log",
        "full_action": "Refer to the nbwebservice and Snapshot Manager log\nand ensure that all Snapshot Manager services are running."
    },
    "9882": {
        "code": 9882,
        "desc": "Failed to create disks selection file during volume restore operation.",
        "first_action": "Ensure that all NetBackup services are running and try",
        "full_action": "Ensure that all NetBackup services are running and try\nthe operation again."
    },
    "9883": {
        "code": 9883,
        "desc": "Failed to retrieve disks selection information during volume restore operation.",
        "first_action": "Ensure that all NetBackup services are running and try",
        "full_action": "Ensure that all NetBackup services are running and try\nthe operation again."
    },
    "9884": {
        "code": 9884,
        "desc": "Snapshot Manager server fails to retrieve the specified cloud domains, against the specified plug-in instance.",
        "first_action": "EnsurethattheNetBackupservicesandSnapshotManager",
        "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nserver containers are running. Check connectivity between the NetBackup primary\nserver, the Snapshot Manager server, and the cloud service provider. Retry the\noperation again."
    },
    "9886": {
        "code": 9886,
        "desc": "Snapshot Manager server fails to retrieve the specified cloud domain attributes, against the specified plug-in instance.",
        "first_action": "EnsurethattheNetBackupservicesandSnapshotManager",
        "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\ncontainers are running. Confirm the connectivity between the NetBackup primary\nserver, the Snapshot Manager server, and the cloud service provider. Retry the\noperation."
    },
    "9888": {
        "code": 9888,
        "desc": "Cannot access Snapshot Manager extensions from the Snapshot Manager.",
        "first_action": "Ensure that the NetBackup services and the Snapshot",
        "full_action": "Ensure that the NetBackup services and the Snapshot\nManager containers are running. Check the connectivity between the NetBackup\nmaster server, the Snapshot Manager, and the cloud service provider. Retry the\noperation again."
    },
    "9890": {
        "code": 9890,
        "desc": "Failed to update capability of Snapshot Manager in NetBackup server.",
        "first_action": "EnsurethattheNetBackupservicesandSnapshotManager",
        "full_action": "EnsurethattheNetBackupservicesandSnapshotManager\nare running. Check the connectivity between the NetBackup master server, the\nSnapshot Manager, and the cloud service provider. Retry the operation again."
    },
    "9891": {
        "code": 9891,
        "desc": "FailedtoupdateSnapshotManagerextensionsfromSnapshotManager.",
        "first_action": "Ensure that the NetBackup services and the Snapshot",
        "full_action": "Ensure that the NetBackup services and the Snapshot\nManagercontainersarerunning.CheckconnectivitybetweentheNetBackupmaster\nserver, the Snapshot Manager, and the cloud service provider. Retry the operation\nagain."
    },
    "9894": {
        "code": 9894,
        "desc": "Cannot retrieve plug-in details for the agent.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue."
    },
    "9895": {
        "code": 9895,
        "desc": "Cannot retrieve configuration details of the plug-in.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com.TheCohesitySupportsiteoffersadditionalinformationtohelp\nyou troubleshoot this issue."
    },
    "9896": {
        "code": 9896,
        "desc": "FailedtoaddNetBackupSnapshotManagerduetocertificategeneration failure.",
        "first_action": "Review the NetBackup nbemm logs to identify the exact error.",
        "full_action": "Perform one or more of the following actions, depending\nupon the error you see:\n■ Review the NetBackup nbemm logs to identify the exact error.\n■ Review your network connectivity with Snapshot Manager\n■ Resolve network issues if any, using netstat or a similar network diagnosis\ntool.\n■ Determine if nbcertcmdtool is able to connect to the web service running on\nthe NetBackup primary server to generate the NetBackup certificates.\n■ UsethentpdatecommandtosynchronizeclocktimesfortheNetBackupprimary\nserver and the Snapshot Manager.\n■ UpdatetheDNSentrieswithDockerandhostentriesfortheSnapshotManager.\nUpdate the /cloudpoint/openv/etc/hosts file with the DNS entries. Use\ndifferent network cards, IP addresses, or host names for registering the\nco-located media server and the Snapshot Manager. Also, if the media server\nandtheSnapshotManagerareco-located,andthemediaserverusesport443,\nthen the Snapshot Manager must use a custom SSL port."
    },
    "9897": {
        "code": 9897,
        "desc": "Failed to reassign the ownership of the root certificate path or file to the service user.",
        "first_action": "Add or modify the Snapshot Manager configuration using the tpconfig",
        "full_action": "Perform the following as appropriate:\n■ Add or modify the Snapshot Manager configuration using the tpconfig\ncommand. Run the tpconfig command as a root user. This action re-assigns\nthe ownership of the root certificate path or the certificate file to the NetBackup\nservice user.\n■ Review and re-assign the ownership and permissions for the NetBackup\ncertificate store (/usr/openv/var/global/cloudpoint) to the NetBackup\nservice user."
    },
    "9901": {
        "code": 9901,
        "desc": "'backupId' has an invalid syntax",
        "first_action": "Checktoseeif'backupId'hasavalidsyntax;forexample,",
        "full_action": "Checktoseeif'backupId'hasavalidsyntax;forexample,\ntestclient_1054264097."
    },
    "9902": {
        "code": 9902,
        "desc": "No recovery request specified",
        "first_action": "The recovery request body should not be empty.",
        "full_action": "The recovery request body should not be empty."
    },
    "9903": {
        "code": 9903,
        "desc": "'vmDisplayName' must not contain more than 80 characters.",
        "first_action": "Pleasemakesurethat'vmDisplayName'doesnotcontain",
        "full_action": "Pleasemakesurethat'vmDisplayName'doesnotcontain\nmore than 80 characters."
    },
    "9904": {
        "code": 9904,
        "desc": "'defaultDiskProvisioning' has an invalid value",
        "first_action": "The 'defaultDiskProvisioning' identifier should have",
        "full_action": "The 'defaultDiskProvisioning' identifier should have\none of the following values: thin, thick-lazy-zeroed, or thick-eager-zeroed."
    },
    "9905": {
        "code": 9905,
        "desc": "'type' specified in the recovery request is invalid",
        "first_action": "The 'type' identifier in the recovery request must be set",
        "full_action": "The 'type' identifier in the recovery request must be set\nto 'recoveryRequest'."
    },
    "9906": {
        "code": 9906,
        "desc": "'transportMode' has an invalid syntax",
        "first_action": "The 'transportMode' identifier must be specified in",
        "full_action": "The 'transportMode' identifier must be specified in\nlowercase, with colon-separated values; for example, hotadd:nbd:nbdssl:san.\nThe order of the specified modes is significant, as NetBackup attempts each mode\nin order until the recovery is successful."
    },
    "9907": {
        "code": 9907,
        "desc": "'recoveryPoint' must be specified in the recovery request",
        "first_action": "The 'recoveryPoint' identifier is mandatory for the",
        "full_action": "The 'recoveryPoint' identifier is mandatory for the\nrecovery operation, so it must be specified in the recovery request."
    },
    "9909": {
        "code": 9909,
        "desc": "Failed to fetch all the required images.",
        "first_action": "Review the information for a recovery point and use a",
        "full_action": "Review the information for a recovery point and use a\nrecovery point with a valid, complete set of images."
    },
    "9910": {
        "code": 9910,
        "desc": "'datacenter' must not be blank",
        "first_action": "Youmustspecifyadatacentervalueforthe'datacenter'",
        "full_action": "Youmustspecifyadatacentervalueforthe'datacenter'\nidentifier."
    },
    "9911": {
        "code": 9911,
        "desc": "'vmxDatastore' must not be blank",
        "first_action": "You must specify the vmx datastore type for the",
        "full_action": "You must specify the vmx datastore type for the\n'vmxDatastore' identifier."
    },
    "9912": {
        "code": 9912,
        "desc": "'diskMediaServer' must not be blank",
        "first_action": "You must specify a disk media server for the",
        "full_action": "You must specify a disk media server for the\n'diskMediaServer' identifier. For example, \"diskMediaServer\" :\n\"media-server.example.com\"."
    },
    "9913": {
        "code": 9913,
        "desc": "'defaultDiskProvisioning' must not be blank",
        "first_action": "You must specify a value for the",
        "full_action": "You must specify a value for the\n'defaultDiskProvisioning' identifier. Valid values are thin, thick-lazy-zeroed,\nor thick-eager-zeroed."
    },
    "9914": {
        "code": 9914,
        "desc": "'esxiServer' must not be blank",
        "first_action": "You must specify a server name for the 'esxiServer'",
        "full_action": "You must specify a server name for the 'esxiServer'\nidentifier. For example, \"esxiServer\" : \"esx-server.example.com\"."
    },
    "9915": {
        "code": 9915,
        "desc": "'vmFolder' must not be blank",
        "first_action": "You must specify a VM folder name for the 'vmFolder'",
        "full_action": "You must specify a VM folder name for the 'vmFolder'\nidentifier."
    },
    "9916": {
        "code": 9916,
        "desc": "'network' must not be blank",
        "first_action": "YoumustspecifythenameoftheVirtualMachineNetwork",
        "full_action": "YoumustspecifythenameoftheVirtualMachineNetwork\nfor the 'network' identifier."
    },
    "9917": {
        "code": 9917,
        "desc": "'recoveryHost' must not be blank",
        "first_action": "You must specify the recovery host name for the",
        "full_action": "You must specify the recovery host name for the\n'recoveryHost' identifier. For example, \"recoveryHost\" :\n\"recovery-proxy.example.com\"."
    },
    "9918": {
        "code": 9918,
        "desc": "'resourcePoolOrVapp' must not be blank",
        "first_action": "You must specify the pathname of either the resource",
        "full_action": "You must specify the pathname of either the resource\npool destination or the vApp for the 'resourcePoolOrVapp' identifier."
    },
    "9919": {
        "code": 9919,
        "desc": "'transportMode' must not be blank",
        "first_action": "You must specify the transport mode combination that is",
        "full_action": "You must specify the transport mode combination that is\nto be used to perform the recovery. The string must be specified in lowercase, with\ncolon-separatedvaluessuchashotadd:nbd:nbdssl:san.Theorderofthespecified\nmodes is significant, as NetBackup attempts each mode in the specified order until\nthe recovery is successful. If none of the modes are successful, the recovery fails."
    },
    "9920": {
        "code": 9920,
        "desc": "'vCenter' must not be blank",
        "first_action": "You must specify the vCenter server name; for example,",
        "full_action": "You must specify the vCenter server name; for example,\n\"vCenter\" : \"vcenter-server.example.com\"."
    },
    "9921": {
        "code": 9921,
        "desc": "'datacenter' must begin with a '/'",
        "first_action": "The 'datacenter' path must begin with a forward slash (/);",
        "full_action": "The 'datacenter' path must begin with a forward slash (/);\nfor example, \"datacenter\" : \"/example-DC\"."
    },
    "9922": {
        "code": 9922,
        "desc": "'vmFolder' must begin with a '/'",
        "first_action": "You must specify a forward slash (/) at the beginning of",
        "full_action": "You must specify a forward slash (/) at the beginning of\nthe 'vmFolder' path; for example, \"vmFolder\":\"/example-DC/vm\"."
    },
    "9923": {
        "code": 9923,
        "desc": "'resourcePoolOrVapp' must begin with a '/' NetBackup status codes 1193 NetBackup status codes",
        "first_action": "You must specify a forward slash (/) at the beginning of",
        "full_action": "You must specify a forward slash (/) at the beginning of\nthe 'resourcePoolOrVapp' path; for example, \"resourcePoolOrVapp\" :\n\"/example-DC/host/esx.example.com/Resources/example-res-pool\"."
    },
    "9926": {
        "code": 9926,
        "desc": "JSON input is invalid",
        "first_action": "The JSON request has an invalid syntax.",
        "full_action": "The JSON request has an invalid syntax."
    },
    "9928": {
        "code": 9928,
        "desc": "No workload is specified",
        "first_action": "Specify the workload in the Recovery API endpoint with",
        "full_action": "Specify the workload in the Recovery API endpoint with\nthe following format:\n/recovery/workloads/workload/scenarios/scenario/recover\nFor example, /recovery/workloads/vmware/scenarios/full-vm/recover."
    },
    "9929": {
        "code": 9929,
        "desc": "Invalid workload specified",
        "first_action": "SpecifythecorrectworkloadintherecoveryrequestURL.",
        "full_action": "SpecifythecorrectworkloadintherecoveryrequestURL."
    },
    "9930": {
        "code": 9930,
        "desc": "No scenario is specified",
        "first_action": "Specify the scenario in the Recovery API endpoint with",
        "full_action": "Specify the scenario in the Recovery API endpoint with\nthe following format:\n/recovery/workloads/workload/scenarios/scenario/recover\nFor example, /recovery/workloads/vmware/scenarios/full-vm/recover."
    },
    "9931": {
        "code": 9931,
        "desc": "Invalid scenario specified",
        "first_action": "Specify the correct scenario in the recovery request URL.",
        "full_action": "Specify the correct scenario in the recovery request URL."
    },
    "9934": {
        "code": 9934,
        "desc": "The specified end date time in the 'filter' must not be less than the start date time",
        "first_action": "Specify an end date in the 'filter' that is not less than the",
        "full_action": "Specify an end date in the 'filter' that is not less than the\nstart date. See the following example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\""
    },
    "9935": {
        "code": 9935,
        "desc": "The specified date-time values in the 'filter' must use a valid ISO 8601 format",
        "first_action": "Specifythedate-timevaluesinthe'filter'usingavalidISO",
        "full_action": "Specifythedate-timevaluesinthe'filter'usingavalidISO\n8601format.FormoreinformationabouttheISO8601format,seeISO8601format.\nSee the following example for a valid ISO 8601 format:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\""
    },
    "9936": {
        "code": 9936,
        "desc": "The specified date-time values in the 'filter' must not be in the future",
        "first_action": "Specify the date-time values in the 'filter' so they are less",
        "full_action": "Specify the date-time values in the 'filter' so they are less\nthan the current time."
    },
    "9937": {
        "code": 9937,
        "desc": "Either 'backupId' or 'client' must be specified in the recovery request",
        "first_action": "Specifyeither'backupId'or'client'intherecoveryrequest.",
        "full_action": "Specifyeither'backupId'or'client'intherecoveryrequest.\nThe recovery request requires either the 'backupId' or 'client' name."
    },
    "9938": {
        "code": 9938,
        "desc": "'backupId' must not be specified along with 'client' or 'filter'",
        "first_action": "Do not specify 'backupId' with 'client' or 'filter'.",
        "full_action": "Do not specify 'backupId' with 'client' or 'filter'."
    },
    "9939": {
        "code": 9939,
        "desc": "Invalid 'filter' syntax",
        "first_action": "Specify the 'filter' field with a valid Odata syntax. See the",
        "full_action": "Specify the 'filter' field with a valid Odata syntax. See the\nfollowing example:\n\"filter\" : \"backupTime ge '2017-11-20T23:20:50Z' and backupTime le '2018-12-20T23:20:50Z'\""
    },
    "9940": {
        "code": 9940,
        "desc": "'backupId' must not be specified with either 'sourceAsset' or 'filter'",
        "first_action": "Specify 'backupId' without either 'sourceAsset' or 'filter.'",
        "full_action": "Specify 'backupId' without either 'sourceAsset' or 'filter.'\nThe recovery request only accepts 'backupId'; it does not work along with\n'sourceAsset' or filter."
    },
    "9941": {
        "code": 9941,
        "desc": "'attributes' must be specified in the recovery request",
        "first_action": "Specify 'attributes' in the recovery request.",
        "full_action": "Specify 'attributes' in the recovery request."
    },
    "9942": {
        "code": 9942,
        "desc": "Either 'backupId' or 'sourceAsset' must be specified in the recovery request",
        "first_action": "Specifyeither'backupId'or'sourceAssetId'intherecovery",
        "full_action": "Specifyeither'backupId'or'sourceAssetId'intherecovery\nrequest."
    },
    "9944": {
        "code": 9944,
        "desc": "No matching backup image found to perform the recovery NetBackup status codes 1197 NetBackup status codes",
        "first_action": "Ensure that the client exists and, if it exists, then ensure",
        "full_action": "Ensure that the client exists and, if it exists, then ensure\nthat it has been backed up at least once."
    },
    "9946": {
        "code": 9946,
        "desc": "Invalid field was specified in the 'filter'",
        "first_action": "Ensure that the 'filter' is allowed on the specified field.",
        "full_action": "Ensure that the 'filter' is allowed on the specified field.\nRefer to the API documentation for the allowable filter operations."
    },
    "9947": {
        "code": 9947,
        "desc": "Invalid comparison operator specified for the field",
        "first_action": "Ensure that the comparison operators specified are",
        "full_action": "Ensure that the comparison operators specified are\nsupported for the field. Refer to the API documentation for the correct operators for\neach supported field."
    },
    "9948": {
        "code": 9948,
        "desc": "Grouping operator is not allowed in the 'filter'",
        "first_action": "The grouping operator is not allowed in the 'filter.' Refer",
        "full_action": "The grouping operator is not allowed in the 'filter.' Refer\nto the API documentation for the allowable filter operation."
    },
    "9949": {
        "code": 9949,
        "desc": "Invalid logical operator is specified in the 'filter'",
        "first_action": "The logical operator is not allowed in the 'filter.' Refer to",
        "full_action": "The logical operator is not allowed in the 'filter.' Refer to\nthe API documentation for the allowable filter operation."
    },
    "9968": {
        "code": 9968,
        "desc": "No recovery object specified as part of the recovery request.",
        "first_action": "Verify that the recoveryObject field is specified and that",
        "full_action": "Verify that the recoveryObject field is specified and that\nit is not empty."
    },
    "9969": {
        "code": 9969,
        "desc": "Invalid recovery object specified.",
        "first_action": "Verify that the value of recoveryObject is an object and",
        "full_action": "Verify that the value of recoveryObject is an object and\nthat it contains all required fields: credentials and assetId."
    },
    "9970": {
        "code": 9970,
        "desc": "Failed to get the result of the recovery request.",
        "first_action": "Verify that NetBackup services are running and that the",
        "full_action": "Verify that NetBackup services are running and that the\nrequest has the proper syntax."
    },
    "9971": {
        "code": 9971,
        "desc": "The recoveryPoint field must be specified.",
        "first_action": "Verify that the recoveryPoint field has been provided",
        "full_action": "Verify that the recoveryPoint field has been provided\nand that it is not an empty string. Also ensure that the scenario is a complete\ndatabaserecoveryintheURL.SpecifyarecoverypointintherecoveryPointfield."
    },
    "9972": {
        "code": 9972,
        "desc": "The assetId field must be specified.",
        "first_action": "Verify that the assetId field has been provided and that",
        "full_action": "Verify that the assetId field has been provided and that\nit is not an empty string. Specify an asset ID in the assetId field."
    },
    "9973": {
        "code": 9973,
        "desc": "The domain field must be specified.",
        "first_action": "Verify that the domain field has been provided and that it",
        "full_action": "Verify that the domain field has been provided and that it\nis not an empty string. Specify a domain in the domain field."
    },
    "9974": {
        "code": 9974,
        "desc": "The user field must be specified.",
        "first_action": "Verify that the user field has been provided and that it is",
        "full_action": "Verify that the user field has been provided and that it is\nnot an empty string. Specify a user name in the user field."
    },
    "9975": {
        "code": 9975,
        "desc": "The password field must be specified.",
        "first_action": "Verify that the password field has been provided and that",
        "full_action": "Verify that the password field has been provided and that\nit is not an empty string. Specify a password in the password field."
    },
    "9976": {
        "code": 9976,
        "desc": "ExactlyoneoptioninthealternateFileLocationfieldmustbespecified.",
        "first_action": "Verify that only one of the options is specified. Specify",
        "full_action": "Verify that only one of the options is specified. Specify\nonly one of the alternate file location options in the alternateFileLocation field."
    },
    "9977": {
        "code": 9977,
        "desc": "The renameAllFilesToSameLocation field must be specified.",
        "first_action": "If the renameAllFilesToSameLocation field is specified,",
        "full_action": "If the renameAllFilesToSameLocation field is specified,\nverify that it is not an empty string. Specify a location to which to restore all files in\nthe renameAllFilesToSameLocation field."
    },
    "9978": {
        "code": 9978,
        "desc": "The renameEachFileToDifferentLocation field must be specified.",
        "first_action": "If the renameEachFileToDifferentLocation field is",
        "full_action": "If the renameEachFileToDifferentLocation field is\nspecified, verify that none of the fields of any of its list items is an empty string.\nSpecify a list of file names and alternate paths in the\nrenameEachFileToDifferentLocation field."
    },
    "9979": {
        "code": 9979,
        "desc": "The restorePriority field must be specified.",
        "first_action": "If the restorePriority field is specified, verify that it is",
        "full_action": "If the restorePriority field is specified, verify that it is\nnot an empty string. Specify a valid restore priority in the restorePriority field.\nValid values are in the range 0-99999."
    },
    "9980": {
        "code": 9980,
        "desc": "The destinationAssetId parameter is required for alternate restore.",
        "first_action": "ProvidethedestinationassetIDandre-runtheoperation.",
        "full_action": "ProvidethedestinationassetIDandre-runtheoperation."
    },
    "9981": {
        "code": 9981,
        "desc": "Invalid parameter destinationAssetId provided for restore to original location.",
        "first_action": "Remove the destination asset ID parameter and re-run",
        "full_action": "Remove the destination asset ID parameter and re-run\nthe operation."
    },
    "9982": {
        "code": 9982,
        "desc": "Recovery request contains an invalid value for the image copy. Provide a value between 1 to 10.",
        "first_action": "Provide a value between 1 and 10 for the image copy.",
        "full_action": "Provide a value between 1 and 10 for the image copy.\nFor primary copy, do not provide any value and skip this step."
    },
    "9983": {
        "code": 9983,
        "desc": "Invalid asset ID specified in the recovery request.",
        "first_action": "Review the asset ID and confirm that it is correct. If the",
        "full_action": "Review the asset ID and confirm that it is correct. If the\nissue persists, contact Cohesity Technical Support for additional troubleshooting."
    },
    "9984": {
        "code": 9984,
        "desc": "Invalid parameter destinationAssetId provided for rollback recovery.",
        "first_action": "Remove the destination asset ID parameter and re-run",
        "full_action": "Remove the destination asset ID parameter and re-run\nthe operation."
    },
    "9986": {
        "code": 9986,
        "desc": "Input validation of GRT request failed.",
        "first_action": "For more information, refer to the NetBackup Cloud",
        "full_action": "For more information, refer to the NetBackup Cloud\nFile-Folders restore request API documentation and sample payload."
    },
    "9990": {
        "code": 9990,
        "desc": "The target host staging location path contains non-ASCII characters.",
        "first_action": "Provide the staging location, on the target host, using",
        "full_action": "Provide the staging location, on the target host, using\nACSII characters."
    },
    "9991": {
        "code": 9991,
        "desc": "The backupId, sourceAsset, or filter cannot be specified with providerRecoveryPointId.",
        "first_action": "If the providerRecoveryPointId is specified, then the",
        "full_action": "If the providerRecoveryPointId is specified, then the\nbackupId, sourceAssetId, or filter cannot be specified in the API call. The\noptions are applicable only for the provider-generated recovery points."
    },
    "9992": {
        "code": 9992,
        "desc": "Cannot perform recovery because the resource was not found.",
        "first_action": "Retry the operation and if the issue persists, visit",
        "full_action": "Retry the operation and if the issue persists, visit\nsupport.veritas.com. The Cohesity Technical Support website site offers additional\ninformation to help you troubleshoot this issue."
    },
    "9993": {
        "code": 9993,
        "desc": "Cannot perform recovery due to a restricted operation.",
        "first_action": "To perform the requested operation, you must be a root",
        "full_action": "To perform the requested operation, you must be a root\nuser, administrator, or have the appropriate privileges through RBAC. Contact the\nNetBackup system administrator.\n1204\nNetBackup KMS status codes"
    },
    "9997": {
        "code": 9997,
        "desc": "Backup from snapshot and indexing is not supported for an Azure disk encryption enabled virtual machine.",
        "first_action": "Only snapshot and restore are supported for Azure disk encryption enabled virtual",
        "full_action": "Perform the following as appropriate:\nOnly snapshot and restore are supported for Azure disk encryption enabled virtual\nmachine."
    },
    "9998": {
        "code": 9998,
        "desc": "Snapshot is not supported for Azure disk encryption-enabled volume.",
        "first_action": "Single volume snapshot is not supported. Perform a snapshot of the entire virtual",
        "full_action": "Perform the following as appropriate:\nSingle volume snapshot is not supported. Perform a snapshot of the entire virtual\nmachine."
    }
}