Cloning Hard Drives - RemotelyTrouble cloning a Macbook Pro hard driveCloning a dieing driveDrive cloning...
Paper published similar to PhD thesis
Is there a math equivalent to the conditional ternary operator?
Why doesn't "adolescent" take any articles in "listen to adolescent agonising"?
What's the best tool for cutting holes into duct work?
Named nets not connected in Eagle board design
Is being socially reclusive okay for a graduate student?
Where do you go through passport control when transiting through another Schengen airport on your way out of the Schengen area?
Can a space-faring robot still function over a billion years?
Python 3.6+ function to ask for a multiple-choice answer
Is there a way to find out the age of climbing ropes?
Remove object from array based on array of some property of that object
If nine coins are tossed, what is the probability that the number of heads is even?
What is the meaning of option 'by' in TikZ Intersections
Is it a Cyclops number? "Nobody" knows!
Why won't the strings command stop?
Can inspiration allow the Rogue to make a Sneak Attack?
How can I be pwned if I'm not registered on the compromised site?
Why would the IRS ask for birth certificates or even audit a small tax return?
Are small insurances worth it
Can you run a ground wire from stove directly to ground pole in the ground
Affine transformation of circular arc in 3D
Problems with rounding giving too many digits
Why do we call complex numbers “numbers” but we don’t consider 2 vectors numbers?
Deal the cards to the players
Cloning Hard Drives - Remotely
Trouble cloning a Macbook Pro hard driveCloning a dieing driveDrive cloning with Rsynccloning drives to correct RAID 10 failureRemotely changing hard drive boot order, windows 7Trouble Cloning Hard Drive with ClonezillaCloning partitions of a drive to anotherCloning 64TB HD to offsite replicaCloning Hard Drive with DD May have Bricked the PC?Cloning a RAID-1 Array in Linux to a Larger Capacity Drive
I have two servers, A and B.
I would like to clone server A to B. A is running Linux, and they are both remote, I don't have a physical access to them
What is the best way to approach this?
linux clone remote-access disk-cloning
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
bumped to the homepage by Community♦ 22 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have two servers, A and B.
I would like to clone server A to B. A is running Linux, and they are both remote, I don't have a physical access to them
What is the best way to approach this?
linux clone remote-access disk-cloning
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
bumped to the homepage by Community♦ 22 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What OS B computer is running?
– jet
Apr 1 '11 at 18:30
add a comment |
I have two servers, A and B.
I would like to clone server A to B. A is running Linux, and they are both remote, I don't have a physical access to them
What is the best way to approach this?
linux clone remote-access disk-cloning
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
I have two servers, A and B.
I would like to clone server A to B. A is running Linux, and they are both remote, I don't have a physical access to them
What is the best way to approach this?
linux clone remote-access disk-cloning
linux clone remote-access disk-cloning
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
edited Aug 21 '11 at 6:52
studiohack♦
11.3k1880114
11.3k1880114
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
asked Feb 24 '11 at 23:01
soulSurfer2010soulSurfer2010
13216
13216
bumped to the homepage by Community♦ 22 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 22 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
What OS B computer is running?
– jet
Apr 1 '11 at 18:30
add a comment |
What OS B computer is running?
– jet
Apr 1 '11 at 18:30
What OS B computer is running?
– jet
Apr 1 '11 at 18:30
What OS B computer is running?
– jet
Apr 1 '11 at 18:30
add a comment |
4 Answers
4
active
oldest
votes
I believe rsync is the solution here. I am not sure whether all files will be writable during an rsync session, though...
Have you concidered making a dd clone of the partitions on server A and transferring it to server B? It sounds a bit wild, but perhaps as a last resort?
answered Feb 24 '11 at 23:22
xciterxciter
51427
add a comment |
For disk imaging, I like clonezilla, but you need physical access to boot from the disk to make it work. Honestly, I don't think you can do a completely lights-out remote full-system copy. rsync will only get you so far. If both have full systems already installed, and they are otherwise identical, then you can get the same apps installed on host B as are on host A. Then it's just a matter of copying the necessary config files from A to B. You don't necessarily need to copy everything.
answered Apr 1 '11 at 14:40
SethGSethG
1612
add a comment |
Cloning remote Linux machines
The bash script backup-images-1.0.sh automates the process of cloning disks of remote Linux machines. It uses the dd command together with ssh and gzip commands to copy and compress remote disks and send them on the fly to a local disk over an SSH connection.
Examples of cloning a remote disk to a local disk using backup-images-1.0.sh written by Radovan Brezula, who wrote backup-images-1.0.sh.
- http://brezular.com/2015/06/04/cloning-remote-linux-machines/
Example of cloning a local disk to a remote disk using dd
dd if=/path/to/disk/image ibs=4096 conv=notrunc,noerror | (ssh 132.183.12.128 dd of=/remote-archive/test/remote-archive-test.img obs=4096)
ibs=4096read up to 4096 bytes at a timeconv=notrunc,noerrordo not truncate the output file and continue after read errorsobs=4096write 4096 bytes at a time
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
add a comment |
There are al least three different ways to do this.
1 scripted setups.
This option is mostly useful in large corporations with proper documentation and likely expands into setups with PXE booting and puppet or similar setups.
Basically you repeat the same steps which you used to configure server A on server B.
This works very well if your setup is big enough (e.g. you are running 100 servers and want to spin up server 101. PXE boot, tell your puppet config that it needs to be a server of $type and come back an hour later. Done!).
A lot of work to set up, but perfect afterwards. And with all the setup work probably not worth it for copying a setup once.
2 filesystem copy.
You can copy all files from server A to server B, preserving their rights and users. rsync is probably the best tool for this.
For this you want to prepare the target server with a similar setup (e.g. copy the partition setup) and then rsync most files over. The tricky part here is that you do not want to rsync some files (e.g. skip /proc and /dev) and that you need to have something to receive the rsync files on server B.
For the last you probably want to boot server B from a different disk, or use the ILO/DRAC/.. to boot from an liveCD iso image on your desktop, leaving its disk bare and ready to receive the rsync files.
3 Copy disk.
This is diffent from copying the filesystem. It is much easier and probably a lot faster, but raw disk access (e.g. with dd) ignores all filesystem changes. This means that you really do not want to copy a running filesystem.
To help you understand this easier, imaging a book. This book has an index and four stories. The rest of the book is blank and this is also nicely indicated in the books index.
Now we start copying. We copy the index. We copy story 1, we copy...
** hold briefly, let me add a new story here and change the index**
We copy stopry 2, 3, 4 and 5...
We now have aq book with an index showing four stories (not five, since we copied that before writing story 5, and five stories)... a corrupt book.
Something similar can (and will) happen if you use raw disk access to copy a running system. So before using a raw disk copy make sure that the OS is off-line. Either boot something different (e.g. from a second disk, from a local CD, or via the network (PXE, DRAC, ...) and then copy.
Details on how to do this are already in plenty posts here on [su].
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f250024%2fcloning-hard-drives-remotely%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe rsync is the solution here. I am not sure whether all files will be writable during an rsync session, though...
Have you concidered making a dd clone of the partitions on server A and transferring it to server B? It sounds a bit wild, but perhaps as a last resort?
answered Feb 24 '11 at 23:22
xciterxciter
51427
add a comment |
I believe rsync is the solution here. I am not sure whether all files will be writable during an rsync session, though...
Have you concidered making a dd clone of the partitions on server A and transferring it to server B? It sounds a bit wild, but perhaps as a last resort?
answered Feb 24 '11 at 23:22
xciterxciter
51427
add a comment |
I believe rsync is the solution here. I am not sure whether all files will be writable during an rsync session, though...
Have you concidered making a dd clone of the partitions on server A and transferring it to server B? It sounds a bit wild, but perhaps as a last resort?
answered Feb 24 '11 at 23:22
xciterxciter
51427
I believe rsync is the solution here. I am not sure whether all files will be writable during an rsync session, though...
Have you concidered making a dd clone of the partitions on server A and transferring it to server B? It sounds a bit wild, but perhaps as a last resort?
answered Feb 24 '11 at 23:22
xciterxciter
51427
answered Feb 24 '11 at 23:22
xciterxciter
51427
answered Feb 24 '11 at 23:22
xciterxciter
51427
answered Feb 24 '11 at 23:22
xciterxciter
51427
51427
add a comment |
add a comment |
For disk imaging, I like clonezilla, but you need physical access to boot from the disk to make it work. Honestly, I don't think you can do a completely lights-out remote full-system copy. rsync will only get you so far. If both have full systems already installed, and they are otherwise identical, then you can get the same apps installed on host B as are on host A. Then it's just a matter of copying the necessary config files from A to B. You don't necessarily need to copy everything.
answered Apr 1 '11 at 14:40
SethGSethG
1612
add a comment |
For disk imaging, I like clonezilla, but you need physical access to boot from the disk to make it work. Honestly, I don't think you can do a completely lights-out remote full-system copy. rsync will only get you so far. If both have full systems already installed, and they are otherwise identical, then you can get the same apps installed on host B as are on host A. Then it's just a matter of copying the necessary config files from A to B. You don't necessarily need to copy everything.
answered Apr 1 '11 at 14:40
SethGSethG
1612
add a comment |
For disk imaging, I like clonezilla, but you need physical access to boot from the disk to make it work. Honestly, I don't think you can do a completely lights-out remote full-system copy. rsync will only get you so far. If both have full systems already installed, and they are otherwise identical, then you can get the same apps installed on host B as are on host A. Then it's just a matter of copying the necessary config files from A to B. You don't necessarily need to copy everything.
answered Apr 1 '11 at 14:40
SethGSethG
1612
For disk imaging, I like clonezilla, but you need physical access to boot from the disk to make it work. Honestly, I don't think you can do a completely lights-out remote full-system copy. rsync will only get you so far. If both have full systems already installed, and they are otherwise identical, then you can get the same apps installed on host B as are on host A. Then it's just a matter of copying the necessary config files from A to B. You don't necessarily need to copy everything.
answered Apr 1 '11 at 14:40
SethGSethG
1612
answered Apr 1 '11 at 14:40
SethGSethG
1612
answered Apr 1 '11 at 14:40
SethGSethG
1612
answered Apr 1 '11 at 14:40
SethGSethG
1612
1612
add a comment |
add a comment |
Cloning remote Linux machines
The bash script backup-images-1.0.sh automates the process of cloning disks of remote Linux machines. It uses the dd command together with ssh and gzip commands to copy and compress remote disks and send them on the fly to a local disk over an SSH connection.
Examples of cloning a remote disk to a local disk using backup-images-1.0.sh written by Radovan Brezula, who wrote backup-images-1.0.sh.
- http://brezular.com/2015/06/04/cloning-remote-linux-machines/
Example of cloning a local disk to a remote disk using dd
dd if=/path/to/disk/image ibs=4096 conv=notrunc,noerror | (ssh 132.183.12.128 dd of=/remote-archive/test/remote-archive-test.img obs=4096)
ibs=4096read up to 4096 bytes at a timeconv=notrunc,noerrordo not truncate the output file and continue after read errorsobs=4096write 4096 bytes at a time
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
add a comment |
Cloning remote Linux machines
The bash script backup-images-1.0.sh automates the process of cloning disks of remote Linux machines. It uses the dd command together with ssh and gzip commands to copy and compress remote disks and send them on the fly to a local disk over an SSH connection.
Examples of cloning a remote disk to a local disk using backup-images-1.0.sh written by Radovan Brezula, who wrote backup-images-1.0.sh.
- http://brezular.com/2015/06/04/cloning-remote-linux-machines/
Example of cloning a local disk to a remote disk using dd
dd if=/path/to/disk/image ibs=4096 conv=notrunc,noerror | (ssh 132.183.12.128 dd of=/remote-archive/test/remote-archive-test.img obs=4096)
ibs=4096read up to 4096 bytes at a timeconv=notrunc,noerrordo not truncate the output file and continue after read errorsobs=4096write 4096 bytes at a time
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
add a comment |
Cloning remote Linux machines
The bash script backup-images-1.0.sh automates the process of cloning disks of remote Linux machines. It uses the dd command together with ssh and gzip commands to copy and compress remote disks and send them on the fly to a local disk over an SSH connection.
Examples of cloning a remote disk to a local disk using backup-images-1.0.sh written by Radovan Brezula, who wrote backup-images-1.0.sh.
- http://brezular.com/2015/06/04/cloning-remote-linux-machines/
Example of cloning a local disk to a remote disk using dd
dd if=/path/to/disk/image ibs=4096 conv=notrunc,noerror | (ssh 132.183.12.128 dd of=/remote-archive/test/remote-archive-test.img obs=4096)
ibs=4096read up to 4096 bytes at a timeconv=notrunc,noerrordo not truncate the output file and continue after read errorsobs=4096write 4096 bytes at a time
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
Cloning remote Linux machines
The bash script backup-images-1.0.sh automates the process of cloning disks of remote Linux machines. It uses the dd command together with ssh and gzip commands to copy and compress remote disks and send them on the fly to a local disk over an SSH connection.
Examples of cloning a remote disk to a local disk using backup-images-1.0.sh written by Radovan Brezula, who wrote backup-images-1.0.sh.
- http://brezular.com/2015/06/04/cloning-remote-linux-machines/
Example of cloning a local disk to a remote disk using dd
dd if=/path/to/disk/image ibs=4096 conv=notrunc,noerror | (ssh 132.183.12.128 dd of=/remote-archive/test/remote-archive-test.img obs=4096)
ibs=4096read up to 4096 bytes at a timeconv=notrunc,noerrordo not truncate the output file and continue after read errorsobs=4096write 4096 bytes at a time
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
edited Oct 8 '15 at 13:57
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
answered Oct 8 '15 at 13:42
karelkarel
9,27293139
9,27293139
add a comment |
add a comment |
There are al least three different ways to do this.
1 scripted setups.
This option is mostly useful in large corporations with proper documentation and likely expands into setups with PXE booting and puppet or similar setups.
Basically you repeat the same steps which you used to configure server A on server B.
This works very well if your setup is big enough (e.g. you are running 100 servers and want to spin up server 101. PXE boot, tell your puppet config that it needs to be a server of $type and come back an hour later. Done!).
A lot of work to set up, but perfect afterwards. And with all the setup work probably not worth it for copying a setup once.
2 filesystem copy.
You can copy all files from server A to server B, preserving their rights and users. rsync is probably the best tool for this.
For this you want to prepare the target server with a similar setup (e.g. copy the partition setup) and then rsync most files over. The tricky part here is that you do not want to rsync some files (e.g. skip /proc and /dev) and that you need to have something to receive the rsync files on server B.
For the last you probably want to boot server B from a different disk, or use the ILO/DRAC/.. to boot from an liveCD iso image on your desktop, leaving its disk bare and ready to receive the rsync files.
3 Copy disk.
This is diffent from copying the filesystem. It is much easier and probably a lot faster, but raw disk access (e.g. with dd) ignores all filesystem changes. This means that you really do not want to copy a running filesystem.
To help you understand this easier, imaging a book. This book has an index and four stories. The rest of the book is blank and this is also nicely indicated in the books index.
Now we start copying. We copy the index. We copy story 1, we copy...
** hold briefly, let me add a new story here and change the index**
We copy stopry 2, 3, 4 and 5...
We now have aq book with an index showing four stories (not five, since we copied that before writing story 5, and five stories)... a corrupt book.
Something similar can (and will) happen if you use raw disk access to copy a running system. So before using a raw disk copy make sure that the OS is off-line. Either boot something different (e.g. from a second disk, from a local CD, or via the network (PXE, DRAC, ...) and then copy.
Details on how to do this are already in plenty posts here on [su].
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
add a comment |
There are al least three different ways to do this.
1 scripted setups.
This option is mostly useful in large corporations with proper documentation and likely expands into setups with PXE booting and puppet or similar setups.
Basically you repeat the same steps which you used to configure server A on server B.
This works very well if your setup is big enough (e.g. you are running 100 servers and want to spin up server 101. PXE boot, tell your puppet config that it needs to be a server of $type and come back an hour later. Done!).
A lot of work to set up, but perfect afterwards. And with all the setup work probably not worth it for copying a setup once.
2 filesystem copy.
You can copy all files from server A to server B, preserving their rights and users. rsync is probably the best tool for this.
For this you want to prepare the target server with a similar setup (e.g. copy the partition setup) and then rsync most files over. The tricky part here is that you do not want to rsync some files (e.g. skip /proc and /dev) and that you need to have something to receive the rsync files on server B.
For the last you probably want to boot server B from a different disk, or use the ILO/DRAC/.. to boot from an liveCD iso image on your desktop, leaving its disk bare and ready to receive the rsync files.
3 Copy disk.
This is diffent from copying the filesystem. It is much easier and probably a lot faster, but raw disk access (e.g. with dd) ignores all filesystem changes. This means that you really do not want to copy a running filesystem.
To help you understand this easier, imaging a book. This book has an index and four stories. The rest of the book is blank and this is also nicely indicated in the books index.
Now we start copying. We copy the index. We copy story 1, we copy...
** hold briefly, let me add a new story here and change the index**
We copy stopry 2, 3, 4 and 5...
We now have aq book with an index showing four stories (not five, since we copied that before writing story 5, and five stories)... a corrupt book.
Something similar can (and will) happen if you use raw disk access to copy a running system. So before using a raw disk copy make sure that the OS is off-line. Either boot something different (e.g. from a second disk, from a local CD, or via the network (PXE, DRAC, ...) and then copy.
Details on how to do this are already in plenty posts here on [su].
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
add a comment |
There are al least three different ways to do this.
1 scripted setups.
This option is mostly useful in large corporations with proper documentation and likely expands into setups with PXE booting and puppet or similar setups.
Basically you repeat the same steps which you used to configure server A on server B.
This works very well if your setup is big enough (e.g. you are running 100 servers and want to spin up server 101. PXE boot, tell your puppet config that it needs to be a server of $type and come back an hour later. Done!).
A lot of work to set up, but perfect afterwards. And with all the setup work probably not worth it for copying a setup once.
2 filesystem copy.
You can copy all files from server A to server B, preserving their rights and users. rsync is probably the best tool for this.
For this you want to prepare the target server with a similar setup (e.g. copy the partition setup) and then rsync most files over. The tricky part here is that you do not want to rsync some files (e.g. skip /proc and /dev) and that you need to have something to receive the rsync files on server B.
For the last you probably want to boot server B from a different disk, or use the ILO/DRAC/.. to boot from an liveCD iso image on your desktop, leaving its disk bare and ready to receive the rsync files.
3 Copy disk.
This is diffent from copying the filesystem. It is much easier and probably a lot faster, but raw disk access (e.g. with dd) ignores all filesystem changes. This means that you really do not want to copy a running filesystem.
To help you understand this easier, imaging a book. This book has an index and four stories. The rest of the book is blank and this is also nicely indicated in the books index.
Now we start copying. We copy the index. We copy story 1, we copy...
** hold briefly, let me add a new story here and change the index**
We copy stopry 2, 3, 4 and 5...
We now have aq book with an index showing four stories (not five, since we copied that before writing story 5, and five stories)... a corrupt book.
Something similar can (and will) happen if you use raw disk access to copy a running system. So before using a raw disk copy make sure that the OS is off-line. Either boot something different (e.g. from a second disk, from a local CD, or via the network (PXE, DRAC, ...) and then copy.
Details on how to do this are already in plenty posts here on [su].
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
There are al least three different ways to do this.
1 scripted setups.
This option is mostly useful in large corporations with proper documentation and likely expands into setups with PXE booting and puppet or similar setups.
Basically you repeat the same steps which you used to configure server A on server B.
This works very well if your setup is big enough (e.g. you are running 100 servers and want to spin up server 101. PXE boot, tell your puppet config that it needs to be a server of $type and come back an hour later. Done!).
A lot of work to set up, but perfect afterwards. And with all the setup work probably not worth it for copying a setup once.
2 filesystem copy.
You can copy all files from server A to server B, preserving their rights and users. rsync is probably the best tool for this.
For this you want to prepare the target server with a similar setup (e.g. copy the partition setup) and then rsync most files over. The tricky part here is that you do not want to rsync some files (e.g. skip /proc and /dev) and that you need to have something to receive the rsync files on server B.
For the last you probably want to boot server B from a different disk, or use the ILO/DRAC/.. to boot from an liveCD iso image on your desktop, leaving its disk bare and ready to receive the rsync files.
3 Copy disk.
This is diffent from copying the filesystem. It is much easier and probably a lot faster, but raw disk access (e.g. with dd) ignores all filesystem changes. This means that you really do not want to copy a running filesystem.
To help you understand this easier, imaging a book. This book has an index and four stories. The rest of the book is blank and this is also nicely indicated in the books index.
Now we start copying. We copy the index. We copy story 1, we copy...
** hold briefly, let me add a new story here and change the index**
We copy stopry 2, 3, 4 and 5...
We now have aq book with an index showing four stories (not five, since we copied that before writing story 5, and five stories)... a corrupt book.
Something similar can (and will) happen if you use raw disk access to copy a running system. So before using a raw disk copy make sure that the OS is off-line. Either boot something different (e.g. from a second disk, from a local CD, or via the network (PXE, DRAC, ...) and then copy.
Details on how to do this are already in plenty posts here on [su].
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
answered Oct 8 '15 at 14:52
HennesHennes
59.2k793142
59.2k793142
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f250024%2fcloning-hard-drives-remotely%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What OS B computer is running?
– jet
Apr 1 '11 at 18:30