07-10-2015 04:58 AM
Hello There.
We have created a new Exchange 2013 farm and now we want to backup this.
The Exchange 2010 backup runs without any problems and i copied the Netbackup policy and changed the entries.
When I start the Exchange 2014 backup with the new Policy, I get this error:
Operation Status: 0
10.07.2015 13:13:09 - end Snapshot: Read File List; elapsed time 0:00:00
10.07.2015 13:13:09 - begin Snapshot: Create Snapshot
10.07.2015 13:13:10 - started process bpbrm (pid=25511)
10.07.2015 13:13:11 - Info bpbrm (pid=25511) dag01.corp.dir is the host to backup data from
10.07.2015 13:13:11 - Info bpbrm (pid=25511) reading file list for client
10.07.2015 13:13:11 - Info bpbrm (pid=25511) start bpfis on client
10.07.2015 13:13:12 - Info bpbrm (pid=25511) Starting create snapshot processing
10.07.2015 13:13:12 - Info bpfis (pid=23496) Backup started
10.07.2015 13:13:29 - Critical bpbrm (pid=25511) from client dag01.corp.dir: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
10.07.2015 13:13:29 - Info bpfis (pid=23496) done. status: 130
10.07.2015 13:13:29 - end Snapshot: Create Snapshot; elapsed time 0:00:20
10.07.2015 13:13:29 - Info bpfis (pid=23496) done. status: 130: system error occurred
10.07.2015 13:13:29 - end writing
Operation Status: 130
10.07.2015 13:13:29 - end Parent Job; elapsed time 0:00:20
10.07.2015 13:13:29 - begin Snapshot: Stop On Error
Operation Status: 0
10.07.2015 13:13:29 - end Snapshot: Stop On Error; elapsed time 0:00:00
10.07.2015 13:13:29 - begin Snapshot: Delete Snapshot
10.07.2015 13:13:30 - started process bpbrm (pid=27173)
10.07.2015 13:13:31 - Info bpbrm (pid=27173) Starting delete snapshot processing
10.07.2015 13:13:33 - Info bpfis (pid=19164) Backup started
10.07.2015 13:13:33 - Critical bpbrm (pid=27173) from client dag01.corp.dir: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.dag01.corp.dir_1436526789.1.0
10.07.2015 13:13:34 - Info bpfis (pid=19164) done. status: 4207
10.07.2015 13:13:34 - end Snapshot: Delete Snapshot; elapsed time 0:00:05
10.07.2015 13:13:34 - Info bpfis (pid=19164) done. status: 4207: Could not fetch snapshot metadata or state files
10.07.2015 13:13:34 - end writing
Operation Status: 4207
10.07.2015 13:13:34 - begin Snapshot: End Notify Script
10.07.2015 13:13:34 - Info RUNCMD (pid=17727) started
10.07.2015 13:13:34 - Info RUNCMD (pid=17727) exiting with status: 0
Operation Status: 0
10.07.2015 13:13:34 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 4207
Could not fetch snapshot metadata or state files (4207)
Here's an excerpt of my Policy
bppllist Exchange_....._DAG01
CLASS Exchange......AG01 *NULL* 0 760000 165600 *NULL*
NAMES
INFO 16 0 0 999 *NULL* 0 0 2147483647 0 0 0 0 0 0 0 0 1 0 1319099685 55DF6302263A11E5BC2600212858BCB3 1 0 0 0 0 0 0 0 -1 0 1 0 0 0 0 1 0 36 0 0 0 0 0 0 1
KEY *NULL*
BCMD *NULL*
RCMD *NULL*
RES Retention_xxJ *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
POOL NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup NetBackup
FOE 0 0 0 0 0 0 0 0 0 0
SHAREGROUP *ANY*
DATACLASSIFICATION *NULL*
SSM VSS
SSMARGCOUNT 4
SSMARG prov_type 0
SSMARG max_snapshots 1
SSMARG snap_attr 0
SSMARG method VSS
EXCHANGESERVER FRSP0171
CLIENT dag01.corp.dir Windows-x86 Windows2008 0 1 0 0 *NULL*
INCLUDE NEW_STREAM
INCLUDE Microsoft Information Store:\
SCHED FULL 0 11 86400 0 0 0 0 *NULL* 0 0 0 0 0 0 -1 0 0 0
SCHEDWIN 0 0 83400 7200 83400 7200 83400 7200 83400 7200 83400 7200 0 0
SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
SCHEDRL 0 1 1 1 1 1 1 1 1 1
SCHEDFOE 0 0 0 0 0 0 0 0 0 0
SCHEDSG *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
SCHED DIFF 1 11 86400 0 0 0 0 *NULL* 0 0 0 0 0 0 -1 0 0 0
SCHEDWIN 21600 28800 0 0 0 0 0 0 0 0 0 0 21600 28800
SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
SCHEDRL 0 1 1 1 1 1 1 1 1 1
SCHEDFOE 0 0 0 0 0 0 0 0 0 0
SCHEDSG *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
Solved! Go to Solution.
08-12-2015 04:03 AM
07-10-2015 05:16 AM
In my experience (on Exchange 2010) this can often be solved by restarting the exchange replication service.
To verify that replication service writer is the issue, run vssadmin list writers
Another thing I have seen cause issues is scanning software for exchange.
As always on windows check the application and system event log for warning/errors.
07-10-2015 05:17 AM
Hi Thomas,
after some Troubleshooting with Symantec support we are able to backup and (!!!) restore auf Exchange 2013 DAG farm.
Our Exchangeteam use the new IPless DAG-Cluster.
There are some setting we have to set.
+ Configure DAG-Name as DNS-Alias for one of your DAG-Nodes
(https://support.symantec.com/en_US/article.TECH223843.html)
+ "Netbackup Client Service" and "NetBackup Legacy Network Service" shold run under a Serviceuser with Exchange-Rights.
+ Configure "Distributed Application Restore Mapping" for your DAG
+ Allow Connect back from DAG-Node to your Masterserver
+ Backup only active copies (Setting in your Policy) in Policy type "MS-Exchange Server" and use the DAG-Name as Client.
I hope this short description helps to find your Problem. Otherwise you can contact me for further details.
07-10-2015 05:53 AM
You should have a look at the bpfis log (easily gathered via log assistant) and the windows event log.
Which version of Netbackup do you use?
Do you use any special snapshot provider?
Good luck
Stefan
07-12-2015 10:50 PM
We run NBU_7.6.0.4 and in the bpfis log ( Master and Media Server ) is no entry.
I check today the snapshot provider, but this ois not simple because the Exchange servers are in france :)
But i think there are the VMWare VSS running.
08-11-2015 03:59 AM
Is dag01.corp.dir a node name or the Virtual name associated with the DAG cluster?
Was NBU client sofware installed on all DAG members?
bpfis log folder needs to be created on the Exchange node, not master or media server.
Create these log folders on all DAG members:
bpfis
bpresolver
bpbkar
08-11-2015 06:22 AM
i can't belive. When i start a backup of the new Exchange fram, i see no Logfiles in the folders
bpfis
bpresolver
bpbkar.
And the dagfr.corp.dir ist the DAG name of the Exchange system
What can it be?
08-11-2015 06:48 AM
Now i have news
After changing the Backup Selection to "Microsoft Exchange Database Availability Groups:\" i get some logfiles. See attached
And here is the Netbackup Job Log:
11.08.2015 15:39:23 - Info nbjm (pid=18305) starting backup job (jobid=5572694) for client dag01.corp.dir, policy Exchange_Fr_DAG01, schedule FULL
11.08.2015 15:39:23 - Info nbjm (pid=18305) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=5572694, request id:{606F7C2C-402E-11E5-AF74-00212858BCB3})
11.08.2015 15:39:23 - requesting resource ADVD_Retention_11J
11.08.2015 15:39:23 - requesting resource nbumaster.NBU_CLIENT.MAXJOBS.dag01.corp.dir
11.08.2015 15:39:23 - requesting resource nbumaster.NBU_POLICY.MAXJOBS.Exchange_Fr_DAG01
11.08.2015 15:39:23 - requesting resource EXCHANGE_RESOLVER.nbumaster.Exchange_Fr_DAG01.dag01.corp.dir
11.08.2015 15:39:23 - granted resource nbumaster.NBU_CLIENT.MAXJOBS.dag01.corp.dir
11.08.2015 15:39:23 - granted resource nbumaster.NBU_POLICY.MAXJOBS.Exchange_Fr_DAG01
11.08.2015 15:39:23 - granted resource EXCHANGE_RESOLVER.nbumaster.Exchange_Fr_DAG01.dag01.corp.dir
11.08.2015 15:39:24 - estimated 0 kbytes needed
11.08.2015 15:39:24 - begin Parent Job
11.08.2015 15:39:24 - Info RUNCMD (pid=15171) started
11.08.2015 15:39:24 - Info RUNCMD (pid=15171) exiting with status: 0
Operation Status: 0
11.08.2015 15:39:24 - end Parent Job; elapsed time 0:00:00
Operation Status: 0
Operation Status: 0
11.08.2015 15:39:25 - started process bpbrm (pid=15184)
11.08.2015 15:39:26 - Info bpbrm (pid=15184) dag01.corp.dir is the host to restore to
11.08.2015 15:39:26 - Info bpbrm (pid=15184) reading file list for client
11.08.2015 15:39:30 - Info bpbrm (pid=15184) client_pid=14140
11.08.2015 15:39:31 - Info bpbrm (pid=15184) from client dag01.corp.dir: TRV - BPRESOLVER has executed on server (FRSP0173)
11.08.2015 15:39:43 - Info bpresolver (pid=14140) done. status: 2
Operation Status: 2
Operation Status: 0
11.08.2015 15:39:43 - Error bpbrm (pid=15184) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup
11.08.2015 15:39:43 - Info bpresolver (pid=14140) done. status: 72: the client type is incorrect in the configuration database
11.08.2015 15:39:43 - Info RUNCMD (pid=15408) started
11.08.2015 15:39:43 - Info RUNCMD (pid=15408) exiting with status: 0
Operation Status: 0
Operation Status: 2
none of the requested files were backed up (2)
08-11-2015 06:58 AM
08-11-2015 07:08 AM
Did you configure the host properties for DAG?
If you use the logging assistant you don't have to worry much about the settings manually, and you can easily turn the logging level down – before accidently you run out of space.
08-11-2015 07:11 AM
Yes dag01.corp.dir is the DAG name and not the server name.
After changing the Backup Selection to -> Database Availability Groups -> i get the error 2, too.
And what is this for a error ???
11.08.2015 16:07:59 - Error bpbrm (pid=8062) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup
11.08.2015 16:07:59 - Info bpresolver (pid=16456) done. status: 72: the client type is incorrect in the configuration database
OMG, i hate exchange :(
Here the full Job Log.
11.08.2015 16:07:39 - Info nbjm (pid=18305) starting backup job (jobid=5572758) for client dag01.corp.dir, policy Exchange_Fr_DAG01, schedule FULL
11.08.2015 16:07:39 - Info nbjm (pid=18305) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=5572758, request id:{5365B57E-4032-11E5-AF41-00212858BCB3})
11.08.2015 16:07:39 - requesting resource ADVD_Retention_11J
11.08.2015 16:07:39 - requesting resource nbumaster.NBU_CLIENT.MAXJOBS.dag01.corp.dir
11.08.2015 16:07:39 - requesting resource nbumaster.NBU_POLICY.MAXJOBS.Exchange_Fr_DAG01
11.08.2015 16:07:39 - requesting resource EXCHANGE_RESOLVER.nbumaster.Exchange_Fr_DAG01.dag01.corp.dir
11.08.2015 16:07:39 - granted resource nbumaster.NBU_CLIENT.MAXJOBS.dag01.corp.dir
11.08.2015 16:07:39 - granted resource nbumaster.NBU_POLICY.MAXJOBS.Exchange_Fr_DAG01
11.08.2015 16:07:39 - granted resource EXCHANGE_RESOLVER.nbumaster.Exchange_Fr_DAG01.dag01.corp.dir
11.08.2015 16:07:40 - estimated 0 kbytes needed
11.08.2015 16:07:40 - begin Parent Job
11.08.2015 16:07:40 - Info RUNCMD (pid=8055) started
11.08.2015 16:07:40 - Info RUNCMD (pid=8055) exiting with status: 0
Operation Status: 0
11.08.2015 16:07:40 - end Parent Job; elapsed time 0:00:00
Operation Status: 0
Operation Status: 0
11.08.2015 16:07:41 - started process bpbrm (pid=8062)
11.08.2015 16:07:42 - Info bpbrm (pid=8062) dag01.corp.dir is the host to restore to
11.08.2015 16:07:42 - Info bpbrm (pid=8062) reading file list for client
11.08.2015 16:07:47 - Info bpbrm (pid=8062) client_pid=16456
11.08.2015 16:07:47 - Info bpbrm (pid=8062) from client dag01.corp.dir: TRV - BPRESOLVER has executed on server (FRSP0173)
11.08.2015 16:07:59 - Info bpresolver (pid=16456) done. status: 2
11.08.2015 16:07:59 - Error bpbrm (pid=8062) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup
11.08.2015 16:07:59 - Info bpresolver (pid=16456) done. status: 72: the client type is incorrect in the configuration database
Operation Status: 0
11.08.2015 16:07:59 - Info RUNCMD (pid=8208) started
11.08.2015 16:07:59 - Info RUNCMD (pid=8208) exiting with status: 0
Operation Status: 0
Operation Status: 2
Operation Status: 2
none of the requested files were backed up (2)
08-11-2015 09:15 AM
I'd say
"Error bpbrm (pid=8062) You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup"
is significant.
Did you follw the steps "ruene" described (which are correct if my memory serves me right, I'm on vacations at the moment)? The settings for DAG seem to be incorrect in your case.
Stefan
08-11-2015 09:29 AM
08-12-2015 04:03 AM
OK, Thank you.
Now i wait for updates from the Exchange admin.