|
Re: Move disk without loosing backup history?
2008-08-28 10:16:31
Gene Heskett wrote:
On Thursday 28 August 2008, Toralf Lund wrote:
I've just moved a disk from one server to another without really
changing anything with respect to how the clients see it; logically, the
disk still represents exactly the same volume on the network. [... ]
Unforch, what I'd call a bug in tar will cause it to be treated as a new
device. Part of tar's detection code makes the device's assigned number part
of the new/old decision. So it will be subjected to a full level 0 backup as
a newly discovered disk.
This is not really a problem. But I don't think I follow you. Perhaps I
wasn't clear enough in my original post; the disk is physically the same
as before, it's the *host* that has changed. I'd really like the DLE in
question to list the actual host it's connected to, and not some client
that mounts the volume, so as to avoid sending the same data twice
across the network. But if I change the DLE just like that, Amanda will
think I'm backing up a new disk (won't it?), so I'll get two separate
indexes for what's exactly the same disk, and if I want to recover a
really old file, I need to remember to switch to the old index/hostname.
Which is something I'd rather avoid.
I'm mainly talking about an "archival" config without tape reuse, by the
way. And yes, I do keep amanda indexes "from the beginning of time" for
those, as the way I see it, without these, the tapes would be pretty
much useless, since nobody would remember what was supposed to be on them...
- Toralf
|
|
|
