Re: Is this a viable backup/restore strategy?
From: Michael Solomon \(MS-MVP Windows Shell/User\) (user_at_#notme.com)
Date: 09/09/04
- Next message: Michael Solomon \(MS-MVP Windows Shell/User\): "Re: Is this a viable backup/restore strategy?"
- Previous message: Fred Goodwin, CMA: "Re: ME to XP: delete restore files?"
- In reply to: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Next in thread: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Reply: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 9 Sep 2004 14:59:38 -0700
Ah, I see, PC 2 would be the storage location for the PC 1 backup and you
would then restore the back to PC 1 by way of the new disk. For this
purpose, imaging would work fine.
That said, I have to go along with the person who suggested restore over a
network. I have a two PC network and I store a copy of my backup as well as
image file copies on the secondary system. It's much easier for me to copy
the necessary files across the network and then restore. It would seem to
be a lot of extra work to connect the drive to the backup PC, do all the
copying or restoring, then disconnect the drive and then reconnect to PC 1.
I think the network solution is much simpler if they are connected. Beyond
that, some imaging software might allow you to send the image file when you
create it to the networked PC, another step saver. As to ntbackup, in terms
of options, it's a bit limited. I can't say for sure if it would work or
tell you the file is missing or can't be used for some reason. I'm not
saying it wouldn't work, I just haven't tried that specifically with
ntbackup and there are more robust applications that have far greater
flexibility. Ntbackup is actually a minimalist version of Backup MyPC,
distributed by Stomp: http://www.stompinc.com/index.phtml?stp and created by
Veritas who now only distributes to enterprise customers.
In principle, I think what you describe should work but I think it would be
simpler if you networked the two machines.
-- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "Jeff W" <msnews@Kwcpa.com> wrote in message news:eykjSIrlEHA.2340@TK2MSFTNGP11.phx.gbl... > Sorry michael - my guess is you mis understood my idea; > > On PC #1 - do the backups, store them on PC #2 > when the disk on PC #1 crashes, add a new disk to PC #2 > On PC #2, do a restore to the new disk > THIS ASSUMES I CAN RESTORE THE SYSTEM STATE TO THE NEW DISK AND NOT ITS > ORIGINAL LOCATION - is this the flaw? > move the new disk from PC #2 to PC #1 and boot. > > make more sense? > /j > > > > Michael Solomon (MS-MVP Windows Shell/User) wrote: > >>Because the System State contains hardware references that wouldn't exist >>on >>the new system. >> >>You would need to run a repair install because XP was originally installed >>on another machine. Aside from all the other different hardware, it is a >>different motherboard and moving the hard drive to the new motherboard >>requires a repair install in order for XP to properly recognize it as well >>as any other new hardware. >> >> >>
- Next message: Michael Solomon \(MS-MVP Windows Shell/User\): "Re: Is this a viable backup/restore strategy?"
- Previous message: Fred Goodwin, CMA: "Re: ME to XP: delete restore files?"
- In reply to: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Next in thread: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Reply: Jeff W: "Re: Is this a viable backup/restore strategy?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
