The Backup Destination in a Continuous Protection Server (CPS) setup displays files with very old creation dates, even when the CPS backup jobs are completing with no errors in the Synchronization phase.

Article:TECH63461  |  Created: 2010-01-02  |  Updated: 2011-08-01  |  Article URL http://www.symantec.com/docs/TECH63461
Article Type
Technical Solution


Environment

Issue



The Backup Destination in a Continuous Protection Server (CPS) setup displays files with very old creation dates, even when the CPS backup jobs are completing with no errors in the Synchronization phase.


Solution



What is Affected:
 
The issue outlined in this article is known to occur in following versions of CPS:
 
  • Backup Exec Continuous Protection Server 11d
  • Backup Exec Continuous Protection Server 12.0
  • Backup Exec Continuous Protection Server 12.5

 
How to Determine Your Product Version:
 
The installed version of CPS can be verified by selecting the "About CPS" option from the Help menu in the CPS console.
 

 
Details of the Issue
 
The Backup Destination in a Continuous Protection Server (CPS) setup displays files with very old creation dates even when the CPS backup jobs are completing with no errors in the Synchronization phase.  A CPS backup job when executed, runs in two phases:
 

1. Synchronization phase

This is the first phase of replication. It ensures that the backup destination on the Continuous Protection Server contains an identical copy of all the files, which are marked for backup on the source server. The first time a backup job starts, all the qualifying files on the Business Server are copied to the backup destination on the Continuous Protection Server, and the attributes of the files on the Continuous Protection Server are matched to the attributes of the corresponding files on the Business Server.

2. Dynamic phase (The Dynamic phase occurs only when the CPS backup jobs are set to run continuously within a time frame or whenever a file changes.)

If a backup job is configured to use continuous replication, CPS implements a second phase called the dynamic replication phase. In this phase, all the changes made to files, which are marked for backup on the Business source server are stored in journal files and are applied to the files on the Continuous Protection Server after the files are Synchronized. Dynamic replication (DR) maintains Write Order Fidelity (WOF) on the Continuous Protection server.

 
If the CPS backup job is paused or canceled during the Synchronization phase, CPS modifies the creation date of the file being replicated at that point to a very old date so that when the CPS job resumes, the partially-replicated file (marked by the very old creation date) will be re-replicated. Following a successful Synchronization, the backup destination should have no such files marked with very old creation dates.
 
Note:  If the CPS job is configured to run continuously within a certain timeframe then it is recommended that in the properties of the backup job, the option to "STOP"  the job when schedule ends rather than "CANCEL" is selected. (Figure 1)
 
Figure 1:
 
 
 
The STOP option allow the CPS backup job to complete the "Synchronization" phase and then finishes the job.
 
The CANCEL option will stop the CPS job immediately irrespective of whether the CPS backup job is running in "Synchronization" phase or "Dynamic" phase. If the job gets canceled in the "Synchronization" phase it may lead to the problem mentioned above.
 

 
In certain cases though, it has been observed that CPS does not correct the files it marked as "partially replicated" even when the CPS backup jobs complete with no errors in the Synchronization phase. If at this stage a backup of the CPS Protected Resources is run using Backup Exec for Windows Servers, the backup job reports such files as corrupt.
 
e0000332 - File(s) are currently being backed up to the CPS Protection Server and cannot be backed up by Backup Exec.
 

Please refer the TechNote 288608, found below in the Related Documents section, for more information about this error in Backup Exec.

 
Formal Resolution:
 
The above mentioned issue has been fixed by a way of a hot-fix in CPS 11D build 40740, CPS 12.0 and CPS 12.5. Please refer to the following links, respective to your environment, for the hot-fix downloads:
 
Workaround Information:
 
At this time, no known workaround is available for this issue.
 

Best Practices:
Symantec strongly recommends the following Best Practices:
1. Always perform a full backup prior to and after any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.


How to Subscribe to Software Alerts:
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alerts, please subscribe at the following link:  
 http://maillist.entsupport.symantec.com/subscribe.asp
 

Supplemental Materials

SourceETrack
Value1412184
Description

CPS:Bkup Destination shows files with funky creation dates even when jobs are completing with no errors in the Sync phase.


SourceError Code
Value0xe0000332
Description

File(s) are currently being backed up to the CPS Protection Server and cannot be backed up by Backup Exec.


SourceUMI
ValueV-79-57344-819
Description

File(s) are currently being backed up to the CPS Protection Server and cannot be backed up by Backup Exec



Legacy ID



308761


Article URL http://www.symantec.com/docs/TECH63461


Terms of use for this information are found in Legal Notices