KNOWN ISSUE: Server Space Management job error with event ID 73
|Article:TECH25401|||||Created: 2006-11-28|||||Updated: 2009-04-28|||||Article URL http://www.symantec.com/docs/TECH25401|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Server Space Management job errors, which refer to retention failure on corrupt file keys, may appear in Recovery Solution 6.2 and 6.2 SP1. Windows application event log example:
Altiris Recovery Solution Error Server Space Management 35 N/A SERVER "RemovePhysicalFile RemovePhysical() returned an error.
Altiris Recovery Solution Error Server Space Management 73 N/A SERVER "Error retentioning file 'winlogon.log' of user 'WKB01874' on volume 'C:'.
FileKey 10448642, file revision 13.
Altiris Recovery Solution Error Server Space Management 2 N/A SERVER "There was an error when a file was being processed for Recovery Solution Server space management.
Problem backing up the file.
Altiris Recovery Solution Error File Repository Engine 12 N/A SERVER "Unable to read file data from the Recovery Solution Server.
Altiris Recovery Solution Error Client Files I/O Engine 72 N/A SERVER "Unable to read data from reference file during restore.
Altiris Recovery Solution Error Client Files I/O Engine 69 N/A SERVER "Missing revision information during file and folder restore.
Recovery Solution 6.2.2106
Recovery Solution 6.2.2332 (SP1)
Incomplete file transferred to the Recovery Server due to network loss during snapshots. Recovery Server errors out clearing out such incomplete files during SSM job. ***NOTE: We have also observed this exact same error sequence when DNS resolution or network routes that define the network path to the Recovery Server are incorrect.
This problem has been found in Recovery Solution 6.2.2106 and cause is fixed by Hotfix 13. More information on this fix can be found in article 28891. This fix is also included in Recovery Solution 6.2 SP1. If you see those errors during SSM and still on 6.2.2106, it is strongly recommended to upgrade to SP1.
***NOTE: Prior to the upgrade, please make sure that DNS entries and network paths resolve correctly for the Recovery Server.
SP1 addresses the original problem; however, you may still see these errors during SSM. Filekeys are processed by SSM and removed from database according to retention rules. And it will take some time for all of these filekeys to disappear.
You may ignore these errors if you are on Recovery Solution 6.2 SP1 unless it causes Full System Recovery or a Rollback to fail. In case of restore failures contact Altiris Support Services for assistance.
|Description||Logged in tlndev (Altiris - Talinn) database|
Article URL http://www.symantec.com/docs/TECH25401