[ Max Kalika wrote: ] > Hi! First of all thank you for integrating some of the fixes I sent in. > Configuring (m)buffer is now nice an convenient :)
Thanks! > I have one last issue/problem. I backup two sets to two different devices > at the same time. Doing this breaks the database because they clobber > eachother's keys at the end of their backup runs because the keys are the > same since they started at the same time. Would it make sense to prepend > the set name to the db key? or maybe use the set name as part of the db > file name? This would be similar to the separation of logs into set names. > > I realize that this can be achieved by doing a -d "index=SETNAME", but I am > wondering if that shouldn't do done as part of the code? Good point. In some intermediate versions I used a timestamp with more resolution, but the filenames etc. were more unwieldy so I dropped it. You are right that with backups to disk you can fire off more than one at the same instant, so this is a problem. I'll think it over, it does need fixing... -- Edwin Huffstutler [EMAIL PROTECTED] GnuPG Key ID: AE782DC9 ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ flexbackup-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/flexbackup-help
