-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/08/11 11:40, Holger Parplies wrote: > For what I think you have in mind I would always use a BackupPC_tarCreate > invocation. > > Of course, your preferences may vary. There might be situations where > downloading an "archive" type tar file via HTTP is both practical and the > most simple solution. In this case, you won't want a name like "restore.tar", > but you might just as well have different preferences/requirements than > whatever BackupPC is going to suggest. In my experience, deleting or > rearranging parts of overly long filename suggestions can be just as > annoying as having to fill out "obvious" information. The best solution > would be to have the suggestion customizable (as in "%h-%n-%s"), but that's > probably a lot of work for little effect (and it should strictly be a per-host > setting). As a simpler solution, I'd suggest "restore-%h-%n" (where %h is the > host name and %n the backup number) (and the .tar/.zip suffix, of course). If > the date of the backup is easily available to the code in question, I'd prefer > the date over the backup number, though there are bound to be people who have > more than one backup on the same date (happens to me if one backup is delayed > past midnight and the next one isn't). Maybe date + backup number. Remember > that even though you might only have 9 backups the backup numbers aren't > intended to wrap around, so they would still be unique for one host unless > you start over with a fresh pool.
Just a small note, I've kept quiet so far, but anyway.. I agree with most of what you say, and personally, I'd suggest the simplest change which gets the greatest benefit it the best solution here. ie, don't try to make everyone happy, just most of people :). Thus, a filename of bpc_restore_$host_$number_$share.(tar|zip) IMHO, if you selected one or more files from a single share (most cases I suspect), then you show that specific share name. If you select one or more files from multiple shares then use the share name of "multiple" or exclude the share name. Personally, I don't want the date/time of when the backup was started, completed, nor the date/time of the files/etc... all that is just a nuisance and asking for trouble with different date formats, timezones, etc... The backup number will provide enough info to go and lookup the date/time if you really need it, and/or give you a rough idea of how old the file is even if you have purged that old backup (ie, 100 backups ago is about 100 days if you do backups daily). If any date/time is really desirable, how about the date/time the restore was done (purely to keep multiple restores of the same host/etc sorted. The restore you did two hours ago compared to the restore you did 30 minutes ago... Again, though, I don't see this as all that sensible because you can always check the mtime or ctime of the file itself... Just my 0.02c... Regards, Adam - -- Adam Goryachev Website Managers www.websitemanagers.com.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5W/tQACgkQGyoxogrTyiXRWACgjNX6dDp7+i2qmHYHfSNvVPVl jAkAniDzwxt2IuwzqbHisLyLZIYLqsB5 =nCZg -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/