cbarratt@... writes:
> I just released BackupPC version 2.0.1 on SourceForge.
Well, that didn't work. A last minute typo caused BackupPC_tarExtract
to fail on certain file sizes. Doh! A new release 2.0.2 is now on
SourceForge.
Here's a summary of the main changes since 2.0.0:
* Fixed stupid last-minute change in octal size conversion in
Backup_tarExtract that broke 2.0.1.
* Fixed handling of >= 8GB files in BackupPC_tarExtract and >= 4GB
files in BackupPC_tarCreate.
* Removed smbclient size repair in BackupPC_tarExtract for files
between 2GB and 4GB. This means that BackupPC_tarExtract 2.0.1
doesn't behave the same as 2.0.0 for file sizes between 2GB and 4GB
extacted using smbclient 2.2.x. If you have problems backing up
files whose size is between 2GB and 4GB using smbclient 2.2.x
you should upgrade smbclient to 3.0, since it now generates
correct file sizes.
* Tested with smbclient/samba 3.0.0.
* Fixed handling of $Conf{HardLinkMax} in BackupPC/Lib.pm. Reported
by Ross Skaliotis.
* For SMB, code that detected files with a read-locked region (eg:
outlook .pst files), removed them and then tried to link with an
earlier version was broken. This code missed a step of mangling
the file names. This is now fixed. Reported by Pierre Bourgin.
* A backup of a share that has zero files is now considered
fatal. This is used to catch miscellaneous Xfer errors that
result in no files being backed up. A new config parameter
$Conf{BackupZeroFilesIsFatal} (defaults to 1) and can be set to
zero to turn off this check. Suggested by Guillaume Filion.
* SMB: now detect NT_STATUS_ACCESS_DENIED on entire share or
BackupFilesOnly (also ERRDOS - ERRnoaccess (Access denied.) for
older versions of smbclient.) Suggested by Guillaume Filion.
* SMB: now detects "tree connect failed: NT_STATUS_BAD_NETWORK_NAME" and
the dump is considered failed.
* Required File::RsyncP version is now 0.44, since File::RsyncP 0.44
fixes large file (>2GB) bugs. Large file bugs reported by Steve
Waltner.
See the ChangeLog for full details.
Enjoy!
Craig
|