I didn't see any file system backup attempt for this host.
As for Exchange, check this error:
Exchange2010 Shell Exception State of runspace is not valid for this operation. in function GetDBServers
This indicates something wrong on the exchange side. Please have Exchange, application and System event logs checked and find out what is going on, as backup fails as soon as this error is popping up.
Having no more logs, I think the most likely cause of this failure is some inconsistency in the Exchange replication. Please ensure that DAG replication is healthy and all nodes have the same Exchange log level.
Also please check the status of the writers by running:
vssadmin list writers
All writers have to be displayed as status [1], last error will most likely display /the Exchange writers) retryable
Did you fun a full backup of a writer level saveset?:
APPLICATIONS:\Microsoft Exchange 2010
Please try with that saveset (if other in place) and give it another try.
If you specify for instance the name of certain DB's, then after a failover is recommended to run a full backup at writer level, which means using saveset APPLICATIONS:\Microsoft Exchange 2010
CarlosRojas
1.7K Posts
0
February 4th, 2013 08:00
Hi Bernd,
I didn't see any file system backup attempt for this host.
As for Exchange, check this error:
Exchange2010 Shell Exception State of runspace is not valid for this operation. in function GetDBServers
This indicates something wrong on the exchange side. Please have Exchange, application and System event logs checked and find out what is going on, as backup fails as soon as this error is popping up.
Having no more logs, I think the most likely cause of this failure is some inconsistency in the Exchange replication. Please ensure that DAG replication is healthy and all nodes have the same Exchange log level.
Also please check the status of the writers by running:
vssadmin list writers
All writers have to be displayed as status [1], last error will most likely display /the Exchange writers) retryable
Thank you.
Carlos.
CarlosRojas
1.7K Posts
0
February 4th, 2013 04:00
Hi,
What is the level of the backup you ran when you got that failure?
What is the saveset you have specified on the client?
Did you fun a full backup of a writer level saveset?:
APPLICATIONS:\Microsoft Exchange 2010
What is the snapshot policy set for the group?
Thank you.
Carlos.
gotschy
1 Rookie
•
72 Posts
0
February 4th, 2013 05:00
Backup level is full
Snapshot Policy: "Serverless Backup"
Backup of filesystem savesets is a good idea and was not tested.
I will do it.
regards
Bernd
CarlosRojas
1.7K Posts
0
February 4th, 2013 05:00
Hi Bernd,
No, I didn't say File system, but Writer level:
Did you fun a full backup of a writer level saveset?:
APPLICATIONS:\Microsoft Exchange 2010
Please try with that saveset (if other in place) and give it another try.
If you specify for instance the name of certain DB's, then after a failover is recommended to run a full backup at writer level, which means using saveset APPLICATIONS:\Microsoft Exchange 2010
Thank you.
Carlos
gotschy
1 Rookie
•
72 Posts
0
February 4th, 2013 05:00
Hallo Carlos,
sorry, I misunderstood you suggestion. Saveset is APPLICATIONS:\Microsoft Exchange 2010 and
backup command nsrsnap_vss_save.
regards
Bernd
CarlosRojas
1.7K Posts
0
February 4th, 2013 06:00
Hi Bernd,
Could you please attach the nmm.log file?
Thank you.
Carlos.
gotschy
1 Rookie
•
72 Posts
0
February 4th, 2013 07:00
Hallo Carlos,
you can see in nmm.raw successful and unsuccessful backups.
Backup of filesystem files also failed.
I still search the reason.
regards
Bernd
1 Attachment
nmm.raw