Re: Replacement Server w old one as Backup Hardware
- From: "Anna Clark" <anna.clark(remove this)@verizon.net>
- Date: Tue, 21 Nov 2006 20:47:07 -0500
Hi Eddie:
See in line answers below:
-Is there a good "how to" on the web for what we want to do with a second
SBS server?
Not that I know of, but maybe I will write one. Seriously, it should not be
hard.
-Is it feasable to have a second "hot spare" server that could be kept atmy
home, possibly, for use in a disaster (fire, torndao, theft, etc) at ourtake
office? My thoughts were possibly to do this at my home, periodically
the tape drive home and restore the server from the tape. We had to do a
restore a couple of years ago from tape when the drives on our production
server were destroyed by a vendor's worker that did not know what he was
doing in rebuilding a RAID array. I was impressed by how the Backup Exec
software worked!
I am not going out on a technical limb here, but I may be a little out there
re MS licensing :-) That is why I am not going to suggest that you install
SBS software on the spare ahead of time.
If you have a server (server1) from an OEM you may have OEM software. If
you already have Open License, or Retail, then ignore my comments re
licensing. That means that you would have to purchase another copy of SBS
for the second server. If you purchase a second server I would purchase it
bare, and then order SBS open license, with or without software assurance.
Mostly because I am concerned that a previous version of SBS might not play
nice with the most recent version, and because I would want the same version
on both systems.
Then look as www.sbsmigration.com to move from server1 to server2, again
because of the version differences. And you can do this at your leisure,
with just one workstation to test it. If I am mistaken about any issues
with version problems, just ask Mr. Middleton, who is the guru behind
sbsmigration.com.
Then, if your new server (server2) goes down you can install the "new" open
license software on your server1 and restore your data files and be good to
go in less than 4 hours. Depending upon the damage to "server2" (read New
Orleans here) you can then replace it and still use your open license
software on "server3".
-I know little about active directory, etc as it relates to Windows Server
2003 (I rely on my tech vendor for that). That said, I would like to have
your "expert" opinions on what we are trying to do.
Any thoughts, ideas or sources for more info?
The servers will have to be fairly close in components, or you will have to
really test this ahead of time. With SCSI or SATA using a plug in
controller rather than an onboard controller, you have a better chance of
getting it to work, since the same drives, or the same backup will work if
the controller is the same. Alternately you can install drivers for the
controller on server1 and server2. The system will ignore the unused one.
Once you get past the controller, Windows will detect the rest of it.
IMHO- go for it, budget allowing, and then test, test, test. You may find,
for example, that the network cards are enough different that you would
choose to disable the on board cards and get plug in ones, just so that they
match from server1 to server2.
Regards:
--
Anna Clark
Please do reply/post the conclusion or solution
to your issue so that others may benefit.
.
- Follow-Ups:
- Prev by Date: Re: Mail not visible in outlook
- Next by Date: Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- Previous by thread: Re: Replacement Server w old one as Backup Hardware
- Next by thread: Re: Replacement Server w old one as Backup Hardware
- Index(es):
Relevant Pages
|
