Date: Fri, 29 May 2009 12:17:33 -0500 From: Martin McCormick <martin@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Subject: Re: Producing Bad Dumps Message-ID: <200905291717.n4THHXGA036429@dc.cis.okstate.edu>
next in thread | raw e-mail | index | archive | help
Jerry McAllister writes: > Probably you did not want the -x or -u, but instead wanted to do > cd /MOUNTED_EMPTY_PARTITION > restore -rf DUMPFILENAME That would be the ideal command. Per haps there is a better approach so I am all ears as the saying goes. I am trying to set up a procedure so that we can take another server, if necessary, format the drive with FreeBSD and then restore the contents of a dead server to this drive and have it ready to run. Of course, dd is great if both drives are the same size but usually, the only thing both servers have in common is they are both i86 systems and the goal is to try to get a platform with a melted hard drive or mother board back on line. The holy grail is a clone operation that can be documented so that a worker of reasonable knowledge can do it successfully. So, you need all the files, but they probably will not occupy a disk that looks like the original one. In that respect, tar does well but trashes special files like /dev > But, I am not sure because it is hard to understand why you chose -xu. The thought was that -u unlinks existing files so one could write the restore right over the minimal system that was there. -x was to extract / in order to get the entire root file system. Again, the idea is to recover a FreeBSD system as quickly as possible and get it back to the patch level and general operating conditions it was originally in before the hardware that supported it died. Again, many thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905291717.n4THHXGA036429>