Re: Casper 4.0 cloning Win XP Pro SP3, SATA internal 0 to SATA intern
- From: "Anna" <myname@xxxxxxxxx>
- Date: Sat, 2 Feb 2008 23:21:27 -0500
<D975XBX2Blue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D25F6AA0-503A-4ED8-BB08-621593BABF69@xxxxxxxxxxxxxxxx
I've been reading these posts here for a couple of days now. I'm new to
the
discussion group community so please forgive any protocol mistakes. I've
read
a lot information similar to my situation, but I wanted to ask about my
system specifically.
There seems to be some pretty knowledgeable folks here in the Win XP Pro
cloning department. I need some feedback and technical advice on cloning a
new install of Win XP Pro. It's taken me countless nights and weekends to
get
this OS tweaked to a state of stability and usefulness and I want to save
it.
When I built the system, I had the good sense to install one SATA 250 GB
HDD
first (port 0). When I got all of the hardware operational, I loaded the
neccessary third party RAID drivers (Marvell and Intel) to support the
eight
SATA ports on my MOB. AFTER I insalled the OS and got everything running
smoothly, I installed a SECOND 250 GB HDD (port 1), went into the Computer
Management Console and 'enabled' the second drive, and nothing else. The
(0)
disk is listed as 'Basic' NTFS, and the (1) disk is listed as 'Dynamic'
unallocated. Now it's just sitting there waiting for someone smarter than
I
am to help me use it!
Q1: Isn't it true that in a RAID system, there is a "Redundant Array" of
drives for the OS and data, but only ONE of these drives contains the
critical MBR? Even though I have RAID capability on this machine, I
really
like the simplicity and security of being able to run cloning software and
copy the entire contents of the primary SATA (0) drive, MBR included, to
the
second SATA (1) drive and be able to remove this drive and store it
seperately from the machine.
Q2: In the event of a failure of the primary drive, I could then re-insert
the cloned drive and boot up without any proprietary software or rescue
disks?
Q3: Is using the Casper 4.0 software possible in this physical
configuration, SATA 0 to SATA 1 ?
Any thoughts about my overall logic, or technical advice on how to do what
I'm attempting, would be much appreciated.
Vegetarian is an old Cherokee word. It means 'Poor Hunter'
--
D975XBX2 Blue
D9...
First of all I note your post's subject-line indicates that you're
apparently working with the XP Pro OS including the SP3 "Release Candidate"
or what many of us commonly refer to as a "beta" release. I would recommend
that at this time you work with *only* the XP Pro OS with the SP2 update and
wait until the final (non-beta) version of SP3 is released before installing
that new SP onto your OS. The final release should be forthcoming within the
next few months.
Anyway it seems apparent from your post that you're not really interested in
establishing a RAID configuration but just want to use your secondary SATA
HDD, the 250 GB one connected to your SATA1 connector (actually apparently
the second SATA connector on your motherboard) as the recipient of the
cloned contents of day-to-day boot drive, the SATA HDD connected to the
SATA0 connector on your motherboard. Do I have all this right as to your
basic objective?
If so, there's no reason why you can't use the Casper 4.0 program that you
mention to achieve your objective. We do this nearly every day.
Are you having some problem in doing so or are you just exploring the
possibility of using the Casper program in the way you want to?
As I've indicated this is a straightforward operation; Casper will see your
boot drive as the "source" drive and identify your secondary HDD as the
"destination" drive. So it's a simple matter to clone the contents of your
source disk to the destination disk. We highly recommend the Casper 4.0
program for basic disk-to-disk cloning purposes.
I'm assuming your overall objective is to establish & maintain a
comprehensive backup system and do so on a routine basis. If this be the
case it would surely be awkward to remove your destination HDD (the
recipient of the clone) from the system following every disk-cloning
operation. I can't imagine your doing this on any routine basis.
Given your objective, would it not be more practical to simply purchase a
USB-SATA enclosure designed to house your secondary SATA HDD and just clone
the contents of your boot drive to the external HDD on a routine basis?
Should your internal HDD fail or the OS become so corrupt that the system is
unbootable you could then (again using the Casper 4.0 program), either clone
the contents of the external HDD to the internal HDD for
recovery/restoration purposes or remove the SATA HDD from its enclosure and
install it as the new boot drive. Either way, a relatively simple &
straightforward process.
And should your motherboard contain a eSATA port, that would be even better
since it would accommodate SATA-to-SATA connectivity using a SATA external
enclosure designed for that purpose.
And in the event your system does not have an eSATA port there's another
option available involving fitting a SATA (or eSATA) adapter to the
backplane of your computer case and using an external SATA enclosure to
provide SATA-to-SATA connectivity, always a desirable objective.
You might even want to consider simply leaving your secondary HDD connected
as an internal HDD in your system and just use it as the destination drive
for the cloned contents of your boot drive. Obviously there's a certain risk
there but we know many users who prefer that configuration. Of course your
BIOS boot order priority setting would indicate the SATA HDD connected to
the SATA0 connector as first in boot order among your HDDs. Naturally for
safety's sake it's always preferable to use an external device as the
recipient of the clone rather than a continuously connected internal HDD.
Anna
.
- Prev by Date: Re: Hard Disk Drive 0 not found...
- Next by Date: Re: Program C:/Program Files/Internet Explorer/iexplore.exe
- Previous by thread: Re: Casper 4.0 cloning Win XP Pro SP3, RAID issue
- Next by thread: Hard Disk Drive 0 not found...
- Index(es):
Relevant Pages
|
