Backup using "Differential/Incremental - using modified time" option backs up all the data rather than just the changed data when no remote agent is present.

Article:TECH68920  |  Created: 2009-01-27  |  Updated: 2012-08-27  |  Article URL http://www.symantec.com/docs/TECH68920
Article Type
Technical Solution

Product(s)

Issue



Backup using "Differential/Incremental - using modified time" option backs up all the data rather than just the changed data when no remote agent is present.


Error



If  Full - Back Up Files - Using modified time, Differential - Using modified time, or Incremental - Using modified time is selected, Backup Exec uses a file's modified time rather than the archive bit to determine if it needs to be backed up.


 


When Backup Exec runs a full or incremental backup, the time the backup launches is recorded in the Backup Exec database. The next time an incremental or differential backup launches, Backup Exec compares the file system time to the backup time recorded in the Backup Exec database. If the file system time is later than the database time, the file is backed up. When an incremental backup is run, a new time is recorded in the Backup Exec database. The database time is not updated with differential backups

NOTE: The Full - Using modified time backup method adds the time of the backup to the Backup Exec database only if the full backup job completes successfully. If the full backup job does not complete successfully, any subsequent backup jobs that use the differential or incremental modified time backup methods back up all of the data instead of just the data that changed since the last full backup


When backing up or protecting remote servers where NO Backup Exec Remote Agent (RAWS) or Remote agent for Linux Server (RALUS) is present the Incremental or differential jobs using modified time may backup more data than expected or run as a FULL.

During the Full - Back Up Files - Using modified time the Backup job may complete with and exception when viewed in the job monitor (FIGURE 1).


(FIGURE 1)
 


Viewing the Backup job log its completing with an Exception and Error indicated in RED (FIGURE 2)

ERROR:

V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine . The media server will use the local agent to try to complete the operation.

WARNING: Media servers cannot completely protect remote Windows-based servers or workstations unless the Backup Exec Remote Agent is installed and running on each remote Windows-based server or workstation to be protected. Data loss can occur if the Remote Agent is not running while backing up remote Windows-based computers. Please refer to the documentation or online help for more information.

Unable to initialize Remote Agent 

Incremental or Differential jobs using modified time ran after the FULL backup using Modified time may backup more data than expected (FIGURE 2)

(FIGURE 2)


Cause



The error during the Full - Back Up Files - Using modified time is due to no remote agent detected or present on the remote server during the Backup.  
 


Solution



All backup methods (Full, Differential, Incremental using Modified Time, etc.) are supported only if the Agent for Windows Systems (AWS) or Remote Agent for Linux/Unix Systems (RALUS) is installed.  For systems unable to have either agent installed, only the backup method FULL is supported.

 Systems without an agent are unable to gather the information necessary to support any other backup method.





 


Supplemental Materials

SourceETrack
Value1544802
Description

Backup using "Differential/Incremental - using modified time" option backs up all the data when RAWS/RALUS not used


SourceUMI
ValueV-79-57344-3844
Description

The media server was unable to connect to the Remote Agent on machine. The media server will use the local agent to try to complete the operation



Legacy ID



321289


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


Terms of use for this information are found in Legal Notices