Forum Discussion

oolmedo's avatar
oolmedo
Level 4
6 years ago

Exchange 2016 grt restore fails with 2810 status error

Hello,

Grt exchange restores failed wit status 2810 after migration of NBU from 7.7.3 to NBU 8.1.1 (master server is AIX) , NBU client is 8.1.1 (also migrated from 7.7.3) installed on Exchange Server 2017 Windows Server 2016.

The first error in restore job is:

03/12/2019 09:41:47 AM - Error bpbrm (pid=5736) from client SVWMAIL4: ERR - unable to create object for restore: \\DAG\Microsoft Information Store\DB22\Database, rai error = 6

Backups and restores (not GRT) continue working properly.

From logs:

1) ncfgre.log:

0,51216,158,352,5669,1575376918260,23244,11776,0:,186:FS_GetCurrentDDB() Failure! (0xE0000388:Cannot log on to EWS with the specified credentials. Review the resource credentials for the job, and then run the job again.)

2) monad:

09:41:47 Exchange2010Component::GetCasDetailsForServerFromWebService - Error: Unable to cast object of type 'Microsoft.Exchange.Data.Directory.ADObjectId' to type 'System.Management.Automation.PSObject'.

3)EWSLog:

2e00] 12/03/19 09:40:49 *************************************************************************
[2e00] 12/03/19 09:40:49 * Veritas Backup Exec EWS Provider Debug Log *
[2e00] 12/03/19 09:40:49 * Date-Time: Tue Dec 03 09:40:49 2019 *
[2e00] 12/03/19 09:40:49 *************************************************************************
[2e00] 12/03/19 09:40:49 ---EWSRemoteExchangeConnection::CreateMAPIProvider---
[2e00] 12/03/19 09:40:49 --- EWSProvider::GetSession ---
[2e00] 12/03/19 09:40:49 --- EWSExchangeSession::Logon ---
[2e00] 12/03/19 09:40:49 ExchangeServer version is Exchange2010_SP1
[2e00] 12/03/19 09:40:50 LoginName Passed ntute\veritasexchange
[2e00] 12/03/19 09:40:50 User Passed veritasexchange
[2e00] 12/03/19 09:40:50 Service Response Timeout ::300000 milliseconds
[2e00] 12/03/19 09:40:50 Server :: SVWMAIL4 mailbox :: veritasexchange username :: veritasexchange domain :: ntute
[2e00] 12/03/19 09:40:50 Inside GetMailBox
[2e00] 12/03/19 09:40:50 Adding mailbox Exchange, Veritas
[2e00] 12/03/19 09:40:50 Adding mailbox
[2e00] 12/03/19 09:40:50 Returnning mailboxex 2
[2e00] 12/03/19 09:40:50 Mailbox is Exchange, Veritas
[2e00] 12/03/19 09:40:50 Continue on using NetworkCredential
[2e00] 12/03/19 09:41:46 AutoDiscover Failed in locating the url The Autodiscover service couldn't be located.
[2e00] 12/03/19 09:41:46 Retrying using CAS server urls from Monad ......
[2e00] 12/03/19 09:41:46 RowSetHelper::Calling Monads GetWebServicesUrls
[2e00] 12/03/19 09:41:47 RowSetHelper::Returned with retval 0iCount 0
[2e00] 12/03/19 09:41:47 RowSetHelper::Returned with retval 0Count 0
[2e00] 12/03/19 09:41:47 Count is 0
[2e00] 12/03/19 09:41:47 GetWebserivcesurl did not return any urls
[2e00] 12/03/19 09:42:05 --- EWSExchangeSession::LogOff ---

Weird that debug log is showing different Exchange Server version (2010 insted of 2016). Also EWS seems not be working properly or connection issues

We asked to Exchange Admins to run the connectivity test:

test-webservicesconnectivity -MailboxCredential $(get-credential) -TrustAnySSLCertificate  | FL

Here is the output:

Scenario            : AutoDiscoverSoapProvider

ScenarioDescription : Autodiscover: SOAP Provider

Result              : Failure

Latency             : 8002

Error               : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a

                      send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing

                      connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An

                      existing connection was forcibly closed by the remote host

                         at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

                         --- End of inner exception stack trace ---

Although this output error, no Exchange issues at any server in DAG and all seems to be working properly with the exception of this GRT restores.

Any advice or clue will be very appreciated.

Thanks.

oolmedo

8
EWS connectivity
Exchange GRT restore
Windows Server 2016
  • Lowell_Palecek's avatar
    Lowell_Palecek
    Level 6
    6 years ago

    The version you see in the EWS log is the interface version of the EWS API that NetBackup requested from the API. The API's maintain backwards compatibility, so it does not need to say Exchange 2016. I'm a bit surprised it doesn't say 2013.

    Whatever causes this error is the root cause:

    Failure! (0xE0000388:Cannot log on to EWS with the specified credentials. Review the resource credentials for the job, and then run the job again.)

    Did you make any Exchange changes along the way? I have a current customer case with similar symptoms, where they created a multi-level domain. They get the same error you get when they use a server in the subdomain as the destination client. Since you are on NetBackup 8.1.1, we have an EEB for that. I think this would have worked without EEB in 7.7.3. It has to do with the ViewEntireForest option in a PowerShell session.

    Talk to Veritas support. They can help you sort out the clues in the logs.

    • osvaldo_olmedo's avatar
      osvaldo_olmedo
      Level 4
      6 years ago

      Thanks Lowell for your reply. Your comment is very usefull, I will talk to Exchange admin about the multi-domain question. 

      In the meantime, we will ask to support team regarding this issue. The customer has opened a case with support, but they are analyzing logs and problem data. We will ask to the support team regarding your comment.

       

      Thanks again for your help

       

      Oolmedo