SharePointExplorer TimeOut U4

[StephanG]

Hi there,

i'm having a timeout of the SharePointExplorer with U4
I found this thread - but i did not find the config.xml
veeam-backup-replication-f2/veeam-explo ... 46051.html

I would take this path
C:\Program Files\Veeam\Backup and Replication\SharePointExplorer

Because in Programdata there is no folder at all referencing to the SharePointExplorer

Case ID is 03441536

[Polina]

Hi Stephan,

Try looking for the Config.xml at the following alternative location: C:\Users\"YOURUSER"\AppData\Local\Veeam\Backup\SharePointExplorer

[StephanG]

Also no directory there

[Polina]

Which means that no changes to the default Veeam Explorer settings have been made so far (as Config.xml is created automatically only when changes occur).

In this case, you need to create it manually, add the required configuration and save the file to C:\Program Files\Veeam\Backup and Replication\SharePointExplorer.

[StephanG]

I created config.xmls everywhere (own profile dir/programdata/programfiles) still not working. A restart of the Explorer itself should help or do i need to restart any other services on this server?

[Polina]

It should be enough to only restart the corresponding Veeam Explorer. And upon a double check, the config.xml destination folders differ according to the VBR version you're running. For 9.5, %programdata%\Veeam\Backup\SharePointExplorer is the correct choice.

[StephanG]

To be sure i restarted the server.
Same problem though

Code: Select all

[04.03.2019 19:17:17] <01> Info     Starting command: Veeam.Backup.UI.RestoreHvCommand
[04.03.2019 19:17:17] <01> Info     Started command: Veeam.Backup.UI.RestoreHvCommand
[04.03.2019 19:17:18] <01> Info     Creating help stopper...
[04.03.2019 19:17:31] <01> Info     Disposing help stopper...
[04.03.2019 19:27:35] <198> Error    Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup.
[04.03.2019 19:27:35] <198> Error    Please wait, and try again later.
[04.03.2019 19:27:35] <198> Error    Error information:
[04.03.2019 19:27:35] <198> Error    Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
[04.03.2019 19:27:35] <198> Error    The wait operation timed out (Veeam.Backup.Common.CSqlException)
[04.03.2019 19:27:35] <198> Error    Server stack trace: 
[04.03.2019 19:27:35] <198> Error       at Veeam.Backup.Common.CExceptionUtil.ThrowSqlException(Exception innerException, Boolean retyable)
[04.03.2019 19:27:35] <198> Error       at Veeam.Backup.DBManager.LocalDbAccessor.GetDataTable(String spName, CommandBehavior commandBehavior, Int32 timeoutSeconds, Boolean retryable, SqlParameter[] spParams)

We have too many site collections. I'm aware of that. But i need to be able to restore anyway.
In former versions you could start the Sharepoint Explorer from SQL Database Explorer but i cannot find this option anymore.

[Mike Resseler]

Hey Stephan,

I noticed that you are working actively with support so keep doing that. I think there might be an issue with your staging SQL server. But based on this snippet of logs, I can't be sure. The full logs will be needed which you delivered so support will dive into those.

Did they already increased the timeout?

[StephanG]

They recommended it. I increased it myself. I there any way to check if the XML is "working" ?

[Mike Resseler]

If you changed the XML file, and restarted the Veeam explorer it takes those settings.

[StephanG]

I wait for the support to tell me what else i can do. Thanks for your help

[StephanG]

[04.03.2019 19:27:35] <198> Error Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup.

this can be due to lack of resources and using earlier version SQL Server. I suggest adding RAM and CPU cores to the server, where your Veeam database is located, upgrading SQL Server version to 2016 and cleaning up the database by following steps from next KB article: https://www.veeam.com/kb1995

After that, please retry the restore and let me know the results.

--

Isn't the "configuration db" in this case the configDB from SharePoint? I use the SQL server for the veeam confdb that got installed by the default setup. I do not even know the sa password Should I? Normally i would document that if i know it.
As a staging server i use SQL 2012 SP4 Enterprise.
It times out perfectly at 10 minutes. So it is still the timeout.

[StephanG]

We are just have to many site collection so i go with the workaround. Opening "File Level Restore" and then Attach the SQL DB and Log directly to SharePoint Explorer.
Works fine and is even faster