Hi Andy
Thanks for sending in the jib files for this one, however, you sent the summary files and I would prefer the job files (the other check box on the bug report form).
The summary log file indicates that you were still using build 2.3.1 (298) when session 1 was restarted, but does not indicate why.
Code: Select all
START AISBackup started: 22 April 2007 21:17:36
INF Priority Changed to: Below Normal
SSTART newfull Backup Session: 1 Started on 22 April 2007 at 21:17:53 Version: 2.3.1 (298)
SESSEND newfull AISBackup Session Finished: 22 April 2007 21:22:08
START AISBackup started: 22 April 2007 21:23:29
INF Priority Changed to: Below Normal
SSTART newfull Backup Session: 1 Started on 22 April 2007 at 21:24:29 Version: 2.3.2 (300)
DEST newfull Backup destination: \\Server1\D\Mob3backup\full\newfull.zip
INF newfull Backing up: 107,003 Files of 29,026.00 Megabytes
INF newfull Ignoring: 8 Files
I hope the backup (zip) files still exist on the network drive so that this situation may be recovered from:
The best method is to use
Manage Backup / Remove Backup Job From List, but do not delete the actual backup. Then use the
Tools / Open Job From Backup Media option to reinstate the job from the network drive \\Server1\D\Mob3backup\full\ (open the bdb file).
If this does not reinstate the proper backup and all the backup (zip) files still exist then use the
Manage Backup / Validate (Test) Backup to recover the backup database, however, if at all possible start with the latest version of the newfull.bdb file you can find (maybe you have a copy on another backup). The zip file format does not know anything about the original disk drive files were located on, so AISBackup will re-instate ‘new’ files as orphans and ask you which drive they should be assigned to (e.g. C: drive).
Barry