An auto started backkup began at 1:00Am. The log shows a 5.5 hr delay before the actuall backingup of the files began. I've enclosed a snipit of the log.
Any idea why this happens?
Time Type Message
1:02:03 AM SSTART Backup Session Auto Run: Started on Thursday, April 21, 2005 at 1:02:03 AM Version: 2.0 (238)
1:02:03 AM INF Run Time Parameters: UNYYYYYN
1:02:04 AM INF Creating Session: 3
1:02:15 AM DEST Backup destination: [XD]:\MTXSV001 D Drive\MTXSV001 D Drive.zip
1:02:15 AM INF Backing up NTFS Security Settings.
1:02:15 AM INF Test Method: File Integrity Method.
6:45:03 AM INF Backing up: 257 Files of 1,666.00 Megabytes
6:45:03 AM INF Ignoring: 114 Files
6:45:03 AM INF Already on Backup: 16,506 Files
6:45:03 AM INF Compression Level: High
6
Long delay during backup.
Long delay during backup.
Mike
Appropriate Systems, LLC
Appropriate Systems, LLC
Long run time
Will you send us the files for this backup job via the Help / Bug Report option please. The statistics from the log may be useful as this shows the time taken by each phase of the backup.
AISBackup is calculating which files need to be backed up in the 5 hour wait. We can understand an infinite calculation when backing up Linux drives that contain symbolic links back to parent folders, the work around here is to use the directive follow symlinks = no in the Samba configuration file.
Running the job via the interactive interface may help identify the problem.
Barry
AISBackup is calculating which files need to be backed up in the 5 hour wait. We can understand an infinite calculation when backing up Linux drives that contain symbolic links back to parent folders, the work around here is to use the directive follow symlinks = no in the Samba configuration file.
Running the job via the interactive interface may help identify the problem.
Barry