michthro wrote:
Great idea. Much better than exporting your player too, in that copying your .dats will only be faster, and you won't have to redownload holds if the worst happens and you have to restore backups.
Well, that would depend on what you do with your backups, really. With only one HD on my box, there is little point in keeping my data on the same box (unless I start screwing up with rm * or some such). A media backup would serve, and I occasionally use those, but I don't put too much faith in these ones as I got a couple bad burns. Redudancy is good.
So, exporting the player file is a much better solution when space is limited, or for speed when *exporting* (I don't mind a slow importing much, and I don't think importing a player file takes much time). The biggest problem is, of course, having to download all those holds again. DROD 3.0 should fix that, but until then. *Shrugs*
Dats and player files don't quite serve the same purpose, I think. That, and I guess I'm biased: I can set up an automatic dat backup already in a couple seconds, so I don't need that feature, but automated player file exporting won't work out. Mmh, unless I made a custom build just for that purpose... which would be somewhat inefficient, but a good excuse to toy with the source.
[Last edited by Alneyan at 09-05-2006 09:58 PM]