This post is more than 5 years old
34 Posts
0
10258
Problem with Backup Exchange 2010 (Passive)
Hello,
I have problems with the backup Exchange 2010 DB passive. I ran the config checker, everythings fine, after 15 minute send me the following error.
savegrp: suppressed 6 lines of verbose output
The term 'Get-DatabaseAvailabilityGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxServer failed.
The term 'Get-MailboxServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
80873:nsrsnap_vss_save:NMM ..DAG name entered for client not in a DAG. Cannot continue.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
Internal error.
68151 1350952447 2 0 0 8576 7152 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
I can list the save set, but with the following information:
C:\Program Files\Legato\nsr\bin>nsrsnap_vss_save -v -?
NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for
multi NIC client.
List of valid saveset entries for APPLICATIONS on client mxpmbx02.pmi.pmicim.com
...
Initializing data to display...
NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchan
ge 2010.
Failed to initialize PowerShell session, retrying to initialize Powershell sessi
on using credentials...
Creating RemotePowershellBase failed.
Connecting to remote server failed with the following error message : The WS-Man
agement service cannot process the request. The system load quota of 1000 reques
ts per 2 seconds has been exceeded. Send future requests at a slower rate or rai
se the system quota. The next request from this user will not be approved for at
least 741870464 milliseconds. For more information, see the about_Remote_Troubl
eshooting Help topic.
powershell.Invoke Get-DatabaseAvailabilityGroup failed.
The term 'Get-DatabaseAvailabilityGroup' is not recognized as the name of a cmdl
et, function, script file, or operable program. Check the spelling of the name,
or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-PublicFolderDatabase failed.
The term 'Get-PublicFolderDatabase' is not recognized as the name of a cmdlet, f
unction, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, functi
on, script file, or operable program. Check the spelling of the name, or if a pa
th was included, verify that the path is correct and try again.
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 8 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 5 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 6 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 7 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 2 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 3 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 1 -- Passive"
powershell.Invoke Get-MailboxDatabaseCopyStatus failed.
The term 'Get-MailboxDatabaseCopyStatus' is not recognized as the name of a cmdl
et, function, script file, or operable program. Check the spelling of the name,
or if a path was included, verify that the path is correct and try again.
79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an
instance of an object.
"APPLICATIONS:\Microsoft Exchange 2010\Public Folder MXPMBX02 -- Active"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
_______________________________________________
My configuration is:
Networker Server & Client Version: 7.6.3
NMM Version 2.3.0
DAG environment Exchange 2010 and W2008 Server R2
Phisycal Clients:
Name: mxpmbx01.pmi.pmicim.com
Name: mxpmbx02.pmi.pmicim.com
SaveSet:
APPLICATIONS:\Microsoft Exchange 2010\Mailbox X
Configurations Clients
Backup command: nsrsnap_vss_save.exe
Application information:
NSR_SNAP_TYPE=vss
NSR_EXCH2010_DAG=.MXPDAG01.pmi.pmicim.com
NSR_EXCH2010_BACKUP=passive
NSR_ALT_PATH=N:\Backup
Configuration DAG Client:
Name: MXPDAG01.pmi.pmicim.com
SaveSet: APPLICATIONS:\Microsoft Exchange 2010\Mailbox X
Backup command: nsrsnap_vss_save.exe
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=N:\Backup
Could you help me to tried undesrtand why I cant backup the DB in passive mode on DAG and why the error send "DAG name entered for client not in a DAG" . if I put the DAG name with FQDN.
Regards
Bebo2k
544 Posts
0
October 25th, 2012 14:00
Hi Michael,
Circular logging must be disabled, this is a Microsoft limitation. For more information check the following EMC KB article:
https://support.emc.com/kb/122216
Disable the circular logging and re-run the backup again. Waiting your updates.
Thanks,
Ahmed Bahaa
Bebo2k
544 Posts
0
October 22nd, 2012 18:00
Hi Michael,
What the status of the vss writers ? vssadmin list writers
Do you have IPv6 enabled ?
Is there any errors in the Exchange applicaiton event logs (event viewer) ?
I would suggest you to do the following as well:
1- Stop NetWorker services ( NetWorker Remote, NetWorker PowerSnap and the two Replication Manager services)
2- Rename the /nsr/tmp directory to tmp.old on the client.
3- Start NetWorker Remote service, NetWorker PowerSnap and the Replicaiton Manager AgantPS respectively, and dont start the Replication Manager Exchange Interface service as it is manual service and will be started when it is needed, so leave it in the stopped manual state.
4- Run the nsrsnap_vss_save -v -? again and check if the output changed or not. If changed re-run the backup again.
If the above steps didnt solve the issue, please provide us with the answers of the first three questions and attach the nmm.raw file.
Thanks,
Ahmed Bahaa
ahmetkececiler
68 Posts
0
October 23rd, 2012 03:00
Hi,
Did you try this
IIS settings
Start IIS Manager
Navigate to à Sites à Default Web Site
Select 'Bindings' under Actions - Edit Site or right click 'Default Web Site' and do properties -> Bindings.
Under Site Bindings, look for 'https' entry, select it and do 'Edit'
In Edit site Bindings Ensure 'SSL certificate' shows Microsoft Exchange (The certificate name may be different)
If the https binding does not exists for Exchange, create a new binding. (One for all 'all assigned' IP address and one for the local host (127.0.0.1))
Restart IIS.
Rerun the backup.
dll register
C:\windows\Microsoft.NET\Framework64\v2.0.50727\regasm "C:\Program Files\Legato\nsr\bin\libnmexchmgmt.dll" /verbose
Also check the IIS settings for windows authentication and kernel authentiaction mode.
Could you please try to run this command on dag client
nsrsnap_vss_save.exe -? -v
Bebo2k
544 Posts
0
October 23rd, 2012 05:00
Hi Michael,
In addition to the steps provided above, I recommend you to upgrade your NMM to version 2.3.122 (Build 122) that includes a lot of important fixes.
Waiting your updates.
Ahmed Bahaa
Michael891
34 Posts
0
October 23rd, 2012 10:00
Hi Ahmed,
The version of NMM is 2.3.0.109.
and I respond your questions.
What the status of the vss writers ? vssadmin list writers
C:\Program Files\Legato\nsr\bin>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {9b0ed482-c8eb-4f21-a12b-c205803a3891}
State: Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b4d468a-bb49-4db7-9d2c-6d322273ad58}
State: Stable
Last error: No error
Writer name: 'Microsoft Exchange Replica Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {874e7a29-314d-4409-8fca-bfc339ff1d33}
State: Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {430b1a93-42f5-49ab-ba15-a51dc2e140c3}
State: Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {be7e21d4-c879-453b-9804-bee708e8583b}
State: Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {b8bb05d9-8b8b-4b6a-a938-dfa53e2612fd}
State: Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {86e1cac2-aa04-4b7e-bfeb-f628127f2816}
State: Stable
Last error: No error
Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {47e43a16-a073-45dd-8fbd-ac81e9585521}
State: Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {f255286a-bda4-4ab3-a17e-2fcfa3a71fcb}
State: Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {ff3de8e1-cd19-463f-beb9-44961d469d61}
State: Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {324c0ecb-8264-4f98-9f2f-ebbfb8bf6931}
State: Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {830eb1df-b805-4c5c-8da8-a6e7fd24ebd3}
State: Stable
Last error: No error
I can See that all is Fine.
Do you have IPv6 enabled ?
In this part I was ran the Config checker on server mxpmbx02.pmi.pmicim.com and I can see the following:
Checking IPV6 component configuration status in the registry as per Microsoft KB 929852.
Checking registry key .
WARNING: DisabledComponents value is not found. Please create and set value 0xffffffff(DWORD), which disables all IPv6 components.
This part alredy ask for check it to Exchange Admin for fix.
In the log Event viewer only appers
NMM backup failed to complete successfully.
I applied your suggest and the backup still fail.
Regards
Bebo2k
544 Posts
0
October 23rd, 2012 12:00
Hi Michael,
Ok, IPv6 must be disabled, so you have to push on the Exchange admin to fix that and re-run the config checker again.
Is there in the Event viewer any other events and errors related to Authentication ? When you run the Config Checker, is all the checks are correct and green or you have some warnings and errors (other than the IPv6 and the NMM backup failure) ?
Try to run from the Exchange client the command vssclupdate.exe and then run the nsrsnap_vss_save -D3vvvv -? , and provide us the output
Did you checked the steps provided previously by ahmetkececiler ?
Would you please attach the nmm.raw for more information ? You can attach it here via the advanced editor.
Waiting your updates.
Thanks,
Ahmed Bahaa
Michael891
34 Posts
0
October 23rd, 2012 15:00
Hi AHmed,
Thanks for all your help.
I update the NMM for the version 2.3 Build 122 and I review th part that send me ahmetkececiler and the IIS for Binding and Permissions is OK. Run the \regasm "C:\Program Files\Legato\
nsr\bin\libnmexchmgmt.dll" /verbose and the output was the following:
Microsoft (R) .NET Framework Assembly Registration Utility 2.0.50727.5420
Copyright (C) Microsoft Corporation 1998-2004. All rights reserved.
Types registered successfully
After run the following commands and the output was:
C:\Program Files\Legato\nsr\bin>vssclupdate.exe
C:\Program Files\Legato\nsr\bin>nsrsnap_vss_save -D3vvvv -? > C:\outputNMM.txt
Samehost test for host1 - null and host2 - MXPMBX02, and determined to be the sa
me machine which is null.
DNS cache:
host: 10.1.1.2, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: 127.0.0.1, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: 169.254.2.136, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: 172.19.120.27, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: ::1, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: fe80::a9fc:748a:e926:9ad9, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.co
m
host: localhost, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: MXPMBX02, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
host: MXPMBX02.pmi.pmicim.com, status: STATUS_OK, head: MXPMBX02.pmi.pmicim.com
Clients cache:
NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for
multi NIC client.
NMM .. started RM session with client.
NMM .. created RM deposit path C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_2317
1012596.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Task Scheduler Writer2317101493.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\VSS Metadata Store Writer23171014670.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Performance Counters Writer23171015232.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\System Writer23171015794.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Microsoft Exchange Replica Writer2317101789.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\ASR Writer23171017744.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\IIS Metabase Writer23171018321.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Microsoft Exchange Writer23171018898.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\IIS Config Writer23171019491.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Shadow Copy Optimization Writer2317102053.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Cluster Database23171020630.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\WMI Writer23171021191.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\Registry Writer23171021753.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\BITS Writer23171022330.xml.
NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012
596\COM+ REGDB Writer23171022892.xml.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1572
Bound TCP/IPv6 socket descriptor 1572 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1576
Bound TCP/IPv6 socket descriptor 1576 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1580
Bound TCP/IPv6 socket descriptor 1580 to port 7938
Attempting to bind IPv6 socket descriptor 1580
Bound TCP/IPv6 socket descriptor 1580 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1576
Bound TCP/IPv6 socket descriptor 1576 to port 7938
Attempting to bind IPv6 socket descriptor 1576
Bound TCP/IPv6 socket descriptor 1576 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. writer ASR Writer is not supported and will not participate in the replic
a. Writers files will be skipped during backup.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1580
Bound TCP/IPv6 socket descriptor 1580 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1584
Bound TCP/IPv6 socket descriptor 1584 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1588
Bound TCP/IPv6 socket descriptor 1588 to port 7938
Attempting to bind IPv6 socket descriptor 1588
Bound TCP/IPv6 socket descriptor 1588 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1584
Bound TCP/IPv6 socket descriptor 1584 to port 7938
Attempting to bind IPv6 socket descriptor 1584
Bound TCP/IPv6 socket descriptor 1584 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Informational .. writer BITS Writer has no components.
NMM .. Supported writer BITS Writer vss type System Service - NMM saveset type S
YSTEM COMPONENTS.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1588
Bound TCP/IPv6 socket descriptor 1588 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1592
Bound TCP/IPv6 socket descriptor 1592 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1596
Bound TCP/IPv6 socket descriptor 1596 to port 7938
Attempting to bind IPv6 socket descriptor 1596
Bound TCP/IPv6 socket descriptor 1596 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1592
Bound TCP/IPv6 socket descriptor 1592 to port 7938
Attempting to bind IPv6 socket descriptor 1592
Bound TCP/IPv6 socket descriptor 1592 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer Cluster Database vss type Bootable System State - NMM sa
veset type SYSTEM COMPONENTS.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1596
Bound TCP/IPv6 socket descriptor 1596 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1600
Bound TCP/IPv6 socket descriptor 1600 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1604
Bound TCP/IPv6 socket descriptor 1604 to port 7938
Attempting to bind IPv6 socket descriptor 1604
Bound TCP/IPv6 socket descriptor 1604 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1600
Bound TCP/IPv6 socket descriptor 1600 to port 7938
Attempting to bind IPv6 socket descriptor 1600
Bound TCP/IPv6 socket descriptor 1600 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer COM+ REGDB Writer vss type Bootable System State - NMM s
aveset type SYSTEM COMPONENTS:\BootableSystemState.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1604
Bound TCP/IPv6 socket descriptor 1604 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1608
Bound TCP/IPv6 socket descriptor 1608 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1612
Bound TCP/IPv6 socket descriptor 1612 to port 7938
Attempting to bind IPv6 socket descriptor 1612
Bound TCP/IPv6 socket descriptor 1612 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1608
Bound TCP/IPv6 socket descriptor 1608 to port 7938
Attempting to bind IPv6 socket descriptor 1608
Bound TCP/IPv6 socket descriptor 1608 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer IIS Config Writer vss type System Service - NMM saveset
type SYSTEM COMPONENTS.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1612
Bound TCP/IPv6 socket descriptor 1612 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1616
Bound TCP/IPv6 socket descriptor 1616 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1620
Bound TCP/IPv6 socket descriptor 1620 to port 7938
Attempting to bind IPv6 socket descriptor 1620
Bound TCP/IPv6 socket descriptor 1620 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1616
Bound TCP/IPv6 socket descriptor 1616 to port 7938
Attempting to bind IPv6 socket descriptor 1616
Bound TCP/IPv6 socket descriptor 1616 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer IIS Metabase Writer vss type System Service - NMM savese
t type SYSTEM COMPONENTS.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1644
Bound TCP/IPv6 socket descriptor 1644 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1640
Bound TCP/IPv6 socket descriptor 1640 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1692
Bound TCP/IPv6 socket descriptor 1692 to port 7938
Attempting to bind IPv6 socket descriptor 1692
Bound TCP/IPv6 socket descriptor 1692 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 1640
Bound TCP/IPv6 socket descriptor 1640 to port 7938
Attempting to bind IPv6 socket descriptor 1640
Bound TCP/IPv6 socket descriptor 1640 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2652
Bound TCP/IPv6 socket descriptor 2652 to port 7938
Attempting to bind IPv6 socket descriptor 2652
Bound TCP/IPv6 socket descriptor 2652 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer System Writer vss type Bootable System State - NMM saves
et type SYSTEM COMPONENTS.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2656
Bound TCP/IPv6 socket descriptor 2656 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2660
Bound TCP/IPv6 socket descriptor 2660 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2880
Bound TCP/IPv6 socket descriptor 2880 to port 7938
Attempting to bind IPv6 socket descriptor 2880
Bound TCP/IPv6 socket descriptor 2880 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2660
Bound TCP/IPv6 socket descriptor 2660 to port 7938
Attempting to bind IPv6 socket descriptor 2660
Bound TCP/IPv6 socket descriptor 2660 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer Task Scheduler Writer vss type Bootable System State - N
MM saveset type SYSTEM COMPONENTS:\BootableSystemState.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2880
Bound TCP/IPv6 socket descriptor 2880 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2816
Bound TCP/IPv6 socket descriptor 2816 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2820
Bound TCP/IPv6 socket descriptor 2820 to port 7938
Attempting to bind IPv6 socket descriptor 2820
Bound TCP/IPv6 socket descriptor 2820 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2816
Bound TCP/IPv6 socket descriptor 2816 to port 7938
Attempting to bind IPv6 socket descriptor 2816
Bound TCP/IPv6 socket descriptor 2816 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer VSS Metadata Store Writer vss type Bootable System State
- NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2820
Bound TCP/IPv6 socket descriptor 2820 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2424
Bound TCP/IPv6 socket descriptor 2424 to port 7937
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2480
Bound TCP/IPv6 socket descriptor 2480 to port 7938
Attempting to bind IPv6 socket descriptor 2480
Bound TCP/IPv6 socket descriptor 2480 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
lgto_auth for `nsrexec' succeeded
Creating tcp RPC client handle with host localhost (::1)
Attempting to bind IPv6 socket descriptor 2424
Bound TCP/IPv6 socket descriptor 2424 to port 7938
Attempting to bind IPv6 socket descriptor 2424
Bound TCP/IPv6 socket descriptor 2424 to port 9226
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
NMM .. Supported writer WMI Writer vss type System Service - NMM saveset type SY
STEM COMPONENTS.
79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an
instance of an object.
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Failed to initialize PowerShell session, retrying to initialize Powershell session using credentials...
Creating RemotePowershellBase failed.
Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the system quota. The next request from this user will not be approved for at least 664882816 milliseconds. For more information, see the about_Remote_Troubleshooting Help topic.
powershell.Invoke Get-DatabaseAvailabilityGroup failed.
The term 'Get-DatabaseAvailabilityGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-PublicFolderDatabase failed.
The term 'Get-PublicFolderDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabase failed.
The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
powershell.Invoke Get-MailboxDatabaseCopyStatus failed.
The term 'Get-MailboxDatabaseCopyStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
List of valid saveset entries for APPLICATIONS on client mxpmbx02.pmi.pmicim.com ...
Initializing data to display...
NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchange 2010.
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 8"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 5"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 6"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 7"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 2"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 3"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 1"
"APPLICATIONS:\Microsoft Exchange 2010\Public Folder MXPMBX02"
nmm.raw log
0 23/10/2012 12:10:00 p.m. 0 0 1 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for multi NIC client.
64712 23/10/2012 12:10:00 p.m. 1 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RMAPI version: 5.3.0.2
63344 23/10/2012 12:10:02 p.m. 1 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM has initialized Replication Manager in preparation for displaying Writer Metadata.
80745 23/10/2012 12:10:15 p.m. 1 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchange 2010.
79598 23/10/2012 12:10:19 p.m. 5 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Exchange2010 Shell Object reference not set to an instance of an object.
63309 23/10/2012 12:10:19 p.m. 1 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68150 23/10/2012 12:10:19 p.m. 2 0 0 10184 5752 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with success.
52701 23/10/2012 12:41:36 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Command line:\n C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe -A optype=conventional -A NSR_SNAP_TYPE=vss -A NSR_EXCH2010_BACKUP=passive -A NSR_EXCH2010_DAG=mxpdag01.pmi.pmicim.com -A NSR_ALT_PATH=N:\Backup -A NSR_PARENT_JOBID=1277480 -c mxpmbx02.pmi.pmicim.com -g Prueba -LL -m mxpmbx02.pmi.pmicim.com -s vwcapbckp002.pemex.pmx.com -l full -q -W 78 -A snap_sessionid=1351014096 -A NSR_STRICT_SYNC=0 -A NSR_PS_DEBUG_ID=1351014092 -A NSRSNAP_JOBID=1277482 APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4
52702 23/10/2012 12:41:36 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save System Version: 6.1 Build 7601 S
52705 23/10/2012 12:41:36 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Computer Name: MXPMBX02 User Name: NT AUTHORITY\SYSTEM (SYSTEM)
73064 23/10/2012 12:41:36 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe:\n Original file name: nsrsnap_vss_save.exe\n Version: 2.3.0.109\n Comments: NetWorker Module for Microsoft Applications (x64)
52681 23/10/2012 12:41:37 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NetWorker Server Version: NetWorker 7.6.3.4.Build.879 NetWorker Source Capacity Data Zone Enabler
50423 23/10/2012 12:41:37 p.m. 0 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Unknown Application Information parameter: NSRSNAP_JOBID, may not be supported
50411 23/10/2012 12:41:37 p.m. 0 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Data mover host name not specified. Assuming local host: mxpmbx02.pmi.pmicim.com
50402 23/10/2012 12:41:39 p.m. 0 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Inserting APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4 in saveset list
80271 23/10/2012 12:41:39 p.m. 0 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Valid snapshot policy. Group: "Prueba" Snapshot Policy: "Serverless Backup" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
80873 23/10/2012 12:41:41 p.m. 5 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ..DAG name entered for client not in a DAG. Cannot continue.
63335 23/10/2012 12:41:41 p.m. 5 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM backup failed to complete successfully.
50404 23/10/2012 12:41:41 p.m. 0 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed
0 23/10/2012 12:41:41 p.m. 2 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4: failed
63309 23/10/2012 12:41:41 p.m. 1 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68151 23/10/2012 12:41:41 p.m. 2 0 0 4080 7052 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure.
52701 23/10/2012 12:41:58 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Command line:\n C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe -A optype=conventional -A NSR_SNAP_TYPE=vss -A NSR_EXCH2010_BACKUP=passive -A NSR_EXCH2010_DAG=mxpdag01.pmi.pmicim.com -A NSR_ALT_PATH=N:\Backup -A NSR_PARENT_JOBID=1277480 -c mxpmbx02.pmi.pmicim.com -g Prueba -LL -m mxpmbx02.pmi.pmicim.com -s vwcapbckp002.pemex.pmx.com -l full -q -W 78 -A snap_sessionid=1351014117 -A NSR_STRICT_SYNC=0 -A NSR_PS_DEBUG_ID=1351014112 -A NSRSNAP_JOBID=1277484 APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4
52702 23/10/2012 12:41:58 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save System Version: 6.1 Build 7601 S
52705 23/10/2012 12:41:58 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Computer Name: MXPMBX02 User Name: NT AUTHORITY\SYSTEM (SYSTEM)
73064 23/10/2012 12:41:58 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save Version information for C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe:\n Original file name: nsrsnap_vss_save.exe\n Version: 2.3.0.109\n Comments: NetWorker Module for Microsoft Applications (x64)
52681 23/10/2012 12:41:59 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NetWorker Server Version: NetWorker 7.6.3.4.Build.879 NetWorker Source Capacity Data Zone Enabler
50423 23/10/2012 12:41:59 p.m. 0 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Unknown Application Information parameter: NSRSNAP_JOBID, may not be supported
50411 23/10/2012 12:41:59 p.m. 0 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Data mover host name not specified. Assuming local host: mxpmbx02.pmi.pmicim.com
50402 23/10/2012 12:42:01 p.m. 0 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Inserting APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4 in saveset list
80271 23/10/2012 12:42:02 p.m. 0 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Valid snapshot policy. Group: "Prueba" Snapshot Policy: "Serverless Backup" Snapshots Per Day: "1" Retain: "0" Backup Snapshots: "All" Level: "full".
80873 23/10/2012 12:42:03 p.m. 5 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ..DAG name entered for client not in a DAG. Cannot continue.
63335 23/10/2012 12:42:03 p.m. 5 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM backup failed to complete successfully.
50404 23/10/2012 12:42:03 p.m. 0 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed
0 23/10/2012 12:42:03 p.m. 2 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4: failed
63309 23/10/2012 12:42:03 p.m. 1 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68151 23/10/2012 12:42:03 p.m. 2 0 0 8084 10396 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure.
0 23/10/2012 04:01:58 p.m. 0 0 1 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for multi NIC client.
64712 23/10/2012 04:01:58 p.m. 1 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RMAPI version: 5.3.0.2
63344 23/10/2012 04:02:00 p.m. 1 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM has initialized Replication Manager in preparation for displaying Writer Metadata.
80745 23/10/2012 04:02:13 p.m. 1 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchange 2010.
79598 23/10/2012 04:02:16 p.m. 5 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Exchange2010 Shell Object reference not set to an instance of an object.
63309 23/10/2012 04:02:16 p.m. 1 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68150 23/10/2012 04:02:16 p.m. 2 0 0 10528 8784 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with success.
0 23/10/2012 05:04:35 p.m. 0 0 1 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for multi NIC client.
64712 23/10/2012 05:04:35 p.m. 1 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RMAPI version: 5.3.0.2
63344 23/10/2012 05:04:36 p.m. 1 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM has initialized Replication Manager in preparation for displaying Writer Metadata.
80745 23/10/2012 05:04:48 p.m. 1 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchange 2010.
79598 23/10/2012 05:04:52 p.m. 5 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Exchange2010 Shell Object reference not set to an instance of an object.
63309 23/10/2012 05:04:52 p.m. 1 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68150 23/10/2012 05:04:52 p.m. 2 0 0 9512 6928 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with success.
0 23/10/2012 05:10:11 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for multi NIC client.
64712 23/10/2012 05:10:11 p.m. 1 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RMAPI version: 5.3.0.2
0 23/10/2012 05:10:12 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. started RM session with client.
63344 23/10/2012 05:10:12 p.m. 1 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM has initialized Replication Manager in preparation for displaying Writer Metadata.
0 23/10/2012 05:10:12 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. created RM deposit path C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596.
0 23/10/2012 05:10:14 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Task Scheduler Writer2317101493.xml.
0 23/10/2012 05:10:15 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\VSS Metadata Store Writer23171014670.xml.
0 23/10/2012 05:10:15 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Performance Counters Writer23171015232.xml.
0 23/10/2012 05:10:17 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\System Writer23171015794.xml.
0 23/10/2012 05:10:17 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Microsoft Exchange Replica Writer2317101789.xml.
0 23/10/2012 05:10:18 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\ASR Writer23171017744.xml.
0 23/10/2012 05:10:18 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\IIS Metabase Writer23171018321.xml.
0 23/10/2012 05:10:19 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Microsoft Exchange Writer23171018898.xml.
0 23/10/2012 05:10:20 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\IIS Config Writer23171019491.xml.
0 23/10/2012 05:10:20 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Shadow Copy Optimization Writer2317102053.xml.
0 23/10/2012 05:10:21 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Cluster Database23171020630.xml.
0 23/10/2012 05:10:21 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\WMI Writer23171021191.xml.
0 23/10/2012 05:10:22 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\Registry Writer23171021753.xml.
0 23/10/2012 05:10:22 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\BITS Writer23171022330.xml.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. RM deposited WMD -- C:\Users\dctibk01\AppData\Local\Temp\3\RMDir_23171012596\COM+ REGDB Writer23171022892.xml.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. writer ASR Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Informational .. writer BITS Writer has no components.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer BITS Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Cluster Database vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer COM+ REGDB Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
0 23/10/2012 05:10:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer IIS Config Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
0 23/10/2012 05:10:24 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer IIS Metabase Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
80745 23/10/2012 05:10:24 p.m. 1 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchange 2010.
0 23/10/2012 05:10:25 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:22 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:22 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:22 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Microsoft Exchange Replica Writer vss type User Data - NMM saveset type APPLICATIONS.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. unable to obtain database distinguished name or object class for adding to opaque data. Could negate directed recover later.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Microsoft Exchange Writer vss type User Data - NMM saveset type APPLICATIONS.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Performance Counters Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Registry Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Informational .. writer Shadow Copy Optimization Writer has no components.
0 23/10/2012 05:11:23 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Shadow Copy Optimization Writer vss type User Data - NMM saveset type APPLICATIONS.
0 23/10/2012 05:11:24 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer System Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS.
0 23/10/2012 05:11:24 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer Task Scheduler Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
0 23/10/2012 05:11:24 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer VSS Metadata Store Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
0 23/10/2012 05:11:24 p.m. 0 0 1 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Supported writer WMI Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
79598 23/10/2012 05:11:26 p.m. 5 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. Exchange2010 Shell Object reference not set to an instance of an object.
63309 23/10/2012 05:13:16 p.m. 1 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save NMM .. bye bye.
68150 23/10/2012 05:13:16 p.m. 2 0 0 9020 5336 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save nsrsnap_vss_save: Exiting with success.
Regards
Bebo2k
544 Posts
0
October 23rd, 2012 17:00
Hi Michael,
It seems that you have different problems, so we will try to fix it one by one and this will needs hands from the Exchange Admins:
1- IPv6 is still enabled and this may be the main reason for the issue, so please disable the IPv6 using the following Microsoft article:
http://support.microsoft.com/kb/929852
2- The second error is "Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded", This is mainly an Exchange issue where the user who had permission to communicate with the Exchange (either by PowerShell or even by GUI ) is not able to initialize or process any requests to Exchange, and this occurs when NetWorker tries to get the Exchange databases available on the host. This error will be reported as well in the Event viewer under Event ID 32784 . To fix this issue, you have to run firstly iisreset command which may solve the problem. If the problem still occurs, your Exchange Admin have to check some Microsoft Technet threads like :
http://social.technet.microsoft.com/Forums/en/exchange2010/thread/4d396628-3867-4c95-9541-e0eb021e0135
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/1cc17514-44dc-41d9-b319-3232107490c0
Or contact Microsoft to check this issue and solve it.
3- The third error is "The term 'Get-MailboxDatabase' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again" . On the Exchange host, launch Exchange Management Shell. At the command prompt, run the command:
Get-mailboxserver -identity mxpmbx02
The hostname should be mxpmbx02.pmi.pmicim.com . The correct DAG name should be mxpdag01.pmi.pmicim.com returned from the command:
Get-DatabaseAvailibilityGroup -Identity mxpdag01| fl
Make sure that the names are correct.
4- Make sure the you can resolve the DAG name from the backup server (Shortname & FQDN), as well as the Exchange nodes as well, using the ping, nslookup and rpcinfo -p clientname , may be you have a naming resolution or communication problem.
5- You may had a permission issue where the Replication Manager Exchange Interface has a logon information with a user with no permissions on Exchange. Use the following procedure to change the user account or password information for the COM+ component with an account that is Exchange Admin:
This will also modify the account information for the Replication Manager Exchange Interface Service.
After performing the above steps and clear all of them, please run the backup again to check if the problem solved or not. If still persists, please run NMM Config Checker and attach here the report results to check what else is missing.
Hope this helps you, Waiting your update.
Ahmed Bahaa
Bebo2k
544 Posts
0
October 23rd, 2012 17:00
Forgot to mention before running the backup, do the same steps I provided before again:
1- Stop NetWorker services ( NetWorker Remote, NetWorker PowerSnap and the two Replication Manager services)
2- Rename the /nsr/tmp directory to tmp.old on the client.
3- Start NetWorker Remote service, NetWorker PowerSnap and the Replicaiton Manager AgantPS respectively, and dont start the Replication Manager Exchange Interface service as it is manual service and will be started when it is needed, so leave it in the stopped manual state.
4- Run from the Exchange client the command vssclupdate.exe
After that run the backup and if the problem still persists, please run the Config Checker and attach the report here.
Thanks,
Ahmed Bahaa
Michael891
34 Posts
0
October 24th, 2012 13:00
Hello Ahmed,
Thaks four your answer.
I attached the config checker files from the 2 servers.
Only we need the IPv6 and with the Admin exchange Server and the error with the connection remote that you mention me.
When we can review the above, so run the backup.
Thaks for all your help Ahmed.
Regards
1 Attachment
EMC Config Checker.doc
Bebo2k
544 Posts
0
October 24th, 2012 14:00
Hi Michael,
Thanks for the config checker report, it seems good, just waiting for disabling the IPv6 components by the registry key and check the Exchange connection issue.
Additionally please double check with the Exchange Admins the configurations of the Mailbox Databases and the Public Folders database as well. Because there is the following warning about the database path and log path. Just check which scenario is the databases and logs paths configured. You have below the supported and unsupported scenarios:
The database path and log path is recommended to be in different volumes for database name:[ Mailbox 8] in Exchange 2010.
Below are the supported and unsupported scenarios.
Supported scenarios:
1)DB and logs are on the same LUN and in different directories.
2)DB and logs are on different LUNs and mounted on the same drive in different directories.
3)DB and logs are on the same LUN, using the same mount point, and DB and logs are in different directories.
Unsupported scenarios:
1)DB and logs are on the same path (same directory).
2)DB and logs are on the same volume where one component is using physical paths and the other is using mount points mounted on the same drive(volume).
3)DB and logs are on the same LUN using different Mount points on the same drive.Possible Workaround: Disable Consistency check.
I will be waiting your updates after disabling the IPv6 components and solve the Exchange connection issue.
Thanks,
Ahmed Bahaa
Michael891
34 Posts
0
October 25th, 2012 11:00
Hi Ahmed,
Thanks for your recomendations. One momento ago the Admin Exchange fix the problem with IPv6. I run the command nsrsnap_vss_save -v -? and show me the following:
C:\Users\dctibk01>nsrsnap_vss_save -v -?
NMM .. changing backup name MXPMBX02 to primary name mxpmbx02.pmi.pmicim.com for
multi NIC client.
List of valid saveset entries for APPLICATIONS on client mxpmbx02.pmi.pmicim.com
...
Initializing data to display...
NMM ... Using client name MXPMBX02, the version of the Exchange server is Exchan
ge 2010.
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 8 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 5 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 6 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 7 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 2 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 3 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 4 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox 1 -- Passive"
79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an
instance of an object.
"APPLICATIONS:\Microsoft Exchange 2010\Public Folder MXPMBX02 -- Active"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Now send me the error:
savegrp: suppressed 4 lines of verbose output
63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined Non Transportable.
83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation. Details in nmm.raw on MXPMBX02.pmi.pmicim.com and in the Windows Application or System Event Log.
49931:nsrsnap_vss_save:RM .. 000285 ERROR:Circular logging is enabled for Mailbox 1. You must disable circular logging before creating replicas otherwise your replicas will fail.
49931:nsrsnap_vss_save:RM .. 102206 ERROR:Validation failed.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
68151 1351186494 2 0 0 8756 7104 0 mxpmbx02.pmi.pmicim.com nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
Exchange server is Exchange 2010.
82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010\Mailbox 1 is valid.
NMM .. -A NS
I think that now I have check that the circular logging is disabled with Exchange admin
Ahmed, I have a doubt. When run the Backup Group, can I send one Member of DAG or have I send both DAG's Member at same time?
I attach the new config checker
1 Attachment
EMC Config Checke1.doc
Bebo2k
544 Posts
0
October 28th, 2012 16:00
Hi Michael,
Any updates after disabling the circular logging ? How is it going now ?
Waiting your updates.
Ahmed Bahaa
Michael891
34 Posts
0
October 29th, 2012 17:00
Thaks a lot for all your help. tha backup was success after the Exchange admin disable the Circular Logging. One moment ago run a Full backup and incremental backup, both was success.
I attached the new daemon.raw
1 Attachment
nmm_logs (3)
Bebo2k
544 Posts
0
October 29th, 2012 18:00
That is cool
, Glad that your problem has been solved.
Ahmed Bahaa