Exchange2016 Backup with error 130
Hi! We using Netbackup 7.6.1.1. One of the jobs copied the Exchange 2016 databases in the DAG (mail02, mail03 servers). I see that the databases from the mail02 server are being copied normally. As a result, the MAIL03 server receives error 130: I see the following in the task log: DAG 18.09.2025 19:00:00 - Info nbjm(pid=3828) starting backup job (jobid=560085) for client dag.main.msa.ru, policy Exchange2016, schedule Differential-Inc 18.09.2025 19:00:00 - Info nbjm(pid=3828) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=560085, request id:{E6D62052-337D-4EBE-B208-C365494A3AE6}) 18.09.2025 19:00:00 - requesting resource srv-nbu01-hcart2-robot-tld-0 18.09.2025 19:00:00 - requesting resource srv-nbu01.main.msa.ru.NBU_CLIENT.MAXJOBS.dag.main.msa.ru 18.09.2025 19:00:00 - requesting resource srv-nbu01.main.msa.ru.NBU_POLICY.MAXJOBS.Exchange2016 18.09.2025 19:00:00 - requesting resource EXCHANGE_RESOLVER.srv-nbu01.main.msa.ru.Exchange2016.dag.main.msa.ru 18.09.2025 19:00:00 - granted resource srv-nbu01.main.msa.ru.NBU_CLIENT.MAXJOBS.dag.main.msa.ru 18.09.2025 19:00:00 - granted resource srv-nbu01.main.msa.ru.NBU_POLICY.MAXJOBS.Exchange2016 18.09.2025 19:00:00 - granted resource EXCHANGE_RESOLVER.srv-nbu01.main.msa.ru.Exchange2016.dag.main.msa.ru 18.09.2025 19:00:00 - estimated 0 Kbytes needed 18.09.2025 19:00:00 - begin Parent Job 18.09.2025 19:00:00 - begin Exchange 14 Resolver, Start Notify Script 18.09.2025 19:00:01 - Info RUNCMD(pid=12468) started 18.09.2025 19:00:04 - Info RUNCMD(pid=12468) exiting with status: 0 Status 0 18.09.2025 19:00:04 - end Exchange 14 Resolver, Start Notify Script; elapsed time: 0:00:04 18.09.2025 19:00:04 - begin Exchange 14 Resolver, Step By Condition Status 0 18.09.2025 19:00:04 - end Exchange 14 Resolver, Step By Condition; elapsed time: 0:00:00 18.09.2025 19:00:04 - begin Exchange 14 Resolver, Read File List Status 0 18.09.2025 19:00:04 - end Exchange 14 Resolver, Read File List; elapsed time: 0:00:00 18.09.2025 19:00:04 - begin Exchange 14 Resolver, Resolver Discovery 18.09.2025 19:00:04 - started process bpbrm (13728) 18.09.2025 19:00:06 - Info bpbrm(pid=13728) dag.main.msa.ru is the host to restore to 18.09.2025 19:00:06 - Info bpbrm(pid=13728) reading file list for client 18.09.2025 19:00:16 - Info bpbrm(pid=13728) client_pid=45728 18.09.2025 19:00:16 - Info bpbrm(pid=13728) from client dag.main.msa.ru: TRV - BPRESOLVER has executed on server (MAIL01) 18.09.2025 19:02:08 - Info bpresolver(pid=45728) done. status: 0 18.09.2025 19:02:08 - Info bpresolver(pid=45728) done. status: 0: the requested operation was successfully completed Status 0 18.09.2025 19:02:08 - end Exchange 14 Resolver, Resolver Discovery; elapsed time: 0:02:04 18.09.2025 19:02:08 - begin Exchange 14 Resolver, Persist Discovery Status 0 18.09.2025 19:02:08 - end Exchange 14 Resolver, Persist Discovery; elapsed time: 0:00:00 18.09.2025 19:02:08 - begin Exchange 14 Resolver, Policy Execution Manager Preprocessed Status 130 18.09.2025 19:46:14 - end Exchange 14 Resolver, Policy Execution Manager Preprocessed; elapsed time: 0:44:06 18.09.2025 19:46:14 - begin Exchange 14 Resolver, Stop On Error Status 0 18.09.2025 19:46:14 - end Exchange 14 Resolver, Stop On Error; elapsed time: 0:00:00 18.09.2025 19:46:14 - begin Exchange 14 Resolver, End Notify Script 18.09.2025 19:46:15 - Info RUNCMD(pid=13972) started 18.09.2025 19:46:19 - Info RUNCMD(pid=13972) exiting with status: 0 Status 0 18.09.2025 19:46:19 - end Exchange 14 Resolver, End Notify Script; elapsed time: 0:00:05 Status 130 18.09.2025 19:46:19 - end Parent Job; elapsed time: 0:46:19 system error occurred (130) MAIL03 18.09.2025 19:41:30 - Info nbjm(pid=3828) starting backup job (jobid=560086) for client MAIL03.MAIN.msa.ru, policy Exchange2016, schedule Differential-Inc 18.09.2025 19:41:30 - Info nbjm(pid=3828) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=560086, request id:{6EDD80D8-2A76-48D0-8330-32519FE4C2E4}) 18.09.2025 19:41:30 - requesting resource srv-nbu01-hcart2-robot-tld-0 18.09.2025 19:41:30 - requesting resource srv-nbu01.main.msa.ru.NBU_CLIENT.MAXJOBS.MAIL03.MAIN.msa.ru 18.09.2025 19:41:30 - requesting resource srv-nbu01.main.msa.ru.NBU_POLICY.MAXJOBS.Exchange2016 18.09.2025 19:41:30 - awaiting resource srv-nbu01-hcart2-robot-tld-0 - No drives are available 18.09.2025 19:42:42 - granted resource srv-nbu01.main.msa.ru.NBU_CLIENT.MAXJOBS.MAIL03.MAIN.msa.ru 18.09.2025 19:42:42 - granted resource srv-nbu01.main.msa.ru.NBU_POLICY.MAXJOBS.Exchange2016 18.09.2025 19:42:42 - granted resource M009L5 18.09.2025 19:42:42 - granted resource IBM.ULT3580-TD6.000 18.09.2025 19:42:42 - granted resource srv-nbu01-hcart2-robot-tld-0 18.09.2025 19:42:42 - estimated 9723692 Kbytes needed 18.09.2025 19:42:42 - begin Parent Job 18.09.2025 19:42:42 - begin Exchange 14 Snapshot, Step By Condition Status 0 18.09.2025 19:42:42 - end Exchange 14 Snapshot, Step By Condition; elapsed time: 0:00:00 18.09.2025 19:42:42 - begin Exchange 14 Snapshot, Read File List Status 0 18.09.2025 19:42:42 - end Exchange 14 Snapshot, Read File List; elapsed time: 0:00:00 18.09.2025 19:42:42 - begin Exchange 14 Snapshot, Create Snapshot 18.09.2025 19:42:42 - started process bpbrm (14124) 18.09.2025 19:42:42 - started 18.09.2025 19:42:43 - Info bpbrm(pid=14124) MAIL03.MAIN.msa.ru is the host to backup data from 18.09.2025 19:42:43 - Info bpbrm(pid=14124) reading file list for client 18.09.2025 19:42:43 - Info bpbrm(pid=14124) start bpfis on client 18.09.2025 19:42:44 - Info bpbrm(pid=14124) Starting create snapshot processing 18.09.2025 19:42:45 - Info bpfis(pid=58732) Backup started 18.09.2025 19:43:54 - Critical bpbrm(pid=14124) from client MAIL03.MAIN.msa.ru: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 18.09.2025 19:43:54 - Info bpbrm(pid=14124) DB_BACKUP_STATUS is 103 18.09.2025 19:43:55 - Info bpbrm(pid=14124) DB_BACKUP_STATUS is 103 18.09.2025 19:43:55 - Critical bpbrm(pid=14124) from client MAIL03.MAIN.msa.ru: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 18.09.2025 19:43:55 - Info bpfis(pid=58732) done. status: 130 18.09.2025 19:43:55 - end Exchange 14 Snapshot, Create Snapshot; elapsed time: 0:01:13 18.09.2025 19:43:55 - Info bpfis(pid=58732) done. status: 130: system error occurred 18.09.2025 19:43:55 - end writing Status 130 18.09.2025 19:43:55 - end Parent Job; elapsed time: 0:01:13 18.09.2025 19:43:55 - begin Exchange 14 Snapshot, Stop On Error Status 0 18.09.2025 19:43:55 - end Exchange 14 Snapshot, Stop On Error; elapsed time: 0:00:00 18.09.2025 19:43:55 - begin Exchange 14 Snapshot, Delete Snapshot 18.09.2025 19:43:56 - started process bpbrm (9816) 18.09.2025 19:43:57 - Info bpbrm(pid=9816) Starting delete snapshot processing 18.09.2025 19:43:58 - Info bpfis(pid=39408) Backup started 18.09.2025 19:43:59 - Critical bpbrm(pid=9816) from client MAIL03.MAIN.msa.ru: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.dag.main.msa.ru_1758213762.1.0 18.09.2025 19:44:00 - Info bpfis(pid=39408) done. status: 4207 18.09.2025 19:44:00 - end Exchange 14 Snapshot, Delete Snapshot; elapsed time: 0:00:05 18.09.2025 19:44:00 - Info bpfis(pid=39408) done. status: 4207: Could not fetch snapshot metadata or state files 18.09.2025 19:44:00 - end writing Status 4207 18.09.2025 19:44:00 - end operation Status 130 18.09.2025 19:44:00 - end operation system error occurred (130) I ask for help in resolving the error.120Views0likes7Commentsstatus: 26: client/server handshaking failed
I am trying to restore a single DB instance from Exchange in NBU 7.6.1 the problem is that I dont have support, So I have it difficult. Everytime I try to restore I keep getting the "handshake" error then 2810 error. The output: "06/08/2018 21:31:01 - begin Restore 06/08/2018 21:31:01 - Info bprd(pid=7064) Found (12.178) files in (1) images for Restore Job ID 23319.xxx 06/08/2018 21:31:01 - media 000613 required 06/08/2018 21:31:01 - restoring image dagpge_1532613051 06/08/2018 21:31:05 - Info bprd(pid=7064) Searched ( 6) files of (12.178) files for Restore Job ID 23319.xxx 06/08/2018 21:31:05 - Info bprd(pid=7064) Restoring from copy 1 of image created 07/26/18 08:50:51 from policy DAGPGE_correo 06/08/2018 21:31:06 - Info bpbrm(pid=7344) CORREONEW is the host to restore to 06/08/2018 21:31:06 - Info bpbrm(pid=7344) reading file list for client 06/08/2018 21:31:08 - connecting 06/08/2018 21:31:08 - Info bpbrm(pid=7344) starting bptm 06/08/2018 21:36:11 - Error bpbrm(pid=7344) handshake failure when starting tar on CORREONEW; read: 06/08/2018 21:36:11 - Info tar32(pid=0) done. status: 26: client/server handshaking failed 06/08/2018 21:36:11 - Error bpbrm(pid=7344) client restore EXIT STATUS 26: client/server handshaking failed 06/08/2018 21:36:11 - restored image dagpge_1532613051 - (client/server handshaking failed(26)); restore time 0:05:10 06/08/2018 21:36:11 - end Restore; elapsed time: 0:05:10 MS-Exchange-Server policy restore error (2810)" So now I am short of Ideas Attached to the mail you can see some screenshots of the steps I am following3.1KViews0likes4CommentsExchange server Error 26
Hello, I have NBU 8.0. One of my policies which is a Exchange server policy is returning an error. the error is: ----------- ul 29, 2018 1:06:12 PM - end Parent Job; elapsed time 2:00:11 Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) from client server.com: ERR - Send bpfis state to Masterserver.com failed. status = -3 Jul 29, 2018 1:27:26 PM - Info bpfis (pid=8072) done. status: 0 Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) could not write filelist start to OUTSOCK Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) could not write EXIT STATUS to OUTSOCK Jul 29, 2018 1:27:26 PM - Info bpfis (pid=8072) done. status: 24: socket write failed client/server handshaking failed (26) ---------- The work I have done to solve it are: restarting the exchange server restarting the exchange replication service deleteing the shadow list on exchange I have done all the searches on the net and did everything need but unsuccessful. Before this i get 130 error but after restarting teh replication service anddeleting the shadows it became the mentioend error 26. Thanks in advance, Ashkan1.2KViews0likes2CommentsExchange 2013 CCR native protection or Netbackup
I'm not an exchange admin so i apoligize for any lingo missteps, etc.. My company is doing Exchange 2013 CCR/DAG with a production and a DR site. Currently we are backing up passive copies of exchange @ our DR site with Netbackup. Doing a non GRT backup with daily DIFF and weekly FULL approach, with 90 days retention, all on disk, no tape out. We have dialed up retention for the users to 5GB per mailbox, and have 14 days of recovery enabled natively in Exchange. Most of our end user driven restores are handled without ever needing to go to netbackup. We are considering extending the native recovery in Exchange to 45 or maybe 90 days with the end game of not backing up Exchange anymore. I'm curious if any others have moved away or are considering moving away from backing up exchange? thanks958Views0likes3Commentsexchange backup failed with status code 4200
Dear all , i have an backup enviroment contains solarois master server and windows media server i have alot of exchange databases distributed on 3 nodes "dag " recently i noticed that alot of database failed with status code 4200 " Operation failed: Unable to acquire snapshot lock (4200) on the same node and other policies complete successfully on the same node most of my backup policies start from 5pm till 4 am next day i have searched for the status code error , it indicate that the snapshot processis taken by another process but i can't point to the main problems i think that the problem due to current running jobs to same node , but every thing was running successfully with out making any changes to the enviroment , when i run the failed policies during the working hours , it complete successfully with out any errors another databases on other nodes of the cluster running successfully4KViews0likes7CommentsExchange Policy doesn't show Information Store
Hi, First we created an Exchange Policy and specified the Microsoft Information Store to be backed up, and everything went fine. After we opted to delete this policy and create a new one, this time when we tried to add the Microsoft Information Store it didn't show up ! So we checked the permisions and all prerequisites. After 2 days we tried again and it showed up and backed up succesfully , and then we wanted to change the destination storage and here the same issue appeared again. Thank youSolved1.9KViews0likes9CommentsExchange GRT browsing slow NBU 2.7.3 / 7.7.3
Hi all, I am experiencing a very definite slowness when browsing an Exchange backup in NBU in order to perform a GRT restore for testing. After selecting a backup image each time I attempt to drill down to a sub level it creates a new Restore task in the activity monitor and each task takes between 3 and 5 minutes to complete, during this time the restore console is unusable. For example navigating as follows "Microsoft Informaiton Store" > DB Name > Database > Mailbox name > Mailbox folder has resulted in four Restore tasks and has taken 15 minutes in order to display the contents of the inbox of a single mailbox. At this rate it would be quicker for me to restore the entire database to a recovery database and copy the individual messages should it be required - thankfully I am just performing a test restore at the moment. Is this slow navigation normal with NBU? Thanks1.6KViews0likes2Comments