Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all articles
Browse latest Browse all 10494

Re: v8.12 dbsm.exe hangs with 100% CPU, restore of Virtual Envrionment backup of VMWare 5.5 fails

$
0
0

I checked lab cases, and the Knowledgebase, and found almost nothing on the error

 

[62:1021] Bar restore session was started but no client connected
in 600 seconds

 

although I found lots on Backup

 

I guess that you can try increasing the 'global' variable

 

# SmWaitForFirstRestoreClient=WaitForInMinutes

# default: 10 minutes
# This timeout is used by the Restore Session Manager. After the
# restore script on the BAR system starts, the RSM will wait for
# specified timeout for the first  client  connection.  If there
# are no connections in the specified timeout, RSM will go down.

 

On the cell manager, edit the file

 

  Program Data -> Omniback -> Config -> Server -> Options -> global

 

Look for this line:

 

# SmWaitForFirstRestoreClient=WaitForInMinutes

 

Make a copy of this line, edit one of the lines to remove teh # sign and the 'space' that follows, and set it to 20 minutes, double the default value

 

SmWaitForFirstRestoreClient=20

# SmWaitForFirstRestoreClient=WaitForInMinutes

 

Save the file, stop and restart Data Protector, try another restore.  There is least an even chance that you will get a 1200 second timeout. If you do, re-edit the 'global' file to remove the line you added


Viewing all articles
Browse latest Browse all 10494

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>