07-12-2013 06:53 AM
I am using netback up 7.1 to make exchange backups, we have 5 databases to backup, now the problem is, when the backup running it does not backup all the databases.
Now I want to make a policy for each database to be backup
Here are the one that we run daily Microsoft Exchange Database Availability Groups:\
It then run this
NEW_STREAM
Microsoft Information Store:\Gauteng-Pretoria DB2
NEW_STREAM
Microsoft Information Store:\Gauteng-Pretoria DB3
Now I am trying to run this just for one database, but it gives me error, 130.
Microsoft Exchange Database Availability Groups:\Microsoft Information Store:\Gauteng-Pretoria DB1
I am doing this correct.
Clientname PRASSADAG01
07-12-2013 07:20 AM
Hendrik, please check out the NBU landing page:
and enter the search string: status 130 exchange
See if the results are helpful.
07-12-2013 07:24 AM
No this does not help, it only hsows the error code and nothing else.
Just want to know if my input is correct.
07-12-2013 07:30 AM
Try this:
Microsoft Exchange Database Availability Groups:\DB1
07-12-2013 07:33 AM
Please see Table 4-5 'Example policy that backs up a database for an Exchange DAG' on p. 64 of NBU for Microsoft SQL Server Admin Guide http://http://www.symantec.com/docs/DOC3670 :
07-12-2013 08:17 AM
If you open your policy you should be able to browse to the datbases and select them to ensure you have the correct paths
If they still fail with a 130 then it is something else causing the error
Hope this helps
07-13-2013 02:01 AM
Hi,
Exchange Writer is not in Satble state
VSSADMIN LIST writers and VSSADMIN LIST providers
You need to fix the Exchange Writers and they should stay in stable state until the Exchange backup completes and if they fail the snapshot processing will fail and you will get status code 130.
The Windows backup utility uses the System Writers in order to perform the snapshot creation for the entire server and that is expected.
Rgds,
Pawan
07-13-2013 03:49 AM
check the Event Viewer in Exchage server , you would probably see the errors related to this failurs..
take that error to exchage admin ask him to look in to that..
07-21-2013 07:21 AM
Please try it after re-starting Exchange replication & VSS services on both active & passive node.
Even ask Exchange admin to perform consistency check on the respective Databases/Data Stores.
07-21-2013 12:16 PM
08-06-2013 08:23 AM
There may be issue with Writers, chck the exchange writers or else try restarting the exchange replication services.!
08-20-2013 11:33 PM
can you ask exchange team to take windows level backup for perticular database which is failing with 130 error and let us know the status