About the dd method:
On Wed, 30 Sep 2009 11:30:58 -0400, Jerry McAllister wrote:
> It can be used, but it is not a good way to do it.
For regular backups or even for cloning, it's not very
performant, I agree. I'm mostly using this method for
forensic purposes, when I need a copy of a media (a
w
On Wed, Sep 30, 2009 at 05:08:05AM +0200, Polytropon wrote:
> Forgot to mention this:
>
>
> On Tue, 29 Sep 2009 22:23:00 -0400, PJ wrote:
> > 1. will the s1a slice dump the entire system, that is, the a, d, e, f
> > and g slices or is it partitions?
>
> The ad0s1 slice (containing the a, d, e,
On Tue, Sep 29, 2009 at 10:48:30PM -0400, PJ wrote:
> Polytropon wrote:
> > On Tue, 29 Sep 2009 21:26:19 -0400, PJ wrote:
> >
> >> But what does that mean? But ad2s1a has just been newfs'd - so how can
> >> it be dumped if its been formatted?
> >>
> > When you're working on this low level
On Tue, Sep 29, 2009 at 07:44:38PM -0400, PJ wrote:
> I am getting more and more confused with all the info regarding backing
> up and cloning or moving systems from disk to disk or computer to computer.
> I would like to do 2 things:
> 1. clone several instances of 7.2 from and existing installat
On Wed, 30 Sep 2009, Polytropon wrote:
On Tue, 29 Sep 2009 21:49:01 -0600 (MDT), Warren Block
wrote:
So usually I back up /, /var, and /usr to files
on a USB disk or sshfs. Then I switch to the new target system, booting
it with a FreeBSD disk and doing a minimal install. That makes sure th
On Tue, 29 Sep 2009 22:23:00 -0400, PJ wrote:
> Polytropon wrote:
>> Assuming nobody uses tape drives anymore, you need to specify
>> another file, which is the standard output in this case, which
>> may not be obvious, but it is if we reorder the command line:
>>
>> # dump -0 -L - a -u -f - /dev/
On Tue, 29 Sep 2009 21:49:01 -0600 (MDT), Warren Block
wrote:
> So usually I back up /, /var, and /usr to files
> on a USB disk or sshfs. Then I switch to the new target system, booting
> it with a FreeBSD disk and doing a minimal install. That makes sure the
> MBR is installed, gives me a c
On Wed, 30 Sep 2009, Polytropon wrote:
On Tue, 29 Sep 2009 21:37:50 -0600 (MDT), Warren Block
wrote:
Why make it harder than it needs to be? Call it / or /var or /usr
instead of /dev/ad0s1whatever. dump will handle it.
This works without problems as long as it is running from the
system t
On Tue, 29 Sep 2009, Warren Block wrote:
On Wed, 30 Sep 2009, Polytropon wrote:
On Tue, 29 Sep 2009 22:48:30 -0400, PJ wrote:
Duh I think I see where this is leading... I'm pretty sure it was
issued from / which makes it redundant, right? I should have issued it
from somewhere else, like
On Tue, 29 Sep 2009 21:37:50 -0600 (MDT), Warren Block
wrote:
> Why make it harder than it needs to be? Call it / or /var or /usr
> instead of /dev/ad0s1whatever. dump will handle it.
This works without problems as long as it is running from the
system to be copied. In case you use a live sy
On Wed, 30 Sep 2009, Polytropon wrote:
On Tue, 29 Sep 2009 22:48:30 -0400, PJ wrote:
Duh I think I see where this is leading... I'm pretty sure it was
issued from / which makes it redundant, right? I should have issued it
from somewhere else, like from home, usr or whatever but not from /
On Wed, 30 Sep 2009, Polytropon wrote:
Forgot to mention this:
On Tue, 29 Sep 2009 22:23:00 -0400, PJ wrote:
1. will the s1a slice dump the entire system, that is, the a, d, e, f
and g slices or is it partitions?
The ad0s1 slice (containing the a, d, e, f and g partitions) can
be copied 1:
On Tue, 29 Sep 2009, PJ wrote:
$ newfs -U /dev/ad2s1a
$ mount /dev/ad2s1a /target
$ cd /target
$ dump -0Lauf - /dev/ad1s1a | restore -rf -
dump is reading /dev/ad1s1a and using stdout for output.
restore is writing to the current directory (/target) and is reading
from stdin.
But what
On Tue, 29 Sep 2009 22:48:30 -0400, PJ wrote:
> Duh I think I see where this is leading... I'm pretty sure it was
> issued from / which makes it redundant, right? I should have issued it
> from somewhere else, like from home, usr or whatever but not from / as
> that is what I was trying to dum
Forgot to mention this:
On Tue, 29 Sep 2009 22:23:00 -0400, PJ wrote:
> 1. will the s1a slice dump the entire system, that is, the a, d, e, f
> and g slices or is it partitions?
The ad0s1 slice (containing the a, d, e, f and g partitions) can
be copied 1:1 with dd. By using dump + restore, the
On Tue, 29 Sep 2009 22:23:00 -0400, PJ wrote:
> I feel a bit stupid, as usual, my carelessness led me to miss the
> difference between ad1 and ad2... dumb, dumb, dumb.
As long as you realize it BEFORE any writing operation, it's
no problem. Keep in mind that the numbering of ad*, as well
as of da
Polytropon wrote:
> On Tue, 29 Sep 2009 21:26:19 -0400, PJ wrote:
>
>> But what does that mean? But ad2s1a has just been newfs'd - so how can
>> it be dumped if its been formatted?
>>
>
> When you're working on this low level, triple-check all your
> commands. Failure to do so can cause da
Olivier Nicole wrote:
$ newfs -U /dev/ad2s1a
$ mount /dev/ad2s1a /target
$ cd /target
$ dump -0Lauf - /dev/ad1s1a | restore -rf -
>>> [...]
>>>
>> But what does that mean? But ad2s1a has just been newfs'd - so how can
>>
>
> Thats ad*1*s1a that has
You are a Master among masters... extraordianry understanding of the
genre and ver, very clear explanations...
I guess my filter between the brain and the computer is a bit foggy... :-(
I really appreciate your explanations.
But I still have a couple of small questions below...
Polytropon wrote:
On Tue, 29 Sep 2009 21:26:19 -0400, PJ wrote:
> But what does that mean? But ad2s1a has just been newfs'd - so how can
> it be dumped if its been formatted?
When you're working on this low level, triple-check all your
commands. Failure to do so can cause data loss. In the example
you presented, a
On Tue, 29 Sep 2009 19:09:51 -0600 (MDT), Warren Block
wrote:
> On Wed, 30 Sep 2009, Polytropon wrote:
> >> So far, I have been unable to dump the / slice, not even with the -L
> >> option.
> >
> > Always keep in mind: Use dump only on unmounted partitions.
>
> That is unnecessary. The -L optio
> >> $ newfs -U /dev/ad2s1a
> >> $ mount /dev/ad2s1a /target
> >> $ cd /target
> >> $ dump -0Lauf - /dev/ad1s1a | restore -rf -
> >[...]
> But what does that mean? But ad2s1a has just been newfs'd - so how can
Thats ad*1*s1a that has just been formatted, not ad2...
Best,
Olivier
___
Warren Block wrote:
> On Tue, 29 Sep 2009, PJ wrote:
>
>> I am getting more and more confused with all the info regarding backing
>> up and cloning or moving systems from disk to disk or computer to
>> computer.
>> I would like to do 2 things:
>> 1. clone several instances of 7.2 from and existing
On Wed, 30 Sep 2009, Polytropon wrote:
So far, I have been unable to dump the / slice, not even with the -L
option.
Always keep in mind: Use dump only on unmounted partitions.
That is unnecessary. The -L option is there just for dumping mounted
filesystems.
-Warren Block * Rapid City, Sou
On Tue, 29 Sep 2009 19:44:38 -0400, PJ wrote:
> This may be clear to someone; it certainly is not to me.
> As I understand it, newfs will (re)format the slice.
No. The newfs program does create a new file system. In
other terminology, this can be called a formatting process.
Note that NOT a slice
On Tue, 29 Sep 2009, PJ wrote:
I am getting more and more confused with all the info regarding backing
up and cloning or moving systems from disk to disk or computer to computer.
I would like to do 2 things:
1. clone several instances of 7.2 from and existing installation
2. set up a backup scri
I am getting more and more confused with all the info regarding backing
up and cloning or moving systems from disk to disk or computer to computer.
I would like to do 2 things:
1. clone several instances of 7.2 from and existing installation
2. set up a backup script to back up changes either every
27 matches
Mail list logo
