At 10:02 26/06/2001 +0000, Jon LaBadie <[EMAIL PROTECTED]> wrote:
>Solaris 8, which is running on some systems I'm backing up,
>has a new feature "file system snapshots".
>
> - Create the file system snapshot.
>
> - dump the snapshot device
>
> - unmount (if necessary) and delete the snapshot
>
>Before I reinvent someones wheel, has anyone tried this?
I have just started using Linux LVM (logical volume manager) to do
something similar. I wondered about using your scheme but it was suggested
that I should leave the read-only snapshot available for 24 hours. The idea
of this is to remove the bulk of my retore requests by allowing a user to
do it themselves. While I was looking at a dump wrapper, I thought the
thing to do would be to alter run-dump and tell amanda to use that.
My approach is to:-
- remove yesterday's snapshot
- create a new snapshot
- dump the snapshot
You are right, this means the backed up directory and disk list entry are
different from the writeable place for a restore, which makes amrecover a
little fiddly to get right. This is so far only on the server which is a
combined amanda and file server. If you are looking at a client machine,
then you would need be sure that the snapshot had been correctly made
before the dump started, or you might end up backing up 24-hour old data.
Chris Ritson
--
EMAIL: [EMAIL PROTECTED] POST: Chris Ritson,
PHONE: +44 191 222 8175 Department of Computing
Science,
FAX : +44 191 222 8232 University of
Newcastle upon Tyne,
ROOM: 618 Claremont Bridge (the Mill) United Kingdom NE1 7RU.
Chris Ritson
--
EMAIL: [EMAIL PROTECTED] POST: Chris Ritson,
PHONE: +44 191 222 8175 Department of Computing
Science,
FAX : +44 191 222 8232 University of
Newcastle upon Tyne,
ROOM: 618 Claremont Bridge (the Mill) United Kingdom NE1 7RU.
Chris Ritson
--
EMAIL: [EMAIL PROTECTED] POST: Chris Ritson,
PHONE: +44 191 222 8175 Department of Computing Science,
FAX : +44 191 222 8232 University of Newcastle upon
Tyne,
ROOM: 618 Claremont Bridge (the Mill) United Kingdom NE1 7RU.
