I did a complete reinstall of NetWorker Client and NMM + GLR. Config Checker states, that everything is okay (only one warning, no fails). After rebooting the system, I get the same errors when issueing "nsrsnap_vss_save -v -?". There are still lots of PowerShell errors, although the commands are functioning in the Exchange PowerShell.
for all mounted DBs, except for the not mouted "Restore"-DB. Logs and edb-Files are on different disks.
I experimented with the Get-ExecutionPolicy command, to set it to "unrestricted" or "remoteSigned". Both had no effect on the nsrsnap_vss_save -v -? command.
CarlosRojas
1.7K Posts
0
February 13th, 2013 02:00
Hello Heiko,
What do you get when you run this Exchange cmdlets in Exchange Power Shell?:
Get-MailboxDatabase
Get-DatabaseAvailabilityGroup
Get-PublicFolderDatabase
Also, could you please attach the nmm.raw file from the NMM client?
Thank you.
Carlos.
Elviz42
37 Posts
0
February 13th, 2013 04:00
Hi Carlos,
thanx for your help. I re-ran Config Checker. It complains, that IPV6 is activated. I wouldn´t change this, if your problem is not related to this.
This is the output:
[PS] C:\Windows\system32>Get-MailboxDatabase
Name Server Recovery ReplicationType
---- ------ -------- ---------------
Mailbox Database 1512643350 DGHAMS88 False None
nd DGHAMS88 False None
so DGHAMS88 False None
msd DGHAMS88 False None
vgm DGHAMS88 False None
id DGHAMS88 False None
ikom DGHAMS88 False None
Restore DGHAMS88 False None
[PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
[PS] C:\Windows\system32>Get-PublicFolderDatabase
Name Server
---- ------
PublicFolder DGHAMS88
[PS] C:\Windows\system32>
I´ll send you the nmm.txt via email.
Thanx a lot
Heiko
CarlosRojas
1.7K Posts
0
February 13th, 2013 04:00
Hi Heiko,
I gather that this is stand alone Exchange 2010, right? It is not a DAG? as the command Get-DatabaseAvailabilityGroup didn't return any output.
In that case we would need to focus on the client configuration NMC.
Can you please let me know what backup command you have set, as well as all the Application Information variables?
Thank you.
Carlos
Elviz42
37 Posts
0
February 13th, 2013 05:00
Hi Carlos,
attached you´ll find our nmm.raw .
Thanx
Heiko
Von: CarlosRojas
Gesendet: Mittwoch, 13. Februar 2013 11:28
An: Kuhlmann, Heiko
Betreff: New message: "NMM Exchange 2010 Backup fails with PowerShell errors"
EMC Community Network
Re: NMM Exchange 2010 Backup fails with PowerShell errors
created by CarlosRojas in NetWorker Support Forum - View the full discussion
1 Attachment
nmm.txt
CarlosRojas
1.7K Posts
0
February 13th, 2013 05:00
Hi Heiko,
Is this DAG or stand-alone environment?
Please ensure that all the DB's are active and mounted:
nsrsnap_vss_save NSR warning NMM .. Exchange Database ikom is dismounted and not in the proper state for backup
nsrsnap_vss_save NSR warning NMM .. Exchange Database so is dismounted and not in the proper state for backup
same message for all DB's.
Please ensure that all DB's are mounted, or at least mount one of them and specify the correct saveset and give the backup another try.
Thank you.
Carlos.
Elviz42
37 Posts
0
February 13th, 2013 06:00
Hi Carlos,
The Exchange is Stand-Alone, your right. All DBs ARE mounted except for “Restore”:
Save Set is:
APPLICATIONS:\Microsoft Exchange 2010
Application Information:
NSR_SNAP_TYPE=vss
NSR_EXCH_RETAIN_SNAPSHOTS=yes
NSR_ALT_PATH=f:\mount4consistence
NSR_EXCH_CHECK=yes
NSR_ESE_UTIL_SEQUENTIAL=False
NSR_ESE_UTIL_THROTTLE=False
NSR_CHECK_JET_ERRORS=all
Backup command:
Nsrsnap_vss_save
Thanx for your help,
Heiko
Von: CarlosRojas
Gesendet: Mittwoch, 13. Februar 2013 14:17
An: Kuhlmann, Heiko
Betreff: New message: "NMM Exchange 2010 Backup fails with PowerShell errors"
EMC Community Network
Re: NMM Exchange 2010 Backup fails with PowerShell errors
created by CarlosRojas in NetWorker Support Forum - View the full discussion
1 Attachment
image001.png
Elviz42
37 Posts
0
February 14th, 2013 15:00
Hi Carlos,
I did a complete reinstall of NetWorker Client and NMM + GLR. Config Checker states, that everything is okay (only one warning, no fails). After rebooting the system, I get the same errors when issueing "nsrsnap_vss_save -v -?". There are still lots of PowerShell errors, although the commands are functioning in the Exchange PowerShell.
Do You have any idea?
Thanx for helping,
Heiko
CarlosRojas
1.7K Posts
0
February 15th, 2013 04:00
Hi Heiko,
Note that one of the DB's is not mounted, so do as follows:
Change the saveset to:
APPLICATIONS:\Microsoft Exchange 2010\id
Also I suspect that in at least one of the DB's you have the DB (.edb) file and the log files in the same path. If so please change that.
Thank you
Carlos
Elviz42
37 Posts
0
February 18th, 2013 08:00
Hi Carlos,
i changed the savesets to
APPLICATIONS:\Microsoft Exchange 2010\id
APPLICATIONS:\Microsoft Exchange 2010\nd
...
for all mounted DBs, except for the not mouted "Restore"-DB. Logs and edb-Files are on different disks.
I experimented with the Get-ExecutionPolicy command, to set it to "unrestricted" or "remoteSigned". Both had no effect on the nsrsnap_vss_save -v -? command.
Thanx for helping
Heiko
Elviz42
37 Posts
0
February 18th, 2013 12:00
I think I found it. I've forgotten to add the backup account to the Organization Management Exchange Security Group...
It is an old account, we always used for Exchange Backups (send-and-receive-rights etc. ) . It seems the Replication Manager part needs more rights.
So a big *RTFM* to myself, Nmm Install Guide, Page 19.
Thanx a lot for your help,
Heiko