I guess we are thinking on the same wavelength! I think that the
compressed backups would be a great idea!
On Mar 28, 2007, at 10:49 AM, Wayne Boucher wrote:
> I agree (see my email which crossed yours in the post). If people had
> some alternative big disk for backup (and who does?) that would help.
> Alternatively possibly we could just gzip everything (XML is over
> so gzip works well on it).
> On Wed, 28 Mar 2007, Johnny Eugene Croy wrote:
>> In regards to this problem that you described in which backups are
>> sometimes inconvinent, I suggested to Tim that a good idea would be
>> to have an option for an incremental backup scheme, where each backup
>> point is written to a distinct file. For example, backup #1 would be
>> written to a file called backup_001.xml and backup #2 would be
>> written to a file called backup_002.xml, etc.
>> This was a nice feature that I miss from the ANSIG days, but Tim
>> brought up a good point that each backup is a big file and people not
>> aware of this would quickly fill up a hard drive and then run into
>> more serious problems. Still, I think that it would be good for
>> people who would like to use the backup feature and have some sort of
>> way to go back in time after making a mistake or realizing that
>> something was done wrong.
>> Wayne, any thoughts?
>> - J
>> On Mar 28, 2007, at 10:31 AM, Martin Christen wrote:
>>> Thanks for the detailed explanations, Wayne.
>>> You were right again, I also had to recover
>>> the Analysis.xml file from the backup.
>>> Everything seems to work fine now but just in case,
>>> I kept a copy of the corrupted project folder.
>>> As a sidenote, I don't use the automated backup feature.
>>> I ran into the problem that it would make a backup at
>>> an undesirable time (for example, I try something that
>>> goes wrong and right after that, the autobackup decides that
>>> it's time to save - oops!), so I just make regular copies
>>> of the project folders manually instead.
>>> Thanks again!