Symantec LiveState Recovery Manager 6.0.x Release Notes
| Article:TECH55059 | | | Created: 2007-01-29 | | | Updated: 2008-01-29 | | | Article URL http://www.symantec.com/docs/TECH55059 |
Problem
Symantec LiveState Recovery Manager 6.0.x Release Notes
Solution
This document describes the changes made in Symantec LiveState Recovery Manager 6.0.x.
Symantec LiveState Recovery Manager 6.0.1
The following problems have been fixed in Symantec LiveState Recovery Manager 6.0.1:
Agent 7.0 Issues
Dual NIC computers do not wake up when the server sends something out
Delivery agent hangs in middle of getting package
Fixed.
Older version of the Windows Agent overwrites the newer version when LSRM installed over LSD
Fixed.
Documentation Issues
- Documentation gives incorrect port numbers for using LSRM through a firewall
Errors have been corrected and all information relating to configuring and working with firewalls has been consolidated into Appendix B.
Provide information on backing up non-VSS-aware Active Directory. This can be found in the Administering Jobs section, "Backing up Non-VSS-aware databases."
Clarify in documentation how to install the Windows Agent and then the LiveState Recovery Agent
Clarified in chapter 3 - Quick Start.
Workaround for "Selected drive is not NTFS"
Added to Appendix A.
"Best practices" and troubleshooting for LSRM server with multiple NICs
See the Troubleshooting section, "Deploying agents using a specific IP address... "
.NET Framework 2.0 is installed, but LSR is prompting for .NET Framework 1.1
Information added to the Readme.txt.
The solution is to use LSR 6.0.1 instead of LSR 6.0.0.
How to enable quiet mode in the Windows Agent install
Added to the Troubleshooting section under the heading, "Hiding the LiveState Agent for Windows system tray icon".
Computers with no keyboard or mouse attached. e.g. Blade Centers, have problems connecting
Added to the Troubleshooting section, under the heading "Connecting to the LiveState Recovery Manager server from a computer that does not have an attached keyboard or mouse".
LSR Issues
- Upgrading from LSR Standard Server Agent to LSR Advanced Server Agent fails during install of Management Control
Error "Could not add job to specified computer. Cannot convert time zone"
Fixed. This issue was due to not correctly handling the English (New Zealand) Regional settings.
LSR version numbers do not agree
Fixed. When creating packages of LSR 6.0.1, the version number for the package would show up as 6.1.
LSRM Server Issues
- Changing password for recovery point location fails to change client jobs
Changes to backup jobs intermittently fail to update LSR on client
Fixed.
Dropping jobs on a group sometimes doesn't drop anything on clients with LSR Standard Server. If you have a computer with LSR Standard Server in a group with other computers with different versions of LSR that can do incremental backups and then you select and drop several jobs on the group where one of the jobs is an incremental job, the machine with LSR Standard Server was not receiving any jobs.
Jobs are not getting re-pushed when editing the backup location
If you have a job that creates recovery points for all drives on a computer, then you edit that job, the changes were not being re-pushed to the computers that had that job. Note: Windows caches this information, so the client machine would need to be rebooted, or the share name renamed to force a reconnect in Windows.
XML Parsing error ("Could not retrieve the discovery status: Unhandled exception") discovering computers in a domain.
Cannot login if Server.xml is changed so that server listens on port 443
When LSR publishes information back to the server, sometimes the server would be unable to accept another connection and would error out with "Error E339197C: An error occurred while publishing"
Password change in job fails to change password and job fails to complete
Password changes to a job were not always getting pushed to a machine containing the job.
Management Control Issues
Client machine stopped reporting after successfully running more than a week
Error E39197C occurred while publishing. The underlying connection was closed A
few changes have been made in the Management Control piece to make it more robust and better able to handle the situation of the server being momentarily busy servicing another machine.
Create Recovery Point after Run Job crashes Management Control
Fixed.
Computers erroneously flagged as "Not Reporting" Time between server and client is not synched correctly
Assigning a monthly schedule displays "E339197C An error occurred while publishing"
Fixed. The issue was due to the time on the client machines getting ahead of the server.
Not Reporting status takes precedence over a Recovery point failed status
Fixed. This was masking the true problem that the Recovery Point failed.
Can't change out job location when you run out of space on destination
Fixed.
In some situations, the Management Control uninstallation fails on client machine because it is not able to stop a dependent service
Fixed.
UI -Console
- Sorting on IP sorts as if it is a string instead of a number
The Console sometimes displays the job status tab info incorrectly when the job is being displayed in the context of a machine
Fixed.
Users cannot drag and drop a job to a group of computers
Usability issue. To make it more apparent that you can drag a drop jobs onto a group, the Jobs and Computer Groups nodes in the tree view are now open by default.
After doing a Discover Computers, the console window would drop behind other windows, if they were up
Fixed.
Add Computer Information window may freeze when trying to access it after two or three minutes
Fixed.
Management Control install errors should display on console
Fixed.
A new status of Management Control Installation failed has been added. It will show in the console for a particular machine, if an installation of Management Control fails.
Console does not refresh after LOR is installed on a group. In some instances the Install LOR wizard would not close when finished
Fixed.
History is not found after logoff and login to the console
Fixed.
This issue was due to the way the Display Complete History check box was being interpreted.
"Unable to retrieve volume of specified computer" error displays on removing computer
In this situation, which two consoles attached to the server, one would report correctly the removal of a computer the other would show this error.
Fixed.
In some situations, the Console would stop responding if the Time Out dialog was left open
If you sort Status Type on the Status tab for a computer, the rest of the information displayed would occasionally not be synchronized
Fixed.
Scheduling a Monthly Base with Incremental job reports an incorrect next run time with the current date instead of the scheduled time
Fixed.
In some situations, the Console will display an error if you try to assign the job to the computer group by right-clicking
Fixed.
Computers are not getting displayed under "Managed Computers" Node
Fixed. Sometimes when adding a group of computers, an occasional computer would not show up as managed until after the LSRM server had been restarted.
Not able to uninstall LSR when the uninstall of Management Control is in a failed state
Fixed.
Discovered Computers are not remembered after a time-out
Fixed.
The corrected behavior is as follows: When a user logs out explicitly, the unmanaged node will be explicitly cleared. When session time-out happens and the user logs back into the same server, unmanaged computers will be retained. When session time-out happens and user logs back into a different server, the unmanaged computers list will be cleared out.
|
|
Legacy ID
293470
Article URL http://www.symantec.com/docs/TECH55059
Terms of use for this information are found in Legal Notices
Thank you.