I run a shell script which also support NFS (I wrote it)... He's an example
email report:
It works quite well...
[23-Nov-01,19:00:00] Full backup starting...
archiving to device /dev/nst0
using a cpio blocksize of 4096
Current tape name in device : Friday-1
[23-Nov-01,19:00:40] Mounting NFS file systems for backup
Mount of NFS Volume [ OK ]: /firewall
Mount of NFS Volume [ OK ]: /firewall/boot
Mount of NFS Volume [ OK ]: /firewall/home
Mount of NFS Volume [ OK ]: /firewall/usr
Mount of NFS Volume [ OK ]: /firewall/var
[23-Nov-01,19:01:35] Pass I - writing archive...
tape name writing to device [Friday-1]
/...............................................24 block(s)
/boot............................................2 block(s)
/home.........................................1012 block(s)
/local...........................................1 block(s)
/usr...........................................465 block(s)
/var............................................66 block(s)
/citadel......................................3279 block(s)
/firewall.......................................53 block(s)
/firewall/boot...................................3 block(s)
/firewall/home.................................451 block(s)
/firewall/usr..................................548 block(s)
/firewall/var...................................43 block(s)
[23-Nov-01,22:26:43] Pass II - reading archive...
tape name read from device [Friday-1]
/...............................................24 block(s)
/boot............................................2 block(s)
/home.........................................1012 block(s)
/local...........................................1 block(s)
/usr...........................................465 block(s)
/var............................................66 block(s)
/citadel......................................3279 block(s)
/firewall.......................................53 block(s)
/firewall/boot...................................3 block(s)
/firewall/home.................................451 block(s)
/firewall/usr..................................548 block(s)
/firewall/var...................................43 block(s)
[24-Nov-01,00:53:15] Pass III - checking archive...
[24-Nov-01,00:53:29] Unmounting NFS file systems
Umount of NFS Volume [ OK ]: /firewall/usr"
Umount of NFS Volume [ OK ]: /firewall/var"
Umount of NFS Volume [ OK ]: /firewall/home"
Umount of NFS Volume [ OK ]: /firewall/boot"
Umount of NFS Volume [ OK ]: /firewall"
[24-Nov-01,00:53:42] Last successful backup: Full
to device: /dev/nst0
cpio blocking factor: 4096 bytes per block
number of files: 533082
number of blocks written: 5947
Total blocks written: 5947
Total files written: 533082
[24-Nov-01,00:53:42] Backup completed successfully.
thanks,
George Vieira
Systems Manager
Citadel Computer Systems P/L
-----Original Message-----
From: Matt Hyne [mailto:[EMAIL PROTECTED]]
Sent: Monday, 26 November 2001 2:59 PM
To: [EMAIL PROTECTED]
Subject: [SLUG] Backup solutions
I am looking at a way of doing a SIMPLE bare metal recovery plan for my
development linux box.
What I am interested in hearing is people's comments on using 'tar' or
'dump' as the backup program and why I would use one over the other. (ie
restrictions, advantages etc).
My main requirement is that I be able to restore the tape on a totally new
machine should my old machine go up in smoke. This would mean that such
things as 'dd' cannot be used since the new hard drive probably won't be the
same size as the old one.
I am currently using "tar" to backup to a QIC tape. I also have a bootable
crash-recovery CDROM that I can use to boot a new machine and then restore
the tape from.
Comments ?
Matt
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
