On Jul 22, 2011, at 2:23 PM, Jon LaBadie wrote:
On Fri, Jul 22, 2011 at 01:18:05PM -0400, myron wrote:
On Jul 22, 2011, at 1:04 PM, Frank Smith wrote:
Tar deals with filesystems, so you need to either change /dev/md0
to / (or whatever directory is mounted on it), or use dump, which
deals with devices. Personally, I'd stick with tar, but others may
prefer to use dump.
Frank
df -h reports these filesystems. So, I should have something like
this in disklist.
errol /dev/mapper/system-root linux-tar # /
errol /dev/mapper/system-home linux-tar # /home
errol /dev/mapper/system-var linux-tar # /var
errol /dev/mapper/system-scratch linux-tar # /scratch
No, as Frank said, tar needs to know what directory to
start from; dump needs to know what device to back up.
If you run "ls -lL /dev/mapper" you will see that
each of your names above are either block or character
devices (b or c as first char of line).
What you want for tar is:
errol / linux-tar
errol /home linux-tar
errol /var linux-tar
errol /scratch linux-tar
In this case the 2nd column is both what to back up
and the DLE name used in reports. You could also do
something like:
errol Root / linux-tar
errol Home /home linux-tar
errol Var /var linux-tar
errol Scratch /scratch linux-tar
In this case Root, Home, etc., when combined with the
host "errol" are the DLE name and /, /home, etc. are
where tar is to start. The combined host:name must
be unique in the disklist.
Jon
I think I understand now. We'll see how tonight's backups go.
Thanks for your help.
--
Jon H. LaBadie [email protected]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
