On Tue, 14 Sep 2010 09:21:47 -0400 Brian Cuttler <[email protected]> wrote:
> On Mon, Sep 13, 2010 at 07:37:52PM -0600, John Hein wrote: > > Chris Lee wrote at 22:23 +0100 on Sep 13, 2010: > > > The way I see it the DLE is for the admin to make sub divisions > > > in the backup to make backing up easier to manage. The software > > > should store the file object with path and hostname, with the > > > DLE as an after thought; that way for the other direction of > > > recovery I only need the Date, file and hostname, the backup > > > software should do the gruntwork to find the tape required and > > > DLE if it needs to know to get my file back. > > > > What if the hostname changes - let's say just slightly (like it > > moves to a different subdomain)? I was looking for a way to have > > amanda (or tell amanda) about the history change and have > > operations (restore, incremental backup, etc.) be able to cross the > > history boundary seamlessly. > > A hostname and DLE name synonym table ? Currently the DLE consists of the host name, the path and the dump type. How about adding an optional DLE name to the disklist entries. Then as the others change over time, Amanda could track those changes. Also, that would let amrecover use DLE names. So you use a new command, setdle, which takes a DLE name. That is one step instead of the current two steps, setting the host and then the path. And less error prone. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
