Video Screencast Help

Configuring SPSWrapper Timeout via registry.

Created: 04 Jun 2013 • Updated: 04 Jun 2013 • 3 comments
Gaurav Kaushal's picture
+3 3 Votes
Login to vote

Hi,

Recently I have seen a spate of escalations where the Microsoft SharePoint Resources node is not visible in Backup Archive and Restore (BAR) GUI and as a result SharePoint backup fails with Status 2.

Initially I suspected some configuration steps were missing but SharePoint_check.exe came clean and so does our spprobe.exe but the issue still remains.

After investigating the logs from various customers, it was discovered that the process SPSWrapperX.exe, which is responsible for discovering SharePoint topology, is timing out before we could discover the topology and hence we are not seeing the Microsoft SharePoint Resources Node in BAR GUI.

To overcome this problem we can configure a Timeout option in registry for discovering topology.

Create a new Key called “Timeout“ under

HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\SharePoint\

Then create a REG_DWORD value “gettopology”  under Timeout and assign it a decimal value to the number of Seconds for timeout.

 

Timeout.png

After we set this, the SpswrapperX.exe process would use this timeout for discovering topology from next time.

NOTE - This modification needs to be done on SharePoint Servers and not on SQL backend. This is because we specify the SharePoint server name in the backup client in the NetBackup policy and that server is responsible for discovering the SharePoint topology.

Regards,
Gaurav Kaushal

 

Comments 3 CommentsJump to latest comment

srk's picture

Thanks, Gaurav, great info.

For reference sake, can you share with us the value for the default timeout (without the registry entry) and what settings, in your experience, have been sufficient?  Understanding, of course, that this will vary somewhat from one environment to the next.

Thanks,

Steve

+1
Login to vote
Gaurav Kaushal's picture

Hi Steve,

The default value of timout is 30 Seconds and if we do not specify the timeout in registry the default value of 30 seconds is used.

On customer setups facing this issue i have always tried with 512 (decimal) or 200 (Hex) value for the timeout and the discovery have been succesfull with in this time.

Regards,
Gaurav Kaushal

Thanks and Regards.
~gk

+1
Login to vote
Gaurav Kaushal's picture

One point to keep in mind that you need to apply the fixes that takes this registy value into account.

Only creating registry entry will not serve the purpose.

 

 

Thanks and Regards.
~gk

0
Login to vote