05-07-2012 09:37 PM
I've attached below the log FYI.
I wonder if symantec ever have solved the Invalid device problem? Anywayz, the backup exec always run into problem even if it do restore before. It's been 4-5 times I've failed to restore exchange individual email.
[5868] 05/08/12 12:21:46 NDMP version 3 connection CONNECTED
[5868] 05/08/12 12:21:46 NDMPAgentConnector::AuthenticateClient(): Using SSPI authentication with SLA/DLA as a fallback
[5868] 05/08/12 12:21:46 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): Attempting SSPI authentication...
[5868] 05/08/12 12:21:46 NDMP_SSPI: InitializeSecurityContext status 0x00090312 in 0 out 57
[5868] 05/08/12 12:21:46 NDMP_SSPI: InitializeSecurityContext status 0x00000000 in 204 out 72
[5868] 05/08/12 12:21:46 NDMP_SSPI: client authenticated with server
[5868] 05/08/12 12:21:46 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): SSPI authentication success.
[5868] 05/08/12 12:21:46 PDIRestoreBSDProcessor::EstablishPDIDataConnection() - data connection established successfully.
[5868] 05/08/12 12:21:46 PDIRestoreBSDProcessor::ProcessPDIDataTransfer: Starting data transfer between EXCHANGE and BACKUPHOST
[5868] 05/08/12 12:21:48 ERROR: 10 Error: Invalid device
[5868] 05/08/12 12:21:48 Enter RestoreMessageHandler::GetMachineName
[5868] 05/08/12 12:21:48 Exit GetMachineName - Machine name: [EXCHANGE]
[5868] 05/08/12 12:21:48 @@@@@@@MyCloseSocket called with sockfd = 1732(0x6c4) retval = 0
[5868] 05/08/12 12:21:48 @@@@@@@MyCloseSocket called with sockfd = -1(0xffffffff) retval = -1
[5868] 05/08/12 12:21:48 NDMPAgentConnector::EndConnection(): Data Server = BACKUPHOST
[5868] 05/08/12 12:21:48 @@@@@@@MyCloseSocket called with sockfd = 1564(0x61c) retval = 0
[5868] 05/08/12 12:21:48 @@@@@@@MyCloseSocket called with sockfd = -1(0xffffffff) retval = -1
[5868] 05/08/12 12:21:48 NDMPAgentConnector::EndConnection(): Data Server = EXCHANGE
[5868] 05/08/12 12:21:48 Merging of BE / VSR Job Logs not necessary for this Type of Job
[5868] 05/08/12 12:21:48 Job thread terminating
Any help would greatly be appreciated. Thanks.
Solved! Go to Solution.
05-09-2012 01:10 AM
What about the brand new exchange? how come it doesn't restore even I can expand the mailbox successfully? Any ideas?
05-09-2012 01:15 AM
Hi
On new exchange again you need to ensure things are in place
1 The account you are using is having all right & configured correctly as per the above technote
2 Mapi cdo 1.2.1 that is mapi client is install on new exchange server
3 Management tool on exchange server matches with level of management tool on Media server for which you can compare ese.dll version & ensure they are same
4 Backupexec is full patched up & remote agent is upto date
5 If exchange is on win2008 then 11d doesnot support win2008 so that can be also an issue ,so if that is the case then it should be using BE 12.5 or BE 2010 r3 , I would recommend in that case BE 2010 r3 sp2
Thanks
05-09-2012 01:27 AM
On new exchange again you need to ensure things are in place
1 The account you are using is having all right & configured correctly as per the above technote
2 Mapi cdo 1.2.1 that is mapi client is install on new exchange server
3 Management tool on exchange server matches with level of management tool on Media server for which you can compare ese.dll version & ensure they are same
4 Backupexec is full patched up & remote agent is upto date
5 If exchange is on win2008 then 11d doesnot support win2008 so that can be also an issue ,so if that is the case then it should be using BE 12.5 or BE 2010 r3 , I would recommend in that case BE 2010 r3 sp2
05-09-2012 01:33 AM
Old exchange:
MFCMAPI works fine with Outlook 2010 x86 using the BE service account. So my Old Exchange working fine?
05-09-2012 01:48 AM
Hi
If Mfc mapi is working then backupexec also should not have any issue expanding the mailboxes in backup seleciton , that should work fine too
If not either you can upgrade to more recent version to check which BE 2010 r3 with all updates or you can open a case with symantec to resolve this further
Thanks
05-09-2012 02:26 AM
...how can you tell someone to uninstall a service pack for Exchange after they've probably had to prep their domain for it? That's no troubleshooting step. It's not like uninstalling a SP or patch for BE!
05-09-2012 07:51 PM
Thanks all. I've successfully restore the old backup to the new exchange server by the latest trial version of BE. But the reason why it's not working on the new old server is still a mystery.
While upgrading to BE2010 r3 will obviously work, there's no gurantee that it will continuously works and won't stop working all a sudden, just like the BE 11d version.
Any ideas?
05-09-2012 08:02 PM
Hi
Good to know its working with new version & to investigate why it is not working on old system with 11d you can open a formal case with symantec were they can investigate it further by checking relevant logs as we have almost checked everyhting were in this case issue is with MAPI & with MFC mapi it is working but not with backupexec so they can have a look
Thanks
05-09-2012 08:08 PM
Many Thanks for your kindly help. Wish no one ran into the same issue. good luck~
05-09-2012 11:51 PM
...the simple fact is that once you upgrade the SP on Exchange 2007 (or move to Exchange 2010), BE 11d will no longer support it.
Grab copies of your Data/Catalogs folders, and consider an upgrade to BE 2010 R3 with the latest SP and patches. If it works on the temporary server (for which you too the initiative to do), it's a good indication that your solution will work on your production server.
You can test this by running a backup or 2 (or more!) on the test server. Once done, try restoring again to that box.