VMware backup failures with status code 200
Having a heck of a time trying to figure this out. 14 of my 21 VMware policies are failing with a status code 200 for some reason. Credentials are good and we can do a test query with no issues. Windows 2012 VMware Backup Host 5.5 Update 2 7.6.0.2 and I verified the VDDK is 5.5.0 I have attached all of the logs that would actually run. I cranked VXMS up to 5, but no log was created as I am guessing it just doesnt get that far into the process. Detailed Job Status: 07/22/2015 11:00:59 - Info nbjm (pid=1310) starting backup job (jobid=3391315) for client MEDIA_SERVER, policy Omaha_VMware_INFOBLOX, schedule Full_Daily 07/22/2015 11:00:59 - Info nbjm (pid=1310) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=3391315, request id:{D84F647C-308A-11E5-9F49-002128A6F97C}) 07/22/2015 11:00:59 - requesting resource XP53TAPE009 07/22/2015 11:00:59 - requesting resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - granted resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - estimated 11832060 kbytes needed 07/22/2015 11:00:59 - begin Parent Job 07/22/2015 11:00:59 - begin Application Resolver: Start Notify Script 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) started 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) exiting with status: 0 Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Start Notify Script; elapsed time 0:00:01 07/22/2015 11:01:00 - begin Application Resolver: Step By Condition Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Step By Condition; elapsed time 0:00:00 07/22/2015 11:01:00 - begin Application Resolver: Resolver Discovery Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Resolver Discovery; elapsed time 1:30:04 07/22/2015 12:31:04 - begin Application Resolver: Policy Execution Manager Preprocessed 07/22/2015 12:31:04 - Warning nbpem (pid=1367) VM retrieval failed, server = [53apps178vm]. Operation Status: 200 07/22/2015 12:31:04 - end Application Resolver: Policy Execution Manager Preprocessed; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: Stop On Error Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Stop On Error; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: End Notify Script 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) started 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) exiting with status: 0 Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: End Notify Script; elapsed time 0:00:00 Operation Status: 200 07/22/2015 12:31:04 - end Parent Job; elapsed time 1:30:05 scheduler found no backups due to run (200)
Netbackup Deduplication Engine takes lot of time to load into memory
Hello, I just wanted to know why Netbackup Deduplication Service(spoold) takes time to load into memory.(To start completely) I have seen sometimes it took more than 4 hours to start, when checking in Windows Task Manager the memory for spoold.exe is increasing gradually. Thanks & Regards Sujit
Use RMAN to backup number of copies of archive log
Hi , I hope you're doing well, I have a problem here, I want to have multiple backups for my oracle's Archive log area in two different media servers and I need them to be executed using RMAN. I've to say that we have a STU type of BasicDisk and I don't want to use SLP approach. Is there any suggestions you can make? Thanks in advance.
NetBackup SQL job failures - network connection timed out 41
Hi All, This is not a query for help but a note on a solution to a rather pesky problem with NetBackup SQL job failures and status message "network connection timed out 41". While it took me some time to figure out the root cause behind these failures, in the end it turned out to be nothing related to the usual suspects such as DNS/Hosts resolution, network bottlenecks or similar issues. I've been checking literally all aspects of all involved components (NBU Master, Media, Client, SQL DB, networking, etc.) but unfortunately nothing useful appeared in any of the logs. The most misleading part was when tracing error messages such as: ERR - Error in VxBSACreateObject: 3. CONTINUATION: - System detected error, operation aborted. ERR - Error in GetCommand: 0x80770004. DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][SQL Server Native Client 11.0][SQL Server]Write on "VNBU0-9280-5168-1609373275" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)>. CONTINUATION: - An abort request is preventing anything except termination actions. INFO Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the server. INFO Error in VxBSACreateObject: 3. INFO System detected error, operation aborted. INFO Error in GetCommand: 0x80770004. INFO An abort request is preventing anything except termination actions. INFO ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][SQL Server Native Client 11.0][SQL Server]Write on "VNBU0-8380-13048-1609410056" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)>. ...and also SQL errors like: 2020-12-30 23:52:19.11 Backup BackupIoRequest::ReportIoError: write failure on backup device 'VNBU0-9808-5248-1609367774'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.). 2020-12-30 23:52:19.11 Backup Error: 3041, Severity: 16, State: 1. 2020-12-30 23:52:19.11 Backup BACKUP failed to complete the command BACKUP DATABASE DB01. Check the backup application log for detailed messages. 2020-12-30 23:52:19.11 spid56 Error: 18210, Severity: 16, State: 1. 2020-12-30 23:52:19.11 spid56 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'VNBU0-9808-5248-1609367774'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.). 2020-12-31 00:00:19.10 spid31s This instance of SQL Server has been using a process ID of 8844 since 12/30/2020 10:23:10 PM (local) 12/30/2020 9:23:10 PM (UTC). This is an informational message only; no user action is required. 2020-12-31 00:10:03.71 Backup Error: 3041, Severity: 16, State: 1. Unfortunately neither "dbclient" nor "bprd" provided any useful indication on what's going on, but at the same time taking SQL backups natively via SQL Management Studio worked just fine. So, long story short... If you encounter such messages and you are using SQL instances in a VMware virtualized environment, make sure to check also against your "VSS appliaction quiescing" settings. In case you may have this set to "disabled", then this could be very much the source of the issue as it was in my case. In normal circumstances quiescing shouldn't be disabled at all, however I've seen many discussions over the years where users are suggesting to do so in order to avoid a long existing problem with failures over generic VM backups about which vendors are fingerpointing to each other but no effective long-term solution has been made available yet. The process of disabling VSS quiesced application based snapshots is outlined on the link below where in my case I had a legacy VM which was applied with the "tools.conf" option. https://kb.vmware.com/s/article/2146204 After removing the "vss.disableAppQuiescing = true" line from the "tools.conf" file the backups started to work immediately. I didn't test if disabling the disk UUID would end up with the same results but if I get a spare moment, then I may actually check it and report back here on the results. Perhaps this whole scenario should be tested by NetBackup engineers and in case they can confirm the behavior then a side note on the below link would be appropriate: https://www.veritas.com/content/support/en_US/doc/44037985-142651971-0/v15097395-142651971 Cheers
