Matt Hyne wrote:
>
> 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).
tar can restore to any filesystem type, dump is restricted
to the filesystem type used to create the dump.
dump can backup meta-data known only to the filesystem.
For example, the ext2 filesystem attributes or the xfs
storage management information. You need to make other
arrangements to record and restore these (eg for ext2:
"lsattr -R / > /e2attr.txt" before running tar).
Neither tar nor dump can backup a running database. You
either need to use the backup facility provided by the
database, dump the database to SQL [2], or stop the DBMS during
the backup. This can also apply to applications with
backend DBMSs, such as some LDAP servers.
Glen
[2] You need to test this option, some DBMS's won't dump
the commnads to create the tables and indexes; these
dumps don't work too well for restores.
--
Glen Turner Network Engineer
(08) 8303 3936 Australian Academic and Research Network
[EMAIL PROTECTED] http://www.aarnet.edu.au/
--
The revolution will not be televised, it will be digitised
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
