On Mar 2, 2011, at 3:31 AM, Craig Barratt wrote: > The code continues to support the 3.x storage format, so you can > upgrade to 4.x and still access/view/restore the 3.x backups. > However, the first backup after upgrading to 4.x will need to be > a full to establish the first filled reference backup.
reading this, and the other things you've sent, I wonder if it would be better to forget about backward compatibility. given the storage efficiency it's just not a huge burden to start over. Not that I think that should be an explicit *goal*, but it sounds like this has been a hassle. Don't need a bunch of discussion on this, and I'm sure there are those who disagree with me, but keep it in mind if it gets tough. Dan Pritts, Sr. Systems Engineer Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224 ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ BackupPC-devel mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
