From owner-freebsd-questions Tue Jan 5 09:14:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08303 for freebsd-questions-outgoing; Tue, 5 Jan 1999 09:14:16 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from loviatar.webcom.com (loviatar.webcom.com [209.1.28.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08298 for ; Tue, 5 Jan 1999 09:14:15 -0800 (PST) (envelope-from graeme@echidna.com) Received: from kigal.webcom.com (kigal.webcom.com [209.1.28.57]) by loviatar.webcom.com (8.9.1/8.9.1) with SMTP id JAA09038 for ; Tue, 5 Jan 1999 09:13:37 -0800 Received: from [204.143.69.51] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 16181371; Tue Jan 05 09:11 PST 1999 Message-Id: <36924895.5807@echidna.com> Date: Tue, 05 Jan 1999 12:15:01 -0500 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win95; I) Mime-Version: 1.0 To: FreeBSD Questions Cc: Graeme@echidna.com Subject: Transferring all data from old to new boot drive Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a 2.2.7S/CAM system in which I need to replace the hard drive which serves as the boot drive (with /, most of /usr, /var, /tmp) by a new hard drive. There is a second drive in this system with plenty of free space. So I would like to transfer the contents of the boot drive to this and subsequently restore to the new drive, preserving the current state of original installation exactly. What is the best way to do this? The system has a Adaptec 7890 SCSI controller, so my understanding is I can't use a standard 2.2.7 boot floppy. I'm assuming I can use 3.0 boot and fixit floppies, and use these to create the filesystems on the new disk, and then transfer all the contents of a backup from the second disk. In particular, I'm assuming that whatever I do with 3.0 here (disklabel, making filesystems, restoring files) is compatible with 2.2.7. I tried tarring the whole drive with # tar cf /usr/backup/all.tar / When I restore to a test directory like /usr/test with /usr/test# tar xpf /usr/backup/all.tar the contents of the disk seem to be restored correctly under /usr/test with a couple of exceptions (or at least, these are the ones I noticed): (a) The kernel flags (normally shcg) are not set. Does tar not know about file flags? Are there any other places files normally have flags set? I read Elizabeth Zwicky's backup article (http://reality.sgi.com/zwicky_neu/testdump.doc.html), and it doesn't seem to mention file flags at all! (b) During the tar create operation, tar complains about a whole slew of /dev/* files, saying (e.g.) "tar: /dev/wd0s3: minor number too large; not dumped". Consequently some 50 odd device nodes are not recreated when untarring. How should these be handled? (c) Some files are untarred onto /proc - presumably I should get rid of these. I guess it would be best to not have the /proc files (other than the directory itself?) in the archive, but I don't know how to do this in a straightforward way. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message