On Tue, Sep 14, 2010 at 10:32:55AM -0600, Charles Curley wrote: > 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.
I wonder if rather than tracking name changes in a synonym table, an additional parameter, if present (default value is "host/dle") you could use a DLE-IDentifier field, essentially a new DLE label. When thor /export/zone comp-user becomes odin /export/zones comp-user where in the first case the missing first field is assumed, giving an effective thor_/export_zone thor /export/zone comp-user and after the change over the new entry should look like thor_/export_zone oldin /export/zones comp-user ** Choose your own syntax. I was thinking 'labels' so collumn one but actual implemention depends on what is happening under the hood and what makes sense in practice. === On a different topic, if you have spindles shared across hosts and want to use spindle numbers to avoid contention a possible solution is a new optional disklist parameter for host or spindle groups. ...because I have work to do in DNS... > > > -- > > 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 --- Brian R Cuttler [email protected] Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
