Timothy J. Massey wrote: > Hello! > > Short summary: it seems that whenever the file is dropped from phase 0 > of a rsyncd backup and retried in phase 1 the file does *not* show up in > the GUI. However, the file *is* actually stored in the proper > pc/<server/<path>/ directory. > > > Long description: > > I had to restore a file today. The file is a backup of an Exchange 2003 > datastore that is created by NTBACKUP running on the Exchange server. > This file, therefore, changes every day, and is ~20GB big. The server > is then backed up using rsyncd to the BackupPC server. > > It seems that there is approximately a 50% chance that I'm going to see > something like this in the log file for the BackupPC backup of this machine: > > BAK/ExchangeDataStore/ExchangeData.bkf: md4 doesn't match: will retry in > phase 1; file removed > > From my understanding, this is a normal byproduct of the way rsync > transfers files: due to hashing issues, the file will be removed from > phase 0, but will be retried in the more exhaustive phase 1. This seems > to be demonstrated in the log for such a backup. At the very end of the > log I see this: > > create 700 4294967295/401 21050720256 > BAK/ExchangeDataStore/ExchangeData.bkf > > Which seems to me to mean that the file was indeed backed up properly. > So far, so good. > > However, here's what the GUI looks like for that file in the history of > the BAK/ExchangeDataStore directory: > > History of D/BAK/ExchangeDataStore > > Backup number 27 47 59 73 87 101 107 108 > 109 110 111 112 113 > Backup time 9/19 20:00 10/26 02:00 11/20 15:09 12/4 20:00 > 12/18 20:00 > 1/1 20:00 1/7 20:00 1/8 20:00 1/9 20:00 1/10 20:00 > 1/11 20:00 1/12 > 20:00 1/13 20:00 > ExchangeData.bkf v0 v1 v2 v3 v4 v5 > v6 v7 > > > The formatting is near useless, but notice this: there are 14 backups > represented on that screen (between 27 and 113), but only *7* versions > of the file in the history. From checking the logs, it seems that > whenever the file is retried in phase 1 the file does *not* show up in > the GUI. However, if I go to the actual backuppc pc/<server>/<path> > directory, the file *is* actually in the proper directory. > > Is this a bug in the BackupPC GUI? Or am I missing something? > It is a bug, it got fixed in 3.1. I had exactly the same issue and saw it disappear in 3.1
It only happens for large files. you can still use BackuPC_Zcat to get to the files via the command line, i've never had to do it though. Regards, Les ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
