cancel
Showing results for 
Search instead for 
Did you mean: 

LiveState Recovery Advanced Server 6.0 Hangs

Jay_Gray
Level 2
I am using Symantec LiveState Recovery Advanced Server 6.0 with the LiveState Recovery Manager 6.0. I've configured 8 servers to create base recovery points each Sunday at 10:00 PM with incrementals Mon-Sat. Every Monday when I check the status of the jobs, at least 2-4 of the servers show up as not reporting. I check the event log for any errors, but only find:

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002.v2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002_i012.iv2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002_i024.iv2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002_i036.iv2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002_i048.iv2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F043D: Recovery point F:\SERVERNAME_C_Drive002_i060.iv2i deleted to comply with the number of recovery points to save for each drive.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:21 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F042F: Consolidation of incremental recovery points completed successfully.
Details:
Source: LiveState Recovery

Event Type:Information
Event Source:LiveState Recovery
Event Category:High Priority
Event ID:100
Date:4/23/2006
Time:10:09:03 PM
User:N/A
Computer:SERVERNAME
Description:
Description: Info 6C8F0435: A scheduled base recovery point of C:\ completed successfully.
Details:
Source: LiveState Recovery

There are no other LiveState Recovery events past that point.

In order to get things working properly on each server, I have to kill the Symantec LiveState Recovery process, VProSvc.exe, through the task manager (it times out trying to shut down the service), then start the service again. It will continue to run without problem until the next Sunday/Monday when I have to do the same thing again. Does anyone have any idea what might be causing this kind of problem? Anything I can check? Thanks in advance.
9 REPLIES 9

Mr__Fabietto
Level 4
Employee
Hi Jay,

Maybe the problem you are experiencing is related to the number of recovery points you have configured in your job. Check inside the job details how many recovery points to keep and modify it to a number that could be stored in your HDD. Eg. I will start trying by selecting to keep just 1 recovery point and see what happens.

Mr. Fabietto
https://spaces.msn.com/fcerullo

Jay_Gray
Level 2
Thank you for your reply. I'll try that and post the results.

Mr__Fabietto
Level 4
Employee
Hi Jay

Any luck with the tests?

Thanks

Mr. Fabietto
http://spaces.msn.com/fcerullo

Jay_Gray
Level 2
Sorry, I had problems configuring the Jobs using LiveState Recovery Manager (it kept locking up on me), and I haven't had a chance to look into it again. I'll make some time to work on this, then let you know what I find out.

Mr__Fabietto
Level 4
Employee
Hi Jay

Any luck with the tests?

Thanks

Mr. Fabietto
http://spaces.msn.com/fcerullo

Jay_Gray
Level 2
I set the option to limit the number of recovery points saved for each volume to 1, but I'm still having the same problem. I did a search for the most recently modified files in the \Program Files\Symantec\LiveState Recovery\Advanced Server 6.0 directory. The following files were the most recently modified (6/11/2006 10:04 PM). Could the answer be in any of these files?

...\Agent\Symantec LiveState Recovery.dbg
...\Agent\Schedule\{A69AAC95-C1CD-11DA-8762-00D0B7B66CD2}.pqj
...\Agent\History\M1250445960Offset63_Volume.pqh
...\Agent\LiveState Recovery.log.txt
...\Manager\PublishQ.xml

I didn't notice any problems in the log. The last information recorded indicates that the scheduled base recovery point completed successfully, then it deleted recovery points to comply with the number of recovery points to save for each drive.

{A69AAC95-C1CD-11DA-8762-00D0B7B66CD2}.pqj seems to be an XML file containing the settings for the job, so I've included it below so you can see how the job is configured.

-

0
1
100
9
0
0
{A69AAC95-C1CD-11DA-8762-00D0B7B66CD2}
-1
-1
Recovery point of C:\ to F:\
-1
1
-1
0
0
12
0
0
12
06/12/2006 04:00:00
-1

0
0
0
0
06/12/2006 04:00:00
-
Base Schedule
{6C7D35E3-772B-4B9B-9E7B-4582A6F5353D}
-1
04/02/2006 05:00:00
12/30/1899 00:00:00
06/12/2006 04:04:38
3
1
-420
0
-60
06/08/2006 23:04:12
12/30/1899 00:00:00

-
Incremental Schedule
{1FDC90DF-E388-431C-B068-CC2B18D8B622}
-1
04/01/2006 14:00:10
12/30/1899 00:00:00
06/11/2006 00:00:32
3
4294967422
-420
0
-60
06/08/2006 23:04:12
04/02/2006 01:00:10


M1250445960Offset63_Volume
-
folder
&Local File
-1
0
-1
f:\
SERVERNAME_C_Drive
.v2i

-
install.exe
setup.exe
msiexec.exe
update.exe

Markus_Koestler
Moderator
Moderator
   VIP   
Same Probleme with me on Windows 2000 Server. We've opend a case at Symantec but they weren't able to solve to problem until now.


What came up during my investigations is, that this hangs have a relation to the availability of the backup medium: If the backup medium becomes unavailable during the backup, the service hangs. But not always, sometimes the services "survies" and writes an error message to the logs.

Installation Version 6.0.2 eases the pain a little but the hangs still occur.

techno_nerd
Level 4
These issues should be resolved in the latest version of BESR 6.5. I have had much better luck since upgrading.

Thanks,

Technonerd

Markus_Koestler
Moderator
Moderator
   VIP   
I was given accress to Version 6.5.4. In this version, according to Symantec Support, the freeze problem should be eliminated.