The tables below list the new features and the bugs fixed for Symantec LiveState™ Recovery Manager 6.0.2.

New Features

 

New Feature	Description
Alternate Method of Installing LiveState Recovery and Management Control Provided	Due to customer requests, an alternate method for installing LiveState Recovery and Management Control on each client machine has been provided. Please see Appendix A of the Implementation Guide for more details. This method allows the network administrator to implement the rollout of LiveState Recovery and Management Control via deployment tools and/or scripts they may already have in place.

Features/Functionality modified

 

Feature

Description of modification

New Outbound Communication Path

Functionality was implemented to allow communication from the LiveState Recovery Manager 6.0.2 server directly to the Management Control on each managed computer. This new functionality makes use of port 763 to wake up the Management Control to check for new jobs and schedules. (See Appendix B of the Implementation Guide for more details on port usage.) Due to the changes in the way the LiveState Recovery Manager 6.0.2 server and the Management Control communicate, Management Control must be updated on all managed computers. Also, it is no longer necessary for LiveState Recovery Manager to keep the LiveState Delivery Agent on a managed computer after LiveState Recovery and Management Control have been deployed to a computer.

Features/Functionality removed
No features or functionality have been removed.

Bugs fixed in this release

Agent 7.0 Issues

 

Description	Action Taken
Discover LiveState Recovery package hangs.	Fixed
If using Remote Desktop to a computer that you then try to manage, the LiveState Delivery Agent freezes.	Fixed
"Error 4001: Cannot connect to client PC with client ID to configuration server."	Fixed

Documentation Issues
 

Description	Action Taken
Documentation erroneously states that four areas are required to change ports.	Fixed

Localization Issues
 

Description	Action Taken
In Japanese, pushing LiveState Recovery dialog is not translated.	Fixed
Incorrect password message displays in English on a German system.	Fixed

LSRM Server Issues

 

Description	Action Taken
Implement optimized defaults for the underlying database into SP2.	Fixed
Dropping multiple jobs on large groups of computers can cause multiple errors.	Fixed
"Get Next Run time is earlier..." error sometimes shows up when managing computers in different time zones.	Fixed
Run Job Now fails to remove Not Reporting after successful completion.	Fixed
Successful consolidation of incremental backups is not reported if server and client are in different time zones.	Fixed
Next Run Time shown for a Job does not show runtime for next computer in stagger.	Fixed
Managing a computer with existing LiveState Recovery sometimes hangs in the state "Waiting for client info".	Fixed

Management Control Issues
 

Description	Action Taken
LiveState Recovery/Management Control installation sometimes reports back 'Unlicensed' after the installation.	Fixed
Not reporting status is sometimes shown for computers in other time zones.	Fixed
Managing a computer with existing LiveState Recovery does not show job history prior to becoming managed.	Fixed
Client computer can get stuck in a 'Updating Client' status when adding a job.	Fixed
Have Management Control specify the time of the last attempt to publish.	Fixed

UI –Console
 

Description	Action Taken
Job progress status is not refreshed in all locations when running a job.	Fixed
Job assigned status for client is not updating in lower pane.	Fixed
Error message "Could not retrieve LiveState Recovery agent event log data" pops up when first logging into LSRM console.	Fixed
Warning message for changing client port resets server ports to default.	Fixed
Unable to cancel or retry LSR discovery if LSR discovery is in progress.	Fixed
Can't sort Events by Date/Time.	Fixed
Need Cancel/Retry buttons on Status panel for LiveState Recovery and Management Control installations.	Fixed

This section discusses information that should be submitted to Symantec when reporting problems with Symantec LiveState™ Recovery Manager 6.0.2.

Before doing a Trouble Report

How to enable debugging for the LiveState Recovery Manager server, console, and management control (Publisher).
Setting the debug mode for:

LiveState Recovery Manager server
1. On the LiveState Recovery Manager server, stop all LiveState Recovery Manager services by opening a command prompt to the \dbin directory where the LiveState Recovery Manager server is installed and type recovery stop.
2. In Windows Explorer, open log4j.properties in Notepad.  The file is located in C:\Symantec\LiveState\config\services\tomcat\webapps\asix\WEB-INF\classes.
3. Search and replace the uppercase word WARN with the uppercase word INFO.
4. Open a command prompt to the \dbin directory where the LiveState Recovery Manager server is installed and type recovery start. You will have all logging information reporting to the Axis.log file found in C:\Symantec\LiveState\config\log.

LiveState Recovery Manager console
1. Open log4j.properties in Notepad. The file is located in C:\Program Files\Symantec\LiveState Recovery\Manager 6.0\lib.
2. Search and replace the uppercase word WARN with the uppercase word INFO.
3. All logging will go to the Manager Console.log file at the root of the LiveState Recovery Manager 6.0 directory.

Management Control (Publisher)
1. On the client computer open Windows Services and stop the Symantec LiveState Recovery service.
2. Launch regedit and browse to HKeyLocalMachine\Software\Symantec\LiveState Recovery Manager\6.0\Publisher
3. Right-click the key LogMessageType and select Modify.
4. Change the value to All.
5. Close regedit and restart the LiveState Recovery service from Windows Services.
6. All logging can be found in C:\Program Files\Symantec\LiveState Recovery 6.0\Console\_PubLog.xml file.

Setting the Autoadd feature of the Windows Agent.
1. On the client computer open Windows Services and stop the Symantec LiveState Agent for Windows service.
2. Launch regedit and browse to HKeyLocalMachine\Software\csd\Control\2.0\Server.
3. Right-click the key Autoadd and select Modify.
4. Change the number value from 0 to 1.
5. Close regedit and restart the LiveState Agent for Windows service.
6. The Windows Agent will try to again add the client information to the database.

Adding a managed computer
When you add a computer, the LiveState Recovery Manager server is connecting to the C$ share of the client and trying to copy the Windows Agent installation files to run them from the client computer. If a computer cannot be added, check to be sure the credentials being supplied are valid by browsing to the C$ share of the client through Network Neighborhood and attempting to connect using the same credentials provided when using the LiveState Recovery Manager console.