Re: Moving SCSI RAID array to new server
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Tue, 8 Nov 2005 11:35:47 +1100
Moving from SBS 4.5 to 2003 I _strongly_ recommend www.sbsmigration.com
Swing It! migration.
There is a great advantage in keeping the same NETBIOS domain and server
name. (one aspect being avoiding every office document previously created
opening slowly)
In your situation I would:
Swing It! migrate the domain.
Transfer the data to a temp holding place on the new SBS by establishing an
RDP connection with 'connect local drives' enabled thrugh the external
interfaces.
Wipe the array on the SBS 4.5 when I was satisfied the migration had
completed successfully. (including bringing up the workstations as members
of the 2003 AD, a standard part of the procedure which requires no change to
the client PCs except program updates (MS Proxy is replaced by ISA, etc)
Install the now blank array into the SBS2003, create the RAID volume, etc...
I'd also probably lose the shirty SATA drives and eventually swing the whole
installation to the SCSI array, possibly using the SATA drives for DATA, or
in a workstation where they belong.
BTW, you did buy the upgrade to SBS2003 Premium rather than 'outright
purchase' Standard, didn't you?
Also, how familiar are you with SBS 2003? If you have not yet done a full
install I (again _strongly_) recommend playing around with it a little, grab
the new box, if it's preinstalled blow the install away, set it up, come
back, ask questions, blow it away again, ask again, do it a third time.
SBS2003 is significantly different than 4.5.
"Al Williams" <donotreplydirect@xxxxxxxxxxxxxxxx> wrote in message
news:%23LYK4b$4FHA.1772@xxxxxxxxxxxxxxxxxxxxxxx
> More details:
>
> Old box: SBS 4.5 with a 2100 RAID5 array (bootable).
> New box: SBS 2003 installed on a mirrored SATA array (on board NVIDIA BIOS
> on ASUS A8N).
>
> My migration stategy is basically the MS method using ADMT. After I
> migrate the settings from the old server I just want to move the old RAID5
> array over to basically transfer the data. I will then reconfigure the
> system to eliminate unneeded data (ie: the old NT stuff) and re-organize
> the rest of the data for optimal usage (logs on SATA, exchange on RAID,
> etc.)
>
> I've verified that the 2100 is supported on Win2003, just want an idea of
> what to expect when I move the controller over.
>
> I'm hoping that the drives will simply show up (hopefully they won't blow
> away existing drive mappings), I will reset ownership & permissions and
> the data will be accessible.
>
> --
> Allan Williams
>
>
>
> "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
> news:O%23KF$3%234FHA.3276@xxxxxxxxxxxxxxxxxxxxxxx
>> Do you have SBS 2003 installed on the old array (old box)?
>>
>> It _may_ be possible to 'forklift' your whole installation to the new
>> system.
>>
>> If you just wish to move the data, yes, it is quite possible that moving
>> the controller and array to the new system will make the data available
>> almost immediately.
>>
>> gotcha
>> You can have problems (depending on the mobo bios) having two bootable
>> controllers attached. I'm pretty sure you can tell the 2100 not to be
>> bootable.
>>
>> A brief description of the new box may be in order.
>>
>> Also, notes about your 'migration' strategy may be helpful. It is quite
>> likely that if you describe what you are going from (domain or workgroup,
>> SBS existing, etc...) and how you intend getting to SBS2003 that the
>> group can advise how to avoid common pitfalls.
>>
>> "Al Williams" <donotreplydirect@xxxxxxxxxxxxxxxx> wrote in message
>> news:urlPiD94FHA.252@xxxxxxxxxxxxxxxxxxxxxxx
>>> As part of my migration I am going to move our old SCSI RAID controller
>>> (Adaptec 2100) and RAID5 array over to the new SBS2003 hardware.
>>>
>>> I am hoping it will come over intact so I can mount the original data on
>>> the new server but I am wondering if there are any gotcha's associated
>>> with doing this? Do the new drives just mount automatically or do you
>>> need to do something first? One issue I can think of is the drive
>>> letters overlap some existing ones in the new server, but I'm not sure
>>> that will be an issue.
>>>
>>> Thx
>>> --
>>> Allan Williams
>>>
>>>
>>>
>>>
>>
>>
>
>
.
- References:
- Moving SCSI RAID array to new server
- From: Al Williams
- Moving SCSI RAID array to new server
- Prev by Date: Re: change internal subnet for a SBS 2003 nework
- Next by Date: Re: Refresher in adding a new user and computer
- Previous by thread: Moving SCSI RAID array to new server
- Next by thread: Certificate Services fails to start
- Index(es):
Relevant Pages
|
