04-28-2015 03:39 AM
Dear All,
product: Net backup 7.0.1
backup :exchange server 2010 (Not DAG )
Although Exchange database backuped succssfully,report in exchange server displays that no backup taken .
how to make sure that backup was taken or not ?
Best Regards,
Solved! Go to Solution.
04-30-2015 01:47 AM
HI Mahmoud
Do you see events logged right after backups were completed. (It might take time to show up in event viewer on exchange node which owns DB copy.
There should be ample info on backup timestamps event being logged.
This happed with me in past with same scenario NBU 701 with ex2010 dag Backups were successful however Exchange admin confirms with earlier timestamp of successful backups.
04-28-2015 03:53 AM
Does the backups are successfull with status code 0?
are you taking the backup from passive node?
i have seen this issue previoiusly , its more likely exchange side issues.. usually resolves in next backups or restart of replication between the passive and active nodes or with exchage server reboot.
<<EDIT>>, i misread it as DAG, please disagree my commnet above...
04-28-2015 04:17 AM
So, this is Standalone Exch 2010?
Please show us the Exchange policy config on the master:
bppllist <policy-name> -U
as well as all text in Job Details of successful job.
04-28-2015 04:38 AM
Does the backups are successfull with status code 0?
do you see any errors in event log at the time of backup?
04-28-2015 04:40 AM
Are you sure the Exchange database isn't on the exclude list. Please verify !!
http://www.symantec.com/docs/HOWTO85811
04-28-2015 04:57 AM
No it is not standalone it was (DAG) 2 servers cas & 2 hup one of them Virtual and the othe Physical but
exchange admin has aproblems in Virtual servers so he request to backup database is Physical server only ,
we edit the policy (clint) we deleted DAG and add the Physical server.and run the backup
text in Job Details of successful job.
4/28/2015 7:55:39 AM - estimated 81742249 Kbytes needed
4/28/2015 7:55:40 AM - started process bpbrm (4064)
4/28/2015 7:55:47 AM - connecting
4/28/2015 7:55:51 AM - connected; connect time: 00:00:04
4/28/2015 7:56:01 AM - begin writing
4/28/2015 8:29:27 AM - Info bpbrm(pid=4064) from client ucmx02b108: TRV - Exchange granular database changes were backed up successfully.
4/28/2015 8:29:47 AM - end writing; write time: 00:33:46
the requested operation was successfully completed(0)
04-28-2015 05:09 AM
Does the backups are successfull with status code 0?
yes.
do you see any errors in event log at the time of backup?
no.
04-28-2015 05:11 AM
Screenshot of Attributes tab only does not help.
Please show output of bppllist command from cmd on the master server (see my previous post).
The job above seems to be for an Incremental backup:
Exchange granular database changes were backed up successfully.
Please show us job details for a Full backup?
Ensure all of these log folders exist on Exch client for further troubleshooting:
bpresolver
bpfis
bpbkar
04-28-2015 05:20 AM
Exchange database isn't on the exclude list.
04-28-2015 06:08 AM
Agree with Marianne
Please attach the debug log as text files to a post - DO NOT bluk past into a post.
04-28-2015 06:39 AM
i run the command but how i can save it in txt file?
04-28-2015 06:45 AM
bppllist <policy-name> -U > C:\Temp\policy.txt
(Assuming C:\Temp folder exists. Create the folder if not or specify another folder).
To upload logs, copy log files on the Exch server to .txt (e.g. bpresolver.txt) and then use 'File attachments' link at the bottom of this page to upload the text files.
04-28-2015 06:57 AM
i run the command as follows,
C:\>Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe exchange_temp -U > C:\Temp\policy.txt
'Program' is not recognized as an internal or external command, operable program or batch file.
04-28-2015 07:02 AM
There is a space in "Program Files". Put the entire path and command in quotes or else cd into the path.
"C:\>Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe" Exchange_temp -U > C:\Temp\policy.txt
Have you checked if C:\Temp folder exists?
04-28-2015 07:18 AM
------------------------------------------------------------
Policy Name: exchange_temp
Policy Type: MS-Exchange-Server
Active: yes
Effective date: 09/26/2010 16:17:23
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: EXCH_new_temp
Volume Pool: Daily
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Exchange Source active db: yes
Exchange 2010 Preferred Server: server1 server2
Granular Restore Info: yes
Ignore Client Direct: no
HW/OS/Client: Windows-x86 Windows2008 server1
Include: Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-CO
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-EXP
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-FC
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-INT
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-OPR
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-PLN
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-PRD
Schedule: full
Type: Automatic Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 5 (3 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 1
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Sunday, Week 2
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Sunday, Week 3
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Sunday, Week 4
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Sunday, Week 5
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
EXCLUDE DATE 0 - 01/19/2012
EXCLUDE DATE 1 - 01/20/2012
EXCLUDE DATE 2 - 01/21/2012
EXCLUDE DATE 3 - 02/09/2012
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 22:00:00 --> Sunday 24:00:00
Monday 22:00:00 --> Monday 24:00:00
Tuesday 22:00:00 --> Tuesday 24:00:00
Wednesday 22:00:00 --> Wednesday 24:00:00
Thursday 22:00:00 --> Thursday 24:00:00
Friday 22:00:00 --> Friday 24:00:00
Saturday 22:00:00 --> Saturday 24:00:00
04-28-2015 07:23 AM
------------------------------------------------------------
Policy Name: exchange_temp
Policy Type: MS-Exchange-Server
Active: yes
Effective date: 09/26/2010 16:17:23
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: EXCH_new_temp
Volume Pool: Daily
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Exchange Source active db: yes
Exchange 2010 Preferred Server: server1 server2
Granular Restore Info: yes
Ignore Client Direct: no
HW/OS/Client: Windows-x86 Windows2008 server1
Include: Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-CO
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-EXP
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-FC
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-INT
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-OPR
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-PLN
Microsoft Exchange Database Availability Groups:\UCMXDAG1\Microsoft Information Store\EX-PRD
Schedule: full
Type: Automatic Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 5 (3 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 1
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Sunday, Week 2
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Sunday, Week 3
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Sunday, Week 4
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Sunday, Week 5
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
EXCLUDE DATE 0 - 01/19/2012
EXCLUDE DATE 1 - 01/20/2012
EXCLUDE DATE 2 - 01/21/2012
EXCLUDE DATE 3 - 02/09/2012
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 22:00:00 --> Sunday 24:00:00
Monday 22:00:00 --> Monday 24:00:00
Tuesday 22:00:00 --> Tuesday 24:00:00
Wednesday 22:00:00 --> Wednesday 24:00:00
Thursday 22:00:00 --> Thursday 24:00:00
Friday 22:00:00 --> Friday 24:00:00
Saturday 22:00:00 --> Saturday 24:00:00
04-28-2015 07:45 AM
exchange
04-28-2015 07:50 AM
Thanks for the policy config.
We now need Details of a Full backup.
The previous info seems to be from an Incr backup.
Please select 'Allow Multiple Data Streams' in the policy attributes.
This will create a new job for each IS and make troubleshooting a bit easier.
Remember to create log folders as suggested earlier.
04-29-2015 07:57 AM
Hi,
1) Have u checked the compatability list for exchange servers. Even service pack matters
2) If the exchange server is compatible , kindly post the ouput of bpps from client. There may be stuck bpfis process or any other related process
04-30-2015 01:03 AM