Quoting Kern Sibbald <[EMAIL PROTECTED]>:
In principle you are right, but personally, I would be a bit nervous
restoring
a 2.6 system using a 2.4 kernel. For example, there are often new features
added to newer kernels -- e.g. ext3 probably was not in kernel 2.2, so trying
to get back an ext3 system would be a bit hard. Anyway, as I say, in
principle, you are right, but good restore practice (IMO) dictates using the
best matched kernel possible.
Usually, what you do not want is restoring using newer kernel than the one
you'll be using (in case of filesystems, they usually ignore extra metadata
info, but you can't use LVM2 on kernel that only knows about LVM1 metadata
format). If you are also building software RAID devices and/or configuring
LVM, you probably also do not want too old kernel (as long as version
of MD and
LVM use same metadata format, you are OK), although things would work (you'd
only loose some newer features). Ext3 is same thing as ext2 with journaling
added (mkfs.ext3 is exactly the same thing as mkfs.ext2 -j). You can restore
onto ext2 and enable journaling after restore (tunefs -j). It might result in
.journal file being visible in root directory of the file system if you
are not
carefull (but there's a simple procedure for fixing that too, and it's mostly
cosmetic thing anyhow).
In short, it is safe as long as you know what you are doing ;-)
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
