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)3.2KViews0likes12CommentsHow to identity Status of a backup using Netbackup CLI ?
I launch 'bpbackup' command in my program and it just gives the return code. There is no way to know the corresponding JobId. Before I launch the next backup, I want to check the status of the Previous backup and make some decision. 'bpimagelist' command can be used with 'keyword' as filter so that I can search my backup job uniquely. Problem is, it only lists the Successful backups. 'bpdbjobs' command can be used to list out all jobs (successful, failed, in progress) but there is no way to uniquely find the backup job because it does not support filtering the result with 'keyword' attribute. Also Want to filter the status of individual client what I still not able to get using bpdbjobs. Any help is highly appreciated. DebSolved6.3KViews0likes5CommentsNDMP bakup failing with status 99
We are getting backup failures on 2 different filers for volume level backups: Backups are successful for other volumes on the same filers for volume level, qtree level and snapshot level backups. The backups are failing after backing up same amount of data with the following error: 03/24/2012 16:01:57 - positioned A03544; position time: 0:00:42 03/24/2012 16:01:57 - begin writing 03/24/2012 17:34:18 - Error bpbrm (pid=20453) db_FLISTsend failed: network connection timed out (41) 03/24/2012 17:34:18 - Error ndmpagent (pid=20459) write socket err 4 (Interrupted system call) 03/24/2012 17:34:19 - Error ndmpagent (pid=20459) FH send to BRM failed - Ino - 4096 0 4096 0 41756 0 0 8 16384 root root 4096 1305309404 1235758793 1235758793 00000000000000000000000000312de9 3223017/ 03/24/2012 17:34:19 - Error ndmpagent (pid=20459) NDMP backup failed, path = /vol/amavol 03/24/2012 17:34:35 - Error bptm (pid=20461) io_ioctl_ndmp (MTBSF) failed on media id A03544, drive index 40, return code 18 (NDMP_XDR_DECODE_ERR) (bptm.c.8774) 03/24/2012 17:34:35 - Critical bpbrm (pid=20453) unexpected termination of client ampnfas96001 03/24/2012 17:34:36 - Info bptm (pid=20461) EXITING with status 99 <---------- 03/24/2012 17:34:36 - Info ndmpagent (pid=0) done. status: 99: NDMP backup failure 03/24/2012 17:34:36 - end writing; write time: 1:32:39 03/24/2012 17:54:36 - Info nbjm (pid=21152) starting backup job (jobid=1020807) for client ampnfas96001, policy NDMP-ampnfas96001-amavol, schedule Full 03/24/2012 17:54:43 - Info bpbrm (pid=3714) ampnfas96001 is the host to backup data from NDMP backup failure (99) The volumes for which the backup are failing are on netapp filers and are online. # ssh ampnfas96001 vol status amavol Volume State Status Options amavol online raid_dp, flex maxdirsize=62914, sis fractional_reserve=0 Containing aggregate: 'aggr_1' tpautoconf -verify output is as follows: bash-3.00# tpautoconf -verify ampnfas96001 Connecting to host "ampnfas96001" as user "root"... Waiting for connect notification message... Opening session--attempting with NDMP protocol version 4... Opening session--successful with NDMP protocol version 4 host supports MD5 authentication Getting MD5 challenge from host... Logging in using MD5 method... Host info is: host name "AMPNFAS96001" os type "NetApp" os version "NetApp Release 7.3.3P5" host id "0118071324" Login was successful Host supports LOCAL backup/restore Host supports 3-way backup/restore bash-3.00# It doesnt seems to be an issue from the filer side as backups for other volumes on the same filer are successful. We have recently upgraded our environment to 7.1.0.3 from 7.0.1 Do we need any upgradation from NDMP point of view.Solved4.2KViews0likes18CommentsOps Center not emailing new reports
Had this problem a couple months back and it randomly fixed itself. Unfortunately that hasn't happened this time. Created new scheduled reports with new time schedules. The reports are set to export and email. The export works, the email doesn't. The reason this is particularly vexing is that I have other scheduled reports that work just fine. New reports are set up just like the working ones. I have created mutiple time and report schedules, tried sending it to different email addresses, rebooted the server, restarted the services, nothing works.1.6KViews1like9CommentsWhere I can find client software image.
Hi everyone, I'm going to test BMR features. When I'm creating an SRT for Window, the wizard ask for a client software image path. What does it mean? Where do I find this image? is it something that I must create from a client? Could anyone help me please? Thanks Bonovox703Views0likes4CommentsNDMP error 99
Hi, Since fewdays, I have some trouble on my NDMP backups. My backup selection is shared between many streams. All full backup are OK, but some of incr backup failswith status 99. Apparently, the level 0 dump is post-dated, and I have this error : "Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump." 14/02/2016 22:36:37 - connecting 14/02/2016 22:36:37 - connected; connect time: 00:00:00 14/02/2016 22:36:38 - mounting CAD126 14/02/2016 22:38:15 - Info bptm(pid=17364) media id CAD126 mounted on drive index 2, drivepath nrst1a, drivename HP.ULTRIUM5-SCSI.002, copy 1 14/02/2016 22:38:15 - mounted; mount time: 00:01:37 14/02/2016 22:38:20 - Info ndmpagent(pid=18976) bstou103: SCSI: TAPE READ: short read for nrst1a 14/02/2016 22:38:21 - positioning CAD126 to file 44 14/02/2016 22:39:35 - Info ndmpagent(pid=18976) bstou103: DUMP: creating "/vol/volpoles/../snapshot_ for_backup.3112" snapshot. 14/02/2016 22:39:35 - positioned CAD126; position time: 00:01:14 14/02/2016 22:39:35 - begin writing 14/02/2016 22:39:37 - Info ndmpagent(pid=18976) bstou103: DUMP: Using subtree dump 14/02/2016 22:39:51 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of this level 1 dump snapshot: Sun Feb 14 22:40:46 2016. 14/02/2016 22:39:52 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of last level 0 dump: Tue Jan 19 04:14:07 2038. 14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump. 14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Dump failed to initialize. 14/02/2016 22:39:53 - Error ndmpagent(pid=18976) bstou103: DUMP: DUMP IS ABORTED 14/02/2016 22:39:54 - Info ndmpagent(pid=18976) bstou103: DUMP: Deleting "/vol/volpoles/../snapshot_ for_backup.3112" snapshot. 14/02/2016 22:39:56 - Error ndmpagent(pid=18976) bstou103: DATA: Operation terminated: EVENT: INTERNAL ERROR (for /vol/volpoles/qtpoles/PRP/ SERIS) 14/02/2016 22:39:56 - Error ndmpagent(pid=18976) NDMP backup failed, path = /vol/volpoles/qtpoles/PRP/ SERIS 14/02/2016 22:39:57 - Error bptm(pid=17364) none of the NDMP backups for client bstou103 completed successfully 14/02/2016 22:40:23 - Info bptm(pid=17364) EXITING with status 99 <---------- 14/02/2016 22:40:24 - end writing; write time: 00:00:49 NDMP backup failure(99) Any idea ? My version is 7.5.0.4 Thanks !Solved4.6KViews0likes22Comments**NEW** Alta Recovery Vault Direct Connect & ExpressRoute Overview Guide
Hello friends, GNeil and I are happy and proud to share with you all - Veritas is now certified to use AWS Direct Connect & Azure ExpressRoute for Alta Recovery Vault. Here's a sneak peek at the guide : Veritas Alta™ Recovery Vault AWS Direct Connect Overview Guide :click here Veritas Alta™ Recovery Vault Azure ExpressRoute Overview Guide :click here Guide includes informative diagrams that can aid in visualization. Also, we have performance numbers in the guide, see how much I like you ! Here's a diagram that will give you an idea of what was tested in AWS Direct Connect for Alta Recovery Vault : Please feel freeto give feedback and we cananswer any questions you have.We appreciate everyone’s time! Thanks -Sakshi1.4KViews3likes3Comments